From: Brad Laue <brad@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] reason for dhcpcd in system profile ?
Date: Sun, 24 Aug 2003 11:09:56 -0400 [thread overview]
Message-ID: <3F48D544.80005@gentoo.org> (raw)
In-Reply-To: <1061714007.6740.38.camel@localhost>
Kevyn Shortell wrote:
> I'd have to take a guess that Comcast in California has more DHCP cable
> customers than Canada has broadband customers.
Bell Canada's Sympatico service started out as the driving force behind
the development of PPPoE clients under Linux, and the past two releases
of both Mandrake and RedHat have in fact included built-in support and
configuration frontends that enable a user to get online with minimal
hassle.
Re: the sanity of choosing DHCP over PPPoE, the main perceived drawback
is the dynamic IP. This is a management issue - PPPoE is as capable of
delivering a static IP to the user as standard PPP is. As for
encapsulation overhead, 1meg and 3meg service render this unnoticeable
to the user (it may perhaps be 'less efficient' from a purist
standpoint, but these are residential connections we're talking about).
At any rate, seeing as both PPPoE and DHCP are not as universal as
ethernet (which requires the presence of such utilities as ifconfig in
the basic system), and are both really fast emerges, wouldn't they
contribute to a nice small base system? They seem more reasonable
choices than some of the other suggestions I'm seeing.
> I agree that pruning the base system is probably a good idea, but why
> look at basic network components that atleast half of our users require
> in order to get their machine on the net?
Because they're options, and options are not defaults. :P
Brad
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-08-24 15:10 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 [this message]
2003-08-24 20:41 ` Kevyn Shortell
2003-08-23 21:25 ` Norberto BENSA
2003-08-23 20:34 ` Yuri Enshin
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=3F48D544.80005@gentoo.org \
--to=brad@gentoo.org \
--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