public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: George Shapovalov <georges@its.caltech.edu>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] New Install Instructions
Date: Wed, 20 Mar 2002 09:48:24 -0800	[thread overview]
Message-ID: <200203201746.JAA17959@chamber.cco.caltech.edu> (raw)
In-Reply-To: <3C98C5AD.5080005@nitech.com>

Ok, this is it :-).
I have been following the discussion of these new install instructions and my 
feeling is that it is about the right place now.  Adding many small 
specialized topics will make it large and hard for 1st read and step-trough 
installation.
However there definitely are people interested in that or another special 
topic, and it would be unfare to just draw the line and not accept anything 
new. 
So what about having one "basic" install guide and provide a link to a 
"special topic collection"? For which experts on certain topics willing to 
see the topic covered will write up a short paraghraph or two and send it to 
maintainer so it gets included? This is of course if maintainer accept new 
responsibility. He is doing a great job (and demanding one) already!
Just my 2 cents on this :-)

George

On Wednesday 20 March 2002 09:23, you wrote:
> How about adding a small section for installation of a software RAID
> system. It would be nice to show a brief overview of how to get this
> working...
>
> Michael Lang wrote:
> > At 01:19 PM 3/15/2002 -0600, you wrote:
> >> 1. In either the "/etc/localtime" or the "/etc/rc.conf" section add a
> >> note about setting "localtime" or "UTC", I thought that most people
> >> use localtime, so maybe it should be default in /etc/rc.conf(which is
> >> unrelated to this of course).
> >
> > What's the verdict on this one?  I think I put localtime, thinking UTC
> > might mess up my dual booting back to Windoze, but not sure.
> >
> >> 2. In the "Final Configuration" section you didn't mention lilo in
> >> summary since you added it; also, in the "lilo" section it almost
> >> seems like that is the next step, maybe show that you can do lilo or
> >> grub, user following down the list might not realise or may do both.
> >
> > Good points here.  Turned this into a Bootloader chapter with overview.
> >
> >> 3. Link or more info on USE flags would be awesome.
> >
> > I'm not really qualified to write about the USE flags.  Anybody want
> > to provide me with a paragraph or two?  Or if there's a url somewhere
> > covering this, please point me there.
> >
> >> 4. In the "Setting up partitions" section, note about ext2/3 being
> >> resizeable, xfs growth but not shrink, etc. would be helpful.  I
> >> realize you have a link to in-depth discusion about filesystems, but
> >> I don't think this was discussed in those articles either.  Also a
> >> not about parted and/or fips and other tools to modify partitions.
> >
> > Again, I'm not really qualified to write this up.  If there's any
> > volunteers or someone can point me to some good docs, I'll be glad to
> > add info to docs...however, I'm not sure we want to put *every* sort
> > of detail into the install docs as this tends to clutter it a good bit.
> >
> > I tried to clean up a lot of this clutter..while I have definitely
> > trimmed a lot of fluff out, I don't think I've deleted any actual
> > information, yet.  A lot of things got pushed to the top into the
> > Overview chapter and then where ever I spotted the info being
> > rehashed, I zapped it.
> >
> > One thing I'm curious about is the Important Note about being at
> > FOSDEM...is this a note affecting the vast majority of installers
> > (i.e. something that should definitely be left in), or is this a
> > highly targeted notes to Gentoo developers or from earlier Gentoo days?
> >
> >> 5. Booting section, maybe make link to 3 separate pages, rather than
> >> all in one, same with lilo and grub install section.
> >
> > I thought about doing this as well, but figured people might want to
> > be printing the guide out because they are potentially going to be
> > offline for a while while bringing new system on-line.  Any others
> > with feedback?
> >
> > I have been re-drafting as ideas come in.  Please check out latest
> > revisions at:
> >
> > http://www.gibberishcode.net/gentoo-web/xsl/build.html
> >
> > Michael
> >
> > President
> > www.cybrains.net
> >
> > "All things should be as simple as possible, but no simpler" -- Albert
> > Einstein
> >
> > _______________________________________________
> > gentoo-dev mailing list
> > gentoo-dev@gentoo.org
> > http://lists.gentoo.org/mailman/listinfo/gentoo-dev


  reply	other threads:[~2002-03-20 17:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-15 19:19 [gentoo-dev] New Install Instructions Nathan Nutter
2002-04-16 17:51 ` Michael Lang
2002-03-16 18:04   ` Avi Schwartz
2002-03-16 20:34     ` Daniel Robbins
2002-03-20 17:23   ` Steve Ackerman
2002-03-20 17:48     ` George Shapovalov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-15  6:34 Michael Lang
2002-03-15  7:39 ` George Shapovalov
2002-03-15 16:10   ` Michael Lang
2002-03-15 16:58     ` George Shapovalov
2002-03-15 15:56 ` Dan Armak
2002-03-15 17:11 ` Daniel Robbins
2002-03-15 20:35   ` Michael Lang
2002-03-15 22:14     ` Daniel Robbins

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=200203201746.JAA17959@chamber.cco.caltech.edu \
    --to=georges@its.caltech.edu \
    --cc=gentoo-dev@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