From: Yuri Enshin <kot@formoza-centre.ru>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] reason for dhcpcd in system profile ?
Date: Sun, 24 Aug 2003 00:34:02 +0400 [thread overview]
Message-ID: <3F47CFBA.7040805@formoza-centre.ru> (raw)
In-Reply-To: <20030823210429.57e7e85c.genone@genone.de>
Marius Mauch wrote:
>Hi,
>
>what's the reason for dhcpcd being in the system profile
>(default-x86-1.4 at least, haven't checked the others)? If it's only
>because it might be used in /etc/conf.d/net I think it should be
>removed, as there are IMO many users who don't need/want dhcpcd on their
>systems. I know there are a lot of people using dhcp for their network
>config, but why should that impose it on people not using it (e.g. I
>only need it on one of my three boxes)?
>Of course if I miss something obvious here please correct me.
>
>Marius
>
>--
>gentoo-dev@gentoo.org mailing list
>
>
>
Hmm... May be, extend your question?
Some users know all about linux, so no reason to include man and
man-pages in system.
Some users never change default console font or keyboard layout, so no
reason to include kbd or console-tools in system.
Some users have no ext2/ext3 partiotions, so no reason to include in
system e2fsprogs.
Some users never use 'emerge sync' (only download snapshots), so no
reason to include rsync.
Some users never use less, hdparm, fbset...
Some users have no network on computer at all, so no reason to include
any network related programs in system.
I can continue this list.
The reason for dhcpcd *in* system, IMHO: support for dhcp client - part
of universal, standart set of full-functional network-ready computer.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-08-23 20:33 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-23 19:04 [gentoo-dev] reason for dhcpcd in system profile ? Marius Mauch
2003-08-23 19:20 ` Wolfram Schlich
2003-08-23 20:23 ` Daniel Armyr
2003-08-23 21:20 ` Wolfram Schlich
2003-08-24 6:08 ` Daniel Armyr
2003-08-23 23:06 ` Luke-Jr
2003-08-24 3:21 ` A. Craig West
2003-08-24 8:59 ` Spider
2003-08-24 16:32 ` Alec Berryman
2003-08-24 16:44 ` Spider
2003-08-24 18:16 ` Paul de Vrieze
2003-08-24 18:40 ` Alec Berryman
2003-08-24 18:55 ` Andrew Gaffney
2003-08-24 18:47 ` Paul de Vrieze
2003-08-24 19:05 ` Andrew Gaffney
2003-08-24 19:03 ` Marius Mauch
2003-08-25 0:44 ` Andrew Gaffney
2003-08-25 0:48 ` Andrew Gaffney
2003-08-24 22:00 ` Grant Goodyear
2003-08-25 3:07 ` Luke-Jr
2003-08-23 19:29 ` Stewart Honsberger
2003-08-23 20:29 ` Kevyn Shortell
2003-08-24 7:22 ` Stewart Honsberger
2003-08-24 8:33 ` Kevyn Shortell
2003-08-24 15:09 ` Brad Laue
2003-08-24 20:41 ` Kevyn Shortell
2003-08-23 21:25 ` Norberto BENSA
2003-08-23 20:34 ` Yuri Enshin [this message]
2003-08-23 21:27 ` Norberto BENSA
2003-08-23 23:16 ` Luke-Jr
2003-08-24 8:15 ` Martin Schlemmer
2003-08-25 2:18 ` Luke-Jr
2003-08-25 4:24 ` Martin Schlemmer
2003-08-25 4:46 ` Martin Schlemmer
2003-08-25 13:46 ` Luke-Jr
2003-08-25 16:27 ` William Hubbs
2003-08-23 23:08 ` Lloyd D Budd
2003-08-24 4:28 ` Andrew Gaffney
2003-08-24 14:14 ` Marius Mauch
2003-08-24 14:33 ` Martin Schlemmer
2003-08-24 15:09 ` Paul de Vrieze
-- strict thread matches above, loose matches on Subject: below --
2003-08-24 20:40 Spider
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=3F47CFBA.7040805@formoza-centre.ru \
--to=kot@formoza-centre.ru \
--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