December 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

linuxrc - netdevice=<hwaddress>
by John Willis 18 Dec '12

18 Dec '12

Does anyone know if any of the SLES releases 9 or 10 support passing the linuxrc option netdevice=<hardware mac address> ? I noticed Red Hat has had this for sometime and it seems totally missing in SuSE which seems really odd. I'm still scratching my head if we really are still passing only by kernel interface name. I read in the change log for linuxrc-1.8.6-3 a change that "sounds" like this feature. * Mon Mar 14 2005 - snwint(a)suse.de - s390: fix segfault in net_list_s390_devs() - extra root image was sometimes not used - allow netdevices to be specified by hwaddress But it looks like linuxrc-1.8.6-3 is only available in SuSE Professional 9.3. "any" commentary would be sincerely appreciated the feature also seems to be fairly minor since any delimiter seperating the octets in the hwaddr string could be used to identify the difference between an interface name and interface hw address if i could figure out a generic method of overriding the linuxrc with a custom script and daisy chain it back into linuxrc after setting up the interface name, I would.. and have a slight idea on how to do that.. but i'd rather find out i'm just missing something and the feature is already there Thanks!

3 2

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

05 Mar '08

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

4 6

Scripting dirinstall?
by Teun 25 Feb '07

25 Feb '07

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

3 2

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

03 Jan '07

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

2 3

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

02 Jan '07

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

3 3

[opensuse-autoinstall] Autoinstall Package Selection in 10.2
by Alan Becker 29 Dec '06

29 Dec '06

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

1 0

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

29 Dec '06

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

1 0

[opensuse-autoinstall] Re: [suse-autoinstall] Please include the right DTDs in SuSE 10.2
by David Werner 20 Dec '06

20 Dec '06

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

2 4

[opensuse-autoinstall] SLED10 - Patterns error
by Mark Rodee 19 Dec '06

19 Dec '06

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

1 0

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

18 Dec '06

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

1 0

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

18 Dec '06

