Slashdot Mirror

kthreadd writes: 15 years after the release of CUPS 1.0, Apple has now released version 2.0 of the printing system for GNU/Linux and other Unix-style operating systems. One of the major new features in 2.0 is that the test program for ippserver now passes the IPP Everywhere self-certification tests. Also, they've made an interesting blog post looking at the past and future of printing. Since the first major release in 1999, printing has become much more personal. Printer drivers are going away, and mobile usage is now the norm."

kthreadd writes: 15 years after the release of CUPS 1.0, Apple has now released version 2.0 of the printing system for GNU/Linux and other Unix-style operating systems. One of the major new features in 2.0 is that the test program for ippserver now passes the IPP Everywhere self-certification tests. Also, they've made an interesting blog post looking at the past and future of printing. Since the first major release in 1999, printing has become much more personal. Printer drivers are going away, and mobile usage is now the norm."

kthreadd writes: 15 years after the release of CUPS 1.0, Apple has now released version 2.0 of the printing system for GNU/Linux and other Unix-style operating systems. One of the major new features in 2.0 is that the test program for ippserver now passes the IPP Everywhere self-certification tests. Also, they've made an interesting blog post looking at the past and future of printing. Since the first major release in 1999, printing has become much more personal. Printer drivers are going away, and mobile usage is now the norm."

Rick Richardson writes to note a posting on cups.org that reveals that Apple, which in 2002 first licensed CUPS for printing in OS X, purchased the source code last February and hired its main developer, Michael R. Sweet. Sweet writes: "CUPS will still be released under the existing GPL2/LGPL2 licensing terms, and I will continue to develop and support CUPS at Apple." There are no comments on the post. What exactly did Apple purchase? It was and is an open source project. Trademarks aren't mentioned.

linuxtag-reporter writes "The first day of LinuxTag, Europe's biggest Free Software event (expecting 25,000 visitors) already has one big highlight. It seems that Fabian Franz from the Knoppix Project hacked up a 'FreeNX Server' based on NoMachine's NX technology (poor NoMachine might lose business now). Fabian Franz presented a first preview of the 'GPL Edition' in a live demo together with Kurt Pfeifle. The demo showed sessions going from Germany to Italy just based on a slow WLAN connectivity (shared with hundreds of visitors). A connection lost due to bad network conditions was easily re-connected to, and a deliberately suspended session was revitalized too -- it was just like 'screen' with a GUI! A report on the official LinuxTag webpage says FreeNX will be publically released for the first time as part of the upcoming Knoppix-3.6 release. The Kalyxo project is building and hosting Debian packages of FreeNX and NX/GPL for everyone to use."

Bootsy Collins writes "Using the recent experience of trying to configure CUPS on his home network, Eric Raymond has written an interesting new screed on poor design of user interfaces in general, and configuration interfaces in particular, in open source software, entitled The Luxury of Ignorance. A sample quote: 'This kind of fecklessness is endemic in open-source land. And it's what's keeping Microsoft in business -- because by Goddess, they may write crappy insecure overpriced shoddy software, but on this one issue their half-assed semi-competent best is an order of magnitude better than we usually manage.'"

McSnarf writes "What is CUPS, anyhow? And does it make sense to buy a book about a GPLed piece of software? CUPS is an acronym for Common Unix Printing System, software that was written to replace the rather powerless printing system found in Unix and Linux. If you run any current Linux distro, the chances are that you already use CUPS for printing." That being the case, read on for McSnarf's review of Michael R. Sweet's book on the topic. CUPS - Common Unix Printing System author Michael R. Sweet pages 650 publisher SAMS Publishing rating 10 reviewer McSnarf ISBN 0672321963 summary More than just a complete reference to CUPS

Background Information CUPS is developed and maintained by Easy Software Products, which is co-owned by the author of the book, Mike Sweet.

The complete table of contents for CUPS - Common Unix Printing System, aka "The Octopus Book" can be found here. The CUPS web site also contains errata lists and example code. In addition, Easy Software Products sells a companion CD for the book, only available on their web site.

Who should read it? If you do not use a printer with Unix or Linux, or if you do and you are perfectly happy with the results (maybe because the distro came with all the right stuff pre-installed), this book is not for you.

However, if you are serious about printing, if you are considering replacing the outdated legacy printing system that came with your Unix or Linux or if you are a developer even remotely interested in Linux/Unix printing, this book is for you.

Did I mention that the Octopus Book is also very helpful when it comes to understanding IPP, the Internet Printing Protocol? If you tried to read through all the RFCs on IPP out there and managed to understand IPP afterwards -- congratulations! I tried that, failed, bought the Octopus Book and finally understood.

How will it help users and admins? This book will show you how to install, administer and use CUPS. While the documentation that comes with CUPS is very good already, having everything in one handy package has its advantages, especially as the book goes into more detail than the on-line documentation. In addition, this book will explain to you in great detail how to extend CUPS. If you've ever wanted to be able to directly print some rather unusual file type -- or need a mechanism to create PDF files and email a copy of each PDF whenever you print them to a certain printer, this book will tell you how to do that.

Anything for developers? Sure. Complete API documentation with loads of example code. Everything from "How can I add good printing support to my application" to "How do I write a printer driver?" is in there. Likes and dislikes Of course, no book is perfect. This book comes close, but you should know that a lot of it is already available for free on the CUPS web site. It also lacks details on how to rip the old printing system out of your legacy Unix -- but if you've got root, this is something you should know anyhow.

Another thing - it is not as funny as Terry Pratchett. But I can live with that.

As you might have noticed, I really like this book. It definitely made my work much easier -- I work for a manufacturer of (among other things) large printers and this (by now well-worn) book has been granted dedicated space on a very crowded desktop.

You can purchase CUPS - Common Unix Printing System from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

McSnarf writes "What is CUPS, anyhow? And does it make sense to buy a book about a GPLed piece of software? CUPS is an acronym for Common Unix Printing System, software that was written to replace the rather powerless printing system found in Unix and Linux. If you run any current Linux distro, the chances are that you already use CUPS for printing." That being the case, read on for McSnarf's review of Michael R. Sweet's book on the topic. CUPS - Common Unix Printing System author Michael R. Sweet pages 650 publisher SAMS Publishing rating 10 reviewer McSnarf ISBN 0672321963 summary More than just a complete reference to CUPS

Background Information CUPS is developed and maintained by Easy Software Products, which is co-owned by the author of the book, Mike Sweet.

The complete table of contents for CUPS - Common Unix Printing System, aka "The Octopus Book" can be found here. The CUPS web site also contains errata lists and example code. In addition, Easy Software Products sells a companion CD for the book, only available on their web site.

Who should read it? If you do not use a printer with Unix or Linux, or if you do and you are perfectly happy with the results (maybe because the distro came with all the right stuff pre-installed), this book is not for you.

However, if you are serious about printing, if you are considering replacing the outdated legacy printing system that came with your Unix or Linux or if you are a developer even remotely interested in Linux/Unix printing, this book is for you.

Did I mention that the Octopus Book is also very helpful when it comes to understanding IPP, the Internet Printing Protocol? If you tried to read through all the RFCs on IPP out there and managed to understand IPP afterwards -- congratulations! I tried that, failed, bought the Octopus Book and finally understood.

How will it help users and admins? This book will show you how to install, administer and use CUPS. While the documentation that comes with CUPS is very good already, having everything in one handy package has its advantages, especially as the book goes into more detail than the on-line documentation. In addition, this book will explain to you in great detail how to extend CUPS. If you've ever wanted to be able to directly print some rather unusual file type -- or need a mechanism to create PDF files and email a copy of each PDF whenever you print them to a certain printer, this book will tell you how to do that.

Anything for developers? Sure. Complete API documentation with loads of example code. Everything from "How can I add good printing support to my application" to "How do I write a printer driver?" is in there. Likes and dislikes Of course, no book is perfect. This book comes close, but you should know that a lot of it is already available for free on the CUPS web site. It also lacks details on how to rip the old printing system out of your legacy Unix -- but if you've got root, this is something you should know anyhow.

Another thing - it is not as funny as Terry Pratchett. But I can live with that.

As you might have noticed, I really like this book. It definitely made my work much easier -- I work for a manufacturer of (among other things) large printers and this (by now well-worn) book has been granted dedicated space on a very crowded desktop.

You can purchase CUPS - Common Unix Printing System from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

McSnarf writes "What is CUPS, anyhow? And does it make sense to buy a book about a GPLed piece of software? CUPS is an acronym for Common Unix Printing System, software that was written to replace the rather powerless printing system found in Unix and Linux. If you run any current Linux distro, the chances are that you already use CUPS for printing." That being the case, read on for McSnarf's review of Michael R. Sweet's book on the topic. CUPS - Common Unix Printing System author Michael R. Sweet pages 650 publisher SAMS Publishing rating 10 reviewer McSnarf ISBN 0672321963 summary More than just a complete reference to CUPS

Background Information CUPS is developed and maintained by Easy Software Products, which is co-owned by the author of the book, Mike Sweet.

The complete table of contents for CUPS - Common Unix Printing System, aka "The Octopus Book" can be found here. The CUPS web site also contains errata lists and example code. In addition, Easy Software Products sells a companion CD for the book, only available on their web site.

Who should read it? If you do not use a printer with Unix or Linux, or if you do and you are perfectly happy with the results (maybe because the distro came with all the right stuff pre-installed), this book is not for you.

However, if you are serious about printing, if you are considering replacing the outdated legacy printing system that came with your Unix or Linux or if you are a developer even remotely interested in Linux/Unix printing, this book is for you.

Did I mention that the Octopus Book is also very helpful when it comes to understanding IPP, the Internet Printing Protocol? If you tried to read through all the RFCs on IPP out there and managed to understand IPP afterwards -- congratulations! I tried that, failed, bought the Octopus Book and finally understood.

How will it help users and admins? This book will show you how to install, administer and use CUPS. While the documentation that comes with CUPS is very good already, having everything in one handy package has its advantages, especially as the book goes into more detail than the on-line documentation. In addition, this book will explain to you in great detail how to extend CUPS. If you've ever wanted to be able to directly print some rather unusual file type -- or need a mechanism to create PDF files and email a copy of each PDF whenever you print them to a certain printer, this book will tell you how to do that.

Anything for developers? Sure. Complete API documentation with loads of example code. Everything from "How can I add good printing support to my application" to "How do I write a printer driver?" is in there. Likes and dislikes Of course, no book is perfect. This book comes close, but you should know that a lot of it is already available for free on the CUPS web site. It also lacks details on how to rip the old printing system out of your legacy Unix -- but if you've got root, this is something you should know anyhow.

Another thing - it is not as funny as Terry Pratchett. But I can live with that.

As you might have noticed, I really like this book. It definitely made my work much easier -- I work for a manufacturer of (among other things) large printers and this (by now well-worn) book has been granted dedicated space on a very crowded desktop.

You can purchase CUPS - Common Unix Printing System from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

McSnarf writes "What is CUPS, anyhow? And does it make sense to buy a book about a GPLed piece of software? CUPS is an acronym for Common Unix Printing System, software that was written to replace the rather powerless printing system found in Unix and Linux. If you run any current Linux distro, the chances are that you already use CUPS for printing." That being the case, read on for McSnarf's review of Michael R. Sweet's book on the topic. CUPS - Common Unix Printing System author Michael R. Sweet pages 650 publisher SAMS Publishing rating 10 reviewer McSnarf ISBN 0672321963 summary More than just a complete reference to CUPS

Background Information CUPS is developed and maintained by Easy Software Products, which is co-owned by the author of the book, Mike Sweet.

The complete table of contents for CUPS - Common Unix Printing System, aka "The Octopus Book" can be found here. The CUPS web site also contains errata lists and example code. In addition, Easy Software Products sells a companion CD for the book, only available on their web site.

Who should read it? If you do not use a printer with Unix or Linux, or if you do and you are perfectly happy with the results (maybe because the distro came with all the right stuff pre-installed), this book is not for you.

However, if you are serious about printing, if you are considering replacing the outdated legacy printing system that came with your Unix or Linux or if you are a developer even remotely interested in Linux/Unix printing, this book is for you.

Did I mention that the Octopus Book is also very helpful when it comes to understanding IPP, the Internet Printing Protocol? If you tried to read through all the RFCs on IPP out there and managed to understand IPP afterwards -- congratulations! I tried that, failed, bought the Octopus Book and finally understood.

