Antw: Re: Antw: [EXT] [systemd???devel] starting networking from within single user mode?

["Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>]

>>> Mantas Mikulenas <grawity@xxxxxxxxx> schrieb am 11.11.2022 um 15:49 in
Nachricht
<CAPWNY8Xz-N6S_JwkCsr+wK7Tu92LQw+U0DCp8NbKinrTF7zXWQ@xxxxxxxxxxxxxx>:
> On Fri, Nov 11, 2022 at 4:19 PM Brian Reichert <reichert@xxxxxxxxxxx> wrote:
> 
>> On Fri, Nov 11, 2022 at 08:02:00AM +0100, Ulrich Windl wrote:
>> > >>> Brian Reichert <reichert@xxxxxxxxxxx> schrieb am 10.11.2022 um
>> 23:04 in
>> > Nachricht <20221110220426.GA17371@xxxxxxxxxxx>:
>> > > I've managed to hose a SLES12 SP5 host; it starts to boot, then hangs.
>> >
>> > And what did you do to mess it up? And what do the boot messages say?
>>
>> A good question, and not specific to systemd, so I don't want to
>> pollute the list archives too much on this matter.
>>
>> 'All' I did was remove many RPMs that I arbitrarily deemed
>> unnecessary.
>>
>> I came up with a heavily trimmed-down list of SLES RPM for my SLES12
>> Sp5 environment.
>>
>> I successfully installed a server using just that trimmed-down list;
>> yay me!
>>
>> I then explored 'upgrading' a running (slight older) SP5 box, using
>> this trimmed-down list.  A purposeful side effect was to uninstall
>> RPMs not in that trimmed-down list.
>>
>> This latter box begins to boot, and gets at least as far as loading
>> the initrd image, before hanging.
>>
> 
> Boot with "systemd.debug-shell" and use tty9 to investigate from the inside.

Wow! never heard of that option. Is that a kind of target, or what is the mechanism?
Which of the 196 (man -k systemd | wc -l) systemd-related manual pages would describe it? ;-)

Regards,
Ulrich