openSUSE Autoinstall April 2002

autoinstall@lists.opensuse.org

10 participants
14 discussions

[suse-autoinstall] full solution: fetching the autoyast control.xml via NFS

by Hella.Breitkopf＠varetis.de

Problem was: Using a nfs source for the control.xml file didn't work as described. ** Doesn't work (as input to the boot prompt): linux autoyast=nfs://ip-of-nfs1:/path/control.xml install=nfs://ip-nfs2:/other-path/suse8.0 (one will be asked for a valid path to a control file, later) ** Doesn't work , either: linux autoyast=nfs://ip-of-nfs1/path/control.xml install=nfs://ip-nfs2:/other-path/suse8.0 (no colon after nfs-server1's ip in the autoyast statement) Anas Nashif <nashif(a)suse.de> gave the tip: >Try without the : in the URL <snip> > >So the URL should look like this: > install=nfs://123.123.123.111/installs/suse8.0 Ah - the trick is to leave out *both* times the colon .. If one of these lines on the boot prompt, it works: ** Works: linux autoyast=nfs://ip-nfs1/path/control.xml install=nfs://ip-nfs2/other-path/suse8.0 ** Works, too: linux autoyast=http://ip-www/control.xml install=nfs://ip-nfs2:/other-path/suse8.0 (Here the colon after the nfs-server ip doesn't hurt in the install statement) Anis Nashif mentions further: > This is a known issue and it was fixed and > an updated version will be available for nfs installs soon. Is there a open list of "known issues" ? (I've got some more small issues, but if they are known, I don't want to bother the list with them.) And - soon is approximatly when? (Should I start to play with autoinstall boot CDs with the old version or is it worth to wait for the new version?) Regards, Hella

20 years

fetching the autoyast control.xml via NFS

by Hella.Breitkopf＠varetis.de

Hi List, as everybody else, I'm playing with this nice new toy^h^h^h tool. I like it very much - but sometimes one runs still in some small problems: Fetching the file as "autoinst.xml" from floppy works fine, and typing an http path to the control file to the boot prompt, too : autoyast=http://123.123.123.231/1.xml works as advertised. But if I try to give a NFS path for the control file like this autoyast=nfs://123.123.123.231:/autoinstall/1.xml yast doesn't find the control file on the first try and asks for it later in the installation again. When I fill out that GUI request with the same data, it *does* work. (The directory is exported to everybody and the file is readable by everybody.) The boot prompt takes an NFS installation source without further questions: install=nfs://123.123.123.111:/installs/suse8.0 Anybody who does fetch the contol file via NFS successfully ? Other experiences ? Best regards, Hella -- -- -- -- -- hella breitkopf unix + network administrator varetis AG

20 years

Further plans ...

by Marcel Ritter

Hi there! I did a couple of test installations with SuSE 8.0 and the new autoinstall - works fine so far. But I'd like to have some more possibilities to change settings Are there plans to implement new YaST2 modules for autoinst configuration? I currently work with kxmledit, but in some cases it's hard to see where you're going ... Ciao, Marcel

20 years

Re: [suse-autoinstall] Anyone using AutoYast2 with PXE?

by Anas Nashif

