If you have more than 1 system try ping, ssh, etc from another system to see if the hung system responds.

Does pressing caps/num/shift lock turn on the light on the keyboard?

Do any of the lights on the motherboard or NIC show anything significant (if the light's usually on when it's working and off when it's sleeping what does it show when the systems hung?)

Chris

Pressing control-S just after the messages come out might enable you to read them (then control-Q to continue).

If that fails could you take a video of the console during shutdown, then play it back slowly?

Chris

Hello,

I had a lot of "fun" getting CUDA working under Devuan. See the following threads for details:
https://dev1galaxy.org/viewtopic.php?id=2299
https://dev1galaxy.org/viewtopic.php?id=2259

And search the forum for keywords like CUDA, Nvidia, nouveau, etc.

Chris

ESR is one of the better known figures in the UNIX world. You can read most of his writings at http://www.catb.org/~esr/ (several are well worth reading).

He made several good points about how to make Devuan easier to install. In particular having one and only one installer per architecture that then asks what sort of install you want to do and if you want to install non-free code. If you must keep old versions available then clearly label them as deprecated (and don't put them on the home page).

He could have been a bit more tactful but that's no reason to reject everything he said.

A magazine cover disk may need to be more specialized since space is limited (they may want to have more than 1 distro on a single DVD) and it should be usable to install on a system that does not have internet access. But the people building the cover disk should be more experienced than the average user.

Chris

For messages coming out during the bootup try control-s to freeze screen output and control-q to restart it. That should stop them long enough to copy them down (or take a photo of the screen).

Chris

Check what /etc/nsswitch.conf says for hosts (see the man page for nsswitch.conf for what it means).
Check /etc/resolv.conf (that tells the system which DNS server(s) to use).

If there is more than 1 DNS server in there try commenting out all but one and checking if it works with that one.
If there is only one them comment it out and add nameserver 8.8.8.8 (that's google's nameserver).

Chris

It's worth fighting for access to source code whenever you can.

Eg if you are involved in a product liability lawsuit make sure your side's lawyers ask for full source code during the discovery phase. That makes life harder for whoever owns proprietary code (it's usually easy to find a few silly bugs in any sizeable amount of source code which makes them look bad in court).

Chris

Running chmod 755 /var/log/lost+found as root will allow all users to read /var/log/lost+found but not put anything in it. lost+found is where fsck puts files it has recovered from a damaged filesystem so there is usually nothing in there. I would not worry about allowing read access to it unless I have sensitive data on the system that not all users should be able to read.

Chris

From the log

Jul 15 21:36:55 BOSSDESK kernel: [28145.560311] [ pid ]   uid  tgid total_vm      rss nr_ptes nr_pmds swapents oom_score_adj name
...
Jul 15 21:36:55 BOSSDESK kernel: [28145.560366] [  864]  1000   864  7501335  1891569   13923      33  5141580             0 mate-settings-d
...
Jul 15 21:36:55 BOSSDESK kernel: [28145.560437] Out of memory: Kill process 864 (mate-settings-d) score 968 or sacrifice child
Jul 15 21:36:55 BOSSDESK kernel: [28145.560449] Killed process 864 (mate-settings-d) total-vm:30005340kB, anon-rss:7566276kB, file-rss:0kB, shmem-rss:0kB

So I think mate-settings-d has a bug. It should not have that large a RSS (Resident Set Size).

Chris

The way I would have done it it to make all systems that act as servers have a fixed IP address. Then systems connecting to them can use that IP address (preferably an entry in /etc/hosts).

First check what range of addresses your DHCP server can hand out (eg 192.168.1.2 to 192.168.1.200). Then give the server an IP address that's not in that range. You get problems if two systems try to use the same IP address.

Or configure the DHCP server to give the relevant system a fixed IP address.

You may not need this advice now, but someone else might find it useful.

Chris

See https://www.schneier.com/blog/archives/ … o_tra.html for details of a big hole in most browsers cookei handling.

Chris

First try:
ping -c 1 wiki.debian.org
on both systems. You should get something like:

$ ping -c 1 wiki.debian.org 
PING wilder.debian.org (82.195.75.112) 56(84) bytes of data.
64 bytes from wilder.debian.org (82.195.75.112): icmp_seq=1 ttl=53 time=41.9 ms

--- wilder.debian.org ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 41.989/41.989/41.989/0.000 ms

Chris