[Bug 201486] Re: add boot argument to allow legacy change_root removal
maximilian attems
maks at debian.org
Fri Jul 8 14:23:36 UTC 2011
initrd-tools is long gone, thus closing.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/201486
Title:
add boot argument to allow legacy change_root removal
Status in “initramfs-tools” package in Ubuntu:
Fix Released
Bug description:
Binary package hint: initramfs-tools
In Linux 2.6 the change_root method of invoking initrd is considered
"legacy", and might be removed in future. The new method is
pivot_root, which does not have any special case code paths in kernel
for initrd after it's block device /dev/ram0 is created. The kernel
should be booted "vmlinux root=/dev/ram0" which will mount the initrd,
and execute /sbin/init.
At present, this is problematic for initrd-tools (Gutsy), since there
is no way to specify the "real" root filesystem that is desired,
without using root= kernel commandline argument.
I propose a new argument be interpreted by initrd-tools /init script,
to allow migration to a fixed "root=/dev/ram0" on all kernels using
initrd to mount the real root device. There is precedent with
rdinit=, although "rdroot=/dev/sda1" seems counterintuitive.
Alternatives should be considered that are not confusing. Perhaps
root2=, realroot=, or some other form.
Parsing the new argument could be conditional on finding
"root=/dev/ram0" in kernel commandline, to make things more precise.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/201486/+subscriptions
More information about the foundations-bugs
mailing list