Am Donnerstag, 1. Juni 2006 12:29 schrieb Uwe Gansert:
that's right. Both ways work. There often is a third way of just dropping the <device>...</device> line from the profile. Autoyast starts guessing then which often works too (depends a bit on the hardware and bios).
This method worked. However there are still some strange issues. First of all. If I include a <use>all</use> directive everything works except for the fact that the bootloader config is of course created for the proposed partitioning scheme, the one I actually do not want to use. Next I tried <use>linux</use> this worked on one host but on another (IBM laptop) the installtion failed again when the partitioning plan was set up. However the laptop had a linux boot, root and swap partiton on it, but it seems autoyast failed to reuse it. There were two additional windows and a hidden IBM service partition on the disk as well. Perhaps this caused the problem. Even if the reuse works, the bootloader config is still wrong (wrong root partition in grub config). I completely removed the bootloader section from the autoyast file, thinking that in this cast yast would propose a default one fitting the partitioning scheme, but this did not work as expected. I could however remove the proposed (wrong) grub config in yast and have yast create a new proposal which was correct then. Are there any know problems with this? Thnaks Rainer -- --------------------------------------------------------------------------- Rainer Krienke, Universitaet Koblenz, Rechenzentrum, Raum A022 Universitaetsstrasse 1, 56070 Koblenz, Tel: +49 261287 -1312, Fax: -1001312 Mail: krienke@uni-koblenz.de, Web: http://www.uni-koblenz.de/~krienke Get my public PGP key: http://www.uni-koblenz.de/~krienke/mypgp.html ---------------------------------------------------------------------------