January 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

/dev/fd0 unknown fs type when trying to install from floppy
by Gunreben, Peter (Peter) 21 Jan '04

21 Jan '04

Hi, I'm currently trying to use autoyast (SuSE 9.0) for the first time. After creating the autoinst.xml, I've created a boot floppy and the modules1 floppy disk via yast2. Hence, I've copied the autoinst.xml into the root directory of the Modules1 floppy. When booting from floppy, I've selected the Installation and used "autoyast=floppy" in the boot parameters. Everything works fine until the installation procedure tries to find the configuration file. In console 3 it reports ... Hardware probing finished. floppy: /dev/fd0 /dev/fd0: unknown fs type got info from cmdline Automatic setup is not possible. ... As said before, this floppy is the Modules1 disk and was created using yast2. However, I can mount this floppy on another computer without any problems and I can read the content. Any ideas? Peter.

2 1

Auto-Update
by discip＠pjm.com 21 Jan '04

21 Jan '04

While I am familiar with the autoinstall procedures, I thought I had come across something about AutoYast being able to push out new packages to managed hosts. Does anyone have any information about this? Thanks, Paul

2 1

Post-install script question
by Mouncef_Belcaid＠blm.gov 21 Jan '04

21 Jan '04

Hi everyone, I was wondering if anyone has a sample post install script that will load a NIC module (bcm5700) and configure it to start on boot using DHCP. The DHCP server will be providing the hostname, domain name and resolv.conf info. Any help will be appreciated. Thanks, mb

2 1

is there a length limit on the line of parameters passed to isolinux.bin ?
by francois.blaes＠eu.effem.com 20 Jan '04

20 Jan '04

Hi all To perform AutoYAST installs, we use a custom boot CD based on the boot CD that ships with SLES8 SP2a The isolinux.cfg file has been tweaked to contain our standard install parameters (config and rpms repository, for instance) At the boot prompt, we append additional per-server parameters like the hostip, which makes the line even longer The install process works fine on some servers but fails on some others, noticeably on ones located on differnet subnets. Switching to the log displayed on tty3, we eventually found out that it fails when the line of parameters exceeds a certain length. The last characters are dropped, so the gateway IP is truncated and linuxrc fails of course to reach the repository Is this a known issue with isolinux ? What is the authorized length ? Is there a workaround ? Thanks in advance for your help. Francois BLAES ? Global Unix Team ? Mars ISI DDI *170 1639 ? Tel +33 (0) 3 88 05 16 39 ? Fax +33 (0) 3 88 05 16 79

3 3

Possible to install Suse Linux 8.1 with Suse Linux 9.0 autoyast?
by Kristian Köhntopp 20 Jan '04

20 Jan '04

Is it possible to PXE install Suse Linux 8.1 with a Suse Linux 9.0 autoyast installation? I have a vmware Suse Linux 9.0 ingeniously called "server" that has a copy the Suse Linux 8.1 CDs. I PXE boot a second vmware called "client", which shall be installed as a Suse Linux 8.1 system (with tons of addons). Possible? The Suse Linux 8.1 autoyast seems to be very much a work in progress and I'd rather use the 9.0 autoyast to do the install. Kristian

1 0

problem configuring network interface
by Duane Mari I. Deang 20 Jan '04

20 Jan '04

hi, i'm new to autoyast and did my first network autoinstall of suse8.2pro last week. everything went well except that no network interface was configured even if it was defined in the config file as follows: <networking> <dns> <dhcp_hostname config:type="boolean">true</dhcp_hostname> <dhcp_resolv config:type="boolean">true</dhcp_resolv> <domain>local</domain> <hostname>linux</hostname> <nameservers config:type="list"/> <searchlist config:type="list"/> </dns> <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth-pcmcia</device> <dhclient_set_down_link>yes</dhclient_set_down_link> <startmode>hotplug</startmode> <wireless>no</wireless> </interface> </interfaces> <modules config:type="list"/> <routing> <ip_forward config:type="boolean">false</ip_forward> <routes config:type="list"/> </routing> </networking> after installation, i had to configure the pcmcia device by hand using normal yast. then everything was ok. i would appreciate any ideas as to why the network configuration was not done during the autoinstall. thanks, Duane Deang

1 0

typo in rules.dtd in SuSE 9.0
by Frank Steiner 20 Jan '04

20 Jan '04

