openSUSE Autoinstall December 2007

autoinstall@lists.opensuse.org

18 participants
18 discussions

by John Willis

Does anyone know if any of the SLES releases 9 or 10 support passing the linuxrc option netdevice=<hardware mac address> ? I noticed Red Hat has had this for sometime and it seems totally missing in SuSE which seems really odd. I'm still scratching my head if we really are still passing only by kernel interface name. I read in the change log for linuxrc-1.8.6-3 a change that "sounds" like this feature. * Mon Mar 14 2005 - snwint(a)suse.de - s390: fix segfault in net_list_s390_devs() - extra root image was sometimes not used - allow netdevices to be specified by hwaddress But it looks like linuxrc-1.8.6-3 is only available in SuSE Professional 9.3. "any" commentary would be sincerely appreciated the feature also seems to be fairly minor since any delimiter seperating the octets in the hwaddr string could be used to identify the difference between an interface name and interface hw address if i could figure out a generic method of overriding the linuxrc with a custom script and daisy chain it back into linuxrc after setting up the interface name, I would.. and have a slight idea on how to do that.. but i'd rather find out i'm just missing something and the feature is already there Thanks!

9 years, 5 months

RE: [suse-autoinstall] SLES 10 RC2 remove-packages section?

by Matt Gillard

I dont have kinternet installed. This is what doesnt seem to work: <software> <patterns config:type="list"> <pattern>default</pattern> <pattern>Basis-Devel</pattern> <pattern>x11</pattern> </patterns> <packages config:type="list"> <packages>perl-libwww-perl</packages> <packages>net-snmp</packages> <packages>kernel-source</packages> </packages> <remove-packages config:type="list"> <packages>pptp</packages> <packages>smpppd</packages> <packages>ppp</packages> <packages>wvdial</packages> <packages>mutt</packages> </remove-packages> </software> In y2log it mentions that those packages should be removed, but it goes ahead and installs them anyway. I can do it manually on the command line: # rpm -e pptp smpppd ppp wvdial mutt and that works fine so I know I have no dependency problems. matt > -----Original Message----- > From: Uwe Gansert [mailto:ug@suse.de] > Sent: Friday, 30 June 2006 12:50 AM > To: suse-autoinstall(a)suse.com > Subject: Re: [suse-autoinstall] SLES 10 RC2 remove-packages section? > > > On Thursday 29 June 2006 16:45, Manfred Hollstein wrote: > > > If that fails, you have kinternet installed; add that to > the list and it > > should work. > > good point. > <remove-packages> can not break dependencies and so it's very > likely that > there is still a package that needs those packages. > I did a very small installation with no X - so it worked for me. > > -- > ciao, Uwe Gansert > > Uwe Gansert, Server Technologies Team > SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany > Fax: +49-(0)911-74053-476, Web: http://www.suse.de/~ug > now playing Covenant - Wasteland > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses. No warranty is made that this material is free from computer virus or any other defect or error. Any loss/damage incurred by using this material is not the sender's responsibility. The sender's entire liability will be limited to resupplying the material.

14 years, 2 months

[opensuse-autoinstall] fetch profile via nfs in 10.3

by Ulrich Hoelscher

Hi, in 10.2 I deploy the autoyast profiles via nfs, this works out of the box. To use it I call autoyast=nfs://.../autoinst.xml If i try it with 10.3 this is not possible. The installation sources are also deployed via nfs, which works fine. After starting the installation in autoyast mode it not possible to mount the nfs share. The reason is the locks can not be handled. As a work around I use http to deploy the profiles and nfs to deploy the rpms. Is this a bug or a desired feature? regards Ulrich -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

14 years, 3 months

[opensuse-autoinstall] nfs_server: cannot update idmap.conf

by Lars Stavholm

