| 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: <20080306115315.GA8972@elf.ucw.cz> Date: Thu, 6 Mar 2008 12:53:17 +0100 From: Pavel Machek <pavel@....cz> To: Ingo Molnar <mingo@...e.hu> Cc: Chris Wedgwood <cw@...f.org>, Pawel Plociennik <paplociennik@...il.com>, linux-kernel@...r.kernel.org Subject: Re: [PATCH 2.6.24] chroot= as a new kernel parameter On Thu 2008-03-06 12:37:29, Ingo Molnar wrote: > > * Chris Wedgwood <cw@...f.org> wrote: > > > > But given an existing initrd (which might have come from the distro, > > > etc.) i prefer adding boot options instead of modifying the initrd. > > > > I assume this is so you have have /distro1 /distro2 and use your boot > > option to (help) select which one you boot into? > > while i have no personal use for chroot=, i generally test distros that > way, yes - and i try to keep them as unmodified as possible. > > "Use the initrd as an extended boot commandline" is a poor answer IMO. > > _Everything_ we do on the boot commandline that affects user-space can > be done in an initrd in theory - but still we have hundreds of boot > options. Yes, please. chroot= is useful, nonintrusive, and it just should be there. -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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