OpenSuse - Revision history

WikiSysop at 13:17, 2 April 2024

2024-04-02T13:17:09Z

← Older revision		Revision as of 13:17, 2 April 2024
Line 296:		Line 296:
	Use YAST to set NTP servers for your domain rather than Opensuse's defaults. New installations of Leap will use chrony rather than ntp for improved synchronization. With ntp, check the performance using "/usr/sbin/ntpq -p" or with chrony use "/usr/bin/chronyc tracking". As of July 2018, chronyc is a preferred option.		Use YAST to set NTP servers for your domain rather than Opensuse's defaults. New installations of Leap will use chrony rather than ntp for improved synchronization. With ntp, check the performance using "/usr/sbin/ntpq -p" or with chrony use "/usr/bin/chronyc tracking". As of July 2018, chronyc is a preferred option.

	On a longer term, routine updates can be done from the command line ~~with~~		On a longer term, routine updates that will change repositories as needed can be done from the command line

	zypper up		zypper dup

	Add any needed Python3 modules requiring pip, notably matplotlib (see below)		Add any needed Python3 modules requiring pip, notably matplotlib (see below)
Line 305:		Line 305:
	== Your own local binary file directory ==		== Your own local binary file directory ==

	The Unix system resource directory /usr/local with its bin, src, lib, lib64 and other subdirectories is the normal place to drop software that is not available as a package and is used system wide. There are potential conflicts with identically named code in the system that may be resolved by the PATH environment, and by rename files to be distinctive. Python installed in /usr/local/bin/ can be especially problematic because it is used for system utilities, and if the system Python is set up to run a virtual environment for an end user who has venv activated, even knowing which Python is running a code can be uncertain. The preferred solution for our systems is to let any end user install their own versions of ~~softare~~ in their personal /home/user/local directory and ~~but~~ the /home/user/local/bin/ directory in their search PATH. That works for AstroImageJ as well, which can be installed anywhere in a user's space with a softlink from /home/user/bin or from /home/user/local/bin to the executable "AstroImageJ".		The Unix system resource directory /usr/local with its bin, src, lib, lib64 and other subdirectories is the normal place to drop software that is not available as a package and is used system wide. There are potential conflicts with identically named code in the system that may be resolved by the PATH environment, and by rename files to be distinctive. Python installed in /usr/local/bin/ can be especially problematic because it is used for system utilities, and if the system Python is set up to run a virtual environment for an end user who has venv activated, even knowing which Python is running a code can be uncertain. The preferred solution for our systems is to let any end user install their own versions of software in their personal /home/user/local directory and put the /home/user/local/bin/ directory in their search PATH. That works for AstroImageJ as well, which can be installed anywhere in a user's space with a softlink from /home/user/bin or from /home/user/local/bin to the executable "AstroImageJ".

			Some distributions of software source files require fine tuning to compile and install in other than the default directories, notably astrometry.net uses

			make install INSTALL_DIR=/home/user/local/astrometry CFITS_INC="-I/home/john/local/include" CFITS_LIB="-L/home/user/local/lib64 -lcfitsio"

			for a "user" where cfitsio is also installed in that local directory.

	== Python ==		== Python ==

WikiSysop at 19:46, 15 March 2024

2024-03-15T19:46:47Z

Show changes

WikiSysop at 05:55, 21 July 2023

2023-07-21T05:55:44Z

← Older revision		Revision as of 05:55, 21 July 2023
Line 869:		Line 869:

	to implement the TigerVNC version used by the script.		to implement the TigerVNC version used by the script.

			The VNC server uses a configuration file .vnc in the user's home directory. Two typical entries are

			geometry=2000x1200
			localhost

			which set the size of the virtual terminal and make the service only available locally for security. Use SSH to tunnel to this service from the remote user

			ssh -L 5901:localhost:5901 user@remote.site

			as an example.

WikiSysop at 05:48, 21 July 2023

2023-07-21T05:48:41Z

