You can name the file diagnostics.sh and place it anywhere you like. However, you can redirect the output to a file by appending > /path/to/outputfile.txt at the end of each command so you have a file which you can parse once the file has finished running. Keep in mind that any output generated, will get sent to the console (screen). System_profiler SPHardwareDataType | grep -i Identifier # Get the model of the machine in question

However, if you are getting diagnostic info, for example, you can have a script that does #!/bin/bash Now, this all depends on the they types of command and whether or not they require user intervention. You can also see here on Stack Overflow for a bit more information.Ī script is just a series of commands, so you could put it into a bash script. If the end user isn't an administrator, but you need to do something that required root access, you can use su someAdminName, which will perform the command as someAdminName (you'll need his password).When the script runs, you'll have to enter your password (and be an administrator)

If you need to do something that requires root (admin) access, you can prefix your command with sudo.

Dragging over the terminal icon will also work.

You're done! Double-click the file to run.

This will give the terminal permission to run the file. Run chmod u+x ~/Desktop/m圜mand in your terminal, where ~/Desktop/m圜mand is the path to your script. Convert it to plain text by clicking Format > Make Plain Text.

Mac terminal commands bazel conad