TazPuppy 5.0 rc2

Under development: PCMCIA, wireless, etc.
Message
Author
darry19662018
Posts: 721
Joined: Sat 31 Mar 2018, 08:01
Location: Rakaia
Contact:

#301 Post by darry19662018 »

Basically for me the firewall is the most important item. If that script could handle iptables and configuring a basic firewall that would be cool.The trouble I have found with the Puppy Linux firewall is that it is that it is designed for a single user root system and doesn't work well with using the Tux account. I have been trying to get it to start each reboot and of course I use the Tux account and it doesn't.

I tried Ufw and that caused iptables errors.

s243a
Posts: 2580
Joined: Tue 02 Sep 2014, 04:48
Contact:

#302 Post by s243a »

darry19662018 wrote:Basically for me the firewall is the most important item. If that script could handle iptables and configuring a basic firewall that would be cool.The trouble I have found with the Puppy Linux firewall is that it is that it is designed for a single user root system and doesn't work well with using the Tux account. I have been trying to get it to start each reboot and of course I use the Tux account and it doesn't.

I tried Ufw and that caused iptables errors.
I think you have to change in
/etc/slitaz/firewall.conf so that line 12 says:

Code: Select all

IPTABLES_RULES="yes"
It looks like the slitaz firewall is started at boot because in /etc/rcS.conf
it has the following:

Code: Select all

# Daemons to start at boot time. DBUS daemon is started before the
# login manager and from: /etc/init.d/system.sh
RUN_DAEMONS="firewall httpd acpid pup_pcmcia pup_sfs_load pup_zramswap ntpd"
looking at the comment, I'm wondering if DBUS needs to be installed. If you want to use the puppy firewall instead then we need to remove friewall as one of the items in RUN_DAEMONS and in /etc/rc.d/rc.sysinit we need to add back the line which calls rc.local.

Note that the daemon that is started for the Slitaz firewall is

Code: Select all

/etc/init.d/firewall
This scipt on line 9 sources /etc/slitaz/firewall.conf

If iptables is enabled then it calls

Code: Select all

/etc/slitaz/firewall.sh
You can modify firewall.sh if you want to change which iptables commands are called. If you you like the way that puppy does it then you can copy your configuration in puppy from

Code: Select all

/etc/rc.d/rc.local
to

Code: Select all

/etc/slitaz/firewall.sh

darry19662018
Posts: 721
Joined: Sat 31 Mar 2018, 08:01
Location: Rakaia
Contact:

#303 Post by darry19662018 »

Thank you I think the Slitaz firewall is now running.

I still believe long term down the line that the Puppy Firewall would be better as it is so much easier to configure.

User avatar
don570
Posts: 5528
Joined: Wed 10 Mar 2010, 19:58
Location: Ontario

#304 Post by don570 »

Suggestion for improvement of rox package...

When I installed rox tazpkg I discovered that neither a SendTo or OpenWith folder was inside. So when a right click utility was used a
SendTo folder was created.(see image)


The problem with this is that Puppy linux
expects an OpenWith folder to exist.

So I suggest that the rox tazpkg have a SendTo folder and a link to the SendTo folder
called OpenWith.

This will help make Tazpup compatible with Puppylinux.

________________________________________________________
Attachments
screenshot-rox-tazpup.png
(14.36 KiB) Downloaded 318 times
Last edited by don570 on Sun 27 May 2018, 19:28, edited 1 time in total.

User avatar
don570
Posts: 5528
Joined: Wed 10 Mar 2010, 19:58
Location: Ontario

#305 Post by don570 »

To take a screenshot is easy using mtpaint file menu :lol:
However there is a small script that does the same...
mtpaintscreenshot.sh

http://www.murga-linux.com/puppy/viewtopic.php?t=55843

_______________________________________
Attachments
mtpaintsnapshot.gif
(10.21 KiB) Downloaded 320 times

User avatar
don570
Posts: 5528
Joined: Wed 10 Mar 2010, 19:58
Location: Ontario

pupmd5sum-tazpup-1.5a.tazpkg

#306 Post by don570 »

I made a small change to pupmd5sum 1.5 to place the right click menu item
in the SendTo folder...
This should solve problem with Rox

pupmd5sum-tazpup-1.5a.tazpkg
Size: 11k
https://drive.google.com/open?id=18Le-h ... YD1n6yHU3Z
____________________________________

User avatar
don570
Posts: 5528
Joined: Wed 10 Mar 2010, 19:58
Location: Ontario

