https://fedoraproject.org/wiki/Features/Upstart0.6.0
was approved at today's FESCo meeting. We hope to land this in the next week or so.
What this means for you (for very specific values of you):
If you own any of the following packages, you have upstart job files that will need modified for any needed format changes, and the new location.
* vpnc rjones * ConsoleKit mccann * clamav ensc * dhcp-forwarder ensc * hdapsd ttorcz * ip-sentinel ensc * milter-greylist ensc * olpc-utils pbrobinson * tor ensc
We're willing to do the legwork for you, or you can do the update yourself once we land 0.6.x; give us a reply with which you'd prefer. See the feature page for more details on the changes required.
What this means for you (for very general values of you):
Once it lands, it's going to be a bit of a bumpy first yum upgrade. You will likely have to reboot with 'reboot -f', as the job formats have changed slightly, and the communication with init(8) has changed. We can investigate adding some compat code to ease this, if people would really prefer.
Once you reboot, things should work pretty much the same.
Obvious FAQ:
Q: Should we port our SysV scripts to native upstart scripts?
A: No, not at this time.
Questions? Comments?
Bill
Bill Nottingham (notting@redhat.com) said:
Obvious FAQ:
Q: Should we port our SysV scripts to native upstart scripts?
A: No, not at this time.
Q: I'd like to play with it before it lands.
A: There's a repo at http://notting.fedorapeople.org/upstart0.6/. You can also check the new upstart package out of devel/ CVS, and the initscripts changes out of the upstart-0.6.0-branch in initscripts git.
Bill
On Fri, Dec 04, 2009 at 04:10:34PM -0500, Bill Nottingham wrote:
The features highlight list has: Communication with the init daemon over D-Bus.
Questions? Comments?
Does this mean that running dbus will be required to reboot/shutdown the system?
Miroslav Lichvar (mlichvar@redhat.com) said:
On Fri, Dec 04, 2009 at 04:10:34PM -0500, Bill Nottingham wrote:
The features highlight list has: Communication with the init daemon over D-Bus.
Questions? Comments?
Does this mean that running dbus will be required to reboot/shutdown the system?
No. The init daemon speaks the dbus protocol, and can be communicated with over the system daemon. But it can also be talked to directly.
Bill
On Fri, Dec 4, 2009 at 3:45 PM, Bill Nottingham notting@redhat.com wrote:
Miroslav Lichvar (mlichvar@redhat.com) said:
On Fri, Dec 04, 2009 at 04:10:34PM -0500, Bill Nottingham wrote:
The features highlight list has: Communication with the init daemon over D-Bus.
Questions? Comments?
Does this mean that running dbus will be required to reboot/shutdown the system?
No. The init daemon speaks the dbus protocol, and can be communicated with over the system daemon. But it can also be talked to directly.
Bill
-- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Why aren't the sysVinit scripts being ported over to native upstart scripts? I thought the reason why upstart was adopted was to be able to utilize the benefits of native upstart scripts (event based daemon handling, etc.)?
Why aren't the sysVinit scripts being ported over to native upstart scripts? I thought the reason why upstart was adopted was to be able to utilize the benefits of native upstart scripts (event based daemon handling, etc.)?
No one is holding you back from starting to convert them now, but the format is most probably going to change again till the 1.0 release. Happy porting to you. ;)
kind regards, Rudolf Kastl
-- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Sir Gallantmon (ngompa13@gmail.com) said:
Why aren't the sysVinit scripts being ported over to native upstart scripts? I thought the reason why upstart was adopted was to be able to utilize the benefits of native upstart scripts (event based daemon handling, etc.)?
- Semantics may change for 1.0 (although they're trying to keep the format the same between 0.6 and 1.0) - A system that's half-upstart and half-SysV has a variety of compatiblity problems, if you ever need to have dependencies between them.
Bill
On Fri, 2009-12-04 at 16:45 -0500, Bill Nottingham wrote:
Miroslav Lichvar (mlichvar@redhat.com) said:
On Fri, Dec 04, 2009 at 04:10:34PM -0500, Bill Nottingham wrote:
The features highlight list has: Communication with the init daemon over D-Bus.
Questions? Comments?
Does this mean that running dbus will be required to reboot/shutdown the system?
No. The init daemon speaks the dbus protocol, and can be communicated with over the system daemon. But it can also be talked to directly.
Looking at upstart-0.6.3-3.fc13.src.rpm, the specfile includes /sbin/shutdown etc. ... and looking at the tarball those seem to come from util/*.c. Which AFAICS require DBus to work.
Also given that init now listens and is controlled by DBus, has anyone done any analysis of how resistant DBus services are to DOS attacks?
James Antill (james@fedoraproject.org) said:
Does this mean that running dbus will be required to reboot/shutdown the system?
No. The init daemon speaks the dbus protocol, and can be communicated with over the system daemon. But it can also be talked to directly.
Looking at upstart-0.6.3-3.fc13.src.rpm, the specfile includes /sbin/shutdown etc. ... and looking at the tarball those seem to come from util/*.c. Which AFAICS require DBus to work.
... which does not *require* the system dbus daemon.
Bill
Bill Nottingham notting@redhat.com writes:
If you own any of the following packages, you have upstart job files that will need modified for any needed format changes, and the new location.
- clamav ensc
- dhcp-forwarder ensc
- ip-sentinel ensc
- milter-greylist ensc
- tor ensc
We're willing to do the legwork for you, or you can do the update yourself once we land 0.6.x; give us a reply with which you'd prefer.
I updated (but not tested) them in rawhide.
Enrico
On Fri, Dec 04, 2009 at 04:10:34PM -0500, Bill Nottingham wrote:
[...]
If you own any of the following packages, you have upstart job files that will need modified for any needed format changes, and the new location.
- vpnc rjones
[...]
We're willing to do the legwork for you, or you can do the update yourself once we land 0.6.x; give us a reply with which you'd prefer. See the feature page for more details on the changes required.
I'm quite happy for you to make the changes.
Rich.
What this means for you (for very specific values of you):
If you own any of the following packages, you have upstart job files that will need modified for any needed format changes, and the new location.
- olpc-utils pbrobinson
We're willing to do the legwork for you, or you can do the update yourself once we land 0.6.x; give us a reply with which you'd prefer. See the feature page for more details on the changes required.
I'm quite happy for you to make the changes.
Cheers, Peter
On Fri, Dec 04, 2009 at 04:10:34PM -0500, Bill Nottingham wrote:
https://fedoraproject.org/wiki/Features/Upstart0.6.0
was approved at today's FESCo meeting. We hope to land this in the next week or so.
If you own any of the following packages, you have upstart job files that will need modified for any needed format changes, and the new location.
- hdapsd ttorcz
hdapsd is ready in version 20090401-5.
-
Bill Nottingham -
Enrico Scholz -
James Antill -
Miroslav Lichvar -
Neal Gompa -
Peter Robinson -
Richard W.M. Jones -
Rudolf Kastl -
Tomasz Torcz