Ed_P wrote: ↑24 Aug 2024, 22:25
jjr wrote: ↑24 Aug 2024, 17:01
Again, these types of threads wouldn't exist if Porteus had a wizard-like installer that asks the user what they want (desired firmwares, desired gpt/mbr type, desired FS layouts, optional ESP marking) and handles partitioning, file copying, and BIOS install, all-in-one.
Do you think new Linux users, and even new users from Ubuntu and other Linux system's, will know what type of firmware, gpt/mbr type, FS layouts & etc will be comfortable using such a new system start up?

I know if I was faced with this type of setup when I started using Linux I wouldn't be here.
Ed_P, I take that to mean you think it's impossible to develop friendly UIs.
Some basic principles of friendly UI design:
- Word things in a simple, plain-English way
- Use intelligent defaults
- Hide technical options behind Advanced disclosures
Example:
UEFI = "modern computers"
BIOS = "old computers"
Silent default = install for
both firmwares
If the target drive is >2 TiB, use GPT. Otherwise, use MBR.
It's not that complicated.
Partitions don't even have to be mentioned:
[x] I want a storage area for large files, readable by Windows
(that's referring to the FAT32 file size limitation)
Are you really claiming that the current paradigm of throwing an incomplete install doc at the user and expecting them to muddle through the rest on their own and/or ask for help on a forum -- is somehow
ideal?
Are you denying that a graphical wizard with friendly, tiered UX could not
possibly reduce some of the install questions/troubles on this forum?
I find it hard to believe you truly believe that
Or you just doubt that it can be done by anyone here. Either way, I find your position deeply frustrating.
Ed_P wrote: ↑24 Aug 2024, 22:25
jjr wrote: ↑24 Aug 2024, 17:01
I just don't want OP and others to be confused by inoperative instructions.
Me either and I can assure you my instructions work, I have been using them for quite awhile.
Ed_P, let me clarify.
(1)
You wrote "the USB drive won't boot when used on BIOS systems if it's not set"
This would suggest to the casual reader (
or possibly OP himself) that setting the boot flag here will enable BIOS booting.
It will not. The implied instruction was inoperative for BIOS booting.
I explained that other steps and caveats would need to be added if you wanted to cover BIOS booting, which your comment suggested.
(2)
Inoperative has a second meaning, which is "not having effect".
Setting the MBR active/boot flag has
no effect for installing on BIOS nor UEFI, because the BIOS installer already sets it, and it's meaningless for UEFI.
Adding meaningless instructions (in the case of UEFI) leads people down mental paths that lead to confusion, making harder for smart-but-not-yet-knowledgeable users to understand what they're doing.
Remember, OP is an embedded developer. That's why I entered this thread. It's because I can empathize with someone (OP) being smart but lacking some relevant knowledge, but being given recipes that don't actually provide understanding.
---
I'm being frustrated, and maybe I will regret my tone when I cool down. Or maybe you can understand where I'm coming from. I appreciate the time that you and others contribute to providing support on the forums. I do think that things could be more efficient and effective for
everyone (you, me, OP, and others like him).