Hi list, We're using SuSE 10.3 retail autoyast, and with some recent advice from Uwe, it works like a charm, except for one minor detail: When reaching the System Configuration stage, specifically the Configuring nfs_server step, we get a pop-up saying "Unable to write to idmapd.conf". A quick check under the hood at that point reveals that the /etc/idmapd.conf file is indeed present and has some content. The permissions on the file allows root to write to it. /etc/idmapd.conf seems to be part of the nfs-client package, which seems to be installed alright. It's a minor annoyance, but still, the installation is now not really unattended, since we have to be there to click OK on the pop-up to let the installation continue. Any advice appreciated. R /Lars -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

14 years, 4 months

[opensuse-autoinstall] quota

by Lars Stavholm

How do I enable quota support in my autoinst.xml? /L -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

14 years, 5 months

[opensuse-autoinstall] snort

by Lars Stavholm

Does anyone know why snort is excluded from SuSE 10.3 retail? /L -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

14 years, 5 months

[opensuse-autoinstall] Repeating pre-script

by Lars Stavholm

Hi all, we've just started playing with SuSE 10.3 retail and we seem to have a problem with a pre-script that keeps getting executed over and over again by autoyast. The pre-script has been successfully used in SuSE 10.2 to autodetect hard drives and memory size, and then producing a modified.xml that then gets used by the rest of the autoyast session. We have verified that the script runs fine and exits with status (zero) by means of the pre-script debug option. But nevertheless, it gets executed over and over again in an endless loop. Has anyone encountered any problems with re-executed pre-script? Any input appreciated /Lars -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

14 years, 5 months

[opensuse-autoinstall] Hard drive detection order

by Mohammad Haque

Hi, I have a system with hardware RAID and virtual media (CD and Floppy). If I boot the system with SLES 10 SP 1, the RAID drive is seen as /dev/sda. However, if I boot the same system from the network (PXE), the drive is shown as /dev/sdc. Does anybody know why virtual media is detected first when I boot from the network? Is there a way to make it detect the RAID drive first and shown as /dev/sda when I boot from network? Thanks! "Tumbleweed Communications <tumbleweed.com>" made the following annotations on 12/16/07, 20:28:57 ------------------------------------------------------------------------------ === Tumbleweed Communications Disclaimer === This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. Tumbleweed Communications Corp., an industry leader in managed file transfer and content security, provides enterprise-class solutions to organizations of all sizes. Tumbleweed's innovative products enable organizations to effectively manage and protect business-critical Internet communications, with capabilities that span secure file transfer, encryption, data loss prevention, and email security. ============================================================================== -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

14 years, 5 months

[opensuse-autoinstall] security and xml file

by Jochen Schaefer

Hi, I'm looking for a secure way to retrieve the autoyast xml file to the device. The reason is that some applications which we have to install need a clear text password. Is it possible to have SSL connections with client certificates via autoyast? I also thought about an authenticated connection to a webserver via HTTPS. Is that possible? Thanks, Jochen -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

14 years, 5 months

[opensuse-autoinstall] New kernel for installer yields... no install

by Dan Stromberg

Hi folks. I'm having some trouble with a SLES 10.1 install, but we'll be doing the same thing with openSUSE 10.3 shortly. Basically, we're adding a bunch of RPM's via a post install script, and some of those RPM's are miffed that the kernel we're installing with isn't the same as the kernel that we end up with after the install. So we're wanting to change our installs to use the same kernel, to see if we can get those RPM's added via the same mechanism we're using for most of our RPM's (in a post install chroot script), rather than needing to add them via an rc script. However, when I changed the kernel and initrd for the installer to be the as what we're installing, the installer no longer appears to be running. Instead, we get a grub menu via PXE like usual, but the installer just boots to the previous-installed OS on disk. We were using a kernel and initrd from off the CD image, and that was working fine. All I changed was the kernel and initrd. Is there some kernel command line option I need to add for a more generic kernel, to make it usable for during an install? Thanks! -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

14 years, 5 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall December 2007