In this case, '~' is mounted as the home directory. It's where all the Puppy OS 'stuff' lives.the main Tahr64 SFS file, vmlinuz (the kernel), initrd.gz (Puppy's compressed virtual file-system).stuff like that. Mnt/home is the 'base' level of the partition where Puppy is installed (in this case your USB drive).
This is Puppy's 'home' directory.but it's not the 'home' you're looking for. No, you'll find that anything with the 'squiggle' (as I call it!), refers to /root. I doubt you're any worse than most of us were when we first started we all have to take small steps to begin with, until you become more confident.! TheScorpion wrote:I'm pretty dumb when it comes to Linux. Keepass.png PNG icon for KeePass (7.11 KiB) Downloaded 759 times KeePass-MenuEntry.pet MenuEntry for KeePass password manager. You can edit the name, if you want, and/or give it an icon. (Or, if you want, just drag it onto the desktop, where it'll act as its own 'launcher'.
#Keepass for linux install
If you place the AppImage in /mnt/home, then install the attached MenuEntry.pet, this will keep it outside of 'Puppyspace' (your save-file/folder), and allow you to start it from the Menu.
It'll unpack itself into /tmp for the duration, and, all things being equal, will run from there. Tick off the three 'execute' checkboxes, then click 'Refresh'. And it doesn't want to play ball with the 32-bit lib, naturally! As with so many current applications, it's been compiled to want the very newest of everything.Įven the newest mainstream releases, although they provide a 64-bit package, it appears to contain a 32-bit binary. Everybody has a 32-bit package for this, but I could not find one single 64-bit version anywhere. I tried re-building the package step provided from FatDog64 (it needed a fair few extremely new Qt5 modules), but I came unstuck on libicui18n.so.57. The official KeePass AppImage works OOTB in Tahr64.
0 kommentar(er)
