December 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

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