BookwormPup32

[peebee]

First Release 28-December-2023:

07b89ab51a83081ffc05aec7339de72f BookwormPup32-23.12+2.iso - from here or later releases here

bookwormpup32.png (5.59 KiB) Viewed 17585 times

Discussion thread

Download map: https://sourceforge.net/projects/pb-gh- ... /stats/map

32-bit version of BookwormPup - built from Debian 12 Bookworm components.

Closely aligned to BookwormPup64 (BWP64) and uses the configs of BWP64 as developed by @radky from the original work by @dimkr (many thanks to both).
It is a full Woof-CE Github Actions build.

Kernel is Debian config 6.1.x
OverlayFS provides the layered filesystem
GTK+3 apps are provided wherever possible
apt / synaptic deb package management & PPM for other package types
Sound control is by pipewire
Connman provides connection management - with a switcher to NetWizard if needed
Comprehensive firmware in the fdrv is provided. (large)

Some differences with BWP64:

• built-in browser is Light in the adrv rather than Firefox (Chromium, Firefox, Palemoon and SeaMonkey are available for download)
• xz sfs compression is used instead of zst
• celluloid is not included (gobject segfault issues)
• samba is provided in a separate sfs

An LXDE ydrv is also available.

Screenshot.png (188.07 KiB) Viewed 20478 times

[peebee]

reserved

[peebee]

reserved

[peebee]

Sorry folks - there was a config error with +0 so +1 is released..... see post #1

The build is now on Github Actions rather than local.

Update deltas are available.

[peebee]

A new Github Actions build is available 231221 - see post #1

[peebee]

07b89ab51a83081ffc05aec7339de72f BookwormPup32-23.12+2.iso
see post #1

281223

Updates to align with BookwormPup64-10.0.4 - thanks @radky

[peebee]

[Clarity]

@peebee, a very nice, well-structured video. +1

[oui]

The menu includes an (very old) item " Puppy installer " but nothing happens

I will really install a full installation on the hard disk.

Is that (today not) possible (any more)?

[peebee]

Full install is still there - it's just "hidden" to make it difficult to use:

Code: Select all

# to enable full install to hdd (before running this script - puppyinstaller):
#   export ENABLE_FULLINSTALL=1 

[arslan]

Why would you want to make anything difficult to use?

[Wiz57]

Why would you want to make anything difficult to use?

Because the normal Linux "full install" is not the more common method of using Puppy Linux versions. Puppy and most derivatives on the forum
are designed to be "frugal installed", which means they take less room on storage, they don't have to have a full partition on the storage device,
and some applications are designed to be loaded as you go (SFS load/unload). SFS on the fly doesn't work well with typical full partition installations.
Most of the Puppy Linux developers go to great lengths to keep SFS file handling intact, and getting help on the forum with "frugal install" is fairly
easy and many forum members will help a new user. The primary advantage of Puppy's frugal method of installation is no need to partition, format
then install the OS as is typical in other distros installers. You can simply make a directory (or folder in Windows) and extract the files from the
ISO into that directory, and add a stanza to your bootloader, or if totally new, use a bootloader installer to create a bootloader configuration.
With a frugal install you still get the complete operating system, but it uses much less in storage space. You can even try multiple Puppys by
creating a directory on the drive, extract the iso into that directory, add the bootloader stanza and boot them up...all without tinkering with
your storage drives formatting, partitioning, etc.
Wiz

[melodie11]

Hello,
I am trying BookworkPup32 latest version (BookwormPup32-23.12-240504.iso) in Virtualbox, in order to test it to eventually install it to some oldies (ie: an Asus eeepc netbook), and I stumble upon the installer that does not start. So I have started digging, and sorry I can't copy paste for now, but here is a screenshot of my finding:

https://yourimageshare.com/ib/wGsQHm6McZ

And it appeared no package with this name (gtkdialog) could be found, nor a package containing the file missing (using apt-file search which I installed in order to search).

Any thoughts on that?

Best regards,
Mélodie

[sonny]

@melodie11

Someone or some of us will get back to you shortly.

[melodie11]

Thanks sonny!

[BologneChe]

Hello,
I am trying BookworkPup32 latest version (BookwormPup32-23.12-240504.iso) in Virtualbox, in order to test it to eventually install it to some oldies (ie: an Asus eeepc netbook), and I stumble upon the installer that does not start. So I have started digging, and sorry I can't copy paste for now, but here is a screenshot of my finding:

https://yourimageshare.com/ib/wGsQHm6McZ

And it appeared no package with this name (gtkdialog) could be found, nor a package containing the file missing (using apt-file search which I installed in order to search).

Any thoughts on that?

Best regards,
Mélodie

Type puppyinstaller in the terminal.

[BologneChe]

Why would you want to make anything difficult to use?

Because the normal Linux "full install" is not the more common method of using Puppy Linux versions. Puppy and most derivatives on the forum
are designed to be "frugal installed", which means they take less room on storage, they don't have to have a full partition on the storage device,
and some applications are designed to be loaded as you go (SFS load/unload). SFS on the fly doesn't work well with typical full partition installations.
Most of the Puppy Linux developers go to great lengths to keep SFS file handling intact, and getting help on the forum with "frugal install" is fairly
easy and many forum members will help a new user. The primary advantage of Puppy's frugal method of installation is no need to partition, format
then install the OS as is typical in other distros installers. You can simply make a directory (or folder in Windows) and extract the files from the
ISO into that directory, and add a stanza to your bootloader, or if totally new, use a bootloader installer to create a bootloader configuration.
With a frugal install you still get the complete operating system, but it uses much less in storage space. You can even try multiple Puppys by
creating a directory on the drive, extract the iso into that directory, add the bootloader stanza and boot them up...all without tinkering with
your storage drives formatting, partitioning, etc.
Wiz

