| Link: Rosetta Stone for Unix |
|
Monday, July 18th, 2016 04:22:16 GMT |
Usually I use Puppy Linux. And, reluctantly and relatively rarely, I sometimes use Mac OS.
OR What do they call that in this world?
▲ Top ▼ Bottom △ TOC ↓ Down Up ↑
| Librepup 6.0.2.2 |
|
Friday, November 13th, 2015 20:28:59 GMT |
As usual, I haven't been staying very up to date with most anything going on in the world. So, I didn't find this until today:
And here's the Puppy Linux Discussion Forum thread about Librepup.
I haven't tried Librepup yet, but, wanted to point it out anyway, since I find this Pup particularly notable because I'm not sure if there's any other Puppy or Puppy-based distro (yet) which so strongly emphasizes exclusively free, libre, open source software.
▲ Top ▼ Bottom △ TOC ↓ Down Up ↑
| systemd - probably a bad thing |
|
Thursday, March 19th, 2015 13:56:08 GMT |
Here's an interesting thread I found on the Puppy Linux Discussion Forum:
End of addition.
"systemd" isn't used in Puppy Linux, so no wonder I mostly hadn't encountered stuff about it before.
Except I had recently run across this post on Tumblr, which I didn't understand at the time:
I get the impression from what I've read that "systemd" might be a serious threat to free (as in freedom), libre, open source software.
I don't understand it well enough myself yet to write clearly about it, but, hopefully just pointing out that boycott systemd discussion thread will help raise awareness of the potential problems. That discussion thread is currently 14 pages long and contains a lot of interesting info and links.
Barry Kauler, the creator of Puppy Linux, doesn't like systemd either, according to this blog post from March 2013:
Addition, 3/22/2015, 6:14 PM: And also according to this more recent blog post from Nov. 14, 2014:
I'm still not a Linux expert, and I ought to pay more attention to news in general (not just Linux news)... so, until the past couple hours or so, I wasn't even aware of "systemd" and how bad it is reputed to be, and quite probably actually is, in my opinion.
Anyway, even though I don't fully understand what "systemd" is and all the arguments for and against it, it seems like this is probably a pretty important issue, and thus worth spreading the news about.
And, for people who'd prefer non-technical information on this topic, here's another amusing Tumblr post about "systemd":
| Basic Tips for Using TrueCrypt in Puppy Crypt 4.3 |
|
Friday, February 25th, 2011 19:44:44 GMT |
Tips |
Here are some brief notes on how to use TrueCrypt in the Puppy Crypt 4.3 variant of Puppy Linux. I'm guessing the info in this post probably works (or mostly works) with other types of Linux as well.
First of all, here's a great YouTube video I found that helped me - Install and use TrueCrypt Disk Encryption freeware on Ubuntu & other Linux Distros
That video is by Johnson Yip.
I was initially baffled about how to even locate my encrypted file containers in the Select File window (since you can't just go to the C or D drive).
But, thanks in part to the above video, I wasn't baffled for long.
To mount an encrypted file container in TrueCrypt:
(In case you don't know how to find your encrypted file container - in Puppy Linux, there are icons on the desktop which will allow you to open up your computer's drives (or partitions of drives). Those icons have names like sda2 or sda3 (in my case, those are the C and D partitions of my hard drive) or sdb1 (my USB flash thumb drive), or sr1 (my DVD-RW drive)).
or
Click the Select File button, click File System in the Places list, and click the mnt directory. If the drive (or partition) where you have your TrueCrypt encrypted file container is mounted, it will be listed in that directory, and you can just click on that drive (or partition) and navigate to your encrypted file container.
However, if the drive (or partition) where you have your TrueCrypt encrypted file container isn't listed in the mnt directory already, you'll have to mount it. In Puppy Linux, you can mount drives and partitions just by clicking the desktop icons with names like sda2, sda3, sb1, or sr1. When those drives (or partitions) are mounted, they'll instantly appear in the mnt directory list, and then you'll be able to navigate to your encrypted file container.
(There's also a Linux command to mount things from a command line - the mount command. However, that looks awfully complicated and I don't fully understand that yet. It's much easier to just click the icons to mount your drives and partitions.)
My TrueCrypt encrypted file containers were all created with TrueCrypt for Windows, and happily, they seem to work perfectly with TrueCrypt for Linux as well.
TrueCrypt in Linux looks almost just like TrueCrypt in Windows. The most noticeable difference (at least to me) at a glance is that instead a list of drive letters being shown in the main window, numbers in a column called "Slot" are shown instead.