BionicPup32 (UPupBB) (27 June 2020)
My setup is simple...router..subnet 192.168.0.* and 6 machines 2 net cameras connected right now. the network app works on all my Xenial and Tahr machines but not Bionic. the app finds the shares but will not mount them with out the modification I've indicated.
pnethood works well on Bionic but fails in Xenial..... YASSM works on all but I do not use it much without the search feature.
Thanks for your time peebee....I am sure it is some small thing....
pnethood works well on Bionic but fails in Xenial..... YASSM works on all but I do not use it much without the search feature.
Thanks for your time peebee....I am sure it is some small thing....
- Attachments
-
- Screenshot4-800px.png
- (48.77 KiB) Downloaded 1806 times
pnethood in action... as one can see a DELL, Gateway, Dell Poweredge,Dell Optiplex and an eMachine...all pretty old units
But some of the servers are missing that the network app finds. On another machine the optiplex with Bionic 18.05 kernel4.17 pnethood works flawlessly
But some of the servers are missing that the network app finds. On another machine the optiplex with Bionic 18.05 kernel4.17 pnethood works flawlessly
- Attachments
-
- Screenshot7-800px.png
- (87.81 KiB) Downloaded 1802 times
UPup Bionic Beaver 64 bit with "xenial pup updater"
here is a thought! why not create a UPup Bionic Beaver 64 bit with the "xenial pup 7.5 updater" Quickpet !!!???
Is it possible?
it would be a dream come trough
kindly Gnimmlef
Is it possible?
it would be a dream come trough
kindly Gnimmlef
UPDATE 21-jul-2018
bc8ca18f3aacd26609b1bee0955b96f5 upupbb-18.05+9.iso
{delta}
BUILD_FROM_WOOF='master;ec80b41b;2018-06-23 11:36:40 +0800'
gtk+3 libraries "rearranged" =
new devx
= glade now runs
bc8ca18f3aacd26609b1bee0955b96f5 upupbb-18.05+9.iso
{delta}
BUILD_FROM_WOOF='master;ec80b41b;2018-06-23 11:36:40 +0800'
gtk+3 libraries "rearranged" =
new devx
= glade now runs
Last edited by peebee on Sat 21 Jul 2018, 08:21, edited 7 times in total.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
I'm not sure I'm afraid - where did you get "it_IT langpack" from?? Do you know how it was built? Have you tried to "look inside"? maybe it is possible to manually edit?picatrix wrote:I installed it_IT langpack, there's a couple of missing menu entries translations: Is there an easy way to fix them?
You might get more help from other forums - follow links from:
http://puppylinux.org/wikka/italiano?redirect=no ??
or ask on:
http://murga-linux.com/puppy/viewtopic.php?t=94195
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Hi peebee.
Would you mind terribly if I wrote a script to combine the adrv, fdrv and
ydrv of your Beaver/Bionic/Pup?
The idea would be to free one "position" or "letter" so the user can
transform his / her big pupsave into say, an adrv or whatever "letter" is
available. I notice that your ydrv doesn't have much in it, only don570's
right-click menu links, at 72 k, or something like that.
The concept of tranforming a big pupsave file into the adrv (e.g.) as an
alternative to a full remaster (it preserves the pup sfs as pristine) goes
back to either ASRI or Sailor Enceladus. (As you may perhaps know
already.)
Thanks in advance for any response or insight.
BFN.
Would you mind terribly if I wrote a script to combine the adrv, fdrv and
ydrv of your Beaver/Bionic/Pup?
The idea would be to free one "position" or "letter" so the user can
transform his / her big pupsave into say, an adrv or whatever "letter" is
available. I notice that your ydrv doesn't have much in it, only don570's
right-click menu links, at 72 k, or something like that.
The concept of tranforming a big pupsave file into the adrv (e.g.) as an
alternative to a full remaster (it preserves the pup sfs as pristine) goes
back to either ASRI or Sailor Enceladus. (As you may perhaps know
already.)
Thanks in advance for any response or insight.
BFN.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
No problem whatsoever....musher0 wrote:Would you mind terribly if I wrote a script to combine the adrv, fdrv and ydrv of your Beaver/Bionic/Pup?
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Hello picatrix.picatrix wrote:First of all thanks for your great work Peebee!
I installed it_IT langpack, there's a couple of missing menu entries translations: "Run" and "Leave", so the Puppy Log Out window and the upper menu bar tooltips.
Is there an easy way to fix them?
Thanks in advance
In addition to peebee's information above, perhaps you have heard of
these sites / forum threads related to localization:
https://translations.launchpad.net/ubun ... anslations
-- general page
https://launchpad.net/~ubuntu-l10n-it
-- Ubuntu's team of Italian translators
https://www.transifex.com
-- where teams of volunteer translators focus on translating one app.
https://unix.stackexchange.com/question ... nux-ubuntu
-- As the name of this thread implies. Explains how to bring up the man
pages in your language
https://www.kernel.org/doc/man-pages/translations.html
-- general information page
Of course, not all apps have an Italian localization (or French, Polish,
German, Portuguese, etc.). OpenOffice and LibreOffice are notable
exceptions.
You may have to continue to dig with a good search engine.
Replying to your exact question: you may have to update this Italian
translation yourself using a ".po" or "gettest" utility (if you find no ready-
made IT translations).
IHTH. Good luck!
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Hello peebee and all.
(I hope this post goes here.)
Please find attached the script announced above. With thanks to peebee
for his permission.
Users, please read the comments inside the script carefully before
running it, including the Notes at bottom.
Once the script has combined all the ?drv*.sfs archives in fdrv*.sfs, the
only thing left for the user to do will be, after rebooting BionicPup, to edit
file defaultbrowser at /usr/local/bin like so:This edit will call the U_Light browser directly, instead of showing a
warning that the adrv*.sfs is not there (anymore).
Aside from that, don570's right-click menus work fine, as does everything
else, AFAICT. I think I gave this script a good go, but please report any
oddities. TIA.
A final note -- (edited for grammar, 21-06-2018)
Only BionicPup users who wish (was "which", sorry) to free the
"adrv*.sfs" position or archive to convert a BIG pupsave to an adrv -- as
an alternative to traditional remastering -- should use this script.
Because this BionicPup is a little wonder as it is! Bravo, peebee!
(I'm wrting this post from it now.)
TWYL.
~~~~~~~~~~~~~~~
(I hope this post goes here.)
Please find attached the script announced above. With thanks to peebee
for his permission.
Users, please read the comments inside the script carefully before
running it, including the Notes at bottom.
Once the script has combined all the ?drv*.sfs archives in fdrv*.sfs, the
only thing left for the user to do will be, after rebooting BionicPup, to edit
file defaultbrowser at /usr/local/bin like so:
Code: Select all
#!/bin/sh
exec /usr/local/lib/light/light "$@"
# light "$@"
warning that the adrv*.sfs is not there (anymore).
Aside from that, don570's right-click menus work fine, as does everything
else, AFAICT. I think I gave this script a good go, but please report any
oddities. TIA.
A final note -- (edited for grammar, 21-06-2018)
Only BionicPup users who wish (was "which", sorry) to free the
"adrv*.sfs" position or archive to convert a BIG pupsave to an adrv -- as
an alternative to traditional remastering -- should use this script.
Because this BionicPup is a little wonder as it is! Bravo, peebee!
(I'm wrting this post from it now.)
TWYL.
~~~~~~~~~~~~~~~
Code: Select all
#!/bin/bash
# combine-drvs.sh
#
# Save this script under / Enregistrer ce script sous
# /opt/local/bin OR/OU /root/my-applications/bin
# and make executable. / et rendre exécutable.
###
# Goal : reduce the number of ?drv*.sfs archives to one
# in a Puppy that has a full complement of them. /
#
# Objectif : réduire le nombre d'archives ?drv*.sfs à une
# dans un Puppy | Toutou qui les a toutes.
###
# Usage -- Important : utiliser ce script d'un autre Puppy | Toutou que BionicPup.
# ........ Ouvrir une console dans le répertoire de BionicPup et lancer ce script.
# ........ Quand le script est terminé, redémarrer BionicPup. /
#
# Usage -- Important : run this script from another Pup than the BionicPup. <=-
# ........ Open a console in BionicPup's directory and run this script.
# ........ When done, restart BionicPup.
###
# -=> Please read the notes at bottom. / Veuillez lire les notes au bas de ce script. <=-
####
# © Christian L'Écuyer (alias musher0), Gatineau (Qc), Canada, 2018-06-16. GPL3.
# GPL3 licence in English: https://opensource.org/licenses/GPL-3.0
##########
# Ce programme est libre : vous pouvez le redistribuer ou modifier selon les termes de la
# Licence Publique Générale GNU publiée par la Free Software Foundation (v. 3 ou toute
# version ultérieure choisie par vous).
# Ce programme est distribué dans l'espoir qu'il sera utile, mais SANS AUCUNE
# GARANTIE, ni explicite ni implicite, y compris des garanties de commercialisation ou
# d'adaptation à un but spécifique. Pour plus de détails, veuillez vous reporter au
# texte de cette licence à https://opensource.org/licenses/GPL-3.0 pour le texte officiel, à
# http://www.linux-france.org/article/these/gpl.html pour une traduction et à
# https://fr.wikipedia.org/wiki/Licence_publique_générale_GNU pour une explication en français.
################
####
for archive in `ls -1 ?drv* | grep -v zdrv`;do
unsquashfs -d "${archive:0:4}" "$archive"
wait
mv -f $archive $archive.bckp
wait
done
cd fdrv
for combine in adrv ydrv;do
rsync -avzm ../$combine/* .
wait
done
cd ..
mksquashfs fdrv fdrv_upupbb_18.05.sfs -noappend -all-root -b 1048576 -comp xz -Xdict-size 100%
wait
for ReP in adrv fdrv ydrv;do
rm -rdf $ReP/*
rmdir --ignore-fail-on-non-empty $ReP
done
exit
### Notes ###
EN -- Back-ups of the ?srv*.sfs archives are made: do not erase them.
This script has been tested. But should something go wrong, in console, type
mv -f ?drv_upupbb_18.05.sfs.bckp ?drv_upupbb_18.05.sfs
(Replace the ? with the letters a, f and y.)
FR -- Des sauvegardes des archives ?srv*.sfs sont faites : ne les effacez pas.
Ce script a été testé. Si quelque chose n'allait pas, en console, taper
mv -f ?drv_upupbb_18.05.sfs.bckp ?drv_upupbb_18.05.sfs
(Remplacer le ? par les lettres a, f et y.)
##################
- Attachments
-
- Screenshot.jpg
- Backdrop credit: Cassie Boca, photo 293379 at unsplash.com
- (104.22 KiB) Downloaded 874 times
-
- combine-drvs.sh.zip
- The script above in a zip archive.
- (1.62 KiB) Downloaded 121 times
Last edited by musher0 on Thu 21 Jun 2018, 05:58, edited 1 time in total.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
- Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
Hi, all.
Now then; would appreciate a wee bit of advice.
Currently running 18.05+1. I've swapped over the contents for those of 18.05+5, but could someone please explain to a dunderhead what it is I actually do with the 'delta'.....and how do I use it? And will it do whatever it is that it does with my 'old' save-file from 18.05+1 loaded.....or does this need to be done with 18.05+5 in 'pristine' condition?
My own fault, I confess; I simply haven't got involved enough in the 'testing' side of things to have become aware of this stuff. I've preferred to concentrate on the Pups I have installed which I really like, and to 'develop' those to the extent which I prefer.
TIA.
Mike.
Now then; would appreciate a wee bit of advice.
Currently running 18.05+1. I've swapped over the contents for those of 18.05+5, but could someone please explain to a dunderhead what it is I actually do with the 'delta'.....and how do I use it? And will it do whatever it is that it does with my 'old' save-file from 18.05+1 loaded.....or does this need to be done with 18.05+5 in 'pristine' condition?
My own fault, I confess; I simply haven't got involved enough in the 'testing' side of things to have become aware of this stuff. I've preferred to concentrate on the Pups I have installed which I really like, and to 'develop' those to the extent which I prefer.
TIA.
Mike.
Hi Mike, hope this helps.
The delta is applied to the original iso generating a new iso image. When delta 1 is applied to upupbb-18.05.iso will generate upupbb-18.05+1.iso. The contents of the deltas for upup bionic are accumulative, so delta-5 applied to upupbb-18.05.iso, generates upupbb18.05+5.iso. Put the delta in the same folder as the iso and click it and it'll do its stuff.
The delta is applied to the original iso generating a new iso image. When delta 1 is applied to upupbb-18.05.iso will generate upupbb-18.05+1.iso. The contents of the deltas for upup bionic are accumulative, so delta-5 applied to upupbb-18.05.iso, generates upupbb18.05+5.iso. Put the delta in the same folder as the iso and click it and it'll do its stuff.
Delta to make updated iso
G'day Mike W.,
In the Utility menu is the gui X-delta difference manager.
Drag the specified original iso to its location (see screenshot).
Drag the delta file to its location.
Click the button to generate the new iso.
The new iso will probably be where the old original is.
Note, you can only use the specified original iso, as per the delta file name, not necessarily the last iso you have. I speak from considerable experience (of doing the wrong thing ).
David S.
In the Utility menu is the gui X-delta difference manager.
Drag the specified original iso to its location (see screenshot).
Drag the delta file to its location.
Click the button to generate the new iso.
The new iso will probably be where the old original is.
Note, you can only use the specified original iso, as per the delta file name, not necessarily the last iso you have. I speak from considerable experience (of doing the wrong thing ).
David S.
- Attachments
-
- Screenshot.png
- (19.44 KiB) Downloaded 751 times
- Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
Hi, Terry.
Ah. So, having downloaded (and am about to use) the 18.05+5 .iso, then I don't actually need to use the delta at this point in time?
Or I could apply the 'delta' to the existing 18.05+1 that I've been using, and it would then 'generate' a new. 18.05+5 .iso?
('Salright; I ought to get a handle on this stuff at some point.....even though I'm not one of those folks who regularly switch to the very newest versions the instant they come out. I like to let distros 'prove' themselves, and 'get the bugs outta the system' and settle down.....typically not bothering with new versions for around a year.)
Mike.
Ah. So, having downloaded (and am about to use) the 18.05+5 .iso, then I don't actually need to use the delta at this point in time?
Or I could apply the 'delta' to the existing 18.05+1 that I've been using, and it would then 'generate' a new. 18.05+5 .iso?
('Salright; I ought to get a handle on this stuff at some point.....even though I'm not one of those folks who regularly switch to the very newest versions the instant they come out. I like to let distros 'prove' themselves, and 'get the bugs outta the system' and settle down.....typically not bothering with new versions for around a year.)
Mike.
- Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
Hiya, David.
Mm. O-kayyy....
So; to test my knowledge here, as things stand, I've downloaded the newest iteration (18.05+5), and the 'new' devx (bandwidth hasn't been a problem for me for around 2 1/2 years now, ever since we went 'unlimited' back in Jan 2016).
If I've got this right then, I can just go right ahead and use these with my existing save-file, yes? (Please correct me if I'm wrong; I'd rather get this right from the beginning, instead of messing about and having to re-do things again & again..!)
Haven't quite got the patience I used to have.....to say nothing of having considerably less spare time. And I didn't get hold of the original 18.05 anyway; by the time I decided to try this, peebee had already changed the link in the first post to that of 18.05+1....
Mike.
Mm. O-kayyy....
So; to test my knowledge here, as things stand, I've downloaded the newest iteration (18.05+5), and the 'new' devx (bandwidth hasn't been a problem for me for around 2 1/2 years now, ever since we went 'unlimited' back in Jan 2016).
If I've got this right then, I can just go right ahead and use these with my existing save-file, yes? (Please correct me if I'm wrong; I'd rather get this right from the beginning, instead of messing about and having to re-do things again & again..!)
Haven't quite got the patience I used to have.....to say nothing of having considerably less spare time. And I didn't get hold of the original 18.05 anyway; by the time I decided to try this, peebee had already changed the link in the first post to that of 18.05+1....
Mike.
Yes, and occasionally No. Deltas upgrade the operating system. If a puppy creator has published a system change (as by way of a pet or recommended edit of a system file) and you've applied it, that change is part of your SaveFile/Folder. It would unnecessarily duplicate the change provided by the delta, or perhaps conflict with it. As far as I recall, peebee hasn't done that for upupbb or other Puppies. But other Devs might.Mike Walsh wrote: If I've got this right then, I can just go right ahead and use these with my existing save-file, yes?
Similarly, you, yourself, may have effected an operating system change.
So if all that your SaveFile/Folder only holds are 'normal-user-work' applications and their configurations nothing needs to be done. But system changes made before upgrading via a delta --just like those before replacing a prior ISO's content with a newer version-- should probably be removed from a SaveFile/Folder.
mikesLr
Here's the link to where you can download upupbb-18.05.iso. The deltas are in the updates folder and the devx is in the appropriately named folder. I don't know how good your internet service is but I find it well worth while to download 20MB as opposed to 270MB.Mike Walsh wrote: I didn't get hold of the original 18.05 anyway; by the time I decided to try this, peebee had already changed the link in the first post to that of 18.05+1....
Cheers, J