BionicPup32 (UPupBB) (27 June 2020)

[TiredPup]

@williams2 wrote:

sudo asks for a password.

sudo asks for spot's password.
root's password will not work.

I don't understand. Why use sudo on puppy linux?

[mikeslr]

@ gera,

Puppies neither require sudo, su nor similar as they already run as root; neither do they use apt (or synaptic). Perhaps someone else can advise you how to install a key. I've never been able to figure it out.

However, if you already have a Windscribe account probably the easiest way to use it under Puppies is to use a firefox-quantum web-browser and the Windscribe addon. https://addons.mozilla.org/en-US/firefo ... ppver=69.0.

I can think of several alternatives. One is to switch to a DebianDog --look in the Projects Section. DebianDogs closely follow debian's/ubuntu's installation routines including (I think) how to add repositories.

Another alternative is to install Pkg - CLI package manager if it's not already in Bionicpup32. http://murga-linux.com/puppy/viewtopic. ... 531#985531. See that thread for instructions.

The third is to use OpenVPN, then follow the instructions of this thread, http://murga-linux.com/puppy/viewtopic. ... 88#1017988. I think this version, http://www.murga-linux.com/puppy/viewto ... 455#986455, is 32-bit and may work with Bionicpup32. If not, ask on that thread.

[john4gaming]

I understand and some way to install Spotify on BionicPup32?

[perdido]

@john4gaming wrote:

http://www.murga-linux.com/puppy/viewtopic.php?t=82034
http://www.smokey01.com/tempestuous/spo ... .4.183.pet

@tempestous wrote:

Spotify client for Tahrpup 6 & Slacko 5.7

Here is the official Linux Spotify client.
UPDATE Aug 19 2015 - now at version 0.9.4.183.

Under Linux one of the dependencies is Qt4

Bionicpup 32 does not have QT4. Bionicpup32 has QT5. QT4 is an older version of t he QT libraries and was current at the time Ubuntu Trusty Tahr and Tahrpup 6.0 were released in 2014. The version of Spotify provided in that post was provided in 2015.

The short of it is that version of Spotify will not run on Bionicpup out of the box and it may not run at all on Bionicpup given the age of the software.

Forum member festus made an .sfs of QT4 for bionicpup 18.05 that would satisfy the QT4 requirement.
It also works ok in bionicpup 19.03
http://murga-linux.com/puppy/viewtopic.php?t=113302

.

[TiredPup]

Perdido wrote:

Forum member festus made an .sfs of QT4 for bionicpup 18.05 that would satisfy the QT4 requirement.
It also works ok in bionicpup 19.03
http://murga-linux.com/puppy/viewtopic.php?t=113302

Perfect! I looked but did not find hoping to be of help. I do know that there is a 64 bit bionicpup derivative by Exton that has Spotify pre-installed.

[glene77is]

to : PeeBee

Thank you for providing such very good UpupBB systems.
I have read through your code, making notes, and adding my echo markers.

EDIT 200108 ***Problem Solved***
Thank you, PeeBee.

###########################################

My file system has this directory:
/initrd/mnt/dev_save/pup_UpupBB+16/upupbbsave-BB19+16-0101

I did find the script:
/initrd/DISTRO_SPECS .

containing this line:
DISTRO_PUPPYDATE='Dec 2019'

I suggest that this system constant
can identify the Build Date of the current UpupBB.
as long as PeeBee produces only one re-build per month.

SO, now I can identify the various running UpupBB systems,
+11, +12, +13, +14, +15, +16 !
at runtime with a "splash"
by reading this constant and displaying it
in my special "system signature" when rc.sysinit is running,
which is documented below.

###########################################

Also,
My UpupBB savefolders are in are in the 30 to 60 MB range
... Very Small !
Very Quick to Backup via my version of 2Byte hot backup.

