Quoting Brian (2019-09-17 00:11:33)
> On Mon 16 Sep 2019 at 15:16:34 -0400, The Wanderer wrote:
> 
> > On 2019-09-16 at 15:07, Brian wrote:
> > 
> > > On Sun 15 Sep 2019 at 21:52:50 -0400, Dan Ritter wrote:
> > > 
> > >> Roger Lynn wrote:
> > >> 
> > >>> Hi,
> > >>> 
> > >>> I have three Stretch AMD64 systems with sysvinit - a desktop and
> > >>> laptop running KDE and a headless server. Is there any
> > >>> information available anywhere to tell me what will happen when I
> > >>> attempt to upgrade them to Buster? The release notes don't
> > >>> mention it and other sources I can find just talk about switching
> > >>> from systemd to sysvinit, which doesn't look easy with a desktop
> > >>> environment.
> > >> 
> > >> If you want to keep sysvinit, here's the order of events:
> > >> 
> > >> change sources from stretch to buster
> > > 
> > > Fine.
> > > 
> > >> apt update
> > > 
> > > Splendid.
> > > 
> > >> apt dist-upgrade
> > > 
> > > Great.
> > > 
> > >> apt install sysvinit-core
> > > 
> > > What happens if this is not done?
> > 
> > Next time you reboot, you'll have systemd as init.
> > 
> > The dist-upgrade will have resulted in installing the systemd-sysv
> > package, which (despite its name) has nothing to do with sysvinit; it is
> > the package which sets systemd as the primary / active / default init
> > system.
> > 
> > Installing sysvinit-core will uninstall that package.
> 
> What causes systemd-sysv to be installed?

One way to answer that is "your `apt dist-upgrade` call": Dist-upgrade 
sort-of means "give me newer stuff, even if it means sliding sideways 
and removing some existing parts".

You can instead do "apt upgrade" which is more conservative - meaning 
that it will hold back stuff without a direct upgrade.  It is *not* 
sensible to _only_ do "apt upgrade", you must deal with the pieces leaft 
behind without a simply upgrade path permitted by conservative 
upgrading.  One way to deal with that is to use aptitude in fullscreen 
mode to inspect and manually decide what to do with each remaining 
package (upgrade, remove, hold, downgrade, replace).  Another way is to 
explicitly do "apt install ..." for each package you want to 
force-upgrade.

A nifty trick when using "apt install ..." is that you can remove+avoid 
packages by negating them: Simply add a hyphen at the end of a package 
and it won't get installed and if already installed it will get removed.

Enjoy,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: signature

Reply via email to