Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Sat 18 Nov 2017, 23:09
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
StretchDog
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 3 of 5 [73 Posts]   Goto page: Previous 1, 2, 3, 4, 5 Next
Author Message
don570


Joined: 10 Mar 2010
Posts: 4755
Location: Ontario

PostPosted: Tue 17 Oct 2017, 15:51    Post subject:  

Quote:
it needs Porteus that it has to be in the /puppy_StretchDog64/live/Porteus <--- not sure what it meant actually. Anything else i need to do?


In this situation two folders were created --> /puppy_StretchDog64/live/

Then you drag the contents of the Porteus folder
into the 'live' folder

_________________________________________
Back to top
View user's profile Send private message 
don570


Joined: 10 Mar 2010
Posts: 4755
Location: Ontario

PostPosted: Tue 17 Oct 2017, 15:58    Post subject:  

BarryK likes uses default applications.

Here is a list that aren't in Stretch Dog..

/usr/local/bin/defaultaudioplayer
/usr/local/bin/defaultpaint
/usr/local/bin/defaultspreadsheet
/usr/local/bin/defaultterm
/usr/local/bin/defaulttexteditor
/usr/local/bin/defaultwordprocessor
/usr/local/bin/defaultmail
/usr/local/bin/defaultdraw
/usr/local/bin/defaulthtmleditor
/usr/local/bin/defaultimageviewer
_______________________________________
Back to top
View user's profile Send private message 
trister

Joined: 01 Mar 2015
Posts: 78

PostPosted: Tue 17 Oct 2017, 16:39    Post subject:  

ethplorer wrote:
trister wrote:
Very good job Fred Smile

@ethplorer:

my menu.lst entry is like this :

Code:
title PorteusStretchDog EXIT: changes32
find --set-root --ignore-floppies /puppy_StretchDog64/live/initrd1.xz
kernel /puppy_StretchDog64/live/vmlinuz1 from=/puppy_StretchDog64 changes=EXIT:/puppy_StretchDog64/changes32.dat
initrd /puppy_StretchDog64/live/initrd1.xz

...


while it does work as it starts to read the vmlinuz and initrd, it suddenly stops telling that it needs Porteus that it has to be in the /puppy_StretchDog64/live/Porteus <--- not sure what it meant actually. Anything else i need to do?


