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!
Hello,
I'm trying to have autoyast setup some LVM volume groups. I can get
things setup with a single volume group, but if try to add 2 volume
groups I seem to be running into some issue.
I'm using the following xml inside the partitioning section to setup
the PVs and add to the volume groups.
.
.
.
<drive>
<device>/dev/sdb</device>
<partitions config:type="list">
<partition>
<lvm_group>firstvg</lvm_group>
<partition_type>primary</partition_type>
<size>max</size>
</partition>
</partitions>
<use>all</use>
</drive>
<drive>
<device>/dev/sdc</device>
<partitions config:type="list">
<partition>
<lvm_group>secondvg</lvm_group>
<partition_type>primary</partition_type>
<size>max</size>
</partition>
</partitions>
<use>all</use>
</drive>
.
.
.
The problem is that both disks are configured as PVs in the same VG.
Both sdb and sdc will be added to firstvg and secondvg will not exist.
Am I trying this wrong or am I hitting some sort of bug?
thanks
--
bigbeer
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
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,
we are configuring systems using ayast_setup with a predefined profile. up
to SLES 11.0 all was fine.
Now we are running SLES11SP1 and we now are unable to configure the dump
device using the <kdump> directive.
It really doesn't seem to matter what parameters we put in to this directive
, it just looks like the kdump directive is ignored by ayast_setup.
The file /etc/sysconfig/kdump which should be adjusted with the parameters
used in the the directive remains unchanged.
The y2log doesn't show any references to kdump at all.
Is there anyone on this mailinglist who also have seen this behaviour and
is there a solution known maybee ?
Íf any more information is needed to solve this issue I'm happy to provide
these.
Thanks in advance for any help on this issue.
Ron van Holk
ING
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Background: I have a basic CD-ROM autoinstall working for SLES 11
SP1. Now I am trying to add updates.
I have followed the instructions here:
http://www.suse.com/~ug/AutoYaST_FAQ.html#b8
...to create a custom CD-ROM with a properly constructed "updates"
directory. But I am having trouble figuring out what to use for the
<media_url> in the <add-on> section of my autoinst.xml file.
I boot my CD with "autoyast=file:///autoinst.xml", and that correctly
finds the autoinst.xml file in the root of the CD. So I figured I
could just say:
<add-on>
...
<media_url>file:///updates</media_url>
...
</add-on>
That is, since "file:///autoinst.xml" refers to the autoinst.xml file
at the root of the CD, I was expecting "file:///updates" to refer to
the updates directory also at the root of the CD.
But when I try this, I get an error: "Failed to add add-on product."
So my question is, what URL should I use to reference an add-on
product on my CD-ROM? If "file:///updates" is supposed to work, how
should I go about debugging this?
Thanks!
- Pat
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
I need to only format a couple of disks, mount them and place a few
files in one of the partitions. I already have an autoyast XML that
does what I want, partition-wise.
Is it possible to just apply the partitioning scheme to the disks with
AutoYaST? No software installation at all.
--
-- Erico
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hi,
I need to create a driver update disk for SLED11-sp1 to include some updated
yast modules at install time.
Are there any docs anywhere on how to create a DUD ? I've seen very rough ones
out there for sle10, but nothing for sle11.
Thanks
--
Simon Crute
ACS Information Technologies UK Ltd. A Xerox company
working on behalf of Novell IS&T
+44-(0)-1344-326-313 (desk)
+44-(0)-7733-106041 (mobile)
SameTime: Simon Crute
GWIM: scrute.novell
MSN: simon.crute(a)snccc.co.uk
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Re-sending to the list without HTML...
2010/11/19 Erico Mendonça <erico.mendonca(a)gmail.com>
>
>
> On Thu, Nov 18, 2010 at 5:49 PM, Patrick J. LoPresti <lopresti(a)gmail.com> wrote:
>>
>> So my question is, what URL should I use to reference an add-on
>> product on my CD-ROM? If "file:///updates" is supposed to work, how
>> should I go about debugging this?
>
>
> I use it like this:
>
> <add-on>
> <add_on_products config:type="list">
> <listentry>
> <media_url>cd:///myaddon</media_url>
> <product>MyAddon</product>
> <product_dir>/</product_dir>
> <name>My own add-on</name>
> <signature-handling>
> <accept_unsigned_file config:type="boolean">true</accept_unsigned_file>
> <accept_verification_failed config:type="boolean">true</accept_verification_failed>
> </signature-handling>
> </listentry>
> </add_on_products>
> </add-on>
>
>
> This allows me to place my own unsigned repository (created with createrepo) on the root of the CDROM (at /myaddon).
>
> --
> -- Erico
--
-- Erico
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Greetings,
is it possible to skip steps of the installation procedure, like
partitioning and software installation?
I'm trying to set up an autoyast profile (for an installation CD) that
basically just asks a few (network) values in the initial stage,
patches them back into the bootloader section of the profile and then
just installs the bootloader with these values, skipping everything
else. After reboot, the machine uses the boot parameters to fetch the
"real" installation profile from a server and does a "normal"
installation. (After installation, the machines will be managed by
bcfg2.)
The reason I'm trying to do this is twofold: First, I have to give
those discs out to users and would like to never change them, if
possible. Thus, the split-up between "bootstrap" and the real,
changeable, profile on the network. Second, it is unlikely these users
will have DHCP available, and I don't want them having to type endless
boot parameters like
hostip=1.2.3.4 netmask=255.255.255.0 gateway=1.2.3.1
install=http://network-repo/... autoyast=http://network-source/...
So, is this possible with autoyast, or do I have to resort to putting
more complexity on the CD, (changing things after installation with
bcfg2) and possibly sending out new discs for profile
errors/enhancements and new openSUSE releases?
thanks,
686f6c6d
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org