openSUSE Autoinstall December 2004

autoinstall@lists.opensuse.org

43 participants
70 discussions

Interactive option checked BEFORE scripts?
by Jesse Keating 25 May '05

25 May '05

I'm using the modified.xml method of dynamic autoinstall control files. One of the things I wanted dynamic was the interactive or not choice, controlled by: <mode> <confirm config:type="boolean">false</confirm> If this was set to true, it should be interactive. I have this being set in modified.xml, however it does not take effect. Is this option checked BEFORE the pre-scripts run? -- Jesse Keating RHCE Pogo Linux -- Linux Systems Engineer tel: (888) 828-7646 ex: 436

3 2

SCR problem
by Brian Corriveau 05 Jan '05

05 Jan '05

How do I run this from the bash shell? (from clients/inst_finish.ycp) SCR::Write (.target.string, "/var/lib/YaST2/runme_at_boot", "") I want to try running this manually so I can understand why it is failing during autoinstallation. This is failing for my target, as are a couple other SCR commands. I can run the command from a chroot post-script to get the help output with: chroot /mnt /usr/lib/YaST2/servers/scr -h So the command seems to run somewhat, but for the runme_at_boot creation I get the Y2log error: 2004-12-18 02:34:13 <0> linux(3172) [liby2] Y2ProgramComponent.cc(launchExternall Program):292 Going to execute /usr/lib/YaST2/servers/scr with chroot /mnt 2004-12-18 02:34:13 <0> linux(519) [libycp] Scanner.cc(Scanner):107 Scanner settting builtinTable to 0x507d10 2004-12-18 02:34:13 <0> linux(519) [libycp] Scanner.cc(initTables):146 m_globalTT able 0x1776bb0 2004-12-18 02:34:13 <0> linux(519) [libycp] Scanner.cc(initTables):158 m_localTaable 0x52fd60 2004-12-18 02:34:13 <0> linux(519) [libycp] parser.yy(yyparse):284 ------------------------------------------- accept ------------------------------ -------------- 2004-12-18 02:34:13 <0> linux(519) [liby2] Y2ProgramComponent.cc(sendToExternal)) :377 Error writing to external program /usr/lib/YaST2/servers/scr: Couldn't sendd (`Write (.target.string, "/var/lib/YaST2/runme_at_boot", "")) (Broken pipe) 2004-12-18 02:34:13 <3> linux(519) [liby2] Y2ProgramComponent.cc(receiveFromExtee rnal):343 External program /usr/lib/YaST2/servers/scr died unexpectedly 2004-12-18 02:34:13 <3> linux(519) [Interpreter] scr:240 SCR::Write() did not reeturn a boolean So I'd like to understand what is wrong with my target's environment that this would fail. thanks, Brian

1 1

EXTRA_PROV_FILE missing from SLES8 s390
by Kohrs, Steven 03 Jan '05

03 Jan '05

I'm trying to update the package description of a SLES8 s390 distribution which is being housed on a SLES9 x86 server. /usr/bin/create_package_descr EXTRA_PROV_FILE location missing. Call this script with -x <location to EXTRA_PROV file>. The EXTRA_PROV is available on the first CD in the directory suse/setup/descr There is no "EXTRA_PROV" included with the SLES8 s390 media.

2 3

Firstboot questions
by Anthony Staples 03 Jan '05

03 Jan '05

Is there a way to easily force FIRSTBOOT to run the X11 and Network setup screen sections of YAST after a ghost image is loaded to a new machine? I have looked over the doc and I _think _it would involve adding information to the control.xml file under the firstboot section, but I am uncertain how to proceed. Basically I would like "firstboot" to behave as sysprep does for XP. I would also like to turn off the resetting of the root password... I don't want the user's changing the root password. Is it as simple as commenting out that section under "firstboot" in the control.xml file? Cheers, -T 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.

2 3

Re: Fw: [suse-autoinstall] customizing initrd
by Aaron Amauba 30 Dec '04

30 Dec '04

