Puppy Linux Discussion Forum

[R-S-H]

[Gnuxo]

Oh...

What version of puppy will 3.0 be based on?

I found that my graphics card will only work with ati catalyst 10.10 and kernel 3.7 and AMD no longer support it.



Do you have any ways that I can continue to get the best out of my system?

Lazypuppy is currently my puppy of choice, and I run a 64 bit system.
It works better then most big 64 bit non-pae Operating systems.
...And that's Lazy Puppy 2.0.

[R-S-H]

[Gnuxo]

I guess if it's still based on the same lucid pup, then I don't have much to worry about.

Regardless though, it's still one of my favorite OSes.

[R-S-H]

Yeah, I don't want to make the whole work done on LazY Puppy again and again on new distros. And if I would have to change it later, I do try to make LazY Puppy features ready for use after installing in another distro.

The 3HD VSP Puppy is a first step - currently installing 8 PETs doing 7 manually steps and ready is the VSP Puppy ! But surely can be refined though.

However: LazY Puppy will be LazY Puppy based on Lucid 5.2.8-004.

But, PLEASE, let me know: are you using a save file or don't you?

RSH

[Gnuxo]

Do you think newer programs will ever work in Lazy?

[Gnuxo]

Can I ask for some help?

I'm not sure where to ask. I'm in Lazy Puppy and I am trying to compile the newest Qupzilla.

I loaded Pemasu's newest QT.dev.sfs

...I also loaded Devx.

But when I try Qmake I get this error.

[R-S-H]

[R-S-H]

Hi.

Here's just some information about progress in development of LazY Puppy 3 with adrv option added.

I'm running LazY Puppy 3 now for a few days several hours a day using the new adrv option (thanks to mavrothal) activated in LazY Puppy.

But, as always, I do use this in excess, because LazY Puppy is a SFS Puppy. And if this wouldn't be enough, I do use this on a slightly different way: I can control the adrv option from boot menu entries in menu.lst - so, I can boot LazY Puppy 3 without any adrv (yes, there are several), with all added or with just a small selection of the adrv files.

Ok, here is the current setup of the LazY Puppy adrv option

ADRVSFS = LP2_Applications.sfs
BDRVSFS = LP2_Backgrounds.sfs
CDRVSFS =
DDRVSFS = LP2_Data.sfs
EDRVSFS =
FDRVSFS = LP2_Fonts.sfs
GDRVSFS = LP2_Guides.sfs
HDRVSFS =
IDRVSFS =
JDRVSFS =
KDRVSFS =
LDRVSFS = LP2_Languages.sfs
MDRVSFS =
NDRVSFS =
ODRVSFS =
PDRVSFS = LP2_Programming.sfs
QDRVSFS =
RDRVSFS = LP2_RunScripts.sfs
SDRVSFS =
TDRVSFS =
UDRVSFS =
VDRVSFS =
WDRVSFS = LP2_WindowManagers.sfs
XDRVSFS = LP2_XorgHigh.sfs
YDRVSFS =

YES! They are all available and usable: from A to Y (but currently only the filled ones are tested and also currently running) ! ! !

In front of this but thought as an addition I have also invented the LazY Puppy Personal Data SFS (but mavrothal informed me that there's something similar used in Tiny Core, which I did not know at this time). The Personal Data SFS can be loaded at boot up (also a boot menu option) and saved at shut down (selectable in shutdown GUI). Files can easily added to or removed from the Personal Data SFS by right-click-action - everything is temporarily until it would be saved!!!

Ok, now something to see, to look at, to make big eyes!

LazY Puppy 3 default desktop, no extra drvsfs loaded (103 MB the SFS)


LazY Puppy 3 default desktop, all current available extra drvsfs loaded (FbPanel shows it)


LazY Puppy 3 BDRV = LP2_Backgrounds.sfs - Wallpapers from Openbox menu


LazY Puppy 3 FDRV = LP2_Fonts.sfs - 1092 TTF Fonts


LazY Puppy 3 RDRV = LP2_RunScripts.sfs - 339 RunScripts


LazY Puppy 3 Mount Points in /initrd and list of loaded SFS files in Openbox menu (in alphabetical order, can be directly unloaded from the menu entry)


LazY Puppy 3 Portable Linux and Windows (Wine) Programs stored on USB Flash Drive executable from Openbox menu


All Wallpapers in the images are switched via Openbox menu!

Ok, some more facts:

So, 25 extra drvsfs mount points plus the new Personal Data SFS is really a huge step forward for LazY Puppy (yes, a logical step as well) and after adding all needed code to init in initrd.gz and also sfs_load I did get in trouble...

...from over where in the hell should I take 25 different sfs files (also different from all my other sfs files (currently 344)), to do some tests on all of this - so, by now just the ones are filled in at above list are tested (but the code is checked twice). Almost speechless about having now such new options and possibilities I did decide to make one more huge step forward...

...backward...

...no, forward...

...no, backward-forward...

Yes, backward-forward!

Tomorrow I will kick LazY Puppy back to the real beginning of Puppy Linux and because of this will be a huge step backward, this will also be a huge step forward:

Tomorrow I will REMOVE ANY CODE FROM INIT and RC.SHUTDOWN (no, I'm not screaming, just want to make it absolutely clear) that is used to create and/or save a save file (in rc.shutdown) or (in init) able to load any save file ! ! !

LazY Puppy 3.0.0 will be then a VarioMenu-SFS-P.L.U.S.-no-save-file Puppy - preferred for the use from

- USB Flash drive
- USB HD drive
- internal IDE HD drive

I think that's all for now...

From now on each and every day is a good day to grab and maybe keep the stuff from LazY Puppy 2.0.2-005 - because of all the above...

Have fun with LazY Puppy...

RSH

[Gnuxo]

That all sounds interesting and scary at the same time.

So we won't be able to save anymore? How will we retain settings?
While it's true that when I load and unload firefox.sfs, I keep settings but that's only because the save file makes a record of the settings in /root

Without a save file, I won't have any saved settings for Firefox or other applications.

Without a save file, Lazy puppy almost doesn't seem like a puppy anymore.
*Maybe because I haven't been around since the beginning*

...And maybe I'm just so used to it. And I'm also worried about grub.

I have a few puppies added to grub manually, And if there is a large entry to get lazy 3 to load all the adrv files then I don't know if I'll just be able to do it manually anymore.

And I don't want any of the other puppies in grub to be effected.

Have you thought about solutions to problems like that in the development of this?

[R-S-H]

[Gnuxo]

I see.

...One thing I'm surprised about is that I've always thought that .sfs files were read only. For an .SFS to be an effective save medium, it would need to be written to.

Though I understand about the awkwardness of saving regularly. if I install something by accident or screw up, all those screw ups are saved.

I always wanted a way to choose when to save or not. It would have given me more control. In fact I brought that up in feature requests a while back and I was criticized for mentioning it.

People said that such an option wouldn't be user friendly for newbies.

I think it would be safe for newbies. It would make things idiot proof.

[R-S-H]

[Gnuxo]

Wow! That's interesting.

Though that means that after using 3.0 five or six times, there would five or six backup .sfs in the frugal directory.

Those would have to be cleared out manually before they start to clutter the partition outside the frugal install.

...Did I understand that correctly? Or would there only be one .bak as the new backup would overwrite the last?

I'd also like to know what effect the loading and unloading of the personal data .sfs has on performance. As you add more settings and programs, would the puppy slow down more then usual?


Currently I'm using the newest Lazy Puppy final build 05.

[R-S-H]