:: Re: [DNG] New build + extras
Top Page
Delete this message
Reply to this message
Author: Steve Litt
To: Devuan ML
Subject: Re: [DNG] New build + extras
o1bigtenor said on Mon, 30 May 2022 21:16:02 -0500

>On Mon, May 30, 2022 at 8:55 PM Steve Litt <slitt@???>
>> o1bigtenor via Dng said on Mon, 30 May 2022 17:07:44 -0500
>> >On Mon, May 30, 2022 at 5:03 PM o1bigtenor <o1bigtenor@???>
>> >Not trying to start any kind of 'holy war' but was thinking of using
>> >SysV init unless there are some great arguments where another option
>> >is better - - - that is something that needs its own advice.
>> Before I continue, I was quite happy with sysvinit 1998 to whenever
>> upstart took over. Sysvinit does the job.
>> In my opinion the difference between sysvinit and OpenRC is not
>> enough to walk away from the familiar sysvinit.
>> Now, because runit exists, I would never again start up my daemons
>> using sysvinit. Instead, I would do one of the two following:
>> 1: Use sysvinit for PID1, and:
>>         A: Start runit in /etc/inittab as a respawn
>>         B: For each daemon:
>>                 i: Disable the daemon in sysvinit
>>                 ii: Enable it in runit

>> 2: Use runit as a complete init system
>> If I were using Devuan (my Daily Driver Desktop (DDD) is Void), I
>> would choose alternative 1 because it's simple and sticks with what
>> I know. If I were using a native runit distro like Void I'd use
>> alternative 2.
>> I think #1 is a great way to slowly wade from the shallow end of to
>> the deep end.
>So on a complicated system - - - - this sounds like things could get
>sorta interesting. I have some 14+ GB of software in my /usr partition
>so I don't think I'm into straightforward stuff (LOL). Dunno what this
>would be like in real life.
>I need to make a decision quickly because the new system will
>hopefully be here by the end of the week and then its assemble
>and start the loading!!

Then use sysvinit, and then, at your leasure, slowly move more and more
to runit.

>How does runit improve things from SysV?

Thousands of ways. No more PID files to go corrupt or unerased or
prematurely erased. No more 300 line init scripts: The average runit
run script has a line count in the single digits. Runit automatically
respawns everything it starts. If for some reason you want a specific
daemon not to respawn, leave that daemon in sysvinit.

Runit's easier to understand.

But please understand you can use sysvinit as PID1 and do some or all
daemon spawning and respawning from runit.

>Have you tried running devuan on 64 bit SOCs yet?

I've only run Devuan on qemu VMs.

>Am thinking of using some such for servers - - - dunno where to
>get info - - - - looking at some interesting logging for a fairly
>large amount of inputs and then afterward looking at the data for
>determining a number of different things. The software - - - looks
>like I'm going to have to roll my own. Just isn't much that I think is
>good stuff at prices I'm willing to pay (ag related stuff).

Runit can log to the individual daemon's logs, or to syslog type stuff
if you run a logging program.

>Thanks for the tip!

You're very welcome.


Steve Litt
March 2022 featured book: Making Mental Models: Advanced Edition