__________________________________________________
We make use of SFS-load-on-the-fly v.3.0" for
"U-Lite browser" ,
"Iron-56 browser" ,
"Libre-Office 6.3.2",
"Gimp 2.6 for Lucid".
We seldom call for "snapmergepuppy"
in order to reduce internet Browser dumping into the SafeFolder.

__________________________________________________
Tip for Users :
We have, sometimes, three open Puppy systems, just for "tinkering' ,
and in our advancing years, we get them mixed up.

So, we insert a "signature" into the header of each main script
which splashes colorfully each time the script is run:
"rc.sysinit, rc.shutdown, sfs_load, fixmenus, rc.update, etc.
and sometimes little date-time markers so we can mark "time-usage".

For the record, our "System Signature Line"
is pre-pended to each major script ( rc.sysinit, rc.shutdown, rc.update ).
The code is essentially these simple, colorful lines:

lcMsgStr="UpupBB"
lcMsgOS="19.03+16"
/bin/echo -en "\\033[0;39m" > /dev/console ### clear color
/bin/echo -en "\\033[10G\\033" > /dev/console ### left margin
/bin/echo -en "\\033[1;37m*" >> /dev/console
/bin/echo -en "\\033[1;33m*" >> /dev/console
/bin/echo -en "\\033[1;32m*" >> /dev/console
/bin/echo -en "\\033[1;31m[" >> /dev/console
/bin/echo -en "\\033[1;36m : ${lcMsgStr}" >> /dev/console
/bin/echo -en "\\033[1;34m : ${lcMsgOS}" >> /dev/console
/bin/echo -en "\\033[1;31m]" >> /dev/console
/bin/echo -en "\\033[1;32m*" >> /dev/console
/bin/echo -en "\\033[1;33m*" >> /dev/console
/bin/echo -en "\\033[1;37m*" >> /dev/console
/bin/echo -e "\\033[0;39m" > /dev/console

__________________________________________________
Also,
We have been inserting an identifying line into the PUPSTATE file
by inserting simple BASH code into "sysinit"
in order to echo my identifier strings

id='=========================
id='...UpupBB-1903-Kernel=4.9.163'
id='...Distro: BionicPup32 19.03 +12'
id='========================='

at the bottom of the PUPSTATE file
and this runs each time I boot UpupBB.

__________________________________________________

Tip for Users :
In the /usr/shared/audio directory,
try renaming a "2barks.mp3" to replace
the M$XP "sys-login.mp3" melody .

__________________________________________________
( Summary )
So, to PeeBee , I say
This is the best written Puppy/Ubuntu system you have put together.

[peebee]

Hi @glene77is

That is tricky as the iso is renamed after the build process....

You can always download:
https://sourceforge.net/projects/zestyp ... t/download
and compare the md5 checksum or the build_date provided by Menu->Notes

[perdido]

This issue is solved - see the edit at the bottom of this post.
--------------------------------------------------------------------------------------

Noticed a tiny issue with the "places" icon placement in the upper-right corner of the screen when using the "Original Pup" desktop theme in BionicPup32
Theme is installed from - Applications-->Desktop-->Puppy Theme Manager-->Original Pup

The "places" icon placement in the "Original Pup" desktop theme becomes an issue when a program window is at full-screen and you try to click the "X" to close
the full-screen program window - the "places" icon can pop up over the "X" and covers up the "X" preventing the mouse pointer from clicking the "X" - so that when you
mouse-click to close the window the "places" menu comes up instead - Especially if you are fast and not real careful with the mouse (like me) all it takes is the
pointer to touch the top edge of the screen and the icon pops up over the "X" that closes the window

The "places icon automatically shows up in the far right-top corner of the screen after choosing the "Original Pup" theme - No way to move or remove it
Maybe someone knows the solution to get the "places" icon repositioned?

See 2nd pic for reference, this happens when trying to close a program window that uses the whole screen area.

