sg[..] errors / warnings

Hi, I just noticed my system (4.2-STABLE as of Nov. 23) reporting a couple messages that don't say me much. As they contain a time out related to ahc0, they seem very much to be relevant for scsi. Over the weekend, the machine rebooted once after reporting these errors. Now, they appeared again w

Buildworld fails for perl

A freshly cvsup'd -stable. Doing "make buildworld": ... Cleaning current config before rebuilding Makefile... make -f Makefile.old clean > /dev/null 2>&1 || /bin/sh -c true /usr/obj/usr/src/gnu/usr.bin/perl/perl/../miniperl/miniperl "-I/usr/obj/usr/src/gnu/usr.bin/perl/perl/lib" "-I/usr/obj/usr

Re: Suggestion for change of /usr/src/UPDATING (was: Re: HEADS UP! Always use the 'make buildkernel' target to make yer kernels)

Johan Karlsson <[EMAIL PROTECTED]> writes: > This has been taken care of in current but in a slightly different way. > When using the build/installkernel targets the built / installed kernel > is named 'kernel' > Hence, when these changes are MFC:ed this part is not needed at all in > UPDATING.

Re: HEADS UP: /etc/rc.shutdown calls local scripts now

Thomas Gellekum <[EMAIL PROTECTED]> writes: > | exit 64 Is this return code 64 on intention or would everything else besides 0 be ok too? Roland To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message

Re: [Conspectus] -stable, week ending 5th June 2000

Josef Karthauser <[EMAIL PROTECTED]> writes: > Are we going to see any more of these Nik? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message

Re: hosts.allow: deny set but ping requests come through

Tobias Roth <[EMAIL PROTECTED]> writes: > Your tcp dump says that you send out an ICMP reply. ICMP != tcp. Correct. "Dan Larsson" <[EMAIL PROTECTED]> writes: > These have nothing to do with icmp restrictions, use firewall rules > to limit icmp: 'man 8 ipfw' Good point and thanks for the point

Re: Error building freshly cvsuped libcrypt

Kris Kennaway wrote: > The original person was probably cvsupping his secure/ sources to > -CURRENT, not -STABLE. That was me, and yes it's true. I cvsupped src-all using tag=RELENG_3 and crypto using RELENG=. That's what happens when one simply copies over the provided cvsup file examples witho