Basic Linux Installation Guide - Revision history

Lynn: /* Fix sudo to not prompt for password */

2026-08-25T19:51:30Z

Fix sudo to not prompt for password

← Older revision		Revision as of 19:51, 25 August 2026
Line 127:		Line 127:
	<syntaxhighlight lang="shell">		<syntaxhighlight lang="shell">
	echo "${USER} ALL=(ALL) NOPASSWD:ALL">${USER};chmod 400 ${USER};sudo chown 0:0 ${USER}		echo "${USER} ALL=(ALL) NOPASSWD:ALL">${USER};chmod 400 ${USER};sudo chown 0:0 ${USER}
	~~</syntaxhighlight>~~
	~~<syntaxhighlight lang="shell">~~
	sudo mv ${USER} /etc/sudoers.d/${USER}		sudo mv ${USER} /etc/sudoers.d/${USER}
	</syntaxhighlight>		</syntaxhighlight>

Lynn: /* On Ubuntu continue configuring the system from an ssh terminal session */

2026-08-25T19:50:34Z

On Ubuntu continue configuring the system from an ssh terminal session

← Older revision		Revision as of 19:50, 25 August 2026
Line 99:		Line 99:

	==On Ubuntu continue configuring the system from an ssh terminal session==		==On Ubuntu continue configuring the system from an ssh terminal session==
	{{note \| With Kubuntu, skip this section}}		{{note \| With Kubuntu and Zorin skip this section}}
	===Install Putty===		===Install Putty===
	Click on the Application Launcher. Search for the putty app. Click on the selection to connect to ssh servers. Click on install in the installation popup. Once installed, just click on launch. Enter localhost as the Host Name. Accept on the Security Alert popup.		Click on the Application Launcher. Search for the putty app. Click on the selection to connect to ssh servers. Click on install in the installation popup. Once installed, just click on launch. Enter localhost as the Host Name. Accept on the Security Alert popup.

Lynn: /* Install and Configure sshd */

2026-08-25T19:46:33Z

Install and Configure sshd

← Older revision		Revision as of 19:46, 25 August 2026
Line 90:		Line 90:

	==Install and Configure sshd==		==Install and Configure sshd==
	~~{{note \| With Kubuntu user the local Konsole window as ssh is quite broken. The ssh server is still needed}}~~
	The sshd server needs to be running so that you can login. This is required in order to cut and paste. This means that you need to type the commands manually.		The sshd server needs to be running so that you can login. This is required in order to cut and paste. This means that you need to type the commands manually.
	<syntaxhighlight lang="shell" line>		<syntaxhighlight lang="shell" line>
Line 97:		Line 96:
	</syntaxhighlight>		</syntaxhighlight>
	Input your password if prompted.		Input your password if prompted.
	{{note \| ~~With~~ Kubuntu ~~use the local Konsole window since ssh is quite broken~~}}		{{note \| Kubuntu has problems with cut and paste in terminal windows}}

	==On Ubuntu continue configuring the system from an ssh terminal session==		==On Ubuntu continue configuring the system from an ssh terminal session==

Lynn: /* Install and Configure sshd (Minimal Install only) */

2026-08-25T19:42:23Z

Install and Configure sshd (Minimal Install only)

← Older revision		Revision as of 19:42, 25 August 2026
Line 89:		Line 89:
	{{todo \| Add the connection information to the Start.me section for connections}}		{{todo \| Add the connection information to the Start.me section for connections}}

	==Install and Configure sshd ~~(Minimal Install only)~~==		==Install and Configure sshd==
	{{note \| With Kubuntu user the local Konsole window as ssh is quite broken. The ssh server is still needed}}		{{note \| With Kubuntu user the local Konsole window as ssh is quite broken. The ssh server is still needed}}
	The sshd server needs to be running so that you can login. This is required in order to cut and paste. This means that you need to type the commands manually.		The sshd server needs to be running so that you can login. This is required in order to cut and paste. This means that you need to type the commands manually.

Lynn: /* Install and Open Cockpit */

2026-08-25T19:38:44Z

Install and Open Cockpit

