August 2002 - openSUSE Autoinstall - openSUSE Mailing Lists

RE: [suse-autoinstall] applying patches
by Kugelberg, Thorsten 26 Aug '02

26 Aug '02

Hello, the script is nice, beside one little error: There is no dir called "inst-sys" inside the suse directory... so I changed it to setup/descr Regards Thorsten -----Original Message----- From: Anas Nashif To: Kugelberg, Thorsten Cc: suse-autoinstall(a)suse.com Sent: 26.08.2002 17:13 Subject: Re: [suse-autoinstall] applying patches * Kugelberg, Thorsten <thorsten.kugelberg(a)realtech.de> [Aug 26. 2002 17:01]: > Hello, > > is it also possible to install the updated packages from the beginning (without update)? Anything is possible... But this requires either a dirty workaround or a complete recreation of the package database avail. on the CDs. 1. dirty hack: Just overwrite the old packages with the new ones 2. create a new common.pkd (suse/setup/descr/common.pkd) This is a simple text based database which contains data from the packages. Using a simple shell script which queries the RPM package will do the job. I once written a script like that, not sure how compatible with current format though (http://www.suse.de/~nashif/makeCommon.sh which should be available online in 1 hour approx.) Anas > > All the systems I am installing via autoyast, are freshly installed once a week. So if I could just copy the updated rpms into the installation directory that would be the best way! > In case of using YOU it would take quite a long time to install all the packages and update them afterwards... > > Regards > Thorsten > > -----Original Message----- > From: Anas Nashif > To: ralonso(a)lis.state.oh.us > Cc: suse-autoinstall(a)suse.com > Sent: 21.08.2002 13:48 > Subject: Re: [suse-autoinstall] applying patches > > * ralonso(a)lis.state.oh.us <ralonso(a)lis.state.oh.us> [Aug 20. 2002 > 23:17]: > > I'd like to have the machines I build with autoyast to have the latest > > patches already applied. Obviously, I don't want to have to run > Online > > Update on each machine manually. Does anyone know of a way to apply > the > > patch rpms automatically? > > I have a a directory tree under /var/lib/YaST/patches/i386/update/8.0 > with > > all the patches for 8.0. Is there a way to use this directory to > patch the > > machines instead of running YOU on each? > > Please take a look at both these articles: > > http://sdb.suse.de/en/sdb/html/mlasars_yousync.html > http://sdb.suse.de/en/sdb/html/yast2_ncurses.html > > Regards, > Anas > > > > Thanks, > > Robert > > > > -- > > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > -- > Anas Nashif <nashif(a)suse.com>, SuSE Linux AG > Montreal (Laval), Canada > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > -- Anas Nashif <nashif(a)suse.com>, SuSE Linux AG Montreal (Laval), Canada

2 1

RE: [suse-autoinstall] applying patches
by Kugelberg, Thorsten 26 Aug '02

26 Aug '02

Hello, is it also possible to install the updated packages from the beginning (without update)? All the systems I am installing via autoyast, are freshly installed once a week. So if I could just copy the updated rpms into the installation directory that would be the best way! In case of using YOU it would take quite a long time to install all the packages and update them afterwards... Regards Thorsten -----Original Message----- From: Anas Nashif To: ralonso(a)lis.state.oh.us Cc: suse-autoinstall(a)suse.com Sent: 21.08.2002 13:48 Subject: Re: [suse-autoinstall] applying patches * ralonso(a)lis.state.oh.us <ralonso(a)lis.state.oh.us> [Aug 20. 2002 23:17]: > I'd like to have the machines I build with autoyast to have the latest > patches already applied. Obviously, I don't want to have to run Online > Update on each machine manually. Does anyone know of a way to apply the > patch rpms automatically? > I have a a directory tree under /var/lib/YaST/patches/i386/update/8.0 with > all the patches for 8.0. Is there a way to use this directory to patch the > machines instead of running YOU on each? Please take a look at both these articles: http://sdb.suse.de/en/sdb/html/mlasars_yousync.html http://sdb.suse.de/en/sdb/html/yast2_ncurses.html Regards, Anas > > Thanks, > Robert > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- Anas Nashif <nashif(a)suse.com>, SuSE Linux AG Montreal (Laval), Canada -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

cannot find info-file
by Menkhoff, Malte 23 Aug '02

23 Aug '02

hi anas! i´m trying to install suse 8.0 via autoyast and a bootdisk. cause of techn. reasons it´s not possible zo use dhcp or bootp. the howto gives me the information that i have to create an info-file where infos `bout ip, nameserver, and so on will be given for the mini linux. but by every test the system found not the info-file. i named it info. what can i do to boot over disk with my info-file without dhcp or bootb? malte menkhoff

3 2

applying patches
by ralonso＠lis.state.oh.us 21 Aug '02

21 Aug '02

I'd like to have the machines I build with autoyast to have the latest patches already applied. Obviously, I don't want to have to run Online Update on each machine manually. Does anyone know of a way to apply the patch rpms automatically? I have a a directory tree under /var/lib/YaST/patches/i386/update/8.0 with all the patches for 8.0. Is there a way to use this directory to patch the machines instead of running YOU on each? Thanks, Robert

3 2

AW: [suse-autoinstall] Modprobe for NIC's
by Kugelberg, Thorsten 20 Aug '02

20 Aug '02

Hello, well, since I stopped the service hotplug, the "Plug&Pray Manager" was gone! To get rid of the "Welcome Window" I configured the desktop like it should be, disabled the Welcome Message, and did everything for a my user. Then I made a tar archive of the Home-Directory and copied it to /etc. Now every time the X-Server starts, I untar the archive. This has the advantage, that after every login, the Desktop is initial again. This is done by editing the file /etc/X11/xdm/Xsetup . As is for an Internet Cafe Workststion, it is pretty nice and very useful!!! Regards Thorsten -----Ursprüngliche Nachricht----- Von: Marc Peter [mailto:marc.peter@avitech.de] Gesendet: Dienstag, 20. August 2002 09:12 An: suse-autoinstall(a)suse.com Betreff: [suse-autoinstall] Modprobe for NIC's hi, i have succesfully made a custom cd with only needed packages. Is there a way to make a automatic configuration of the NIC maybe with "modeprobe" or "autoprobe". another question, how can i prevent on first login the "welcome window" and "pnp manager" to configure the NIC again. greetings marc -- ************************************************* Avitech Aviation Management Technologies GmbH Marc Peter Bahnhofplatz 1 D-88045 Friedrichshafen Phone: +49 7541/282-451 Fax: +49 7541/282-199 mailto:marc.peter@avitech.de ************************************************* -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Modprobe for NIC's
by Marc Peter 20 Aug '02

20 Aug '02

hi, i have succesfully made a custom cd with only needed packages. Is there a way to make a automatic configuration of the NIC maybe with "modeprobe" or "autoprobe". another question, how can i prevent on first login the "welcome window" and "pnp manager" to configure the NIC again. greetings marc -- ************************************************* Avitech Aviation Management Technologies GmbH Marc Peter Bahnhofplatz 1 D-88045 Friedrichshafen Phone: +49 7541/282-451 Fax: +49 7541/282-199 mailto:marc.peter@avitech.de *************************************************

1 0

Re: [suse-autoinstall] LILO problems
by Marcel Ritter 19 Aug '02

19 Aug '02

> Hi Marcel. > > I'm a newbie and had this problem (01 01 01...). I got around it by > placing a /boot partition (1 cyl, 10Mb) on the primary HD and the rest > on the second HD. > > Hope this helps. Thanx - this could indeed be the problem. Other machines had a separate /boot partition and installed fine. The affected setup has no /boot entry. Anyhow - I think this is either a bug in the lilo configuration or it should be mentioned somewhere that you need to have a /boot partition to make lilo work. Ciao, Marcel > Graham > > On 15 Aug 2002 at 11:15, Marcel Ritter wrote: > > > And once again problems ... > > > > ... this time it's the bootloader. > > > > YaST2 seems to have problems if the install uses non-standard partitioning > > setups (such as installation on the second harddisk, or preserving an > > existing partition). At least I got this impression as it worked ok on all > > Systems with one "all Linux" harddisk. > > > > Now I only get things like > > > > LIL- > > or > > 01010101010101...(forever) > > or > > 08080808080808...(forever) > > > > and the lilo.conf is not based on the setup on my autoyast.xml > > > > I'd like to use a template or whatever to make things work. > > > > Perhaps there's even some option I could try, but unfortunately the > > docs are neither consistent nor up-to-date: > > > > According to "profile.elem.bootloader.html" bootloader only contains: > > (activate,linear,location,parameters), but in the example section there > > are several other things mentioned: > > > > <bootloader> > > <write_bootloader>true</write_bootloader> > > <location>mbr</location> > > <linear>false</linear> > > <lba_support>false</lba_support> > > <activate>true</activate> > > <kernel_parameters></kernel_parameters> > > <initrd_modules config:type="list" > > > <module>+++some kernel module name+++</module> > > </initrd_modules> > > </bootloader> > > > > I'd appreciate any hints and I'd be especially happy about a complete and > > up-do-date description of the available options. > > > > Ciao, > > Marcel > > > > ---- > > Marcel Ritter > > Linux Betreuer > > Regionales Rechenzentrum Erlangen > > ---- > > Unix _IS_ user friendly... It's just selective about who its friends are. > > > > > > -- > > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > > > > > ---- Marcel Ritter Linux Betreuer Regionales Rechenzentrum Erlangen ---- Unix _IS_ user friendly... It's just selective about who its friends are.

2 2

Install with various NIC's = Problem
by Alexander.Gehrig＠RSD.rohde-schwarz.com 19 Aug '02

19 Aug '02

Hi All I use Autoyast2 to make an unattened installation of SUSE 8.0 in my company. I just have a problem, perhaps there is someone who can help me. I boot from floppydisk, the installationfiles are on a nfsserver. The PC-Systems have different hardware, so this systems have differnet NIC's too. What to do that autoprobe will install and config this NIC before the installation, after this autoyast2 is avaiable to mount a directory on a nfsserver. What i have to do that all 3 Moduledisk will be loaded? Thanks! bye Alexander Gehrig

2 1

RE: [suse-autoinstall] Still problems with <kernel_parameters> -tag in autoinstall.xml
by Kugelberg, Thorsten 16 Aug '02

16 Aug '02

Hello, I had quite a similar problem: I was trying not to install a bootloader by setting <activate config:type="boolean">false</activate> . That does not work! Lilo is installed into the MBR! Propably there is something wrong with the bootloader option... Regards Thorsten -----Original Message----- From: bernd.ronecker(a)t-online.de To: suse-autoinstall(a)suse.com Sent: 16.08.2002 12:13 Subject: [suse-autoinstall] Still problems with <kernel_parameters> -tag in autoinstall.xml Hi there, during my automatic installation (SuSE 8.0, Autoyast2) I want to setup LILO with a special kernel-parameter. I am trying to do this via the <kernel_parameter>-tag in the bootloader-section in the autoinstall-xml-file. Regardless of which kernel-parameter I try to pass, the lilo.conf won't change at all. Am I doing something wrong or is there any other way to modify the LiLo BEFORE the first reboot during the installation? Here is a snippet from my autoinst.xml-file --------8<-------- <bootloader> <activate config:type="boolean">true</activate> <linear config:type="boolean">false</linear> <location>mbr</location> <kernel_parameters>ramdisk_blocksize=1024</kernel_parameters> </bootloader> --------8<-------- Regards Bernd. -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Still problems with <kernel_parameters> -tag in autoinstall.xml
by bernd.ronecker＠t-online.de 16 Aug '02

16 Aug '02

Hi there, during my automatic installation (SuSE 8.0, Autoyast2) I want to setup LILO with a special kernel-parameter. I am trying to do this via the <kernel_parameter>-tag in the bootloader-section in the autoinstall-xml-file. Regardless of which kernel-parameter I try to pass, the lilo.conf won't change at all. Am I doing something wrong or is there any other way to modify the LiLo BEFORE the first reboot during the installation? Here is a snippet from my autoinst.xml-file --------8<-------- <bootloader> <activate config:type="boolean">true</activate> <linear config:type="boolean">false</linear> <location>mbr</location> <kernel_parameters>ramdisk_blocksize=1024</kernel_parameters> </bootloader> --------8<-------- Regards Bernd.

1 0