Found these links:

https://dev1galaxy.org/viewtopic.php?id=4039
https://dev1galaxy.org/viewtopic.php?id=2856

maybe those will be helpful some day. Before that i would like to make lvm, sudo and some other packages work. It seems that i have to install something called libsystemd so that i can install lvm2.https://pkginfo.devuan.org/cgi-bin/pack … =2.03.22-1

Although, if i remember correctly, i'll may have to update initrd in order to enable /home on a logical volume.
I wonder if there is going to be problems with that updated initrd when shim or SB is enabled?

Today i'm not in the mood for writing an initscript to enable lvm after initrd is done.
Edit. i think i saw some lvm-related scripts under /etc/init.d inside virtual machine i made. I installed Chimaera on that vm.

Planning to figure out what mokutil can and cannot do.

It seems that i have to sign vmlinuz and initrd if i want to boot Devuan when SB is enabled.  It would be nice if i could sign more than just those. Just in case.

I have also heard about something called EFI-Stub. Can i bypass loading anything from EFI partition with that?

But one step at a time...

Either there were no /dev/dsp in my Chimaera install or "chmod o+rw /dev/dsp" as root didn't help. Not quite sure anymore which one was the case. Should document better.

Made a working /boot and /boot/EFI for Ubuntu. Also made additional partitions and installed Daedalus into one of them.
Tried to chain-boot from Ubuntu's /boot to Daedalus's /boot with:

menuentry chain {
insmod chain
set root=(hd0, part_x)
chainloader +1
}

as grub.cfg in /boot/EFI/ubuntu . Got some EFI-related complaints from GRUB. I hope i got the partition number right in "set root"-line. I mean that part_x should be the /boot of Daedalus.

Also i tried to boot straight into /boot partition of Daedalus with super grub disk. That worked.
So, chain-loading from UEFI with GRUB, is it possible or not?

Also, should there be signed .efi-files inside that Daedalus install disk? I'm starting to think that maybe using that Ubuntu-disk wasn't absolutely necessary step...

Tried to boot Fujitsu with devuan live. It worked. And after that, tried youtube. I got sounds out of my hardware. So the silence may be a problem with configuration after all.

Some day i have to re-install that Devuan. Getting tired with that "super grub disk 2 method". That disk is getting scratched and external dvd will outlive its usefulness some day.

May of last year, i had w10 install disk that was ancient enough to co-operate with D4. I may have misplaced it somewhere. So Ubuntu install disk may be needed.
There is some highly mysterious dark magic going on with that laptop and its firmware.
W10 install disk seemed to fix some of that weirdness.

I think that booting from usb stick or optical disc is not supposed to work when secureboot is active.

From the VirtialBox User Manual i found this:"Delayed writing through the host OS cache is less secure. When the guest OS writes data,
it considers the data written even though it has not yet arrived on a physical disk". That may explain the missing files and wrong content.
But i still think vbox could warn end-users about that, on the "Settings->Storage"-section.

I mean , sometimes vbox warns about wrong chipset or dislay settings. It could say something about that caching thing too...

Maybe i'll try that "hostiocache off"-thing. Hopefully usb keeps working without problems... or i have to start to use GitHub or Dropbox or something.

It seems that i can make sqlalchemy fetch some data from tables when the connectionstrings are right.
But another thing i noticed, with a new vm, docker-compose can't find the .yml-file with -f. I have to say it's absolute path, then d-c finds it.
Any ideas why? And how to fix that? I ask here, in the case this is a Devuan-specific problem. (Almost 20 years there were some kind of a RedHat-related problem with package gcc, that other distros did'nt have.)

Something may have gone wrong with thet new vm's install. Or there is some important package missing. I noticed also that in the new vm's xfce terminal, there is no colours with output of "ls".

That's not weird when using root-account. But using a normal user account...

I guess i can forget to save file when tired enough. Or save under a wrong name. But 2 or 3 weeks of commits missing from git's log? Come on.

When i shut down a vm by clicking it's window's close button i get options to a) save machine state b) send shutdown signal c) send power off. Anything but a) could undo the changes.

But I usually shut down vm by saying sudo /sbin/shutdown or sudo /sbin/halt inside tah vm. So vbox should commit changes into the virtual hd.

Has Oracle changed vbox's behaviour concerning shutting down a vm , after 6.0 ? Or is it just a bug that reveals itself in the situation where the backing fs is almost full ?

For some reason i would like to mention another non-default-thing i did with virtualbox 5.x. I tried doing dd if=/dev/usb-disk or dd of=/dev/usb-disk and managed to froze the host machine so badly that i had to turn it off by pushing powerbutton.

With vbox 6.0 that usb-situation got little better. Don't remember freezing my machine with dd after that.

I always manage to try Things That Are Forbidden.

Maybe stackexchange.com would be a better place for this topic. But i don't have account on that site.

Anyways, changed logging settings in postgres-container. I started getting "LOG connection authetticated"-messages.
Entered into running python container with docker exec, started Python interpreter and started entering commands. Those "authenticated"-messages arrived into stderr. So now i know that sqlalchemy can connect into  postgres.

But "r=conn.execute(text("SELECT * FROM table1"))", which i tried instead of "c.select().where()" is still a problem. For some reason it doesn't return any rows. I think it should.
And it is very stupid if i have to enter commands that way.   I thought that with sqlalchemy, another way of doing queries would be possible.