Command Line vs. GUI on Linux
-
@boomzilla I have noticed that The Babylon Bee really has it in for Calvinists.
-
@jaloopa said in Command Line vs. GUI on Linux:
Is that the one that uses
ifandoffor source and destination?Yes.
Horrible tool. Writing something custom from scratch in whatever programming language has got to be more accessible to the average user than that. But it's one of the few things you've got when you're trying to fix why the system isn't mounting your disks right and consequently isn't loading the GUI or the network driver userland…
-
@dkf said in Command Line vs. GUI on Linux:
@pie_flavor I still think that
ddis about the worst, as it has a thoroughly weird syntax in the first place, options that look extremely similar to each other, and is used in places where getting anything wrong will destroy the contents of your hard disk irreparably. It's true “put anechoin front of it first to make sure you don't fire it off before you're 100% sure it says what it should” territory.There's a reason it's sometimes nicknamed Disk Destroyer.
-
@pleegwat That's a feature. It prevents use of the command, which is generally the correct day to day usage of
dd.
-
I have no fucking clue what happened, but in theory a command-line interface might have had more to say...
-
@Tsaukpaetra said in Command Line vs. GUI on Linux:
I have no fucking clue what happened, but in theory a command-line interface might have had more to say...
I'd bet it did, but the GUI did not understand what it was saying.
-
@Tsaukpaetra said in Command Line vs. GUI on Linux:
I have no fucking clue what happened, but in theory a command-line interface might have had more to say...
Looks like a charset issue. HTH!!!
-
@Gribnit said in Command Line vs. GUI on Linux:
Looks like a charset issue. HTH!!!
I ??? your judgement.
-
@Applied-Mediocrity said in Command Line vs. GUI on Linux:
@Gribnit said in Command Line vs. GUI on Linux:
Looks like a charset issue. HTH!!!
I ??? your judgement.
It's not a judgement.