So what was the change that was made in response to [bug] init-script does not require network now > -----Original Message----- > From: Uwe Gansert [mailto:ug@suse.de] > Sent: Monday, December 18, 2006 5:28 AM > To: opensuse-autoinstall(a)opensuse.org > Subject: Re: [opensuse-autoinstall] SUMMARY: Init-scripts and > nfs location > > On Friday 15 December 2006 20:03, Andrew Laden wrote: > > > 6: Note that even your init scripts will not have the > network up when > > they run as of Sles10, sp1. > > (http://www.suse.com/~ug/autoyast_changes_SLES10SP1.html) > So if your > > init scripts need the network, you will have to bring it up in them. > > that's not true. If the network is configured, then it's > raised up before the init-script on SP1. > > -- > ciao, Uwe Gansert > > Uwe Gansert, Server Technologies Team > SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany > Business: http://www.suse.de/~ug > -- > To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org > For additional commands, e-mail: > opensuse-autoinstall+help(a)opensuse.org > > -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

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

18 Dec '06

To summarize the answers and solution. 1: At the time that the init-scripts are fetched, the network is not available. So you can not use <location>...</location> references with nfs, http, ftp etc. Only with file. Anyone who says they have it working has probably brought the network up in a previous script. 2: The following works. <scripts> <post-scripts config:type="list"> <listentry> <filename>fetch-init.sh</filename> <interpreter>shell</interpreter> <source><![CDATA[ /etc/init.d/network start /etc/init.d/portmap start /bin/mount -r 192.168.1.1:/vol/source /mnt /bin/cp /mnt/initfile.sh /tmp /bin/umount /mnt /etc/init.d/portmap stop /etc/init.d/network stop ]]></source> </listentry> </post-scripts> <init-scripts config:type="list"> <listentry> <filename>initscript.sh</filename> <location>file:///tmp/initfile.sh</location> </listentry> </init-scripts> </scripts> Notes: 1: The network has been configured at the point the postinstall runs (if you are just using autoyast to configure it), so this works even with dhcp, and DNS. 2: portmap is necessary for NFS. If you just want to use http or ftp, then you just need the network. (curl is available in a minimal install, wget is not) 3: The reason for putting it into tmp then using the init-script, is that if there are no init-scripts defined, then autoyast will not put the hook in to run them, even if there are scripts in /var/adm/aytoinstall/init.d 4: Yes the syntax is file:///path/file. 2 slashes, the the full path starting with a /. 5: What if you don't down the network? Probably nothing, but if you have later scripts that configure the network, and it is already up, your changes wont take affect. 6: Note that even your init scripts will not have the network up when they run as of Sles10, sp1. (http://www.suse.com/~ug/autoyast_changes_SLES10SP1.html) So if your init scripts need the network, you will have to bring it up in them. Thanks all -Andrew > -----Original Message----- > From: Andrew Laden [mailto:Andrew.Laden@tudor.com] > Sent: Tuesday, December 12, 2006 3:26 PM > To: opensuse-autoinstall(a)opensuse.org > Subject: [opensuse-autoinstall] Init-scripts and nfs location > > Using autoyast on Sles 9 SP3. pxebooting using dhcp. > Installing over NFS, Autoyast file served up via NFS, so I > know that all works fine. > Autoinstall all works fine. I get a fully installed ready to > go system. > > So now I am trying to use/configure some init scripts. I have > two of them. One I have placed the source in the xml, and the > other via NFS. > > <scripts> > <init-scripts config:type="list"> > <script> > <filename>init-zeus_bootstrap</filename> > <interpreter>shell</interpreter> > > <location>nfs://192.168.1.1/vol/prod_LinuxInstall_grn_x/zeus/z > eus_bootst > rap</location> > </script> > <script> > <filename>init-online-update.sh</filename> > <interpreter>shell</interpreter> > <source><![CDATA[ > /usr/bin/online_update -s -u http://lx4-adm.grn.tudor.com/YOU > -V > /var/tmp/online-update.out 2> /var/tmp/online-update.err > ]]></source> > </script> > </init-scripts> > </scripts> > > > The one with source works fine. The other doesn't seem to work. So > 1: Is the location paramter supported on Sles 9.3 for init scripts. > 2: Is this section parsed and the files created at a time > when the network is up, so that NFS is available? > 3: Are there some log files that will help me. Since the > script never runs, there is nothing in /var/adm/autoinstall. > It looks like the script never gets copied from NFS and > placed in there. > > Thanks > -Andrew > > -- > To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org > For additional commands, e-mail: > opensuse-autoinstall+help(a)opensuse.org > > -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

Re: [opensuse-autoinstall] how to create customized Install CD that have pre-defined installation so
by 张韡武 17 Dec '06

17 Dec '06

在 2006-12-16六的 15:14 +0000，Yan Fitterer写道： > install=ftp://host.name/path/to/network/install/source autoyast=ftp://host.name/path/to/autoinstall.xml > > Never created a CD myself, but those are the two critical parameters you need on the kernel command line to kick off an autoinstall. And of course a working network install source and a working autoyast .xml file. > > Good luck Ah, thank you very much! I do have tried to specify 'autoyats=' and also tired to specify 'install=' but never tired to use them together! That's because I started to think autoyast and installation are not related, otherwise install source should be a part of autoyast. Stupid I am. Anyway, problem solved. > Yan > > >>> 张韡武 <zhangweiwu(a)realss.com> 16/12/2006 14:18 >>> > Hello. right now I badly need to create customized SuSE mini-install CDR > that default to install from the http installation source we provide. > > Today and yesterday I have been struggling with autoyast and (what the > hell) I cannot find a way to specify default installation source for > creating customized mini-install CD. The autoyast document > (http://www.suse.com/~ug/autoyast_doc/) has a lot of pages and I read > through them, there are all options about how to partition, how to set > up RAID, how to setup user account and do software selection, but no > simple answer on how to specify network installation source URI. I also > tried to reach a lot of webpages about yast2-cd-creator, so far it seems > yast2-cd-creator can neither use network installation source nor can it > create CDR that can use network installation source. > > I also tried to create my own bootable CDROM and assign boot parameter > 'install=ftp://our.ftp.inst-source.mirror/opensuse/distribution/10.2' > and > 'install=ftp://our.ftp.inst-source.mirror:/opensuse/distribution/10.2' > in /boot/i386/loader/isolinux.cfg and create bootable CDR with 'mkisofs > -b .. -c ..' and both do not seem to work (after boot, still prompt me > for installation source and path, default path is '/' so my path setting > seems have no effect) > > So I am completely stuck here: I don't know how can I go on. What's > worse, tomorrow is the day when we collected a lot of new guys who wish > to try Linux together for a workshop, at which event we shall distribute > the CDR. > > Before the event I planned two days for working out this issue > (yesterday and today) and I don't understand why this problem look so > simple (create CD with pre-defined installation source URI) but this > difficult to do. I almost read every webpage I can google out. > > Any other hint you can give me or link that point me to go to? > -- 锐业软服（国内业务） http://www.realss.cn Real SoftService http://www.realss.com 销售咨询(Sales Department): 0086 592 20 99987 (Chinese, German, English) 国际业务(International Sales): 0086 10 8460 6011 (German and English) 联系：厦门大学科技园，嘉庚二号楼6楼邮政：厦门大学2312号信箱（邮编361005）

1 0

Re: [opensuse-autoinstall] how to create customized Install CD that have pre-defined installation so
by Yan Fitterer 16 Dec '06

16 Dec '06

install=ftp://host.name/path/to/network/install/source autoyast=ftp://host.name/path/to/autoinstall.xml Never created a CD myself, but those are the two critical parameters you need on the kernel command line to kick off an autoinstall. And of course a working network install source and a working autoyast .xml file. Good luck Yan >>> 张韡武 <zhangweiwu(a)realss.com> 16/12/2006 14:18 >>> Hello. right now I badly need to create customized SuSE mini-install CDR that default to install from the http installation source we provide. Today and yesterday I have been struggling with autoyast and (what the hell) I cannot find a way to specify default installation source for creating customized mini-install CD. The autoyast document (http://www.suse.com/~ug/autoyast_doc/) has a lot of pages and I read through them, there are all options about how to partition, how to set up RAID, how to setup user account and do software selection, but no simple answer on how to specify network installation source URI. I also tried to reach a lot of webpages about yast2-cd-creator, so far it seems yast2-cd-creator can neither use network installation source nor can it create CDR that can use network installation source. I also tried to create my own bootable CDROM and assign boot parameter 'install=ftp://our.ftp.inst-source.mirror/opensuse/distribution/10.2' and 'install=ftp://our.ftp.inst-source.mirror:/opensuse/distribution/10.2' in /boot/i386/loader/isolinux.cfg and create bootable CDR with 'mkisofs -b .. -c ..' and both do not seem to work (after boot, still prompt me for installation source and path, default path is '/' so my path setting seems have no effect) So I am completely stuck here: I don't know how can I go on. What's worse, tomorrow is the day when we collected a lot of new guys who wish to try Linux together for a workshop, at which event we shall distribute the CDR. Before the event I planned two days for working out this issue (yesterday and today) and I don't understand why this problem look so simple (create CD with pre-defined installation source URI) but this difficult to do. I almost read every webpage I can google out. Any other hint you can give me or link that point me to go to? -- 锐业软服（国内业务） http://www.realss.cn ( http://www.realss.cn/ ) Real SoftService http://www.realss.com ( http://www.realss.com/ ) 销售咨询(Sales Department): 0086 592 20 99987 (Chinese, German, English) 国际业务(International Sales): 0086 10 8460 6011 (German and English) 联系：厦门大学科技园，嘉庚二号楼6楼邮政：厦门大学2312号信箱（邮编361005） -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] how to create customized Install CD that have pre-defined installation source?
by 张韡武 16 Dec '06

16 Dec '06

Hello. right now I badly need to create customized SuSE mini-install CDR that default to install from the http installation source we provide. Today and yesterday I have been struggling with autoyast and (what the hell) I cannot find a way to specify default installation source for creating customized mini-install CD. The autoyast document (http://www.suse.com/~ug/autoyast_doc/) has a lot of pages and I read through them, there are all options about how to partition, how to set up RAID, how to setup user account and do software selection, but no simple answer on how to specify network installation source URI. I also tried to reach a lot of webpages about yast2-cd-creator, so far it seems yast2-cd-creator can neither use network installation source nor can it create CDR that can use network installation source. I also tried to create my own bootable CDROM and assign boot parameter 'install=ftp://our.ftp.inst-source.mirror/opensuse/distribution/10.2' and 'install=ftp://our.ftp.inst-source.mirror:/opensuse/distribution/10.2' in /boot/i386/loader/isolinux.cfg and create bootable CDR with 'mkisofs -b .. -c ..' and both do not seem to work (after boot, still prompt me for installation source and path, default path is '/' so my path setting seems have no effect) So I am completely stuck here: I don't know how can I go on. What's worse, tomorrow is the day when we collected a lot of new guys who wish to try Linux together for a workshop, at which event we shall distribute the CDR. Before the event I planned two days for working out this issue (yesterday and today) and I don't understand why this problem look so simple (create CD with pre-defined installation source URI) but this difficult to do. I almost read every webpage I can google out. Any other hint you can give me or link that point me to go to? -- 锐业软服（国内业务） http://www.realss.cn Real SoftService http://www.realss.com 销售咨询(Sales Department): 0086 592 20 99987 (Chinese, German, English) 国际业务(International Sales): 0086 10 8460 6011 (German and English) 联系：厦门大学科技园，嘉庚二号楼6楼邮政：厦门大学2312号信箱（邮编361005）

1 0

Re: Re: [opensuse-autoinstall] [SLES 10] error using autoyast=device://cciss/c0d0p1/autoinst.xml (nested devices)
by Petteri Hakkarainen 15 Dec '06

15 Dec '06

> The use of : autoyast=device://cciss/c0d0p1/autoinst.xml failed (profile file not found error in Yast) Throw in three slashes with device, i.e. ...device:///cciss/... This notation works with floppies, anyway. Petteri -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

Re: Re: [opensuse-autoinstall] Re: [suse-autoinstall] SuSE 10.2 problems
by Petteri Hakkarainen 15 Dec '06

15 Dec '06

Uwe, > > >autoyast=http:/server/path/to/autoyast.xml to the append line on my > >> Isn't there one slash missing (http://)? >yes, there is one missing. >Did you find that in the documentation somewhere? No I did not find that in documentation, unless my thoughts would be considered as such (hopefully not, of course). Actually, I based my note on a conclusion that with a network protocol I've always seen two slashes to be used. If you do not have the server part, then three slahes (eg. autoyast=floppy:///path/autoinst.xml). Petteri -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

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

14 Dec '06

> Andrew Laden wrote: > > Does this work with DHCP? If you set your interfaces to configure > > themselves with dhcp, then will a simple /sbin/ifup $nic have them get > > an IP address also? (I am going back and forth with the idea of giving > > all my servers static IP's or letting them all dhcp. If I let them all > > dhcp, then I can basically use 1 xml for all my machines. If I want > > static addresses, then I have to build an xml per machine.) > > > > Yes, it works with DHCP or static, basically just uses what > AutoYaST configured the nic for at install time. I realize > now I probably just could have done a /etc/init.d/network > start || stop to achieve the same thing, I can't remember why > I made it more complex. It's been a while and just works for > us. And at this point DNS is up and configured so that works as well. > So then, I should be able to write a post-install script that /etc/init.d/network start Mount nfs share Copy file over Do chkconfig voodoo to get it to run when I want in the boot. /etc/init.d/network stop Is it that simple. (I'll let you know after I test) -Andrew -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

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

14 Dec '06

> > Uwe Gansert wrote: > > On Wednesday 13 December 2006 11:25, Uwe Gansert wrote: > > > > > >>> 1: Is the location paramter supported on Sles 9.3 for > init scripts. > >>> > >> yes > >> > > > > sorry, a network location is not supported for init-scripts on SLES9 > > > > > >>> 2: Is this section parsed and the files created at a time > when the > >>> network is up, so that NFS is available? > >>> > >> yes, that works fine (I just tried it again to be sure) > >> > > > > my test was wrong. A big sorry for that but I accidently raised the > > network up during my test by myself. > > At the time where the init-script must be fetched, the > network is down > > on SLES9. So a network <location> does not work. > > You can try <location>file:///...</location> for the > init-script and > > fetch the script with a post-script (network_needed=true) I did not > > try that but it should work > > > > > Like a lot of folks, I grew weary of XML changes and kind of > went the other route. I have a very simplistic path through > my code to generate bare bones XML, really 2, one for > patterns, one for packages, and tend to do almost all of the > post install heavy lifting in a perl script. > It's just easier for me to maintain that way, your mileage may vary. > > I also give allow my users to layer in as much bash as they'd > like in post, so they can tweak things like SSH keys and > firewall rules based on what type server they are building. > So here's how I did it: > Does this work with DHCP? If you set your interfaces to configure themselves with dhcp, then will a simple /sbin/ifup $nic have them get an IP address also? (I am going back and forth with the idea of giving all my servers static IP's or letting them all dhcp. If I let them all dhcp, then I can basically use 1 xml for all my machines. If I want static addresses, then I have to build an xml per machine.) -Andrew > <scripts> > <post-scripts config:type="list"> > <script> > <filename>final</filename> > <interpreter>perl</interpreter> > <source> > <![CDATA[ > #Find a nic to activate for %post install my $nic; > opendir(DIR,"/etc/sysconfig/network"); > foreach my $file (readdir(DIR)) { > next unless ($file =~ /^ifcfg-eth/); > print "Found $file -"; > $file =~ s/^ifcfg-//; > $nic = $file; > last; > } > closedir(DIR); > print " calling /sbin/ifup $nic!\n"; > system "/sbin/ifup $nic"; > open(NIC,">/tmp/nic"); > print NIC "$nic\n"; > close(NIC); > > # A whole bunch of PERL that does stuff like configure apt or > yum, install 3rd party software like OpenView, # Data > protector, bond production nics, setup NTP server based on > location, apply patches, etc. > # I own this code, system managers can't touch/see it. > # At this point you could wget/execute your final script(s). > > ]]> > </source> > </script> > <script> > <filename>final-user</filename> > <interpreter>shell</interpreter> > <source> > <![CDATA[ > > # Here's where I put in the system manager's BASH. They do > things like tweak firewall rules, install # SSH keys, etc. > Since APT/YUM are installed and pointed out our internal > depots, they manage all this # stuff using RPMs for the most part. > > if [ -r "/tmp/nic" ] > then > NIC=`cat /tmp/nic` > /sbin/ifdown $NIC > fi > ]]> > </source> > </script> > </post-scripts> > </scripts> > > Yes, most of this could be done with AutoYast, but I'd have > to track every RTG/DTD change, and that got tedious for me. > This also works on 9.X/OpenSuSE as well as SLES, so it's how > we do it all. Does it take a little longer than doing it all > in AutoYast? Maybe, but we tend to install once, run for a > LONG time, so it's a don't care for me. > > There's more than one way to do it, I work for HP (so we're > an HP shop needless to say :). I know this works on > ProLiants and lots of different HP desktops/laptops. > > Hope that helps, > > Lee > -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

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

14 Dec '06

> > On Wednesday 13 December 2006 11:25, Uwe Gansert wrote: > > > > 1: Is the location paramter supported on Sles 9.3 for > init scripts. > > > > yes > > sorry, a network location is not supported for init-scripts on SLES9 That makes more sense. Though I geuss the docs need a serious updating. > > > 2: Is this section parsed and the files created at a time > when the > > > network is up, so that NFS is available? > > > > yes, that works fine (I just tried it again to be sure) > > my test was wrong. A big sorry for that but I accidently > raised the network up during my test by myself. > At the time where the init-script must be fetched, the > network is down on SLES9. So a network <location> does not work. > You can try <location>file:///...</location> for the > init-script and fetch the script with a post-script > (network_needed=true) I did not try that but it should work > At that point I don't need an init_script, I can just drop the script into /var/adm/autoinstall/init.d, things should work. So can you answer the following 1: For which script types is the network available when the scripts are fetched? 2: Where is the file system located at the time that "post-script (network_needed=true) runs? Is it / or /mnt? 3: Is the network available at run time for chroot scripts (Either pre or post chroot) Thanks -Andrew -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] Init-scripts and nfs location
by Andrew Laden 14 Dec '06

14 Dec '06

Using autoyast on Sles 9 SP3. pxebooting using dhcp. Installing over NFS, Autoyast file served up via NFS, so I know that all works fine. Autoinstall all works fine. I get a fully installed ready to go system. So now I am trying to use/configure some init scripts. I have two of them. One I have placed the source in the xml, and the other via NFS. <scripts> <init-scripts config:type="list"> <script> <filename>init-zeus_bootstrap</filename> <interpreter>shell</interpreter> <location>nfs://192.168.1.1/vol/prod_LinuxInstall_grn_x/zeus/zeus_bootst rap</location> </script> <script> <filename>init-online-update.sh</filename> <interpreter>shell</interpreter> <source><![CDATA[ /usr/bin/online_update -s -u http://lx4-adm.grn.tudor.com/YOU -V > /var/tmp/online-update.out 2> /var/tmp/online-update.err ]]></source> </script> </init-scripts> </scripts> The one with source works fine. The other doesn't seem to work. So 1: Is the location paramter supported on Sles 9.3 for init scripts. 2: Is this section parsed and the files created at a time when the network is up, so that NFS is available? 3: Are there some log files that will help me. Since the script never runs, there is nothing in /var/adm/autoinstall. It looks like the script never gets copied from NFS and placed in there. Thanks -Andrew -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 3

RE: [opensuse-autoinstall] Network and file systems availability during user script levels
by Andrew Laden 13 Dec '06

13 Dec '06

To people who have gotten <location> references to work, can you email me 1: The relevent (scripts) portion of your autoyast.xml 2: A pxeboot config file. I am curious if tweaking the dhcp settings may help. I tried a boot with DHCP=0 and useDHCP=0, passing in HostIP, IPAddr, netmask, gateway and nameserver. Not only did the <location> script still not get installed, but the installation bombed out after reboot, as for some reason, post install it tries to install libcap from the nfs source. Since this works with DHCP, it seems that there must be some network up at some point after the reboot before autoyast is finished. Which goes back to my original question. At what script point are both the network and the filesystem available. (and where) > -----Original Message----- > From: Andrew Laden [mailto:Andrew.Laden@tudor.com] > Sent: Wednesday, December 13, 2006 12:46 PM > To: Jorge Alvarado; Rich; opensuse-autoinstall(a)opensuse.org > Subject: RE: [SPAM] - RE: [opensuse-autoinstall] Network and > file systems availability during user script levels - Email > found in subject > > Makes 2 of us. > > 2006-12-12 17:15:06 <3> linux(3497) [agent-curl] > CurlAgent.cc(Get):70 curl told us 7 > > Were you using static IP's or DHCP? > > > -----Original Message----- > > From: Jorge Alvarado [mailto:jalvarado@pervasive.com] > > Sent: Wednesday, December 13, 2006 12:09 PM > > To: Andrew Laden; Rich; opensuse-autoinstall(a)opensuse.org > > Subject: RE: [SPAM] - RE: [opensuse-autoinstall] Network and file > > systems availability during user script levels - Email found in > > subject > > > > yep, I couldn't get <location> to work for a post-install script. > > y2log had a curl rc 7 failure when retrieving the script. I > tried ftp > > and http, no luck. > > > > so, I would also be interested in any debug info...I may > revisit this > > later. > > > > -----Original Message----- > > From: Andrew Laden [mailto:Andrew.Laden@tudor.com] > > Sent: Wednesday, December 13, 2006 11:02 AM > > To: Rich; opensuse-autoinstall(a)opensuse.org > > Subject: [SPAM] - RE: [opensuse-autoinstall] Network and > file systems > > availability during user script levels - Email found in subject > > > > > > > Andrew Laden wrote: > > > > Heya all > > > > > > > > Since I cant seem to get the <location> option to work, > > and since in > > > > > > i can get <location> working just fine, using http://<ip>/path it > > > kinda "just worked" for me :) > > > > At least one other person responded that they didn't work. > > Maybe it is isolated to a particular network card or config? > > I don't know. These two errors lead me to think it's a > > network issue. (I did also try http, with the same lack of success.) > > > > 2006-12-12 14:54:10 <3> linux(3497) [bash] > > ShellCommand.cc(shellcommand):73 mount server reported tcp > > not available, falling back to udp > > 2006-12-12 14:54:10 <3> linux(3497) [bash] > > ShellCommand.cc(shellcommand):73 mount: RPC: Remote system > > error - Network is unreachable > > > > If there is any other debugging I can do, please let me know. > > > > > > > > > sles10, init scripts changed to run before the network is > > up. (which > > > > > > hmm. not according to > > > http://www.suse.com/~ug/autoyast_doc/createprofile.scripts.htm > > > l (and my > > > setup) : > > > > > > "Starting from SLES9, network is not available during > > > post-installation script execution. To access the > network, network > > > device has to be configured in the script. > > > > > > It is possible to execute the post scripts in an earlier > > phase while > > > the installation network is still up and before AutoYaST > configures > > > the system. To run network enabled post scripts, the > > boolean property > > > network_needed has to be set to true." > > > > > > this is about postinstall, not init scripts - which, in turn : > > > > > > "These scripts are executed during the initial boot process > > and after > > > YaST2 has finished. The final scripts are executed using > a special > > > init.d script which is executed only once. The final scripts are > > > executed toward the end of the boot process and after > > network has been > > > intialized." > > > > > > i have an init script which nicely downloads required > files, and it > > > works fine. > > > > Check the release notes for Changes between sles10 and sp1 > > http://www.suse.com/~ug/autoyast_changes_SLES10SP1.html > > [bug] init-script does not require network now > > > > -- > > To unsubscribe, e-mail: > opensuse-autoinstall+unsubscribe(a)opensuse.org > > For additional commands, e-mail: > > opensuse-autoinstall+help(a)opensuse.org > > > > > -- > To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org > For additional commands, e-mail: > opensuse-autoinstall+help(a)opensuse.org > > -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] Network and file systems availability during user script levels
by Andrew Laden 13 Dec '06

13 Dec '06

Heya all Since I cant seem to get the <location> option to work, and since in sles10, init scripts changed to run before the network is up. (which defeats the purpose I needed them for anyway) My current plan is to write a small script that I can place in the xml that will, at the appropriate time, mount the nfs share, copy the files into place, and then unmount. My question is what is the right phase to run in? The 6 possible phase are: Pre-install Chroot (pre chroot) Chroot (post chroot) Post install (network available) Post install (no network) Init Pre-install work work as the File system isnt there. Post install (no network) work work as I have no network. Init wont work, in sles 10 I wont have network. (there is another issue in that I want the script I am downloading to run in an rc level, so placing it duing init time would be too late anyway.) Is the network available during the chroot phases? My best option would be during the chroot (post chroot) phase, as I can drop the file in and then do a chkconfig -a to get them added in to the boot sequence. If that doesn't work, then where is the file system located in the post-install (network available) phase, so I can drop the files in myself. Thanks -Andrew -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

RE: [SPAM] - RE: [opensuse-autoinstall] Network and file systems availability during user script levels - Email found in subject
by Andrew Laden 13 Dec '06

13 Dec '06

Makes 2 of us. 2006-12-12 17:15:06 <3> linux(3497) [agent-curl] CurlAgent.cc(Get):70 curl told us 7 Were you using static IP's or DHCP? > -----Original Message----- > From: Jorge Alvarado [mailto:jalvarado@pervasive.com] > Sent: Wednesday, December 13, 2006 12:09 PM > To: Andrew Laden; Rich; opensuse-autoinstall(a)opensuse.org > Subject: RE: [SPAM] - RE: [opensuse-autoinstall] Network and > file systems availability during user script levels - Email > found in subject > > yep, I couldn't get <location> to work for a post-install > script. y2log had a curl rc 7 failure when retrieving the > script. I tried ftp and http, no luck. > > so, I would also be interested in any debug info...I may > revisit this later. > > -----Original Message----- > From: Andrew Laden [mailto:Andrew.Laden@tudor.com] > Sent: Wednesday, December 13, 2006 11:02 AM > To: Rich; opensuse-autoinstall(a)opensuse.org > Subject: [SPAM] - RE: [opensuse-autoinstall] Network and file > systems availability during user script levels - Email found > in subject > > > > Andrew Laden wrote: > > > Heya all > > > > > > Since I cant seem to get the <location> option to work, > and since in > > > > i can get <location> working just fine, using http://<ip>/path it > > kinda "just worked" for me :) > > At least one other person responded that they didn't work. > Maybe it is isolated to a particular network card or config? > I don't know. These two errors lead me to think it's a > network issue. (I did also try http, with the same lack of success.) > > 2006-12-12 14:54:10 <3> linux(3497) [bash] > ShellCommand.cc(shellcommand):73 mount server reported tcp > not available, falling back to udp > 2006-12-12 14:54:10 <3> linux(3497) [bash] > ShellCommand.cc(shellcommand):73 mount: RPC: Remote system > error - Network is unreachable > > If there is any other debugging I can do, please let me know. > > > > > > sles10, init scripts changed to run before the network is > up. (which > > > > hmm. not according to > > http://www.suse.com/~ug/autoyast_doc/createprofile.scripts.htm > > l (and my > > setup) : > > > > "Starting from SLES9, network is not available during > > post-installation script execution. To access the network, network > > device has to be configured in the script. > > > > It is possible to execute the post scripts in an earlier > phase while > > the installation network is still up and before AutoYaST configures > > the system. To run network enabled post scripts, the > boolean property > > network_needed has to be set to true." > > > > this is about postinstall, not init scripts - which, in turn : > > > > "These scripts are executed during the initial boot process > and after > > YaST2 has finished. The final scripts are executed using a special > > init.d script which is executed only once. The final scripts are > > executed toward the end of the boot process and after > network has been > > intialized." > > > > i have an init script which nicely downloads required files, and it > > works fine. > > Check the release notes for Changes between sles10 and sp1 > http://www.suse.com/~ug/autoyast_changes_SLES10SP1.html > [bug] init-script does not require network now > > -- > To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org > For additional commands, e-mail: > opensuse-autoinstall+help(a)opensuse.org > > -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

RE: [opensuse-autoinstall] Network and file systems availability during user script levels
by Andrew Laden 13 Dec '06

13 Dec '06

> Andrew Laden wrote: > > Heya all > > > > Since I cant seem to get the <location> option to work, and since in > > i can get <location> working just fine, using > http://<ip>/path it kinda "just worked" for me :) At least one other person responded that they didn't work. Maybe it is isolated to a particular network card or config? I don't know. These two errors lead me to think it's a network issue. (I did also try http, with the same lack of success.) 2006-12-12 14:54:10 <3> linux(3497) [bash] ShellCommand.cc(shellcommand):73 mount server reported tcp not available, falling back to udp 2006-12-12 14:54:10 <3> linux(3497) [bash] ShellCommand.cc(shellcommand):73 mount: RPC: Remote system error - Network is unreachable If there is any other debugging I can do, please let me know. > > > sles10, init scripts changed to run before the network is up. (which > > hmm. not according to > http://www.suse.com/~ug/autoyast_doc/createprofile.scripts.htm > l (and my > setup) : > > "Starting from SLES9, network is not available during > post-installation script execution. To access the network, > network device has to be configured in the script. > > It is possible to execute the post scripts in an earlier > phase while the installation network is still up and before > AutoYaST configures the system. To run network enabled post > scripts, the boolean property network_needed has to be set to true." > > this is about postinstall, not init scripts - which, in turn : > > "These scripts are executed during the initial boot process and after > YaST2 has finished. The final scripts are executed using a > special init.d script which is executed only once. The final > scripts are executed toward the end of the boot process and > after network has been intialized." > > i have an init script which nicely downloads required files, > and it works fine. Check the release notes for Changes between sles10 and sp1 http://www.suse.com/~ug/autoyast_changes_SLES10SP1.html [bug] init-script does not require network now -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

RE: [SPAM] - RE: [opensuse-autoinstall] Network and file systems availability during user script levels - Email found in subject
by Jorge Alvarado 13 Dec '06

13 Dec '06

yep, I couldn't get <location> to work for a post-install script. y2log had a curl rc 7 failure when retrieving the script. I tried ftp and http, no luck. so, I would also be interested in any debug info...I may revisit this later. -----Original Message----- From: Andrew Laden [mailto:Andrew.Laden@tudor.com] Sent: Wednesday, December 13, 2006 11:02 AM To: Rich; opensuse-autoinstall(a)opensuse.org Subject: [SPAM] - RE: [opensuse-autoinstall] Network and file systems availability during user script levels - Email found in subject > Andrew Laden wrote: > > Heya all > > > > Since I cant seem to get the <location> option to work, and since in > > i can get <location> working just fine, using > http://<ip>/path it kinda "just worked" for me :) At least one other person responded that they didn't work. Maybe it is isolated to a particular network card or config? I don't know. These two errors lead me to think it's a network issue. (I did also try http, with the same lack of success.) 2006-12-12 14:54:10 <3> linux(3497) [bash] ShellCommand.cc(shellcommand):73 mount server reported tcp not available, falling back to udp 2006-12-12 14:54:10 <3> linux(3497) [bash] ShellCommand.cc(shellcommand):73 mount: RPC: Remote system error - Network is unreachable If there is any other debugging I can do, please let me know. > > > sles10, init scripts changed to run before the network is up. (which > > hmm. not according to > http://www.suse.com/~ug/autoyast_doc/createprofile.scripts.htm > l (and my > setup) : > > "Starting from SLES9, network is not available during > post-installation script execution. To access the network, > network device has to be configured in the script. > > It is possible to execute the post scripts in an earlier > phase while the installation network is still up and before > AutoYaST configures the system. To run network enabled post > scripts, the boolean property network_needed has to be set to true." > > this is about postinstall, not init scripts - which, in turn : > > "These scripts are executed during the initial boot process and after > YaST2 has finished. The final scripts are executed using a > special init.d script which is executed only once. The final > scripts are executed toward the end of the boot process and > after network has been intialized." > > i have an init script which nicely downloads required files, > and it works fine. Check the release notes for Changes between sles10 and sp1 http://www.suse.com/~ug/autoyast_changes_SLES10SP1.html [bug] init-script does not require network now -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] autoyast with /dev/disk/by-path not working
by Hartmut Gottwald 13 Dec '06

13 Dec '06

Hello list, using /dev/disk/by-path syntax in autoyast control file does not work but the equivalent /dev/sd? devices do. Is this a known issue and a fix available? Need by-path syntax to avoid trashing other devices during autoinstall in case one of the system disks failed and is missing. <drive>  <device>/dev/sdb</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> Thanks, Hartmut -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 3

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

13 Dec '06

> On Tuesday 12 December 2006 21:25, Andrew Laden wrote: > > > The one with source works fine. The other doesn't seem to work. So > > 1: Is the location paramter supported on Sles 9.3 for init scripts. > > yes > > > 2: Is this section parsed and the files created at a time when the > > network is up, so that NFS is available? > > yes, that works fine (I just tried it again to be sure) > Because you are doing a network installation, it should work > for you too. > At the moment I can not say why it does not work for you. > It works fine here. > Any ideas as to what else I can do to debug? Is there a way to pause the autoyast setup at the point when it should be fetching the files so I can see why it cant detect a network? I sent out the log in a previous email. Thanks -Andrew -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] [SLES 10] error using autoyast=device://cciss/c0d0p1/autoinst.xml (nested devices)
by Sylvain Le Courtois (alplog) 13 Dec '06

13 Dec '06

Hello All, I send this message to give information about a bug I encountered using autoyast SLES 10 and Profilant HP servers. The HP Smart array raid controllers creates "nested" devices in /dev : cciss/c0d0p1 is the first partition of the first logical drive of the first controller The use of : autoyast=device://cciss/c0d0p1/autoinst.xml failed (profile file not found error in Yast) After some time consuming investigations, I found these lines in the y2log file : 006-07-17 17:18:06 <1> 192.168.0.43(3346) [YCP] autoinstall/io.ycp:227 nested device found 2006-07-17 17:18:06 <1> 192.168.0.43(3346) [YCP] autoinstall/io.ycp:232 Host=cciss/ Path=c0d0p1/autoinst/autoinst.xml 2006-07-17 17:18:06 <1> 192.168.0.43(3346) [YCP] autoinstall/io.ycp:227 nested device found 2006-07-17 17:18:06 <1> 192.168.0.43(3346) [YCP] autoinstall/io.ycp:232 Host=cciss//c0d0p1 Path=autoinst/autoinst.xml 2006-07-17 17:18:06 <1> 192.168.0.43(3346) [agent-system] SystemAgent.cc(Read):544 Can't access directory '/dev/cciss//c0d0p1': Not a directory' 2006-07-17 17:18:06 <3> 192.168.0.43(3346) [bash] ShellCommand.cc(shellcommand):78 /bin/cp: cannot stat `/tmp/YaST2-03346-Op2jd3/tmp_mountautoinst/ autoinst.xml': No such file or directory 2006-07-17 17:18:06 <3> 192.168.0.43(3346) [YCP] autoinstall/io.ycp:243 file /tmp/YaST2-03346-Op2jd3/tmp_mountautoinst/autoinst.xml can't be found The guilty lines are located in the Get function of the io.ycp module. It seems that there is some lines of code to take care of "nested devices" but it does not work. /* sometimes we have devices like /dev/cciss/c1d0p5 those "nested" devices will be catched here as long as we find a directory where we expect a device, we cut down the Path and enhance the Host (device name) */ while( SCR::Read( .target.dir, "/dev/"+Host ) != nil ) { y2milestone("nested device found"); list<string> l = splitstring( Path, "/" ); Host = Host + "/" + l[0]:""; l = remove(l,0); Path = mergestring(l,"/"); y2milestone("Host=%1 Path=%2",Host,Path); } // catching nested devices done autoyast=device://cciss/c0d0p1///autoinst.xml works as a workaround. Hoping that this information can be useful to other happy SuSE administrators. Regards, -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

RE: [SPAM] - [opensuse-autoinstall] Init-scripts and nfs location - Email found in subject
by Andrew Laden 12 Dec '06

12 Dec '06

Not a whole lotta help... 2006-12-12 14:54:10 <1> linux(3497) [YCP] AutoinstScripts.ycp:406 Writing init script into /var/adm/autoinstall/init.d/init-zeus_bootstrap 2006-12-12 14:54:10 <3> linux(3497) [bash] ShellCommand.cc(shellcommand):73 mount server reported tcp not available, falling back to udp 2006-12-12 14:54:10 <3> linux(3497) [bash] ShellCommand.cc(shellcommand):73 mount: RPC: Remote system error - Network is unreachable 2006-12-12 14:54:10 <2> linux(3497) [YCP] autoinstall/io.ycp:146 Mount failed 2006-12-12 14:54:10 <3> linux(3497) [YCP] AutoinstScripts.ycp:412 script nfs://10.2.42.65/vol/prod_LinuxInstall_grn_x/zeus/zeus_bootstrap could not be retrieved Except it seems that the network is not available. Which make me wonder why the option is there..... > -----Original Message----- > From: Jorge Alvarado [mailto:jalvarado@pervasive.com] > Sent: Tuesday, December 12, 2006 3:35 PM > To: Andrew Laden; opensuse-autoinstall(a)opensuse.org > Subject: RE: [SPAM] - [opensuse-autoinstall] Init-scripts and > nfs location - Email found in subject > > look at /var/log/YaST2/y2log. > I also could not get <location> to work. first I thought is > was my ftp setup, but curl continued to return a 7 (failed to > connect to host). The y2log should give some clue. I was > using an http location reference, tried ftp - no go. Take > the same reference after the reboot and curl works. Not > clear why if fails during auto install. > > I went with the <source> reference...had to move on. > > -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

RE: [SPAM] - [opensuse-autoinstall] Init-scripts and nfs location - Email found in subject
by Jorge Alvarado 12 Dec '06

12 Dec '06

look at /var/log/YaST2/y2log. I also could not get <location> to work. first I thought is was my ftp setup, but curl continued to return a 7 (failed to connect to host). The y2log should give some clue. I was using an http location reference, tried ftp - no go. Take the same reference after the reboot and curl works. Not clear why if fails during auto install. I went with the <source> reference...had to move on. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] How to get the right kernel module package installed
by Oliver Schweikert 12 Dec '06

12 Dec '06

Hello all, i have built kernel module packages (KMP) as described at http://www.suse.de/~agruen/KMPM/KernelModulePackagesManual-CODE10.pdf: MODULE-kmp-default MODULE-kmp-smp MODULE-kmp-debug ... Each package provides the capability "MODULE-kmp". When i install another package, which depends on "MODULE-kmp", yast does not choose the right one - in my case MODULE-default, because the default kernel is installed - , but MODULE-debug and installs the corresponding kernel package, too. In /var/log/Yast2/y2log i cannot found any hit, why yast makes this decision. All i can see is, that each of the KMP gets recognized, to provide "MODULE-kmp", which is correct. Has anybody an idea? Regards Oliver -- Oliver Schweikert Software Development Horiba Europe Automation Division GmbH Zabergäustr. 3 73765 Neuhausen Tel: +49 - (0)7158-933-413 Fax: +49 - (0)7158-933-613 Email: osw(a)head.de -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] Running chroot-script from cd/dvd medium
by Thomas Glanzmann 12 Dec '06

12 Dec '06

Hello, I try to run a chroot-script from the install cd/dvd medium using autoyast. Running it via http is easy. The only reference[1] I found using google is for post-install script. The only error message I see is: (none):/var/adm/autoinstall # find . -type f ./cache/installedSystem.xml ./logs/chroot-scripts.log (none):/var/adm/autoinstall # cat logs/chroot-scripts.log /bin/sh: /var/adm/autoinstall/scripts/chroot-scripts: No such file or directory I also found in the y2log: 2006-12-11 07:50:26 <3> linux(5877) [bash] ShellCommand.cc(shellcommand):78 cp: cannot stat `/autoyast/chroot.sh': No such file or directory 2006-12-11 07:50:26 <3> linux(5877) [bash] ShellCommand.cc(shellcommand):78 cp: cannot stat `/tmp/YaST2-02679-C4nfqw/tmp_mount//autoyast/chroot.sh': No such file or directory My entry in the autoyast.xml is: <scripts> <chroot-scripts config:type="list"> <script> <chrooted config:type="boolean">true</chrooted> <filename>chroot.sh</filename> <location>file:///autoyast/chroot.sh</location> <interpreter>shell</interpreter> </script> </chroot-scripts> </scripts> [1] http://lists.suse.com/archive/suse-autoinstall/2005-Nov/0064.html Thomas -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 2

[opensuse-autoinstall] Re: [suse-autoinstall] SuSE 10.2 problems
by Lonni J Friedman 11 Dec '06

11 Dec '06

On 12/7/06, Lonni J Friedman <netllama(a)gmail.com> wrote: > On 12/7/06, Uwe Gansert <ug(a)suse.de> wrote: > > On Wednesday 06 December 2006 19:20, Lonni J Friedman wrote: > > > I have to ask. Why is autoyast > > > being reinvented from scratch with every single release? Every single > > > release has non-trivial changes which lead to non-ending pain & > > > > Since 10.0 (and that was the release I took over autoyast) there was just > > one incompatibility (selections -> patterns). > > Everything else should be still compatible. The change from DTD to RNG is no > > icompatibility. It does not matter for your profile if RNG files are used > > or DTD files are used to check the syntax. > > > > > suffering. Is it too much to expect that a working autoyast.xml from > > > one release continue to work, or at least not fail fatally, in the > > > next release? > > > > no, it's not. > > If you detect such an incompatibility that is not documented by me, feel > > free to open a bugreport or ask here on the list. > > I don't know a lot about autoyast in the pre 10.0 time but I try to keep > > compatibility as high as possible. > > I'm sorry if you had compatibility issues in the past but for the future, > > let me know if you have such problems. And let me know as soon as you > > discover such a problem please. > > I just went to setup 10.2 using the autoyast file that works for > SLED10, and it blew up with bad/invalid patterns. Amongst other > things, basis-devel seems to have been renamed devel_basis, and > kernel-devel was renamed devel_kernel. > > This is the stuff i'm referring to. I shouldn't have to update the > pattern names every time there's a new release. Sadly, there are more problems. After fixing my autoyast.xml file, now the installation bombs out much earlier (which admittedly suggests that I did something wrong). Now I just got prompted to "Make sure that CD number 1i s in your drive". On Alt-F3, I see a bunch of modules getting insmodded, and then: Looking for a openSUSE CD... disk: trying to mount /dev/hda disk: /dev/hda: not a openSUSE install medium Automatic setup not possible I've got an info and autoyast.xml files inside the initrd. Thinking perhaps that support had changed such that yast now assumes that the install 'media' is always going to be in the same place as the autoyast.xml file, I tried putting the autoyast.xml file on the web server where the SuSE-10.2 installation tree is located. I added autoyast=http:/server/path/to/autoyast.xml to the append line on my pxeboot server, and now I get a completely different failure. The installer attempts to get a dhcp lease, and fails nearly instantaneously (it waits perhaps 2 seconds at most): Looking for anetwork server... Trying to activate eth0 Setting up localhost..done Sending DHCP request to eth0... no/incomplete answer. Automatic setup not possible At which point I get dumped to the manual installation dialogue, where I have no problems getting a dhcp lease and performing the installation over the network without any problems. Something is broken somewhere. It might be user error, but the fact that just dropping in an autoyast.xml from an older version doesn't work seems like a pretty huge regression. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ L. Friedman netllama(a)gmail.com LlamaLand http://netllama.linux-sxs.org -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 3

[opensuse-autoinstall] SLES 9 VLAN (802.1q)
by Valentin Eberhardt 08 Dec '06

08 Dec '06

I've been looking through the documentation and in the archive for the configuration of network devices in trunked VLANs (802.1q) and found nothing. Is there though a way to configure in autoyast? Thanks, Valentin Eberhardt -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] Re: [suse-autoinstall] Please include the right DTDs in SuSE 10.2
by Lonni J Friedman 07 Dec '06

07 Dec '06

On 12/6/06, Uwe Gansert <ug(a)suse.de> wrote: > On Tuesday 05 December 2006 21:34, David Werner wrote: > > > Today I tried an Installation of RC1 of 10.2. > > To me it looks like that the DTDs of 10.2 > > currently (RC1) do not include: > > autoyast no longer uses DTDs but RNG files (they are created from RNC files > which are human readable). > http://www.suse.de/~ug/autoyast_doc/Profile.DTD.html > The RNG files are in /usr/share/YaST2/schema/autoyast/rng > They are a lot better than the DTDs were but I'm afraid, they are still not > complete. > I hope we will have them complete on SLES10 SP1 At the risk of being labeled a troll, I have to ask. Why is autoyast being reinvented from scratch with every single release? Every single release has non-trivial changes which lead to non-ending pain & suffering. Is it too much to expect that a working autoyast.xml from one release continue to work, or at least not fail fatally, in the next release? Everytime a new SuSE/SLE* release comes out I end up spending 1+ hours having to debug everything that got broken/changed in autoyast from the previous release. With Redhat/FC, I just drop in the kickstart file from the previous release and everything just works(tm). I yearn for the day when SuSE can get this figured out. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ L. Friedman netllama(a)gmail.com LlamaLand http://netllama.linux-sxs.org -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 2

[opensuse-autoinstall] post script location tag
by Jorge Alvarado 07 Dec '06

07 Dec '06

Looks like ftp is causing my gas. Autoyast (via curl) seems to be making an ftp call to retrieve the post script. After the box boots, the "curl http:..." works fine. I tried a curl w/ftp and it fails, just as during post install, get curl: (7). Anyway, working on fixing ftp. > <location>http://196.168.0.68/autoy/SuSE9Post.sh</location> -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

Installing from locally attached Raid?
by Frank Steiner 07 Dec '06

07 Dec '06

Hi, is it possible to use a locally attached raid storage as installation source for autoyast? I.e., boot our NFS server (that usually serves the autoyast install repository via NFS to the clients) from a second dhcp/tftp server, but then let it mount it's raid locally and install from there. So sth. like "install=local://..." or whatever. Assuming the neccessary modules are preloaded. Is that possible? 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 7

[opensuse-autoinstall] post script location tag
by Jorge Alvarado 06 Dec '06

06 Dec '06

> I'm having problems locating a post script file. Attempting to auto install suse 9. > The post script is; > <scripts> > <post-scripts config:type="list"> > <script> > <debug config:type="boolean">true</debug> > <feedback config:type="boolean">false</feedback> > <interpreter>shell</interpreter> > <location>http://196.168.0.68/autoy/SuSE9Post.sh</location> > <network_needed config:type="boolean">false</network_needed> > </script> > </post-scripts> > </scripts> > > The yast error log shows; > 2006-12-05 17:36:14 <3> linux(1518) [YCP] autoinstall/io.ycp:69 Can't find URL: http://196.168.0.68/autoy/SuSE9Post.sh > 2006-12-05 17:36:14 <3> linux(1518) [YCP] AutoinstScripts.ycp:445 script http://196.168.0.68/autoy/SuSE9Post.sh could not be retrieved > > On this box, 196.168.0.68. the htdocs has an autoy directory, and within that the shell script resides. has rw-r--r-- permissions, owned by root. > /srv/www/htdocs/autoy > > any clue what is up here? > > thanks, > Jorge -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] [ml-admin] Migration complete
by Henne Vogelsang 06 Dec '06

06 Dec '06

Hi, the migration is done now. Have a lot of fun. Henne -- ml-admin -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

Problems using a HTTP Repository and LVM Partitioning
by Marko Karg 04 Dec '06

04 Dec '06

Hi all, I am experiencing problems while the installation of SLES 9 with the following setup: A HTTP Repository holds the complete installation media and the autoyast xml control files. Booting the machine which is about to be installed works as far as it concerns reading the control file, partitioning the harddisk and starting the installation. The partition table looks as the following: /boot 100M /swap memory-dependant LVM containing / /usr /var /opt /srv The installation stops with this error message: ERROR(Media:Unknown error in subsystem)[/var/adm/YaST/InstSrcManager/IS_CACHE_0x00000002/MEDIA/media.2] If I do not use LVM the installation proceeds smoothly. Any help is appreciated! Kind regards Marko

2 2

AutoYaST - Not skipping second stage (SuSE 10.1)?
by Justin McCormick 04 Dec '06

04 Dec '06

Hello folks! I'm developing a provisioning system, and am trying to fully automate the install of SuSE as a part of the system.... I need the install to be 100% automated, from booting up, doing the install, and then booting the system. Needs to be completely a hands off install.... and I've setup a very basic config file as a test, but for some reason it does not skip the second stage of the install. I've searched around to no avail, maybe I am missing something? A second thing, unrelated to the second stage of the install that I've noticed, is for some reason when the first stage of the install finishes, the system reboots but it seems to hang on trying to boot. Never loads a kernel, never says anything at all actually after the initial BIOS screens. Could that be an issue with not specifying or setting up a bootloader in the config file? Or any other ideas? Any help would be greatly appreciated! - Justin (jlmccorm at gmail dot com) Below is the autoyast.xml file I'm using: (For SuSE 10.1) <?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"> <general> <signature-handling> <accept_unsigned_file config:type="boolean">true</accept_unsigned_file> <accept_file_without_checksum config:type="boolean">true</accept_file_without_checksum> <accept_verification_failed config:type="boolean">true</accept_verification_failed> <accept_unknown_gpg_key config:type="boolean">true</accept_unknown_gpg_key> </signature-handling> <mode> <halt config:type="boolean">false</halt> <onfirm config:type="boolean">false</confirm> <second_stage config:type="boolean">false</second_stage> </mode> </general> <partitioning config:type="list"> <drive> <use>all</use> </drive> </partitioning> <software> <base>Minimal</base> <packages config:type="list"> <package>tftp</package> </packages> </software> <networking> <dns> <dhcp_hostname config:type="boolean">true</dhcp_hostname> <dhcp_resolv config:type="boolean">true</dhcp_resolv> <domain>local</domain> <hostname>linux</hostname> </dns> </networking> <users config:type="list"> <user> <encrypted config:type="boolean">false</encrypted> <username>root</username> <user_password>myunsafeplaintextpw</user_password> <forename/> <surname/> </user> <user> <encrypted config:type="boolean">false</encrypted> <username>myuser</username> <user_password>myotherunsafepw</user_password> <forename/> <surname/> </user> </users> <scripts> <chroot-scripts config:type="list"> <script> <chrooted config:type="boolean">true</chrooted> <filename>kspost</filename> <interpreter>shell</interpreter> <source> <![CDATA[ #/bin/sh echo "get finished_suse_01-00-02-55-57-1b-bf" | /usr/bin/tftp 192.168.0.3 & sleep 1 killall tftp ]]> </source> </script> </chroot-scripts> </scripts> </profile>

2 1

SLES10: console_shutdown
by Bernhard Duebi 01 Dec '06

01 Dec '06

Hello, it's me again. I have the following line in my autoinst.xml <console_shutdown>ignore</console_shutdown> But in /etc/inittab I find the following line ca::ctrlaltdel:/sbin/shutdown -r -t 4 now With SLES9 this was no problem. Any idea what's wrong ? Sincerely Bernhard

2 3

lvm on top of raid?
by Jochen Schaefer 01 Dec '06

01 Dec '06

Hi list, could somebody help out with the attached xml-snippet please? I can't find the error in the partitioning section. Any help is greatly appreciated. Thanks, Jochen -- Jochen Schaefer Senior Consultant Integrated Services Novell GmbH Mobil: +49(0)1735876969 E-mail: jschaef(a)novell.com Address: Duesseldorf , 40470, Germany Noerdlicher Zubringer 9-11 http://www.novell.com

2 4