Thanks for the reply. 1st time doing this for me, so pls bear with... Also, this might be the wrong list for this, but since its breaking the AutoYast installation (Well, no network support = no AutoYast).... The x346 has the new BCM5721 chip. SLES8 does not have built in support for this chip, so to get network support into the install initrd I had to do the fillowing. Build the new module against the same kernel tree as the install kernel. The one I was using happaned to be 2.4.21-138 (I also used the smp the 1st time by accident). Save the original initrd zcat initrd > rd mount -oloop rd /mnt copy the new .o file to /mnt/modules/ umount /mnt gzip -9 rd mv rd.gz initrd So, now I had a initrd with the new bcm5700.o file (with support for the 5721 chip). The only modules.pcimap I could find was in /lib/modules/modules.pcimap in the build tree. Not in initrd. It didnt have an entry for the new chip. I know the vendor ID is 14e4 and the device ID is 1659. But I dont know the subvendor, sbudevice, class, class_mask or device_data. Im assuming this is the correct place to update. I am having difficulty finding docs for this. What I did find said the distro usually fills out this information. Any more suggestions or links to Doc's I should read? Thanks Joseph V Moss <jmoss(a)ichips.intel.com> 12/29/2004 04:30 PM To Aaron Amauba <aapa20032003(a)yahoo.com> cc suse-autoinstall(a)suse.com Subject Re: Fw: [suse-autoinstall] customizing initrd Update the modules.pcimap (in /lib/modules/<kernel_version>-default/ in the initrd) with the PCI ID of the new chip. > I am trying to do the same thing (except with a x346 instead). I added the new bcm5700.o file to the /modules directory in initrd. After I do that I have to add the module manually. Its nots found automatically. What else do I have to change? > > > > > > Thomas Mieslinger <Thomas.Mieslinger(a)gls-itservices.com> > 11/25/2004 12:26 PM > > > > > > To > > suse-autoinstall(a)suse.com > cc > > > Subject > > Re: [suse-autoinstall] customizing initrd > > > > > I'd like to install a new ibm x336 with bcm5721 network chips. These are > not support by the standard kernel so I need to change the bcm5700.o. > -- > GLS IT Services > Thomas Mieslinger > GLS Germany Str. 1-7 fon: +49 6677 17 463 > 36286 Neuenstein fax: +49 6677 17 111 > Germany eMail: thomas.mieslinger(a)gls-itservices.com > > Anas Nashif <nashif(a)suse.de> schrieb am 25.11.2004 21:22:33: > > > The trailing garbage message can be ignored. I have no idea where it > > comes from, but after recreating the initrd as described earlier, it > > works. What exactly did you change in the initrd? > > > > Anas > > > > Thomas Mieslinger wrote: > > > > > > > > > > > > Hi Andi, > > > > > > this initrd is right off the SLES 8 SP3 cd. Without the trailing > garbage it > > > doesn't boot anymore. How can I re-add this to the initrd? > > > > > > Thanks in advance > > > > > > Thomas > > > -- > > > GLS IT Services > > > Thomas Mieslinger > > > GLS Germany Str. 1-7 fon: +49 6677 17 463 > > > 36286 Neuenstein fax: +49 6677 17 111 > > > Germany eMail: thomas.mieslinger(a)gls-itservices.com > > > > > > Andi Kleen <ak(a)suse.de> schrieb am 25.11.2004 20:57:09: > > > > > > > > >>On Thu, Nov 25, 2004 at 08:52:05PM +0100, Thomas Mieslinger wrote: > > >> > > >>> > > >>> > > >>> > > >>>>Well I think the problem is that during uncompression I get this > > > > > > message. > > > > > >>>>root@deinst01> gzip -d initrd.gz > > >>>> > > >>>>gzip: initrd.gz: decompression OK, trailing garbage ignored > > >>>> > > >>>>when I recompress this file it is smaller than the original and > > >>>>doesn't boot anymore. > > >>>> > > >>>>What is that "trailing garbage ignored"? > > >> > > >>It's possible to append a custom DSDT to the initrd. DSDT is a BIOS > > >>ACPI table which is often buggy on laptops and can be replaced. > > >>But for non laptops that's rarely done and the installer never > > >>does it on its own. > > >> > > >>-Andi > > > > > > > > > > > > > -- > > 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 > > > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com --------------------------------- Do you Yahoo!? The all-new My Yahoo! � What will yours do?

1 0

installation_sources
by Michael Shannon 30 Dec '04

30 Dec '04

Is there anyway to make installation_sources use active instead of passive ftp? -m Michael Shannon | Sr. Systems Engineer - UNIX Systems Engineering Schedule: In between 06:30 and 07:00 Out around 15:00 PST InfoSpace INC 601 108th Ave NE | Suite 1200 | Bellevue, WA 98004 Tel 425.201.8750 | Fax 425.201.6160 | Mobile 206.310.4664 michael.shannon(a)infospace.com <mailto:michael.shannon@infospace.com> | www.infospaceinc.com

1 0

how to install suse via http proxy?
by Kai Zhang 30 Dec '04

30 Dec '04