How will it help users and admins? This book will show you how to install, administer and use CUPS. While the documentation that comes with CUPS is very good already, having everything in one handy package has its advantages, especially as the book goes into more detail than the on-line documentation. In addition, this book will explain to you in great detail how to extend CUPS. If you've ever wanted to be able to directly print some rather unusual file type -- or need a mechanism to create PDF files and email a copy of each PDF whenever you print them to a certain printer, this book will tell you how to do that.

Anything for developers? Sure. Complete API documentation with loads of example code. Everything from "How can I add good printing support to my application" to "How do I write a printer driver?" is in there. Likes and dislikes Of course, no book is perfect. This book comes close, but you should know that a lot of it is already available for free on the CUPS web site. It also lacks details on how to rip the old printing system out of your legacy Unix -- but if you've got root, this is something you should know anyhow.

Another thing - it is not as funny as Terry Pratchett. But I can live with that.

As you might have noticed, I really like this book. It definitely made my work much easier -- I work for a manufacturer of (among other things) large printers and this (by now well-worn) book has been granted dedicated space on a very crowded desktop.

You can purchase CUPS - Common Unix Printing System from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

McSnarf writes "What is CUPS, anyhow? And does it make sense to buy a book about a GPLed piece of software? CUPS is an acronym for Common Unix Printing System, software that was written to replace the rather powerless printing system found in Unix and Linux. If you run any current Linux distro, the chances are that you already use CUPS for printing." That being the case, read on for McSnarf's review of Michael R. Sweet's book on the topic. CUPS - Common Unix Printing System author Michael R. Sweet pages 650 publisher SAMS Publishing rating 10 reviewer McSnarf ISBN 0672321963 summary More than just a complete reference to CUPS

Background Information CUPS is developed and maintained by Easy Software Products, which is co-owned by the author of the book, Mike Sweet.

The complete table of contents for CUPS - Common Unix Printing System, aka "The Octopus Book" can be found here. The CUPS web site also contains errata lists and example code. In addition, Easy Software Products sells a companion CD for the book, only available on their web site.

Who should read it? If you do not use a printer with Unix or Linux, or if you do and you are perfectly happy with the results (maybe because the distro came with all the right stuff pre-installed), this book is not for you.

However, if you are serious about printing, if you are considering replacing the outdated legacy printing system that came with your Unix or Linux or if you are a developer even remotely interested in Linux/Unix printing, this book is for you.

Did I mention that the Octopus Book is also very helpful when it comes to understanding IPP, the Internet Printing Protocol? If you tried to read through all the RFCs on IPP out there and managed to understand IPP afterwards -- congratulations! I tried that, failed, bought the Octopus Book and finally understood.

How will it help users and admins? This book will show you how to install, administer and use CUPS. While the documentation that comes with CUPS is very good already, having everything in one handy package has its advantages, especially as the book goes into more detail than the on-line documentation. In addition, this book will explain to you in great detail how to extend CUPS. If you've ever wanted to be able to directly print some rather unusual file type -- or need a mechanism to create PDF files and email a copy of each PDF whenever you print them to a certain printer, this book will tell you how to do that.

Anything for developers? Sure. Complete API documentation with loads of example code. Everything from "How can I add good printing support to my application" to "How do I write a printer driver?" is in there. Likes and dislikes Of course, no book is perfect. This book comes close, but you should know that a lot of it is already available for free on the CUPS web site. It also lacks details on how to rip the old printing system out of your legacy Unix -- but if you've got root, this is something you should know anyhow.

Another thing - it is not as funny as Terry Pratchett. But I can live with that.

As you might have noticed, I really like this book. It definitely made my work much easier -- I work for a manufacturer of (among other things) large printers and this (by now well-worn) book has been granted dedicated space on a very crowded desktop.

You can purchase CUPS - Common Unix Printing System from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

McSnarf writes "What is CUPS, anyhow? And does it make sense to buy a book about a GPLed piece of software? CUPS is an acronym for Common Unix Printing System, software that was written to replace the rather powerless printing system found in Unix and Linux. If you run any current Linux distro, the chances are that you already use CUPS for printing." That being the case, read on for McSnarf's review of Michael R. Sweet's book on the topic. CUPS - Common Unix Printing System author Michael R. Sweet pages 650 publisher SAMS Publishing rating 10 reviewer McSnarf ISBN 0672321963 summary More than just a complete reference to CUPS

Background Information CUPS is developed and maintained by Easy Software Products, which is co-owned by the author of the book, Mike Sweet.

The complete table of contents for CUPS - Common Unix Printing System, aka "The Octopus Book" can be found here. The CUPS web site also contains errata lists and example code. In addition, Easy Software Products sells a companion CD for the book, only available on their web site.

Who should read it? If you do not use a printer with Unix or Linux, or if you do and you are perfectly happy with the results (maybe because the distro came with all the right stuff pre-installed), this book is not for you.

However, if you are serious about printing, if you are considering replacing the outdated legacy printing system that came with your Unix or Linux or if you are a developer even remotely interested in Linux/Unix printing, this book is for you.

Did I mention that the Octopus Book is also very helpful when it comes to understanding IPP, the Internet Printing Protocol? If you tried to read through all the RFCs on IPP out there and managed to understand IPP afterwards -- congratulations! I tried that, failed, bought the Octopus Book and finally understood.

How will it help users and admins? This book will show you how to install, administer and use CUPS. While the documentation that comes with CUPS is very good already, having everything in one handy package has its advantages, especially as the book goes into more detail than the on-line documentation. In addition, this book will explain to you in great detail how to extend CUPS. If you've ever wanted to be able to directly print some rather unusual file type -- or need a mechanism to create PDF files and email a copy of each PDF whenever you print them to a certain printer, this book will tell you how to do that.

Anything for developers? Sure. Complete API documentation with loads of example code. Everything from "How can I add good printing support to my application" to "How do I write a printer driver?" is in there. Likes and dislikes Of course, no book is perfect. This book comes close, but you should know that a lot of it is already available for free on the CUPS web site. It also lacks details on how to rip the old printing system out of your legacy Unix -- but if you've got root, this is something you should know anyhow.

Another thing - it is not as funny as Terry Pratchett. But I can live with that.

As you might have noticed, I really like this book. It definitely made my work much easier -- I work for a manufacturer of (among other things) large printers and this (by now well-worn) book has been granted dedicated space on a very crowded desktop.

You can purchase CUPS - Common Unix Printing System from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

McSnarf writes "What is CUPS, anyhow? And does it make sense to buy a book about a GPLed piece of software? CUPS is an acronym for Common Unix Printing System, software that was written to replace the rather powerless printing system found in Unix and Linux. If you run any current Linux distro, the chances are that you already use CUPS for printing." That being the case, read on for McSnarf's review of Michael R. Sweet's book on the topic. CUPS - Common Unix Printing System author Michael R. Sweet pages 650 publisher SAMS Publishing rating 10 reviewer McSnarf ISBN 0672321963 summary More than just a complete reference to CUPS

Background Information CUPS is developed and maintained by Easy Software Products, which is co-owned by the author of the book, Mike Sweet.

The complete table of contents for CUPS - Common Unix Printing System, aka "The Octopus Book" can be found here. The CUPS web site also contains errata lists and example code. In addition, Easy Software Products sells a companion CD for the book, only available on their web site.

Who should read it? If you do not use a printer with Unix or Linux, or if you do and you are perfectly happy with the results (maybe because the distro came with all the right stuff pre-installed), this book is not for you.

However, if you are serious about printing, if you are considering replacing the outdated legacy printing system that came with your Unix or Linux or if you are a developer even remotely interested in Linux/Unix printing, this book is for you.

Did I mention that the Octopus Book is also very helpful when it comes to understanding IPP, the Internet Printing Protocol? If you tried to read through all the RFCs on IPP out there and managed to understand IPP afterwards -- congratulations! I tried that, failed, bought the Octopus Book and finally understood.

How will it help users and admins? This book will show you how to install, administer and use CUPS. While the documentation that comes with CUPS is very good already, having everything in one handy package has its advantages, especially as the book goes into more detail than the on-line documentation. In addition, this book will explain to you in great detail how to extend CUPS. If you've ever wanted to be able to directly print some rather unusual file type -- or need a mechanism to create PDF files and email a copy of each PDF whenever you print them to a certain printer, this book will tell you how to do that.

Anything for developers? Sure. Complete API documentation with loads of example code. Everything from "How can I add good printing support to my application" to "How do I write a printer driver?" is in there. Likes and dislikes Of course, no book is perfect. This book comes close, but you should know that a lot of it is already available for free on the CUPS web site. It also lacks details on how to rip the old printing system out of your legacy Unix -- but if you've got root, this is something you should know anyhow.

Another thing - it is not as funny as Terry Pratchett. But I can live with that.

As you might have noticed, I really like this book. It definitely made my work much easier -- I work for a manufacturer of (among other things) large printers and this (by now well-worn) book has been granted dedicated space on a very crowded desktop.

You can purchase CUPS - Common Unix Printing System from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

bmeteor writes: "Short and very sweet: CUPS is licensed by Apple. A boon for both Apple and GNU." CUPS (Common UNIX Printing System) is a system based on the Internet Printing Protocol for standardized printing on Unix systems. That's nice, but when can I print over the network to my Epson inkjet, like I can in Mac OS 9 with USB Printer Sharing?

Clinton Work asks: "There are tons of cheap/high quality inkjet printers on the market, but all of them use proprietary Windows printer drivers. The older HP inkjets have Linux drivers but are no longer on the market. Your only option is too choose a more expensive inkjet or a cheap laser printer with postscript support. I have looked at the modern printing software like LPRng and CUPS without any luck. Does anybody have a solution?"

Updates on Tom's detective work, Kevin's touchy look-but-don't touch semi-citizen status, and last but not least a word from the elusive printman, here folded, spindled and mutilated for your edification.

Danke sehr, Herr Doktor Pabst! The sighs -- nay, screams! -- of disappointment rose like the wail of a cat in heat following the announcement that AMD's new chips would be clock-locked, nullifying the advantages of Abit's ultra-overclockable motherboard. Jonathan Dabian writes: "This is probably a little late for me to get the name postage on the front page, but Tom's Hardware posted a new story that is an update to the Monday Blurb where they revealed that the new AMD processors would be multiplier locked. In this new story, Tom Pabst reveals the information he has since pieced together about the connections on the top of the processor, and ideas on how to alter those laser etched connections. Overclocking on the Duron and Thunderbird isn't dead. All that's needed is an easy way to alter those connections."

How do you like your quasi-futuristic clothing, Mr. Mitnick? One of the many following the bizarre turns of the Kevin Mitnick saga, RadarRider writes: "According to the following article on MSNBC:' Reversing a previous decision, Kevin Mitnick?s probation officer has given the notorious computer intruder permission to lecture on hacking and cracking, work as a security consultant and write a column for a soon-to-be-launched e-commerce site.'"

Disallowing use of computers unless specially granted seems a fairly over-the-top punishment -- everything has embedded processors. I wonder if Kevin has to ask permission to use an infrared-type automatic toilet, or a programmable thermostat. Where's King Solomon when you need him?

Unca Steve, Unca Steve! Tell us a bedtime story, OK? Speaking of *ashback, gwernol writes: "There's a fascinating letter from Woz - one of the co-founders of Apple on his web page at woz.org. Its a candid glimpse into the early days of the computer world, including tales of hacking the world's first video games -Pong and Breakout - at Atari. See inside the mind of one of the truly great ones. Some interesting perspective on Steve Jobs, too."

