Bookworm Build script

[sin4ez]

20240111_113932.jpg (128.49 KiB) Viewed 1188 times

Unfortunately, file manager doesn't work properly.
It can't mount a ventoy partition from that subj was runned.

It's not mounted!

[fredx181]

Problem installing wine32:i386 on Bullseye was reported by @Luluc here: viewtopic.php?t=10789
Same problem was on Bookworm too, but should be fixed (just now added i386 libelogind0 and libelogind-compat packages to custom repo)
To install wine32 on Bookworm amd64:

Code: Select all

dpkg --add-architecture i386
apt update
apt install wine wine32

[dancytron]

I was able to build scrcpy (application for using computer as a thin client for your android device) using the same instructions as puppy, except I edited out the "sudo" in the script before I tried it.

Seems to work fine.

viewtopic.php?p=113651#p113651

https://github.com/Genymobile/scrcpy

2024-03-16-125406_800x_scrot.png (408.96 KiB) Viewed 871 times

[Null_ID]

Which package has wi-fi firmware (the more the merrier)? I attempted to run this build script on a Thinkpad T420 running MX Linux 21.3, and the build process itself went smoothly. It came out with a functional enough system that booted to desktop. But there was no wi-fi firmware for these:

Code: Select all

[   10.204186] iwlwifi 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
[   10.235917] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-6000g2a-6.ucode (-2)
[   10.235953] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-6000g2a-6.ucode (-2)
[   10.235956] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-6000g2a-6.ucode failed with error -2
[   10.235984] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-6000g2a-5.ucode (-2)
[   10.236005] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-6000g2a-5.ucode (-2)
[   10.236007] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-6000g2a-5.ucode failed with error -2
[   10.236010] iwlwifi 0000:03:00.0: minimum version required: iwlwifi-6000g2a-5
[   10.236013] iwlwifi 0000:03:00.0: maximum version supported: iwlwifi-6000g2a-6

and I'm not sure what to pass to the script to get them installed. (If it's important, I did a pretty minimal build to begin with, the 1st option that I was offered when asked about the desktop environment.)

Another question, if you don't mind me asking, does the kernel offered with the builds this script puts out support the ExFat file system, and are the Samsung ExFat-utils available in the repo?

[dcung]

... Thinkpad T420 running MX Linux 21.3, ... But there was no wi-fi firmware for these:

Check out if your MX Linux 21.3 have those files in /lib/firmware, if so, you maybe able to copy and use those.

.. does the kernel offered with the builds this script puts out support the ExFat file system, and are the Samsung ExFat-utils available in the repo?

I bought Samsung SSD that came ExFat pre-formatted. I had to install ExFat support after the build to access it. Unless Fred has changed/added since, ExFat support need to be added after your build. It's available from Debian repo.
Not sure about Samsung ExFat-utils, I didn't use it.

Edit - Update/Correction @Null_ID :
Having read @fredx181 reply below, i.e. new kernel support ExFat OOTB now.
viewtopic.php?p=117826#p117826

I tested with my fresh DOGS build (made on 24/4/2024).
I didn't have to do anything now. My ExFat SSD was accessible OOTB.
I checked, turned out I bought the SSD in May 2022 - I was using build made before that time.

[fredx181]

But there was no wi-fi firmware for these

