Classic Pup 2.14X -- Updated 2 series

[Sit Heel Speak]

Yep, the frugal install reads the savefile which it itself created. Strange that it won't read the one created by the live CD.

Unfortunately, the init also picks up on the existence of my boxpup-421-retro savefile, which is in psubdir /boxpup-421-retro, so the init process halts to give me the choice between the two.

Perhaps study of the init and Puppy Universal Installer of boxpup-421-retro might yield clues as to how to make 214x create the installation in a psubdir, and work properly while co-existing with other frugal installs in their own psubdir's.

Anyway, on now to see if I can make my unmodified Opera .pet and/or .sfs work in it...done.

[MinHundHettePerro]

Yep, the frugal install reads the savefile which it itself created. Strange that it won't read the one created by the live CD.

Unfortunately, the init also picks up on the existence of my boxpup-421-retro savefile, which is in psubdir /boxpup-421-retro, so the init process halts to give me the choice between the two.

Perhaps study of the init and Puppy Universal Installer of boxpup-421-retro might yield clues as to how to make 214x create the installation in a psubdir, and work properly while co-existing with other frugal installs in their own psubdir's.

Anyway, on now to see if I can make my unmodified Opera .pet and/or .sfs work in it...

There was a (semi?)-conclusive discussion on this a few thousand ( ) posts back in this thread.
I don't remember all the variants of how to enable having all 214X-files in a sub-directory, though. I simply applied the full-caboodle solution and have only copied/pasted/modified the GRUB entries for new 214X frugal installations. At times I've had a lot of them frugally installed, all in their own sub-dir.
Anyway, I'll attach the GRUB entry I use, with the reservation that some parts could be superfluous.

Code: Select all

#
title Puppy 214XRC5_P on hda5/puppy_214XRC5P_ReiserFS
rootnoverify (hd0,4)
kernel /puppy_214XRC5P/vmlinuz root=/dev/ram0 PMEDIA=idehd PDEV1=hda5 PUPMODE=12 DEV1FS=ext2 SFSFILE=ext2,hda5,/puppy_214XRC5P/pup_214X.sfs ZDRV=ext2,hda5,/puppy_214XRC5P/zdrv_214X.sfs PUPSAVE=ext2,hda5,/puppy_214XRC5P/pup_save-214XRC5P.rfs PKEYS=se pTZ="PUP-1"
initrd /puppy_214XRC5P/initrd.gz
#

There was also a subsequent discussion on how much of the above could be omitted (also a few thousand posts back)...

The above boot stanza inhibits the choice between save-files - only boots the one specified ...

fwiw/hth /
MHHP

[Sit Heel Speak]

...There was a (semi?)-conclusive discussion on this a few thousand ( ) posts back in this thread...MHHP

Ah. I see. Thanks.

However, I don't think I will be lingering here. Puppy Studio 3.3, with icewm reconfigured a bit, suits my needs so well --it is the first Puppy, ever, that I actually find pleasant to use-- --heck, I'm in freakin' love with the thing-- that I now find it painful to use other Puppies.

Here is one of the things I find most painful about 214x-top6. This is not meant to take away from the prodigious amount of work which ttuuxxx has put into it, but, I find these scrunched-up columns in Rox to be unacceptable:
http://i54.tinypic.com/2e2pm6p.png

Also, when you have as many files in a subdirectory as I do, the older disk drivers in kernel 2.6.18.n just do not compare with the speed of the ones in newer kernels, i.e. I fall asleep waiting for rox and find.

[_Mark_]

Hey ttuuxxx

Found a bit of a typo in the logout screen you missed a c out of switch, on the switch to jwm button

[ttuuxxx]

Here is one of the things I find most painful about 214x-top6. This is not meant to take away from the prodigious amount of work which ttuuxxx has put into it, but, I find these scrunched-up columns in Rox to be unacceptable:
http://i54.tinypic.com/2e2pm6p.png

Hmm I never had rox look like that, are you sure you didn't reconfigure it? Are you sure you don't have a pupsave from 2.14R, I remember it looked like that. Below is what it looks like when you bootup live. Rox also has never been slow on 2.14X, well not on any of my pc's. The only time its a bit slower compared to 4&5 series is when I install very large pets, around 80+ MB
ttuuxxx

