Using Puppy - my perspective
On another thread - @bert07 - wrote about his overall impression of Puppy Linux. He described a problem or two and suddenly the theme of that thread changed from "overall impression" to "let's help @Bert07". My intent, in writing this, is to describe the impressions of another Puppy Linux user - me, Cobaka. Perhaps I'm a 'typical' user of Puppy Linux; I'm certainly a non-technical person. If my experience is typical, perhaps the development gang may read this and understand the relative importance of the various functions offered by Puppy Linux.
I have used Puppy Linux exclusively for longer than I can remember - errrrr about 4 years now. I had some older laptops that were quite functional - in terms of hardware - functional but stuggled with Windows. My pocket struggled in sympathy. I installed Puppy Linux from a CD and after that I went on to install Puppy Linux onto thumb drives. Thumb-drives, plural. In a short time I found that not all Puppies were equal; after that I loaded ONE Puppy (uPupBB32) onto the hard drive and strange problems vanished. Moral #1. If you mix different versions of Puppy Linux on the same machine and don't manage the save-file properly - be aware that bad things can/will happen. Moral #2. Unusual implementations of any software (and especially an operating system) must be well documented - and especially the 'gotchas'.
Puppy Linux is not Windows. The brilliance behind the design of Windows comes with the work that has gone into removing 'gotchas' for the ignorant. As an example of this, in the Windows filing system a 'magic' process transparently makes file names case insensitive. MYfile == myfile (and so on). Or (another example) in the filing system: The naming convention used by Windows is simpler. I see C: or D: or H: Easy-peasy. The Linux directory organisation is a little more difficult to understand. Sketching a map on paper helps. I had little problem with this but a well educated friend still struggles to navigate around the directory tree.
Nothing is free. The eternally popular Windows has a LOT more source code than Linux. This amounts to more potential (and actual) bugs. Add to that a slower overall response when booting and running. I prefer Puppy Linux - but I had to spend a little time learning detail that Microsoft diligently hid. That said, I was delighted when Puppy Linux ran while Windows acted like a fly swimming in treacle. The moral: do the essential things only. Being 'clever' has a cost.
Installation: Now that I understand the process whereby Puppy Linux is installed - I find it more convenient to install than Windows. This comes, in part, because Microsoft had to protect it's investment, Puppy Linux doesn't do that. I have a directory where I keep one master Puppy Linux file. For me - it's uPupBB32. I have used this one file dozens of times - yes dozens - as the installation base. Even on this 64bit desktop I'm using uPupBB32. Yes, I rarely use more than one or two PCs at a time - but I just love the ease of installation. I understand what gParted does. I understand what GRUB2 does. Connecting to the internet is just soooo easy.
More on installation. For a newbie, installation is the most important thing. Initially I installed Puppy Linux using Windows. For any-one migrating from Windows to the Puppy some method of 'jumping over' is essential. The essential items (for me) were (1) the ability to down-load "puppy.iso" (2) Nero burning - that could burn a bootable CD from Windows (3) the ability to boot whatever-PC from the newly-burnt CD and (4) the ability to return to Windows without pain. After that I learnt how to burn (and boot) a thumb-drive. That was more difficult because I didn't understand the significance of detail in gParted and GRUB. At that time I used laptops with BIOS. Later, I had to learn about UEFI. The process of abandoning Windows and taking up Puppy must be simple and bug-free.
The thing I like most about the Puppy is that I (generally) understand where everything "lives" on any particular PC/laptop and this knowledge is most useful when I install "my" Puppy to some desktop/laptop I dragged in from the cow-paddock. Sometimes the hardware found in the cow-paddock is old - maybe 15 years old. Sometimes the clock is only 1.2GHz. Sometimes it has only 2GiB of RAM but Puppy seems to run this old 'stuff'.
$$ I try to remember to re-imburse who-ever developed uPupBB. [hello @peebee!] I try to do that every year - there is certainly a lot of work in packaging a complete Puppy. I might have 4 or 5 desktops running from the same download and I got this for a very reasonable annual 'donation'.
A bigger/better Puppy? @BarryK & @bigpup (and others) talk about developing Puppy further. Well - Puppy does everything I need - pretty well - at the moment. Why develop it further? Answer: Because no technology stands still; obsolescence is obscurity and oblivion. At the same time I believe "apps" are as least as important as the operating system. With limited resources should we work on the system or on "apps"?
Things I don't do: Never played a game on this desktop or on Puppy Linux. Not even Tetris. Certainly not multi-user, internet-based games. I'll bet others do!
My main uses: Office-suites: word-processing, text editing, spreadsheets. Browser-based activities, esp e-mail, viewing public transport schedules. I spend some hours a week looking at You-Tube - mainly history/science lectures. I spent some time learning how to use bash and the terminal. Windows has something similar, I believe, called "powershell". Powershell sounds impressive; "bash" or "sh" is just another Linux buzz-word, but the terminal is very useful. I use it daily - sometimes for an hour or so switching to (and from) Geany. Couldn't live without them. Started to lear "C". Got a small amount of most useful help from the forum. Sometimes older versions of Puppy Linux no longer have a net-compatible browser.
Things I want to do but haven't yet. Become sufficiently competent in "C" to compile/debug source code. This is a 'me' problem, not a Puppy problem. Use/draw in some small CD package. Have done this under DOS and in Windows after that (TinyCAD). Use TinyCAD to lay out time-lines for historical events. Again, this posting isn't a 'let's help Cobaka' thread. It's a general comment on PL.
I didn't understand the significance of *.sfs files. Down-loaded & used Firefox for some time. Then a friend wanted Firefox on her machine. Easy-peasy! I erased Foxfox from my PC. I had a plan. After erasing Firefox I would re-install it, writing a 'how-to-do-it' note as I did each step. Uh-oh! I didn't know something! I am living in the 1990s - where erasing a file means that the file is erased. Puppy Linux (sfs files) work differently! To this day I haven't re-installed Firefox. The moral: never second-guess how The Puppy works!
This brings me back to the topic of installation and re-installation. I spent a lot of time understanding a small number of technical points about installation. Formatting. Bootloading. Flags. UEFI. BMR. Partitioning. GRUB & GRUB2. After that I found installing Puppy Linux easy and convenient.
Hope the few who develop Puppy Linux find these notes useful.
Why don't you write your experience using PL?
Cobaka.