On Wednesday 22 July 2009 14:40:50 Thomas Zander wrote:
On Wed, Jul 22, 2009 at 22:33, Michael D.
Stackhousemstackho...@samsa.com wrote:
I think we'll investigate VLC as an alternative. Not too comfortable
building around a solution that's not being maintained as it should be.
mplayer is
On Sat, 25 Jul 2009 02:39:52 +0200
Raymond Vetter raymo...@gmx.de wrote:
FreeBSD Ports provide only Samba 3.0.x.
It is possible to port Samba 3.2.x, 3.3.x for the current FreeBSD?
The 3.0.x is quit old.
When was the last time you updated your ports tree?
--
Jerry
ges...@yahoo.com
A highly
Hello.
I'm using afpd on a 6.3/i386 and I make it authenticate to pam_smb.
Everything was fine with 2.0.3.
As soon as I upgraded to 2.0.4, I started getting:
Jul 13 09:28:38 x afpd[89271]: dhx login: yyy
Jul 13 09:28:38 x afpd[89271]: in openpam_load_module(): no
My system (uname -a) is FreeBSD grenache.lib.uchicago.edu
7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #0: Fri Jun 26 15:23:52 CDT 2009
r...@grenache.lib.uchicago.edu:/usr/obj/usr/src/sys/GENERIC
amd64.
I recently installed security/krb5 which is my first installed port
that has set
On Sat, 25 Jul 2009 11:50:17 -0500
Peggy Wilkins enli...@gmail.com wrote:
My system (uname -a) is FreeBSD grenache.lib.uchicago.edu
7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #0: Fri Jun 26 15:23:52 CDT 2009
r...@grenache.lib.uchicago.edu:/usr/obj/usr/src/sys/GENERIC
amd64.
I recently
On Sat, 2009-07-25 at 18:54 +0200, Andrea Venturoli wrote:
Hello.
I'm using afpd on a 6.3/i386 and I make it authenticate to pam_smb.
Everything was fine with 2.0.3.
As soon as I upgraded to 2.0.4, I started getting:
Jul 13 09:28:38 x afpd[89271]: dhx login: yyy
Jul 13 09:28:38
Argh! This again.
On Sat, 25 Jul 2009 11:50:17 -0500
Peggy Wilkins enlil65 at gmail.com wrote:
I recently installed security/krb5 which is my first installed port
that has set WITH_OPENSSL_PORT in its Makefile. It didn't take me
long to notice after the installation of security/krb5 that
Thanks very much for the clear replies to my question about how to use
openssl from ports. It looks like it should be straightforward in most
circumstances. However, unfortunately I seem to have run into exactly
the problem on my system that is described in this PR:
Hi,
I am testing HPLIP 3.9.6, from the latest port candidate on this
mailinglist.
Tonight I was changing my cupsd.conf so that I could access my printer from
another machine on the local network. During that exercise, I made a few
errors, which resulted in cupsd writing those errors to syslog,
