Hi Anas, Anas Nashif wrote:
1) One cannot specify the disk option for lilo.conf. This is very bad if you have a host with scsi and ide disks and want to boot from the scsi disk.
Cant you do that with <location> ?
sorry, I was not precise here. I meant stuff like this: disk=/dev/sda bios=0x80 disk=/dev/hda bios=0x81 Anyway, there is this other bug I reported back in January which inserts the wrong boot device (hda even if sda was specified), so we have to boot manually once anyway during the installation of our scsi servers :-) It would be nice if that bug would be fixed in the next release...
3) It would be nice if you could include special kernel packages to be used outside of the general package repository, ...
This should be possible. You can always create a new source tree a la SLES with your customized packages.
Ah, ok, I will try this! I missed that this was possible!
5) Please bring back that fstab-search feature :-) It ...
Its already back :) Check it out on the next release.
Cool :-))) Thanks a lot! Will it, by the way, be possible to use the autoyast from SuSE 9.1 for 9.0 e.g.? Or are all the versions tied to their SuSE releases?
6) I would like to specify a rule without condition in rules.xml. Reason is to add a general profile ...
Note that you can also use classes. For example in my test env. I keep all partitioning data out of the profile and include them using classes. It works great. This of course combined with rules works also.
There I have a general problem, because from the online documentation I couldn't figure out how and where exactly I could use classes, especially in rules.xml. I wrote this in the January mail, too, that I could not insert classes anywhere without the xml validator complaining. The website is also not very detailed in this point (combining rules and classes), so I tried to check from the dtd where I could include classes. But the main problem was that when inserted any class in rules.xml, I couldn't validate automatically anymore (we do this always by some scripts before starting an installation). If you could send me an example for classes in rules.xml or maybe your profile example using classes for partitioning data, that would help me lot!
9) An easy way to add general includes would be nice. The entity include mechanism does not work in rules.xml. As we have to specify about 40 partition rules (depending on the IP and the type), we would like to use a separate file for this and include it to keep rules.xml small.
Dont understand what you mean here.
That was connected to point 6) (bad sorting I did there ;-)) Since I wasn't able (or just too stupid :-)) to work with classes in rules.xml, I had to put all the 40 rules for partition matching in the rules.xml itself. You wrote in some older mail on this list that one could use the general include mechanism for xml to include parts of profiles into others, i.e., defining another xml file as entity and including it in the body with &whatever;. I don't remember if that worked for normal profiles, anyway, it does not work for rules.xml because the file to be included is not transfered. So the idea here was just "write some line into rules.xml causing it to include some other rules file". I think if I understand how to use classes in rules.xml, I have everything I need! About all the other points let me just say "thanks a lot" for at considering them, and I will just be happy if some of the features might make it into some release one day :-) cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: -4054 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *