StretchDog

[fredx181]

Thanks trister !

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 doesn't seem as much of a problem but since it is a live CD it might matter.

Oh, strange, that shouldn't be like that (for me it connects right away)

@all For Info: I probably won't be very active replying in the next days because I have the flu (began yesterday, don't know how it goes in the next days)

Fred

[trister]

@all For Info: I probably won't be very active replying in the next days because I have the flu (began yesterday, don't know how it goes in the next days)

Fred

I hope you get well soon.

[rufwoof]

@trister http://murga-linux.com/puppy/viewtopic. ... 601#850601 did it for me, logs in as puppy fine now.

@fred. ditto (flu), started today. Feeling pretty lousy.

How can user puppy be prevented from mounting partitions (force having to Ctrl-Alt-Fn ... login as root and mount a drive, or run sudo to mount a drive)?

Uncomment "chpupsocket $USER:$USER &" in /home/puppy/.config/openbox/autostart

Code:
# chpupsocket $USER:$USER &

(reboot required)

Btw, FYI, puppy can mount (by clicking drive icons) but has no write permissions

Not having cli permission to mount is good enough. Quite like still being able to mount from the desktop/gui as that relatively locks out cli breakins from doing something nasty like installing ransomware, but still being able to mount things as puppy from within the desktop environment. Mine mounts with rw permissions after a 'puppy' user desktop drive icon is clicked !!! That's great assuming it continues to work that way as more like running as root in feel, but with the ability to lock down partition access in the event of a hackers browser breakout.

I've adopted jwm as the wm and have set left click of the clock to be the MENU (right mouse click clock to showdesktop).

Not sure why the firewall isn't working under user puppy (shows as green when logged in as root, but under puppy I can't seem to turn it on).

[rcrsn51]

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?

[prehistoric]

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.

[fredx181]

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.

Yes, thanks !
So to upgrade to patched wpasupplicant on StretchDog:

Code: Select all

apt-get update
apt-get install wpasupplicant

Fred

[marcelo4768]

i want to install full stretchdog in a laptop year 2010 with 1,6 ghz and 3 gb ram and 300 gb hdd, help please, i have to use gparted first ? already have deepin installed but i want erase it and use only with stretchdog, my hangout is marcelo4768

[don570]

i want to install full stretchdog in a laptop year 2010 with 1,6 ghz and 3 gb ram and 300 gb hdd, help please

Open up the iso file(with a click) and read the readme file inside.
Once you get a Porteus install i.e. into a folder named 'live' on hard drive to work
you can then do a full install to an empty partition .
_______________________________________________________

[don570]

I was able to use the most recent version of pfind 6.3
(it needs a recent version of pfilesearch as well so I put it inside the package)
and I made a debian package so others can try it.

Available:
pfind_6.3_all.deb
Size: 28k
https://drive.google.com/open?id=0B7JZA ... 0djdmtPZUU
--------------------------------------------------------------------

I added a file --->

/usr/local/bin/defaultfilemanager and pointed it to thunar.

'Open location' feature will use it.

________________________________________

[ethplorer]

Very good job Fred

@ethplorer:

my menu.lst entry is like this :

Code: Select all

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

Btw, If anyone wants to try KODI without installing it :
kodi_2.3a17.1+dfsg1-3_amd64-deb_.squashfs https://1fichier.com/?5sl6u1qbfs
kodi_libs_addon_v001d_.squashfs https://1fichier.com/?gcn37ed4h6
maybe you'll also need this:
python279apt2sfs.squashfs https://1fichier.com/?ytqs6spvxt

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?

[don570]

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

_________________________________________

[don570]

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
_______________________________________

[trister]

Very good job Fred

@ethplorer:

my menu.lst entry is like this :

Code: Select all

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 it searches my puppy_StretchDog64 folder. This means I can move this folder in any drive and I don't have to change anything

[rufwoof]

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

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.

[rcrsn51]

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.

[trister]

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

[don570]

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

____________________________________

[fredx181]

Hi rcrsn51, trister

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: Select all

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

[rcrsn51]

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.

[fredx181]

Hi rcrsn51

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: Select all

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