January 2007 - openSUSE Autoinstall - openSUSE Mailing Lists

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] partitioning problem 10.2 and autoinstall
by fschuett 06 Feb '07

06 Feb '07

Hallo, what am I doing wrong here? I have a setup with three linux partitions, that should be reused (formatted but not created) on installation. I need to keep AutoYaST from creating his own partitions since I use reborn network cards that do the partitioning themselves, which is a common setup in a school like ours. I followed the documentation and created this partitioning section: -------------------------------------------------------- <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list"> <partition> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">ext3</filesystem> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> </partition> <partition> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">ext3</filesystem> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> </partition> <partition> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">swap</filesystem> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">3</partition_nr> </partition> </partitions> </drive> </partitioning> ------------------------------------------------------- With this setup, AutoYaST reuses hda1 as boot as expected but creates a new partition hda4 as root. The partition table ist: ------------------------------------------------------ /dev/hda1 * 1 13 184391 83 Linux /dev/hda2 2883 5432 83 Linux /dev/hda3 5433 5560 83 Linux /dev/hda4 14 2882 83 Linux (this one is created by AutoYaST). ------------------------------------------------------ "fdisk" tells me that the partitions are not in disk order. Has anyone an idea about this? I used this setup for a while already and experimented a lot with different "partitioning" sections but I can't keep AutoYaST from creating his own partition. Any help appreciated. Bye, Frank Frank Schuette, Gymnasium Himmelsthuer, Germany fschuett(a)gymnasium-himmelsthuer.de -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 9

[opensuse-autoinstall] VNC password setting for autoyast
by Ian Grant 01 Feb '07

01 Feb '07

Dear List, Having recently resurrected my info file using the kernel parameter info=file:///info I get prompted (by linuxrc?) to enter a VNC password. The info file on the initrd has this: install: ... autoyast: ... loghost: .... vnc: 1 vncpassword: thepassword And in addition the kernel command line includes: append initrd=initrd splash=silent showopts install=... autoyast= ... vnc=1 vncpassword=thepassword info=file:///info (without the line-breaks of course.) Can anyone see what I am doing wrong? -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 5

Re: [opensuse-autoinstall] not partitioning, only formatting and using existing partitions
by Sebastian Reitenbach 31 Jan '07

31 Jan '07

Uwe Gansert <ug(a)suse.de> wrote: > On Wednesday 31 January 2007 18:30, Sebastian Reitenbach wrote: > > > I try to install openSUSE 10.2 on a hp dl 385. unfortunately the parted > > tool in the 10.2 is unable to partition the disk on the cciss controller. > > why? Does it work in a manual installation? no, it is this bug: https://bugzilla.novell.com/show_bug.cgi?id=228707 (just found it, maybe I work around it, as there suggested replacing the /usr/lib64/liby2storage.so.2.0.0) > > > I can partition it before I start autoyast, but I am wondering how to > > tell the autoyast process to just only using the partitions as they are, > > format them and setup the mount points in fstab accordingly. > > set <create ...>false</create> > <format ...>true</format> > and set the correct <partition_nr ...> thanks a lot, this is what I needed, and sounds way easier, than replacing some files .... kind regards Sebastian -- 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] not partitioning, only formatting and using existing partitions
by Sebastian Reitenbach 31 Jan '07

31 Jan '07

Hi all, I try to install openSUSE 10.2 on a hp dl 385. unfortunately the parted tool in the 10.2 is unable to partition the disk on the cciss controller. I can partition it before I start autoyast, but I am wondering how to tell the autoyast process to just only using the partitions as they are, format them and setup the mount points in fstab accordingly. kind regards Sebastian -- 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] Adding checksums to an autoyast repository
by Ian Grant 31 Jan '07

31 Jan '07

This is a bit OT, apologies in advance. This message is about two things. One is a question about adding checksums for certain files which checksums rug/zypper complains are missing and the other is that the instructions for create_update_source may need updating. The following is what zypper sa complains about: $ sudo zypper sa \ > nfs://svr.cl.cam.ac.uk/vol/vol3/sys-li9/suse-10.2/updates > \ > SUSE-10.2-CL-updates root's password: 6733 zmd ZENworks Management Daemon is running. WARNING: this command will not synchronize changes. Use rug or yast2 for that. Determining nfs://svr.cl.cam.ac.uk/vol/vol3/sys-li9/suse-10.2/updates source type... .. not YUM nfs://svr.cl.cam.ac.uk/vol/vol3/sys-li9/suse-10.2/updates is type YaST No digest for ./suse/setup/descr/EXTRA_PROV, continue [y/n]y No digest for ./suse/setup/descr/packages, continue [y/n]y No digest for ./suse/setup/descr/packages.DU, continue [y/n]y No digest for ./suse/setup/descr/packages.en, continue [y/n]y Added Installation Sources: [x]* SUSE-10.2-CL-updates To set this update source up I am using the script create_update_source in the inst-source-utils RPM and a version of the instructions provided here: http://www.suse.com/~ug/ and here: http://en.opensuse.org/Inst-source-utils These instructions may need updating because I had problems specifying a name for the update source directory. In the crib below, BASE is set to the top-level of my network installation source. The difference between this and the instructions on the web page above is that I no longer can choose the sub-directory name to be e.g. myInstallSource as they suggest, rather create_update_source always creates $TARGET/updates where $TARGET is whatever directory name is the parameter. VERSION=10.2 BASE=/usr/groups/suse-$VERSION KEYID=rpm-packager RPMS=/global/src/RPMS/ # Build the repository cd $BASE create_update_source.sh ./ for arch in i386 i586 i686 x86_64 ; do mkdir -p updates/suse/$arch cp $RPMS/*.$arch.rpm updates/suse/$arch/ done cd updates/suse/ create_package_descr -x setup/descr/EXTRA_PROV cd setup/descr/ ls > directory.yast # Sign it cd $BASE/updates gpg --export --armor $KEYID > content.key gpg -b --sign --armor -u $KEYID content ls > directory.yast -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 1

