public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Lang <mwlang@cybrains.net>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] New Install Instructions
Date: Fri, 15 Mar 2002 01:34:55 -0500	[thread overview]
Message-ID: <5.1.0.14.2.20020315013412.0207d7e8@mail.cybrains.net> (raw)

Here are the new install instructions.  Not knowing the "proper" way to put 
this out for review, I have put it up at the following URL (my pardons if 
this breaks any protocols):

http://www.gibberishcode.net/gentoo-web/xsl/build.html

What to expect:

The first half has been completely overhauled to allow more than one method 
of documentation to be written.   I tried to take scattered notes about the 
system requirements and misc notes and collect them into an overview so 
that we weren't losing valuable info in cluttered notes and "oh, by the 
way" sort of remarks.

I felt that it was starting to get confusing talking about both fast-binary 
and from scratch installation methods in one sweep and it would've gotten 
really confusing with interlacing the third method, which I have written 
here for installing from existing distro.

This reorganization leads to _some_ duplication of material which you will 
see at the modprobe area, but I figured this was better than mingling the 
different install processes (and thus overly confusing the reader).

I didn't incorporate the altinstall doc which has installation over network 
instructions, but this can probably be easily incorporated if desired.

Most of the changes take place before the Setting up Partitions 
chapter.  Notes were inserted as appropriate after this point.

A section for Lilo was added as I figured this is a common occurrence for 
those converting over from existing distro.  In any event, I have no 
experience with Grub, so I can't comment on how to convert a Lilo system to 
grub.

Please keep in mind that I am a Linux newbie, so if I said something that 
made absolutely no sense or is completely wrong, then please definitely let 
me know without totally trashing me.  I made a lot of assumptions and 
"interpretation" of what Linux is doing on the system level based on my 
experience with Windoze.

There is a completely commented out section (search for BAH).  If you can 
offer some insights here, that would be great.

Regards,

Michael Lang

President
www.cybrains.net

"All things should be as simple as possible, but no simpler" -- Albert Einstein



             reply	other threads:[~2002-03-15  6:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-15  6:34 Michael Lang [this message]
2002-03-15  7:39 ` [gentoo-dev] New Install Instructions 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
  -- strict thread matches above, loose matches on Subject: below --
2002-03-15 19:19 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

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=5.1.0.14.2.20020315013412.0207d7e8@mail.cybrains.net \
    --to=mwlang@cybrains.net \
    --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