openSUSE Autoinstall March 2007

autoinstall@lists.opensuse.org

24 participants
27 discussions

linuxrc - netdevice=<hwaddress>
by John Willis 18 Dec '12

18 Dec '12

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!

3 2

RE: [suse-autoinstall] SLES 10 RC2 remove-packages section?
by Matt Gillard 05 Mar '08

05 Mar '08

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.

4 6

[opensuse-autoinstall] Strange problem with creating a modified.xml
by Mike Marion 28 Sep '07

28 Sep '07

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

3 9

[opensuse-autoinstall] ldap problems
by Lars Stavholm 05 Apr '07

05 Apr '07

Hi All, I've managed to use the ldap client (<ldap>) and server (<ldap-server>) sections of my autoinst.xml to setup the server with both as ldap server and ldap client. I would assume that the ldap client stuff will work eventually, but there's a problem with the server part: the ldap database does not get initialized, I still have to go in and do that step manually. Does anyone know how to automate this step? Any thoughts appreciated /Lars -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 4

[opensuse-autoinstall] Repository layout for SLES10 SP?
by Jeremy Silver 02 Apr '07

02 Apr '07

All, I have searched this list and www.suse.de/~ug/.cannot and cannot find any documentation on adding a service pack to a SLES10 installation repository - is this documented anywhere? Thanks, -- Jeremy Silver jeremy(a)broadware.com -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 2

[opensuse-autoinstall] Error while configuring partitions. Try again.
by Ian Grant 02 Apr '07

02 Apr '07