EDIT ***Problem Solved***
Found a solution.
The places icon is considered a "tray" when you switch over to "Original Pup" desktop theme. Part of the "new" desktop handling system, I suppose it has to be present so here is how to hide it.

In the Menu-->Desktop-->Desktop Settings-->Tray-->Placement
That will show a grid of 9 squares representing where on desktop you want your tray. In this case it positions the "places" icon thingy and not the tray. I moved the position of the tray to lower left (see top pic)
and the real tray swallowed the "places" icon thingy - it no longer shows in the "Original Pup" theme.

[Mike Walsh]

@ john4gaming:-

The whole 'issue' with running any of the Chromium 'clones' is that there's no consistency with the way they run.

Modern Chromium, along with its 'offspring', Google's Chrome, hasn't run as root since around version 61/2. Flashpeak's SlimJet has only recently switched to insisting on being run as 'a user'.....and SRWare's Iron (a perfect copy of Chrome itself) will still, to this day, run as root. I download the tar.xz packages from the SRWare forum link, then re-build/re-pack them to run as root. And that's the way I run it. Much easier.

--------------------------------------

@ Gera:-

As Mikeslr has said, Pups don't run as a 'normal user', nor do they use the dozy 'sudo' system. Sudo is fine where you've got several different people, all using terminals, and acessing a common system - it's necessary, even - but in Puppy (a 'hobbyist' system, where invariably just one person runs it, along with full admin privileges), there is absolutely sod-all point in having to request access to your own system.....is there? Think about it.

With Pup, you learn to be a bit more careful, that's all. Even so, it's only a 5-minute job to re-install/restore from a backup, so it's not perhaps as critical as with most of the mainstream distros.....

BTW; no Puppy, to the best of my knowledge, uses RPM packages without some modification.


Mike.

[OscarTalks]

DeaDBeeF 1.8.2 compiled from source in BionicPup32 and including all optional dependency libs. Only pulse is disabled. Notify plugin is included but you have to enable it in Preferences if you want it to display pop-ups.

Recent Puppies have Dunst desktop notification daemon included and running. Not sure if people have it doing very much. I might start another thread about it. It does work with DeaDBeeF. I compiled latest version of Dunst (1.4.1) which has better support for displaying icons in pop-ups and I made a few tweaks to the configuration file for it. Restart X after installation, it will display a startup confirmation notification.

@peebee
The package libcurl3-nss (runtime, not -dev) is needed by DeaDBeeF, missing from this Puppy but apparently not missing from others? There is no libcurl3-nss-dev but the corresponding -dev file libcurl-nss.so is supposed to be provided by libcurl4-nss-dev (note the number difference 3 and 4) but that is missing as well, so perhaps check that all files from that package are in the devx.

I am still finding that symlinks (of shared libs) are NOT copied into the new dir when running new2dir make install although they are correctly installed into system. Happens with ScPup as well so something at the WoofCE level perhaps?

Packages uploaded for testing:-
http://smokey01.com/OscarTalks

[rockedge]

When runnning as root sudo can be used to run programs or scripts as another user which can be helpful at times

Code: Select all

sudo -u spot some_program.sh

-

[perdido]

If you are looking for a virus scanner.

clam anti virus compiled in bionicpup32
http://www.murga-linux.com/puppy/viewtopic.php?t=118996



.

[B.K. Johnson]

peebee took the issue of long pathnames causing the incomplete display at the left to GitHub. After it was closed as too difficult, I thought I'd do a Frankenstein using MochiMoppel's dynamicmenu_recent.sh.(Thanks Mochi) The result can be seen in screenshot, ruplaces.png. If you are a Recently used user, please note that this version operates differently from that OOTB in the following respects.
1. Only the file names are displayed, not paths.
2. When a previously listed file is renamed, deleted or moved, it is excluded from subsequent lists.

I can do without the path. I can easily and quickly see the path in the ROX header when I click the file. The contents and file attributes are discernible in the usual way.

To modify your Recently used,

