On Sun, 2 Jan 2005 22:36:00 -0700, Dmitry Sorokin <dimon at intellinet dot ca> wrote:
> I'm trying to hack m0n0wall to run a printserver (lpd + samba)
> I was able to add lpt support to the kernel, recompiled the image to include
> binaries and configs for lpd and samba.
> lpd seems to be working fine, I can print with lp command locally
> Also I cam run nmbd -D and smbd -D with no errors, but when I try to print
> something from the client computer, here what smbd -i says:
> Please, if somebody have an idea where I need to look to fix that, let me know.
m0n0wall doesn't include all the libraries a stock FreeBSD system
does. Any that are required and aren't there will need to be manually
added to your image. To find out what a specific binary needs, run
ldd on it. Like:
-bash-2.05b$ ldd /usr/local/sbin/nmbd
libcups.so.2 => /usr/local/lib/libcups.so.2 (0x280d7000)
libssl.so.3 => /usr/local/lib/libssl.so.3 (0x280f3000)
libcrypto.so.3 => /usr/local/lib/libcrypto.so.3 (0x281b9000)
libpam.so.1 => /usr/lib/libpam.so.1 (0x282a8000)
libpopt.so.0 => /usr/local/lib/libpopt.so.0 (0x282b2000)
libc.so.4 => /usr/lib/libc.so.4 (0x282b9000)
libintl.so.6 => /usr/local/lib/libintl.so.6 (0x28352000)
libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x2835b000)
If you don't care about image size, you could throw in /usr/lib/* and
/usr/local/lib/* as well as probably some other lib dir's I'm not
thinking of off hand.
> I know, most of you will say right away, that m0n0wall is not intended for that
> kind of hacks, but that's something I personally would like to have at home, so
> I don't have to keep one of my workstations on to print from another. And I'm
> pretty sure a lot of people out there would like to have printserver on their
> PC based m0n0 boxes at their homes or small offices.
We could argue all day whether or not that's a good thing to run on a
firewall. I won't go there. :)