On Wed, 18 May 2016 19:23:27 +0200, Irrwahn wrote in message
<48e882e7-9b75-2bb5-769f-a93c4126e4a3@???>:

> On Wed, 18 May 2016 18:24:23 +0200, Arnt Karlsen wrote:
>
> [about booting a system after Debian\Sid to Devuan\Ceres transition]
>
> > ..now having thrown out all the systemd crud I see mentioned here
> > at DNG, I'm still left with runlevel 1, the damned thin will only
> > accept root's passwd on the console, I can start and run ssh and X
> > etc all day, and it works all nice except I have my password
> > rejected once I try a login.
> >
> >
> > ..exactly how is a Devuan boot supposed to work these days?
> > And what systemd crud could could my logins?
> > And what logs do I check these days?
> >
> > ..last time I had this laptop this bogged down, I simply wiped
> > /etc/rc2.d/ clean and made it lean, does anyone have a lean
> > Devuan machine so I can see /etc/rcS.d/ and /etc/rc2.d/ listings?
>
> Hi Arnt,
>
> below you find the output of ls /etc/rc[S2].d, created
> using one of the unofficial minimal Devuan Jessie beta
> images posted on DNG a few days ago.

..thank you. :o)

> However, with all due respect, just wiping the thing
> and doing a genuine Devuan install might save you a lot
> of headache. Just thinking.

..the crazy thing is you are actually wrong here, ;o)
this install will survive 2 disks, 4 laptops and a
desktop box. ;oD

..it started as Squeeze/Sid on a Fujitsu Celsius H240
on a 160GB disk, first the disk died and the OS was
dd'ed onto a 750GB, then the Celsius needed a certain
thawing procedure to boot, as the thaw gradient window
narrowed, the 750GB moved into a desktop and then an
HP nw8440 with such nice tight lid hinges one broke,
then a few weeks in a Lifebook S6420 until a wee gale
broke the screen, another coupla weeks in a big ass
Amilo Xi 1554 and now it's in a Dell Precision M4400,
honed to my taste, all done myyyyyyyy waaaaaaaay. ;o)

> Regards
> Urban
>
>
> /etc/rc2.d:
> README
> S01motd
> S01rsyslog
> S01uuidd
> S02acpid
> S02atd
> S02cron
> S02gpm
> S02rsync
> S02ssh
> S03bootlogs
> S04rc.local
> S04rmnologin
>
> /etc/rcS.d:
> README
> S01live-config
> S02hostname.sh
> S02mountkernfs.sh
> S03udev
> S04mountdevsubfs.sh
> S05keymap.sh
> S06keyboard-setup
> S08checkroot.sh
> S09checkfs.sh
> S10checkroot-bootclean.sh
> S10kmod
> S11mountall.sh
> S12mountall-bootclean.sh
> S13procps
> S13udev-finish
> S13urandom
> S14networking
> S15rpcbind
> S16nfs-common
> S17mountnfs.sh
> S18mountnfs-bootclean.sh
> S19kbd
> S20console-setup
> S21bootmisc.sh
> S21screen-cleanup
> S22live-tools
>

..has anyone tried to do e.g. an /etc/rcR.d, or is my big
ass /etc/rcS.d pile best spread out across /etc/rc[3-5].d ?
root@debian:/var/cache/apt/archives# ll /etc/rcS.d/ |wc -l
58
root@debian:/var/cache/apt/archives# ll /etc/rc2.d/ |wc -l
91
root@debian:/var/cache/apt/archives# ll /etc/rc3.d/ |wc -l
311
root@debian:/var/cache/apt/archives#

..the one big thing I like about systemd, is I've been able
to escape from bat shit high load near crashes with e.g.
"systemctl isolate kdm". Wonderful idea we should steal
into our next init and process management packages.

--
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.