FTP server at freebsd.isc.org is broken
During an unattended, non-interactive build of many ports this evening I ran into what I think indicates that the FTP server at freebsd.isc.org is broken. Here is what I believe to be evidence, performed from a FreeBSD 8.2 server at one site: site1# fetch -vvp ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/GD-Arrow-0.01.tar.gz scheme: [ftp] user: [] password: [] host: [ftp.freebsd.org] port: [0] document: [/pub/FreeBSD/ports/distfiles/GD-Arrow-0.01.tar.gz] --- ftp.freebsd.org:21 looking up ftp.freebsd.org connecting to ftp.freebsd.org:21 220 Welcome to freebsd.isc.org. USER anonymous 331 Please specify the password. PASS ag...@rose.agile.lan 500 OOPS: cannot change directory:/home/ftp fetch: ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/GD-Arrow-0.01.tar.gz: Syntax error, command unrecognized # echo $FTP_PASSIVE_MODE YES site1# ftp freebsd.isc.org Trying 204.152.184.73... Connected to freebsd.isc.org. 220 Welcome to freebsd.isc.org. Name (freebsd.isc.org:agile): anonymous 331 Please specify the password. Password: 500 OOPS: cannot change directory:/home/ftp ftp: Login failed. ftp bye 500 OOPS: priv_sock_get_cmd There's no reason that I know of for anything on my end to be referencing /home/ftp. I get this on a Windoze system from a second site (different LAN, different WAN address, same city, same ISP): C:\ftp freebsd.isc.org Connected to freebsd.isc.org. 220 Welcome to freebsd.isc.org. User (freebsd.isc.org:(none)): anonymous 331 Please specify the password. Password: 500 OOPS: cannot change directory:/home/ftp 500 OOPS: priv_sock_get_cmd Connection closed by remote host. And I found this blog entry dated today in which the author is seeing the same problem: http://salihsblog.blogspot.com/2011/05/freebsd-pkgadd-error-syntax-error.html (http://tinyurl.com/42g7dv5) When problems like this arise, shouldn't the FreeBSD port building mechanisms take advantage of the redundant FreeBSD mirrors to roll over to another working server? I use portmaster for port building and it terminates with this sort of output when this scenario arises: = Attempting to fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/gd-2.0.35.tar.bz2 fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/gd-2.0.35.tar.bz2: Syntax error, command unrecognized = Couldn't fetch it - please try to retrieve this = port manually into /usr/ports/distfiles// and try again. *** Error code 1 Stop in /usr/ports/graphics/gd. What is the recommended way to enable portmaster to be more resilient against such failures? Carl / K0802647 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: src upgrading jails (no ezjail, no service jails)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5/31/11 11:00 PM, Aleksandr Miroslav wrote: I have 4 jails that are running 8.2-RELEASE that I would like to upgrade. The host system, which was also running 8.2-RELEASE, has been successfully upgraded to 8.2-p2. I have /usr/src ready with the new world and new kernel. I did not create the jails using ezjails, so I cannot use that utility to upgrade it. I did not create the jails using the template method described in Handbook (section 15.6.1.2), so the method recommended to upgrade them, i.e.: http://www.freebsd.org/doc/handbook/jails-application.html#JAILS-SERVICE-JAILS-UPGRADING would not work for me. What is the proper way for me to upgrade these jails? thanks, Alex Hi Alex, You can do this: cd /usr/src make installworld DESTDIR=jaildir1 make distribution DESTDIR=jaildir1 ... ... make installworld DESTDIR=jaildirN make distribution DESTDIR=jaildirN Then restart your jails. Regards, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/cpucycle/ - Follow you, follow me -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3mOp0ACgkQ0sRouByUApAvyQCfYDh/dwd5/PB2zElwPuz1NC+D I8kAoJ+tS9UaQqMDHmxophZ8F+dBuMuI =eiBQ -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
perl5.12 - perl5.14 upgrade problem
I try to upgrade perl5.12 to perl5.14 according to /usr/ports/UPDATING of date 110517 the step Reinstall everything that depends on Perl : # portupgrade -fr perl in my case, needs to recompile 318 packages (pkg_info -R perl-5.14.0 | wc -l ) but I get: ... make: don't know how to make /usr/local/lib/perl5/5.14.0/mach/CORE/cc_runtime.h. Stop causing not to rebuild the following packages Stop in /usr/ports/net-mgmt/net-snmp Stop in /usr/ports/www/p5-HTML-Parser Stop in /usr/ports/textproc/p5-XML-Parser Stop in /usr/ports/databases/p5-DBI Stop in /usr/ports/devel/p5-IO-Tty Stop in /usr/ports/x11-toolkits/p5-Tk Stop in /usr/ports/graphics/p5-GD Stop in /usr/ports/databases/rrdtool Stop in /usr/ports/www/mod_perl2 Stop in /usr/ports/converters/p5-MIME-Base64 Stop in /usr/ports/graphics/ImageMagick and checking for XML::Parser... configure: error: XML::Parser perl module is required for intltool === Script configure failed unexpectedly causes not to rebuild: Stop in /usr/ports/misc/shared-mime-info Stop in /usr/ports/sysutils/polkit Stop in /usr/ports/sysutils/policykit and the recompile of another 58 packages were skipped 'because requisite package failed' (one of the above) So it seems to all boil down to that one cause: I DO NOT have a file /usr/local/lib/perl5/5.14.0/mach/CORE/cc_runtime.h in the /usr/local/lib/perl5/5.14.0/mach/CORE directory 1. why, what's wrong and how to fix ? 2. when fixed, if I do a # portupgrade -fr perl again, it there some way to avoid recompiling everything that already compiled successfully ? ( so far some 250 packages compiled successfully but this took 10 hours ...) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: I486_CPU or I586_CPU in kernel config
On Mon, 30 May 2011, Warren Block wrote: On Mon, 30 May 2011, Adam Vande More wrote: Perhaps this is the one you meant? http://lists.freebsd.org/pipermail/freebsd-questions/2009-January/190568.html That's the one! Thanks! Actually the two threads touch on the same subject, and it seems removal of those options is still desirable on newer CPU's. sys/i386/i386/support.s is mentioned, but doesn't seem to have anything explicitly specific for 586. There are some i686 entries. A test for cpu_class==CPUCLASS_586 in /sys/i386/isa/npx.c is mentioned in the thread, but that check isn't in the current code. A little empirical testing: Times for buildworld after a fresh reboot, /usr/obj/usr deleted, GENERIC included, running ccache: default (486/586 included) 9:05.84 nocpu I486, nocpu I586_CPU 9.27.88 nocpu I486_CPU 8.53.86 So maybe a 6% increase by removing 486 but leaving 586... These were not rigorous benchmarks, it might just be measurement noise. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
