You are not logged in.
After reading first few messages of this topic, i was going to suggest "tar -cp" and "tar -xp".
But maybe unmounting and dd'ing the underlying partition from source to destination would be better.
Although those commands are dangerous with wrong parameters, especially when ran as root. But same can be said about cp and rsync also.
E.
'
https://linux.die.net/man/1/tar
https://linux.die.net/man/1/dd
Not 100% sure about those acl's, attributes or capabilities while using tar's "-p" - option. But owners and access rights should go into archive and out of it.
(Once or tiwce managed to screw up my OS with those options.)
And then there are some fs-specific things with dd. Ext-family of filesystems better be unmounted while doing dd.
And with xfs there may be some problems when there are 2 filesystems with exactly same identifiers.
Other than that, i like to think that dd should be thorough enough even if tar's -p isn't.
For beginners, maybe Clonezilla would be a good idea. Haven't tried it myself though.
https://www.youtube.com/watch?v=ggK2sV8 … p=iAQB8AUB Black Sabbath - Ancient Warrior
Found a cheap desktop and bought it. So , propably nothing is going to happen in this topic after this message.
E.
How should i configure the UEFI/BIOS before installation for example?
I think i have figured those out by now.
And also, no special options to boot prompt are necessary except maybe keyboard settings when using desktop live image.
But maybe that one is not meant for installing.
It is also a good idea to throw those memory cards and sticks into garbage bin and use optical discs and drives instead.
E2. that shop offered to diagnose that Fujitsu for a reasonable amount of money. But it is unclear how much resources it would take to actually fix it. Or is it possible to fix. So the path of least action seemed to be to buy a another machine.
I also find it annoying, with UEFI_as_firmware_machines, that "boot from ssd immediately"-thing. Many times i had to keep F-buttons down in the keyboard while pushing powerbutton. That seems to be a reliable way to get that configuration- or boot-menu.
Why on earth shim has to answer to http requests?
I thought that shim is supposed to be just a bootloader.
O tempora o mores...
I rarely even log into X as root. I think about 1-2 years ago i had to, after screwing up with slim somehow.
But anyways. I have browsed grub's documentation, it seems that it can verfify signatures. So it should be possible tp sign the whole kernel and initrd. So no need to use openssl to sign every module that goes into initrd.
And if /boot-partition doesn't change too often, it may be practical to calculate hash of the whole partition and store it somewhere. To check just before giving control from firmware to bootloader. And warning user if content has changed.
Unattended access could be bigger problem with laptops than with desktops, i thjink.
Maybe {Core/LIbre}boot could be run inaide a vm? Would like to find out how that software works in practice.
Looks like i don't have a right kind of cable. So cannot test if Fujitsu's display is faulty or not.
On the other hand, the display was fine right before i mis-configured that firmware.
Edit. As you may already know, F2 after powerbutton should result a box where you could enter the firmware's admin passwd. After entering the right passwd there should be that configuration menu.
And F12 after powerbutton should give the boot menu, after entering the right hdd passwd.
But there's only a dark gray screen, barely noticeble difference from from completely black screen.
Don't have a support contract with Fujitsu so i should go through that shop. But they couldn't say how much time and money it would take to fix that machine.
(Or if it is possible to fix or not.)
https://www.youtube.com/watch?v=oGED_XorcRY a.k.a
FAUN - Ylfa Spere (Official Video)
It would be useful to be able to check if 1st MB of primary HDD/SDD or an entire /boot -partition have been suffering a bitrot or a malware infection.
Maybe with Coreboot i can do that?
Some BIOSes have a similar feature but i haven't yet confirmed if that works or not. Those old machines succumb to Alzheimer too quickly.
And i've been having some UEFI-related problems too, so haven't had the time or energy to find out what UEFI's can and cannot do, regarding to that "HDD/SDD-protection".
I guess with elder hardware, i'm more likely to run into bitrot. Not in the customs of clicking a wrong link in email while logged in as root.
That forum link seemed intresting.
The shop i bought Fujitsu from, told me to first try "push power button for x second"-trick which i already know from BIOS-machines.
The hopes were, that the settings which told to read from ssd before doing anything else, would go away. And maybe also those settings that say that the primary ssd is disabled.
That trick haven't worked. yet
Right after pushing powerbutton, F2 results in a beep and the screen goes from black ro dark gray. So the machine has noticed that i have pushed a key bot nothing else happens after that.
And F12 right after powerbutton results to a beep and dark gray screen also.
The next step would be to send that machine back to that shop. And it would take yet-to.-be-determined amount of money and time.
I'm between sixes and sevens, should i sent that machine back or not.
On the other hand, that old laptop will cease to work some day.
https://www.youtube.com/watch?v=TTNeAwFRRN4 What If Death Wrote BLACKENED by Metallica
I have tried many times, to get into the Fujitsu's UEFI configuration menu, to no avail. So i cannot reset to factory defaults.
It was a Big Mistake to disable the primary ssd. And also forgetting to do domething about those remains of previous install in that boot menu, that was a BIg Mistake too.
Found out the Hard Way that is not a proper way to enforce booting from optical disk.
It doesn't matter if that ssd is connected or not.
Now Lord Anubis is in need for a new host.
Now i think i have done 2 mistakes, if i want to boot from optical while no ssd connected.
FIrst was setting the ssd passwd. (Sometimes i wonder is that passwd about authentication, like in /etc/shadow, or about encryption like in cryptsetup ? )
Second was not removing those remains of previous installs from boot menu.
And then there were the 3rd mistake. Not quite sure if i can get to configuration_menu or boot_menu after that.
It would be easy if i could just make that machine somehow forget that it is supposed to access ssd before booting from optical.
But the first attempts at that have not been successful.
Set a main passwd for the firmware.
Set passwd for ssd, disabled asking it later.
Enabled tpm, disabled secureboot.
Enabled booting for removable drives.
Enabled boot menu also.
Enabled that boot menu for all users, not just for admin.
And noticed that cannot boot from usb-dvd-drive if that ssd is disconnected.
It may have been a mistake to set that disk passwd. I suspect it to be the cause that firmware needs ssd before booting from optical.
In boot order optical is before ssd, but not the absolutely first, i think. Have to confirm if i get a chance.
E. Firmware version is 1.28 . The date of it is from december of 2022, i think. Suspect that date is when the firmware was updated, not the date when fujitsu published it.
https://www.youtube.com/watch?v=HmgSBUPA0UA&t=1723s
I get a slight Opeth-vibe from this song.
UFW (Uncomplicated Firewall)
If you have rules you're happy with, there's also netfilter-persistent and iptables-persistent.
sudo disease
I don't think sudo in itself is a disease. But that "ALL=ALL NOPASSWD"-thing definitely is.
I like to think that the usb-dvd-drive was before ssd in booting order. But i'm not 100% sure about that.
Tried heads once, 4 years ago. For some reason the dvd i burned didn't boot. Would like to try again some day with more recent .iso .
Science is the art of deception.
I thought that was war.
I haven't been troubled with rubber-feets of laptops.
But hardware support is always a problem with linux. Even with desktops.
Ok, usually you can get your graphics card working, kind of. But then you'll be stuck with the distro's kernel. No compiling the latest from kernel.org if you want those blobs working.
And then there's the new firmware that replaced BIOS. Recently noticed that i cannot boot from dvd if ssd is removed. What will i do if that ssd breaks?
With old hardware i could boot from dvd even after removing the hdd. But not necessarily with new machines.
I find that annoying.
ttps://en.wikipedia.org/wiki/Barrett_M82
It won’t work, the FPV drone will attack from above. This is right today, right now...
I think Barret is capable of shooting down drones, at least with explosive or armor-piercing round.
If not, there's always https://en.wikipedia.org/wiki/ZU-23-2 a.k.a "Sergei". And https://en.wikipedia.org/wiki/Rheinmeta … ennium_Gun .
Very much off-topic, i know.
This mis-adventure continues.
Today i noticed: https://wiki.archlinux.org/title/intel_ … stallation .
These sounded familiar: "There have been couple reports where the whole graphics stack hard freezes" , "not even switching to a different virtual console work" .
And I think there's intel graphic chip in that machine.
But it will take a while to get a chance to try SysRq.
Last night i started the reinstall process. Erased the ssd with dd as a first step, to start with a "clean slate".
Should find out if there is xterm installed outside of vm.
There is xterm installed on that host. So lack of xterm won't explain anything.
But on the other hand: https://duckduckgo.com/?t=ftsa&q=xsessi … ion&ia=web .
May be related or may be not. I get that xsession-complaint when logging in to xfce from lightdm.
But i think today's agenda is to find out what happens if i try to remove package elogind from those 2 vm's i mentioned before.
It would be nice if i could reproduce the freezing inside a vm , so that i could use ssh to find out what went wrong. But won't hold my breath.
There's that full backup of course, but USB ceased to work with vm's . So i need a file server and also the vm's to behave themselves.
EDit. elogind doesn't seem to be too vital package. But on the other hand, purging libelogin* - packages will try to remove xorg-related packages amongst others. So those libraries have to be left installed for now.
And if i purge dbus* - packages, the "openbox-vm" will kind of work still. But no firefox nor pulseaudio.
Btw. any ideas about a desktop environment without need for polkit or policykit?
Now i have a "kind of a theory" why "freezing" happens. When trying to log out, lightdm tries to communicate with polkit but it can't and freezes. But on the other hand, then i would expect that package to go away when removing polkit-packages.
Not yet sure how that explains problems with startx. Should find out if there is xterm installed outside of vm.
And btw, couldn't reproduce the "freezing situation" inside a vm just yet. Did many things differently from 2-3 months ago, thats for sure. Should have documented better how the install went during march-april.
Edit. https://pkginfo.devuan.org/cgi-bin/pack … d=246.10-5 the "Recommends:"-part.
So changing displaymanager won't necessarily help if it is elogind that tries to access policykit-related stuff that is not available.
And elogind need dbus also.
Answering to myself: commands "dpkg -l pol*", "dpkg -l libpol*" and "apt-cache showpkg" could possibly help with finding a proper desktop environment.
In xfce there is thunar which has troubling dependencies. Also i found out that it is libreoffice that needs libcups-something.
Last year i was wondering why libcups was needed, now i got my answer finally ![]()
And of course lxde-something-packages need policykit.
Next time when trying to reinstall, maybe i'll try Deaedalus netinstall with openbox+lxdm.
And then there's always Chimaera. Or how long it is still supported?