openSUSE Autoinstall December 2006

autoinstall@lists.opensuse.org

25 participants
44 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

RE: [suse-autoinstall] SLES 10 RC2 remove-packages section?
by Matt Gillard 05 Mar '08

05 Mar '08

I dont have kinternet installed. This is what doesnt seem to work: <software> <patterns config:type="list"> <pattern>default</pattern> <pattern>Basis-Devel</pattern> <pattern>x11</pattern> </patterns> <packages config:type="list"> <packages>perl-libwww-perl</packages> <packages>net-snmp</packages> <packages>kernel-source</packages> </packages> <remove-packages config:type="list"> <packages>pptp</packages> <packages>smpppd</packages> <packages>ppp</packages> <packages>wvdial</packages> <packages>mutt</packages> </remove-packages> </software> In y2log it mentions that those packages should be removed, but it goes ahead and installs them anyway. I can do it manually on the command line: # rpm -e pptp smpppd ppp wvdial mutt and that works fine so I know I have no dependency problems. matt > -----Original Message----- > From: Uwe Gansert [mailto:ug@suse.de] > Sent: Friday, 30 June 2006 12:50 AM > To: suse-autoinstall(a)suse.com > Subject: Re: [suse-autoinstall] SLES 10 RC2 remove-packages section? > > > On Thursday 29 June 2006 16:45, Manfred Hollstein wrote: > > > If that fails, you have kinternet installed; add that to > the list and it > > should work. > > good point. > <remove-packages> can not break dependencies and so it's very > likely that > there is still a package that needs those packages. > I did a very small installation with no X - so it worked for me. > > -- > ciao, Uwe Gansert > > Uwe Gansert, Server Technologies Team > SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany > Fax: +49-(0)911-74053-476, Web: http://www.suse.de/~ug > now playing Covenant - Wasteland > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses. No warranty is made that this material is free from computer virus or any other defect or error. Any loss/damage incurred by using this material is not the sender's responsibility. The sender's entire liability will be limited to resupplying the material.

4 6

Scripting dirinstall?
by Teun 25 Feb '07

25 Feb '07

Does anyone know if it is possible to use the 'dirinstall' from the command line? For instance i would like to be able to do something like: # yast dirinstall -d /someroot -s mypackages.sel If i do yast -h it says: "Usage: /sbin/yast [OPTIONS] [MODULE] [module specific parameters]" But is there a way to find out what 'module specific parameters' are available for a specific module? Thanks, Teun

3 2

[opensuse-autoinstall] X11 configuration
by Michael Welle 03 Jan '07

03 Jan '07

Hi, I try to configure x11 with autoyast. Doesn't seem to work as expected. In the best case the machine comes up with a resolution higher than the selected one. Example: <x11> <color_depth config:type="integer">16</color_depth> <configure_x11 config:type="boolean">true</configure_x11> <display_manager>kdm</display_manager> <enable_3d config:type="boolean">true</enable_3d> <monitor> <display> <height config:type="integer">600</height> <width config:type="integer">800</width> </display> <monitor_device>800X600@75HZ</monitor_device> <monitor_vendor> LCD</monitor_vendor> </monitor> <resolution>800x600</resolution> <window_manager>desktop-kde</window_manager> </x11> With this settings the machine comes up with a resolution of 1280x1024. The hardware can drive both resolutions, the desired and the current resolution. I've tried changing the frequency, appending hsync/vsync values, choosing Vesa as monitor vendor, etc. Nothing seems to give a reliable result. After installing the machine I can start yast in interactive mode and choose the desired resolution. No problem. Is there a secret trick I've missed? A bug? Michael -- biff4emacsen - A biff-like tool for (X)Emacs http://www.c0t0d0s0.de/biff4emacsen/biff4emacsen.html -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 3

[opensuse-autoinstall] prompt user for root password and optionally add a new user to system
by Zhang Weiwu 02 Jan '07

02 Jan '07

