September 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

Workshop "automatic installation" at Linuxhotel
by Ingo Wichmann 13 Sep '05

13 Sep '05

Hi! There will be a workshop on the topic of "automatic installation" at the linuxhotel ( http://www.linuxhotel.de ), essen, germany from Friday, Oktober 7 to Sunday Oktober 9. Its a pet-project of mine, i just want to spend a weekend hacking and comparing the different approaches to this topic ( fai, m23, autoyast, kickstart ). So if you want to join, feel free to do so. Prizing: 10 Euros for the drinks and stuff. 50 Euros per night in a shared room for 2 persons. ( Developers who can prove relevant commitments to a relevant projekt on this topic are welcome to stay at the hotel for free ) Just send an email if you want to join. Here is my announcement in German: Hallo Leute! Ich habe grade unheimlich Spaß daran gefunden, automatisch Linux-Rechner zu installieren. Wem das genauso geht, oder wer das interessant findet und ausreichend Vorkenntnisse hat, den lade ich herzlich zu einem Bastel-Wochende vom 07.10. bis zum 09.10. hier ins Linuxhotel ein. Programm: ========= Freitag, 07.10.: 20:00 Uhr bis ca. 21:30 Uhr Vortrag / Demo von mir: Einführung in das Thema, Praxisbeispiel Installation Netzwerkboot mit syslinux/pxelinux, dhcpd und passendem Kernel. Samstag, 08.10: 10:00 bis 17:00 Uhr: Bastel-Session in Eigenregie im wesentlichen mit mitgebracher Hardware. Ein paar Test-Notebooks, Switches und Kabel kann ich auch beisteuern, aber besser ist, jeder bringt selbst genug Rechner bzw. VMware-Lizenzen mit. Ich will in der Zeit verschiedene Varianten austesten ( FAI für Debian, m23 für Debian, autoYast für SuSE, Kickstart für Fedora/RedHat, grub statt pxelinux ) und mich mit Euch austauschen was wofür gut ist. Achtung: das alles ist nicht für Linux-Einsteiger gedacht. Ich freue mich über Leute, die so wie ich selbst mindestens schon erste Erfahrungen mit dem Thema gesammelt haben; gerne auch mehr als das ... es geht mir um einen Austausch auf Gegenseitigkeit. Sonntag, 10:00 bis 16:00 Uhr das selbe wie am Samstag :-) Kosten: ======= 10 Euro für Getränke (Kaffee, Kola, ...) [1] Wer im Linuxhotel übernachten will zahlt noch mal 50 Euro pro Nacht im halben Doppelzimmer. Leute, die zu einem relevanten Projekt ( fai, m23, ... ) in relevantem Umfang beigetragen haben zahlen nix. [2] Plätze: ======= Ich denke mit mehr als 20 Leuten macht das alles keinen Sinn. Anmeldung: ========== Bitte eine Mail an iw at linuxhotel.de deren Betreff das Wort "workshop" enthält und die folgende Fragen beantwortet: Wie heißt Du? Von wann bis wann möchtest Du teilnehmen? Möchtest Du im Linuxhotel übernachten? Aktuellere Infos: ================= https://wiki.villa-vogelsang.de/doku.php?id=autoinstall:start Viele Grüße, Ingo Wichmann [1] wer das nicht zahlen kann: daran soll es auch nicht scheitern ... bitte mich ansprechen. [2] Bitte mit mir absprechen, wer sich dieser Gruppe zugehörig fühlt :-)

1 0

partitioning problem
by Sven Geipel 12 Sep '05

12 Sep '05

Hello, I try to auto-install 9.2 and leave my first (windows) partition untouched. How can I do that? When autoyast is partitioning my disk, it deletes the extended partition no. 2 (ok). Then it tries to create first linux partition at start cylinder 0 but there is my windows partition. It should start after end of first partition: device size F type mountpoint start end /dev/hda 37.2GB 0 4864 /dev/hda1 9.9GB NTFS 0 1303 /dev/hda2 39.2MB F ext3 /boot 0 4 /dev/hda3 1GB F swap swap 5 135 ... What I'm doing wrong? Here's the partition part of my autoinst.xml: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <create config:type="boolean">false</create> <format config:type="boolean">false</format> <partition_nr config:type="integer">1</partition_nr> <size>10g</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>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>32m</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> <partition_type>primary</partition_type> <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>12g</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>/save</mount> <partition_id config:type="integer">131</partition_id> <size>max</size> </partition> </partitions> <use>2</use> </drive> </partitioning> -- best regards Sven Geipel

2 4

Syntax to get autoyast to leave existing partitions untouched?
by Paul Beltrani 12 Sep '05

12 Sep '05

I have reviewed the documentation included with autoyast2 v2.11.13 but have been unable to generate a control file which will reuse partitions on an IDE drive. I used autoyast to do an automated install of 9.3Pro on a workstation and had it automatically create, format and mount the following partitions: Part, type, size, FS, mount point 1, primary, 5GB, reiser, / 2, primary, 512MB, swap 3, primary, 512MB, reiser, /var 4, primary, <remainder of drive>, reiser, /export This worked exactly as expected. I then tried to rebuild the system as 10.0RC1 using the exact same control file with the following changes: 1) Do NOT create any of the partitions 2) Only format partitions 1,2 and 3, NOT partition 4 i.e. Do not change the partition layout and do not touch the filesystem on partition 4. When attempting the rebuild yast states it will first delete all 4 partitions then recreate them. In effect it is completely rebuilding the drive and wiping all info. This is not what I would like to happen. I expect this may have something to do with the <use>all</use> property of the second file. However if I specify any value other than "all" or leave it out completely yast fails with the msg "Error while configuring partitions. Try again". Does anyone have a suggestion as to where the error may be? The partitioning portions of control files follow: Initial build: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list"> <partition> <partition_type>primary</partition_type> <partition_nr config:type="integer">1</partition_nr> <partition_id config:type="integer">131</partition_id> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">reiser</filesystem> <mount>/</mount> <size>5GB</size> </partition> <partition> <partition_type>primary</partition_type> <partition_nr config:type="integer">2</partition_nr> <partition_id config:type="integer">130</partition_id> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">swap</filesystem> <mount>swap</mount> <size>512MB</size> </partition> <partition> <partition_type>primary</partition_type> <partition_nr config:type="integer">3</partition_nr> <partition_id config:type="integer">131</partition_id> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">reiser</filesystem> <mount>/var</mount> <size>512MB</size> </partition> <partition> <partition_type>primary</partition_type> <partition_nr config:type="integer">4</partition_nr> <partition_id config:type="integer">131</partition_id> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">reiser</filesystem> <mount>/export</mount> <size>auto</size> </partition> </partitions> <use>all</use> </drive> </partitioning> Re-build: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list"> <partition> <partition_type>primary</partition_type> <partition_nr config:type="integer">1</partition_nr> <partition_id config:type="integer">131</partition_id> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">reiser</filesystem> <mount>/</mount> </partition> <partition> <partition_type>primary</partition_type> <partition_nr config:type="integer">2</partition_nr> <partition_id config:type="integer">130</partition_id> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">swap</filesystem> <mount>swap</mount> </partition> <partition> <partition_type>primary</partition_type> <partition_nr config:type="integer">3</partition_nr> <partition_id config:type="integer">131</partition_id> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">reiser</filesystem> <mount>/var</mount> </partition> <partition> <partition_type>primary</partition_type> <partition_nr config:type="integer">4</partition_nr> <partition_id config:type="integer">131</partition_id> <create config:type="boolean">false</create> <format config:type="boolean">false</format> <filesystem config:type="symbol">reiser</filesystem> <mount>/export</mount> </partition> </partitions> <use>all</use> </drive> </partitioning>

