March 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

RE: [suse-autoinstall] auto-installing with patched OS
by Suffin, Charles 14 Mar '05

14 Mar '05

Hi folks, I used Anas' create_update_source.sh on my SLES9 installation source. It created an updates/ directory in that source, resulting in a directory structure that looks like this: SLES9/ SUSE-CORE-Version-9/ SUSE-SLES-Version-9/ boot content control.xml media.1 updates/ <-- this was newly-created by the script, as expected yast/ After this, I followed the instructions in the script: 1. I moved my packages into SLES9/updates/suse/<arch> directories. 2. I cd into SLES9/updates/suse. 3. I ran /usr/bin/create_package_descr -x setup/descr/EXTRA_PROV OK, so then I do an autoinstall from this source on a targe machine. After the reboot, there is no sign of my package on the installed machine, and if I search for the package using YaST2 "Install and Remove Software" it is not found by its name. I think I'm missing a step somewhere to cause the installation to actually install my package. What am I missing? Do I need to add a <package> line to the XML file? Do I need to do some more mucking with the installation source? -- Charlie -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Tuesday, March 01, 2005 10:53 PM To: Mark Acosta Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] auto-installing with patched OS Hi, I have a script for doing this you might want to try, see http://www.suse.de/~nashif/autoyast2/scripts/create_update_source.sh The script itself has some additional info on how to use it. The script uses the multiple source feature known from SLES, it will register multiple sources and the latest version of packages available in the original source and the new source will be installed. Give it a try and let me know if it works for you. any feedback is welcome. Anas Mark Acosta wrote: > I need to autoinstall a patched 2.6.8-24.11-default kernel (including > patched utils) for Suse 9.2. The stock kernel is 2.6.8-24.10-default, > but I can't find out how to patch/update to 2.6.8-24.11-default. How is > the best accomplished? > > thanks, > Mark > > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

3 3

self installing DVD
by jan terje tønnessen 13 Mar '05

13 Mar '05

Hi ! I have a working autoyast for Suse9.1. I would now like to make a "self-installing-DVD" which should be 100% automated. I am thinking of two methods: 1) A bootable DVD which starts autoyast (with repository on the same DVD). 2) A bootable DVD which partitions the HD and then 'dd' form the DVD to the HD. Has anybody done something similar ? Br / Jan Terje

1 0

Advice to Incorporate UDEV into auto-install?
by Suffin, Charles 11 Mar '05

11 Mar '05

Hi guys, Have any of you incorporated UDEV device naming into your auto-install? I'm looking for XML examples, docs, howtos... whatever. We need to do this here at Stratus, and about all I know how to do with the autoinstall at this point is to start the boot.udev service at runlevel B. I don't think this will be enough, as configuration work is needed as well. For example, does anyone know how to muck with udev.conf via autoyast/YaST2, or will I have to write a script for this? FYI, our objective is to get fixed device naming for our disks, which is required for our hardware architecture. We might use UDEV for other device naming as well. Forgive the ignorant question(s). Any help is appreciated. -- charlie ----- A. Charles Suffin Senior Software Engineer Stratus Technologies, Inc. (http://www.stratus.com) 111 Powdermill Road Maynard, MA 01754-3409 US (978)461-7590

1 0

RE: [suse-autoinstall] YaST2 Doesn't Search for Source Packages
by Suffin, Charles 11 Mar '05

11 Mar '05

In my example, yes, both of the k3b packages are listed in the packages file, Todd. For the binary package, there's: =Pkg: k3b 0.11.7 23.1 i586 < ... stuff ... > =Src: k3b 0.11.7 23.1 src =Tim: 1088641834 =Loc: 1 k3b-0.11.7-23.1.i586.rpm < ... stuff ... > And then for the source package, there's: =Pkg: k3b 0.11.7 23.1 src =Loc: 3 k3b-0.11.7-23.1.src.rpm src < ... stuff ... > =Shr: k3b 0.11.7 23.1 i586 These two descriptions clearly relate the packages to each other. Does the "src" token in the "=Pkg:" statement inform YaST2 not to show it in a search?? -- Charlie -----Original Message----- From: Ness, Todd [mailto:todd.ness@eds.com] Sent: Wednesday, March 09, 2005 4:43 PM To: suse-autoinstall(a)suse.com Subject: RE: [suse-autoinstall] YaST2 Doesn't Search for Source Packages Try to grep src out of the CD1/suse/setup/descr/packages if it is in there I think the yast sw_single module should be able to see it. You can create packages files with /usr/lib/YaST2/bin/create_package_descr -----Original Message----- From: Suffin, Charles [mailto:Charles.Suffin@stratus.com] Sent: Wednesday, March 09, 2005 1:27 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] YaST2 Doesn't Search for Source Packages Hi guys, This isn't an autoyast question, but it involves an installation server, and I'll bet someone here will know the answer... More to the point, I'm adding packages for my company's software, and I want to do it right! :) With YaST2 pointing at an SLES9 installation server, I find that "Install and Remove Software" does not find the source packages for a given name when you do a search on it (with the filter in search mode). The sources are part of the distro though, and sometimes someone in my dept. wants to study them... For example, the k3b binary package is found if you search for it, but not the source package. The two packages are in the CD1 and CD3 directories, respectively, on the server: ./SUSE-CORE-Version-9/CD1/suse/i586/k3b-0.11.7-23.1.i586.rpm ./SUSE-CORE-Version-9/CD3/suse/src/k3b-0.11.7-23.1.src.rpm The package database on the server (./SUSE-CORE-Version-9/CD1/suse/setup/descr/packages) is standard SLES9, and I see that both the binary and source packages for k3b are listed there. Why doesn't YaST2 find it? Is there something in the syntax of the packages file that indicates whether it should be found by the YaST2 search? Thanks. -- Charlie ----- A. Charles Suffin Senior Software Engineer Stratus Technologies, Inc. (http://www.stratus.com) 111 Powdermill Road Maynard, MA 01754-3409 US (978)461-7590 -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

3 9

Multiple RAID Types with SLES9/SP1 and autoyast
by Brad Hudson 11 Mar '05

11 Mar '05

I need some assistance with getting multiple RAID types to work across disks using autoyast. The formatting of all drives works properly, but the software RAID does not configure properly. I have raid1 for my /boot partition and raid5 for all other /dev/md partitions. The disks (/dev/cciss/c0d*) configure properly, but the software partitions (/dev/md*) all configure as raid1, eventhough raid5 is specified. The pertinent sections of the profile are pasted below. FYI: Each disk is exactly the same simply incremented (c0d0, c0d1, etc.). <partitioning config:type="list"> <drive> <device>/dev/cciss/c0d0</device> <partitions config:type="list"> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">0xFD</partition_id> <partition_type>primary</partition_type> <raid_name>/dev/md0</raid_name> <raid_type>raid</raid_type> <size>136436KB</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">0xFD</partition_id> <partition_type>primary</partition_type> <raid_name>/dev/md1</raid_name> <raid_type>raid</raid_type> <size>421545KB</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">0xFD</partition_id> <partition_type>primary</partition_type> <raid_name>/dev/md2</raid_name> <raid_type>raid</raid_type> <size>1633016KB</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">0xFD</partition_id> <raid_name>/dev/md3</raid_name> <raid_type>raid</raid_type> <size>823014KB</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">0xFD</partition_id> <raid_name>/dev/md4</raid_name> <raid_type>raid</raid_type> <size>1633016KB</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">0xFD</partition_id> <raid_name>/dev/md5</raid_name> <raid_type>raid</raid_type> <size>2449630KB</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">0xFD</partition_id> <raid_name>/dev/md6</raid_name> <raid_type>raid</raid_type> <size>4886036KB</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">0xFD</partition_id> <raid_name>/dev/md7</raid_name> <raid_type>raid</raid_type> <size>1633016KB</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">0xFD</partition_id> <raid_name>/dev/md8</raid_name> <raid_type>raid</raid_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> more drives like above here, then... <drive> <device>/dev/md</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>data=journal,noacl</fstopt> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">0</partition_nr> <raid_type>raid1</raid_type> </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <fstopt>pri=42</fstopt> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">1</partition_nr> <raid_type>raid5</raid_type> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>data=journal,noacl</fstopt> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> <raid_type>raid5</raid_type> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>data=journal,noacl</fstopt> <mount>/opt/emageon</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">3</partition_nr> <raid_type>raid5</raid_type> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>data=journal,noacl</fstopt> <mount>/opt/emageon/var</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">4</partition_nr> <raid_type>raid5</raid_type> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>data=journal,noacl</fstopt> <mount>/opt/emageon/log</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">5</partition_nr> <raid_type>raid5</raid_type> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>data=journal,notail,noacl</fstopt> <mount>/opt/emageon/oradb/online</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">6</partition_nr> <raid_type>raid5</raid_type> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>data=journal,notail,noacl</fstopt> <mount>/opt/emageon/oradb/backup</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">7</partition_nr> <raid_type>raid5</raid_type> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>data=ordered,noacl</fstopt> <mount>/opt/emageon/archive</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">8</partition_nr> <raid_type>raid5</raid_type> </partition> </partitions> <use>all</use> </drive> </partitioning> Brad

