I assume you are using openrc as your init.

You can edit /etc/rc.conf to produce a log file, make these changes:

rc_logger="YES"
rc_verbose=yes

Reboot, view var/log/rc.log and see if anything about noip2.

Now, sysvinit and/or openrc only START service.  They dont care nor know about what service do after they start, they dont keep track if they end abnormally.

So check if your noip2 is actually running via htop or ps aux a or whatever you like.

EDITED - And now I see from your initial post you already have var/log/rc.log enabled, sorry about that.

You quote "OpenRC", and then use "service noip2 start ".  "service" is sysvinit.  "rc-service" is openrc equivalent.

rc-service noip2 start

Does your script have a symlink in an openrc runlevel in /etc/runlevels/...?  If not, then run rc-update to add your service to openrc (runlevel default for example). Openrc will then run your script upon init:

rc-update add noip2 default

As ralph.ronnquist mentions, the files are maintained by insserv.

The files are generated using the LSB header information in the init scripts themselves.  Their purpose is to organize the boot order of the init scripts, based on the requirements of the scripts as defined in their LSB header.  These hidden files are then in turn used to generate the numerically ordered sysmlinks in the runlevel directories rc#/d, or for openrc the deptree in /run/openrc.

I suppose they are hidden so not to create confusion in the init.d directory.

Its been a while since I dual booted, so I will leave the details for someone else to provide (hopefully).  last time I dual booted, I decided how much disk I needed for the entire Linux, performed the "shrink" within windows, then installed Linux and created the partitions as part of the install.

But as @Panopticon points out, it is much cleaner to not dual boot, I havent done it since EFI is used.

I just use a swap and root.  In doing so everything else (home) is under root.  "Root" just means the base / directory.  Home is 1 directory below /;  /home.  Nowdays I also create a separate partition to store data I keep across installs, you could just use your windows for this. 

Not sure about dual booting, but with a Linux only install using EFI, you also need an ESP as partition 1.  100MB is fine.  I think windows already uses this partition?

4GB ram;  4GB for swap should be fine.  Opinions vary on this.  Linux itself should easily use under 5-10 GB for the initial install.  I dont know, 100G?  And 100MB for ESP partition 1 if its not already there.

If you select and install from the "non-free" repositories during the install, all should work out of the box.  Intel should work out of the box.  You may want to check what your wifi hardware is and make sure its supported.  Wifi seems to be where trouble appears for support.  As long as your hardware is not VERY new, you should be ok.

You should be ok with any of them.  This is personal preference.  Xfce is solid.  I see mate mentioned alot.  I have been using LXQT lately, like it.

Someone else can chime in here, I thought I read somewhere Devuan strives for a 2 year cycle, so should be soon.  Many of us are running from testing, its been stable.

OK, thats exactly why the text editors are having trouble reading the log file.  x00 is whats called the string terminating character, it defines the end of a string of text.  Leafpad is doing its job; it encounters the x00 and stops displaying text.  Pluma appears to be too anal; seems to be scanning the file for invalid text before displaying anything. 

Another good text editor as well as very useful all around tool is mc.  It will display ALL of the text, including non-text, and its internal editor allows you to modify the non-text characters.  Very useful.

The x00 being in the log file was definitely caused by the ungraceful shutdown, this often happens.

Sorry, I cant help much with the actual hardware problem nor with more shutdown info.  A long shot, since it seems to be ethernet, did you try disabling wake on lan?

I "think" maybe its because the file at:

https://pkgmaster.devuan.org/devuan/dis … SHA256SUMS

is the latest/current file.

Note the sha you are referring to :

f79ea6e9c962b7b4021a216c0a49d847993303b743773995458ac448d59ebdb0    74077 main/installer-amd64/20181213+devuan1/images/SHA256SUMS

Has a date in the name (20181213).

Then note that the sha that was returned by your check, is listed on line:

 b14f1d9375dad1394ff8e5026c272076c51b1bf76464ff556445d49c91cbb103    74077 main/installer-amd64/20190228+devuan1/images/SHA256SUMS

Note the date difference. 

Does this make sense?  I can hardly follow this myself!

If you want to install a desktop environment, install lightdm then install the meta-packages for either xfce (package xfce4) or lxqt (package lxqt or even lighter- lxqt-core).  I have run both on a netbook similar to yours with no problems.  Understand when installing a meta-package that ALOT gets installed; all the way out to pulseaudio.

Its difficult to uninstall a DE and wanting it to fully clean up after itself.  Files will be left behind; configs, etc.  But for the most part it will be removed.

What you might want to try is to install the devuan netinst.iso and do not install any desktop environment at all, make sure to un-check default desktop.  This will give you console only.  Then if want X, install lightdm along with a basic window manager such as openbox.  This will allow you to install and use desktop applications such as a web browser.  Make sure you install a terminal such as xterm or lxterminal to make the window manager usable.  If you find this too basic, then install xfce or lxqt. 

You can get a much lighter desktop if you do not install via meta-package, instead install the individual packages (xfce4*, lxqt*) with --no-install-recommends.  But you really need to understand the components of the chosen desktop env to do this.

I dont know if this is a viable "fix" to propose, but /run/systemd could be changed to a symlink that points to /run/nosystemd (or whatever).  A process would have to be written (along with other required processing to make it work) to do this during init process.  As something fun to try I just manually made this change and everything seems to be working ok.

dxrobertson@acer:/run$ ls -l
total 32
-rw-------  1 root       root          0 Feb 13 15:15 agetty.reload
drwxr-xr-x  2 root       root         80 Feb 13 15:15 console-setup
-rw-r--r--  1 root       root          5 Feb 13 15:15 crond.pid
----------  1 root       root          0 Feb 13 15:15 crond.reboot
drwxr-xr-x  2 messagebus messagebus   80 Feb 13 15:15 dbus
-rw-r--r--  1 root       root          5 Feb 13 15:16 dhclient.pid
-rw-r--r--  1 root       root          5 Feb 13 15:15 elogind.pid
prw-------  1 root       root          0 Feb 13 15:15 initctl
drwxr-xr-x  2 root       root         80 Feb 13 15:15 initramfs
drwx--x--x  3 root       root         60 Feb 13 15:15 lightdm
-rw-r--r--  1 root       root          5 Feb 13 15:15 lightdm.pid
drwxrwxrwt  2 root       root         60 Feb 13 15:15 lock
drwxr-xr-x  2 root       root         80 Feb 13 16:30 mount
drwxr-xr-x  2 root       root        100 Feb 13 15:15 network
drwxr-xr-x  8 root       root        180 Feb 13 15:15 nosystemd
drwxrwxr-x 14 root       root        320 Feb 13 15:15 openrc
drwxr-xr-x  4 root       root         80 Feb 13 15:15 pm-utils
-rw-r--r--  1 root       root          4 Feb 13 15:15 rsyslogd.pid
-rw-r--r--  1 root       root          1 Feb 13 15:15 runlevel
drwxr-xr-x  2 root       root         60 Feb 13 15:15 sendsigs.omit.d
lrwxrwxrwx  1 root       root          8 Feb 13 15:15 shm -> /dev/shm
drwx--x--x  3 root       root         60 Feb 13 15:15 sudo
lrwxrwxrwx  1 root       root         14 Feb 13 16:27 systemd -> /run/nosystemd
drwxr-xr-x  8 root       root        220 Feb 13 16:29 udev
drwx------  2 root       root         40 Feb 13 15:15 udisks2
drwxr-xr-x  3 root       root         60 Feb 13 15:15 user
-rw-rw-r--  1 root       utmp       4224 Feb 13 15:15 utmp

test it:

dxrobertson@acer:~$ cat /run/systemd/users/1000
# This is private data. Do not parse.
NAME=dxrobertson
STATE=active
STOPPING=no
RUNTIME=/run/user/1000
DISPLAY=1
REALTIME=1550088940339646
MONOTONIC=25991508
SESSIONS=1
SEATS=seat0
ACTIVE_SESSIONS=1
ONLINE_SESSIONS=1
ACTIVE_SEATS=seat0
ONLINE_SEATS=seat0

I personally am not bothered by this use of /run/systemd.  Its just a directory name.  If it makes Devuan easier to maintain and less likely to cause potential problems, then thats fine.

I also have systemd files in /run.  I believe elogind may have something to do with it.  I am running all Beowulf, with LXQt 0.14 from unstable.

root@acer:~# cd /run
root@acer:/run# find systemd
systemd
systemd/inhibit
systemd/inhibit/1
systemd/inhibit/1.ref
systemd/cgroups-agent
systemd/inaccessible
systemd/inaccessible/blk
systemd/inaccessible/chr
systemd/inaccessible/sock
systemd/inaccessible/fifo
systemd/inaccessible/dir
systemd/inaccessible/reg
systemd/machines
systemd/sessions
systemd/sessions/1
systemd/sessions/1.ref
systemd/users
systemd/users/1000
systemd/seats
systemd/seats/seat0
root@acer:/run# 

I then removed /run/systemd.

Then went to a console via <CTRL><ALT>F2, and was surprised to find a series of messages displayed, and continuing to display:

[2299.263755 ] elogind-daemond[2150] failed to save user data /run/systemd/users/1000: no such file or directory

There are also similar messages for session, instead of user.

PID 2150 is elogind-daemon.

elogind version:

root@acer:~# apt list --installed elogind
Listing... Done
elogind/testing,now 239.3+20190131-1 amd64 [installed]

Another reference to run/systemd, unrelated, and since its a "not"; probably actually needed.  From syslog:

Feb 11 16:30:01 acer CRON[3837]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)

Odd.  I am now having the very same problem, with synaptic, in LXQt.  Cant run from menu but can from terminal.  I just switched from using qterminal to using the old lxterminal.  Have the same error as you and same env value: TERM=xterm-256color.  I did not have this problem until I switched to lxterminal.  Will do some more research.

It needs to BE COMMENTED OUT, or removed, /etc/network/interfaces should be:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

It looks like you have an Atheros chip.  Package firmware-atheros should provide the drivers.  Its in non-free so make sure thats included in your sources.list.