How to install jessie without systemd

Discussion of technology related topics including news, events, and announcements.

Re: How to install jessie without systemd

Postby golinux » December 2nd, 2014, 4:39 pm

cynwulf wrote:By their own admission, the fork is not yet a fork - it's yet another debian respin at the moment.

Semantics. As long as it works . . . ;)
May the FORK be with you!
User avatar
golinux
 
Posts: 1118
Joined: July 23rd, 2011, 4:45 pm
Location: not a 'buntard!

Re: How to install jessie without systemd

Postby cynwulf » December 2nd, 2014, 4:46 pm

Two different things. A fork has to go it's own way - so all infrastructure has to be forked. That is one of their stated goals, but at the moment they are a "derivative" (if that).
cynwulf
 
Posts: 2548
Joined: April 26th, 2011, 2:46 pm

Re: How to install jessie without systemd

Postby golinux » December 2nd, 2014, 5:11 pm

Yeah, of course you're right. Give it time. If systemd makes a derivative unworkable, they'll either move to a proper fork or go the way of the dodo.
May the FORK be with you!
User avatar
golinux
 
Posts: 1118
Joined: July 23rd, 2011, 4:45 pm
Location: not a 'buntard!

Re: How to install jessie without systemd

Postby jheaton5 » December 2nd, 2014, 5:12 pm

What is the difference in a fork and a respin?
jheaton5
 
Posts: 1776
Joined: February 9th, 2011, 10:25 am
Location: Newnan, GA USA

Re: How to install jessie without systemd

Postby cynwulf » December 2nd, 2014, 11:05 pm

A fork is where the the codebase goes off in its own direction independently. If the original project dies, the fork continues. Respins/derivatives on the other hand depend on the parent project.
cynwulf
 
Posts: 2548
Joined: April 26th, 2011, 2:46 pm

Re: How to install jessie without systemd

Postby jheaton5 » December 4th, 2014, 9:34 pm

Here is a new idea from Christian Seiler on Bug 762194 Automatic switch to systemd on wheezy->jessie upgrades
The main advice for user's upgrading that want to keep sysvinit is
currently to install the sysvinit-core package before actually
upgrading the rest of the system. Therefore, this behavior could be
leveraged by introducing a trivial empty package 'sysvinit-core' to
wheezy and make 'sysvinit' in wheezy depend on it.

I've tried this with the following patch to wheezy's (!) sysvinit
package:

======================================================================
--- old/debian/control 2013-07-14 19:19:01.000000000+0200
+++ new/debian/control 2014-12-04 15:14:16.569409781+0100
@@ -26,7 +26,9 @@
# For ischroot
debianutils (>= 4),
# Required for TERM=xterm switch (see #605777)
- kbdcontrol (>= 8.2+ds2-6) [kfreebsd-any]
+ kbdcontrol (>= 8.2+ds2-6) [kfreebsd-any],
+# For jessie upgrades
+ sysvinit-core
Description: System-V-like init utilities
This package contains programs required for booting
a Debian system and doing basic process management.
@@ -50,6 +52,15 @@
Specifically, this package includes:
killall5, last, lastb, mesg, pidof, service, sulogin

+Package: sysvinit-core
+Architecture: any
+Description: System-V-like init utilities
+ This package is a transitional package to facilitate transitions to
+ Debian 8 (jessie).
+ .
+ The consequence of this package is that updates to the next Debian
+ version will not change the init system.
+
Package: sysv-rc
Architecture: all
Recommends: lsb-base (>= 3.2-14)
======================================================================

This has the following consequences:

- wheezy systems running sysvinit will not switch init systems on
upgrade (tested with apt-get and aptitude on the command line),
i.e. keep sysvinit as init system

- wheezy systems running systemd-sysv (forced removal of sysvinit
essential package) will also keep their current init system, in
this case systemd

- jessie systems are unaffected, because this change is in wheezy

Therefore, if you really want to prevent init system changes from
wheezy to jessie, given the current state of affairs, this appears to
be the sanest solution, at least from a technical standpoint.
Obviously, this is someting that should probably be discussed with
the release team first, if you really intend to go that route. And
obviously, you should keep in mind that this will then only work for
people who keep their wheezy systems up-to-date.
jheaton5
 
Posts: 1776
Joined: February 9th, 2011, 10:25 am
Location: Newnan, GA USA

Previous

Return to Technical Talk

Who is online

Users browsing this forum: No registered users and 0 guests

x