Re: [opensuse-autoinstall] do I can force autoyast to use eth1 for the installation process?
by Sebastian Reitenbach 26 Jan '07

26 Jan '07

Hi Uwe, Uwe Gansert <ug(a)suse.de> wrote: > On Thursday 25 January 2007 08:34, Sebastian Reitenbach wrote: > > > Do I can tell autoyast to use eth1 for installation, if yes, how? > > SUSE Linux version? > try netdevice=eth1 > thanks a lot, that works. Sebastian -- 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] do I can force autoyast to use eth1 for the installation process?
by Sebastian Reitenbach 26 Jan '07

26 Jan '07

Hi list, I have a notebook, where the wireless card is detected as eth0. I generally do not want to configure this card generally, but also do not want to deactivate it in the bios, to be able to configure it when necessary. Without a configuration of that interface, autoyast stops and asks me for the essid and wep key. Do I can tell autoyast to use eth1 for installation, if yes, how? kind regards Sebastian -- 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] sles 9 sp3 rules problems.
by John Comitas 24 Jan '07

24 Jan '07

I have a rules file, which is read from floppy, but when it tries to open the had.xml file, it can't open /media/floppy. What could be the issue? Info file - Install: nfs//x.x.x.x/sles9-1 Netdevice: eth0 Server: x.x.x.x Ip: x.x.x.x Netmask: 255.0.0.0 Gateway: x.x.x.x Nameserver: x.x.x.x Autoyast: file:/// Rules.xml - <?xml version="1.0"?> <!DOCTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/rules.dtd"> <autoinstall xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <rules config:type="list"> <rule> <custom1> <script> <![CDATA[ if grep hda /proc/partitions > /dev/null; then echo -n "hda" fi; if grep sda /proc/partitions > /dev/null; echo -n "sda" else echo -n "ccis" fi; ]]> </script> <match>*</match> <match_type>exact</match_type> </custom1> <result> <profile>classes/@custom1@.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> </rules> </autoinstall> Can you please give me some assistance? John -- 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] Screen woes on install
by Alec Ross 24 Jan '07

24 Jan '07

Hi Using SuSE 10.0, I've experienced problems in startup where my monitor reported "Input Not Supported" at boot time, but the system loaded and then displayed fine. I'm attempting to update to 10.2, from a DVD, and after choosing "Install" I'm getting the same monitor problem for probably 15 mins so far. (Pressing Esc does not help.) There seems to be some slight intermittent HD activity, tho. How long should I wait for this to finish? What might I best do - apart from getting a new monitor? ;) TIA Alec Ross -- Alec Ross -- 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] /init details (cd boot)
by Jean Marc Le Fevre 24 Jan '07

24 Jan '07

Hi all, I'm looking for the source of /init filr on the boot cd. This init file can be find inside the initrd that has been loaded while booting a mini-iso. thanks in advance. eos -- 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] Do a reboot after paritioning
by Michael Welle 24 Jan '07

24 Jan '07

Hi, is there a way to do a reboot after partioning and/or after formating the disks (without too much hacking)? I would like to utilize such feature to press autoyast in our process and on the other side take advantage of the hardware recognition etc of autoyast. 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

3 6

[opensuse-autoinstall] Copying folders via Autoyast
by Jordan Zebor 24 Jan '07

24 Jan '07

All, I am trying to copy gconf settings via autoyast. These settings are in multiple folders that need to be copied into a users home directory after software installation and before the user logs in for the first time. I've tried using post-scripts to copy from an NFS mount but that fails claiming network unreachable. I just found that INIT scripts will execute after the network interface is active so I will be trying that next. I'm looking for feedback on the best methods for copying folders via autoyast or another method to deploy gconf settings via autoyast. Thanks -- -Jordan -- 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] 10.1 -> 10.2 Documentation Update
by Lee Mayes 22 Jan '07

22 Jan '07

Hi Uwe. After a couple of requests for 10.2 I added it the distros my code supports. I read: http://www.suse.com/~ug/autoyast_changes_10_1-10_2.html closely, scanned the mailing list, and thought it would be a slam dunk, but all my ISOs would simply die at the beginning with 'Cannot find Installation Source'. Long story short, root cause was I use an info file embedded in initrd, and starting with 10.2 it must be spec'd in isolinux.cfg vs. being automatically discovered like it's been since SLES8: http://www.suse.com/~ug/autoyast_doc/appendix.linuxrc.html#id2570172 Could you promote that difference to the 10.1 -> 10.2 changes doc? If anyone else uses an info file this way it could save them some pain and frustration. Thanks and Best Regards, Lee -- 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] auto-install problem using yast clone this system
by David Bolt 22 Jan '07

22 Jan '07

