2.16CE_Home_Alpha4 iso is now uploaded to puppylinux.ca

[ttuuxxx]

Why not take 3.01 and do the final fixes that are posted on here and basically make the 3.02 release, I have found 3.01 extremely stable, I haven't had any problems with it and lets not forget the Slackware aspect which is just incredible,

Precisely. Every consolidation in the 2.15CE version came from user contributions. Bug fixes, updated features, the works. Barry did NOT supply anything for that. He was heavily involved in producing 2.16a at the time. In fact he was pressing us to release quickly so he could get the alpha out early.


Puppy 1.09CE for i486 and P1
Puppy 2.15CE for PII
Puppy 3.02CE for PIII & Pentium M
Puppy 4.0xCE for PIV & Duo Core

Can we see the lineage that I'm talking about here?

Cheers

I agree 150% with WhoDo, I also think that we should revisit the older CE editions and update them accordantly with certain hardware fixes for series of computers that they relate too if need be. "Only the best for Puppy users" I say!.
ttuuxxx

[Lobster]

Puppy 1.09CE - Phoenix 1.10CE starting point
http://puppylinux.org/wikka/Puppy110

2.15 CE - Viz
http://puppylinux.org/wikka/CommunityEdition

Latest Community Edition
http://puppylinux.org/wikka/TalkingStick

[WhoDo]

Puppy charter? Puh-leez!

Suffering short term memory loss, AJ?

The Puppy "charter" or "Project Statement" can be found right here:
http://www.puppylinux.com/development/p ... tement.htm

[WhoDo]

I also think that we should revisit the older CE editions and update them accordantly with certain hardware fixes for series of computers that they relate too if need be. "Only the best for Puppy users" I say!.

In which case a revised 2.15CE based on 2.14R would become 2.15CER (is that pronounced "cur"?)

Hey, I don't have a problem with updating 2.15CE with the revisited 2.14R base. Good job, I'd say. That would build on the already solid reputation of the 2.15CE release by making it better and better. Woot!

Now, back to the issue of Talking Stick, which is still listed on the wiki as a "Series 3 Community Edition", as IMHO it should be. In keeping with Barry's practice it would be 3.02CE because it would be a consolidation and bugfix release, whereas odd numbers are for new features. Barry has given us a system so why won't/can't we follow it?

[Lobster]

I am quite promiscuous when it comes to ISO's


There is another way . . .
I am in Puppy 4 (Dingo Alpha 6)
we know that Puppy 4 will arrive eventually
Talking Stick can be a bug fixed Puppy 4


The important thing is to start putting together
what we have and can

Two years ago Barry mentioned that he had other projects
he was interested in working on, in about two years . . .
That is about now . . .

At this point the community will have to take
more of the decisions.

. . . and now back to the records . . .

[tronkel]

Lobster wrote:

Talking Stick can be a bug fixed Puppy 4

I think he is right.

That seems to be the way it's going. In the not too distant future, Puppy versions 2 as well as 3 (both base and community) will be history.

The 3 series may hand around for a bit longer because of its Slackware compatibility.

A decision needs to be made real soon once and for all, as to where all the development effort is heading. IMHO that should be in the direction of Puppy 4. All the arguments about the previous versions will simply evaporate in the context of events soon to overtake us. A Talking Stick CE version of Puppy 4 is where it's really at. The rest are probably irrelevant now. The confusion will soon give way to concentrated effort by the community.

Barry made the best decision in concentrating on Dingo.

[Sit Heel Speak]

Maybe call it "2.16 Professional Edition-EN" since it has the same partition-icons-across-the-desktop-bottom as Hacao's "2.16 Professional Edition (Vietnamese)" ...however...tronkel's 2.16CE shows a new image/icon for swap partition after each boot; on this system there is only one swap partition, but...

http://i27.tinypic.com/30s7hjd.png

[tronkel]

There seems to be hardware and other issues that affect how HotPup works.

On my system here for example, I have a usb hard drive that HotPup cannot mount although the icon is displayed. Mounts OK with Pmount though, whereupon Hotpup shows it as mounted.

I have never experienced multiple swap mounts in 2.16CE with HotPup. It looks as if the PuppyPin ROX configuration file in /root/Choices/Rox-Filer is not being refreshed with each new boot sequence for some reason. Therefore you could, as a temporary work-around, manually delete the lines that display the swap-partition icon. But, why HotPup is mounting a swap-partition in the first place I couldn't say. The HotPup scripts that Dougal wrote are complex and would perhaps need to be amended to get more hardware working with HotPup. You can comment out or delete the HotPup daemon in your /root/.xinitrc if you want to temporarily dispense with HotPup until a fix is found for this.

I am very keen to get HotPup to work in Chihuahua, so thiis with any luck, could provide a better insight into this problem.

I also cannot get HotPup to work at all in either 3.01Retro (older Kernel 2.6.18.1) or in the version with the later kernel - so something to do with the library changes necessary for Slackware compatibility that were made to Puppy 3 series could be a factor here.