Perceptions of Peter Piper's Puppy's Pickled Printers (very long posts)

[PuppyandCo]

[edited 09/01/2021 - this started off as a long post about user perceptions of Puppy, but turned into an even longer post about printer support. Since posting it I have moved the text around so it follows some logical order, and listed a summary of 8 problems that might affect other users... a few have fixes that could have been more obvious from google or the forum search.]

Hello all,

I've been using Puppy Linux since there was only one flavour of it, so 10-12 years and thought I would say thanks for it and give some (extremely long) feedback on it.

Currently I'm using Puppy USBs very successfully/enjoyably for:-
- work USB that I take into the office instead of using their IT stuff (Slacko 6.0)
- Samba fileserver (forget which)
- bedside laptop for writing (Bionic64)
- CCTV box (Bionic something)

The main PCs in the house are a Windows 7 one in the old "home desktop PC" role, and a Ubuntu Studio (xfce) media centre + gaming.
I personally have come to prefer single-function PCs over one big PC that does everything, and puppy is best for this.

I don't have any technical qualifications but I'm comfortable with terminal commands, and will happily take on challenges like setting up simple scripts, or compiling software. Some stuff takes me a long time, and much of this post is about user problems the user doesn't understand, but hopefully it won't be complete nonsense. Seeing what people find confusing might be useful (I'm not posting this because I need any help or advice with anything btw, my puppies all work as I need them to and I'm very happy overall)

The massive attractions of puppy for me are that:-

