Alex Smith wrote: > VMiklos wrote: > >> On Thu, Nov 02, 2006 at 02:23:21AM +0100, Gabriel C <[EMAIL PROTECTED]> >> wrote: >> >>> I think whatever *I* or the other like it or whatever not you will still >>> try to get some up_foo && up_foo_init_scripts runnig on Frugalware, >>> so the best thing is to *backup* the runit repo and rm -rf it. Then >>> start working on up_foo. The other problem I have with up_foo are the bugs >>> and afaik even on ****buntu are some weird bugs , which just means >>> forget the new init system for 0.6 because is way to late ( already ) >>> and up_foo >>> will need much more testing. >>> >> so the decision is to stop working on the runit repo and remove the "new >> init system" item from TODO-0.6? >> > > No need to remove from TODO. And no I won't rm -rf the runit repo, as I > explained on IRC. > > >> (btw i still like the idea of runit, but i don't have time to do it >> completely myself - i planned to help creating small patches like >> implemention missing --foreground options or small modifications to >> runit >> >> i mean i'm a bit surprised that now both of you started to dislike runit >> from one day to another :) and Alex stated his 2 objections - i offered >> to help solving both of them..) >> >> udv / greetings, >> VMiklos >> >> > > Also, > 13:10 <+crazy> now tell me ( without the event and *we need be experts > to write an init script ) changed to sysvinit > > You do not need to be an expert, once you learn how do do it, which took > me about 10 mins to learn, it's easy. >
you have too if you want *event* based init scripts ( maybe is why ****buntu still does not full use this but a weird symlink && whatever mix ). Of course we have to learn this bus is not the point and is not done in 10 minutes even the up_foo devel does NOT know ( yet ) how to solve some *event based stuff* ( is on up_foo ML && wiki ). The other thing is up_foo *does NOT support splashy nor uspalsh with this event stuff* *and* with the *event* stuff you have to make the init system depends()|rodepends() on 'udev,hal,dbus'. Shall I tell you more odd stuff ? or you want figure yourself ? Pls don't tell me now *but it can be done using sysvinit* I know this but the point is *we want to change sysvinit* and not replace by something add sysvinit back ... And again just do it , I don't want flame about I just think a 'init system' should be small , fast , ( not having weird depends ) , easy to understand ( not only for devels , think on server admins as example ) , of course is my opinion. crazy _______________________________________________ Frugalware-devel mailing list [email protected] http://frugalware.org/mailman/listinfo/frugalware-devel
