Live data from Hacker News

Rapid DHCP: Or, how do Macs get on the network so fast? (2011)

cafbit.com

111–114 of 114 posts

Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)

#111
post #56

Earlier quoted context omitted.

DHCP activity from 4 devices will not slow your network, much less take it down. A DHCP negotiation to get an IP address takes 4 UDP packets, all of them usually below 500 bytes in size. Not even when you have set the lease time to the theoretical minimum of 1s, this traffic will be at all significant in your network.

It will kill my fiber to the home network box that my telco installed, and provides DHCP. It isn't a load issue, it is a "the DHCP server died" issue

I would be talking to my telco in this instance.

Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)

#112

Earlier quoted context omitted.

HN isn't in the mood for levity today....

maybe he was laughing too hard and spit out the coffee that was in the person's mouth

That is indeed what happened. Unfortunately, HN has become so fucking dour, and mindless downvoting is quickly replacing interesting discourse. This is no longer a place for some occasional lighthearted discourse.

Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)

#113
post #103
post #100

Earlier quoted context omitted.

You misunderstood my numbers :) Search "chromebook boot time" on YouTube. Checkout the comparisons between a $200 chromebook from 2013 and a $2000 MBP...

ChromeOS is not a real OS. It's an embedded appliance/cloud OS as a gateway to the web and Google services. Anyone can make a machine boot fast if it has nothing to load.

It's gentoo based. Just because its DE is basically just chrome doesn't make it any less of an OS. Hell, you can even run another OS in a chroot on it.

You'll get similar performance if you put your OS on an SSD, and select services that minimize your boot time.

Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)

#114
post #113
post #103

Earlier quoted context omitted.

ChromeOS is not a real OS. It's an embedded appliance/cloud OS as a gateway to the web and Google services. Anyone can make a machine boot fast if it has nothing to load.

It's gentoo based. Just because its DE is basically just chrome doesn't make it any less of an OS. Hell, you can even run another OS in a chroot on it. You'll get similar performance if you put your OS on an SSD, and select services that minimize your boot time.

Can I join it to my AD infrastructure? Can I access network shares (NFS/SMB) ? I could list off a million "Can I...?" questions but the fact remains that it's a Google Chrome appliance. The detail that hidden underneath is a Linux/Gentoo base is irrelevant. This is no different than your PS4 which runs Orbis, a stripped down OS based on FreeBSD. It's not a real OS targeted for users who want a complete OS computing experience. It's an appliance with a single purpose built upon parts of an existing OS.
Post reply on HN