StretchDog

[rcrsn51]

Just out of curiosity, what happens if you have two squash modules that both have init scripts.

Will they fight with each other?

[fredx181]

Just out of curiosity, what happens if you have two squash modules that both have init scripts.

Will they fight with each other?

Probably it can be that the initscript configuration from .squashfs module higher in alphanumerical order will overwrite and possibly disable initscript from the lower one.
But I don't really know from tests, if I use extra modules, I mostly load "on the fly"

@don570
New pfind is nice! Added to repos and also your mtpaint-64bit, so can be installed with Synaptic or apt-get, thanks again!

@all
Added deadbeef (music player) to the repos, install:

Code: Select all

apt-get update
apt-get install deadbeef-static

Made list for TODO's:
Changes and Fixes list

Fred

[trister]

Just out of curiosity, what happens if you have two squash modules that both have init scripts.

Will they fight with each other?

I hope I understand your question. I've been working entirely with squashfs (custom or/and apt2sfs) so I have some experience in squashfs loading. (the PC I'm typing loads during startup 94 squashfs files -programs & settings).

From my experience all the squashfs load & "overlap" in alphabetical order and they create your filesystem. When all are loaded the latest init files are executed.

When I want to be sure that the script of my squashfs file will certantly run , I rename my squashfs like this : z_slim_manager_replace_init_script.squashfs

If you have the files:
01filesystem.squashfs
a.squashfs
b.squashfs
c.squashfs

that they all contain a different version of file etc/profile

At the end StretchDog and all other puppies will see and execute the one that is in c.squashfs . So , without fighting the last squashfs wins

Especially for /etc/profile when I want something to be certain to run I do this :
eg
a.squashfs contains /etc/profile.d/a.sh
b.squashfs contains /etc/profile.d/b.sh
c.squashfs contains /etc/profile.d/c.sh
You can add the same way files inside folder /root/Startup or /home/puppy/Startup


Another important note : If you make squashfs BE VERY carefull with the owner rights of your folders. What I mean is that if you make a squashfs which contain the folder structure /home/puppy/Startup and you set in this Squashfs (that is loaded last in order) the owner of the folders as root then you will have all the path /home/puppy owned by root!!!.



Another note. Unlike .deb files in squashfs there are no scripts that are run during the *specific* squashfs loading.
At start all the squashfs are merged/fused together (in the order I said above) and THEN linux start (loads init , profiles ,rc etc). That means that you be very careful to where you put your init scripts.

[rcrsn51]

Thanks. Have you made any conclusion about why PeasyWifi did not auto-start? Does Fred have the correct explanation?

[trister]

Thanks. Have you made any conclusion about why PeasyWifi did not auto-start? Does Fred have the correct explanation?

I haven't checked this in the 17-10-10 Stretch but this is probable the case*(It's been a while since I boot the new SD).
I copied several of my older StretchDog64 files to the new StretchDog and I see one of them loaded frisbee.

[don570]

I found a way to make mtpaint open jp2 and j2k file format.
In my previous configure I was using 'nojp2' option in configure command.
http://murga-linux.com/puppy/viewtopic. ... 483#971483

Here is the new method I used...

I use fatdog linux 710 and upgrade it with giflib_5.1.2.orig.tar.bz2
(as previously mentioned) and also

openjpeg-2.1.1.tar.gz

This installed libopenjp2-7 package in fatdog linux.

Next I compiled mtpaint without 'nojp2' option.

Something like

Code: Select all

./configure intl  GIF tiff jpeg  --prefix=/usr

and it found the libopenjp2-7 package .

I then took the binary file and tested on stretch dog linux and then put
together debian package of mtpaint. It will now open more file types jp2 and j2k for example.

Available :
Size 487k
mtpaint_3.49.12_amd64.deb
https://drive.google.com/open?id=0B7JZA ... nlfLVRpLTQ

_______________________________________

[don570]

Some sample jp2 files to test
http://www.gwg.nga.mil/ntb/baseline/sof ... jpeg2k.htm
___________________________

[wjaguar]

openjpeg-2.1.1.tar.gz

BTW: anyone who intends to work with JPEG2000 for real, is advised to switch to the recent OpenJPEG 2.3.0. It is easily 2x the performance of previous versions, and of the JasPer library which was just as slow.
The library should be compiled with the "-DCMAKE_BUILD_TYPE=Release" option, to enable full optimizations (25% faster than without it).

[fredx181]

Available :
Size 487k
mtpaint_3.49.12_amd64.deb
https://drive.google.com/open?id=0B7JZA ... nlfLVRpLTQ

OK, thanks again, replaced in 64bit repo with your new package, btw, edited 'control' file by adding required dependencies on "Depends:" line.

Fred

[don570]

I wanted to be compatible to openjpeg2-7 package that Debian offers

https://packages.debian.org/stable/libs/libopenjp2-7

Now that I read this page it lists openjpeg2_2.1.2.orig.tar.gz as its source package.
I used older source but it works fine. It's the package that is used by stretch dog that is the important one
since that is the one the final user uses to open a file

___________________________________________

[fredx181]