I've a small(ish) problem with the auto-install system of openSUSE 10.2. After using the "clone this system" option at the end of an install I have an autoinst.xml file created that matches the installed system. The problem is that if I use this file to try and perform an auto-installation, every package that has a post-install script fails, returning an error number 255. I don't know why this is happening and, at first I thought the problem was that bash wasn't installed before the packages executing these scripts. Copying the bash executable doesn't make a difference so I'm at a loss as to what's causing the problem. I'm not sure if this is a problem with the autoinst.xml file created by YaST when using the "clone this system" option after installation, or if the problem is in the auto-installation system, so I thought I'd ask here to find out where the problem lies. That way, when I create a bug report about it, I know what would be the correct category to list it under. As the file is about 50KB, and I don't think this list would allow an attachment, a compressed copy of the autoinst.xml file is located here: <URL:http://www.davjam.org/~davjam/autoinst.xml.bz2> Regards, David Bolt -- Member of Team Acorn checking nodes at 50 Mnodes/s: http://www.distributed.net/ AMD1800 1GB WinXP/SUSE 9.3 | AMD2400 256MB SuSE 9.3 | A3010 4MB RISCOS 3.11 AMD2600(64) 512MB SUSE 10.0 | AMD2400 768MB SUSE 10.0 | A4000 4MB RISCOS 3.11 AMD2800(64) 512MB SUSE 10.1 | RPC600 129MB RISCOS 3.6 | Falcon 14MB TOS 4.02 -- 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] defining addon pattern
by Lars Stavholm 20 Jan '07

20 Jan '07

Hi List! I've successfully set up a SuSE Linux 10.2 autoinstallation environment using PXE and autoyast and it works great (kudos to all that made this happen). But, when setting up an addons repository I hit a small snag that I wonder if anyone could help me with. I've read the excellent description of pattern definition for addons at <http://developer.novell.com/wiki/index.php/Creating_Add-Ons>, and I've used the description successfully, but: I would like to have some of the addon packages selected, but not all, when my addons are selected. Does anyone know how to accomplish this? At the moment, I have all my packages defined between the +Prq: and -Prq: tags, and the package subset that I want to have selected by default are listed between the +Prc: and -Prc: tags, but to no avail, all packages are selected by default. Please advice. /Lars Stavholm -- 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] Package selection using Yast Autoinstallation
by Graham Smith 19 Jan '07

19 Jan '07

Hi, I'm having real problems using the Yast autoinstallation program to select a list of packages. On my server I have a number of external repositories installed. e.g. packman, etc When I go into AutoInstall and goto package selection --> configure it displays my current list of selected repositories. This causes a major problem as it is near impossible to determine what packages are contained in the base package set that is installed on the Installation Server ( packages from the opensuse DVD) and the packages derived from external sources. Is there some way of disabling all the external repositories from being included into the Autoinstallation package selection? -- Regards, Graham Smith -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

RE: [opensuse-autoinstall] Odd SLES10 X86_64 autoyast install failure.
by Colin Topliss 17 Jan '07

17 Jan '07

Hi all, It actually turned out to be a corruption in my installation source - though why on Earth it only appeared to cause an issue if I included a <script></script> section is a bit of a mystery to me. Still, thanks to all who replied with suggestions - you helped save my sanity (for another day at least). Col. -----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: 16 January 2007 17:13 To: opensuse-autoinstall(a)opensuse.org Subject: Re: [opensuse-autoinstall] Odd SLES10 X86_64 autoyast install failure. On Tuesday 16 January 2007 17:40, Colin Topliss wrote: > I'm having a bit of trouble with remotely installing SLES10 (X86_64) > over the network with post scripts defined. > > The profile I have works fine.... until I add this section for scripts: hm. Strange. Try to set: > <network_needed config:type="boolean">true</network_needed> this to "false" -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany Business: http://www.suse.de/~ug now playing VNV Nation - Hellraiser (VNV Nation Remix) -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org Ericsson Services Limited Registered Office: Unit 4, Midleton Gate, Guildford Business Park, Guildford, Surrey, GU2 8SG Registered Number in England and Wales: 3709800 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 Services 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

1 0

[opensuse-autoinstall] Odd SLES10 X86_64 autoyast install failure.
by Colin Topliss 16 Jan '07

16 Jan '07

Hi, I'm having a bit of trouble with remotely installing SLES10 (X86_64) over the network with post scripts defined. The profile I have works fine.... until I add this section for scripts: <scripts> <post-scripts config:type="list"> <script> <network_needed config:type="boolean">true</network_needed> <filename>test.sh</filename> <interpreter>shell</interpreter> <source><![CDATA[ #!/bin/sh ################################ # Setup script for new servers # ################################## # Add host entry for sudo server # ################################## echo "10.245.13.12 dserv-mgt sudo-host" >> /etc/hosts #################################################### ############################################## # Start up NFS and untar LINUX_NEWSERVER.tar # ############################################## mkdir -p /media/nfs /etc/init.d/portmap start mount 10.244.35.51:/depot/SUSE/i386 /media/nfs cd / tar -xvf /media/nfs/conf/S10LINUX_NEWSERVER.tar ]]> </source> </script> </post-scripts> </scripts> I even tried splitting it out, using location instead: <scripts> <post-scripts config:type="list"> <script> <network_needed config:type="boolean">true</network_needed> <location>http://10.244.35.51:/conf/scripts/SLES10.sh</location> </script> </post-scripts> </scripts> Doesn't matter what I try, I get the same results (thought it might be a network problem to start with). I even tried the above with the location line deleted and had the same error. I've even stripped the script down to a basic echo out to a file - same error. This, however, works fine under SLES9. The problem? After the first reboot, it detects the network card, goes on to perform 'installation', I briefly see a message about running scripts, then the hald stops with the error: /usr/lib/YaST2/startup/YaST2.call: line 306: 4074 Aborted The system has not been set up correctly (in-fact I can't even log in - I ended up using a screen capture to get the error message above). As soon as I remove everything from <scripts> to </scripts> all works fine again (the system installs correctly). Not sure what I am missing here..... Colin Ericsson Services Limited Registered Office: Unit 4, Midleton Gate, Guildford Business Park, Guildford, Surrey, GU2 8SG Registered Number in England and Wales: 3709800 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 Services 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