Dear List With my autoyast script I get a dialog "Error while configuring partitions. Try again." during the phase 'Create partition plans.' A syslog server sees only a few kernel log message from the install host. The /var/log/Yast2 log on the install host gives no clue about what the error is. Can anyone suggest how to get a more useful diagnostic? Here is my xml file FWIW <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <add-on> <add_on_products config:type="list"/> </add-on> <bootloader> <activate config:type="boolean">true</activate> <device_map config:type="list"> <device_map_entry> <firmware>fd0</firmware> <linux>/dev/fd0</linux> </device_map_entry> <device_map_entry> <firmware>hd0</firmware> <linux>/dev/sda</linux> </device_map_entry> </device_map> <global> <activate>true</activate> <boot_root>true</boot_root> <gfxmenu>/boot/message</gfxmenu> <lines_cache_id>3</lines_cache_id> <timeout config:type="integer">8</timeout> </global> <loader_device>/dev/sda</loader_device> <loader_type>grub</loader_type> <location>mbr</location> <repl_mbr config:type="boolean">true</repl_mbr> </bootloader> <firewall> <FW_ALLOW_FW_BROADCAST_DMZ></FW_ALLOW_FW_BROADCAST_DMZ> <FW_ALLOW_FW_BROADCAST_EXT>ntp</FW_ALLOW_FW_BROADCAST_EXT> <FW_ALLOW_FW_BROADCAST_INT></FW_ALLOW_FW_BROADCAST_INT> <FW_DEV_DMZ></FW_DEV_DMZ> <FW_DEV_EXT>eth0</FW_DEV_EXT> <FW_DEV_INT></FW_DEV_INT> <FW_SERVICES_EXT_TCP>ssh</FW_SERVICES_EXT_TCP> <FW_SERVICES_EXT_UDP>ntp</FW_SERVICES_EXT_UDP> <enable_firewall config:type="boolean">true</enable_firewall> <start_firewall config:type="boolean">true</start_firewall> </firewall> <general> <mode> <confirm config:type="boolean">true</confirm> <halt config:type="boolean">false</halt> <second_stage config:type="boolean">true</second_stage> </mode> <mouse> <id>none</id> </mouse> <signature-handling> <accept_file_without_checksum config:type="boolean">false</accept_file_without_checksum> <accept_unknown_gpg_key config:type="boolean">false</accept_unknown_gpg_key> <accept_unsigned_file config:type="boolean">false</accept_unsigned_file> <accept_verification_failed config:type="boolean">false</accept_verification_failed> <import_gpg_key config:type="boolean">false</import_gpg_key> </signature-handling> </general> <keyboard> <keymap>english-uk</keymap> </keyboard> <language> <language>en_GB</language> <languages></languages> </language> <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <size>max</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <size>4G</size> </partition> </partitions> <use>all</use> </drive> </partitioning> <proxy> <enabled config:type="boolean">true</enabled> <ftp_proxy>http://host.cam.ac.uk:8080/</ftp_proxy> <http_proxy>http://host.cam.ac.uk:8080/</http_proxy> <https_proxy></https_proxy> <no_proxy>localhost, 127.0.0.1, cam.ac.uk</no_proxy> <proxy_password></proxy_password> <proxy_user></proxy_user> </proxy> <report> <errors> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </errors> <messages> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </messages> <warnings> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </warnings> <yesno_messages> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </yesno_messages> </report> <runlevel> <default>5</default> </runlevel> <users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <user_password>obscured</user_password> <username>root</username> </user> </users> <scripts> <init-scripts config:type="list"> <script> <debug config:type="boolean">true</debug> <filename>post-init</filename> <location></location> <source><![CDATA[#! /bin/bash echo "$(date): in post-init script" >>/tmp/install.log # Mount filer volume mkdir /mnt/nfs || exit 1 mount somehost:/vol/vol3/sys-li9/suse-10.2 /mnt/nfs || exit 1 # Call out to shell script, logging everything /bin/bash -x /mnt/nfs/autoyast/post-init.sh >>/tmp/install.log 2>&1 umount /mnt/nfs ]]></source> </script> </init-scripts> </scripts> <software> <patterns config:type="list"> <pattern>apparmor</pattern> <pattern>base</pattern> <pattern>fonts</pattern> <pattern>imaging</pattern> <pattern>kde</pattern> <pattern>kde_basis</pattern> <pattern>kde_imaging</pattern> <pattern>sw_management</pattern> <pattern>sw_management_x11</pattern> <pattern>x11</pattern> <pattern>xgl</pattern> <pattern>yast2_basis</pattern> <pattern>zmd</pattern> <pattern>zmd_x11</pattern> </patterns> <remove-packages config:type="list"> <package>smtp_daemon</package> </remove-packages> </software> <timezone> <hwclock>UTC</hwclock> <timezone>Europe/London</timezone> </timezone> <user_defaults> <expire></expire> <group>100</group> <groups>video,dialout</groups> <home>/home</home> <inactive>-1</inactive> <shell>/bin/bash</shell> <skel>/etc/skel</skel> </user_defaults> <networking> <dhcp_options> <dhclient_additional_options></dhclient_additional_options> <dhclient_client_id></dhclient_client_id> <dhclient_hostname_option>AUTO</dhclient_hostname_option> </dhcp_options> <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth0</device> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> <managed config:type="boolean">false</managed> <modules config:type="list"> <module_entry> <device>static-0</device> <module></module> <options></options> </module_entry> </modules> <routing> <ip_forward config:type="boolean">false</ip_forward> </routing> </networking> <online_update> <autoget config:type="boolean">false</autoget> <enable_autoupdate config:type="boolean">true</enable_autoupdate> <skipPre config:type="boolean">false</skipPre> <update_time> <day config:type="integer">0</day> <hour config:type="integer">0</hour> <minute config:type="integer">0</minute> <random_time config:type="boolean">true</random_time> <timing>daily</timing> </update_time> </online_update> <x11> <color_depth>24</color_depth> <display_manager>kdm</display_manager> <enable_3d config:type="boolean">false</enable_3d> <window_manager>kde</window_manager> </x11> </profile> -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 4

[opensuse-autoinstall] sysconfig
by Lars Stavholm 29 Mar '07

29 Mar '07

I'm trying to use the sysconfig setting as described in <http://www.suse.com/~ug/autoyast_doc/createprofile.sysconfig.html> like so: <sysconfig config:type="list" > <sysconfig_entry> <sysconfig_key>DISPLAYMANAGER_AUTOLOGIN</sysconfig_key> <sysconfig_path>/etc/sysconfig/displaymanager</sysconfig_path> <sysconfig_value>root</sysconfig_value> </sysconfig_entry> </sysconfig> That doesn't bite, there's no change being performed. What am I doing wrong here? /Lars Stavholm -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 2

[opensuse-autoinstall] SLES 9 and SLES 10 autoyast NTP client configuration bug?
by Anton Altaparmakov 29 Mar '07

29 Mar '07