Hi Don, FYI, I added now libopenjp2-7 to Depends: line in 'control' (previously didn't)
https://fredx181.github.io/StretchDog/a ... _amd64.deb

Fred

[backi]

By the way .....
Maybe Off-Topic .........but who really cares .

...........does anybody know where mcewanw is hiding ?

"The King is gone......but he`s not forgotten "
https://www.youtube.com/watch?v=t4Y1wDdMYH4

[fredx181]

Included youtube-get2 in StretchDog needed some fixes, see: Changes and Fixes list (4)

And added to custom repositories: emelfm2 file manager for X/gtk (taken from Ubuntu Trusty PPA, works fine in Stretch from what I tested), to install:

Code: Select all

apt-get update
apt-get install emelfm2

Or install from Synaptic

Fred

[belham2]

Included youtube-get2 in StretchDog needed some fixes, see: Changes and Fixes list (4)

And added to custom repositories: emelfm2 file manager for X/gtk (taken from Ubuntu Trusty PPA, works fine in Stretch from what I tested), to install:

Code: Select all

apt-get update
apt-get install emelfm2

Or install from Synaptic

Fred

Thank you, Fred! The darn thing is kinda nice as a backup filemanager, one I can leave in dual-pane mode set to handle only copying between the two designated partitions I am always usually fooling with. Just hope it doesn't start acting up (copying large files) like SpaceFM did. Thanks again for emelfm2!!

[don570]

StretchDog needed some fixes, see: Changes and Fixes list (4)

...says that you're making default apps..

I noticed in the Stretch dog iso that I downloaded that there was a 'defaultmediaplayer' but it was a bad link ???

Shouldn't it be linked to executable?
_______________________________________________

[fredx181]

StretchDog needed some fixes, see: Changes and Fixes list (4)

...says that you're making default apps..

I noticed in the Stretch dog iso that I downloaded that there was a 'defaultmediaplayer' but it was a bad link ???

Shouldn't it be linked to executable?
_______________________________________________

Yes, in next ISO release these default application symlinks should be fixed, indeed some are broken symlinks.
(completely forgot to pay attention to it when I made StretchDog 2017-10-10 ISO)

Fred

[don570]

Here's an observation...

When I installed stretchdog from the ISO
I read the Readme file inside and
I dragged live folder to a hard drive partition
and made simple menu.lst addition

Code: Select all

title stretch (sda1) 
root (hd0,0)
kernel (hd0,0)/live/vmlinuz1 noauto from=/ changes=EXIT:/live/
initrd (hd0,0)/live/initrd1.xz

and it worked.

However I tried dragging the live folder to another folder porteus
and changed menu.lst...

Code: Select all

title stretch (sda1) 
root (hd0,0)
kernel (hd0,0)/porteus/live/vmlinuz1 noauto from=/ changes=EXIT:/porteus/live/
initrd (hd0,0)/porteus/live/initrd1.xz

and I got got the warning that a search for stretch-x86_64.sgn file would take place and it wouldn't boot.

_____________________________________________

[fredx181]

Here's an observation...

When I installed stretchdog from the ISO
I read the Readme file inside and
I dragged live folder to a hard drive partition
and made simple menu.lst addition

Code: Select all

title stretch (sda1) 
root (hd0,0)
kernel (hd0,0)/live/vmlinuz1 noauto from=/ changes=EXIT:/live/
initrd (hd0,0)/live/initrd1.xz

and it worked.

However I tried dragging the live folder to another folder porteus
and changed menu.lst...

Code: Select all

title stretch (sda1) 
root (hd0,0)
kernel (hd0,0)/porteus/live/vmlinuz1 noauto from=/ changes=EXIT:/porteus/live/
initrd (hd0,0)/porteus/live/initrd1.xz

and I got got the warning that a search for stretch-x86_64.sgn file would take place and it wouldn't boot.

_____________________________________________

Then you need to change from=/... (from=/... should be considered parent folder of "live")

So this should work then according to your setup:

Code: Select all

title stretch (sda1) 
root (hd0,0)
kernel /porteus/live/vmlinuz1 noauto from=/porteus changes=EXIT:/porteus/live/
initrd /porteus/live/initrd1.xz

Btw, name of "parent folder" can be be anything, e.g. if "live" is inside "stretch_dog":

Code: Select all

title stretch from stretch_dog (sda1) 
root (hd0,0)
kernel /stretch_dog/live/vmlinuz1 noauto from=/stretch_dog changes=EXIT:/stretch_dog/live/
initrd /stretch_dog/live/initrd1.xz

Fred

[don570]

Useful info!

The Readme file in the ISO should have this example.

_____________________________________________

Code: Select all

kernel (hd0,0)/live/vmlinuz1

was causing problems with the booting process, but it would eventually boot

_____________________________________

[fredx181]

kernel (hd0,0)/live/vmlinuz1

was causing problems with the booting process, but it would eventually boot Rolling Eyes

Not sure, but I think you mean: "I didn't specify from=/ and still it boots"

The default folder to search for is "live", so if it's on the root of a partition, the from= is in fact not needed, so with above kernel line it boots without save and auto-mounting all partitions.

P.S. I will edit example boot codes file on next ISO release, thanks.
There's also Wiki page BTW.

Fred