There's at least half a dozen small distros that make it easy for a regular user to both add and remove software. I'm honestly curious why the people who wish Puppy was more like TinyCore, AntiX, Slax, xPud, or Slitaz don't just switch.

Precisely. TinyCore is a cute idea, but once you install a few major apps, its footprint is almost as big as a basic Puppy.

And don't bother trying to use TInyCore as a live CD/live USB/rescue distro because it can't do anything useful until you download a bunch of extensions.

I've had a number of Windows repair people tell me that Puppy is their favourite rescue Linux.

There's at least half a dozen small distros that make it easy for a regular user to both add and remove software. I'm honestly curious why the people who wish Puppy was more like TinyCore, AntiX, Slax, xPud, or Slitaz don't just switch.

...Or that those who want Puppy to be as large, complete and powerful as Ubuntu, Debian, Redhat..., don't switch...

I really like that Puppy is quite complete, for all of the basics, without all the bloat that comes from "fringe" tools. And it is generally extensible, if someone really wants to install those tools (i.e. power users aren't limited, but at the same time newbies aren't overwhelmed).

As I've said before, the one main change I would request is that the live-boot CD always check the pupsave for errors, before loading, as corrupted pupsaves seem to be the bane of newbies.

While not a Linux newbie, I started using Puppy as a live-boot CD + pupsave combo -- nothing to install (pusave on the HDD). Every few days my pupsave would become seriously corrupted, requiring a rebuild. This seems to occur less frequently (or perhaps "almost never") when running the pupsave from a flash drive (different "sync" branch in the code). I found this chronic corruption quite irritating. I have since re-mastered the 4.3.1 CD to perform a fsck on boot and I no longer have corruption problems.

The power users who don't like that particular feature can easily turn it off (as they both know how to use the boot options, and how to remaster the CD...assuming that they haven't done a true Frugal or full-blown install -- which allows them to configure it in their menu.lst).

The newbies would not have to learn how to turn it on, since it would happen automagically.

While not a Linux newbie, I started using Puppy as a live-boot CD + pupsave combo -- nothing to install (pusave on the HDD). Every few days my pupsave would become seriously corrupted, requiring a rebuild. This seems to occur less frequently (or perhaps "almost never") when running the pupsave from a flash drive (different "sync" branch in the code). I found this chronic corruption quite irritating. I have since re-mastered the 4.3.1 CD to perform a fsck on boot and I no longer have corruption problems.

While not a Linux newbie, I started using Puppy as a live-boot CD + pupsave combo -- nothing to install (pusave on the HDD). Every few days my pupsave would become seriously corrupted, requiring a rebuild. This seems to occur less frequently (or perhaps "almost never") when running the pupsave from a flash drive (different "sync" branch in the code). I found this chronic corruption quite irritating. I have since re-mastered the 4.3.1 CD to perform a fsck on boot and I no longer have corruption problems.

Well ideally, we'd put that in woof, or at least add it to all the puplets so nobody needs to deal with it anymore. Pair that with Ext3/4 save files, and fscks after an unclean shutdown (Puppy couldn't do this before because all shutdowns were technically unclean), and it should be relatively bullet proof.

Well ideally, we'd put that in woof, or at least add it to all the puplets so nobody needs to deal with it anymore. Pair that with Ext3/4 save files, and fscks after an unclean shutdown (Puppy couldn't do this before because all shutdowns were technically unclean), and it should be relatively bullet proof.

This would be perfect.

