Feature changed by: Otso Rajala (daedaluz) Feature #305705, revision 21 Title: Types/Category of installation Hackweek V: Unconfirmed Priority Requester: Mandatory openSUSE-11.2: Rejected by Stephan Kulow (coolo) reject date: 2009-06-24 12:11:17 reject reason: for 11.2 this goes too deep and we didn't even start to think about implementation details. So whoever thinks about it, I suggest to do a more detailed proposal. The patterns were supposed to have more weight than just the package selection, but I guess most these settings can be bound to packages installed. E.g. Terminalserver and SUPER install max-performance, laptop installs battery-saving and both these packages conflict. But as I said: 11.3 material imo. Priority Requester: Important openSUSE-11.3: Evaluation Priority Requester: Important openSUSE-11.4: Unconfirmed Priority Requester: Mandatory Requested by: Agustin Chavarria (dj_ubun_1) Description: would be good, that at the time of installation opensuse, ask what you want to install, like a template, without having to go to edit to add software. System installation tweak with special packages, performance and settings for example * Office: max performance for OpenOffice, KOffice Evolution … * Laptop: Wifi Tool, Batterie saving, … * Webserver: minimal system performance, no many tool, apache …. * Linux Home Server: Webserver to configuation, special packages, samba, router, server, ... * Terminalserver: max performance, nx … * MTA Server: postfix all other packages clamav, avais-d… * SUPER SuSe: MAX performace an no many software * minimal Server: core packages, minimal X11, full networking (i.e. nfs, ssh, dhcp), minimal desktop (kde, gnome or xfce), with freenx to facilitate remote GUI admin, but the absolute smallest diskspace. Good for DataCenter server installs. * and other Category installations… developer install Discussion: #1: Claus Rebler (zunami) (2009-01-19 21:41:32) good idea System installation tweak with special packages, performance and settings for example: * Office: max performance for OpenOffice, KOffice Evolution … * Laptop: Wifi Tool, Batterie saving, … * Webserver: minimal system performance, no many tool, apache …. * Linux Home Server: Webserver to configuation, special packages, samba, router, server, ... * Terminalserver: max performance, nx … * MTA Server: postfix all other packages clamav, avais-d… * SUPER SuSe: MAX performace an no many software * Minimal Server: core packages, minimal X11, full networking (i.e. nfs, ssh, dhcp), minimal desktop (kde, gnome or xfce), with freenx to facilitate remote GUI admin, but the absolute smallest diskspace. Good for DataCenter server installs. * and other Category installations… #2: Rajko Matovic (rajko_m) (2009-03-30 01:44:57) Discussion in this thread has same topic: http://lists.opensuse.org/opensuse-project/2009-03/msg00233.html The benefits of proposed storage for user package selection and configuration files are many: * Streamline package management. When user wants more then one selection, all YaST has to provide is to merge few of them, or to extract parts that belong to unwanted. * Streamline process of user contribution to openSUSE in this area. This will end discussions what to include in default installation, which can be cut down to fewer basic desktop components and then user can import selection with few clicks. * Reuse experience of experts in different fields. They know what they need and what application is better for the particular purpose. It will be possible to create specialized selections that need few tweaks to come close to user wishes. * Developers can offer during installation few of popular package selections. What is popular can be found from download logs on server that will offer this. There is few questions to answer: * What else can be added as validation of package selections beside downloads? Five star system, for instance. * How to correct mistakes? * How to prevent malicious file to land on server? * How to motivate users to contribute? * Are there ready to go solutions, that we can reuse? #3: Andreas Jaeger (a_jaeger) (2009-06-09 14:30:44) I fear this gets rather complicated but let's evaluate it a bit. #4: Robert Davies (robopensuse) (2009-12-02 19:26:38) Debian Install (least expert version) has various "typical" use scenarios, with software selection based on those. These are similar to the broad pattern categories in YaST Software Manager. I don't think changing configuration settings for performance is a good idea. The reason is that it is liable to explode the number of configurations that need testing. If someone decides to tweak something like "echo 100 > /proc/sys/vm/swappiness" or "put /etc/stab entries barriers=0", and it exposes a bug, it is an isolated change and obvious. Asking volunteer test effort to try Web Server, Terminal Server, Home Server and Desktop, rather than taking & customising a core default system appears unrealistic. Finally in long run, as the kernel changes, what is a good idea for one release, becomes unecessary or counter productive in later releases. Creating code to do the tweaking is causing a maintenance burden. Example, 2.6.31 now enables relatime by default with 24 hour daily update tweak. Any past tweaks for "noatime" behaviour would now be dubious, and need discussing. + #5: Otso Rajala (daedaluz) (2010-08-16 02:42:27) + I recall how back in 2000 RedHat asked similar question during + installation. Mandrake efforts improved automatic hardware detection & + configuration so much, that it was done away with. I don't see point in + this, but the option of installing or removing additional software + during DVD install should be better presented. -- openSUSE Feature: https://features.opensuse.org/305705