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 list,
I'm having difficulties enabling systemd services in openSUSE 12.2 from
the autoyast file.
Our current way doesn't work anymore:
<runlevel>
<default>3</default>
<services config:type="list">
<service>
<service_name>rpcbind</service_name>
<service_status>enable</service_status>
</service>
</services>
</runlevel>
At least not for rpcbind. My workaround currently is to use a post-script
to do a "systemctl enable rpcbind.service".
--
Kind regards.
Conny Seidel
##################################################################
# Email : conny.seidel(a)amd.com GnuPG-Key : 0xA6AB055D #
# Fingerprint: 17C4 5DB2 7C4C C1C7 1452 8148 F139 7C09 A6AB 055D #
##################################################################
# Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach #
# General Managers: Alberto Bozzo #
# Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen #
# HRB Nr. 43632 #
##################################################################
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org
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
Splitting this because AFAICT it has nothing to do with systemd, I
just ran into it while trying to get systemd to work.
On Tue, Apr 10, 2012 at 1:19 PM, 686f6c6d <686f6c6d(a)googlemail.com> wrote:
> On Mon, Apr 2, 2012 at 16:16, 686f6c6d <686f6c6d(a)googlemail.com> wrote:
>>
>> - Using kernel-default-3.1.0-1.2.1.x86_64 from the "install" repo, the
>> installation succeeds.
>> - Using kernel-default-3.1.9-1.4.1.x86_64 from the "update" repo, the
>> installation fails.
>
> Let me correct that: Once I changed the profile again to re-include
> some of our scripts (that were disabled while debugging), even
> kernel-default 3.1.0 fails with the same problem.
> Need to do further debugging.
Those seem to be unrelated problems. One thing I can say with
certainty right now is that my profile does not work when I enable the
update repo: installation of kernel-default fails because large parts
of the device nodes in /dev are missing. When I disable the repo,
everything works fine.
Uwe: What is the best way to proceed from here? Should I open a bug
for autoyast (although autoyast is not the real culprit here), or
should we debug further on this list/off-list and then open bugs for
the correct packages?
I'm currently sanitizing the logs of both installations with and
without the update repo enabled, which will take a while.
--
Kind regards
686f6c6d / 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
Hello,
for using autoyast per http i want to configure network with linuxrc [1]
and its kernel boot parameters (hostip, netmask, ...), resp. with the
appropriate installation dialogue [2].
Unfortunately both don't work for me: The machine doesn't react to ping
nor is "ifconfig -a" showing an active network interface or ip address.
But i can set it manually with "ifconfig eth0 inet ..." at the same
phase of installation, so missing network drivers shouldn't be the problem.
The problem appears both on opensuse release 12.1 and 12.2/Milestone-3,
both in a virtual and a physical machine.
Any hints?
PS: I know that linuxrc hasn't directly to do with autoyast, but perhaps
it's often used there(?). I already asked at the german opensuse-de@
mailing list, but found no solution there.
Dominik.
[1] http://en.opensuse.org/SDB:Linuxrc
[2]
http://paste.opensuse.org/6379e182http://paste.opensuse.org/af7f337d
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-autoinstall+owner(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
Hi there,
I just wanted to check before I do a trial and error test...
Autoyast's file section currently allows me to:
* Fetch files from remote source using
<file_location>http://my.server.site/issue</file_location> for example.
* Create directories by adding a slash, i.e.,
<file_path>/mydir/a/b/c/</file_path>
So, natural question: Can Autoyast fetch directories by combining both?
<file_location>http://my.server.site/issue/</file_location><!-- note the
slash -->
<file_path>/mydir/a/b/c/</file_path>
If not, I will use a script to do that... but it would be nice :-)
--
Dipl.-Ing. Joschi Brauchle, M.S.
Institute for Communications Engineering (LNT)
Technische Universitaet Muenchen (TUM)
80290 Munich, Germany
Tel (work): +49 89 289-23474
Fax (work): +49 89 289-23490
E-mail: joschi.brauchle(a)tum.de
Web: http://www.lnt.ei.tum.de/
Hi,
I'm currently testing ldap-client configuration using autoyast.
Here is a list of issues I found. Please comment.
I'll probably file some bug reports next week. Testing system is
factory snapshot from April 12, 2012 (that is, M3, probably).
- (YaST) Issues during installation:
- Both the reference profile and the XML schema allow the parameter
<bind_dn>, but there's no binddn in /etc/ldap after installation.
- missing support for additional LDAP configuration parameters, for
example there ought to be a parameter <bind_pw> resulting in a
bindpw in /etc/ldap.conf after installation. Also, I could use a
way wo put the tls certfile into the autoyast xml, e.g. using a
parameter <tls_cacertfile-content><source><![CDATA[...]]></...
- Yast Reference Profile (created using Yast -> Autoyast -> Tools ->
Create Reference Profile) issues:
- A created reference profile has a parameter <mkhomedir>, but it
isn't allowed according to the XML schema
(/usr/share/YaST2/schema/autoyast/rng/ldap.rng) and apparently
isn't used, i.e. it didn't appear in /etc/ldap.conf after
installation (I only had it set to "false", though).
- schema only issues:
- The parameters <sssd>, <tls_cacertdir> and <tls_cacertfile> aren't
in the XML schema (/usr/share/YaST2/schema/autoyast/rng/ldap.rng)
They are, however reference profiles created with Yast -> AutoYast
and are used during installation
Thanks and best regards
Robert
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org
Hello list,
I'm having diufficulties enabling systemd services in openSUSE 12.2 from
the autoyast file.
Our current way doesn't work anymore:
<runlevel>
<default>3</default>
<services config:type="list">
<service>
<service_name>rpcbind</service_name>
<service_status>enable</service_status>
</service>
</services>
</runlevel>
At least not for rpcbind. My workaround currently is to use a post-script
to do a "systemctl enable rpcbind.service".
--
Kind regards.
Conny Seidel
##################################################################
# Email : conny.seidel(a)amd.com GnuPG-Key : 0xA6AB055D #
# Fingerprint: 17C4 5DB2 7C4C C1C7 1452 8148 F139 7C09 A6AB 055D #
##################################################################
# Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach #
# General Managers: Alberto Bozzo #
# Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen #
# HRB Nr. 43632 #
##################################################################