dear anas nashif, during my installation over net via nfs i have to use three disks [boot-disk, modules_1, modules_3]. is there any possibility to reduce to two disks or one cdrom? have you an idea to realise this facility? Mit freundlichen Grüßen Malte Menkhoff mailto:malte.menkhoff@telekom.de
dear anas nashif,
during my installation over net via nfs i have to use three disks [boot-disk, modules_1, modules_3]. is there any possibility to reduce to two disks or one cdrom? have you an idea to realise this facility?
Perhaps you'd like to try a grub bootdisk. I had a similar problem around here and I build a grub boot floppy (grub does support booting from net for most of the standard network cards). You can also add the autoyast.xml file (containing the configuration) to the disk ... all you need is a TFTP (for kernel and initrd) and a NFS server (for the rest). No DHCP is needed. If you're interested in this, I can send the necessary scripts and a little docu to the list. Ciao, Marcel
Mit freundlichen Gr��en
Malte Menkhoff mailto:malte.menkhoff@telekom.de
---- Marcel Ritter Linux Betreuer Regionales Rechenzentrum Erlangen ---- Unix _IS_ user friendly... It's just selective about who its friends are.
* Menkhoff, Malte <Malte.Menkhoff@telekom.de> [Aug 29. 2002 12:36]:
dear anas nashif,
during my installation over net via nfs i have to use three disks [boot-disk, modules_1, modules_3]. is there any possibility to reduce to two disks or one cdrom? have you an idea to realise this facility?
If network booting is not an option for you, Why dont you use the CDs to boot, floppies, unless customized, are almost useless for the autoinstallation. Anas
Mit freundlichen Grüßen
Malte Menkhoff mailto:malte.menkhoff@telekom.de
-- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada
Am Donnerstag, 29. August 2002 15:02 schrieb Anas Nashif:
If network booting is not an option for you, Why dont you use the CDs to boot, floppies, unless customized, are almost useless for the autoinstallation.
Sometimes, booting form CD is not posible. @ Malte Menkhoff There was a thread about creating your own bootdisk, module disks some weeks ago http://lists.suse.com/archive/suse-autoinstall/2002-Jun/0000.html I made a Doku, but only in German: http://www.familiewallner.de/georg/Linux/yast2AutoInstall/AutoInstallDiskett... CU Georg
Hi, I tried to make a use of <config_file> for copying a prepared configuration for autorpm to the clients' /etc directory. The autoinstall-gui coming with yast2 doesn't support that feature, so I added the following lines to the control file by hand: ------- [...] <files config:type="list" > <config_file> <file_path>/etc/autorpm.d/autorpm.conf</file_path> <file_contents><![CDATA[ ########################################################## # $Id: samples.conf,v 1.4 1998/03/20 00:35:59 kirk Exp $ ########################################################## ########################################################## # Put the email address of the person to receive the reports from # AutoRPM (usually the system administrator) Set_Var("ReportDest","Christian.Schromm@erlf.siemens.de"); # This is whoever you want the report on what actually happened # (i.e. abc-1.6 was installed... bbb-2.1 failed to be installed) # to go to. Report_Queues_To ("${ReportDest}"); # This is what you would run on the client machines, # assuming the server's /updates directory is mounted # on /mnt/updates: directory ("/usr/local/dist/suse8.0patches") { # Since there is no Compare_To_Dir, the files # will be compared to the local RPM database. action (updated) { Install (Auto); Report (Yes); } } ]]></file_contents> </config_file> </files> [...] ----- When I reopened the control file with the yast2-autoinstall-gui the passage above was changed to ----- [...] <files config:type="list" > <listentry> <file_contents>########################################################## # $Id: samples.conf,v 1.4 1998/03/20 00:35:59 kirk Exp $ ########################################################## ########################################################## # Put the email address of the person to receive the reports from # AutoRPM (usually the system administrator) Set_Var("ReportDest", "Christian.Schromm@erlf.siemens.de"); # This is whoever you want the report on what actually happened # (i.e. abc-1.6 was installed... bbb-2.1 failed to be installed) # to go to. Report_Queues_To ("${ReportDest}"); # This is what you would run on the client machines, # assuming the server's /updates directory is mounted # on /mnt/updates: directory ("/usr/local/dist/suse8.0patches") { # Since there is no Compare_To_Dir, the files # will be compared to the local RPM database. action (updated) { Install (Auto); Report (Yes); } }</file_contents> <file_path>/etc/autorpm.d/autorpm.conf</file_path> </listentry> </files> [...] ---- The <![CDATA[ ... ]]> tag was gone, <listentry> replaced <file_contents>, and the content was merged into one line, resulting in one huge comment. Is this a known bug? any hints? -- Bye, Christian Schromm
On Mon, 2 Sep 2002, Christian Schromm wrote: [...]
The <![CDATA[ ... ]]> tag was gone, <listentry> replaced <file_contents>, and the content was merged into one line, resulting in one huge comment.
The same thing happens with <script> when merging classes... -- Ciao, Christian Schromm --------------------------------- Christian Schromm A&D SH 12 Siemens AG
participants (5)
-
Anas Nashif -
Christian Schromm -
Georg Wallner -
Marcel Ritter -
Menkhoff, Malte