Code: Select all

 
Download the attached [i]menu_build_recent_docs.gz[/i] to anywhere convenient.
Remove the fake .gz 
Copy the [i]menu_build_recent_docs[/i] file to /usr/local/jwm_config, overwriting the existing file.

You can test immediately, but to make the change permanent, either click the Save icon on the desktop or save the session at shutdown. The latter is safer. Use the former only if there is plenty of free space in your personal storage file.

Attachments: ruplaces.png, menu_build_recent_docs.gz

[peebee]

5-oct-2019

iso md5 = 52a591deae87d71fe88451a392cc8564 bionicpup32-8.0+13-uefi.iso

see post #1

Ubuntu updates....

[perdido]

Hi peebee
One of the changes I just noticed between bionicpup1805 and bionicpup1903 is the BootFlash USB installer. I like it Very nice, thanks for the useful tool!

GParted just needs to catch up now, it does not see all 3 partitions just a big iso9660 CD disk. All three partitions are available on the desktop when booting from the USB stick.
Attached a pic at the bottom of the post.

Some background for reference;
If you like the security of running from a live CD the new BootFlash USB installer can give you the same security from a usb stick. You may think "so what? - we
could always dd the hybrid iso image to usb stick". What makes the BootFlash USB installer a great tool is that it will automatically recover the unused space on the usb
stick by resizing the partitions, that is something that I always had to manually do using tools from different systems.

Initially when you dd a hybrid .iso to usb pen drive it turns the whole usb stick into a big iso9660 write protected CD disk - getting the unused space back can be troublesome.
This new BootFlash USB installer resizes the partitions and recovers the unused space into an extra ext2, ext3, ext4, fat32, vfat, ntfs (your choice) formatted partition automatically.

#############################

EDIT - Some additional informaton about significant differences between upupbb 18.05 and bionicpup32 19.03 concerning remastering and writing a remastered .iso image to usb pen
drives using the BootFlash USB installer in BionicPup32 19.03. For best results I recommend using only the BionicPup32 19.03 hybrid .iso either in its original form or as a remastered
custom .iso. The reasons for this recommendation are listed below.

1.Bionicpup32 19.03 can create a custom remastered .iso while retaining the properties of its hybrid .iso and can subsequently write that custom .iso to usb pen drive where it will be fully
functional and capable of using the extra space created on the usb stick for storage after using the BootFlash USB installer. option.

A remastered custom Upupbb 18.05 .iso does not retain the hybrid properties of the original .iso and will fail to boot if installed onto a usb pen drive using the install program in
Bionicpup32 19.03. Additionally the install program will complain that the .iso is not a hybrid .iso which is good. I have not tried other puppy releases with the BootFlash USB
installer in BionicPup32 19.03.

2. The BootFlash USB installer in BionicPup32 19.03 seems to work with all hybrid .iso images and reports(complains) if the .iso image you are asking it to write is not a hybrid .iso
- it will let you write it if you wish but the usb stick will not boot.

Please note that this does not mean that all hybrid .iso images written with the BootFlash USB installer will be able to see or use the additional drive space made available on the
written-to USB drive. An example is the upupbb_18.05 .iso as released, is is a hybrid .iso but does not see nor can it use the space freed up on the usb drive by the new BootFlash USB
installer in BionicPup32_19.03, - maybe due to operating system limits but would need further investigating to identify the exact cause.

In the case of a remastered custom .iso in upupbb 18.05 not retaining hypbrid capability, there may be differences in how the remastered custom .iso is produced in upupbb 18.05 or just
the limitations of the upupbb 18.05 operating system . FWIW, that issue would need further testing by remastering the upupbb 18.05 /livecdbuild/ directory using the Remaster Puppy Live-CD
tools in the BionicPup32 19.03 release - if that is even possible. Maybe I will try that and see if that produces a bootable usb that can read the additional space (would be interesting
mainly due to applying that process to other .iso puppy variants, both hybrid and non-hybrid in the chance it will produce a bootable usb that can use the reclaimed space on the usb stick.)

