(old)Puppy Linux Discussion Forum

BusterPup 8.0 CE (Beta-1)

• Traditional Woof-CE build of Puppy Linux
• Based on 32-bit Debian Buster binaries (LTS: 5 years)
• Runs efficiently on 32-bit and 64-bit PC hardware
• Low-memory footprint when booting
• Modern long-term maintenance kernel: 4.19.56-i686-pae
• Desktop: JWM or optional FbPanel/Openbox environment
• Default wallpaper: based on futurePrototype by Alex Makas

Although full package support for the Dpup Stretch variant of Puppy Linux will continue through June 2022, the developers of Debian Linux have now transitioned from the version 9 "Stretch" series to the version 10 "Buster" series for the current stable release.

Keeping pace with Debian Linux development, BusterPup has evolved as a natural transition from Dpup Stretch, sharing a similar desktop presentation that is functional and easy to use.

The 32-bit BusterPup and 64-bit DPupBuster by josejp2424, though divergent in desktop presentation, are complementary products of the Woof-CE build system. To that end, this release is a simple alternative build of Puppy Linux based on Debian Buster binaries. Undoubtedly, additional Dpup variants will follow as Woof-CE and other build systems are further refined in the coming months.

The traditional Woof-CE build system for Puppy Linux continues to evolve at a rapid pace and now includes code once considered experimental. This build of BusterPup derives primarily from Woof-CE code defined through 7 June 2019, though additional code commits after that date are selectively included.

Caveats