1 0

pxe boot, timeout on initrd tftp transfert
by Marc Sauton 10 Mar '05

10 Mar '05

Hi all, I have this 9.2 (eval, and SLES soon) network install on a Dell System PowerEdge 2850 (on its second net interface, eth1) running from a 9.0 server, and failing on a timeout when there is an attempt from the tftp server to send the ramdisk, or may be when the booting client seem to have lost its network config (crashed?), please see a trace and some details below, specially the last lines (some addresses removed for this text). Thanks for any suggestions, Marc. >From the booting client console: Intel(R) Boot Agent GE v1.2.16P6 Copyright (C) 1997-2004, Intel Corporation Intel(R) Boot Agent PXE Base Code (BA1216BD) Copyright (C) 1997-2003, Intel Corporation CLIENT MAC ADDR: xx xx xx xx xx xx GUID: ... CLIENT IP: 10.x.x.x MASK: 255.255.255.0 DHCP IP: 10.x.x.x GATEWAY IP: 10.x.x.x PXELINUX 2.06 0x3fc70fbd Copyright (C) 1994-2003 H. Peter Anvin UNDI data segment at: 000969A0 UNDI data segment size: 6240 UNDI code segment at: 0009CBE0 UNDI code segment size: 28D0 PXE entry point found (we hope) at 9CBE:0106 My IP address seems to be xxxxxxxx 10.x.x.x ip=10.x.x.x:10.x.x.x:10.x.x.x:255.255.255.0 TFTP prefix: Trying to load: pxelinux.cfg/01-xx-xx-xx-xx-xx-xx Trying to load: pxelinux.cfg/xxxxxxxx Loading 9.2.eval.dvd/boot/loader/linux64............................. Loading 9.2.eval.dvd/boot/loader/initrd64... and then time out. On the install server: ls -l /tftpboot/ total 17 drwxr-xr-x 4 root root 176 2005-03-09 18:17 . drwxr-xr-x 23 root root 536 2005-03-04 11:49 .. drwxr-xr-x 7 root root 792 2005-03-07 11:23 9.2.eval.dvd -rw-r--r-- 1 root root 188 2005-03-09 15:47 test.xml -rw-r--r-- 1 root root 11308 2003-11-28 01:05 pxelinux.0 drwxr-xr-x 2 root root 184 2005-03-10 12:52 pxelinux.cfg /tftpboot/pxelinux.cfg/default default linux serial 0,115200n8 label linux kernel 9.2.eval.dvd/boot/loader/linux64 append textmode=1 console=ttyS0,115200n8 initrd=9.2.eval.dvd/boot/loader/initrd64 autoyast=tftp://install.server.ip/test.xml A tcpdump and /var/log/messages on the tftp server show this: Mar 10 13:14:18 hostname dhcpd: DHCPDISCOVER from booting.client.mac.addr via eth1 Mar 10 13:14:18 hostname dhcpd: DHCPOFFER on booting.client.ip to booting.client.mac.addr via eth1 Mar 10 13:14:22 hostname dhcpd: DHCPREQUEST for booting.client.ip (install.server.ip) from booting.client.mac.addr via eth1 Mar 10 13:14:22 hostname tftpd[10243]: Serving pxelinux.0 to booting.client.ip:2070 Mar 10 13:14:22 hostname tftpd[10243]: Serving pxelinux.0 to booting.client.ip:2071 13:14:22.948925 IP booting.client.ip.57089 > install.server.ip.69: 63 RRQ "pxelinux.cfg/booting.client.mac.addr" octet tsize 0 blks 13:14:22.949348 IP install.server.ip.32796 > booting.client.ip.57089: UDP, length: 18 13:14:22.953048 IP booting.client.ip.56834 > install.server.ip.69: 51 RRQ "pxelinux.cfg/0A0A1426" octet tsize 0 blksize 1440 13:14:22.953503 IP install.server.ip.32796 > booting.client.ip.56834: UDP, length: 25 13:14:22.953676 IP booting.client.ip.56834 > install.server.ip.32796: UDP, length: 4 13:14:22.953816 IP install.server.ip.32796 > booting.client.ip.56834: UDP, length: 453 13:14:22.953925 IP booting.client.ip.56834 > install.server.ip.32796: UDP, length: 4 13:14:22.957419 IP booting.client.ip.56835 > install.server.ip.69: 62 RRQ "9.2.eval.dvd/boot/loader/linux64" octet tsize 0 blksi 13:14:22.957876 IP install.server.ip.32796 > booting.client.ip.56835: UDP, length: 29 13:14:22.958049 IP booting.client.ip.56835 > install.server.ip.32796: UDP, length: 4 13:14:22.958163 IP install.server.ip.32796 > booting.client.ip.56835: UDP, length: 1444 .....snip........ 13:14:23.245002 IP booting.client.ip.56835 > install.server.ip.32796: UDP, length: 4 13:14:23.415832 IP install.server.ip.32796 > booting.client.ip.56836: UDP, length: 29 Mar 10 13:14:22 hostname tftpd[10243]: Serving pxelinux.cfg/booting.client.mac.addr to booting.client.ip:57089 Mar 10 13:14:22 hostname tftpd[10243]: Serving pxelinux.cfg/0A0A1426 to booting.client.ip:56834 Mar 10 13:14:22 hostname tftpd[10243]: Serving 9.2.eval.dvd/boot/loader/linux64 to booting.client.ip:56835 Mar 10 13:14:23 hostname tftpd[10243]: Serving 9.2.eval.dvd/boot/loader/initrd64 to booting.client.ip:56836 13:14:28.585856 IP install.server.ip.32796 > booting.client.ip.56836: UDP, length: 29 Mar 10 13:14:28 hostname tftpd[10243]: timeout: retrying... 13:14:33.585049 IP install.server.ip.32796 > booting.client.ip.56836: UDP, length: 29 13:14:38.584206 IP install.server.ip.32796 > booting.client.ip8.56836: UDP, length: 29 13:14:43.583383 IP install.server.ip.32796 > booting.client.ip8.56836: UDP, length: 29 13:14:48.582561 IP install.server.ip.32796 > booting.client.ip.56836: UDP, length: 29 Mar 10 13:14:48 hostname last message repeated 4 times