Hello. This is my first question on this list so let me know if I started a stupid question: is it possible to set up autoyast so that during installation the installer ASK user for root password and ASK USER optionally add a new user to system (and decide if he should auto-login)? I read the document and I know how to define default root password and add a user in yast configuration. Here the expected result is user enter their root password themselves. Is it possible? Samuel Partida wrote: > Am Montag, 11. Dezember 2006 15:03 schrieb 张韡武: > > Hello. In the campus we have setup a SuSE Mirror (the first we had in > > campus) that include online installation service. We are going to > > distribute community SuSE installation CDROM on the next LUG event. > > > > Here is the question: can we modify OPENSUSE mini-install CDROM so that > > when it boot: > > I. it automatically select Simplified Chinese as main language and > > US as keyboard layout (it's too hard to find non-US keyboard > > here); > > II. it automatically select network installation, type is FTP and > > server host name, path are automatically filled; > > III. it automatically launch yast to start the installation > > > > I have heard of autoyast but as far as I know the kind of automatic we > > want (described as step 1-3 above) are BEFORE yast starts, does autoyast > > also cover my situation? > > > > (I think the one with graphic user interface is yast, the steps 1-3 done > > on a console is not yet yast, correct me if I am wrong) > > > > Thank you! > > Hi, I think that autoyast covers perfectly your needs. This could be > very helpful http://forgeftp.novell.com/yast/doc/SL10.0/autoinstall/ > > Good luck! ;) -- 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] Autoinstall Package Selection in 10.2
by Alan Becker 29 Dec '06

29 Dec '06

I'm having trouble with the Package Selection portion of the AutoInstallation applet. I installed 10.2 on my notebook (dual-boot w/ WinXP) from the Retail DVD, and now am attempting to create an autoinstall control file to set up a series of other machines, which will have little in common with my notebook. The Autoinstall applet is acting more like the "Software Management" applet, in that it preconfigures the package selection with the packages that are installed on the notebook, and when I right-click on a pattern entry (or an individual package), the local menu shows options such as Keep, Delete, or Update, rather than the Install/Don't Install/Taboo options one would expect. Also, if I use the Software Management applet and install or remove individual packages, the changes I make show up in the packages that are preselected when I go back to the Autoinstall applet. Note that when I highlight "Package Selection" in the tree on the left, in the right panel the "Selected Patterns" shows "Not configured yet", and the "Individually selected packages" count is zero. However, when I click the Configure button, and change to Pattern or Package Group view, then I see the preselected items. I have tried the "Reset Configuration" button, and I tried loading a manually edited control file with the Patterns and Packages removed. These things made no difference. Is there anything I can do to make this applet disregard the locally installed patterns/packages? Otherwise, is there some workaround? I am also concerned that the dependency resolution may be influenced improperly by what is going on with the packages. TIA, A. Becker -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

Re: [opensuse-autoinstall] SLED10 - Patterns error
by Mark Rodee 29 Dec '06

29 Dec '06

Lee, Thanks for the reply, It does not look like that is the case. But, looking at the y2log I see the following - ":321 User does not want to trust key error" with my key for the source. Then just a little lower on the list I see: "SourceCreate for 'nfs://<source>' product '' has failed For testing, I've added the following to my XML profile - <accept_unsigned_file config:type="boolean">true</accept_unsigned_file> <accept_verification_failed config:type="boolean">true</accept_verification_failed> <accept_unknown_gpg_key config:type="boolean">true</accept_unknown_gpg_key> and still hit the error. Suggestions? On Tue, 2006-12-19 at 17:01 -0500, Lee Mayes wrote: > Mark, > > I remember seeing this a while back. Did you by any chance unpack, > tweak, and repack initrd? If you did, this *must* be done as root (or > chown -R root:root /dir/with/initrd before re-cpio'ing it). If you > check /var/log/YaST/y2log at the failure time, you'll see errors about > /var/adm/XXXX not writeable if that's what's happening. > > It caused me quite a bit of grief. > > Hope that helps! > > Lee > > > Mark Rodee wrote: > > Good Morning! > > > > I'm catching a warning in my SELD10 profile for autoyast. It states > > "Could not set patterns or selections: Default" I've tried the patterns > > listed in suse/setup/descr/ with no luck. I've also read the past three > > months of postings for clues. Here is the important part of my autoyast > > profile. This is booted from the SLED10 cd, pointed at a NFS share for > > the source, and the same share for the profile. Any suggestions? > > > > <?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"> > > <software> > > <accept_unsigned_file config:type="boolean">true</accept_unsigned_file> > > <accept_verification_failed > > config:type="boolean">true</accept_verification_failed> > > <accept_unknown_gpg_key > > config:type="boolean">true</accept_unknown_gpg_key> > > <patterns config:type="list"> > > <pattern>default</pattern> > > </patterns> > > </software> > > ... More if needed. > > > > Thanks > > -- > > > > > > -- -- 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] Re: [suse-autoinstall] Please include the right DTDs in SuSE 10.2
by David Werner 20 Dec '06

