From owner-freebsd-questions Mon Jul 31 11:56:16 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id LAA18779 for questions-outgoing; Mon, 31 Jul 1995 11:56:16 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id LAA18773 for ; Mon, 31 Jul 1995 11:56:14 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA24347; Mon, 31 Jul 95 12:48:53 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9507311848.AA24347@cs.weber.edu> Subject: Re: Setting up a network printer To: gibbs@freefall.cdrom.com (Justin T. Gibbs) Date: Mon, 31 Jul 95 12:48:53 MDT Cc: thor@paxs.com, questions@freebsd.org In-Reply-To: <199507301914.MAA20192@freefall.cdrom.com> from "Justin T. Gibbs" at Jul 30, 95 12:14:23 pm X-Mailer: ELM [version 2.4dev PL52] Sender: questions-owner@freebsd.org Precedence: bulk > >I've got a good one--I'm running FreeBSD networked with > >a few Win95 machines. These machines can route through the > >FreeBSD machine, and I can ping them, etc, and ftp directly > >to them. There is no WinNT server, though. > > SAMBA in the ports collection may allow you to do this. It won't. You'll beed to put client services on the BSD box by hacking up their client paying special attention to how they handle the incoming print requests in Samba itself. Basically, this meand moving the SMB-over-TCP client services into a more general code abstraction. I've been meaning to put this in the kernel under socket services, mostly to support BSD mounts of LANManager drives, but I haven't had time. In such a design, printing would just be a bonus; the big deal is allowing it to be a consumer of file system services. Maybe in 1997. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.