public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Brian Dwornick" <bdwor@comcast.net>
To: <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Installer For Gentoo
Date: Wed, 14 Jan 2004 16:09:10 -0500	[thread overview]
Message-ID: <001101c3dae2$a8596200$d30111ac@spider> (raw)
In-Reply-To: 4005682C.2070708@stevesworld.hopto.org

There are two very different reasons that I can see for making an installer.
One is to make it easier to install gentoo for people that are not
comfortable with linux.  This in my opinion would be a bad move as gentoo
isn't aimed to be the first linux distribution someone uses.  The seconds
reason would be to make it easier to install in a corporate enviroment
(server farms, multiple offices, etc.)  With this in mind, I believe an
"installer" should be implemented as a text based script, not a pretty GUI.
It should read a config file made by whoever is doing the install that has
many default configs in it and maybe prompt for the uses of the machine.
IE:

The following configs have been detected please choose one:
[0] Prompt for config
[1] Desktop (KDE)
[2] Laptop (KDE)
[3] Email/Web/DNS Server (No X)
[4] Rendering Farm
? 2

What stage would you like to start from?
[1]
[2]
[3]
...
At this point the installer could make choices that would produce the
optimal system but without the system admin having to sit and type the same
things over and over.  The make.conf could be generated by using /proc and
the settings from the loaded config.

Basically, distributions like Redhat make many decisions for you.  I would
hate to see an installer that took choices from the users hands, as, gentoo
seems to be about choice.

My two cents,
Brian

----- Original Message ----- 
From: "Stephen Clowater" <steve@stevesworld.hopto.org>
To: <gentoo-dev@lists.gentoo.org>
Sent: Wednesday, January 14, 2004 11:02 AM
Subject: [gentoo-dev] Installer For Gentoo

*snip*


--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2004-01-14 21:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-14 16:02 [gentoo-dev] Installer For Gentoo Stephen Clowater
2004-01-14 17:28 ` Patrick Lauer
2004-01-14 20:57   ` Stephen Clowater
2004-01-14 21:09 ` Brian Dwornick [this message]
2004-01-14 22:08   ` Patrick Lauer
2004-01-14 23:34     ` Brian Dwornick
2004-01-15  0:14       ` Jeff Griffiths
2004-01-15 10:04         ` Paul de Vrieze
2004-01-16  3:50         ` Drake Wyrm
2004-01-15  3:47   ` Eric Sammer
2004-01-15  2:58 ` Robin H. Johnson
2004-01-15 15:10   ` Stephen Clowater
2004-01-15 15:33     ` Chris Gianelloni
2004-01-15 20:50       ` Paul de Vrieze
2004-01-16  7:31 ` John Nilsson
2004-01-21  8:25 ` John White
  -- strict thread matches above, loose matches on Subject: below --
2002-05-31 21:31 [gentoo-dev] Installer for Gentoo Victor R. Prada
2002-06-01  8:49 ` Meir Kriheli
2002-06-01  9:20   ` Joshua Hansen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='001101c3dae2$a8596200$d30111ac@spider' \
    --to=bdwor@comcast.net \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox