Re: ftp/fetch "command not understood" on stable and current
From: "Brandon Fosdick" <[EMAIL PROTECTED]> > On both stable and current I'm having problems getting ftp or fetch to > connect to ftp servers (fetch can't connect to anything). I'm behind a > firewall but the ftp ports are open and I'm sitting next to an HPUX box > that doesn't have the same problem. > > All of the output below came from a 5.1-R box: > 13:16 [EMAIL PROTECTED]>uname -a > FreeBSD mse.fbm.lmms.lmco.com 5.1-RELEASE FreeBSD 5.1-RELEASE #0: Thu > Jun 5 02:55:42 GMT 2003 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 > > Here's what happens when I ftp to ftp.freebsd.org and try to do 'ls' (or > anything other command for that matter)... > --- > Trying 2001:4f8:0:2::e... > ftp: connect to address 2001:4f8:0:2::e: No route to host > Trying 204.152.184.73... > Connected to ftp.freebsd.org. > 220 freebsd.isc.org FTP server ready. > Name (ftp.freebsd.org:bfoz): anonymous > 331 Guest login ok, send your complete e-mail address as password. > Password: > 230- > 230-You have reached freebsd.isc.org/ftp.freebsd.org. > 230- > 230- > 230- > 230-This server is operated by Internet Software Consortium (ISC), > 230-on behalf of the FreeBSD Project, and is serving the full > 230-FreeBSD FTP archive via IPv4 and IPv6. > 230- > 230 Guest login ok, access restrictions apply. > Remote system type is UNIX. > Using binary mode to transfer files. > ftp> ls > 500 command not understood > 227 Entering Passive Mode (204,152,184,73,184,121) > --- > Your ftp client went into passive mode. The reason it went to passive mode is because the /etc/login.conf file is setting an environment variable ((FTP_PASSIVE_MODE=YES) to turn on passive mode. To disable it, run ftp or fetch under sh as follows: FTP_PASSIVE_MODE=NO ftp ... FTP_PASSIVE_MODE=NO fetch ... or change FTP_PASSIVE_MODE to NO in the "default" section of /etc/login.conf, and then use cap_mkdb /etc/login.conf to rebuild the login.conf.db. Scot ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Hardcoded krb reference in ports/postfix
From: "Vivek Khera" <[EMAIL PROTECTED]>
> > "MS" == Melvyn Sopacua <[EMAIL PROTECTED]> writes:
>
> MS> AFAIK - my /usr/lib/libkrb.a stems from the 4.2-RELEASE cd install I
started
> MS> this comp with (it's dated Nov 2000) and thus hasn't been updated
since and
>
> Then delete the file. If it exists, it is assumed you use kerberos in
> the current 4.x releases. It doesn't exist otherwise.
>
> Patches to alter the bahavior are welcome, if you don't agree with
> this.
>
I had to deal with this problem in the security/cyrus-sasl port where
/usr/lib/krb.a existed but the user didn't want it or needs to use the krb4
port due to Kerberos IV is no longer in -CURRENT. I use the following,
which allows -CURRENT and -STABLE users to use the security/krb4 port, or
use Kerberos IV libraries that is built during a buildworld on on systems
who's OSVERSION is <+ 500105:
# KERBEROS 4 was removed in FreeBSD 5.0-CURRENT
.if ${OSVERSION} > 500105
.if defined(WITH_KERBEROS4)
LIB_DEPENDS+= krb.2:${PORTSDIR}/security/krb4
CONFIGURE_ARGS+=--enable-krb4=${LOCALBASE}/krb4
.else
CONFIGURE_ARGS+=--disable-krb4
EBONES= "@comment "
.endif
.elif exists(/usr/lib/libkrb.a) && defined(MAKE_KERBEROS4) &&
!defined(WITHOUT_KERBEROS4)
CONFIGURE_ARGS+=--enable-krb4
.elif !exists(/usr/lib/libkrb.a) && defined(WITH_KERBEROS4)
LIB_DEPENDS+= krb.2:${PORTSDIR}/security/krb4
CONFIGURE_ARGS+=--enable-krb4=${LOCALBASE}/krb4
.else
CONFIGURE_ARGS+=--disable-krb4
EBONES= "@comment "
.endif
I use two *_KERBEROS4 variables:
WITH_KERBEROS4-CURRENT: Selects the security/krb4 port
-STABLE: Selects the security/krb4
port if /usr/lib/libkrb.a dosen't exist.
WITHOUT_KERBEROS4OSVERSION <= 500105: Used to deselect Kerberos IV
if MAKE_KERBEROS4 is defined in /etc/make.conf.
Scot
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Stable#1
From: "Jeffrey" <[EMAIL PROTECTED]> > Got a pretty stupid question... My kernel is now 4.8 Stable#1 but when does the number change when i do makeworld > and the other things? or where can i see that? > The "#1" only changes when you re-compile the kernel using the same sources. If you use cvsup/cvs between kernel rebuilds, the number is reset back to one. Scot ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Weird messages
From: "Gavin Atkinson" <[EMAIL PROTECTED]> > On Fri, 28 Mar 2003, Craig Boston wrote: > > Okay, is there something wrong with the mailing list, my mail server, or > > am I just going insane? > > > > Seeming random messages (from completely different people) are showing > > up as mutipart/mixed, with an empty application/pgp-signature part and > > and a text/plain part containing only the following: I see these messages haveing 2 attachements [original message (text/plain), pgp-signature (application/pgp-signature)] and the tag line placed by the mailing list software (text/plain). > [snip example] > > It's not just you - i'm seeing similar. The emails show up fine in pine, > but in Evolution or MS Outlook, i get exactly what you describe. I first > noticed it on Wednesday. > This is because the sender of these mail are PGP signing their messages. Which causes problems for users that don't have a mail program that understands PGP signed messages. hmm, It looks as thought the Mailing List software was changed from MajorDomo to Mailman-Version: 2.1.1, and instead of appending the list signature to the end of a message. The Mailing List software now encapsulates the "Content-Type: multipart/signed; micalg=pgp-sha1" inside a "Content-Type: multipart/mixed; " before appending the list signature. Unfortuanately, this now breaks my de-pgp-sig filter which had converted multipart/signed to multipart/mixed (it only replaced signed with mixed in the header). Scot ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: apache - fp
From: "Ing. Antonín Walter" <[EMAIL PROTECTED]> > anybody can advice how and from where to install DES libraries on 4.4 box. > It use to be an option with 4.1 but it did not show up during instalation > now. > You don't need to install the libdescrypt libraries on a 4.4 box as they have been combined with libscrypt into a single libcrypt library. Since your subject mentions apache - fp, you'll need to download the latest apache13-fp port that has been fixed to work with the new libcrypt library in 4.4. Scot To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: FreeBSD sendmail libmilter
From: "Mike Lambert" <[EMAIL PROTECTED]> > On Fri, 25 May 2001, Arthur W. Neilson III wrote: > > Recently I downloaded amavis-perl-11 and want to implement it using the miltering > > interface. It's not clear to me how to build the sendmail 8.11.3 which is integrated > > with FreeBSD 4.3 with libmilter support. > > Having just recently gone through this very maze, I think I can answer > with some accuracy. > > The short answer: You can't. If you want sendmail with the milter API > enabled, you need to build sendmail from ports. > Actually, you can build sendmail with milter API from the FreeBSD Sources. You just need to apply a patch to the build process. I had submitted the patch to Greg Shapiro as PR 23811, but he advised that he didn't want to enable the Milter API since it was marked FFR (For Future Release) in 8.11. He also advised he expects to enable the Milter API when Sendmail 8.12 is released, and it is no longer marked FFR. http://www.freebsd.org/cgi/query-pr.cgi?pr=23811 Scot To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: apache-1.3.19 segfaulting on FreeBSD-4.3 RC
From: "Dan Larsson" <[EMAIL PROTECTED]> > Does anyone have a clue why I get these segfaults? > > (The apache port installed is /usr/ports/www/apache13 with no > optimizations or extra modules) > This problem ocurs when the ServerName directive is not defined in the httpd.conf file. Program received signal SIGSEGV, Segmentation fault. 0x8064287 in ap_get_local_host () (gdb) bt It occurs because "p" is null. The Apache folks have fixed the problem for the next release 1.3.2x. I have fixed this problem in the Apache13-fp port (patch-fj) a week ago. The fix should be applied to the other apache ports (apache13, apache13-modssl, apache13+ipv6). http://www.freebsd.org/cgi/cvsweb.cgi/ports/www/apache13-fp/files/patch-fj?r ev=1.3&content-type=text/x-cvsweb-markup We should get this patch into the other apache13 ports before 4.3-RELEASE. Otherwise we'll have a broken apache server on the Release CDs. Scot Note: the fix is in the last two patches of patch-fj. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: kde-2.1/freebsd 4.3beta/konqueror and openssl
From: "Dinesh Nair" <[EMAIL PROTECTED]> > one a related note, though i've got most of the files in /usr/lib dated > March 7, 2001, a few of them are still dated July 28, 2000 as per the > 4.1-RELEASE i installed of the cd sets. as some of these include rsaref > and libssl_p.a libraries, i was wondering if this was contributing to the > problem. > > -r--r--r-- 1 root wheel 9196 Jul 28 2000 librsaUSA.so.1 > -r--r--r-- 1 root wheel 6394 Jul 28 2000 librsaUSA.a > -r--r--r-- 1 root wheel 7158 Jul 28 2000 librsaUSA_p.a > -r--r--r-- 1 root wheel 880 Jul 28 2000 libRSAglue_p.a > -r--r--r-- 1 root wheel 244522 Jul 28 2000 libssl_p.a > -r--r--r-- 1 root wheel 2284 Jul 28 2000 libRSAglue.so.1 > -r--r--r-- 1 root wheel 822 Jul 28 2000 libRSAglue.a > > if it isnt, would it be safe to rm these July 28th dated libraries out of > /usr/lib ? > The *_p.a files are profiled libraries that can be safely removed from the system. librsaUSA.*, and libRSAglue.* have been integrated into the OpenSSL distribution since the RSA patent has expired. You may remove these libraries if you have no ports that are still depending on them. Just rebuild all ports that depend on OpenSSL. Scot To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: make world
From: "Robert Banniza" <[EMAIL PROTECTED]> > Rather than doing a 'make buildworld &', wouldn't you want to do a 'nohup > make buildworld' to keep the process running even after getting > disconnected? I thought the & only put the process in the background and > that the bg process would stop after being disconnected. Maybe I'm misled > here. > The process will continue running until it has completed. Scot To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: rpc.lockd
From: "Roman Shterenzon" <[EMAIL PROTECTED]> > On Tue, 19 Sep 2000 [EMAIL PROTECTED] wrote: > > Yeah probably should...perhaps suggest it to -docs. Someone (from > > something.edu, perhaps rpi.edu) posted a URL to one of the lists of a > > working but untested rpc.lockd. You might like to try it...if it gets > > enough testing it should make it in for 4.2 (one hopes). > > > > Andrew > > > Thanks, I'm ready to give it a try, does anyone the URL? > I'll search the archives meanwhile. > (Was it ported from NetBSD?) > I kind of remember reading about it on the current mailing list. Current-Users: Has a working rpc.lockd been imported into CURRENT. If it has, is there a possibility of getting it MFC'd to STABLE. Thanks, Scot To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: apach+ssl+php port
From: "Vincent Poy" <[EMAIL PROTECTED]> > Hmmm, I remember there were some issues about fp extensions back > in November 1999 about DES and MD5 passwords.. > Back in November 1999, we only had the BSDI extentsion, and fpsrvadm.exe was/is compiled statically with the DES libcrypt. This required the Apache server to be compiled statically with libdescrypt, or libcrypt linked to libdescrypt on FreeBSD in order to authenticate Frontpage users. Now that we have the FreeBSD extentsions, fpsrvadm.exe is compiled dynamically with libcrypt. Unfortunately, RTR forgot to test fpsrvadm.exe with libscrypt, thus MD5 passwords didn't work. Scot PS. This doesn't belong on STABLE anymore, so adjust you replies accordingly. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: apach+ssl+php port
From: "fbsd stable" <[EMAIL PROTECTED]> > ... one question though, if i have just the plain > apache-1.3.12 installed and would want to install it > with FP extensions, would i have to uninstall > apache-1.3.12 first then install apache13-fp ?or is it > ok to install the apache13-fp port right away? i am > running FBSD-4.1 stable though ... > To go from apache13 -> apache13-fp: 1. Build the apache13-fp port cd /usr/ports/www/apache13-fp make build 2. Edit /usr/local/etc/apache/httpd.conf, change "AllowOverride: None" to "AllowOverride: All" for the Document Root. NOTE: Needed for fpsrvadm.exe during install. 3. Stop apache13 & uninstall apache13 /usr/local/etc/rc.d/apache.sh stop pkg_delete apache-1.3.12 4. Install apache13-fp make install 5. Compare httpd.conf with httpd.conf-default 6. Start apache13-fp /usr/local/etc/rc.d/apache.sh start Scot To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: apach+ssl+php port
From: "Vincent Poy" <[EMAIL PROTECTED]> > I noticed on your website that both you and Matthew Dodd were > working on Apache and modules: mod_ssl, mod_frontpage, mod_php3, mod_php4, > and mod_jserv. > > Aren't these already available? > mod_jserv (aka apache-jserv), mod_php3, mod_php4 are currently available in the ports collection. mod_frontpage - requires a patched Apache server (from website only) mod_ssl - requires an apache+eapi server (from website only) The ports on the website are a bit out of date, and will require a bit of work to bring them back to fully functional ports. Scot To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: sendmail missing?
From: "Jim Mock" <[EMAIL PROTECTED]> > On Wed, 26 Apr 2000 at 18:38:02 -0700, Chad R. Larson wrote: > > As I recall, Jim Mock wrote: > > > On Wed, 26 Apr 2000 at 17:42:11 -0700, Chad R. Larson wrote: > > > > This may have already been discussed on some other list, but I'm > > > > surprised to find sendmail has gone missing from the ports > > > > collection. > > > > > But if so, why isn't it? We've got ports for things like Adobe > > Acrobat, which only fetch and install a binary. We surely could fetch > > and build sendmail from Sendmail.org. > There was talk on creating a sendmail port on the current list last year, when it was proposed that sendmail be replaced with postfix(?). There is no reason not to have a port for sendmail as it allows us to use the latest version, while we wait for it to get imported into base system. Check the PR database to see if someone has cobbled together a sendmail port, if not see if you can create one and submit it to the ports collection. > There's no real reason to have the same version of sendmail available in > the base system as in the ports tree. I do think, however, that if > there are beta versions of sendmail available, a port of it is > reasonable for the simple fact that the source tree has the latest > 'stable' version of it even though some people would want newer betas. > Then again, there's no reason why you can't compile sendmail from source > since it works just fine ;-) > The latest release of Sendmail is 8.10.1, while in stable & current we have 8.9.3. Some one should put together a port of Sendmail 8.10, with optional support on the security/cyrus-sasl port (Adds AUTH capability to Sendmail). Scot To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: build failure
From: "Kip Macy" <[EMAIL PROTECTED]> > I just grabbed the source from > ftp://ftp3.freebsd.org/u/FreeBSD/releases/i386/3.3-RELEASE/src/ > and ran install.sh. That always built in the past when I grabbed it from > ftp.freebsd.org, but the encryption source may no longer be included due > to export restrictions. Is that the case? The Crypto sources were never included in the src directory, you need to install them separately by getting them from the des directory (scrypto.*, skerbero.*, ssecure.*). NOTE: if your not in the US/CANADA you need to fetch them from ftp.internat.freebsd.org. Scot To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
