February 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

RE: [suse-autoinstall] Separate dirs for original and own packages?
by Schumacher, Gordon 03 Feb '05

03 Feb '05

I think to do this you need the instructions in section 4.5.3 of the docs, "Installing additional and customized Packages". Now, that said I haven't successfully managed to build the new package database and gotten YaST to be able to read it yet but I'm still playing with it. -----Original Message----- From: Ole Streicher [mailto:ole-suse-autoyast@gmx.net] Sent: Tuesday, February 01, 2005 6:39 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Separate dirs for original and own packages? Dear group, I would like to use the original version of a SuSE mounted read-only, but I have some additional packages that should also be installed. Is it possible to have a separate installation directory for own packages when using autoyast? The documentation only states that it is no possible to hold everything in one place, which leads to the assumption that the opposite is (was?) also possible. BTW, I didn't get any reply to my last question about the sysconfig variable mystery. Is it really a bug or something trivial I have misunderstood? Best regards Ole -- Sparen beginnt mit GMX DSL: http://www.gmx.net/de/go/dsl -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

SLES9 + SP1 network install directory structure
by Egan Ford 03 Feb '05

03 Feb '05

I need to setup SLES9 + SP1 for network install, however the NFS server is not SLES9. The notes recommend using yast to set this up. How do I setup it up manually? Thanks.

2 1

RE: [suse-autoinstall] Funny partitioning behaviour
by Ryan Allen 02 Feb '05

02 Feb '05

Thanks Charlie. This solved my problem. I also changed: <initialize config:type="boolean">false</initialize> to true, that is supposed to tell the installer to wipe out any existing partitions on the HD. Thanks for your help! -- Ryan > -----Original Message----- > From: Suffin, Charles [mailto:Charles.Suffin@stratus.com] > Sent: Tuesday, February 01, 2005 6:01 PM > To: Ryan Allen; suse-autoinstall(a)suse.com > Subject: RE: [suse-autoinstall] Funny partitioning behaviour > > I think you need to use the partition_nr property in the definition of > your > partitions, Ryan. If you tell autoyast that /boot is 1, swap is 2, and / > is > 3, I think you will not run into the problem of YaST attempting to add > new > partitions to the disk: > > . > . > . > <partitions config:type="list"> > <partition> > <mount>/boot</mount> > <filesystem config:type="symbol">ext2</filesystem> > <format config:type="boolean">true</format> > <partition_id config:type="integer">131</partition_id> > * --> <partition_nr config:type="integer">1</partition_nr> > <partition_type>primary</partition_type> > <size>1gb</size> > . > . > . > > -- Charlie > > -----Original Message----- > From: Ryan Allen [mailto:r.allen@f5.com] > Sent: Tuesday, February 01, 2005 8:44 PM > To: suse-autoinstall(a)suse.com > Subject: [suse-autoinstall] Funny partitioning behaviour > > > > Hi, > > > > I'm doing automated (no user intervention) installs of suse 9.2 using > autoyast. I would like autoyast to wipe clean the partition table, > create new partitions regardless of what's there, and format them. For > some reason, it's creating the first partition on /dev/hda6, and going > up from there. The install fails because it thinks there is not enough > HD space. > > > > I'd like it to start from /dev/hda1: > > > > /dev/hda1 30 Megs /boot > > /dev/hda2 1 Gig /var > > /dev/hda3 512 Megs swap > > /dev/hda4 remainder of HD / > > > > Here is my config. What am I doing wrong? > > > > Thanks, > > Ryan > > > > P.S. also, why did autoyast put in the <crypt> tags and can I take them > out? Thanks again! > > > > <partitioning config:type="list"> > > <drive> > > <device>/dev/hda</device> > > <initialize config:type="boolean">false</initialize> > > <partitions config:type="list"> > > <partition> > > <crypt>twofish256</crypt> > > <filesystem config:type="symbol">reiser</filesystem> > > <format config:type="boolean">true</format> > > <loop_fs config:type="boolean">false</loop_fs> > > <mount>/boot</mount> > > <partition_id config:type="integer">131</partition_id> > > <size>30M</size> > > </partition> > > <partition> > > <crypt>twofish256</crypt> > > <filesystem config:type="symbol">swap</filesystem> > > <format config:type="boolean">true</format> > > <loop_fs config:type="boolean">false</loop_fs> > > <mount>swap</mount> > > <partition_id config:type="integer">130</partition_id> > > <size>512M</size> > > </partition> > > <partition> > > <crypt>twofish256</crypt> > > <filesystem config:type="symbol">swap</filesystem> > > <format config:type="boolean">true</format> > > <loop_fs config:type="boolean">false</loop_fs> > > <mount>/var</mount> > > <partition_id config:type="integer">131</partition_id> > > <size>1G</size> > > </partition> > > <partition> > > <crypt>twofish256</crypt> > > <filesystem config:type="symbol">reiser</filesystem> > > <format config:type="boolean">true</format> > > <loop_fs config:type="boolean">false</loop_fs> > > <mount>/</mount> > > <partition_id config:type="integer">131</partition_id> > > <size>max</size> > > </partition> > > </partitions> > > <use>all</use> > > </drive> > > </partitioning> > > > > > >

