Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 15 Nov 2002 09:23:30 -0800
From:      Andrew Stuart <elitetek@tekrealm.net>
To:        dwcjr@FreeBSD.ORG, ports@FreeBSD.ORG
Subject:   Re: samba 2.2.6
Message-ID:  <20021115172330.GA94538@freebsd.tekrealm.net>
In-Reply-To: <20021115121823.GB3096@wwweasel.geeksrus.net>
References:  <20021115084921.GA83250@freebsd.tekrealm.net> <20021115121823.GB3096@wwweasel.geeksrus.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 15 Nov 2002 at 07:18:23 -0500, AlanE wrote:
> On Fri, Nov 15, 2002 at 12:49:21AM -0800, Andrew Stuart wrote:
> >I believe this port needs a pkg-message or something alerting
> >people to the fact that upgrading a prior samba release to 2.2.6
> >with the CUPS option enabled (or not disabling it if its found on 
> >the system already) may/will cause prior printer connectivity to fail.
> >
> >if you do not specify disabling cups and are using printing=bsd, samba
> >refuses to print, it acts like it is doing everything correctly, it just
> >never prints. prior versions of samba dont seem to have this problem.
> >
> >I have been seeing alot of people in the other lists with problems with 
> >printing, and this seems to be the cause.
> 
> I'm the cups-meister, and the samba-cups fucker-uppper, so I'll put this
> on my queue behind the other 39281774522 things that are already there.
> No changes should be made w/o a full analysis of what is happening. 
> 
> Also, cups 1.1.16 is around the corner, down six blocks, and hiding
> behind the bus stop. It contains a new driver that allows you to use
> the windows driver and cups acts like a pass-trhru. like it does when
> printing postscript (I think).
> 
> The cups upgrades will not come for a few weeks; i'm looking for
> a job that pays $95+/y and the job market is ... well ... shitty.
> 
> I also have KDE to deal withk the development version of the autoauto
> twins.
> 
> The best you can expect is a couple weeks. In the meantime, *if* I get
> time, I will look at this problem. Are you willing to test for me, as I
> have no Windows box
> 
> -- 
> Alan Eldridge
> Unix/C(++) IT Pro for 20 yrs, seeking new employment.
> (http://wwweasel.geeksrus.net/~alane/resume.txt)
> KDE, KDE-FreeBSD Teams (http://www.kde.org, http://freebsd.kde.org/)

lol, I dont think you need to be so hard on yourself, but ok. Yeah I
will be glad to test it for you, i have cups installed in 2 production
environments, along with samba, so it shouldnt be to big of a problem.

Although I don't believe it is your fault, it appears to be more then
bsd related. I am not positive of this but i am seeing people have
simular results with other *nix's. it appears that if you dont specify 
the --disable-cups or whatever the configure argument is, cups takes
over..

Anyways, good luck on the job scene, and as far as the fix, i think a
simple pkg-message would do the trick in the mean time, or I will just
keep an eye out for others who are having the problem, and forward on 
what i found out.

-- 
Andrew Stuart
http://www.tekrealm.net


What if everything is an illusion and nothing exists?  In that case, I
definitely overpaid for my carpet.
		-- Woody Allen, "Without Feathers"

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021115172330.GA94538>