#307 Post by don570 »

BarryK wrote a little helper app called getlocalip that I find useful.
I'd like it included in tazpup.

http://bkhome.org/news/201802/new-getlo ... ility.html
The source is in 'pup-tools-20180225.tar.gz':

http://distro.ibiblio.org/quirky/quirky ... betical/p/
_____________________________________________________

I compiled it precise puppy and included it in mpscan 1.1.
I use this app to track down my raspberry pi2 board :lol:
From image I see that it is on address 192.168.1.102

Available:

mpscangui-tazpup-1.1.tazpkg
Size :15k
https://drive.google.com/open?id=1mc5ia ... SeSCzBfnzL

_________________________________________
Attachments
screenshot4543.png
(16.66 KiB) Downloaded 317 times

mistfire
Posts: 1411
Joined: Wed 05 Nov 2008, 00:35
Location: PH

#308 Post by mistfire »

Tazpup alpha 9 released

* sh now symlinked to busybox-pup
* puppy firewall is now used
* mksquashfs now included
* remasterpup now working
* firewall_ng is now included
* pmount is now included
* readlink is replaced with full one
* underdog might work


Download: https://drive.google.com/file/d/14EkyM- ... sp=sharing

Build kit: https://drive.google.com/file/d/1emA9OQ ... sp=sharing

Delta: https://drive.google.com/file/d/1rTp0co ... sp=sharing
Last edited by mistfire on Mon 28 May 2018, 10:20, edited 1 time in total.

User avatar
rg66
Posts: 1158
Joined: Mon 23 Jul 2012, 05:53
Location: Vancouver, BC Canada / Entebbe, Uganda Africa!?!

#309 Post by rg66 »

mistfire wrote:Tazpup alpha 9 released
Cheers mistfire!