[ttuuxxx]

Hey ttuuxxx

Found a bit of a typo in the logout screen you missed a c out of switch, on the switch to jwm button

thanks mark I'll look at it
ttuuxxx

[Sit Heel Speak]

Hi ttuuxxx,

...Hmm I never had rox look like that, are you sure you didn't reconfigure it?

Only as I usually do:

Rox in 214x-top6:
http://i51.tinypic.com/2cy8f5.png

Rox in Puppy Studio 3.3:
http://i54.tinypic.com/5oegd1.png

...AHA!!! It's that Max Width --> Small Icons setting.

Boosted it to 250 and now it is usable.

Are you sure you don't have a pupsave from 2.14R?

Yes, there is no other 214 pup_save on this machine. I named it specifically, "pup_save-214xtop6.3fs". All other pup_save's are within psubdir's. boxpup-421-retro's pup_save is the only other pup_save the 214x-top6 init sequence detects the presence of. There are 27 other pup_save's in this partition, besides 214x-top6's and boxpup's, but 214x-top6 evidently stops looking after it finds boxpup's, which is the next Puppy alphabetically.

Another noticed flaw: the pup_events collection of scripts...whichever is the responsible one...is drawing the drive icons too close to the bottom edge when Rox->Options->Pinboard->Icon grid step is set to Coarse. The drive labels are covered over by the taskbar, see above-linked screenshot. If I drag them up so the labels are visible, the icons drop back down again upon next reboot.

I can definitely notice the difference in speed with which Rox loads a partition's contents for display, and speed of PFind and find, between kernel 2.6.18.1 and 2.6.33.2. But then, all my disks on this machine are SATA 150 --I've gotten rid of all my SCSI gear. It stands to reason that the driver has been improved.

Best,
SHS

[efiguy]

Hi,

Been awhile since I tried a new Puppy, couldn't resist with all your improvements listed.

using Pfix=ram it loaded like a champion, and I found network perfectly, as actually posting from 214xt6 here.

Don't know where to list possible bug, but could not locate the "Left Hand" mouse switch button, could be my system as using a KVM system switcher but other Pups have had the left hand switch.
Great job, works fast on this custom 933 P3, w512, rtl netcrd

PostScript_1
Just noticed clock is wrong and no menu way to set it, also looking at loaded modules Hiawatha had started on initial load

PostScript_2
WoW!!! shutdown Cups and Webserver _ 276 Mb of free mem as a pfix ram full load
I think I'll move this SFS into my exe install dir


Thank You - thank you
jay

[sheldonisaac]

Most snipped.

1 Just noticed clock is wrong and no menu way to set it

Menu -> Desktop -> Set date and time

[MinHundHettePerro]

1b ..., also looking at loaded modules Hiawatha had started on initial load

Easiest, non-destructive, way to stop it from starting at every boot is to remove Exec-permissions of /etc/rc.d/init.d/hiawatha.run:

Code: Select all

chmod 644 /etc/rc.d/init.d/hiawatha.run

Cheers /
MHHP

[ttuuxxx]

I've took one of the backgrounds in 2.14x made a system link, added lots of code to the gtk theme and came up with menu background in the menu. do you guys like it?
also added arrows, blue and green
ttuuxxx

[James C]

Nice.

[ttuuxxx]

it also works in rox , so it works with rox in jwm also.
ttuuxxx

[glenco]

ttuuxxx
That is the sharpest looking menu I’ve seen since we started playing around JWM themes way back when. But, that grey taskbar has gotta go. LOL

[MinHundHettePerro]

Nice one, ttuuxxx !

Care to share the gtk theme-hack ?

Cheers /
MHHP

[ttuuxxx]

Nice one, ttuuxxx !

Care to share the gtk theme-hack ?

Cheers /
MHHP

I'm still working on it, but I was just going to add it to the next release, Probably in a day or two , well a new Firefox is out and The default layout bugs me so I'll revert it to the older look.
ttuuxxx

[Sit Heel Speak]

I've took one of the backgrounds in 2.14x made a system link, added lots of code to the gtk theme and came up with menu background in the menu. do you guys like it?

Hooo-eeey, I don't suppose you could transplant that into l0wt3ch's MyCrossover icewm theme, as supplied in Puppy Studio 3.3?

[clarf]

To answer your question:
I've been thinking about how to upgrade the kernel to sfs ver. >=3.1 (proper, 214 has some 3.1rc[1|2]), and also whether it would be feasible to upgrade the kernel to 2.6.18.8. Kernel 2.6.18.1 that was used for 214[-|r|X], 216(1) and 217(1) were patched by BK and all the links to the original, complete, sources, patches and all, seemed dead (puptrix.org, e.g.); I had some patched sources of K2.6.18.1 stashed away, and ttuuxxx provided some more at his smokey01 repo.
Regardless, I wanted to (at least in the first go at it) keep all the original BK-patches to the kernel, so as not to risk loosing any support for older hardware that was working, thus I manually patched BK's K2.6.18.1 (already patched with sfs-3.1rc?) with sfs-3.4.

AFAIK, BK's K2.6.18.8 was compiled way later than the K2.6.18.1 used in the original 2-series puppies, in a woof attempt at pup218, and judging from the file name of the patched sources, there could be some patches omitted from this later version.

I have started looking into how to upgrade the kernel in 214X to K2.6.18.8, while ensuring all the original patches are preserved (comparing the patched sources of kernels used in 214/216 and BK's 2.6.18.8 with vanilla sources of 2.6.18.1 and 2.6.18. - might have a go at it in a week or two.

OTOH, if someone has a link to (or can provide) the complete kernel sources of K2.6.18.1 (of puppy 214 or 216), patches and all, I would be very much obliged .

Cheers /
MHHP

Hi MHHP,

I agree that's the right approach to achieve maximum compatibility with old hardware and keep the 214X kernel original essence.

I also tried to find the individual kernel patches by their name, but I had no luck. I could not find the loglevel, via, dpath or ksize patches.

I just found newer unionfs releases for 2.6.18.X but as I described in the upgrade process I have to test those versions, and hope the Unix socket problem is solved and track any other inconsistency.

Did you have any luck with the patches sources? How is the compare process going on?

Greetings,
clarf

[sinc]

Hey ttuuxxx, since the topic of how to boot 214x on a frugal install seems to appear over and over again maybe you can add MHHP's example GRUB to the first post where your download files are. Bc PSUBDIR doesn't work people who are used to using current versions are not sure how to boot. Just a thought to clear up some confusion that keeps happening.... Or else get psubdir to work..

#
title Puppy 214X
rootnoverify (hd0,4)
kernel /puppy_214XRC5P/vmlinuz root=/dev/ram0 PMEDIA=idehd PDEV1=hda5 PUPMODE=12 DEV1FS=ext2 SFSFILE=ext2,hda5,/puppy_214XRC5P/pup_214X.sfs ZDRV=ext2,hda5,/puppy_214XRC5P/zdrv_214X.sfs PUPSAVE=ext2,hda5,/puppy_214XRC5P/pup_save-214XRC5P.rfs
initrd /puppy_214XRC5P/initrd.gz
#

[MinHundHettePerro]

Hey ttuuxxx, since the topic of how to boot 214x on a frugal install seems to appear over and over again maybe you can add MHHP's example GRUB to the first post where your download files are. Bc PSUBDIR doesn't work people who are used to using current versions are not sure how to boot. Just a thought to clear up some confusion that keeps happening.... Or else get psubdir to work..

#
title Puppy 214X
rootnoverify (hd0,4)
kernel /puppy_214XRC5P/vmlinuz root=/dev/ram0 PMEDIA=idehd PDEV1=hda5 PUPMODE=12 DEV1FS=ext2 SFSFILE=ext2,hda5,/puppy_214XRC5P/pup_214X.sfs ZDRV=ext2,hda5,/puppy_214XRC5P/zdrv_214X.sfs PUPSAVE=ext2,hda5,/puppy_214XRC5P/pup_save-214XRC5P.rfs
initrd /puppy_214XRC5P/initrd.gz
#

Hello !
Perhaps even more instructive, are the following posts by vg1: post_1, post_2 and post_3.

(On a sidenote, in my quoted boot stanza above; my pupsave-file having the extension .rfs is not a typo (I am using a reiserfs-formatted pupsave, which is only implemented in my own initrd.gz), everybody else should use .2fs or .3fs.)

Cheers /
MHHP