3.7 KiB
scripts saved in /home/make of our image
If you don't wish to install via downloading and exploding an tarball image, and follow the live net-installation method you will miss on a few helper scripts that make guess-work easier.
Install X + openbox + jwm
The first script that many may be interested in is simply a file list needed on top of base to start X and openbox or jwm. Note here that you don't need a kernel or a fully booted system to run X, you can chroot from console from another system, and if mounting of system directories is equivalent to arch's arch-chroot, you can switch to user, go to the home directory and simply type xinit or startx.
installX
#!/usr/bin/zsh sudo pacman -Sy $(cat X.list) --noconfirm # sudo /usr/local/bin/cldoc # use if you want documentation/help removed to save space xinit
cldoc is an other optional script for those who would rather reach documentation through network and don't need it in their minimalist system
/usr/local/bin/cldoc
% sudo chmod 0755 /usr/local/bin/cldoc
contents:
#!/bin/sh
sudo rm -rf /usr/share/{doc,man,html}/*
sudo rm -rf /usr/local/share/{doc,man,html}/*
X.list is separated from the script and it is just the list of proposed packages we suggest for your first start. Unfortunately the configurations are stored in that /home/make directory, and without them the setup will be as plain and boring as arch.
This X.list is as follows and feel free to subtract and add what you know will work better for you. It is meant for remembering what is needed and not keep reading Xorg.0.log for what is missing.
~/X.list
arandr conky elinks feh jwm leafpad lxterminal obconf obmenu-generator openbox-patched virtualbox-guest-utils xdg-user-dirs xf86-video-ati xf86-video-amdgpu xf86-video-intel xf86-video-vesa xf86-video-vmware xorg-server xorg-xinit pcmanfm libtool package-query
At this point you have to make sure you have this minimal file in your home directory:
~/.xinitrc
#!/usr/bin/zsh exec openbox-session #exec jwm #exec lxterminal
then simply type xinit (or startx no difference).
mkpkg and makepkg script
makepkg is the pacman subprogram for building a package from a template/recipe pacman defaults as PKGBUILD. PKGBUILD is a bash script because pacman was written to read bash commands to build a package. Someone should tell those fools who edit strict bash syntax and acuse predecesors of "extreme bashism", that this is what pacman was written with default, not a PKGBUILD editor's choice. Thankfully for those fools, bash has evolved in being more elastic and accepting more universal sh syntax and not enforce strictly its own, otherwise many arch/artix/obarun/manjaro/hyperbola/parabola pkgs wouldn't build! Mere linux is about the first distribution we have seen honoring this pacman quality and beginning their PKGBUILDs with a bash shebang.
sudo chmod +x /usr/local/bin/mkpkg
#!/bin/sh time numactl --physcpubind=1,3,5,7 makepkg -f
time: calculates the time interval from initiating the process till it ends, which is what the figures in "time" are in each pkg repository.
numactl: is a program that lets you control on which processors to execute the program. In this example imagine an 8core/thread machine with every other processor being used, to minimize both heat and maintain high functionality on the rest of the system. The makepkg -f cleans up from previous run and starts building from 0.