08-28-2002
First, I think it good that we have a link to the open group. We stayed pretty much on the high road and that's good for everyone, including us.
Second, I agree with jj25 that we should modify the open group post to include mention of the version 3 link. I just visited that link. I did not know that the standard was available via the web. I'll bet that a lot of other people didn't know that either. That was a very useful link. Thanks, jj25.
7 More Discussions You Might Find Interesting
1. Solaris
Hi there
I have a backup script that runs every night and for some reason ive been getting in in the morning and the process has died, Is there any way I can tell when it died? if not .....would anybody recommend some scripting that i could do that would be able to tell me this information
... (3 Replies)
Discussion started by: hcclnoodles
3 Replies
2. UNIX for Dummies Questions & Answers
I am using SunOS 5.7
I have installed Python 2.5 via make install
Without going into details, I'd like to uninstall it and replace it with an earlier version. Maybe as far back as 2.2.3. Unfortuantely, make uninstall gives me Don't know how to make target 'uninstall'. This is thematically... (2 Replies)
Discussion started by: Dbecker
2 Replies
3. Shell Programming and Scripting
two things.
why doesn't the 'die' message get displayed - "Error: release log directory creation failed..."?
why does the script name and line number get displayed despite the inclusion of a '\n'. apparently adding a newline prevents this from happening.
if (! -d "$logdir") {
use... (4 Replies)
Discussion started by: mjays
4 Replies
4. Shell Programming and Scripting
I have a perl program that I want to read from a file passed as an argument or from a pipe. If their is no pipe or arguments, I want it to output a help message. I am stuck on how to prevent perl from reading from the keyboard if it isn't fed any file names or data from a pipe. The only things I... (4 Replies)
Discussion started by: ilikecows
4 Replies
5. Post Here to Contact Site Administrators and Moderators
First of all, I want to thank everyone who runs this forum for the fine job they've done. While I myself have not yet had any need for help, I have enjoyed and learned while helping others.
Due diligence disclaimer: I searched for a discussion on this issue, using "tynt" and "copy paste", but... (11 Replies)
Discussion started by: alister
11 Replies
6. Shell Programming and Scripting
Hi,
I will ftp aroung 80 files after connecting to an FTP Server. But after 2 minutes of connection, it is timed out and connection is dying. Server had a 2 minute connection timeout if connection is idle. But my question, Isn't tranfering files not considered as an activity. Is the connection... (7 Replies)
Discussion started by: vasuarjula
7 Replies
7. What is on Your Mind?
Update: UserCP Screeching Frog 0.7641 - Changed Live Chat to Live Updates
In this version of the UserCP, I have changed "Live Chat" to "Live Updates" by disabling the ability to post in the "live chat" area and changed the name to "Live Updates"
The reason for this change is that experienced... (6 Replies)
Discussion started by: Neo
6 Replies
LN(1) General Commands Manual LN(1)
NAME
ln - make links
SYNOPSIS
ln [ -s ] sourcename [ targetname ]
ln [ -s ] sourcename1 sourcename2 [ sourcename3 ... ] targetdirectory
DESCRIPTION
A link is a directory entry referring to a file; the same file (together with its size, all its protection information, etc.) may have
several links to it. There are two kinds of links: hard links and symbolic links.
By default ln makes hard links. A hard link to a file is indistinguishable from the original directory entry; any changes to a file are
effective independent of the name used to reference the file. Hard links may not span file systems and may not refer to directories.
The -s option causes ln to create symbolic links. A symbolic link contains the name of the file to which it is linked. The referenced
file is used when an open(2) operation is performed on the link. A stat(2) on a symbolic link will return the linked-to file; an lstat(2)
must be done to obtain information about the link. The readlink(2) call may be used to read the contents of a symbolic link. Symbolic
links may span file systems and may refer to directories.
Given one or two arguments, ln creates a link to an existing file sourcename. If targetname is given, the link has that name; targetname
may also be a directory in which to place the link; otherwise it is placed in the current directory. If only the directory is specified,
the link will be made to the last component of sourcename.
Given more than two arguments, ln makes links in targetdirectory to all the named source files. The links made will have the same name as
the files being linked to.
SEE ALSO
rm(1), cp(1), mv(1), link(2), readlink(2), stat(2), symlink(2)
4th Berkeley Distribution April 10, 1986 LN(1)