January 2009 - openSUSE Autoinstall - openSUSE Mailing Lists

[opensuse-autoinstall] Opensuse 11.1 nis_by_dhcp config?
by Pierre Girard 27 Jan '09

27 Jan '09

Hello, in my autoyast 11.0 configuration there was an option to get nis servers from dhcp. That option doesn't seem to be available in 11.1. Is that the case? Is there an alternative to that? -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] Upgrade from SLES 9 to SLES 10 silently/automatically
by Enamul Haque 21 Jan '09

21 Jan '09

I am trying to upgrade from SLES 9 to SLES 10. When I boot from the SLES 10 DVD, I am presented the following questions: 1. Select Boot from disk or Installation 2. Select New installation or Upgrade 3. Select Language 4. Accept License Agreement 5. Select root partition .... For the OEM customers, I would like to automate the upgrade process. I would like something similar to autoyast. Is it possible to upgrade SLES 9 to SLES 10 silently (without any end-user input)? If yes, how? TIA, Enamul -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] Add on software and autoyast classes problems.
by Salmon, Rene 21 Jan '09

21 Jan '09

Hi, I am trying to get use classes with autoyast. The class I am trying to use also include an add-on product. My xml looks like this. <?xml version="1.0"?> <!DOCTYPE profile> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.c om/1.0/configns"> <deploy_image> <image_installation config:type="boolean">false</image_installation> </deploy_image> <add-on> <add_on_products config:type="list"> <listentry> <media_url>nfs://1.2.3.4/data1/suse/SLES/sles-devel- DVD1</media_url> <product>SUSE Linux Enterprise Software Development Kit</product> <product_dir>/</product_dir> </listentry> </add_on_products> </add-on> <software> . . . .</software> <classes config:type="list">  <class> <class_name>BASE</class_name> <configuration>base.xml</configuration> <dont_merge config:type="list"> <element>script</element> </dont_merge> </class> </profile> If I merge the above xml and the base.xml into a single file myself and run autoyast everything works fine. If I try to run the above xml and the base.xml as a class autoyast complains with an error message that states it can't find the add-on product. Any ideas as to why? is there a particular place the add-on section should go in? is there a particular order to get this to work? thanks Rene -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 6

[opensuse-autoinstall] 11.1 autoyast UI: Online Update vs. Online Update Configuration
by Andreas Vetter 09 Jan '09

09 Jan '09

In yast2 - autoinstallation -software are two entries: - Online Update - Online Update Configuration the upper does not do anything. Bug or feature? -- Mit freundlichen Gruessen, Andreas Vetter -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 5

[opensuse-autoinstall] Re: kexec failing
by Bernhard Walle 09 Jan '09

09 Jan '09

* Henrik Schmidt [2009-01-09 11:25]: > > During autoinstallation kexec is booting the kernel. This often fails > here on different computers and the system hangs at this stage. I have > to reset the computer for the installation to continue. Up to now it > happened 3 times out of 9 installs. Sometimes it works on the same > machine, sometimes not. SLES or openSUSE? You can disable kexec with kexec_reboot=0 in the command line. In SLES it is disabled by default, in openSUSE it's enabled by default. Bernhard -- Bernhard Walle, SUSE Linux Products GmbH, Architecture Development -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] "EDD information not available" messages during v11.1 autoyast install?
by PGNet 08 Jan '09

08 Jan '09

I'm building/booting a Xen DomU using an Autoyast template. Under opensuse v11.0 (as Dom0 & DomU) all's well. Under v11.1, I see a bunch of 'new', EDD-related messsages @ console -- & I'm not clear if they're just new diagnostic, or a new problem: ... >>> openSUSE installation program v3.3.22 (c) 1996-2008 SUSE Linux Products GmbH <<< Starting udev... udevd version 128 started rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0 netfront: Initialising virtual ethernet driver. xen-vbd: registered block device major 202 blkfront: xvda: barriers enabled xvda: unknown partition table ok GGLoading basic drivers...Uniform Multi-Platform E-IDE driver SCSI subsystem initialized st: Version 20080504, fixed bufsize 32768, s/g segs 256 BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. NET: Registered protocol family 17 BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. NET: Registered protocol family 10 lo: Disabled Privacy Extensions BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. RPC: Registered udp transport module. RPC: Registered tcp transport module. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. loop: module loaded BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. ok BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. Starting hardware detection... ok (If a driver is not working for you, try booting with brokenmodules=driver_name.) Xen Virtual Storage 0 ... My autoyast template starts with, <?xml version="1.0"?> <!DOCTYPE profile> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <initrd_module><module>edd</module></initrd_module> <bootloader> <loader_type>grub</loader_type> <initrd_modules config:type="list"> <initrd_module><module>xenblk</module> </initrd_module> <initrd_module><module>xennet</module> </initrd_module> <initrd_module><module>processor</module></initrd_module> ... Something's changed from v11.0 -> v11.1. Is there something I need to do differently to avoid/fix these messages? Or, are they not a problem, just 'noisy' reporting? Thanks. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 4