| 1 |
Well I for one would be completely SOL without it, my isp is sane and |
| 2 |
doesn't use PPPoE thank god. They do however use DHCP. And in case your |
| 3 |
wondering who my ISP is, it's Comcast Cable, which probably has more |
| 4 |
users than SOHO DSL. It isn't as if they are a little ISP. |
| 5 |
|
| 6 |
Also, every wireless gateway on the planet uses DHCP, same goes for |
| 7 |
basic firewall boxes. |
| 8 |
|
| 9 |
I don't see the need to tell all those users that they have to do |
| 10 |
additional things in order to get thier box on the net during the |
| 11 |
install process. Do you? It doesn't hurt anything to leave it. |
| 12 |
|
| 13 |
my .02 cents... |
| 14 |
|
| 15 |
Kevyn |
| 16 |
|
| 17 |
On Sat, 2003-08-23 at 12:29, Stewart Honsberger wrote: |
| 18 |
> Marius Mauch wrote: |
| 19 |
> |
| 20 |
> > what's the reason for dhcpcd being in the system profile |
| 21 |
> [...] |
| 22 |
> |
| 23 |
> I agree completely. I maintain several Gentoo workstations that use |
| 24 |
> PPPoE, static IPs, or ISC's DHCP server/client. On only a scant handfull |
| 25 |
> of workstations do I use dhcpcd. |
| 26 |
> |
| 27 |
> I imagine with the popularity of SOHO ADSL, statically configured LANs |
| 28 |
> et al. dhcpcd is rather useless to a large percentage of our userbase. |
| 29 |
> |
| 30 |
> Perhaps it could/should be relegated to the cron / syslog / kernel |
| 31 |
> section of the install guide - eg, another optional component after the |
| 32 |
> system is merged. |
| 33 |
> |
| 34 |
> I, for one, have always advocated that the base system be just that - |
| 35 |
> enough to make the system useable upon first boot. Enough to allow root |
| 36 |
> to log in and merge functionality and nothing more. |
| 37 |
> |
| 38 |
> Besides, then we can start a running tally; "Three years without an |
| 39 |
> exploit in our base install!" (Apologies to Theo) |
Archives