The installer is useful if you want to test in a virtual machine. I understand very well the developer's motivations but we must also take into account the user's needs.

[peebee]

Hello,
I am trying BookworkPup32 latest version (BookwormPup32-23.12-240504.iso) in Virtualbox, in order to test it to eventually install it to some oldies (ie: an Asus eeepc netbook), and I stumble upon the installer that does not start. So I have started digging, and sorry I can't copy paste for now, but here is a screenshot of my finding:

https://yourimageshare.com/ib/wGsQHm6McZ

And it appeared no package with this name (gtkdialog) could be found, nor a package containing the file missing (using apt-file search which I installed in order to search).

Any thoughts on that?

Best regards,
Mélodie

Hi Melodie

The file is actually : /usr/lib/gtkdialog/xml_info_gtk2

dotpup is a very old script - probably not used for many years!! It has been wrongly patched by the build process - will be fixed in future builds.

[melodie11]

Thanks peebee, but I am giving up, because after install (in virtualbox) I realized it is not working the way classic distributions do : root as the default session and having to indicate which apps are to be started as the default (dog name) user, is not the way I can make users adopt a Linux setup for their daily use.
But thanks for the help!

[mmcdonald22]

Thanks for this distro. Works great! Have Wine.SFS, Dosbox, Palemoon, Chromium 124, FirefoxESR, Winamp, SPFSE, Bleachbit all working. Runs fast! Daily driver now. Easily copies from one machine to another (whole folder) run grubdos (old version) and it works same on new work laptop.

[mmcdonald22]

Screenshot2.png (397.45 KiB) Viewed 12824 times

[peebee]

Ahhhh - that shows BWP64 - not BWP32 - wrong thread??

[BologneChe]

Outstanding work as expected from you

[wanderer]

hi peebee and bookworm team

thank you for doing all this work
and creating this masterpiece

in 10 months we are going to have to decide
what our new distrowatch candidate will be

do you think we should upgrade bookworm ?
or do you think we should consider another candidate ?

i will report what you suggest
on the whats up in puppy world thread so everyone can see it

wanderer

[wanderer]

hi peebee

using your bookworm32 now

was afraid to switch from my upup32

but this one is fantastic

do you have a firefox.sfs file for it
edit never mind i forgot about the get browser feature

thanks

wanderer

[wanderer]

hi peebee

what do you think about just making your bookwormpup32 better and better
and leaving it as our candidate on distrowatch

do you have another one of your pup32s you would prefer

i do like debian
and think it will be supported long term

wanderer

[somge]

Hello!
I tried the latest release of Sep7 I guess on Aspire One 2Gb RAM, booted from a USB stick. All went well until connecting WiFi then stuck at scanning for networks. Same thing happens if I start with Bluetooth. Bt was exactly the reason that made me try the latest Bookwarm.
Currently I run NoblePuppy32 without any hickups, the only thing missing is Bluetooth.
I wonder if it would be fixed?

[peebee]

Hello!
I tried the latest release of Sep7 I guess on Aspire One 2Gb RAM, booted from a USB stick. All went well until connecting WiFi then stuck at scanning for networks. Same thing happens if I start with Bluetooth. Bt was exactly the reason that made me try the latest Bookwarm.
Currently I run NoblePuppy32 without any hickups, the only thing missing is Bluetooth.
I wonder if it would be fixed?

What wifi? What BT? hardware: lspci lsusb

Maybe missing firmware........ any error messages from dmesg ? In a terminal:

dmesg | grep firm

[somge]

Below Lspci/lsusb output.
Hardware/firmware missing: hardly so because I'm sending this via WiFi under NoblePuppy32.

00:00.0 Host bridge: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx DMI Bridge
00:02.0 VGA compatible controller: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller
00:02.1 Display controller: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller
00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 2 (rev 02)
00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 (rev 02)
00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 (rev 02)
00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation NM10 Family LPC Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation NM10/ICH7 Family SATA Controller [AHCI mode] (rev 02)
00:1f.3 SMBus: Intel Corporation NM10/ICH7 Family SMBus Controller (rev 02)
01:00.0 Ethernet controller: Qualcomm Atheros AR8132 Fast Ethernet (rev c0)
02:00.0 Network controller: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01)

Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 04f2:b175 Chicony Electronics Co., Ltd 4-Port Hub
Bus 002 Device 004: ID 0930:6545 Toshiba Corp. Kingston DataTraveler 102/2.0 / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 0489:e011 Foxconn / Hon Hai Acer Bluetooth module

[peebee]

Below Lspci/lsusb output.
Hardware/firmware missing: hardly so because I'm sending this via WiFi under NoblePuppy32.
02:00.0 Network controller: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01)

Bus 005 Device 002: ID 0489:e011 Foxconn / Hon Hai Acer Bluetooth module

They have different firmware - different fdrv

What is the output from dmesg | grep firm ?

Try the fdrv from NoblePup in BoolwormPup