You are not logged in.
If you have a routing problem try sudo route -n on the pi *and* on your other system both when the ethernet cable is plugged in and when it's not. If you can't work out how to fix it after reading the man page for route then post all the output here.
I'm not an expert but I have managed to fix a few routing problems. Although mostly by guesswork.
Chris
@Head_on_a_Stick
nobody@toshiba128:~$ pgrep -a expressvpn && echo 'It's running' || echo 'Not running' >
The command you were given contains an odd number of quotes. Try
pgrep -a expressvpn && echo 'It is running' || echo 'Not running'Chris
Where did you get the installation medium from? And when did you download it? What version of Devuan does it say it is?
Chris
To save typing I'll assume the user account is called fred. Replace it below if that's not true.
The first thing to try is ctrl-alt-F1 to get to a text console, then try logging on as fred. If it fails you may get interesting messages.
If that fails use ctrl-alt-F7 (or ctrl-alt-F6) to get back to the normal GUI, log on as root, open a console and enter su fred. If that works the account should be OK, but the password may not be what you think it should be.
To fix the password enter passwd fred. This should ask you for a new password for fred. Then try logging on as fred.
If that fails post output from grep fred /etc/passwd here.
If all else fails set up another user account from scratch.
Chris
My first step would be to add:
set -xnear the start of the script. This would tell bash to display the dd command as it will be executed after variable substitution. See the man page for bash for details.
Also look at set -n which tells bash to read commands but not execute them. This could be useful to syntax check the script before letting it do anything.
Chris
Does a directory called /var/db exist? If not try sudo mkdir /var/db
NB: I'm only guessing since I don't use DHCP. But the "can't create /var/db/dhclient.leases: No such file or directory" message looks suspicious.
Chris
It runs well enough on the core i5 with 4Gb desktop I'm posting from. So he should be OK (unless being a notebook causes a problem).
Chris
Reading distro notes: Until Devuan, never wasted one minute reading them. Either an OS is transparent, and works effortlessly, or it needs criticism.
The release notes should be the first place to look if you do have problems. Or want to know the distro in depth.
And please allow for the fact that it's impossible to test a distro with *every* combination of hardware etc that any user could have.
Also remember that the people who built it are doing it in their own free time. Ask yourself how you would feel if you were the one being asked about something you built in your own time. Politeness will be more likely to get you helped. As will providing details of what you are doing and think is wrong.
Chris
At a guess FDE stands for Full Disk Encryption. Which seems to match his description.
But we still need more details to have any chance of solving the problem.
Chris
It sounds like it would be a good idea to disconnect from the Internet before starting Firefox for the first time. So you could configure it to disable telemetry etc without giving it a chance to phone home first.
But it's a bad sign if you need to do that. Ideally it should be shipped with telemetry etc disabled by default.
Chris
Try sudo -i in a terminal window. Hopefully that should ask for your user password then take you into a root shell. Then you can use passwd root to change the root password (it sounds as if it's not what you think it is).
Chris
root@devuan3:/# ls /dev/nvidia ls: cannot access '/dev/nvidia': No such file or directory root@devuan3:/#
Try ls -l /dev/nvidia* (the file names just start /dev/nvidia so the * is important). And ls -l to see what permissions they have is useful.
I get:
chris@rigel:~/bin$ ls -l /dev/nvidia*
crw-rw-rw-+ 1 root root 195, 0 Aug 25 2019 /dev/nvidia0
crw-rw-rw-+ 1 root root 195, 255 Aug 25 2019 /dev/nvidiactl
crw-rw-rw-+ 1 root root 195, 254 Aug 25 2019 /dev/nvidia-modeset
crw-rw-rw-+ 1 root root 248, 0 Aug 27 2019 /dev/nvidia-uvm
crw-rw-rw-+ 1 root root 248, 1 Aug 27 2019 /dev/nvidia-uvm-toolsChris
Hello bimon,
The staphylococcus poisoning was probably an accident. It's impossible to say exactly what effect it would have on any given individual. So it's not any use to control someone.
There's an old saying, "Never ascribe to malice anything adequately explained by stupidity". Which fits this case quite well.
But if you do need to keep secrets:
1: The safest option is to keep it all in your head. If you must share information talk face to face and make sure there are no listening devices around.
2: Use pencil (or pen) and paper. Mass surveilance of mail is too much work for the authorities (at least in civilised countries). If you must use a computer use one that's not connected to the internet (check for wireless adapters etc). This is standard for tax advisers etc (not illegal but laws can be changed to your disadvantage if they know what you are planning).
3: If you have to use the internet then use normal computer security procedures. And keep anything really sensitive off the system.
Chris
My approach is to put entries in /etc/hosts for local hardware. See the man page for hosts for details of how to format entries. This is quite manageable if you only have a few systems which all have fixed IP addresses (eg 1 router and 1 printer). And then use DNS for everything on the internet.
Chris
To ask the obvious question, how much RAM and swap space has your new laptop got? Run free -ht on it to find out (and on your old one to see the difference).
Chris
Try ctrl-alt-f1 (pressing all 3 keys at once in that order). That may get you to a text console. Then you could log on and investigate.
If you have another system try logging on over the network.
How hard is it hung? Does pressing caps/num/scroll lock toggle the LEDs on the keyboard?
What sort of system is it (laptop or desktop, make, model, cpu, etc)?
Does it have a reset button? If so does it work in the hung state?
Chris
ps -e | grep DeleteService should tell you the PID in the first column of output. Try ps -p xxx where xxx is the PID. Then ps -fp xxx and ps -Fp xxx.
If the last two don't work look in /proc/xxx and see if you can find out what it is (compare with /proc/n for tasks that appear normal).
If you can't find the PID try ps -e | less and ps -ef | less etc.
But I don't have such a task running so I'm guessing if this will help.
Chris
All it's doing is checking how many lines containing 'load average' uptime produced. So it's just testing if you can use sudo. But I've not seen this technique before. And as bgstack15 said "sudo -l /actual/command/to/run ; echo $?" is probably better, it should not fail if you can run uptime but can't run the actual command.
Chris
Why use SAMBA between Linux and Mac? They are both UNIX variants so NFS or something similar is more likely to work.
The only situation I would want to use SAMBA is if I needed to share files between Windows and Linux systems.
Chris
Can you ssh onto the new system from your old system? That would enable you to read dmesg, /var/log/messages, etc to see if they say anything useful without having to enter commands blind. And to update files on the new system if necessary.
Chris
Do you have a desktop or a laptop? In either case my first thought would be to clean dust etc out of it to stop it overheating. If that fails on a desktop I would think of improving case ventilation or fitting a better cooler.
I've had systems where clearing dust and fluff out reduced CPU temperature several degrees.
Chris
Before setting up a user called pi you could try ln -s /home/chris /home/pi (replace chris with your id). It probably needs to run as root to update /home.
If it doesn't work delete it before trying to set up a user called pi. Or "interesting" things might happen.
Chris
The config.log file should be in the same directory you ran ./configure in. Try less config.log to see what's in it.
If that fails ./configure is usually a script so you could look at it to see where it puts config.log. But it might be hard to follow if you don't know shell scripting.
And you may need to build a live CD with gcc on it to make this work.
Chris
Assuming the network is working run ifconfig on the new system (or /sbin/ifconfig if not running as root). That should tell you what IP address it has. Then ssh to that IP address from the system you are posting from. That should get round DNS not being set up. You may need to start sshd on the new system and/or update the firewall on it to allow ssh connections. Reply "yes" when ssh says it doesn't know the host key.
Then you can run commands on it and post output from them here (include the command itself in your post).
Chris
I've got several systems I administer by ssh'ing from my main system so I had this problem too.
My main system sets the window title to match the prompt, eg to the following:
chris@rigel:~/binBut most of the other systems don't set it. As a work around I created a directory named after each system on my main system, cd'ed into it and ssh'ed from there onto the other system. So the window title says something like:
chris@rigel:~/vegawhich tags the window as being the one ssh'ed onto vega. It's not ideal but it helps.
Also on all my systems the prompt says the hostname as well as the current directory. Train yourself to look at it before doing anything. You might be able to set the prompt to different colours on different systems (although I prefer green prompt most of the time, but red if I need to run as root).
Chris