:: Re: [DNG] init systems
Top Page
Delete this message
Reply to this message
Author: The Original Linux Fan
Date:  
To: dng
Subject: Re: [DNG] init systems
Yes it does!  Many thanks!  Init is one place that I did
not ever delve into very much.  I'm told that systemd
actually speeds things up, but it always appears to me
to be due to the extreme slowing down of the user
interface.  I'm unwilling to give that away.

I have an old 1GHz 32-bit AMD 686 machine, and it is
actually more responsive to the user than my new(ish)
56 intel cpu HP machine.  That is my issue.  But I know
that the new machine doesn't have a proper video
card (proprietary card is missing driver, afaik).  But
when I do, `make -j 40` on any significant software
package, it is like jumping into a drag-racer, instead
of my old pinto.

So, if I can solve the user response, mostly keyboard,
on all my "new" machines, then I'll feel like my mach-
ines are actually responsive.  (I'm aging too, which is a
problem as well.  I'm a little over 60 now, but I type
more now, than I used to.  Fun, fun, fun....)

I make lots of typos on new stuff due to the lag.  The
timing between the machine and I just isn't there on
new machines.  It is frustrating, and is teaching me
bad typing habits.

Anyway, removing systemd seems to help significantly,
but some problems still exist.  Mostly bloatware?

The simple solution would be to just always run my
old 686 as xterm, but when I tried that with debian,
it blew up stuff on the 686, so I air-gapped it, as it
has some (Torah) software that I've been working on
for nearly 15 years.  I'm trying to migrate it, but it is
a huge issue to migrate it, even though it is almost
all just bash scripts and Lex/C code.  Python was
involved, and it depends on the oldest version, which
isn't supported now.

Sorry about the long diatribe, but that old 686 is still
the center of my world, even though I only power it
on about once or twice a week, to copy or test code.
The new gcc won't even compile stuff correctly, yet,
on the ported software.

I'm hoping I can stuff it on a VM on my 56 core, but
that's more stuff to learn....

Shalom,
(orig) Linuxfan

On 3/8/23 00:29, Steve Litt wrote:
> The Original Linux Fan via Dng said on Tue, 7 Mar 2023 12:40:20 -0800
>
>> SteveT,
>> Could you post some example scripts on such a
>> configuration?  Just a skeleton.  I don't know a thing
>> about runit or s6 yet.
> Here it is:
>
> UNBOUND:
> #!/bin/sh
> exec unbound -dp
>
> CUPSD:
> #!/bin/sh
> exec 2>&1
> exec cupsd -f
>
> CROND:
> #!/bin/sh
> [ -r conf ] && . ./conf
> exec cronie-crond -n $OPTS 2>&1
>
> AGETTY-TTY1:
> #!/bin/sh
>
> tty=${PWD##*-}
>
> [ -r conf ] && . ./conf
>
> if [ -x /sbin/getty -o -x /bin/getty ]; then
>     # busybox
>     GETTY=getty
> elif [ -x /sbin/agetty -o -x /bin/agetty ]; then
>     # util-linux
>     GETTY=agetty
> fi

>
> exec chpst -P ${GETTY} ${GETTY_ARGS} \
>     "${tty}" "${BAUD_RATE}" "${TERM_NAME}"

>
>
> WPA_SUPPLICANT:
> #!/bin/sh
> if [ -r ./conf ]; then
>     . ./conf
>     : ${OPTS:=-M -c
> ${CONF_FILE:-/etc/wpa_supplicant/wpa_supplicant.conf}
> ${WPA_INTERFACE:+-i ${WPA_INTERFACE}} ${DRIVER:+-D ${DRIVER}} -s} else
> . ./auto OPTS="${AUTO} -s"
> fi

>
> exec 2>&1
> exec wpa_supplicant ${OPTS}
>
>
> DOVECOT:
> #!/bin/sh
> exec 2>&1
> install -d -m 0755 -o root -g root /var/run/dovecot
> exec dovecot -F
>
> DHCPCD:
> #!/bin/sh
> [ -r conf ] && . ./conf
> exec dhcpcd -B ${OPTS:=-M} 1>&2
>
> SSHD:
> #!/bin/sh
> ssh-keygen -A >/dev/null 2>&1 # Will generate host keys if they don't
>                                # already exist
> [ -r conf ] && . ./conf
> exec /usr/bin/sshd -D $OPTS

>
> DBUS:
> #!/bin/sh
> [ ! -d /run/dbus ] && install -m755 -g 22 -o 22 -d /run/dbus
> exec dbus-daemon --system --nofork --nopidfile
>
> HTH,
>
> SteveT
>
> Steve Litt
> Autumn 2022 featured book: Thriving in Tough Times
> http://www.troubleshooters.com/bookstore/thrive.htm
> _______________________________________________
> Dng mailing list
> Dng@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng