(old)Puppy Linux Discussion Forum

rerwin wrote:

After the "dust settles" on what gets included, my plan is to start a new thread for "5.2.8.6" to support further contributions to it.

1 month of dust ..

Several kernels may need several new threads ..

Just a notice .

About the "repos.conf" file, playdayz has recommended that fix to me. It will be in the next set of uploads, along with an updated list of official lucid packages that includes the proprietary video drivers for k2.6.37 (3HD).

Playdayz has also pointed me to yet another kernel-3.x version of lupu to add to the set. Now we have essentially three-headed-dog versions for k2.6.37, k3.0.25 and k3.2.13! Would it make more sense to settle on one 3.x version? Is there any need to make that the same as for precise pup? Is there any need to keep any of the in-between versions?

Also, is the kernel-swap process so tricky that I could not do it myself? Or would one of you volunteer to create the best version that works?

Regarding the dust settling: I am still verifying that the libreoffice SFS implementation actually works. Still messing with java to be sure it is added correctly, without error messages.

musher0 wrote:Lucid Puppy has passed the test of time. The scripts and programs offered in Lucid Puppy, given the large user base and the careful edits over time of its various developers (including you!) Smile, have been well tested, and everything just works, without any surprises that would have you go "Eh?".

That is playdayz' and my goal for lupu. My fear about going too far with the 3.x kernels is that we may run into incompatibilities with other functions such as ALSA and udev versions and who-knows-what-else.

Sorry about forgetting the link to the download page (158):
http://www.murga-linux.com/puppy/viewto ... 108#726108
Richard

Just for informational purposes....... the k-3.2.13 version appears to be working well. If memory serves, that kernel was compiled by Pemasu and used in Saluki and Carolina.Already has the Quickpet fix too.

# report-video
VIDEO REPORT: Three-Headed_Dog, version 005

Chip description:
Intel Corporation 82865G Integrated Graphics Controller

Driver used by Xorg:


Video mode used by Xorg:
Resolution: Depth:

...the above also recorded in /tmp/report-video # free
total used free shared buffers
Mem: 2585748 540492 2045256 0 34144
Swap: 4198396 0 4198396
Total: 6784144 540492 6243652
#

Personally, I'm planning on sticking with the two original kernel versions...2.6.33.2 and 2.6.37.6....but I'll try to help a bit with testing.

The Puppy Package Manager in the lupu-5.2.8.6 seems missing the repoes,
puppy-common and puppy-noarch.

rerwin wrote:Now we have essentially three-headed-dog versions for k2.6.37, k3.0.25 and k3.2.13! Would it make more sense to settle on one 3.x version? Is there any need to make that the same as for precise pup? Is there any need to keep any of the in-between versions?

Both 3.0 and 3.2 kernels are "longterm" kernels. However, 3.0 support finishes this month, while 3.2 in 2016.
So the original (for "happy customers") and the latest 3.2 (3.2.50+) would make sense and keep maintenance (and hopefully any trouble) to the minimum possible.

Maybe in a year or so try 3.10-LTS

Made a DVD-RW using "lupusuper-5.2.8.6-20131012.iso"...
Modofied the isolinux.cfg file in the iso to include pmedia=ataflash...
Renamed the iso to "lupusuper-5.2.8.6-20131012-ataflash.iso" and made a new CD.
Both seem to be working just fine with this "new" 2012 desktop PC.
Wiped the 1st CD.

Now all I need is to find the time to tweak it to suit my likes.

Sylvander

Modofied the isolinux.cfg file in the iso
to include pmedia=ataflash...

Cool how does one do such?

Reporting success on all fronts after 12 hours of testing the new "sulu"
version. Works like a charm! It picked up my 5.2.8.6 lupusave without
raising an eyebrow, I just needed to change the beginning of the 2fs
filename from lupu to sulu.

Good work, rerwin!

Wow I've not paid attention. is there a 528-006 even.

I ahve to try that one too then

rerwind seems to have it for download here

http://puppylinuxstuff.meownplanet.net/ ... 131012.iso

I am not sure what one looses with a newer kernel, but there are so many AWESOME new Puppies out there, but they do not have the repo or number of pets.

Just the last 24 hours i tested

Simplicity 13.10
FatDog64 630rc1
AlphaOS 12.1

I think the strength of Lupu or is it Lucid, is in the hidden treasures in the forum, pets and SFS that are not in the repo or in the QuickPet.
These are goodies like=


Shareinternet (as custom as it gets)
Nwipe
LHMP
Tixati

Could it be that these and probably lots of others are left behind if one starts competing with other Puppy's that has newer stuff under the hood, but that are not allrounders like 5.2.8?