I can install suse via direct ftp access to ftp.mirror.ac.uk with no problem. But now I am behind firewall with only http proxy. With boot disk I can see it loading data into ramdisk from ftp server and load GUI. The major problem prevent me from completing the installation is the error msg: Software Cannot read package data from installation media. Media Error? For god sake it's suppose to be a ftp installation. I tried different ftp suse download servers, all have the same problem! I guess this is because it can't read the packages (or at least the list of the packages) on the ftp server. I've searched everywhere for solution. Please help! Regards, Kai

1 0

Re: Fw: [suse-autoinstall] customizing initrd
by Aaron Amauba 30 Dec '04

30 Dec '04

I am trying to do the same thing (except with a x346 instead). I added the new bcm5700.o file to the /modules directory in initrd. After I do that I have to add the module manually. Its nots found automatically. What else do I have to change? Thomas Mieslinger <Thomas.Mieslinger(a)gls-itservices.com> 11/25/2004 12:26 PM To suse-autoinstall(a)suse.com cc Subject Re: [suse-autoinstall] customizing initrd I'd like to install a new ibm x336 with bcm5721 network chips. These are not support by the standard kernel so I need to change the bcm5700.o. -- GLS IT Services Thomas Mieslinger GLS Germany Str. 1-7 fon: +49 6677 17 463 36286 Neuenstein fax: +49 6677 17 111 Germany eMail: thomas.mieslinger(a)gls-itservices.com Anas Nashif <nashif(a)suse.de> schrieb am 25.11.2004 21:22:33: > The trailing garbage message can be ignored. I have no idea where it > comes from, but after recreating the initrd as described earlier, it > works. What exactly did you change in the initrd? > > Anas > > Thomas Mieslinger wrote: > > > > > > > > Hi Andi, > > > > this initrd is right off the SLES 8 SP3 cd. Without the trailing garbage it > > doesn't boot anymore. How can I re-add this to the initrd? > > > > Thanks in advance > > > > Thomas > > -- > > GLS IT Services > > Thomas Mieslinger > > GLS Germany Str. 1-7 fon: +49 6677 17 463 > > 36286 Neuenstein fax: +49 6677 17 111 > > Germany eMail: thomas.mieslinger(a)gls-itservices.com > > > > Andi Kleen <ak(a)suse.de> schrieb am 25.11.2004 20:57:09: > > > > > >>On Thu, Nov 25, 2004 at 08:52:05PM +0100, Thomas Mieslinger wrote: > >> > >>> > >>> > >>> > >>>>Well I think the problem is that during uncompression I get this > > > > message. > > > >>>>root@deinst01> gzip -d initrd.gz > >>>> > >>>>gzip: initrd.gz: decompression OK, trailing garbage ignored > >>>> > >>>>when I recompress this file it is smaller than the original and > >>>>doesn't boot anymore. > >>>> > >>>>What is that "trailing garbage ignored"? > >> > >>It's possible to append a custom DSDT to the initrd. DSDT is a BIOS > >>ACPI table which is often buggy on laptops and can be replaced. > >>But for non laptops that's rarely done and the installer never > >>does it on its own. > >> > >>-Andi > > > > > > > > -- > 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 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

RE: [suse-autoinstall] re-visited YaST.firstboot question
by Michael Shannon 28 Dec '04

28 Dec '04

Excellent, once I started editing the right section of control.xml everything fell into place :) -m -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Monday, December 27, 2004 4:10 PM To: Michael Shannon Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] re-visited YaST.firstboot question The answer to your question lies in the control.xml file which controls the workflow of the installation. autoyast has a different workflow than the manual installation and it shows no proposals in second stage. If you want the network proposal, you have to added it to the autoinstallation workflow. See http://yast2.suse.com/tdg/html/yast2-installation.html#product_control for more detailes. (Above document is still work in progress). Anas Michael Shannon wrote: > I know I've asked this once before, but I've spent some more time going > through the scripts and still can't find out how to accomplish what I'm > looking for (having the lan module run during Yast2.firstboot, without > taking the default proposals) > > From what I gather, if you use autoyast it does a few things to prep the > system for the first. > 1) creates the /var/lib/YaST2/runme_at_boot file and > 2) creates the /etc/install.inf > > ... It does other stuff, but I'm not worried about that right now. > > When /etc/init.d/boot is run it checks for runme_at_boot and if that > exists then /usr/lib/YaST2/bin/YaST2.firstboot runs and that starts > > /usr/lib/YaST2/bin/YaST2 installation continue > > This reads the /etc/install.inf file and the values there are used for > the rest of the autoinstall. > > If I make Manual = 1 in /etc/install.inf, yast asks about the network > modules, but never drops me to the yast2 lan module, it looks like it > just accepts the proposal based on the autoyast=file///a.xml file. > > If I could force the lan module to run and not accept any defaults it > would save me the hassle of having to generate new ssl certificates > after running yast lan (host name changes). > > > Thanks again, > > -m > > > > > -----Original Message----- > From: Michael Shannon [mailto:Michael.Shannon@infospace.com] > Sent: Tuesday, December 21, 2004 2:42 PM > To: suse-autoinstall(a)suse.com > Subject: [suse-autoinstall] YaST.firstboot question > > > For a while we thought using DHCP with autoyast sounded like a good > idea, but then we decided not to go that direction. > > I would really like YaST.firstboot to run the lan module on first boot, > I've read through the scripts and its not very obvious to me how to make > this happen. I've completely removed the lan configuration from > autoyast.xml hoping that would force YaST.firstboot to run the lan > module, but my efforts yielded very little fruit :( > > It looks like there might be something in the install.inf file that is > telling YaST that the interface has been configured, is there a way > around this? > > Thanks, > > -m > > > >

