New option for ln, firmlinks!

2004-01-24 Thread Alfred M. Szmidt
Howdy, The following hack implements the --firm/-m option for ln so that it will create firm links. Now, most GNU/Linux people won't be familiar with the concept, and I'm not really sure how to explain it either. The best example I can think of that explains the difference between symlinks and fi

Re: New option for ln, firmlinks!

2004-01-24 Thread Andreas Schwab
"Alfred M. Szmidt" <[EMAIL PROTECTED]> writes: > Howdy, > > The following hack implements the --firm/-m option for ln so that it > will create firm links. Now, most GNU/Linux people won't be familiar > with the concept, and I'm not really sure how to explain it either. > The best example I can th

Re: New option for ln, firmlinks!

2004-01-24 Thread Alfred M. Szmidt
> hurd:/home/ams/coreutils/coreutils/src# ./ln -s /ams/foo symlink > hurd:/home/ams/coreutils/coreutils/src# ./ln -m /ams/foo firmlink > hurd:/home/ams/coreutils/coreutils/src# cd symlink > hurd:/home/ams/coreutils/coreutils/src/symlink# ls .. > foo hurd.obj lost+found oskit.obj

Re: ls --color feature request: ordinary files uncoloured

2004-01-24 Thread Ed Avis
Jim Meyering <[EMAIL PROTECTED]> wrote: >>I think it would be better for plain files to not have any ANSI >>escape sequences around them, and for colouring to apply only to >>directories, *.gz and so on. >>Shall I send a patch for this? > >Please do. diff -ru coreutils-5.0.91/src/ls.c coreutils-

Re: bug in hostname

2004-01-24 Thread Bob Proulx
Paul Jarc wrote: > A hostname program does not need to talk to the network at all. The > kernel keeps exactly one hostname in memory, and the hostname program > gets/sets it via gethostname()/sethostname(). It's fine to also > provide access to any names found in DNS, but that isn't central. Par

Re: New option for ln, firmlinks!

2004-01-24 Thread Andreas Schwab
"Alfred M. Szmidt" <[EMAIL PROTECTED]> writes: >> hurd:/home/ams/coreutils/coreutils/src# ./ln -s /ams/foo symlink >> hurd:/home/ams/coreutils/coreutils/src# ./ln -m /ams/foo firmlink >> hurd:/home/ams/coreutils/coreutils/src# cd symlink >> hurd:/home/ams/coreutils/coreutils/src/sy

Re: New option for ln, firmlinks!

2004-01-24 Thread Alfred M. Szmidt
I don't know much about union file-systems, but AFAIK they are different from bind mounts. A bind mount is created by "mount -o bind /foo /bar" and causes the tree under /foo to be overlayed over /bar, with the former contents of /bar being hidden. It's like a regular mount, except

Re: New option for ln, firmlinks!

2004-01-24 Thread Andreas Schwab
"Alfred M. Szmidt" <[EMAIL PROTECTED]> writes: >I don't know much about union file-systems, but AFAIK they are >different from bind mounts. A bind mount is created by "mount -o >bind /foo /bar" and causes the tree under /foo to be overlayed over >/bar, with the former contents of

Re: New option for ln, firmlinks!

2004-01-24 Thread Alfred M. Szmidt
You can also bind-mount a regular file (and probably other types, I didn't try yet). The only difference to firmlinks is, at it seems, that the destination must already exist and it must be of the same type as the source. Not entirerly true, the source and destination aren't the same

Re: New option for ln, firmlinks!

2004-01-24 Thread Andreas Schwab
"Alfred M. Szmidt" <[EMAIL PROTECTED]> writes: >You can also bind-mount a regular file (and probably other types, I >didn't try yet). The only difference to firmlinks is, at it seems, >that the destination must already exist and it must be of the same >type as the source. > > Not

Re: New option for ln, firmlinks!

2004-01-24 Thread Alfred M. Szmidt
> Was it possible to jump out of a chroot with bind's? Not sure what you mean. A bind-mountpoint behaves like any other mountpoint. Well, can you do the something along the following with bind-mountpoints (using settrans to be clear): $ settrans -ac /new-root/etc /hurd/firmlink /etc $

Re: New option for ln, firmlinks!

2004-01-24 Thread Andreas Schwab
"Alfred M. Szmidt" <[EMAIL PROTECTED]> writes: > Well, can you do the something along the following with > bind-mountpoints (using settrans to be clear): > > $ settrans -ac /new-root/etc /hurd/firmlink /etc > $ chroot /new-root > $ cat /etc/passwd > > And get the content of REAL-ROOT/etc/passwd fo

Re: New option for ln, firmlinks!

2004-01-24 Thread Alfred M. Szmidt
> Well, can you do the something along the following with > bind-mountpoints (using settrans to be clear): > > $ settrans -ac /new-root/etc /hurd/firmlink /etc > $ chroot /new-root > $ cat /etc/passwd > > And get the content of REAL-ROOT/etc/passwd for example? Yes. The

Re: bug in hostname

2004-01-24 Thread Paul Jarc
[EMAIL PROTECTED] (Bob Proulx) wrote: > But the -f, --fqdn in particular must use DNS if the real hostname > is not already fully qualified. Well, that's one way it can try to go about it. There's also getdomainname(), on systems that have it, or uname(). One might also argue that it would be re

coreutils-5.1.2 released

2004-01-24 Thread Jim Meyering
This is a bug-fix-only release. I hope to make a `stable' release pretty soon, so if you know of any outstanding bugs, please report (or re-report) them ASAP. Here are the compressed sources: ftp://alpha.gnu.org/gnu/coreutils/coreutils-5.1.2.tar.gz (6.2MB) ftp://alpha.gnu.org/gnu/coreutils/