1 - The default desktop environment of BusterPup is generated by JWM (Joe's Window Manager). For those who prefer the Openbox window manager, the included adrv.sfs provides an optional desktop environment (FbBox) which integrates Openbox with FbPanel. Go to Menu -> Desktop -> WM Switcher.

With some kernels the Evdev keybindings for certain keyboards may have mapping issues in the Openbox desktop environment. For example, the PrtScr, Up and End keys may not function correctly. If you observe this issue in the FbBox desktop environment, please go to FbPanel configuration -> Plugins tab -> Key Bindings -> select 'true' -> click Apply -> then restart X-server.

2 - Compared to its Dpup Stretch predecessor, BusterPup has increased in size due to the inclusion of more kernel drivers, additional library dependencies and, of course, a greater complement of default menu applications than typically found in Puppy Linux. Even so, this distro has a relatively small memory footprint when booting to the initial desktop.

3 - In this release, keyboard and mouse actions are managed by the Xorg Evdev interface with no dependence on conventional input drivers (kbd_drv.so and mouse_drv.so).

4 - For those with recent Intel processors, the BusterPup kernel defaults to the pstate power scaling driver for Sandy Bridge and newer CPUs. If this driver is problematic for your Intel CPU, add 'intel_pstate=disable' to the kernel line and reboot.

5 - Although BusterPup contains a wide range of built-in WiFi drivers, recent hardware may require updated firmware available in the optional fdrv.sfs (which is automatically loaded when placed in the same location as the puppy_buster_8.0.sfs).

6 - The PulseAudio sound server is a dependency for audio when the Firefox Quantum Browser is optionally installed. However, in BusterPup, the smaller 'apulse' package provides PulseAudio emulation for ALSA. To run Firefox Quantum, prepend 'apulse' to the command line, for example, 'apulse firefox'.

Downloads

buster-8.0-uefi-k4.19.56.iso (12-Jul-2019)
http://smokey01.com/radky/Woof/buster-8 ... .19.56.iso
md5: 211066320039ed2248d4b007ad4bf606

Optional fdrv.sfs with comprehensive firmware (20-Jun-2019)
http://smokey01.com/radky/Woof/fdrv_buster_8.0.sfs
md5: 0d16c2a1968cf34463a8c1b3f63a8020

Devx (12-Jul-2019)
http://smokey01.com/radky/Woof/devx_buster_8.0.sfs
md5: 62c6dd00f70cd6c4ab749b840b6ca352

Kernel Sources (12-Jul-2019)
http://smokey01.com/radky/Woof/kernel-4 ... buster.sfs
md5: 0224b6687727247a1ac00b2a76eac5f6

Default JWM Desktop

Reserved

Reserved

Reserved

Reserved

When I run claws-mail in this BusterPup, and try to get mail, I get

claws-mail: symbol lookup error: /usr/lib/i386-linux-gnu/libetpan.so.20: undefined symbol: SSLv23_client_method

It happens with SFS-loaded claws-mail 3.16 or with pet-installed claws-mail 3.17. claws-mail 3.16 has been working well in DpupStretch.

Any help will be much appreciated.

Thank you,
Sheldon

Radky congratulations...
Sure it will be a great puppy like it is DPUP Stretch.

sheldonisaac wrote:Any help will be much appreciated.

Sheldon

@Sheldon,

BusterPup has the Sylpheed email client.

However, if you prefer claws-mail, please try claws-mail_3.17.3_busterpup.pet:

http://smokey01.com/radky/Apps/claws-ma ... terpup.pet

josejp2424 wrote:Radky congratulations...
Sure it will be a great puppy like it is DPUP Stretch.

@josejp2424,

Thanks for your kind comments, and my best wishes as you continue development of DpupBuster64.

Thanks radky for this latest release, you've been very busy.

New frugal install to internal SSD in Dell 3350 Laptop Core i3-5200U. After initial setup and connecting to internet, I attempted to launch palemoon, which didn't run. Thus was first thing I attempted after start up.

There appears to be an issue that palemoon won't launch using the desktop launcher contained in the trays or directly using the defaultbrowser.desktop or palemoon.desktop. If I navigate to /opt/palemoon the executable runs successfully.

I checked the /usr/bin/palemoon in buster 8.0 and latest stretch 7.5 and they are the same, so don't know why palemoon won't run.

Terry H wrote:There appears to be an issue that palemoon won't launch using the desktop launcher contained in the trays or directly using the defaultbrowser.desktop or palemoon.desktop. If I navigate to /opt/palemoon the executable runs successfully.

Terry,

For me, palemoon launches correctly from the main menu, or by accessing the tray launcher, or by clicking defaultbrowser.desktop or palemoon.desktop.

All of the above execute 'palemoon' (i.e., /usr/bin/palemoon), which in turn calls /opt/palemoon/palemoon.

Is it possible you have a corrupt download of BusterPup?

radky wrote: Is it possible you have a corrupt download of BusterPup?

I checked the checksum, which matched. As terminal output above, just odd that 2 desktop files and one executable won't run, but palemoon.bin executes successfully.

I'll re-download and do again.

Hi radky.

Can you produce a diff, or some two-columns comparison of the main execs, between
your Buster and josejp2424's? TIA. So users can readily see the difference.

On another level, I can't see the point of providing a competing new DPupBuster when an
excellent one has been published 5 months ago.

Regards.

hi Radky,

not a thorough test but running well in a vm.
doesn't boot to desktop on my main comp and i have to choose the frame buffer option. this may be my setup as i've had bionicpup do this before and will have to look into it.

a few issues noticed so far ....

the kernel needs to be recompiled in the released iso as the nvidia driver complains about the wrong gcc version used to compile the kernel.

i tried compiling a new kernel and needed to re-install libglib2.0-dev. this may be a woof issue with the package-template or some deps might be missing.

also i needed to install libncurses-dev.

vmware-tools, to allow shared folders, needs some directories in /etc
rc0.d
rc1.d
rc2.d
rc3.d
rc4.d
rc5.d
rc6.d
(these are now in woofce)

that's all so far, will keep testing

good work!

Hi radky,

It has been awhile lol, will sown load and give it a spin

Terry H wrote:

radky wrote: Is it possible you have a corrupt download of BusterPup?

I checked the checksum, which matched. As terminal output above, just odd that 2 desktop files and one executable won't run, but palemoon.bin executes successfully.

I'll re-download and do again.

Re-downloaded and checked md5sum which matched.

On initial boot I did same procedure as previous, selecting to run palemoon as spot on first run setup. Same errors.

Rebooted pfix=ram and didn't select to run palemoon as spot, defaultbrowser / palemoon executes correctly. So a difference between stretch 7.5 and buster 8.0 when running internet apps as spot.

Edit: Same error message returned when running from terminal: run-as-spot palemoon

radky wrote:

sheldonisaac wrote:Any help will be much appreciated.
Sheldon

@Sheldon,

BusterPup has the Sylpheed email client.
However, if you prefer claws-mail, please try claws-mail_3.17.3_busterpup.pet:
http://smokey01.com/radky/Apps/claws-ma ... terpup.pet

Many thanks, radky! I just came home and tried this. Downloaded that claws-mail pet.
Booted BusterPup 8.0 without the savefolder.
Installed the claws-mail pet. Works well!
Later today I will boot this BusterPup, and try it again.
---------------------
Made a savefolder. claws-mail_3.17 still works well!

Thanks again.
Sheldon

mirrored here: http://archive.org/details/Puppy_Linux_BusterPup

Terry H wrote:

Terry H wrote:

radky wrote: Is it possible you have a corrupt download of BusterPup?

I checked the checksum, which matched. As terminal output above, just odd that 2 desktop files and one executable won't run, but palemoon.bin executes successfully.

I'll re-download and do again.

Re-downloaded and checked md5sum which matched.

On initial boot I did same procedure as previous, selecting to run palemoon as spot on first run setup. Same errors.

Rebooted pfix=ram and didn't select to run palemoon as spot, defaultbrowser / palemoon executes correctly. So a difference between stretch 7.5 and buster 8.0 when running internet apps as spot.

Edit: Same error message returned when running from terminal: run-as-spot palemoon

Terry,

We could replace the /bin/su binary with a symlink to busybox.

In a terminal, execute the following three-line code, then try again to launch palemoon as spot:
Thanks

radky wrote:

Terry H wrote:

Terry H wrote: I checked the checksum, which matched. As terminal output above, just odd that 2 desktop files and one executable won't run, but palemoon.bin executes successfully.

I'll re-download and do again.

Re-downloaded and checked md5sum which matched.

On initial boot I did same procedure as previous, selecting to run palemoon as spot on first run setup. Same errors.

Rebooted pfix=ram and didn't select to run palemoon as spot, defaultbrowser / palemoon executes correctly. So a difference between stretch 7.5 and buster 8.0 when running internet apps as spot.

Edit: Same error message returned when running from terminal: run-as-spot palemoon

Terry,

We could replace the /bin/su binary with a symlink to busybox.

In a terminal, execute the following three-line code, then try again to launch palemoon as spot:

Code: Select all

cd /bin
rm -f su
ln -sf busybox su

Thanks

All OK now, palemoon is able to run as spot.

Thank you.