StretchDog is by default reading initrd1.xz and vmlinuz1 from inside a /live folder.
If you put everything inside that /puppy_StretchDog64 folder/live folder (I've put live inside the puppy_StretchDog64 folder) then it should work.
Note the names are "initrd1.xz " (and not initrd.img which is used for another boot method-not porteus)

The parameter from=/puppy_StretchDog64 tells linux that my live folder is inside /puppy_StretchDog64 folder

The parameter changes=EXIT:/puppy_StretchDog64/changes32.dat tells linux that my save file name is changes32.dat and where it is located

The entry
find --set-root --ignore-floppies /puppy_StretchDog64/live/initrd1.xz
is my favorite Smile it searches my puppy_StretchDog64 folder. This means I can move this folder in any drive and I don't have to change anything
Back to top
View user's profile Send private message 
rufwoof

Joined: 24 Feb 2014
Posts: 2161

PostPosted: Tue 17 Oct 2017, 17:58    Post subject:  

prehistoric wrote:
Just want to mention that there is a patch for Debian Stretch for the WPA2 Krack attack. This puts it ahead of many other distros.

https://marc.info/?l=openbsd-misc&m=150815942414653&w=2
Quote:
Why did OpenBSD silently release a patch before the embargo?

OpenBSD was notified of the vulnerability on 15 July 2017, before
CERT/CC was involved in the coordination. Quite quickly, Theo de Raadt
replied and critiqued the tentative disclosure deadline: In the open
source world, if a person writes a diff and has to sit on it for a
month, that is very discouraging. Note that I wrote and included a
suggested diff for OpenBSD already, and that at the time the tentative
disclosure deadline was around the end of August. As a compromise, I
allowed them to silently patch the vulnerability. In hindsight this was
a bad decision, since others might rediscover the vulnerability by
inspecting their silent patch. To avoid this problem in the future,
OpenBSD will now receive vulnerability notifications closer to the end
of an embargo.
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 11720
Location: Stratford, Ontario

PostPosted: Wed 18 Oct 2017, 09:42    Post subject:  

rcrsn51 wrote:
trister wrote:
The first thing I noticed at start is that I need to run "reconnect" from peasyWifi to get an IP from my router the first time I enter the system.

This sounds like a timing issue.

Look at the script /etc/rc.d/rc.nework. PWF makes two tries (line 19) with a 5 second pause between (line 23). Each try is controlled by the -t and -T options (line 21).

Maybe increasing some of these will help.

If you watch the boot messages, there should be a line near the end for "udhcpc". Do you see it?


No reply? If there is a timing issue here, the only person who can help fix it is the one who is experiencing it.
Back to top
View user's profile Send private message 
trister

Joined: 01 Mar 2015
Posts: 78

PostPosted: Thu 19 Oct 2017, 15:27    Post subject:  

rcrsn51 wrote:
rcrsn51 wrote:
trister wrote:
The first thing I noticed at start is that I need to run "reconnect" from peasyWifi to get an IP from my router the first time I enter the system.

This sounds like a timing issue.

Look at the script /etc/rc.d/rc.nework. PWF makes two tries (line 19) with a 5 second pause between (line 23). Each try is controlled by the -t and -T options (line 21).

Maybe increasing some of these will help.

If you watch the boot messages, there should be a line near the end for "udhcpc". Do you see it?


No reply? If there is a timing issue here, the only person who can help fix it is the one who is experiencing it.


Sorry, I've been using the older StretchDog and didn't have much time troubleshooting the issues I have at the 2017-10-10StretchDog64 .

Btw, if anyone interested in trying Docker : docker-ce_17.09.0~ce-0~debian_amd64.squashfs : https://1fichier.com/?90slf7h5sk
Back to top
View user's profile Send private message 
don570


Joined: 10 Mar 2010
Posts: 4755
Location: Ontario

PostPosted: Thu 19 Oct 2017, 18:48    Post subject: mtpaint 3.49.12 for stretch dog  

mtpaint 3.49.12 for stretch dog (64bit) available

see next page

Note:
This package was compiled on Fatdog linux 710 .
What I did was to upgrade Fatdog linux 710 to libgif.so.7 by downloading and compiling
giflib_5.1.2.orig.tar.bz2

The libraries were then correct except for libopenjpeg so I compiled with configuration
'nojp2'

The result is that the executable will open and save to the common image formats except for jp2

____________________________________

Last edited by don570 on Sat 21 Oct 2017, 12:00; edited 2 times in total
Back to top
View user's profile Send private message 
fredx181


Joined: 11 Dec 2013
Posts: 2585
Location: holland

PostPosted: Fri 20 Oct 2017, 06:02    Post subject:  

Hi rcrsn51, trister

Quote:
rcrsn51 wrote:
trister wrote:
The first thing I noticed at start is that I need to run "reconnect" from peasyWifi to get an IP from my router the first time I enter the system.

This sounds like a timing issue.

Look at the script /etc/rc.d/rc.nework. PWF makes two tries (line 19) with a 5 second pause between (line 23). Each try is controlled by the -t and -T options (line 21).

Maybe increasing some of these will help.

If you watch the boot messages, there should be a line near the end for "udhcpc". Do you see it?


I had the same problem at some point, reason was that /etc/init.d/rc.network-start wasn't executed.
That was because I had a .squashfs module loaded at boot that was created on another build (not with peasywifi installed), so the file /etc/init.d/.depend.start was overwritten and didn't have the proper config for rc.network-start e.g. this:
Code:
rc.network-start: cgmanager cgproxy start-pup-volume-monitor rsyslog motd bootlogs console-setup.sh acpid anacron dbus loadcpufreq rsync cpufrequtils slim


It could well be that a similar thing was the case for trister (I know from earlier posts that he uses extra .squashfs modules regularly)
Besides that, I think that a timing issue isn't very likely because you have set it to rather high already.
Lesson learned, only use a .squashfs module created by apt2sfs on the same build (although there are probably exceptions)

@don570, thanks for your contributions!, I'll get back on it later.

Fred
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 11720
Location: Stratford, Ontario

PostPosted: Fri 20 Oct 2017, 09:28    Post subject:  

Thanks Fred. Hopefully, that's the answer.

Under what conditions would a squashfs module contain /etc/init.d/depend.start?

I looked at one I made with apt2sfs and it wasn't there.
Back to top
View user's profile Send private message 
fredx181


Joined: 11 Dec 2013
Posts: 2585
Location: holland

PostPosted: Fri 20 Oct 2017, 10:01    Post subject:  

Hi rcrsn51

Quote:
Under what conditions would a squashfs module contain /etc/init.d/depend.start?


For every package that has an initscript included, and has in postinst script "update-rc.d ...." command

For me it was with mpd .squashfs (Music Player Daemon) (which I made with apt2sfs on another build), it has in postinst script:
Code:
update-rc.d mpd defaults

And /etc/init.d/.depend.start will be new created (also .depend.stop, btw)

To avoid the conflicting I just removed /etc/init.d and all the other rc* folders in /etc from the extracted mpd.squashfs folder (I don't need to run mpd as daemon, just on demand), created mpd.squashfs again and then worked without conflicting problems.

Fred
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 11720
Location: Stratford, Ontario

PostPosted: Fri 20 Oct 2017, 20:52    Post subject:  

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

Will they fight with each other?
Back to top
View user's profile Send private message 
fredx181


Joined: 11 Dec 2013
Posts: 2585
Location: holland

PostPosted: Sat 21 Oct 2017, 08:02    Post subject:  

rcrsn51 wrote:
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:
apt-get update
apt-get install deadbeef-static


Made list for TODO's:
Changes and Fixes list

Fred

_________________
Dog Linux website
Back to top
View user's profile Send private message 
trister

Joined: 01 Mar 2015
Posts: 78

PostPosted: Sat 21 Oct 2017, 09:59    Post subject:  

rcrsn51 wrote:
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 Smile

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.
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 11720
Location: Stratford, Ontario

PostPosted: Sat 21 Oct 2017, 10:24    Post subject:  

Thanks. Have you made any conclusion about why PeasyWifi did not auto-start? Does Fred have the correct explanation?
Back to top
View user's profile Send private message 
trister

Joined: 01 Mar 2015
Posts: 78

PostPosted: Sat 21 Oct 2017, 10:34    Post subject:  

rcrsn51 wrote:
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.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 3 of 5 [73 Posts]   Goto page: Previous 1, 2, 3, 4, 5 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Projects
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1567s ][ Queries: 12 (0.0132s) ][ GZIP on ]