From: Corvus Corax <eric.noack@gmx.de>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] /etc/init.d the real question!?
Date: Mon, 11 Mar 2002 23:33:37 +0100 [thread overview]
Message-ID: <20020311223337.C578A173653@VikingPC.home> (raw)
In-Reply-To: <Pine.LNX.4.21.0203111640580.6352-100000@lucifer.evil-core.com>
This topic goes quite long now doesnt it?
Is it realle the question if /etc/init.d should be masked or not?
Since every user is able to change this himself i`d like to say the real
question is:
What initial knowledge requirements should a newbee GENTOO USER have?
Here comes a list, what i think a gentoo user needs to know till now to
install a new gentoo onto his mashine:
general LINUX knowledge -- the user should have used Linux before
knowledge of bash -- you need it to install at least base-layout
knowledge of nano / vi -- without knowing how to use an editor he is lost <g>
knowledge how to setup
either LAN
or PPPd / dialin
or ADSL /cable / ... -- without the user wont get a single ebuild
installed
knowledge how to configure
the kernel -- imagine one who has never made the
make menuconfig && make dep && make clean && make bzImage &&
make modules && make modules_install &&
cp arch/i386/boot/bzImage /boot ... --->completely LOST!
knowledge how to setup
his preferred boot-loader -- which does he want? grub? lilo?, ... but you
need one.
knowledge how to compile -- should know about the usual ./configure &&
make && make install series or not?
knowledge of the portage sys -- a user who trys to install gentoo without
having read the docs on gentoo.org? ooops <g>
to be continued...
Hmmm don't you think a user who got thus far doesnt know how the init process
works, and what he has to do with the ._cfg00?_* files ? especially since
emerge prompts for them after every installed ebuild?
my opinion, as an gentoo user --- Corvus V Corax
next prev parent reply other threads:[~2002-03-11 22:37 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-11 17:48 [gentoo-dev] /etc/init.d Yannick Koehler
2002-03-11 17:52 ` Matt Beland
2002-03-11 17:54 ` Ric Mesier
2002-03-11 18:43 ` Benjamin Ritcey
2002-03-11 18:45 ` Ric Mesier
2002-03-11 18:47 ` Ric Mesier
2002-03-11 19:55 ` Ian Smith
2002-03-11 18:02 ` Craig M. Reece
2002-03-11 18:16 ` Yannick Koehler
2002-03-11 18:52 ` mbutcher
2002-03-11 19:05 ` Craig M. Reece
2002-03-11 21:11 ` Yannick Koehler
2002-03-11 18:54 ` Matt Beland
2002-03-11 19:43 ` Martin Schlemmer
2002-03-11 20:44 ` Yannick Koehler
2002-03-11 21:10 ` Martin Schlemmer
2002-03-11 22:16 ` Matt Beland
2002-03-11 23:28 ` Yannick Koehler
2002-03-11 18:45 ` Per Wigren
2002-03-11 19:06 ` Craig M. Reece
2002-03-11 19:35 ` Yannick Koehler
2002-03-11 18:17 ` Yannick Koehler
2002-03-11 18:42 ` Matt Beland
2002-03-11 19:32 ` Yannick Koehler
2002-03-11 19:37 ` Ric Mesier
2002-03-11 21:13 ` Yannick Koehler
2002-03-11 22:07 ` Defresne Sylvain
2002-03-11 22:42 ` Ian Smith
2002-03-11 22:49 ` Defresne Sylvain
2002-03-11 22:55 ` Martin Schlemmer
2002-03-11 23:12 ` Ian Smith
2002-03-11 23:29 ` Yannick Koehler
2002-03-11 22:28 ` Ian Smith
2002-03-11 22:33 ` Ian Smith
2002-03-11 19:50 ` Martin Schlemmer
2002-03-11 19:56 ` Matt Beland
2002-03-11 21:25 ` Yannick Koehler
2002-03-11 18:41 ` Thilo Bangert
2002-03-11 19:49 ` Joachim Blaabjerg
2002-03-11 21:15 ` Yannick Koehler
2002-03-11 21:03 ` Tod M. Neidt
2002-03-11 21:30 ` Yannick Koehler
2002-03-11 16:26 ` Bob Phan
2002-03-11 21:39 ` Craig M. Reece
2002-03-11 16:42 ` Bob Phan
2002-03-11 22:33 ` Corvus Corax [this message]
2002-03-11 23:33 ` [gentoo-dev] /etc/init.d the real question!? Yannick Koehler
2002-03-12 11:03 ` [gentoo-dev] /etc/init.d Craig M. Reece
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=20020311223337.C578A173653@VikingPC.home \
--to=eric.noack@gmx.de \
--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