I guess i should have changed tables rules and install+configure dns stuff *before* i started removing unnecessary packages. The removal of unnecessary packages caused removal of iptables also and after that things went kind of complicated.

Anyways, dd or cp from hdd to sdd is still an option.

That reminds me of avahi. It got in my way when i tried if it is possible to do thing x with dnsmasq. Some webpages have also considered avahi as a security risk.

I guess distros with systemd work in a sense that i can run firefox and vlc and virtualbox and stuff like that.
But i'm not fully convinced it is a way to go. On the other hand i sometimes wonder if all those scripts related to sysvinit are absolutely necessary, could you do things another way instead? Make init or inittab do the jobs of those rc-scripts somehow?

But i'm more familiar with shellscripts and maybe Python and Docker than i'm with C so i guess for now i use sysvinit and that's it.
Familiar in the sense that i can be dangerous with them, i mean

Again i think that bios battery is not the whole story. With my "new" desktop things have detoriorated to a situation where it won't boot even from hard disk. I get complaints from bios instead.

I have changed battery 2 or 3 times this year. Tried also returning bios settings to factory defaults once or twice. Changed sata cables also, just in case.
Very interesting problem indeed. Unfortunately i have some things to do, preferably within a deadline. So now is not a good time for further research.

In a way this reminds me the last seasons of Stargate, there were this bad guy called Anubis. He had to change hosts often.

For a while i thought that wrong access rights in /tmp-directory was a root of all problems i've been lately having with Devuan. Now i'm not so sure anymore. This morning i tried again installling Devuan into Fujitsu. With chimaera desktop image on a stick i mostly made it working.

Then i screwed up something, again. (Being tired enough is not so different from being drunk. ) Could't login as a normal user even after chmod 777 /tmp. And also something went wrong with "iptables/dnsmasq/dhclient"-side of things in the sense that apt didn't work. There were some complaints related to name service.

Again it seems necessary to find a software less difficult than slim.
I don't think sudo is a problem anymore.

Now i have confirmed that the scripts are cause for "su"-related problems. Command "su -" worked as normal user before.
So now i have to rewrite the scripts from scratch, preferably up-down-style this time, AND inside a virtual machine so that the damage to host os is limited to absolute minimum.

Maybe some day i have a working Devuan in my desktop's harddrive. After that it is time to find out if that dd-trick works with Fujitsu.

Also reconfigured most of the installed packages so that i could kill X with ctr+alt+backspace. After reconfiguration that combination still doesn't work.
Btw, why there's no configuration file for X under /etc/X11 ?

It starts to look like quicker just to copy contents of my old laptop's ssd into new laptop's ssd. I mean, if i can trust that the install stick and usb-storage module still works. I have noticed that the memory sticks and cards today tend to be use-once-and-throw-away garbage.

What kind of installation media are you planning to use? Those which have Refractainstaller or netinstall ?

I could get in only into 1 tty. I'll soon check what /etc/inittab says. Maybe something is still missing or Fujitsu's keyboard is a bit faulty.

It kind of made sense that i cannot get into root account by using "su -" if i enter wrong password too many times. But now i think that it could be unrealiable caps lock key/light also.

More successful attempt this time.
I can log in as root. And as a normal user.
But i cannot get into root account by saying "su -" (as a normal user). Have to add "man su" into my reading list to find out why.

Some of the weird behaviour can be explained by the absence of sudo. I had some scripts to automate some tasks. Those scripts required sudo and there was none. Also there were some dependencies that i missed. That's why netfilter-persistent didn't work.
It have become clear that last year when i previously tried Devuan netinstall, i didn't pay attention to that "sudo-situatopn". Root-on-lvm was more important.

X works. But the "pad" and external mouse don't. Are people still configuring X or does that happen automagically?

This time i think i try alternatives for slim and xfce. Lxdm seems to attract libavahi and libcups so maybe not that.

One thing i noticed while going through UEFI settings:it has been updated last ... december. So in theory that update could have complicated the process.

Now i have new stick for round #2. First I thought that i'll copy Daedalus into it. But i can't find SHA256SUMS or SHA256SUMS.asc in https://files.devuan.org/devuan_daedalus/installer-iso/ . What's up with that?
Maybe i''l stick to Chimaera for now  and confirm that the dvd's i have are intact before dd.

Lack of sudo was 1 thing that made me think that there's something wrong with install medium. Problems with /e/i.d/netfilter-persistent and stubby another.
I also find "Ubuntu-style-sudo or no sudo at all"-attitude bit childish. Or i'm just not that much into Manowar

Let's see how it goes this time.
It is not first time that i use Devuan/Debian netinst cd/dvd or expert mode. But it seems that i have been installing too much into easy hardware.

Oh yes, i found the lack of sudo weird, that's why i mentioned it. I thought that it would come with netinst, but after the installation i got complaints about that command. Didn't find /etc/sudoers either. So maybe the netinst disk was scratched or the stick was faulty or something completely different.

And netfilter-persistent not doing what it was supposed to, that was weird also.
I had a similar experience during 2008. Debian 4 install disk had kernel 2.6.18 which was not new enough for the hardware i had then. Had to wait until 2.6.24, if i remember correctly. That kernel co-operated with the hardware i had.

Maybe i'll try installing D again into that Fujitsu. But now it is not a good time for that.

For some reason "man crypsetup" sounds like a good idea in that situation. Or at least i don't think that gparted is the right tool. If i remember correctly there may be some options(with command cryptsetup) which have something to do with resizing.