Hi, Both on SLES 9 and SLES 10 when you configure the NTP client via the autoyast profile, when the system is installed the config file /etc/ ntp.conf is lacking the line: driftfile /var/lib/ntp/drift/ntp.drift Which means that every time the machine is rebooted NTP has to establish the drift from scratch which means the time oscillates randomly for about 15 minutes after booting up. This in turn causes problems with time sensitive applications and in particular our web authentication servers have a problem as suddenly things start appearing to be in the future which is treated as an error... The autoyast snippet we use to do the ntp client config is (I have obfuscated the ip addresses of the NTP servers): <quote> <ntp-client> <peers config:type="list"> <peer> <initial config:type="boolean">false</initial> <key>server</key> <value>blah0.blah.blah</value> </peer> <peer> <initial config:type="boolean">false</initial> <key>server</key> <value>blah1.blah.blah</value> </peer> <peer> <initial config:type="boolean">false</initial> <key>server</key> <value>blah2.blah.blah</value> </peer> </peers> <start_at_boot config:type="boolean">true</start_at_boot> </ntp-client> </quote> This results in this ntp config file: <quote> server blah0.blah.blah server blah1.blah.blah server blah2.blah.blah # alternate log file # logconfig =syncstatus + sysevents # logconfig =all # statsdir /tmp/ # directory for statistics files # filegen peerstats file peerstats type day enable # filegen loopstats file loopstats type day enable # filegen clockstats file clockstats type day enable # # Authentication stuff # # keys /etc/ntp.keys # path for keys file # trustedkey 1 2 3 4 5 6 14 15 # define trusted keys # requestkey 15 # key (7) for accessing server variables # controlkey 15 # key (6) for accessing server variables </quote> Is this a bug or are we missing some magic line(s) in the autoyast profile to cause a drift file to be added so our web authentication servers stop being confused when they are rebooted? The autoyast documentation does not seem to suggest that there is a way to configure a drift file in the autoyast profile so I think this is a bug with autoyast... Thanks a lot in advance! Best regards, Anton -- Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @) Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK Linux NTFS maintainer, http://www.linux-ntfs.org/ -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 4

[opensuse-autoinstall] SLES10 updates failing even though signature-handling set
by Mike Marion 28 Mar '07

28 Mar '07

While working on a SLES10 image, I'm running into a problem where it's ignoring my updates path, even though I've signed content and put the key into the initrd file, and included the signature parts in the profile: My general section looks like: <general> <mode> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">false</forceboot> </mode> <mouse> <id>none</id> </mouse> <signature_handling> <accept_file_without_checksum config:type="boolean">true</accept_file_without_checksum> <accept_unsigned_file config:type="boolean">true</accept_unsigned_file> <accept_unknown_gpg_key config:type="boolean">true</accept_unknown_gpg_key> <accept_verification_failed config:type="boolean">true</accept_verification_failed> </signature_handling> </general> but I still get "Can't find packages openafs, openafs-client, openafs-devel" (Our builds of openafs) that are in updates, and y2log shows: 2007-03-26 18:16:35 <0> 10.42.37.135(3306) [zypp] ExternalProgram.cc(checkStatus):333 pid 3816 successfully completed 2007-03-26 18:16:35 <1> 10.42.37.135(3306) [zypp::KeyRing] KeyRing.cc(verifyFileSignatureWorkflow):328 File [/var/tmp/TmpDir.CnJ7LU/DATA/content] ( /content (nfs://10.46.16.35/local/mnt/x86_64/sles10/updates) ) signed with unknown key [] 2007-03-26 18:16:35 <1> 10.42.37.135(3306) [zypp::KeyRing] KeyRing.cc(verifyFileSignatureWorkflow):336 User does not want to accept unknown key 2007-03-26 18:16:35 <5> 10.42.37.135(3306) [base] Exception.cc(log):94 SuseTagsImpl.cc(downloadMetadata):261 THROW: SuseTagsImpl.cc(downloadMetadata):261: Error. Source signature does not validate and user does not want to continue. 2007-03-26 18:16:35 <0> 10.42.37.135(3306) [zypp] PathInfo.cc(_Log_Result):295 recursive_rmdir /var/tmp/TmpDir.CnJ7LU 2007-03-26 18:16:35 <0> 10.42.37.135(3306) [zypp] TmpPath.cc(~Impl):78 TmpPath cleaned up /var/tmp/TmpDir.CnJ7LU{d 0700 0/0} 2007-03-26 18:16:35 <5> 10.42.37.135(3306) [base] Exception.cc(log):94 SuseTagsImpl.cc(saveMetadataTo):339 THROW: SuseTagsImpl.cc(saveMetadataTo):339: Downloading metadata failed (is a susetags source?) or user did not accept remote source. Aborting refresh. It explicitly says "User does not want to accept unknown key" which isn't true. An almost identical setup for SLED10 is working (it's updates path was create with create_update_source.sh from SLED10, the above from the SLES10 version of the script). The key also shouldn't show up as unknown (I would think) since it had imported the key left in the initrd. Also.. there seem to be tons of things missing from the dtd files so that using xmllint --valid is basically useless because things like signature_handling aren't even defined (nor are it's interior bits). I have applied the sles10 root fix v.4 script too. -- Mike Marion-Unix SysAdmin/Staff IT Engineer-http://www.qualcomm.com Peggy: "12 years old and drinking a beer!?!" Bobby: "I didn't even like it!" Hank: "Well now you're just trying to get me mad!" ==> King of the Hill -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 3