1 0

AW: [suse-autoinstall] SLES8 autoyast with http repository
by Hollmann Frank 02 Feb '05

02 Feb '05

Hi, SP3 means Service Pack3 for SuSE Linux Enterprise Server. Frank -----Ursprüngliche Nachricht----- Von: Daniel Fitzner [mailto:t-systems-fitz@web.de] Gesendet: Mittwoch, 2. Februar 2005 11:40 An: suse-autoinstall(a)suse.com Cc: nashif(a)suse.de Betreff: [suse-autoinstall] SLES8 autoyast with http repository Hello, what do you exactly mean with using SP3???? The http repository is with the original SLES and UL Cds and with the both SP3 CDs according to http://www.suse.de/~nashif/autoinstall/multiplesource.html. I created the bootable cd according to http://lists.suse.com/archive/suse-autoinstall/2004-May/0008.html, and in this comment : >== 7 == Make a custom boot cd >========================================================= >Mount and copy your SLES8 CD1 to /iso/cdboot/ You can delete all rpm in >/iso/cdboot/ to reduce the size of the final cd Mount the SP3 CD to >/mnt/sp3 ### script ### cp /mnt/sp3/boot/loader/linux >/iso/cdboot/boot/loader/ cp /mnt/sp3/boot/loader/initrd >/iso/cdboot/boot/loader/ cp /mnt/sp3/boot/loader/initrd /iso/ So I think I am using SP3. The problem appears as soon as yast want s to install the packages. It makes a wget to http://<INSTALLSRVIP>/SuSE/SLES8/suse/xxx.rpm an not to http://<INSTALLSRVIP>/SuSE/SLES8/sles8-i386/CD1/suse/xxx.rpm which would be the right path. I hope this information helps. best regards daniel >Are you using SP3? Without SP3, HTTP installs do not work. >Anas Daniel Fitzner wrote: >> Hello guys, >> >> I am trying to setup a autoyast environment for sles8 with a http >> repository. >> >> According to >> http://www.suse.de/~nashif/autoinstall/multiplesource.html I setup >> the repository. >> >> I created a bootable CD mit an info file, thats looks: >> >> install: http://<INSTALLSRVIP>/SuSE/SLES8/ >> netdevice: eth0 >> hostip: <CLIENTIP> >> gateway: <CLIENTGATEWAY> >> nameserver: <DNS> >> netmask: 255.255.255.0 >> textmode: 1 >> forceinsmod: 1 >> nopcmcia: 1 >> >> and a working xml -file. >> >> If I boot with the cd at first everything works fine, the clients >> gets all information needed, like network configuration, partitioning >> infos from xml-file and so on. >> >> But if the yast wants to start the installation it cannot find any >> package. I checked the logs of the http-server and saw that yast >> searches the packages at the wrong directory. >> >> Do you have any ideas, why??? >> >> > ______________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193 -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