A: user=root (The user is God. If God has to enter God's password every time they copy and paste a command from the internet, and very frequently ends up without permissions to save God's display settings... that's a bug. And about security, if God can't access *your* online banking (to give you money)... that's also a bug!)

B: everything is in RAM. I started off using puppy on older PCs but on newer PCs I find it's more responsive than Windows or Ubuntu. I can't say if that's due to everything being in RAM, but I guess Windows loads what it thinks you need into RAM, and fetches what you in fact want from off the HDD. Puppy already fetched everything, that seems like better service to the user.

C: the networking sets up really easily. I have relatively little know-how compared to the complexity of my home network so this is a huge plus.

To auto-mount a drive on ubuntu I have to work out a config line like this by trial and error:-
#//192.168.1.xxx/ONE /mnt/Disk-I cifs users,exec,dev,suid,rw,credentials=/.smbcredentials,iocharset=utf8,sec=ntlm 0 0
(and god help us if the permissions on .smbcredentials aren't set)
On puppy I just run pnethood and drag a folder onto the desktop

The Samba fileserver was as simple as plugging an external hdd dock into a micro-PC, and pressing "Samba On"... it beats the hell out of a home NAS.I can plug in any internal HDD, tell Puppy's Samba interface to call it "ONE", and all the other PCs in the house can see it. It would be nice if it wasn't limited to three drives but three is fine

Between Frisbee and Network Wizard I can report 100% success connecting to other people's networks. Some of the other options in the Network Connection Wizard (like dial-up and Simple Network Setup) feel redundant to me.

D: with Firefox, LibreOffice, and Qoppa pdfstudio (commercial/paid-for) puppy can do almost anything I would need Windows for. I have a windows machine now because of janky applications like MS Teams that clients expect you to have, or in case I particularly want to play a game that only works on windows.

E: the hardware support is incredible. Touchpads and wifi cards on obscure Chinese-made laptops work first time off the kernel. No display problems ever. I haven't yet had cause to install proprietary Nvidia drivers and run projectors and graphics tablets, and higher-spec games on puppy linux like I do with Ubuntu Studio, but I've got Steam and GoG running nicely for recent indie titles.

[PuppyandCo]

=====

1. Choosing a puppy
My perception is that in 2008 or whenever I started there was one flavour, then there was a confusing proliferation of different sorts of puppy in 2013 (when I next looked because I began using slacko at work), and now there are a few survivors-of-the-fittest.

As a user I can't tell the difference between any of them, and I don't remember what puppies I've installed.

I think that is a great virtue of puppy linux, e.g. compared with Firefox where they constantly pull the rug out from under the users for the sake of it.

I would find it useful on the main puppy page where it lists the different flavours to have a bit more of a steer as to why I'd want each one: I understand the basic logic like Raspbian is for Raspberry Pi and slacko works with slackware (but with slacko I only chose it because it recognized my printer, and find most debian apps run on it anyway or people have turned them into pup files). I chose Bionic most recently because it said it supported UEFI (but my laptop BIOS can't seem to boot it that way and has to be set to Legacy Boot, so again it's arbitrary what puppy I've ended up with and to me that doesn't matter). I can't see from the homepage and don't understand things like why someone would want Fossapup vs. Xenialpup.

==

2. Installing the puppy
My perception (sorry to say this) is that puppy linux is hideously difficult to install, but incredibly robust once it's done. My slacko work USB has been continuous since 2013. I'm conscious my experience isn't a fair test: I find windows and ubuntu tend to get glitchier as time goes on and the more software has been installed... with ubuntu in particular always ending in some library/repository mismatch breaking the entire system.

Puppy linux can take me a WHOLE DAY to install though and I'd rather clone a USB from 2014 than risk installing a more recent version.
It takes 10 minutes to download, 10 minutes to burn the Live USB, 10 minutes to run the install tool... multiplied by like 10 attempts.

My user case for Puppy is to unchain the OS from the PC... to run everything off the USB, so I can carry it round and plug it into any computer, and use all my apps, logins, and settings. I like to have a 128Gb USB key, boot from it, and then keep my user files inside a 100Gb NTFS-formatted veracrypt container. I don't want savefiles or anything else putting on the local HDDs. I don't really like the savefiles concept (despite having read all the advantages and for reasons I'll go into), but the "full install to USB" I've never been able to do, so I go along with frugal installs as recommended. A great thing about running an OS from USB is that you can easily clone a USB key and it will work.

I've used Universal USB installer from Windows, and unetbootin from Ubuntu... I haven't tried Rufus or Yumi. I personally took a long time to work out that these tools set up a "Live USB" on FAT32 and then the "Live USB" next has to be used to install puppy to an ext4/3/2 partition on a second USB stick. Creating a Live USB feels like an annoying, confusing, and very time-consuming extra stage when I just want to install puppy on a USB.

Making the USB keys bootable is often a nightmare for me, as the GUI application offers defaults that won't boot (despite the LiveUSB booting fine) or calls GParted and lets me choose from even more combinations that won't work. I'd like it much more if full/frugal installs were there as options INSIDE the third-party USB installers (I feel they shouldn't assume the USB is to be used in place of an install CD with the contents eventually destined to go onto a HDD). I also feel the whole concept of Live CDs is slightly apologetic, like there would be windows there in the first place.

I find it weird that Live USBs often won't install over themselves once puppy is loaded into RAM... and that "Universal USB Installer" doesn't have a linux version and its windows version can't create ext 4/3/2 partitions... Fat32 and some of the other formats with drawbacks seem like they could be in an "advanced" menu.

I've sometimes found it worked better to copy boot files (sorry not sure of the terms) like vmlinuz from another usb key I had got working, than to generate them during install.

Overall, my user case is simple and to achieve it feels like balancing a complicated tower of BIOS>Grub>GParted>Install Tool>LiveUSB Installer

The tips presented inside the "Install" Tool could be better. Some of the either/or choices the user has to make depend on arcane or puppy-specific concepts. On my one currently in Bionic64 v8 the first choice is between:-

Universal Installer (required for full install)
OR
Bootflash USB Installer (install to flash drive - destructive method)

tbf there is a link to the "Installation Introduction Homepage", but I just want to install an OS, without learning arcane concepts first

I always arrive at this menu thinking I want to do a full install to a USB, but the one I need to choose is Bootflash USB Installer.

==

3. Savefiles and Frugal
The only major limitation I see there to be in Puppy is that when an application has a memory leak, through no fault of puppy's, puppy tends to let it carry on consuming more and more of the PC's resources until it's no longer possible to right-click that application and Kill it.

The Kill command itself works (with a beautiful perfection and efficiency that Windows' ctrl+alt+del altogether lacks), but too often you don't get the chance to actually send it to the application: puppy is quite happy, the network access light is flashing, but 99.999% of the CPU or memory are servicing an error in Libreoffice or Firefox. The mouse pointing starts updating every second... every other second... every ten seconds... and so on forever. The power switch can be good for getting out of this into an orderly shutdown, but I find it's about 50/50 whether it can. This leads to applications forcing hard resets even though they haven't actually crashed the OS.

Hard resets are A Bad Thing when your computer is a USB key, and A Very Bad Thing when all your user data is inside an encryption container on a USB key. What I would find invaluable is an emergency key combination (or maybe the power button) that pushes through phases: (1) close every application except for stuff like X and JWM (2) same as 1 but bloody well kills them if necessary; (3) same as 2 and forces the PC into an orderly shutdown. pprocess can do anything the windows ctrl+alt+del task manager can do - this would be for situations where you can't open pprocess anymore

Another problem (I find) with savefiles for my USBs is that sometimes if you swap them from PC to PC a few times, puppy will fail to boot because it can't find the .sfs and savefile... until you remove the USB key and re-insert it into the "right" USB port. There might be some other cause, but this *feels* to me as if puppy looks for the .sfs and savefile based on the device number (sdb1 sdb0) when for my user case it should be using the UUID. FIXED 08/01/2021 (note below)

The savefiles themselves always still work after hard resets, but installed software or settings changes since the last save vanish which I guess is to be expected.

To me, even after 10 years, the relationship between puppy's sfs's, its savefiles, its "personal storage", and the storage partition on the USB might as well be voodoo. I don't know which parts of the filesystem I can save stuff to without it vanishing in the (exceptional) cases of a hard reset or the personal storage running out... so I end up only saving files to the encryption container.

I know it operates rationally, it's just that I've read the explanations dozens of times without it sinking in. I think it was along the lines that everything in puppy's / directory is really inside the savefile... which only exists in the RAM until it's "saved".

The Veracrypt container is good because unlike the encrypted savefile it can be opened off the USB without booting into puppy first.

I suppose the original/primary/intended puppy user case might have been to run everything in RAM whilst using the HDD for storage (notwithstanding it probably also had a windows install on it), and that the apps that react badly to these hard resets are ones like FF/TB/JWM which perhaps have made assumptions like "profiles are on a hdd and not a savefile in RAM, so they can be extremely large". I want to divorce from the HDD as well though: ideally I would only have one HDD in the house (the one plugged into the fileserver).

Ideally ideally my puppy fileserver would be a webserver as well and I could plug my puppy USB into any PC in the world as a client and listen to my mp3 collection at home on it. Not like a thin client... my data is universal across my network and the terminals I use to interact with it are specialised to different roles whilst being independent of hardware. For Steam games in the dining room, find the Steam Gaming puppy image on the fileserver, and burn it to a USB.

FIXED - set savefile location based on UUID of a USB Key
This is possible by editing menu.lst (or creating this file using grub4dos) and it is explained here
http://puppylinux.info/topic/about-your ... s-uuid-etc

but it's so important it should also be explained here imo:-
http://wikka.puppylinux.com/BootParametersPuppy

It took hours to find this kind person's explanation - and the time this problem has wasted me over the last few years has been horrific, the first time it happened before I worked out that it (sometimes) matters which usb port the usbkey is in I drove across town thinking I had lost all my files.

[PuppyandCo]

==

4. JWM
Related to the above, JWM feels like it has a lot of file handles. When Puppy has to be hard reset, I find most everything recovers from it well. The encryption container on Veracrypt sometimes locks itself to Read Only until I repair its filesystem in Windows, but even after having this happen dozens of times I haven't had any actual data loss in 6+ years. (I should say I am pretty conscientious about storage and backups, I don't keep user files on my puppy USBs apart from work in progress). The one thing that always seems to get corrupted is JWM, which causes various parts of the panel, or sometimes all of it, to stop working. This is normally recoverable by reinstalling JWM, but on the USBs I have been using longer there are some minor things like broken icons.

Also about the desktop, JWM treats the desktop as a place to put .desktop launchers. This is philosophically superior to it being a place I can put files I'm working on or have just downloaded, except that I hate it. On my desktop, I have a .desktop launcher to a directory in the encryption container called... "desktop", where I put files. What would be good is if there was an option for the desktop to automatically create .desktop launchers for those files, as then it could offer a pure user interface wihtout telling users how to use.

==

5. Software that's unavailable (afaik)

I find that software either works perfectly on puppy or doesn't work at all. I resist installing new applications in case it forces a hard reset, but once something is installed it will carry on working for years of daily use with fewer glitches. Firefox and LibreOffice I mentioned have some specific problems to do with opening malformed content in them.

Some types of applications I've had trouble installing or substituting are:-
- "collaboration" apps (like MS Teams/Slack/Zoom) (Fixed:- for Teams https://github.com/IsmaelMartinez/teams ... x/releases and for Zoom http://murga-linux.com/puppy/viewtopic.php?t=118289 )
- "remote access" apps (like Teamviewer)
- "webdrives" (like Dropbox/Google Drive)... bearing in mind though I don't want to sync+backup, I want to mount the webdrive.

These things have in common that they are still perceived as monetizable and linux is seen to be is too small a "market". But where they even have Linux clients they are often a bit sensitive and won't run on Puppy.

==

6. Tweaks I have to make after each install

pprocess - I find easier than lxtask
lxterminal - I find easier than rxvt
xfreerdp - tiny but vital for work
hplip - legacy printer drivers
engrampa - needed to edit .xpi extensions to work on the old versions of firefox that puppy always uses
screenshot - default is set to mspaint when TAS is better and hotkey has to be taken off up arrow
fonts - arial and times new roman (appreciate there might still be license issues)
FF/TB profile folders and Wine C drive - moving these outside the savefile is so important that it should come up as an alert
Changing grub time limits down from 15 seconds (1-2 is fine)
Making an icons directory in an easy-to-find place
Setting up keyboard shortcuts + scripts to control volume and monitor brightness
Script in root/startup/ to create mountpoint: mkdir /mnt/vol2/
Command to mount LAN hdd: mount -t cifs -o username=XXXX //192.168.1.XXX/vol2 /mnt/vol2/
Add line to fstab to automount LAN hdd
Script to mount encryption container at boot (the reason for encrypting is in case the USB key is lost, not to protect from puppy's user)
[I find puppy always crashes if commands like the above one that expect a password are made into executable scripts... I guess there is a different syntax in puppy from Ubuntu, but it should give an error rather than crashing - fixed - this must be done by setting up etc/fstab and .smbcredentials (like in the guides for Ubuntu) and then putting mount -a into startup. This is better than what I wanted, but it's still strange that running the command in terminal works but running it as a script crashes the PC...]

===

7. Shutting down doesn't switch off the power at the end (ACPI=force?)

8. The PPM supplied version of Flatpak (v.1.0.9) doesn't work well because of a default setting min.required.space=3%. In my case this prevents any flatpaks from installing if the free space falls below 500Mb but it's looking at the Puppy's home folder. More recent versions of flatpak removed this setting.

9. Copying a puppy:

2-day nightmare to copy a puppy.

Normally I do this by cloning the USB in Windows, but that doesn't work when the master_USB (128Gb) is larger than the new_USB (32Gb).

"Remaster" produces an 8Gb .sfs (probably duplicating the savefile into it).
"Install" automatically formats the new USB to FAT32.

The only way I could eventually find to do it was to go back to the original Live-CD I installed my puppy from, run a destructive-install to a third USB key ("new_USB") with the Grub4dos option to a ext4 partition... then go onto my puppy ("master_USB"), delete all the files from the new_USB that was just installed, and replace them by copying across all the files from the master_USB.

I wonder if frugal-to-USB puppies would be easier to install with just a GParted command with some options to format the USB key to be bootable, and then you manually download ~234Mb of files onto it. Defaulting to FAT32 without asking the user is a bad default behaviour because it prevents savefiles or encryption containers larger than 4Gb.

===

??. Future ideas

(i) If I could mount a webdrive in puppy, even a small one, I could avoid carrying an encryption container around everywhere
(ii) If BIOSes could boot not just from USB or from LAN, but from internet, I wouldn't need to carry a USB key at all
(iii) Commercial portal-based internet services will hopefully die off and be replaced with self-service (e.g. serving my text from the localhost without FB Messenger, my webcam without Teams, P2P webspiders+locally-hosted search engine wihtout Google). If so, puppy will prosper mightily.

[rockedge]

If I could mount a webdrive in puppy

I do all the time with an ownCloud server I run. The sync app works well on my Puppy's

[Clarity]

Hello @PuppyandCo

In reverse order #7. I have used my Google Account (PUP utilities available) and Dropbox (both available in FATDOG.

Also, early on, you mentioned you have various PCs scattered about. Thus Puppy come with SAMBA and the mount command of shares over your LAN should give both access as well as NAS options you can gain thru your home's router or other PCs. This affords you several electable options for storage needs beyond your local PUP PC via both your LAN, Web, and Remote Desktop solutions..

More on the other topics later. Hope this helps

[PuppyandCo]

Bionic64 v8.0

Zoom - the version of Zoom available via Quickpet is no longer supported and says it has to be updated. But the Ubuntu version doesn't display properly (application opens but window is entirely black. buttons work as normal and bring up meetings etc, but can't see anything) (Fixed:- remove the .pets from PPM and install the .sfs of Zoom version 5.1 from the forum post at http://murga-linux.com/puppy/viewtopic.php?t=118289. )

Also:- "log in via Google" allows a Google account to be connected, but the button calls the browser that then can't call the app

Google Drive - the version of Google drive available via Quickpet can't connect to a Google Account, giving the error:
"Couldn't sign you in. This browser or app may not be secure. Learn more. Try using a different browser. If you’re already using a supported browser, you can refresh your screen and try again to sign in."

====

This is another perception of Puppy generally:- due to the appearance of strong Ubuntu compatibility, people get stuff working once and then it doesn't anymore. I haven't tried dropbox as I know it doesn't do what I need.

It seems to me that rather than supporting web services, it's that Puppy can be made to support web services that support other flavours of linux. But it's dependent on i) the provider maintaining itself considerately e.g. with legacy support to old versions of clients and old versions of browsers ii) volunteers in the community updating Puppy versions of clients every time a provider changes something. Very few commercial providers maintain Puppy .pet packages, I've only seen this to occur one time.

==

PRINTERS
Installing a HP laserjet printer (network printer over Samba) that I know works on puppy, and takes 30 minutes to set up on Ubuntu on Puppy.... has taken... 4 days.

problems are listed below and described in more detail in the other posts...

[PuppyandCo]

LIST OF 8 PROBLEMS INSTALLING A PRINTER

1 - The "printer wizard" GUI in the menu literally just loads an html page with general help (about CUPS, missing the installation of proprietary drivers beforehand)
2 - the Puppy Package Manager could list the installed packages more usefully (e.g. options to list in date order)
3 - libnetsnmp-devel library requested by the hplip installer (when the network drivers option is selected) isn't available in PPM and couldn't (easily) be compiled from the net-snmp source code. It might be possible to improve support for hplip by making a puppy version of this library. [workround: the option isn't actually needed]
4 - The devx .sfs file puppy uses for the gcc compiler and python isn't at http://distro.ibiblio.org/puppylinux/pe ... -bionic64/ [fix: get it from archive.org]
5 - loading the devx .sfs when the filename had been accidentally changed broke x [fix: reboot with pfix=clean option]
6 - GCC links in /usr/include/sys all broke giving the error ""fatal error: gcc "Too many levels of symbolic links"" [fix: they can be replaced from a clean copy of the .sfs] (this may have been a user error or caused by installing and uninstalling packages)
7 - it wasn't possible (for an ordinary user) to reconcile the dependencies for the HP developers' hplip installation program against puppy's repository
8 - During printer setup in Puppy's CUPS it provides a link to work out the network URI... but it's a dead link making it harder to get the Address: correct in CUPS

[rockedge]

Setting up a Puppy for compiling, using PERL and some of Python 2.7, will be present by loading the Devx SFS.

A solid Python3 environment is tricky to set up. So after many many failures and missing python modules I've come to the conclusion for a great Python3 set up just use an ActiveState python.
Download, extract and run ./install.sh. I choose usually to load it in /opt. A couple of symlinks that I add and ready to go. I have good results in Puppy Bionic and Focal (Fossapup) with it. Also at the ActiveState website one can customize completely what modules will be included from start in your python set up.

Getting the printer to work.....well HP libs I've grabbed from all over and from many different distros that eventually I got going in Puppy. What works on one system may or may not work in another that seems almost exactly the same as the first...but that's computing (since I started in 1975 that has held true over and over)

I did manage to to use a Tahr-6.0.5 to simulate an AirPrint network printer with a dirt cheap Canon printer. Still to this day not sure how I did it exactly...the configuration of Avahi so iPhones, iPads, tablets, Android can print reliably on our home LAN is working, but if I had to do it again right now? I would be starting from zero since I did this like 5 years ago and it's worked solid since without intervention and as of late I've been making a 32 bit operating system with a JWM+ROX desktop so printing technology has been on the back burner.
That now reminds me that WeeDog32-Void has no CUPS installed at all.

Getting python3-opencv installed and working is a challenge. But once it is Puppy can do face recognition among many other tasks well.

[PuppyandCo]

Getting python3-opencv installed and working is a challenge. But once it is Puppy can do face recognition among many other tasks well.

Thanks for this! On my layperson's rules that is an excellent package because i) it's in package manager, ii) it has a short name, iii) it has a keyword (python)

I think my python environment is alright, but the official net-snmp tarball either has bugs in it (developers who post bugs on sourceforge are getting similar errors at a similar stage in the compile) or I need a very specific set of 'configure' options. Disabling things seems to make it better, but there are too many options to guess it by trial-and-error and I don't even know for sure that installing this will give me the missing package for hplip.

I did succeed in this once before on Slacko 6.3 in about 2016 so I won't give up. But it's the typical Linux user-experience.
I suspect puppy's hplip needs a look if the default package tries to install a GUI but doesn't bring up the GUI and the commands don't seem to do anything in terminal
I suspect puppy generally needs a printer wizard, the menu makes it look like it has one but it just loads a html page
I don't blame puppy for hplip not installing, it looks to me as if it stems from HP having 10 dependencies an ordinary user can install and 1 that they can't

[rcrsn51]

Another community member has reported getting a functional hplip-print-scan package from a Puppy repo at archive.org.

That might be worth investigating for your situation.

[mikewalsh]

@PuppyandCo :-

The reason Puppy uses the CUPS web-interface is simple; we all have a browser. And it saves having to create yet another app just to "coddle" ex-Windows users, for most of whom it's too much like hard work to have to get used to summat different...

Most folks are comfortable with what they DO know, and see no point in having to learn a new way of tackling the same issue.

(*shrug*)

Mike.

[PuppyandCo]

Another community member has reported getting a functional hplip-print-scan package from a Puppy repo at archive.org.

That might be worth investigating for your situation.

Thanks you're right about that there is a .pet file there (at least one). I tried keywords puppy+linux+hp+printer and it brought up this (which is sadly 32-bit)
https://archive.org/download/rcrsn51_foomatic20140426

========

In a way, if a user who knows how to patch an install file... is finding it necessary to patch the install file... that kind of tells me that getting an HP printer to work on puppy is very difficult indeed. It seems like a collision between the philosophy of stripping down all the libraries and the HP linux developers assuming the end-user can apt-get a list of 10 relatively complex software frameworks. From what I read of snmp, it lets devices on networks talk to each other, on virtually any -nix... it looks like quite a big operation, with an ecosystem and regular updates, and all the rest. Puppy linux be like "yyyeah, we'll let users build that if they want, saving 256kb comes first!".

========

DAY 1+2

Problem 1 The "printer wizard" GUI in the menu literally just loads an html page with vague help.
I know that I need hplip and the plugin so I download v.3.17.10 through the package manager, it won't open. It creates a menu link for a GUI but that doesn't work, and the command line tools fail.

The hp-lip installer at the HP developers throws up a large and nasty list of dependencies but I get them all except libsnmp-dev
libsnmp-dev is available online for Ubuntu in some .rpm packages, these convert into .pets but don't work / whatever they install doesn't meet the installer's dependency.
I can nearly compile net-snmp from source, but there's a bug.

I was nearly able to complete the hplip installation script by switching off all the optional items. Removing network support (which did not seem a good idea) got me almost all the way to the end, but it started giving a new dependency error for libjpeg.so.8 which needed to be symlinked from the Steam folder (of all places). And then ghostscript... and then the GUI to configure the printer started, and immediately crashed the PC.

GCC then broke (because the headers were somehow deleted from /usr/include/sys and replaced with infinite or circular symlinks), returning an incomprehensible error message. In the process of trying to mend GCC I downloaded another 2Gb of cruft... which I can't remove easily because...

Problem 2 the package manager's uninstall utility doesn't list what's been installed in date order... doesn't show the sizes of the packages... doesn't show what came with the install... doesn't provide any way to roll-back... can't export them as a text file to assist manual reinstallation... and the packages all have names like libsn-python.cruft and descriptions like "library to sign cruft plugins for python". The personal space has now been filled. And this might partly be caused ironically: by the space-saving philosophy of removing unnecessary libraries.

Problem 3 the snmp library required by the hplip installer's network option would not compile in any circumstances. Workaround 3 fortunately the hplip installer only needed to complete so that the HP drivers were available to CUPS and the hp-plugin command could be run. It was able to complete with all options set to No.

DAY 3

Removing and re-adding the devx .sfs doesn't change the headers back

But an sfs is not like a package... The menu doesn't let you install-or-delete them, it is load-or-unload. SFS stands for squashed filesystem, so hopefully I have messed up some files inside the sfs which are then unloaded and loaded whilst still being wrong. This might also be why trying to 'find' the messed up config file didn't work - it was packed back into the .sfs. So I can try replacing my devx_bionicpu64_8.0.sfs with a new one from the file repository and loading that one instead.

Problem 4 The devx .sfs file puppy uses for the gcc compiler and python isn't at http://distro.ibiblio.org/puppylinux/pe ... -bionic64/
Workaround 4 It is available from https://archive.org/download/Puppy_Linux_Bionicpup64

Problem 5 loading the devx .sfs when the filename had been mistakenly changed broke x
I had renamed devx_bionicpu64_8.0.sfs to devx_bionicpu64_8.0.sfs.bak and forgotten to rename it back before I shut down. JWM gave a screen full of errors on shutdown and on startup it went to a tty1 login: prompt then bash shell.
Fix 5 Typing startx at the bash shell worked though. I then rebooted puppy with pfix=clean and that repaired it. Except that root is now called bash-4.4 and my terminal history is gone. From doing 'less /etc/passwd' I believe the user is root and the name change is just cosmetic.

Problem 6 Although the sfs has been replaced, gcc still doesn't work though. The error is shown in config.log as "fatal error: gcc "Too many levels of symbolic links""
Fix 6:- the C headers in /usr/include/sys/ had all been replaced with symlinks that linked to symlinks and so on for at least 8 levels. I needed to copy them from inside a clean copy of the devx sfs (mount the .sfs, navigate inside it to /usr/include/sys and copy the files to ~/usr/include/sys... not sure if I have expressed that accurately the sys is like a virtual filesystem with the same directory names so I copied the files across into the real filesystem.

DAY 4

Fixed lost C headers. SNMP now gives the error from day 2 again:-

Code: Select all

making install in /mnt/veracrypt1/Downloads/net-snmp-5.9/man
make[1]: Entering directory '/mnt/veracrypt1/Downloads/net-snmp-5.9/man'
make[1]: *** No rule to make target '../sedscript', needed by 'agentxtrap.1'.  Stop.
make[1]: Leaving directory '/mnt/veracrypt1/Downloads/net-snmp-5.9/man'
Makefile:983: recipe for target 'installsubdirs' failed
make: *** [installsubdirs] Error 1

but hplip might work now if the options to install the network AND gui are both marked No. I think this will probably cause the printer not to be able to print over the network but let's see...

hplip completed installation but asking it to setup a printer crashed puppy again. starting again again.
Among other things, I removed hplip v3.17.10 from PPM, reinstalled it... ran it (unsuccessfully) and then downloaded and installed the installer from the hplip developers site for v3.20.11... I chose option 7 (ubuntu), option 15 (Bionic Beaver), install (d)iscrete drivers... and the rest of the options were straightforward.

once hplip was installed, the hp-plugin command could be run in terminal. Installation made the driver visible to CUPS and the plugin stopped the CUPS error saying "filter error". I installed numerous other packages by trial and error to get to this point though, including (names are approximate) xsane_DEV, glibc-source, python-avahi, avahi-discover, libavahi-core-dev. Several sub-packages (sorry I don't know the right term, I mean the little files that are only available in a library package) were requested including libhpmud.so.0, libhpip.so.0, cupsext...

Problem 7: basically it wasn't possible (for an ordinary user) to reconcile the HP installation program's dependencies against puppy's repository. I'd have been happier if the help file could have listed 10-20 packages to start with, like a shopping list. I also suspect the HP installation program doesn't make enough concessions to end-users (other than Ubuntu ones for whom "it just works").

Problem 8:
CUPS couldn't discover this printer as Ubuntu does. During printer setup in Puppy's CUPS it provides a link to work out the network URI... but it's a dead link and I wasn't able to find a correct list of URIs. Fortunately I had a huge head start in being able to copy the Address that Ubuntu's printer toolbox discovered, probably I wouldn't have managed this otherwise. For some reason Ubuntu accesses this printer (usb printer plugged into windows 7 and then shared) via smb:// but for CUPS on puppy that doesn't work and it needs the ("install windows features") LPD service to be running and for CUPS to access the printer via lpd:192.168.1.xxx/printer_name

The test page prints, it may be there will be other fun and games but on slacko 6.3 with this printer (both HP CP1215 and HP CP1217) I never needed to do anything further once it was working.

List of installed packages

Code: Select all

.:
adwaita-icon-theme_3.28.0.files
ap-utils_1.5-3.files
avahi-daemon_0.7.files
avahi-discover_0.7.files
avahi-utils_0.7.files
bind9-host_9.11.3+dfsg.files
breeze-icon-theme_5.44.0.files
build-essential_12.4ubuntu1.files
builtin_files
clisp_2.49.20170913.files
clisp-module-bindings-glibc_2.49.20170913.files
Custom_SFSs
db-date
devscripts_2.17.12ubuntu1.1.files
devx-only-installed-packages
dh-python_3.20180325ubuntu2.files
dirmngr_2.2.4.files
DISTRO_COMPAT_REPOS
DISTRO_PET_REPOS
DISTRO_PET_REPOS-orig
DISTRO_PKGS_SPECS
docbook-xml_4.5-8.files
docbook-xsl_1.79.1+dfsg-2.files
engrampa_1.20.0-1.files
engrampa-common_1.20.0-1.files
facetimehd_bionic64_4.19.23-1.files
firefox-62.0.2-x86_64.files
foomatic-db-compressed-ppds_20180306-1.files
gcc-6-base_6.5.0.files
gcc-6-cross-base_6.5.0.files
gcc-7-base_7.5.0.files
gcc-7-cross-base_7.5.0.files
gcc-8-base_8.4.0.files
gdal-data_2.2.3+dfsg-2.files
geany-plugin-commander_1.32+dfsg-3.files
gir1.2-glib-2.0_1.56.1-1.files
gir1.2-gtk-3.0_3.22.30.files
glibc-source_2.27.files
gnupg_2.2.4.files
gnupg-l10n_2.2.4.files
gnupg-utils_2.2.4.files
gpg_2.2.4.files
gpg-agent_2.2.4.files
gpgconf_2.2.4.files
gpgsm_2.2.4.files
gpgv_2.2.4.files
gpg-wks-client_2.2.4.files
gpg-wks-server_2.2.4.files
gsfonts_8.11+urwcyr1.0.7.files
gsfonts-other_6.0.files
gsfonts-x11_0.25.files
gstreamer1.0-alsa_1.14.5.files
gstreamer1.0-plugins-base_1.14.5.files
gstreamer1.0-pulseaudio_1.14.5.files
hplip_3.17.10+repack0-5.files
hplip-data_3.17.10+repack0-5.files
hplip-gui_3.17.10+repack0-5.files
humanity-icon-theme_0.6.15.files
jwm_2.3.7-1.files
jwmconfig3-151025.files
JWMDesk-2.5.files
jwm_theme_stark-blueish-1.files
kdelibs5-data_4.14.38.files
kdelibs5-plugins_4.14.38.files
kdelibs-bin_4.14.38.files
kde-runtime_17.08.3.files
kde-runtime-data_17.08.3.files
kde-style-breeze_5.12.8.files
kde-style-breeze-qt4_5.12.8.files
kdoctools_4.14.38.files
kinit_5.44.0.files
kio_5.44.0.files
konsole_17.12.3.files
konsole-kpart_17.12.3.files
kwayland-data_5.44.0.files
layers-installed-packages
libaec0_0.3.2-2.files
libaribb24-0_1.0.3-1.files
libarmadillo8_8.400.0+dfsg-2.files
libarpack2_3.5.0+real-2.files
libassuan0_2.5.1-2.files
libattica0.4_0.4.2-2.files
libavahi-core7_0.7.files
libavahi-core-dev_0.7.files
libbasicusageenvironment1_2018.02.18-1.files
libbind9-160_9.11.3+dfsg.files
libblas3_3.7.1.files
libcaja-extension1_1.20.2.files
libcharls1_1.1.0+dfsg-2.files
libclass-accessor-perl_0.51-1.files
libclucene-core1v5_2.3.3.4+dfsg-1.files
libconfig-inifiles-perl_2.94-1.files
libcrypto++6_5.6.4-8.files
libcrypto++-dev_5.6.4-8.files
libdap25_3.19.1.files
libdapclient6v5_3.19.1.files
libdb1-compat_2.1.3-20.files
libdb5.3_5.3.28.files
libdbusmenu-qt2_0.9.3+16.04.20160218.files
libdbusmenu-qt5-2_0.9.3+16.04.20160218.files
libdlrestrictions1_0.15.28ubuntu1.files
libdns1100_9.11.3+dfsg.files
libepsilon1_0.9.2+dfsg-2.files
libexporter-tiny-perl_1.000000-2.files
libfabric1_1.5.3-1.files
libfam0_2.7.0-17.2.files
libffcall1b_2.1-1.files
libfile-homedir-perl_1.002-1.files
libfile-which-perl_1.21-1.files
libfreexl1_1.0.5-1.files
libfyba0_4.1.1-3.files
libgdal20_2.2.3+dfsg-2.files
libgdcm2.8_2.8.4.files
libgeos-3.6.2_3.6.2.files
libgeos-c1v5_3.6.2.files
libgeotiff2_1.4.2.files
libgfortran4_7.5.0.files
libgl2ps1.4_1.4.0+dfsg1-1.files
libgpgme11_1.10.0.files
libgpgme++2v5_4.14.10.files
libgpgmepp6_1.10.0.files
libgroupsock8_2018.02.18-1.files
libhdf4-0-alt_4.2.13-2.files
libhdf5-100_1.10.0-patch1+docs-4.files
libhdf5-openmpi-100_1.10.0-patch1+docs-4.files
libhpmud0_3.17.10+repack0-5.files
libhwloc5_1.11.9-1.files
libhwloc-plugins_1.11.9-1.files
libibverbs1_17.1.files
libilmbase12_2.2.0.files
libindicator3-7_16.10.0+18.04.20180321.1.files
libindicator3-dev_16.10.0+18.04.20180321.1.files
libindicator7_16.10.0+18.04.20180321.1.files
libindicator-dev_16.10.0+18.04.20180321.1.files
libisc169_9.11.3+dfsg.files
libisccc160_9.11.3+dfsg.files
libisccfg160_9.11.3+dfsg.files
libkactivities6_4.13.3.files
libkate1_0.4.1.files
libkcmutils4_4.14.38.files
libkde3support4_4.14.38.files
libkdeclarative5_4.14.38.files
libkdecore5_4.14.38.files
libkdesu5_4.14.38.files
libkdeui5_4.14.38.files
libkdewebkit5_4.14.38.files
libkdnssd4_4.14.38.files
libkemoticons4_4.14.38.files
libkf5archive5_5.44.0.files
libkf5attica5_5.44.0.files
libkf5auth5_5.44.0.files
libkf5auth-data_5.44.0.files
libkf5bookmarks5_5.44.0.files
libkf5bookmarks-data_5.44.0.files
libkf5codecs5_5.44.0.files
libkf5codecs-data_5.44.0.files
libkf5completion5_5.44.0.files
libkf5completion-data_5.44.0.files
libkf5configcore5_5.44.0.files
libkf5config-data_5.44.0.files
libkf5configgui5_5.44.0.files
libkf5configwidgets5_5.44.0.files
libkf5configwidgets-data_5.44.0.files
libkf5coreaddons5_5.44.0a.files
libkf5coreaddons-data_5.44.0a.files
libkf5crash5_5.44.0.files
libkf5dbusaddons5_5.44.0.files
libkf5dbusaddons-data_5.44.0.files
libkf5doctools5_5.44.0.files
libkf5globalaccel5_5.44.0.files
libkf5globalaccel-data_5.44.0.files
libkf5guiaddons5_5.44.0.files
libkf5i18n5_5.44.0.files
libkf5i18n-data_5.44.0.files
libkf5iconthemes5_5.44.0.files
libkf5iconthemes-data_5.44.0.files
libkf5itemviews5_5.44.0.files
libkf5itemviews-data_5.44.0.files
libkf5jobwidgets5_5.44.0.files
libkf5jobwidgets-data_5.44.0.files
libkf5kiocore5_5.44.0.files
libkf5kiontlm5_5.44.0.files
libkf5kiowidgets5_5.44.0.files
libkf5notifications5_5.44.0.files
libkf5notifications-data_5.44.0.files
libkf5notifyconfig5_5.44.0.files
libkf5notifyconfig-data_5.44.0.files
libkf5parts5_5.44.0.files
libkf5parts-data_5.44.0.files
libkf5pty5_5.44.0.files
libkf5pty-data_5.44.0.files
libkf5service5_5.44.0.files
libkf5service-bin_5.44.0.files
libkf5service-data_5.44.0.files
libkf5solid5_5.44.0.files
libkf5solid5-data_5.44.0.files
libkf5sonnet5-data_5.44.0.files
libkf5sonnetcore5_5.44.0.files
libkf5sonnetui5_5.44.0.files
libkf5style5_5.44.0.files
libkf5textwidgets5_5.44.0.files
libkf5textwidgets-data_5.44.0.files
libkf5wallet5_5.44.0.files
libkf5wallet-bin_5.44.0.files
libkf5wallet-data_5.44.0.files
libkf5waylandclient5_5.44.0.files
libkf5widgetsaddons5_5.44.0.files
libkf5widgetsaddons-data_5.44.0.files
libkf5windowsystem5_5.44.0.files
libkf5windowsystem-data_5.44.0.files
libkf5xmlgui5_5.44.0.files
libkf5xmlgui-bin_5.44.0.files
libkf5xmlgui-data_5.44.0.files
libkfile4_4.14.38.files
libkhtml5_4.14.38.files
libkio5_4.14.38.files
libkjsapi4_4.14.38.files
libkjsembed4_4.14.38.files
libkmediaplayer4_4.14.38.files
libkmlbase1_1.3.0-5.files
libkmldom1_1.3.0-5.files
libkmlengine1_1.3.0-5.files
libknewstuff3-4_4.14.38.files
libknotifyconfig4_4.14.38.files
libkntlm4_4.14.38.files
libkparts4_4.14.38.files
libkpathsea6_2017.20170613.44572.files
libkpty4_4.14.38.files
libkrosscore4_4.14.38.files
libksba8_1.3.5-2.files
libktexteditor4_4.14.38.files
libkwalletbackend5-5_5.44.0.files
libkxmlrpcclient4_4.14.10.files
liblapack3_3.7.1.files
liblept5_1.75.3-3.files
liblirc-client0_0.10.0-2.files
liblist-moreutils-perl_0.416.files
liblivemedia62_2018.02.18-1.files
liblwres160_9.11.3+dfsg.files
libmatroska6v5_1.4.8-1.1.files
libmicrodns0_0.0.8-1.files
libminizip1_1.1.files
libnetcdf13_4.6.0.files
libnetcdf-c++4_4.2-8.files
libnet-snmp-perl_6.0.1-3.files
libnfs11_2.0.0-1.files
libnmap-parser-perl_1.36-1.files
libnpth0_1.5-3.files
libntrack0_016-1.3.files
libntrack-qt4-1_016-1.3.files
libodbc1_2.3.4.files
libogdi3.2_3.2.0+ds-2.files
libopencv-calib3d3.2_3.2.0+dfsg.files
libopencv-contrib3.2_3.2.0+dfsg.files
libopencv-features2d3.2_3.2.0+dfsg.files
libopencv-flann3.2_3.2.0+dfsg.files
libopencv-highgui3.2_3.2.0+dfsg.files
libopencv-imgcodecs3.2_3.2.0+dfsg.files
libopencv-ml3.2_3.2.0+dfsg.files
libopencv-objdetect3.2_3.2.0+dfsg.files
libopencv-photo3.2_3.2.0+dfsg.files
libopencv-shape3.2_3.2.0+dfsg.files
libopencv-stitching3.2_3.2.0+dfsg.files
libopencv-superres3.2_3.2.0+dfsg.files
libopencv-video3.2_3.2.0+dfsg.files
libopencv-videoio3.2_3.2.0+dfsg.files
libopencv-videostab3.2_3.2.0+dfsg.files
libopencv-viz3.2_3.2.0+dfsg.files
libopenexr22_2.2.0.files
libopenhpi3_3.6.1.files
libopenmpi2_2.1.1-8.files
libopenmpt-modplug1_0.3.6-1.files
libperl5.26_5.26.1.files
libphonon4_4.10.0-2.files
libphonon4qt5-4_4.10.0-2.files
libplacebo4_0.4.0-2.files
libplasma3_4.14.38.files
libpolkit-agent-1-0_0.105.files
libpolkit-backend-1-0_0.105.files
libpolkit-gobject-1-0_0.105.files
libpolkit-qt-1-1_0.112.0-5.files
libpolkit-qt-1-dev_0.112.0-5.files
libpolkit-qt5-1-1_0.112.0-5.files
libpolkit-qt5-1-dev_0.112.0-5.files
libportmidi0_217-6.files
libproj12_4.9.3-2.files
libpsm-infinipath1_3.3+20.604758e7-5.files
libpython3.6_3.6.9-1.files
libpython3.6-minimal_3.6.9-1~18.04ubuntu1.3_amd64.files
libpython3.6-stdlib_3.6.9-1~18.04ubuntu1.3_amd64.files
libpython3-stdlib_3.6.7-1~18.04_amd64.files
libqca2_2.1.3.files
libqhull7_2015.2-4.files
libqt4-dbus_4.8.7+dfsg.files
libqt4-declarative_4.8.7+dfsg.files
libqt4-designer_4.8.7+dfsg.files
libqt4-dev_4.8.7+dfsg.files
libqt4-dev-bin_4.8.7+dfsg.files
libqt4-help_4.8.7+dfsg.files
libqt4-network_4.8.7+dfsg.files
libqt4-opengl_4.8.7+dfsg.files
libqt4-qt3support_4.8.7+dfsg.files
libqt4-script_4.8.7+dfsg.files
libqt4-scripttools_4.8.7+dfsg.files
libqt4-sql_4.8.7+dfsg.files
libqt4-svg_4.8.7+dfsg.files
libqt4-test_4.8.7+dfsg.files
libqt4-xml_4.8.7+dfsg.files
libqt4-xmlpatterns_4.8.7+dfsg.files
libqt5designer5_5.9.5.files
libqt5qml5_5.9.5.files
libqt5quick5_5.9.5.files
libqt5script5_5.9.5+dfsg.files
libqt5texttospeech5_5.9.5.files
libqtassistantclient4_4.6.3.files
libqtcore4_4.8.7+dfsg.files
libqtdbus4_4.8.7+dfsg.files
libqtgui4_4.8.7+dfsg.files
libqtwebkit4_2.3.2.files
librdmacm1_17.1.files
libreadline5_5.2+dfsg.files
libresid-builder0c2a_2.1.1.files
libruby2.5_2.5.1.files
libsane-hpaio_3.17.10+repack0-5.files
libsensors4-dev_3.4.0-4.files
libshout3_2.4.1.files
libsidplay2_2.1.1.files
libsmi2ldbl_0.4.8+dfsg2-15.files
libsnmp30_5.7.3+dfsg.files
libsnmp-base_5.7.3+dfsg.files
libsnmp-dev_5.7.3+dfsg.files
libsnmp-extension-passpersist-perl_0.07-2.files
libsnmp-info-perl_3.39-1.files
libsnmpkit2v5_0.9.files
libsnmpkit-dev_0.9.files
libsnmp-mib-compiler-perl_0.06-2.2.files
libsnmp-multi-perl_2.1-4.files
libsnmp-perl_5.7.3+dfsg.files
libsnmp-session-perl_1.14.files
libsocket++1_1.12.13-9.files
libsolid4_4.14.38.files
libspatialite7_4.3.0a.files
libssh2-1_1.8.0-1.files
libstreamanalyzer0v5_0.7.8-2.2.files
libstreams0v5_0.7.8-2.2.files
libsub-name-perl_0.21.files
libsuperlu5_5.2.1+dfsg1-3.files
libsz2_0.3.2-2.files
libtcl8.6_8.6.8+dfsg-3.files
libtesseract4_4.00.files
libthreadweaver4_4.14.38.files
libtk8.6_8.6.8-4.files
libunique-1.0-0_1.1.6-6.files
libupnp6_1.6.24-4.files
libupsclient4_2.7.4.files
liburiparser1_0.8.4-1.files
libusageenvironment3_2018.02.18-1.files
libutempter0_1.1.6-3.files
libvisual-0.4-0_0.4.0-11.files
libvlc5_3.0.8.files
libvlccore9_3.0.8.files
libvte-2.91-0_0.52.2.files
libvte-2.91-common_0.52.2.files
libvtk6.3_6.3.0+dfsg1.files
libvulkan1_1.1.70+dfsg1.files
libwebpdemux2_0.6.1-2.files
libwxbase3.0-0v5_3.0.4+dfsg-3.files
libwxgtk3.0-gtk3-0v5_3.0.4+dfsg-3.files
libxerces-c3.2_3.2.0+debian-2.files
libxml-twig-perl_3.50-1.files
libyaml-0-2_0.1.7.files
list.txt
lxsession-data_0.5.3.files
lxterminal_0.3.1.files
mime-support_3.60ubuntu1_all.files
net.downloadhelper.coapp.files
net-snmp-5.4.1-i486.files
net-snmp-5.7.3.files
ntrack-module-libnl-0_016-1.3.files
nut_2.7.4.files
nut-client_2.7.4.files
nut-server_2.7.4.files
nut-snmp_2.7.4.files
ocl-icd-libopencl1_2.2.11.files
odbcinst1debian2_2.3.4.files
odbcinst_2.3.4.files
odrive-0.2.1_x86_64.files
openhpi-plugin-snmp-bc_3.6.1.files
oxygen-icon-theme_5.44.0.files
Packages-puppy-bionic64-official
Packages-puppy-common64-official
Packages-puppy-noarch-official
Packages-puppy-tahr64-official
Packages-puppy-xenial64-official
Packages-ubuntu-bionic-main
Packages-ubuntu-bionic-multiverse
Packages-ubuntu-bionic-universe
perl-openssl-defaults_3build1.files
phonon_4.10.0-2.files
phonon4qt5_4.10.0-2.files
phonon4qt5-backend-vlc_0.10.1-2.files
phonon-backend-gstreamer_4.9.0-1.files
phonon-backend-gstreamer-common_4.9.0-1.files
php7.2-common_7.2.24.files
php7.2-snmp_7.2.24.files
php-common_60ubuntu1.files
php-snmp_7.2.files
pinentry-curses_1.1.0-1.files
PKGS_HOMEPAGES
PKGS_HOMEPAGES_OUT
PKGS_MANAGEMENT
plasma-scriptengine-javascript_17.08.3.files
policykit-1_0.105.files
printer-driver-hpcups_3.17.10+repack0-5.files
proj-data_4.9.3-2.files
pslib1_0.4.5.files
psutils_1.17.dfsg-4.files
pypi2deb_1.20170623.files
pypibrowser_1.5-2.1.files
pyppd_1.0.2-6.files
pyqt4-dev-tools_4.12.1+dfsg-2.files
python3_3.6.7-1~18.04_amd64.files
python3.6-minimal_3.6.9-1~18.04ubuntu1.3_amd64.files
python3-aiohttp_3.0.1-1.files
python3-asn1crypto_0.24.0-1.files
python3-async-timeout_2.0.0-1.files
python3-attr_17.4.0-2.files
python3-certifi_2018.1.18-2.files
python3-chardet_3.0.4-1.files
python3-cryptography_2.1.4.files
python3-dbus_1.2.6-1.files
python3-dbus.mainloop.pyqt5_5.10.1+dfsg.files
python3-debian_0.1.32.files
python3-distutils_3.6.9-1~18.04_all.files
python3-gi_3.26.1.files
python3-idna_2.6-1.files
python3-jinja2_2.10.files
python3-lib2to3_3.6.9-1~18.04_all.files
python3-markupsafe_1.0.files
python3-multidict_4.1.0-1.files
python3-numpy_1.13.3.files
python3-opencv_3.2.0+dfsg.files
python3-openssl_17.5.0.files
python3-pexpect_4.2.1-1.files
python3-pil_5.1.0.files
python3-pkginfo_1.2.1-1.files
python3-pkg-resources_39.0.1-2.files
python3-ply_3.11-1.files
python3-pyasn1_0.4.2-3.files
python3-pycryptodome_3.4.7.files
python3-pyqt5_5.10.1+dfsg.files
python3-pysmi_0.2.2-1.files
python3-pysnmp4_4.4.3-1.files
python3-pyx_0.14.1-8.files
python3-redis_2.10.6.files
python3-reportlab_3.4.0.files
python3-reportlab-accel_3.4.0.files
python3-requests_2.18.4.files
python3-requests-toolbelt_0.8.0-1.files
python3-setuptools_39.0.1-2.files
python3-setuptools-git_1.2-1.files
python3-setuptools-scm_1.15.6-1.files
python3-six_1.11.0-2.files
python3-snimpy_0.8.12-1.files
python3-tqdm_4.19.5-1.files
python3-urllib3_1.22.files
python3-yarl_1.1.0-1.files
python-asn1crypto_0.24.0-1.files
python-avahi_0.7.files
python-cryptography_2.1.4.files
python-dbus_1.2.6-1.files
python-dbus-dev_1.2.6-1.files
python-dbus.mainloop.pyqt5_5.10.1+dfsg.files
python-dbusmock_0.17.1-1.files
python-dbus-tests_1.2.6-1.files
python-enum34_1.1.6-2.files
python-gdbm_2.7.17-1.files
python-gi_3.26.1.files
python-idna_2.6-1.files
python-ipaddress_1.0.17-1.files
python-netsnmp_5.7.3+dfsg.files
python-notify_0.1.1-4.files
python-notify2_0.3-3.files
python-openssl_17.5.0.files
python-pil_5.1.0.files
python-pip_9.0.1-2.3.files
python-pip-whl_9.0.1-2.3.files
python-pkg-resources_39.0.1-2.files
python-ply_3.11-1.files
python-pyasn1_0.4.2-3.files
python-pycryptodome_3.4.7.files
python-pypm_0.0.7-8.files
python-pyscript_0.6.1-4.files
python-pysmi_0.2.2-1.files
python-pysnmp4_4.4.3-1.files
python-pysnmp4-apps_0.3.2-1.files
python-pysnmp4-mibs_0.1.3-1.files
python-pyx_0.12.1-9.files
python-qt4_4.12.1+dfsg-2.files
python-qt4-dbus_4.12.1+dfsg-2.files
python-qt4-dev_4.12.1+dfsg-2.files
python-reportlab_3.4.0.files
python-reportlab-accel_3.4.0.files
python-setuptools_39.0.1-2.files
python-setuptools-git_1.2-1.files
python-setuptools-scm_1.15.6-1.files
python-sip_4.19.7+dfsg.files
python-sip-dev_4.19.7+dfsg.files
python-six_1.11.0-2.files
python-snimpy_0.8.12-1.files
python-wxgtk3.0_3.0.2.0+dfsg-7.files
python-wxversion_3.0.2.0+dfsg-7.files
qdbus_4.8.7+dfsg.files
qt4-linguist-tools_4.8.7+dfsg.files
qt4-qmake_4.8.7+dfsg.files
qt5-qmake_5.9.5+dfsg.files
qt5-qmake-bin_5.9.5+dfsg.files
qtbase5-dev_5.9.5+dfsg.files
qtbase5-dev-tools_5.9.5+dfsg.files
qtchooser_64-ga1b6736-5.files
qtcore4-l10n_4.8.7+dfsg.files
rake_12.3.1.files
ruby_2.5.1.files
ruby2.5_2.5.1.files
ruby-did-you-mean_1.2.0-2.files
rubygems-integration_1.11.files
ruby-minitest_5.10.3-1.files
ruby-net-telnet_0.1.1-2.files
ruby-power-assert_0.3.0-1.files
ruby-snmp_1.2.0-1.files
ruby-test-unit_3.2.5-1.files
sensible-utils_0.0.12.files
sip-dev_4.19.7+dfsg.files
smitools_0.4.8+dfsg2-15.files
snmp_5.7.3+dfsg.files
snmpd_5.7.3+dfsg.files
snmptrapd_5.7.3+dfsg.files
snmptt_1.4-1.files
steam-bionicpup.files
thunderbird_68.10.0+build1.files
tor-browser-8.0-x86_64.files
twine_1.10.0-1.files
ubuntu-mono_16.10+18.04.20181005.files
user-installed-packages
veracrypt-1.24-Update7-Debian-9.files
vlc-data_3.0.8.files
vlc-plugin-base_3.0.8.files
vlc-plugin-video-output_3.0.8.files
wine64-3.15_v4.1.files
woof-build.conf
woof-installed-packages
wx-common_3.0.4+dfsg-3.files
xsane_DEV-0.999-x86_64_bionic.files
zoom_amd64.files
zoom-x86_64.files

./builtin_files:
915resolution
a52dec
aalib
abiword
acl
acpi
acpid-busibox
alsa-base
alsa-driver
alsaequal
alsa-lib
alsa-utils
alsa_zzBTfix
apparmor
apulse
aria2
arp-scan
aspell
asunder
atk
atkmm
at-spi2-atk
attr
audiofile
audit
avahi
avfs
axel
babeltrace
bash
bbe
bc
bcrypt
bdb
bluez
bluez-alsa
boehm-gc
busybox
bzip2
ca-certificates
cairo
cairomm
caps
cdparanoia
cdrkit
cdrtools
change_kernels
chntpw
cifs-utils
claws-mail
clipit
close
colord
compton
copy-fast
coreutils
cpio
crda
cryptsetup
ctorrent
cups
cups_backend
cups-filters
curl
cyrus-sasl2
dbus
dbus-glib
d-conf
ddcprobe
deadbeef
debianutils
dejavu_fonts
desk_icon_theme_ardis
desk_icon_theme_blue_moon
desk_icon_theme_jq8raised
desk_icon_theme_Moka
desk_icon_theme_Numix
desk_icon_theme_uniform
desktop-file-utils
devmapper
dhcpcd
dialog
dictd_client
diffstat
diffutils
directfb
disktype
dmidecode
dosfstools
dpkg
dunst
dvdauthor
dvd+rwtools
e2fsprogs
ed
edid
efibootmgr
efivar
eject
elfutils
elogind
enchant
ethtool
eudev
exfat
exiv2
expat
f2fs-tools
faac
faad
fdisk
ffmpeg
ffmpegdev
file
findnrun
findutils
firewall_ng
firewallstatus
flac
flsynclient
fontconfig
foomatic-db-engine
foomatic-filters
fpm2
freeglut
freememapplet
freetype
fribidi
frisbee
fuse
gail
galculator
gamin
gawk
gcc_lib
gconf
gdbm
gdk-pixbuf
gdmap
geany
geany-plugins
getcurpos
getflash
get_libreoffice
gettext
gexec
gftp
ghostscript
giflib
gifsicle
glib
glibc
glibc32
glibc_locales
glibmm
glib-networking
gmeasures
gmp
gnet
gnome-keyring
gnome-menus
gnome-vfs
gnumeric
gnutls
gobject-introspection
goffice
go-mtpfs
gpart
gparted
gperf
gphoto2
gphotofs
gpick
gplanarity
gpm
gpptp
gptfdisk
graphite2
grep
grsync
grub
grub2_efi
grub4dos
gsettings-desktop-schemas
gsm
gstreamer1
gtk+
gtk2-engines-pixbuf
gtk+3
gtk-chtheme
gtkdialog
gtkhash
gtklp
gtkmm
gtksourceview
gtkspell
gtk_theme_flatbluecontrast
gtk_theme_flat_grey_rounded
gtk_theme_numix
gtk_theme_stardust_zigbert
gtk_theme_stark
gtk_theme_stark-blueish
gtk-update-icon-cache
gutenprint
guvcview
gview
gxlat
gxmessage
gzip
hal_flash
hardinfo
harfbuzz
hdparm
heimdal
hexalate
hexchat
hiawatha
hicolor-icon-theme
homebank
hotplug2stdout
htop
hunspell
hunspell-en-us
icu
id3lib
ijs
init-system-helpers
inkscapelite
inotail
inotify-tools
installwatch
intltool
iptables
iqpuzzle
iso-codes
isomaster
iw
janky_BT
jbig2dec
jbigkit
jimtcl
json-c
jwm
jwmconfig3
JWMDesk
jwm_theme_stark-blueish
keyutils
kmod
kodi_missing
krb5
lame
lcms
lcms2
leafpad
legacy_grub_2013
less
libaacs
libao
libappindicator
libarchive
libargon
libart
libasyncns
libb2
libbluray
libbonobo
libboost-filesystem
libboost-iostreams
libboost-locale
libboost-system
libboost-thread
libbsd
libc6-i386
libcaca
libcanberra
libcap
libcap-ng
libcapnp
libcddb
libcdio
libcdk5
libcgi-pm-perl
libcom-err2
libcroco
libcurl3-gnutls
libdaemon
libdatrie
libdbusmenu
libdc1394
libdca
libde265
libdjvulibre
libdmx
libdouble-conversion
libdrm
libdv
libdvbpsi
libdvdcss
libdvdnav
libdvdread
libebml
libedit
libenca
libepoxy
libevdev
libevent
libexif
libexif-gtk
libfdk_aac
libffi
libfftw3
libfs
libgc
libgcrypt
libgd2
libgdbm-compat
libgee
libgeoip
libgif
libglade2
libgles
libglvnd
libgnome
libgnomecanvas
libgnome-keyring
libgnomeui
libgpg-error
libgphoto2
libgringotts
libgsf
libgtkhtml
libgudev
libhogweed
libical
libid3tag
libidl
libidn
libieee1284
libimlib
libindicator
libinput
libip4tc
libip6tc
libjack
libjansson4
libjpeg
libjpeg62
libjpeg8
libjsoncpp1
libjson-glib
libloudmouth
libltdl
liblua5
liblz4
libmad
libmbed
libmcrypt
libmirclient
libmng
libmnl
libmpcdec
libmpdec2
libmpfr
libmtp
libnatpmp
libnetfilter-conntrack
libnfnetlink
libnl
libnl3
libnotify
libofx
libogg
libopencore
libpaper
libpcap
libpciaccess
libpcsclite
libpng
libpng14
libproxy
libraw1394
librest
librevenge
librsvg
libsamplerate
libsbc
libseccomp
libsecret
libselinux
libsensors4
libsepol
libsigc++
libsigsegv
libslang
libsmartcols
libsndfile
libsoup2.4
libspectre
libstdc++5
libstdc++6
libstdc++-7-dev
libsystem
libsystemd
libtalloc
libtar
libtasn1
libthai
libtheora
libtiff
libtubo
libunistring
libusb
libusb1
libv4l
libva
libvdpau
libvorbis
libvpx
libvte
libwbclient
libwmf
libwpd
libwpg
libx86
libxatracker2
libxcb
libxdg-basedir
libxkbcommon
libxml2
libxshmfence
libxslt
libxvmc
libzip
libzstd
lirc
ListDD
llvm-cut
lsb-base
lvm2
lxrandr
lxtask
lzma
lzo2
madplay
makebootfat
man_cut
mesa
metamail
mhash
mhwaveedit
minidlna
miniupnpc
modem-stats
mp
mpeg2dec
mpv
ms-sys
mtdev
mtPaint
mtp_phone_connect
mtr
multirename
nas
nbtscan
ncurses
ndiswrapper
nenscript
netmon_wce
netpbm
nettle
net-tools
network_wizard
normalize
notecase
nrg2iso
nspr
nss
ntfs-3g
ntpdate
numactl
numlockx
opencv
openldap
opensp-runtime
openssh_client
openssl
opus
orbit2
orc
osmo
ots
p11-kit
p7zip-full
PackIt
palemoon
pam
pango
pangomm
parted
pburn
pcd
pciutils
pclock
pcmciautils
pcre
pdiag
pdvdrsab
peasydisc
peasyglue
peasypdf
peasyport
peasyscale_64bit
perl-digest-sha1
perl-html-parser
perl_tiny
pfilesearch
pfind
pgprs
picocom
picpuz
pixman
pkg
pmirrorget
pnethood
pnscan
poppler
popt
portaudio
pplog
ppp
pprocess
pptp
Primrose
procps
programchooser
pschedule
psmisc
ptiming
pulseaudio
PupClockset
pupdial
puppy_icon_theme
puppyinputdetect
puppyphone
puppyserialdetect
Pup-SysInfo
python
pythondev
python-libxml2
python_support
qbat
qpdf
qpdfview
qt5
QtNote
quickpet_bionic64
qwinff
raptor2
readline
redland
redshiftgui
redshiftgui_wrapper
retrovol
rox-filer
rpl
rp-pppoe
rsync
rtmpdump
rubix
rxvt-unicode
samba
sane-backends
scale2x
scrot
sdl
sed
setserial
setvol
shared-mime-info
simplegtkradio
simple_network_setup
simplescreenrecorder
simsu
speex
sqlite
squashfs-tools4
ssh-gui
ssl-certificate-fix
startup-notification
streamripper
sudo
sunfish_chess
sysfsutils
syslinux
sysvinit
taglib
tar
tas
tbb
tcp-wrappers
tdb
telepathy-glib
tevent
tidy
time
transmission
tree
ucf
udev
uextract
uget
unclutter
unrar
unzip
UrxvtControl
usb-modeswitch
usb-modeswitch-data
usbutils
util-linux
vamps
vcdimager
viewnior
vo-aacenc
vo-amrwbenc
vobcopy
vorbis-tools
wallpaper
wayland
wayland-protocols
wcpufreq
wget
wireless-tools
wmctrl
wpa_supplicant
wv
wvdial
wvstreams
x264
x265
xarchive
xauth
xaw3d
xcb-util
xclip
xcur2png
xdelta
xdg_puppy
Xdialog
xfdiff
xfonts-encodings
xlock_gui
xlockmore
xorg_base_new
xorg_dri
xsane
xserver_xorg
xvidcore
xvkbd
xz
yad
yahtzeez
yajl
YASSM
zip
zlib
zz_bionicfix64

[PuppyandCo]

@PuppyandCo :-

The reason Puppy uses the CUPS web-interface is simple; we all have a browser. And it saves having to create yet another app just to "coddle" ex-Windows users, for most of whom it's too much like hard work to have to get used to summat different...

Most folks are comfortable with what they DO know, and see no point in having to learn a new way of tackling the same issue.

(*shrug*)

Mike.

The CUPS interface is superior to the windows print manager, whilst being pretty familiar/accessible to windows users.

Puppy's "CUPS Manage Printing" menu entry isn't part of CUPS though, and instead of doing what would make sense for it to do (open the CUPS interface in the browser, which would help train the ex-windows user in the new way of working, away from reaching for Start Menu>Control Panel) it opens a help document in abiword. The help document might be very helpful regarding CUPS, but CUPS won't install a proprietary driver for them - the user must first get their printer installed so CUPS can talk to it. This menu entry should say "guide to setting up printing" or something.

screenshot of CUPS Manage Printing menu entry

Puppy Printing.png (26.67 KiB) Viewed 865 times

And it saves having to create yet another app

Behind this there is another question whether yet another app (or apps) should be created for installing proprietary print drivers. If the drivers can't be installed without the compiler, and getting compilers to work on puppy is challenging (because of what they are, and given upstream developers may package source code assuming libraries are being apt-gotten correctly rather than individually curated by an incompetent like me), it follows an app should be created. (Someone's gotta program it, and it ain't the user.) CUPS can load a .ppd so it might be that my printer is unfortunate in needing the proprietary driver along with its plug-in, in which case Puppy can say HP is supported as long as you don't need the proprietary driver... that's fine I can buy another printer, I don't *expect* 14-year old laser printers to work it's that I've kept mine this long partly because I've known it to work well on linux, including puppy.

[Amigodetux]

I think Cups is great, opinions can vary according to the needs of each person. In my case, thanks to CUPS, my printer works without the annoying messages of incompatibility of cartridges and other inconveniences when I used it in Wind0ws. I'm not an expert, but as a home user, I have had no problems using CUPS. It has worked for me with HP although I currently use a Canon.

[Geek3579]

I am currently using Bionicpup64 as my do-all-go-to desktop, and must have a printer connection. HP printers from my experience have been difficult to make work. But it seems Bionicpup64 and perhaps Fossapup64 have better or updated HP software.

All I do is search for HPLIP in the Puppy Package Manager and load any software that comes up with HPLIP in the name (about 3). Of course you have to set it up (add new printer, and configure) in the CUPS printer management section. I have a scanner/printer combo and It seems to connect better if I try to scan a document first before printing.

[gusfagan]

When will Puppy Linux put an updated hplip package in PPM? It's currently 3.17.10. There have been quite a few printers added since then.

[gusfagan]

When will Puppy Linux put an updated hplip package in PPM? It's currently 3.17.10. There have been quite a few printers added since then.

[pcplague]

In Fossapup 9.5 installed HPLIP version 20 after updating ppm.
In CUPS page in administration there was my printer HP 4200.
Also tested the scanner with Xscale