2 1

[opensuse-autoinstall] Execution order of scripts
by Michael Welle 16 Jan '07

16 Jan '07

Hi, is there any assured execution order of scripts of the same type? Imagine two chroot-scripts foo.sh and bar.sh. Are they executed in the order they appear in the autoyast file? Or is the order more or less random? 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 2

[opensuse-autoinstall] Unable to start openSUSE 10.2 graphical installer on Dell Optiplex GX110
by Vegard 15 Jan '07

15 Jan '07

I am new to Linux and originally installed Ubuntu 6.10 on my Dell Optiplex GX110 system without any fatal problems. After reading a very positive review on Linux.com, "openSUSE 10.2: the best Linux desktop yet?" <http://www.linux.com/article.pl?sid=06/12/11/1526210>, I installed openSUSE 10.2 on my notebook computer without problems and liked it so much that I want to switch to openSUSE on my desktop computer as well. I'm getting this installation error: "Your computer does not fulfill all requirements for a graphical installation. There is less than 96 MB memory or the X server could not be started. As a fall back, the text front-end of YaST will guide you through the installation..." The problem is likely that "the X server could not be started", because my system has 256 MB SDRAM installed. The CPU is an Intel Pentium IIIE, 933 MHz. The properties of the integrated video adapter are: Device Description Intel Corporation 810 Graphics Controller Hub Adapter String Intel810 Video Accelerator BIOS String Intel Video BIOS Chip Type Intel810 DAC Type Internal Memory Size 4 MB My monitor is a Samsung SyncMaster 753DF: Manufacture Date 2003 Max. Visible Display Size 32 cm x 24 cm ( 15.7") Picture Aspect Ratio 4:3 Horizontal Frequency 30 - 71 kHz Vertical Frequency 50 - 160 Hz Maximum Resolution 1280 x 1024 Gamma 1.82 DPMS Mode Support Active-Off Has anyone run into this problem and found a solution, know a likely solution, or have some pointers on how to solve an installation problem like this? -- 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] Firewall on Ethernet port?
by Alec Ross 15 Jan '07

15 Jan '07

