| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <200803081710.24137.a1426z@gawab.com> Date: Sat, 8 Mar 2008 17:10:24 +0300 From: Al Boldi <a1426z@...ab.com> To: linux-kernel@...r.kernel.org Subject: Re: [PATCH 2.6.24] chroot= as a new kernel parameter Christian Kujau wrote: > On Fri, 7 Mar 2008, devzero@....de wrote: > >> * H. Peter Anvin <hpa@...or.com> wrote: > >>> init=/path/to/any/sbin/chroot /newroot /sbin/init > > Great, I was looking for something like this myself some time ago! > > > wouldn`t it be useful to add a hint to kernel-parameters.txt ? > > How about: > > init= [KNL] > - Format: <full_path> > + Format: <full_path> <options> > Run specified binary instead of /sbin/init as init > - process. > + process. init= is able to take more than one option > + allowing us to do: > + init=/path/to/any/sbin/chroot /newroot /sbin/init > + ...and thus booting into /newroot. Nice try, but this only works on the surface. Try remounting root to see what I mean. Now, for a patch that actually does what we want, try this: [PATCH][retry-2] init: Introduce rootdir bootparm to select which dir to sys_chroot Thanks! -- Al -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists