BionicPup32 (UPupBB) (27 June 2020)

[gyro]

David, try putting your data partition mounting script in /etc/init.d instead of /root/Startup. It will start earlier. You can put it to the head of the queue by naming it with a 0 at the beginning, eg: 0_mntmydrv.

If you do, remember that scripts in /etc/init.d get called during startup with a parameter of "start" and again at shutdown with a parameter of "stop".

gyro

[davids45]

G'day jrb and gyro,

David, try putting your data partition mounting script in /etc/init.d instead of /root/Startup. It will start earlier. You can put it to the head of the queue by naming it with a 0 at the beginning, eg: 0_mntmydrv.

Thanks for the advice.
I had already seen the name "0_" prefix idea and use it with my mount script in Startup for all my Pups.

I've now tried your tip with /etc/init.d in today's first Pup (LxPupSc-19.04 with the 64-bit 5.0.5 kernel) and it is looking fine. I also added to /etc/init.d a script to load a temperature module now that Boot manager is broken in quite a few Pups (most Bionics I think, Sc (Slackos) are still OK, but this is simpler than running Boot manager anyway).

So I'll slowly work through my Pups with this init.d refinement, and add to new Pups as they come along.

David S.

[Brant]

After so much work, it seems petty to ask for something else, but
would it be a nuisance to post a SHA 256 checksum?

Thanks

[loot]

I know this is elementary, but I'm a simple user.

When I try to copy the updated files (usually just puppy*.sfs) to frugal install directory, I get "protected file system, won't copy" or something like that. I'm on an older BionicPup, so how do I force the copy?

loot

[6502coder]

Sounds like you're trying to update the BionicPup while you're running BionicPup. You can't do that; it's like sawing off the branch of a tree you're sitting on.

Boot your BionicPup with "pfix=ram" and then copy over the new SFS. Or boot into any Puppy from a LiveCD/LiveDVD/LiveUSB and then copy over the new SFS.

[loot]

Actually I'm using a fresh iso and delta.
Also, I tried to delete the adrv file, wouldn't let me do that either.

loot.

[musher0]

Actually I'm using a fresh iso and delta.
Also, I tried to delete the adrv file, wouldn't let me do that either.

loot.

Hi loot.

That's the other branch you'd be sitting on!

All PuppyLinux's have a main puppy_xyz.sfs and a zdrv. The zdrv contains the
kernel modules. So that's two branches you can't cut.

Counting your pupsave file or folder, that makes three.

The more recent Puppies can also have an adrv, an fdrv, and / or a ydrv. So, in total,
in a Puppy, you may have as many as six branches you're not supposed to "cut".

You were considering a career in pruning, I suppose?!

IHTH.

[6502coder]

Actually I'm using a fresh iso and delta.
Also, I tried to delete the adrv file, wouldn't let me do that either.

Um....You need EITHER the latest ISO, OR the ORIGINAL ISO plus the latest delta. If you have the latest ISO, you do not need the delta. If you only have the ORIGINAL ISO and the latest delta, you have to apply the delta to the ISO to produce the latest ISO.

[Sage]

Um....You need EITHER the latest ISO, OR the ORIGINAL ISO plus the latest delta. If you have the latest ISO, you do not need the delta. If you only have the ORIGINAL ISO and the latest delta, you have to apply the delta to the ISO to produce the latest ISO.

Q.E.D. ! Out, out damn deltae!

[peebee]

11-may-2019

iso md5 = 1d3401a56b750cb8589b88015f098fd4 bionicpup32-8.0+5-uefi.iso

see post #1

[sheldonisaac]

11-may-2019
iso md5 = 1d3401a56b750cb8589b88015f098fd4 bionicpup32-8.0+5-uefi.iso
see post #1

Got it. Many thanks.

> ls -lt /mnt/home/upup32/
total 230424
drwxr-xr-x 9 root root 4096 May 11 09:39 upupbbsave-may11
-rw-r--r-- 1 root root 203497472 May 11 07:38 puppy_upupbb_19.03.sfs
-rw-r--r-- 1 root root 2585690 May 11 07:32 initrd.gz
-rw-r--r-- 1 root root 24334336 Mar 14 12:43 zdrv_upupbb_19.03.sfs
-rw-r--r-- 1 root root 5528448 Mar 14 11:46 vmlinuz

[loot]

Howto:
- download .delta and put into same directory as base .iso
- click on .delta to generate new .iso
- check md5 sumcheck of new .iso against *.iso.md5.txt file contents
- click on new .iso to open it
- copy updated files (usually just puppy*.sfs) to frugal install directory
- close new .iso by clicking on it
- reboot
Source: README.txt, updated 2019-04-15

This is what I followed. But I didn't check of the md5 sum of the new .iso; would that make a difference?

I read the adrv contains the web browser and can be replaced. Why couldn't I just delete it?

loot.

[rockedge]

you can

[paulh177]

This all works out-of-the-box for me so far as I can tell, but my needs are fairly simple, except ...

I've gotten used to having to reinstall & reconfigure all my applications every time I want to move to a later Puppy, but JWM config setup seems to have changed out of all recognition, and I can't seem to just copy over the .~/.jwm* files & directory plus the PuppyPin and have my working environment look the same.

Is there a quick/easy way to dump that fcking menu-bar-thing at the top and revert to an old-style icons-on-the-desktop setup?
Or even a slow/painful way?

thanknx

[peebee]

Is there a quick/easy way to dump that ..... menu-bar-thing at the top and revert to an old-style icons-on-the-desktop setup?
Or even a slow/painful way?

Desktop -> Puppy theme manager -> Original Pup -> Apply

[paulh177]

God I feel like a proper user now

To think, I've used Puppy since 2006, and one of my PETs once even made it into the standard distribution ...

thanks tho'

[fishmanluvslinux]

Hey Yall! I am happy to report that this flavor of Puppy Linux works fine on my ASUS Eee PC 900HD Netbook.I was curious how well it would work with my Broadcom Wireless and everything works great out-of-the-box. Great job to everyone involved.

[peebee]

27-may-2019

bffd1a3ae09c7bffd5a40a69a452c5ab bionicpup32-8.0+6-uefi.iso

see post #1

[simes]

Hi, I'm coming back to Puppy after a year or two distracted by other operating systems, so I may have overlooked something simple and if so I apologize. I like the polish and speed of this latest LxPup (1903 update) very much, thank you PB. I downloaded the Chromium SFS and loaded it but Chromium doesn't start. Starting it from the command line produces this message:- "# chromium
/usr/lib/chromium/chromium: /lib/libm.so.6: version `GLIBC_2.29' not found (required by /usr/lib/chromium/libgtk-3.so.0)
chown: /root/spot/Downloads/*: No such file or directory
# EXIT="Exit on mouse-over"
^C
"
...which looks like a GLIBC compatibility problem. What have I missed?
Thank you!

[peebee]

I downloaded the Chromium SFS and loaded it but Chromium doesn't start.

No such problem here..........suspect you have the wrong version of Chromium...........

see:
http://murga-linux.com/puppy/viewtopic. ... 80#1028880