April 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

mkinitrd (or grub) hanging on install of sles10-b9
by Mike Marion 10 Apr '06

10 Apr '06

Working on autoyast install of SLES10-beta9 and I've got it going all the way to the end, but the main console hangs at "Creating initrd..." f2 console shows no processes related to initrd or grub running, yast processes just sitting there. last of logs show (went all the way back to the line saying rpm installs finished to be sure I got it all): Apr 4 17:58:48 jumpmm yast2[3324]: <1> [wfm] Source.cc(SourceFinishAll):234 All sources finished Apr 4 17:58:48 jumpmm yast2[3324]: <1> [wfm] clients/pkg_finish.ycp:51 Pkg Builtin called: TargetFinish Apr 4 17:58:48 jumpmm yast2[3324]: 2006-04-04 18:58:48 <1> 129.46.234.55(3324) [rpm] RpmDb.cc(closeDatabase):711 Calling closeDatabase: RpmDb[V4(Xcm)V3(---): '(/mnt)/var/lib/rpm'] Apr 4 17:58:48 jumpmm yast2[3324]: 2006-04-04 18:58:48 <1> 129.46.234.55(3324) [rpm] librpmDb.cc(blockAccess):313 Block access Apr 4 17:58:48 jumpmm yast2[3324]: 2006-04-04 18:58:48 <1> 129.46.234.55(3324) [rpm] RpmDb.cc(closeDatabase):739 closeDatabase: RpmDb[NO_INIT] Apr 4 17:58:48 jumpmm yast2[3324]: 2006-04-04 18:58:48 <1> 129.46.234.55(3324) [target] TargetImpl.cc(~TargetImpl):90 Targets closed Apr 4 17:58:48 jumpmm yast2[3324]: 2006-04-04 18:58:48 <1> 129.46.234.55(3324) [rpm] RpmDb.cc(~RpmDb):318 ~RpmDb() Apr 4 17:58:48 jumpmm yast2[3324]: 2006-04-04 18:58:48 <1> 129.46.234.55(3324) [rpm] RpmDb.cc(~RpmDb):323 ~RpmDb() end Apr 4 17:58:48 jumpmm yast2[3324]: <1> [YCP] clients/pkg_finish.ycp:66 pkg_finish finished Apr 4 17:58:48 jumpmm yast2[3324]: <1> [Interpreter] clients/pkg_finish.ycp:66 Called YaST client returned: nil Apr 4 17:58:48 jumpmm yast2[3324]: <1> [wfm] Y2CCWFM.cc(createInLevel):153 Parsing finished Apr 4 17:58:48 jumpmm yast2[3324]: <1> [Interpreter] clients/driver_update1_finish.ycp:60 Calling YaST client driver_update1_finish (arguments: ["Write"]) Apr 4 17:58:48 jumpmm yast2[3324]: <1> [YCP] clients/driver_update1_finish.ycp:33 starting driver_update1_finish Apr 4 17:58:48 jumpmm yast2[3324]: <3> [libscr] clients/driver_update1_finish.ycp:46 No SCR instance found Apr 4 17:58:48 jumpmm yast2[3324]: <1> [YCP] clients/driver_update1_finish.ycp:60 driver_update1_finish finished Apr 4 17:58:48 jumpmm yast2[3324]: <1> [Interpreter] clients/driver_update1_finish.ycp:60 Called YaST client returned: nil Apr 4 17:58:48 jumpmm yast2[3324]: <1> [wfm] Y2CCWFM.cc(createInLevel):153 Parsing finished Apr 4 17:58:48 jumpmm yast2[3324]: <1> [Interpreter] installation/misc.ycp:111 Calling YaST client yast_inf_finish (arguments: ["Write"]) Apr 4 17:58:48 jumpmm yast2[3324]: <1> [YCP] clients/yast_inf_finish.ycp:40 starting yast_inf_finish Apr 4 17:58:48 jumpmm yast2[3324]: <1> [YCP] Linuxrc.ycp:120 WriteYaSTInf($["Keytable":"us.map.gz", "Language":"en_US", "RebootMsg":"0", "Root":"reboot"]) = Keytable: us.map.gz Language: en_US RebootMsg: 0 Root: reboot Apr 4 17:58:48 jumpmm yast2[3324]: <3> [libscr] clients/yast_inf_finish.ycp:99 No SCR instance found Apr 4 17:58:48 jumpmm yast2[3324]: <3> [YCP] clients/yast_inf_finish.ycp:101 Couldn't create target /var/lib/YaST2/runme_at_boot Apr 4 17:58:48 jumpmm yast2[3324]: <1> [YCP] clients/yast_inf_finish.ycp:111 yast_inf_finish finished Apr 4 17:58:48 jumpmm yast2[3324]: <1> [Interpreter] installation/misc.ycp:111 Called YaST client returned: nil Apr 4 17:58:48 jumpmm yast2[3324]: <1> [wfm] Y2CCWFM.cc(createInLevel):153 Parsing finished Apr 4 17:58:48 jumpmm yast2[3324]: <1> [Interpreter] clients/bootloader_finish.ycp:135 Calling YaST client bootloader_finish (arguments: ["Write"]) Apr 4 17:58:48 jumpmm yast2[3324]: <1> [YCP] clients/bootloader_finish.ycp:37 starting bootloader_finish Apr 4 17:58:48 jumpmm yast2[3324]: <3> [libscr] clients/bootloader_finish.ycp:77 No SCR instance found Apr 4 17:58:48 jumpmm yast2[3324]: <1> [YCP] Bootloader.ycp:365 Writing bootloader configuration Apr 4 17:58:48 jumpmm yast2[3324]: <3> [libscr] Bootloader.ycp:410 No SCR instance found Apr 4 17:58:48 jumpmm yast2[3324]: <1> [YCP] Bootloader.ycp:418 Device mapper and LVM initialization output: nil Apr 4 17:58:48 jumpmm yast2[3324]: <1> [YCP] Initrd.ycp:342 Initrd::Write called, changed: true, list: ["amd74xx", "sata_nv", "processor", "thermal", "fan", "reiserfs"] Apr 4 17:58:48 jumpmm yast2[3324]: <3> [libscr] Initrd.ycp:367 No SCR instance found Apr 4 17:58:48 jumpmm yast2[3324]: <3> [libscr] Initrd.ycp:369 No SCR instance found Apr 4 17:58:48 jumpmm yast2[3324]: <1> [YCP] Initrd.ycp:377 Modules [] were added to initrd not using Initrd module Apr 4 17:58:48 jumpmm yast2[3324]: <3> [libscr] Initrd.ycp:386 No SCR instance found Apr 4 17:58:48 jumpmm yast2[3324]: <1> [YCP] Initrd.ycp:389 Writing modules amd74xx sata_nv processor thermal fan reiserfs Apr 4 17:58:48 jumpmm yast2[3324]: <3> [libscr] Initrd.ycp:390 No SCR instance found Apr 4 17:58:48 jumpmm yast2[3324]: <3> [libscr] Initrd.ycp:391 No SCR instance found Apr 4 17:58:48 jumpmm yast2[3324]: <3> [libscr] Initrd.ycp:396 No SCR instance found Apr 4 17:58:48 jumpmm yast2[3324]: <3> [libscr] Initrd.ycp:399 No SCR instance found Apr 4 17:58:48 jumpmm yast2[3324]: <3> [ui] YUI_widgets.cc(createRichText):1122 Invalid arguments for the Label RichText: `RichText (`opt (`plainText), nil) Apr 4 17:58:48 jumpmm yast2[3324]: <3> [ui] YUI_widgets.cc(widgetWithId):2404 No widget with `id( `ok_help ) Apr 4 17:58:48 jumpmm yast2[3324]: <3> [libycp] Initrd.ycp:327 No widget with `id( `ok_help ) ========= Not sure why it's hanging there. Not using any initrd configs in my profiles and grub config is (I know this section is short, I'm doing a lot of includes now): <install> <bootloader> <global config:type="list"> <global_entry> <key>prompt</key> <value config:type="boolean">false</value> </global_entry> </global> <loader_device></loader_device> <loader_type>grub</loader_type> <location>mbr</location> <repl_mbr config:type="boolean">true</repl_mbr> <sections config:type="list"/> </bootloader> <general> <mode> <confirm config:type="boolean">false</confirm> </mode> </general> </install> Also, I don't seem to seem to be copying over my pre/chroot/post scripts either, even though they're in the xml file on the host after all the includes and such. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Frasier: "Well I had to, what with you underneath the covers with a flashlight looking at the National Geographics." Niles: "I was looking at the maps!" Frasier: "THAT'S what makes it so scary!" -- Frasier

2 3

SLES 9 SP3, Autoyast and multiple NICS trouble
by Cameron Seader 10 Apr '06

10 Apr '06

Greetings, There seems to be an issue with multiple NICS on SLES 9 SP3 Here is the xml we have at the moment between the networking tag. <networking> <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <dhcp_resolv config:type="boolean">false</dhcp_resolv> <domain>my.domain</domain> <hostname>myhostname</hostname> <nameservers config:type="list"> <nameserver>xxx.xxx.xxx.xxx</nameserver> <nameserver>xxx.xxx.xxx.xxx</nameserver> <nameserver>xxx.xxx.xxx.xxx</nameserver> </nameservers> </dns> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <device>eth0</device> <ipaddr>xxx.xxx.xxx.xxx</ipaddr> <netmask>xxx.xxx.xxx.xxx</netmask> <startmode>onboot</startmode> </interface> <interface> <bootproto>static</bootproto> <device>eth1</device> <ipaddr>xxx.xxx.xxx.xxx</ipaddr> <netmask>xxx.xxx.xxx.xxx</netmask> <startmode>onboot</startmode> </interface> <interface> <bootproto>static</bootproto> <device>eth2</device> <startmode>off</startmode> </interface> <interface> <bootproto>static</bootproto> <device>eth3</device> <startmode>off</startmode> </interface> <interface> <bootproto>static</bootproto> <device>eth4</device> <ipaddr>xxx.xxx.xxx.xxx</ipaddr> <netmask>xxx.xxx.xxx.xxx</netmask> <startmode>onboot</startmode> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>eth0</device> <module>tg3</module> </module_entry> <module_entry> <device>eth1</device> <module>tg3</module> </module_entry> <module_entry> <device>eth2</device> <module>e1000</module> </module_entry> <module_entry> <device>eth3</device> <module>e1000</module> </module_entry> <module_entry> <device>eth4</device> <module>e1000</module> </module_entry> </modules> <routing> <ip_forward config:type="boolean">false</ip_forward> </routing> </networking> When i use this configuration i get two of the Network interfaces configured in /etc/sysconfig/network and only one gets turned on. The NIC that gets turned on is the first one in the interfaces tag list, and the two that get configured in /etc/sysconfig/network is the first one listed in the interfaces tag list and one that is listed with the startmode as "off", all the rest of them do not even get configured at all. Why is this happening? Is there something that i need to be doing different here? Thanks, Cameron Seader

2 1

Upgrading the installation kernel for pxeboot?
by Michael T. Halligan 10 Apr '06

10 Apr '06

I'm trying to track down a problem, and to do this I'd like to upgrade the kernel before installation. Going from 2.6.5 (the kernel that SLES9 is sadly stuck at) to 2.6.16 (latest kernel) means that my sata controller starts getting addresses as /dev/sd* instead of /dev/hd*. So, my question is, what's involved in upgrading the kernel? Can I merely change the kernel, and mount the intrd to change themodules, or is there a cleaner way to do this? perhaps a script that exists which SuSE uses when they generate their installation environment? Michael T. Halligan ------------------------------------- BitPusher, LLC http://www.bitpusher.com/

1 0

RE: [suse-autoinstall] Autoyast including latest patches
by Frank van Tol 07 Apr '06

07 Apr '06

The patches are installed once, but a lot packages get installed as an rpm and once more in an update, more often than not close to the size of the original rpm. -----Original Message----- From: Peter Schwenk [mailto:schwenk@UDel.Edu] Sent: vrijdag 7 april 2006 16:19 To: Frank van Tol Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Autoyast including latest patches Why are they getting installed twice? Installing all the available patches takes some time anyway. Last time I looked there were 100 or so. I have my SuSE_10 patches on an NFS share, and I run online_update -V -u 'nfs://<file server IP>/path/to/patches' , and it runs like a charm. Patches are only getting installed once. On Apr 7, 2006, at 3:17 AM, Frank van Tol wrote: > > I use SuSe 10 and the init-script route is what I use now (I'd have > mentioned that) but that means that a lot (big) packages get installed > 2x, adding something like up to 10 minutes to the process. -- - Peter Schwenk - CITA-3, Systems Administrator - Mathematical Sciences - University of Delaware - (302) 831-0437 - schwenk _at_ math _dot_ udel _dot_ edu - http://www.math.udel.edu/~schwenk

2 1

RE: [suse-autoinstall] Autoyast including latest patches
by Frank van Tol 07 Apr '06

07 Apr '06

I use SuSe 10 and the init-script route is what I use now (I'd have mentioned that) but that means that a lot (big) packages get installed 2x, adding something like up to 10 minutes to the process. -----Original Message----- From: Peter Schwenk [mailto:schwenk@UDel.Edu] Sent: donderdag 6 april 2006 17:30 To: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Autoyast including latest patches I've done this using an init-script. Hopefully, you are using a version of SuSE that has init-scripts during autoyast. init-script is nice because it runs during the first boot of the fully-configured system, so you have network and everything. It made doing an 'online_update' a no-brainer. On Apr 6, 2006, at 8:21 AM, Frank van Tol wrote: > > Is it possible to use autoyast to install a desktop including the > latest patches for the installed packages ? > So really combine autoyast + you in one go, assuming I have the CD and > latest patches downloaded to a server. > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > -- - Peter Schwenk - CITA-3, Systems Administrator - Mathematical Sciences - University of Delaware - (302) 831-0437 - schwenk _at_ math _dot_ udel _dot_ edu - http://www.math.udel.edu/~schwenk -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

Re: [suse-autoinstall] Where are instorder and order in SLES 10?
by Uwe Gansert 06 Apr '06

06 Apr '06

On Monday 13 March 2006 16:25, Klaus Kaempf wrote: > > you are right, yast/order and yast/instorder will not work for SLES10 > > I'll try to find out how the new resolver wants that now. > > This will be defined by jsrain(a)suse.cz > He's already working on the new specification. I'll announce the solution here on the mailinglist as soon as the specification is ready. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert(a)suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de

2 1

Autoyast including latest patches
by Frank van Tol 06 Apr '06

06 Apr '06

Is it possible to use autoyast to install a desktop including the latest patches for the installed packages ? So really combine autoyast + you in one go, assuming I have the CD and latest patches downloaded to a server.

2 1

GRUB Loading stage2 -- hangs
by Sean.Gilley＠huntington.com 05 Apr '06

05 Apr '06

I've got an install server set up based upon instructions at http://www.novell.com/coolsolutions/feature/15522.html . I've got all six SLES 9 disks there, plus the three SP3 disks, set up exactly as that page says to do. I've created an install CD on which I've modified boot/loader/isolinux.cfg to add some command line options to the "install" menu item to add networking paramters, autoyast parameters, and also changes the timeout variable to zero. I've also created an "info" file in initrd which contains a single line pointing to an autoyast install file. That file was created from a machine I hand installed. For a while, everything looks as if it works, but after the first reboot, the machine hangs with the following on the screen: GRUB Loading stage2 This has occured on two different machines, it also occurs if I boot the original SLES 9 disk or the SP3 disk, and then autoinstall from the server. If I hand load the machines with the disks, everything works just fine. I'm lost as to how to debug this. Any help would be appreciated. Thanks, Sean. --- Sean L. Gilley Senior Systems Administrator 614-331-9468, 614-374-7573 (mobile) My idea of art probably isn't your idea of art. But no matter how much I dislike the art you admire, I will never seek to have it banned. I only ask you do the same for me. Quiz. Translate: 3 W on a T

1 0

Re: WELCOME to suse-autoinstall@suse.com
by Bhargavi 05 Apr '06

05 Apr '06

On Wednesday 05 April 2006 12:09, suse-autoinstall-help(a)suse.com wrote: > Hi! This is the ezmlm program. I'm managing the > suse-autoinstall(a)suse.com mailing list. > > I'm working for my owner, who can be reached > at suse-autoinstall-owner(a)suse.com. > > Acknowledgment: I have added the address > > bhargavi_karanam(a)infosys.com > > to the suse-autoinstall mailing list. > > Welcome to suse-autoinstall(a)suse.com! > > Please save this message so that you know the address you are > subscribed under, in case you later want to unsubscribe or change your > subscription address. > > To unsubscribe, send a message to: > > <suse-autoinstall-unsubscribe-bhargavi_karanam=infosys.com(a)suse.com> > > Please read the following frequently asked, frequently asked questions > before posting to the list. As with any mailing list or newsgroup, > it's usually a good idea to read the list for a few days before > posting. > > Please do not send test messages to the list -- it's annoying and rude. > Instead, use our test list. Send an email to > test-list-subscribe(a)suse.com > and reply to the confirmation request you will receive (just like you > did to subscribe to suse-autoinstall). To unsubscribe, send an email to > test-list-unsubscribe(a)suse.com > or do nothing...you'll be automatically unsubscribed within 24 hours. > > > ----Some Frequently Asked, Frequently Asked Questions > > > Q1. What is the suse-autoinstall mailing list? > A1. suse-autoinstall is a mailing list devoted to auto-installation > features in YaST. (YaST2 in particular, but YaST1 auto-install > issues are also open to discussion). > > > Q2. What is appropriate content for the list? > A2. Information, discussion and announcements regarding auto-installation > with SuSE Linux. > > > Q3. What is not appropriate content for the list? > A3. Commercial postings of any kind, job postings, non-computer/Linux > related material. > > Q4. How can I retrieve the FAQ? > A4. Send an email to suse-autoinstall-faq(a)suse.com > > Q5. Can I send attachments to the list? > A5. The short answer is 'no', you can't but see the FAQ more details. > > Q6. Are there archives of the list? > A6. Yes, http://lists.suse.com/archive/suse-autoinstall/ > Currently, they are not searchable. > > Q7. Why do my replies go to the original poster and not the list? > A7. There is a more complete answer in FAQ, but the short answer > is that it's better this way. Trust us on this one, please. > > Q8. Can I get the list in digest form? > A8. Not from us. There's a much more complete discussion about > this in the FAQ as well. > > Q9. How do I pause deliveries from the list while I'm on vacation? > A9. You unsubscribe before you leave and resubscribe when you return. > > Q10. How do I contact a human regarding a problem I'm having with > the list? > A10. Send an email to suse-autoinstall-owner(a)suse.com > > > --- Administrative commands for the suse-autoinstall list --- > > I can handle administrative requests automatically. Please > do not send them to the list address! Instead, send > your message to the correct command address: > > For help and a description of available commands, send a message to: > <suse-autoinstall-help(a)suse.com> > > To subscribe to the list, send a message to: > <suse-autoinstall-subscribe(a)suse.com> > > To remove your address from the list, just send a message to > the address in the ``List-Unsubscribe'' header of any list > message. If you haven't changed addresses since subscribing, > you can also send a message to: > <suse-autoinstall-unsubscribe(a)suse.com> > > For addition or removal of addresses, I'll send a confirmation > message to that address. When you receive it, simply reply to it > to complete the transaction. > > If you need to get in touch with the human owner of this list, > please send a message to: > > <suse-autoinstall-owner(a)suse.com> > > Please include a FORWARDED list message with ALL HEADERS intact > to make it easier to help you. > > --- Enclosed is a copy of the request I received. > > Return-Path: <Bhargavi_Karanam(a)infosys.com> > Received: (qmail 16275 invoked from network); 5 Apr 2006 06:39:56 -0000 > Received: from unknown (HELO Relay1.suse.de) (195.135.221.8) > by 0 with SMTP; 5 Apr 2006 06:39:56 -0000 > Received: from Relay1.suse.de (localhost [127.0.0.1]) > by Relay1.suse.de (Postfix) with ESMTP id 25F336957A > for > <suse-autoinstall-sc.1144218924.dbnonccoihhanbgjbnnf-bhargavi_karanam=infos >ys.com(a)lists.suse.com>; Wed, 5 Apr 2006 08:39:56 +0200 (CEST) Received: > from Relay1.suse.de ([127.0.0.1]) > by Relay1.suse.de (Relay1 [127.0.0.1]) (amavisd-new, port 10026) with > ESMTP id 01170-11 > for > <suse-autoinstall-sc.1144218924.dbnonccoihhanbgjbnnf-bhargavi_karanam=infos >ys.com(a)lists.suse.com>; Wed, 5 Apr 2006 08:39:55 +0200 (CEST) > Received: from mx1.suse.de (mx1.suse.de [195.135.220.2]) > (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) > (No client certificate requested) > by Relay1.suse.de (Postfix) with ESMTP id CA95061A13 > for > <suse-autoinstall-sc.1144218924.dbnonccoihhanbgjbnnf-bhargavi_karanam=infos >ys.com(a)lists.suse.com>; Wed, 5 Apr 2006 08:39:55 +0200 (CEST) Received: > from Kecgate06.infosys.com (kecgate06.infosys.com [61.95.162.82]) by > mx1.suse.de (Postfix) with ESMTP id A57A2EABB > for > <suse-autoinstall-sc.1144218924.dbnonccoihhanbgjbnnf-bhargavi_karanam=infos >ys.com(a)suse.com>; Wed, 5 Apr 2006 08:39:54 +0200 (CEST) Received: from > INDHUBBHS02.ad.infosys.com ([192.168.200.82]) by Kecgate06.infosys.com with > InterScan Messaging Security Suite; Wed, 05 Apr 2006 12:09:26 +0530 > Received: from BLRKECMSG14.ad.infosys.com ([172.22.147.6]) by > INDHUBBHS02.ad.infosys.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 5 > Apr 2006 12:09:15 +0530 > Received: from BLRKECOWA01.ad.infosys.com ([192.168.200.65]) by > BLRKECMSG14.ad.infosys.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 5 > Apr 2006 12:09:15 +0530 > Received: from myshec44234d.ad.infosys.com ([172.22.10.39]) by > BLRKECOWA01.ad.infosys.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 5 > Apr 2006 12:09:15 +0530 > From: Bhargavi <bhargavi_karanam(a)infosys.com> > Organization: Infosys > To: > suse-autoinstall-sc.1144218924.dbnonccoihhanbgjbnnf-bhargavi_karan(a)suse.de, > am=infosys.com(a)suse.com > Subject: Re: confirm subscribe to suse-autoinstall(a)suse.com > Date: Wed, 5 Apr 2006 12:09:56 +0530 > User-Agent: KMail/1.8.2 > References: <1144218924.11198.ezmlm(a)suse.com> > In-Reply-To: <1144218924.11198.ezmlm(a)suse.com> > MIME-Version: 1.0 > Content-Type: text/plain; > charset="iso-8859-1" > Content-Transfer-Encoding: 7bit > Content-Disposition: inline > Message-Id: <200604051209.56920.bhargavi_karanam(a)infosys.com> > X-OriginalArrivalTime: 05 Apr 2006 06:39:15.0208 (UTC) > FILETIME=[A8286880:01C6587B] X-Virus-Scanned: by amavisd-new at > Relay1.suse.de > X-Spam-Status: No, hits=0.2 tagged_above=-20.0 required=5.0 tests=BAYES_50, > DNS_FROM_RFC_ABUSE > X-Spam-Level: > > On Wednesday 05 April 2006 12:05, suse-autoinstall-help(a)suse.com wrote: > > Hi! This is the ezmlm program. I'm managing the > > suse-autoinstall(a)suse.com mailing list. > > > > I'm working for my owner, who can be reached > > at suse-autoinstall-owner(a)suse.com. > > > > To confirm that you would like > > > > bhargavi_karanam(a)infosys.com > > > > added to the suse-autoinstall mailing list, please send > > an empty reply to this address: > > > > > > suse-autoinstall-sc.1144218924.dbnonccoihhanbgjbnnf-bhargavi_karanam=info > >sy s.com(a)suse.com > > > > Usually, this happens when you just hit the "reply" button. > > If this does not work, simply copy the address and paste it into > > the "To:" field of a new message. > > > > or click here: > > mailto:suse-autoinstall-sc.1144218924.dbnonccoihhanbgjbnnf-bhargavi_kara > >na m=infosys.com(a)suse.com > > > > This confirmation serves two purposes. First, it verifies that I am able > > to get mail through to you. Second, it protects you in case someone > > forges a subscription request in your name. > > > > > > --- Administrative commands for the suse-autoinstall list --- > > > > I can handle administrative requests automatically. Please > > do not send them to the list address! Instead, send > > your message to the correct command address: > > > > For help and a description of available commands, send a message to: > > <suse-autoinstall-help(a)suse.com> > > > > To subscribe to the list, send a message to: > > <suse-autoinstall-subscribe(a)suse.com> > > > > To remove your address from the list, just send a message to > > the address in the ``List-Unsubscribe'' header of any list > > message. If you haven't changed addresses since subscribing, > > you can also send a message to: > > <suse-autoinstall-unsubscribe(a)suse.com> > > > > For addition or removal of addresses, I'll send a confirmation > > message to that address. When you receive it, simply reply to it > > to complete the transaction. > > > > If you need to get in touch with the human owner of this list, > > please send a message to: > > > > <suse-autoinstall-owner(a)suse.com> > > > > Please include a FORWARDED list message with ALL HEADERS intact > > to make it easier to help you. > > > > --- Enclosed is a copy of the request I received. > > > > Return-Path: <bhargavi_karanam(a)infosys.com> > > Received: (qmail 11171 invoked from network); 5 Apr 2006 06:35:24 -0000 > > Received: from unknown (HELO Relay2.suse.de) (195.135.221.8) > > by 0 with SMTP; 5 Apr 2006 06:35:24 -0000 > > Received: from Relay2.suse.de (localhost [127.0.0.1]) > > by Relay2.suse.de (Postfix) with ESMTP id 47E696A848 > > for <suse-autoinstall-subscribe(a)lists.suse.com>; Wed, 5 Apr 2006 > > 08:35:24 +0200 (CEST) Received: from Relay2.suse.de ([127.0.0.1]) > > by Relay2.suse.de (Relay2 [127.0.0.1]) (amavisd-new, port 10026) with > > ESMTP id 03932-12 for <suse-autoinstall-subscribe(a)lists.suse.com>; > > Wed, 5 Apr 2006 08:35:24 +0200 (CEST) > > Received: from mx2.suse.de (cantor2.suse.de [195.135.220.15]) > > (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) > > (No client certificate requested) > > by Relay2.suse.de (Postfix) with ESMTP id 130CC6A833 > > for <suse-autoinstall-subscribe(a)lists.suse.com>; Wed, 5 Apr 2006 > > 08:35:24 +0200 (CEST) Received: from turing.suse.de (turing.suse.de > > [195.135.220.3]) by mx2.suse.de (Postfix) with ESMTP id E166A1D7C4 > > for <suse-autoinstall-subscribe(a)suse.com>; Wed, 5 Apr 2006 08:35:23 > > +0200 (CEST) Content-Disposition: inline > > Content-Transfer-Encoding: quoted-printable > > Content-Type: text/plain > > MIME-Version: 1.0 > > X-Mailer: MIME::Lite 2.117 (F2.71; T0.16; A1.47; B2.12; Q2.03) > > Date: Wed, 5 Apr 2006 06:35:23 UT > > From: bhargavi_karanam(a)infosys.com > > To: suse-autoinstall-subscribe(a)suse.com > > Message-Id: <20060405063523.C4BB12EA00(a)turing.suse.de> > > X-Virus-Scanned: by amavisd-new at Relay2.suse.de > > X-Spam-Status: Yes, hits=5.3 tagged_above=-20.0 required=5.0 > > tests=BAYES_50, DNS_FROM_RFC_ABUSE, EMPTY_MESSAGE, MISSING_SUBJECT, > > NO_REAL_NAME > > X-Spam-Level: ***** > > Subject: SPAM: > > X-Spam-Flag: YES > > **************** CAUTION - Disclaimer ***************** > This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended > solely for the use of the addressee(s). If you are not the intended > recipient, please notify the sender by e-mail and delete the original > message. Further, you are not to copy, disclose, or distribute this e-mail > or its contents to any other person and any such actions are unlawful. This > e-mail may contain viruses. Infosys has taken every reasonable precaution > to minimize this risk, but is not liable for any damage you may sustain as > a result of any virus in this e-mail. You should carry out your own virus > checks before opening the e-mail or attachment. Infosys reserves the right > to monitor and review the content of all messages sent to or from this > e-mail address. Messages sent to or from this e-mail address may be stored > on the Infosys e-mail system. ***INFOSYS******** End of Disclaimer > ********INFOSYS***

1 0

add repository possible in 10.1?
by Andreas Vetter 04 Apr '06

04 Apr '06

Hi, 10.1 has the nice feature that you can add repositories before installation. Is this possible with 10.1 autoyast, too? Regards, Andreas -- Andreas Vetter

1 0