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!
Repository Priority is obviously a useful thing to be able to
manipulate. Yast lets me set it and zypper lets me set it.
Yet, if I have multiple repositories defined at the beginning
of my autoyast (including update repos so I get an up to date
system built out of the box), I don't seem to have any control
over the respective repository priorities - they're all defaulted.
Or did I miss a subtle option somewhere?
Tim
--
Tim Kirby 651-605-9074
trk(a)cray.com Cray Inc. Information Systems
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hello,
someone may start to laugh now for my (OT) question, but I can't find a
satisfying solution :-/
How do you manage patches, updates, etc. for your running opensuse
clients (not enterprise linux, just the "regular" opensuse distribution)?
Is there a way like known from M$-World (WSUS)? As I know "Zend
Management Server" is not open source (and not supported any more?!).
Or can the complete management only be handled with self written scripts?
Thanks!
Regards,
Ivan
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hi,
I try to install sles 11 via autoyast. I did an installation from dvd,
and pulled an autoyast profile. This profile works, and can be installed
via pxe.
Now I want to add the following packages:
findutils-locate, dhcp-server, bind, apache2, vsftpd, nfs-kernel-server
I do this via the gui. I have also tried to do it with an editor, as the
gui messed up profiles in sles10sp2.
In both cases, after the first reboot, I get the errormessage:
"The package resolver run failed. Please check your software section in
the aut" [oyast profile] (last part invisible, I guess it should be the
software section in my autoyast profile :-))
This a real problem, as I have to confirm this message, thus it stops
the autoinstall process.
After confirming, the autoinstall process continues. Right bevor I can
log in, I get
"Could not update ICEauthority file /var/lib/gdm/.ICEauthority"
I confirm, and get:
"There is a problem with the configuration server.
(/usr/lib/GConf/2/gconf-sanity-check-2 exited with status 256)"
I confirm, and can log in. Theses messages are presistend after reboot.
Its annoying, but not a stopper like the first problem.
Why is this? Can I avoid this?
Isaac
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hi,
well, it's not that it can read XML files from a twitter feed now ;) but after the blog(*), starting from today, AutoYaST goes one further step to web 2.0 and has it's own twitter account (**).
It's not for great hints or enhanced support or so. It's just a little look behind the curtain of my life with AutoYaST ... for those who care ;)
And it seems you can't do any bigger project these days without something like a blog, twitter or facebook or ... so ... here it is.
(*) http://ugansert.blogspot.com
(**) http://twitter.com/autoyast
ciao, Uwe Gansert
Uwe Gansert, Server Technologies Team
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Business: http://www.suse.de/~ug
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
hi all,
I apologize, this is not a real autoyast questions but you may have some pointers for me.
We are using autoyast to install different SLED releases. My problem is that for higher SP releases the "updates" repo from Novell grows quite big, most of the packages have several different versions in the repo. For SP3, there are more than 10.000 rpms in updates.
What I'm looking for is a script that can help me to find/remove obsolete rpms. Do you know any?
thanks,
Miki
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Thank you for responding.
>>> On 6/17/2010 at 16:39, Uwe Gansert <ug(a)suse.de> wrote:
> on Thursday 17 June 2010 Andreas Taschner wrote:
>
>> I am trying to duplicate a problem at a customer that has a RAID1 setup
>> with /boot, / and other partitions on md. For this I install SLES10SP2 as
>> step one and upgrade to SLES10SP3 as step2. Doing this manually works
>> fine, but when installing SP2 or upgrading to SP3 using AutoYaST, the
>
> how do you upgrade with autoyast? you leave the partitioning as it is but
> format all system-relevant parts?
If we stick to the installation of SP2 for now, then I format md* and initialize both physical drives (added the initialize manually).
Changing persistent_superblock from false to true has not changed the situation.
What I find really strange about the upgrade profile (generated as the last step during the upgrade) also formats all partitions ???
So that one would probably never work anyway...
I have attached an archive of the partition tag of both SP2 installation and SP2-->SP3 profiles.
>
>> /boot/grub/menu.lst refers to /dev/md? and I have tried configuring
>> device.map to map to both /dev/sd? and /dev/disk/by-id/*. Another funny
>> observation : Switching the bootable flag from sdb1 to sda1 changes the
>> boot error from "Invalid partition able" to "No operating system"
>>
>> So it looks like the RAID setup somehow does not make it to disk when using
>> AutoYaST.
>>
>> Any ideas ?
>
> the only idea and bug that comes close to it is
> https://bugzilla.novell.com/show_bug.cgi?id=581523
> it's about LVM but RAID was affected too.
> SP3 accidently pulls in multipath drivers into the ramdisk and those make
> trouble during the reboot.
> But actually your sympthons are a bit different, so I have doubts that you
> hit
> that problem.
Thank you for any inspiration.
//Andreas
Hi,
I am trying to install custom packages using add_on_products.
I am creating my own install dvd:
- as a base SLES10 SP3 is used,
- i copy the dvd to some directory DVD_REP,
- then i create then updates directory stucture there with
create_update_source.sh(http://www.suse.com/~ug/)
- then i create new DVD with mkisofs -R DVD_REP(so updates directory
is the same medium as SLES)
- then I want to instruct autoyast.xml to take this into
consideration, this should be present in add_on_products file on my
DVD
media_url [path_on_media [product_1 [product_2 [....]]]
My question is:
How should media_url look like, when my update source is on the same
DVD as SLES10 SP3?
Next question is where can I specify that my my_test.rpm should be
installed, can I do it in software section
<software>
<packages config:type="list">
<package>my_test</package>
</packages>
</software>
and installation process will search updates directory for this rpm?
Regards,
Vladimir Ondrus
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
I have an autoyast-based installation that needs to be split into CDs,
and possibly remove unneeded packages. Is there a tool for that?
--
-- Erico
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hi there...
I'm currently trying to include an additional repository on a custom
installation ISO with autoyast. Basically I'm copying the directory to
the root of the media, and would like to include it as a valid package
repo (it's already an YUM repo).
I placed this in the autoyast XML:
<add-on>
<add_on_products config:type="list">
<listentry>
<media_url>dir:///myrepo</media_url>
<product>Custom-REPO</product>
<product_dir>/</product_dir>
<name>Custom packages</name>
</listentry>
</add_on_products>
</add-on>
and placed my repository on the /myrepo directory on the media.
However, it won't find/recognize this as a valid repo. I get a "Failed
to add add-on product" error.
I already tried other URL schemes as well, like file://. What am I missing here?
--
-- Erico
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org