A Simple Linux Router Upgrade
Apparently as a Christmas present someone cracked into my old router for my home network. It looks like they couldn't do much because of the sparse configuration on that system but I decided it was time for an upgrade.
I was running a Debian distribution from a couple of years ago that I had configured myself to do IP Masquerading and some port mapping. All this on a 486/33 with a 500MB disk. What you might call a set it and forget it system.
Well, the crack inspired me to go for a change. I knew of a few single-floppy routers but had never configured one. This seemed like the perfect chance to try one out because it meant I didn't have to trash to running but insecure current config making it possible to fetch stuff off the net if my first try didn't work.
I decided to go for a quick search on freshmeat and see what was out there. The listings are alphabetical and the first I came to that sounded like it would work was BBIagent.net. This package offers a Linux 2.4.13 kernel, fits on one floppy and includes a form on the web site that you fill out to get your own custom floppy image. To top it all of it would run in 8MB of RAM--an easy fit for my huge 16MB system.
Once you boot it up you configure it remotely using a Java-enabled web browser on your LAN. Sounded secure enough so I went for it. After all, the price was right and it looked like very little work.
The configuration was almost a snap. That is, it was a snap but the first two disks I wrote weren't happy setting up my two 3C509 Ethernet cards. I had been thorough and gave I/O addresses and IRQs.
I decided being dumb was probably the way to go and told the config program I didn't know this info so it should auto-probe. Another boot and it worked like a charm.
Once you configure it from the browser you can save your configuration options to the boot floppy. That's about it. Now I just need to pop the case on the system and unplug the now unused hard drive.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Tech Tip: Really Simple HTTP Server with Python
- Managing Linux Using Puppet
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- SuperTuxKart 0.9.2 Released
- Doing for User Space What We Did for Kernel Space
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide