gcc and gpc (C and Pascal)

Compilation

ALTERNATIVE 1 Plain gcc compilation (direct invocation)

• -v = verbose
• -o = is followed by the name of the executable
• showenv.c = the sourcecode

• -E : don't compile, just preprocess
• -S : save the intermediate assembly language (remove the -o flag then)
• -c : create object files ending in .o
• -L/src/local/lib : to link with library /src/local/lib

ALTERNATIVE 2 MAKE

• ---contents sample 'make'-file ---
• # makefile : compilation resulting in the executable 'showenv'
• # execution of the makefile: "make showenv"
• showenv:
• gcc showenv.c -v -o showenv

• --- end of contents of sample 'make'-file ---

ALTERNATIVE 3 Automake, autoconf, libtool

ALTERNATIVE 4 ANT

Execution

configure and make

Java

Debian approach

• Install 'sudo apt-get install openjdk-17-jdk'
• Uninstall: 'sudo apt auto-remove openjdk-17-jdk'

• Libraries: libice-dev libpthread-stubs0-dev libsm-dev libx11-dev libxau-dev libxcb1-dev libxdmcp-dev libxt-dev x11proto-dev xorg-sgml-doctools xtrans-dev
• Two jdk packages: openjdk-17-jdk openjdk-17-jdk-headless

openjdk-17-jdk

openjdk-17-jdk-headless

openjdk-17-jre

openjdk-17-jre-headless

ca-certificate-java

Other

IntelliJ IDEA approach

Fact finding

Debian basic installation

What answers to the java command

Fact finding

• 'which java'
• /usr/bin/java (if there is no PATH in .bashrc ('# PATH=/home/marc/.jdks/openjdk-18.0.2/bin:$PATH'))
• OR
• openjdk version "18.0.2" 2022-07-19 (if there is such a PATH in .bashrc)

Which version of java is this

• 'java -version' (will match your PATH)
• openjdk version "18.0.2" 2022-07-19
• OpenJDK Runtime Environment (build 18.0.2+9-61)
• OpenJDK 64-Bit Server VM (build 18.0.2+9-61, mixed mode, sharing)

Basics - path and classpath

Path

Classpath

Execution of a jar

IntelliJ on GrayTiger Debian 11 Bullseye

• IntelliJ IDEA Ultimate: commercial edition for JVM, web, and enterprise development. Includes the features of the Community edition, plus support for languages that other IntelliJ platform-based IDEs focus on, as well as support for a variety of server-side and front-end frameworks, application servers, integration with database and profiling tools, and more.
• IntelliJ IDEA Community Edition.

Install/remove on GrayTiger

Installation

1. Unpacked the IntelliJ IDEA distribution archive into /Downloads/.... This location is the {installation home}.
2. To start the application, open a console, cd into "{installation home}/bin" and type: ./idea.sh. This will initialize various configuration files in the configuration directory: ~/.config/JetBrains/IdeaIC2022.2
3. [OPTIONAL] Add "{installation home}/bin" to your PATH environment variable so that you can start IntelliJ IDEA from any directory/li>
4. [OPTIONAL] To adjust the value of the JVM heap size, create a file idea.vmoptions (or idea64.vmoptions if using a 64-bit JDK) in the configuration directory and set the -Xms and -Xmx parameters. To see how to do this, you can reference the vmoptions file under "{installation home}/bin" as a model but do not modify it, add your options to the new file.
5. [OPTIONAL] Change the location of the "config" and "system" directories - By default, IntelliJ IDEA stores all your settings in the ~/.config/JetBrains/IdeaIC2022.2 directory and uses ~/.local/share/JetBrains/IdeaIC2022.2 as a data cache. To change the location of these directories:
• Open a console and cd into ~/.config/JetBrains/IdeaIC2022.2
• Create a file idea.properties and set the idea.system.path and idea.config.path variables, for example:
• idea.system.path=~/custom/system
• idea.config.path=~/custom/config

Removal

• Delete the installation directory (GrayTiger: ~/Downloads/idea-IC-222.3345.118/)
• Remove the following directories:
• ~/.config/JetBrains/
• ~/.cache/JetBrains/
• ~/.local/share/JetBrains/

• As I installed OpenJDK 18, this must be manually removed (if you wish) from /home/marc/.jdks/openjdk-18.0.2/.
• There exists /home/marc/.java which contains e.g. fonts for JDK 17 and 18

Start-up

Getting started

Configuration

JDK

Libraries

Projects

• GTTI - building on TI - incomplete
• GLEIF-TI
• EU DSS - programming to understand e.g. validation
• Springkasteel - BouncyCastle

• /home/marc/IdeaProjects/GTTI-prj/GTTI-prj.iml - XML config data
• /home/marc/IdeaProjects/GTTI-prj/.idea - here you find a pointer to the xalan libraries

• /home/marc/Downloads/bc/bctest/bctest.iml - XML config data
• /home/marc/Downloads/bc/bctest/.idea

• global (available for many projects),
• project (available for all modules within a project),
• module (available for one module).

GLEIF-TI project

Run/debug configuration

• In program source right-click on main - 'Modify run configuration'
  • Here you can add eg CLI parameters
• Open 'Run' and select 'Edit configurations'.
  • Here you can edit existing run/debug configurations

Bouncy Castle test programs

• org.bouncycastle.crypto.test
• org.bouncycastle.jce.provider.test
• org.bouncycastle.cms.test
• org.bouncycastle.mail.smime.test
• org.bouncycastle.openpgp.test
• org.bouncycastle.tsp.test

• org.bouncycastle.mail.smime.examples
• org.bouncycastle.openpgp.examples

Legacy - Eclipse on GrayTiger Debian 11 Bullseye

Legacy on Debian 8 Jessie

Legacy

JDK1.1.3 on toothbrush (SuSE 5.3)

• the java runtime (i.e. classes.zip)
• java sources for public classes (i.e. src.zip)
• tools such as javac, java etc.
• documentation & demos

1. You need the right PATH statement. ">which java" results in ">/usr/lib/java/bin/java". Mind you, "java" is just a wrapper script, locating and starting the right binaries. Apparently, PATH gets set in /etc/profile.
2. You need the right CLASSPATH statement. What is your current CLASSPATH's value? ">echo $CLASSPATH". If nothing comes back, the variable is not set.
   • Fixing the classpath for the jdk itself I ran ">java -v(erbose) -classpath /Java/nsm1.class", resulting in "unable to find java/lang/threads". (((with hindsight: note you will now overwrite the standard classpath - so the regular classes are gone))) This is a fundamental problem, you don't find the class to create the first thread. Apparently the wrapper does not look into the right location /usr/lib/jdk113 where YaST put the binaries. So the solution is to ">export CLASSPATH=/usr/lib/jdk1.1.3:/Java". You set first the jdk binaries, and then where java can find your own classfiles.
   • Fixing "Can't find class nsm1.class" This means you made a naming mistake (or you have a classpath problem). The same name should be used 3 times:
     • for your sourcefile (foo.java),
     • for your main (inside that sourcefile) and
     • for the classfile (foo.class).

• >"export CLASSPATH=/usr/lib/java-----:/YourOwnAddition...."
• >"cd /Java" (change to the dir where your .jave file resides)

• >"javac nsm1.java" (note that you have to specify the .java extension)

JDK1.1.3 - a word about Applets

JDK1.1.3 - a word about Security

JDK1.1.7 on malekh (SuSE 6.1)

• /usr/doc/packages/java: SuSE 6.1 comes with Blackdown's jdk117, includes Metro Link's Motif - contains a README.linux - and an interesting index (pointing to the standard jdk117 README)
• /usr/doc/packages/javadoc: all the Sun documentation and demos
• /usr/doc/packages/javarunt: info about the run time environment

• "which java" results in "/usr/lib/java/bin/java"
• "java -version" results in "version 1.1.7".

1. "CLASSPATH=/JavaSamples/CoreJavaVol1+2" (setting the classpath too deep results in not finding your imports...)
2. alternatively, you can also append more: "CLASSPATH=/JavaNSMsec:/JavaSamples/CoreJavaVol1+2"
3. "export CLASSPATH"
4. "env" shows you the value of your environment variables, include CLASSPATH
5. "sh -x javac myprogram.java" will show the wrapper's substitution of CLASSPATH

1. "CLASSPATH=/JavaSamples/CoreJavaVol1+2:/JavaNSMsec" (no leading ".")
2. "export CLASSPATH" - you can use "env" to check...
3. "javac myprogram.java" or "sh -x javac myprogram.java"
4. now again explicitly set CLASSPATH, with a leading ".": "CLASSPATH=.:/JavaSamples/CoreJavaVol1+2:/JavaNSMsec"
5. "java myprogram" or "sh -x java myprogram"

1. "cd /JavaNSM"
2. "javac master09.java" or
3. "sh -x [/usr/lib/java/bin/]javac nsm9.java" to see substitutions in the wrapper
4. "ls -l" will show the timestamp of the .class file
5. "java master09" (or "sh -x java master09")

JDK1.1.7v3 on avina

• /usr/lib/jdk1.1.7 (from package 'java')
• /usr/lib/jdk1.1.8 (from packages 'ibmjdk' and 'ibmjre')

Java2 on tux (SuSE 7.0)

• standard:
  • JAVA2: java2-1.2.2-7 (Java2 SDK - Standard Edition v1.2.2) - /usr/lib/jdk1.2.2/bin/javac and /jre/bin/... (keytool, ...)
  • - /usr/share/doc/packages/java2
  • * which makes me conclude we don't have any 'standard extensions' such as javax.swing ... are they available for Linux?
  • JAVA1: java-1.1.8v1-2 (older JDK1.1.8)
  • JAVA1: javadoc-1.1.3-43
  • JAVA1: javarunt-1.1.7v3-19
• from IBM:
  • jikes-1.06-119 - IBM Jikes compiler, http://ibm.com/developerworks/opensource
  • ibmjava2-1.3-8 - /usr/share/doc/packages/ibmjava2 ("Sun's Java 1.3 - J2SE") => even higher than Sun's 1.2???
  • ibmjre2-1.3-8 - /usr/share/doc/packages/ibmjre2
  • ibmjaas-1.3-8 - /usr/share/doc/packages/ibmjaas
  • ibmjcom-1.3-8 - /usr/share/doc/packages/ibmjcom
• other goodies:
• jakarta-3.1-31
• jserv-1.1.2-25
• jtools-...

• "which java" results in "/usr/lib/java/bin/java" (same as with previous versions, actually a wrapper to .java_wrapper which is a shell script provided by Sun)
• "java -version" results in "version 1.2.2","Classic VM (build 1.2.2-L, green threads, nojit)"

1. Java2D demo's:
   • "cd /usr/share/doc/packages/java2/demo/jfc/Java2D" (exact path may vary)

   • "java -jar Java2Demo.jar" ===> nice demo

   • "cd /usr/share/doc/packages/java2/demo/applets/MoleculeViewer"
   • "appletviewer example3.html"
2. SwingSet demo's:
   • "cd /usr/share/doc/packages/java2/demo/jfc/SwingSet"
   • "java -jar SwingSet.jar" ===> nice demo
3. "appletviewer /usr/share/doc/packages/IBMJava2-SDK/jfc/demo/SwingSet2/SwingSet2.html"
4. Others: Metalworks, SwingApplet, ...

Java2 on imagine2 (SuSE 7.2)

FIRST TRY Installation of basic JDK and JRE done as part of the overall YaST2 installation. Running "java -version" tells me I have "java 1.3.0". xrpm tells me "java2 1.3-46" resides in "/usr/lib/jdk1.3". Doc and demos in "/usr/share/doc/packages/java2". SECOND TRY Yast2 installation of Java does not result in a working "javac" or "which java". So I did: "PATH=$PATH:/usr/lib/jdk1.3/bin" and "export PATH". Then OK.

Swing

See JTK1.html .

Java LDAP SDK

From the "LDAP programming in Java" book. The actual SDK classes reside in /packages/ldapjdk.jar and /packages/ldapfilt.jar. These must be included in the CLASSPATH. Useful programs include /src/netscape/ldap/tools/LDAPsearch.java etc. Usage e.g. "java LDAPSearch -h memberdir.netscape.com -b" "ou=member_directory, o=netcenter.com" "cn=tony d*"

JBuilder V3.5

Note that having Java2 installed is a prerequisite.

The JIT

JBuilder - install

JBuilder - components

1. JBuilder
2. JDatastore
3. Documentation
4. Samples

5. OpenTools

• usr/local/jbuilder35: the basics
• root/.jbuilder: properties, license info, ...
• root/.jdatastore: datastore properties
• root/jbproject/ the individual projects (ref infra)

mySQL

IV.109.1 What have we got..

• /usr/share/doc/packages/mysql - documentation
• /var/mysql - databases and logfiles
• /usr/bin - programs such as
  • mysql - the default client program to connect to the mysqld
  • mysql_install_db - installation script
  • mysql_findrows, zap, dump, import, dbug, show, acces, ...
• /usr/sbin/mysqld - server program
• /usr/share/mysql - misc additional files e.g. language extensions
• /usr/include/mysql - include files
• /usr/lib/mysql - static libs
• /usr/lib/mysqlclient.so* - runtime libs
• /usr/share/sql-bench - benchmarks - testsuite
• kmysqlad (KDE-admin)
• kmysql

IV.109.2 Completing the installation

• mysqladmin status
• mysqladmin extended-status
• but even better: via kmysqladmin and kmysql

IV.109.3 Creating databases and tables

• "mysql -h localhost -u root" to connect, then enter "CREATE DATABASE db_name" commands
• you can also use mysqladmin to create databases
• it should be possible via JDBC as well

• "show databases;"
• "select database();" tells you what database is currently selected
• "GRANT ALL ON menagerie.* TO your_sql_name;"
• "CREATE DATBASE menagerie"
• "USE menagerie"
• "SHOW TABLES"
• "CREATE TABLE pet (name varchar(20), ...);"
• "DESCRIBE pet;" shows you the structure
• "INSERT INTO pet VALUES (...);" to manually insert a record at a time
• "LOAD DATA ...;" to load from an ASCII text file
• "SELECT what FROM table WHERE conditions"

IV.109.4 Batch mode (scripts)

IV.109.5 Via JDBC

Ant

Installing Ant

Preparing to run Ant

• execute "export ANT_HOME=/jakarta-ant-1.4.1" (or whatever directory ant resides in)
• execute "which java" to determine java's home (e.g. /usr/lib/java/bin/java - this should be linked to e.g. /jdk1.3.1_01)
• execute "export JAVA_HOME=/usr/lib/java" (note that you cut-off the last /bin/java - appended automatically)
• execute "export PATH=${PATH}:${ANT_HOME}/bin" (this appends the ant bin directory to your path)
• I DID PUT THIS IN /root/.bash_profile
• Remember you can use "env" to display your environment variables.

Ant basics

• name: the project name
• default: the default target to make when no target is given
• basedir: the base-dir from where all path calculations are done

Running Ant

Poseidon UML

Installing Poseidon

Maven (version 3)

Installation on GrayTiger

Initial status

• libapache-pom-java - 'Maven metadata for all Apache projects'
• libcommons-parent-data - 'Maven metadata for Apache Commons project'

• /usr/share/doc/libapache-pom-java
• /usr/share/doc/libapache-pom-java/changelog.Debian.gz
• /usr/share/doc/libapache-pom-java/copyright
• /usr/share/maven-repo
• /usr/share/maven-repo/org
• /usr/share/maven-repo/org/apache
• /usr/share/maven-repo/org/apache/apache
• /usr/share/maven-repo/org/apache/apache.
• /usr/share/maven-repo/org/apache/apache./18
• /usr/share/maven-repo/org/apache/apache./18/apache.-18-site.xml
• /usr/share/maven-repo/org/apache/apache./18/apache.-18.pom
• /usr/share/maven-repo/org/apache/apache./debian
• /usr/share/maven-repo/org/apache/apache./debian/apache.-debian-site.xml
• /usr/share/maven-repo/org/apache/apache./debian/apache.-debian.pom
• /usr/share/maven-repo/org/apache/apache/18
• /usr/share/maven-repo/org/apache/apache/18/apache-18.pom
• /usr/share/maven-repo/org/apache/apache/debian
• /usr/share/maven-repo/org/apache/apache/debian/apache-debian.pom

Installation

• Use your preferred archive extraction tool => extracted into /home/marc/Downloads/mvn/
• Add the bin directory of the created directory /home/marc/Downloads/mvn/apache-maven-3.8.6/bin to the PATH environment variable
• Set the path in the startup file (~/.bashrc) as 'PATH=/home/marc/Downloads/mvn/apache-maven-3.8.6/bin:$PATH'
• Confirm with mvn -v in a new shell.

• Deleted /home/marc/Downloads/mvn/
• Removed the path in the startup file (~/.bashrc)

• how to use maven under IDEA?
• or alternatively: use the IDEA maven via CLI, by adding its path to PATH ===> DONE

Maven's functionality

General introduction

Configuration

Plugins

Help plugin

1. help:active-profiles - Displays a list of the profiles which are currently active for this build.
2. help:all-profiles - Description: Displays a list of available profiles under the current project. Note: it will list all profiles for a project. If a profile comes up with a status inactive then there might be a need to set profile activation switches/property.
3. help:describe - Description: Displays a list of the attributes for a Maven Plugin and/or goals (aka Mojo - Maven plain Old Java Object).
4. help:effective-pom - Description: Displays the effective POM as an XML for this build, with the active profiles factored in, or a specified artifact. If verbose, a comment is added to each XML element describing the origin of the line.
5. help:effective-settings - Description: Displays the calculated settings as XML for this project, given any profile enhancement and the inheritance of the global settings into the user-level settings.
6. help:evaluate - Description: Evaluates Maven expressions given by the user in an interactive mode.
7. help:help - Description: Display help information on maven-help-plugin. Call mvn help:help -Ddetail=true -Dgoal= to display parameter details.
8. help:system - Description: Displays a list of the platform details like system properties and environment variables.

Other plugins

• Build plugins will be executed during the build and they should be configured in the < build/ > element from the POM.
• Reporting plugins will be executed during the site generation and they should be configured in the < reporting/ > element from the POM. Because the result of a Reporting plugin is part of the generated site, Reporting plugins should be both internationalized and localized.

Nutshell

Project creation through Archtypes

• maven-archetype-archetype - to generate a sample archetype project.
• maven-archetype-j2ee-simple - to generate a simplifed sample J2EE application.
• maven-archetype-mojo - to generate a sample a sample Maven plugin.
• maven-archetype-plugin - to generate a sample Maven plugin.
• maven-archetype-plugin-site - to generate a sample Maven plugin site.
• maven-archetype-portlet - to generate a sample JSR-268 Portlet.
• maven-archetype-quickstart - to generate a sample Maven project.
• maven-archetype-simple - to generate a simple Maven project.
• maven-archetype-site - to generate a sample Maven site which demonstrates some of the supported document types like APT, XDoc, and FML and demonstrates how to i18n your site.
• maven-archetype-site-simple - to generate a sample Maven site.
• maven-archetype-webapp - to generate a sample Maven Webapp project.

Usage

Directory layout

options

• -am,--also-make If project list is specified, also build projects required by the list
• -amd,--also-make-dependents If project list is specified, also build projects that depend on projects on the list
• -B,--batch-mode Run in non-interactive (batch) mode (disables output color)
• -b,--builder The id of the build strategy to use
• -C,--strict-checksums Fail the build if checksums don't match
• -c,--lax-checksums Warn if checksums don't match
• -cpu,--check-plugin-updates Ineffective, only kept for backward compatibility
• -D,--define Define a system property
• -e,--errors Produce execution error messages
• -emp,--encrypt-master-password Encrypt master security password
• -ep,--encrypt-password Encrypt server password
• -f,--file Force the use of an alternate POM file (or directory with pom.xml)
• -fae,--fail-at-end Only fail the build afterwards; allow all non-impacted builds to continue
• -ff,--fail-fast Stop at first failure in reactorized builds
• -fn,--fail-never NEVER fail the build, regardless of project result
• -gs,--global-settings Alternate path for the global settings file
• -gt,--global-toolchains Alternate path for the global toolchains file
• -h,--help Display help information
• -l,--log-file Log file where all build output will go (disables output color)
• -llr,--legacy-local-repository Use Maven 2 Legacy Local Repository behaviour, ie no use of _remote.repositories. Can also be activated by using -Dmaven.legacyLocalRepo=true
• -N,--non-recursive Do not recurse into sub-projects
• -npr,--no-plugin-registry Ineffective, only kept for backward compatibility
• -npu,--no-plugin-updates Ineffective, only kept for backward compatibility
• -nsu,--no-snapshot-updates Suppress SNAPSHOT updates
• -ntp,--no-transfer-progress Do not display transfer progress when downloading or uploading
• -o,--offline Work offline
• -P,--activate-profiles Comma-delimited list of profiles to activate
• -pl,--projects Comma-delimited list of specified reactor projects to build instead of all projects. A project can be specified by [groupId]:artifactId or by its relative path
• -q,--quiet Quiet output - only show errors
• -rf,--resume-from Resume reactor from specified project
• -s,--settings Alternate path for the user settings file
• -t,--toolchains Alternate path for the user toolchains file
• -T,--threads Thread count, for instance 2.0C where C is core multiplied
• -U,--update-snapshots Forces a check for missing releases and updated snapshots on remote repositories
• -up,--update-plugins Ineffective, only kept for backward compatibility
• -v,--version Display version information
• -V,--show-version Display version information WITHOUT stopping build
• MLS: -X seems to produce full debug info (not documented?)

Lifecycles, their phases, goals

• clean
• default
• site

• clean - pre-clean, clean, post-clean (so there's both a lifecycle and a phase called clean)
• default - validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy
• site - pre-site, site, post-site, site-deploy

Execution

• project : top-level element in all Maven pom.xml files.
• modelVersion : what version of the object model this POM is using. The version of the model itself changes very infrequently but it is mandatory in order to ensure stability of use if and when the Maven developers deem it necessary to change the model.
• groupId : the unique identifier of the organization or group that created the project. The groupId is one of the key identifiers of a project and is typically based on the fully qualified domain name of your organization. For example org.apache.maven.plugins is the designated groupId for all Maven plugins.
• artifactId : the unique base name of the primary artifact being generated by this project. The primary artifact for a project is typically a JAR file. Secondary artifacts like source bundles also use the artifactId as part of their final name. A typical artifact produced by Maven would have the form -. (for example, myapp-1.0.jar).
• version : the version of the artifact generated by the project. Maven goes a long way to help you with version management and you will often see the SNAPSHOT designator in a version, which indicates that a project is in a state of development. We will discuss the use of snapshots and how they work further on in this guide.
• name : the display name used for the project. This is often used in Maven's generated documentation.
• url : where the project's site can be found. This is often used in Maven's generated documentation.
• properties : value placeholders accessible anywhere within a POM.
• dependencies : this element's children list dependencies. The cornerstone of the POM.
• build : this element handles things like declaring your project's directory structure and managing plugins.

Netbeans

Node.js, nvm and npm

• Node.js is an asynchronous event-driven JavaScript runtime (jsre)
• nvm (Node Version Manager) allows to download and install Node.js (in multiple versions if you want)
• npm (Node Package Manager) allows to install javascript packages (npm comes with Node.js so if you have node installed you most likely have npm installed as well)

Install on DebbyBuster

nvm on DebbyBuster

• nvm --version lists the version of nvm that is installed (e.g. 0.38.0)
• nvm ls List available versions
• apparently DebbyBuster has version 8 - 14 available, the default is 8
• nvm install 8.0.0 Install a specific version number (of Node.js - implicit)
• nvm use 8.0 Use the latest available 8.0.x release
• nvm use node Use the latest version
• nvm run 6.10.3 app.js Run app.js using node 6.10.3
• nvm ls-remote List available versions remotely
• nvm exec 4.8.3 node app.js Run `node app.js` with the PATH pointing to node 4.8.3
• nvm alias default 8.1.0 Set default node version on a shell
• nvm alias default node Always default to the latest available node version on a shell
• nvm install node Install the latest available version
• nvm install --lts Install the latest LTS version
• nvm use --lts Use the latest LTS version

npm on DebbyBuster

Install on Kali

What and where

Nodeclipse

Visual Studio Code - VSCode

Install on GrayTiger

sudo apt install ./code_1.83.1-1696982868_amd64.deb 
[sudo] password for marc: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'code' instead of './code_1.83.1-1696982868_amd64.deb'
The following NEW packages will be installed:
  code
0 upgraded, 1 newly installed, 0 to remove and 322 not upgraded.
Need to get 0 B/95.7 MB of archives.
After this operation, 386 MB of additional disk space will be used.
Get:1 /home/marc/Downloads/vs_code/code_1.83.1-1696982868_amd64.deb code amd64 1.83.1-1696982868 [95.7 MB]
Selecting previously unselected package code.
(Reading database ... 628885 files and directories currently installed.)
Preparing to unpack .../code_1.83.1-1696982868_amd64.deb ...
Unpacking code (1.83.1-1696982868) ...
Setting up code (1.83.1-1696982868) ...
Processing triggers for gnome-menus (3.36.0-1) ...
Processing triggers for shared-mime-info (2.0-1) ...
Processing triggers for mailcap (3.69) ...
Processing triggers for desktop-file-utils (0.26-1) ...

Install additional tools on GrayTiger

• Yeoman - An application scaffolding tool, a command line version of File > New Project.
• generator-hottowel - A Yeoman generator for quickly creating AngularJS applications.
• Express - An application framework for Node.js applications using the Pug template engine.
• Gulp - A streaming task runner system which integrates easily with VS Code tasks.
• Mocha - A JavaScript test framework that runs on Node.js.
• Yarn - A dependency manager and alternative to npm.

User interface

Settings

Rust in VS Code

Install on DebbyBuster

• nvm install --lts (to run with the latest long term support version of nvm - otherwise VS Code/execution complains)
• create HelloWorldApp.js using VSCode
• cd /home/marc/VS-Code/HelloWorld
• node HelloWorldApp.js (executes)
• alternatively, execute within VSCode
• open a terminal and 'node HelloWorldApp.js'
• 'run' - but this insists on using an outdated version of node.js and fails - where is this configured? - in /.vscode/launch.json file - use "runtimeVersion": "14.17.4"

• jsconfig.json - the presence of a jsconfig.json file in a directory indicates that the directory is the root of a JavaScript project - see https://code.visualstudio.com/docs/languages/jsconfig
• launch.json - described at https://github.com/microsoft/vscode-js-debug/blob/main/OPTIONS.md

{
  "compilerOptions": {
    "module": "commonjs",
    "target": "es6"
  },
  "exclude": ["node_modules"]
}

Minimal launch.json file:
{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
               {
            "type": "pwa-node",
            "runtimeVersion": "14.17.4", // 
            "request": "launch",
            "name": "Launch Program",
            "skipFiles": [
                "/**"
            ],
            "program": "${workspaceFolder}/HelloWorldApp.js"
        }
    ]
}

Extend with 'Express'

• create : myExpressApp/ --- contains the app.js application
• create : myExpressApp/public/ --- public code and data etc - static content
• create : myExpressApp/public/javascripts/
• create : myExpressApp/public/images/
• create : myExpressApp/public/stylesheets/
• create : myExpressApp/public/stylesheets/style.css
• create : myExpressApp/routes/ ---how an application responds to a client request to a particular endpoint, which is a URI (or path) and a specific HTTP request method (GET, POST, and so on), for details refer to https://expressjs.com/en/guide/routing.html.
• create : myExpressApp/routes/index.js
• create : myExpressApp/routes/users.js
• create : myExpressApp/views/
• create : myExpressApp/views/error.jade
• create : myExpressApp/views/index.jade
• create : myExpressApp/views/layout.jade
• create : myExpressApp/app.js
• create : myExpressApp/package.json ---the package information
• create : myExpressApp/bin/
• create : myExpressApp/bin/www ---a javascript that creates an http server (not a binary)

• change directory: $ cd myExpressApp
• install dependencies: $ npm install
• run the app: $ DEBUG=myexpressapp:* npm start

• cd myExpressApp
• npm install

Install on Kali

• Install and run the Express Generator to create an Express application structure
• npm install to install all the dependencies
• an Express application has a package.json file that includes a start script to run node ./bin/www
• next do npm start
• this starts the node.js webserver, and you can visit http://localhost:3000

Visual Studio Code - VSCode for Rust

Install on GrayTiger

IntelliJ IDEA

Git

Basics

• the local information
• the local description in LW0400ITDEV

Debian info

• Git Debian reference

Installation of git on Debian

• GrayTiger: git and git-man installed - and plenty of packages not installed; 'git --version' yields git version 2.30.2
• BlackTiger: same; git version 2.20.1
• Observation in Synaptics: weird messages such as installation of 'git-all' requires removal of virtually all gnome stuff (?).

Github CLI gh

Basics

Installation of gh on Debian

Repo for OPTEE

Basics

• homepage at https://gerrit.googlesource.com/git-repo
• doc at https://source.android.com/docs/setup/create/repo
• Repo install including chmod command: https://source.android.com/docs/setup/download

Repo installation attempt 1

• Installation on BlackTiger: 'sudo apt-get install repo' (ok)
• Result: man page works, repo commands do no, ...
  • In /home/OPTEE there is ./repo / deleted since repo fails to work
  • In / there is .repoconfig with GPG keys
• Execution: 'repo init -u url ... ' (not ok, fails saying 'command not found, syntax error, line 94')
  • Essentially 'repo' is a python script, main.py, with a wrapper 'repo'. The lines around 94 deal with minimum Python version, and messages such as your Python 3 is too old.
  • Which leads to the question: what Python is BlackTiger running? 'apt show python' reveals 'version 2.7.16-1'. On python.org you find the most recent version Oct 2023 is 3.12, so 2.7 is probably too old.
  • Refer to Python language discussion.
  • Refer to Python installation.

Repo installation attempt 2

• Installation on BlackTiger: 'sudo apt-get install repo' (ok)
• Then 'dpkg -L repo' returns
  • /usr/bin/repo - which is a script that checks Python versions, contains 'Init', 'Fetch' and much more
  • /usr/share/bash-completion/completions/repo - not sure what that is
  • /usr/share/doc/repo - minimal info
  • /usr/share/man/man1/repo.1.gz - man page - referring to use in Android source download
  Repo install including chmod command (if needed)]
• https://source.android.com/docs/setup/download
• https://source.android.com/docs/setup/download#installing-repo
• Installation verification: 'repo version', should return something like repo not installed>; repo launcher version 2.15; (from /usr/bin/repo)< OK, try repo init next/li>
• Next is initialisation, see https://source.android.com/docs/setup/download/downloading#initializing-a-repo-client, this fails
• Get https: gerrit.googlesource.com/git-repo/clone.bundle
• Get https: gerrit.googlesource.com/git-repo/
• File "/home/marc/OPTEE/.repo/repo/main.py", line 94, ) syntax error - invalid syntax
• Some googling: may have to do with your Python version (what does repo expect??? Possible solution: invoke through python3
• python3 /usr/bin/repo init -u https://git.gitlab.arm.com/arm-reference-solutions/arm-reference-solutions-manifest.git -m pinned-rdv1.xml -b refs/tags/RD-INFRA-2021.02.24
• python3 /usr/bin/repo sync -c -j $(nproc) --fetch-submodules --force-sync
• Trying: 'python3 /usr/bin/repo init' - results in 'please use python 2.7' - 'a new version of repo is available' - 'the launcher is run from /usr/bin/repo, the launcher is not writable' - 'fatal: manifest url is required'
• Trying: 'python3 /usr/bin/repo help init' - results in 'please use python 2.7' - 'a new version of repo is available' - 'the launcher is run from /usr/bin/repo, the launcher is not writable' - 'fatal: manifest url is required' - followed by the help information on 'init'
• Trying again since the main error seems to be 'manifest url is required': 'python3 /usr/bin/repo init -u https://github.com/OP-TEE/manifest.git -m qemu_v8.xml' - OK 'repo has been initialised in /home/marc/OPTEE'
• Then need to sync it: 'python3 /usr/bin/repo sync' - OK results in many subdirs under /home/marc/OPTEE:
• build, buildroot
• hafnium
• linux
• mbedtls
• optee_benchmark
• optee_client
• optee_examples
• optee_os
• optee_rust
• optee_test
• qemu
• trusted-firmware-a
• u-boot

• mkdir -p ~/.bin
• PATH="${HOME}/.bin:${PATH}"
• curl https://storage.googleapis.com/git-repo-downloads/repo > ~/.bin/repo
• chmod a+rx ~/.bin/repo
• ... where a corresponds to all, i.e. user, group, others - so this would mean give all read and execute rights on repo - but if not writeable - maybe rwx - ok, did so on BlackTiger
-

Python and SageMath

Python versions

• Python 2.0 was released in 2000. Python 2.7.18, released in 2020, was the last release of Python 2.
• Python 3.0, released in 2008, was a major revision not completely backward-compatible with earlier versions.
• What's on GrayTiger? Synaptics: python2 (version 2.7.18), python3 (3.9.2), and a zillion other packages/libs.
• What's on BlackTiger? Synaptics: python2 (version 2.7.16) , python3 (version 3.7.3), and a zillion other packages/libs.

Invocation

Python interpreter

Jupyter notebook

Sagemath notebook

• /usr/lib/python3 (GrayTiger)
• /usr/share/doc/sagemath (GrayTiger)
• But starting a notebook and going through help gets you started alright

• 'sage' in a console starts a Sage session. To quit the session enter quit and then press .
• To start a Jupyter Notebook instead of a Sage console, run the command 'sage -n jupyter', then select 'New'
• HELP takes you to tutorials etc
• For usage refer to LTK-SageMath.

Rust

Basics

• rustc is the compiler for the Rust programming language, provided by the project itself, takes your source code and produce binary code, either as a library or executable
• cargo the package manager and build system
• To see how cargo calls rustc, you can do cargo build --verbose, and it will print out each rustc invocation.
• rustup is the installation tool

Rust installation

Intro - Rust's rustup

• Rustup
• rustup is a toolchain multiplexer. It installs and manages many Rust toolchains and presents them all through a single set of tools installed to ~/.cargo/bin.
• The rustc and cargo executables installed in ~/.cargo/bin are proxies that delegate to the real toolchain.
• rustup then provides mechanisms to easily change the active toolchain by reconfiguring the behavior of the proxies.

Intro - the Debian view

• wiki.debian.org/Rust
• debcargo, tool for packaging Rust crates into Debian systems

• [source]
• [source.debian-packages]
• directory = "/usr/share/cargo/registry"
• [source.crates-io]
• replace-with = "debian-packages"

Installation

• https://rust-lang.github.io/rustup/ for info
• https://rustup.rs/ explains to run 'curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh' .

info: downloading installer
Welcome to Rust!
This will download and install the official compiler for the Rust programming language, and its package manager, Cargo.

Rustup toolchains and metadata are installed into the Rustup home directory, located at:  /home/marc/.rustup  - can be modified with the RUSTUP_HOME environment variable 
The Cargo home directory is located at:  /home/marc/.cargo - can be modified with the CARGO_HOME environment variable

The cargo, rustc, rustup and other commands will be added to Cargo's bin directory, located at:  /home/marc/.cargo/bin

This path will then be added to your PATH environment variable by modifying the profile files located at /home/marc/.profile and/or /home/marc/.bashrc. 

You can uninstall at any time with rustup self uninstall and these changes will be reverted.

Current installation options:

   default host triple: x86_64-unknown-linux-gnu
     default toolchain: stable (default)
               profile: default
  modify PATH variable: yes

1) Proceed with installation (default)
2) Customize installation
3) Cancel installation

info: profile set to 'default'
info: default host triple is x86_64-unknown-linux-gnu
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: latest update on 2023-10-05, rust version 1.73.0 (cc66ad468 2023-10-03)
info: downloading component 'cargo'
  7.8 MiB /   7.8 MiB (100 %)   2.3 MiB/s in  3s ETA:  0s
info: downloading component 'clippy'
info: downloading component 'rust-docs'
 13.8 MiB /  13.8 MiB (100 %)   3.2 MiB/s in  4s ETA:  0s
info: downloading component 'rust-std'
 24.7 MiB /  24.7 MiB (100 %)   2.2 MiB/s in 11s ETA:  0s
info: downloading component 'rustc'
 61.6 MiB /  61.6 MiB (100 %)   2.5 MiB/s in 25s ETA:  0s
info: downloading component 'rustfmt'
info: installing component 'cargo'
info: installing component 'clippy'
info: installing component 'rust-docs'
 13.8 MiB /  13.8 MiB (100 %)   8.0 MiB/s in  1s ETA:  0s
info: installing component 'rust-std'
 24.7 MiB /  24.7 MiB (100 %)  17.2 MiB/s in  1s ETA:  0s
info: installing component 'rustc'
 61.6 MiB /  61.6 MiB (100 %)  19.1 MiB/s in  3s ETA:  0s
info: installing component 'rustfmt'
info: default toolchain set to 'stable-x86_64-unknown-linux-gnu'

stable-x86_64-unknown-linux-gnu installed - rustc 1.73.0 (cc66ad468 2023-10-03)

Rust is installed now. Great!

To get started you may need to restart your current shell. 
This would reload your PATH environment variable to include Cargo's bin directory ($HOME/.cargo/bin).

To configure your current shell, run: source "$HOME/.cargo/env"   // 'help source' : Execute commands from a file in the current shell.

Installation outcome

GrayTiger

• GrayTiger's main Rust directories
• GrayTiger's Rust toolchains where you find cargo and rustc in /bin
• GrayTiger's cargo directories
• GrayTiger's main Rust directories

BlackTiger

• BlackTiger's main Rust directories

Omid's SP-MAC-EQ in Rust

Round 1 on GrayTiger

cargo build --verbose
info: syncing channel updates for 'nightly-2021-09-20-x86_64-unknown-linux-gnu'
info: latest update on 2021-09-20, rust version 1.57.0-nightly (5ecc8ad84 2021-09-19)
info: downloading component 'cargo'
info: downloading component 'clippy'
info: downloading component 'rust-docs'
info: downloading component 'rust-std'
info: downloading component 'rustc'
info: downloading component 'rustfmt'
info: installing component 'cargo'
info: installing component 'clippy'
info: installing component 'rust-docs'
info: installing component 'rust-std'
info: installing component 'rustc'
info: installing component 'rustfmt'
    Updating crates.io index
error: failed to select a version for the requirement `tonic = "^0.10.0"`
candidate versions found which didn't match: 0.8.3, 0.8.2, 0.8.1, ...
location searched: crates.io index
required by package `SP-MAC-EQ v0.1.0 (/home/marc/OPTEE_GT/optee_rust/examples/SP-MAC-EQ)`

• The failed requirement for tonic is stated in the 'Cargo.toml' file under dependencies. Tonic is an implementation of the gRPC framework, see https://crates.io/crates/tonic and https://grpc.io/.
• Feedback from Cargo includes 'location searched: crates.io index'
• At https://crates.io/crates/tonic/versions you find there have so far been 38 versions of Tonic, with the most recent being 0.10.2, from September 28, 2023
• Tonic version 0.10.0 is available at crates.io, and dates back to September 1, 2023
• So why does this fail?
• There's also 'candidate versions found which didn't match: 0.8.3, 0.8.2, 0.8.1, ...' - why, what version do we actually need??? All these 0.8.* versions are also listed at crates.io...
• According to the doc you can find detailed info in file 'Cargo.lock' - however, in /SP-MAC-EQ there is no such file (plenty of such files in other dirs)
• According to https://blog.illixion.com/2021/10/fix-failed-to-select-a-version-cargo/, 'Apparently, Cargo can sometimes get into a state where its local registry cache will corrupt itself, and Cargo won’t be able to discover new versions of the dependencies. To resolve this, delete the ~/.cargo/registry folder and run the build command again.'

• Consider https://wiki.debian.org/Rust, which has a statement about 'To only use the local (Debian) version of crates, place the following snippet in a .cargo/config file at your projects' root: ' ... '.. and install any of its crate dependencies via apt install librust-CRATE-dev (or declare them in debian/control if it's for a package). '
• So:
  • What local Debian versions of crates are already in place?
  • List: Synaptics shows many librust-... libraries are available, including librust-crates-io-dev, librust-cargo-..., ... XXXXXXXXXXXXXXXXXXXX
  • Do I have 'librust-CRATE-dev ', or can I do 'apt install librust-CRATE-dev'?

X-server and Wayland

BlackTiger - Debian 10 Buster

• Approach 1: 'echo $XDG_SESSION_TYPE' ---> returns 'X11'
• Approach 2: 'loginctl' returns , then 'loginctl show-session -p Type' ---> returns 'X11'

• ldm is the X11 Light Display Manager
• there are config files on BlackTiger in /etc/lightdm: keys.conf, lightdm.conf (barebones), lightdm-gtk-greeter.conf, users.conf
• So BlackTiger was installed with X11 and lightdm
• lightdm homepage on github
• Debian lightdm manpage
• You can use the dm-tool (see https://manpages.debian.org/buster/lightdm/dm-tool.1.en.html) to lock the screen ('dm-tool lock')
• ldm is the LTSP display manager (Linux Terminal Server Project), an X11 display manager (similar to xdm, gdm and kdm), but unlike those it wraps the X11 traffic within an SSH tunnel to provide a secure login mechanism for remote X sessions.

Wayland

X11

• X, the so-called X-server (e.g. XF86 or MetroX) is in fact the display and keyboard server;
• the window manager (e.g. fvwm1, fvwm2, fvwm95, olwm, mwm (motif or lesstif), kde's wm) is a special client that draws the windows for the other Xclients;
• Xclients are all these Xapplications.

Customization of XF86, the X-server

What have we got to start with in case of Red Hat?

V.102.2 Initial customization via .Xclients

Created a .Xclients in my home directory of root (/root/.Xclients). If there is already an existing .Xclients file, save this as .Xclients.original. I'm sure you know you can verify the existence of . files via 'ls -a'. In my customized .Xclients file, I specified a minimal set-up of clients, and I start fvwm (rather than fvwm5).

V.102.3 Desktop customization via system.fvwmrc

Summary of configarable items

===> If your Xserver hangs, you can use Cntl-Alt-Backspace to kill it.
  Part 2 : fvwm - the window manager

CI 3 : /etc/X11/fvwm/system.fvwmrc
Overall window manager & desktop settings. Here you call the executable program from the menu option.

CI 4 /root/.Xclients :
--- use the xsetroot command to set the root window ---
 

Part 3 : individual application settings

... to be further elaborated ...
 

SuSe and SaX

SuSe's SaX will write your XF86Config into /etc/X11/XF86Config. So if you want to reuse the pre-toothbrush XF86Config, I guess you'll have to write it there... For some odd reason, the old XF86Config file does not seem to work. Fortunately SaX is pretty good. Running "startx" will create server logfiles in "/root/Serverlog".

KDE

X goodies

Remote desktop - VNC and Krdc

Server

• X11VNC is common under KDE, Vino is the default Gnome server
• install via sudo apt-get install x11vnc
• start server without password (not recommended) x11vnc -forever -rfbport 5900
• better to (1) create password:
  • mkdir ~/.vnc
  • x11vnc -storepasswd YOUR_PASSWORD ~/.vnc/x11vnc.pass
  Then start server using the password
  • x11vnc -forever -rfbport 5900 -rfbauth ~/.vnc/x11vnc.pass -o ~/.vnc/x11vnc.log -loopbg -display :0
  • put "/usr/bin/x11vnc -forever -rfbport 5900 -rfbauth ~/.vnc/x11vnc.pass -o ~/.vnc/x11vnc.log -loopbg -display :0" in X11VNCstartscript

Client

• install via sudo apt-get install krdc
• use via icon or invoke as krdc vnc://
• connecting to a Windows server: krdc rdp://: (mind you: 'rdp')

Audio, sound, music

AV Linux

Clevo Debbybuster

ALSA

ALSA intro

ALSA and hardware

• check /proc/asound/cards: 'cat /proc/asound/cards' - on GrayTiger:

  0 [Generic    ]: HDA-Intel - HD-Audio Generic
                   HD-Audio Generic at 0xd04c8000 irq 76
  1 [Generic_1  ]: HDA-Intel - HD-Audio Generic
                   HD-Audio Generic at 0xd04c0000 irq 77
  

  • The numbers to the left indicate the card number. This means hw:0 and hw:1 are GrayTiger's the ALSA device names.

• But this doesn't tell the whole story. There may be multiple devices per card, aplay -l shows:

**** List of PLAYBACK Hardware Devices ****
card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: Generic [HD-Audio Generic], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Generic_1 [HD-Audio Generic], device 0: ALC293 Analog [ALC293 Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0

• card 0:device 3: HDMI 0 ---> hw:0,3
• card 0:device 7: HDMI 1 ---> hw:0,7
• card 1:device 0: ALC293 Analog ---> hw:1,0
• Note that there is also a subdevice level. It appears that the general form is hw:card,device,subdevice. If you leave subdevice or device off, it assumes 0.
• So on GrayTiger: try hw:1,0 first
• sox -b 16 -n test.wav rate 44100 channels 2 synth 1 sine 440 gain -1
• aplay -D hw:1 test.wav
• ---> 'aplay: main:830: audio open error: Device or resource busy' ---> which means someone else (like pulseaudio) is using the soundcard. In that case "-D pulse" might work.
• ---> 'echo "suspend 1" | pacmd' ---> suspends pulseaudio
• aplay -D hw:1 test.wav
• ---> ok, works
• ---> 'echo "suspend 0" | pacmd' ---> unsuspends pulseaudio

ALSA config files

• Alsa GrayTiger config files
• alsa and asoundrc info

ALSA utilities

• alsamixer, an ncurses-version of amixer, shows you what you've got available
• alsactl is a way to save settings for your device (?)
• amixer is a command line app which allows adjustments to be made to a devices volume and sound controls
• The aconnect and aseqview applications are for making MIDI connections and viewing the list of connected ports.
• aconnect connects/disconnect two existing ports on the ALSA sequencer system. The ports with the arbitrary subscription permission, such as created by aseqview, can be connected to any (MIDI) device ports using aconnect. For example, to connect from port 64:0 to 65:0, run as follows: 'aconnect 64:0 65:0'
• To list ports: 'aconnect -i' and 'aconnect -o'
• To remove all existing exported connections: 'aconnect -x', useful for terminating the ALSA drivers, because the modules with sequencer connections cannot be unloaded unless their connections are removed.
• aseqview: as explained on https://tracker.debian.org/pkg/aseqview : removed from Debian
• The aplay and arecord applications are for commandline playback and recording of a number of file types including raw, wave and aiff at all the sample rates, bitdepths and channel counts known to the ALSA library - DebbyBuster: ALC293 Analog
• aplay - switch -l will list playback devices

PulseAudio - by default present on GrayTiger

• To find out if it's running: 'pgrep -a pulseaudio'
• ---> GrayTiger: '1707 /usr/bin/pulseaudio --daemonize=no --log-target=journal'

• pasuspender -- jackd -d alsa --device hw:1 --rate 44100 --period 128
• echo "suspend 1" | pacmd // to unsuspend: echo "suspend 0" | pacmd
• If you'd like to get rid of pulseaudio at boot, edit /etc/pulse/client.conf and set autospawn to no: 'autospawn = no'. After a reboot, pulseaudio will not come up unless you ask for it manually: $ pulseaudio --start

Linux sound files

• GrayTiger /usr/share/sounds directory with sf2, sf3, etc

JACK

• Jackaudio.org - main site

Installation - JACK1 or JACK2?

• Run the jackdaemon: 'jackd -d alsa --device hw:1 --rate 44100 --period 128'
• ---> The playback device "hw:1" is already in use. Please stop the application using it and run JACK again
• ---> Might be due to pulseaudio - try 'echo "suspend 1" | pacmd' but that makes no change .., Might be due to open Audacity, fluidsynth, qsynth, ...
• ---> ps -e | grep fluidsynth ---> PID 418885 ---> sudo kill 418885 ---> jackd -d alsa --device hw:1 --rate 44100 --period 128 ---> starts ok now
• Test jack: install 'jack-tools' via Synaptics
• Generate a .wav file: 'sox -b 16 -n test.wav rate 44100 channels 2 synth 1 sine 440 gain -1'
• Tell jack-play what JACK port to connect to via the JACK_PLAY_CONNECT_TO environment variable: 'export JACK_PLAY_CONNECT_TO=system:playback_%d'
• Note: The "%d" is expanded to the channel number while connecting. So, with a stereo WAV file and the above value, jack-play will connect to system:playback_1 and system:playback_2.
• Test jack: 'jack-play test.wav'
• Stop jack: 'killall jackd'

JACK2 config and qjackctl

JACK2 config and .jackdrc - Ted Felix approach

Jack and FluidSynth

Run fluidsynth with Jack - Ted Felix approach

• First use aplaymidi to find out what port number fluidsynth is waiting on: '$ aplaymidi -l'
• If fluidsynth is on port 128: 'aplaymidi -p 128:0 song.mid'
• On GrayTiger: aplaymidi -p 128:0 '/home/marc/Documents/Alpha/002-Sel Marc prive/201-MLS-Guitar/Z_MIDI_files/bach_846.mid'

JACK2 config - complementary info

• JACK set up managers, which allow you to start up JACK with specific settings
• JACK connection managers, which primarily deal with making connections

qjackctl

• qjackctl.sourceforge.io
• local: /usr/share/doc/qjackctl - start through gnome desktop, but it needs to be configured

Configuration on GrayTiger with qjackctl - jackdbus

Configuration on GrayTiger with qjackctl - legacy

• Error 'unable to connect to server'

16:21:48.096 JACK is starting...
16:21:48.102 /usr/bin/jackd -dalsa -dhw:0 -r44100
Cannot connect to server socket err = No such file or directory
---> note that hw:0 should be hw:1 on GrayTiger

• Change interface from default to ALC293 - starting now possible.
• Configuring connections: start qjackctl, setup/settings/misc, 'replace connections with graph button' was activated by default - deactivate this to get the simple connections button used in the beginners guide

• Before getting started with JACK, be sure to close any audio applications you've been using. xxx continue here with Ted Felix xxx

Usage

• Connection: system capture, system playback, Midi Through, ...
• Graph: system capture, system playback, Midi Through, ...
• Patchbay: input and output sockets, each can be Audio, MIDI or ALSA - to avoid making the same connections every time you start JACK, the Patchbay will automatically make the defined connections every time JACK opens.

• In Audacity you can configure JACK as 'host' (but recording then leads to error msg)
• You can start
• If you start JACK via QjackCtl, you don't hear any sound anymore, and sound programs refuse to start

Clevo Debbybuster VMPK, FluidSynth and Jack

• Kill FluidSynth - To stop fluidsynth, type "quit" at its ">" prompt. Or 'ps -e | grep fluid' and kill the process.
• Kill Jack - 'killall jackd'
• Kill pulseaudio - 'echo "suspend 1" | pacmd'
• Try 'aconnect -x'.

Clevo Debbybuster Pipewire

[E][000048160.516447][module-protocol-native.c:575 lock_socket()] server 0x563dfed421b0: unable to lock lockfile '/run/user/1000/pipewire-0.lock': Resource temporarily unavailable (maybe another daemon is running)
[E][000048160.516548][impl-module.c:281 pw_context_load_module()] "/usr/lib/x86_64-linux-gnu/pipewire-0.3/libpipewire-module-protocol-native.so": failed to initialize: Resource temporarily unavailable
[E][000048160.516612][main.c:126 load_module()] daemon 0x7ffc2e91d0c0: could not load module "libpipewire-module-protocol-native": Resource temporarily unavailable
[E][000048160.516628][main.c:441 main()] failed to load modules: Resource temporarily unavailable

Samson USB microphone

• Samson G track Pro USB Audio - Headset
• Samson G track Pro USB Audio - Internal

Audacity

Installations

• Linux: in 2022-01, DebbyBuster had Audacity 2.2.2 installed, via Synaptics.
• Windows: in 2024-03, HP Envy had Audacity 3.4.2 installed, which uses .aup3 file format, incompatible with Audacity version prior to 3.

• cd /usr/marc/Downloads/Audacity
• ./audacity....

Using USB turntable

AV Linux

Muse Sounds Manager/Muse Score

Muse Sounds Manager

Muse Score Studio

Muse Score on GrayTiger

• Local installation files on GrayTiger - see also Synaptics info

/usr/bin/mscore
/usr/bin/musescore
/usr/share
/usr/share/applications
/usr/share/applications/mscore.desktop
/usr/share/doc
/usr/share/doc/musescore

• remove Muse Score 2 using Synaptics, then
• download from https://github.com/musescore/MuseScore/releases into /home/marc/Downloads/MuseScore_4

Muse Score 4 on AV Linux

Guitarix

Tux-guitar

Impro-Visor

• cd /Downloads/Impro-Visor
• chmod +x Impro-Visor_unix_5_16.sh
• ./Impro-Visor_unix_5_16.sh
• Outputs in /home/marc/Impro-Visor10.2

Rosegarden

Hydrogen

Obtain more drumkits

.h2drumkits

Ubuntu

GSequencer - dropped

Amarok

Rythmbox

• file:///home/marc/.local/share/rhythmbox/ e.g. file rhythmdb.xml

• ~/.local/share/rhythmbox
• ~/.cache/rhythmbox - this is where e.g. album art is cached
• ~/.gconf/apps/rhythmbox

iPod

iPod Classic/GTKPOD

File conversion towards mp3

Legacy

• kernel log: "write access to a journaled filesystem is not supported, use the force option at your own risk, mounting readonly."

• mount output: "/dev/sdi2 on /media/SiLVER type hfsplus (rw,nosuid,nodev,uhelper=hal)"

Networking

NET-3

Intro

Basic choices to be made

• 127.0.0.1 for the loopback interface
• 10.0.0.1 if Kassandra acts as a ppp server via nullmodem, this Class A address automatically uses 255.0.0.0 as netmask. And the IP address of your host is also stored in /etc/hosts.

/etc/rc.d/init.d/network : initial script that verifies the existence of /etc/sysconfig/network, which contains definitions like e.g. HOSTNAME=Kassandra. If it finds it, it cd's to /etc/sysconfig/network-scripts, where the configuration scripts (e.g. ifup-routes etc...) reside.
 

Traceroute - tracepath

DNS - nslookup - ksoa

DNS on Kassandra (RH 5.0):

On Toothbrush (SuSE 5.3):

On boy (SuSE 6.0):

nslookup - ksoa

DNS on malekh

• www.dns.be (under 'domain index' you find name servers for all ISP's registered in Belgium
• auth00.ns.be.uu.net - 194.7.1.9

• auth50.ns.be.uu.net - 194.7.15.66

Serial communication/nullmodem

Com ports

• COM1 out = /dev/cua0
• COM1 in = /dev/ttyS0
• COM2 out = /dev/cua1 ... (cfr Linux Serial-HOWTO)

Incoming traffic : getty -mingetty-

securetty

Minicom

Basics Documentation:

• /dev/modem (if the link has been set)
• /dev/cua0 or cua1 (on Borsalino /dev/cua1 was the external serial interface)
• ---> apparently since kernel 2.2, cua is no longer used, it became /dev/ttyS...
• /dev/ttyS0 (on Avina this is the external serial interface)
• /dev/ttyS2 (on Aviana this is the pcmcia card modem)

Minicom configuration

1. by running it with the -s switch: minicom -s
2. once within minicom, use Alt-O or Cntl-A O (cOnfigure?)

Minicom trouble shooting

1. identify the locking PID in the logfile and kill it: one way is to peek inside "/var/lock/LCK..cua1" here you'll find a PID. Kill it with e.g. "kill -n 9 PID".
2. reboot the machine.

ppp

PPP basics

1. Ensure dhcp-client has been stopped, e.g. /sbin/init.d/dhclient stop - or /etc/init.d/...
2. Via minicom, dial out
3. Logon to your ISP machine using your uid/psw
4. [Optionally, you may need to start the pppd server on the ISP side (but this is rare)]
5. Quit minicom without resetting the modem (Cntl-A Q or Alt-Q)
6. Start pppd as a client, e.g.:
   1. cd /usr/lib/ppp
   2. pppd -d -detach/dev/____ &
7. Optionally, you may need to define the ppp link as the default outgoing route. Do this in three steps:
   1. ifconfig will show you the other side of the ppp link, e.g. P-t-P: 193.74.1.238
   2. now do: route add default gw 193.....
   3. ping, e.g. your name server (cfr /etc/resolv.conf)
8. check again with ifconfig, netstat, pppstats
9. start your browser
10. terminate with ppp-off.

PPP : info via control panel/package manager

PPP server via nullmodem

PPP on malekh

• Point minicom to the serial device /dev/ttyS0 (serial port) or ttyS2 (typically PCMCIA)....!
• Reset /etc/resolv.conf (e.g. from /etc/resov.conf.original) - careful with SuSe, which starts from /etc/rc.config for name server configuration etc
• If running, stop your dhcp client'/sbin/init.d/dhclient stop' - or /etc/init.d/... (pppd will allocate the IP address)
• Launch ppp with "pppd -d -detach /dev/ttyS0 &" or ttyS2...!
• Use "ifconfig" and "route add default gw ..."

• If you want to surf, let Netscape use a direct link, no proxies (Edit/preferences/advanced/proxy)

tcpdump

tcpdump introduction

• IP hdr includes 8 bit 'protocol'field, where 1=ICMP, 2=IGMP, 6=TCP, 17=UDP.

• TCP/UDP hdr include the port numbers, with well-known ports defined in /etc/services.

tcpdump on malekh

• -v and -vv for very verbose
• -e print link-level header on each line
• -s snaft snaplen bytes of data rather than the 68 bytes default
• -a convert addresses into names - seems to generate nice output for SMB

• expression: here you can specify e.g. TYPE: 'host foo', 'net 10.54', 'port 23', or DIRection: 'src foo', 'dst net 10.54', or PROTO: 'tcp port 21'

iptraf

cmu-snmp

Firewalls

dhcp - proxy servers - Brussels/KL - c4.net

General information on dhcp

• the dhcp server is "dhcpd", reading configuration information from "/etc/dhcpd.conf" and keeping track of leases in "dhcp.leases". Address pools are allocated per subnet.

• the dhcp client is "dhclient", reading configuration info from "/etc/dhclient.conf".

• /etc/init.d/dhclient
• /etc/dhclient.conf
• man dhclient

• man dhclient.conf

• dhcpd (the server himself)
• /etc/dhcpd.conf (config file)
• man dhcpd
• man dhcpd.conf

• man dhcpd.leases

malekh - dhclient at PwC Brussels/KL

• contains information on what is expected from the dhcp server (subnet mask, broadcast address, dns, ...)

• points to "/sbin/dhclient-script" where various "ifconfig" and "route add" commands are executed.

• the W95 box' own IP address (obtained via dhcp) is e.g. 10.54.18.216
• the corresponding subnetmask is 255.255.252.0
• the default gw is 10.54.16.2
• dns and dhcp server are combined on 10.54.20.40

• the outgoing proxy is found at 10.54.14.10 (used to be 10.54.20.04)

malekh - dhclient & server -v'portable'

• parameters, e.g. how long lasts a lease, provide addresses to unknown clients, make suggestions with regard to default gw's, ...

• declarations, e.g. describing the topology, the clients, the addresses they can use, ... This includes shared and subnet declarations.

Some core decisions for c4.net, taking into account the IPv4 address is 32 bits long, composed of network number and host number. Let's select a class B network address. This means: '10''--14-bits-network''---16-bits-host---', which makes 32 bits altogether. Class B ranges from 128.* to 191.* .

According to the rules for private networks (RFC1918), for class B, we can select between '172.16.0.0' and '172.31.255.255'. The standard subnetmask for class B is '255.255.0.0'.

So let it be: network '172.16.0.0', addresses ranging '172.16.0.10..20', with a subnetmask of '255.255.0.0'. Save this in '/etc/dhcpd.config'.

Two alternatives to start dhcpd:

1. by updating '/etc/rc.config' (start dhcpd) and running '/sbin/SuSEconfig', or

2. by '/sbin/init.d/dhcpd start'.

The second alternative is preferred. HOWEVER this runs into problems. The dhcpd parameters conflict with what's already defined in /etc/rc.config as IP address. SOLUTION:

1. Manually stop your dhcp client'/sbin/init.d/dhclient stop';

2. Manually 'ifconfig/ eth0 172.16.0.1'

Starting & stopping the dhcp server:

• Starting up the dhcp server: '/sbin/init.d/dhcp start'.

• Shutting down the dhcp server: '/sbin/init.d/dhcp stop'.

Starting & stopping the dhcp client:

• Starting up the dhcp client: '/sbin/init.d/dhclient start'.

• Shutting down the dhcp client: '/sbin/init.d/dhclient stop'.

VI.111.4 avina - dhclient

DHCP client is by default not installed, instead the DHCP server was automatically installed. Used YaST to remove the server and install the client. Then use Yast1 to configure and activate it.

VI.111.5 Overview of proxy servers

• PwC Belgium: proxy-be, or 10.54.20.4 (remember to enable SSL 40-bit ! )

• PwC UK: 10.44.240.41:80

• PwC Australia: 10.140.10.2

VI.112 diald

PCMCIA support

Intro - PCMCIA on boy - SuSE 6.0

Howto in "/usr/doc/howto/en/PCMCIA-HOW.gz". SuSE uses a Sys V init editor's "initscript". However, I don't find a script to start pcmcia. Script should be "/sbin/init.d/pcmcia". I don't have the script, I assume pcmcia is not installed.

PCMCIA installation on boy - SuSE 6.0

• SuSE 6.0 manual p. 339 explains that "/etc/rc.config" defines whether the pcmcia subsystem is launched at boot time (PCMCIA=i82365 or tcic - whatever that means).
• there exists /etc/pcmcia, which contains e.g. sample config files from David Hinds.
• Howto: "/usr/doc/howto/en/PCMCIA-HOW.gz"
• Package documentation: "/usr/doc/packages/pcmcia/..." - here file SUPPORTED.CARDS explicitly states that my 3COM 3C589C is supported. In fact, it's on the top of the list. The Howto in this directory states that virtually all cards are i82365.
• SuSE's pcmcia start-up config is kept in "/etc/rc.config", with "/sbin/init.d/pcmcia" as the start-up script.
• Programs include: cardmgr, cardinfo
• Helpful: lsmod

VI.113.3 PCMCIA on malekh SuSE 6.1

QUESTION: How to install PCMCIA services?

Remember that pcmcia is a package of the 'a' series. Some fact finding:

• No variable found in /etc/rc.config (should be PCMCIA="82365").

• No references to pcmcia in the system log /var/log/messages .

• Neither in /var/log/boot.msg .

• No beep at boot time.

• No reference to pcmcia in /var/adm/inst-log/installation-990828 .

• Insertion results in two high beeps, in rapid succession.
• The log shows that an "insmod /...../3C589_cs.o" happens.
• After that, the script "network start" is executed.
• The cardinfo utility reports a 3C589 card.

• Insertion results in a first beep,followed by another one various seconds later. So there's a difference there...
• The log shows an "insmode /..../xirc2ps_cs.o" happens.
• Then "insmode /..../serial_cs.o" happens as well.
• After that, script "network start eth0" is executed. Options are read from /etc/pcmcia/network.opts.
• And script "serial start ttyS3". Options are read from /etc/pcmcia/serial.opts.
• However, there is no feedback to be found after the execution of the scripts.
• File /var/run/stab contains an entry for socket 1, stating the card is ttyS3, major node 4, minor node 67
• Cardinfo reports a Xircom CEM56, both as eth0 and ttys3 as serial device. So the type is not entirely correct (CEM56 versus CEM56-100).
• Also, "file /dev/modem" reveals it is a link to /dev/cua3. That looks OK.
• Still,/ Minicom (or Seyon) does not seem to find it.
• The PCMCIA HOWTO states that a single beep means the card was identified successfull. The second beep would mean the configuration went OK. This second beeps takes quite a while on malekh. The HOWTO suggests to run "sh -x /etc/pcmcia/serial start ttyS3". Which runs fine, ending in linking cua3 to modem. So far so good.
• Still, Minicom doesn't find it.
• ...maybe the problem's due to me using a CEM56-100, rather than a simple CEM56.

• Running "cardctl scheme" informs me that I have the default scheme.
• File /var/run/pcmcia-scheme is empty...STRANGE...

• Running "setserial /dev/modem" shows I have a UART 16550A, port ..., IRQ 5.

VI.113.4 PCMCIA on avina SuSE 6.4

VI.113.5 PCMCIA on imagine SuSE 7.2

xnetload - ntop

SAMBA - smbclient

• smbd, the server daemon, configured via smb.conf, handles file & print services
• nmdb, the netbios name services daemon, can also be used interactively to query various name servers

• /etc/smb.conf (configuration file, mainly oriented towards the server-side)

• smbclient, a client that allows to access SMB shares e.g. in a WfWG environment - try "man smbclient"...
• various other utilities such as smbprint, smbtar (dumping smb shares directly into tar), ...
• testparm (a test utility)

• smbstatus

1. use smbclient to work on a windows share (e.g. Win2000-Kassandros)

2. use smbd to let a windows client access an avina 'share'

• "smbstatus": not very helpful

• "smbclient -L kassandros" : does not get you very far due to security

• "smbclient -L kassandros -U administrator" : if then you provide the right password, you get a list of shares back

• "smbclient //kassandros/tux -U administrator" : provide the psw, and you have access to /tux

• use the -l flag e.g. "smbclient ... -l logfilename" to enable logging

• use the -d flag e.g. "smbclient ... -d 3" to see debug messages in the log files
  • use "?" to list the possible commands now

• "mkdir / mget (kassandros -> tux) / mput (tux -> kassandros) / ls ..."

• "recurse" to turn recursion on/off for directory operations

• "mask" to define exactly what is mget/mput when recurse is "on" (?)

• "lcd" to position your local directory

• "exit" to quit

• Before using "smbclient", the Linux box needs to be able to resolve kassandros into 10.0.0.5 . A simple way is by editing "/etc/hosts" on Linux, and entering there the IP address that kassandros got from the dhcp server (on W2000, use "ipconfig" to learn kassondros' IP address)
• Connect: "smbclient //kassandros/tux -U administrator" : provide the psw, and you have access to /tux - use "?" to list the possible commands ...
• General preparation:
  • "recurse" (to turn recursion on - works alright on the local side, but does not recursively create subdirs on the server side ...)
  • "prompt" (to turn prompting off)
• Adjust the local path:
  • "lcd /Java01Net" ("lcd" works on the local side)
  • "lcd" (acts as a local "pwd")
• Adjust the remote path:
  • "pwd" ("pwd" works on the remote server)
  • "mkdir /Java999"
  • "cd /Java999" ("cd" works on the remote server)
• Do the transfer:
  • "mput *.*"
  • "dir" ("dir" works on the remote server)

  • "du" ("du" works on the remote server)

• create appropriate /etc/smb.conf
• then execute "testparm"
• then update /etc/rc.config to start samba, and run SuSEconfig
• reboot to start smbd and nmdb
• * alternatively: "/etc/rc.d/init.d/smb stop | start"
• you get details in "/var/log/smb.log"
• smbstatus
• smbclient '\\TUX\HOMES' -U root ("homes" is the name of the share in /etc/smb.conf)
• smbclient '\\TUX\AAATEST' -U marcsel (must be capital letters for the service, and you must use marcsel which was enabled via smbpasswd)
• - and the access rights must allow marcsel to read/write AAATEST and subdirs ...
• used "chmod -R o+r /Kassandra_Data/*" - this seemed to do the trick

sniffit

VI.118 Networking source code

Check out /usr/src/linux..., particularly the make files and:

• tcp.c: "/usr/src/linux.../net/ipv4/tcp.c": the implementation of tcp

• ip: "/usr/src/linux.../net/ipv4/ip_input.c": the implementation of ip

Documentation can e.g. be found in "/usr/src/linux.../Documentation/networking/tcp.txt"

ISDN

Native ISDN connection

• /usr/doc/howto/en/NET-3 - contains a section on ISDN, and a pointer to a faq
• /usr/src/linux.../documentation/ISDN
• /usr/doc/packages/i4l
• /usr/doc/packages/i4ldoc: FAQ:eng-i4l-faq.html
• /usr/doc/packages/i4ldoc/howto - tutorial - ...

VI.119.2 ISDN via 3COM 3C891 ISDN LAN modem

• reset the PCMCIA card (pull it out, plug it in)
• physically connect malekh to the ISDN LAN modem
• start your dhcp client ('/sbin/init.d/dhclient start')
• use 'ifconfig' to see whether you did obtain an IP address for eth0
• you can try to ping 192.168.1.1
• point your browser to '192.168.1.1/mainpage' / alternatively, you can also telnet
• psw for 3COM could be: qdge0416

VI.120 Fax

VI.121 NFS

NFS basics

NFS components:

• portmapper (rpc.portmap or rpcbind) to map ports to rpc programs

• rpcinfo, use "rpcinfo -p", or for the remote side "rpcinfo -p 10.0.0.3".

• server-side: /etc/exports

• server-side: nfsd (sometimes called rpc.nfsd) and mountd (sometimes called rpc.mountd)

• client-side: mount/umount (you can use "-v" for verbose output, and -o timeo=n to increase the timeout value)

Of course, there is an NFS-HowTO. The "tar" seems to be the fastest way to pass files over. Debugging: on the server-side, running "rpcinfo -p" should show at least portmapper, mountd and nfsd running. You can also check /var/log/messages for daemon output. Easy way: make a tar file, export it to the client. On the client, move the tar file into "/" and untar it there.

History - NFS with tintin (compaq Philippe Dhainaut)

SAVING to tintin

Connect both tintin (NFS server) and malekh (client issuing 'mount') to a hub, then:

1. on tintin: mkdir ttmalekh, and include a line "/ttmalekh (rw)" in /etc/exports

2. on tintin: restart the nfs server

3. on malekh: mkdir tintin

4. on malekh: mount 192.168.1.3:/ttmalekh /tintin (use "-v" for verbose output, and "-o timeo=n" with default n starting at 7 increased to e.g. 21)

You can also use KDE to copy files (but it's slow).

RESTORING from tintin

Mounting on tintin from avina fails with the msg: RPC timed out. Try the other way round: On avina:

• mkdir tintin

• make sure the nfs server is started (in /etc/rc.config)

• make sure outsiders can write to /tintin; here various alternatives exist, probably best is to handle it at individual user level & via PAM, however, for the time being: simply used MC to allow "others" to write

On tintin:

• mount 192.168.1.253:/tintin /avina
• cp -r Cryptix3 /avina (where the -r stands for recursively)

• cp -r ...

NFS with tux (HP 4150)

1. on tux: mkdir TuxAvina, and include a line "/TuxAvina (rw)" in /etc/exports
2. on tux: restart the nfs server ("/sbin/init.d/nfsserver stop" "start")
3. on avina: mkdir tux
4. on avina: mount 10.0.0.5:/ttmalekh /tintin
   • => results in "mount: RPC: program not registered"
   • solution: NFS server was not started in /etc/rc.config on tux, hence update and run /sbin/SuSEconfig
   • => results in "RPC: timed out"
   • solution: simply retry (sometimes a reboot of the server machine seems to be necessary), then issue "mount"

VI.122 Wireless

VI.201 NetworkManager Kubuntu 12.10

On Angkor2, Kubuntu 12.10 comes with "NetworkManager". Good intro in Wikipedia. Documentation seems hard to find on the running Angkor2, but there is https://live.gnome.org/NetworkManager.

Cloud and virtualisation

AWS

Installation

• Start from instructions at: https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html
• Download into /Download, then sudo install, cli can be run via '/usr/local/bin/aws', or just 'aws' from Linux cli.
• Then do: https://docs.aws.amazon.com/cli/latest/userguide/getting-started-quickstart.html

Quickstart

• Access key ID
• Secret access key
• AWS Region
• Output format
• json, yaml, yaml-stream, ...
• text, table

Usage

Linux virt-manager

Linux KVM

kvm_amd               151552  0
kvm                  1085440  1 kvm_amd
irqbypass              16384  1 kvm
ccp                   114688  1 kvm_amd

ls -al /dev/kvm
crw-rw----+ 1 root kvm 10, 232 Sep 24 17:14 /dev/kvm

sudo usermod -aG kvm marc
[sudo] password for marc: 
configuration error - unknown item 'ALWAYS_SET_PATH' (notify administrator)
marc@GrayTiger:~$ sudo usermod -aG kvm $marc
configuration error - unknown item 'ALWAYS_SET_PATH' (notify administrator)
Usage: usermod [options] LOGI

Docker

Docker basics

• local Docker introduction

Docker installation

Prerequisites

• Debian Bookworm 12 (stable)
• Debian Bullseye 11 (oldstable) => GrayTiger

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package 'docker.io' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 325 not upgraded.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package 'docker-doc' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 325 not upgraded.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package 'docker-compose' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 325 not upgraded.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package podman-docker
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package 'containerd' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 325 not upgraded.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package 'runc' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 325 not upgraded.

Installation

• Docker Engine comes bundled with Docker Desktop for Linux. This is the easiest and quickest way to get started. BUT I HAVE KVM ISSUES APPARENTLY...ref above
• Set up and install Docker Engine from Docker's Apt repository.
• Install it manually and manage upgrades manually.
• Use a convenience scripts. Only recommended for testing and development environments.

Step 1

    containerd.io__.deb
    docker-ce__.deb
    docker-ce-cli__.deb
    docker-buildx-plugin__.deb
    docker-compose-plugin__.deb

Step 2

$ sudo dpkg -i ./containerd.io__.deb \
  ./docker-ce__.deb \
  ./docker-ce-cli__.deb \
  ./docker-buildx-plugin__.deb \
  ./docker-compose-plugin__.deb

sudo dpkg -i ./containerd.io_1.6.8-1_amd64.deb 
[sudo] password for marc: 
Selecting previously unselected package containerd.io.
(Reading database ... 628390 files and directories currently installed.)
Preparing to unpack .../containerd.io_1.6.8-1_amd64.deb ...
Unpacking containerd.io (1.6.8-1) ...
Setting up containerd.io (1.6.8-1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/containerd.service → /lib/systemd/system/containerd.service.
Processing triggers for man-db (2.9.4-2) ..

sudo dpkg -i ./docker-ce-cli_24.0.5-1~debian.11~bullseye_amd64.deb 
Selecting previously unselected package docker-ce-cli.
(Reading database ... 628418 files and directories currently installed.)
Preparing to unpack .../docker-ce-cli_24.0.5-1~debian.11~bullseye_amd64.deb ...
Unpacking docker-ce-cli (5:24.0.5-1~debian.11~bullseye) ...
Setting up docker-ce-cli (5:24.0.5-1~debian.11~bullseye) ...
Processing triggers for man-db (2.9.4-2) ...

sudo dpkg -i ./docker-ce_24.0.5-1~debian.11~bullseye_amd64.deb 
(Reading database ... 628615 files and directories currently installed.)
Preparing to unpack .../docker-ce_24.0.5-1~debian.11~bullseye_amd64.deb ...
Unpacking docker-ce (5:24.0.5-1~debian.11~bullseye) over (5:24.0.5-1~debian.11~bullseye) ...
Setting up docker-ce (5:24.0.5-1~debian.11~bullseye) ...
configuration error - unknown item 'ALWAYS_SET_PATH' (notify administrator)
Created symlink /etc/systemd/system/multi-user.target.wants/docker.service → /lib/systemd/system/docker.service.
Created symlink /etc/systemd/system/sockets.target.wants/docker.socket → /lib/systemd/system/docker.socket.

sudo dpkg -i ./docker-buildx-plugin_0.11.1-1~debian.11~bullseye_amd64.deb 
Selecting previously unselected package docker-buildx-plugin.
(Reading database ... 628615 files and directories currently installed.)
Preparing to unpack .../docker-buildx-plugin_0.11.1-1~debian.11~bullseye_amd64.deb ...
Unpacking docker-buildx-plugin (0.11.1-1~debian.11~bullseye) ...
Setting up docker-buildx-plugin (0.11.1-1~debian.11~bullseye) ...

sudo dpkg -i ./docker-compose-plugin_2.5.0~debian-bullseye_amd64.deb 
Selecting previously unselected package docker-compose-plugin.
(Reading database ... 628619 files and directories currently installed.)
Preparing to unpack .../docker-compose-plugin_2.5.0~debian-bullseye_amd64.deb ...
Unpacking docker-compose-plugin (2.5.0~debian-bullseye) ...
Setting up docker-compose-plugin (2.5.0~debian-bullseye) ...

Step 3

• sudo service docker start
• sudo docker run hello-world

sudo docker run hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
719385e32844: Pull complete 
Digest: sha256:88ec0acaa3ec199d3b7eaf73588f4518c25f9d34f58ce9a0df68429c5af48e8d
Status: Downloaded newer image for hello-world:latest

Hello from Docker!
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:
 1. The Docker client contacted the Docker daemon.
 2. The Docker daemon pulled the "hello-world" image from the Docker Hub. (amd64)
 3. The Docker daemon created a new container from that image which runs the executable that produces the output you are currently reading.
 4. The Docker daemon streamed that output to the Docker client, which sent it to your terminal.

To try something more ambitious, you can run an Ubuntu container with: $ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker ID: https://hub.docker.com/

For more examples and ideas, visit: https://docs.docker.com/get-started/

Files and database storage

Peeking inside a large file with less

Splitting a large file with split

The split command

• By default the outputfile's size is 1000 lines
• To have another outputfile size: specify '-b, --bytes=SIZE' to put SIZE bytes per output file

Splitting data.world L1 ttl (unnecessary if you use graphdb's server import feature

Splitting a gleif-concatenated file - first attempts - legacy

Splitting a GLEIF concatenated file with split - legacy

firefox-esr-l10n-en-gb/now 91.13.0esr-1~deb11u1 all [installed,upgradable to: 115.13.0esr-1~deb11u1]
firefox-esr/now 91.13.0esr-1~deb11u1 amd64 [installed,upgradable to: 115.13.0esr-1~deb11u1]

Install Firefox .deb package for Debian-based distributions

To install the .deb package through the APT repository, do the following:

    Create a directory to store APT repository keys if it doesn't exist: sudo install -d -m 0755 /etc/apt/keyrings
     >OK 
    Import the Mozilla APT repository signing key:
    wget -q https://packages.mozilla.org/apt/repo-signing-key.gpg -O- | sudo tee /etc/apt/keyrings/packages.mozilla.org.asc > /dev/null
    >OK, there's a key present now
    
    The fingerprint should be 35BAA0B33E9EB396F59CA838C0BA5CE6DC6315A3. You may check it with the following command:

    gpg -n -q --import --import-options import-show /etc/apt/keyrings/packages.mozilla.org.asc | awk '/pub/{getline; gsub(/^ +| +$/,""); if($0 == "35BAA0B33E9EB396F59CA838C0BA5CE6DC6315A3") print "\nThe key fingerprint matches ("$0").\n"; else print "\nVerification failed: the fingerprint ("$0") does not match the expected one.\n"}'
    >OK, matches
    
    Next, add the Mozilla APT repository to your sources list:
    echo "deb [signed-by=/etc/apt/keyrings/packages.mozilla.org.asc] https://packages.mozilla.org/apt mozilla main" | sudo tee -a /etc/apt/sources.list.d/mozilla.list > /dev/null
    >OK, included 
    
    Configure APT to prioritize packages from the Mozilla repository:

    echo '
    Package: *
    Pin: origin packages.mozilla.org
    Pin-Priority: 1000
    ' | sudo tee /etc/apt/preferences.d/mozilla
    
    >OK, or so it seems

    Update your package list and install the Firefox .deb package: sudo apt-get update && sudo apt-get install firefox
    >Results in: 
    
    sudo apt-get update && sudo apt-get install firefox
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://security.debian.org/debian-security bullseye-security InRelease   
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease                  
Hit:4 http://deb.debian.org/debian bullseye-backports InRelease                
Hit:6 https://eid.static.bosa.fgov.be/debian bullseye InRelease                
Get:7 https://dl.google.com/linux/chrome/deb stable InRelease [1,825 B]        
Hit:8 https://files.eid.belgium.be/debian bullseye InRelease                   
Hit:9 https://packages.microsoft.com/repos/ms-teams stable InRelease
Hit:5 https://packages.microsoft.com/repos/code stable InRelease
Get:10 https://packages.mozilla.org/apt mozilla InRelease [1,528 B]
Err:7 https://dl.google.com/linux/chrome/deb stable InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E88979FB9B30ACF2
Get:11 https://packages.mozilla.org/apt mozilla/main all Packages [12.8 MB]
Get:12 https://packages.mozilla.org/apt mozilla/main amd64 Packages [227 kB]
Fetched 13.1 MB in 6s (2,113 kB/s)                                             
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://dl.google.com/linux/chrome/deb stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E88979FB9B30ACF2
W: Failed to fetch https://dl.google.com/linux/chrome/deb/dists/stable/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E88979FB9B30ACF2
W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  firefox
0 upgraded, 1 newly installed, 0 to remove and 395 not upgraded.
Need to get 70.3 MB of archives.
After this operation, 254 MB of additional disk space will be used.
Get:1 https://packages.mozilla.org/apt mozilla/main amd64 firefox amd64 128.0.3~build1 [70.3 MB]
Fetched 70.3 MB in 24s (2,912 kB/s)                                            
Selecting previously unselected package firefox.
(Reading database ... 639502 files and directories currently installed.)
Preparing to unpack .../firefox_128.0.3~build1_amd64.deb ...
Unpacking firefox (128.0.3~build1) ...
Setting up firefox (128.0.3~build1) ...
Processing triggers for mailcap (3.69) ...
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for gnome-menus (3.36.0-1) ...
    
    

sudo dmesg -k

info: syncing channel updates for 'nightly-x86_64-unknown-linux-gnu'
info: latest update on 2023-10-13, rust version 1.75.0-nightly (e20cb7702 2023-10-12)
info: downloading component 'cargo'
  7.7 MiB /   7.7 MiB (100 %)   2.8 MiB/s in  2s ETA:  0s
info: downloading component 'clippy'
info: downloading component 'rust-docs'
 14.4 MiB /  14.4 MiB (100 %)   3.1 MiB/s in  4s ETA:  0s
info: downloading component 'rust-std'
 26.5 MiB /  26.5 MiB (100 %)   2.6 MiB/s in 10s ETA:  0s
info: downloading component 'rustc'
 55.6 MiB /  55.6 MiB (100 %)   2.6 MiB/s in 20s ETA:  0s
info: downloading component 'rustfmt'
info: installing component 'cargo'
info: installing component 'clippy'
info: installing component 'rust-docs'
 14.4 MiB /  14.4 MiB (100 %)   6.1 MiB/s in  1s ETA:  0s
info: installing component 'rust-std'
 26.5 MiB /  26.5 MiB (100 %)  17.2 MiB/s in  1s ETA:  0s
info: installing component 'rustc'
 55.6 MiB /  55.6 MiB (100 %)  19.4 MiB/s in  2s ETA:  0s
info: installing component 'rustfmt'
info: default toolchain set to 'nightly-x86_64-unknown-linux-gnu'

  nightly-x86_64-unknown-linux-gnu installed - rustc 1.75.0-nightly (e20cb7702 2023-10-12)

info: downloading component 'rust-std' for 'x86_64-fortanix-unknown-sgx'
info: installing component 'rust-std' for 'x86_64-fortanix-unknown-sgx'
 20.2 MiB /  20.2 MiB (100 %)  16.7 MiB/s in  1s ETA:  0s

echo "deb https://download.fortanix.com/linux/apt xenial main" | sudo tee -a /etc/apt/sources.list.d/fortanix.list >/dev/null
curl -sSL "https://download.fortanix.com/linux/apt/fortanix.gpg" | sudo -E apt-key add -
sudo apt-get update
sudo apt-get install intel-sgx-dkms

docker: unknown server OS: .
See 'docker run --help'.

sudo docker run --detach --restart always --device /dev/isgx --volume /var/run/aesmd:/var/run/aesmd --name aesmd fortanix/aesmd
Unable to find image 'fortanix/aesmd:latest' locally
latest: Pulling from fortanix/aesmd
40908747a28d: Pull complete 
Digest: sha256:53c3dee56f32922ce807aedc8fe8653ca6c03d8c16991779f2e903d8b408d7a1
Status: Downloaded newer image for fortanix/aesmd:latest
a73e63bdd4ca8685bbbec8a559d305f4c69f93df961fe97267de174230821d27
docker: Error response from daemon: error gathering device information while adding custom device "/dev/isgx": no such file or directory.

sudo apt-get install pkg-config libssl-dev protobuf-compiler
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
pkg-config is already the newest version (0.29.2-1).
pkg-config set to manually installed.
The following additional packages will be installed:
  libprotobuf-dev libprotobuf-lite23 libprotobuf23 libprotoc23 libssl1.1
Suggested packages:
  libssl-doc protobuf-mode-el
The following NEW packages will be installed:
  libprotobuf-dev libprotoc23 libssl-dev protobuf-compiler
The following packages will be upgraded:
  libprotobuf-lite23 libprotobuf23 libssl1.1
3 upgraded, 4 newly installed, 0 to remove and 322 not upgraded.
Need to get 6,632 kB of archives.
After this operation, 23.1 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://deb.debian.org/debian bullseye/main amd64 libssl1.1 amd64 1.1.1w-0+deb11u1 [1,566 kB]
Get:2 http://deb.debian.org/debian bullseye/main amd64 libprotobuf23 amd64 3.12.4-1+deb11u1 [891 kB]
Get:3 http://deb.debian.org/debian bullseye/main amd64 libprotobuf-lite23 amd64 3.12.4-1+deb11u1 [242 kB]
Get:4 http://deb.debian.org/debian bullseye/main amd64 libprotobuf-dev amd64 3.12.4-1+deb11u1 [1,234 kB]
Get:5 http://deb.debian.org/debian bullseye/main amd64 libprotoc23 amd64 3.12.4-1+deb11u1 [802 kB]
Get:6 http://deb.debian.org/debian bullseye/main amd64 libssl-dev amd64 1.1.1w-0+deb11u1 [1,820 kB]
Get:7 http://deb.debian.org/debian bullseye/main amd64 protobuf-compiler amd64 3.12.4-1+deb11u1 [75.3 kB]
Fetched 6,632 kB in 3s (2,509 kB/s)         
Reading changelogs... Done
Preconfiguring packages ...
(Reading database ... 628622 files and directories currently installed.)
Preparing to unpack .../libssl1.1_1.1.1w-0+deb11u1_amd64.deb ...
Unpacking libssl1.1:amd64 (1.1.1w-0+deb11u1) over (1.1.1n-0+deb11u3) ...
Setting up libssl1.1:amd64 (1.1.1w-0+deb11u1) ...
(Reading database ... 628622 files and directories currently installed.)
Preparing to unpack .../0-libprotobuf23_3.12.4-1+deb11u1_amd64.deb ...
Unpacking libprotobuf23:amd64 (3.12.4-1+deb11u1) over (3.12.4-1) ...
Preparing to unpack .../1-libprotobuf-lite23_3.12.4-1+deb11u1_amd64.deb ...
Unpacking libprotobuf-lite23:amd64 (3.12.4-1+deb11u1) over (3.12.4-1) ...
Selecting previously unselected package libprotobuf-dev:amd64.
Preparing to unpack .../2-libprotobuf-dev_3.12.4-1+deb11u1_amd64.deb ...
Unpacking libprotobuf-dev:amd64 (3.12.4-1+deb11u1) ...
Selecting previously unselected package libprotoc23:amd64.
Preparing to unpack .../3-libprotoc23_3.12.4-1+deb11u1_amd64.deb ...
Unpacking libprotoc23:amd64 (3.12.4-1+deb11u1) ...
Selecting previously unselected package libssl-dev:amd64.
Preparing to unpack .../4-libssl-dev_1.1.1w-0+deb11u1_amd64.deb ...
Unpacking libssl-dev:amd64 (1.1.1w-0+deb11u1) ...
Selecting previously unselected package protobuf-compiler.
Preparing to unpack .../5-protobuf-compiler_3.12.4-1+deb11u1_amd64.deb ...
Unpacking protobuf-compiler (3.12.4-1+deb11u1) ...
Setting up libprotobuf23:amd64 (3.12.4-1+deb11u1) ...
Setting up libprotobuf-lite23:amd64 (3.12.4-1+deb11u1) ...
Setting up libprotoc23:amd64 (3.12.4-1+deb11u1) ...
Setting up libssl-dev:amd64 (1.1.1w-0+deb11u1) ...
Setting up protobuf-compiler (3.12.4-1+deb11u1) ...
Setting up libprotobuf-dev:amd64 (3.12.4-1+deb11u1) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for libc-bin (2.31-13+deb11u3) ...

Installing /home/marc/.cargo/bin/sgx-detect
  Installing /home/marc/.cargo/bin/sgxs-append
  Installing /home/marc/.cargo/bin/sgxs-build
  Installing /home/marc/.cargo/bin/sgxs-info
  Installing /home/marc/.cargo/bin/sgxs-load
  Installing /home/marc/.cargo/bin/sgxs-sign
   Installed package `sgxs-tools v0.8.6` (executables `sgx-detect`, `sgxs-append`, `sgxs-build`, `sgxs-info`, `sgxs-load`, `sgxs-sign`)
     Summary Successfully installed fortanix-sgx-tools, sgxs-tools!

[target.x86_64-fortanix-unknown-sgx]
runner = "ftxsgx-runner-cargo"

 sgx-detect
Detecting SGX, this may take a minute...
✘  SGX instruction set
  ✘  CPU support
✘  SGX system software
  ✘  SGX kernel device
  ✘  libsgx_enclave_common
  ✘  AESM service
🕮  SGX instruction set > CPU support
It appears your hardware does not have SGX support.
(run with `--verbose` for more details)
More information: https://edp.fortanix.com/docs/installation/help/#cpu-support
🕮  SGX system software > SGX kernel device
The SGX device (/dev/sgx/enclave, /dev/sgx or /dev/isgx) is not present.
It could not be detected whether you have an SGX driver installed. Please make sure the SGX driver is installed and loaded correctly.
(run with `--verbose` for more details)
More information: https://edp.fortanix.com/docs/installation/help/#sgx-driver
🕮  SGX system software > AESM service
AESM could not be contacted. AESM is needed for launching enclaves and generating attestations.
Please check your AESM installation.
(run with `--verbose` for more details)
More information: https://edp.fortanix.com/docs/installation/help/#aesm-service

make[2]: Leaving directory '/home/marc/OPTEE/qemu/build'
make[1]: Leaving directory '/home/marc/OPTEE/qemu'
/home/marc/OPTEE/build/../toolchains/aarch64/bin/aarch64-linux-gnu-objcopy -O binary \
				-R .note \
				-R .comment \
				-S /home/marc/OPTEE/build/../linux/vmlinux \
				/home/marc/OPTEE/build/../out/bin/linux.bin
/home/marc/OPTEE/build/../u-boot/tools/mkimage -A arm64 \
			-O linux \
			-T kernel \
			-C none \
			-a 0x42200000 \
			-e 0x42200000 \
			-n "Linux kernel" \
			-d /home/marc/OPTEE/build/../out/bin/linux.bin /home/marc/OPTEE/build/../out/bin/uImage
Image Name:   Linux kernel
Created:      Tue Oct 31 14:44:00 2023
Image Type:   AArch64 Linux Kernel Image (uncompressed)
Data Size:    38783488 Bytes = 37874.50 KiB = 36.99 MiB
Load Address: 42200000
Entry Point:  42200000
ln -sf /home/marc/OPTEE/build/../out-br/images/rootfs.cpio.gz /home/marc/OPTEE/build/../out/bin
/home/marc/OPTEE/build/../u-boot/tools/mkimage -A arm64 \
			-T ramdisk \
			-C gzip \
			-a 0x45000000 \
			-e 0x45000000 \
			-n "Root file system" \
			-d /home/marc/OPTEE/build/../out/bin/rootfs.cpio.gz /home/marc/OPTEE/build/../out/bin/rootfs.cpio.uboot
Image Name:   Root file system
Created:      Tue Oct 31 14:44:00 2023
Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
Data Size:    8831884 Bytes = 8624.89 KiB = 8.42 MiB
Load Address: 45000000
Entry Point:  45000000
make run-only
make[1]: Entering directory '/home/marc/OPTEE/build'
ln -sf /home/marc/OPTEE/build/../out-br/images/rootfs.cpio.gz /home/marc/OPTEE/build/../out/bin/

* QEMU is now waiting to start the execution
* Start execution with either a 'c' followed by  in the QEMU console or
* attach a debugger and continue from there.
*
* To run OP-TEE tests, use the xtest command in the 'Normal World' terminal
* Enter 'xtest -h' for help.

# Option “-x” is deprecated and might be removed in a later version of gnome-terminal.
# Option “-x” is deprecated and might be removed in a later version of gnome-terminal.
# Use “-- ” to terminate the options and put the command line to execute after it.
# Use “-- ” to terminate the options and put the command line to execute after it.
# watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0)
# watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0)
# unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1)
# unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, estaFlying Knowledge Toolboxblishing: 1)
# watch_established: "/org/gnome/terminal/legacy/" (establishing: 0)
# watch_established: "/org/gnome/terminal/legacy/" (establishing: 0)
cd /home/marc/OPTEE/build/../out/bin && /home/marc/OPTEE/build/../qemu/build/aarch64-softmmu/qemu-system-aarch64 \
	-nographic \
	-serial tcp:localhost:54320 -serial tcp:localhost:54321 \
	-smp 2 \
	-s -S -machine virt,acpi=off,secure=on,mte=off,gic-version=3,virtualization=false \
	-cpu max,sme=on,pauth-impdef=on \
	-d unimp -semihosting-config enable=on,target=native \
	-m 1057 \
	-bios bl1.bin		\
	-initrd rootfs.cpio.gz \
	-kernel Image \
	-append 'console=ttyAMA0,38400 keep_bootcon root=/dev/vda2 ' \
	 \
	-object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0,max-bytes=1024,period=1000 -netdev user,id=vmnic -device virtio-net-device,netdev=vmnic
qemu-system-aarch64: -netdev user,id=vmnic: network backend 'user' is not compiled into this binary
make[1]: *** [Makefile:480: run-only] Error 1
make[1]: Leaving directory '/home/marc/OPTEE/build'
make: *** [Makefile:438: run] Error 2

	cd $(BINARIES_PATH) && $(QEMU_BUILD)/aarch64-softmmu/qemu-system-aarch64 \

ii  tor                 0.4.5.10-1~deb11u1 amd64        anonymizing overlay network for TCP
un  tor-arm             <none>             <none>       (no description available)
ii  tor-geoipdb         0.4.5.10-1~deb11u1 all          GeoIP database for Tor
ii  torbrowser-launcher 0.3.3-6            amd64        helps download and run the Tor Browser Bundle
ii  torsocks            2.3.0-3            amd64        use SOCKS-friendly applications with Tor

/etc
/etc/apparmor.d                                         => apparmor stuff!
/etc/apparmor.d/abstractions
/etc/apparmor.d/abstractions/tor
/etc/apparmor.d/system_tor
/etc/cron.weekly
/etc/cron.weekly/tor
/etc/default
/etc/default/tor
/etc/init.d
/etc/init.d/tor
/etc/logrotate.d
/etc/logrotate.d/tor
/etc/runit
/etc/runit/runsvdir
/etc/runit/runsvdir/default
/etc/sv
/etc/sv/tor
/etc/sv/tor/.meta
/etc/sv/tor/.meta/installed
/etc/sv/tor/log
/etc/sv/tor/log/run
/etc/sv/tor/run
/etc/tor
/etc/tor/torrc
/lib
/lib/systemd
/lib/systemd/system
/lib/systemd/system/tor.service
/lib/systemd/system/tor@.service
/lib/systemd/system/tor@default.service
/lib/systemd/system-generators
/lib/systemd/system-generators/tor-generator
/usr
/usr/bin
/usr/bin/tor
/usr/bin/tor-gencert
/usr/bin/tor-print-ed-signing-cert
/usr/bin/tor-resolve
/usr/bin/torify
/usr/sbin
/usr/sbin/tor-instance-create
/usr/share
/usr/share/doc
/usr/share/doc/tor
/usr/share/doc/tor/NEWS.Debian.gz
/usr/share/doc/tor/README.Debian
/usr/share/doc/tor/changelog.Debian.gz
/usr/share/doc/tor/changelog.gz
/usr/share/doc/tor/copyright
/usr/share/doc/tor/tor-exit-notice.html
/usr/share/doc/tor/tor-gencert.html
/usr/share/doc/tor/tor-print-ed-signing-cert.html
/usr/share/doc/tor/tor-resolve.html
/usr/share/doc/tor/tor.html
/usr/share/doc/tor/torify.html
/usr/share/doc/tor/torrc.sample.gz
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/tor
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/tor-gencert.1.gz
/usr/share/man/man1/tor-print-ed-signing-cert.1.gz
/usr/share/man/man1/tor-resolve.1.gz
/usr/share/man/man1/tor.1.gz
/usr/share/man/man1/torify.1.gz
/usr/share/man/man5
/usr/share/man/man8
/usr/share/man/man8/tor-instance-create.8.gz
/usr/share/runit
/usr/share/runit/meta
/usr/share/runit/meta/tor
/usr/share/runit/meta/tor/installed
/usr/share/tor
/usr/share/tor/tor-service-defaults-torrc
/usr/share/tor/tor-service-defaults-torrc-instances
/var
/var/log
/var/log/runit
/var/log/runit/tor
/etc/sv/tor/log/supervise
/etc/sv/tor/supervise
/usr/sbin/tor
/usr/share/man/man5/torrc.5.gz

 tor
Dec 16 18:20:44.744 [notice] Tor 0.4.5.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1n, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 and Glibc 2.31 as libc.
Dec 16 18:20:44.744 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Dec 16 18:20:44.745 [notice] Read configuration file "/etc/tor/torrc".
Dec 16 18:20:44.746 [notice] Opening Socks listener on 127.0.0.1:9050
Dec 16 18:20:44.746 [warn] Could not bind to 127.0.0.1:9050: Address already in use. Is Tor already running?
Dec 16 18:20:44.746 [warn] Failed to parse/validate config: Failed to bind one of the listener ports.
Dec 16 18:20:44.746 [err] Reading config failed--see warnings above.

# This file is a self-modifying .desktop file that can be run from the shell.
# It preserves arguments and environment for the start-tor-browser script.
#
# Run './start-tor-browser.desktop --help' to display the full set of options.
#
# When invoked from the shell, this file must always be in a Tor Browser root
# directory. When run from the file manager or desktop GUI, it is relocatable.
#
# After first invocation, it will update itself with the absolute path to the
# current TBB location, to support relocation of this .desktop file for GUI
# invocation. You can also add Tor Browser to your desktop's application menu
# by running './start-tor-browser.desktop --register-app'
#
# If you use --register-app, and then relocate your TBB directory, Tor Browser
# will no longer launch from your desktop's app launcher/dock. However, if you
# re-run --register-app from inside that new directory, the script
# will correct the absolute paths and re-register itself.
#
# This file will also still function if the path changes when TBB is used as a
# portable app, so long as it is run directly from that new directory, either
# via the shell or via the file manager.