Re: Upstart on kFreeBSD? [was: The future of the boot system in Debian]
On Sat, 2009-11-07 at 14:00:23 +0000, Alan Jenkins wrote:
> On 9/5/09, Petter Reinholdtsen <firstname.lastname@example.org> wrote:
> > change the init.d script
> > handling to treat upstart jobs as init.d scripts, to provide an
> > alternative for architectures lacking upstart support
> I read this as a euphemism for non-linux architectures such as
> kFreeBSD. But I don't understand how this would be done.
> An alternative would be to make upstart more portable. At the moment
> the only obvious technical problem is the use of ptrace(), but I don't
> see this as insurmountable. I think the biggest problem would be to
> persuade upstream.
There's several others (taken from this thread ):
* epoll, eventfd, signalfd, timerfd
* netlink proc connector
* netlink udev interface
Check Scott's  and Petr's  mails on that thread for more details.
> I'm prepared to work on the code... if it's really feasible, it
> shouldn't take too long. What I can't do is make a solid case to
> upstream by myself. It would really need agreement from the debian
> upstart maintainers that this is their preferred way forward, along
> with a commitment that Debian will help resolve any portability issues
> which arise in future versions of upstart.
The biggest issue I see is that someone will have to step up and
become “upstream” for the non-Linux ports, given Scott's position.
I'm not sure how he'd expect those to get released, if as outright
forks or something else, that'd need to be discussed with him. It will
also need copyright assignments  for the code that might need to be
> Does this make any sense? Is anyone already working on running
> upstart scripts on non-linux architectures?
It was brought up in the debian-bsd list, but I don't know of any one
working on it.