(Anas, this is identical to an email I sent to you yesterday - I forgo to CC it to suse-autoinstall@suse.com) Anas Nashif wrote:

* Phil Tregoning [Sep 19. 2002 19:31]:

...

Hi,

A few questions about NFS installs with AutoYaST and SuSE 8.0:

1) How can I use the graphical configuration tool to specify non-ReiserFS partitions that I want mounted but not formatted?

How do you want to mount a non-formatted partition? To mount a partition it has to have a valid filesystem. Or are you trying to do something else?

I want to try and use AutoYaST as an alternative to backups for root filesystems (with suitable change control). I want to format all the partitions on first install; then later on I want to reinstall, and not format but still mount /home (for example), For example: Install Format /dev/sda1 and mount as / Format /dev/sda2 as swap Format /dev/sdb1 and mount as /home Reinstall: Format /dev/sda1 and mount as / Format /dev/sda2 as swap Do NOT format /dev/sdb1, but still mount as /home This may not be a problem for me any more, because I don't think I will be able to use the graphical tool for what I want, and if I edit the XML manually and change format to false (but keep the filesystem type) it works fine.

...

3) Where the documentation says in 4.6.2 about customized packet selection:

Beside the pre-defined selections, you can create custom selections by providing a customized selection file in the selection directory.

Where is the "selection directory"? Does anybody have an example of what exactly to do to create and use your own customized packet selection? When I tried it, either the install barfed on installing the kernel (error 1 returned from the installation of "k_deflt"), or my customizations were ignored.

Selection directory is in suse/setup/descr on the CDs. Selections end with .sel.

A selection should have no conflicts and dependent packages should be added as well, if it cant be resolved automatically by rpm. k_deflt normally should not be included in the selection. Kernel is supplied using another resource in the control file.

Thanks. Given that, I will probably use individual packet specification in the XML on top of Minimal.sel, rather than write my own .sel files. That way I don't have to change the distribution directory if I want to add a package, only the XML profile. Do you have a .dtd or .xsl file that I can use with the XML profiles for editing and verification? I haven't been able to find one anywhere - there is some example .dtd in the manual, but it is only a subset. Phil T