August 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

Addon-Media on Autoyast of SuSE 10.1
by Daniel Spannbauer 11 Aug '06

11 Aug '06

Hallo, I try to Install some Packages from a Addon-Media. This Media is on a NFS-Share. So if I try to configure the XML-File with the Autoyast-Tool from SuSE 10.1 I get an Error when I try to configure the Addon-Source. The "normal" Yast is accepting that Media. Is this a Bug or did I something wrong? Regards Daniel Daniel Spannbauer EDV Systembetreuung marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-66 Auf der Wies 8, D 87727 Babenhausen Fax +49 8333 9233-11 http://www.marco.de/ Email ds(a)marco.de

2 6

Reusing fstab and saving partitions issue (sles9-sp1/3)
by Mike Marion 11 Aug '06

11 Aug '06

I really like being able to re-use the exiting fstab file and to save partitions (/local/mnt and /local/scratch in our case.. they're paths we use) but I have one problem. Everything works as expected but the installation hangs at the end with the error: Root device: /dev/cciss/c0d0p2 (mounted on / as reiserfs) Module list: cciss amd74xx reiserfs () Screenshot for the curious: http://www.miguelito.org/images/autoyast.png If I get on the console and hit ok.. everything is fine. But I'd like to remove the need for that. That case happens to be on an HP box.. doesn't matter the hardware, whether ide disks, sata, whatever. Dropping into console 2 and using fuser, I find the following process holding /mnt (same named process everytime): root 6428 0.0 0.1 59769 8276 tty1 S+ 17:43 00:00 scr stdio scr Obviously the pid, memory, etc change.. but it's always 'scr stdio scr' This never happens when I don't reuse the fstab file. Any clues why this proc sticks around like this when I do? The xml file bit to reuse the fstab is: === <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <install> <partitioning_advanced> <fstab>  <use_existing_fstab config:type="boolean">true</use_existing_fstab>  <partitions config:type="list"> <partition> <format config:type="boolean">false</format> <mount>/local/mnt</mount> </partition> <partition> <format config:type="boolean">false</format> <mount>/local/scratch</mount> </partition> </partitions> </fstab> </partitioning_advanced> </install> </profile> === Am I missing some config bit in there? -- Mike Marion-Unix SysAdmin/Staff IT Engineer-http://www.qualcomm.com "Thanks for inquiring, the spell chicker works fine." --Computer Stupidities http://www.rinkworks.com/stupid

2 2

User root in config-File?
by Daniel Spannbauer 10 Aug '06

10 Aug '06

Hello, I've cloned my SuSE 10.1-System. Nw I opened the xml-File with kxml-editor but I can't find the entry for the User "root" and his password? When I install with autoyast and this XML-File the User "root" is there but has no password so I can't login. How ca I fix this? Regards Daniel Daniel Spannbauer EDV Systembetreuung marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-66 Auf der Wies 8, D 87727 Babenhausen Fax +49 8333 9233-11 http://www.marco.de/ Email ds(a)marco.de

2 3

LVM configuration with SLES10
by tobias.mucke＠man-mit.com 10 Aug '06

10 Aug '06

Hi list, I have a complex partitioning setup with LVM. Some partitions have to be added to a VG vg_system. These are tagged with lvm_group in xml file. Then I create LVs for the most important FS. After installation everything seems fine, but all partitions are added to vg_system and logical volumes are spreaded over all partitions! Has anybody seen this before? Here is my partitioning setup. <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <partitioning config:type="list"> <drive> <device>/dev/cciss/c0d0</device> <partitions config:type="list"> <partition> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <partition_id config:type="integer">131</partition_id> <size>128M</size> <filesystem config:type="symbol">ext2</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount> </partition> <partition> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <partition_id config:type="integer">130</partition_id> <size>4G</size> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> </partition> <partition> <partition_nr config:type="integer">3</partition_nr> <partition_type>primary</partition_type> <partition_id config:type="integer">142</partition_id> <size>3G</size> <lvm_group>vg_system</lvm_group> </partition> <partition> <partition_nr config:type="integer">5</partition_nr> <partition_id config:type="integer">142</partition_id> <size>3G</size> <lvm_group>vg_system</lvm_group> </partition> <partition> <partition_nr config:type="integer">6</partition_nr> <partition_id config:type="integer">142</partition_id> <size>3G</size> <lvm_group>vg_system</lvm_group> </partition> <partition> <partition_nr config:type="integer">7</partition_nr> <partition_id config:type="integer">142</partition_id> <size>3G</size> <lvm_group>vg_system</lvm_group> </partition> <partition> <partition_nr config:type="integer">8</partition_nr> <partition_id config:type="integer">142</partition_id> <size>3G</size> </partition> <partition> <partition_nr config:type="integer">9</partition_nr> <partition_id config:type="integer">142</partition_id> <size>3G</size> </partition> <partition> <partition_nr config:type="integer">10</partition_nr> <partition_id config:type="integer">142</partition_id> <size>3G</size> </partition> <partition> <partition_nr config:type="integer">11</partition_nr> <partition_id config:type="integer">142</partition_id> <size>3G</size> </partition> <partition> <partition_nr config:type="integer">12</partition_nr> <partition_id config:type="integer">142</partition_id> <size>3G</size> </partition> <partition> <partition_nr config:type="integer">13</partition_nr> <partition_id config:type="integer">142</partition_id> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/vg_system</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <lvm2 config:type="boolean">true</lvm2> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>lv_root</lv_name> <mount>/</mount> <size>1G</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>lv_usr</lv_name> <mount>/usr</mount> <size>2G</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>lv_usr_local</lv_name> <mount>/usr/local</mount> <size>512M</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>lv_opt</lv_name> <mount>/opt</mount> <size>2G</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>lv_srv</lv_name> <mount>/srv</mount> <size>512M</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>lv_var</lv_name> <mount>/var</mount> <size>1G</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>lv_var_tmp</lv_name> <mount>/var/tmp</mount> <size>1G</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>lv_home</lv_name> <mount>/home</mount> <size>1G</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>lv_tmp</lv_name> <mount>/tmp</mount> <size>1G</size> </partition> </partitions> <pesize>32M</pesize> <use>all</use> </drive> </partitioning> </profile> Tobias This message and any attachments are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person.

2 3

Information available to postinstall, and DHCP
by Andrew Laden 10 Aug '06

10 Aug '06

Hello New to the list, and new to autoyast in general. I did a quick archive search, but didn't find anything. I have pxeboot with dhcp working, and can autoyast my way up to a running system. A few questions.. 1: Is there a reference doc of what information is available to postinstall scripts. (ie, IP address, install server, etc) I know I could probably run some commands in postinstall to get it, but If there are preset varaibles, it would be easier. 2: Is there a way to have autoyast configure the interface that uses for the install to use dhcp for its IP address, hostname, router, resolve.conf etc. Right now after the install, the machine reboots, It gets it IP. But DHCPCD isnt running, it thinks its hostname is "linux.site" and has no meaningful network info. The interfaces are listed as unconfigured in YaST. 3: What information needs to be in the linuxrc.config file in the initrd, vs the pxeconfig boot file. ie, if I have install=nfs://<NFSSOURCE> insmod=bcm5700-new autoyast=nfs://<AUTOYASTSRC> in my pxeconfig boot file, do I also need them in the linuxrc.config file? Right now I have similar entries in both. I'd rather strip down so I can use the same initrd for all machines, and supply as much info as possible in the pxeconfig file and via dhcp. Idealy I'd like the same initrd, the same pxeconfig file, and do everything via dhcp. 4: Is there a more detailed document as to actual parameters you can use in an autoyast file. The doc gives lots of samples, but not the full list. If you don't want to do things like the examples, you are out of luck it seems. Thanks -Andrew

2 1

ntp server in sles9
by Salbeck, Christian, MSOP51 09 Aug '06

09 Aug '06

Hi list, in SLES9 I want a list of ntp-servers, 2 clocks and a local server. For a local server i want to add the following entry to /etc/ntp.conf: server 127.127.1.0 fudge 127.127.1.0 stratum 10 Adding the ntp.conf via the files-section doesn't work. So I used the xml-file: The xml -file looks like this: <ntp-client> <peers config:type="list"> ... <peer> <address>127.127.1.0</address> <initial_sync config:type="boolean">true</initial_sync> <fudge_options>127.127.1.0 stratum 10</fudge_options> <type>server</type> </peer> </peers> <start_at_boot config:type="boolean">true</start_at_boot> <start_in_chroot config:type="boolean">true</start_in_chroot> </ntp-client> The problem is, that the <fudge_options> tag does not affect the ntp.conf file. It seems it doesn't work at all. I got that tag out of the ntp-client.dtd, by the way! So, is there any way of getting that line into place? mit freundlichen Grüssen Salbeck Christian Dipl.-Ing.(FH) www.eads.com <http://www.eads.com/> EADS Deutschland GmbH Coastal Surveillance Systems MSOP51 Landshuter Straße 26 85716 Unterschleißheim Germany <http://link2.map24.com/?street0=Landshuter+Str.+26&zip0=85716&city0=Untersc…> Phone: +49 (089) 3179 - 2102 E-Mail christian.salbeck(a)eads.com <mailto:christian.salbeck@eads.com>

2 1

Local online update server
by Andrew Laden 08 Aug '06

08 Aug '06

While I still have outstanding questions from my last email, I have a few more. I am trying to set up a Local YOU server. I have enabled http, and that part looks fine. I have run online_update -G to pull down all the patches, and I see a lot of data under /var/lib/YaST2/you/mnt When I try to connect to the server from a newly built machine, using online update, most of the commands list no patches. (ie, -s is blank, -k reports no updates available) Yet when I connect to https://you.novell.com/Updates <https://you.novell.com/Updates> , it shows a list of patches, and indicates updates available. Is there some trick to setting up a local YOU server to make it respond the same way that Novell's does? Or is there something odd with Novell's YOU server. (I used to use sdb.suse.de, but it stopped responding yesterday, though it looks like it is back today. Also, when I first build a server, it want to get the patch-youfix from novell. Is there a way to serve that patch up from my local YOU server as well? Thanks -Andrew

1 0

Re: [suse-autoinstall] add_on_products fails to add source
by Frank Steiner 08 Aug '06

08 Aug '06

Hmm, file to large to send to the list. I've put it here: http://www.bio.ifi.lmu.de/~steiner/y2log.gz Uwe Gansert wrote >> Do you want the full logfile? > > yes, that can't hurt but I'll take a look at it tomorrow. Ok, thanks! I've shortened the software section to <software> <base>Minimal</base> </software> to make the logfile shorter. The add_on_products file contains nfs://<our ip>//rpm-export/i586/10.1/SuSE/updates and the updates/ subdir has created with your script. I wonder if I missed sth. again :-/ cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

2 3

add_on_products fails to add source
by Frank Steiner 07 Aug '06

07 Aug '06

Hi, after failing to integrate own packages into the standard SuSE sources (see my former mail), I tried the way described for SuSE 10.1. I created a file add_on_products in the SuSE source directory, with content nfs://<my_ip>/rpm-export/i586/10.1/addons In this directory I added a i586/ subdirectory, containing my own packages, and called create_package_descr, so that the addons subdir now contains i586/ setup/ But autoyast still fails to add e.g. the kernelbio-source rpm that I include in the <packages> list. Looking at y2log I see that AY mounts the addons directory and tries to identify it as some sort of source: First it tries to find /repodata/repomd.xml and concludes it's not a YUM source. Then it fails to find /media/media.1, so it's also not a "SUSE tags source", then AY says "No next type of source" and fails to add the addons/ directory. What's wrong? What else do I need to do? The online HOWTO and the FAQ don't mention anything else... cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

3 8

Swap as an LVM volume not working ?
by Bruno Marcondes 07 Aug '06

07 Aug '06

Hello guys, i'm trying to make a fs layout with swap as a LVM logical volume, my autoyast configuration is something like this <partitioning> ... <drive> <device>/dev/vol</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <lv_name>swap</lv_name> <mount>swap</mount> <size>1gb</size> </partition> <partition> ....  ... </drive> .... </partitioning> During the installation process YaST tries to mount /dev/vol/swap as an reiserfs partition and got error code "-3003" :( Am I doing something wrong , missing some configuration ? Removing this swap partition under the /dev/vol device makes it all work... Thanks in advance ! []'s -- "If you really want something in this life, you have to work for it. Now, quiet! They're about to announce the lottery numbers..." - Homer Simpson

2 1