Changes To Linux Journal
By the time you have reached this page, you may have noticed some changes in the appearance of Linux Journal. The changes are more than skin deep and, in this column, I will let you know what is happening.
The changes have come about both in response to reader feedback and in our attempt to streamline production of the magazine. Up through issue 11, layout was done on a contract basis by an outside person. This interface, both because of the physical location of layout being in a different place than the rest of magazine production and because there was a Macintosh involved, took more time and effort than was practical. With issue 12 we started to move layout in-house and, after a false start or two, we are happy to say all is under control.
Our new layout person is Amy Wood. She has previously worked for a weekly newspaper and the biggest problem we have with her is convincing her that she has a whole month between magazines instead of a week. The layout itself is still done in Quark XPress but it now runs on an MS-Windows system which is connected to our Linux network. The actual interface is handled by Samba (see LJ issue 7 for more info on Samba) and is transparent to Amy. For the rest of us, it means that files can be sent to and from that system without the need for sneaker-net. (In a future issue we will have an article on how Linux Journal is produced using mostly Linux systems.)
Because Amy had so much extra time after finishing up issue 13 she looked at the assorted comments about our layout and along with her own ideas, came up with the current layout. The major changes you should notice are a cleanup of the page format and the addition of “continued-from” lines on the continuation pages of articles which include a keyword so you know what article you are reading. Also, she is putting a lot of effort into minimizing the number of jumps within articles. Please let us know what you think of her work.
The second big change is still under way but should be done by the time you read this. We have established a WWW site, www.ssc.com. As well as having information on SSC products, we will be putting up information from Linux Journal. First we will put up the tables of contents and advertisers indices and then add some of the articles from the magazine. Advertisers can request links from their index entry to their web page and, if they don't have their own web site, for a nominal fee we will put their web pages on www.ssc.com. If you are an advertiser and need more information on this, contact Carlie Fairchild at (206) 782-7733.
As well as SSC and Linux Journal information, we will have some general Linux information on the site so if you are looking for something to browse try www.ssc.com. This is, of course, a Linux machine. If there are things you think should be added to the site, send e-mail to firstname.lastname@example.org.
Finally, with Linux 1.2 out there, more commercial vendors are starting to take Linux seriously. If you see anyone with a commercial interest in Linux, whether it is a vendor interested in making their product work with Linux or a company that is using Linux, please point them our way. The more information of commercial interest we can get in LJ, the easier it is for us to convince others that Linux is a viable alternative to other operating systems.
|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|
- RSS Feeds
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Designing Electronics with Linux
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- A Topic for Discussion - Open Source Feature-Richness?
- Drupal Is a Framework: Why Everyone Needs to Understand This
- Validate an E-Mail Address with PHP, the Right Way
- What's the tweeting protocol?
- Kernel Problem
9 hours 24 min ago
- BASH script to log IPs on public web server
13 hours 51 min ago
17 hours 27 min ago
- Reply to comment | Linux Journal
17 hours 59 min ago
- All the articles you talked
20 hours 23 min ago
- All the articles you talked
20 hours 26 min ago
- All the articles you talked
20 hours 27 min ago
1 day 52 min ago
- Keeping track of IP address
1 day 2 hours ago
- Roll your own dynamic dns
1 day 7 hours ago
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!
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?