Linux Does Comics
A few years ago, some friends and I opened a small store selling mostly role-playing games. We stocked many other games and as a sideline some of the partners wanted to sell comics.
A little bit later, after Linux version 0.11 hit the streets, I bought my first home PC. It was a 386/33dx with 120 MB of disk and 20 MB of RAM, and for a while it was just my toy.
Back at the store, comic sales were picking up, and when you sell comics you also take subscriptions. So Tony, one of the partners, started to take lists of comic subscriptions written on paper. When the comics orders came in he would spread out all the new comics on a table and scan each list for titles on the table, and when he saw one he would put it in the subscriptions folder.
Tony started to stress out when there were about 50 people with subscriptions. The time to scan the 50 lists on paper with the 100 comic titles spread out on the table was getting overwhelming. Tony would try to hurry, but then he started to miss comics and make mistakes, and then people would ask why we did not save their comics for them.
At this point one of our less computer-oriented partners, Greg, tried to put the subscriptions on a spreadsheet. He tried to list each customer as a row and each comic title as a column. It did not work, because the spread sheet was too wide to print. At this point I brought in my computer from home, and Greg helped me type in the comic data. I stored each subscription in a separate file. Now the big transformation that was needed was simply to use cat and sort. This turned lists of subscriptions (of titles) into lists of titles (of subscriptions). “The Guys” like hard copy, so they print the list sorted by titles, take each title in turn, find the list of subscriptions for that title on the printout, and put a copy into each comic slot.
My first incarnation of this was written under DOS mostly with DOS-perl. But being a Unix hacker, I missed all the Unix system calls and stuff. After playing a bit more with Linux, and after I installed the first MCC-interim Linux distribution on my PC, I switched the comic system over to Linux.
Now the comics were going to the right customers. We still used the paper pages for users to make changes to their subscriptions, though. And one of us still had to take each page each week and enter the changes into a file and print out the new subscriptions.
After a few months of editing subscription pages it became tiresome and error-prone to make all the customer changes. Customers would come in and ask us where the X-Men titles they signed up for were, and we would check their current list on the computer, and it would not be there, but the paper page where they requested it would be in the book.
I wrote a set of menus with perl (what else) that would let users delete and change their subscriptions online. So far, so good, but we could not allow a customer to add simply anything to their subscription. We could have a customer try to subscribe to something new that we could not get for them, so we had a problem with customers adding things.
My solution was that a customer could add any title that another customer was already getting. At least most of the time, if one customer was getting a copy of some item, getting another copy was not a problem. For this I took the current list of titles of things being asked for and made a file that the user could search through to get to a single item that was desired. This item then could be added to their subscription.
So now customers were able to add something old to their subscription. Now for the new stuff. The comic book distributors we use have a computerized ordering system, so they supply us with a computerized listing of new titles at the beginning of each month. This data is in the form of a DOS disk with a file of one-line entries for each title. Yet another perl script pulls out the new titles and saves them in another file like the current items listing I just talked about. Now the users can search through this file and add new titles to their subscription. The distributers also supply a 300- to 400-page catalog that we give out free to our subscription holders.
There is a two week window each month from when we get the data and the catalogs to the time our customers can add anything from the catalogs to their subscription. After two weeks we make our order to the distributor, so I delete the new titles file, and the menus detect this and no longer let customers add new stuff, so only the current old titles are available after the 15th.
I set up a dumb serial terminal in the front of the store and wrote some menus that would let customers edit their subscription file. Customers can add titles from the distributors' listings or from a list of popular titles. This way a customer cannot add a title we can not get, but he can change the number of each title or the starting and ending issue numbers, as well as delete a title. We have been using this system for nearly two years, and we now have over 200 subscribers managing over 1800 subscriptions on-line with Linux.
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| Designing Electronics with Linux | May 22, 2013 |
| Dynamic DNS—an Object Lesson in Problem Solving | May 21, 2013 |
| Using Salt Stack and Vagrant for Drupal Development | May 20, 2013 |
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
- New Products
- Linux Systems Administrator
- UX Designer
- Senior Perl Developer
- Technical Support Rep
- Web & UI Developer (JavaScript & j Query)
- Designing Electronics with Linux
- RSS Feeds
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using an SMS Server to Provide a Robust Alerting Service for Nagios
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi

It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Featured Jobs
| Linux Systems Administrator | Houston and Austin, Texas | Host Gator |
| Senior Perl Developer | Austin, Texas | Host Gator |
| Technical Support Rep | Houston and Austin, Texas | Host Gator |
| UX Designer | Austin, Texas | Host Gator |
| Web & UI Developer (JavaScript & j Query) | Austin, Texas | Host Gator |
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?




9 hours ago
19 hours 40 min ago
1 day 1 hour ago
1 day 1 hour ago
1 day 3 hours ago
1 day 5 hours ago
1 day 12 hours ago
1 day 12 hours ago
1 day 14 hours ago
1 day 20 hours ago