1 0

FW: [suse-autoinstall] re-visited YaST.firstboot question
by Michael Shannon 28 Dec '04

28 Dec '04

Sorry, Anas, didn't mean to send this directly to you.. -----Original Message----- From: Michael Shannon Sent: Tuesday, December 28, 2004 8:46 AM To: 'Anas Nashif' Subject: RE: [suse-autoinstall] re-visited YaST.firstboot question Yup, that's exactly what I was looking for: ) I looked through the control.xml file and it wasn't clear to me how to translate this: <module> <label>Network</label> <name>proposal</name> <arguments>true,true,`net</arguments> </module> I know it starts the inst_proposal module in `net mode, but its not clear to me what "true,true" does. I read /usr/share/doc/packages/yast2-installation/autodocs/inst_proposal.html /usr/share/doc/packages/yast2-installation/proposal-API.txt And /usr/share/YaST2/clients/inst_proposal.ycp I didn't anything in inst_proposal.ycp that parses the arguments, so I'm wondering if those arguments actually do anything? I'm going to change the values and see what happens, but if there's even more documentation to be read, I'd be happy to read that instead of bother the list. Thanks, -m -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Monday, December 27, 2004 4:10 PM To: Michael Shannon Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] re-visited YaST.firstboot question The answer to your question lies in the control.xml file which controls the workflow of the installation. autoyast has a different workflow than the manual installation and it shows no proposals in second stage. If you want the network proposal, you have to added it to the autoinstallation workflow. See http://yast2.suse.com/tdg/html/yast2-installation.html#product_control for more detailes. (Above document is still work in progress). Anas Michael Shannon wrote: > I know I've asked this once before, but I've spent some more time going > through the scripts and still can't find out how to accomplish what I'm > looking for (having the lan module run during Yast2.firstboot, without > taking the default proposals) > > From what I gather, if you use autoyast it does a few things to prep the > system for the first. > 1) creates the /var/lib/YaST2/runme_at_boot file and > 2) creates the /etc/install.inf > > ... It does other stuff, but I'm not worried about that right now. > > When /etc/init.d/boot is run it checks for runme_at_boot and if that > exists then /usr/lib/YaST2/bin/YaST2.firstboot runs and that starts > > /usr/lib/YaST2/bin/YaST2 installation continue > > This reads the /etc/install.inf file and the values there are used for > the rest of the autoinstall. > > If I make Manual = 1 in /etc/install.inf, yast asks about the network > modules, but never drops me to the yast2 lan module, it looks like it > just accepts the proposal based on the autoyast=file///a.xml file. > > If I could force the lan module to run and not accept any defaults it > would save me the hassle of having to generate new ssl certificates > after running yast lan (host name changes). > > > Thanks again, > > -m > > > > > -----Original Message----- > From: Michael Shannon [mailto:Michael.Shannon@infospace.com] > Sent: Tuesday, December 21, 2004 2:42 PM > To: suse-autoinstall(a)suse.com > Subject: [suse-autoinstall] YaST.firstboot question > > > For a while we thought using DHCP with autoyast sounded like a good > idea, but then we decided not to go that direction. > > I would really like YaST.firstboot to run the lan module on first boot, > I've read through the scripts and its not very obvious to me how to make > this happen. I've completely removed the lan configuration from > autoyast.xml hoping that would force YaST.firstboot to run the lan > module, but my efforts yielded very little fruit :( > > It looks like there might be something in the install.inf file that is > telling YaST that the interface has been configured, is there a way > around this? > > Thanks, > > -m > > > >

1 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall December 2004