RE: [suse-autoinstall] Hybrid Auto Install (CD - FTP/HTTP)
Hi Charles, My understanding is that YaST software is not actually in initrd, but in /boot/root. The boot process is as follows (I think): kernel boot's - load's initrd - which loads linuxrc - linuxrc sets up various things (NIC, install settings etc) and then loads /boot/root and mounts it as the root filesystem. This contains YaST which is then started with the settings that were configured by linuxrc (can anyone confirm I have got this right...). I have just been using the default install CD (so isolinux I guess), and I am quite happy building my own initrd or /boot/root filesystems, but I do not know what changes I will need to make in achieve what I want (/boot/root loaded from CD but install rpm's fetched via http). Thanks again for all your help, Nick. -----Original Message----- From: Suffin, Charles [mailto:Charles.Suffin@stratus.com] Posted At: 01 February 2005 12:13 Posted To: Nick-Forbes.SPAM Conversation: [suse-autoinstall] Hybrid Auto Install (CD - FTP/HTTP) Subject: RE: [suse-autoinstall] Hybrid Auto Install (CD - FTP/HTTP) OK, Nick. I haven't built my own initrd for YaST, but my understanding was that the YaST/autoYaST software that lives in the root filesystem is built into the initrd -- i.e., the kernel boots, loads initrd, and then starts YaST/autoYaST. So, it seems to me that the process of booting a CD already implies that the root directory is extracted from initrd, Nick. I'm sure my lack of knowledge in this area is why I'm having trouble understanding you ("it's not you, it's me. ;)") Are you using isolinux or grub as a bootloader on the CD? Enclosed is the isolinux.cfg that I use on our network install CD at Stratus... Note the "append=" statements for each kernel label... Does that help you? I guess that exhausts my knowledge on the subject (which isn't hard to do). Good luck; I'll be following the discussion on the email list. -- Charlie _____________________________________________________________________ VirusChecked for the Incepta Group plc _____________________________________________________________________
Hi, Nick Forbes wrote:
Hi Charles,
My understanding is that YaST software is not actually in initrd, but in /boot/root. The boot process is as follows (I think):
true.
kernel boot's - load's initrd - which loads linuxrc - linuxrc sets up various things (NIC, install settings etc) and then loads /boot/root and mounts it as the root filesystem. This contains YaST which is then started with the settings that were configured by linuxrc (can anyone confirm I have got this right...).
true.
I have just been using the default install CD (so isolinux I guess), and I am quite happy building my own initrd or /boot/root filesystems, but I do not know what changes I will need to make in achieve what I want (/boot/root loaded from CD but install rpm's fetched via http).
Why exactly do you want to load the root file from the CD? any special reason? Anas
Thanks again for all your help,
Nick.
-----Original Message----- From: Suffin, Charles [mailto:Charles.Suffin@stratus.com] Posted At: 01 February 2005 12:13 Posted To: Nick-Forbes.SPAM Conversation: [suse-autoinstall] Hybrid Auto Install (CD - FTP/HTTP) Subject: RE: [suse-autoinstall] Hybrid Auto Install (CD - FTP/HTTP)
OK, Nick.
I haven't built my own initrd for YaST, but my understanding was that the YaST/autoYaST software that lives in the root filesystem is built into the initrd -- i.e., the kernel boots, loads initrd, and then starts YaST/autoYaST.
So, it seems to me that the process of booting a CD already implies that the root directory is extracted from initrd, Nick. I'm sure my lack of knowledge in this area is why I'm having trouble understanding you ("it's not you, it's me. ;)")
Are you using isolinux or grub as a bootloader on the CD? Enclosed is the isolinux.cfg that I use on our network install CD at Stratus... Note the "append=" statements for each kernel label... Does that help you?
I guess that exhausts my knowledge on the subject (which isn't hard to do).
Good luck; I'll be following the discussion on the email list. -- Charlie
_____________________________________________________________________ VirusChecked for the Incepta Group plc _____________________________________________________________________
participants (2)
-
Anas Nashif -
Nick Forbes