(Hint: some of the same words you can't say on television are off-limits to mass-market video games, too!)

Now I can print up dozens of tasty eclaires under Linux! If you followed the recent story about modernizing UNIX printing standards, you may have caught the news that CUPS 1.1 has been released. Here's some more information from the horse's mouth. printman writes: "Nine months after the CUPS 1.0 release, we are proud the announce the birth of CUPS 1.1, with documentation nearly 500 pages long and distributions weighing in at around 4MB.

"What is CUPS", you ask? The Common UNIX Printing System ("CUPS") is an IPP-based printing system developed by Easy Software Products as a replacement for the aging and clunky Berkeley (LPD) and System V printing systems. CUPS provides all of the modern printing ammenities, including support for user-defined printers and options, non-PostScript printers, color management, and page accounting.

CUPS 1.1 continues our commitment to an open-sourced, IPP-based printing system for all UNIX's. The new release contains many of the functional enhancements that have been requested by our users, including:

1. New USB backend and backend device discovery.
2. Banner page support
3. Digest authentication
4. Directory service enhancements, including polling, relaying, and access control
5. Directory structure changes to conform to the FHS 2.0 standard used by most Linux distributions.
6. Documentation improvements and additions
7. Drivers for EPSON printers
8. Filters - new PostScript RIP based on GNU Ghostscript 5.50 core, new PDF filter based on Xpdf, new text filter supporting Unicode and bidirectional text
9. IPP/1.1 support
10. Job persistence & history
11. Licensing change - the CUPS API is now provided under the GNU LGPL
12. LPD client support
13. User-defined printers and options
14. Web administration interface

In addition we have contributed more new code to the SAMBA team to support CUPS printing "natively" via IPP, providing a faster, more reliable Windows printing experience.

Others have also been busy at work adding to CUPS. Besides our ESP Print Pro software, two new graphical interfaces have appeared for CUPS - KUPS is a KDE-based interface for CUPS, and XPP is a FLTK-based interface for CUPS.

On the driver front, Grant Taylor has come up with CUPS-o-matic, a PPD file generator and filter script for existing Ghostscript printer drivers, and the GIMP print plug-in developers are working towards "universal" drivers for GIMP, Ghostscript, and CUPS.

Finally, many Linux distributions are including (or planning to include) CUPS or ESP Print Pro. This should provide the final push to get printer manufacturers to support their printers under Linux and *BSD.

For more information on CUPS, go to: www.cups.org

And for bonus points ... Katsu Jin Ken writes: "Indrema has posted a new picture of their upcoming console on their front page." It's looking a lot svelter and sleeker than the old look, and like the finest computers everywhere, features a blue LED. (On the other hand, beware the rude no-exit site design.) Please, Indrema, make it so!

Updates on Tom's detective work, Kevin's touchy look-but-don't touch semi-citizen status, and last but not least a word from the elusive printman, here folded, spindled and mutilated for your edification.

Danke sehr, Herr Doktor Pabst! The sighs -- nay, screams! -- of disappointment rose like the wail of a cat in heat following the announcement that AMD's new chips would be clock-locked, nullifying the advantages of Abit's ultra-overclockable motherboard. Jonathan Dabian writes: "This is probably a little late for me to get the name postage on the front page, but Tom's Hardware posted a new story that is an update to the Monday Blurb where they revealed that the new AMD processors would be multiplier locked. In this new story, Tom Pabst reveals the information he has since pieced together about the connections on the top of the processor, and ideas on how to alter those laser etched connections. Overclocking on the Duron and Thunderbird isn't dead. All that's needed is an easy way to alter those connections."

How do you like your quasi-futuristic clothing, Mr. Mitnick? One of the many following the bizarre turns of the Kevin Mitnick saga, RadarRider writes: "According to the following article on MSNBC:' Reversing a previous decision, Kevin Mitnick?s probation officer has given the notorious computer intruder permission to lecture on hacking and cracking, work as a security consultant and write a column for a soon-to-be-launched e-commerce site.'"

Disallowing use of computers unless specially granted seems a fairly over-the-top punishment -- everything has embedded processors. I wonder if Kevin has to ask permission to use an infrared-type automatic toilet, or a programmable thermostat. Where's King Solomon when you need him?

Unca Steve, Unca Steve! Tell us a bedtime story, OK? Speaking of *ashback, gwernol writes: "There's a fascinating letter from Woz - one of the co-founders of Apple on his web page at woz.org. Its a candid glimpse into the early days of the computer world, including tales of hacking the world's first video games -Pong and Breakout - at Atari. See inside the mind of one of the truly great ones. Some interesting perspective on Steve Jobs, too."

(Hint: some of the same words you can't say on television are off-limits to mass-market video games, too!)

Now I can print up dozens of tasty eclaires under Linux! If you followed the recent story about modernizing UNIX printing standards, you may have caught the news that CUPS 1.1 has been released. Here's some more information from the horse's mouth. printman writes: "Nine months after the CUPS 1.0 release, we are proud the announce the birth of CUPS 1.1, with documentation nearly 500 pages long and distributions weighing in at around 4MB.

"What is CUPS", you ask? The Common UNIX Printing System ("CUPS") is an IPP-based printing system developed by Easy Software Products as a replacement for the aging and clunky Berkeley (LPD) and System V printing systems. CUPS provides all of the modern printing ammenities, including support for user-defined printers and options, non-PostScript printers, color management, and page accounting.

CUPS 1.1 continues our commitment to an open-sourced, IPP-based printing system for all UNIX's. The new release contains many of the functional enhancements that have been requested by our users, including:

1. New USB backend and backend device discovery.
2. Banner page support
3. Digest authentication
4. Directory service enhancements, including polling, relaying, and access control
5. Directory structure changes to conform to the FHS 2.0 standard used by most Linux distributions.
6. Documentation improvements and additions
7. Drivers for EPSON printers
8. Filters - new PostScript RIP based on GNU Ghostscript 5.50 core, new PDF filter based on Xpdf, new text filter supporting Unicode and bidirectional text
9. IPP/1.1 support
10. Job persistence & history
11. Licensing change - the CUPS API is now provided under the GNU LGPL
12. LPD client support
13. User-defined printers and options
14. Web administration interface

In addition we have contributed more new code to the SAMBA team to support CUPS printing "natively" via IPP, providing a faster, more reliable Windows printing experience.

Others have also been busy at work adding to CUPS. Besides our ESP Print Pro software, two new graphical interfaces have appeared for CUPS - KUPS is a KDE-based interface for CUPS, and XPP is a FLTK-based interface for CUPS.

On the driver front, Grant Taylor has come up with CUPS-o-matic, a PPD file generator and filter script for existing Ghostscript printer drivers, and the GIMP print plug-in developers are working towards "universal" drivers for GIMP, Ghostscript, and CUPS.

Finally, many Linux distributions are including (or planning to include) CUPS or ESP Print Pro. This should provide the final push to get printer manufacturers to support their printers under Linux and *BSD.

For more information on CUPS, go to: www.cups.org

And for bonus points ... Katsu Jin Ken writes: "Indrema has posted a new picture of their upcoming console on their front page." It's looking a lot svelter and sleeker than the old look, and like the finest computers everywhere, features a blue LED. (On the other hand, beware the rude no-exit site design.) Please, Indrema, make it so!

Updates on Tom's detective work, Kevin's touchy look-but-don't touch semi-citizen status, and last but not least a word from the elusive printman, here folded, spindled and mutilated for your edification.

Danke sehr, Herr Doktor Pabst! The sighs -- nay, screams! -- of disappointment rose like the wail of a cat in heat following the announcement that AMD's new chips would be clock-locked, nullifying the advantages of Abit's ultra-overclockable motherboard. Jonathan Dabian writes: "This is probably a little late for me to get the name postage on the front page, but Tom's Hardware posted a new story that is an update to the Monday Blurb where they revealed that the new AMD processors would be multiplier locked. In this new story, Tom Pabst reveals the information he has since pieced together about the connections on the top of the processor, and ideas on how to alter those laser etched connections. Overclocking on the Duron and Thunderbird isn't dead. All that's needed is an easy way to alter those connections."

How do you like your quasi-futuristic clothing, Mr. Mitnick? One of the many following the bizarre turns of the Kevin Mitnick saga, RadarRider writes: "According to the following article on MSNBC:' Reversing a previous decision, Kevin Mitnick?s probation officer has given the notorious computer intruder permission to lecture on hacking and cracking, work as a security consultant and write a column for a soon-to-be-launched e-commerce site.'"

Disallowing use of computers unless specially granted seems a fairly over-the-top punishment -- everything has embedded processors. I wonder if Kevin has to ask permission to use an infrared-type automatic toilet, or a programmable thermostat. Where's King Solomon when you need him?

Unca Steve, Unca Steve! Tell us a bedtime story, OK? Speaking of *ashback, gwernol writes: "There's a fascinating letter from Woz - one of the co-founders of Apple on his web page at woz.org. Its a candid glimpse into the early days of the computer world, including tales of hacking the world's first video games -Pong and Breakout - at Atari. See inside the mind of one of the truly great ones. Some interesting perspective on Steve Jobs, too."

(Hint: some of the same words you can't say on television are off-limits to mass-market video games, too!)

Now I can print up dozens of tasty eclaires under Linux! If you followed the recent story about modernizing UNIX printing standards, you may have caught the news that CUPS 1.1 has been released. Here's some more information from the horse's mouth. printman writes: "Nine months after the CUPS 1.0 release, we are proud the announce the birth of CUPS 1.1, with documentation nearly 500 pages long and distributions weighing in at around 4MB.

"What is CUPS", you ask? The Common UNIX Printing System ("CUPS") is an IPP-based printing system developed by Easy Software Products as a replacement for the aging and clunky Berkeley (LPD) and System V printing systems. CUPS provides all of the modern printing ammenities, including support for user-defined printers and options, non-PostScript printers, color management, and page accounting.

CUPS 1.1 continues our commitment to an open-sourced, IPP-based printing system for all UNIX's. The new release contains many of the functional enhancements that have been requested by our users, including:

1. New USB backend and backend device discovery.
2. Banner page support
3. Digest authentication
4. Directory service enhancements, including polling, relaying, and access control
5. Directory structure changes to conform to the FHS 2.0 standard used by most Linux distributions.
6. Documentation improvements and additions
7. Drivers for EPSON printers
8. Filters - new PostScript RIP based on GNU Ghostscript 5.50 core, new PDF filter based on Xpdf, new text filter supporting Unicode and bidirectional text
9. IPP/1.1 support
10. Job persistence & history
11. Licensing change - the CUPS API is now provided under the GNU LGPL
12. LPD client support
13. User-defined printers and options
14. Web administration interface

In addition we have contributed more new code to the SAMBA team to support CUPS printing "natively" via IPP, providing a faster, more reliable Windows printing experience.

Others have also been busy at work adding to CUPS. Besides our ESP Print Pro software, two new graphical interfaces have appeared for CUPS - KUPS is a KDE-based interface for CUPS, and XPP is a FLTK-based interface for CUPS.

On the driver front, Grant Taylor has come up with CUPS-o-matic, a PPD file generator and filter script for existing Ghostscript printer drivers, and the GIMP print plug-in developers are working towards "universal" drivers for GIMP, Ghostscript, and CUPS.

Finally, many Linux distributions are including (or planning to include) CUPS or ESP Print Pro. This should provide the final push to get printer manufacturers to support their printers under Linux and *BSD.

For more information on CUPS, go to: www.cups.org

And for bonus points ... Katsu Jin Ken writes: "Indrema has posted a new picture of their upcoming console on their front page." It's looking a lot svelter and sleeker than the old look, and like the finest computers everywhere, features a blue LED. (On the other hand, beware the rude no-exit site design.) Please, Indrema, make it so!

Matthew Miller recently went through the RH300 training course, as well as the RHCE Certification Exam. He was kind enough to write an overview and give us his opinions on both of them, as well as his opinions on the relevance and quality of the training and the exam. Certification has been discussed extensively with regards to Linux, and here's a big scoop of food for thought.

The following was written by Slashdot Reader Matthew Miller

I'm fortunate enough to work at a place that realizes the importance of keeping employees educated and up-to-date. Since my largest current project is Linux-related, and based on Red Hat's distribution in specific, we thought it'd be worthwhile to send me to Red Hat for their RH300 course. I'm pretty familiar with Linux, but I'm a long way from knowing everything, and it's always interesting to learn what the vendor thinks are the most important parts of their product. We chose RH300 because it's the highest-level systems administration class currently offered. It's also the one linked to the RHCE exam, which was an added bonus, but learning was my main goal, not getting the certification. This is my report on the experience -- hopefully, it will help you decide if this is a good choice for you, either as a sysadmin or as an employer.

The Training Center

This course is not only available directly from Red Hat, but also from various partner organizations, including Global Knowledge, which has a training center here in Boston. However, we decided that if we were going to go to the expense of sending me, I might as well go directly to Red Hat, to increase the chances of getting a good instructor, and to insure adequate access to resources. We've had experiences in the past with third-party instructors who didn't know much beyond what was written in the materials. Of course, I don't know that this would be the case with Global Knowledge's version of RH300 -- perhaps someone else can comment on any experience they've had there.

So, it was off to the Red Hat headquarters in Durham, NC. Incidentally, I stayed in the Residence Inn there -- it was on Red Hat's site as being nearby. They didn't mention that it was on the other side of a major highway, with no provision for pedestrians to get across. Moral: stay at one of the closer hotels, or else get a car. Anyway, the RH building is very nice -- much bigger than I expected. (I suppose the IPO cash is going to good use.) Of course, as students, we weren't shown much of it -- no tour, and we weren't introduced to any of the celebrity employees. (Fair enough -- with several classes coming through every week, they'd never get anything done.) The people I did meet seemed pretty cool, and in general I got the impression that it's a fun place to work.

The classroom was about as I expected -- projection screen up front, rows of decent-enough small-brand Celeron-based systems (one per student). The machines were on a private network -- reasonable for the course, but unfortunately there was no provision for Internet access, which at the least would have been nice to have when I finished labs early.

We did have access to a breakroom with free soft drinks / juice and various snack items. This is also where the lunches were served -- to my surprise, these were quite good, and there were even decent non-meat choices.

The Teacher

The instructor was very knowledgeable -- not necessarily a complete guru, but he knew his stuff, including the "why" behind the course material. He was able to present the material in a good way, and was good at answering questions. I think the decision to go to Red Hat directly was wise; unlike a third-party consultant, he had some idea of what was going on inside of Red Hat and of their potential future plans. For example, during the section on the printing subsystem, he mentioned that they're considering a replacement for LPR in future releases -- perhaps LPRng or even CUPS. It's unlikely that someone from a different company would have had access to that kind of information.

Other Students

The other students in the course had a wide range of skills and backgrounds. I think that everyone probably met the listed better than pico. However, I could tell that some people were struggling. The instructor mentioned that the pass rate for the exam is about 65%, and I wouldn't be surprised if our class came out at that level or worse. It's not that anyone was stupid -- just that some people were out of their depth. On the other end of the spectrum, there were some people who were over-qualified: a few highly experienced sysadmins, and some folks from IBM taking the class because they are soon going to teach it.

The Course

The course was generally similar to the outline found on Red Hat's site, although I think the online information is a bit out of date. (Notice that the Web page makes reference to ipfwadm instead of ipchains or netfilter.) The eight units had slightly different names, and covered slightly different information. In the most drastic example, Unit 8, listed on the Web site as "Systems Administration and Security II", has turned into "Routers, Firewalls, Clusters and Troubleshooting". Some of the information listed in the online Unit 8 was moved into Unit 7, and some of it (cops, for instance) wasn't talked about at all. Hopefully, the online info will be updated soon.

Overall, the class went into less depth than I was hoping. Some of this was due to limitations of the lab setup -- it's a bit difficult to experiment with RAID in any meaningful way when you've only got one IDE hard drive, and obviously impossible to set up a cluster on one machine (short of running VMware). Other things where just plain introductory -- the section on the kernel, for example, focused on the steps required to build and install a new kernel, rather than being an in-depth discussion of tunable parameters. The part about Apache was similar; I was hoping to hear "You've all configured Apache before; here's things you should be aware of when you need it to do such-and-such", but the most advanced we got was setting up a virtual host. Building RPMs from source was mentioned briefly, but there was no information given on important and largely undocumented topics like --buildpolicy.

That's not to say I didn't learn anything -- the section on LVS / Piranha was enlightening even without hands-on experience, and I appreciated the part about quotas, which isn't something I've worked with much. And, I learned a large number of tiny things which add up to making the experience worthwhile to me. RPM can now do globbing over ftp! Portmap uses tcp_wrappers, but doesn't do reverse name lookups, so be sure to use IP addresses instead of names. RH Linux provides a little script called "service" that lets one avoid the tedium of typing /etc/rc.d/init.d/servicename all the time. And so on....

The "300" designation is a bit misleading. This isn't really what I'd consider an upper-level course -- it's more along the lines of SysAdmin 101. Overall, I think this class is probably worthwhile to someone with a good RH Linux background who hasn't done any systems administration. In fact, I'd even recommend it to people in that situation. On the other hand, if you've been a Linux sysadmin for a while, you'll probably be bored most of the time. It might be valuable to experienced Unix sysadmins who haven't dealt with Linux much (or even Linux admins who haven't used Red Hat Linux), but the course wasn't particularly taught from that angle and there are probably better options.

The Exam

Since I signed a confidentiality agreement, I can't talk about specific details of the test, but I will address the exam in general terms. It's a day-long three part process, with each part being worth 1/3 of the total. To pass, your overall score must be at least 80%, and you can't do worse than 50% on any one part.

One of the sections is a typical multiple-choice test, but the other two are lab based. I was quite impressed with the hands-on tests -- they are certainly what makes the RHCE meaningful. I'm not aware of any other sysadmin certifications that work this way.

For one of the lab tests, students are given a several-page specification, and must install and configure Red Hat Linux and several network services. This wasn't particularly difficult, and shouldn't be for anyone with much experience. For me, the hardest part was resisting the temptation to go beyond the spec -- since I finished the given requirements with plenty of spare time, I considered installing and setting up additional services in a way that would fit in with the listed goals. But, I decided that it'd be better to leave well-enough alone -- there's no concept of extra credit.

The other hands-on test is the cool and exciting one. Students are given preconfigured setups which are broken in some way, and given a task that must be completed. The system's problem doesn't necessarily relate directly to the task, but does interfere with it. The test-taker must find out what's wrong and correct the error. (Reinstalling packages is not allowed.) Being able to list the steps taken and to repeat the fix is important, but ultimately the test is scored on a works / doesn't work basis. One the examiner verifies that the problem is fixed, he or she wipes the system and provides another broken config.

This problem-solving section directly tests skills important to being a sysadmin in the real world; if someone has trouble with these, they're probably not ready for a systems administration job. Of course, just passing this test doesn't guarantee good problem solving skills (let alone all the other needed abilities), but it does seem a genuinely valuable indicator.

I've only two complaints with this part of the test. First, I'd make it a much larger section -- at least 50% -- and I'd increase the number of problems given so that there'd be a better sample size. The various challenges are assigned at random, and some are easier than others, and each tests knowledge of different parts of the system. The way it's done isn't bad, but it wouldn't hurt to have a lot more of it. Second, I'd give each student two computers, and make more of the problems network-related. This has logistical and cost issues (especially in places other than Red Hat's own training centers), but since many of the problems faced in the real world have to do with the way systems interact, I feel it'd be worth it.

The Exam Separated From The Course

You may have noticed that I seem a lot more excited by the exam than by the course itself. I think both are valuable, but they seemed aimed at slightly different levels. The course definitely can serve as a good review for the exam, but if you need the course, you won't do well on the test. If you're tight on cash and the certification seems valuable to you or to your employer, going straight to the exam would be reasonable. (Make sure you take a look at Red Hat's test prep page.) On the other hand, if you need to be quickly brought up to speed on the basic knowledge required of a RH Linux sysadmin, it might make sense to take this course without worrying about the test. Since RH300 is equivalent to RH033 + RH133 + RH253, this could be a much more intensive and time-efficient option.

Red Hat-Specificness

It's probably obvious, but bears mentioning anyway: this is a Red Hat Linux course and certification, not a general Linux one. I found this to be true both explicitly and implicitly. The instructor was good about saying "This is the Red Hat way of doing things -- it's possibly different on other distributions." (I found the increase-the-whole-pie attitude to be common to all of the RH employees I talked to.) There were also quite a few things that were just assumed. If you take the exam without knowing a lot about Red Hat Linux in particular, you're likely to have trouble.

This doesn't make the certification meaningless for organizations running other distributions -- many of the skills and knowledge required for the test (especially the problem solving part) are generally applicable anywhere. In fact, due to the lab-based testing process, I have more respect for this exam than I might for a multiple-choice test covering more distributions. I think this issue is a one-way sort of thing: the RHCE exam requires knowledge of Red Hat Linux, but anyone who can pass it shouldn't have much trouble picking up other flavors.

Stuff

Ok, the Web page promises that they'll give Red Hat promotional items to course participants. Yeah, well, they can do better on this front. Not even a t-shirt! C'mon, everyone gives t-shirts. Vendor shirts are a staple of my wardrobe! All we got was a mousepad, some stickers, and a baseball cap. (No chance of getting a red fedora.) Oh, and of course an official copy of the CD (with the 180 days of support). Many people in the class were surprised to learn that Red Hat doesn't sell anything from their offices -- you can't buy copies of the distro or additional merchandise. They've got a lot of students coming through there, so it seems like this could be a decent (even if relatively small) revenue stream.

A Bit About Study Guides

Before I went, I flipped through RHCE Exam Cram , the sole study guide I found at the local bookstore. Someone in the class actually purchased it and brought it with them, and I got a chance to read more of it then. I wasn't really impressed. The book was especially concerned with what it called "trick questions", and indeed its sample questions were sometimes a bit confusing -- and often poorly worded. After taking the test, I can say that this seems mostly to be a problem with the book, not something encountered on the actual exam, which was mostly straightforward and fair.

There are RHCE study guides, but I wouldn't recommend spending any money on any of them. As the course instructor told us: if you're going to pass, you'll do so even if you don't have a guide. And if you're going to fail, the guide won't be much help.

Conclusion

I think the RH300 course and RHCE certification can be valuable to both employers and individuals. The course provides a nice quick overview of the basics needed to move, for example, from being a systems operator to being an admin. I wouldn't think of it as either a requirement for the test or as something that can make someone not ready suddenly have the skills required for the exam. Since the exam is hands-on and lab based, those abilities can only come from real world experience. Looking at that from the other direction: this is exactly what makes the RHCE worth anything. While it's not a total statement on someone's talent, being able to pass is a strong indicator that they have the basic skills for a systems administration job. If I were making hiring decisions, I wouldn't make the RHCE a requirement, but I would have more confidence in applicants who have it.

Michael Sweet writes "Well, it's taken us long enough (nearly 2 years since we started the project), but the Common UNIX Printing System, or "CUPS", is finally out of beta and ready to replace all those 1970's line printer spoolers masquerading as printing systems. What is CUPS, you ask?

Well, it's basically a completely new printing system based on the Internet Printing Protocol ("IPP") that supports PostScript and non-PostScript printers and a variety of different file formats to make your life easier.

CUPS provides all of the normal printing commands ("lpr", "lp", etc.) - you still use "lpr" to print from Netscape, etc. However, these commands take on a new life with CUPS - instead of bringing up an application everytime you want to print, you can print most images, PDF files, etc. directly. CUPS figures out the type of file and runs any necessary filters to format it for the printer. Have a file that CUPS doesn't handle? No problem, just add a filter and CUPS will handle it, for any printer you have.

Printer drivers are provided for PostScript and HP PCL based printers. We're hoping that the filters provided with CUPS (including a PostScript RIP based on GNU GhostScript) will encourage independent developers and printer manufacturers like EPSON to start developing drivers that use CUPS. Only time will tell.

CUPS can be downloaded from our website at cups.org and is provided under the terms of the GNU General Public License. Commercial printer drivers based on CUPS are available from our main website. "

Michael Sweet writes "Well, it's taken us long enough (nearly 2 years since we started the project), but the Common UNIX Printing System, or "CUPS", is finally out of beta and ready to replace all those 1970's line printer spoolers masquerading as printing systems. What is CUPS, you ask?

Well, it's basically a completely new printing system based on the Internet Printing Protocol ("IPP") that supports PostScript and non-PostScript printers and a variety of different file formats to make your life easier.

CUPS provides all of the normal printing commands ("lpr", "lp", etc.) - you still use "lpr" to print from Netscape, etc. However, these commands take on a new life with CUPS - instead of bringing up an application everytime you want to print, you can print most images, PDF files, etc. directly. CUPS figures out the type of file and runs any necessary filters to format it for the printer. Have a file that CUPS doesn't handle? No problem, just add a filter and CUPS will handle it, for any printer you have.

Printer drivers are provided for PostScript and HP PCL based printers. We're hoping that the filters provided with CUPS (including a PostScript RIP based on GNU GhostScript) will encourage independent developers and printer manufacturers like EPSON to start developing drivers that use CUPS. Only time will tell.

CUPS can be downloaded from our website at cups.org and is provided under the terms of the GNU General Public License. Commercial printer drivers based on CUPS are available from our main website. "