Hello!
I found some very strange behaviour while trying to
let autoyast create partitions on /dev/hda and
/dev/hdb. The partitioning scheme I need is very
simple:
/dev/hda1 - /boot (primary, auto size, ext2)
/dev/hda2 - swap (primary, auto size)
/dev/hda3 - / (primary, max size, reiser)
/dev/hdb1 - /home (primary, max size, reiser)
Autoinstall was fine while I was using /dev/hda only.
But after /dev/hdb1 was added, yast2 died while
installing the RPMs - fried by the OOM-killer. I could
strip down the problem to a possible bug in autoyast.
The XML below contains only the partition info, it was
created from scratch with autoyast from SUSE 10.0 (but
SUSE 9.3 does the same). The partitioning in the first
interactive install screen says only "create /dev/hdb1
with reiserfs", all info from /dev/hda ist lost. With
my full autoinstall XML this screen was not shown, the
installer has no real root, uses the ramdisk - and
gets slayed some minutes later by the OOM-killer.
Can anyone comfirm this problem, or am I
misunderstanding some of the autoyast options (i.e.the
"primary" or the "auto/max")?
Thanks
Michael
---- snip
<?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">
<partitioning config:type="list">
<drive>
<device>/dev/hdb</device>
<initialize
config:type="boolean">true</initialize>
<partitions config:type="list">
<partition>
<crypt>twofish256</crypt>
<filesystem
config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<fstopt>noatime,acl,user_xattr</fstopt>
<label></label>