← Older revision		Revision as of 19:38, 25 August 2026
Line 81:		Line 81:
	http://<ip address>:9090 or http://localhost:9090		http://<ip address>:9090 or http://localhost:9090
	</syntaxhighlight>		</syntaxhighlight>
	Login with the user created on the install. After logging in, do a quick check, switch to administrative access and then open the terminal window. ~~Change~~ the ~~network connection information~~ and verify that the DNS server is set to 192.168.86.2		Login with the user created on the install. After logging in, do a quick check, switch to administrative access and then open the terminal window. Assign a fixed IP address. By convention, the main servers are below 30. The thirties are VMs. The fifties are the Raspbery Pi systems. The seventies are physical workstations.

			Disable IPv6 and verify that the DNS server is set to 192.168.86.2
	====See Also====		====See Also====
	[https://www.linode.com/docs/ Cockpit Reference]		[https://www.linode.com/docs/ Cockpit Reference]

Lynn: /* Install and Open Cockpit */

2026-08-25T19:01:51Z

Install and Open Cockpit

← Older revision		Revision as of 19:01, 25 August 2026
Line 78:		Line 78:
	</syntaxhighlight>		</syntaxhighlight>
	Open URL from a web browser:		Open URL from a web browser:
	<syntaxhighlight ~~lang="shell"~~>		<syntaxhighlight>
	~~https~~://<ip address>:9090		http://<ip address>:9090 or http://localhost:9090
	</syntaxhighlight>		</syntaxhighlight>
	Login with the user created on the install. After logging in, do a quick check, switch to administrative access and then open the terminal window. Change the network connection information and verify that the DNS server is set to 192.168.86.2		Login with the user created on the install. After logging in, do a quick check, switch to administrative access and then open the terminal window. Change the network connection information and verify that the DNS server is set to 192.168.86.2

Lynn: /* Or Create a VM from the Proxmox Console */

2026-08-25T18:59:02Z

Or Create a VM from the Proxmox Console

← Older revision		Revision as of 18:59, 25 August 2026
Line 17:		Line 17:

	==Or Create a VM from the Proxmox Console==		==Or Create a VM from the Proxmox Console==
			If you are not creating a VM skip on down.
	===Connect to PVE and verify distro===		===Connect to PVE and verify distro===
	Open the Proxmox GUI: [http://pve.lan:8006 http://pve.lan:8006]		Open the Proxmox GUI: [http://pve.lan:8006 http://pve.lan:8006]

Lynn: /* Before We Begin */

2026-08-25T18:57:52Z

Before We Begin

← Older revision		Revision as of 18:57, 25 August 2026
Line 2:		Line 2:
	There are lots of Unix distributions that are available. The all start with the same basic parts and then create distributions that tend to focus on a particular audience. Some are seriously minimal others are more comprehensive. The first separation is Redhat vs Debian variants. Pick one. They each have a specific way of doing things. This is more important when administering rather than just using. The examples below are all Debian based. Next is the desktop. This obviously doesn't matter if the system is a server version. The two big ones are KDE and Gnome. I tend to prefer KDE but can easily use either.		There are lots of Unix distributions that are available. The all start with the same basic parts and then create distributions that tend to focus on a particular audience. Some are seriously minimal others are more comprehensive. The first separation is Redhat vs Debian variants. Pick one. They each have a specific way of doing things. This is more important when administering rather than just using. The examples below are all Debian based. Next is the desktop. This obviously doesn't matter if the system is a server version. The two big ones are KDE and Gnome. I tend to prefer KDE but can easily use either.

	My current choices are Ubuntu for the VMs and Kubuntu or Zorin the physical one.~~=s.~~		My current choices are Ubuntu for the VMs and Kubuntu or Zorin the physical one.

	=Installing Linux systems=		=Installing Linux systems=
	The installation process for both the desktop physical machines and Linux VMs is pretty straight forward. The idea is to get a vanilla basic installation that can be built on to. The process is similar doing it on a physical machine as it is on a VM.		The installation process for both the desktop physical machines and Linux VMs is pretty straight forward. The idea is to get a vanilla basic installation that can be built on to. The process is similar doing it on a physical machine as it is on a VM.

Lynn: /* Installing Linux systems */

2026-08-25T18:57:34Z

Installing Linux systems

← Older revision		Revision as of 18:57, 25 August 2026
Line 1:		Line 1:
			=Before We Begin=
			There are lots of Unix distributions that are available. The all start with the same basic parts and then create distributions that tend to focus on a particular audience. Some are seriously minimal others are more comprehensive. The first separation is Redhat vs Debian variants. Pick one. They each have a specific way of doing things. This is more important when administering rather than just using. The examples below are all Debian based. Next is the desktop. This obviously doesn't matter if the system is a server version. The two big ones are KDE and Gnome. I tend to prefer KDE but can easily use either.

			My current choices are Ubuntu for the VMs and Kubuntu or Zorin the physical one.=s.
	=Installing Linux systems=		=Installing Linux systems=
	The installation process for both the desktop physical machines and Linux VMs is pretty straight forward. The idea is to get a vanilla basic installation that can be built on to. The process is similar doing it on a physical machine as it is on a VM. ~~There~~		The installation process for both the desktop physical machines and Linux VMs is pretty straight forward. The idea is to get a vanilla basic installation that can be built on to. The process is similar doing it on a physical machine as it is on a VM.
	==Setup a Bootable USB key==		==Setup a Bootable USB key==
	If you are installing on a VM, skip on down.		If you are installing on a VM, skip on down.

Lynn: /* First Things First */

2026-08-25T18:43:10Z

First Things First

← Older revision		Revision as of 18:43, 25 August 2026
Line 55:		Line 55:

	=After Installation Actions=		=After Installation Actions=
	~~==First Things First==~~
	===Get the System Up To Date===		===Get the System Up To Date===
	In spite of selecting to install updates during the main installation, the non-OS packages don't get this treatment in the full install. Regardless, this step is a good idea.		In spite of selecting to install updates during the main installation, the non-OS packages don't get this treatment in the full install. Regardless, this step is a good idea.