Altoid wrote:

Why it is alluring to so many people?

Well the 5nm process is pretty good, especially considering that Intel are still stuck with their antediluvian 14nm dies, and the reported benchmarks are actually quite impressive. But Ryzen still kills it

Anyway I'm with steve_v — Apple are a bunch of ****s. I threw a massive party when Steve Jobs died.

Wayland and Gnome is the only combination (must tell I didn't know how it is on KDE) there you get a completely color managed environment. Even the desktop picture is color managed. Because I use Linux even to photomanagement It's a big step forward. And Wayland works fine.

Thanks for the several comments.  Tone:
some folks dislike criticism.
Fine.  Tough.  Don't read my submissions.

Reading distro notes:   Until Devuan, never wasted one minute reading them.  Either an  OS is transparent, and works effortlessly, or it needs criticism.

Fanboy club:   I am not such a person.

I see some very good things here at Devuan, and including this forum.  I also see a couple of issues that need clarification.  I still don't have the answer to my questions about the distinction between Devuan and systemd, with respect to that obscure file,  and the need to comment out a line of code to enable sound.  How could that attribute (absence of sound on initial boot up after installation) pass inspection/quality control, prior to release of the distro?   There ought to be an explanation for this peculiarity.  Why is this feature something that Devuan developers are PROUD of?  Do the problems that I encountered relate to the Cinnamon desktop in particular?  Does printing work with Devuan, and NOT with all the other distros, because Devuan bypasses systemd, or because of the version of Cinnamon in Devuan: 3.8.8, vs Mint 19.3 :  4.4.8 ?

"That's how we do it here at..."  Nuts.  Nonsense.  Stupidity.

Tone II.  Really?  You  work with LInux, and you want someone to write soothing remarks, in a mild, temperate, inoffensive manner.  Linux, at least back in '94, was created and operated out of anger at the stupidity of society sucking on the Microsoft teat.  I did not catch on, until '98. Even then, I stayed with M$ 98->XP for a decade.

I am ANGRY.  I wasted hours trying to find what was wrong with my computers, because of stupid mistakes.  I made them, and Devuan made them.  But, not reading the release notes, was not one of those errors.

I like that review. I also appreciate having a systemd free distro that works well. Took me a little time and work to get it set up (not weeks like the "CFI" haha), but it was worth it.

SOLVED:  sound works now, after reading RELEASE NOTES, and editing the obscure, incomprehensibly named file "00-disable-autospawn.conf", to REMOVE (unintuitive--why would anyone have to comment out a line of code to enable something to work, normal software engineering works in just the opposite fashion, edit a file to add something desired--here we are removing a constraint which prevents what we NORMALLY expect, from happening.) Devuan demands that every user insert a pound sign, " # " in a line of code in a configuration file, to be able to hear sound as expected. 
That's just too much 1960's architecture for my taste.  I am seeing cold rooms with big tape drives, and heavy security to access the wonderful IBM hardware.  NOT for me.

(Editing this silly file is certainly not required to hear music, in running Cinnamon on any other distro, that I have used, e.g. Mint 17.1, Debian Squeeze.)

Pulseaudio
- If you have no sound, make sure the following line in
   /etc/pulse/client.conf.d/00-disable-autospawn.conf is commented as
   shown here:
   #autospawn=no

In other words, the much vaunted, highly touted "RELEASE NOTES", illustrate how that line in the file must look, AFTER editing, by each user of Devuan.   BEFORE editing, that line of text reads like this:
   autospawn=no

To listen to music, with Devuan, but not other Cinnamon versions, one must insert a pound sign into a line of text, to disable that text.

I am very keen to learn which page of Donald Knuth's "The Art of Computer Programming, volume I", corresponds to this notion, demanding that users comment out a line of code in order for a particular function to work as one normally would anticipate, upon successfully completing an installation of Devuan.

Why would several forum participants request/demand "relevant troubleshooting information", to solve this problem?

What is the difference between ADDING a pound sign in front of a line of code not required, vs, changing the code to read:
   autospawn=yes

?
What is it about "system D" that enables that collection of code to permit the user to hear music at once, upon completing the installation, vs whatever it is that Devuan uses to replace "system D", i.e. why should "system D" enable sound, but not whatever it is that Devuan is using?

caieng

No.

Ron and zapper retaliated to post no 4, with the somewhat condescending "stockholm syndrome" comments, then proceeded with a line of argumentation in much the same format - i.e emotionally charged and misinformed.

Then when I offered critique of their top favourite web browser, grew more hostile and emotional and continued to paint me as a google fan / apologist.

I'm more of a Microsoft fan actually.

zapper wrote:

+1 for locking this dumb thread

Well, this wasn't a "dumb thread" when I started it.

Looking at how fast it went off the rails in several respects, though, I regret having opened it in the first place.

Some people, it seems, just can't have a civil discussion. And, apparently, you're one of them.

Is it time to lock this useless thread?

zapper wrote:

Whenever HyperbolaBSD is finished...

I wouldn't hold your breath nor stake your hopes on a project which makes such "hyperbolic" statements as:
"Due to the Linux kernel rapidly proceeding down an unstable path..." and talks a lit about GPL3 while planning to base its project on code which is anything but.

zapper wrote:

I have interest in this because of wine-staging doesn't work in it

So you have an interest in an, at this stage, theoretical project from developers that want use the OpenBSD kernel, GNU userland, remove all firmware and "liberate" the kernel, just so that you can run wine and MS Windows programmes? I see.

zapper wrote:

Edit here, OpenBSD disabled the mutlilib in wine for security reasons,

The OpenBSD project don't do any work on wine. The wine port has been incomplete / broken / abandoned for years.

zapper, there is no "feud". You are spreading misinformation and betraying your own ignorance. Please stop.

This a bad case of "the mote and the beam"... first exhibit is your trolling of the OpendBSD misc mailing list with misinformation:

https://marc.info/?l=openbsd-misc&m=158692336815902&w=2

Software like wine or palemoon belongs in "ports" in any of the BSD projects. They are not part of the base system. If you want an OpenBSD port of palemoon, you're free to contribute one.

Your embarassingly childish outburst again on the misc mailing list, only betrayed yout complete lack of knowledge of the project.

https://marc.info/?l=openbsd-misc&m=158692845817261&w=2

Because you cannot post snything factual or worth taking the time to read you are ignored.

@Ron, is "old and obsolete, though still actively developed, code" better?