Andrei Borzenkov composed on 2016-06-22 06:39 (UTC+0300):
> TBH, switch between run-time levels never really worked in the past,
> before systemd, so at least there is no regression :)
This is news to me. I was doing this for years. What brokenness was I
not encountering?
> Well, getty's are sp
On 2016-06-22 13:32, Andrei Borzenkov wrote:
Well, depends =) It was easy to do it cleanly, but rarely anyone cared. It's
How is different to what we have now? :)
I guess =)
Well, getty's are spawned dynamically on demand and there is no direct
dependency between various targets and runn
On Wed, Jun 22, 2016 at 10:38 AM, Michal Soltys wrote:
> On 2016-06-22 05:39, Andrei Borzenkov wrote:
>>
>> 21.06.2016 23:23, Michal Soltys пишет:
>>
>> TBH, switch between run-time levels never really worked in the past,
>> before systemd, so at least there is no regression :)
>>
>>
>
> Well, dep
On 2016-06-22 05:39, Andrei Borzenkov wrote:
21.06.2016 23:23, Michal Soltys пишет:
TBH, switch between run-time levels never really worked in the past,
before systemd, so at least there is no regression :)
Well, depends =) It was easy to do it cleanly, but rarely anyone cared.
It's kind of
21.06.2016 23:23, Michal Soltys пишет:
> Hi,
>
> This was tested with recent stock arch distro. I'm not sure if it's
> intended to be able to isolare rescue.target from multi-user, but I
> noticed two issues:
>
TBH, switch between run-time levels never really worked in the past,
before systemd,
Hi,
This was tested with recent stock arch distro. I'm not sure if it's
intended to be able to isolare rescue.target from multi-user, but I
noticed two issues:
1) getty service and IgnoreOnIsolate option
This beautifully conflicts for console access with sulogin on whichever
console systemc