With the default setup for openSUSE 10.2, will the firewall filter traffic on an ethernet connection? (I'm considering using an ethernet bridge to connect to the Internet via WiFi.) TIA -- Alec Ross -- 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] Two problems, patterns and grub
by Henrik Schmidt 12 Jan '07

12 Jan '07

1. I switched from addons with 10.0 to patterns with 10.2 but it does not work as expected. If I use patterns and additional packages then autoinstall tries to install packages first which will fail of course as vital files are missing (sh, libz ...). Patterns are only installed correctly if I remove all additional <package> definitions. Expl : <software> <patterns config:type="list"> <pattern>base</pattern> <pattern>kde</pattern> </patterns> </software> will install base + kde but <software> <patterns config:type="list"> <pattern>base</pattern> <pattern>kde</pattern> </patterns> <packages config:type="list"> <package>lynx</package> </packages> </software> will try to install lynx first and fails miserably. What do I miss ? 2. With 9.3 I could set for grub : <global_entry> <key>timeout</key> <value config:type="integer">8</value> </global_entry> which did not work for 10.0 any longer. What do I miss here ? Hope someone can help me. Henrik Schmidt -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 4

[opensuse-autoinstall] Image install.
by Simon Crute 12 Jan '07

12 Jan '07

Hi list. I'm experimenting with the image install options introduced with opensuse10.2. In the docs it sais [func] an experimental imaging feature was added. Instead of installing via RPM, you can provide an image script that is doing the installation: <software> <image> <script_location>http://10.10.0.162/image.sh</script_location> </image> the image.sh script looks like this: #!/bin/sh wget -O - http://10.10.0.162/image.tgz 2>/dev/null| tar xfvz - -C /mnt I'm trying the following. <software> <image> <script_location>http://autoyast/image.sh</script_location> </image> </software> the image.sh script is. #!/bin/sh wget -O - http://autoyast/autoconf-sl102/suse10.2.tgz 2>/dev/null| tar xfvz - -C /mnt The relevant extract from the log file seems to be 2007-01-12 10:11:24 <1> 192.168.21.107(3801) [agent-curl] CurlAgent.cc(Execute):218 Output: /var/adm/au toinstall/scripts/image.sh 2007-01-12 10:11:24 <3> 192.168.21.107(3801) [agent-curl] CurlAgent.cc(Get):55 Cant open file /var/adm/ autoinstall/scripts/image.sh 2007-01-12 10:11:24 <3> 192.168.21.107(3801) [YCP] autoinstall/io.ycp:84 Can't find URL: http://autoyas t/image.sh 2007-01-12 10:11:24 <3> 192.168.21.107(3801) [bash] ShellCommand.cc(shellcommand):78 /bin/sh: /tmp/imag e.sh: No such file or directory 2007-01-12 10:11:24 <1> 192.168.21.107(3801) [Interpreter] clients/inst_autoimage.ycp:46 Called YaST cl ient returned: `next If I grab the file from wget, on the test machine, using the same URL, then it works. So, I'm stumped. -- Simon Crute IS&T Bracknell Novell UK Ltd -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 6

Re: [opensuse-autoinstall] Two problems, patterns and grub
by Lars Stavholm 12 Jan '07

12 Jan '07

Henrik Schmidt wrote: > Am Dienstag, 9. Januar 2007 14:42 schrieben Sie: >> Henrik Schmidt wrote: >>> 1. >>> >>> I switched from addons with 10.0 to patterns with 10.2 but it does not >>> work as expected. If I use patterns and additional packages then >>> autoinstall tries to install packages first which will fail of course as >>> vital files are missing (sh, libz ...). >> Well, I had the same problem for a while, until I realized >> that the actions of autoyast and the error messages were >> all misleading. It turned out that I had some problems in >> one of my own add on packages that made autoyast go bananas. >> However, once the packaging problem was solved, it works >> flawlessly. >> >> I suggest you start without add ons (or updates) at all. >> >> Then move on to one add on package and make pretty damn >> sure that it is correctly built. >> > > Hi Lars, > > please note that I do not use any self made addon packages. > Check my example. It is very simple and does not work. Using base + kde > patterns is fine but as soon as I add a single simple predefinded package > like <package>lynx</package> (to add the lynx rpm) it fails as described. > > I will try and check for clues in the logfiles. Ah, I see, your first sentence mentioned addons, that threw me off. In any case, my statement stands, patterns works just fine. A goos starting point is to clone an already installed machine. That's were I take most of my stuff from. Below's a working set that I use a lot now, it's taken from a cloned autoinst.xml after installing Minimal with Graphic. And it is working. Maybe that set could give you a clue. Cheers /Lars --- Begin Included Message --- <software> <packages config:type="list"> <package>3ddiag</package> <package>915resolution</package> <package>CheckHardware</package> <package>Mesa</package> <package>MozillaFirefox-translations</package> <package>OpenEXR</package> <package>PolicyKit</package> <package>a2ps</package> <package>aalib</package> <package>acpid</package> <package>agfa-fonts</package> <package>alsa</package> <package>aspell</package> <package>aspell-en</package> <package>at</package> <package>atk</package> <package>audiofile</package> <package>audit</package> <package>autofs</package> <package>autoyast2</package> <package>autoyast2-installation</package> <package>bc</package> <package>bind-libs</package> <package>bind-utils</package> <package>binutils</package> <package>blocxx</package> <package>boost</package> <package>bootcycle</package> <package>bootsplash</package> <package>bootsplash-theme-SuSE</package> <package>cabextract</package> <package>cairo</package> <package>checkmedia</package> <package>compat</package> <package>compat-libstdc++</package> <package>compat-openssl097g</package> <package>cpp</package> <package>cpp41</package> <package>cpufrequtils</package> <package>cron</package> <package>cups</package> <package>cups-libs</package> <package>dbus-1-glib</package> <package>dbus-1-mono</package> <package>dbus-1-x11</package> <package>deltarpm</package> <package>desktop-data-SuSE</package> <package>desktop-file-utils</package> <package>desktop-translations</package> <package>dhcpcd</package> <package>dialog</package> <package>dmraid</package> <package>dos2unix</package> <package>dosfstools</package> <package>dovecot</package> <package>enscript</package> <package>esound</package> <package>evms-gui</package> <package>expat</package> <package>fam</package> <package>fbset</package> <package>foomatic-filters</package> <package>freeglut</package> <package>freetype2</package> <package>fribidi</package> <package>ft2demos</package> <package>ftgl</package> <package>fvwm2</package> <package>gail</package> <package>gawk</package> <package>gconf2</package> <package>gdb</package> <package>gdbm</package> <package>gettext</package> <package>ghostscript-fonts-other</package> <package>ghostscript-library</package> <package>ghostscript-x11</package> <package>giflib</package> <package>gimp</package> <package>glib</package> <package>glib-sharp2</package> <package>glib2</package> <package>glibc-i18ndata</package> <package>glibc-locale</package> <package>glitz</package> <package>gnome-filesystem</package> <package>gnome-icon-theme</package> <package>gnome-keyring</package> <package>gnome-mime-data</package> <package>gnome-vfs2</package> <package>gnutls</package> <package>gpart</package> <package>gpg</package> <package>gpm</package> <package>gtk</package> <package>gtk-sharp2</package> <package>gtk2</package> <package>hal</package> <package>hal-resmgr</package> <package>hdparm</package> <package>hfsutils</package> <package>hplip</package> <package>hplip-hpijs</package> <package>ifplugd</package> <package>imlib</package> <package>info</package> <package>initviocons</package> <package>inst-source-utils</package> <package>irqbalance</package> <package>ispell</package> <package>ispell-american</package> <package>jfsutils</package> <package>joe</package> <package>kdelibs3</package> <package>ksh</package> <package>libacl</package> <package>libart_lgpl</package> <package>libattr</package> <package>libbonobo</package> <package>libbonoboui</package> <package>libcap</package> <package>libcom_err</package> <package>libcroco</package> <package>libdrm</package> <package>libevent</package> <package>libexif</package> <package>libgcc41</package> <package>libgcrypt</package> <package>libgimpprint</package> <package>libglade2</package> <package>libgnome</package> <package>libgnomecanvas</package> <package>libgnomecups</package> <package>libgnomeprint</package> <package>libgnomeprintui</package> <package>libgnomesu</package> <package>libgnomeui</package> <package>libgpg-error</package> <package>libgphoto2</package> <package>libgsf</package> <package>libgssapi</package> <package>libgtkhtml</package> <package>libicu</package> <package>libidl</package> <package>libidn</package> <package>libieee1284</package> <package>libjasper</package> <package>libjpeg</package> <package>liblazy</package> <package>liblcms</package> <package>libltdl</package> <package>libmng</package> <package>libnetpbm</package> <package>libnscd</package> <package>libopencdk</package> <package>libpcap</package> <package>libpng</package> <package>libqt4</package> <package>libqt4-dbus-1</package> <package>libqt4-qt3support</package> <package>libqt4-sql</package> <package>libqt4-x11</package> <package>librpcsecgss</package> <package>librsvg</package> <package>libsmbclient</package> <package>libstdc++41</package> <package>libstroke</package> <package>libtiff</package> <package>libusb</package> <package>libvolume_id</package> <package>libwmf</package> <package>libxcrypt</package> <package>libxml2</package> <package>libxslt</package> <package>liby2util</package> <package>libzio</package> <package>libzypp</package> <package>lsb</package> <package>lsof</package> <package>lukemftp</package> <package>lzo</package> <package>m4</package> <package>mDNSResponder-lib</package> <package>make</package> <package>man</package> <package>man-pages</package> <package>master-boot-code</package> <package>mono-core</package> <package>mono-data</package> <package>mono-web</package> <package>mozilla-nspr</package> <package>mozilla-nss</package> <package>mozilla-xulrunner181</package> <package>mpt-status</package> <package>net-snmp</package> <package>netcat</package> <package>netpbm</package> <package>nfs-utils</package> <package>nfsidmap</package> <package>nscd</package> <package>ntfsprogs</package> <package>numlockx</package> <package>openct</package> <package>openldap2-client</package> <package>opensc</package> <package>openslp</package> <package>openssh-askpass</package> <package>opensuse-manual_en</package> <package>opensuse-updater</package> <package>orbit2</package> <package>pango</package> <package>patch</package> <package>pax</package> <package>pciutils</package> <package>pciutils-ids</package> <package>pcre</package> <package>pcsc-lite</package> <package>perl-Bootloader</package> <package>perl-Compress-Zlib</package> <package>perl-Config-Crontab</package> <package>perl-Crypt-SmbHash</package> <package>perl-DBD-SQLite</package> <package>perl-DBI</package> <package>perl-Digest-MD4</package> <package>perl-Digest-SHA1</package> <package>perl-File-Tail</package> <package>perl-Net-Daemon</package> <package>perl-PlRPC</package> <package>perl-TermReadKey</package> <package>perl-TimeDate</package> <package>perl-URI</package> <package>perl-XML-Parser</package> <package>perl-XML-Writer</package> <package>perl-gettext</package> <package>pkgconfig</package> <package>pm-utils</package> <package>pmtools</package> <package>popt</package> <package>portmap</package> <package>postfix</package> <package>powersave</package> <package>powersave-libs</package> <package>ppp</package> <package>pptp</package> <package>prctl</package> <package>preload</package> <package>procinfo</package> <package>procmail</package> <package>providers</package> <package>python</package> <package>python-qt</package> <package>python-xml</package> <package>qlogic-firmware</package> <package>qscintilla</package> <package>qt3</package> <package>readline</package> <package>recode</package> <package>release-notes</package> <package>resmgr</package> <package>rrdtool</package> <package>rsync</package> <package>sane</package> <package>sane-frontends</package> <package>sash</package> <package>sax2</package> <package>sax2-gui</package> <package>sax2-ident</package> <package>sax2-libsax</package> <package>sax2-libsax-perl</package> <package>sax2-tools</package> <package>scpm</package> <package>screen</package> <package>scsi</package> <package>sensors</package> <package>shared-mime-info</package> <package>sharutils</package> <package>siga</package> <package>smartlink-softmodem</package> <package>smartmontools</package> <package>smpppd</package> <package>sqlite</package> <package>sqlite-zmd</package> <package>startup-notification</package> <package>strace</package> <package>sudo</package> <package>suseRegister</package> <package>suspend</package> <package>tcl</package> <package>tcpd</package> <package>tcpdump</package> <package>tcsh</package> <package>telnet</package> <package>terminfo</package> <package>tightvnc</package> <package>timezone</package> <package>tk</package> <package>udev</package> <package>ulimit</package> <package>unclutter</package> <package>unzip</package> <package>update-alternatives</package> <package>usbutils</package> <package>utempter</package> <package>vlan</package> <package>wdiff</package> <package>wireless-tools</package> <package>wol</package> <package>words</package> <package>wvdial</package> <package>wvstreams</package> <package>x11-input-synaptics</package> <package>x11-input-wacom</package> <package>x11-tools</package> <package>xaw3d</package> <package>xdg-menu</package> <package>xdg-utils</package> <package>xdmbgrd</package> <package>xfsprogs</package> <package>xinetd</package> <package>xkeyboard-config</package> <package>xli</package> <package>xlockmore</package> <package>xntp</package> <package>xorg-x11</package> <package>xorg-x11-Xvnc</package> <package>xorg-x11-driver-input</package> <package>xorg-x11-driver-video</package> <package>xorg-x11-libICE</package> <package>xorg-x11-libSM</package> <package>xorg-x11-libX11</package> <package>xorg-x11-libX11-ccache</package> <package>xorg-x11-libXau</package> <package>xorg-x11-libXdmcp</package> <package>xorg-x11-libXext</package> <package>xorg-x11-libXfixes</package> <package>xorg-x11-libXmu</package> <package>xorg-x11-libXp</package> <package>xorg-x11-libXpm</package> <package>xorg-x11-libXprintUtil</package> <package>xorg-x11-libXrender</package> <package>xorg-x11-libXt</package> <package>xorg-x11-libXv</package> <package>xorg-x11-libfontenc</package> <package>xorg-x11-libs</package> <package>xorg-x11-libxkbfile</package> <package>xorg-x11-server</package> <package>xtermset</package> <package>yast2-control-center</package> <package>yast2-registration</package> <package>yast2-samba-server</package> <package>yast2-sound</package> <package>yast2-trans-en_US</package> <package>yast2-trans-stats</package> <package>yp-tools</package> <package>ypbind</package> <package>zen-updater</package> <package>zip</package> <package>zisofs-tools</package> <package>zsh</package> </packages> <patterns config:type="list"> <pattern>addons</pattern> <pattern>apparmor</pattern> <pattern>base</pattern> <pattern>fonts</pattern> <pattern>sw_management</pattern> <pattern>sw_management_x11</pattern> <pattern>x11</pattern> <pattern>yast2_basis</pattern> <pattern>zmd</pattern> <pattern>zmd_x11</pattern> </patterns> <remove-packages config:type="list"> <package>smtp_daemon</package> </remove-packages> </software> --- End Included Message --- -- 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] WiFi Setup problems
by Alec Ross 12 Jan '07

12 Jan '07

Hi, I'm looking for advice with setup of WiFi on 10.2. I've tried on 10.0, an upgrade to 10.2, and a fresh install of 10.2 - all without success. I'm using a a Belkin wireless G, version 3000uk card. Apparently _this version works w/ SuSE 10.0, and OTB w/ 10.2. (But though this is detected, it has not worked for me. :( ) The gateway is set up to do NAT, and will support multiple concurrent wireless clients. (And I have this working with MS Win.) From the 'net I can find various indirect approaches (ndis wrapper ...); but I suspect that the problem may be due to inappropriate settings that I've entered. Can anyone help? I'd be happy to post relevant extracts of the system log if this would be useful. TIA Alec -- Alec Ross -- 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] I am not sure how to configure info, autoinst.xml, and rules.xml files to work together
by John Comitas 11 Jan '07

