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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1277553549.29791.38.camel@fermat.scientia.net>
Date:	Sat, 26 Jun 2010 13:59:09 +0200
From:	Christoph Anton Mitterer <calestyo@...entia.net>
To:	linux-kernel@...r.kernel.org
Subject: (stupid) how to specify the root-device via kernel parameters

Hi,...

Ok this might sound really stupid, but I've seen several ways of doing
this and want to get this cleaned up.

Nevertheless....

kernel-parameters.txt has the following options where you can specify
the root-fs and related flags:
root=           [KNL] Root filesystem
nfsroot=        [NFS] nfs root filesystem for disk-less boxes.

Plus further options like: ro, rootdelay=, rootflags=, rootfstype=,
rootwait, etc.


My question:
These are intended (especially root/nfsroot) to really name the device,
on which the filesystem directly lays, right?
E.g. if the ext4-root-fs is on /dev/sda1,... => root=/dev/sda1

I've seen several initramfs scripts (which I'd like to fix),... where
people abuse this or misuse this in setups where a root-fs is used on
multi-stacked block layers (e.g. something like disk->lvm->dm-crypt->fs)


Cheers,
Chris.

--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