Using AppImages in Puppy...
Mike Walsh, "to disentangle the KDEnlive stuff from the Openshot stuff, hopefully resulting in a 'standalone' SFS of current, 2-series Openshot that anyone can just load, and it'll run.....I don't think that someone is going to be me, somehow... (*shakes head*) Mikeslr, d'you fancy attacking this one with P.A.D.S and a copious supply of coffee...? "
Not me. O.F.I.N.S.I.S's build has, apparently, overcome the primary reason for NOT simultaneously having both Openshot and KDEnlive one's system: the previous incompatibility of the python modules they employed.
Here's the thing which I've yet to completely get my head around. The computing environment has changed and somewhere along the line of Puppy's evolution something may also have changed; or maybe I always misunderstood. A couple years ago I ran some experiments comparing the amount of available RAM with applications installed as pets, loaded as SFSes or merely linked as portables. At that time having only 512 Mbs of RAM or less was common. The thinking was SFSes were superior to pets because by unloading an SFS it would obviously use No RAM; while a pet, occupying space in a SaveFile would always need some RAM. That concept held true. However, what the exploration revealed was that even the then RAM hog LIbreOffice, however deployed, only required what in today's computing environment is an insignificant amount of RAM WHEN THE APPLICATION WAS NOT IN USE. By way of illustration LibreOffice at that time required 768 Mbs of Space on Storage and/or in a SaveFile: if installed but not opened it only required about 11 Mbs of RAM more than the same Puppy booted to desktop without LibreOffice installed. What's 11 Mbs of RAM when you now have 2 Gb or more? Especially under Bionicpup64 which, itself, requires at least 1 Gb for satisfactory performance.
My recent exploration of nic007's technique of substituting an adrv for a SaveFile reveals similar results. An adrv created from a SaveFile which exceeded 1 Gb had hardly any impact on the available RAM at bootup.
I used to think this phenomena had to do with the creation of inodes which pointed to files on Storage rather than copying them into RAM. But, explorations with using an adrv and removing the USB-Key from which Puppy was booted confirmed william2's proposition that 'everything' was copied into RAM on bootup. So I guess it has to do with caching and buffering --which I don't understand.
At any rate, its hardly likely that removing those files in O.F.I.N.S.I.S' 284 Mb SFS which are only required by KDEnlive would make a significant difference in the amount of available RAM for doing anything.
Not me. O.F.I.N.S.I.S's build has, apparently, overcome the primary reason for NOT simultaneously having both Openshot and KDEnlive one's system: the previous incompatibility of the python modules they employed.
Here's the thing which I've yet to completely get my head around. The computing environment has changed and somewhere along the line of Puppy's evolution something may also have changed; or maybe I always misunderstood. A couple years ago I ran some experiments comparing the amount of available RAM with applications installed as pets, loaded as SFSes or merely linked as portables. At that time having only 512 Mbs of RAM or less was common. The thinking was SFSes were superior to pets because by unloading an SFS it would obviously use No RAM; while a pet, occupying space in a SaveFile would always need some RAM. That concept held true. However, what the exploration revealed was that even the then RAM hog LIbreOffice, however deployed, only required what in today's computing environment is an insignificant amount of RAM WHEN THE APPLICATION WAS NOT IN USE. By way of illustration LibreOffice at that time required 768 Mbs of Space on Storage and/or in a SaveFile: if installed but not opened it only required about 11 Mbs of RAM more than the same Puppy booted to desktop without LibreOffice installed. What's 11 Mbs of RAM when you now have 2 Gb or more? Especially under Bionicpup64 which, itself, requires at least 1 Gb for satisfactory performance.
My recent exploration of nic007's technique of substituting an adrv for a SaveFile reveals similar results. An adrv created from a SaveFile which exceeded 1 Gb had hardly any impact on the available RAM at bootup.
I used to think this phenomena had to do with the creation of inodes which pointed to files on Storage rather than copying them into RAM. But, explorations with using an adrv and removing the USB-Key from which Puppy was booted confirmed william2's proposition that 'everything' was copied into RAM on bootup. So I guess it has to do with caching and buffering --which I don't understand.
At any rate, its hardly likely that removing those files in O.F.I.N.S.I.S' 284 Mb SFS which are only required by KDEnlive would make a significant difference in the amount of available RAM for doing anything.
- Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
Hallo, Mike.
Well now; I'm no longer really in the traditional Puppy 'mould', any more. This new hardware has a fast (3.7 GHz) quad-core Pentium Gold 'CPU', with advanced modern instruction sets; currently 8 GB of 2400 MHz DDR4 RAM; I finally have a discrete Nvidia GPU with 2 GB of dedicated GDDR5 VRAM, running with the proprietary Nvidia drivers, some of which I've compiled myself, using Shinobar's Get-Nvidia 1.5.pet.....and over 4 TB of internal storage. (I ripped the Barracuda drive out of the 3 TB external Seagate USB 3.0 drive I had, and added it as a secondary internal drive. Despite this HP mini-tower being physically smaller than ye olde Compaq tower, it seems to have a darned sight more space inside it.....no doubt due to all the components being that much smaller, including the minute slim-line PSU HP have seen fit to saddle it with..!)
Consequently, I'm having even more fun with Puppy now than over the last 5 years.....and the size of packages bothers me even less than it did previously. To that end, and bearing in mind the sheer number of AppImages & portables I've got kicking around, I've taken on board your suggestion from earlier; rather than loading O.F.I.N.S.I.S's humungous SFS package into my existing, general-purpose Bionicpup64 and risking it breaking stuff, I've created a second save-folder, loaded it into that, and made use of all those AppImages to build myself a dedicated, multimedia Puppy around it.
And so, here IS
"MediaPup" 8.0..!
'Clean':-
.....and 'dirty':-
What'cha reckon, huh? Hell, I've got the storage & RAM, and the processing power to do things with it now, so.....why not.
Life's good (all things considered), and I'm having a lot of fun.
Mike.
Well now; I'm no longer really in the traditional Puppy 'mould', any more. This new hardware has a fast (3.7 GHz) quad-core Pentium Gold 'CPU', with advanced modern instruction sets; currently 8 GB of 2400 MHz DDR4 RAM; I finally have a discrete Nvidia GPU with 2 GB of dedicated GDDR5 VRAM, running with the proprietary Nvidia drivers, some of which I've compiled myself, using Shinobar's Get-Nvidia 1.5.pet.....and over 4 TB of internal storage. (I ripped the Barracuda drive out of the 3 TB external Seagate USB 3.0 drive I had, and added it as a secondary internal drive. Despite this HP mini-tower being physically smaller than ye olde Compaq tower, it seems to have a darned sight more space inside it.....no doubt due to all the components being that much smaller, including the minute slim-line PSU HP have seen fit to saddle it with..!)
Consequently, I'm having even more fun with Puppy now than over the last 5 years.....and the size of packages bothers me even less than it did previously. To that end, and bearing in mind the sheer number of AppImages & portables I've got kicking around, I've taken on board your suggestion from earlier; rather than loading O.F.I.N.S.I.S's humungous SFS package into my existing, general-purpose Bionicpup64 and risking it breaking stuff, I've created a second save-folder, loaded it into that, and made use of all those AppImages to build myself a dedicated, multimedia Puppy around it.
And so, here IS
"MediaPup" 8.0..!
'Clean':-
.....and 'dirty':-
What'cha reckon, huh? Hell, I've got the storage & RAM, and the processing power to do things with it now, so.....why not.
Life's good (all things considered), and I'm having a lot of fun.
Mike.
- Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
Wonderful news, boys & girls.
The utterly AWESOME LosslessCut video trimmer/editor is now available as an AppImage. And about time, too!
I've followed this thing from the very early days:-
http://www.murga-linux.com/puppy/viewto ... 112245#top
It's always been built using the 'Electron' framework; this necessarily means it's gonna be large, 'cos Electron is essentially a 'stripped-down' Chromium browser. 'Nuff said.
v1.10.0 was extremely basic, and hardly did much of anything at all. However, its developer, "mifi", released this most recent 'stable' build - v3.17.9 - just 3 days ago.....and it's now stuffed to bursting with tons of goodies, all powered by the amazing ffmpeg.
(In the last 24 hours, mifi has committed seven further 'point releases' to his project page over at Github! I think it's fair to say this lad has got the bit firmly between his teeth, and is full of ideas. All credit to him, I say, especially when he puts out such an amazing app as this one.)
This release runs OOTB under Bionicpup64, and is just one of the 'stars' of my newly put-together 'MediaPup 8.0' (see my post above). No, it's not a new Puppy, but it was inspired by a comment Mikeslr made during the last day or two about creating a separate save-folder for running the 2-series Openshot SFS package O.F.I.N.S.I.S has put together recently.....this is to do with multiple Python 'issues', nothing else.
I'd got a whole stash of multimedia-type AppImages & portable apps sitting around doing nothing, so I thought I'd put together a dedicated Puppy and put 'em to good use at long last.....
----------------------------------
This is available as either a 'straight' Electron package:-
https://github.com/mifi/lossless-cut/re ... ux.tar.bz2
.....or an AppImage:-
https://github.com/mifi/lossless-cut/re ... x.AppImage
As with everything these days, these are now 64-bit only. They run OOTB under Bionic; I'm going to try this release in Xenialpup64 tomorrow, but I'm not hopeful.....I think the older glibc will be the killer. We'll see.
In all cases, this needs to be started with the
....'flag'.
EDIT:- My fears were unfounded. This fires straight up under Xenialpup64, so.....nice one.
Mike.
The utterly AWESOME LosslessCut video trimmer/editor is now available as an AppImage. And about time, too!
I've followed this thing from the very early days:-
http://www.murga-linux.com/puppy/viewto ... 112245#top
It's always been built using the 'Electron' framework; this necessarily means it's gonna be large, 'cos Electron is essentially a 'stripped-down' Chromium browser. 'Nuff said.
v1.10.0 was extremely basic, and hardly did much of anything at all. However, its developer, "mifi", released this most recent 'stable' build - v3.17.9 - just 3 days ago.....and it's now stuffed to bursting with tons of goodies, all powered by the amazing ffmpeg.
(In the last 24 hours, mifi has committed seven further 'point releases' to his project page over at Github! I think it's fair to say this lad has got the bit firmly between his teeth, and is full of ideas. All credit to him, I say, especially when he puts out such an amazing app as this one.)
This release runs OOTB under Bionicpup64, and is just one of the 'stars' of my newly put-together 'MediaPup 8.0' (see my post above). No, it's not a new Puppy, but it was inspired by a comment Mikeslr made during the last day or two about creating a separate save-folder for running the 2-series Openshot SFS package O.F.I.N.S.I.S has put together recently.....this is to do with multiple Python 'issues', nothing else.
I'd got a whole stash of multimedia-type AppImages & portable apps sitting around doing nothing, so I thought I'd put together a dedicated Puppy and put 'em to good use at long last.....
----------------------------------
This is available as either a 'straight' Electron package:-
https://github.com/mifi/lossless-cut/re ... ux.tar.bz2
.....or an AppImage:-
https://github.com/mifi/lossless-cut/re ... x.AppImage
As with everything these days, these are now 64-bit only. They run OOTB under Bionic; I'm going to try this release in Xenialpup64 tomorrow, but I'm not hopeful.....I think the older glibc will be the killer. We'll see.
In all cases, this needs to be started with the
Code: Select all
--no-sandbox
EDIT:- My fears were unfounded. This fires straight up under Xenialpup64, so.....nice one.
Mike.
Last edited by Mike Walsh on Thu 02 Apr 2020, 09:42, edited 1 time in total.
Mike wrote:Well now; I'm no longer really in the traditional Puppy 'mould', any more. This new hardware has a fast (3.7 GHz) quad-core Pentium Gold 'CPU', with advanced modern instruction sets; currently 8 GB of 2400 MHz DDR4 RAM; I finally have a discrete Nvidia GPU with 2 GB of dedicated GDDR5 VRAM, running with the proprietary Nvidia drivers, some of which I've compiled myself, using Shinobar's Get-Nvidia 1.5.pet.....and over 4 TB of internal storage.
You #%¤@ traitor!
True freedom is a live Puppy on a multisession CD/DVD.
- Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
Hah! Hark who's talking....tallboy wrote:Mike wrote:Well now; I'm no longer really in the traditional Puppy 'mould', any more. This new hardware has a fast (3.7 GHz) quad-core Pentium Gold 'CPU', with advanced modern instruction sets; currently 8 GB of 2400 MHz DDR4 RAM; I finally have a discrete Nvidia GPU with 2 GB of dedicated GDDR5 VRAM, running with the proprietary Nvidia drivers, some of which I've compiled myself, using Shinobar's Get-Nvidia 1.5.pet.....and over 4 TB of internal storage.
You #%¤@ traitor!
Perhaps a 'traitor' where hardware's concerned, Olaf, but my God! Pup absolutely screams on this thing.....and after trying out I don't know HOW many other distros over the last few years, I always return home to the sanity of the kennels, and the support of an amazing community.
(I'm loyal, if nothing else mate.... )
Mike.
It was stricktly meant as a hardware joke, Mike. I don't think anyone can accuse you of not being a loyal 'Puppyteer', they dance to your moves!
I hope you are extra careful these days, disaster lurks at home, if you get infected. Wear gloves, use facemask, wear protection glasses, wash hands. This is bad!
I hope you are extra careful these days, disaster lurks at home, if you get infected. Wear gloves, use facemask, wear protection glasses, wash hands. This is bad!
True freedom is a live Puppy on a multisession CD/DVD.
- Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
Cryptomator 1.5.0 encryption 256 AES tool distributed as AppImage:
https://cryptomator.org/downloads/
Only 64 bit. Working in quirkyApril-light64 by jrb.
https://cryptomator.org/downloads/
Only 64 bit. Working in quirkyApril-light64 by jrb.
- Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
Evening, kiddiwinks.
Just a quick one for y'all tonight. Mikeslr has dug up a very neat little AppImage for checking codecs of films, audio tracks, anything media-related, really.....in both 32- & 64-bit versions. Fires straight up in most relatively modern Puppies, OOTB.
MediaInfo
You can find the link for it here:-
http://www.murga-linux.com/puppy/viewto ... 56#1058456
Thanks, Mike..!
T'other Mike.
Just a quick one for y'all tonight. Mikeslr has dug up a very neat little AppImage for checking codecs of films, audio tracks, anything media-related, really.....in both 32- & 64-bit versions. Fires straight up in most relatively modern Puppies, OOTB.
MediaInfo
You can find the link for it here:-
http://www.murga-linux.com/puppy/viewto ... 56#1058456
Thanks, Mike..!
T'other Mike.
Find today that Molotov : French tv player has an appimage
https://www.molotov.tv/download
To be more secure install firejail it's an easy way to use sandbox programs :
And run your molotov :
I have done this on :
Enjoy
https://www.molotov.tv/download
Code: Select all
Don't run as root so do in a console where your appimage is :
./molotov.AppImage --no-sandbox
Code: Select all
pkg a firejail
Code: Select all
firejail --noprofile ./molotov.AppImage --no-sandbox
Code: Select all
cat /etc/os-release
NAME=Puppy
VERSION="8.0"
ID=puppy_bionicpup64
VERSION_ID=8.0
PRETTY_NAME="bionicpup64 8.0"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:puppy:puppy_linux:8.0"
HOME_URL="http://puppylinux.com/"
SUPPORT_URL="http://www.murga-linux.com/puppy/index.php"
BUG_REPORT_URL="https://github.com/puppylinux-woof-CE/woof-CE"
JpLt
hi, I installed firejail from the ppm but it gives error when I try to lunch ut. screenshot;jplt3 wrote:Find today that Molotov : French tv player has an appimage
https://www.molotov.tv/download
To be more secure install firejail it's an easy way to use sandbox programs :Code: Select all
Don't run as root so do in a console where your appimage is : ./molotov.AppImage --no-sandbox
Code: Select all
pkg a firejail
http://i.imgur.com/tc7is0d.png
Xanialpup 7.5 32 bit
This should take care of the error in your image so long as you can interpret Rosika's workaround.
BTW, you don't really wanna run Slimjet. If however you insist, you wanna run "flashpeak-slimjet," NOT slimjet.
A whole bag-O-goodies await...
BTW, you don't really wanna run Slimjet. If however you insist, you wanna run "flashpeak-slimjet," NOT slimjet.
A whole bag-O-goodies await...
>>> Living with the immediacy of death helps you sort out your priorities. It helps you live a life less trivial <<<
Semme wrote:This should take care of the error in your image so long as you can interpret Rosika's workaround.
BTW, you don't really wanna run Slimjet. If however you insist, you wanna run "flashpeak-slimjet," NOT slimjet.
A whole bag-O-goodies await...
oke, now this needs explanation, why ? what is the difference ? are not they both the same? and only slimjet 15 run reasonably good on this machine
can you elaborate ?
Code: Select all
sh-4.3# firejail --noprofile slimjet
Parent pid 16909, child pid 16910
The new log directory is /proc/16910/root/var/log
Child process initialized
[2:31:0531/180909.299565:ERROR:service_manager.cc(158)] Connection InterfaceProviderSpec prevented service: content_plugin from binding interface: memory_instrumentation::mojom::Coordinator exposed by: content_browser
exit
Warning: removing 5 bytes from stdin
parent is shutting down, bye...
Code: Select all
sh-4.3# firejail -private=/slimjet
Error: invalid -private=/slimjet command line option
Xanialpup 7.5 32 bit