If I was to compare 5.2.8 with something on wheels, it would be this thing here that i used to have...

What i have been missing the most is to round up e'm lost pets in the forum and elsewhere and get them presented in a good way like QuickPet.

Look at Quickpet in Simplicity. It was surprisingly amounts of software there.

I think its a bit like of it will not run 5.2.8, you jump on to Slitaz for support for older hardware and even 486 compatibility.

In my view 5.2.8 should not join the Kernel race, but rather round up em lost pets there out in the wild.

I test Lupusuper now and report. Just need to reboot:-)

Tested lupusuper and it works great, discovering all of my 4 gig of ram:-)

So i guess this is a PAE version? Very cool.

Quickpet is not connecting
Packet manager does and i am udating it... *Update... Packet manager does download stuff like firefox 24, the same file that Quickpet does not.*

is there anything special that i should test or post?

The machine is a ASUS U36SD with i5 and 4 gig ram.

I shall test to install some pets and SFS anyhow.

UPDATE And they do install fine. Testing OpenOffice now as a SFS as Firefox 24 and Gpredict installed fine.

nooby wrote:Cool how does one do such?

See this.
Except...
These days I'm finding that the filemnt command fails to mount the ISO [held on an external HDD (USB connected)], so I'm now often forced to copy the isolinux.cfg file from the mounted CD ["partition file system"][by clicking on the CD icon on the desktop]...
Then modify it, and then follow the method given [using ISOMaster] to replace the ISO copy of isolinux.cfg with the new edited version.

Although I think I have seen mention of the "ataflash" business in many threads or periods, but never grasped the complete picture as to what is deficient and what is desired. Has it ever been resolved in a puppy version somewhere? I would like to help with solving the issues (whatever they are) if I can.

From the above postings I conclude that flash media are being used as substitute hard drives but are not being treated appropriately for flash media (the delayed writes). But I am confused about discussion of iso images. I think I have heard of the concept of booting from an ISO image, but that seems a different issue than the delayed writes to flash media. Could someone "spell it out" for me, so I can home in on a solution, if possible?

From the above postings, a simple/simplistic solution might be to offer ISO files with the isolinux.cfg file already set with "ataflash". But how should I describe how/when it should be used? Also, what is the problem with using the boot parameter, media=ataflash?

Or is there something needed for the installer to cause it to know when ataflash is appropriate. I hope this has been fixed somewhere. But I am willing to try for a fix of some sort, for lupu and maybe then for other puppies.
Richard

The only catch is that I downloaded Lupu Libre and Libre office wasn't on the download. I had to install the sfs

Thanks Sylvander!

1.

rerwin wrote:From the above postings I conclude that flash media are being used as substitute hard drives...

I hope you didn't get that idea from anything I said.
Actually, it's exactly the opposite.
I use the pmedia=ataflash setting in isolinux.cfg...
To make the Puppy treat the pupsave file on an internal HDD as though it is a pupsave on a Flash Drive.
[See item 4 here]
Hence:
a. The "Menu->System->Puppy Event Manager->Save Session->Save interval" can be set to zero [0], so that there is no autosaving during the session.
[As in item 1 here]
Then I can also...
b. Make some modifications so as to be given the choice at shutdown/reboot "to save or not to save".
[See item 2 here]
And so as to make "Don't save..." the default:
See this post.

2. By-the-way...
The creator of Lighthouse64 told me [in a post on his thread] that...
The next version of Lighthouse64...
Will include a simple command that can be entered during Startup...
To turn off auto-saving by default...
And this turn-off will then be permanent for that installation of Puppy.
At present there is a simple command to do this, but it lonly lasts for the following session; is not permanent.

Hello.

This may be of interest to some.

Upgrading the support files of a Puppy distro: a successful experiment

http://murga-linux.com/puppy/viewtopic. ... ost#731719

Bye for now.

musher0

rerwin?

I just read a post
http://murga-linux.com/puppy/viewtopic. ... ost#731472
mentioning that is the better way to launch icewm.

If lupu/sulu is launched with that command, the result is that fbpanel is launched also. (Please see attached pics.)

If the existing line 163 of .xinitrc is replaced with this one: fbpanel is not launched.

I hope this helps. Best regards.

musher0

I could not find a place to put this link that I found on the great service offered by NewsNow Linux section

But being a 5.2.8 fan, i hope this can be of use or interest for a renewed version concerning icons for the distro

Nitrux-OS-Pack with latest set if icons

Sorry if this is not directly 5.2.8.06 related, but I hope it can become:-)

ffconvert-1.4 adds new feature, ffinfo and mkplaylist, ROX Filer right-click options.
http://www.murga-linux.com/puppy/viewto ... &start=196