joborun/web
2
1
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

more explanations about some new scripts

Browse source 
improve
This commit is contained in:
joborun linux 2022-04-20 14:35:54 +00:00
parent 20c7aefccb
commit ba219af277
1 changed files with 6 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
scripts.md
View file

@ -1,9 +1,9 @@
### [[Back to the top joborun wiki page|index.md]] ###
## scripts saved in /home/make of our image ##
## scripts saved in /home/make or /usr/local/bin of our image ##
If you don't wish to [[install|https://git.disroot.org/joborun/web/src/branch/main/inst_from_image.md]] via downloading and exploding an tarball image, and follow the [[live net-installation|https://git.disroot.org/joborun/web/src/branch/main/install.md]] method you will miss on a few helper scripts that make guess-work easier.
If you don't wish to [[install|https://git.disroot.org/joborun/web/src/branch/main/inst_from_image.md]] via downloading and exploding a tarball image, and follow the [[live net-installation|https://git.disroot.org/joborun/web/src/branch/main/install.md]] method, you will miss on a few helper scripts that make guess-work easier. Here they are, we publish them so you can adopt some of the experience of the tar.ball.
#### Install X + openbox + jwm ####
@ -90,7 +90,7 @@ 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.
numactl: is a program that lets you control on which processors/threads 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.
<b>Add s6 and 66 for alternative init and supervision system.</b>
@ -126,6 +126,9 @@ you can add, and should add, sudo <b> 66-env -t boot -e nano boot@sys </b> and e
/home/make/rm.66
To remove s6/66 and return to your runit only system use this rm.66 script.
Emphasis on the script to have first booted with runit before you cleanly remove s6 and 66. The reason is that even though s6 is still pid 1 even after removing the package, it would take an existing instance of execline and skalibs to execute a proper shutdown. s6 is nearly impossible to kill unless its own routine is followed. You can kill every other process in the system and if s6 is pid1 it will reconstruct the system as the first moment it booted. Try this security with any other init system, but make sure there is an sshd still running in the system before it becomes a zombie system. "Ideal for a server" you say, you got it!
<pre>
#!/usr/bin/zsh
echo "you should ONLY remove 66 when you have booted with runit, otherwise"