This thread is intended as the maintenance center for further support of Lucid Pup. The next few messages are reserved for particular subjects, specifically issues related to reinstallation with later versions of the ISO files and collection of links to component package updated since the latest upgrade date. I hope this thread can become a resource for users as well as a feedback thread. (The original Lucid Pup 5.2.8 thread was:
http://www.murga-linux.com/puppy/viewtopic.php?p=554253#554253)

The download site contains a set of ISO files of identical function, different only in their internal structure. All were created with the "remaster" tool. Of all these variants, the one that supports both dialup hardware and the (xz) compression method used in modern SFS files is lupusuper2 (or lupusuper2plus, with LibreOffice, or lupusuper2libre)

The ISO files will be updated together and will have the same date-tag in their names. The "libre" and "plus" files may be updated with later versions of LibreOffice but the date stamp will be unchanged because it relates only to the puppy version.

Note that Lucid Pup is not released in the same manner as other puppy projects. The version level is frozen at "5.2.8", so that all puppy-main files are named "lupu_528" and will not trigger the normal pupsave-update function. To manage the cases where a pet package has been installed and becomes part of a later upgrade of lupu, after replacement of the main files in a frugal installation and subsequent boot-up, a check is made for packages now included in the main (lupu_528) file. If a conflict is found, a (pop-up) recommendation is made to uninstall the conflicting package, so as to utilize the new version in lupu.

This effort is endorsed by the originator of Lucid Pup, playdayz, who has committed to maintain the QuickPet aspect of lucid support and advise me in maintaining the core of Lucid Pup. A big "thank you", playdayz!

mavrothal,
I have never gotten into the business of maintaining a distro, but feel comfortable doing remasters, which is how playdayz, as I understand, maintained lupu. I have no experience with bumping version numbers and whatever goes along with that, so simply continue playdayz' practice with the "528-00x" series. Consider this as 528-006.

I want to keep lupu going by adding only essential fixes that remove impediments to keeping lupu for basic long-term functions, for those already committed to using lupu because of its stability. It won't be able to keep up with the capabilities of the newer kernels and apps.

I will need to just freeze 5.2.8.6 fairly soon and use this thread for adding packages for patches and links to upgraded components. But I hope the final 5.2.8.6 will be solid enough that no critical fixes are needed.

In addition to keeping lupu pasted together, we can use this thread for improving the functionality of the lupusuper/sulu variants of lupu for various k3.x kernels. But that goes beyond my mission to maintain lupu as is. I will leave it to others to innovate with sulu, although I can help by consolidating the results of experimentation for general use.
Richard

I have no experience with bumping version numbers and whatever goes along with that, so simply continue playdayz' practice with the "528-00x" series. Consider this as 528-006.

Actually bumping version is _very_ simple and can be done manually.
All you need is to change the version number in DISTRO_SPECS and the corresponding names of the sfs files.
The only "tricky" thing I can think is that you also have to change the version number in the intird/DISTRO_SPECS. but is really simple:

I think there is even pets somewhere in the forum that types these 5 lines for you

I think between 5 rounds of playdayz' updates and 6-7 from you it deserves an updated version
The rational is that Luci is already 2-3 years in use and the save files probably have plenty of files that without a "proper" update may not allow some of the updated files in the SFS to work/showup since the sfs goes at the bottom of the layered file system.

Just my $0.02_________________Kids all over the world go around with an XO laptop. They deserve one puppy (or many) too

Some form of long term stable is welcome and basing it on probably one of the best puppy varients around thats popular with good reason is an excellent choice.

Please do keep the version number as a constant too... puppy has suffered version madness along with the rest of the software world recently and the subsequent confusion and almost religious fevour towards such is hardly constuctive.
There would not even be a need for distrospecs if we did not have several entirely different pups all with overlapping version numbers.

Take something that works well and update as needed.... the rate of new hardware seems to have slowed down and drivers can be built for the existing kernels(s) anyway and I find the Lucid software base to be new enough for current reasonable software.
A similar approach with older distros keeps them useful for years...I am still in lenny/slax6/puppy 4 land for day to day usage.

Yes a recent discussion http://murga-linux.com/puppy/viewtopic.php?t=88347 showed that Lucid and other puppy kernels limit the number of cores used ie the CONFIG_NR_CPUS= parameter.
Bit like the limit of loop devices...why...don't ask . The latter can be overwridden with a boot parameter so its possible the number of cores can be too.

The builtin sound card wasn't seen at all but when I plugged in the
usb soundcard it was and it works fine.

Please tell us more about your built-in sound card, particularly its hardware ID and whatever description you can find. While I am not eager to try to keep up with new hardware, the basic info can help to determine if there is an easy remedy for supporting it.

The builtin sound card wasn't seen at all but when I plugged in the
usb soundcard it was and it works fine.

Please tell us more about your built-in sound card, particularly its hardware ID and whatever description you can find. While I am not eager to try to keep up with new hardware, the basic info can help to determine if there is an easy remedy for supporting it.

RE the comment that Lucid is one of the most popular versions - why is this?

I tried both Lucid and Precise - mostly because I failed to realize that Precise was available initially. And I've thought about trying Racy and Slacko, but every time I do, I sort of think .. well, what's REALLY the difference? Because I saw little difference between Lucid and Precise, aside from the fact that Precise lacked some configuration options and ran "hotter" temp wise. (So I too am running Lucid atm!)

I personally value ease of use & setup, pleasing UI, and a high-spec browser. On this computer I do nearly everything in the browser, so I favor slim OS with little software.

I'm sure more knowlegable people than I can just compare the version descriptions, but I'd love even just two sentences on what makes one version of Puppy preferred over another ..