05-21-2011
In my humble opinion nothing good comes when file and directory names contain spaces. Not only is it a pain each time you enter the file/directory name on the command line, as you've discovered, scripts tend not to quote variables containing filenames and will break from similar problems. Use underbars (_) or dots (.) and avoid using spaces at all costs.
Again, this is my opinion, but one I do feel strongly about.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Sorry for my poor english.
Unix is SCO ODT ver 3.0
Mine problem is :
when I login via some terminal emulator and type :
who am i
I see information like this :
username ttyp02 Feb 28 09:53
after logoff and type who command (from some other terminal)
I see that ttyp02 is still... (2 Replies)
Discussion started by: bane_yu
2 Replies
2. UNIX for Dummies Questions & Answers
I have a problem to....
(1).List the number of unique users that has active
processes.
(2).List the number of active processes for each of
the users in (1).
(3).Determine total memory usage for each user.
Help me please....thank you.
Best... (2 Replies)
Discussion started by: robocup
2 Replies
3. Shell Programming and Scripting
Hi, folks.
Sorry for bothering, but maybe someone could help me please.
The problem is the following:
there is some script that copies files from local file system to AFS. The copying is performed with dd command.
The script copies data into some AFS volumes.
The problem appeared with one... (0 Replies)
Discussion started by: Anta
0 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I am triying to make sure that there exists only one file with the pattern abc* in path /path/. This directory is having many huge files. If there is only one file then I have to take its complete name only to use furter in my script.
I am planning to do like this:
if ; then... (2 Replies)
Discussion started by: new_learner
2 Replies
5. Solaris
Hi all
I use to run sql loader inside a script with usename and password written in syntax. Now when I use 'ps' command to know about the status of loading, it also shows username and password that I don't want to share with someone who is sitting with me. If you have any idea except encryption... (1 Reply)
Discussion started by: sanjay1979
1 Replies
6. Shell Programming and Scripting
Hello, excuse me for my english, i'm a french man.
I have a problem with the command tr in applescript (with the accent...in french we have a lot of accents), i have read that is a problem with the version 10.5 of leopard then i would want to download the version 10.4 of universal binary of tr... (1 Reply)
Discussion started by: protocomm
1 Replies
7. Red Hat
Please help me this script !!!!
Script
*****
a=2.0.0.0
b=1.0.0.0
#if test $a -ge $b
if
then
echo "A is Greater than B"
else
echo "B is Greater than A"
fi
i am getting following error
>sh abc
abc: line 6: [: 2.0.0.0: integer expression expected (8 Replies)
Discussion started by: ponmuthu
8 Replies
8. Shell Programming and Scripting
Hi guys,
first of all I would say that this is my first time I write in a Forum.
I've read the "forum rules" and I hope i will respect them.
I searched everywhere for the solution of my problem but I didn't find anything.
Here my problem:
I'm using a sap job scheduler: in a particular job... (7 Replies)
Discussion started by: Antcam
7 Replies
9. Shell Programming and Scripting
Hi friends,
Today I found one strange behaviour of the tr command.
I used the following command:
echo "NEE"|tr
Sometimes it was giving "nee" as ouput . sometimes it was giving "NEE" as output.
Finally I used the below code:
echo "NEE"|tr "" ""
... and it gave me the correct... (17 Replies)
Discussion started by: neelmani
17 Replies
10. AIX
exec(): 0509-036 Cannot load program /usr/opt/freeware/bin/rpm because of the following errors:
0509-022 Cannot load module /opt/freeware/lib/libintl.a(libintl.so.1).
0509-150 Dependent module /opt/freeware/lib/libiconv.a(shr4.o) could not be loaded.
0509-152 Member... (4 Replies)
Discussion started by: Ohmkar
4 Replies
LEARN ABOUT REDHAT
mkmanifest
mkmanifest(1) General Commands Manual mkmanifest(1)
Name
mkmanifest - makes list of file names and their DOS 8+3 equivalent
Note of warning
This manpage has been automatically generated from mtools's texinfo documentation, and may not be entirely accurate or complete. See the
end of this man page for details.
Description
The mkmanifest command is used to create a shell script (packing list) to restore Unix filenames. Its syntax is:
mkmanifest [ files ]
Mkmanifest creates a shell script that aids in the restoration of Unix filenames that got clobbered by the MS-DOS filename restrictions.
MS-DOS filenames are restricted to 8 character names, 3 character extensions, upper case only, no device names, and no illegal characters.
The mkmanifest program is compatible with the methods used in pcomm, arc, and mtools to change perfectly good Unix filenames to fit the MS-
DOS restrictions. This command is only useful if the target system which will read the diskette cannot handle vfat long names.
Example
You want to copy the following Unix files to a MS-DOS diskette (using the mcopy command).
very_long_name
2.many.dots
illegal:
good.c
prn.dev
Capital
Mcopy converts the names to:
very_lon
2xmany.dot
illegalx
good.c
xprn.dev
capital
The command:
mkmanifest very_long_name 2.many.dots illegal: good.c prn.dev Capital >manifest
would produce the following:
mv very_lon very_long_name
mv 2xmany.dot 2.many.dots
mv illegalx illegal:
mv xprn.dev prn.dev
mv capital Capital
Notice that "good.c" did not require any conversion, so it did not appear in the output.
Suppose I've copied these files from the diskette to another Unix system, and I now want the files back to their original names. If the
file "manifest" (the output captured above) was sent along with those files, it could be used to convert the filenames.
Bugs
The short names generated by mkmanifest follow the old convention (from mtools-2.0.7) and not the one from Windows 95 and mtools-3.0.
See Also
Mtools' texinfo doc
Viewing the texi doc
This manpage has been automatically generated from mtools's texinfo documentation. However, this process is only approximative, and some
items, such as crossreferences, footnotes and indices are lost in this translation process. Indeed, these items have no appropriate repre-
sentation in the manpage format. Moreover, not all information has been translated into the manpage version. Thus I strongly advise you
to use the original texinfo doc. See the end of this manpage for instructions how to view the texinfo doc.
* To generate a printable copy from the texinfo doc, run the following commands:
./configure; make dvi; dvips mtools.dvi
* To generate a html copy, run:
./configure; make html
A premade html can be found at: `http://mtools.linux.lu' and also at: `http://www.tux.org/pub/knaff/mtools'
* To generate an info copy (browsable using emacs' info mode), run:
./configure; make info
The texinfo doc looks most pretty when printed or as html. Indeed, in the info version certain examples are difficult to read due to the
quoting conventions used in info.
mtools-3.9.8 02Jun01 mkmanifest(1)