On Sun, 6/19/16, Stephanie Daugherty <sdaugherty@???> wrote:

Subject: Re: [DNG] Mini init script written in Perl boots.
To: "Edward Bartolo" <edbarx@???>, "Rainer Weikusat" <rweikusat@???>
Cc: dng@???
Date: Sunday, June 19, 2016, 8:54 AM
>
> When recovering from systermd-related breakage while first trying out Debian jesse, I ended up booting with init=/bin/bash a lot.
>
> You can rather easily bring up a fully functional system that way, at least for long enough to fire up a browser, find the problem, and then recover.
>
> My process for doing so was fairly simple.
- boot into bash
- remount / rw
- mount the rest of the filesystems
- start up udev (this was early in unstable or testing I think when it wasn't merged with systemd yet)
- start up screen
- bring up network interfaces
- start up "important" system services (cron, syslog, and friends)
- fire up a display manager (not strictly required, but easy enough to do, so why not)
>
> I'd suggest that this is a really good way to understand what's actually necessary to bring up the system, without writing a bit of cod, and reproducing the steps by hand provides the level of understanding that a sysadmin needs to have of init IMHO.
>
--------------------------------------------

Most of this thread has been over my head (most posts to this list are). So thank you for this very understandable explanation, Stephanie. I have actually used init=/bin/bash then remount / rw to change root PW a few times. Now I have a better grasp of just what I was doing and what this entire discussion is about.

golinux