openSUSE Autoinstall June 2007

autoinstall@lists.opensuse.org

21 participants
22 discussions

[opensuse-autoinstall] Installer resolution

by Alan Mosca

Hi, I was wondering if there was an option to change the screen resolution used in the install process, can anyone help? Thanks. -- Alan Mosca -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

15 years

[opensuse-autoinstall] Configuring multiple volume groups

by Oliver Schweikert

Hi list, I have problems to create a working autoyast profile with 2 physical volumes and 2 volume groups. I am using SLES 10 and profile works for one VG. After adding another PV and a VG, yast complains, that it could not create "a logical volume of requested size" an no note has been logged to y2log. Size of disks is large enought available, of course. Here is the partitioning part of my profile: <partitioning config:type="list"> <drive> <device>/dev/cciss/c0d0</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext2</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>auto</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_type>primary</partition_type> <size>auto</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>1GB</size> </partition> <partition> <lvm_group>system</lvm_group> <mount></mount> <partition_id config:type="integer">142</partition_id> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/system</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>usr</lv_name> <mount>/usr</mount> <size>2GB</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>var</lv_name> <mount>/var</mount> <size>2GB</size> <partition> <filesystem config:type="symbol">ext2</filesystem> <format config:type="boolean">true</format> <lv_name>tmp</lv_name> <mount>/tmp</mount> <size>1GB</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>srv</lv_name> <mount>/srv</mount> <size>5GB</size> </partition> </partitions> <pesize>4M</pesize> <use>all</use> </drive> <drive> <device>/dev/cciss/c0d1</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <lvm_group>database</lvm_group> <mount></mount> <partition_id config:type="integer">142</partition_id> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/database</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiserfs</filesystem> <format config:type="boolean">true</format> <lv_name>oracle</lv_name> <mount>/var/opt/oracle</mount> <size>20GB</size> </partition> </partitions> <pesize>4M</pesize> <use>all</use> </drive> </partitioning> I also tried to use 2 seperate partitioning elements, but the later one overrides all. Also surprising was, that when using an empty partions list for the second volume group, a `pvscan' during installation shows, that both PVs are assigned to the same VG 'system'. Has anybody an idea? Regards Oliver -- Oliver Schweikert Software Development Horiba Europe Automation Division GmbH Zabergäustr. 3 73765 Neuhausen Tel: +49 - (0)7158-933-413 Fax: +49 - (0)7158-933-613 -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

15 years

[opensuse-autoinstall] nfs mount options in info file?

by Jochen Schaefer

Hi list, how can I specify nfs options in the info file? When installing SLES10-SP1-RC5 via nfs we tried nfs://10.1.6.1/install/sles10-sp1-rc5,fg,nointr,hard,v3,nolock,rsize=32768,wsize=32768,udp,noacl the result in the installation environment was: cat /proc/mounts ... 10.1.6.1:/install/sles10-sp1-rc5 /var/adm/mount/AP_0x00000001 nfs ro,v3,rsize=32768,wsize=32768,soft,nolock,proto=tcp,addr=10.1.6.1 0 0 see the difference: udp changed to tcp and hard to soft So it seems that the parameters given with the above used syntax are partially ignored. Thanks, Jochen -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

15 years

[opensuse-autoinstall] mount option "notail" in autoyast

by Jung, Jochen

Hi, I'm trying to mount a reiserfs filesystem with the notail option using autoyast, but it seams to me, autoyast can not handle this option. Here is an example, what my partition definitions in autoyast.xml look like: <partition> <filesystem config:type="symbol">reiser</filesystem> <lv_name>rootlv</lv_name> <fstopt>defaults,notail</fstopt> <mount>/</mount> <size>500mb</size> </partition> I tried an installation of SLES9. Maybe autoyast just understands the "normal" options, wich could be used along with any filesystem. Has anyone successfully createt a partition with the notail option? With kind regards Jochen Jung > Freudenberg IT > > Freudenberg Hosting KG > Hoehnerweg 2 - 4 > 69469 Weinheim, Germany > County Court Mannheim, HRA 431161 > Phone +49 (0) 62 01 80-82 47 > mailto: jochen.jung(a)freudenberg-it.com > http://www.freudenberg-it.com > -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

15 years

[opensuse-autoinstall] Problem with local update repository

by Stephens, Bill {PBSG}

Hi, I'm really scratching my head on this one. I had a working update directory for my SLES10 install tree. I pulled down the current updates from Novell's site, and ran create_package_descr -x setup/descr/EXTRA_PROV. Now when I try to install from my source tree, my script only wants to install 18 packages, instead of the requested packages: <packages config:type="list"> <package>gnome-vfs2-32bit</package> <package>libbonobo-32bit</package> <package>libidl-32bit</package> <package>orbit2-32bit</package> <package>gdbm-32bit</package> <package>gdbm-devel</package> <package>rpm-python</package> <package>python-elementtree</package> <package>python-sqlite</package> <package>python-urlgrabber</package> <package>dbus-python</package> <package>pygobject2</package> <package>yum</package> <package>yum-utils</package> <package>yumex</package> <package>kyum</package> <package>createrepo</package> <package>ed</package> <package>dejavu</package> <package>psmisc</package> <package>findutils-locate</package> <package>yast2-powertweak</package> </packages> <patterns config:type="list"> <pattern>dhcp_dns_server</pattern> <pattern>ccb</pattern> <pattern>apparmor</pattern> <pattern>lamp_server</pattern> <pattern>Basis-Devel</pattern> <pattern>x11</pattern> <pattern>gnome</pattern> <pattern>base</pattern> <pattern>WBEM</pattern> </patterns> Any ideas what I might be missing? -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

15 years

[opensuse-autoinstall] Autoinstall of all packages...

by Cameron Seader

Greetings, Red Hat has a way of selecting everything when installing their distribution. Is there a way to do the same thing with SUSE Linux. Anyone have any ideas?? -Cameron -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

15 years

[opensuse-autoinstall] Why getting different setups on identical HW although "CLONING" using autoyast ??

by Elmar Marschke

Hi, I'm trying to create an exact clone of a machine running openSuSE 10.1. Highest priority is to end up with a pair of machines that have EXACTLY the SAME SOFTWARE PACKAGES installed. These machines are build exactly of the same hardware, shipped from the same vendor on the same day, so there should'nt be a problem (HP Pavilion AMD 64 X2 Dual Core). 1. I did a fresh install on the first machine; and directly after that (without changing anything on that machine)... 2. i created a xml-profile using "yast2 autoyast", choosed "create reference profile" (and did NOT choose or change anything else manually...) and copied this file to a webserver running on a third machine. 3. I started a network installation on the second machine, telling it to use that profile (boot option "autoyast=http://my_ip/my_profile.xml") and to use the same installation source as was used for the first machine (that was a SuSE 10.1 DVD lying around on a samba share of a fourth machine). I expect this to end up with exactly the same software installed on both machines (is this right or do i misunderstand something??); and besides that anything else also be the same (partitioning and so on...). Unfortunately this is not the case. I checked the output of "rpm -qa" of both machines with a perl script i wrote and it reported the following differences: "This exists in machine2.txt only: libgcj-32bit-4.1.0-25 This exists in machine2.txt only: java-1_4_2-gcj-compat-32bit-1.4.2.0-33" I doublechecked this manually; it's true. On the first machine, these packages are not installed, however packages of the same name but without the "32bit" in it are installed (but these are ALSO installed on the second machine). Question 1: Can someone explain me why this is happening? Is there a mistake in my approach? Besides that i got the same problem trying to do the same on some production servers, which are running since a long time. However in those cases the difference is even bigger, there are around 80 packages reported to be installed on just the second machine, which i expected to be an exact clone (also identical hardware and so on). My assumption in this case is that some packages are being installed on the "clone", because an "addon" section like "KDE" is in the profile.xml; while some packages of the "kde" selection were separately removed from the "original" machine after installation (without removing the whole selection "kde"). Could this be the cause? Question 2: Does "yast2 autoyast / create reference profile" really represent the actual status of that machine concerning installed software and anything else? Is there a better way to reach my goal (two machines with exactly the same software installed; exact clone); how can i create a working xml-profile that ensures this; even if there were lots of software installations and deinstallations on the original machine after the first "initial setup"? Thanks in advance.. -- Dipl.Ing FH Elmar Marschke Schenker & CO AG IT-Innovation SO-Europa / IT-Innovation SE-Europe 1010 Wien / Vienna Austria -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

15 years

[opensuse-autoinstall] Install / Copy Question

by King, Richard (CE1 UNIX Admin)

Hello All, I am installing NLD9 via autoyast, which I've been using for a long time, and does work very well. However, I have a new RPM to add, but the only catch is that the rpm will not install unless the "--force" option is used, if I were to install the rpm by hand with the "--force" option, the rpm will install. I did edit the control file accordingly and added the new rpm. After the install is finshed, the new rpm is listed when I run "rpm -qa", however, the file is not present. I was curious if there was a way to use the "--force" option during the autoyast install process for the software section. If not, I could copy the files needed onto the target machine during the autoyast install. This leads me to my next question. If I need to copy a binary file to a specific directory on the target machine, what is the best way to to accomplish this task during the autoyast install? As a test, I wrote a script in the pre-script section of the control file to "cp -p binary_file /usr/sbin", which didn't work. Then I used the absolute path of the binary_file, "cp -p /local/SuSE/i386/nld9/binary_file /usr/sbin/binary_file", which didn't work either. **Background** The new rpm that I am referring to is the new tg3 NIC driver which I created an rpm from a source rpm. The old tg3 driver will not work with the new workstations. Help with this problem would be greatly appreciated. -- Rick King -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

15 years

[opensuse-autoinstall] IBM x3550 SLES 9 Autoyast with PXE Boot

by Jonathan Buys

Hello All, I've got a rack full of IBM x3550's which need SLES 9 installed on them. I've configured a PXE and Autoyast server, which seem to be working, however, the 3550's seem to have a problem with the sles9 sp3 driver module. The nic will not load properly, and the autoinstall process fails out almost immediately after the syslinux kernel is loaded. I have the kernel set to load the bnx2 module, which is what it uses once it is installed locally, but I'm still not having any luck. Any suggestions? Thanks, Jon -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

15 years

[opensuse-autoinstall] updating sles 10 during autoinstallation through a proxy

by Rich

it seems that we have hit a couple of problems/questions regarding sles10 update through a proxy during autoinstallation. sles10 with sles10_root_fix_v0.4 applied was used; 1. autoinstallation profile has both <customer_center> and valid proxy set. unfortunately, an attempt to register at ncc during autoinstallation fails - it does not use proxy as configured in yast/autoyast. it seems that this proxy is not exported to profile early enough, as adding "export http_proxy=<valid proxy>" allows registering to proceed. that seems a bit hackish approach, so maybe there is another, better way to solve this issue ? 2. update itself requires another way of a proxy setting, "rug set proxy-url". is there a way to force rug to use a proxy specified in environment variable or maybe there is a separate setting in the profile available (though using the proxy set through yast/variables would be preferred :) ) -- Rich -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

15 years

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall June 2007