The officially official Devuan Forum!

You are not logged in.

#1 Re: Installation » two questions, new to Devuan » 2020-11-07 14:19:17

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.

#2 Re: Installation » two questions, new to Devuan » 2020-11-04 15:35:06

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.)

- 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:

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:

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:

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?


#3 Re: Installation » SOLVED: Release file for updates is not valid yet » 2020-11-04 14:42:47

Thanks very much Head_on_a_Stick, wasted so much time trying to figure out why the clock was wrong on Devuan but not on any of my other cinnamon desktops.  It is now correct, thanks to your help:   
# apt install ntp
That's all I needed.   Reboot, and now it acts like all the other Cinnamon desktops from Debian, Mint, Manjaro..
When I saw that message on my screen, a couple of days ago, just as nobodyuknow has written: not valid yet (invalid for another 3h 4min 44s),
I had entered bios, changed passwords, danced a jig, and played the ukelele, all to no avail.

#4 Installation » two questions, new to Devuan » 2020-10-29 12:34:12

Replies: 18

Please feel free to move this to "Other topics", or elsewhere if another section is more appropriate.  Two questions and accompanying comments.  Today was my first encounter with Devuan, and the overall experience was largely positive--thank you.

1.  Printer:  effortless.  Worked very well.  Thanks to all.  Question is coming....  First:  a dozen odd (and some "old", but all 64 bit) computers running Debian, Mint 19.3, or 20.0.   A fresh install of 19.3 is accomplished just as easily as today's install of Devuan Beowulf.  No such luck, however, with Mint 20.  Reason, I guess, is because Ubuntu no longer supports 32 bit drivers for my printers, scanners, etc....all of which, themselves, work just fine, though they are a decade or so, old.  I am not flush with cash, and reluctant to discard something just because a shiny new toy exists.  I am keeping my printers and scanners, and hoping that I will continue to find a Linux version to support them, though they are connected via Win XP software, on a separate computer running that antique operating system.  Question:  How long will I be able to use Beowulf, to print, or, is the future looking just as bleak, as it does, for Mint 20 --where my devices no longer function?

2.  Sound:  Wow, felt like back in 1980 running Unix on a Dec VAX.  Very primitive, completely the contrary to the experience with Mint 16, 17....20.   This is to my way of thinking, a killer, for this OS, if it isn't possible to fix, in a forthcoming iteration.  Of course, could be user fault.  This is my first experience, and four hours later, I still haven't solved the issue.  Granted, unlike the first hour, I do have sound!!!  hurrah.  BUT, the road isn't obvious, nor does it work, simply by turning on the computer, as everything else does.   In the olden times, we had to type, for example, startx, which was a user interface to the X-Windows system.  How many users of Devuan would be pleased to know that they could see the desktop, whenever they wanted, just by typing startx ?  I don't want to type startx.  I want the desktop to work when I turn on the computer.  Ditto for sound.   More than an hour of fiddling, editing obscure files in /etc, and so on, I STILL DON"T HAVE audio, unless I open a terminal, and yes, TYPE, no, not startx, but rather, pulseaudio --check   followed by pulseaudio -D.  N.B.  (nota bene) these two commands work, and work well, however, one must not type pulseaudio -check, or pulseaudio --D.    Those hash marks, i.e. hyphens, must be spaced and elaborated, exactly as shown.  WHY?  Why must I type these two commands with their oddly asymmetric hyphens, every time I boot the computer, as if "startx", all over again?  (mind you, startx was  itself, an improvement, three decades ago, over the alternative!!!)


Board footer

Forum Software