Dear Herbert,
I'm not happy about systemd too,
but the choice is now playing like for ~8 years on Debian (only a bit
diverts to redhat) and vserver or use LXD/LXC
there is no doku (the webpage has no change for years),
no repro nothing anymore,
so, using a complete divert Distro playing on the heart by changes on
startup and kernel and by the way the until- too....
not knowing what happens on update process on that changes.
a good choice for a production system??? maybe for playing on Sunday.
For a big big while ago I ask for centos7 ... the answer there is time 6
is working...
yes, its working but not long anymore and 8 is upcoming
I think to inform that it will never or not or in time supported, is
gone a big while ago.
so where is the question about reduced isolation and slighly higher
overhead,
I can’t see the choice please show me how to get such a stabil and
maintaind (kernel und until repro) system like under centos6 on/with
vserver.
BRG Roman
Am 2019-01-17 05:54, schrieb Herbert Poetzl:
> On Wed, Jan 16, 2019 at 06:56:41PM +0100,
> roman.pretory@austrianonlines.com wrote:
>> Bad or no news,
>
> Well, If I'm not completely wrong, Jacques Gelinas
> created a script which replaces systemctl and allows
> to start systemd services on Guest startup ...
>
> I have to admit, I never tried it, but it seemed
> to work for him back then.
>
>> if there is no support for systemd means
>
> Systemd doesn't like to run inside a proper isolated
> container especially not with reduced capabilities.
>
> That said, it seems to work in LXC nowadays, so I'm
> kind of confident that with just enough permissions
> it will probably work with only small or no modifications.
>
> To be honest, there hasn't been much interest in getting
> systemd running inside a Linux-VServer guest in the past
> few years ...
>
>> no redhat, fedora, centos, debian, suse.. and many more
>
> While there are many other distributions which work
> just fine without systemd, most distribution services
> can be started from a simple script without the need
> for systemd bossing around mainly because all of the
> hardware related stuff has been taken care of already
> and sshd and friends usually do not need a nanny to
> watch over them.
>
>> and means this project is dieing or already dead.
>
> Well, if you like systemd and don't mind the reduced
> isolation and slighly higher overhead, you are probably
> fine with LXC.
>
> Note that if there is real interest in getting systemd
> working under Linux-VServer (for whatever reason) then
> I'm willing to investigate this, but it's no fun to
> debug stuff with systemd so it has to be worthwhile.
>
> Best,
> Herbert
>
>> very upset.
>
>
>> Am 2019-01-16 15:13, schrieb Günther Fuchs:
>>> AFAIK util-vserver doesnt work with systemd, so CentOS 7 probably
>>> does
>>> not work, neither as host nor as guest
Received on Thu Jan 17 07:34:16 2019