I'm running a pretty conventional setup with a server providing
nat/dhcp/dns/nfs/yp to about 15 workstations. These nfs mount /home
via /etc/rc.local from where they find another script that nfs
mounts /usr and does some trivial local house keeping.
My reluctance to use systemd is mainly that the documentation seems to
be fragmented and lacking a decent overview, and I'm never keen on
learning a system by hacking it about until it Seems To Work. On the
other hand I know that my existing configuration files for sysv will
Just Work, or require minimal tweezing at most.
However, it doesn't look as if systemd is going away any time soon, and
I suspect that hybrid solutions may be overly complex for my needs.
Something to mull over at the pub tonight ...
On Fri, 2016-05-06 at 14:07 +0100, Michael Howe wrote: > Hi Mark,
> On Fri, May 06, 2016 at 01:33:11PM +0100, Mark Poolman wrote:
> > Dear All,
> > I am about to upgrade a small network from debian Wheezy to Jessie,
> > something I've been putting off for much too long, but now circumstances
> > have forced the issue. Part of my reluctance is that Jessie is systemd
> > based, and apart from the controversy surrounding this, don't really
> > want to put time and effort into learning something I don't really need,
> > sysv is just fine in my environment.
> > However, I discover that devuan now has Jessie released in beta, so the
> > question is whether or not to use that instead. The network in question
> > is used by a small research group, and long term stability is paramount.
> > Should I bite the bullet and learn systemd, or stick with the comfort
> > blanket of sysv and trust that devuan has enough of a critical mass o be
> > a viable long term option?
> I'm not sure if you're talking about servers or desktops or both here.
> Despite much of the noise to the contrary, it is possible to run jessie
> without systemd - we are doing it on our systems following steps like
> Yes, if you're doing a clean install you do end up with systemd
> installed briefly, but we haven't seen any problems on >30 systems.
> Note that systemd-sysv is the init replacement package - you may find
> that other systemd packages are pulled in, but these are harmless and
> can safely be ignored.
> Certainly on servers we've found that everything still Just Works; I
> don't know true that is for desktops (I've just accepted systemd on the
> handful of desktops/laptops I'm responsible for and none of the problems
> I've had have been systemd's fault), or how that will map into stretch
> (current testing), but I hope by 2017 systemd will be more stable and so
> migration to it will be easier, should we choose to.
> I haven't used devuan - I will be interested to see how it works out,
> but I wouldn't use it for a production system, and certainly not one I
> wanted to know would be supported for a while and don't have much time
> to look after.
> Best wishes,
This message was posted to the following mailing lists: