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!
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.
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
Hi,
I'm posting this as a follow-up to older posts I found on the mailing-
list archives regarding problems with nfs during the autoinstall
procedure (and possibly related topics) with 10.3. The posts I'm
referring to are:
http://lists.opensuse.org/opensuse-autoinstall/2007-10/msg00031.htmlhttp://lists.opensuse.org/opensuse-autoinstall/2007-10/msg00007.html
and possibly:
http://lists.opensuse.org/opensuse-autoinstall/2007-10/msg00010.html
I found a solution to start the nfs-mount manually and described this
in:
http://forums.suselinuxsupport.de/index.php?act=ST&f=20&t=63305
However, this is merely a workaround and identifies the source of the
problem, while I still don't know how to automize this in a fashion,
such that the autoinstallation procedure runs clean without stopping
and returning errors in between. Furthermore I do understand, from
what a learned from the first mentioned reference, that Uwe Gansert
already has a solution to this problem. I would be very interested in
learning more about this, since I unfortunately couldn't find any
description of such a solution.
many thanks
Vincent David
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hi
I've been looking over the documentation for <ask> at http://newsportal.novell.com/article.php?id=1565&group=novell.support.sles.… - but it leave's me with several questions (sorry for my ignorance, I'm new to all this autoyast stuff ;) )
- if I use the "<file>/tmp/answer_hostname</file>", what is the format of the answer file?? just an empty text file with the answer or?
- what about the value to be exchanged? should it be empty, or will any predefined value be exchanged with the one asked for?
- Will it be possible to answer serveral "paths" with the same question?? eg. below
<ask>
<path>arkmanager,dbpassword</path>
<path>ca_mgm,password</path>
<question>Type Password</question>
<stage>initial</stage>
<default>Type in your password here</default>
</ask>
or is there, a more clever solution to such a question?
- How about the password... is it possible to get this read from an clear text string? (I'm installing OES2, and there are several passwords and some are written in clear text, and some ain't)
regards
Flemming
(Terribly sorry if my post occurs twice, haven't noticed the no HTML part at first)
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
I am using SLES 10 SP1 and AutoYaST. I have my autoyast profile setup to configure Novell Customer Center with the correct registration code and I verified that my server gets registered with NCC. Now I'd like to have AutoYaST install all the latest patches at the appropriate place during auto-installation. Is this possible?
Thanks,
Chris
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
First, thanks for the help on figuring out how to create an ask-list. I
have it working now. I am asking several questions on install that are
related.
When I have each question in it's own dialog everything is working
great. As the questions are related I want to put them in grouped
dialog boxes. When I do this, I seem to be getting corrupted answers.
I grouped them by simply adding the dialog key to each stand alone
question set.
My ask section looks like this:
<ask-list config:type="list">
<ask>
<dialog config:type="integer">1</dialog>
<path>networking,dns,hostname</path>
<question>Enter Hostname (without domain)</question>
<stage>cont</stage>
<default></default>
</ask>
<ask>
<dialog config:type="integer">1</dialog>
<path>networking,dns,domain</path>
<question>Enter Domain (ex: level3.net)</question>
<stage>cont</stage>
<default></default>
</ask>
<ask>
<dialog config:type="integer">2</dialog>
<path>networking,interfaces,0,ipaddr</path>
<question>Enter IPv4 address</question>
<stage>cont</stage>
</ask>
<ask>
<dialog config:type="integer">2</dialog>
<path>networking,interfaces,0,netmask</path>
<question>Enter netmask </question>
<stage>cont</stage>
<default>255.255.255.0</default>
</ask>
<ask>
<dialog config:type="integer">2</dialog>
<path>networking,routing,routes,0,gateway</path>
<question>Enter default IPv4 gateway</question>
<stage>cont</stage>
</ask>
...
Anything jump out as a problem?
I am seeing the 1st answer come out correct, but the subsequent ones do
not...
Thanks!
--
Andrew
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Im tring to create a virtual machine using Xen in openSUSE 10.3 using
the Xen Virtual Machine Manager in Yast. In creating the virtual
machine, I specify the location of the 10.3 (32 bit) iso and the
location of the autoyast profile in the appropriate text boxes.
In my autoyast profile, I specify the add-on repositories I would like
to add. Below are portions of the autoyast xml profile.
After the autoyast installer runs, and the virtual machine boots, I
look in Yast2->Software->Software Repositories to find that the add-on
repositories have not been added.
Without the <signature-handling> stanza inside of <add_on_products>,
no error dialog is produced during, but after installation finishes,
the repositories are not available.
With the <signature-handling> stanza inside of <add_on_products> an
error dialog appears saying "Error: Failed to add add-on product".
I have read section "4.5.4. Installing additional and customized
Packages" in the autoyast documentation at:
http://forgeftp.novell.com/yast/doc/SL10.3/autoinstall/CreateProfile.Softwa…
and believe that I am following the instructions correctly.
Is there something clearly wrong with my profile? How can I fix it so
that my add-on repositories are available once the installation is
complete?
<?xml version="1.0"?>
<!DOCTYPE profile>
<profile xmlns="http://www.suse.com/1.0/yast2ns"
xmlns:config="http://www.suse.com/1.0/configns">
<add-on>
<add_on_products config:type="list">
<listentry>
<media_url>http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_10.3/</media_url>
<product>Build Service Repository</product>
<product_dir>/</product_dir>
</listentry>
<listentry>
<media_url>http://download.opensuse.org/repositories/ruby/openSUSE_10.3/</media_url>
<product>Ruby Repository</product>
<product_dir>/</product_dir>
</listentry>
<signature-handling>
<accept_file_without_checksum
config:type="boolean">true</accept_file_without_checksum>
<accept_non_trusted_gpg_key
config:type="boolean">true</accept_non_trusted_gpg_key>
<accept_unknown_gpg_key
config:type="boolean">true</accept_unknown_gpg_key>
<accept_unsigned_file config:type="boolean">true</accept_unsigned_file>
<accept_verification_failed
config:type="boolean">true</accept_verification_failed>
<import_gpg_key config:type="boolean">true</import_gpg_key>
</signature-handling>
</add_on_products>
</add-on>
..... some xml ...
<general>
..... some xml ...
<signature-handling>
<accept_file_without_checksum
config:type="boolean">true</accept_file_without_checksum>
<accept_non_trusted_gpg_key
config:type="boolean">true</accept_non_trusted_gpg_key>
<accept_unknown_gpg_key
config:type="boolean">true</accept_unknown_gpg_key>
<accept_unsigned_file config:type="boolean">true</accept_unsigned_file>
<accept_verification_failed
config:type="boolean">true</accept_verification_failed>
<import_gpg_key config:type="boolean">true</import_gpg_key>
</signature-handling>
</general>
..... more xml ...
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
unsubscribe opensuse-autoinstall(a)opensuse.org
--
This e-mail is intended exclusively for the addressee(s), and may not be
passed on to, or made available for use by any person other than the
addressee(s). Siennax rules out any and every liability resulting from
any electronic transmission.
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hi,
autoupdater on a opensuse 10.3 64 bit system has just uninstalled
libzypp and zypper on my system, caused by an autoupdate of boost, which
has unsolved dependencies. That's quite bad, because anyone who's new to
linux is left without the possibility of easy software installation.
> #### YaST2 conflicts list - generated 2007-11-16 21:11:38 ####
>
> Can't satisfy requirement libboost_filesystem.so.1.33.1()(64bit) for libzypp-3.26.3-1.1.x86_64
>
> === libzypp-3.26.3-1.1.x86_64 ===
> boost-1.33.1-108.x86_64 provides libboost_filesystem.so.1.33.1()(64bit), but is scheduled to be uninstalled.
> boost-1.33.1-108.x86_64[http://download.opensuse.org/repositories/openSUSE:… provides libboost_filesystem.so.1.33.1()(64bit), but another version of that package is already installed.
> libzypp-3.26.3-1.1.x86_64 depends on boost
> libzypp-3.26.3-1.1.x86_64 is lacking the requirement libboost_filesystem.so.1.33.1()(64bit)
> (null)
> Conflict Resolution:
> ( ) delete libzypp
> ( ) Ignore this requirement just here
> ( ) Generally ignore this requirement
> Can't satisfy requirement libboost_regex.so.1.33.1()(64bit) for zypper-0.8.25-0.1.x86_64
>
> === zypper-0.8.25-0.1.x86_64 ===
> boost-1.33.1-108.x86_64 provides libboost_regex.so.1.33.1()(64bit), but is scheduled to be uninstalled.
> boost-1.33.1-108.x86_64[http://download.opensuse.org/repositories/openSUSE:… provides libboost_regex.so.1.33.1()(64bit), but another version of that package is already installed.
> zypper-0.8.25-0.1.x86_64 depends on boost
> zypper-0.8.25-0.1.x86_64 is lacking the requirement libboost_regex.so.1.33.1()(64bit)
> (null)
> Conflict Resolution:
> ( ) delete zypper
> ( ) Ignore this requirement just here
> ( ) Generally ignore this requirement
> No valid solution found with just resolvables of best architecture.
> With this run only resolvables with the best architecture have been regarded.
> Regarding all possible resolvables takes time, but can come to a valid result.
> Conflict Resolution:
> ( ) Make a solver run with ALL possibilities.
>
> #### YaST2 conflicts list END ###
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org