Skip to content

Releases: nathanjhood/UBento

Pre-release v.0.1.24-01-2023_x64-beta.1

24 Jan 20:59
d7208c1
Compare
Choose a tag to compare
Pre-release
  • All basic profile files and permissions in place in /root and /etc/skel, meaning you can just simply download the attached .tar archive and run the following;
wsl --import UBento "D:\UBento" "C:\Users\<username>\Downloads\ubento.tar"

...and this will land you in the actual first launch of the distro, starting as 'root' with the almost-equivalent of Ubuntu-Minimal, but with all UBento aliases, exports, functions, and everything else described in the README already set. There are NO additional packages or anything installed - the distro as attached has never actually been run, only edited externally (being very mindful of permissions - see below) and then packed and uploaded.

  • Once the UBento files were all in place, and right before packing, it was necessary to make a permissions amendment to the /tmp and /root folders - again, performed externally on the bare files, not from within the distro's own terminal - as they appeared to have been altered by the tar CLI. This was fixed by simply cd'ing into the repo's base folder and running (SO link also provided);
chmod 755 / && \
chmod 1777 /tmp 
find /tmp \
     -mindepth 1 \
     -name '.*-unix' -exec chmod 1777 {} + -prune -o \
     -exec chmod go-rwx {} +

https://unix.stackexchange.com/questions/71622/what-are-correct-permissions-for-tmp-i-unintentionally-set-it-all-public-recu

  • To reiterate once again - this distro has not been mounted and/or launched, only edited externally as a repo within VSCode. You are launching the Ubuntu-Minimal image pulled from Docker Desktop, just with some souped-up Bash scripts already in place. You will have to decide what to install, from the very first package (apt-utils and dialog are recommended as a very minimum) onwards, including mainstays such as sudo, python, git, etc.

  • Per the above, there are also no users or adduser routines (besides the obligatory 'root') pre-installed or running at initialization. So you can scale per your needs!

  • If you want to use the updated keyring, just be 'root' and get_<package> - you can then sudo apt install the updated <package> as your user.

Pre-release v.0.1.06-01-2023_x64-beta.1

06 Jan 04:01
ca1c67c
Compare
Choose a tag to compare
Pre-release
  • All basic profile files and permissions in place in /root and /etc/skel, meaning you can just simply download the attached .tar archive and run the following;
wsl --import UBento "D:\UBento" "C:\Users\<username>\Downloads\ubento.tar"

...and this will land you in the actual first launch of the distro, starting as 'root' with the almost-equivalent of Ubuntu-Minimal, but with all UBento aliases, exports, functions, and everything else described in the README already set. There are NO additional packages or anything installed - the distro as attached has never actually been run, only edited externally (being very mindful of permissions - see below) and then packed and uploaded.

  • Once the UBento files were all in place, and right before packing, it was necessary to make a permissions amendment to the /tmp and /root folders - again, performed externally on the bare files, not from within the distro's own terminal - as they appeared to have been altered by the tar CLI. This was fixed by simply cd'ing into the repo's base folder and running (SO link also provided);
chmod 755 / && \
chmod 1777 /tmp 
find /tmp \
     -mindepth 1 \
     -name '.*-unix' -exec chmod 1777 {} + -prune -o \
     -exec chmod go-rwx {} +

https://unix.stackexchange.com/questions/71622/what-are-correct-permissions-for-tmp-i-unintentionally-set-it-all-public-recu

  • To reiterate once again - this distro has not been mounted and/or launched, only edited externally as a repo within VSCode. You are launching the Ubuntu-Minimal image pulled from Docker Desktop, just with some souped-up Bash scripts already in place. You will have to decide what to install, from the very first package (apt-utils and dialog are recommended as a very minimum) onwards, including mainstays such as sudo, python, git, etc.

  • Per the above, there are also no users or adduser routines (besides the obligatory 'root') pre-installed or running at initialization. So you can scale per your needs!

  • If you want to use the updated keyring, just be 'root' and get_<package> - you can then sudo apt install the updated <package> as your user.