From: Thilo Bangert <thilo.bangert@gmx.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] FAQ
Date: Mon, 8 Apr 2002 21:59:09 +0200 [thread overview]
Message-ID: <20020408215909.03ad451d.thilo.bangert@gmx.net> (raw)
In-Reply-To: <1018294763.4266.8.camel@maas.wired>
On 08 Apr 2002 21:39:20 +0200
Erik Grinaker <erikg@wired-networks.net> wrote:
> On Mon, 2002-04-08 at 21:17, Thilo Bangert wrote:
>
> > well - this has come up pretty often lately....
> >
> > I can't use the gentoo boot cd - is there any other
> > way...
>
> Hmmm... I've just experienced the joys of completely reinstalling a
> server while it was actually running. That is, I installed gentoo on
> it while I had the RedHat installation running - and just replaced
> the services from the RedHat system with those from the Gentoo
> chroot one by one until everything ran from the Gentoo installation.
> I then did a quick reboot and had a fully functional Gentoo
> replacement system running. Downtime was two minutes.
>
great - i plan on doing this myself.
good to hear somebody already accomplished this...
(amazing downtime!)
> I can also contribute with maybe a bootdisk/netinstall and even a
> more automated installation process for people not really knowing
> what they are doing - if there is any interest for it
i've said this before: i wouldn't want to make it too easy for
people - thats what made gentoo really fun
yes, a steep learning curve will scare some people away, but it will
make tech support much more easy (in the long)
(perhaps this is all wrong, because then people just start
doing new stuff...)
also, gentoo is constantly under (more or less) heavy development
(getting better every day). brave newbies have no problem dealing
with that, but they can handle heavy documentation as well...
i don't want to kill your attempt on doing something good - i just
personally feel we should not lower the high standards (in terms
of dificulty or "heaviness") of the gentoo documentation
a dedicated gentoo floppy bootdisc really sounds like a good idea
just my 2 cents
regards
Thilo
next prev parent reply other threads:[~2002-04-08 19:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-06 4:49 [gentoo-dev] FAQ Glen Redden
2002-04-06 7:27 ` George Shapovalov
2002-04-05 22:44 ` Dan Armak
2002-04-06 19:30 ` Erik Grinaker
2002-04-06 19:44 ` Erik Grinaker
2002-04-07 4:29 ` George Shapovalov
2002-04-07 12:45 ` Erik Grinaker
2002-04-07 15:14 ` Spider
2002-04-06 8:14 ` Bjarke Sørensen
2002-04-08 19:17 ` Thilo Bangert
2002-04-08 19:39 ` Erik Grinaker
2002-04-08 19:59 ` Thilo Bangert [this message]
2002-04-08 20:22 ` Erik Grinaker
2002-04-08 20:28 ` Erik Grinaker
2002-04-08 20:47 ` Michael Frank
2002-04-08 21:40 ` Thilo Bangert
2002-04-09 0:27 ` Kain
2002-04-08 20:05 ` Michael Lang
2002-04-08 20:32 ` Erik Grinaker
2002-04-08 21:43 ` George Shapovalov
[not found] <20020405200404.D8AFE20F0D8C@chiba.3jane.net>
2002-04-05 19:17 ` Glen Redden
-- strict thread matches above, loose matches on Subject: below --
2002-04-05 18:15 Sean Mitchell
2002-04-05 18:27 ` Bjarke Sørensen
2002-04-05 20:02 ` George Shapovalov
[not found] <20020404232306.D13FE20F0B2D@chiba.3jane.net>
2002-04-04 23:48 ` Glen Redden
2002-04-05 6:41 ` Geert Bevin
2001-09-10 8:44 Djamil ESSAISSI
2001-09-10 8:57 ` Einar Karttunen
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=20020408215909.03ad451d.thilo.bangert@gmx.net \
--to=thilo.bangert@gmx.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