[00:08] perfect [00:08] thanks :) === ion__ is now known as ion_ [20:45] Keybuk: ping [20:48] hello [20:49] Keybuk: ah, you're around :) [20:50] briefly [20:50] what's up? [20:50] Keybuk: so what's been moving with upstart? I've been distracted for awhile so I haven't even seen if you've pushed code in awhile [20:50] busy coding on it ;) [20:50] no pushes though [20:50] keeping all the fun to yourself yet again :) [20:51] I'm doing what all the cool people (ie. git users) do [20:51] code in private, then rework all the commits before pushing [20:52] mostly just because I keep changing function names and filenames [20:52] and that kind of thing is hell for a revision control system [20:52] there's a NetworkManager Sucks flamewar on fedora-devel, which got me thinking about replacing NM with a series of upstart jobs [20:53] what do you think? [20:53] NM is just fine the way it is [20:53] eh. probably. [20:53] Upstart is just a service manager [20:53] I know [20:53] you'd still need the mechanism daemon and policy agent of NM [20:53] but what occurs to me is so is NM [20:54] just that NM would use Upstart's service manager for things like wpa, dhclient, etc. [20:54] which I've already talked to dcbw about [20:54] it occured to me awhile ago actually that reimplementing our sysvinit network service in Upstart would probably be most of NM [20:55] NM has a lot more know-how about things [20:56] that and it introduces some service relationships that we don't have now (the 'network' state is up when ANY of the 'interface' states are up EXCEPT the 'lo' interface..) [20:57] did you do any of that writeup/documentation stuff you wanted done? [20:57] not yet [20:59] damn. that means I have to do coursework now instead of hacking on stuff. [21:02] I apologize, but the problem was not a network one at all. The [21:02] problem was that the NetworkManager did not have dependencies [21:02] installed correctly, and turned out to be related to a peculiar [21:02] yum/Anaconda install scenario. [21:02] -- [21:02] so it wasn't even an NM problem? :p [21:04] Keybuk: wrong thread I'm guessing. [21:05] Keybuk: its the System Config Tools Cleanup Project thread [21:05] Keybuk: someone wanted to remove the system-config-network gui (which hasn't changed since like 1993) and people were like OMG THEY'RE GONNA MAKE US USE NETWORMANAGER!!!!!!