11 Jan '07

I am running sles9-sp3 I am not sure how to setup rules file along with autoinst.xml. How would I configure info, rules, and autoinst files? -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

RE: [SPAM] - [opensuse-autoinstall] autoinstall fails with exit code 11 - Email found in subject
by Jorge Alvarado 11 Jan '07

11 Jan '07

anybody? I'm still dead-in-the-water. anybody seen this? any debug tips? thanks. -----Original Message----- From: Jorge Alvarado [mailto:jalvarado@pervasive.com] Sent: Tuesday, January 09, 2007 6:08 PM To: opensuse-autoinstall(a)opensuse.org Subject: [SPAM] - [opensuse-autoinstall] autoinstall fails with exit code 11 - Email found in subject Hi list, anybody seen this before? install gets kicked off, then get a error pop up. the console shows the following; http: //192.../install/se9/content 640 bytes http: //192.../install/se9/media.1/info.txt 13422 bytes http: //192.../install/se9/control.xml 17722 bytes Loading "/install/se9/driverupdate" ramdisk /dev/ram3 freed starting setctsid "showconsole" inst_setup yast install program exit code is 11 I added y2debug to the boot parameters, but see no other debug info. No command line, probably too early in the install, so can't look at y2logs, etc. any help appreciated. thanks, Jorge -- 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

