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!
I dont have kinternet installed.
This is what doesnt seem to work:
<software>
<patterns config:type="list">
<pattern>default</pattern>
<pattern>Basis-Devel</pattern>
<pattern>x11</pattern>
</patterns>
<packages config:type="list">
<packages>perl-libwww-perl</packages>
<packages>net-snmp</packages>
<packages>kernel-source</packages>
</packages>
<remove-packages config:type="list">
<packages>pptp</packages>
<packages>smpppd</packages>
<packages>ppp</packages>
<packages>wvdial</packages>
<packages>mutt</packages>
</remove-packages>
</software>
In y2log it mentions that those packages should be removed, but it goes ahead and installs them anyway. I can do it manually on the command line:
# rpm -e pptp smpppd ppp wvdial mutt
and that works fine so I know I have no dependency problems.
matt
> -----Original Message-----
> From: Uwe Gansert [mailto:ug@suse.de]
> Sent: Friday, 30 June 2006 12:50 AM
> To: suse-autoinstall(a)suse.com
> Subject: Re: [suse-autoinstall] SLES 10 RC2 remove-packages section?
>
>
> On Thursday 29 June 2006 16:45, Manfred Hollstein wrote:
>
> > If that fails, you have kinternet installed; add that to
> the list and it
> > should work.
>
> good point.
> <remove-packages> can not break dependencies and so it's very
> likely that
> there is still a package that needs those packages.
> I did a very small installation with no X - so it worked for me.
>
> --
> ciao, Uwe Gansert
>
> Uwe Gansert, Server Technologies Team
> SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany
> Fax: +49-(0)911-74053-476, Web: http://www.suse.de/~ug
> now playing Covenant - Wasteland
>
> --
> To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com
> For additional commands, e-mail: suse-autoinstall-help(a)suse.com
>
>
This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses. No warranty is made that this material is free from computer virus or any other defect or error. Any loss/damage incurred by using this material is not the sender's responsibility. The sender's entire liability will be limited to resupplying the material.
What does "Can't detect Profile Version" usually indicate?
>From y2log..
===
2007-02-28 01:27:04 <1> 10.42.37.174(3375) [YCP] AutoinstScripts.ycp:545 Script Execution command: /bin/sh /tmp/YaST2-03375-S80cIe/pre-scripts/pre.sh 2&> /tmp/YaST2-03375-S80cIe/pre-scripts/logs/pre.sh.log
2007-02-28 01:27:04 <1> 10.42.37.174(3375) [YCP] XML.ycp:113 Reading /tmp/profile/modified.xml
2007-02-28 01:27:04 <1> 10.42.37.174(3375) [agent-xml] XmlAgent.cc(Read):758 Setting XML generic error handler
2007-02-28 01:27:04 <1> 10.42.37.174(3375) [agent-xml] XmlAgent.cc(Read):793 Freeing generic XML error handler
2007-02-28 01:27:04 <1> 10.42.37.174(3375) [YCP] Profile.ycp:167 importing profile
2007-02-28 01:27:04 <1> 10.42.37.174(3375) [YCP] Profile.ycp:149 Can't detect Profile Version
===
The bizarre thing is that I'm trying to use a pre.sh script to replace
some lines in the profile, writing it out as /tmp/profile/modified.xml
and this fails. But, if I take exactly that modified.xml file (scp'd
off via the console) and feed that back into the same host again on a new
attempt at installing, I get the above error, but the autoinst.xml
(which should be invalid too since it's identical[*]) works fine. This
makes no sense... why would it reject modified.xml but work just fine as
the fallback?
Is there something in the parsing of modified.xml that is a little more
strict I might be missing?
[*]there are differences in a couple of the scripts, the parsing I'm
doing removes the backslashes that I used i some sed commands, so I
double backslash them. This doesn't effect the profile itself though.
A diff shows that the autoinst.xml (which works) vs the modified.xml
(which is rejected) are the same, other then the backslashes inside the
scripts CDATA blocks.
--
Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com
Grandpa: "Quick! We have to kill the boy!"
Marge: "How'd you know he's a vampire?"
Grandpa: "He's a vampire?!? Ahhh...." [runs away] ==> Simpsons
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hi,
After the 1st part of the installation the system reboots normally.
My HP bl460c "starts the reboot" process, the screen becomes dark but
the server "hangs" in this state (is still powered on).
If I reset the sever manually the installation continues normally.
I tried the automatic installation with SLES10 and SLES10-SP1 with the
same strange effect. If you install the server manually the reboot works
as expected. An automatic installation with SLES9-SP3 also works without
any problem.
Best regards
Andre
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hi all together,
I install SLES10 from an ftp installation server with autoyast. No
problem so far.
Now I would like patching the system during installation.
I would prefer using a "patch depot" on my installation server.
How can I install a SLES10 "patch server"?
Is there a way to patch one "master server" with online update,
afterwards put all the patches on my ftp installation server and from
now on patch all further machines with the the patches on my
installation server?
Best regards
Andre
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
I make a bootable disk, and I can start to install the SUSE, but when it
tries to find the autoyast file, it can't find it, and I write the kernel
parameter like this :
title SUSE 10 Installation
root (hd0,0)
kernel /boot/linux root=/dev/sda1 ramdisk_size=8192 install=hd://sda1/SUSE
autoyast=device://sda1/autoinst.xml splash=silent showopts
initrd /boot/initrd
When I try autoyast=device://sda1/autoinst.xml, the error is ,
"An error occurred while fetching the profile:
File /tmp/Yast2-02878-KeDBUh/tmp_mount/autoinst.xml cannot be found"
And when I use file:///autoinst.xml and default, the error is,
"An error occurred while fetching the profile:
Reading file on /var/adm/mount//autoinst.xml failed.
Reading file on /autoinst.xml failed.
Reading file on CD failed. Path
/tmp/Yast2-02878-KeDBUh/tmp_mount/autoinst.xml"
And when I try to use hd://sda1/autoinst.xml
It tells me hd is unknown protocol,
Can someone tell how should I write the parameter for autoyast, or do you
know somebody else can help me on this ? Or this is a bug of SUSE?
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hello,
Is it possible to install the last Opensuse 10.2 kernel (2.6.18.8-0.5)
from an autoinstall xml file ?
I must use kernel tag in my autoinstall xml file but when my Pc
reboot, I have the default version kernel (2.6.18.2-34)
Sorry for my english :-(
Fabien.
Hi,
I'm trying to use Advanced partitioning options to format the root partition
and keep the home. In general this works well, however if I switch
architecture (i386 to x86_64 or the other way round) I get an error "No linux
root partitions found"
The last couple of lines in the error log look related
2007-07-17 16:28:12 <1> 192.168.21.127(3306) [YCP] RootPart.ycp:1216
$["detected_fs":`ext3, "device":"/dev/sda7", "fsid":131, "fstype":"Linux
native", "name":"sda7", "nr":7, "region":[1500, 17952], "size_k":144199408,
"type":`logical, "udev_id":["scsi-SATA_SAMSUNG_HD160JJ_S0DFJ1HL462797-part7",
"ata-SAMSUNG_HD160JJP_S0DFJ1HL462797-part7"],
"udev_path":"pci-0000:00:1f.2-scsi-0:0:0:0-part7", "used_fs":`ext3,
"uuid":"531d2ab2-a30e-4cb1-8e53-ffe32a4e183d"] $[`arch:"unknown", `fs:`ext3,
`fstype:"Linux native", `label:"", `name:"unknown", `valid:false]
2007-07-17 16:28:12 <1> 192.168.21.127(3306) [YCP] RootPart.ycp:1283
rootPartitions: $["/dev/sda6":$[`arch:"i386", `fs:`ext3, `fstype:"Linux
native", `label:"", `name:"SUSE Linux Enterprise Desktop 10", `valid:false],
"/dev/sda7":$[`arch:"unknown", `fs:`ext3, `fstype:"Linux native", `label:"",
`name:"unknown", `valid:false]]
The section of profile (after running through the rules parser and pre
scripts) looks like this
<partitioning_advanced>
<fstab>
<initialize config:type="boolean"></initialize>
<partitions config:type="list">
<partition>
<format config:type="boolean">false</format>
<mount>/home</mount>
</partition>
<partition>
<filesystem>ext3</filesystem>
<format config:type="boolean">true</format>
<mount>/</mount>
</partition>
</partitions>
<root_partition>/dev/sda6</root_partition>
<use_existing_fstab config:type="boolean">true</use_existing_fstab>
</fstab>
</partitioning_advanced>
Uwe, do you want a bugzilla for this ?
--
Simon Crute
IS&T.
Bracknell.
UK.
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
hello list,
i tried to merge some profiles together (with rules) but experienced
some problems. Basically i have two goals at the moment: 1.) to merge
software selections (a default one and some additional ones) 2.) to
merge scripts together (like i have one init script in one profile and
another in a additional profile).
How can i archive that? ... i already tried different dont_merge
statements in the rules.xml file.
yh and im using sles10 sp1.
best regards
martin
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org
Hi!
That's my second attempt with this issue. In short: re-installing a
Proliant box
I get the following error:
----------------------------------------------
INFO POPUP:The partitioning on disk /dev/cciss/c0d0 is not readable by
the partitioning tool parted, which is used to change the
partition table.
You can use the partitions on disk /dev/cciss/c0d0 as they are.
You can format them and assign mount points to them, but you
cannot add, edit, resize, or remove partitions from that
disk with this tool.
------------------------------------------------
This is the partitioning part:
<?xml version="1.0"?>
<partitioning config:type="list" xmlns="http://www.suse.com/1.0/yast2ns"
xmlns:config="http://www.suse.com/1.0/configns" xmlns:xinclude="
http://www.w3.org/2001/XInclude">
<drive>
<device>/dev/cciss/c0d0</device>
<initialize config:type="boolean">true</initialize>
<partitions config:type="list">
<partition>
<partition_id config:type="integer">242</partition_id>
<partition_nr config:type="integer">1</partition_nr>
<partition_type>primary</partition_type>
<format config:type="boolean">false</format>
<size>6mb</size>
</partition>
<partition>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<label>boot</label>
<mount>/boot</mount>
<size>128mb</size>
</partition>
<partition>
<filesystem config:type="symbol">swap</filesystem>
<format config:type="boolean">true</format>
<mount>swap</mount>
<partition_id config:type="integer">130</partition_id>
<size>512mb</size>
</partition>
<partition>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<label>root</label>
<mount>/</mount>
<size>8GB</size>
</partition>
<partition>
<lvm_group>vg00</lvm_group>
<size>max</size>
</partition>
</partitions>
<use>all</use>
</drive>
<drive>
<device>/dev/vg00</device>
<initialize config:type="boolean">true</initialize>
<is_lvm_vg config:type="boolean">true</is_lvm_vg>
<partitions config:type="list">
<partition>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<lv_name>home</lv_name>
<mount>/home</mount>
<fstopt>nodev,nosuid</fstopt>
<size>10GB</size>
</partition>
<partition>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<lv_name>tmp</lv_name>
<mount>/tmp</mount>
<fstopt>nodev,nosuid,noexec</fstopt>
<size>1GB</size>
</partition>
<partition>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<lv_name>usr</lv_name>
<mount>/usr</mount>
<fstopt>nodev</fstopt>
<size>5GB</size>
</partition>
<partition>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<lv_name>var</lv_name>
<mount>/var</mount>
<fstopt>nodev,nosuid</fstopt>
<size>2GB</size>
</partition>
<partition>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<lv_name>amacore</lv_name>
<mount>/www</mount>
<fstopt>nodev,nosuid</fstopt>
<size>max</size>
</partition>
</partitions>
<use>all</use>
</drive>
</partitioning>
This seems to be bug. Can somebody confirm it at least?
Thanks!
Valentin
IMPORTANT - CONFIDENTIALITY NOTICE - This e-mail is intended only for
the use of the individual or entity shown above as addressees. It may
contain information which is privileged, confidential or otherwise
protected from disclosure under applicable laws. If the reader of this
transmission is not the intended recipient, you are hereby notified that
any dissemination, printing, distribution, copying, disclosure or the
taking of any action in reliance on the contents of this information is
strictly prohibited. If you have received this transmission in error,
please immediately notify us by reply e-mail or using the address below
and delete the message and any attachments from your system.
Amadeus Data Processing GmbH
Geschäftsführer: Eberhard Haag
Sitz der Gesellschaft: Erding
HR München 48 199
Berghamer Strasse 6
85435 Erding
Germany
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org