Hello:

Please correct me if I am wrong ...

Am I to understand that the Alpine distribution has issued a patch that basically backpedals on what Poettering so stubbornly pushed through?
And that in doing so, the line in dmesg complaining about group 'kvm' not being found is then not generated by the system?

TIA

A.

Hello:

I think I got the right idea.  =^)

Just commenting out chmod 0666 /dev/kvm and chgrp kvm /dev/kvm (reported as a bug in the thread I linked to) should suffice. 

From what I have read (not nearly enough) it seems that it is something used solely by the qemu-kvm package.

eg: I run a couple of VMs via VirtualBox in my ascii installation

groucho@devuan:~$ uname -a
Linux devuan 4.9.0-13-amd64 #1 SMP Debian 4.9.228-1 (2020-07-05) x86_64 GNU/Linux
groucho@devuan:~$ 

The node is there:     (the cpu-checker package does not seem to be in the ascii repository)

~$ ls /dev/kvm
/dev/kvm
~$ 

I don't have a 'kvm' group:

~$ grep kvm /etc/group
~$ 

Yes, under the modularization principles that governed Debian development and maintenance from the start, crap like this would never have happened.
Nor would a thread as the one I linked to even existed.

That's where we are.

Thanks a lot for your input.

Cheers,

A.

Hello:

Right.
I'll try that.

But ...
The file starts like this:

# do not edit this file, it will be overwritten on update

# The static_node is required on s390x and ppc (they are using MODULE_ALIAS)
KERNEL=="kvm", GROUP="kvm", MODE="0666", OPTIONS+="static_node=kvm"

Is this ^^ the line?
I guess I could comment out the whole line, see what happens and remember when an update comes along.

Q: isn't s390x a 64bit IBM mainframe and PPC PowerPC?
ie: need a diiferent kernel than the one (amd64) we're using?
If so, what valid motive is there for this 'kvm' group thing?   

I'm not a maintainer, coder or even an advanced user but I get a bad feeling when I see things like these being done in this manner ie: just because.
From reading the thread I linked to I cannot but suspect that, coming from systemd's creator, there may be something else behind this.
But then that's just me.

Thanks for your input.

A.

Hello:

OK.

Indeed ...   =^)

I know that feeling too well ...

The Beowulf installation I'm working on is a net-install which I expected to be bare-bones by design.
But live-tools seems to have been installed either by the net-install installation process itself or something else.

~$ apt list | grep -i live-tools
live-tools/stable,now 1:20171207 all [installed,automatic]  <--- came with what?
~$ su -

I certainly don't recall installing it.

I've removed it as per your suggestion.
Did not drag anything along with it.   =^)

I'll keep it.

Thanks for your input.

Cheers,

A.

Hello:

Right.

No problem whatsoever.
Thanks a lot for your input.

Cheers,

A.

Hello:

Right.

So, when I drop to a terminal via  Ctrl+Alt+F1 I will be on TTY1 (or TTYn depending on the Fn used) save for TTY7 which is already running and which I get back to by means of Ctrl+Alt+F7. Yes?

Thanks for the explanation.

Cheers,

A.

Hello:

I find the tone in your posts to be both unwarranted and out of place, a view that I expect many here at Dev1 share.

I would personally appreciate your showing more respect to those who volunteer their work to keep this site working.

Thank you.

A.

Hello:

Apparently it is all fixed.
I'll have to see how things go with the logfiles and MSOffice/LibreOffice stuff.

~$ cat /etc/default/keyboard
# KEYBOARD CONFIGURATION FILE
# Consult the keyboard(5) manual page.

XKBMODEL="pc105"
XKBLAYOUT="latam"
XKBVARIANT="deadtilde"
XKBOPTIONS="lv3:ralt_switch,terminate:ctrl_alt_bksp"

BACKSPACE="guess"
~$ 

Took me a while because I was incorrectly setting nodeadtilde, fussing up the layout.

~$ cat /etc/default/locale
#  File generated by update-locale
LANG=en_GB.UTF-8
#LANGUAGE=en_GB.UTF-8
LC_CTYPE="en_GB.UTF-8"
LC_NUMERIC="en_GB.UTF-8"
LC_TIME="en_GB.UTF.8"
LC_COLLATE="en_GB.UTF-8"
# LC_MONETARY="en_GB.UTF-8"
LC_MESSAGES="en_GB.UTF-8"
LC_PAPER="en_GB.UTF-8"
LC_NAME="en_GB.UTF-8"
LC_ADDRESS="en_GB.UTF-8"
LC_TELEPHONE="en_GB.UTF-8"
LC_MEASUREMENT="en_GB.UTF-8"
LC_IDENTIFICATION="en_GB.UTF-8"
LC_ALL=
~$ 

~$ locale -a
C
C.UTF-8
en_GB.utf8
es_AR.utf8
POSIX
~$ 

For future reference in case anyone else comes across a similar problem, this is the keyboard layout -> http://kbdlayout.info/KBDLA/
No, I don't use a MS kb. this web page is very useful (has scan codes, virtual keys, etc.) and references to kbdla.dll which is a MS file. 8^P

Thanks for your input.

Cheers,

A.

Hello:

I think that posts which have not received an answer should have no time limit for edition by the OP, who should also be able to delete it if deemed necessary.

But, if a post has received an answer the OP should not be able to delete it.

With respect to editing a post that has received an answer, I'd say that it depends on the forum.

I have had a forum member (not here, of course ...) edit his original post and in doing so make my answer look out of place.
ie: like if I was replying to something that he did not write, to the extent of making me doubt for a second as to what I had read.

It's only happened to me once in more that 20 years of participating in different fora, but I found it to be rather unsettling.

I'm sure that here at Dev1 it could be allowed (with the provision of automatic edit notices) for as long as it takes for a second reply to come in.
From the on, that particular post would be closed to editing.

Make sense?

Cheers,

A.

Hello:

I see ...

But I have not had to do this in any of the other instances where I installed these same legacy-340xx drivers in other Linux distributons.

It did not happen when I moved from Linux Mint to a fresh Devuan Jesse installation either.
So why does it happen now in Beowulf?

The legacy-340xx driver is in the Beowulf distribution just as it was in the Jesse distribution.

Thanks for the heads-up, I'll keep the link in the Devuan bookmarks folder.

Once again, thanks for your help.
I certainly would not have my three screens in Beowulf without it.

Cheers,

A.