This repository holds my recipes to set up my working box quickly.

         _sudZUZ#Z#XZo=_
      _jmZZ2!!~---~!!X##wa
   .<wdP~~            -!YZL,
  .mX2'       _%aaa__     XZ[.
  oZ[      _jdXY!~?S#wa   ]Xb;
 _#e'     .]X2(     ~Xw|  )XXc
..2Z`      ]X[.       xY|  ]oZ(
..2#;      )3k;     _s!~   jXf`
 1Z>      -]Xb/    ~    __#2(
 -Zo;       +!4ZwaaaauZZXY'
  *#[,        ~-?!!!!!!-~
   XUb;.
    )YXL,,
      +3#bc,
        -)SSL,,
           ~~~~~

Frech companies are funny: they hire you as a Unix or Linux administrator (for example), and you spent all your working hours, but you have to work from a Windows station. I try to used on that, but, after a week with PuTTy windows everywhere, I end up installing a virtual machine with a Debian distro (this is my favorive at work, whereas I use Slackware at home, and really don't need neither any rolling release nor some other nice solid reach featured.)

Well, as Ops/Admin networks can't and shouldn't accessed from outside, I cannot have a working box outside the corporation. It may take arond a month to get everything set up because I don't remeber everything I've installed for some reason, until I need it again and have to take time to get it work as I like. I don't go a template way either because I need to stay flexible (depending on the contractor, I may use VMware workstation or Oracle VirtualBox or even some container! also there're specific parts to care of) So this repository is a work-in-progress with very few changes.

Of course, the first step is to create the VM (or configure a PM for the purpose) then install the OS.

After a fresh install, with a mininal/net ISO, I need some tweaking and have to add some enterprise stuffs to have a box ready for my own use. That's the purpose of this script. It usage is very simple:

# be sure to switch to root first, e.g:
su -
# download the script second, e.g:
wget https://raw.githubusercontent.com/gilcot/mydese/master/pic.sh
# launch the script at last, e.g:
sh pic.sh

Well, but what if you have different needs? Easy: before launching the script, prepare one of those files:

• some files for specific things related to the organisation
  • *.list: specific source lists to add
  • $domainname.setup: shell commands source before other processing
  • root_bashrc: own ~/root/.bashrc instead of script default
• two files to override default packages installation
  • all.deb.lst: list of system packages to install
  • all.pip.lst: list of Python packages to install
• two files for additional packages installation
  • $hostname.deb.lst: list of system packages to install
  • $hostname.pip.lst: list of Python packages to install

Packages lists can be retrieved, for example, from:

# Debian packages currently installed
dpkg --get-selections
# Python packages currently installed
pip list

But beware: only the first column is used, and therefore versions information are left (in fact one may use comments there.) However, if you need a specific version instead of the latest, add it to the name with the packages manager syntax.

Last words: Known alternatives are provided for some console programms. (I don't use any X application, and won't include things not in standard repositories.)