April 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

Interactive option checked BEFORE scripts?
by Jesse Keating 25 May '05

25 May '05

I'm using the modified.xml method of dynamic autoinstall control files. One of the things I wanted dynamic was the interactive or not choice, controlled by: <mode> <confirm config:type="boolean">false</confirm> If this was set to true, it should be interactive. I have this being set in modified.xml, however it does not take effect. Is this option checked BEFORE the pre-scripts run? -- Jesse Keating RHCE Pogo Linux -- Linux Systems Engineer tel: (888) 828-7646 ex: 436

3 2

partitioning SuSE Professional 9.3 keep partition
by Hoepfner, Enrico 12 May '05

12 May '05

Hi, I've a problem to keep a partition by a new installaiton with autoyast (SuSE Professional 9.3). There is a logical partition /dev/hda7 mounted on /data1 wich i want to keep with all data on it. The oether logical partitions /dev/hda5 + /dev/hda6 should use for "/" and "swap". The strange is that my XML-config did exactly what i want in SuSE 9.2 but not in SuSE 9.3. What i have, before installation: /dev/hda Partition Size Mount FS Type /dev/hda1 extended partition /dev/hda5 376mb swap swap logical partition /dev/hda6 5gb / ext3 logical partition /dev/hda7 xx /data1 ext3 logical partition What i want is the following: /dev/hda Partition Size Mount Format FS Type /dev/hda1 extended partition /dev/hda5 auto swap F swap logical partition /dev/hda6 5gb / F ext3 logical partition /dev/hda7 xx /data1 -- logical partition (KEEP) My XML-configuration looks so: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <mount>/data1</mount> <create config:type="boolean">false</create> <format config:type="boolean">false</format> <partition_nr config:type="integer">7</partition_nr> <filesystem config:type="symbol">ext3</filesystem> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">6</partition_nr> <size>5gb</size> </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">5</partition_nr> <size>auto</size> </partition> </partitions> <use>5,6</use> </drive> </partitioning> What i get ist: Device F Typ MountP /dev/hda1 extended /dev/hda2 Linux /data1 /dev/hda5 swap swap /dev/hda6 Linux /dev/hda7 Linux My Question: What have i get wrong? How can I configure what I want (also with SuSE 9.3)? thanks enrico

3 7

Fwd: [suse-autoinstall] auto updating install tree
by Ashe Canvar 06 May '05

06 May '05

I am still not clear about the process of getting the updates from SuSe. 1. The command line (online_update) does not have any parameters for passing my portal username and password. 2. I don't want to use the GUI because I want to script this. 3. man online_update does not exist. -h is very little help either. 4. If I use the gui via YaST2 then the patches get downloaded in /var/lib/Yast2/you/blah.. This happens for the i386 architecture by default. How do I also do this for the x86_64 architecture ? (SLES9). 5. There do not seem to be too many rpms doenloaded after step 4. But a lot of patch-xxx files. What do I do with these ? 6. What do I do with .patch.rpm packages ? I am so confused that I would rather go back to freebsd and its awesome cvsup system. Any help would be appreciated esp with the command lines to get the updates and info on what parts of the downloaded tree to move into the updates folder created by Anas's script. Thanks! On 4/27/05, Ashe Canvar <acanvar(a)gmail.com> wrote: > Perfect. I got the script after some digging. Will let you know if this works. > > http://www.suse.de/~nashif/autoyast2/scripts/create_update_source.sh > > On 4/24/05, Anas Nashif <nashif(a)suse.de> wrote: > > Hi, > > > > If you dont know it by now, there is a command line utility for YOU > > > > /usr/bin/online_update > > > > What you can do is download all updates (download only) to the server, > > create an update source with the script I have posted some weeks ago and > > copy the rpms to this new source and recreate the package database > > everytime something changes. All those steps can be automated using a > > smart script run by cron. > > > > Then you can install new machines with the new packages and without the > > need to run YOU afterwards... > > > > > > Anas > > > > Ashe Canvar wrote: > > > Hi all, > > > > > > I am tryng to make a fully automated installation system for SLES9 for > > > x86_64 and i386. First of all I must congratulate Suse for such an > > > excellent, well thought out installation automation system. Yast does > > > have its issues, but once I learnt the ropes it has made me pretty > > > productive. > > > > > > The issue I am not clear about is as follows: > > > > > > - I created my base install image following the docs in > > > http://www.suse.de/~nashif/autoinstall/9.1/html/ch05s02.html#id2523126 > > > > > > - if I install 20 machines and then YOU them then it takes a long > > > time, even if I run a local YOU server. > > > > > > - What I ideally want is to update the installation tree I have > > > created above such that doing a YOU update post-install is not even > > > required. > > > > > > Is there any way to accomplish this ? > > > > > > How do I download the rpm's that have been released as updates to the > > > base SLES9 release ? Doing that through the portal site is pretty > > > painful/manual. > > > > > > I would ideally like to automate this if possible as a weekl > > > build/test/publish cycle for my organization. > > > > > > Thanks! > > > > > >

2 2

Re: [suse-autoinstall] ANSWER: autoyast=file: with CDROM based control file
by Michael Marion 29 Apr '05

29 Apr '05

On 29 Apr, Schumacher, Gordon wrote: > And per SuSE's standard, it would be cd://xxxxx > I don't know if it will recognize that already or not... it > might be worth a shot though! Depending on which device the cdrom is, it might work as hdc://xxxx too. or hdb, hdd, etc. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Half of the people I talk to need a good going over with the old clue-by-four. - Tracy Reed...Regarding RoadRunner Tech Support

1 0

RE: [suse-autoinstall] ANSWER: autoyast=file: with CDROM based control file
by Schumacher, Gordon 29 Apr '05

29 Apr '05

# From: Dax Kelson [mailto:dax@gurulabs.com] # Sent: Friday, April 29, 2005 3:56 PM # To: autoinstall # Subject: [suse-autoinstall] ANSWER: autoyast=file: with CDROM based # control file # # How about adding the syntax, # # autoyast=cdrom:/filename # # To reference a control on the top level of the booted cdrom? Well, it would still have two slashes (you always have two for the schema). And per SuSE's standard, it would be cd://xxxxx I don't know if it will recognize that already or not... it might be worth a shot though!

1 0

ANSWER: autoyast=file: with CDROM based control file
by Dax Kelson 29 Apr '05

29 Apr '05

After quite a bit of testing, I have determined that the autoyast=file:///filename syntax doesn't work with placing the bare control file on a CDROM (if I'm wrong please show me). It works with if the control file is INSIDE of a initial ram disk (or initramfs on SL9.3) or on a floppy. The documentation here: http://yast.suse.com/autoinstall/9.1/html/invoking_autoinst.html Implies very strongly that it should work outside of the initial ram disk/fs. I couldn't get this to work. Also, the documentation is very ambiguous on // versus ///. How about adding the syntax, autoyast=cdrom:/filename To reference a control on the top level of the booted cdrom? Thanks, Dax Kelson Guru Labs

1 0

Creating DVD from CDs
by Robertson, Hill 29 Apr '05

29 Apr '05

