On May 11, 2005, at 11:18 AM, Ed Howland wrote:
Also, what I don't grok very well is how the various boot options get passed arround. Like how does setting options for screen geometry in the knoppix boot loader affect X which doesn't happen until latter in the boot process when the init scripts are running.
My guess, and only a guess, is that something later in the boot process reads /proc/cmdline and parses out the options that the process is interested in. One way to test it would be the following:
- positive control: boot into runlevel 5 with some X boot options (e.g. xmodule=fbdev)
- negative control: boot into runlevel 5 without some X boot options
- boot into runlevel 2 with some X boot options, remove them from / proc/cmdline, then init 5
- boot into runlevel 2 without some X boot options, add them to / proc/cmdline, then init 5
I don't know if it is possible to modify the /proc/cmdline, but it would be cool to try.
So much to learn, so little time to learn it. An entire semester's course could be taught detailing the boot process in various OS's (from Windows to Unix to Linux (various distros) and MacOSX) This could come under the hading of system admin, home customization or security.
No kidding.
Regards, - Robert http://www.cwelug.org/downloads Help others get OpenSource software. Distribute FLOSS for Windows, Linux, *BSD, and MacOS X with BitTorrent
_______________________________________________ CWE-LUG mailing list CWE-LUG@lists.firepipe.net http://www.cwelug.org/ http://www.cwelug.org/archives/ http://www.cwelug.org/mailinglist/
