Puppy Linux Discussion Forum

Hello. Why does the "mklive bullseye script" always install packages (yad gtkdialog gnome-icon-theme fonts-dejavu-core gtk2 libs) before download kernel? Even if you delete all packages from the configuration file. I just want to install a basic system and use only console apps. Cheked script, but cant find where this hapen.
Config File:

### Start configuration

# Be careful with removing from this section (mostly essential)  
BASE_INSTALL="wget"

# Base Dog Packages, recommended to keep:
# yad gtkdialog obshutdown pup-volume-monitor peasywifi
BASE_DOG_APPS_INSTALL=""

BASE_APPS_INSTALL=""

DESK_APPS_INSTALL=""
  
FIRMWARE=""

EXTRA_DOG_APPS_INSTALL=""

REM_AUTO_INST="TRUE"
# Force 32 bit on 64 bit OS (set to FALSE for 64-bit build on 64-bit OS)
FORCE32="FALSE"
KEEPLOCALES="FALSE"
KEEPMANDOC="FALSE"
SYSTEMD="FALSE"
RUNXTERM="FALSE"
LBINITRD="FALSE"
ISOUEFI="FALSE"
### End configuration

Hi @donvon
Well it's actually not made for "no X" , but I found what's causing the install of these packages, its "porteusbootscripts" package that brings the gui app. as dependencies.
I experimented modifying to this in mklive-bullseye , line 1235-1240 (avoid installing porteusbootscripts, but NOT a problem as the scripts are already copied, so works with CLI, not with GUi then)

# in case udev installed, replace with eudev
if [ "$SYSTEMD" = "FALSE" ]; then
apt-get install -y eudev     # porteusbootscripts
#else
#apt-get install -y   #   porteusbootscripts
fi

Also it's needed to install xinit (otherwise there will be no init system in the end), and I'd suggest xterm, so then in your .conf ;
BASE_INSTALL="wget xinit xterm"
And perhaps change to this too:
RUNXTERM="TRUE"
Then xterm will run in the chroot and you'll be able to do things, e.g. remove packages (if still too much unwanted) or install more.

From my test the ISO resulted in size 137M (gzip compressed .squashfs) and it booted OK (except at the end it says no X found, but CTRL-C (edit; or wait a while) got me on the command line)
(autologin is on by default, can be disabled in /etc/inittab, auto start X on too, configured in /etc/profile)

Thank you @fredx181
One more question.
How can i increase ram disk size (not sure how it's called)? On regualr puppys i can do:

mount -t tmpfs -o "remount,size=95%" tmpfs

to increase ram disk size to 95% of ram. Debian dog by default use around 50-55 %.

donvon wrote: Sun Oct 30, 2022 9:58 pm

Thank you @fredx181
One more question.
How can i increase ram disk size (not sure how it's called)? On regualr puppys i can do:

Code: Select all

mount -t tmpfs -o "remount,size=95%" tmpfs

to increase ram disk size to 95% of ram. Debian dog by default use around 50-55 %.

I think it's set with a boot parameter/cheat code in the menu.1st or grub.cfg entry.

try

ramsize=some_value%

I got that from the porteus help documentation. http://www.porteus.org/component/conten ... -them.html

dancytron wrote: Mon Oct 31, 2022 2:33 pm

I think it's set with a boot parameter/cheat code in the menu.1st or grub.cfg entry.

try

Code: Select all

ramsize=some_value%

I got that from the porteus help documentation. http://www.porteus.org/component/conten ... -them.html

Yes default is 60% and e.g. ramsize=95% on boot kernel line works, but only in combination with changes=EXIT:/... parameter (changes in RAM, save (or not) at shutdown or on demand).
From a running system you can do mount -t tmpfs -o "remount,size=95%" /mnt/live/memory/changes which has same result (if booted with changes=EXIT:/.... , if not, then /mnt/live/memory/changes is not a ramdisk)
EDIT: Forgot to mention if booting without changes= specified, then ramsize=95% should work too.

@donvon It depends what you want to use it for. There are a few tmpfs available, check with df -h for example /mnt/live is a ram disk , to increase to 95% do mount -t tmpfs -o "remount,size=95%" /mnt/live

@dancytron wrote:

I got that from the porteus help documentation.http://www.porteus.org/component/conten ... -them.html

Very useful Info