2 1

[opensuse-autoinstall] autoinstall fails with exit code 11
by Jorge Alvarado 10 Jan '07

10 Jan '07

Hi list, anybody seen this before? install gets kicked off, then get a error pop up. the console shows the following; http: //192.../install/se9/content 640 bytes http: //192.../install/se9/media.1/info.txt 13422 bytes http: //192.../install/se9/control.xml 17722 bytes Loading "/install/se9/driverupdate" ramdisk /dev/ram3 freed starting setctsid "showconsole" inst_setup yast install program exit code is 11 I added y2debug to the boot parameters, but see no other debug info. No command line, probably too early in the install, so can't look at y2logs, etc. any help appreciated. thanks, Jorge -- 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] addon packages
by Lars Stavholm 07 Jan '07

07 Jan '07

Hi List, anyone know how to use the pattern format file(s) for addon packages? Or are we to use the old(er) selection format files for addons? The documentation describes sel files for addons. Thanks /Lars -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 5

[opensuse-autoinstall] package selection
by Lars Stavholm 05 Jan '07

05 Jan '07

Hi All, just started trying out SuSE Linux 10.2 and I'm looking for an easy way to say "Minimal+X11" using the new patterns format. Is there a way? Or do I have to list all the actual packages? I checked the documentation, and couldn't find anything. Any input appreciated. /Lars Stavholm -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 2

[opensuse-autoinstall] bootloader
by Lars Stavholm 04 Jan '07

04 Jan '07

Hi List, does anyone have a suggestion for a good bootloader config? I've looked through the manual, but cannot find an answer. I'm looking for the following requirements: 1. Write as little/brief as possible in the autoyast.xml, instead let the autoyast fill in the blanks. 2. Boot any of three RAID1 disks. I've got the following at the moment, and I'm not sure it's enough: <bootloader> <activate config:type="boolean">true</activate> <global> <activate>true</activate> <generic_mbr>true</generic_mbr> </global> <loader_device>/dev/md</loader_device> <loader_type>grub</loader_type> <location>mbr</location> <repl_mbr config:type="boolean">true</repl_mbr> </bootloader> Any input appreciated. /Lars Stavholm -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

