to, 2011-01-13 kello 07:34 -0800, ext Arjan van de Ven kirjoitti: > On 1/13/2011 5:46 AM, Tapio Rantala wrote: > > Package sysvinit will not include actual sysvinit daemon anymore. Init > > scripts within fastinit will no longer be functional with original > > sysvinit as they are modified for upstart. > > I don't like that at all... > why would upstart package just not provide a complete replacement??????
There are several packages which require fastinit directly (xinetd, kbd, foomatic, openssh) and others that depend on init for processing /etc/init.d/ (corewatcher, dbus, dsme, firstboot, fuse, iptables, moblin-live, ntp, ntpdate, ohm, openssh-server, sensorfw, sreadahead, sysklogd, timed, trousers, udev, xinetd), which use things like /etc/init.d/functions that are part of fastinit. /etc/init.d/functions then uses stuff from sysvinit-tools. I do not believe for a second that all of these could be fixed to upstart-style before feature freeze or even that it would be a sane thing to do. I say let them use sysvinit-style init functions and fastinit function libraries, upstart can handle them too. > this upstart migration is starting to sound like a bigger and bigger > deal that is visible to applications etc... > ... not a good idea since upstart is only for one release. It's visibility to applications is much lower if there isn't a need to get rid of everything that is fastinit/sysvinit. -- Tapio Rantala _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