[opensuse-autoinstall] Issues during the auto-installation of SLES 10 with autoyast scripts!!! Pls help!!
by chengnt＠lenovo.com 28 Mar '07

28 Mar '07

Hi, all, When we develop the software, one tough issue happens during the auto-installation of SLES 10 with autoyast scripts (see below). Pls give us some suggestions or solutions to this issue. Look forward to your reply. Thanks!! [Issue summary]:Autoinstall SLES10 with autoyast scripts. If there are four primary partitions on the disk, three of them are used to install OS, then the fourth partition can not be remained. Why? And how to keep the fourth primary partition? [Issue details] Partition List： Device Boot Start End Blocks Id System /dev/hdc1 * 1 582 293296+ 83 Linux /dev/hdc2 583 1746 586656 82 Linux swap /dev/hdc3 1747 17248 7813008 83 Linux /dev/hdc4 17249 39770 11351088 83 Linux SLES10 is planned to install on the previous three partitions: /dev/hdc1---------/boot, formatted as ext2 in advanced, put autoinstall scripts on this partition(path: /prep/autoinst.xml) /dev/hdc2---------swap, formatted in the process of auto-install /dev/hdc3---------/, formatted as reiser in the process of auto-install /dev/hdc4-------suppose that this partition is a data section need to be remained. Step 1: make auto-install scripts - "autoinst.xml" as follows: Reference to http://forgeftp.novell.com/yast/doc/SLES10/autoinstall/CreateProfile.Partit… ... <partitioning config:type="list"> <drive> <device>/dev/hdc</device> <partitions config:type="list"> <partition> <create config:type="boolean">false</create> <format config:type="boolean">false</format> <mount>/boot</mount> <partition_nr config:type="integer">1</partition_nr> </partition> <partition> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">swap</filesystem> <partition_nr config:type="integer">2</partition_nr> <mount>swap</mount> </partition> <partition> <create config:type="boolean">false</create> <format config:type="boolean">true</format> <filesystem config:type="symbol">reiser</filesystem> <mount>/</mount> <partition_nr config:type="integer">3</partition_nr> </partition> </partitions> <use>1,2,3</use> </drive> </partitioning> ... Step 2: Boot by SLES10 DVD, set startup parameter: autoyast=device://hdc1/prep/autoinst.xml Step 3: The error would be prompted when the process comes to "Create Partition Plan". Then the installation would abort. At this time, check /var/log/YaST2/y2log, we have found that error exists in /usr/share/YaST2/include/autoinstall/autopart.ycp. Try other way: 1>Change scripts like <use>linux</use> or <use>all</use> No error would be promped. But the fourth primary partition - hdc4 is deleted. 2>Make use of OpenSUSE 10.2 DVD to boot system and don't change scripts (keep the same script above). The whole process of auto-install is normal. 3>When the error happens, /usr/share/YaST2/include/autoinstall/autopart.ycp is replaced by autopart.ycp of OpenSUSE10.2. Then rebuild /usr/share/YaST2/modules/AutoinstStorage.ycp to generate AutoinstStorage.ybc. After updating this new AutoinstStorage.ybc in SLES10, the whole process of auto-install is normal. Whether is this one bug of SLES 10? Furthermore, if the fourth partition is extended section (see below), the auto-install of SLES 10 is also ok. /dev/hdc1 * 1 582 293296+ 83 Linux /dev/hdc2 583 1746 586656 82 Linux swap /dev/hdc3 1747 17248 7813008 83 Linux /dev/hdc4 17249 39770 11351088 5 Extended /dev/hdc5 17249 39770 11351056+ 83 Linux By the way, refer to http://www.suse.de/~ug/autoyast_changes_SLES10SP1.html, SLES10SP1 has resolved this issue on the condition of four primary partitions. Is that right? Pls confirm it. If it's true, when will SLES10SP1 be released? Best Regards! ***************************************** Cheng Ningting(Carol Cheng) Server Business Department Lenovo Group Limited 6#,ShangDi ChuangYe Road,HaiDian,BEIJING TEL：（010）58864185 E_Mail：chengnt(a)lenovo.com **************************************** We are the new, we are the future, we are LENOVO!

3 5

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall March 2007