openSUSE Autoinstall May 2008

autoinstall@lists.opensuse.org

22 participants
19 discussions

by John Willis

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!

9 years, 5 months

[opensuse-autoinstall] best way to install "own" rpms

by Ralf Prengel

Hallo, what is the best way to manage and install own rpm-collections. My idea: 1) saving the rpms in an own repo 2) adding this repo while autoyast is installing the system 3) installing the packages after the basic-system is ready using a script My idea is that an own rep gives me the chance to manage updates for these packages too. Thanks for hints and ideas. -- i.A. Ralf Prengel Customer Care Manager Comline AG Hauert 8 D-44227 Dortmund/Germany Fon +49231 97575- 904 Fax +49231 97575- 905 EMail ralf.prengel(a)comline.de www.comline.de Vorstand Stephan Schilling, Erwin Leonhardi Aufsichtsrat Dr. Franz Schoser (Vorsitzender) HR Dortmund B 14570 USt.-ID-Nr. DE 124727422 -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

13 years, 11 months

[opensuse-autoinstall] 10SP2

by LDB

Cannot add 10SP2 SDK as an installation source for autoyast or within YasT. I get a "cannot add installation source /var/adm/mount/APx000000 ..." dialog with 10SP2 SDK ... Is there something special I need to perform besides copying the DVD to the disk? Thanks, LDB -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

13 years, 11 months

[opensuse-autoinstall] How to configure LVM in AutoYast?

by Wil Decius

Hello, 1. In the AutoYast docs, http://www.suse.com/~ug/autoyast_doc/CreateProfile.Partitioning.html, the Description for attribute("is_lvm_vg"), says "DEPRECATED since SLES10SP1 and SL10.2 - use type instead. Must be true if this device is a LVM volume group. The default is false." The examples on that page only use the old "<is_lvm_vg config:type="boolean">true</is _lvm_vg>" and not the new "type". Can someone give an example of the correct, new usage? 2. I want to make an LVM created by autoyast "grow-able". All of the examples I found for doing this in autoconfiguration talk about using "--grow" in Red Hat Kickstart. How do I define "grow-able" in Autoyast? Wil -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

13 years, 12 months

[opensuse-autoinstall] YaST and UNIQUE in ifcfg-eth-id.....

by Colin Topliss

Hi, I have a large number of systems I need to install (250+), and I want to generate the network config files for the NICs (of which there are 4) using a script rather than having to go into yast on every single server to do it (because I am using bonding and need the configs there to start with). I have everything I need to generate the ifcfg-eth-id config - except I can't see how to generate the UNIQUE value. Looking at the comments in /etc/sysconfig/network/ifcfg.template (which say that UNIQUE is an internal variable for YaST), I'm not even sure I need to worry about it? So, the questions are: 1) Is there something that already exists that I can use to generate the config rather that writing my own script? 2) If not, do I need to generate a UNIQUE entry? 3) If I need the UNIQUE entry, now can I generate it? Thanks Colin. Ericsson Limited Registered Office: Unit 4, Midleton Gate, Guildford Business Park, Guildford, Surrey, GU2 8SG Registered Number in England and Wales: 942215 This communication is confidential and intended solely for the addressee(s). Any unauthorised review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you. Ericsson Limited does not enter into contracts or contractual obligations via electronic mail, unless otherwise agreed in writing between the parties concerned. E-mail including attachments is susceptible to data corruption, interruption, unauthorised amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof. ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

13 years, 12 months

[opensuse-autoinstall] Adding kernel parameters to the bootloader

by Lonni J Friedman

Is there a straightforward means of appending additional kernel parameters to the bootloader (GRUB) kernel line without having to create a fully populated bootloader section? -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

13 years, 12 months

Re: [opensuse-autoinstall] no user root in reference xml file

by Uwe Gansert

On Friday 16 May 2008, you wrote: > 10.3 is in use > > > > > which Version of SUSE do you use? I'll never get used to that kind of quoting. Anyway, please reply to the list always. It works for me here. Do you have yast2-users installed and did you check the checkbox to clone the user management? -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

13 years, 12 months

[opensuse-autoinstall] no user root in reference xml file

by Ralf Prengel

Hallo, i m using Yast2 autoyast to build an reference-file. That is working fine and an full installtion via small bootdisk and autoyast using a http-server works fine. But now after several experiments I ve the following problem. The users aren t stored any longer in the xml-file. That is definitly a problem because without a working root-login nothing works. It s no problem to merge an older working file with a newer one to configure root but I want to find out what is going wrong. Thanks for hints Ralf Prengel -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

14 years

[opensuse-autoinstall] LVM partitioning on multiple drives without specifying device

by Magnus Boman

Hello, I'm trying to create an autoinstall configuration that's as generic as possible. It'll be used on VMware, Xen and on physical machines with two drives. The problem I have is that I can't create the partitioning scheme without specifying <device>/dev/xvda</device> and <device>/dev/xvdb</device>. Anyone know if it's possible to configure this so that it automatically figures this out? Thanks, Magnus <partitioning config:type="list"> <drive> <device>/dev/system</device> <lvm2 config:type="boolean">true</lvm2> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>root</lv_name> <mount>/</mount> <mountby config:type="symbol">device</mountby> <size>3393191936</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <lv_name>swap</lv_name> <mount>swap</mount> <mountby config:type="symbol">device</mountby> <size>805306368</size> </partition> </partitions> <pesize>4M</pesize> <type config:type="symbol">CT_LVM</type> <use>all</use> </drive> <drive> <device>/dev/tmp</device> <lvm2 config:type="boolean">true</lvm2> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>tmp</lv_name> <mount>/tmp</mount> <mountby config:type="symbol">device</mountby> <size>1069547520</size> </partition> </partitions> <pesize>4M</pesize> <type config:type="symbol">CT_LVM</type> <use>all</use> </drive> <drive> <device>/dev/xvda</device> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">ext2</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount> <mountby config:type="symbol">device</mountby> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <size>57544192</size> </partition> <partition> <create config:type="boolean">true</create> <lvm_group>system</lvm_group> <partition_id config:type="integer">142</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <size>4203118080</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/xvdb</device> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <lvm_group>tmp</lvm_group> <partition_id config:type="integer">142</partition_id> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <size>4285338112</size> </partition> </partitions> <use>all</use> </drive> </partitioning> -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

14 years

[opensuse-autoinstall] keep_install_network and default route

by Axel Geyer

Hello, I am trying to follow the instructions in http://lists.opensuse.org/opensuse-autoinstall/2008-02/msg00045.html to change from a dhcp configuration to a static configuration with the information that the machine received during installation. I have this in my xml file: <networking> <keep_install_network config:type="boolean">true</keep_install_network> </networking> ifcfg-eth0 and routes are created in a post script using the information of /var/lib/dhcpcd/dhcpcd-eth0.info The ifcfg-eth0 remains on the machine, but the routes file gets moved to routes.YaST2save and an empty routes file is created. So the system has no defaut route. How can I make shure that also the routes file will survive the installation process? Thank you in advance. Axel Geyer s+c ag -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

14 years

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall May 2008