OK. I've been browsing through the archives and can't seem to find exactly what I need (although I can't believe no one else has asked this). Please forgive me if this has been answered and I have overlooked it. I've seen a lot of posts that get close to what I want but not quite enough to help my situation. I think I'm really close and just need to tweak a couple of media.X, order files, or infofile/kernel paramaters but I'm having trouble getting everything right. I have all of the SLES9 CDs as well as the SP1 CDs. I need to create a single DVD from these. I have a script that I wrote that generates the autoinst.xml file and writes it to floppy. I just want to have my floppy inserted with the installation DVD and boot. I just can't seem to get the DVD properly created to work. It always end up going into manual installation mode. I was able to get it to "sort of" install except YaST said it couldn't find the installation media and then when I manually told it to boot from the hard drive (but selected had - which is my DVD-ROM drive) the rest of the install worked. However, I need to remove this manual part. I want to be able to install from one DVD just like I can install from a NFS server. I do network installs all the time but the DVD install is not going so well. What is the exact step-by-step procedure to create an autoinstalling DVD? Do I need any special info file or kernel parameters (instmode=cd or instmode=hd)? Any help will be GREATLY appreciated. Thanks, Hill

1 0

RE: [suse-autoinstall] Using autoyast=file:// with CDROM based file, broken?
by Ness, Todd 29 Apr '05

29 Apr '05

the file:///pathtofile seems to work really well if you imbed the control file in the initrd. Unzip initrd, mount it as a loop device, copy the control file to the right path, umount the initrd, zip it back up and make a new CD. Todd -----Original Message----- From: Dax Kelson [mailto:dax@gurulabs.com] Sent: Friday, April 29, 2005 11:37 AM To: boopathy krishnamoorthy Cc: autoinstall Subject: Re: [suse-autoinstall] Using autoyast=file:// with CDROM based file, broken? On Fri, 2005-04-29 at 05:52 +0100, boopathy krishnamoorthy wrote: > You have to use the autoyast in isolinux.cfg as > follows. > autoyast=file:///d8. > If d8 is present in the "installroot" directory > itself. > here "installroot" denotes the base directory of CD or > DVD. I tried with three slashes, eg, file:///d8 and I'm still getting the error. Is this supposed to work? I'm trying to do a NFS based autoyast install, but I'm booting off a CDROM I created that only contains the 5 files: isolinux.bin isolinux.cfg linux initrd d8 <--- my autoyast control file In my isolinux.cfg I have: label sl93ay kernel linux append initrd=initrd install=nfs://10.100.0.254/export/netinstall/SL9.3 ip=10.100.0.8 netmask=255.255.255.0 gateway=10.100.0.254 nameserver=10.100.0.254 textmode=1 autoyast=file:///d8 I still get an error saying it can't read the file. If I place the autoyast file on a NFS server and change the autoyast= like to point to it, it installs OK. So I know the syntax is valid inside the "d8" file. Dax Kelson Guru Labs -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

RE: [suse-autoinstall] Using autoyast=file:// with CDROM basedfile, broken?
by Schumacher, Gordon 29 Apr '05

29 Apr '05

# From: Dax Kelson [mailto:dax@gurulabs.com] # Sent: Friday, April 29, 2005 11:37 AM # To: boopathy krishnamoorthy # Cc: autoinstall # Subject: Re: [suse-autoinstall] Using autoyast=file:// with CDROM # basedfile, broken? # # I tried with three slashes, eg, file:///d8 and I'm still getting the # error. Is this supposed to work? Yep, three slashes is right. The first two are for the file:// scheme itself, and the third one is part of the path (/d8). (I learned this the hard way by finding out that file links to Windoze UNC network paths have to be specified as file://///comp/share - yep, five slashes.)

1 0

Re: [suse-autoinstall] Using autoyast=file:// with CDROM based file, broken?
by boopathy krishnamoorthy 29 Apr '05

29 Apr '05

You have to use the autoyast in isolinux.cfg as follows. autoyast=file:///d8. If d8 is present in the "installroot" directory itself. here "installroot" denotes the base directory of CD or DVD. consider if d8 is present in some directory "Installroot/custom" u have to use the autoyast as follows autoyast=file:///custom/d8. --- Dax Kelson <dax(a)gurulabs.com> wrote: > I have a custom CDROM I burnt with the following > contents: > > isolinux.bin > isolinux.cfg > linux > initrd > d8 <--- my autoyast control file > > In my isolinux.cfg I have: > > label sl93ay > kernel linux > append initrd=initrd ramdisk_size=65536 > splash=silent showopts > install=nfs://10.100.0.254/export/netinstall/SL9.3 > ip=10.100.0.8 netmask=255.255.255.0 > gateway=10.100.0.254 nameserver=10.100.0.254 > textmode=1 autoyast=file://d8 > > > The last part, "autoyast=file://d8" I came up with > based on the > documentation here: > > http://yast.suse.com/autoinstall/9.1/html/invoking_autoinst.html > > When I try to use this, I an error message during > the: > > => Retrieve Read Control File > > stage > > A dialog pops up and says, "A profile for this > machine could not be > found or retrieved..." and a box where I delete and > replace the > file:=//d8 > > Isn't this supposed to work? > > Any help great appreciated. > > Dax Kelson > Guru Labs > > > -- > To unsubscribe, e-mail: > suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: > suse-autoinstall-help(a)suse.com > > ________________________________________________________________________ Yahoo! India Matrimony: Find your life partner online Go to: http://yahoo.shaadi.com/india-matrimony

2 2

RE: [suse-autoinstall] Update boot cd with new driver
by Stephens, Bill {PBSG} 29 Apr '05

29 Apr '05

Ok, I'm making some progress. I forgot to turn on Joliet support when I created the ISO. Once I did that, I could manually load the necessary device driver from the CD. What command-line option do I pass to linuxrc to have it check the cd for the updated drivers? If I pass dd, it checks the diskette, but doesn't seem to check the cd. -----Original Message----- From: Steffen Winterfeldt [mailto:snwint@suse.de] Sent: Friday, April 29, 2005 8:37 AM To: Stephens, Bill {PBSG} Cc: suse-autoinstall(a)suse.com Subject: RE: [suse-autoinstall] Update boot cd with new driver On Fri, 29 Apr 2005, Stephens, Bill {PBSG} wrote: > That's what I thought, I'm guessing I'm not putting the modules in the > right place. I've tried copying the 01 and 02 directories to the root > directory on the cd and the boot directory on the CD. Do I just need the > modules, or do I need to put the directories somewhere else? Placing them into the root of the CD is basically correct. linuxrc will look at the CD for driver updates only if it has to access the CD for other purposes anyway (say, if it installs from CD). If you need to update a network driver to do a network installation, this does unfortunately not work. In this case the only way is to put the new modules into the initrd and, in case the new driver doesn't get loaded automatically (you'd probably have to update /lib/modules/*/modules.pcimap for that), add it to the autoload section in modules.config (or use insmod=foo on the command line). Steffen

2 1

RE: [suse-autoinstall] Update boot cd with new driver
by Stephens, Bill {PBSG} 29 Apr '05

29 Apr '05

That's what I thought, I'm guessing I'm not putting the modules in the right place. I've tried copying the 01 and 02 directories to the root directory on the cd and the boot directory on the CD. Do I just need the modules, or do I need to put the directories somewhere else? Thanks, Bill -----Original Message----- From: Steffen Winterfeldt [mailto:snwint@suse.de] Sent: Friday, April 29, 2005 6:57 AM To: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Update boot cd with new driver On Thu, 28 Apr 2005, Stephens, Bill {PBSG} wrote: > Is it possible to update the boot cd with a vendors device driver? The > driver diskette from the vendor works fine, but I'd like the process to be > seamless for my system installers. If I use the diskette, it requires some > manual intervention which could get a little irritating. Driver updates are looked for on any medium. You can just add the data to your cd or install source. Steffen -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

Update boot cd with new driver
by Stephens, Bill {PBSG} 29 Apr '05

29 Apr '05

Is it possible to update the boot cd with a vendors device driver? The driver diskette from the vendor works fine, but I'd like the process to be seamless for my system installers. If I use the diskette, it requires some manual intervention which could get a little irritating. Thanks, Bill Stephens

2 1

Re: [suse-autoinstall] Using autoyast=file:// with CDROM based file, broken?
by Michael Marion 29 Apr '05

29 Apr '05

On 28 Apr, Dax Kelson wrote: > A dialog pops up and says, "A profile for this machine could not be > found or retrieved..." and a box where I delete and replace the > file:=//d8 You'll get that error even if it reads the file, if there's an error in it. The best way I've found to troubleshoot this stuff it to use the loghost option to send syslog info to a syslog server.. it's extremely verbose and really helps. Note that your append line is getting really long too, at 255 characters or so, the rest will be chopped off, you might want to put some of the options (like loghost, ip, dns servers, etc) into an info file. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Groundskeeper Willie: "oooh.. Me mule wouldn't walk in the mud. So I had to put 17 bullets in 'em." ==> Simpsons

1 0

Using autoyast=file:// with CDROM based file, broken?
by Dax Kelson 28 Apr '05

28 Apr '05

I have a custom CDROM I burnt with the following contents: isolinux.bin isolinux.cfg linux initrd d8 <--- my autoyast control file In my isolinux.cfg I have: label sl93ay kernel linux append initrd=initrd ramdisk_size=65536 splash=silent showopts install=nfs://10.100.0.254/export/netinstall/SL9.3 ip=10.100.0.8 netmask=255.255.255.0 gateway=10.100.0.254 nameserver=10.100.0.254 textmode=1 autoyast=file://d8 The last part, "autoyast=file://d8" I came up with based on the documentation here: http://yast.suse.com/autoinstall/9.1/html/invoking_autoinst.html When I try to use this, I an error message during the: => Retrieve Read Control File stage A dialog pops up and says, "A profile for this machine could not be found or retrieved..." and a box where I delete and replace the file:=//d8 Isn't this supposed to work? Any help great appreciated. Dax Kelson Guru Labs

1 0

RE: [suse-autoinstall] Suse9.2 autoinstall crashes without error
by Schumacher, Gordon 28 Apr '05

28 Apr '05

# From: Boris "BXS" Schulz [mailto:boris.schulz@gmail.com] # Sent: Thursday, April 28, 2005 9:23 AM # To: suse-autoinstall(a)suse.com # Subject: [suse-autoinstall] Suse9.2 autoinstall crashes without error # # # Hi, # # I tried to install Suse9.2 via the autoinstaller on a PC. It seemed to # work just fine however, suddenly - probably (it is really fast, so I # cannot be sure) at the end of the list of options that are executed, # and that can be seen on the left side of the screeen - the screen goes # blac, some lines flash by and I get put back to the old manual # installation screen. # Is there a way to see at wich point the autoinstall-process stops? You might try the remote logging, as described here: http://www.tcm.phy.cam.ac.uk/~mr349/suse/autoyast.html

1 0

RE: [suse-autoinstall] How can I regularly update the install rep ository?
by Stephens, Bill {PBSG} 28 Apr '05

28 Apr '05

Thanks, it was the preceding / that did the trick. -----Original Message----- From: Michael Marion [mailto:mmarion@qualcomm.com] Sent: Wednesday, April 27, 2005 3:44 PM To: Bill.Stephens(a)pbsg.com Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] How can I regularly update the install rep ository? On 26 Apr, Stephens, Bill {PBSG} wrote: > LABEL SUSE LINUX Version 9.1 Try changing the label.. I changed mine from SUSE CORE Version 9 to SUSE Updates > DESCRDIR /SUSE-updates/updates/setup/descr > DATADIR /SUSE-updates/updates And remove the preceeding / from the above paths.. I think they should be relative from the base of the path the content file is in. I.e. my content file is located at: <long path>/sles9/SUSE-Updates/content and the two lines are: DESCRDIR updates/setup/descr DATADIR updates Where the directory "updates" is directly under the SUSE-Updates path. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com "The Tuxomatic 2200(TM) with patented Gates-Be-Gone(TM) gets rid of blue screens in a flash! It forks! It blits! Look at those fantastic pixels! It surfs the web! You could even host an ISP with it!" -- Matthew Sachs on Slashdot

1 0

Short dentist app this morning
by Mitko Haralanov 28 Apr '05

28 Apr '05

The appointment is at 10am but I should be back by 10:30-10:45 -- Mitko Haralanov mitko(a)pathscale.com http://www.pathscale.com ========================================== There's got to be more to life than compile-and-go.

1 0

Suse9.2 autoinstall crashes without error
by Boris "BXS" Schulz 28 Apr '05

28 Apr '05

Hi, I tried to install Suse9.2 via the autoinstaller on a PC. It seemed to work just fine however, suddenly - probably (it is really fast, so I cannot be sure) at the end of the list of options that are executed, and that can be seen on the left side of the screeen - the screen goes blac, some lines flash by and I get put back to the old manual installation screen. Is there a way to see at wich point the autoinstall-process stops? greetings, B.S.

1 0

Re: [suse-autoinstall] Custom package installation using AutoYaST
by boopathy krishnamoorthy 28 Apr '05

28 Apr '05

I am using SUSE SLES version 9. My requirement is to put all my packages in a separate directory and to install it. My control file is given below. <software> <addons config:type="list"> <addon>Base-System</addon> <addon>X11</addon> <addon>YaST2</addon> </addons> <base>Minimal+X11</base> <extra_packages> <package_location> custom </package_location> <packages config:type="list"> <package>glibc</package> // this is my <package>libnscd</package> // package list </packages> </extra_packages> <packages config:type="list"> <package>acct</package> <package>glibc-devel</package> <package>glibc-i18ndata</package> . . // here I give the . // packages list given </packages> // in the selection file </software> I didn't use and selection file. I had given it directly in the control file itself. After placing all my packages in "Install_root/suse/custom", I run create_package_descr -d . -x setup/descr/EXTRA_PROV and obtained "suse/setup/descr/packages". But during installation an error Error: File glibc 2.3.3 118.x86_64 not found. Details: File not found on the medium. This is the package i had placed under my "custom" directory. And also several packages had been not installed properly. During investigation it founds that yast didn't get the package name given under <extra_packages> tag. If we simply add details for new packages into "suse/setup/descr/packages", whether it is enough for installing the new packages. --- Uwe Gansert <ug(a)suse.de> wrote: > On Tuesday 26 April 2005 16:28, boopathy > krishnamoorthy wrote: > > > I had customised the installation using > AutoYaST. > > For adding my own package to install using > AutoYaST, i > > had created a directory "custom" under > > "install_root/suse/". > > # ls suse > > i586 custom noarch nosrc setup src > > x86_64 > > > > In the control.xml i added the following portion > > <extra_packages> > > <package_location> > > custom > > </package_location> > > <packages config:type="list"> > > <package>glibc</package> > > <package>libnscd</package> > > </packages> > > </extra_packages> > > </software> > > AFAIK since version 9.1 it's not necessary to > enhance the autoast profile. > Just do: > cd INSTALLATION_ROOT/suse > cp my.rpm ./i586/ > create_package_descr -d . -x setup/descr/EXTRA_PROV > > at the next installation, the new RPM should be > found > > -- > ciao, Uwe Gansert > > Uwe Gansert, Server Technologies Team > SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 > Nürnberg, Germany > e-mail: uwe.gansert(a)suse.de, Tel: > +49-(0)911-74053-0, > Fax: +49-(0)911-74053-476, Web: http://www.suse.de > > > -- > To unsubscribe, e-mail: > suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: > suse-autoinstall-help(a)suse.com > > ________________________________________________________________________ Yahoo! India Matrimony: Find your life partner online Go to: http://yahoo.shaadi.com/india-matrimony

2 1

Autoyast questions
by suse_list＠infineon.net 28 Apr '05

28 Apr '05

Hi, I managed to get most of the autoyast stuff to work with PXE boot, though there are a couple of questions and suggestions. With the release of Suse Pro 9.3 it seems that the yast autoinstall tool breaks the partitioning sizing in the autoyast config files. The question i have is i would like to enable that after the basic install on first boot one can get suse to check for online_updates, like one can do with installing from CD or installing via failsafe. Anyone have any ideas as to what to add to the autoyast config files? The other question, is there some way to determine in a post script the DHCP network information given and setting it to static on the machine? Please let me know thanks S.

2 1

Custom package installation using AutoYaST
by boopathy krishnamoorthy 28 Apr '05

28 Apr '05

Hi I had customised the installation using AutoYaST. For adding my own package to install using AutoYaST, i had created a directory "custom" under "install_root/suse/". # ls suse i586 custom noarch nosrc setup src x86_64 In the control.xml i added the following portion <software> <addons config:type="list"> . </addons> <packages config:type="list"> . . </packages> <extra_packages> <package_location> custom </package_location> <packages config:type="list"> <package>glibc</package> <package>libnscd</package> </packages> </extra_packages> </software> But after installation my packages doesn't get installed. And i don't know whether AutoYaST read's <extra_packages> portion. Give ur valuable points over this. And i want to know which file contains the list of packages that AutoYaST read from control.xml. ________________________________________________________________________ Yahoo! India Matrimony: Find your life partner online Go to: http://yahoo.shaadi.com/india-matrimony

2 1

Custom CD for SLES9 x86_64
by Bernhard Duebi 28 Apr '05

28 Apr '05

Hello everybody, I try to create a custom CD for SLES9 x86_64. With Yast CD Creator I setup the hierarchy needed to install Linux. Then I put Enterprise Agents into a separate directory. These get installed by the postinstall script. Then I compiled everything with mkisofs. I can boot from the CD, there's a popup complaining that I try to install 32bit software on a 64bit hardware. In the Yast log file I can see that yast is doing some magic to avoid this messages. Is somebody willing to share this magic with me ? Sincerely Bernhard

2 1

Re: [suse-autoinstall] How can I regularly update the install rep ository?
by Michael Marion 27 Apr '05

27 Apr '05

On 26 Apr, Stephens, Bill {PBSG} wrote: > LABEL SUSE LINUX Version 9.1 Try changing the label.. I changed mine from SUSE CORE Version 9 to SUSE Updates > DESCRDIR /SUSE-updates/updates/setup/descr > DATADIR /SUSE-updates/updates And remove the preceeding / from the above paths.. I think they should be relative from the base of the path the content file is in. I.e. my content file is located at: <long path>/sles9/SUSE-Updates/content and the two lines are: DESCRDIR updates/setup/descr DATADIR updates Where the directory "updates" is directly under the SUSE-Updates path. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com "The Tuxomatic 2200(TM) with patented Gates-Be-Gone(TM) gets rid of blue screens in a flash! It forks! It blits! Look at those fantastic pixels! It surfs the web! You could even host an ISP with it!" -- Matthew Sachs on Slashdot

1 0

RE: [suse-autoinstall] How can I regularly update the install rep ository?
by Stephens, Bill {PBSG} 27 Apr '05

27 Apr '05

Also, when I try adding the install source, I get the following error: Local Source Adding dir:///usr/suse9.1//SUSE-updates/ ERROR(InstSrc:E_no_instsrc_on_media) -----Original Message----- From: Stephens, Bill {PBSG} [mailto:Bill.Stephens@pbsg.com] Sent: Tue 4/26/2005 5:17 PM To: Michael Marion Cc: suse-autoinstall(a)suse.com Subject: RE: [suse-autoinstall] How can I regularly update the install rep ository? Ok, I think I'm making some progress, but I can't seem to find the glue that brings it all together. I created a content file and media.1 directory, but it's still not installing. Here's what I have: Root content file: PRODUCT SUSE LINUX VERSION 9.1 DISTPRODUCT SUSE-LINUX-DVD-i386 DISTVERSION 9.1-0 BASEPRODUCT SUSE LINUX BASEVERSION YOUTYPE YOUPATH i386/update/9.1 VENDOR SUSE LINUX AG RELNOTESURL http://www.suse.com/relnotes/i386/SUSE-LINUX/9.1/release-notes.rpm ARCH.i686 i686 i586 i486 i386 noarch ARCH.i586 i586 i486 i386 noarch ARCH.i486 i486 i386 noarch ARCH.i386 i386 noarch DEFAULTBASE i386 REQUIRES distribution-release LINGUAS de en LABEL SUSE LINUX Version 9.1 LABEL.de SUSE LINUX in der Version 9.1 DESCRDIR suse/setup/descr DATADIR suse FLAGS update LANGUAGE en_US TIMEZONE America/Los_Angeles SUSE-updates content file: PRODUCT SUSE LINUX VERSION 9.1 DISTPRODUCT SUSE-LINUX-UPDATE-i386 DISTVERSION 9.1-1 BASEPRODUCT SUSE LINUX BASEVERSION YOUTYPE YOUPATH i386/update/9.1 VENDOR SUSE LINUX AG RELNOTESURL http://www.suse.com/relnotes/i386/SUSE-LINUX/9.1/release-notes.rpm ARCH.i686 i686 i586 i486 i386 noarch ARCH.i586 i586 i486 i386 noarch ARCH.i486 i486 i386 noarch ARCH.i386 i386 noarch DEFAULTBASE i386 REQUIRES distribution-release LINGUAS de en LABEL SUSE LINUX Version 9.1 LABEL.de SUSE LINUX in der Version 9.1 DESCRDIR /SUSE-updates/updates/setup/descr DATADIR /SUSE-updates/updates FLAGS update LANGUAGE en_US TIMEZONE America/Los_Angeles SUSE-updates/media.1/media file: SuSE Linux AG 20040407221453 2 doublesided MEDIA1 SUSE LINUX PROFESSIONAL 9.1 SIDE A DVD INSTALLATION 32BIT MEDIA2 SUSE LINUX PROFESSIONAL 9.1 SIDE A DVD UPDATE 32BIT SUSE-updates/media.1/products file: /SUSE-updates SUSE-LINUX-UPDATES-i386 9.1 -----Original Message----- From: Michael Marion [mailto:mmarion@qualcomm.com] Sent: Tue 4/26/2005 3:30 PM To: Bill.Stephens(a)pbsg.com Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] How can I regularly update the install rep ository? On 26 Apr, Stephens, Bill {PBSG} wrote: > My yast directory contains the following order file: > > /SUSE-updates/ /SUSE-updates/ In there, did you create a content file, and a media.1 directory with files in there? I copied the files from the base suse stuff and edited them slightly. One way to test the updates path is to open yast2, and try setting that path as another install source. If it's not valid, it'll say.. if it's ok, it'll show you the name, I think from the PRODUCT line in the content file.. mine's "SUSE Updates" Look for a reply from me with subj and date: Subject: Re: [suse-autoinstall] Custom install source for yast in SLES9 Date: Fri, 15 Apr 2005 12:50:53 -0700 (PDT) Where I include most of those files. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Homer: "Oh.. I hate having parties. The toilet always gets backed up!" ==> Simpsons -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

RE: [suse-autoinstall] How can I regularly update the install rep ository?
by Stephens, Bill {PBSG} 26 Apr '05

26 Apr '05

Ok, I think I'm making some progress, but I can't seem to find the glue that brings it all together. I created a content file and media.1 directory, but it's still not installing. Here's what I have: Root content file: PRODUCT SUSE LINUX VERSION 9.1 DISTPRODUCT SUSE-LINUX-DVD-i386 DISTVERSION 9.1-0 BASEPRODUCT SUSE LINUX BASEVERSION YOUTYPE YOUPATH i386/update/9.1 VENDOR SUSE LINUX AG RELNOTESURL http://www.suse.com/relnotes/i386/SUSE-LINUX/9.1/release-notes.rpm ARCH.i686 i686 i586 i486 i386 noarch ARCH.i586 i586 i486 i386 noarch ARCH.i486 i486 i386 noarch ARCH.i386 i386 noarch DEFAULTBASE i386 REQUIRES distribution-release LINGUAS de en LABEL SUSE LINUX Version 9.1 LABEL.de SUSE LINUX in der Version 9.1 DESCRDIR suse/setup/descr DATADIR suse FLAGS update LANGUAGE en_US TIMEZONE America/Los_Angeles SUSE-updates content file: PRODUCT SUSE LINUX VERSION 9.1 DISTPRODUCT SUSE-LINUX-UPDATE-i386 DISTVERSION 9.1-1 BASEPRODUCT SUSE LINUX BASEVERSION YOUTYPE YOUPATH i386/update/9.1 VENDOR SUSE LINUX AG RELNOTESURL http://www.suse.com/relnotes/i386/SUSE-LINUX/9.1/release-notes.rpm ARCH.i686 i686 i586 i486 i386 noarch ARCH.i586 i586 i486 i386 noarch ARCH.i486 i486 i386 noarch ARCH.i386 i386 noarch DEFAULTBASE i386 REQUIRES distribution-release LINGUAS de en LABEL SUSE LINUX Version 9.1 LABEL.de SUSE LINUX in der Version 9.1 DESCRDIR /SUSE-updates/updates/setup/descr DATADIR /SUSE-updates/updates FLAGS update LANGUAGE en_US TIMEZONE America/Los_Angeles SUSE-updates/media.1/media file: SuSE Linux AG 20040407221453 2 doublesided MEDIA1 SUSE LINUX PROFESSIONAL 9.1 SIDE A DVD INSTALLATION 32BIT MEDIA2 SUSE LINUX PROFESSIONAL 9.1 SIDE A DVD UPDATE 32BIT SUSE-updates/media.1/products file: /SUSE-updates SUSE-LINUX-UPDATES-i386 9.1 -----Original Message----- From: Michael Marion [mailto:mmarion@qualcomm.com] Sent: Tue 4/26/2005 3:30 PM To: Bill.Stephens(a)pbsg.com Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] How can I regularly update the install rep ository? On 26 Apr, Stephens, Bill {PBSG} wrote: > My yast directory contains the following order file: > > /SUSE-updates/ /SUSE-updates/ In there, did you create a content file, and a media.1 directory with files in there? I copied the files from the base suse stuff and edited them slightly. One way to test the updates path is to open yast2, and try setting that path as another install source. If it's not valid, it'll say.. if it's ok, it'll show you the name, I think from the PRODUCT line in the content file.. mine's "SUSE Updates" Look for a reply from me with subj and date: Subject: Re: [suse-autoinstall] Custom install source for yast in SLES9 Date: Fri, 15 Apr 2005 12:50:53 -0700 (PDT) Where I include most of those files. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Homer: "Oh.. I hate having parties. The toilet always gets backed up!" ==> Simpsons

1 0

Re: [suse-autoinstall] How can I regularly update the install rep ository?
by Michael Marion 26 Apr '05

26 Apr '05

On 26 Apr, Stephens, Bill {PBSG} wrote: > My yast directory contains the following order file: > > /SUSE-updates/ /SUSE-updates/ In there, did you create a content file, and a media.1 directory with files in there? I copied the files from the base suse stuff and edited them slightly. One way to test the updates path is to open yast2, and try setting that path as another install source. If it's not valid, it'll say.. if it's ok, it'll show you the name, I think from the PRODUCT line in the content file.. mine's "SUSE Updates" Look for a reply from me with subj and date: Subject: Re: [suse-autoinstall] Custom install source for yast in SLES9 Date: Fri, 15 Apr 2005 12:50:53 -0700 (PDT) Where I include most of those files. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Homer: "Oh.. I hate having parties. The toilet always gets backed up!" ==> Simpsons

1 0

Grub and packages on autoinstalls
by suse_list＠infineon.net 26 Apr '05

26 Apr '05

Hi, We seem to be experiencing some really strange things with SuSE 9.3 used in a build server. We purchased the SuSE 9.3 Proffessional (on box it says update edition). The problems we are experiencing is first, that when a system is installed and booted the first time we get a "Grub Harddisk Error", and system won't load. The only way to load is to go through booting failsafe and then telling it to boot the system. Having searched on google it seems to do something be grub getting confused with the disk. Booting from harddisk via PXE will fail also, as it can't find FS to boot from. The machine is a IBM Intellistation M Pro, (2.2Ghz Xeon), with a 100GB Western Digital IDE disk in it. Anyone have any ideas ? The other problem is that when we add customized packages and run the createpkg_descr script on the directory it seems to find it ok, but when we even add the package to the build profile, it doesn't seem to even install the package, but unlike SuSE 9.2 it doesn't fail either (stating it didn't find the package). Anyone have any ideas here? Please let us know Thanks S.

1 0

RE: [suse-autoinstall] How can I regularly update the install rep ository?
by Stephens, Bill {PBSG} 26 Apr '05

26 Apr '05

I must be screwing something fundamental up. The majority of doc I've found centered around SLES 8 and 9. I'm trying to do this with suse pro 9.1. I copied the DVD to my nfs mount source. When I boot my root dir structure looks like this: -r--r--r-- 1 root root 9129056 Apr 7 2004 ARCHIVES.gz -r--r--r-- 1 root root 17992 Apr 7 2004 COPYING -r--r--r-- 1 root root 25733 Apr 7 2004 COPYING.de -r--r--r-- 1 root root 1438 Apr 7 2004 COPYRIGHT -r--r--r-- 1 root root 1606 Apr 7 2004 COPYRIGHT.de -r--r--r-- 1 root root 3808102 Apr 7 2004 ChangeLog -r--r--r-- 1 root root 57276 Apr 7 2004 INDEX.gz -r--r--r-- 1 root root 363 Apr 7 2004 LIESMICH -r--r--r-- 1 root root 377 Apr 7 2004 LIESMICH.DOS -r--r--r-- 1 root root 356 Apr 7 2004 README -r--r--r-- 1 root root 370 Apr 7 2004 README.DOS drwxr-xr-x 3 root 500 4096 Apr 25 10:14 SUSE-updates -r--r--r-- 1 root root 2238 Apr 7 2004 SuSEgo.ico -r--r--r-- 1 root root 36 Apr 7 2004 autorun.inf dr-xr-xr-x 3 root root 4096 Apr 7 2004 boot -r--r--r-- 1 root root 592 Apr 7 2004 content -r--r--r-- 1 root root 21394 Apr 5 2004 control.xml -r--r--r-- 1 root root 273 Apr 26 09:50 directory.yast dr-xr-xr-x 3 root root 4096 Apr 7 2004 docu dr-xr-xr-x 20 root root 4096 Apr 7 2004 dosutils -r--r--r-- 1 root root 1694 Apr 7 2004 gpg-pubkey-3d25d3d9-36e12d04.asc -r--r--r-- 1 root root 2295 Apr 7 2004 gpg-pubkey-9c800aca-39eef481.asc -r--r--r-- 1 root root 105066 Apr 7 2004 ls-lR.gz dr-xr-xr-x 2 root root 4096 Apr 7 2004 media.1 -r--r--r-- 1 root root 2817 Apr 7 2004 pubring.gpg dr-xr-xr-x 6 root root 4096 Sep 20 2004 suse drwxr-xr-x 2 root root 4096 Apr 26 11:58 yast My yast directory contains the following order file: /SUSE-updates/ /SUSE-updates/ / / and instorder file: / /SUSE-updates/ I've run the create_package_descr script and confirmed that /SUSE-updates/updates/setup/descry/packages* files are there. When I run the install, none of the updated packages get picked up. What am I missing? I suspect the directory structure isn't set up correctly, but with 9.1 pro, I don't have a sles or core directory. Thanks, Bill Stephens -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Monday, April 25, 2005 5:03 AM To: Richard Bos Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] How can I regularly update the install repository? Richard Bos wrote: > Op woensdag 13 april 2005 23:56, schreef Michael Marion: >>Note that you have to remove conflicting old rpms too.. i.e. if you put >>something new in, like autofs-4.1.4, you have to remove autofs-4.1.3 before >>running the create_package_descr script. > > I don't think this is required, yast will determine what is newest version > available (making life much easier). > right. A much cleaner solution is to create a seperate source for updates usign the script I posted a while ago, this way you dont change the original SUSE sources.. Anas -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Network configuration with post install script.
by dbenisty＠free.fr 26 Apr '05

26 Apr '05

I'm trying to automate the network configuration on a post install script with autoyast. I cannot predict the number of ethernet card and the ones that will be used before the installation. So i wrote a script that ask the user all the network info, hostname, gateway etc . . . Actually the problem i have is when i want to use the ifcfg-eth-xxxxx file generated by autoyast when i put this : <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth0</device> <startmode>onboot</startmode> </interface> <interface> <bootproto>dhcp</bootproto> <device>eth1</device> <startmode>onboot</startmode> </interface> <interface> <bootproto>dhcp</bootproto> <device>eth2</device> <startmode>onboot</startmode> </interface> <interface> <bootproto>dhcp</bootproto> <device>eth3</device> <startmode>onboot</startmode> </interface> <interface> <bootproto>dhcp</bootproto> <device>eth4</device> <startmode>onboot</startmode> </interface> </interfaces> the file generated by autoyast have not the same content that when i use yast and give the same info. With autoyast i don't have a _nm_name=..... field on the ifcfg file and so i don't have the hwcfg-$_nm_name associated file created on /etc/sysconfig/hardware I could bypass that but it seems that i need this field to configure the bonding that i want to use on all my servers. By parsing the 'hwinfo --network' output i could generate by myself the ifcfg-xxx files & hwcfg-xxxx associated files but i'm not sure it's the way i should go. I simply cannot predict the number of card and associated driver before the install and so i cannot predict the final parameters before scanning the hardware and asking the user witch card he wanna use. So i cannot put those info on the autoyast xml file, that's why i doing that on a post instal script. So my question is, how can i automate the network configuration for various servers (i have i386 & ia64 arch) with autoyast & post install scripts ? something like that : card_list=`ls -A /sys/class/net | grep eth` choice=`kdialog --title "Bonding interfaces" --inputbox "Activate Bonding on ? (ethx ethy) :" "$card_list"` and then i ask all the network config for the bonding and i wanna be able to generate all the associated config files. i can find the info for generating the files with requests like : # the simple name here hwinfo --network | grep "Device File" | echo `awk '{print $3}'` # the driver here hwinfo --network | grep "Driver:" | awk '{print $2}' # The Driver # the pci-bus-xxxx string there hwinfo --network | grep "SysFS Device Link:" | awk '{print $4}' | grep -n devices | echo `awk -F/ '{print "pci-bus-"$NF}'` # the HW Adress hwinfo --network | grep "HW" | echo `awk '{print $3}'` # the unique id hwinfo --network | grep "Unique" | echo `awk '{print $3}'` if guess there are simple a way to do that, but i can't find it :) Greetings. Daniel

2 1

x11 - sax2
by Peter Guyan 26 Apr '05

26 Apr '05

Hi My newbie-question: In a classroom with six identical machines i try to netinstall with pxe and autoyast2 under suse9.2. I set up one machine and create a profile with it. All works fine until after the first boot, where I just get a text based login. I have to login as root, run SaX2 and init 5 to test and complete. On the "master"-machine X11 works fine. After reading some messages in the archive i suppose, that autoyast2 can't install X11. Is this correct? There were some hints on a very basic installation with VESA, which I also tried to setup - without success. Can someone give me an example of a post-install-script to setup SaX2, because my attempts did not work. Thanks. Peter

2 1

Re: [suse-autoinstall] How can I regularly update the install repository?
by Michael Marion 25 Apr '05

25 Apr '05

On 13 Apr, Luca Pacor wrote: > I am asking myself whether it would be possible to online_update the > autoinstall repository: it would be nice to be able to install new > machines using an up-to-date repository reducing this way the install > time ... > I am using SuSE 9.2 You could regularly pull down updates into your own update path, and use that. I created a SUSE-Updates tree at the same level as my SUSE-CORE and SUSE-SLES paths, and put updates into there. Then use create_package_descr to make the descr files. i.e. under sles9/SUSE-Updates/updates I have dirs for i586, x86_64, noarch and setup I put the rpms into the right paths based on arch, then cd into sles9/SUSE-Updates/updates and run: /opt/kde3/share/apps/krpmview/create_package_descr -d . That creates the files under setup: cornholio updates {1229}$ find setup/ setup/ setup/descr setup/descr/packages setup/descr/packages.DU setup/descr/packages.en Note that you have to remove conflicting old rpms too.. i.e. if you put something new in, like autofs-4.1.4, you have to remove autofs-4.1.3 before running the create_package_descr script. You could setup a tree like this and rsync in new packages when you get them, and even remove older ones if you script well enough. I do it by hand since we have to test all new changes and stuff here before we push them out into our compute farm. You also have to have the order and instorder files setup to see that path, mine are: cornholio sles9 {1234}$ cat yast/order /SUSE-Updates /SUSE-Updates /SUSE-SLES-Version-9/CD1 /SUSE-SLES-Version-9/CD1 /SUSE-CORE-Version-9/CD1 /SUSE-CORE-Version-9/CD1 cornholio sles9 {1235}$ cat yast/instorder /SUSE-CORE-Version-9/CD1 /SUSE-Updates /SUSE-SLES-Version-9/CD1 When you start a new install, or use yast to point to the Updates path, you'll know pretty quickly if it's seen as valid or not. I've used this setup to add in a lot of things we needed that weren't stock in sles9, or just to update packages. I added openafs, updated autofs with direct map support, updated kernel (mostly for autofs patches), etc. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com [Jerry and George describe wedgies to Elaine] Elaine: "Boys are sick!" Jerry: "Well what do girls do?" Elaine: "We just tease someone until they develop an eating disorder." ==> Seinfeld.

4 3

auto updating install tree
by Ashe Canvar 25 Apr '05

25 Apr '05

Hi all, I am tryng to make a fully automated installation system for SLES9 for x86_64 and i386. First of all I must congratulate Suse for such an excellent, well thought out installation automation system. Yast does have its issues, but once I learnt the ropes it has made me pretty productive. The issue I am not clear about is as follows: - I created my base install image following the docs in http://www.suse.de/~nashif/autoinstall/9.1/html/ch05s02.html#id2523126 - if I install 20 machines and then YOU them then it takes a long time, even if I run a local YOU server. - What I ideally want is to update the installation tree I have created above such that doing a YOU update post-install is not even required. Is there any way to accomplish this ? How do I download the rpm's that have been released as updates to the base SLES9 release ? Doing that through the portal site is pretty painful/manual. I would ideally like to automate this if possible as a weekl build/test/publish cycle for my organization. Thanks!

2 1

Autoinstall and Root-Password
by Daniel Spannbauer 25 Apr '05

25 Apr '05

Hello, I'm a novice in Installing with autoyast. I try a lot at this time. I have some trouble with installig SuSE 9.2 with autoyast. Problem1: The User "root" has no password, I try to fix it with: <window_manager>kde</window_manager> </x11> <users config:type="list"> <user> <username>root</username> <user_password>password</user_password> <encrypted>true</encrypted> <forename/> <surname/> </user> </users> </configure> After this the User "root" has a password but I can*t login as root. Must the password in the config-File be Plain Text? Problem2: The Installation gives an Error-Message. "Wrong LDAP-Config". This Message comes with or without an Ldap-Entry in the config-File. Has anybody the same Problems? Greetings Daniel -- Daniel Spannbauer EDV Systembetreuung marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-66 Auf der Wies 8, D 87727 Babenhausen Fax +49 8333 9233-11 http://www.marco.de/ Email ds(a)marco.de

4 4

autoinstall of OES novell components
by Victor Billings 25 Apr '05

25 Apr '05

Sorry if this has been answered previously, I have done a rudimentary search of the archive and found no answers. I have used autoinstall in the past and been quite pleased. But now I am trying to do an autoinstall of the Novell components of OES. While I can get the packages to install correctly, the YaST configuration is a complete mystery. The Novell components all show up in my software addons section ie; <addon>novell-base</addon> <addon>novell-eDirectory</addon> correctly, but I do not have the respective configuration of those components. I have been unable to find a UI in Autoinstall for the configuration of the novell components. Is this currently possible via autoinstall? Thanks, Victor

2 1

SuSE 9.0 Mount From a Post-Install Script "only root can do that"
by Ragnar Skaret 23 Apr '05

23 Apr '05

Hi, I use SuSE 9.0 professional CD version as installation source. I'm trying to run a mount within a post script but as reported earlier it fails with "mount: only root can do that" Here is the result log from post.sh.log: ----------------------- + id uid=0(root) gid=0(root) + whoami root + mount /dev/sda1 on / type ext3 (rw) proc on /proc type proc (rw) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) /dev/sda3 on /data type ext3 (rw) tmpfs on /dev/shm type tmpfs (rw) + ls -l total 156 drwxr-xr-x 2 bin bin 4096 2005-04-01 11:42 bin drwxr-xr-x 3 root root 4096 2005-04-01 11:42 boot drwxr-xr-x 3 root root 4096 2005-04-01 11:38 data drwxr-xr-x 31 root root 73728 2005-04-01 11:44 dev drwxr-xr-x 43 root root 4096 2005-04-01 11:45 etc drwxr-xr-x 3 root root 4096 2005-04-01 11:45 home drwxr-xr-x 8 root root 4096 2005-04-01 11:41 lib drwx------ 2 root root 16384 2005-04-01 11:38 lost+found drwxr-xr-x 5 root root 4096 2005-04-01 11:45 media drwxr-xr-x 2 root root 4096 2003-09-23 18:02 mnt drwxr-xr-x 3 root root 4096 2005-04-01 11:39 opt dr-xr-xr-x 49 root root 0 2005-04-01 11:43 proc drwx------ 5 root root 4096 2005-04-01 11:45 root drwxr-xr-x 3 daemon daemon 8192 2005-04-01 11:41 sbin drwxr-xr-x 4 root root 4096 2005-04-01 11:39 srv drwxrwxrwt 7 root root 4096 2005-04-01 11:45 tmp drwxr-xr-x 12 root root 4096 2005-04-01 11:39 usr drwxr-xr-x 13 root root 4096 2005-04-01 11:39 var + mount -a 192.168.113.107:/data1/SuSE90 /mnt mount: only root can do that + cd /mnt/post_scripts/ /var/adm/autoinstall/scripts/post.sh: line 9: cd: /mnt/post_scripts/: No such file or directory + cp php-4.3.4.tar.gz /tmp ----------------------- When the installation is finished I executed command "mount" and then the installation media was mounted (nfs) but it was not mounted at this point of the installation process Is the post scripts executed "between" first boot and the installation of the remaining RPMs? (Since I'm using a CD version as installation media, the CD1 is installed then a boot is performed and then the remaining CDs are installed) Is there a fix for this problem anywhere? Should I provide more logs? Any help is much appreciated This is part of my autoyast xml: <scripts> <post-scripts config:type="list" > <script> <filename>post.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ #!/bin/sh id whoami mount ls -l mount -a 192.168.113.107:/data1/SuSE90 /mnt cd /mnt/post_scripts/ cp php-4.3.4.tar.gz /tmp ]]> </source> </script> </post-scripts> </scripts> Regards Ragnar Skaret ------------------------------------------------------------ Få din egen @start.no-adresse gratis på http://www.start.no/

1 0

Autoyast file(s)
by suse_list 22 Apr '05

22 Apr '05

Hi, I was wondering a few things about the YAST autoinstall config files. I have setup the rules file correctly and all seems to work. Now what i would like to do is to split up the config files so that the <software> section is in a separate file and can be included in different config files. Basically i want custom configurations only for partitioning trees, and the rest to be modular. Another question is, how would i set it up in the config files that when it installs it also runs online updates as well and configures it to do auto-online updates from a specified server? Please let me know Thanks Sascha

2 1

multiple ethernet interfaces causes duplicate host records in the /etc/hosts file?
by deet 22 Apr '05

22 Apr '05

Hello. I am using autoyast/sles9. I just started building hosts with more than 1 physical ethernet interface which resulted in some surprising entries in the /etc/hosts file. here is the snippet of my control.xml file that pertains to the hosts networking setup. <?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"> <configure> <networking> <dns> <domain>atl.company.com</domain> <hostname>app01</hostname> <nameservers config:type="list"> <nameserver>172.17.9.25</nameserver> </nameservers> <searchlist config:type="list"> <search>atl.company.com</search> </searchlist> </dns> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <device>eth0</device> <startmode>onboot</startmode> <broadcast>172.17.177.255</broadcast> <netmask>255.255.255.0</netmask> <ipaddr>172.17.177.54</ipaddr> </interface> <interface> <bootproto>static</bootproto> <device>eth1</device> <startmode>onboot</startmode> <broadcast>10.170.3.255</broadcast> <netmask>255.255.255.0</netmask> <ipaddr>10.170.3.21</ipaddr> </interface> </interfaces> The resulting hosts file has these 2 entries. 10.170.3.21 app01.atl.company.com 172.17.177.54 app01.atl.company.com app01 The question is. Why is the line "10.170.3.21 app01.atl.company.com" being added to the /etc/hosts file? If I cannot stop this from occuring can I at least control the name that gets associated with the 2nd interface so I might end up with 10.170.3.21 eth1-app01.atl.company.com or something like that? TIA. Deet.

2 1

rules.xml and profiles question - howto define variable in rules.xml
by deet 19 Apr '05

19 Apr '05

Hello. We are running SLES9 and use autoyast to perform our client installations. I'm trying to get my installation environment to the point where I can build machines which have a hostname set and non dhcp ip's for eth0/eth1 with various routes entries. I've now been able to kind of get a working understanding of using rules.xml and profiles (mainly through reading postings from this list). So i've got this rule working which grabs the appropriated domain profile (extra domains removed for readability). The domain profile basically has all the general high level settings that apply to hosts in a domain. But then I need to be able to incorporate each host specific profile which contains host specific entries such as hostname/ip address/gateway/static routes/etc. <rule> <domain> <match>ca.company.net</match> <match_type>exact</match_type> </domain> <result> <profile>sles9.ca.cfg</profile> <continue config:type="boolean">true</continue> </result> </rule> But now I'm trying to configure the host specific profile. I realized I could add in and rule for every single host that I'm installing which would do the following but I dont like the idea of having to edit the rules file for every single host that I install. <rule> <mac> <operator>and</operator> <match>00093f10cc32</match> <match_type>exact</match_type> </mac> <result> <result> <profile>host42.ca.company.net.xml</profile> </result> </rule> Ideally I would like to see something where I have a catch all rule for all hosts which ends in a match and the resulting profile it looks for is an xml file that I have created which would be something like <mac_address>.xml or <ip_address>.xml. I've seen a posting from Anas that I could use some notation like <profile>profile-@mac@.xml</profile> But I dont know how to set that "mac" variable within the rule. Would I do a custom rule to do this and if so how would I do it? If I'm running a custom script do I embed it in the xml or have a path to a script that gets executed? I would really appreciate any pointers or tips on this topic as I feel if I can get over this last hurdle I will have a fairly portable autoyast structure that I can propogate to our various sites without much modification. If anyone would be able to include any custom rule examples I would be very greatful. Thanks for your help! Derek.

2 1

Re: [suse-autoinstall] Custom install source for yast in SLES9
by Michael Marion 15 Apr '05

15 Apr '05

On 15 Apr, Campbell, Fraser wrote: > Can anyone point me to documentation on this? Are there tools to help set > this up? Not sure on full docs, But I created a media.1 dir and a content file. So I have: SUSE-Updates/ /updates/ /i586/ /noarch/ /setup/ /x86_64/ /media1/ /directory.yast /info.txt /media /products /content Content is (Created by slightly modifying the one that came with sles9): PRODUCT SUSE Updates VERSION 9 DISTPRODUCT SUSE-Linux-SLES-x86-64 DISTVERSION 9-0 BASEPRODUCT SUSE CORE BASEVERSION 9 YOUTYPE business YOUPATH x86_64/update/SUSE-SLES/9 YOUURL http://www.suse.de/cgi-bin/suseservers.cgi VENDOR SUSE LINUX AG RELNOTESURL http://www.suse.com/relnotes/x86_64/SUSE-SLES/9/release-notes.rpm ARCH.x86_64 x86_64 i686 i586 i486 i386 noarch DEFAULTBASE x86_64 REQUIRES sles-release-9 LINGUAS de en LABEL SUSE Updates LABEL.de SUSE SLES in der Version 9 DESCRDIR updates/setup/descr DATADIR updates FLAGS update LANGUAGE en_US TIMEZONE America/Los_Angeles ====== In media.1.. directory.yast is: info.txt media products ====== info.txt is just a direct copy from the sles9 media.1 ====== media is: SuSE Linux AG 20040702194312 1 ====== Products is: / SUSE-Updates-x86-64 9 ====== I don't know which are completely required, but I was just copying files from sles9 and editing them as I saw fit.. and I'd keep trying to add the path as an install source until it worked. And it worked with the above. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com The needs of the many outweigh the needs of the few, or the one. That's from Trek. Pretty cool, huh? -- Dennis Miller

1 0

Custom install source for yast in SLES9
by Campbell, Fraser 15 Apr '05

15 Apr '05

Hi, I have a directory tree like this: Mypackages____ i386 |__ i586 |__ i686 |__ noarch |__ setup__descr The directory Mypackages/setup/descr contains files packages, packages.DU and packages.en ... the files were generated with the following command: cd Mypackages && create_package_descr -x path/EXTRA_PROV_FILE_FROM_SLES9CD1 When I export this source with NFS to an existing SLES9 server I get the message "There is no product information available at the given location. If you expected to address a product, return and enter the correct location." Can anyone point me to documentation on this? Are there tools to help set this up? Thanks, Fraser

1 0

HOWTO: SLES9: create a DVD with alle packages and the newest service pack?
by Hans Kamm 14 Apr '05

14 Apr '05

Hi, is there a way to create a new install-media with alle packages plus the newest service pack with some updates? Regards, Hans _________________________________________________________________ Eine für alle. MSN Suche. http://search.msn.de Finden statt suchen!

1 0

partition error with 9.3,, part II
by Henrik Schmidt 14 Apr '05

14 Apr '05

I checked the y2log more carefully and found an entry ["auto_added"=true] for a /boot ext2 partition. Now I understand why it fails as I already created 4 primary partitions using all space [swap,/,/export/opt,/export/home]. Why is this auto added, it wasn't with 9.2 and /boot happily lived on my root partition ? How can I disable this auto addition, I just don't want it ? Thanks Henrik -- Henrik Schmidt Christian-Albrechts-Universitaet zu Kiel Institut fuer Informatik +49 (431) 880 75 - 50 Fax or 43 Phone Olshausenstr. 40 http://www.ks.informatik.uni-kiel.de 24098 Kiel, Germany email: hbs(a)ks.informatik.uni-kiel.de

1 0

Re: [suse-autoinstall] Problems donwloading driverupdate-SLES8
by Michael Marion 13 Apr '05

13 Apr '05

On 7 Apr, Ivor Terret wrote: > GET //distro/SLES_8_0_IA32/UL/CD1/content HTTP/1.0" 200 587 Looks like your content file is linked to the content file on the first UnitedLinux cd, when it should be linked to the content file on the sles8 specifc cd. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com [Jerry and George describe wedgies to Elaine] Elaine: "Boys are sick!" Jerry: "Well what do girls do?" Elaine: "We just tease someone until they develop an eating disorder." ==> Seinfeld.

1 0

Re: [suse-autoinstall] UpdateDir:
by Michael Marion 13 Apr '05

13 Apr '05

On 6 Apr, Radzai, Bridgette A. wrote: > Can someone tell me what the UpdateDir: parameter in used for in the > linuxrc.config file? It is a default parameter and is set to > /linux/suse/i386-sles9 Well, in my sp1 image, that directory has: ls linux/suse/x86_64-sles9/ dud.config inst-sys y2update in it. dud.config has info on the SP: cornholio x86_64-sles9 {1195}$ cat dud.config UpdateName: Service Pack 1 UpdateID: 7cbcbaef9f9d4490 UpdatePriority: 100 inst-sys has a few updated binaries/libs, probably to override those on the root image from the SLES9 initial release: cornholio x86_64-sles9 {1201}$ find inst-sys/ inst-sys/ inst-sys/sbin inst-sys/sbin/save_y2logs inst-sys/usr inst-sys/usr/lib64 inst-sys/usr/lib64/YaST2 inst-sys/usr/lib64/YaST2/plugin inst-sys/usr/lib64/YaST2/plugin/libpy2qt.so inst-sys/usr/lib64/YaST2/plugin/libpy2qt.so.2 inst-sys/usr/lib64/YaST2/plugin/libpy2qt.so.2.0.0 inst-sys/usr/lib64/libhd.so.8 inst-sys/usr/lib64/libhd.so.8.78 and y2update has a bunch of udpated yast scripts.. or at least I think that's what they are. Obviously I'm on an x86_64 host too. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com [Talking about web page "design"] "I think my standards have lowered enough that now I think ``good design'' is when the page doesn't irritate the living #$*% out of me." ==>jwz (http://www.jwz.org/gruntle/design.html)

1 0

partition error with 9.3
by Henrik Schmidt 13 Apr '05

13 Apr '05

I'm using autoyast with pxeboot. I get "Error while configuring partitions" with a setup that worked with 9.2. What's new with 9.3 ? I noticed that I had to manually agree to the license, how to skip this automatically ? Where can I read about autoyast changes from 9.2 to 9.3 ? I checked /var/log/YaST2/y2log but couldn't find an error message. Any help ? I want to preserve partition 4 and format the rest with reiserfs. --------------- partition setup ------------------------ <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">swap</filesystem> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <size>1gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <size>15gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/export/opt</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">3</partition_nr> <partition_type>primary</partition_type> <size>15gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <create config:type="boolean">true</create> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/export/home</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">4</partition_nr> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning> ---------------------------------------------------------- -- Henrik Schmidt Christian-Albrechts-Universitaet zu Kiel Institut fuer Informatik +49 (431) 880 75 - 50 Fax or 43 Phone Olshausenstr. 40 http://www.ks.informatik.uni-kiel.de 24098 Kiel, Germany email: hbs(a)ks.informatik.uni-kiel.de

1 0

How can I regularly update the install repository?
by Luca Pacor 13 Apr '05

13 Apr '05

Hello everybody, I am asking myself whether it would be possible to online_update the autoinstall repository: it would be nice to be able to install new machines using an up-to-date repository reducing this way the install time ... I am using SuSE 9.2 Any hint would be greatly appreciated. Many thanks in advance Luca

1 0

Re: [suse-autoinstall] Installing 64-bit software on 64-bit computer
by Steffen Winterfeldt 13 Apr '05

13 Apr '05

Hi, [getting rid of boot loader 64 bit check on SL 9.1+] the correct way is to remove the 'notice <N>' line from isolinux.cfg/syslinux.cfg. N is a bitmask, currently these bits are defined: 0: wrong side of a two-sided dvd 1: enable 64bit check 2: software is 64bit 3: is dvd 4: software is 32+64bit (Needs bit 1 set, too!) (9.2+) 5: default install source is slp (9.3+) Steffen

1 0

can not create an 64 bit auto-install with a 32-bit system (can not select 64-bit packages)
by Marco Manngatter 13 Apr '05

13 Apr '05

hello, i have a 32-bit system(SuSE 9.2 Professional) installed, can i create an auto-install for a 64-bit system with my 32-bit system? (i can not select any 64-bit package, only 32-bit packages) OR i must install a 64-bit system to create a 64-bit auto-install(to select 64-bit packages)? thx marco manngatter

1 0

Mountpoints missing in clone.xml/SLES8
by Oliver Schweikert 12 Apr '05

12 Apr '05

Hi all, when i create a clone of my SLES 8 system, the mount points are missing for cciss devices (autoyast2-2.6.46-3). I figured out that the function findMountpoint() in AIClone.ycp assumes, that e.g. the 1. partition of /dev/hda is associated to /dev/hda1, which is correct, but for the file /dev/cciss/c0d0 the 1. partition is /dev/cciss/c0d0p1 (the "p" makes the difference). Maybe using the device major/minor numbers will be a solution. Because i have not the skills to do it on my own in a acceptabe length of time, i would be glad if a fix would be available. Regards, Oliver

1 0

Re: Re: [suse-autoinstall] Re: How to set up PXE server?
by Magnus Gedda 08 Apr '05

08 Apr '05

Hello! Im trying to follow the PXE HOW-TO for installing SuSE 9.2 on my brand new IBM Thinkpad X40. I have set up the tftp-server, copied pxegrub to the tftpboot directory, added the suggested lines to the dhcp server configuration (Im pretty sure the bootp client gets an ID, dhcp server allows IPs 192.168.0.200-204), copied the kernel and the initrd to to the tftp directory and created the sample menu.lst in the tftp boot directory. The first suggested change of the menu.lst is not done yet, since I havent found out the module name of the network card yet, but I still think that the actions above would present me with a grub bootloader screen on my X40 when booting over LAN. As connection between my X40 and my server I use a cross-connected TP cable. Now to the problem. When I boot my X40 over LAN I get the following messages: _____messages_start___________________________________________ Intel(R) Boot Agent GE v1.2.17 Copyright (C) 1997-2003, Intel Corporation Intel(R) Boot Agent PXE Base Code (BA1217BC) Copyright (C) 1997-2003, Intel Corporation CLIENT MAC ADDR: <macaddr> GUID: <guid> CLIENT IP: 192.168.0.203 MASK: 255.255.255.0 DHCP IP: 192.168.0.2 GATEWAY IP: 192.168.0.2 Probing...[RTL8139] - The PCI BIOS has not enabled this service! Updating PCI command 0106->0107. pci_bus 00 pci_device_fn 00 PCI latency timer (CFLT) is unreasonably low at 0. Setting to 32 clocks. ioaddr 0X0000, addr AA:AA:00:00:AA:AA 10Mbps full-duplex _____messages_end_____________________________________________ It seems that the dhcp service works since the client gets an IP of 192.168.0.203, but after that Im completely at a loss. Can anyone please help me figure out what is wrong and why I dont get the menu screen? What is the client probing for, and what is RTL8139? I cannot find anything about it in the BIOS, so haw do I enable it? Any help at all would be greatfully appreciated! Sincerely, Magnus Gedda

2 1

partitioning problem.
by Chuck Clark 07 Apr '05

07 Apr '05

I'm getting an error during the partitioning process of the autoyast install. I have the following partition definitions and it complains that it could not do the partitioning plan and to check the control file. SuSE 8.2. <drive> <device>/dev/sda</device> <use>all</use> <partitions config:type="list"> <partition> <size>1gb</size> <mount>swap</mount> </partition> <partition> <size>5gb</size> <mount>/</mount> </partition> <partition> <size>max</size> <mount>/other</mount> </partition> </partitions> </drive> Any help will be greatly appreciated. Thanks in advance, Chuck

1 0

Problems donwloading driverupdate-SLES8
by Ivor Terret 07 Apr '05

07 Apr '05

Hello list I am trying to install SLES8 for x86 SP 3or SP4 over network using http. Autoyast starts ok, but when i reach the "software configuration" stage, it exits with "error with your software selection" My setup is according to the SuSE documentation, both in the HOWTO and on the WWW. It seems that the client os not requesting the driverupdate file at all. What determines if the client requests the driverupdate file or not? The last error entry in the /var/log/Yast2/y2log complains about /media.1/product but wget retrieves this ok. Thanks Ivor

1 1

UpdateDir:
by Radzai, Bridgette A. 06 Apr '05

06 Apr '05

Can someone tell me what the UpdateDir: parameter in used for in the linuxrc.config file? It is a default parameter and is set to /linux/suse/i386-sles9 I could not find it documented anywhere. Thanks, Bridgette

1 0

RE: [suse-autoinstall] Yast, autoyast, LDAP and home/small company networking
by Schumacher, Gordon 06 Apr '05

06 Apr '05

I don't know if this is a good solution for you... but if your requirement is mainly to get the package selection the same, a simpler thing that using AutoYaST would be to configure your package selection, and then save the list out to a floppy (YaST can do that). -----Original Message----- From: Birger Kollstrand [mailto:birger.kollstrand@losmail.no] Sent: Monday, March 28, 2005 5:08 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Yast, autoyast, LDAP and home/small company networking Hi, I have looked around on the SuSE web nad searched the lists to find information on Yast and home/small company network setup. I have com up short on a couple of areas and would very much appreciate som help and guidance. Please redirect me to other mailing lists if this is not the right place. Here is what I want to accomplish on my 8 machine home network first. 1. Authenticate users towards OpenLDAP (or eDirectory) 2. Automount the home directories 3. Add roming possibility so the users can log on while not beeing able to contact the LDAP server. For this I have been thinking of using the http://www.padl.com/OSS/nss_updatedb.html . 4. I want to do this to new machines via autoyast. All machines are different so generating an immage is not good. 5. I want to be able to add necesary SW/Config already configured machines automagically. Now I have accomplished to set up the OpenLDAP server ( although there was no YAST module for that) and I have via YAST set up a client to successfully authenticate towards the OpenLDAP server. In the YAST module I have ticked of the "Start Automounter", but the home directory is not mounted upon login. I can mount the home directory manually without any problems. So the questions are : 1. What does the "Start Automounter" setting actually mean? 2. Is the nss_updatedb the right way to go to achieve the possibility for local login? 3. Can autoyast be used to achieve point 4 and 5 above? (What is the best documentation for autoyast? http://www.novell.com/documentation/nld/index.html?page=/documentation/nld/… ?) 4. There is no mailinglist for Yast. Is it possible to get in contact with the maintainer to discuss enhancements? I'm willing to test and (with my limited c++/qt skills) develop aditions in this area. regards Birger Kollstrand -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Too long append-line for pxe-installation
by Ragnar Kjørstad 06 Apr '05

06 Apr '05

Hi We have encountered a problem where the append-line for kernel-arguments for the install-kernel (PXE-boot) exceeds 255 characters. Is there any way we can shorten the commandline by moving some of the arguments into the autoyast-file? We currently use the following options: - load_ramdisk - initrd - autoyast - install - netdevice - gateway - nofb - textmode In particular, the "install"-option takes up a lot of characters (with a long nfs-url). -- Ragnar Kjørstad Software Engineer Scali - http://www.scali.com High Performance Clustering

3 4

RE: [suse-autoinstall] Too long append-line for pxe-installation
by Ness, Todd 05 Apr '05

05 Apr '05

There should be plenty of mail on this in the archive, but, look at using the info file in the initrd. -----Original Message----- From: Ragnar Kjørstad [mailto:suse@ragnark.vestdata.no] Sent: Tuesday, April 05, 2005 7:29 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Too long append-line for pxe-installation Hi We have encountered a problem where the append-line for kernel-arguments for the install-kernel (PXE-boot) exceeds 255 characters. Is there any way we can shorten the commandline by moving some of the arguments into the autoyast-file? We currently use the following options: - load_ramdisk - initrd - autoyast - install - netdevice - gateway - nofb - textmode In particular, the "install"-option takes up a lot of characters (with a long nfs-url). -- Ragnar Kjørstad Software Engineer Scali - http://www.scali.com High Performance Clustering -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

OES for Linux - network autoinstall problem
by John Line 05 Apr '05

05 Apr '05

I've been doing some preparation for (PXE+HTTP) network installation of a group of new servers (soon to be ordered, don't have them yet) using VMware (V5 beta, with host system running SuSE 9.2 Professional). I was originally installing SLES9 but switched to an evaluation download of OES for Linux (i.e. SLES9 + extras) when that became available. This is using PXE boot and HTTP access to the installation source. [I suspect those details aren't relevant to the problem, but mentioned "just in case".] The fairly basic (so far!) autoinstallation configuration that worked fine with SLES9 also mostly worked with OES, but one significant detail (that I've noticed so far, there may be others) fails consistently without any explanation or comment that I've seen. [Side-issue: is there any documentation of changes and additions to the available XML configuration settings, for OES as compared to SLES9? The DTDs show what differs at the syntactic level, but that's only half the story.] The problem is with nameserver configuration - with SLES9, that "just worked" but with OES it simply fails to create /etc/resolv.conf with the obvious effects on network access. Other aspects of the network configuration (e.g. setting up static IP addresses and default router, and enabling the network) *did* work in OES, the effect is as though something simply forgot to install the nameserver configuration. The namserver-related part of the configuration that's currently getting ignored is <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <dhcp_resolv config:type="boolean">false</dhcp_resolv> <domain>mynet</domain> <hostname>oestest</hostname> <nameservers config:type="list"> <nameserver>131.111.8.32</nameserver> <nameserver>131.111.12.20</nameserver> </nameservers> <searchlist config:type="list"> <search>mynet</search> <search>cam.ac.uk</search> </searchlist> </dns> Has anyone else seen this problem? Is there any better solutio than creating the missing file by using a postinstall script? I tried recreating the network configuration definitions for autoinstallation, using yast after manually installing OES, but I don't think it was any different from what I'd been trying and it made no difference anyway, resolv.conf still not created - so the obvious possibility, that the required XML definitions had changed incompatibly for OES - seems to be ruled out as an explanation. John Line -- John Line - web & news development, University of Cambridge Computing Service

1 0

Autoyast
by Chuck Clark 04 Apr '05

04 Apr '05

Greetings- I have attempted many times to set up the auto install and it continues to give me a problem. I've modified the initrd, I've modified the isolinux.cfg, I've created a simple info file and have the autoinst.xml. Yet it still continues to look for the first disk ??? I've created a directory structure as follows: Boot/ Bootdisk Loader/ Autoinst.xml Initrd Isolinux.bin Isolinux.cfg Linux message Infofile Suse/ I586/ I686/ Noarch/ Setup/ My goal is to create my own distro. With the rpms that I need, is this possible? Thanks ahead of time for the help. Chuck

1 0

RE: [suse-autoinstall] SLES9 Installation Tree
by Radzai, Bridgette A. 04 Apr '05

04 Apr '05

Frank, Thank you for the information. One major issue is my source installation server is a Windows server, so I am unable to use the great tools that yast supplies to do this. One thought I had has to create a Sles9 server and use yast to create my Sles9 SP1 directory tree. Then copy it all to my Windows server. Any thoughts? What will Windows do with the symbolic links? Any other suggestions? I am even seeing issues with my boot CD since I changed the "Linux" and "initrd" files to the SP1 versions. I am so close, but yet so far with this whole project. It seems so straight forward, but I can't get it to work. Thanks for the help! Bridgette -----Original Message----- From: Frank Steiner [mailto:fsteiner-mail@bio.ifi.lmu.de] Sent: Friday, April 01, 2005 7:12 AM To: Radzai, Bridgette A. Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] SLES9 Installation Tree I had the same problem as you can see in the archives. It seems that things can go wrong if you set up your installation directory manually and then try to integrate the SP1 stuff. Rename you current directory, and setup the installation sources again with yast. Then also add the SP1 sources with yast. Then it should work, and will still continue working if you rename the directories (fixing their names in the yast (inst)order, too) afterwards. I could even remove the CD? subdirectories and put all the stuff in the same directory, i.e., just having sles9/ and sles9-SP1/ directories with no further CD? subdirectories. SDK sources could not be added with yast, I added them manually after renaming the subdirs. And that worked fine. cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

3 2

RE: [suse-autoinstall] Network Ports and /etc/sysconfig/network
by Schumacher, Gordon 04 Apr '05

04 Apr '05

Out of curiosity - will those RPMs work with SuSE 9.2? -----Original Message----- From: Suffin, Charles [mailto:Charles.Suffin@stratus.com] Sent: Wednesday, March 23, 2005 3:07 PM To: 'Anas Nashif' Cc: suse-autoinstall(a)suse.com Subject: RE: [suse-autoinstall] Network Ports and /etc/sysconfig/network Anas, Looks good now!!! You've really helped me out. The latest batch of RPMs create the files in /etc/sysconfig/network and they contain all the correct information, including the "UNIQUE=" data. Thank you so much for your assistance in getting this resolved. -- Charlie -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Friday, March 18, 2005 12:28 PM To: Suffin, Charles Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Network Ports and /etc/sysconfig/network Hi, There is an update pending you might want to try which fixes some issues with network and autoyast. See http://www.suse.de/~nashif/autoyast2/rpms/sles9/sles9-i386/ You will need all rpms. Create a new source with those updates using the script: http://www.suse.de/~nashif/autoyast2/scripts/create_update_source.sh and put all the above rpms in there. Dont forget to run create_package_descr after you have copied the rpms. then, you will need something like that: <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth0</device> <startmode>onboot</startmode> </interface> <interface> <bootproto>dhcp</bootproto> <device>eth1</device> <startmode>onboot</startmode> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>eth0</device> <module>e1000</module> </module_entry> <module_entry> <device>eth1</device> <module>e100</module> </module_entry> </modules> Please report if that works for you. Anas Suffin, Charles wrote: > Hi folks, > > It seems that the auto-installation of network ports (which are described in > the XML control file) doesn't create files in /etc/sysconfig/network. > However, if you run YaST2 Network Devices (left) Network Card (right) and > add a network port, a file in /etc/sysconfig/network like > ifcfg-eth-id-AA:BB:CC:DD:EE:FF is created -- the name corresponds to the MAC > address of the card. > > Here's a snippet from my XML. Anyone know why auto-install isn't creating > the file(s) in /etc/sysconfig/network? Or, do you know what source code I > should look at to figure this out? : > > <interfaces config:type="list"> > <interface> > <bootproto>dhcp</bootproto> > <device>eth0</device> > <startmode>onboot</startmode> > </interface> > <interface> > <bootproto>dhcp</bootproto> > <device>eth1</device> > <startmode>onboot</startmode> > </interface> > </interfaces> > <modules config:type="list"> > <module_entry> > <device>bus-pci-0000:01:03.0</device> > <module>e1000</module> > </module_entry> > <module_entry> > <device>bus-pci-0000:01:06.0</device> > <module>e100</module> > </module_entry> > </modules> > > -- Charlie > > p.s./ I'm talking about auto-installation of SLES9 and SLES9-SP1. > > ----- > A. Charles Suffin > Senior Software Engineer > Stratus Technologies, Inc. (http://www.stratus.com) > 111 Powdermill Road > Maynard, MA 01754-3409 > US (978)461-7590 > > > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

RE: [suse-autoinstall] autoyast missing packages when creating iso
by Schumacher, Gordon 04 Apr '05

04 Apr '05

If I'm not mistaken, this is because you've upgraded packages (with something like YOU). I did this, and I had to remove part of the revision number. For instance, in your example below, you'd want: ./suse/i586/3ddiag-0.703.i586.rpm ./suse/i586/BASS-20030801.i586.rpm You should be able to do that with a regex search-and-replace. -----Original Message----- From: Martyn Iles [mailto:martyn@kryten.org] Sent: Friday, March 25, 2005 4:19 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] autoyast missing packages when creating iso I'm having a problem when trying to create an automatic install of SuSE to put on CDROM. This is SuSE 9.0, if that makes any difference. I go through AutoYaST, tell it to clone my config and then select the Create ISO option, but then I get: Missing Packages ./suse/i586/3ddiag-0.703-172.i586.rpm ./suse/i586/BASS-20030801-55.i586.rpm Plus loads of others Now, I've got the entire SuSE 9.0 (all 7Gb) on an FTP server of mine and if I go into YaST and install extra packages, they install fine. Note that this was NOT where I installed from - I used a remote ftp mirror for the install as my local copy hadn't finished downloading so I've been into Yast and changed the installation source (could autoyast be picking up the path to the original RPMS from somewhere?). If I ftp to the machine and cd to the directories listed above its fine: ftp> cd ./suse 250 CWD command successful. ftp> ls 200 PORT command successful. 150 Opening ASCII mode data connection for file list. i586 i686 noarch nosrc setup src 226 Transfer complete. ftp: 39 bytes received in 0.00Seconds 39000.00Kbytes/sec. ftp> cd i586 250 CWD command successful. ftp> ls 3dd* 200 PORT command successful. 150 Opening ASCII mode data connection for file list. 3ddiag-0.703-172.i586.rpm 226 Transfer complete. ftp: 27 bytes received in 2.12Seconds 0.01Kbytes/sec. ftp> So, any suggestions for what I've done wrong? I've spent over a day on this, had the SuSE available on multiptle FTP/HTTP sites and I just cannot get it to work! Does AutoYaST actually work (I've tried this on two different SuSE 9.0 machines)? If not, how else can I clone a SuSE 9.0 install so that it can be installed (without much user intervention) on multiple machines from a CDROM? -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

RE: [suse-autoinstall] Network Ports and /etc/sysconfig/network
by Suffin, Charles 01 Apr '05

01 Apr '05

Oooh, I don't know, Gordon. I've only tried them (and they work) with SLES9 SP1, using the "update" directory that's created by Anas' script in the installation source. -----Original Message----- From: Schumacher, Gordon [mailto:gordon_schumacher@maxtor.com] Sent: Friday, April 01, 2005 1:32 PM To: Anas Nashif Cc: suse-autoinstall(a)suse.com Subject: RE: [suse-autoinstall] Network Ports and /etc/sysconfig/network Out of curiosity - will those RPMs work with SuSE 9.2? -----Original Message----- From: Suffin, Charles [mailto:Charles.Suffin@stratus.com] Sent: Wednesday, March 23, 2005 3:07 PM To: 'Anas Nashif' Cc: suse-autoinstall(a)suse.com Subject: RE: [suse-autoinstall] Network Ports and /etc/sysconfig/network Anas, Looks good now!!! You've really helped me out. The latest batch of RPMs create the files in /etc/sysconfig/network and they contain all the correct information, including the "UNIQUE=" data. Thank you so much for your assistance in getting this resolved. -- Charlie -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Friday, March 18, 2005 12:28 PM To: Suffin, Charles Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Network Ports and /etc/sysconfig/network Hi, There is an update pending you might want to try which fixes some issues with network and autoyast. See http://www.suse.de/~nashif/autoyast2/rpms/sles9/sles9-i386/ You will need all rpms. Create a new source with those updates using the script: http://www.suse.de/~nashif/autoyast2/scripts/create_update_source.sh and put all the above rpms in there. Dont forget to run create_package_descr after you have copied the rpms. then, you will need something like that: <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth0</device> <startmode>onboot</startmode> </interface> <interface> <bootproto>dhcp</bootproto> <device>eth1</device> <startmode>onboot</startmode> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>eth0</device> <module>e1000</module> </module_entry> <module_entry> <device>eth1</device> <module>e100</module> </module_entry> </modules> Please report if that works for you. Anas Suffin, Charles wrote: > Hi folks, > > It seems that the auto-installation of network ports (which are described in > the XML control file) doesn't create files in /etc/sysconfig/network. > However, if you run YaST2 Network Devices (left) Network Card (right) and > add a network port, a file in /etc/sysconfig/network like > ifcfg-eth-id-AA:BB:CC:DD:EE:FF is created -- the name corresponds to the MAC > address of the card. > > Here's a snippet from my XML. Anyone know why auto-install isn't creating > the file(s) in /etc/sysconfig/network? Or, do you know what source code I > should look at to figure this out? : > > <interfaces config:type="list"> > <interface> > <bootproto>dhcp</bootproto> > <device>eth0</device> > <startmode>onboot</startmode> > </interface> > <interface> > <bootproto>dhcp</bootproto> > <device>eth1</device> > <startmode>onboot</startmode> > </interface> > </interfaces> > <modules config:type="list"> > <module_entry> > <device>bus-pci-0000:01:03.0</device> > <module>e1000</module> > </module_entry> > <module_entry> > <device>bus-pci-0000:01:06.0</device> > <module>e100</module> > </module_entry> > </modules> > > -- Charlie > > p.s./ I'm talking about auto-installation of SLES9 and SLES9-SP1. > > ----- > A. Charles Suffin > Senior Software Engineer > Stratus Technologies, Inc. (http://www.stratus.com) > 111 Powdermill Road > Maynard, MA 01754-3409 > US (978)461-7590 > > > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

SLES9 Installation Tree
by Radzai, Bridgette A. 01 Apr '05

01 Apr '05

I have integrated SP1 into my current sles9 MS directory structure as outlined in Anas' 2/05/05 posting to Egan. I have updated my boot cd with the "linux" and "initrd" from the sp1 CD1. Modified the linuxrc.config. I believe something is incorrect with my directory structure, the installation server is found, loads the SUSE SLES CD1 successfully, but when it tries to find SUSE CORE CD1 I get: Insert 'SUSE LINUX Enterprise Server 9 CD2' URL http://...../sles9_x86/SUSE-SLES-Version-9/CD1 SuSE Linux = SuSE Linux AG 2000040702202411 ! = 20040702201519 Did my media.1 folders not get copied correctly? Thanks in advance for the assistance! Bridgette

2 1

Re: [suse-autoinstall] SLES9 Installation Tree
by Alfred Isele 01 Apr '05

01 Apr '05

Hi Bridgette, We run a remote autoyast installation started via pxeboot. See below out directory structure, media files ... Hope this will help you. Regards Alfred autoyast yast SLES/CD1 SP1/CD1 SP1/CD2 SP1/SP3 CORE/CD1 CORE/CD2 CORE/CD3 CORE/CD4 CORE/CD5 boot -> SLES/CD1/boot content -> SLES/CD1/content control.xml -> SLES/CD1/control.xml driverupdate -> SP1/CD1/driverupdate linux -> SP1/CD1/linux media.1 -> SLES/CD1/media.1 # cat SLES/CD1/media.?/media SuSE Linux AG 20040702202411 1 MEDIA1 SUSE LINUX Enterprise Server 9 CD1 # cat SP1/CD?/media.?/media SuSE Linux AG 20050117203108 3 SuSE Linux AG 20050117203108 SuSE Linux AG 20050117203108 # cat CORE9/CD?/media.?/media SuSE Linux AG 20040702201519 5 SuSE Linux AG 20040702201519 SuSE Linux AG 20040702201519 SuSE Linux AG 20040702201519 SuSE Linux AG 20040702201519 # cat yast/order # entries here are tab delimited! /SP1/CD1 /SP1/CD1 /SLES/CD1 /SLES/CD1 /CORE9/CD1 /CORE9/CD1 # cat yast/instorder /SP1/CD1 /SLES/CD1 /CORE9/CD1 At 23:33 31.03.2005, Radzai, Bridgette A. wrote: >I have integrated SP1 into my current sles9 MS directory structure as >outlined in Anas' 2/05/05 posting to Egan. > >I have updated my boot cd with the "linux" and "initrd" from the sp1 >CD1. Modified the linuxrc.config. > >I believe something is incorrect with my directory structure, the >installation server is found, loads the SUSE SLES CD1 successfully, > >but when it tries to find SUSE CORE CD1 I get: > > > >Insert 'SUSE LINUX Enterprise Server 9 CD2' > >URL http://...../sles9_x86/SUSE-SLES-Version-9/CD1 > >SuSE Linux = SuSE Linux AG > >2000040702202411 ! = 20040702201519 > > > >Did my media.1 folders not get copied correctly? > > > >Thanks in advance for the assistance! > > > >Bridgette > >

1 0