[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#760897: release-notes: systemd switch: customised init scripts

Control: tags -1 pending

On Tue, 09 Sep 2014 10:35:41 +1000 Stuart Prescott <stuart@debian.org>
> Package: release-notes
> Severity: normal
> Exactly how the init system is to be handled for wheezy->jessie upgrades is
> still being argued about (and probably still will be in a few months...). What
> is clear, however, is that some sort of "migration to systemd" documentation
> would be appropriate to include in the release notes. Interested admins will
> want to know how to go about changing irrespective of whether the migration
> is done by default or not.
> There is a starting point on the wiki (although that is probably overly verbose
> to include in the release notes as it is)
>     https://wiki.debian.org/systemd
> One point for migration that came up on debian-devel [1] is that local
> modifications to init scripts may well need to be ported over to the systemd
> units. This can't be done automatically and it's not even going to be easy to
> work out if there is a systemd unit for any given local modification. What we
> can do, however, is help the admin prepare a list of init scripts that have
> been modified so they can add them to their own TODO list for checking.
> One of the following is a good starting point for this:
> [...]
> [1]  http://lists.debian.org/<540E056A.3040909@free.fr>

Hi Stuart,

Thanks for reporting this issue.

I have applied the attached patch to the release note.  A review is very
welcome. :)


Attachment: 0001-en-issues-Document-the-need-for-migrating-sysvinit-s.patch
Description: application/mbox

Reply to: