Debian 9 post-installation arrangement automation

In several (mostly rare) cases Linux kernel can't work correctly with your hardware and point on this by messages (dmesg and /var/log/ also). The general concept is:

If something goes wrong it must do it loudly!

thus, in incorrect work case kernel fills the log with the ERROR messages and it should easily detected by user.

It's easy, as a day: hardware incompatibility - sometimes arbitrary piece of your PC might be equipped by proprietary hardware (e.g. Wi-Fi card from Atheros, or Bluetooth adapter from unknown manufacturer). That's it - it just deny to serve as expected by the Kernel. All you might need a set of proprietary drivers on your device.

In flip side: when you're got a tons of Error messages and device is stubborn as a mule, it is unavoidable.

There are a lot of approaches how to blacklist, and the stem idea is to expel erroneous modules out from usage by the Kernel.

Initial source is an official Docker site

# apt-get remove docker docker-engine docker.io
# apt-get update
# apt-get install apt-transport-https /
  ca-certificates curl gnupg2 software-properties-common
# curl -fsSL https://download.docker.com/linux/debian/gpg | sudo apt-key add -
# apt-key fingerprint 0EBFCD88
# add-apt-repository    "deb [arch=amd64] https://download.docker.com/linux/debian \
			 $(lsb_release -cs) \
			 stable"
# apt-get update
# apt-get install docker-ce

docker --version

Docker version 17.06.0-ce, build 02c1d87

Post-installation procedures

Jenkins is an open source continuous integration tool written in Java and released under the MIT License. It is a server-based system running in a servlet container such as Apache Tomcat.

LTS version

# wget -q -O - http://pkg.jenkins-ci.org/debian-stable/jenkins-ci.org.key | apt-key add -
# echo "deb http://pkg.jenkins-ci.org/debian-stable binary/" | tee -a /etc/apt/sources.list

# apt-get update
# apt-get install jenkins -y

After that it would be feasible to login to Jenkins at localhost:8080 For secure necessity you'll be owe to enter password allocated in file with root access only.

# nano /var/lib/jenkins/secrets/initialAdminPassword

Source

Easy peasy.

Source

Unfortunately it is impossible to install it as a single app, but only as Google Chrome plugin. To do so:

# wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
# dpkg -i google-chrome-stable_current_amd64.deb

After that you should download and install google-talkplugin_current_amd64.deb

As I'm expect to store my data locally and I'm a user in generic sense of this word, lets check-up /usr/local/ directory as a potential storage for my data.

tree -L 1 /usr/local/

/usr/local/
├── bin
├── etc
├── games
├── include
├── lib
├── man -> share/man
├── sbin
├── share
└── src

9 directories, 0 files

tree -L 2 /usr/local/lib/

/usr/local/lib/
├── python2.7
│   ├── dist-packages
│   └── site-packages
└── python3.5
    └── dist-packages

5 directories, 0 files

tree -L 2 /usr/local/share/

/usr/local/share/
├── anki
│   ├── anki.xml
│   ├── bin
│   ├── Makefile
│   └── README
├── applications
│   ├── anki.desktop
│   └── mimeinfo.cache
├── ca-certificates
├── emacs
│   ├── 25.1
│   └── site-lisp
├── fonts
├── man
│   └── man1
├── pixmaps
│   ├── anki.png
│   └── anki.xpm
├── sgml
│   ├── declaration
│   ├── dtd
│   ├── entities
│   ├── misc
│   └── stylesheet
└── xml
    ├── declaration
    ├── entities
    ├── misc
    └── schema

22 directories, 5 files

Seems like the best place to put any data on UNIX host is /usr/local/ that have lib and share folders which are the pertinent place for shared data and some library-like one.

On my point of view the most convenient place to put some shared data on your Debian 9 host is /usr/local/share/

By default convention the user don't allowed to write into /usr/local/, but staff group is a special case:

staff: Allows users to add local modifications to the system (/usr/local) without needing root privileges…

Initially it is an empty group, there are no users in it:

groups | grep staff
echo "---"
groups alioth | grep staff

---

Now, when you're added into staff group it would be possible to execute any secure command from current user. Let's create in /usr/local/ several additional folders for books, courses and repositories:

Any contemporary software development inevitably tied with version control systems there Git and Mercurial deserve to be noticed. Thus it would be a wise decision to provide folder separation for these VCS locally on your HD:

mkdir /usr/local/git/ /usr/local/hg/

After that it might be easily cloned some particular content there. And let call this schema folder per VCS

User separation might avert any mess when there are several users. Respectively it might be accomplishing in our case by:

mkdir /usr/local/git/0--key/ /usr/local/git/annelida/

Now, when you're prepared place where to allocate your forks or clones - it's very time to clone it there.

Exactly for clarity purpose it would be useful to utilize folder per user schema, with inner repositories allocation.

mkdir /usr/local/git/0--key/
cd /usr/local/git/0--key/
git clone https://github.com/0--key/lib.git
git clone https://github.com/0--key/org-pub.git
git clone https://github.com/0--key/0--key.github.io.git

as a result you should get something around this:

tree -L 2 /usr/local/git/

/usr/local/git/
├── 0--key
│   ├── 0--key.github.io
│   ├── lib
│   ├── nltk
│   ├── org-pub
    └── talk-python-transcripts

As I'm prefer to store my Emacs' settings in the Git cloud.

ln -s -T /usr/local/git/0--key/lib/Emacs/default.lenovo.el \
/usr/local/share/emacs/site-lisp/default.el
ln -s -T /usr/local/git/0--key/lib/Emacs/init_generic.el \
~/.emacs.d/init.el

It's a routine task, thus there is a simple and native solution.

• Find out custom-set-variables section in your init.el
• Evaluate it by M-x eval-region

• Now look on package-selected-packages variable

  (print package-selected-packages)
  

  
  (org bookmark+ color-theme elfeed elpy google-translate howdoi key-chord magit marshal org-bullets org-pomodoro pcache travis voca-builder ereader docker)
  
  

• C-h v package-selected-packages
• Ensure package-selected-packages is fulfilled (not nil)
• package-install-selected-packages
• DONE

It's easy:

# apt-get install install-info

Now just type C-h i and enjoy!

Is a cool feature to use in daily work for each developer. Thus it is necessary to assign a semantically pertinent path to allocate all theirs venvs in some particular folder:

mkdir -p /usr/local/share/DVCS/alioth
mkdir -p /usr/local/share/DVCS/vikky

E.g. two our users would place the individual version of venvs in separate folders.

Suppose you're alerady installed virtualenv on your system. Thus:

python --version
virtualenv -p /usr/bin/python3 /usr/local/share/DVCS/alioth/venv3

Python 2.7.13
Already using interpreter /usr/bin/python3
Using base prefix '/usr'
New python executable in /usr/local/share/DVCS/alioth/venv3/bin/python3
Also creating executable in /usr/local/share/DVCS/alioth/venv3/bin/python
Installing setuptools, pkg_resources, pip, wheel...done.

Try to overview your venv:

tree -L 1 /usr/local/share/DVCS/alioth/venv3/

/usr/local/share/DVCS/alioth/venv3/
├── bin
├── lib
└── share

3 directories, 0 files

Seems like all jobe is done and let's activate our venv:

(pyvenv-activate "/usr/local/share/DVCS/alioth/venv3/")

Check-up results:

python --version

Python 3.5.3

And let's return into innate state:

(pyvenv-deactivate)

python --version

Python 2.7.13

It is a good idea to utilize the isolated DevEnv for Python and it demands to install several handy packages into each DevEnv.

pip install jedi yapf flake8 autopep8

# usermod -aG vboxusers alioth

After this you must to re-login to savor these changes.