04-26-2005
Quote:
grep ls (this is where I am most stuck - adding the ‘mail/' before each name and a carriage return as the delimiter) > .mailboxlist (??)
Unix uses a newline as a line terminator, not a carriage return. This tend to happen automatically. You need to do stuff to suppress it, not get it.
ls | sed 's=^=mail/=' > .mailboxlist
will do what I think you want. If you need something else, tell us what os and shell you are using.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I have a problem with syntax methinks, when it comes to sed.
This is my script for a user to type sed commands:-
yes=y
function writefunction
{
$tool $command $newfilename $filename
}
echo
echo
echo "1. Type the name of the tool you are using i.e sed."
read tool
echo... (3 Replies)
Discussion started by: Trufla
3 Replies
2. Shell Programming and Scripting
I am new to shell scripting and would appreciate any help I can get.
I need to write a Unix shell script that I will run whenever I have a tar file to uncompress(Korn shell). Please put in mind that I have different environements that I will run it on.
Thanks in advance ;) (4 Replies)
Discussion started by: nkem22
4 Replies
3. UNIX for Dummies Questions & Answers
thanks guys i managed to answer (0 Replies)
Discussion started by: bebop1111116
0 Replies
4. Shell Programming and Scripting
I'm getting the following errors when I try to write a script to unzip some zip files. When I use the free trial copy of the commerical winzip program, however, they work fine. When I use -l or -t on unzip it indicates no errors. When I use the -o switch interactively from the bash command line it... (1 Reply)
Discussion started by: siegfried
1 Replies
5. Shell Programming and Scripting
I need to get files names passed to a script. Here number of files passed may vary
like MyScript.ksh file1 file2 file3..... so on
I am writting script somthing like this
set -A Files
while (i<=$#)
do
File=$i
let i=i+1
done
Is this correct way doing this. Is there any other way.... (5 Replies)
Discussion started by: unishiva
5 Replies
6. Shell Programming and Scripting
Hi,
I am new to scripting, so any help on this would be much appreciated.
I am trying to rename a bunch of files, taking the names sequentially from a list read in another file...
# ls oldnames
file_1
file_2
file_3
# cat names
red
yellow
green
I want the files to take on the... (6 Replies)
Discussion started by: starsky
6 Replies
7. Shell Programming and Scripting
can anyone help me in writing script in UNIX for copying files in two server from the third server after checking the files in the third server and if there is anything new in the third server automatically it should be added to the rest of the two servers and if same file is existing in the two... (4 Replies)
Discussion started by: REKHA09
4 Replies
8. Shell Programming and Scripting
I would like to find whether a file exists in the UNIX machine. That i can check using
if ;then
echo "exists"
echo " `cat $file` "
else
echo "invalid file"
fi.
and i can find out using :
find / -name "filename" . But it i have wanted to search in all directories. How to get... (3 Replies)
Discussion started by: rparsa001
3 Replies
9. UNIX for Dummies Questions & Answers
Hi
Here is my script that calls my awk script
#!/bin/bash
set -x
dir="/var/local/dsx/csv"
testfile="$testfile"
while getopts " f: " option
do
case $option in
f ) testfile="$OPTARG";;
esac;
done
./scriptFile --testfile=$testfile >> $dir/$testfile.csv
It calls my awk... (1 Reply)
Discussion started by: ladyAnne
1 Replies
10. UNIX for Dummies Questions & Answers
Hi,
I would like to write a loop to change the names of files in a directory. The files are called data1.txt through data1000.txt. I'd like to change their names to a1.txt through a1000.txt. How do I go about doing that? Thanks! (2 Replies)
Discussion started by: evelibertine
2 Replies
OPEN(5) File Formats Manual OPEN(5)
NAME
open, create - prepare a fid for I/O on an existing or new file
SYNOPSIS
Topen tag[2] fid[2] mode[1]
Ropen tag[2] fid[2] qid[8]
Tcreate tag[2] fid[2] name[28] perm[4] mode[1]
Rcreate tag[2] fid[2] qid[8]
DESCRIPTION
The open request asks the file server to check permissions and prepare a fid for I/O with subsequent read and write messages. The mode
field determines the type of I/O: 0, 1, 2, and 3 mean read access, write access, read and write access, and execute access, to be checked
against the permissions for the file. In addition, if mode has the OTRUNC (0x10) bit set, the file is to be truncated, which requires
write permission (if the file is append-only, and permission is granted, the open succeeds but the file will not be truncated); if the mode
has the ORCLOSE (0x40) bit set, the file is to be removed when the fid is clunked, which requires permission to remove the file from its
directory. If other bits are set in mode they will be ignored. It is illegal to write a directory, truncate it, or attempt to remove it
on close. If the file is marked for exclusive use (see stat(5)), only one client can have the file open at any time. That is, after such
a file has been opened, no other open will succeed until fid has been clunked. All these permissions are checked at the time of the open
request; subsequent changes to the permissions of files do not affect the ability to read, write, or remove an open file.
The create request asks the file server to create a new file with the name supplied, in the directory (dir) represented by fid, and
requires write permission in the directory. The owner of the file is the implied user id of the request, the group of the file is the same
as dir, and the permissions are the value of
(perm&(~0777|0111)) | (dir.perm&perm&0666)
if a regular file is being created and
(perm&~0777) | (dir.perm&perm&0777)
if a directory is being created. This means, for example, that if the create allows read permission to others, but the containing direc-
tory does not, then the created file will not allow others to read the file.
Finally, the newly created file is opened according to mode, and fid will represent the newly opened file. Mode is not checked against the
permissions in perm. The qid for the new file is returned with the create reply message.
Directories are created by setting the CHDIR bit (0x80000000) in the perm.
The names . and .. are special; it is illegal to create files with these names.
It is an error for either of these messages if the fid is already the product of a successful open or create message.
An attempt to create a file in a directory where the given name already exists will be rejected; in this case, the create system call (see
open(2)) uses open with truncation. The algorithm used by create is: first walk to the directory to contain the file. If that fails,
return an error. Next walk to the specified file. If the walk succeeds, send a request to open and truncate the file and return the
result, successful or not. If the walk fails, send a create message. If that fails, it may be because the file was created by another
process after the previous walk failed, so (once) try the walk and open again. For the behavior of create on a union directory, see
bind(2).
ENTRY POINTS
Open and create both generate open messages; only create generates a create message.
OPEN(5)