| |||||||||||||
|
| |||||||||||||
profiles?profiles?Posted Apr 23, 2007 12:23 UTC (Mon) by NAR (subscriber, #1313)In reply to: profiles? by eru Parent article: OpenSUSE to drop ZENworks Well, the boot manager could pass a command line to the kernel, which would be ignored by the kernel, but the init scripts could read it from the /proc/cmdline and could do different things depending on this parameter... Our local IT staff uses a (very limited) solution like this, so the laptops have "network" and "standalone" menu items in lilo.
(Log in to post comments)
Kernel command line usage Posted Apr 24, 2007 5:54 UTC (Tue) by eru (subscriber, #2753) [Link] Interesting! I always thought the kernel command line is available only for passing options to the kernel itself. But how can I make sure that any extra 'profile' options placed on the command line are not intercepted by the kernel (not now, nor in the future when new kernel options are added)?
Kernel command line usage Posted Apr 24, 2007 22:11 UTC (Tue) by nix (subscriber, #2304) [Link] You, um, can't. A number of things (notably arch-dependent things) getinvolved even before the initramfs runs, and can consume args as they wish. (Adding extra arguments is *very* useful for initramfses and initrds; arguments to mount root filesystems in unusual ways, to run emergency repair shells just before or just after mounting root, and, well, to trigger anything else you can think of).
However, it's quite unlikely that a random argument you pick will
|
|
||||||||||||