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
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
Hi,
I'm currently building a SLES11 SP1 Image and using this customized CD
for a pxe boot.
During boot and scanning the /add_on_products.xml file the installation
complains about the repository.
In the y2log these comments werde made:
---- snip
Callback ImportGpgKey not registered, using default value: false
(verifyFileSignatureWorkflow):417 User does not want to trust key
62A0C0D5C5....
---- snip
Where is the switch to trust the key?
The installation procedure then using a profiles directory structure
with the same repositories in. In this case everything works well - In
the profiles xml file the gpg/pgp switch are all set to trust unknown keys.
Thanks in advance
Regards
Ruediger
--
Ruediger Gunreben
--
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
Have enjoyed the YaST add-on-creator and built an add-on with a hello-world package. Impressing tool BTW - must be popular. (Only changed the vendor from the default in the wizard).
Including it in the autoyast profile (for SLES11SP1)
<add_on_products config:type="list">
<listentry>
<media_url>http://atw510.nts.com/Andreas-add-on</media_url>
<product>Andreas-add-on</product>
<product_dir>/</product_dir>
<name>Hello-world-name-addon-product</name>
</listentry>
</add_on_products>
results in the following :
0) The Add-On product is not shown in the package installation window
1) zypper products lists the product, but not as installed
2) The service and repository for the add-on are enabled
3) The package does not get installed automatically
Have I done something wrong in the creation of the add-on, or do I need to modify the profile to explicitly request installation of all/every package in the add-on repo ?
Related question :
Is it possible to have the add-on on a separate DVD (customer needs to install on isolated servers in outposts with no infrastructure) and get the installation flow to eject the installation medium and ask for another DVD ?
Thanks.
Best regards
Andreas
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
I know SLES9u4 is old, and if there is a better mailing list than this
one please re-direct me to it. :)
I'm trying to PXE boot and install SLES9u4, and 32bit works fine, but
the 64bit one invariably gives me these messages during boot up, and
then drops me to a blue curses GUI screen declaring there has been an
error.
I'm not convinced that I didn't do something wrong settingup the NFS
and PXE configs, but I'm at a loss as to where to start debugging this.
What RAMdisk file is it that was loaded right before these errors? the
initrd from grub? or some other install ramdisk?
Any and all help is appreciated!
-Kyle
> TCP: Hash tables configured (established 524288 bind 65536) NET:
> Registered protocol family 1 ACPI: (supports S0 S1 S4 S5) md:
> Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE.
> RAMDISK: Compressed image found at block 0 VFS: Mounted root (minix
> filesystem). Moving into tmpfs... done. ramdisk /dev/ram0 freed
> created /dev tree (14704 inodes)
>>>> SUSE LINUX Enterprise Server 9 installation program v1.6.36
>>>> (c)
> 1996-2004 SUSE LINUX AG <<< [9;0]Starting hardware detection...
> Activating usb devices... done Searching for info file...
> Sending DHCP request to eth0... Driver Update: Service Pack 4
> Loading data into RAM disk... (57950
> kB)............................. creating device nodes ... done
> integrating the shared objects of the installation system...
> /sbin/adddir: line 37: /bin/mv: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 50: /bin/rm: No such file or directory
> /sbin/adddir: line 53: /bin/ln: No such file or directory
> /sbin/adddir: line 1: /bin/mktemp: No such file or directory
> /sbin/inst_setup: line 107: /sbin/checkproc: No such file or
> directory starting syslog (messages are logged to /dev/tty4)...
> /sbin/inst_setup: line 109: /bin/sh: No such file or directory
> /sbin/inst_setup: line 115: /sbin/checkproc: No such file or
> directory starting klogd ... /sbin/inst_setup: line 117:
> /sbin/klogd: No such file or directory /sbin/inst_setup: line 1:
> /bin/uname: No such file or directory integrating kernel modules of
> the installation system... /sbin/inst_setup: line 143: /bin/grep:
> No such file or directory /sbin/inst_setup: line 148: /bin/grep: No
> such file or directory
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (MingW32)
iQEcBAEBAgAGBQJMvvZuAAoJEEADRM+bKN5wzIUH/jgxmXk/zPXXXYlSw/JI/eez
OrfgGKan6q9j8pw/F6di1jMVnYctQONQzYJ/dNRqJe8ZazWYuOOZ+veykKzrHkpX
PUgg/sO/B3Mtbk/JajuHzATaweUZXc+Tz74hZ0dYL804iA3ggol73Xd6hMVrBdk/
8+PyNGZt+Ai5rvPbbVGLYBHK2Z3y1K3DxqF5wVfBvscgg2Vsm47jNoPO8EHirQkV
F3VvhbMlC1mzbBMU/wbbCd8OeG2AKNECEI22B7KJvuh9plm56HTXLa4rYa6yQJZO
D0nIjOYlbGvlOvRrqxGPM/O60UVVUOeNX+EGNMnCiXtoab6k8z+iVSMtaP2rI28=
=Rh14
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hi All,
I'm trying to run yast2 for a specific module in an init-script,
but yast2 complains about the lack of tty.
Does anyone now how to get around this?
One of the commands I'm trying to run is:
yast2 ldap-server service verbose enable
Any input appreciated.
/Lars Stavholm
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org