No, I have made the distupgrade release by release
and checked, whether anything was working.

And yes, from Etch to Lenny, Squeeze and Wheeze it was working.

And then the nightmare came over me!

Currently I install a Wheeze Workstation + Server around 3 GByte
of installation will back it up and try the migration to Jessie again.

If anything goes wrong, my bootloader is configured to boot a
rescue system which reinstall the Wheeze backup...


2015-07-22 22:03 GMT+02:00 T.J. Duchene <t.j.duchene@???>:

>
> From: Dng [mailto:dng-bounces@lists.dyne.org] On Behalf Of Michelle
> Konzack
> Sent: Tuesday, July 21, 2015 11:55 PM
> To: dng@???
> Subject: Re: [DNG] Interesting comment from a kernel developer
>
> Hello *,
>
> 2015-07-22 3:07 GMT+02:00 Go Linux <golinux@???>:
> What is this about 'baroque init scripts' and wanting to have only ONE
> option? Rather prescient in light of where we are now . . .
>
>
> This mean, Debian has droped anything and now users AND developers have
> to bother with crappy "systemd".
> Some days ago I have updated an Etch system release by release to Jessie
> and now, nothing is working anymore! Have killed Jessie and installed in
> the Last two days a new Wheeze MiniITX machine and now anything is working
> as expected.
> I will do anything to get rid of "systemd"!!! It is a nightmare!
>
> --
> Michelle Konzack
> GNU/Linux Developer
> 0049-176-86004575
>
> [T.J. Duchene]
> Sorry to hear about your troubles, Michelle. =(
>
> Yes, Debian has adopted systemd. As a quick fix, you can stick with
> Wheezy; or you can install Jessie and then install systemd-shim and
> sysvinit. After you install systemd-shim and sysvinit, Jessie should work
> more or less as expected. If I might say so, your problems may have
> stemmed from trying to jump from Etch to Jessie, skipping Wheezy. Skipping
> versions is something that you should never do with in-place upgrades.
> While you technically CAN do it, you probably shouldn't. It causes all
> kinds of errors because Debian (or anyone else) seldom tests the
> procedure. The configuration files held from the older install can cause
> startup failures that do not necessarily have anything to do with systemd.
>
>
> Best luck and wishes!
> T.J.
>
>


--
Michelle Konzack
GNU/Linux Developer
0049-176-86004575