openSUSE Autoinstall September 2010

autoinstall@lists.opensuse.org

9 participants
13 discussions

linuxrc - netdevice=<hwaddress>
by John Willis 18 Dec '12

18 Dec '12

Does anyone know if any of the SLES releases 9 or 10 support passing the linuxrc option netdevice=<hardware mac address> ? I noticed Red Hat has had this for sometime and it seems totally missing in SuSE which seems really odd. I'm still scratching my head if we really are still passing only by kernel interface name. I read in the change log for linuxrc-1.8.6-3 a change that "sounds" like this feature. * Mon Mar 14 2005 - snwint(a)suse.de - s390: fix segfault in net_list_s390_devs() - extra root image was sometimes not used - allow netdevices to be specified by hwaddress But it looks like linuxrc-1.8.6-3 is only available in SuSE Professional 9.3. "any" commentary would be sincerely appreciated the feature also seems to be fairly minor since any delimiter seperating the octets in the hwaddr string could be used to identify the difference between an interface name and interface hw address if i could figure out a generic method of overriding the linuxrc with a custom script and daisy chain it back into linuxrc after setting up the interface name, I would.. and have a slight idea on how to do that.. but i'd rather find out i'm just missing something and the feature is already there Thanks!

3 2

[opensuse-autoinstall] Repository Priority
by Tim Kirby 28 Sep '11

28 Sep '11

Repository Priority is obviously a useful thing to be able to manipulate. Yast lets me set it and zypper lets me set it. Yet, if I have multiple repositories defined at the beginning of my autoyast (including update repos so I get an up to date system built out of the box), I don't seem to have any control over the respective repository priorities - they're all defaulted. Or did I miss a subtle option somewhere? Tim -- Tim Kirby 651-605-9074 trk(a)cray.com Cray Inc. Information Systems -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 2

[opensuse-autoinstall] OT: Centralized patch management for OpenSuse 11.x
by Ivan De Masi 14 Jan '11

14 Jan '11

Hello, someone may start to laugh now for my (OT) question, but I can't find a satisfying solution :-/ How do you manage patches, updates, etc. for your running opensuse clients (not enterprise linux, just the "regular" opensuse distribution)? Is there a way like known from M$-World (WSUS)? As I know "Zend Management Server" is not open source (and not supported any more?!). Or can the complete management only be handled with self written scripts? Thanks! Regards, Ivan -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 3

[opensuse-autoinstall] Skip software installation
by 686f6c6d 19 Nov '10

19 Nov '10

Greetings, is it possible to skip steps of the installation procedure, like partitioning and software installation? I'm trying to set up an autoyast profile (for an installation CD) that basically just asks a few (network) values in the initial stage, patches them back into the bootloader section of the profile and then just installs the bootloader with these values, skipping everything else. After reboot, the machine uses the boot parameters to fetch the "real" installation profile from a server and does a "normal" installation. (After installation, the machines will be managed by bcfg2.) The reason I'm trying to do this is twofold: First, I have to give those discs out to users and would like to never change them, if possible. Thus, the split-up between "bootstrap" and the real, changeable, profile on the network. Second, it is unlikely these users will have DHCP available, and I don't want them having to type endless boot parameters like hostip=1.2.3.4 netmask=255.255.255.0 gateway=1.2.3.1 install=http://network-repo/... autoyast=http://network-source/... So, is this possible with autoyast, or do I have to resort to putting more complexity on the CD, (changing things after installation with bcfg2) and possibly sending out new discs for profile errors/enhancements and new openSUSE releases? thanks, 686f6c6d -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 4

[opensuse-autoinstall] Adding packages to profile triggers error message
by Isaac Hailperin 07 Nov '10

07 Nov '10

Hi, I try to install sles 11 via autoyast. I did an installation from dvd, and pulled an autoyast profile. This profile works, and can be installed via pxe. Now I want to add the following packages: findutils-locate, dhcp-server, bind, apache2, vsftpd, nfs-kernel-server I do this via the gui. I have also tried to do it with an editor, as the gui messed up profiles in sles10sp2. In both cases, after the first reboot, I get the errormessage: "The package resolver run failed. Please check your software section in the aut" [oyast profile] (last part invisible, I guess it should be the software section in my autoyast profile :-)) This a real problem, as I have to confirm this message, thus it stops the autoinstall process. After confirming, the autoinstall process continues. Right bevor I can log in, I get "Could not update ICEauthority file /var/lib/gdm/.ICEauthority" I confirm, and get: "There is a problem with the configuration server. (/usr/lib/GConf/2/gconf-sanity-check-2 exited with status 256)" I confirm, and can log in. Theses messages are presistend after reboot. Its annoying, but not a stopper like the first problem. Why is this? Can I avoid this? Isaac -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 2

[opensuse-autoinstall] Packages in add-on product do not get installed
by Andreas Taschner 29 Oct '10

29 Oct '10

Hi Have enjoyed the YaST add-on-creator and built an add-on with a hello-world package. Impressing tool BTW - must be popular. (Only changed the vendor from the default in the wizard). Including it in the autoyast profile (for SLES11SP1) <add_on_products config:type="list"> <listentry> <media_url>http://atw510.nts.com/Andreas-add-on</media_url> <product>Andreas-add-on</product> <product_dir>/</product_dir> <name>Hello-world-name-addon-product</name> </listentry> </add_on_products> results in the following : 0) The Add-On product is not shown in the package installation window 1) zypper products lists the product, but not as installed 2) The service and repository for the add-on are enabled 3) The package does not get installed automatically Have I done something wrong in the creation of the add-on, or do I need to modify the profile to explicitly request installation of all/every package in the add-on repo ? Related question : Is it possible to have the add-on on a separate DVD (customer needs to install on isolated servers in outposts with no infrastructure) and get the installation flow to eject the installation medium and ask for another DVD ? Thanks. Best regards Andreas -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 5

[opensuse-autoinstall] LDAP server
by Lars Stavholm 17 Oct '10

17 Oct '10

s it possible to use autoyast to include an LDAP server setup in the installation? /L -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 3

[opensuse-autoinstall] Persistent enumeration of net devices
by Andreas Taschner 28 Sep '10

28 Sep '10

Hi My customer has run into what seems to be a general problem regarding the network interface names. They want to create an autoyast-based install of SLES11 on 100+ HP DL380 and DL360 machines, which are all equipped with an extra interface card. However Linux maps the logical interfaces depending on which of the internal or the extra card that answer first during the installation. This mapping can also differ from one OS installation to the next on the same box. We somehow need to ensure persistent mapping of device names to real physical ports. Trying to work around this they have developed as script that will be run after the SLESinstallation. The script will replace the /etc/udev/rules.d/70-persistent-net.rules file with new rules that * Splits the name space of eth into "drivername" with individual enumeration, for each driver. * Uses busid instead of MAC to facilitate easy swap of broken cards. Also pci bus-id naming seems to follow the physical port assignment on the ports, which MAC address does not. However there must (hopefully) be an easier way of achieving this.. Despite searching high and low we have had no success in finding out how to switch to bus-id instead of MAC and to adapt the naming in /lib/udev/write_net_rules. How to do using yast2 is well described, but autoyast or adapting the generator scripts is very unclear. Most information talks about changing the rule-file itself, but not the scripts that generate it. Any information on how to do this would be most helpful. Thank you. Best regards Andreas Taschner Designated Support Engineer Novell Making IT work as one www.novell.com -- 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] rules
by dutchguy69 28 Sep '10

28 Sep '10

Hello, I would like to make a custom rule that can differentiate between a kde and gnome installation. What is possible around setting a variable somehow that can then be used for this selection between the 2 display managers. I'm using a linuxrc info file to start the whole installation process, would it be possible to do something in here that can be used within the rules file to detect whether to install gnome or kde. Where can I find more information around this since I have been searching for this but so far not found anything useful. -- 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_products.xml priority
by Lars Stavholm 24 Sep '10

24 Sep '10

Does anyone know how to specify the repo priority in add_on_products.xml? /Lars -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall September 2010