Hi Anas, the rules.dtd on SuSE 9.0 (DVD version) specifies "hostadress" with one "d", while the docu and the yast2 module specify and expect hostaddress with two "d". cu, Frank -- Dipl.-Inform. Frank Steiner Mail: fst_at_bio.informatik.uni-muenchen.de Lehrstuhl f. Bioinformatik Mail: frank_at_familiesteiner.de LMU, Amalienstr. 17 Phone: +49 89 2180-4049, Fax: -4054 80333 Muenchen, Germany http://www.informatik.uni-kiel.de/~fst/

1 0

"Device not found"/ configuring/operating modem
by Chris Guillet 20 Jan '04

20 Jan '04

> I am having difficulty getting a Winmodem to be detected and operable, > running version 9.0. Here's the situation: 1. Using Sony VAIO, Intel Pentium II (former stock Windows 95 machine) 2. Removed Windows and all files prior to installing 9.0 3. No problems during auto-installation--used all suggested settings 4. 9.0 could not configure the Lucent winmodem 5. Downloaded the ltmodem rpm file through the ftp server (of SuSE) and installed with YaST2--no problems 6. Configured the modem with YaST--again, no problems 7. The auto-configure set the modem at: /dev/ttyLT0 8. I set up Internet settings after configuring modem 9. When I try to connect via KInternet, nothing happens; the log message says something like "No such device: /dev/ttyLT0. 10. I did verify using the bash shell that the file "ttyLT0" > is in fact located in /dev. Any suggestions? As you might tell, I am a relative novice. The SuSE support people got me this far but the winmodem isn't covered in support, so I must solve myself. Thanks in advance.

1 0

Re: [suse-autoinstall] Autoinstallation and SuSE 8.2 Pro
by Mouncef_Belcaid＠blm.gov 19 Jan '04

19 Jan '04

I stopped getting that error after copying the DVD to the 8.2 directory using the same command mentioned below. I apologize for wasting everyone's valuable time. Thanks mb ----- Forwarded by Mouncef Belcaid/NIRM/BLM/DOI on 01/19/2004 04:19 PM ----- Mouncef_Belcaid@b lm.gov To: suse-autoinstall(a)suse.com cc: 01/19/2004 08:50 Subject: Re: [suse-autoinstall] Autoinstallation and SuSE 8.2 Pro AM Thank you for the suggestion. I copied all CDs to one directory using the following command for all CDs: mount /media/cdrom; cp -va /media/cdrom /repository/suse/8.2; eject Mouncef Anas Nashif <nashif(a)suse.de> To: suse-autoinstall(a)suse.com cc: 01/16/2004 07:02 Subject: Re: [suse-autoinstall] Autoinstallation and SuSE 8.2 Pro PM Patrick Greenwell wrote: > http://portal.suse.de/sdb/en/2003/03/rschmid_slesnfs.html > may help. > not reallly, this is more for sles configurations.. Mouncef, how did you copy the CDs, are all in the same directory or do you have seperate dirs for every CD? You have to copy them all into one directory if you wish to run the create_package_descr command, otherwise you dont need to run it, unless you change the packages. Anas > > On Jan 16, 2004 4:29 PM, Mouncef_Belcaid(a)blm.gov wrote: > > >> >> >> >> >>Hi everyone, >> >>I have been trying to install SuSE 8.2 using autoyast2 for the past couple >>of days. It worked with SuSE 9.0 but I'm having trouble with 8.2. >>I set up a repository from the 5 CDs provides with the SuSE distribution >>under /repository/suse/8.2, ran the following command: >>/usr/lib/YaST2/bin/create_package_descr -d /repository/suse/8.2/suse and >>shared it using nfs. This server is the pxe/tftp server as well as the nfs >>and dhcp server. >> >>I start the test machine, it goes through the configuration, formatting and >>installation process. Once it reboots the first time, it tries to install >>more packages and that is when it asks me to insert "CD 2". My question is, >>why doesn't it retrieve the rest of the packages from the nfs mount? This >>issue didn't happen with the SuSE 9.0 automated installation. >> >>Any help will be appreciated. >> >>Thanks in advance, >>Mouncef >> >> >>-- >>To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com >>For additional commands, e-mail: suse-autoinstall-help(a)suse.com >> > > > > > > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

logrotate
by Lyle Giese 19 Jan '04

19 Jan '04

I have installed my first SuSE(pro v8.2) machine and have a minor problem. It looks like logrotate is broken. Or did I miss something simple? I see all the required stuff in /etc and /etc/cron.* and /etc/crontab.d, but no log rotations... The binary is in /usr/sbin and cron is working.... Thanks, Lyle

1 0