Bionicpup64 8.0 CE

[RedQuine]

Two issues with the upgrade, although one of them is minor:

1. On first boot, I was unable to configure my trackpad with flSynclient. A dialog box popped up, but it only had an exclamation mark in it (no text), and when I clicked OK, flSynclient closed. Once I'd created a fresh pupsave and rebooted, it worked perfectly - so this one's definitely just a minor issue.

2. I decided to be sensible and boot into RAM as suggested. I then created a new pupsave and rebooted.

At this point, I would normally open my old pupsave and copy across my favourite tweaks and quirks to the new one. Unfortunately, this time, the old one appears to have been wiped; all it contains is a broken symlink to /initrd/mnt/tmpfs/pup_rw

Should I have copied everything off it before I rebooted with the new pupsave? I've never had to do that before; unless I upgraded it, the old one was left untouched. Not a disaster as I had a recent backup, but worth mentioning nonetheless.

Other than that, everything's looking great so far. Many thanks!

[666philb]

Two issues with the upgrade, although one of them is minor:

1. On first boot, I was unable to configure my trackpad with flSynclient. A dialog box popped up, but it only had an exclamation mark in it (no text), and when I clicked OK, flSynclient closed. Once I'd created a fresh pupsave and rebooted, it worked perfectly - so this one's definitely just a minor issue.

2. I decided to be sensible and boot into RAM as suggested. I then created a new pupsave and rebooted.

At this point, I would normally open my old pupsave and copy across my favourite tweaks and quirks to the new one. Unfortunately, this time, the old one appears to have been wiped; all it contains is a broken symlink to /initrd/mnt/tmpfs/pup_rw

Should I have copied everything off it before I rebooted with the new pupsave? I've never had to do that before; unless I upgraded it, the old one was left untouched. Not a disaster as I had a recent backup, but worth mentioning nonetheless.

Other than that, everything's looking great so far. Many thanks!

there's been a lot of changes in woofce during bionicpupos development and using old savefiles from the betas isn't recommended and is known to cause problems

[artsown]

Fresh "from scratch" frugal to hard drive of 8.0 using a core i5 and 4 gig
ram desktop. Installation of all my usual stuff was uneventful. It seems that
8.0 is noticeably faster than the 7.9.8 rc.

I noticed that 8.0 has the same old HTOP version 1.0.3 that xenialpup64
version 7.5 has. Ram useage reports are now much lower than they
are on bio 7.9.8 rc with its version 2.0.2 version HTOP. In fact, the
ram useage reports are comparable to xenialpup64. I wonder why
you chose the old and outdated version of HTOP for the 8.0 release?

Anyway, your bionicpup64 is by far the best pup for my purposes, and
I thank you again for it!

Art

[RedQuine]

At this point, I would normally open my old pupsave and copy across my favourite tweaks and quirks to the new one. Unfortunately, this time, the old one appears to have been wiped; all it contains is a broken symlink to /initrd/mnt/tmpfs/pup_rw

there's been a lot of changes in woofce during bionicpupos development and using old savefiles from the betas isn't recommended and is known to cause problems

I appreciate the reasons for the change and I'm absolutely fine with them. However, there were icons and application settings in there which shouldn't have caused any problems with woofce, and I appear to have lost them all permanently. As I say, I have a backup so it's not a disaster. I was just wondering why the old pupsave was wiped during the upgrade.

[666philb]

Fresh "from scratch" frugal to hard drive of 8.0 using a core i5 and 4 gig
ram desktop. Installation of all my usual stuff was uneventful. It seems that
8.0 is noticeably faster than the 7.9.8 rc.

I noticed that 8.0 has the same old HTOP version 1.0.3 that xenialpup64
version 7.5 has. Ram useage reports are now much lower than they
are on bio 7.9.8 rc with its version 2.0.2 version HTOP. In fact, the
ram useage reports are comparable to xenialpup64. I wonder why
you chose the old and outdated version of HTOP for the 8.0 release?

Anyway, your bionicpup64 is by far the best pup for my purposes, and
I thank you again for it!

Art

believe it or not this wasn't deliberate & i've just spent the last 40mins trying to figure this out. Htop has always been a .pet in bionic and when building with woof it looks for the .pet in allocated repos. in bionicpup it looks in this order.
Packages-puppy-bionic-official
Packages-puppy-noarch-official
Packages-puppy-xenial64-official
Packages-puppy-tahr64-official
Packages-puppy-common64-official
i built htop 2.10 for bionicpup but never added to bionicpups repo as it didn't render properly in urxvt with its default settings.
so woof not finding htop in bionicpup repo should next look in noarch not find it there,and then xenial where it does find it.
in this build this is what it has done and grabbed xenials htop 1.0.3.

unusually in older builds, it skipped the htop in xenials repo and grabbed htop 2.0.2 from tahrpups repo. (no idea why this htop-2.0.2 never got used in tahr or xenial, was possibly added for tahr6.0.6 which never materialised)

anyway i'm currently re-uploading the iso & devx as i missed a printing bug fix, so i also added htop 2.0.2 as i think it shows a more realistic memory usage.

thanks for pointing this out.

[666philb]

At this point, I would normally open my old pupsave and copy across my favourite tweaks and quirks to the new one. Unfortunately, this time, the old one appears to have been wiped; all it contains is a broken symlink to /initrd/mnt/tmpfs/pup_rw

there's been a lot of changes in woofce during bionicpupos development and using old savefiles from the betas isn't recommended and is known to cause problems

I appreciate the reasons for the change and I'm absolutely fine with them. However, there were icons and application settings in there which shouldn't have caused any problems with woofce, and I appear to have lost them all permanently. As I say, I have a backup so it's not a disaster. I was just wondering why the old pupsave was wiped during the upgrade.

hi RedQuine,

i've just tested and seen what you mean. i've taken down the iso and will raise an issue on woofce

thankyou for reporting

[ITSMERSH]

before i raise an issue on woofce, does it affect any other applications or just pmount?

I don't know.

Is there any other applications that could be affected?

[bigpup]

The first Bionicpup64 8.0
Fresh Frugal, using save folder

Before or while you are rebuilding.

I need to use pmcpucurt64 for my temp readout on the tray.

I see you have a pet for it in the Bionicpup64 repository.

In PPM did a search for pmcpucurt64.
The results are it is already installed.

Did a search for it in Pfind.
It says it could not find it

Not sure what is going on here.

From a earlier post. Not sure if this is corrected yet.

CPU temperature monitor for 64-bit Pups
I see someone has uploaded pmcpucurt64.pet to the ibiblio.org site for bionicpup64 pet packages.
http://distro.ibiblio.org/puppylinux/pe ... -bionic64/
This pet package is missing the /root/.config/autostart/pmcpucurt.desktop

So, when the pet is installed. Nothing is put into the autostart directory to make the program load. Thus it is not running and no temp is displayed in the tray.

Here is the topic for pmcpucurt64
http://murga-linux.com/puppy/viewtopic.php?t=114502

Update:
I went to the pmcpucurt64 topic and downloaded and installed the pmcpucurt64.pet.
I also needed the sensors64x.pet.
Now have a working temp indicator in the tray.

[mavrothal]

No major complains
I was surprised at first with these automatic connections on startup but I realised is because of all these scripts in the Startup folder.

Here is the proprietary "wl" broadcom wifi driver and the Facetime broadcom 1570 PCIe webcam driver for the Bionicpup64 8.0 CE, if anyone needs them.

[rockedge]

when will the ISO and devx be avialable for download again?

[666philb]

I see you have a pet for it in the Bionicpup64 repository.

In PPM did a search for pmcpucurt64.
The results are it is already installed.

hi bigpup,
it definitely isn't installed and wasn't meant to be. as far as i can tell it was how the .pet was named in Packages-puppy-bionic64-official

i've renamed the .pet and re-uploaded and it now seems fixed (need to update PPM) BTW sensors is included in the package

BTWx2 careful as i've had to pull the iso until a savefile issue is fixed in woof.
https://github.com/puppylinux-woof-CE/w ... ssues/1335

[666philb]

No major complains
I was surprised at first with these automatic connections on startup but I realised is because of all these scripts in the Startup folder.

Here is the proprietary "wl" broadcom wifi driver and the Facetime broadcom 1570 PCIe webcam driver for the Bionicpup64 8.0 CE, if anyone needs them.

thanks mavrothal,

i'll add them before re-uploading

BTW careful as i've had to pull the iso until a savefile issue is fixed in woof
https://github.com/puppylinux-woof-CE/w ... ssues/1335

[666philb]

when will the ISO and devx be avialable for download again?

hi rockedge,

i'll re-upload as soon as the savefile issue gets fixed in woof.

https://github.com/puppylinux-woof-CE/w ... ssues/1335

[ITSMERSH]

i'll re-upload as soon as the savefile issue gets fixed in woof.

Why do they break stuff, that has worked very well for years?

In my tahr based ArtStudio everything still works fine. Even though I modified the dependent scripts to have also the free space of a drive in the tooltips of drive icons.

The new scripts still don't have such feature, so why to fix anything within these scripts that wasn't broken?

Hopefully it will not take years to fix that broken development.

[rockedge]

@666philb,

Thank you for the information. I am looking forward to the fix and using Bionicpup64 8.0 CE very much...... for advancing the Puppy Linux - ZoneMinder platform using object detection and recognition

[ITSMERSH]

Hi.

I have noticed there's a directory /usr/lib64 in zdrv_bionicpup64_8.0.sfs.

But there's a symbolic link /usr/lib64 in puppy_bionicpup64_8.0.sfs.

The files:

/usr/lib64/libau.so
/usr/lib64/libau.so.2
/usr/lib64/libau.so.2.10

in zdrv_bionicpup64_8.0.sfs will be invisible, no?

[ozsouth]

@RSH - you are right - this can happen in 64 bit when a slacko kernel is used in a ubuntu derivative or the kernel build recipe doesn't specify /usr/lib. Slacko64 uses /usr/lib64; Ubuntu 64 bit derivatives use /usr/lib with /usr/lib64 as a symlink to it. As zdrv .sfs is loaded AFTER puppy .sfs, the needed aufs files will be missing. That's why my kernels are specified as slacko or ubuntu derivative. Have checked version 7.9.7 - has same issue. It can be fixed by recreating the zdrv with the 3 mentioned files in /usr/lib with no /usr/lib64 folder. See:
http://murga-linux.com/puppy/viewtopic. ... 85#1019485

[666philb]

Hi.

I have noticed there's a directory /usr/lib64 in zdrv_bionicpup64_8.0.sfs.

But there's a symbolic link /usr/lib64 in puppy_bionicpup64_8.0.sfs.

The files:

/usr/lib64/libau.so
/usr/lib64/libau.so.2
/usr/lib64/libau.so.2.10

in zdrv_bionicpup64_8.0.sfs will be invisible, no?

thanks

now fixed

[mikeslr]

I've mentioned this before. To distinguish 64-bit libs from 32-bit libs Slackware instituted the use of lib64 folders. Debian/Ubuntu instituted the x86_64_linux-gnu folders: one under lib, one under /usr/lib and one under /usr/local/lib. For whatever reason, 64-bit Puppies can not find the x86_64_linux-gnu folders. The practice developed to place 64-bit libs in 'Ubuntu' Puppies in the three lib folders with symbolic links to them named x86_64_linux-gnu in each /usr/, /usr/local and /lib. In other words, Ubuntu 64-bit applications searching for libs in a x86_64 folder would follow the x86_64 links to the 32-bit lib folders.

For whatever reason 64-bit Puppies, including debian and ubuntu binary-compatible Puppies, can find and use /ib64 folders. Under 64-bit 'Ubuntus' they have to be moved somewhere. It would make more sense to always move 64-bit libraries into /lib64 folders, creating consistency across all puppies.

I don't know enough about coding to do it. But it should be possible to automate such movement:

If X is found in x86_64_linux-gnu
then cp X to /lib64
rm X from x86_64_linux-gnu
if x86_64_linux-gnu folder is empty rm x86_64_linux-gnu_

[blgs]

The new bionicpup64 will be supplied with uefi support?