Ivan Warren wrote:
Mark Post wrote:
Of course the kernel did understand the init= parameter. Getting it
passed to the kernel at boot time is the issue, and I'm not sure the
s390-tools did it, that far back in time.
That's where I'm surprised here..
Kernel parameters to the bootloader is just.. a blob !
A kernel loader may doctor the kernel parm 'blob' (in order to insert
some specific understood parm).. but it shouldn't change/alter/interpret
arbitrary kernel parms specified.
For example, in zipl, if in my parm file, I specify "foo=bar", then
"foo=bar" is passed to my kernel.. no matter what version of zipl I
use.. whether my custom kernel understands the "foo" parameter is none
of zipl's business !
As I understand it, earlier versions of zipl didn't allow boot-time
overrides, and in its easer forms one needs to be able to change
boot-time parameters to get init= in.
Also, it used to be possible to boot the kernel without a boot loader.
That went out in RHL about when the kernel became too big to fit on a
1.4 Mbyte floppy.
--
Cheers
John
-- spambait
1aaaa...@coco.merseine.nu z1aaaa...@coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375
You cannot reply off-list:-)
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
