>Couldn't you easily hack by just creating a program called "modprobe"
>in a directory called "sbin", and chrooting to the parent directory
>of "sbin"? Meaning:
>user bonehead does:
>~bonehead:>mkdir sbin
>~bonehead:>cp hack sbin/modprobe
>~bonehead:>chroot ~bonehead (program that would cause a modprobe)
>The above is fairly simple. Howe does the kernel handle this? Because
>the kernel is affected by a chroot.
This would have been trivial to try before posting to this list.
Had you done that, you would have discovered that you have to be
the superuser to use chroot.
Adam J. Richter __ ______________ 4880 Stevens Creek Blvd, Suite 205
adam@yggdrasil.com \ / San Jose, California 95129-1034
+1 408 261-6630 | g g d r a s i l United States of America
fax +1 408 261-6631 "Free Software For The Rest Of Us."
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu