04-21-2008
Well, I do not know why you are naming those files that way. At least not with the info you are providing us with... But I can tell you how to manage with those files. Two options, as far as I know:
- Name them using a back slash before the white space:
ls K6A80403125051.prn\ :res\ 2330479869879093344\ ext\ 2330477052380546512\ align
- Use quotes:
ls "K6A80403125051.prn :res 2330479869879093344 ext 2330477052380546512 align"
Back to the reason for that filenames, how are them being created? by a script? program? Tell us, so that we can help you.
Regards.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have a problem I don't understand... I am trying to declare a variable, and then output the results of that variable, couldn't be simpler
#!/bin/ksh
VAR='Oranges'
if
then
echo "Found Lemons"
elif
then
echo "Found Oranges"
fi
The output shouold clearly be "Found Oranges", but... (2 Replies)
Discussion started by: danhodges99
2 Replies
2. Solaris
Greetings To All!
I am running Solaris 10 in a sparc environment.
Here is the deal:
In /var/spool/cron/crontabs, there is a cron user named "sys". If I do a
crontab -l sys, it returns:
# 0 * * * 0-6 /usr/lib/sa/sa1
# 20,40 8-17 * * 1-5 /usr/lib/sa/sa1
# 5 18 * * 1-5 /usr/lib/sa/sa2... (8 Replies)
Discussion started by: RobSand
8 Replies
3. Shell Programming and Scripting
I am trying to find the difference in days between 2 dates.
I have to extract the 1st date from a filename, which i did using the awk command.
I have to compare this date to today's date and if the difference is greater than 30 days, do something, else do something else.
This is what i wrote... (22 Replies)
Discussion started by: meeraKh
22 Replies
4. UNIX for Advanced & Expert Users
Hi,
I've Ubuntu 8.04, and it has some files that I just cannot delete. I've tried everything, inode, fsck etc.
Here is what the ls -li outputs
root@ubuntu:/home/luser/.local/share/Trash/files/junk# ls -l
ls: cannot access TRUNK_: No such file or directory
ls: cannot access 2006_output.mv:... (11 Replies)
Discussion started by: nitin
11 Replies
5. Infrastructure Monitoring
Hi,
I want to install net-snmp-devel package but i have following dependecy problem.
It's very odd, i don't get it. One of packages is depended on the other one, the other one is depended on the previous one as well. :S :S
Could you help me please?
Here are the steps:
# ls -l
total... (4 Replies)
Discussion started by: oduth
4 Replies
6. Shell Programming and Scripting
sqlLogftp_mov=$LOGDIR/logftp_mov_$mydate.log
sqlplus -s $ORAUSER << EOF > $sqlLogftp_mov
SET SERVEROUT ON
@/$SCRIPTDIR/rep_comm_ext_tbl_load.sql
EOF
retorno=0
cnt=`grep -q 'ORA-' $sqlLogftp_mov | wc -l`
if ;
then
retorno=1
echo 'Failure'
sendEmailFalha
exit 1
fi
if ;
then
echo... (8 Replies)
Discussion started by: shyamaladevi
8 Replies
7. UNIX for Dummies Questions & Answers
Hi.
First post, and Linux newbie, so maybe I'm missing something obvious:
I have a Synology NAS that is run by a Linux distribution (which?). I have had an external hard drive connected to the NAS for making backups using Synology's backup application Time Backup.
Time Backup is based on... (3 Replies)
Discussion started by: Pokersut
3 Replies
8. Shell Programming and Scripting
awk 'BEGIN{print 1.2.3.4}'
1.20.30.4
Can anyone explain why has extra "0" in the IP address? (3 Replies)
Discussion started by: newoz
3 Replies
9. UNIX for Dummies Questions & Answers
I have a weird issue going on with the join command...
I have two files I am trying to join...here is a line from each file with the important parts marked in red:
file1:
/groupspace/ccops/cmis/bauwkrcn/commsamp_20140315.txt,1
file2:... (3 Replies)
Discussion started by: dbiggied
3 Replies
10. Shell Programming and Scripting
Hi,
I have a simple awk script:
BEGIN{}
{
$a=$2-$1;
print $a
}
END{if(NR==0){
print "0"
}
}
to which I provide the following input
2.9 14
22.2 27 (4 Replies)
Discussion started by: jamie_123
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)