Horizontal measurement (width) is given first. All measurement units are in inches. The publisher reserves the right to alter any artwork not meeting these specifications, at the advertiser’s expense.
2-page spread (trim size): 16–1/4" x 10–7/8" (16.25" x 10.875")
Full page (trim size): 8–1/8" x 10–7/8" (8.125" x 10.875")
Full page: 7" x 10" (7.0" x 10.0")
1/2 page horizontal: 7" x 4–7/8" (7.0" x 4.875")
1/2 page vertical: 3–1/3" x 10" (3.333" x 10.0")
1/4 page: 3–1/3" x 4–7/8" (3.333" x 4.875")
Marketplace Single 3–3/8" x 2–5/16" (3.375" x 2.3125")
Marketplace Double 3–3/8" x 4–3/4" (3.375" x 4.75")
Marketplace Quad 6–7/8" x 4–3/4" (6.875" x 4.75")
Trim Size: 8-1/8" x 10-7/8"
Bleed Matter: At least 1/8" beyond trim on all sides.
Bleed: Bleeds are allowed on all ad sizes other than 1/4 page or Marketplace.
Electronic File Specifications and Formats
Colors may be CMYK, RGB or grayscale. All color and grayscale images should have a resolution of 300dpi at full size. All 1-bit black & white images should have a resolution of 1200dpi at full size.
EPS: All images must be embedded. All fonts must be converted to curves. The file must be saved with a preview.
PDF: All fonts must be embedded.
TIFF: Must be 300dpi.
For further guidelines, please contact Linux Journal’s production department.
Art and Production
Linux Journal will not be responsible for reproduction quality if materials fail to conform to specifications. Linux Journal reserves the right to reduce oversize material and charge for the service involved. Verbal instructions regarding changes for corrections to advertising materials must be confirmed immediately in writing. Linux Journal will hold materials for one year after the last insertion date, unless advertiser requests their return. All materials are destroyed after one year.
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!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- LiveCode Ltd.'s LiveCode
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