How To Install Puppy Linux Tahr On A USB Drive


Puppy Linux is a lightweight Linux distribution designed to run from removable devices such as DVDs and USB drives.
There are a number of Puppy Linux variants including Puppy Slacko, which utilises the Slackware repositories, and Puppy Tahr which utilises the Ubuntu repositories.
Other versions of Puppy Linux include Simplicity and MacPUP.
It is possible to use UNetbootin to create a bootable Puppy Linux USB drive but it isn't the method that is recommended.
Puppy Linux works great on older laptops, netbooks and computers without hard drives. It isn't designed to be installed on a hard drive but you can run it that way if you want to.
-
- Login or register to post comments
Printer-friendly version
- 6442 reads
PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
3 Helpful Networking Projects for Your Raspberry Pi
In spite of being a beloved companion to computer hobbyists the world over, the Raspberry Pi doesn’t get enough credit. In fact, single-board computers of all stripes haven’t gotten their due — I just happen to have a Raspberry Pi. It was upon casting a stray glance into the corner of my room where my Pi is, churning away on the previous task I assigned it, that I pondered all the loftier projects I have in mind for it.
It will probably be a while before I tackle those grand designs. But the next best thing to following my dreams is to share them. The ideas here are charcoal sketches, not full illustrations, but they yield a rough picture.
I should also note that these projects all contain Linux in their blueprints (shocking, I know). As this is the preliminary stage, we can leave the exact distribution blank for now. You can safely trust, though, that any services we might need our Pi to run will fasten flush onto a Linux base.
| GNU Radio 3.9.0.0 released
Dear SDR community most likely to travel in time to save the present, The future is not set, there is no fate but what we make for ourselves. In this very spirit, GNU Radio 3.9 packs a whole bunch of power when it comes to transforming the way GNU Radio and its ecosytem can be developed in the future. You'll find the release tags and signed tarballs now on github, and later on https://www.gnuradio.org/releases/gnuradio/ . Not only did we have great progressions from old dependencies that proved to be all too problematic (SWIG, Python2), but also did we see an incredibly influx of people actively working on how maintainable this code base is. This will nurture the project for years to come. All in all, the main breaking change for pure GRC users will consist in a few changed blocks – an incredible feat, considering the amount of shift under the hood. Mentioning large shifts, the work that went into the PyBind binding, the CMake modernization, the C++ cleanup, the bug-fixing and the CI infrastructure is worthy of explicit call out; I especially thank * Josh Morman * Thomas Habets * Jacob Gilbert * Andrej Rode * Ryan Volz here. For developers of OOTs, I'm sure PyBind11 will pose a surprise. If you're used to SWIG, yes, that's more code to write yourself. But in effect, it's less code that breaks, and when it breaks, it breaks in much more understandable ways. Josh has put a lot of effort into automating as much of that as possible. There's certainly no shortage of demand for that! The ecosystem (remember GNU Radio's tagline?) is in a steady upwind. We've seen more, and more stable, contributions from OOT maintainers. That's great! For in-tree development, newer dependencies and removal of anachronisms will make sure things move much smoother. Our CI is getting – lately literally every day – better, which means we not only catch bugs earlier, but also allow for much quicker review cycles. One central change: If you're contributing code upstream, we no longer need you to submit a CLA; instead, we ask you to just certify, yourself, that you're allowed to contribute that code (and not, e.g. misappropriating someone else's code). That's what the DCO (Developer Certificate of Origin) is: Just a quick, "hey, this code is actually for me to contribute under the project's license"; nothing more. ![]() |
Android Leftovers
| ncmpcpp – featureful ncurses based MPD client inspired by ncmpc
Linux offers a huge array of open source music players. And many of them are high quality. I’ve reviewed the vast majority for LinuxLinks, but I’m endeavoring to explore every free music player in case there’s an undiscovered gem.
MPD is a powerful server-side application for playing music. In a home environment, you can connect an MPD server to a Hi-Fi system, and control the server using a notebook or smartphone. You can, of course, play audio files on remote clients. MPD can be started system-wide or on a per-user basis.
I’ve covered a fair few MPD clients over the past year or so including Cantata, Ymuse, mpdevil, ympd, myMPD, ampd, ncmpy, and ncmpc. My favorite of them is Cantata although Ymuse is a simple alternative. There’s lots of differences between these front-ends. For example, Cantata uses the Qt widget set, whereas Ymuse and mpdevil offer a GTK front-end. ympd, myMPD and ampd are web-based clients. And ncmpy and ncmpc are terminal-based clients. So there’s something for everyone.
ncmpcpp is a terminal-based MPD client with a user interface that seeks inspiration from ncmpc and shares a lot of similarities. But it adds some useful features. Let’s check it out. Before doing so, here’s the obligatory installation section.
|
Recent comments
13 min 36 sec ago
19 min 14 sec ago
1 hour 30 min ago
2 hours 15 min ago
2 hours 50 min ago
5 hours 51 min ago
8 hours 3 min ago
8 hours 21 min ago
14 hours 52 min ago
15 hours 18 min ago