Earlier quoted context omitted.
That's all fine and dandy for the desktop case. But its a dhcp server , network admins would be expected to touch config files, and the interface for a DHCP server really can't be much worse than the GUI version that microsoft supplies! but digressions, to say "this is why I won't use a linux desktop" in response to a server-specific use-case, is at best antagonistic!
The used netgear router a friend gave me, does a fine job of getting my devices ip addresses on time without me touching the config.
Rapid DHCP: Or, how do Macs get on the network so fast? (2011)
41–50 of 114 posts
Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)
#42Earlier quoted context omitted.
An instruction like that is why I don't use Linux as a desktop!
I'm a bit disappointed that you're downvoted to grey right now because editing obscure config files and entering esoteric terminal commands is exactly why Linux is so difficult for the average user, and it's never going to improve if those who're already comfortable with it ignore the problem.
Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)
#43Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)
#44Earlier quoted context omitted.
I'm a bit disappointed that you're downvoted to grey right now because editing obscure config files and entering esoteric terminal commands is exactly why Linux is so difficult for the average user, and it's never going to improve if those who're already comfortable with it ignore the problem.
The windows equivalent to make such a change would be some kind of hidden module for that scm. Exe or whatever that obscure config tool is called.
Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)
#45Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)
#46Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)
#47Earlier quoted context omitted.
That's all fine and dandy for the desktop case. But its a dhcp server , network admins would be expected to touch config files, and the interface for a DHCP server really can't be much worse than the GUI version that microsoft supplies! but digressions, to say "this is why I won't use a linux desktop" in response to a server-specific use-case, is at best antagonistic!
The used netgear router a friend gave me, does a fine job of getting my devices ip addresses on time without me touching the config.
Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)
#48Earlier quoted context omitted.
The windows equivalent to make such a change would be some kind of hidden module for that scm. Exe or whatever that obscure config tool is called.
It would still be an easier to navigate GUI tool, possibly with tooltips and online help along the way, than manually editing /etc or /usr/share files.
Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)
#49This is nice, but kind of useless when waking up from deeper sleep states, which prevent the password dialog from receiving keystrokes for a good five seconds anyway (despite teasing a blinking cursor).
That blinking cursor is especially sneaky. When they just loaded up what is effectively a screenshot while everything loaded, that could've been forgiven (better than a blank screen I suppose). But animating it so that it LOOKS like it's working ...
Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)
#50I guess that modern macbooks keep the connection alive on the PHY level while asleep... they do have that "backup/sync while you sleep" feature, so quite possible that the chip handling this feature only speaks "normal" WPA2, keeps the connection alive and then after resuming the OS only has to re-check the IP address and does not have to do the full PHY handshake first...