RE: [suse-autoinstall] Funny partitioning behaviour
by Suffin, Charles 02 Feb '05

02 Feb '05

I think you need to use the partition_nr property in the definition of your partitions, Ryan. If you tell autoyast that /boot is 1, swap is 2, and / is 3, I think you will not run into the problem of YaST attempting to add new partitions to the disk: . . . <partitions config:type="list"> <partition> <mount>/boot</mount> <filesystem config:type="symbol">ext2</filesystem> <format config:type="boolean">true</format> <partition_id config:type="integer">131</partition_id> * --> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <size>1gb</size> . . . -- Charlie -----Original Message----- From: Ryan Allen [mailto:r.allen@f5.com] Sent: Tuesday, February 01, 2005 8:44 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Funny partitioning behaviour Hi, I'm doing automated (no user intervention) installs of suse 9.2 using autoyast. I would like autoyast to wipe clean the partition table, create new partitions regardless of what's there, and format them. For some reason, it's creating the first partition on /dev/hda6, and going up from there. The install fails because it thinks there is not enough HD space. I'd like it to start from /dev/hda1: /dev/hda1 30 Megs /boot /dev/hda2 1 Gig /var /dev/hda3 512 Megs swap /dev/hda4 remainder of HD / Here is my config. What am I doing wrong? Thanks, Ryan P.S. also, why did autoyast put in the <crypt> tags and can I take them out? Thanks again! <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <size>30M</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <size>512M</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/var</mount> <partition_id config:type="integer">131</partition_id> <size>1G</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning>

2 1

[suse-autoinstall] SLES8 autoyast with http repository
by Daniel Fitzner 02 Feb '05

02 Feb '05

Hello, what do you exactly mean with using SP3???? The http repository is with the original SLES and UL Cds and with the both SP3 CDs according to http://www.suse.de/~nashif/autoinstall/multiplesource.html. I created the bootable cd according to http://lists.suse.com/archive/suse-autoinstall/2004-May/0008.html, and in this comment : >== 7 == Make a custom boot cd >========================================================= >Mount and copy your SLES8 CD1 to /iso/cdboot/ >You can delete all rpm in /iso/cdboot/ to reduce the size of the final >cd >Mount the SP3 CD to /mnt/sp3 >### script ### >cp /mnt/sp3/boot/loader/linux /iso/cdboot/boot/loader/ >cp /mnt/sp3/boot/loader/initrd /iso/cdboot/boot/loader/ >cp /mnt/sp3/boot/loader/initrd /iso/ So I think I am using SP3. The problem appears as soon as yast want s to install the packages. It makes a wget to http://<INSTALLSRVIP>/SuSE/SLES8/suse/xxx.rpm an not to http://<INSTALLSRVIP>/SuSE/SLES8/sles8-i386/CD1/suse/xxx.rpm which would be the right path. I hope this information helps. best regards daniel >Are you using SP3? Without SP3, HTTP installs do not work. >Anas Daniel Fitzner wrote: >> Hello guys, >> >> I am trying to setup a autoyast environment for sles8 with a http >> repository. >> >> According to >> http://www.suse.de/~nashif/autoinstall/multiplesource.html I setup the >> repository. >> >> I created a bootable CD mit an info file, thats looks: >> >> install: http://<INSTALLSRVIP>/SuSE/SLES8/ >> netdevice: eth0 >> hostip: <CLIENTIP> >> gateway: <CLIENTGATEWAY> >> nameserver: <DNS> >> netmask: 255.255.255.0 >> textmode: 1 >> forceinsmod: 1 >> nopcmcia: 1 >> >> and a working xml -file. >> >> If I boot with the cd at first everything works fine, the clients gets >> all information needed, like network configuration, partitioning infos >> from xml-file and so on. >> >> But if the yast wants to start the installation it cannot find any >> package. I checked the logs of the http-server and saw that yast >> searches the packages at the wrong directory. >> >> Do you have any ideas, why??? >> >> > ______________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

1 0

RE: [suse-autoinstall] Hybrid Auto Install (CD - FTP/HTTP)
by Nick Forbes 02 Feb '05