1 0

RE: [suse-autoinstall] Updating an existing NLD repository with N LD sp1.
by Suffin, Charles 10 Mar '05

10 Mar '05

Anas, Isn't that missing a link to linux, as per your email from last month?: linux -> SUSE-SLES-9-Service-Pack-Version-1/CD1/linux/ (just checking) -- Charlie -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Thursday, March 10, 2005 10:23 AM To: Anthony Staples Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Updating an existing NLD repository with NLD sp1. Anthony, The easiest way to integerate the service pack: in your current repository (<rep_dir>) create CD directories: mkdir -p <rep_dir>/SP1/{CD1,CD2,CD3....} mkdir <rep_dir>/yast ln -sf SP1/CD1/driverupdate echo "/SP1 /SP1" > yast/order echo "/" >> yast/order echo "/SP1" > yast/instorder echo "/" >> yast/instorder Anas Anthony Staples wrote: > I am downloading sp1 cd's for Novell Linux Desktop. What is the best, > easiest way to integrate these new packages into my existing > repository? Is there a script available to do it, or do I have to > start with a new repository? > > I see that there is a checkbox in the autoyast repository "Source > Configuration" window to "prompt for additional cds..." But when > trying to edit the existing repository this is greyed out. I don't > remember if it was greyed out when i created the repository. > > Cheers, Tony Staples astaples(a)humana.com > > > > The information transmitted is intended only for the person or entity > to which it is addressed and may contain CONFIDENTIAL material. If > you receive this material/information in error, please contact the > sender and delete or destroy the material/information. > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

SLES 8 - Removing of packages during Installation failed
by Diener, Stefan 10 Mar '05

10 Mar '05

Hi group, i´m having a little problem with the software package configuration using autoyast installation. I want to uninstall some packages automatically during the autoyast installation. Here is the software section from my xml file: ------------------------------------------------------------------------ <software> <addons config:type="list"/> <base>default</base> <packages config:type="list"> <package>kernel-source</package> </packages> <remove-packages config:type="list"> <package>capi4linux</package> <package>i4l-isdnlog</package> <package>i4lfirm</package> <package>i4l-base</package> </remove-packages> </software> ------------------------------------------------------------------------ The installation of the additonal package "kernel-source" is okay, but the uninstallation of the i4l package doesn´t work. A manual removing with the rpm -e command in the order shown above works fine. Any ideas? Best regards, Stefan