← Older revision		Revision as of 05:48, 21 July 2023
Line 1:		Line 1:
	The observatory's servers and control computers run on the OpenSuse distribution of Linux-based software, currently Leap 15.4 . We have chosen the Leap series because of its conservative testing and stability. Generally the slowed cycle of new versions does not cause problems, except where we need software that is pushing the edge, notably AstroPy. We have been using Tumbleweed since it was introduced on selected telescopes where the most recent packages were required, usually without stability issues.		The observatory's servers and control computers run on the OpenSuse distribution of Linux-based software, currently Leap 15.5 . We have chosen the Leap series because of its conservative testing and stability. Generally the slowed cycle of new versions does not cause problems, except where we need software that is pushing the edge, notably AstroPy and Stellarium. We have been using Tumbleweed as well since it was introduced on selected telescopes where the most recent packages were required, usually without stability issues.

	These evolving installation notes originated with much earlier versions of OpenSuse and are rewritten as we gain experience with the most recent releases and work-around solutions to problems.		These evolving installation notes originated with much earlier versions of OpenSuse and are rewritten as we gain experience with the most recent releases and work-around solutions to problems.
Line 846:		Line 846:
	== Tight VNC ==		== Tight VNC ==

	Tumbleweed and Leap 15.4 revised the implementation of VNC such that it ~~requires~~ system management to implement.		Tumbleweed and Leap 15.5 revised the implementation of VNC such that it uses system management to implement in its default installation.
	Use YaST2 to configure the system so that VNC will start as an option through the GDM (light-dm for xfce4).		Use YaST2 to configure the system so that VNC will start as an option through the GDM (light-dm for xfce4).
	*YaSt -> Network Services -> Remote Administration (VNC)		*YaSt -> Network Services -> Remote Administration (VNC)
Line 859:		Line 859:
	*From the console start a shared VNC session with "x0vncserver -PasswordFile /home/username/.vnc/passwd" and the system will return information about the session in that console. Leave that console alone and running to monitor the VNC access. A remote user not has access to this screen through the port and password which is indicated when the session starts. The session is persistent, but it requires that the xserver's display for that user remain live.		*From the console start a shared VNC session with "x0vncserver -PasswordFile /home/username/.vnc/passwd" and the system will return information about the session in that console. Leave that console alone and running to monitor the VNC access. A remote user not has access to this screen through the port and password which is indicated when the session starts. The session is persistent, but it requires that the xserver's display for that user remain live.
	*For remote access using secure shell tunneling the most reliable approach is to port forward in SSH from the remote machine with "ssh -L 5901:localhost:5901 user@remote.address" though the TightVNC client has an SSH tunneling option.		*For remote access using secure shell tunneling the most reliable approach is to port forward in SSH from the remote machine with "ssh -L 5901:localhost:5901 user@remote.address" though the TightVNC client has an SSH tunneling option.

			Alternatively, use the "vncserver" script to start a persistent session with the user's preferences. The script may be copied from other recent installations and edited. Using the one from 15.4, comment out the line

			#$default_opts{rfbwait} = 30000;

			which requires a feature of Xvnc that is not included in the 15.5 system. Also use zypper or YAST to install the package

			xorg-x11-vnc

			to implement the TigerVNC version used by the script.

WikiSysop: /* Conferencing with Zoom */

2022-08-04T06:06:25Z

Conferencing with Zoom

← Older revision		Revision as of 06:06, 4 August 2022
Line 731:		Line 731:

	[https://www.zoom.us Zoom] conferencing requires the installation of a package from their website. As root user you would run		[https://www.zoom.us Zoom] conferencing requires the installation of a package from their website. As root user you would run
	*zypper install zoom_openSUSE_x86_64.rpm
			zypper install zoom_openSUSE_x86_64.rpm

	It may be necessary to ignore the missing or incomplete public key signing. If a working key is available, then first add it with rpm where "RPM-KEY" is the downloaded key file		It may be necessary to ignore the missing or incomplete public key signing. If a working key is available, then first add it with rpm where "RPM-KEY" is the downloaded key file
	*rpm --import RPM-KEY
			rpm --import RPM-KEY

	Zoom provides access to select and control the audio and video sources for your meeting. Sometimes the audio connections will have to be reviewed since these are automatic. Pipewire appears to work better than Pulseaudio with Tumbleweed following changes implemented in the distribution in July 2022.		Zoom provides access to select and control the audio and video sources for your meeting. Sometimes the audio connections will have to be reviewed since these are automatic. Pipewire appears to work better than Pulseaudio with Tumbleweed following changes implemented in the distribution in July 2022.

	Google Meet works in the Chrome browser. Microsoft TEAMS has a browser version and a downloadable application. If you chose to use TEAMS or are required to do so by your institution then consider disabling its default which is to run it whenever you are logged in. This is controlled by the contents of the hidden directory		Google Meet works in the Chrome browser. Microsoft TEAMS has a browser version and a downloadable application. If you chose to use TEAMS or are required to do so by your institution then consider disabling its default which is to run it whenever you are logged in. This is controlled by the contents of the hidden directory
	*.config/autostart


			.config/autostart

	== Wireless ==		== Wireless ==

WikiSysop at 05:52, 4 August 2022

2022-08-04T05:52:06Z

← Older revision		Revision as of 05:52, 4 August 2022
Line 723:		Line 723:


			== Sound ==

	== Zoom ~~not Skype ==~~		As of July 2022 in Tumbleweed, the PulseAudio packages may not connect to Bluetooth headsets or to USB microphones, and will not work with Zoom (see the following). A solution is to remove PulseAudio if it is installed by default. Install all the packages for Alsa, and then install the Pipewire replacement for PulseAudio and Jack. If the Pavucontrol mixer is missing after these changes, then restore it as well for an audio mixer.

	~~While Skype is supported again on Linux through its newer version, it was not working well~~ with ~~Opensuse 42.3 has not been tested with Leap 15.~~ ~~Alternatives include Google Hangouts and conferencing software~~ [https://www.zoom.us Zoom]~~, which is~~ the ~~recommended solution~~. If for ~~university needs or~~ your ~~preference you also want Microsoft Teams,~~ the ~~best solution is~~ to ~~run it~~ in the Chrome browser. ~~The desktop~~ version ~~of Teams for Linux will install an autostart entry~~ and is ~~intended~~ to ~~be dominant on~~ the ~~operating system~~.
			== Conferencing with Zoom ==

			[https://www.zoom.us Zoom] conferencing requires the installation of a package from their website. As root user you would run
			*zypper install zoom_openSUSE_x86_64.rpm
			It may be necessary to ignore the missing or incomplete public key signing. If a working key is available, then first add it with rpm where "RPM-KEY" is the downloaded key file
			*rpm --import RPM-KEY

			Zoom provides access to select and control the audio and video sources for your meeting. Sometimes the audio connections will have to be reviewed since these are automatic. Pipewire appears to work better than Pulseaudio with Tumbleweed following changes implemented in the distribution in July 2022.

			Google Meet works in the Chrome browser. Microsoft TEAMS has a browser version and a downloadable application. If you chose to use TEAMS or are required to do so by your institution then consider disabling its default which is to run it whenever you are logged in. This is controlled by the contents of the hidden directory
			*.config/autostart

WikiSysop at 05:54, 25 July 2022

2022-07-25T05:54:20Z

← Older revision		Revision as of 05:54, 25 July 2022
Line 817:		Line 817:

	Increasingly useful for data analysis, Julia is added on servers and computers where processing is done. The Julia package provided by OpenSUSE is the stable version, while Julia is developing so quickly that the most recent version is best to have on hand. We use the source distribution from the Julia Lanuage Download website [https://julialang.org/downloads/]. Untar the package in /usr/local, and link to the "julia" executable from /usr/local/bin/. This will make it first on your PATH and supercede a system installation.		Increasingly useful for data analysis, Julia is added on servers and computers where processing is done. The Julia package provided by OpenSUSE is the stable version, while Julia is developing so quickly that the most recent version is best to have on hand. We use the source distribution from the Julia Lanuage Download website [https://julialang.org/downloads/]. Untar the package in /usr/local, and link to the "julia" executable from /usr/local/bin/. This will make it first on your PATH and supercede a system installation.


			== Google Chrome ==

			OpenSUSE does not provide the Chrome browser. To install it follow these steps from the command line as root or sudo

			*zypper ar http://dl.google.com/linux/chrome/rpm/stable/x86_64 Google-Chrome
			*wget https://dl.google.com/linux/linux_signing_key.pub
			*rpm --import linux_signing_key.pub
			*zypper ref -f
			*zypper in google-chrome-stable


			== Tight VNC ==

			Tumbleweed and Leap 15.4 revised the implementation of VNC such that it requires system management to implement.
			Use YaST2 to configure the system so that VNC will start as an option through the GDM (light-dm for xfce4).
			*YaSt -> Network Services -> Remote Administration (VNC)
			*Check "Allow Remote Administration without Session Management" and deselect browser option since it is insecure
			*In /etc/tigervnc add a file vncserver.users with lines such as ":1=username" so that the port used by a user is unique to that user.
			*Restart the GDM with system restart xdm.service
			*When a remote user accesses the machine with a VNC client on this port, e.g. 5901 for :1, they should be able to connect to a VNC session using the user's system password.
			Within that session the screen size may be set using xrandr with "xrandr" to see the available geometries and "xrandr -s 1920x1080" to set a preferred geometry.
			*Access through the login and GDM is available only when there is no concurrent session on the console for that users.
			*VNC sessions started in this way are not persistent and will stop when the user logs off. They are not shared.
			*Use vncpasswd to set a user password that will be used for running a screen copy session that may be shared.
			*From the console start a shared VNC session with "x0vncserver -PasswordFile /home/username/.vnc/passwd" and the system will return information about the session in that console. Leave that console alone and running to monitor the VNC access. A remote user not has access to this screen through the port and password which is indicated when the session starts. The session is persistent, but it requires that the xserver's display for that user remain live.
			*For remote access using secure shell tunneling the most reliable approach is to port forward in SSH from the remote machine with "ssh -L 5901:localhost:5901 user@remote.address" though the TightVNC client has an SSH tunneling option.

WikiSysop at 05:44, 25 July 2022

2022-07-25T05:44:39Z

← Older revision		Revision as of 05:44, 25 July 2022
Line 1:		Line 1:
	The observatory's servers and control computers run on the OpenSuse distribution of Linux-based software, currently Leap 15.3 . We have chosen the Leap series because of its conservative testing and stability. Generally the slowed cycle of new versions does not cause problems, except where we need software that is pushing the edge, notably AstroPy. We have been using Tumbleweed since it was introduced on selected telescopes where the most recent packages were required, usually without stability issues.		The observatory's servers and control computers run on the OpenSuse distribution of Linux-based software, currently Leap 15.4 . We have chosen the Leap series because of its conservative testing and stability. Generally the slowed cycle of new versions does not cause problems, except where we need software that is pushing the edge, notably AstroPy. We have been using Tumbleweed since it was introduced on selected telescopes where the most recent packages were required, usually without stability issues.

	These evolving installation notes originated with much earlier versions of OpenSuse and are rewritten as we gain experience with the most recent releases and work-around solutions to problems.		These evolving installation notes originated with much earlier versions of OpenSuse and are rewritten as we gain experience with the most recent releases and work-around solutions to problems.

WikiSysop at 06:36, 7 December 2021

2021-12-07T06:36:43Z

← Older revision		Revision as of 06:36, 7 December 2021
Line 639:		Line 639:
	== Adobe Flash ==		== Adobe Flash ==

	~~Until late 2016 Adobe had stopped supporting~~ Flash ~~on Linux. While Adobe now has resumed security updates for Flash that will work with Firefox, a better solution~~ is ~~to install Google Chrome. This provides full support for the remaining Flash websites~~ and ~~reliable security plus DRM management when~~ needed. ~~Both Chrome and Firefox block Flash content when HTML5 alternatives are available~~.		Flash is obsolete and no longer needed, or supported. It is best forgotten.


Line 714:		Line 714:


	~~VirtualBox as supplied by OpenSuse cannot be updated using~~ the ~~Oracle site. Instead~~ of ~~installing their version, we use~~ the latest ~~Oracle RPM which is currently version 6.0.8.~~		With Tumbleweed, the version of Virtualbox in the latest distribution will be sufficiently current that it will work well simply installed from Yast. With Leap, it may require manual installation from source once a year or so has passed since that version of Leap was introduced. If VirtualBox is going to be used, it may be best to start with Tumbleweed to make long term maintenance easier.

	*Set the BIOS to allow virtualization technology and to allow advanced I/O for sharing resources.
	*Retrieve the packages from https://www.virtualbox.org/wiki/Linux_Downloads .
	*Retrieve the repo file f
	*Retrieve the public key from https://www.virtualbox.org/download/
	*Install the public key with rpm --import public_key.asc
	*Install the repository with zypper ar -f ./file.repo
	*zypper --non-interactive install VirtualBox-xxx-.rpm
	*Retrieve the extension pack from ~~Oracle's download site.~~
	*VBoxManage extpack install .Oracle_VM_VirtualBox_Extension_Pack-xxx.~~vbox-extpack~~
	*In Opensuse YAST, add the Virtualbox guest kernel modules and guest tools, ~~or use the guest additions from Oracle.~~
	*Add the virtualbox group to the user(s) who will run it .
	*Start the qt interface from ~~the command line with ''virtualbox'' .~~
	*Create a ~~directory~~ that ~~will be shared with the guest OS and set this up in virtualbox when building a virtual machine~~ .
	*Once the guest OS is ~~installed~~, ~~add the guest additions to~~ it ~~also,~~ to ~~enable the shared directory and mouse/pointer integration .~~

	*Lastly, read the Virtualbox on-line [https://www.virtualbox.org/manual/ch04.html manual] .

	~~For access to the USB system the guest OS must have a driver installed. Virtualbox presents a virtual xHCI USB3 device~~ to ~~the guest. The driver provided by [https://downloadcenter.intel.com/product/65855/Intel-USB-3-0-eXtensible-Host-Controller-Driver Intel] has worked for us in a Windows 7 installation~~.



Line 746:		Line 726:
	== Zoom not Skype ==		== Zoom not Skype ==

	While Skype is supported again on Linux through its newer version, it was not working well with Opensuse 42.3 has not been tested with Leap 15. Alternatives include Google Hangouts and conferencing software [https://www.zoom.us Zoom], which is the recommended solution.		While Skype is supported again on Linux through its newer version, it was not working well with Opensuse 42.3 has not been tested with Leap 15. Alternatives include Google Hangouts and conferencing software [https://www.zoom.us Zoom], which is the recommended solution. If for university needs or your preference you also want Microsoft Teams, the best solution is to run it in the Chrome browser. The desktop version of Teams for Linux will install an autostart entry and is intended to be dominant on the operating system.

John at 15:35, 30 August 2021

2021-08-30T15:35:27Z

← Older revision		Revision as of 15:35, 30 August 2021
Line 833:		Line 833:

	Both Firefox and Chrome browsers will negotiate an automatic proxy server while curl, zypper, and yast will not.		Both Firefox and Chrome browsers will negotiate an automatic proxy server while curl, zypper, and yast will not.


			== Julia Language ==

			Increasingly useful for data analysis, Julia is added on servers and computers where processing is done. The Julia package provided by OpenSUSE is the stable version, while Julia is developing so quickly that the most recent version is best to have on hand. We use the source distribution from the Julia Lanuage Download website [https://julialang.org/downloads/]. Untar the package in /usr/local, and link to the "julia" executable from /usr/local/bin/. This will make it first on your PATH and supercede a system installation.