Setup command in linux

What is the command to run System Settings from a terminal?

System Settings can be run from the launcher (pinned by default), the Dash, or the power cog. But what command would I enter in a terminal window if I want to run it from there?

9 Answers 9

Note: for versions between 14.04 and 17.04 (when Unity was used instead of GNOME), the command is unity-control-center .

You can still install the unity-control-center on newer versions (17.10+) if you don’t like the newer gnome-control-center

if you run gnome-control-center and get command not found , you can install it with:

sudo apt install gnome-control-center 

14.04 and greater may use the command unity-control-center instead, which was forked from it. There’s no need to install gnome-control-center as well.

Thanks a lot. Sometimes I cannot find the settings icon anywhere in GNOME, perhaps for my own mistakes. With this command, I got it back.

For Ubuntu Mate the command is mate-control-center .

I found a different solution.

1. I tried removing/installing gnome-control-center ; this did reinstall the application I still couldn’t open it.
2. Later I found that it would start up on the side of the screen and I couldn’t access it
3. I changed the display mode to single display and it came back. Hope it helps.

In Crouton, you must run anything that would require a password from the terminal, such as update manager, software center, synaptic, etc. So, to get to system settings you would enter in the terminal:

That will bring up the system settings GUI.

To check for updates, or if the update manager appears in the Unity Launcher, run it from the terminal, not by clicking on it:

The same applies to synaptic, the software center, etc. Anything which requires a password, must be run from the terminal in Crouton with a sudo .

AFAIK GNOME Control Center does not need sudo permissions to run. Also, using sudo to run GUI apps is potentially a bad idea.

Yeah well I ran it without sudo and only three of the setting icons showed up. I ran it with sudo and all the setting icons showed up. What does that tell you?!

Well, in KDE NEON 5.16.4 (Ubuntu 18.04), it is written in the «System Settings Handbook»:

• By selecting Settings → System Settings from the Application Menu.
• By pressing Alt + F2 or Alt + Space . This will bring up the KRunner dialog. Type systemsettings5 , and press Enter .
• Type systemsettings5 & at any command prompt. All three of these methods are equivalent, and produce the same result.

In my case, I needed to configure my HP LaserJet settings. Doing this as user, after applying and saving, they were ignored. So I think I had to do this as root and the settings are stored normaly now, so, each time the user opens the print dialog, the system remembers that I want log side binding and 1200 resolution :=)

I thought that sudo systemsettings5 & was enough, but as Zanna suggests: It should also be recommended to use ‘sudo -H’ if opening a GUI app with sudo.

Источник

Linux set Command & How to Use it

The set command is a built-in Linux shell command that displays and sets the names and values of shell and Linux environment variables. On Unix-like operating systems, the set command functions within the Bourne shell ( sh ), C shell ( csh ), and Korn shell ( ksh ).

In this tutorial, you will learn what the set command is and how to use it.

Linux set Command Syntax

The general syntax for the set command is:

In the context of the set command, [options] are settings or flags that are set or unset in the Bash shell environment. Use it to influence the behavior of defined shell scripts and help execute the desired tasks.

• Set an option by using a minus sign ( — ) followed by the appropriate option.
• Unset an option by using a plus sign ( + ) followed by the appropriate option.

[arguments] are positional parameters and they are assigned in order with the following parameters:

Not specifying any options or arguments causes the command to print all shell variables.

Exit Values

The set command has three exit values:

• 0 . Marks a successful completion.
• 1 . Failure caused by an invalid argument.
• 2 . Failure resulting in a usage message, usually because an argument is missing.

Linux set Command Options

The set command provides an extensive list of options that can be combined.

Most options have a corresponding -o flag that can be used to invoke the option. The table below lists all options and their respective alternative form using the -o flag syntax.

Options	-o flags	Description
-a	-o allexport	Marks all created or modified variables or functions for export.
-b	-o notify	Alerts the user upon background job termination.
-e	-o errexit	Instructs a shell to exit if a command fails, i.e., if it outputs a non-zero exit status.
-f	-o noglob	Disables filename generation (globbing).
-h	-o hashall	Locates and saves function commands when a function is defined. The -h option is enabled by default.
-k	-o keyword	Places all assignment arguments in the environment for a command, not just those preceding the command name.
-n	-o noexec	Reads commands but doesn’t execute them.
-m	-o monitor	Displays a message when a task completes.
-p	-o privileged	Disables the $ENV file processing and shell functions importing. The -p option is enabled by default when the real and effective user IDs don’t match. Turning it off sets the effective uid and gid to the real uid and gid.
-t	-o onecmd	Reads one command and then exits.
-u	-o nounset	Treats unset or undefined variables as an error when substituting (during parameter expansion). Does not apply to special parameters such as wildcard * or @ .
-v	-o verbose	Prints out shell input lines while reading them.
-x	-o xtrace	Prints out command arguments during execution.
-B	-o braceexpand	Performs shell brace expansion.
-C	-o noclobber	Prevents overwriting existing regular files by output redirection. By default, Bash allows redirected output to overwrite existing files.
-E	-o errtrace	Causes shell functions to inherit the ERR trap.
-H	-o histexpand	Enables style history substitution. The option is on by default when the shell is interactive.
-P	-o physical	Prevents symbolic link following when executing commands.
-T	-o functrace	Causes shell functions to inherit the DEBUG trap.
—	n/a	Assigns the remaining arguments to the positional parameters. If there are no remaining arguments, unsets the positional parameters.
—	n/a	Assigns any remaining arguments to the positional parameters. Turns off the -x and -v options.
n/a	-o emacs	Uses and emacs-style line editing interface.
n/a	-o history	Enables command history.
n/a	-o ignoreeof	The shell doesn’t quit upon reading the end of file.
n/a	-o interactive-comments	Allows comments in interactive commands.
n/a	-o nolog	Does not record function definitions in the history file.
n/a	-o pipefail	The return value of a pipeline is the status of the last command that had a non-zero status upon exit. If no command had a non-zero status upon exit, the value is zero.
n/a	-o posix	Causes Bash to match the standard when the default operation differs from the Posix standard.
n/a	-o vi	Uses a line editing interface similar to vi .

Linux set Command Examples

This section lists examples of the most common uses of the set command.

Using the set Command Without Options

Running the command without options or arguments outputs a list of all settings — the names and values of all shell variables and functions. Since the list is very long, you can scroll through it using the Page Up and Page Down keys.

Following is an example of a partial set command output:

Script Debugging

The set command is especially handy when you are trying to debug your scripts. Use the -x option with the set command to see which command in your script is being executed after the result, allowing you to determine each command’s result.

The following example demonstrates how to debug scripts with set -x . Follow the steps below:

1. Run set -x :

2. Use your favorite text editor (we use the vi editor) to create a script. We created a simple loop that allows us to see the -x option effects:

x=10 while [ $x -gt 0 ]; do x=$[ $x-1 ] echo $x sleep 2 done

3. Make sure to chmod the script to make it executable. This step is always mandatory before running a script. The syntax is:

4. Execute the script. The syntax is:

The output prints one line at a time, runs it, shows the result if there is one, and moves on to the next line.

Another way to enable debugging is to place the -x flag on the shebang line of the script:

Script Exporting

Automatically export any variable or function created using the -a option. Exporting variables or functions allows other subshells and scripts to use them.

Enable script exporting by running the following command:

The following example shows how script exporting works. Follow the steps below:

1. Create a new script using your editor of choice. For example:

one=1 two=2 three=3 four=4 /bin/bash

The /bin/bash argument marks the start of a new shell.

2. Check if the script works in a new shell:

The output proves that the function we created was exported and works even when starting a new shell.

Exit When a Command Fails

Use the -e option to instruct a script to exit if it encounters an error during execution. Stopping a partially functional script helps prevent issues or incorrect results.

Create a script with the following contents to test this option:

#!/bin/bash set -e cat nonexistingfile echo "The end" 

In the example above, the script encounters an error when trying to show the contents of nonexistingfile because that file doesn’t exist, causing it to exit at that point. Thus, the final echo command isn’t executed.

Note: You can use the cat command to show a file’s contents in a terminal window.

Prevent Data Loss

The default Bash setting is to overwrite existing files. However, using the -C option configures Bash not to overwrite an existing file when output redirection using > , >& , or <> is redirected to that file.

Bash first allows us to overwrite the listing.txt file. However, after running the set -C command, Bash outputs a message stating that it cannot overwrite an existing file.

Report Non-Existent Variables

The default setting in Bash is to ignore non-existent variables and work with existing ones. Using the -u option prevents Bash from ignoring variables that don’t exist and makes it report the issue.

For example, the following script doesn’t contain the set -u command and Bash ignores that $var2 isn’t defined.

#!/bin/bash var1="123" echo $var1 $var2 

The output contains only $var1 .

However, changing the script and adding the set -u command prevents Bash from ignoring the problem and reports it:

#!/bin/bash set -u var1="123" echo $var1 $var2 

Set Positional Parameters

The set command can also assign values to positional parameters. A positional parameter is a shell variable whose value is referenced using the following syntax:

The [N] value is a digit that denotes the position of the parameter. For example, $1 is the first positional parameter, $2 is the second parameter, etc.

Running the command above sets first to correspond to the $1 positional parameter, second to $2 , and third to $3 . Check this with the echo command:

Unset positional parameters by running:

Split Strings

Use the set command to split strings based on spaces into separate variables. For example, split the strings in a variable called myvar , which says «This is a test».

myvar="This is a test" set -- $myvar echo $1 echo $2 echo $3 echo $4 

Use this option to extract and filter out information from the output of a command, similar to what the awk command does.

Set allexport and notify Flags

The -o allexport flag allows you to automatically export all subsequently defined variables, while the -o notify flag instructs the shell to print job completion messages right away.

In the following example, we see that the shell notifies you upon background job completion since the script was exported:

Note: If you want to run a process in the background, add the ampersand ( & ) symbol at the end of the command.

You now know what the set command is and how you can use it in Linux. Test out the different options to better understand the command and maximize your control of the Linux environment used by different packages.

If Bash is an interesting topic for you, check out our comprehensive tutorial on Bash Functions: How to Use Them.

Источник