From 62b82a66e93dd5cdf7d871a83391aebb98257753 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?G=C3=BCrkan=20Myczko?= <myczko@phys.ethz.ch> Date: Fri, 31 Jan 2025 13:50:15 +0100 Subject: [PATCH] some updates --- ...are_on_the_d-phys_linux_computers.markdown | 52 ++----------------- 1 file changed, 3 insertions(+), 49 deletions(-) diff --git a/linux/software_on_the_d-phys_linux_computers.markdown b/linux/software_on_the_d-phys_linux_computers.markdown index 9e319342..a5970618 100644 --- a/linux/software_on_the_d-phys_linux_computers.markdown +++ b/linux/software_on_the_d-phys_linux_computers.markdown @@ -3,7 +3,7 @@ Software on the D-PHYS Linux Computers Here is a list of some software that is available on the D-PHYS Linux workstations. It is by far incomplete and we install more packages as the need arises. -Currently we run Ubuntu 22.04, migrating to [Debian 12](https://isg.phys.ethz.ch/2024/07/24/linux-workstations-debian/). +Currently we run Debian 12, migrated from [Ubuntu 22.04](https://isg.phys.ethz.ch/2024/07/24/linux-workstations-debian/). Manual Pages, Documentation --------------------------- @@ -44,9 +44,6 @@ Text Processing and Editors GNOME ----- -If you're missing the GNOME dock, you can get it back with -`gnome-shell-extension-tool -e ubuntu-dock@ubuntu.com` - If you still get shown old icons, you can use `gnome-tweak` and select "Yaru" in Appearance. @@ -70,10 +67,6 @@ gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffe Compilers & Interpreters ------------------------ -### BASIC - -* `pcbasic` the [GW-BASIC compatible interpreter](https://github.com/robhagemans/pcbasic) - ### C, Objective-C and C++ * `gcc` and `g++` from the [GNU Compiler Collection](http://gcc.gnu.org/) @@ -121,10 +114,6 @@ Java software usually don't need an installation. They can be just downloaded to your `$HOME` or `/scratch/directory` and unpacked, and run with `java -jar the.jar` -### Perl - -Installed by default. - ### Python See [[linux/workstation/python]] for details on how to load our pre-installed Python packages. @@ -250,7 +239,7 @@ Finding Software Packages You can list all installed packages with `dpkg --list` If you want to search the whole Debian software archive you can use `apt-cache`, e.g. like this: `apt-cache search emacs` -Alternatively you can use the web interface of [Debian](https://packages.debian.org/) or [Ubuntu](https://packages.ubuntu.com/) +Alternatively you can use the web interface of [Debian](https://packages.debian.org/) This command will also find packages which are not installed on our system. You can check whether a specific package is installed by specifying the package name like such: `dpkg -l emacs` @@ -258,38 +247,6 @@ To list the content of a package use `dpkg -L package` Another source of software is https://github.com/ -Installing Software with Spack ------------------------------- - -[Spack](https://github.com/spack/spack) can be installed to -install a lot of software, in multiple versions. Please -read their manual. - -Here is some hints to get started: - -* `spack compiler find` -* `spack external find` - -Show directed acyclic graph (DAG) of a package: - -* `spack graph hdfview` - -Finding installation information: - -* `spack info visit` - -Finding the install location: - -* `spack location --install-dir gcc@8` - -Load the environemnt: - -* `eval $(./spack load --sh gcc@8)` - -List installed packages: - -* `spack find` - Resource Management ------------------- @@ -299,8 +256,6 @@ We have a lot of tools, please use them. * `htop` - shows you number of CPUs/cores and memory/swap usage * `ruptime/rload` - shows you hosts and their CPU/MEM/GPU/GPUMEM usage in %, [Homepage](https://github.com/alexmyczko/ruptime) * `timeout` -* `dmtcp` - Distributed MultiThreaded Checkpointing -installed. * `scr` - [Homepage](https://computing.llnl.gov/projects/scalable-checkpoint-restart-for-mpi) CUDA enabled machines also have @@ -324,8 +279,7 @@ GUENTHER cluster also has * `pestat` * [SLURM](https://scicomp.ethz.ch/wiki/Using_the_batch_system) batch queueing system -You can use `nice` to run jobs niced, or `cpulimit -l 50 -- yourjob` -to limit cpu usage on your job to 50 %. +You can use `nice` to run jobs niced, or `cpulimit -l 50 -- yourjob` to limit cpu usage on your job to 50 %. Debugging --------- -- GitLab