Linux has a lot of peculiar things, and that resulting steep learning curve is much of what discourages newbies (Puppy, of course, conceals most of those under the GUI, so it's not nearly so alien).

BTW, is ext4 really that good?

I recall the earlier days of ext3, a friend was regularly getting severe filesystem corruption -- as it turns out, it has to do with the feature/belief that you need not rescan a drive after a crash, because it has a journalling system. When I searched for the issue, I discovered that the gurus recommended fscking the system as soon as feasible (i.e. bring up the system, get any files you needed right now, then umount and fsck).

For this reason, I've stayed with ext2 for the time being (while I may need to scan after a crash, the filesystem will be repaired and fully functional before I mount it). And with Puppy, the OS partition is so small that it's not painful to perform fsck on every boot.

While not a Linux newbie, I started using Puppy as a live-boot CD + pupsave combo -- nothing to install (pusave on the HDD). Every few days my pupsave would become seriously corrupted, requiring a rebuild. This seems to occur less frequently (or perhaps "almost never") when running the pupsave from a flash drive (different "sync" branch in the code). I found this chronic corruption quite irritating. I have since re-mastered the 4.3.1 CD to perform a fsck on boot and I no longer have corruption problems.

And my (automagic) startup fsck is vastly faster, since the shutdown was clean (I would still, for newbies sake, implement an auto-fsck on startup if the devs can be convinced -- if the shutdown was clean, it doesn't take very long -- if the shutdown was not clean, you should run even though it takes more time).

I have installed Lucidy Puppy 5.1 in hard disk. I would like to know whether I can upgrade to 6.00 by auto update or any separate pet package, if any. Or I have to install Puppy 6.00 from ISO file. ( after burning to CD).

Who said 5.1 will be Puppy 6.0?I think it should be 5.1 to 5.9.
Usually a next puppy version is a complete new base, plus we have Quirky,Wary, the new dpup, plus on going discussions about building 6.0 from scratch, I for one am 100% against a Ubuntu release taking 2 version numbers in a row. Plus I never read at Barry's blog that 5.1 will be 6. If you aks me its kind of arrogant to think that one release will continue without debate, without looking around at other projects. Really now!
ttuuxxx_________________http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games

[quote="ttuuxxx"]Who said 5.1 will be Puppy 6.0?I think it should be 5.1 to 5.9.[ quote]

Nobody.The plans for Lucid Puppy are the upcoming 5.2 release.Playdayz and 01micko are working on 5.12 as I'm typing.
AFAIK, there are no decisions about what will be Puppy 6 and when something will be released.
In the other thread about a possible Puppy 6 there is basically no agreement so we'll just have to see what happens.

Who said 5.1 will be Puppy 6.0?I think it should be 5.1 to 5.9.[ quote]

Nobody.The plans for Lucid Puppy are the upcoming 5.2 release.Playdayz and 01micko are working on 5.12 as I'm typing.
AFAIK, there are no decisions about what will be Puppy 6 and when something will be released.
In the other thread about a possible Puppy 6 there is basically no agreement so we'll just have to see what happens.

Hi James puppy 5 only was released a couple of months ago, usually a puppy series number last around 1yr, so there is tons of times for puppy 5 to grow and mature, I'm not saying that puppy 6 should be in developement stage yet, not at all, First we need to talk about it and then we need someone to build it etc, but what gets me is the title of this thread "Puppy 5.1 to 6" 5 series has nothing to do with 6 series, like 2 series had nothing to with 3 series and 4 series had nothing to do with 3 and 5 series, usually its a drastic base change, so to keep with puppy tradition the 6 series is a new puppy that has nothing to do with 5 or 7 version, hence puppy 6 should not be in the threads title.
ttuuxxx_________________http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games

Other good reasons - it's small and fast, like Puppy. And it works better for reducing writes to flash drives, which is a major market for Puppy.

I'd like to add another vote to do an fsck on every boot, now that the pupsaves seem to be closed clean (or at least we have that capability). And we need to get it right on encrypted pupsaves; I think "pfix=fsck" still doesn't work with them, despite this being a very simple thing to fix. It's an old problem. <sigh>

Other good reasons - it's small and fast, like Puppy. And it works better for reducing writes to flash drives, which is a major market for Puppy.

An excellent point, Paul! I hadn't thought about the flash drive write issue...

Quote:

I'd like to add another vote to do an fsck on every boot, now that the pupsaves seem to be closed clean (or at least we have that capability). And we need to get it right on encrypted pupsaves; I think "pfix=fsck" still doesn't work with them, despite this being a very simple thing to fix. It's an old problem. <sigh>

Yes, the ability for "puppy pfix=fsck" to automatically scan and repair encrypted volumes would be GREAT. That is the only real reason I haven't changed over to at least a lightly encrypted volume (though I suspect that "heavy" is nearly the same speed, on most near-modern machines).

BTW, it occurs to me that having a brief script of load instructions, which Puppy checks for on booting, could be useful. If it's not there, it continues as normal.

Suppose we set the default to "fsck" every boot, but you don't like it, you edit the "pupstart.ini" file (it doesn't exist...yet), and enter "nofsck" to disable this auto-feature. Want to make a backup of your pupsave on every boot? Put the instruction to the pupstart, and it is done before booting. Etc, etc, etc...

This script could allow substantial user customization, without remastering the CD -- one could continue booting from CD, using a pupsave, while tuning their system operation to their favorite settings (no grub, no remastering...).

You could consider putting it inside the pupsave, but then the pupsave would have to be loaded, before you could read these options (making fsck potentially impossible). However, I suppose it could mount, read, umount and run..._________________Add swapfileWellMinded Search

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum