Andreas Jaeger wrote:
Let's not discuss "we need this pattern as well" - but let's discuss and agree on the general framework
this seems very promising and then let's discuss adding
further patterns.
we should add a role "hardware". We should be able to build install cd/dvd on the role base (for example, desktop computers don't need pcmcia, old box don't need sata, some boxes are all scsi or (mostly) no scsi at all) patterns should be more refined. There is a lot of things completely unusefull in the Base packages (for some uses); So we should have * a very minimal set. may be only static kernel, skel. only text console access, neither yast - ideally floppy boot :-) and then a Yast pattern, a X pattern, a sax pattern (may be a SUSE pattern with yast and sax :-) the main difficulty I see is rewriting the rpm dependencies (devs tend to add dependencies to be sure the product run anywhere), but may be the build service can adress this? basically, If I understand well, anybody could go to the build service, load a form, answer detailed questions about his goals and his hardware and use net install. on this respect, it would be very interesting to have an utility (boot floppy or cd, like memtest) that do a hardware check and report; The same thing that is done at install time, but without the installer, just check. May be say "your computer is ready for Linux", or "this part can be a problem". I know this is what is done mostly by the installer, but I think it should be good to have it separated. Any body is anxious when putting an "install" cd on a reader (will this erase my computer?), a diagnostic cd is not so frightening :-) jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory-help@opensuse.org