* Marcel Ritter <Marcel.Ritter(a)rrze.uni-erlangen.de> [Apr 22. 2002 18:22]: > > > On Mon, 22 Apr 2002, Anas Nashif wrote: > > > * Marcel Ritter <Marcel.Ritter(a)rrze.uni-erlangen.de> [Apr 22. 2002 18:12]: > > > > > > Why do you need a floppy image with PXE? > > > > > > To boot with all modules you need to use the images available in > > > > > > suse/images/boot on the first CD. > > > > > > > > > > That's exactly what I missed :-) If I recall correctly on SuSE 7.3 I had > > > > > to hack it myself - if it's already done on SuSE 8.0 -> great :-) > > > > Not really, these files has always been there :-) That is exactly what > > > > we need to create the bootable CDs... > > > > > > If you say so :-) > > > > > > ... first installation is running - one little problem: > > > > > > How to I load aic7xxx_old instead of aic7xxx (which causes some trouble > > > with my controller)? I had a look at the docu but I couldn't find anything > > > similar to the ALICE insmod list. > > You can either add insmod=aic7xxx_old on the command line or have > > a linuxrc conf file (info) on the boot media with the keyword insmod > > just as it was possible with earlier versions. > > I see - so it's the same as it was with ALICE. Not exactly, it is the same as it was with autoyast1. There is another, still untested way to load modules.. In the bootloader directive of the control file you can add a list of initrd modules, i.e. <bootloader> ... <initrd_modules config:type="list"> <initrd_module>aic7xxx_old</initrd_module> </initrd_modules> ... </bootloader> The problem is, by the time this is evaluated, aic7xxx is already loaded... Another way to do it is to use the pre-install scripts, by using rmmod aic7xxx insmod aic7xxx_old I am not 100% sure this will work though. Anas > > > See http://www.suse.de/~nashif/autoinstall/linuxrc.html > > for more information. > > > > Anas Nashif > > Thanx again, > Marcel -- Anas Nashif <nashif(a)suse.com>, SuSE Linux AG Montreal (Laval), Canada

20 years

Re: [suse-autoinstall] Anyone using AutoYast2 with PXE?

by Marcel Ritter

> > > Why do you need a floppy image with PXE? > > > To boot with all modules you need to use the images available in > > > suse/images/boot on the first CD. > > > > That's exactly what I missed :-) If I recall correctly on SuSE 7.3 I had > > to hack it myself - if it's already done on SuSE 8.0 -> great :-) > Not really, these files has always been there :-) That is exactly what > we need to create the bootable CDs... If you say so :-) ... first installation is running - one little problem: How to I load aic7xxx_old instead of aic7xxx (which causes some trouble with my controller)? I had a look at the docu but I couldn't find anything similar to the ALICE insmod list. > Anas > -- > Anas Nashif <nashif(a)suse.com>, SuSE Linux AG > Montreal (Laval), Canada Ciao, Marcel

20 years

Anyone using AutoYast2 with PXE?

by Marcel Ritter

Hi there! Did anyone out there already succeed in using AutoYast2 with PXE network boot? I'd like to have a big "floppy image" that contains all available modules - but at the moment I have no real idea how to build it from the available disks (bootdisk,modules{1,2,3} ...) Perhaps someone has already done this ... ... if not I'll have a closer look ... Ciao, Marcel

20 years

SuSE 8.0 & CUPS

by paedi＠gmxpro.net

Hello, I have a big problem with the CUPS-Modul of Yast. I installed tow times SuSE 8.0 today, all worked fine. But if I changed from LPD to CUPS with YAST2, I becomed some problemes. SuSEconfig with LPD need a minute for all. But SuSEconfig with CUPS need a minute for each task of SuSEconfig, that means more then 10 minutes. I don't understand this. Why is this so? Thanks for help Patrick

20 years, 1 month

profile questions

by Rose Lopez Carreno

Hello Anas, I am back to SuSE 8.0 now. I'm not sure the mailing list is working yet but I will copy this to suse-autoinstall(a)suse.com and see what happens. I installed 8.0, ran the Configuration System, and generated a profile that I copied to a floppy as autoinst.xml. When I use that file to autoinstall 8.0, the autoinstall seems to work, i.e. I do not have to enter the language or other configuration queries, however, I get a partitioning error indicating /dev/sda3 cannot be mounted to /mnt/. Here is the section on partitioning. I have tried varying the partitions and cannot make this work. <partitioning config:type="list" > <drive> <device>/dev/sda</device> <partitions config:type="list" > <partition> <crypt_fs config:type="boolean" >false</crypt_fs> <crypt_key></crypt_key> <filesystem_id config:type="integer" >131</filesystem_id> <format config:type="boolean" >false</format> <mount>/boot</mount> <size>20MB</size> <type>Linux native</type> </partition> <partition> <crypt_fs config:type="boolean" >false</crypt_fs> <crypt_key></crypt_key> <filesystem_id config:type="integer" >130</filesystem_id> <format config:type="boolean" >false</format> <mount></mount> <size>300MB</size> <type>Linux swap</type> </partition> <partition> <crypt_fs config:type="boolean" >false</crypt_fs> <crypt_key></crypt_key> <filesystem_id config:type="integer" >131</filesystem_id> <format config:type="boolean" >false</format> <mount>/</mount> <size>max</size> <type>Linux native</type> </partition> </partitions> <use>all</use> </drive> </partitioning> Is there a more detailed description of how this should look, or how any of the entries in the autoinst.xml file should look. The AutoYast2 document section I. Profile Element Reference lists the entries, but there is not much detail. I noticed also that I cannot abort the installation when the error occurs. If I select abort in the error window, the installation continues. I must select continue and later hit the abort installation button. Thank you, Rose Lopez Carreno Servers Software Development Phone: (919) 543-9284 8-441-9284 (tieline) Email=rlopezca(a)us.ibm.com Anas Nashif <nashif(a)suse.de> To: Rose Lopez Carreno/Raleigh/IBM@IBMUS cc: 04/01/2002 09:13 Subject: Re: Config System/mailing list questions AM Hello, * Rose Lopez Carreno <rlopezca(a)us.ibm.com> [Apr 01. 2002 15:45]: > Hello Anas, I have a few questions for you regarding the Configuration > System and the mailing list. > > I invoke the Configuration System via /sbin/yast2 autoyast > I try to create a single system configuration. I elect to configure a new > profile, configure the options, > but then I cannot save the file. I receive the error: Warning: Error > occured while saving the file. > I tried changing the profile and class directories but that did not help. > Are you trying to run autoyast as normal user by any chance? If yes, make sure that the variable REPOSITORY in /etc/sysconfig/autoinstall is set to a writable direcotry by normal users. It is recommended to run autoyast as root. > Regarding the mailing list, I added my email address to the > suse-autoinstall mailing list. > I expected to see mail by now or perhaps not that active. To post a > message do I just > send mail to suse-autoinstall(a)suse.com? I can read the archives. > Still not active but hopfully with the launch of 8.0 it will be. Yes, please send any emails to suse-autoinstall(a)suse.com. Regards, Anas > Thank you. > > > Rose Lopez Carreno > Servers Software Development > Phone: (919) 543-9284 > 8-441-9284 (tieline) > Email=rlopezca(a)us.ibm.com -- Anas Nashif <nashif(a)suse.com>, SuSE Linux AG Montreal (Laval), Canada Tel./Fax: +1 450 978 2382

20 years, 1 month

segmentation fault error on automated installation

by Miguel Gómez

Hi, I've set up an automated installation environment for SuSE Linux 7.3. The problem is that on certain computers the installation process can't finish due to a "segmentation fault" error during the installation of the kernel. I'm installing SuSE's default 2.4 kernel, that should be suitable for the type of computers I'm working with. ¿Does anybody know what causes this problem and how can I fix it? Thanks. Regards, Miguel Gómez Rodríguez gomez(a)dit.upm.es

20 years, 1 month

by Robert Silge

I can't help but feel that Yast2 is not doing all it can. I installed over FTP, but can't change my source media. The FTP IP address times out, and if I try the NFS server address it tells me that I'm trying to connect to a different version than what my machine says it has. I installed from ftp.suse.com/pub/suse/i386/current/suse so maybe the current vs 7.3 difference is messing it up? What do I need to change to make this work? Thanks, -Rob

20 years, 1 month

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall April 2002