From: R0b0t1 <r030t1@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] install under centos606
Date: Tue, 22 Aug 2017 22:18:06 -0500 [thread overview]
Message-ID: <CAAD4mYh2Wuo1vhDBzZm1D39g8SsqmQreEVU9_0JS=po2oUOVyA@mail.gmail.com> (raw)
In-Reply-To: <00a7e64e-d392-ee42-be07-4d9899e5b755@monksofcool.net>
On Mon, Aug 21, 2017 at 7:08 AM, Ralph Seichter
<m16+gentoo@monksofcool.net> wrote:
> On 21.08.2017 13:49, mad.scientist.at.large@tutanota.com wrote:
>
>> I'm excited about using gentoo, though the online instructions could
>> really use more structuring, i.e. it's hard to avoid reading the parts
>> you don't need to and the "flow" is rather lost. It's an extremely
>> verbose document which makes it very hard to get the gist of the install
>> procedure. it's not a bad document, merely poorly organized. [...]
>
> I completely disagree. I consider the Gentoo installation documentation
> well structured, easy to follow and precise, and I don't know what your
> statements like "most newbies would be helplessly confused" are supposed
> to be based on. Please don't try to pass on your personal opinions as
> facts without providing any proof. Show us a control group of newbies,
> most of them helplessly confused, if you can. ;-)
>
I think most of the problem is all the handbook does is give you a
working system in the technical sense. Everything else is up to you to
discover, which can be very hard if you are lacking terminology or
very specific experience.
A good example of a more fully featured guide is Sakaki's EFI
Installation Guide
(https://wiki.gentoo.org/wiki/Sakaki's_EFI_Install_Guide). I have
proposed the handbook be updated, at least on an architecture-specific
basis, to reflect common installation options (as was it seems was
originally intended). However, the Handbook team seems very
conservative and hard to contact.
Among my suggestions were transferring the Handbook to Gollum, so the
pages could be managed from Git. Porting the whole Wiki to Gollum
might make it hard for normal users to contribute, but I suspect only
particularly adept users would have good contributions to the
Handbook.
R0b0t1.
next prev parent reply other threads:[~2017-08-23 3:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-19 18:28 [gentoo-user] Nameserver lookups fail on virtual server after Kernel upgrade from version 4.9 to 4.12 Ralph Seichter
2017-08-19 22:15 ` Craig MacKinder
2017-08-19 23:14 ` Ralph Seichter
2017-08-20 6:17 ` Neil Bothwick
2017-08-20 12:25 ` Ralph Seichter
2017-08-21 6:08 ` Neil Bothwick
2017-08-21 10:35 ` Ralph Seichter
2017-08-21 11:49 ` [gentoo-user] install under centos606 mad.scientist.at.large
2017-08-21 12:08 ` Ralph Seichter
2017-08-23 3:18 ` R0b0t1 [this message]
2017-08-21 13:03 ` Zhu Sha Zang
2017-08-21 19:18 ` Mick
2017-08-22 5:21 ` Stroller
2017-08-23 3:21 ` R0b0t1
2017-08-21 18:29 ` [gentoo-user] Nameserver lookups fail on virtual server after Kernel upgrade from version 4.9 to 4.12 Mick
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='CAAD4mYh2Wuo1vhDBzZm1D39g8SsqmQreEVU9_0JS=po2oUOVyA@mail.gmail.com' \
--to=r030t1@gmail.com \
--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