I'm going to try an experiment. I will edit the initrd.gz with your tweak Jim and do a frugal to an ext3 partition.. then boot without a pupsave and see if it saves it as 3fs... then see if reboots ok. If the file is created as 3fs then it should probably work ok. I will take a thorough look at the init script just to see if there is anything that might trip up this experiment.

You may want to take a look at Tazoc's and Kirk's changes to their init files. You should have Tazoc's, if you haven't got Kirk's I should be able to post it here.
Jim

My experiment is a success .. and I haven't looked at tazoc'z scripts yet.

I applied your changes to init Jim, no problem.

I then unsquashed lupu-002.sfs and edited the /etc/rc.d/rc.shudown script. That was simple because puppy in the older 2 series supported saving to ext3, ie pupsave.3fs. I just uncommented the lines and the "if" statement. No choice, just detects what ext fs you have and installs 2 for 2 and 3 for 3. No ext4 support. This is where tazoc's shutdown script will come in. Then resquashed.

As far as init goes, the line(s) where it gets mounted "-t ext2" will have to made a variable.. (I'll see what tazoc did once again) something like "-t $EXTFS" where EXTFS is defined by detecting the pupsave filesystem, not a too difficult task.

The fact is that it is good to have choice. Some users find errors creeping into there pupsaves using ext2, others don't. Maybe it's because of the hardware I don't know, but as Jim said there are certain advantages of using ext3 or ext4, as I'm sure there's other advantages to sticking with ext2.

That post talks about 2.6.30.5 and BK did say he would consider the option change. Does anyone know if BK did change it for 2.6.31.5 plus?

For the good order, I booted with pfix=ram.
Configures the wireless connection, which worked file. (SNS)
Created another, new, save file.
Rebooted.

The network configuration wasn't persistent between the boot.
Don't think this is a surprise, as quirky has the same quirk.

Well to my surprise after boot this morning my connection was up and running automatically.
Nice and hope this continues._________________Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
Consult Wikka
Use peppyy's puppysearch

As ayttm crashes, I use Pidgin as IM. In fact I use Pidgin already a long time in all my puppies.

In Lucid there is a problem with sound when entering messages etc..
In puppies using mplayer I can configure Pidgin by configuring mlayer %s
If I configure pidgin with gxine %s, the sound plays but delayed and I have the GUI as well, which disappears after an other delay.
This doesn't arrive with mplayer.

I had in mind in earlier puppies there was also the sound engine xine, but I don't see it in Lucid.

I checked the gxine options, but I don't see anything to play a sound without the GUI.

PPM doesn't show a xine package neither.

Would there be a way to solve this._________________Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
Consult Wikka
Use peppyy's puppysearch

The fact is that it is good to have choice. Some users find errors creeping into there pupsaves using ext2, others don't. Maybe it's because of the hardware I don't know, but as Jim said there are certain advantages of using ext3 or ext4, as I'm sure there's other advantages to sticking with ext2.

That post talks about 2.6.30.5 and BK did say he would consider the option change. Does anyone know if BK did change it for 2.6.31.5 plus?

Didn't realize it immediately, but the icon backgrounds aren't transparant, but black.
I remember something about 16-bit in xorg solved this, so I did run xorgwizard.

Yes .. narrowed down to a JWM issue.. Barry has mailed Joe Wing about this one, although, by all reports, latest xorg (7.5?) is still buggy, especially with Intel chipsets.. (kattman )

Cheers

Well, I wonder if xorg isn't in it for something also.
Reason I say, I have a wine program. In 24-bit icons used are correct.
As I switched to 16-bit for the Lucid (and quirky) issue I just realized, that in this wine program the icons aren't correct any more.
And don't laugh, some icons have a black background instead of a transparent one.

I then unsquashed lupu-002.sfs and edited the /etc/rc.d/rc.shudown script. That was simple because puppy in the older 2 series supported saving to ext3, ie pupsave.3fs. I just uncommented the lines and the "if" statement. No choice, just detects what ext fs you have and installs 2 for 2 and 3 for 3. No ext4 support. This is where tazoc's shutdown script will come in. Then resquashed.

Great, but I don't think that it will be that simple to change the rc_shutdown script. Consider a PM to tazoc, he initially had a problem with frugal installations on an NTFS or FAT32 partition, this was discovered with his initial release of 443G which he had to pull and update. Have you tried it on an NTFS partition?

I'm glad that you've taken an interest in this because when you do, you are determined to see it to a successful conclusion. My code knowledge is so minuscule that all I can do is help test your solutions.

jim1911, Would it be possible to write brief instructions about how to do this. I would personally want to try it. It might be something Barry would consider for inclusion in Puppy 5.

A better source of information is to PM kirk and tazoc. As I stated Kirk's Fatdog 64 creates a pupsave.3fs file by default and Tazoc's Lighthouse 443Gu1 gives a choice. I don't know how their scripts are set up to accomplish that for the save files. Also they have to modify the init file in intrd.gz in order for the save file to mount properly.

2. When booted, running the command mount should show it mounted as 3fs. To accomplish this, the init file in ﻿initrd.gz needs to be edited so that the 3fs save file properly boots.

3. This procedure shows how to unpack and repack initrd.gz ( the Pizzasgood way, I think ) Place the initrd.gz file that is to be edited in a temp directory.

a. Unpack
cd to temp directory containing initrd.gz then execute

Code:

mkdir initrd-tree
cd initrd-tree/
zcat ../initrd.gz | cpio -i -d

b. ﻿Modifying init ---Locate the init file that was unpacked and is now in the initrd-tree directory.
Search for ' -t ext2' - this will pick up the commands
where pup_save gets mounted as -t ext2 and you change it to -t ext3

c. Repack
cd again to initrd-tree then execute

Code:

rm ../initrd.gz
find . | cpio -o -H newc | gzip -9 > ../initrd.gz

I've followed this procedure with 431, 432, dpup, upup, Lighthouse (earlier releases), Stardust, Lucid 002, and others and found that in init, three lines like that need to be changed. All of the above I've run using a pupsave.3fs on ext3 and ext4 partitions with no problems.

Use mount command to confirm that the 3fs is mounted properly.

Thanks again for considering 3fs save files.
Jim

I applied the procedure, but I am not sure about the last part to check with mount.
The save file being on a ext2 partition sdb7 this one is mounted as ext2
How can I verify the save file then?

I applied the procedure, but I am not sure about the last part to check with mount. The save file being on a ext2 partition sdb7 this one is mounted as ext2
How can I verify the save file then?

I have no idea about your mount results, have never converted a pupsave.2fs to 3fs and checked mount on an ext2 partition. Why convert a pupsave.2fs to 3fs when you are using it on an ext2 partition?

I had the impression you had done this 2fs -> 3fs experiment.
Because in quite some threads a 2fs save file is considered unstable due to unclean unmounts. And this is my experience also.
The advice was given to better use a journaling file system like a 3fs.
It's not because the host, in my case the sdb7, is a ext2 partition that a save file automatically is a ext2 file system as well. A save file, be it a 2fs of 3fs file system can be on a partition like ntfs, vfat, ext2 etc...._________________Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
Consult Wikka
Use peppyy's puppysearch

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