public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Yuri K. Shatroff" <yks-uno@yandex.ru>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: stage3 only for i486?
Date: Thu, 04 Apr 2013 12:15:55 +0400	[thread overview]
Message-ID: <515D36BB.7010804@yandex.ru> (raw)
In-Reply-To: <515C84C5.1050005@gmail.com>

On 03.04.2013 23:36, Alan McKinnon wrote:
>
> The reason I say Gentoo shouldn't worry about installers is that the
> typical person installing Gentoo already knows about chroots. Someone
> who doesn't is unlikely to consider Gentoo at all (unless they are
> looking to rice, but we long since moved past that).

As for me, the Gentoo installation process is really much easier than 
that of some installer-based distros. Regardless of knowledge of what 
chroot is, if one follows the (very well written and detailed) 
installation docs, he'd get Gentoo installed with far less effort than 
trying to make out what all these fancy buttons and menus mean in a 
graphical installer.
And from an already-user-of-another-distro point of view, it's even more 
attractive that he can install and tune Gentoo from his 
already-installed linux, not even wasting time writing CDs, booting and 
stuff.

And the guys around here confirmed that they hadn't had problems with 
chroot :)

> This idea will of course not be popular, I'll be told I'm trying to be
> elitist, and so the search for the perfect installer will continue unabated

Well, an installer certainly would find its users. But none is perfect, 
and writing another (imperfect) one exclusively for Gentoo is sort of 
wasting time. A "true" Gentoo way IMO would be a selection of installers 
on the installation medium ;-) But AFAICT it is this idea that wouldn't 
be popular, rather than leaving no-installer at all.
Regarding elitism, can the absence of an installer be considered elite? 
:) I'd rather call 'elite' e.g. the OpenSUSE installer (a claim for 
elite, at least).
Probably it's time for me to agree with the 'Gentoo is what it is' 
pattern I had argued against a month ago. =)

-- 
Best wishes,
Yuri K. Shatroff


  parent reply	other threads:[~2013-04-04  8:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-02 17:51 [gentoo-user] stage3 only for i486? Davide Carnovale
2013-04-02 18:12 ` Michael Hampicke
2013-04-02 18:17 ` Bruce Hill
2013-04-02 18:31   ` Davide Carnovale
2013-04-02 19:17 ` Alan McKinnon
2013-04-02 19:40   ` Davide Carnovale
2013-04-02 20:28     ` Alan McKinnon
2013-04-03 18:44       ` [gentoo-user] " James
2013-04-03 19:36         ` Alan McKinnon
2013-04-04  3:05           ` [gentoo-user] " Stroller
2013-04-04  7:48             ` Davide Carnovale
2013-04-04  8:15           ` Yuri K. Shatroff [this message]
2013-04-04  9:06             ` [gentoo-user] " Alan McKinnon
2013-04-04 12:30               ` Joshua Murphy
2013-04-04 18:02               ` Philip Webb
2013-04-02 23:41   ` [gentoo-user] " Daniel Frey
2013-04-03  1:20     ` Raymond Jennings
2013-04-03  7:59     ` Alan McKinnon
2013-04-03 15:37       ` Peter Humphrey
2013-04-03 19:14         ` Alan McKinnon
2013-04-02 21:01 ` Francesco Talamona
2013-04-02 22:02   ` Davide Carnovale

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=515D36BB.7010804@yandex.ru \
    --to=yks-uno@yandex.ru \
    --cc=gentoo-user@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