Hello:

I have yet to find a logical explanation for the actual benefits of using anything but the default sysvinit in a Devuan desktop box.

A.

Hello:

No idea.
Had never heard of it before Devarch mentioned it.

Apparently (?) it is an alternative to [overlayroot].

[bilibop] Ubuntu manpage.

It can also be found in the Devuan repositories.

Best,

A.

Hello:

Does it?

For whatever reason, you seem to have have generated a size issue in the drive, apparently [root] which the OS reports being full.

Maybe your "small SSD" SDD is indeed too small for what you are attempting to do.
Maybe your partitioning is not the right one for a drive that small.

That said, bear in mind that you are on a [testing] release.
As such, it is usually/always problematic.

Boot with [gparted] live, open a terminal and run df to see "what is where" so to speak.
See what space [/home] and [/var/log] are using/have available and delete whatever you do not need to try to improve the situation.

Nuke a file named [.xsession-errors] usually found in [/home].

You may be able to boot after cleaning up all that.

A.

Hello:

Nice find!

Note that the list of students (seated at the table) in the photo includes a spook suit student from the NSA.

Best,

A.

Hello:

zk is not available in the official Debian repositories, which is the reason for it not being in the Devuan repositories.

If and when it gets included in the Debian repositories and has no 'unfixable' dependencies on systemd, you will find it after a few days in the Devuan repositories.

Until then, you (most probably) have the option of building it from source.

Best,

A.

Hello:

Sorry for the delay in answering, was away from my kb.
Or maybe the kb was away from me? 8^°

Good to know.

Thank you for the detail but I fear it is all rather over my head.
But it is good to know it works as you intended which means that it will most probably work for me.

So, one down. 8^)

The basic question for me would be if it will work for my (simple?) use case and most important, how to go about it.

To wit:

1.
Not decided yet but most probably will not be entering the Devuan Excalibur scene.
Reasons being how complicated it is getting (and will get) and the fact that (as mentioned) my box* works perfectly well with Daedalus.

That means I will not purchase any new core hardware (MB, PSU, etc.) save something wreaking havoc with my Sun U24.
Possible exceptions would be finding the odd SAS2/3 spare and matching controller, or a four socket PCI-E video card to replace the twin two socket FX580s for a decent price (liberating a PCI-E slot) or having to replace one or both of the SyncMaster 940n flanking a newer but also discontinued Dell P1914S.

*
TL;DR: all hardware that will run perfectly well with Devuan Daedalus (or even Chimaera) without a hitch - PBKAC being the obvious exception.

My idea (if feasible) is to run a Devuan Daedalus box in a highly protected space, isolated from the web for work/office crap.

And at the same time have web access by other means. eg: a VM running an up-to-date Devuan live ISO with some sort of sandboxed environment for banking, sharing downloads or video streaming (which I do quite a bit at these days).

My box hosts a headless Devuan Chimaera VM with a Pi-hole/Unbound DNS which could be moved to a RPi3B+ living in a drawer. It may then justify the time and money I spent on the bloody thing and in doing so, liberate memory (8Gb) and CPU (Intel Q9550) cycles for running the above setup.

That is about it.

Best,

A.

Hello:

Not necessarily, more so if your graphics are working properly.

I had the same issue with my Nvidia Quadro FX 580s and Nouveau drivers.

See here: https://dev1galaxy.org/viewtopic.php?pid=51169#p51169

Best,

A.

Hello:

I got rid of all XFCE power management stuff back in ascii, it was a PITA.

Best,

A.

Hello:

Means the same thing as before: screen is going to sleep.  8^°

As you can see from your printout ...

--- snip ---
DPMS (Display Power Management Signaling):
  Standby: 0    Suspend: 0    Off: 0
  DPMS is Enabled
  Monitor is On
--- snip ---

... DPMS is/was enabled.

What does $ xset q say now?
ie: after the commands.

BTW: what desktop have you installed?

If XFCE, have you read this? it is in the body of https://dev1galaxy.org/viewtopic.php?pid=31558#p31558

Best,

A.

Hello:

8^)

Best,

A.

Hello:

Indeed.

Like I wrote elsewhere:

Of course, 'choice' is a good thing to have.
For when it is needed and you absolutely know why you need it.

Not just for the sake of it.

Best,

A.

Hello:

I have had a similar issue with my Sun U24 WS for years, fortunately it is not at every shutdown but just when the %$#"¿ crap BIOS feels like it.

I have found that it occurs when there are sharp changes in ambient temperature between booting and shutting down, most probably due to a badly written BIOS + a faulty/wrong on-board sensor spec, so it is an issue I decided to ignore.

That said, yours seems to be a well known issue with that Dell rig.
A quick web search with the unsolicited Google IA intervention (?) brought up this*:

* to be taken with a few grains of salt. 8^°

See here.

If sudo halt works, you may want to write up a script to shut it down via sudo halt && sudo shutdown -now.
Check the respective man files for the proper syntax.

Best,

A.