Me Too!!! Would like to know ralph's definition of "interesting discussion", that is.
Thorium reactors+proliferation? Connection between arrythmia and coagulation? South american black metal? Something completrely different from those?

Actually i agree with ralph: there is not much interesting discussion here, Should find another forum or quit using web_based_messageboards for anything at all,

Other thing: context.
In topics which have at most 10-20 messages, quoting may not be so necessary/it could be practical to deduce if message #y if a reply to message #x.

But when there are hundreds of messages in a topic, and they are separated in pages, context could be lost.

And that "context loss" made me think about a) slashdot b) some news clients i have used decades ago.
Particularly, that in these examples messages are ordered into a tree-line structure. When using that structure, context is more clear. Not so much need for over-quoting.

E.
Not going to say anything about the content quality of those examples. I think someone will do it for me instead.

Maybe i agree that quoting the whole message is too much. But making quoting complicated may result a bad irc-clone insted of a messageboqard. And some other crap also.

Maybe it's not about web-based forums or death of Usenet.
Manners have become nonexistent instead. (Maybe i'm not completely immune to that but anyways.)

Somehow i doubt that yeti was even born when i used Usenet news first time.

But anyways, this lack of proper quoting is not that good either. When messages are ordered only by the time they are added, it can become difficult to deduce if this_message is a reply to that_message or not. Now there is just chaos of non-connected messages.
This is not a messageboard, it is a bad IRC-clone instead.

(And if someone is too lazy to use real quote properly, that someone is propably too lazy to use quote-tags the way moderators intended, also.)

And if someone thinks that in this forum there were too much quoting, you definitely haven't seen the forums i have seen.

To deepforest: look at the link about dd's man page or say in terminal:

man dd

. The most essential parameters are "if=/dev/source" and "of=/dev/target".

Although, if you're not familiar with dd, i strongly recommend experimenting inside a vm first before using "dd" in bare metal.

Dd'ing to smaller partition will result in a damaged target partition and some complaints from dd when target runs out of space. So, not recommended.

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.

Found a cheap desktop and bought it. So , propably nothing is going to happen in this topic after this message.

E.

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.

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...

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.)

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.

https://www.youtube.com/watch?v=TTNeAwFRRN4 What If Death Wrote BLACKENED by Metallica

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.