On Sat, Jan 24, 2004 at 06:51:53PM +0100, Alfred M. Szmidt wrote:
> 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
> 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
"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
> 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
$
"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
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
"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
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
"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
> 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
"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
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
12 matches
Mail list logo
