Classic Pup 2.14X -- Updated 2 series

[37fleetwood]

I've been watching this thread with much interest. it seems this is the direction Puppy should have gone.
I've been playing with RC-5 and am very impressed! I have one request before you release the final, instead of GQview, can you swap it for Geeqie? GQview is the old dead project, someone has picked the project up and made many very good improvements in Geeqie. it uses GTK2, I don't know enough to know if that will be a problem. it's about the same basic size, puppyluvr made a .pet for use in his Puppy Artist Workshop (based on 4.12) not sure it is usable as it is, but the thread for P.A.W. is here:
http://www.murga-linux.com/puppy/viewtopic.php?t=40876
the Geeqie .Pet is on page 5.

the link to the page for Geeqie is here:
http://geeqie.sourceforge.net/

either way thank you for all your work on this great re-vamping of 2.14, Amazing!

[clarf]

2byte
As to click-mounting .sfs-files in Rox: it works very well for squashfs-files of version 3.0, as used in puppy series 2 (and, I think series 3) but, not for squashfs ver. 3.1, as used in 4.12, nor for squashfs ver. 4, as used in later puppies, quirkies, waries etc.

Yes, I discovered this behavior when I made my

*sfs compatibility chart*

You could update or change you kernel patching it with a newer squashfs version, then this new kernel will be able to load different SFS versions in 214X.

In full install it´s very easy to accomplish, and you can simplify the work if you compile BarryK patched sources (I used 2.16.8.8 patched with squashfs 3.3 version). For frugal is a little more complicated, I´m experimenting with this right now and I have reached some good results with a small effort. There is a good thread about this process, I shared some of my own experiences here:

http://www.murga-linux.com/puppy/viewto ... 1&start=52

In Puppy 214X there are many additional drivers in zdrv_214.sfs file (as we learned with the full installation problems that we had in past releases). The problem is know what should be left in the zdv file and what should go in the pup_xxx.sfs file, there are some size considerations but I don´t know a general rule or standard for that.

I also found some redundant information in zdrv_214.sfs and pup_214.sfs files, for example the Ndiswrapper module is in both SFS files but the size and date are different, I suppose Puppy modprobe script (a workaround/wraper used by Barry to load external modules in zdrv) uses the one from pup_214X.sfs because it´s found first, anyway its unnecessary to have that redundancy.

I think if we do a deep search and classification for these files we could reduce the pup file, moving some modules to the zdr file, obviously the zdrv size will be increased but the boot time and memory consumption will be lower for 2.14X.

The attached pic shows the redundant Ndiswrapper module in zdrv (upper) and pup (bottom) SFS files.

clarf

[Colonel Panic]

I've been watching this thread with much interest. it seems this is the direction Puppy should have gone.
I've been playing with RC-5 and am very impressed! I have one request before you release the final, instead of GQview, can you swap it for Geeqie? GQview is the old dead project, someone has picked the project up and made many very good improvements in Geeqie. it uses GTK2, I don't know enough to know if that will be a problem. it's about the same basic size, puppyluvr made a .pet for use in his Puppy Artist Workshop (based on 4.12) not sure it is usable as it is, but the thread for P.A.W. is here:
http://www.murga-linux.com/puppy/viewtopic.php?t=40876
the Geeqie .Pet is on page 5.

the link to the page for Geeqie is here:
http://geeqie.sourceforge.net/

either way thank you for all your work on this great re-vamping of 2.14, Amazing!

Seconded. I've downloaded and am using Geeqie now and it's as good as GQView was.

[Bligh]

With so many choices, I am not using 2.14x at the moment, but it is great to see a previous version updated. If it works well, there is little reason for it to disappear. A lot of us may not know how to update it. Thanks.
Cheers

[zenfunk]

Hm, seeing the updated series two getting more and more followers I really start to wonder if it would be a good base for new derivatives. Since I'm not willing to read well over 300 pages of thread, could someone enlighten me please, what is 2.14x all about?
Which difference is there between the architecture of 2.14 and say the 4. series?
Is there a webpage with a FAQ?
Which pet packages will work, can I use the latest ubuntu .deb- packages?
Can I remaster it?
Thanks in advance for your information.
Christian

[yorkiesnorkie]

Hi

Quick question. Is there a devx sfs file for 2.14x? I wanted to compile an application for it , clamav 0.96, but I found the lowest version sfs at Ibiblio is devx_216.sfs. It made me wonder if there's something special for 2.14x or if there are other secrets!

y.

[James C]

It was just a couple of pages back, see here.......

http://www.murga-linux.com/puppy/viewto ... 526#412526

I think the actual devx is is at......

http://puppylinux.ca/tpp/ttuuxxx/2.14se ... 4X-RC2.pet

HTH.

[yorkiesnorkie]

Thank you! I might not have picked up on the missing library if it were not for that link.

Thanks again,

y.

[James C]

Thank you! I might not have picked up on the missing library if it were not for that link.

Thanks again,

y.

You're welcome.

[don922]

I cannot figure out how to increase the size of the mrxvt screen. I need it to be at least 80 X 30 -- but I can't find where to make the adjustment in the .mrxvtrc for this version of mrxvt.

In the meantime, I have used a .mrxvtrc from a earlier version of mrxvt. This "sort of works"....but I have lost some of the features from the installed version.

Is the correct description of items in the .mrxvtrc "Mrxvt." or "mrxvt*"? The installed version uses "Mrxvt." The earlier version uses "mrxvt*". (omitting the quotation marks)

