BookwormPup64 10.0.9

[mikeslr]

@Wziris, note the changelog, viewtopic.php?p=89021#p89021 in particular the upgrade to the 6.1.119 kernel. Apparently it lacks the drivers or firmware required by your mouse, keyboard and graphic hardware. If none of the other upgrades are essential, then the easiest solution is return to using Bookwormpup64 10.0.8. Most of the other changes can be individually installed, if desired. The alternative --probably more work-- involves swapping kernels but will provide these changes:

• Update run-as-spot for improved support of chrome-based browsers (thanks fredx181)
• Update Graphite_dark GTK theme for improved visibility of text on a dark background

This can be done by replacing 0.9's kernel with that used in 0.8. That requires substituting 0.8's vmlinuz for 0.9's, and also fdrv_dpupbw64_10.0.8.sfs and zdrv_dpupbw64_10.0.8.sfs for those ending in 0.9, renaming the substituted files to 0.9. The initrd file's arguments spell out what other files will be recognized. viewtopic.php?t=5818.

I'd start by just replacing fdrv_dpupbw64_10.0.9 with 0.8. fdrv's contain firmware and are 'kernel independent': can be used with any kernel having the right architecture -- 64 vs. 32bit, user-merged vs. not. If only the required firmware was missing from 09's ISO, a reboot after that substitution may correct all or some of the issues. If not, then you'd have to replace both the vmlinuz and the zdrv. Zdrv holds drivers which are complied against a specific kernel. Technically, vmlinuz is the kernel; but Puppy devs publish 'hugh-kernels' which also contain drivers (zdrv) compiled against it.

[ozsouth]

@Wziris - as mikeslr says, reverting to 10.0.8 won't cost you much, since it works. If you decided to swap kernels, the kbuild...sfs is also specific to each different BookwormPup, & dpupbw64initmodules.txt (if present) must be also deleted before rebooting into a new version.

[Wziris]

I tried again keeping my dpupbw64save.64 file from version 10.0.8
EVERYTHING works!

[don570]

BookwormPup64 10.0.9 works on my HP Elitedesk 800
Frugal install

Earlier versions work as well.

Suggestions:
1) Right click menu on a mounted partition and use pfind
2) Include ripmime so Uextract can rip open an mhtml file
http://distro.ibiblio.org/fatdog/packag ... 6_64-1.txz
3)When setting up Samba server it would be useful to warn the user to launch the firewall setup app
to allow the Samba server. An inexperienced user wouldn't know that the firewall has to set up.

Screenshot-firewall.png (80.09 KiB) Viewed 1799 times

[don570]

When I copied a link (Search with pfind) to
/root/.config/rox.souceforge.net/SendTo/.inode_mount-point
pfind would do search in a USB drive

Screenshot-pfind.png (33 KiB) Viewed 1715 times

___________________________________
Also I checked 'ripmime' with Uextract and it worked.

[don570]

When I reinstalled Uextract from Smokey repository
the install program put an Uextract icon on desktop and put a right click menu item on mhtml files.
Perhaps it checks if ripmime is installed

[bigpup]

Sudo is broken in BookwormPup64 10.0.9 and also in older versions.

I know sudo is not needed normally in Puppy.

But some Linux software will have scripts that have sudo in the commands.
Try to run the script and it stops running at the command with sudo in it.

Here is a recent example:
viewtopic.php?t=13590

For many years, Puppy would have the basic stuff that would let a sudo command work.

I see BookwormPup64 does have sudo in it, but something must be missing.

[radky]

@bigpup

If I understand correctly, since 2022 Puppy provides a dummy sudo function in /root/.bashrc to handle potential calls to sudo when commands or script are executed through an interactive shell (terminal).

For example (in BW64): sudo apt update should run OK in a terminal.

The dummy sudo simply tests if /usr/bin/sudo is available.

If the test is true (/usr/bin/sudo is available): the script in the terminal executes via sudo
If the test is false (sudo not available): bypass sudo and execute without superuser permissions

https://github.com/puppylinux-woof-CE/woof-CE/pull/2950

[bigpup]

OK

I guess the issues I am seeing, are badly written script files, that have commands with sudo in the command.

I tried a test of a few of them.

One script file, did work up to a point, with some of the sudo commands, but stopped on a specific one.
I removed sudo from the command entry and it then seems to have used the command line.
The script proceeded past that line and no error.
Not sure what that indicates?

This was the command line that worked after removing sudo from it:

Code: Select all

sudo echo > /dev/null

So I guess this is not caused by how Puppy has sudo setup to use, but badly written script files.
Maybe having a command that Puppy does not support.

[don570]

On the subject of sudo

I wanted to switch over to spot user. I read the ReadMe file.
The first suggestion worked...
The second suggestion didn't.
Terminal output...
Perhaps it's the BusyBox version however it's the same version as fatdog64 903
busybox-1.36.1-x86_64-1

Code: Select all

# su --login spot
su: unrecognized option '--login'
BusyBox v1.36.1 (2024-12-09 00:28:32 +08) multi-call binary.

User "spot" is currently used in Puppy by DidiWiki.
See the script /usr/sbin/didiwiki-gui, which is run from
the window manager menu, in "Information managers" submenu.

Screenshot 2025-01-15 15.44.53.png (26.07 KiB) Viewed 1028 times

[Clarity]

... 3)When setting up Samba server it would be useful to warn the user to launch the firewall setup app to allow the Samba server. An inexperienced user wouldn't know that the firewall has to set up. ...

This SHOULD be an OOTB setup from WoofCE production for every modern release. Reason: Almost every home has a PC (one or more) as well as smart-phones (one or more) and smart TVs (one or more) existing on the same network (subnet) where files or media is moved around/shared, often.

Hope WoofCE development and its developers see your post and understand this simple solution I offer to ensure smooth use and acceptance of today's distros for the large communities of users who come to their distros.

Hope this is helpful.

[don570]

Hope WoofCE development and its developers see your post and understand this simple solution

BarryK has made the setting up of the firewall pretty much automatic in Easy OS.

[Electricroo]

Ok, Maybe I'm a putz. I've been using various versions of Puppy over the years off and on in old PC's and installing it for others. My USB sticks are showing up in the Rox file manager. But, this is the first time I tried to format or install an ISO to a USB stick in a version of Puppy. I installed Mintstick but it is not seeing the USB sticks?

[bigpup]

But, this is the first time I tried to format or install an ISO to a USB stick in a version of Puppy.

I assume you have BookwormPup64 10.0.9 booted somehow and running the computer.
want to run an installer program from it.

Use the installer programs that are in BookwormPup64 10.0.9

Menu ->Setup->Frugalpup installers

The stickpup ones are specifically for doing installs to USB sticks.

Click on the help to get info on the difference between them.
.

Screenshot.jpg (64.69 KiB) Viewed 674 times

[dejan555]

Well, well, hello old puppy pals!!!
Sorry for being absent for so long.
I didn't even have a PC at home for some time, been even two years or more.
Today I have found some cheap 'mini pc' box (Intel NUC piko n2820) on the marketplace that I bought and hooked up to my TV with HDMI and wireless inputs
Needless to say that I quickly got bored with Windows installed on it that wasn't working very good even if it's freshly installed
So I hit the google search since I know there were easy options for frugal installs of puppy and indeed, I find LICK
Next, I hit the puppy downloads page and this is the first distro on the list, so I download, install through lick and restart and BAM! here I am typing from it!
A pleasant surprise was also the Simple GTK radio that I found in Multimedia and here's the Aardvark Blues blasting from my TV speakers.
Glad to see my scripts are usefull to puppy still, and that puppy is still evolving and that there's still a community I can come back to.

Anyway just wanted to say hi to everyone.
Keep up the good work.

[Clarity]

@radky @rockedge @peebee @dimkr and other forum Debian distro developers

BKWP64 updated.jpg (41.51 KiB) Viewed 526 times

[JusGellin]

Edit: Sorry wrong forum. I actually installed BookwormPup64_10.0.9_nkb. I need to go over there instead.

[bigpup]

In my topic on using the old save.

Portables all working fine, so far.....haven't got 'em all linked in yet, mind you. We shall see.

But does not say what he had to do to link them in.

If the portable has in it the MenuAdd script file.

Run that and see if it now works.

[davids45]

G'day,
I'm having problems with a couple of C-word applications .

CUPS
I need to be able to paper-print with a network Epson WorkForce but CUPS doesn't find the usual driver in Bookworms 1008 and 1009? And use the Epson to scan if anyone has achieved that in Bookworm.

Installation of the Epson driver via rcrsn51's EPPI method works fine in Fossa and other Pups.

The only sign of a response in Bookworm Pups was a one-off appearance of an Epson Backend printer in the CUPS Printers list which did not work. Mostly no new Printer has appeared in the CUPS list.

Is a manual driver installation possible?

CONKY

Also how do I use the sensors module in Bookworm Pups. The MSI Cube I'm using wants the coretemp module which should be read by conkyrc (again, Fossa96 is fine with this).
I think Bookworm has two libsensors installed in its packages, but how do these work (e.g. terminal command is what?)

David S.

[ozsouth]

@davids45 - some things to try:

Cups - when you go to set up printer, with printer connected & turned on, with the latest Cups I've discovered you need to use Administration, then Find New Printers, as this gets the correct connection string. Then try to find compatible model.

For coretemp, I too found that wasn't discovered, so a hack to fix it (works for me) is to use the dpupbw64initmodules.txt file, which is either in the same folder as puppy ... sfs , or you may have to create it.
If it exists and has entries, after the last entry (no spaces) add ,coretemp (note: yes, comma first)
If it doesn't exist, create it with just coretemp in it
On reboot, coretemp should load. This is not generally a recommended procedure, but it worked for me.

[davids45]

G'day ozsouth,

Thanks for the quick reply.

Unfortunately no joy with either try.

CUPS.
I ran EPPI in 1009.nkb but no entry appeared in the Discovered Network Printers CUPS printer list:

CUPS-try-in-BWnkb.png (234.51 KiB) Viewed 176 times

Same result in BW-1008 and BW1009 - no EpsonWF2860 appears in CUPS as available.

CONKY
I couldn't find the exact dpupbw64initmodules.txt file with PFind.
With 'initmodules', found a file with no mention of 'coretemp' in which I wouldn't know where to copy 'coretemp'

initmodules-search.png (141.18 KiB) Viewed 176 times

So still stuck with Bookworms not doing what I'd like and only having Fossa96 to play with on my new Cube.

David S.

[davids45]

G'day,

CUPS was being blocked from installing my Epson WF2860 by the Bookworm Firewall being 'ON' by default from the get-go! Turning the green shield red and it's 'GO' for printing.

My fault really, in that I haven't used the Firewall in any past Pups, so being 'ON' in BW got 'under my guard'. I haven't needed to set-up Puppy on a new (modern) computer for a long time.

Can the firewall be permanently turned off?

Anyway, only loading the 'coretemp' module in Bookworm needs solving for now. Would 'modeprobe coretemp' work, I wonder, if that's the right Linux command?

David S.

[Clarity]

... Can the firewall be permanently turned off? ...

Yes! when on the BKWP64's desktop, at the tray 'firewall' icon, right-click selecting to "quit & remove". Your choice will survive over reboots, assuming you save your session.

Hope this is helpful