On Dec 1, 2006, at 9:30 AM, Jean-Paul Natola wrote:
Please excuse my ignorance but I believe my symlink is not working,
how can I
verify a symlink?
Most people use ls -l to see where the link is pointing; software
generally uses lstat(2).
And Yes I am a newbie in the BSD / open source
Additionally, find filenamecan tell you if a symbolic link is broken:
% ln -s ./linksource ./linkdest
% file linkdest
linkdest: broken symbolic link to `./linksource'
(In this case linksource simply doesn't exist...)
___
freebsd-questions@freebsd.org
Additionally, find filenamecan tell you if a symbolic link is broken:
% ln -s ./linksource ./linkdest
% file linkdest
linkdest: broken symbolic link to `./linksource'
(In this case linksource simply doesn't exist...)
Uh-oh too much data - not processing-
Maybe if I explain what I was doing-
On Dec 1, 2006, at 10:38 AM, Jean-Paul Natola wrote:
I wanted to have the /var/spool/exim/ subdirecotries (scan , input db,
msglog) run in the /usr slice (as it has ample space)
So I MOVED exim to /usr/var2 and ran
ln -s /var/spool/exim /usr/var2/exim
but I don't think that's right
Yep.
Make sure that your exim data really resides in /usr/var2/exim.
Afterwards, remove /var/spool/exim.
The ln command won't remove any existing files and directories, but it
doesn't complain in this case. And then you have to take care where
you specify source and destination: The source is an
On 01/12/06, Christian Walther [EMAIL PROTECTED] wrote:
The ln command won't remove any existing files and directories, but it
doesn't complain in this case.
Forget it, of course it does complain...
___
freebsd-questions@freebsd.org mailing list
Make sure that your exim data really resides in /usr/var2/exim.
Afterwards, remove /var/spool/exim.
The ln command won't remove any existing files and directories, but it
doesn't complain in this case. And then you have to take care where
you specify source and destination: The source is an
On Fri, Dec 01, 2006 at 12:30:51PM -0500, Jean-Paul Natola wrote:
Please excuse my ignorance but I believe my symlink is not working, how can I
verify a symlink?
Just use it and see what happens.
If it is a symlink to a directory, then do a cd to it.
If it is to a text file, do a vi or
On Fri, Dec 01, 2006 at 09:35:23AM -0800, Chuck Swiger wrote:
On Dec 1, 2006, at 9:30 AM, Jean-Paul Natola wrote:
Please excuse my ignorance but I believe my symlink is not working,
how can I
verify a symlink?
Most people use ls -l to see where the link is pointing; software
generally
You create this link (presuming all dirs exist).
'ln -s /some/other/dir/goodstuff /stuff'
Then do 'cd /stuff'
...textfile
You can use any text editor you like if vi is not to your taste
(though you should at least learn how to use vi since it is so omnipresent
in the UNIX world)
Jean-Paul Natola wrote:
Please excuse my ignorance but I believe my symlink is not working, how can I
verify a symlink?
And Yes I am a newbie in the BSD / open source world.
Jean-Paul Natola
Network Administrator
Information Technology
Family Care International
588 Broadway Suite 503
On Thu, Jul 08, 2004 at 02:40:30PM -0700, Andrew Musselman wrote:
Hello; I'm new to this list.
I've looked and still can't find the path to the command symlink. It
has a man page, but I can't find it. Any suggestions?
symlink has a manpage entry in Section 2, which relates to FreeBSD
In the last episode (Jul 08), Andrew Musselman said:
I've looked and still can't find the path to the command symlink.
It has a man page, but I can't find it. Any suggestions?
That manpage is for the C library function symlink(). The shell
command is ln, which handles both hard and symbolic
Andrew Musselman [EMAIL PROTECTED] wrote:
Hello; I'm new to this list.
I've looked and still can't find the path to the command symlink. It
has a man page, but I can't find it. Any suggestions?
As already described, symlink is for use in code.
If you look at the SEE ALSO section of that
Hello; I'm new to this list.
I've looked and still can't find the path to the command symlink. It
has a man page, but I can't find it. Any suggestions?
Probably what you are looking for is:a link -s
as in:
link -s file_to_link name_of_link
symlink is a library routine
Hello; I'm new to this list.
I've looked and still can't find the path to the command symlink. It
has a man page, but I can't find it. Any suggestions?
Oops, I think I just wrote link -s in the last message
and it should be ln -s
Am hurrying trying to leave, sorry,
jerry
Thanks,
On Wednesday 12 November 2003 20:38, Marty Landman wrote:
At 03:00 PM 11/12/2003, you wrote:
# ln -s /home/steve/directory /tmp/directory
# rm /tmp/directory
In testing, the original directory (/home/steve/directory) did not get
removed
I'm a newbie Steve so maybe will be asking more
On Wednesday 12 November 2003 19:48, Steve Bertrand wrote:
Could someone please briefly describe the reactions to the following
actions? Sometimes I delete the original directories by deleting links,
and hopefully someone can give me some insight.
# ln -s /home/steve/directory /tmp/directory
# ln -s /usr/X11R6 /home/steve/X11R6
Which put a new link from the original to the new location.
If I # rm /home/steve/X11R6, will I be safe as to not delete the original
directory?
I'm sorry, the above line should have read:
# rm /usr/X11R6
not the other way around. In essence, if
19 matches
Mail list logo