4 4

RE: [suse-autoinstall] YaST2 Doesn't Search for Source Packages
by Ness, Todd 09 Mar '05

09 Mar '05

Good question, I always add source packages from the command line. So, I had not run into that problem, hopefully Anas or somebody "more in the know" will respond -----Original Message----- From: Suffin, Charles [mailto:Charles.Suffin@stratus.com] Sent: Wednesday, March 09, 2005 3:04 PM To: suse-autoinstall(a)suse.com Subject: RE: [suse-autoinstall] YaST2 Doesn't Search for Source Packages In my example, yes, both of the k3b packages are listed in the packages file, Todd. For the binary package, there's: =Pkg: k3b 0.11.7 23.1 i586 < ... stuff ... > =Src: k3b 0.11.7 23.1 src =Tim: 1088641834 =Loc: 1 k3b-0.11.7-23.1.i586.rpm < ... stuff ... > And then for the source package, there's: =Pkg: k3b 0.11.7 23.1 src =Loc: 3 k3b-0.11.7-23.1.src.rpm src < ... stuff ... > =Shr: k3b 0.11.7 23.1 i586 These two descriptions clearly relate the packages to each other. Does the "src" token in the "=Pkg:" statement inform YaST2 not to show it in a search?? -- Charlie -----Original Message----- From: Ness, Todd [mailto:todd.ness@eds.com] Sent: Wednesday, March 09, 2005 4:43 PM To: suse-autoinstall(a)suse.com Subject: RE: [suse-autoinstall] YaST2 Doesn't Search for Source Packages Try to grep src out of the CD1/suse/setup/descr/packages if it is in there I think the yast sw_single module should be able to see it. You can create packages files with /usr/lib/YaST2/bin/create_package_descr -----Original Message----- From: Suffin, Charles [mailto:Charles.Suffin@stratus.com] Sent: Wednesday, March 09, 2005 1:27 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] YaST2 Doesn't Search for Source Packages Hi guys, This isn't an autoyast question, but it involves an installation server, and I'll bet someone here will know the answer... More to the point, I'm adding packages for my company's software, and I want to do it right! :) With YaST2 pointing at an SLES9 installation server, I find that "Install and Remove Software" does not find the source packages for a given name when you do a search on it (with the filter in search mode). The sources are part of the distro though, and sometimes someone in my dept. wants to study them... For example, the k3b binary package is found if you search for it, but not the source package. The two packages are in the CD1 and CD3 directories, respectively, on the server: ./SUSE-CORE-Version-9/CD1/suse/i586/k3b-0.11.7-23.1.i586.rpm ./SUSE-CORE-Version-9/CD3/suse/src/k3b-0.11.7-23.1.src.rpm The package database on the server (./SUSE-CORE-Version-9/CD1/suse/setup/descr/packages) is standard SLES9, and I see that both the binary and source packages for k3b are listed there. Why doesn't YaST2 find it? Is there something in the syntax of the packages file that indicates whether it should be found by the YaST2 search? Thanks. -- Charlie ----- A. Charles Suffin Senior Software Engineer Stratus Technologies, Inc. (http://www.stratus.com) 111 Powdermill Road Maynard, MA 01754-3409 US (978)461-7590 -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

RE: [suse-autoinstall] user dialog during post install/config
by Schumacher, Gordon 09 Mar '05

09 Mar '05

I'm doing it like this: <init-scripts config:type="list"> <script> <filename>1-get_username_launch.sh</filename> <interpreter>shell</interpreter> <source><![CDATA[ #!/bin/sh wget http://toolsgrp.corp.mxtr.net/autoinstall/scripts/get_username.sh chmod +x get_username.sh exec ./get_username.sh ]]> </source> </script> I've attached my get_username script (with some site-specific stuff edited out). It's been working pretty well for me, with the caveat that you can't see the text output of the "passwd" command (for whatever reason, it ignores the previous "exec" command. I've been contemplating writing a replacement for the sole purpose of autoinstallation, that will output to stdout. (I'm assuming that there's a good security reason for it to ignore stdout, but for this purpose it would be acceptible to me not to.) -----Original Message----- From: Mark Acosta [mailto:mark@auditude.com] Sent: Tuesday, March 08, 2005 12:32 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] user dialog during post install/config Is there a mechanism/(set of xml tags) to enable user dialogs during post install/config? We need some of our auto-installs to have a user manually enter hostname and network details,etc. thanks, Mark -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0