02 Feb '05

Hi Anas, The answer to your question below is a little complicated but here goes: We have a custom selection of packages that we want to install and be able to maintain so we would like to keep them in a central repository rather than keep burning new CD's every time a package is updated. We want to use this installation all around the world (60+ locations, many with 256kbps WAN links or less)and keep it up-to-date so I wanted to create a boot CD (as small as possible) that I could distribute to people at each location who could use it to install this 'standard' build over the WAN (usually overnight). The problem is that the hardware the build is to be installed on is very varied and many have some "funnies" that cause the installation process to fail during probing etc. I wanted to get the root filesystem on the CD as troubleshooting the installation process when you have to wait 4hours to fetch the root filesystem via HTTP in order to test new settings is very hard work! If the root filesystem could be on the CD but the packages centrally, we can at least be sure the installation process is working OK, before leaving the machine overnight to (slowly) pull down all the current packages. I hope that makes some sort of sense, I'd be happy to consider any other suggestions as to how I might get around this problem... Thanks again, Nick. -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Posted At: 02 February 2005 05:11 Posted To: Nick-Forbes.SPAM Conversation: [suse-autoinstall] Hybrid Auto Install (CD - FTP/HTTP) Subject: Re: [suse-autoinstall] Hybrid Auto Install (CD - FTP/HTTP) --snip-- > Why exactly do you want to load the root file from the CD? any special reason?

1 0

Re: [suse-autoinstall] SLES8 autoyast with http repository
by p.slabiak＠linux-services.org 02 Feb '05

02 Feb '05

Das haette uns doch auch der SuSEsupport schicken koennen... ---------------Urspr�ngliche Nachricht--------------- Von: Anas Nashif <nashif(a)suse.de> An : Daniel Fitzner <t-systems-fitz(a)web.de> CC : suse-autoinstall(a)suse.com ----------------------------------------------------- Are you using SP3? Without SP3, HTTP installs do not work. Anas Daniel Fitzner wrote: > Hello guys, > > I am trying to setup a autoyast environment for sles8 with a http repository. > > According to http://www.suse.de/~nashif/autoinstall/multiplesource.html I setup the repository. > > I created a bootable CD mit an info file, thats looks: > > install: http://<INSTALLSRVIP>/SuSE/SLES8/ > netdevice: eth0 > hostip: <CLIENTIP> > gateway: <CLIENTGATEWAY> > nameserver: <DNS> > netmask: 255.255.255.0 > textmode: 1 > forceinsmod: 1 > nopcmcia: 1 > > and a working xml -file. > > If I boot with the cd at first everything works fine, the clients gets all information needed, like network configuration, partitioning infos from xml-file and so on. > > But if the yast wants to start the installation it cannot find any package. I checked the logs of the http-server and saw that yast searches the packages at the wrong directory. > > Do you have any ideas, why??? > > > > > > > > > > ______________________________________________________________ > Verschicken Sie romantische, coole und witzige Bilder per SMS! > Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193 > > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

RE: [suse-autoinstall] Hybrid Auto Install (CD - FTP/HTTP)
by Nick Forbes 02 Feb '05

02 Feb '05

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 _____________________________________________________________________

2 1

Funny partitioning behaviour
by Ryan Allen 02 Feb '05

02 Feb '05

Hi, I'm doing automated (no user intervention) installs of suse 9.2 using autoyast. I would like autoyast to wipe clean the partition table, create new partitions regardless of what's there, and format them. For some reason, it's creating the first partition on /dev/hda6, and going up from there. The install fails because it thinks there is not enough HD space. I'd like it to start from /dev/hda1: /dev/hda1 30 Megs /boot /dev/hda2 1 Gig /var /dev/hda3 512 Megs swap /dev/hda4 remainder of HD / Here is my config. What am I doing wrong? Thanks, Ryan P.S. also, why did autoyast put in the <crypt> tags and can I take them out? Thanks again! <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <size>30M</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <size>512M</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/var</mount> <partition_id config:type="integer">131</partition_id> <size>1G</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning>

1 0