On Thu, 2011-10-20 at 21:22 +0200, Nicolas Mailhot wrote: > Le jeudi 20 octobre 2011 à 13:08 -0500, Dan Williams a écrit : > > > If you architect a system that accounts for networking changing states, > > then it works for *everyone*. If you depend on networking always being > > there, then it only works for some subset of users that have one type of > > installation. Having one architecture and one codebase (that handles > > both cases) generally means easier maintenance, feature addition, and > > fewer bugs. > > Really, the problem with hardware handling changes in Fedora those past > years is not improved handling of changing states (which benefit every > kind of system), it's the way all those changes have been progressively > tied with the desktop session, and all the efforts to shut down > everything when no one is moving the local mice, or to make every > scenario single-device stopping the old one when a new 'better' one > appears. Note that NM has done multiple active devices for 3+ years... really, really old versions (0.6 and earlier) only allowed one active interface, but that was long ago fixed. Dan > Servers, desktops and permanent set-top boxes can have transient network > links too (typically, when a transient secure link has been established > from an admin node somewhere), but the way those transient links is used > is very different from the way laptop transient links are used (move > everything from wifi to cable and back when ethernet is > plugged/unplugged) > > > -- > Nicolas Mailhot > -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