md5sum for delta and new iso?
X-slacko-5b1 - X-tahr-2.0 - X-precise-2.4
[url=http://smokey01.com/rg66/]X-series repo[/url]

mistfire
Posts: 1411
Joined: Wed 05 Nov 2008, 00:35
Location: PH

#310 Post by mistfire »

@rg66

Tazpup iso
MD5 checksum: 66f7808e467f4620ffcaa467c0fd2817

delta
MD5 checksum: c48e9b6fa7842d905e4822891dd808df

darry19662018
Posts: 721
Joined: Sat 31 Mar 2018, 08:01
Location: Rakaia
Contact:

#311 Post by darry19662018 »

mistfire wrote:Tazpup alpha 9 released

* sh now symlinked to busybox-pup
* puppy firewall is now used
* mksquashfs now included
* remasterpup now working
* firewall_ng is now included
* pmount is now included
* readlink is replaced with full one


Download: https://drive.google.com/file/d/14EkyM- ... sp=sharing

Build kit: https://drive.google.com/file/d/1emA9OQ ... sp=sharing

Delta: https://drive.google.com/file/d/1rTp0co ... sp=sharing
Hey Mistfire thank you for including Puppy firewall congrats on new release.

mistfire
Posts: 1411
Joined: Wed 05 Nov 2008, 00:35
Location: PH

#312 Post by mistfire »

@darry more welcome there is more fix to come. I wonder when I symlinked sh back to busybox-pup. Illegal export -f still happen. Is there anyway to fix that in order to make puppy apps run smoothly with only small revisions. On latest alpha pmount functions was splitted into scripts in order to get worked but it was executed outside the root process.

User avatar
fredx181
Posts: 4448
Joined: Wed 11 Dec 2013, 12:37
Location: holland

#313 Post by fredx181 »

mistfire wrote:I wonder when I symlinked sh back to busybox-pup. Illegal export -f still happen. Is there anyway to fix that in order to make puppy apps run smoothly with only small revisions.
That's the consequence. Only with sh > bash, gtkdialog apps with exported functions will work, maybe you have seen in the Programming section there's a lot of discussion about it recently and wiak made a mod named "gtkwialog" (pre-alpha) to work around that problem to some extend.
So if you stay with busybox-pup > sh, probably most gtkdialog programs (with export -f) need to be altered.

Fred

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#314 Post by rcrsn51 »

fredx181 wrote:need to be altered.
That's putting it mildly. They would need significant rewrites and separate versions.

wiak
Posts: 2040
Joined: Tue 11 Dec 2007, 05:12
Location: not Bulgaria

#315 Post by wiak »

I'm certainly planning to convert my own code, starting with cast2chrome, because that's why I started creating gtkwialog in the first case. For that one, it is to a large extent just going to be a simple matter of putting bash -c before each <action>bash function call string, but no doubt some programs might not be so easy to convert (though I don't know till I've converted a few for practice). I'm in no hurry.

wiak

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#316 Post by rcrsn51 »

I suspect that the problem won't be as much re-coding as testing and re-packaging.

The packaging issue will be significant when it comes to a build system like woof. How will woof handle two versions of the same app - gtkdialog and gtkwialog?

And who will be willing to manage all those parallel versions?

wiak
Posts: 2040
Joined: Tue 11 Dec 2007, 05:12
Location: not Bulgaria

#317 Post by wiak »

I doubt woof will be interested in gtkwialog actually. Very unlikely, seems to me, that Puppy stewards will have anything to do with it - been no comment from them at all during its development, which says plenty to me. Of course if one of the Puppy Stewarts had been developing it, do you think there would have been more comments from others? Puppy politics dictate more than people like to admit (not many longtime faithful puppy users ever comment in Dog threads, for example - odd to me that, really). Like I described in gtkdialog dev thread, for my own system I'll be adding commandline switches to gtkwialog such that it will also handle legacy gtkdialog mode - but I'm not pushing that on anyone else - just know I'll be using that one.

I originally thought of sending patches to Puppy github gtkdialog, but at that time I hadn't got to the stage of getting gtkwialog to work and hadn't thought of making it do either, and then you (rcrsn51) questioned the idea of anyone tinkering with current gtkdialog, which was a fair point; so I decided best to make my altered one a fork, which gives me more freedom in developing it without worries anyway.

As far as my own shell/gtkdialog apps go, the existing ones just stay as they are - a few of these I'll mod to use gtkwialog. New ones will use gtkwialog - that's just my plans for my own home system though. I expect Puppy will continue with gtkdialog, but that means new app writers should be advised to avoid export -f function convenience of bash.

The main problem is for those whose systems are not using /bin/sh -> bash. They have to mod any shell/gtkdialog programs that currently use export -f.

Did Puppy always use bash as /bin/sh? Seems an odd choice to me to use bash for system shell. Maybe it was gtkdialog that forced that choice because bash is more powerful as a programming language so of course its facilities (like export function capability) would be used? But user's interactive shells (and for user shell programming) is really the target for bash, not for system non-interactive shell where resource usage and speed is dictated. It is no accident (in addition to looking for minimal size) that neither Slitaz nor Tiny Core Linux nor Debian proper use bash as their system shell. All is fine if you just use Puppy though, except for current TazPup busybox ash situation.

wiak
Last edited by wiak on Mon 28 May 2018, 18:19, edited 8 times in total.

User avatar
Marv
Posts: 1264
Joined: Wed 04 May 2005, 13:47
Location: SW Wisconsin

#318 Post by Marv »

I removed a bashism from the acpi handler I use for lidsuspend and re-uploaded here My humble approach to tazpup is to have the minimum core puppy substructure (persistence & saving, layered filesystem, suspends, firewall (thanks!) etc. running well and then add all applications from the Slitaz side. Pmount is nice to have for emergencies but with the volume management of PCManFM set up to automatically mount 'remote' drives I find I seldom use it. This overall approach is obviously not everyones cup'o'tea but I'm learning a lot and continually smile at how much can be done in small (again). Alpha9 running very nicely on my main i5 laptop.

Thanks mistfire,
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.

wiak
Posts: 2040
Joined: Tue 11 Dec 2007, 05:12
Location: not Bulgaria

#319 Post by wiak »

Yeah, for tazpup, I would also just use that as nice way to get Puppy save persistence and not using too much RAM and so on - otherwise, nothing wrong with Slitaz apps IMO. Don't need to Puppify it or make it a puppy-lookalike. Anyway, I'm clearly tired now so off to bed and forget computer for a while for me just now.

wiak

s243a
Posts: 2580
Joined: Tue 02 Sep 2014, 04:48
Contact:

#320 Post by s243a »

wiak wrote:Did Puppy always use bash as /bin/sh? Seems an odd choice to me to use bash for system shell. Maybe it was gtkdialog that forced that choice because bash is more powerful as a programming language so of course its facilities (like export function capability) would be used?

wiak
I support your initiative to improve the compatibility of gtkdialog? But as a short term hack, why not just change the hashbang of the scripts that require bash to point to bash?

Maybe this can be done via a delta file and we can run some kind of script to look for bahisms and modify the shebang.

Post Reply