Book
- Basic setup of a SOHO server
- SoHo - Software repositories
- SoHo - Alias of loopback interface
- SoHo - IPtables configuration example
- SoHo - Webmin
- SoHo - DNS
- SoHo - VMWare
- SoHo - Windows
- SoHo - OpenVPN
- SoHo - Remote Desktop
- Nameserver on Windows XP forwarding to public DNS with private zones
- SoHO - NTP
- SoHo - SSH
- SoHo - Ubuntu prerequisites
- How to strengthen SSH
- Fixing Nessus complaints
- Java installation on RHEL 4
- Installing vsFTPd on CentOS
- How to setup CA (certificate authority)
- Installation of VIM X11 and archivers on RHEL 4 x86_64
- SoHo - MS & Open-Office
- User management
- CommuniGate Pro
- Backup
- Issue tracking for small groups
- Jabber setup and configuration
- Monitoring & Statistics
- Printing in SOHO
- Faxes in SOHO
- T38 Modem
- PostScript fonts for faxes
- Installing Brother MFU drivers on Ubuntu
- Installing Hylafax client on RHEL4 and Fedora
- Installing Hylafax server on RHEL4
- Installing Hylafax server on Ubuntu
- Integrating Hylafax with CUPS
- Integrating Hylafax with CommuniGate
- Managing Hylafax from Ubuntu client
- Sending and receiving faxes over internet (links)
- How to test faxing
- Drivers for Brother MFUs
- Brand new idea about faxing
- External faxing resources
- Antivirus & Antispam
- External SOHO References
- Supplementary SOHO procedures
Printing hints
in
Chain printers
By default printers of type ipp: are not propagated via browsing. This can be easily worked around:
cd /usr/lib/cups/backends ln -s ipp ipp2 /etc/init.d/cupsys restart lpadmin -p PropagatedPrinter -v ipp2://somehost/printers/Remote lpadmin -p PropagatedPrinter -o printer-is-shared=true
and it will be propagated
Driver name notation
The lpadmin option -m does not accept absolute file names.The PPD file must fall in one of predefined LSB-compliant locations mapped as follows:
| pattern | location |
| lsb/usr/* | /usr/share/ppd/* |
| lsb/opt/* | /opt/share/ppd/* |
| lsb/local/* | /usr/local/share/ppd/* |
| * | /usr/share/cups/model/* |

Comments
Post new comment