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
Hi list,
is it somehow possible to configure the inode count via autoyast?
Customer reported that settings like:
<fs_options>
- <opt_inode_size>
<option_str>-I</option_str>
<option_value>128</option_value>
</opt_inode_size>
- <opt_inode_density>
<option_str>-i</option_str>
<option_value>8192</option_value>
</opt_inode_density>
</fs_options>
didn't help
Thanks,
Jochen
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org
Sehr geehrte Damen und Herren,
Die Optimierung ist notwendig, wenn auf Sie mindestens einer dieser Sätze zutrifft:
- Sie haben wenige Besuche auf Ihrer Webseite,
- man kann Ihre Webseite in den Suchergebnissen nicht finden oder sie befindet sich an der 2. oder weiteren Unterseite der Suchmaschine,
- Ihr Service präsentiert sich unangemessen in der Suchmaschine,
- die Kunden können keine nötigen Informationen finden und verlassen schnell Ihre Webseite,
- Kunden kaufen bei der Konkurrenz und nicht bei Ihnen,
- Sie möchten sicher sein, dass Ihr Service geschützt wird,
- Sie möchten der Konkurrenz die Stirn bieten und ihr einen Schritt voraussein.
http://www.seoweb-optimierung.net
Zu den wichtigsten Vorteilen der Optimierung gehören:
- Erhöhung der Position der Webseite in den Suchmaschinen, z.B. bei Google,
- häufigere Seitenbewegung und häufigerer Aufruf der Webseite,
- Gewinnung der Zielgruppe von Kunden, die an den Produkten und Dienstleistungen Ihrer Firma wirklich interessiert sind,
- Steigerung der Verkaufsergebnisse,
- Erhöhung der Erkennbarkeit der Firma in Verbindung mit niedrigen Kosten,
- Erhöhung des Prestiges der Firma infolge der Anwendung der modernen Techniken,
- Konkurrenzfähigkeit gegenüber den besten und bekanntesten Firmen im Lande,
- bessere Indexierung des Services durch die Suchmaschinen,
- keine Abonnementzahlung.
Schon nach 2 Wochen nach der Vornahme der Optimierungsmaßnahmen kann Ihre Webseite auf der ersten
Seite unter den ersten Suchergebnissen stehen.
http://www.seoweb-optimierung.net
Mit freundlichen Grüßen
--
SeoWeb
http://www.seoweb-optimierung.net
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org
Hello all,
I would like to update an installed system with a new AutoYast XML
profile (containing only updated stuff) and found that there is a
/sbin/yast ayast_setup setup filename=profile.xml
command that does just that.
Unfortunately, the docs about what this command does exactly are very
spare. Uwe mentions on http://suse.gansert.net/?p=38 that (quoting):
-------
The XML file will be read by AutoYaST and applied to your currently
running system except (and that’s good – you want it that way, believe
me) all 1st stage configuration like partitioning, bootloader, pre- and
chrootscripts and software selection.
-------
=> Thus, for software updates I use post-packages,
=> for scripts I wanted to use post-scripts and init-scripts.
But it looks like init-scripts are not run... is there a complete list
of steps that are actually done by this command?
Background:
I would like to use zypper to enable a repo with the XML mentioned
above. But as it does not run the init-scripts and Yast locks the RPM
database during post-scripts, I looks like zypper cannot be used along
with "ayast_setup setup" at all, right?
Best regards,
Joschi Brauchle
Hi all.
I just got a general question:
When using yast2 autoyast module every value in a section is written on
changes.
e.g.I have only defined that the bootloader should be written to the mbr
but the following properties are set in the XML:
<global>
<boot_boot>false</boot_boot>
<boot_custom></boot_custom>
<boot_extended>false</boot_extended>
<boot_mbr>true</boot_mbr>
<boot_root>false</boot_root>
</global>
As these seems to be default settings, can I just remove them from the
XML? How do you handle it? Do you leave them in, as I guess next time
the profile is edited with yast2 autoyast, they would be inserted again?
Greets
Marcus
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org
Hi,
I have an issue when using an autoyast profile with some 30 add-on
repositories. One or two repositories always fail ("Failed to add add-on
product"). Happens with repositories specified either as ftp or as nfs
repositories. Is there anything known about this? I don't see anything
in the log files of the ftp/nfs-server, just the connections stopping.
Is there anything known about this?
BTW, this is easier to see in the log files when using nfs, so I didn't
notice it earlier: _seven_ connections per repository when adding it as
an add-on product. Seems a bit much..
Best regards
Robert
--
Robert Klein - Max Planck-Institut für Polymerforschung
Ackermannweg 10
55128 Mainz
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org
