- 1 Hyper-V 2012 R2: Pros and Cons of Generation 1 vs. Generation 2 VMs
- 2 Harnessing the Power of Hyper-V Network Virtual Switches
- 3 Working with SSH and Secure FTP Servers in Windows
- 4 Discover Windows 8's Hidden Server Features
- 5 Server Virtualization Customer Reviews: VMware, Hyper-V, XenServer and More
Enterprise Unix Roundup: Open Source, Redefined Page 3
|Main||In Other News||Recent Updates||Tips of the Trade|
SGI released Advanced Linux Environment 3 Security Update #32, which tracks recent errata announced by Red Hat, including fixes to ImageMagick, ipsec-tools, and a Mozilla security update. The release includes updated SGI ProPack 3 Service Pack 4 RPMs for SGI Altix systems.
Gentoo joined the list of distributions patching the MIT Kerberos telnet vulnerability.
Tips of the Trade
Network printing is one of those basic administration chores that can be done many different ways: share user's printers, use a workgroup printer with built-in networking, or use a hardware printer server. The first option is the worst the last thing someone wants is hordes of people trooping into her cubicle to mess with the printer. Workgroup printers are great. They are sturdy and suited to high-demand usage, and they plug directly into the network. But they can also be expensive and difficult to administer.
A stand-alone printer server offers the most flexibility; then you can share any printer you like and not have to pay a premium for built-in networking. A Linux printer server using CUPS and Samba makes a great cross-platform printer server. It gives the most power and flexibility, as well as rock-solid stability. The hardware can be almost anything: an old PC, a new sleek mini-ITX, or a Soekris-type box. Keeping old PCs out of landfills is always a noble goal, and it saves money.
But what if you don't want to sacrifice reliability just to keep some grotty old hardware in service?
Using ordinary PC hardware gives the most flexibility. You can add PCI-parallel adapters, USB ports, and even a wireless adapter for wireless clients or to save running cables. The only cost is the hardware CUPS and Samba are the software that make this all go.
CUPS all by itself makes a great printer server, but it lacks one thing the ability to install Windows drivers over the network. Adding Samba not only allows automatic installation of Windows printers, it also enables access controls to be set up.
A commercial version of CUPS that may better suit your needs is also available. It comes with support, more and better-quality printer drivers, and nice management utilities.
For a good introduction to CUPS, see Chapter 14 of the Linux Cookbook, and check out the related article Network Installation of Windows Printers from Samba.