Puppy Linux Discussion Forum

stu90 · Posted: Tue 05 Apr 2011, 07:57 Post subject:

regarding remaster.

Hi Playdayz,
Had a report over in the Lucid lite thread regarding the lite version as well as the your official version about the personalize settings dialog running on start up (with no save file) even after /root and /etc directories being copied during the remaster - custom setting appear to be copied over as they are now the default in the personalized setting gui but is there any way to disable or stop the personalized setting gui from running?

thanks.

Lobster · Posted: Tue 05 Apr 2011, 08:09 Post subject:

Hey stu - regarding remaster - notice the remastering info
I wanted to see how easy remastering would be
It went well
and I created a nearly 300MB iso

Technical info
Puppy is VERY easy to customise
Set it up and use the Menu/Setup/Remaster Live CD option

What I did
changed wm to jwm and removed Openbox
changed backgrounds more background smaller size - add your own image files to usr/share/backgrounds
removed some games
use menu/setup/remove built in packages
to remove packages

added
python
firefox4
wbar
xaralx
fotoxx
transmission
xchat
skype
openshot
vlc

configured wbar by editing /root/.wbar
i: = icon
c: = command
t: = text under icon

Remastering
Before you remaster, you need to

1. rename /usr/sbin/xorgwizard to /usr/sbin/xorg-setup
2. copy the attached xorgwizard into /usr/sbin. ( right-click -> Save As) http://diddywahdiddy.net/Puppy500/xorgwizard

What is happening is that on first boot, the attached xorgwizard runs and Lucid boots to the desktop, then it renames xorg-setup to xorgwizard so that users can run xorgwizard. Sneaky, huh?

You also need to change the permissions on /root/Startup/fullstart. You could do that during the remastering process when it gives you a chance to adjust files in /root. The way I do it is to right-click and choose Permissions. So if the name fullstart turns green that means the permissions are correct for it to run on first boot.

Full details
http://tmxxine.com/tmx525/

Youtube video
http://www.youtube.com/watch?v=a0wUnOLdkJw

Germador · Joined: 13 Mar 2011 Posts: 7 Location: Yellville, Arkansas

Ubuntu 10.10 calls my Lucid 5.25 an unknown file system but now I don't have to go into BIOS each time and choose each time which hard drive to boot up first. II put the Puppy on the 40 GB hard drive. The Omega disk gives it a bit more memory some how. I had trouble before because Ubuntu 10.10 uses grub2 and I did the grub4dos thing. Puppy is recognized with grub2 now as the unknown file system but it boots okay that way with no problems. So I am glad I didn't use the grub loader in Puppy.as it didn't mess up the SATA drive where Ubuntu is at. Very Happy

live · Joined: 10 Feb 2010 Posts: 108

Bug in Lucid 5.25 but not in Ubuntu 10.10

Under Iron 10 or Firefox 4 if I try to attach a file from sda4/privé/test.pdf Lucis says "Le fichier est introuvable. Vérifiez qu'il s'agit du fichier correct et réessayé" so it means : "The file is not found. Verify that this is the correct file and try again".

Same through LibreOffice, Thunar

Oddly only ok through ROX !

666philb · Joined: 07 Feb 2010 Posts: 1264 Location: wales

willem1940NLD · Posted: Tue 05 Apr 2011, 10:06 Post subject:

Only the link from the start of this thread and it is 128MB.

blopa6 · Joined: 15 Apr 2008 Posts: 32

666philb · Joined: 07 Feb 2010 Posts: 1264 Location: wales

tasmod · Posted: Tue 05 Apr 2011, 11:16 Post subject:

Firewallstate.

In firewallstate the code routine for turning the firewall on/off was originally meant to be for testing purposes, I never meant it to 'kill' the firewall program.

The routine uses the firewall programs stop/start feature. (Note:Firewall program, not firewallstate)

The firewall program once installed writes a code line to etc/rc.d/rc.local that checks for the firewall programs file rc.firewall which is created when the firewall program is first run.
Now this will then start the firewall each time at each boot and is independent of the stop/start feature.

To prevent the firewall from restarting at boot I would need to rewrite the code snippet in firewallstate that turns the firewall on/off so that it would erase the rc.firewall file and the rc.local file line for the firewall. This means that to restart the firewall would require a complete re-run of the firewall wizard install routine, hence the entry for this in the firewallstate menu.

I suppose I could add another option in the stop/start small window that would 'kill' the firewall preventing further boot starts. If that's what you wish. Smile

bigpup · Posted: Tue 05 Apr 2011, 11:26 Post subject:

Terryphi · Posted: Tue 05 Apr 2011, 11:51 Post subject:

RandSec · Joined: 10 Aug 2009 Posts: 81 Location: Austin, Texas

tasmod · Posted: Tue 05 Apr 2011, 14:36 Post subject:

I don't want to get into the argument about default firewall either on/off at starting.

I wrote the basic firewallstate originally just to point out the fact that the firewall was off at first start of a new install. it has just developed from user requests since then.

The option I'm working on will just be for a seasoned user to be able to stop the firewall and prevent it's restart on rebooting.
Although I'm having to do a bit more work than I at first thought. The way it is all written requires checks to be done first before the routine to remove the firewall. Gtkdialog doesn't help Rolling Eyes

RandSec · Joined: 10 Aug 2009 Posts: 81 Location: Austin, Texas

tasmod · Posted: Tue 05 Apr 2011, 15:51 Post subject:

firewallstate-1.9 is available in forum Additional Software - Network.

This has the added stop and remove from bootup for the firewall. It is remembered when off.

Interesting results with gtkdialog in older version I wrote the On/Off routine with and new version.
One would echo a command and stop, the newer version execute it without any syntax change. Confused