3 2

which script-language for pre-inst.script?
by Boris Wokurka 09 Sep '05

09 Sep '05

Hello list, I want to partition the disc via sfdisk in a pre-install-script. The docu tells me only not to use shell or perl, but not what I can use. My shell-script did not work (BTW, it's the first time I used sfdisk...), it looks like this: <configure> <scripts> <pre-scripts config:type="list"> <script> <interpreter>shell</interpreter> <filename>pre-inst.sh</filename> <source><![CDATA[ #!/bin/sh sfdisk /dev/sda << EOF ,8069,L ,,E ,48381,L ,48172,L ,4102,S ,2023,L ,2008,L ; EOF ]]> </source> </script> </pre-scripts> </scripts> Any hints? Thank You, Boris

3 3

How to install 9.3 from network using DVD and samba?
by HG 08 Sep '05

08 Sep '05

Hi! Hopefully somebody here has done this... could not find anything from google. My main computer crashed (well it was an old one...). So now I'm setting up a "new" computer (another old PIII :-). I have the DVD for SuSE 9.3 Pro, but the computer does not have a DVD player. Another Windows laptop does have. So, what I though I'd do is to start the installation over the network using windows sharing of the DVD. >From SuSE netowkr installation cd: "Start Installation of System" + "network" + "SMB / CIFS (Windows share)" and then use DHCP. Now the installation asks for the samba information. This is what I tried to enter: IP: 192.168.1.101 (obviously home network address" share name: suse (this is also correct) directory on the server: I have no idea what to put here. The default is /. Then comes the login information for the server. Now, if I leave the directory empty, the installation will not start. If I enter the default /, the installation starts and I see network sage from the Windows laptop using task manager. So the share works. Well, this far it is. After that I'll get to the YaST. Language settings and then Installation settings. Everything else looks there just like I expected... except the Software selection, which states: "No source found at "smb://USER:PASSWORD@192.168.1.101/suse//;workgroup=home" and "ERROR: No proposal" What now? What am I doing wrong? -- HG.

2 1

partitioning problem
by Boris Wokurka 08 Sep '05

08 Sep '05

Hello list, I have problems with partitioning and autoinstall on SuSE 9.3. What I want to do on my 120gb SATA disk: sda1 => primary, 8gb, ext3, / sda2 => extended, 8gb sda3 => primary, ext3, 48gb, /home sda4 => primary, ext3, rest (=max), /daten2 sda5 => logical, 4gb, swap sda6 => logical, 2gb, /var, ext3 sda7 => logical, 2gb, /tmp, ext3 What I get is: sda1 => primary, 8gb, ext3, / sda2 => primary, 8gb, unformatted sda3 => primary, ext3, 48gb, /home sda4 => extended, 8gb sda5 => logical, ext3, 40gb, /daten2 sda6 => logical, 4gb, swap sda7 => logical, 2gb, /var, ext3 sda8 => logical, 2gb, /tmp, ext3 My autoinst.xml-partitons section lokks like this: <partitioning config:type="list"> <drive> <initialize config:type="boolean">true</initialize> <device>/dev/sda</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <size>8gb</size> </partition> <partition> <partition_id config:type="integer">15</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>extended</partition_type> <size>8gb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/home</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">3</partition_nr> <partition_type>primary</partition_type> <size>48gb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/daten2</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">4</partition_nr> <partition_type>primary</partition_type> <size>max</size> </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">5</partition_nr> <size>4gb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/var</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">6</partition_nr> <size>2gb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/tmp</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">7</partition_nr> <size>2gb</size> </partition> </partitions> <use>all</use> </drive> </partitioning> I have tried various possibilities (leaving the <partition_type>extended</partition_type>, different sorting etc.) without success. In other words: is it impossible to have an extended partition sda2 with autoyast? Is there a way how to do it? Maybe with pre-install-scripts? Any help would be highly appreciated! Thank you, Boris

4 5

Re: [suse-autoinstall] partitioning problem
by Hans-Joachim Ehlers 08 Sep '05

08 Sep '05

The solution from autoyast make sense for me because afaik the partition order is first the primary and then the extended partition. Also is might be not a good idea to define a patition in the middle of your configyration file with the MAX option. So think about your requriement and do not try to get a extended partition in the middle of primary partitions. BTW: In our environment we do not use primary partitions. hth Hajo >>> Boris Wokurka <boris.wokurka(a)zamg.ac.at> 09/08/05 10:32 am >>> Hello list, I have problems with partitioning and autoinstall on SuSE 9.3. What I want to do on my 120gb SATA disk: sda1 => primary, 8gb, ext3, / sda2 => extended, 8gb sda3 => primary, ext3, 48gb, /home sda4 => primary, ext3, rest (=max), /daten2 sda5 => logical, 4gb, swap sda6 => logical, 2gb, /var, ext3 sda7 => logical, 2gb, /tmp, ext3 What I get is: sda1 => primary, 8gb, ext3, / sda2 => primary, 8gb, unformatted sda3 => primary, ext3, 48gb, /home sda4 => extended, 8gb sda5 => logical, ext3, 40gb, /daten2 sda6 => logical, 4gb, swap sda7 => logical, 2gb, /var, ext3 sda8 => logical, 2gb, /tmp, ext3 My autoinst.xml-partitons section lokks like this: <partitioning config:type="list"> <drive> <initialize config:type="boolean">true</initialize> <device>/dev/sda</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <size>8gb</size> </partition> <partition> <partition_id config:type="integer">15</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>extended</partition_type> <size>8gb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/home</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">3</partition_nr> <partition_type>primary</partition_type> <size>48gb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/daten2</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">4</partition_nr> <partition_type>primary</partition_type> <size>max</size> </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">5</partition_nr> <size>4gb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/var</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">6</partition_nr> <size>2gb</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/tmp</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">7</partition_nr> <size>2gb</size> </partition> </partitions> <use>all</use> </drive> </partitioning> I have tried various possibilities (leaving the <partition_type>extended</partition_type>, different sorting etc.) without success. In other words: is it impossible to have an extended partition sda2 with autoyast? Is there a way how to do it? Maybe with pre-install-scripts? Any help would be highly appreciated! Thank you, Boris -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

YOU wants to install patches that are already installed by multiple source autoinstall
by Teun 07 Sep '05

07 Sep '05

Hello, After a lot of trouble setting up an installation server, serving both a SuSE 9. 3 Pro source and an update source, i finally was able to autoinstall a machine which installed all packages and updates in one go. (So it installs the updated packages straight away and not first the older version.) However, when i then run YaST Online Update on the machine it still wants to install all the updates that are already on the system. It even reports that the installed version of a particular package is the exact same package as the one it wants to install. I already found that if i move a file from /var/lib/YaST2/you/mnt/i386/update/9. 3/patches to /var/lib/YaST2/you/installed the problem is solved for that particular package. But the first directory also contains files for packages that are not installed at all, so just copying all of them would not work. I really hope there is a clean solution to fix this? Any help would be highly appreciated. Regards, Teun

1 1

AutoYAST not using provided updates
by Charles Duffy 07 Sep '05

07 Sep '05

I'm trying to do an autoinstall from a number of sources: - SLES9 base - SLES9 SP1 - Custom updates folder Each of these sources has a different version of rug (which is behaving poorly for me): SLES9 base has 2.0.2 SLES9 SP1 has 2.4.4 updates has 2.4.8 When I install my system, however, I find that it has rug 2.4.4 installed, rather than rug 2.4.8! The "updates" folder was created using create_update_source.sh. Any ideas as to what I may be doing wrong? yast/order: /updates /updates /SUSE-SLES-Version-9-SP1/CD1 /SUSE-SLES-Version-9-SP1/CD1 /SUSE-SLES-Version-9-SP1/CD2 /SUSE-SLES-Version-9-SP1/CD2 /SUSE-SLES-Version-9/CD1 /SUSE-SLES-Version-9/CD1 /SUSE-CORE-Version-9/CD1 /SUSE-CORE-Version-9/CD1 / yast/instorder: /updates /SUSE-SLES-Version-9-SP1/CD1 /SUSE-SLES-Version-9-SP1/CD2 /SUSE-SLES-Version-9/CD1 /SUSE-CORE-Version-9/CD1 /

2 1

Media files
by Robison, Jonathon (M.) 07 Sep '05

07 Sep '05

Can anyone tell me which files on a CD describe which CD an rpm is on? i.e. how does YaST know which CD to ask for during installation? --Jon Robison

2 1