Umm... that may be what he wants (probably is), but it isn't what would
happen. I belive that the VFS code checks for file existance and
permissions (of the directory, except in non sitckybit directories) before
calling sb->s_ops->unlink. I could well be wrong here.
> And, we can be even more clever than that. By using:
> # mount -t devfs -o explicit none /gaol/dev
> # mknod /gaol/dev/null c 0 0
> # mknod /gaol/dev/zero c 0 0
>
> we can ensure that *only* dev/null and dev/zero will exist in the
> chroot environment. In other words, you don't need to know which
> devices *may* be possible. This is even better than pre-emptively
> removing entries.
Exactly, and this shouldn't be difficult.
> Regards,
> Richard....
-- Agent K: A person is smart; people are dumb, panicky animals and you know it. Fifteen hundred years ago, everybody knew that the Earth was the center of the Universe. Five hundred years ago, everybody knew that the Earth was flat. Fifteen minutes ago, you knew that humans were alone on this planet. Just think what you'll know tomorrow.-=- Men In Black (1997, Paramount)