Linux Print to a Shared Windows Printer

I've seen a lot of these hints on the Internet, but most of them didn't work for me. This is how I managed to print to a shared Windows printer.

We'll start by opening System Preferences, where we chose the Print & Fax preference pane. There you should see a list with all the printers you've currently installed. Click the '+' button to add a new printer. This opens the Printer Browser. Then hold down the Option key and click More Printers; this lets you access the "Advanced" options from the first popup menu.

Debian Lenny Chroot'ed BIND9 DNS

I've been looking a simplest way to create and secure DNS server on a chroot'ed environment for my private network. and I found this good documentation link.

This guide will show you how to get DNS working on your Debian server using BIND 9. I will show you how to setup the network interface, and how to maximize security by running BIND 9 inside a chroot environment. You will need to register a domain name so there will be no conflicts between internet domains and the domain(s) used on your LAN.

Ampache: Music Server

The Debian Way!! Ampache

In order to install Ampache on Lenny, follow these instructions (synaptic can be used in place of apt-get)

apt-get install mysql-server-5.0 (optional, not needed if you have mysql-server already installed)
apt-get install ampache

If you want some Ampache eye candy

apt-get install ampache-themes

Now set up a mysql "user" account that has global privileges. I use phpmyadmin (much easier), or you can use the command line.

Now point your browser to

http://localhost/ampache

or

http://your.ip.address/ampache

Follow the web install instructions

Done.

Reference:

Troubleshooting newly build BIND DNS under Mandriva Enterprise 5

I'm having a super headache figuring out the solution on how to solve this problem. Ok the problem was i can't query the DNS server from client to Mandriva DNS Server so the solution was this:  

1. check the packets first using tcpdump :  tcpdump -pni any port 53

2. check the server and client using dig command and see if you have the ouput 

3. if you have the output then tail the log file on named  

tail -f -n0 /var/lib/named/var/log/*.log 

4. if you have no output result coming from the client meaning it is blocked by bogon network 

5. go to /var/lib/named/etc/bogon_acl.conf and trusted_networks_acl.conf

6. and check your network 

7. thats it! damn! It gives me a super headache on this simple problem.

Tnx for my fellow linux gurus..