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
Hi,
here's the problems I ran into. They all seem to be related to
systemd, but I did not want to hijack the other thread, although this
one might solve the other problem, too.
1. The final kexec/reboot is not executed. Both
<final_reboot config:type="boolean">false</final_reboot>,
meaning kexec will be used, and
<final_reboot config:type="boolean">true</final_reboot>
have no effect at all[0]. This also means that...
2. Init-Services (<runlevel>) defined in autoyast are not
started/stopped, so, f.e., no ssh keys are generated. (This also
results in a lot of subsequent errors in our setup.)
To fix this, just include:
<software>
<remove-packages config:type="list">
<package>systemd-sysvinit</package>
</remove-packages>
</software>
This way, sysvinit-init will be installed and used.
When can we expect autoyast to support systemd?
[0]: Once you do a manual reboot (if you happen to have access other
than ssh to the machine), the machine will do the autoyast
kexec/reboot after that.
--
Kind regards/Mit freundlichen Grüßen
Christopher 'm4z' Holm
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org
I'm a new to autoyast (2 weeks). I've setup an install procedure for my hosts
but I still fail to setup properly the printer.
I have a "lpadmin" and a "lpoptions" commands working when run as root after the
final reboot.
I've setup a post-scripts to do this automaticaly but it always fail with:
"lpadmin: Unable to connect to server: Connection refused"
Even if my post-script requires network and start cupsd.
<post-scripts config:type="list">
<script>
<debug config:type="boolean">true</debug>
<filename>imprimantes</filename>
<network_needed config:type="boolean">true</network_needed>
<notification>Please wait while setting up printers ...</notification>
<interpreter>shell</interpreter>
<source><![CDATA[
#!/bin/sh
service cups start
lpadmin -p laser5M -m manufacturer-PPDs/hplip/hp-laserjet_4050_series-ps.ppd.gz
-u allow:all -L "Salle A116" -v socket://batA1-most1.hmg.inpg.fr.:9100 -E
lpoptions -d laser5M -o PageSize=A4 -o HPOption_Duplexer=True -o
InstalledMemory=36MB -o HPOption_Tray3=True -o HPOption_Disk=HardDisk -o
Duplex=DuplexNoTumble
]]>
</source>
</script>
</post-scripts>
Any suggestion is welcome.
Patrick
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org
Hello,
strange problem: I have a autoyast-xml-File (made from a set of
xml-sniplets) which causes a Segfault of yast2 when I load that profile
in yast2-Auto-Installation-Module.
YaST got signal 11 at YCP file Profile.ycp:88
/sbin/yast2: line 423: 31763 Segmentation fault $ybindir/y2base
$module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS
System is openSuSE 11.4, autoyast2-installation-2.20.9-1.2.1,
autoyast2-2.20.9-1.2.1,
Can I check the validity of the profile without Yast?
Regards
Daniel
--
Daniel Spannbauer Software Entwicklung
marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11
Rechbergstr. 4 - 6, D 87727 Babenhausen Mobil +49 171 4033220
http://www.marco.de/ Email ds(a)marco.de
Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org
Hello everyone,
I have the following problem:
We have an autoyast base-profile.xml for all our Linux machines, which
includes
---------
<software>
<remove-packages config:type="list">
<package>NetworkManager</package>
</remove-packages>
</software>
---------
because all those machines use the traditional ifup method.
Now, I want to integrate a mobile workstation, which should use
NetworkManager to manage LAN/WLAN/VPN connections. Thus, I would somehow
have to remove the above entry by merging with another XML. Otherwise I
cannot install NetworkManager as a regular <package>.
I guess that is not possible? I can only add/change entries by merging
with another XMl, but not remove thing... correct?
(Of course I could remove that line from the base-profile.xml, but so
far I'm looking for a better solution)
Is it possible to work on the final installation XML file (after merging
is done) with a pre-script? How would I get the path to that file? So
far, it looks like it is burried somewhere in /tmp/Yast-XXXXXX-YYYYY/
during installation...
Thanks for your help!
Regards, Joschi Brauchle
Hello,
yes, I know, it is a known bug. But I have to install some packages as
postpackes.
I searched and found a solution, but I think I do anythuing wrong at it.
I tried to fix it like described here:
https://bugzilla.novell.com/show_bug.cgi?id=679435#c45
So, my xml looks as follows....
---------------------
[...]
<service>
<service_name>smbfs</service_name>
<service_start>disable</service_start>
</service>
<service>
<service_name>splash</service_name>
<service_start>disable</service_start>
</service>
</services>
</runlevel>
<x11>
<color_depth config:type="integer">16</color_depth>
<display_manager>kdm</display_manager>
<enable_3d config:type="boolean">false</enable_3d>
<monitor>
<monitor_device>1280X1024@60HZ</monitor_device>
<monitor_vendor>--> VESA</monitor_vendor>
</monitor>
<resolution>1280x1024 (SXGA)</resolution>
<window_manager>kde</window_manager>
</x11>
<chroot-scripts config:type="list">
<script> <!-- Fix post-packages bug -->
<chrooted config:type="boolean">true</chrooted>
<filename>fix_postinstall_bug.sh</filename>
<interpreter>shell</interpreter>
<source><![CDATA[#!/bin/bash
( while [ ! -f /var/lib/YaST2/installation_disabled_steps ];
do
sleep 1
done
cp /var/lib/YaST2/installation_disabled_steps /var/lib/YaST2
/installation_disabled_steps.bkp
cat /var/lib/YaST2/installation_disabled_steps.bkp | grep -v
"rpmcopy_secondstage" > /var/lib/YaST2/installation_disabled_steps) &]]>
</source>
</script>
</chroot-scripts>
</profile>
----------------------------
But this didn't work. So, I think I have an error at the syntax.
Or do I have to put the chroot-scripts elsewhere in the xml?
Regards
Daniel
--
Daniel Spannbauer Software Entwicklung
marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11
Rechbergstr. 4 - 6, D 87727 Babenhausen Mobil +49 171 4033220
http://www.marco.de/ Email ds(a)marco.de
Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org
I tried to upgrade my autoyast configuration to opensuse 12.1.
In my autoinst.xml I have the section below. The init script worked fine
in openSuse 11.4, but isn't executed with 12.1 after autoyast finishes.
The script is still in /var/adm/autoinstall/init.d
When I reboot the machine myself, the script *is* executed. Could this be
a change or bug related to the new systemd init tool?
thanks in advance
W. Dobbe
<scripts>
<chroot-scripts config:type="list">
(deleted)
</chroot-scripts>
<init-scripts config:type="list">
<script>
<chrooted config:type="boolean">false</chrooted>
<interpreter>shell</interpreter>
<source><![CDATA[
#!/bin/sh
chvt 1
exec < /dev/tty1 > /dev/tty1
cd /opt/vidigo_li/scripts/postinstall
/opt/vidigo_li/scripts/postinstall/run_postinstall.sh
]]></source>
</script>
</init-scripts>
</scripts>
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org
Hello,
I have a somewhat odd question which arose from merging the autoyast
process with some third party tools. During the installation the target
filesystem is mounted on /mnt in the ram disk. Can I configure this
mount point? The third party tools use this mount point also. Trying to
mount or umount something on /mnt while the installer is running leads
to some funny effects ;).
Regards
hmw
--
biff4emacsen - A biff-like tool for (X)Emacs
http://www.c0t0d0s0.de/biff4emacsen/biff4emacsen.html
Flood - Your friendly network packet generator
http://www.c0t0d0s0.de/flood/flood.html
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org
Hello fellow autoyast'ers,
I have a questions that I can't seem to find the answer for in the
autoyast documentation. The question is quite simple:
I want the first partition on each disk to start on block 64 or
preferably block 16384. Is there anyway to accomplish this using
autoyast?
>From what I can see, the partition starts on block 63 on systems
installed with autoyast. I can't see any options for this in the
partition-section of autoyast...
Disk /dev/sda: 53.7 GB, 53687091200 bytes
255 heads, 63 sectors/track, 6527 cylinders, total 104857600 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x0008dbe5
Device Boot Start End Blocks Id System
/dev/sda1 * 63 273104 136521 83 Linux
Thanks,
Alexander Holte-Davidsen
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org