20 Dec '06

On Wed, Dec 06, 2006 at 09:13:54AM +0100, Uwe Gansert wrote: > autoyast no longer uses DTDs but RNG files (they are created from RNC files > which are human readable). > http://www.suse.de/~ug/autoyast_doc/Profile.DTD.html > The RNG files are in /usr/share/YaST2/schema/autoyast/rng > They are a lot better than the DTDs were but I'm afraid, they are still not > complete. > I hope we will have them complete on SLES10 SP1 I just tried that, but I get errors, even on the minimal autoyast configuration I used as test.xml: -- begin test.xml -- ?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> <use>all</use> </drive> </partitioning> <software> <base>default</base> </software> <users config:type="list"> <user> <encrypted config:type="boolean">false</encrypted> <user_password>myrootpassword</user_password> <username>root</username> </user> </users> </profile> -- end test.xml -- and got by running on 10.2 RC1 host (similiar also on a 9.1): /usr/bin/xmllint --noout --relaxng /usr/share/YaST2/schema/autoyast/rng/profile.rng test.xml test.xml:4: element partitioning: Relax-NG validity error : Element profile has extra content: partitioning test.xml fails to validate Similiar errors I have on my current configuration but my first tag <nis> then. I would expect that the <base>-tag in <software> is now wrong (with 10.2), but not that partitioning is wrong. Any help appreciated. Maybe the DOCTYPE is not very consistent with the above scheme. Greetings, David -- 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] SLED10 - Patterns error
by Mark Rodee 19 Dec '06

19 Dec '06

Good Morning! I'm catching a warning in my SELD10 profile for autoyast. It states "Could not set patterns or selections: Default" I've tried the patterns listed in suse/setup/descr/ with no luck. I've also read the past three months of postings for clues. Here is the important part of my autoyast profile. This is booted from the SLED10 cd, pointed at a NFS share for the source, and the same share for the profile. Any suggestions? <?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"> <software> <accept_unsigned_file config:type="boolean">true</accept_unsigned_file> <accept_verification_failed config:type="boolean">true</accept_verification_failed> <accept_unknown_gpg_key config:type="boolean">true</accept_unknown_gpg_key> <patterns config:type="list"> <pattern>default</pattern> </patterns> </software> ... More if needed. Thanks -- -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

RE: [opensuse-autoinstall] SUMMARY: Init-scripts and nfs location
by Andrew Laden 18 Dec '06

18 Dec '06

Ah, cool. Makes a lot more sense now. Thanks -Andrew > -----Original Message----- > From: Uwe Gansert [mailto:ug@suse.de] > Sent: Monday, December 18, 2006 9:35 AM > To: opensuse-autoinstall(a)opensuse.org > Subject: Re: [opensuse-autoinstall] SUMMARY: Init-scripts and > nfs location > > On Monday 18 December 2006 15:31, Andrew Laden wrote: > > > So what was the change that was made in response to > > > > [bug] init-script does not require network now > > there was a bug, that without a network configuration, > init-scripts were not possible at all. > > in "/etc/rc.d/autoyast" the "network" was movend from > "Required-Start:" > to "Should-Start:" > > > -- > ciao, Uwe Gansert > > Uwe Gansert, Server Technologies Team > SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany > 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 > > -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall December 2006