Help!

[MinHundHettePerro]

I cannot figure out how to increase the size of the mrxvt screen. I need it to be at least 80 X 30 -- but I can't find where to make the adjustment in the .mrxvtrc for this version of mrxvt.

In the meantime, I have used a .mrxvtrc from a earlier version of mrxvt. This "sort of works"....but I have lost some of the features from the installed version.

Is the correct description of items in the .mrxvtrc "Mrxvt." or "mrxvt*"? The installed version uses "Mrxvt." The earlier version uses "mrxvt*". (omitting the quotation marks)

Help!

Hello !
Add the line

Code: Select all

Mrxvt.geometry:		    80x30

to /etc/mrxvt/mrxvtrc (of the pre-installed version, where M in Mrxvt needs to be capitalised). Don't know which section of the file would be the appropriate........ Works if just appended, though.

rgds/
MHHP

[MinHundHettePerro]

ttuuxxx

In 214X, on first boot I've always had geany to open too large a window, and offset at that ........

Perhaps this post would apply also to 214X .

Cheers /
MHHP

[yorkiesnorkie]

I use the Geany tag at the bottom of the screen and right click, and maximize. That usually brings it back within the visible area. I've an 800x600 display so that happens sometimes with different windows. Some of the preference windows in Seamonkey for example...

y.

[yorkiesnorkie]

Hi,

Has anyone else had problems with the 2.14xrc5 iso? I downloaded it, and burned it to cd but on booting from the live cd I get

Code: Select all

invalid compression format (err 2)

I thought that was odd. I ran md5sum on the iso and it checks out ok.

I downloaded the iso again on our other pc, ran the md5sum check, it was ok, burned it to cd on that machine, and... I got the same error.



I had just burned an iso of 4.3.1 using the same media (brand of cd) and it works...

I'm not sure what I should do next.

Edit: found this post this morning which is related to it... http://www.murga-linux.com/puppy/viewto ... 6718bb7e89

The md5sum checks out so I'm not quite sure where to go next with this one. The CD drive will boot other Puppy live CDs so I think I can rule that out. Maybe I just got two bad burns for whatever reason. I'll give rc4 iso a go in the meantime and see if that one works. It'll get me where I want to go for the moment although I'd like to run rc5.

y.

[James C]

Hi,

Has anyone else had problems with the 2.14xrc5 iso? I downloaded it, and burned it to cd but on booting from the live cd I get

Code: Select all

invalid compression format (err 2)

I thought that was odd. I ran md5sum on the iso and it checks out ok.

I downloaded the iso again on our other pc, ran the md5sum check, it was ok, burned it to cd on that machine, and... I got the same error.



I had just burned an iso of 4.3.1 using the same media (brand of cd) and it works...

I'm not sure what I should do next.

Edit: found this post this morning which is related to it... http://www.murga-linux.com/puppy/viewto ... 6718bb7e89

The md5sum checks out so I'm not quite sure where to go next with this one. The CD drive will boot other Puppy live CDs so I think I can rule that out. Maybe I just got two bad burns for whatever reason. I'll give rc4 iso a go in the meantime and see if that one works. It'll get me where I want to go for the moment although I'd like to run rc5.

y.

When you downloaded RC5, did you get the entire 115 MB? I downloaded the day it was released and have had no problem either installing or running live.

Corrupted files are a real pain......

[James C]

Well, I just downloaded RC5 ,burned it and am posting from it running live.Loaded perfectly.Don't know what the problem may be but I don't think it's related to caneri's server.

[Aitch]

yorkiesnorkie

This could be an old burn problem....burning too fast at 32x will often wreck a good download, where burning at 8x works OK - if the MD5 hash is good

Different CDR makes also sometimes give problems with some hardware

Try a different make of CDR, if slower burn doesn't work

A final [odd] possibility I've had is when an ISO is saved as a compressed file, by Nero, instead of an ISO - solution, rename the file extension from .zip to .iso

HTH

Aitch

[yorkiesnorkie]

Hi,

If your getting a 115 mb iso, that isn't what I got... My iso download is 118360kb... same download twice... and I got that from puppylinux.ca In ROX it shows the filesize as 116mb. All I can attest to is that the download I have here does not work. All I can do is try the download again and see what the total kb is on the third go around.

y.

[yorkiesnorkie]

yorkiesnorkie

This could be an old burn problem....burning too fast at 32x will often wreck a good download, where burning at 8x works OK - if the MD5 hash is good

Different CDR makes also sometimes give problems with some hardware

Try a different make of CDR, if slower burn doesn't work

A final [odd] possibility I've had is when an ISO is saved as a compressed file, by Nero, instead of an ISO - solution, rename the file extension from .zip to .iso

HTH

Aitch

All burns of the iso files were performed from within puppy linux 4.3.1 one at 4x and the other at 1x. I do this all the time and both burners do work. Like I said I made a new 4.3.1 cd right before the others using the same media at 4x and it works.

I might have a bad download if the file size does not match what I'm reading here. I don't understand why the md5sum isn't erroring out. I'm going to look into that again momentarily.

y.

[James C]

The iso file on my hard drive is 118,360 Kb as well, just checked 30 seconds ago, and when I mouseover it shows 115 mb. Difference between kb and mb and rounding off......

I concur with Aitch, it could be the burning speed.

I generally try to burn as slow as possible,usually 4X , however I recently changer burner drive and anything I burned at 4X was a coaster........started burning at 16x and the discs boot again. Just a thought.