Only handle the simple cases. When they don't tell you exactly what they are going to do, well then they are useless because you can't trust them. Gonna touch the gpt ? Gonna create a hybrid mbr? Gonna force me to use CSM? Gonna *touch* any other partition than what I tell you??? hard pass.
And the answer is that both of the comments are wrong. Of course you can read what they are about to do. But of course that is not what OP meant. You want to see it while doing it. Like *proper* logs. Not have tenthousand lines in some verbose yet write-only language on the side.
By the way: Can we ban any program that doesn't do *proper* logging, up to debug log levels, from being on Linux or being called anything related to Linux? (Ditto for things that don's use
GUI installers (Score:-1)
Only handle the simple cases.
When they don't tell you exactly what they are going to do, well then they are useless because you can't trust them.
Gonna touch the gpt ? Gonna create a hybrid mbr? Gonna force me to use CSM? Gonna *touch* any other partition than what I tell you???
hard pass.
Re:GUI installers (Score:1, Flamebait)
When they don't tell you exactly what they are going to do, well then they are useless because you can't trust them.
But they're open source ! Can't you just read the source and know what they are doing ?
Re: GUI installers (Score:2)
Why is this Flamebait? It is a correct point.
And the answer is that both of the comments are wrong. Of course you can read what they are about to do. But of course that is not what OP meant. You want to see it while doing it. Like *proper* logs. Not have tenthousand lines in some verbose yet write-only language on the side.
By the way: Can we ban any program that doesn't do *proper* logging, up to debug log levels, from being on Linux or being called anything related to Linux?
(Ditto for things that don's use
Re: (Score:2)
I assume real Arch users don't use grub, and type their boot commands directly into the bootloader.