In summary, if you plan on doing a remaster and writing it as a live-cd to a usb pen drive then stick with the Bionicpup32 19.03 releases to guarantee that the remastered .iso will
retain its hybrid properties and will be capable of using the recovered drive space on the usb stick that the Bionicpup32 19.03 install program is now capable of providing.

Will be doing more testing to see what I can get away with using other puppy .iso variants remastered with the tools in BionicPup32 19.03

[OscarTalks]

Some issues that may only arise when compiling.
Now testing in 8.0+13

The file /usr/bin/xxd is a symlink to busybox which errors out.
Suggest replacing this with the real xxd executable from the xxd package (which is now separate but in earlier distros was part of the vim-common package).

The package libglib2.0-dev-bin should perhaps be added to the devx. The executable glib-compile-resources is in this package and was needed in a test build of netsurf-3.9

The libcurl situation still seems a bit peculiar. I think you are still missing a libcurl.so development symlink from the devx and this should be a link to libcurl.so.4.5.0 (the real lib) and not to the other libcurl "flavours" such as libcurl-gnutls or libcurl-nss. In the case of the latter, remove the dev package fully if the shared libs are not present (which they seem not to be as nothing actually depends on them as things are). The test netsurf build was trying to link to libcurl-nss and then didn't work when built. I had to add libcurl.so manually. You might also need a libcurl.so.3 for legacy as well as the libcurl.so.4

Also, I have re-compiled and re-uploaded DeaDBeeF-1.8.2 with the libcurl-nss dependency now corrected and linking to the usual libcurl.so.4

[Gera]

I have BionicPup32, August 2019 edition.

I have save file *.4fs on hard drive. I noticed that every 5 seconds hard drive is accessed even when nothing is happening. I suspect that operating system(OS) is automatically saving changes to save file *.4fs. How can I increase that period to 60 seconds?

And another issue is Light Web Browser that freezes ~once per day (I suppose it's Firefox 48, build-in browser in August edition). It freezes OS unexpectedly, when it happened usually I had YouTube pages with videos opened in 2 tabs. Nothing helps: ctrl-w to close tab or ctrl-shift-w to close browser window. Mouse pointer is slowed and soon everything hangs completely, plus CPU temperature is rising. Only ctrl-alt-backspace helps to restart X. Is that a known issue? What can help to prevent that hanging?

[bigpup]

I have save file *.4fs on hard drive. I noticed that every 5 seconds hard drive is accessed even when nothing is happening. I suspect that operating system(OS) is automatically saving changes to save file *.4fs. How can I increase that period to 60 seconds?

When you say not doing anything.
Is Bionicpup32 just booted to a desktop?
That is all that has been done?
What is Bionicpup32 installed on and booted from?
What format is the partition the save file is on?

[perdido]

I have BionicPup32, August 2019 edition.

I have save file *.4fs on hard drive. I noticed that every 5 seconds hard drive is accessed even when nothing is happening. I suspect that operating system(OS) is automatically saving changes to save file *.4fs. How can I increase that period to 60 seconds?

And another issue is Light Web Browser that freezes ~once per day (I suppose it's Firefox 48, build-in browser in August edition). It freezes OS unexpectedly, when it happened usually I had YouTube pages with videos opened in 2 tabs. Nothing helps: ctrl-w to close tab or ctrl-shift-w to close browser window. Mouse pointer is slowed and soon everything hangs completely, plus CPU temperature is rising. Only ctrl-alt-backspace helps to restart X. Is that a known issue? What can help to prevent that hanging?

Hi Gera,
There is a menu item that can control save interval.

Applications-->Setup-->PupControl Panel-->Event Manager-->Save Session

.

[bigpup]

That only works in pupmode 7 or 13 operation.

Pupmode 12 directly writes to the save all the time.