Bug#765803: Status of prompting / notification on upgrade for init system switch?
Hi Josh,
> inittab_unusual_lines="$(
> grep '^[^#]' /etc/inittab |
> while read line ; do
> case "$line" in
> 'id:2:initdefault:') ;;
[...]
I wonder if it would just be easier to look at the md5sum of the file and
compare it to the md5sum of the inittab that was shipped in various releases
-- that's a fairly idiomatic approach to dealing with config files that
changed.
> modified_initscripts="$(
> grep -lE '^/etc/init\.d/' /var/lib/dpkg/info/*.conffiles |
> xargs basename -s '.conffiles' |
> xargs dpkg -V |
> grep '^..5...... c /etc/init\.d/' |
> cut -d' ' -f3
> )"
For testing for modified init scripts, see also #760897 -- note that dpkg -V
requires jessie's dpkg (it is not available in wheezy). For some upgrades
between releases, we have advocated that people upgrade dpkg and apt first and
then upgrade to the new release using the new versions of the tools but this
is far from idiot proof. There's a persistent expectation that just doing a
dist-upgrade should be enough and we see day-in-day-out that people do *not*
read the release notes.
cheers
Stuart
--
Stuart Prescott http://www.nanonanonano.net/ stuart@nanonanonano.net
Debian Developer http://www.debian.org/ stuart@debian.org
GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
Reply to: