Hi all, suse 8.1 by default installs the grub bootloader. right? Autoinstallation from a SuSE-8.1 repository, which was copied from a (german) SuSE-8.1 DVD also installs the grub bootloader for me. But when I switch to a repository which is based on the SuSE-8.1 FTP Distribution the same autoinst.xml configuration results in lilo getting installed. Interestingly an "interactive" installation from the same SuSE-8.1 FTP still installs grub !?! I tried without a bootloader resource in the control file. Is there a bootloader resource to force the use of grub as bootloader? -- Bernd 'Bing' Leibing <bernd.leibing@rz.uni-ulm.de> Computing Center, University of Ulm, Germany
* Bernd Leibing <bernd.leibing@rz.uni-ulm.de> [Nov 07. 2002 21:34]:
Hi all,
suse 8.1 by default installs the grub bootloader. right?
Autoinstallation from a SuSE-8.1 repository, which was copied from a (german) SuSE-8.1 DVD also installs the grub bootloader for me.
But when I switch to a repository which is based on the SuSE-8.1 FTP Distribution the same autoinst.xml configuration results in lilo getting installed.
Ok, LILO being installed on a new system is not something bad, it can happen in different cases, i.e. Root on RAID/LVM or if grub can't be used. But in this case, it's a bug that was introduced after the release of 8.1 and now it's in the FTP dist. The latest update package fixes this.
Interestingly an "interactive" installation from the same SuSE-8.1 FTP still installs grub !?!
I tried without a bootloader resource in the control file. Is there a bootloader resource to force the use of grub as bootloader?
Currently you cant choose, but we are working on improving the options for the bootloader, i.e. password prtotection etc. Anas
-- Bernd 'Bing' Leibing <bernd.leibing@rz.uni-ulm.de> Computing Center, University of Ulm, Germany
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
-- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada
Anas Nashif wrote:
* Bernd Leibing <bernd.leibing@rz.uni-ulm.de> [Nov 07. 2002 21:34]:
Autoinstallation from a SuSE-8.1 repository, which was copied from a (german) SuSE-8.1 DVD also installs the grub bootloader for me.
But when I switch to a repository which is based on the SuSE-8.1 FTP Distribution the same autoinst.xml configuration results in lilo getting installed.
Ok, LILO being installed on a new system is not something bad, it can happen in different cases, i.e. Root on RAID/LVM or if grub can't be used. But in this case, it's a bug that was introduced after the release of 8.1 and now it's in the FTP dist. The latest update package fixes this.
Which update package exactly? I merged all offical updates and the ones in ftp://ftp.suse.com/pub/people/nashif/autoyast2/8.1/RPMS into my repository, but I am still stuck with LILO Do I have to modify the root image in the boot directory of the repository? Thanks Bernd -- Bernd 'Bing' Leibing Computing Center, University of Ulm, Germany Email: <bernd.leibing@rz.uni-ulm.de> Tel. 0731-50-22516 Homepage (PGP-Key): http://www.uni-ulm.de/~leibing O26/5215
* Bernd Leibing <bernd.leibing@rz.uni-ulm.de> [Nov 08. 2002 23:44]:
Anas Nashif wrote:
* Bernd Leibing <bernd.leibing@rz.uni-ulm.de> [Nov 07. 2002 21:34]:
Autoinstallation from a SuSE-8.1 repository, which was copied from a (german) SuSE-8.1 DVD also installs the grub bootloader for me.
But when I switch to a repository which is based on the SuSE-8.1 FTP Distribution the same autoinst.xml configuration results in lilo getting installed.
Ok, LILO being installed on a new system is not something bad, it can happen in different cases, i.e. Root on RAID/LVM or if grub can't be used. But in this case, it's a bug that was introduced after the release of 8.1 and now it's in the FTP dist. The latest update package fixes this.
Which update package exactly? I merged all offical updates and the ones in ftp://ftp.suse.com/pub/people/nashif/autoyast2/8.1/RPMS into my repository, but I am still stuck with LILO
Do I have to modify the root image in the boot directory of the repository? Yes.
This is needed for any fix of bugs which happen during the initial installation phase (before the system boots for the first time and starts the configuration). Anas
Thanks Bernd -- Bernd 'Bing' Leibing Computing Center, University of Ulm, Germany Email: <bernd.leibing@rz.uni-ulm.de> Tel. 0731-50-22516 Homepage (PGP-Key): http://www.uni-ulm.de/~leibing O26/5215
-- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada
Hello, I freshly installed SuSE-8.1 from CD on my Installation Server. Then I created a software depot, installed all current update-rpm's and used '/usr/lib/YaST2/bin/create_package_descr' to update the new package descriptions. When I tell him '/sbin/yast2 autoyast' I get the YaST2-GUI but when I try to create a new control file and then click on "Software" he answers 'No modules available in this group'. The Package Directory has been set correctly under "Preferences". Or do I have to use a SuSE-8.0 AutoYast in order to create control files (it works fine with SuSE-8.0)?! Thank you very much!! -- Erik Soyez
* Erik Soyez <soyez@science-computing.de> [Nov 12. 2002 09:22]:
Hello,
I freshly installed SuSE-8.1 from CD on my Installation Server. Then I created a software depot, installed all current update-rpm's and used '/usr/lib/YaST2/bin/create_package_descr' to update the new package descriptions.
When I tell him '/sbin/yast2 autoyast' I get the YaST2-GUI but when I try to create a new control file and then click on "Software" he answers 'No modules available in this group'. The Package Directory has been set correctly under "Preferences".
Or do I have to use a SuSE-8.0 AutoYast in order to create control files (it works fine with SuSE-8.0)?!
Thank you very much!!
http://www.suse.de/~nashif/autoinstall/8.1/bugs.html#AEN10 Anas
-- Erik Soyez
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
-- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada
Hi there, I just created an Auto-Installation CD using AutoYast2 (SuSE-8.1). This seemed to be a great option for our customer to quickly reinstall his server in case of failure. ------------------------------------------------------------------------ # rpm -qa | grep autoy autoyast2-installation-2.6.38-1 autoyast2-2.6.38-1 ------------------------------------------------------------------------ After installing the software packages, AutoYast says "18 packages returned an error". It does not show any details - the detailed list button shows an empty page. Then it says something about having problems writing the boot record and gives a kernel panic when trying to boot the installed system. Starting a rescue system shows that no kernel or initrd gets installed under '/boot'. With the netork installation this problem could be solved including: ------------------------------------------------------------------------ <install> <general> <mode><confirm config:type="boolean">false</confirm></mode> .... ------------------------------------------------------------------------ Why does this not work with a CD? Please help me, this is urgent! Thanks, Erik. --
Hi again, what do I have to do in order to update my Installation Server with the latest rpm's and still get the AutoYast Network Installation to work? If I copy all update rpm's into the suse/* directories of my server and then run '/var/lib/YaST2/bin/create_package_descr' AutoYast will still install the old rpm's!! If I delete the old rpm's and run 'create_package_descr' again, the installation failes with the same syptoms as described for the CD-Installation of my last email. Something here does not work the way I would expect. Or is 'create_package_descr' just the wrong script?! :-(Erik. On Thu, 14 Nov 2002, Erik Soyez wrote:
Hi there,
I just created an Auto-Installation CD using AutoYast2 (SuSE-8.1). This seemed to be a great option for our customer to quickly reinstall his server in case of failure.
------------------------------------------------------------------------ # rpm -qa | grep autoy autoyast2-installation-2.6.38-1 autoyast2-2.6.38-1 ------------------------------------------------------------------------
After installing the software packages, AutoYast says "18 packages returned an error". It does not show any details - the detailed list button shows an empty page.
Then it says something about having problems writing the boot record and gives a kernel panic when trying to boot the installed system.
Starting a rescue system shows that no kernel or initrd gets installed under '/boot'.
With the netork installation this problem could be solved including: ------------------------------------------------------------------------ <install> <general> <mode><confirm config:type="boolean">false</confirm></mode> .... ------------------------------------------------------------------------
Why does this not work with a CD? Please help me, this is urgent!
Thanks, Erik.
--
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
--
* Erik Soyez <soyez@science-computing.de> [Nov 14. 2002 13:52]:
Hi again,
what do I have to do in order to update my Installation Server with the latest rpm's and still get the AutoYast Network Installation to work?
Replace packages with new one. Update the root image create a new package database
If I copy all update rpm's into the suse/* directories of my server and then run '/var/lib/YaST2/bin/create_package_descr' AutoYast will still install the old rpm's!! If I delete the old rpm's and run 'create_package_descr' again, the installation failes with the same syptoms as described for the CD-Installation of my last email.
You have to remove old rpms! Always make sure the file packages in suse/setup/desc/Packages are the right version
Something here does not work the way I would expect. Or is 'create_package_descr' just the wrong script?!
Yeah, these steps are tricky and you have to be carefull. I am currently working on detailed documentaion of these steps, many people seem to have problems with them. Anas
On Thu, 14 Nov 2002, Erik Soyez wrote:
Hi there,
I just created an Auto-Installation CD using AutoYast2 (SuSE-8.1). This seemed to be a great option for our customer to quickly reinstall his server in case of failure.
------------------------------------------------------------------------ # rpm -qa | grep autoy autoyast2-installation-2.6.38-1 autoyast2-2.6.38-1 ------------------------------------------------------------------------
After installing the software packages, AutoYast says "18 packages returned an error". It does not show any details - the detailed list button shows an empty page.
Then it says something about having problems writing the boot record and gives a kernel panic when trying to boot the installed system.
Starting a rescue system shows that no kernel or initrd gets installed under '/boot'.
With the netork installation this problem could be solved including: ------------------------------------------------------------------------ <install> <general> <mode><confirm config:type="boolean">false</confirm></mode> .... ------------------------------------------------------------------------
Why does this not work with a CD? Please help me, this is urgent!
Thanks, Erik.
--
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
--
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
-- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada
* Erik Soyez <soyez@science-computing.de> [Nov 14. 2002 13:19]:
Hi there,
I just created an Auto-Installation CD using AutoYast2 (SuSE-8.1). This seemed to be a great option for our customer to quickly reinstall his server in case of failure.
------------------------------------------------------------------------ # rpm -qa | grep autoy autoyast2-installation-2.6.38-1 autoyast2-2.6.38-1 ------------------------------------------------------------------------
After installing the software packages, AutoYast says "18 packages returned an error". It does not show any details - the detailed list button shows an empty page.
This happens if you created a faulty package dabatase. Please make sure /usr/share/autoinstall/EXTRA_PROV is available when you create the database.
Then it says something about having problems writing the boot record and gives a kernel panic when trying to boot the installed system.
Starting a rescue system shows that no kernel or initrd gets installed under '/boot'.
With the netork installation this problem could be solved including: ------------------------------------------------------------------------ <install> <general> <mode><confirm config:type="boolean">false</confirm></mode> .... ------------------------------------------------------------------------
Did you update the root image? It seems you still have the old packages in the root image (inst-sys) Anas
Why does this not work with a CD? Please help me, this is urgent!
Thanks, Erik.
--
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
-- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada
participants (3)
-
Anas Nashif -
Bernd Leibing -
Erik Soyez