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!
On Sun, 29 Jun 2008 11:41:29 +0200, Uwe Gansert wrote
> Am 29.06.2008 um 10:53 schrieb Hubertus A. Haniel:
>
> > Is AutoYast in 11.0 broken? - I can't seem to get the dumping of
> > config files working described at
http://www.suse.com/~ug/autoyast_doc/createprofile.completeconf.html#id2553…
> > to work. It used to work in 11.0 Alpha 2 but it does not seem to
> > work with the current release anymore. - I am pretty much using the
> > same profile since 10.3.
>
> do you have the autoyast2 package installed?
> http://ugansert.blogspot.com/2008/06/section-broken-in-110.html
>
> > The other thing that is not working is adding my custom repository
> > anmore using a add_on_products file. I am getting errors in the yast
> > logs about accepting untrusted signatures even though in my yast
> > profile I tell yast to accept them anyway with the following
> > paragraph:
> >
> > <signature-handling>
> > <accept_unsigned_file config:type="boolean">true</
> > accept_unsigned_file>
> > <accept_file_without_checksum config:type="boolean">true</
> > accept_file_without_checksum>
> > <accept_verification_failed config:type="boolean">true</
> > accept_verification_failed>
> > <accept_unknown_gpg_key config:type="boolean">true</
> > accept_unknown_gpg_key>
> > <accept_non_trusted_gpg_key config:type="boolean">true</
> > accept_non_trusted_gpg_key>
> > <import_gpg_key config:type="boolean">true</import_gpg_key>
> > </signature-handling>
>
> is that a repository you have created from scratch for the 11.0?
> Then you might have forgotten to create the sha1 sums. Check the
> documentation for create_update_source on my homepage.
>
> ciao, Uwe Gansert
>
Thanx for the hint about having to install the autoyast2 package - that solved my
problem in regards to the custom config files. - In regards to my custom
repository, - I am actually using the createrepo tool to create my repositories
and I am using that at work for SLES 10 as well and it still seems to work fine
with SP2. I can still add this repository manually using zypper fine it is just
that autoyast does not seem to like it anymore under 11.0:
2008-06-29 22:04:25 <1> 192.168.0.80(3127) [zypp]
MediaHandler.cc(removeAttachPoint):190 Deleted default attach point
/var/adm/mount/AP_0x00000001
2008-06-29 22:04:25 <1> 192.168.0.80(3127) [zypp] MediaHandler.cc(release):774
Released: http://192.168.0.1/PUBLIC/UNIX/LINUX/opensuse/extra-software/11.0 not
attached; localRoot ""
2008-06-29 22:04:25 <1> 192.168.0.80(3127) [zypp] PathInfo.cc(_Log_Result):295
recursive_rmdir /var/cache/zypp/raw/11.0ybC6sm
2008-06-29 22:04:25 <1> 192.168.0.80(3127) [zypp] PathInfo.cc(_Log_Result):295
2008-06-29 22:04:25 <5> 192.168.0.80(3127) [zypp] Exception.cc(log):119
RepoManager.cc(refreshMetadata):662 CAUGHT: Fetcher.cc(start):249: Signature
verification failed for repomd.xml
2008-06-29 22:04:25 <3> 192.168.0.80(3127) [zypp]
RepoManager.cc(refreshMetadata):663 Trying another url...
2008-06-29 22:04:25 <3> 192.168.0.80(3127) [zypp]
RepoManager.cc(refreshMetadata):672 No more urls...
2008-06-29 22:04:25 <5> 192.168.0.80(3127) [zypp] Exception.cc(log):119
RepoManager.cc(refreshMetadata):673 THROW: RepoManager.cc(refreshMetadata):673:
Valid metadata not found at specified URL(s)
2008-06-29 22:04:25 <3> 192.168.0.80(3127) [Pkg]
Source_Create.cc(SourceCreateEx):729 SourceCreate for
'http://192.168.0.1/PUBLIC/UNIX/LINUX/opensuse/extra-software/11.0' product '/'
has failed
Is this type of repository no longer supported? - I find it a lot simpler to maintain.
Best regards
Hubba
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Is AutoYast in 11.0 broken? - I can't seem to get the dumping of config
files working described at
http://www.suse.com/~ug/autoyast_doc/createprofile.completeconf.html#id2553…
to work. It used to work in 11.0 Alpha 2 but it does not seem to work
with the current release anymore. - I am pretty much using the same
profile since 10.3.
The other thing that is not working is adding my custom repository
anmore using a add_on_products file. I am getting errors in the yast
logs about accepting untrusted signatures even though in my yast profile
I tell yast to accept them anyway with the following paragraph:
<signature-handling>
<accept_unsigned_file
config:type="boolean">true</accept_unsigned_file>
<accept_file_without_checksum
config:type="boolean">true</accept_file_without_checksum>
<accept_verification_failed
config:type="boolean">true</accept_verification_failed>
<accept_unknown_gpg_key
config:type="boolean">true</accept_unknown_gpg_key>
<accept_non_trusted_gpg_key
config:type="boolean">true</accept_non_trusted_gpg_key>
<import_gpg_key
config:type="boolean">true</import_gpg_key>
</signature-handling>
Best regards
Hubba
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hi,
before I open another unnecessary bug report I thought I just ask here. I have
something like the following in my profile:
<software>
<patterns config:type="list">
lots of patterns...
...
</patterns>
<remove-packages config:type="list">
<package>rsh</package>
<package>beagle-index</package>
<package>beagle-gui</package>
<package>beagle-evolution</package>
<package>kerry</package>
<package>kio_beagle</package>
<package>kdebase3-beagle</package>
<package>beagle</package>
</remove-packages>
<post-packages config:type="list">
<package>ICAClient</package>
</post-packages>
</software>
This used to work fine with 10.3 but in 11.0 I can't find any traces of the
ICAClient package on the installed system. I also can't find anything about
the installlation of post-packages in the y2log*. The package autoyast2 is
definitely installed (which was somehow necessary in order to get the <files>
section to work). Now, am I doing something wrong again or is this a bug?
Karsten.
--
The hieroglyphics are all unreadable except for a notation on the back,
which reads "Genuine authentic Egyptian papyrus. Guaranteed to be at
least 5000 years old."
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
I'm trying to create a GRUB-based multi-distro install CD. I've been
partially successful with openSUSE 11.0, I can get linuxrc to launch
YaST but I can't get YaST to use an iso based repository.
Below is an example GRUB menu.lst entry (note that the install= has
wrapped but is actually on the same line as the kernel):
----
title Install Classroom Server Using openSUSE 11.0
kernel (cd)/boot/vmlinuz-s11.0
install=disk:///isos/openSUSE-11.0-DVD-i386.iso
initrd (cd)/boot/initrd-s11.0
----
This works, linuxrc is able to launch YaST, but after some
initialization YaST says:
----
Unable to create repository
from URL 'iso:/?iso=openSUSE-11.0-DVD-i386.iso&url=disk:///isos/'.
Details:
Unsupported URI scheme in 'disk:///isos/'.
----
Setting up a network server is not an option.
I must be doing something wrong, but I've been over the linuxrc &
AutoYaST documentation several times and I don't see what I've missed.
Is it possible to install openSUSE using iso files on a USB drive? What
am I missing?
BTW, once I get this working, I plan on adding an autoyast file to the
mix, so I'm hoping for a solution that won't make that harder.
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
All,
I need to put together a single disc for installing SLES10 SP1. I
searched Uwe's autoyast site and the archives of this list and didn't
find what I need, so can anyone point me to instructions on what needs
to be done to combine the (4) CDs into a single tree, so I can build a
DVD out of it?
I normally do network installations where the multiple CDs in multiple
directories is automatically handled by Autoyast.
All insight is appreciated.
Thanks,
--
Jeremy Silver
jersilve(a)cisco.com
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hello,
I am using autoyast to setup out linux installations of suse11.0, suse10.3 as
well as SELS10. Because we have to install all of these systems there is an
autoyast.xml file for each of the linux systems to be installed. The
installation source are all in out local network, so I simply take the
correct installation CD and then start the installation. To ease this process
I set up a SLP server that offeres me the choice which linux system (10.3,
11.0, ..) I want to install and selects the correct installation source as
well as the correct autoyast file via http:// URLs for each of both.
Up to suse10.3 this used to work fine and was a comfortable solution to get
different systems installed easily. However since 10.3 and unfortunately
still in 11.0 there is a problem with SLP when I want to specify both an
installtion source as well as an autoyast file URL. Please see my bug report
here:
https://bugzilla.novell.com/show_bug.cgi?id=332064.
The bug has not been fixed and I am looking for a better way to get things
done. The problem is that the installation system cannot evaluate the data
provided by the SLP server if there are two parameters provided by SLP
(installation source as well as autoyastfile URL) instead of only the
installation media URL.
So my problem is how can I mostly automatically start an autoyast installation
with the autoyast file reachable via http: when using SLP?
A very basic (non SLP) solution is to boot from CD and manually provide the
installtion media URL (install=) as well as the autoyast URL (autoyast=) on
the commandline, but this is of course very uncomfortable and error prone
because you have to type long URL strings. Is there a better way or is the
only way to fix the bug mentioned above.
Thanks
Rainer
--
Rainer Krienke, Uni Koblenz, Rechenzentrum, A22, Universitaetsstrasse 1
56070 Koblenz, http://www.uni-koblenz.de/~krienke, Tel: +49261287 1312
PGP: http://www.uni-koblenz.de/~krienke/mypgp.html,Fax: +49261287 1001312
Hallo,
using the DVD as inst-source is working perfect but now I changend the
inst-source to local mirror of the 10.3 distribution-directory of
ftp5.gwdg.de.
Since that change java-packages are missing.
Any ideas?
Thanks for hints.
Ralf Prengel
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hello,
I am trying to setup some complex password settings and is having some
problems with both SLES9 and SLES10.
In my autoyast template I have the following <security> section
<security>
<console_shutdown>ignore</console_shutdown>
<cwd_in_root_path>no</cwd_in_root_path>
<fail_delay>5</fail_delay>
<faillog_enab>yes</faillog_enab>
<lastlog_enab>yes</lastlog_enab>
<encryption>blowfish</encryption>
<pass_max_days>60</pass_max_days>
<pass_min_days>0</pass_min_days>
<pass_warn_age>10</pass_warn_age>
<pass_max_len>20</pass_max_len>
<pass_min_len>10</pass_min_len>
<passwd_use_cracklib>yes</passwd_use_cracklib>
<permission_security>secure</permission_security>
</security>
This would generate /etc/security/pam_pwcheck.conf to be
Password: minlen=20 cracklib blowfish nullok
And also in /etc/login.defs sets
PASS_MAX_DAYS 60
PASS_MIN_DAYS 0
PASS_WARN_AGE 10
However when setting up complex passwords using the xlimits on
/etc/pam.d/passwd ie
more /etc/pam.d/passwd
#%PAM-1.0
auth required pam_unix2.so nullok
account required pam_unix2.so
password required pam_pwcheck.so
password required pam_cracklib.so use_first_pass use_authtok
no_obscure_checks retry=3 minlen=11 difok=-1 dcredit=-1 ucredit=-
1
password required pam_pwcheck.so use_authtok remember=12
password required pam_unix2.so nullok use_first_pass use_authtok
session required pam_unix2.so
having the /etc/security/pam_pwcheck.conf as above will break it. So
/etc/security/pam_pwcheck.conf would have to be changed to the following
Password: blowfish nullok
So when I got in touch with novell support they asked me to use <file> to
overwrite the /etc/security/pam_pwcheck.conf and /etc/pam/passwd and also
/etc/login.defs but is there any other solutions than to just over write the
files ?
Thanks
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
All,
Is there a way to tell autoyast to ignore packages
that cannot be found?
We have one autoinst.xml for both i386 and x64
architectures. For 64bit we added the xxx-32bit
packages, but they do not exist in 32bit so autoyast
always throws
an error and we have to press 'enter' to continue...
Thanks,
John
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org