[Libre-soc-dev] Coriolis2 Non-Chroot Script

Andrey Miroshnikov andrey at technepisteme.xyz
Sat Sep 11 19:29:58 BST 2021

On 11/09/2021 18:51, lkcl wrote:
> Andrey, i have a thought:  would you care to non-chrootify the coriolis2 install?
Was just looking at the explanation of schroot "plain" and "directory" 
as you sent the email, as well as the devscripts wiki page which talks 
about setting up a chroot using "mk-deb-chroot".

Yesterday when I ran the scripts which pull in the soc files into ~/src 
directory, I didn't setup a chroot beforehand.
Was I supposed to setup a chroot first, in order to have an isolated, 
standardised root system/environment that can be modified by a non-sudo 

> use the following strategy:
> 1) take a copy
> 2) remove the parts that set up an schroot
> 3) convert anything that requires to be run as a user to just... run as a user
So looking at "coriolis2-chroot" file and for making a non-chroot 
version, I should (file line numbers where functions occur in [] brackets) :
-[6-7] Ignore coriolis chroot creation
-[9-20] Ignore the /tmp/brokenproxy section
-[22-45] Ignore debootstrap, systemd userdb, nssdatabase
-[47-55] Ignore fstab config
-[57-77] Ignore schroot config for coriolis
-[80-100] Install/Remove packages needed for coriolis
-[102-118] Ignore account creation
-[120-151] Compile/Install yosys, coriolis2 (removing schroot statements)
-[153-157] Setup environment vars for coriolisenv
-[159-177] Compile/Install alliance
-[179-198] Compile/Install alliance-check-toolkit

> 4) convert anything that needs root (make install) to use sudo
> 5) convert the *existing* coriolis2-chroot to:
>    a) call mk-deb-chroot
Just giving "mk-deb-chroot" a read, I noticed lines 25-30, 57-62, 69-75, 
79-88, would crash the script (as they are not valid commands, or 
continued by backslashes, or encapsulated by quotes).

Was it used by anyone yet? Also it has reference to supporting Arch 
Linux (lines 39-41), must be have been an experimental script.
I'd need to rework this one before running it as well.

>    b) call the new script created from 1-4 running it
>         *in* the newly-created chroot.
>         this by actually copying the script over to it
> what do you think?I can certainly do it, with some clarification.


More information about the Libre-soc-dev mailing list