In the long run it more often than not is better to show them how to help themselves though. Let’s say they use Mint and want to install something they saw from ElementaryOS, so a new Flatpak repo: Of course in this moment I’d be done faster with their request for help sending them two commands to just paste, but showing them where they can add the new repo themselves and how this will make all the new apps pop up in their Software Store doesn’t just make them more independent and reassure them in trying things themselves, but will make it less likely for them to constantly ask you for help again.

And it makes more people stick with Linux, that’s always good.

Also, CLI is consistent across any distro…

This falsehood crashed so many devices and left so many beginners with error messages it isn’t even funny anymore.

By using a file?

Not to be facious, but in simply asking this question you’re already beyond the scope of the people most GUI tools are designed for (I.e. novices who either don’t need this tool often enough to learn the CLI, or don’t need the advanced features you’d get from doing so).

install tldr and then you have easier commands

> tldr dd

  dd

  Convert and copy a file.
  See also: `caligula`.
  More information: https://www.gnu.org/software/coreutils/manual/html_node/dd-invocation.html.

  - Make a bootable USB drive from an isohybrid file (such as archlinux-xxx.iso) and show the progress:
    sudo dd if=path/to/file.iso of=/dev/usb_drive status=progress

  - Clone a drive to another drive with 4 MiB block size and flush writes before the command terminates:
    sudo dd bs=4M conv=fsync if=/dev/source_drive of=/dev/dest_drive

  - Generate a file with a specific number of random bytes by using kernel random driver:
    dd bs=100 count=1 if=/dev/urandom of=path/to/random_file

  - Benchmark the write performance of a disk:
    dd bs=1M count=1024 if=/dev/zero of=path/to/file_1GB

  - Create a system backup, save it into an IMG file (can be restored later by swapping if and of), and show the progress:
    sudo dd if=/dev/drive_device of=path/to/file.img status=progress

  - Check the progress of an ongoing dd operation (run this command from another shell):
    progress

Try:

man dd

It’s not even that complex, it just looks that way if you’re not used to using it

I know what you mean, just beware: in lots of cases it’s not as universal (as in distro-independent) as some still think it is.

For people who want to get things done with their PC that isn’t inherently IT-related (like, doing office work or music production or anything else) and just need to do the occasional light sysadmin thing like setting up new drives to be auto-mounted somewhere, pointing to GUI tools is just so much better. And in many cases it is also safer (making your system fail on boot with a small typo in the fstab is painfully easy).

Also, GUI changes faster than CLI, CLI has ALWAYS more options, and you can save those commands to a file.

Also can get explanations for every command.

Or pipe GUI output into another GUI function.

Or >> log.txt

So you want newbies blindly entering scripts to there command line and not knowing what that are doing.

basic_task_list = ['copy and paste', 'install package', 'type', 'keyboard', 'read and write' ]

for basic_task in basic_task_list:
    print(f"""
        Newbies can't {basic_task}.
        They never {basic_task} in windows.
        Windows  has replaced {basic_task} with copilot, this is what linux needs to do to compete.

        How will linux ever hope to attract windows user if it still maintains this ancient hacker 1337xor tools like  {basic_task}?

        Users just want to turn on computer and watch it do computance - how does linux not get this?
    """)

Yep, this is just one factor. It’s difficult for people not to judge a book by its cover.

Correctly done, cli is superior for a lot of things.

You forgot to start with shutdown /g

Hope that helps.

I think we should just add a button on the desktop that runs both of those.

We’ll call it… “New All”?

no chkdsk?

I cant think of a time that sfc scannow or dsim cleanup has ever fixed a problem