I run Puppy. Have for a couple years now.
It runs (poorly) on my 1999 Dell Latitude CPi. It runs amazingly well on my custom system that I'm typing this on (Aaeon GENE-QM77 motherboard with i3-3120M CPU and 4gb DDR3, 256gb SSD + 32gb CFast card, built into the underside of a Dell AT-101W keyboard with a little spatial assistance from the bottom half of a very dead Commodore Plus/4 -- I have pictures of the build if anyone is sufficiently bored/interested). There are a few weird thin clients I have -- most notably the Neoware CA19, which has problems with the framebuffer drivers in TahrPup 6.0.2 during boot (it freezes at the point where the viafb driver is supposed to kick in), and the Wyse C90LE (or anything else with a VIA VX855 or related chipset) which needs the latest OpenChrome from github because OpenChrome v.0.3.3 doesn't work on that hardware (it was broken; I was the original reporter of the bug and a part of how it got fixed) -- that have issues, but by and large it runs on anything between those two systems I mentioned. You will generally have issues with extremely ancient systems (5x86-class machines in particular -- stick to Lucid Puppy 5.25 or earlier, or use ClassicPup 2.14x), extremely fancy new systems (that brand new $5k gaming rig you just mortgaged your house for so that you can play Half Life 4-1/2 if it ever comes out), or extremely weird systems (*à la* my hobby of 'reeducating' thin clients into low-power desktop systems).
Also worth knowing. Puppy is more a family of distros than it is one single distro. We have right now two current official releases -- TahrPup 6.0.5CE, TahrPup64 6.0.5CE -- and a whole pile of older releases and community builds. XenialPup (in 32b and 64b flavors both) is in progress at the moment. One of the 'big ideas' of Puppy is 'rolling your own Pup should be easy' -- and it is. I'm no dev and I've done it. Can't support 'em -- so I stopped -- but it's not hard to make and release a Pup. (Terminology I use -- "Puppy" = official, "Puplet" = community-contributed build, "Pup" = generic term for either one. There is no *official* standard on that, but the terminology as described is adhered to somewhat loosely by the community at large.)
If you want to know almost exactly how many Pups there are, go here https://archive.org/details/puppylinux. That repository (at Archive[dot]org, no less!) is maintained by a Puppian (as we call ourselves) who goes by the handle *ally*. There are some very old Pups not in there, but by and large it's *mostly* complete.
The official Puppy forum is here http://murga-linux.com/puppy/index.php.
While Puppy is almost exclusively x86, there is one currently-maintained ARM port, called FatDogARM. (Anything ending in -Dog like that, is not technically Puppy but a highly related species... like a dog vs a fox.) My understanding is that it's a little challenging to set up and get running, but that, otherwise, it's fairly current and fairly functional -- we're not as evolved as say Debian or Ubuntu, you know... Puppy is like a "24 Hours of LeMons" car -- yes, LeM*o*ns not LeM*a*ns, look it up -- it's kind of clunky, and it's all sorts of ugly on the inside (and sometimes the outside as well) -- but it runs, and it's fun to drive, and it *will* get you there -- you'll be a bit bruised if you're not careful, but you'll be there nonetheless.
If anyone on the list about Puppy that the preceding Shakespearean-length soliloquy ( :P ) did not answer -- fire away, I can *probably* give a meaningful response.
Also -- sorry, Luke, for another off-topic lecture.
On Sat, Jul 2, 2016 at 11:58 PM, Alexander Ross < maillist_arm-netbook@aross.me> wrote:
oh i should mention that my knowledge of enlightenment is that, it specialed in running on low end computers = not much in the way of graphics yet still providing a shiny interface. the sort of hardware puppy (gnu/)linux runs on these days (laptops from the mid-late 2000s to current) for example
arm-netbook mailing list arm-netbook@lists.phcomp.co.uk http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook Send large attachments to arm-netbook@files.phcomp.co.uk