The package you'd probably need is "firmware-iwlwifi"
When making a build with mklive, add it to the packages list to be installed.
Or, what I often do is to download the .deb from another OS first (that has network connection) , save it somewhere and then (without having network connection if I'm depending on wifi only) I'm able to install that firmware deb package on the build that is missing it.
Download bookworm "firmware-iwlwifi" deb package here: https://packages.debian.org/bookworm/al ... i/download

[Null_ID]

Or, what I often do is to download the .deb from another OS first (that has network connection) , save it somewhere and then (without having network connection if I'm depending on wifi only) I'm able to install that firmware deb package on the build that is missing it.
Download bookworm "firmware-iwlwifi" deb package here: https://packages.debian.org/bookworm/al ... i/download

Thanks, that .DEB-package you suggested did the trick, and I have Wi-fi now.

I rolled up a new build to add a few things that I missed the last time, and it's a very smooth system now. Thanks again for your efforts. This was my first time doing this via a build script system like this, but it's pretty intuitive once you get the hang of it. I love how much this allows me to customize.

I bought Samsung SSD that came ExFat pre-formatted. I had to install ExFat support after the build to access it. Unless Fred has changed/added since, ExFat support need to be added after your build. It's available from Debian repo.
Not sure about Samsung ExFat-utils, I didn't use it.

All right, thanks for sharing.

[Clarity]

I have a new SSD on order arriving by the weekend.

ALL of my recent USBs and my 2 SSDs came preformatted for exFAT. Now appears to be an manufacturer's industry standard.

Since I am planning an upcoming BKWDog64, is there something at build time needed so that it is incorporated in the completion of the distro where I can reduce/manipulate partition size of exFAT without destroying the partition? Formats, as well.

Curious

[fredx181]

I have a new SSD on order arriving by the weekend.

ALL of my recent USBs and my 2 SSDs came preformatted for exFAT. Now appears to be an manufacturer's industry standard.

Since I am planning an upcoming BKWDog64, is there something at build time needed so that it is incorporated in the completion of the distro where I can reduce/manipulate partition size of exFAT without destroying the partition? Formats, as well.

Curious

Not sure, anyway, the exfat kernel module will be loaded booting a new build, but to manipulate/format exfat partition, it is probably required to add exfatprogs and/or exfat-fuse to the install list.
edit: just saying: building on exfat cannot work, needs to be on a Linux formatted partition e.g. ext3/4

[wanderer]

hi fredx and everyone

using bookworm debiandog
fantastic work
thank you so much for making this

can i run mklive bookworm
in bookworm debiandog
with a wired connection
on a computer with 2 gb ram and a 100 gb free ext2 hard drive

or do i need 4 gb of ram

and how long should it take for the minimal build

thanks again

wanderer

[fredx181]

..
can i run mklive bookworm
in bookworm debiandog
with a wired connection
on a computer with 2 gb ram and a 100 gb free ext2 hard drive

Yes, that should be more than enough.

and how long should it take for the minimal build

It depends on some things, e.g. internet speed, choice of settings, but I'd say around 15 minutes.

[wanderer]

thank you so much fredx

debiandog is awesome

and thanks for all the other great stuff you have done

wanderer

[wanderer]

hi fredx

thank you so much for this masterpiece
and for creating the concept which is truly mind boggling

i always wanted to use debian but i didnt want to download 10 gigs

this also appears to be the solution
of my endless quest for a minimal modular distro

i am using the bookworm iso
and it is everything i could want and more
no need for improvement here

however i would like to learn and play a little
i would like to build a minimal modular system in stages

1. command line only sfs

2. desktop sfs

3. browser sfs

4. mediaplayer sfs

5. utilites sfs

6. etc

and try to use symlinks instead of a layered filesystem

to load an sfs create the symlink
to unload an sfs delete symlink
to reload an sfs create the symlink again

so my first step is to learn how to run your script
to build a command line only core

could you point me to where you have your starting out instructions

and thank you so much again
we are not worthy

wanderer

[dancytron]

Zram will help with only 2 Gb of ram.

The old old debian way to set it up still worked the last time I checked.

https://www.forum.puppylinux.com/viewto ... d1c#p78549

[wanderer]

hi all

removed gz
chmod 777
put bookworm script in a folder on my hard drive
ran the script

ran flawlessly
didnt take much time
made an iso with jwm and firefox

booted flawlessly
works perfectly
looks beautiful

posting from the iso now

awesome

this is what woof-ce should be

fredx
thank you thank you thank you

now i need to play and learn more
how to make the applications into modules

wanderer

[wanderer]

hi all

can one make a template
to tell the bookworm script
what to put in and what to leave out of the iso
so that different particular builds are reproducible

wanderer

[dancytron]

Yes.

Edit your /mnt/sda1/bookworm/build_setup.conf file and give it a different name and put it outside of the /bookworm path.

Then run it like this from a terminal on the drive with the ./mklive-bookworm file with something like this.

Code: Select all

./mklive-bookworm -gui /root/Desktop/build_setup.smaller.conf | tee /root/Desktop/PWStarter.log

[wanderer]

hi dancytron

thanks so much

will check it out

wanderer

[fredx181]

however i would like to learn and play a little
i would like to build a minimal modular system in stages

1. command line only sfs

2. desktop sfs

3. browser sfs

4. mediaplayer sfs

5. utilites sfs

Well, in theory, yes, you could create a very minimal build so then live/01-filesystem.squashfs contains only the base utils. EDIT: Keep the name 01-filesystem.squashfs, do NOT rename it, some applications (e.g. Quick-remaster) depend on that name.
Then afterwards create modules (edit: e.g. with apt2sfs) and place them in the frugal install "live" folder e.g. firefox.squashfs (must have .squashfs extension).

and try to use symlinks instead of a layered filesystem

to load an sfs create the symlink
to unload an sfs delete symlink
to reload an sfs create the symlink again

Probably you mean like TinyCore ? Not really, that would require a whole different approach, this is based on a layered setup , however there's sfsload available that creates symlinks (load 'on-the-fly') the package "sfsload" provides that, install with apt install sfsload. Must say that it is not much tested overall and I cannot guarantee it works as expected in every case.
edit: then, to load sfs e.g.: loadmodule -a /path/to/mymodule.squashfs , to unload loadmodule -d /path/to/mymodule.squashfs
Or run GUI from Menu > Module Tools > SFS-Load GUI

[wanderer]

hi fredx181

thanks for commenting on my half baked ideas

i dont mean to change your system in any way
in my opinion its perfect as it is

you have made what is difficult and complex
easy and simple for us lesser mortals
the true mark of the work of a genius

the thing i intend to try to do
is as you have suggested

"create a very minimal build so then live/01-filesystem.squashfs contains only the base utils.
Then afterwards create modules and place them in the frugal install "live" folder"

but the modules can just be symlinked to the live/01-filesystem

probably sfsload does that

before i found tinycore
i used the puppy ramdrive as the core ( as root / )
and symlinked /user to it
/usr could be either compressed or uncompressed on the hard drive
i found the system to be very simple and reliable
one could load and unload /usr or other modules
by simply making and deleting symlinks
and even write to /usr if it was uncompressed

since make-live is a script
i can read it and try to learn a little
and simply use what you have created to make a version of debiandog
that incorporates some of these ideas

and thanks again for creating debiandog (and all the other stuff you have created )
like any genius
you may not even realize how great your work is

wanderer

[dancytron]

For faster prototyping, you can make grub entries like these that will boot DD in place as created in the /bookworm folder.

Code: Select all

menuentry "DebLive_bookworm-amd64-UEFI on sdb2 bookworm/isodata" {
  echo "Booting ..."
  search --no-floppy --fs-uuid --set=root cf9ade3f-78abnm,hgy
  linux /bookworm/isodata/live/vmlinuz1 edd=off noauto from=UUID:cf9ade3f-78abnm,hgy/bookworm/isodata changes=EXIT:UUID:cf9ade3f-78abnm,hgy/bookworm/isodata
  initrd /bookworm/isodata/live/initrd1.xz
}

menuentry "DebLive_bookworm-amd64-UEFI on sdb2 CleanMode bookworm/isodata" {
  echo "Booting ..."
  search --no-floppy --fs-uuid --set=root cf9ade3f-78abnm,hgy
  linux /bookworm/isodata/live/vmlinuz1 edd=off noauto copy2ram from=UUID:cf9ade3f-78abnm,hgy/bookworm/isodata
  initrd /bookworm/isodata/live/initrd1.xz
}

[wanderer]

thanks dancytron and fredx181

for all your help

this is awesome

wanderer

[wanderer]

hi fredx181

each time the build script runs
does it have to download everything again

is there any way to keep the debs in a local repository on your hard drive
so if you want to try another similar build
you can just fetch them from the local repository
and you dont have to download them all again

it seems it would make similar builds faster and less demanding on the internet

wanderer

[fredx181]

hi fredx181

each time the build script runs
does it have to download everything again
...

No, not all, the cache in apt/archives (deb packages) will be kept if running more than once (all the other stuff in bookworm folder will be deleted though, to really start fresh)

[wanderer]

hi fredx181

i built debiandog in the folder dd-1
now i have 4 folders inside dd-1

1. chroot
2. dog-boot-bookworm-20221013
3. initrdport-bullseye
4. isodata

but i cannot find apt/archives in any of them

where should i look


also can i manually edit
build_setup.conf
to add or remove packages

and once again thanks for all your time
and for all your work

wanderer

[tosim]

@fredx181
@wanderer
I was installing the mklive script, got as far as typing in which compression to use,and here's what I
got, before it shutdown:

script.jpg (25.14 KiB) Viewed 96 times

Your suggestions,please. fred, I agree with wanderer, beautiful script.

[wanderer]

hi tosim

did you put the script in a folder on your ( needs ext filesystem ) hard drive
before you ran it
it needs 3 gb of hard drive space

i used gzip
and it ran fine

i also ran it from a debiandog iso
so it had the libs it needed

wanderer

[fredx181]

@tosim Looks like you didn't type something (at the point of Type gzip or xz:) first type it and then press Enter .
And probably you need to start all over again, sorry to say.

[fredx181]

built debiandog in the folder dd-1
now i have 4 folders inside dd-1

1. chroot
2. dog-boot-bookworm-20221013
3. initrdport-bullseye
4. isodata

but i cannot find apt/archives in any of them

The deb files are in chroot/var/cache/apt/archives and will be kept when running second time , all else will be deleted.

also can i manually edit
build_setup.conf
to add or remove packages

Yes and then when done copy it to somewhere and, similar as dancytron wrote above, run: ./mklive-bookworm -gui /path/to/myconfig.conf
Look also at ./mklive-bookworm --help to see what the options are.

[wanderer]

thank you so much fredx181

wanderer