RE: [SPAM] - Re: [opensuse-autoinstall] invoking auto-install - Email found in subject
by Jorge Alvarado 04 Jan '07

04 Jan '07

Rich, I will change the default to harddisk in the isolinux.cfg. thanks. When using the 1st suse install DVD/CD, the install works ok. The install server can be reached and the autoyat profile is read/parsed and processed ok. I want to kick off the install from the boot cd. I created this boot cd, using this iso: SUSE-Linux-10.1-GM-x86_64-mini.iso. But, I don't seem to have this boot cd correct, since it doesn't recognize the install and autoyast directives in the isolinux.cfg file. I would expect the install to proceed without any manual intervention. Seems like I'm missing something here? thanks, Jorge -----Original Message----- From: Rich [mailto:rich@hq.vsaa.lv] Sent: Thursday, January 04, 2007 3:21 AM To: opensuse-autoinstall(a)opensuse.org Subject: [SPAM] - Re: [opensuse-autoinstall] invoking auto-install - Email found in subject Jorge Alvarado wrote: > I've got a bootable cd, whereby I've updated isolinux.cfg. But the suse installer seems > to be going for a manual install. > > The iso image was created via; > mkisofs -r -T -J -pad -c boot/x86_64/loader/boot.cat -b boot/x86_64/loader/isolinux.bin -no-emul-boot -boot-load-size 4 -boot-info-table -o ../suse10.iso . > > The isolinux.cfg is as follows; > isolinux.cfg: > default autoyast i'd suggest against this. there will be a reboot during installation (upto opensuse 10.2 after the first cd, from that at the end, if i am not mistaken) - and you'll land in an endless loop unless you manually choose hdd entry at the reboot. also, could be nasty to leave this cd in the tray accidentally... > display boot.msg > prompt 1 > timeout 15 > > # auto install > label autoyast > kernel linux > append install=http://192.168.0.76/install/SE10-1 autoyast=http://192.168.0.76/autoy/SuSE10autoy.xml initrd=initrd > > # hard disk > label harddisk > kernel linux > append SLX=0x202 showopts > > > The box will boot up, seems to establish dhcp ok. But then the linuxrc Main Menu pops up, with > "Start Installation or System". Looks like install and autoyast directives were ignored. > > When proceed thru a manual network install, after the "Enter the directory on the server", > the field is pre-populated with "/install/SE10-1", so looks like it got it from the isolinux.cfg. > But after this, get a 404 not found error. well, check server logs to verify what is requested and not found; how did you create the installation source ? is it correct ? check that you can access autoinstall profile from the machine manually > what am I missing? Any help appreciated? > thanks. -- Rich -- 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

3 2

Re: [opensuse-autoinstall] SLED10 - Patterns error
by Mark Rodee 04 Jan '07

04 Jan '07

That did it! Thank you for your time Lee! On Tue, 2007-01-02 at 09:53 -0500, Lee Mayes wrote: > Mark Rodee wrote: > > 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? > > > > > Hi Mark, > > Here's relevant what I use (using HTTP against exploded CD images): > > > <general> > <signature-handling> > <accept_unsigned_file config:type="boolean">true</accept_unsigned_file> > <accept_file_without_checksum > config:type="boolean">true</accept_file_without_checksum> > <accept_verification_failed > config:type="boolean">true</accept_verification_failed> > <accept_unknown_gpg_key config:type="boolean">true</accept_unknown_gpg_key> > <import_gpg_key config:type="boolean">true</import_gpg_key> > </signature-handling> > </general> > <software> > <patterns config:type="list"> > <pattern>default</pattern> > </patterns> > </software> > > We also vend the SDK, so I have this stanza as well: > > <add-on> > <add_on_products config:type="list"> > <listentry> > <media_url> > http://192.168.1.5/LinuxCOE/SuSE/i386/SLE-10-SDK/CD1 > </media_url> > <product>SUSE-Linux-Enterprise-SDK-i386</product> > <product_dir>/</product_dir> > </listentry> > </add_on_products> > </add-on> > > Sorry for the formatting, hope that helps! > > Lee > -- -- 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] invoking auto-install
by Jorge Alvarado 04 Jan '07

04 Jan '07

I've got a bootable cd, whereby I've updated isolinux.cfg. But the suse installer seems to be going for a manual install. The iso image was created via; mkisofs -r -T -J -pad -c boot/x86_64/loader/boot.cat -b boot/x86_64/loader/isolinux.bin -no-emul-boot -boot-load-size 4 -boot-info-table -o ../suse10.iso . The isolinux.cfg is as follows; isolinux.cfg: default autoyast display boot.msg prompt 1 timeout 15 # auto install label autoyast kernel linux append install=http://192.168.0.76/install/SE10-1 autoyast=http://192.168.0.76/autoy/SuSE10autoy.xml initrd=initrd # hard disk label harddisk kernel linux append SLX=0x202 showopts The box will boot up, seems to establish dhcp ok. But then the linuxrc Main Menu pops up, with "Start Installation or System". Looks like install and autoyast directives were ignored. When proceed thru a manual network install, after the "Enter the directory on the server", the field is pre-populated with "/install/SE10-1", so looks like it got it from the isolinux.cfg. But after this, get a 404 not found error. what am I missing? Any help appreciated? thanks. -- 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] 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