From owner-freebsd-current  Sun Dec 17  6:53: 8 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 17 06:53:06 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mimer.webgiro.com (unknown [213.162.128.50])
	by hub.freebsd.org (Postfix) with ESMTP id 8DE5C37B400
	for <freebsd-current@freebsd.org>; Sun, 17 Dec 2000 06:53:05 -0800 (PST)
Received: by mimer.webgiro.com (Postfix, from userid 66)
	id A53FB2DC0B; Sun, 17 Dec 2000 15:57:26 +0100 (CET)
Received: by mx.webgiro.com (Postfix, from userid 1001)
	id 73DDF7817; Sun, 17 Dec 2000 15:50:51 +0100 (CET)
Received: from localhost (localhost [127.0.0.1])
	by mx.webgiro.com (Postfix) with ESMTP
	id 662F010E1B; Sun, 17 Dec 2000 15:50:51 +0100 (CET)
Date: Sun, 17 Dec 2000 15:50:51 +0100 (CET)
From: Andrzej Bialecki <abial@webgiro.com>
To: "Jonathan M. Bresler" <jmb@hub.freebsd.org>
Cc: freebsd@dohd.org, freebsd-current@freebsd.org
Subject: Re: fxp driver not reset after Windows reboot?
In-Reply-To: <20001217015226.19E7637B400@hub.freebsd.org>
Message-ID: <Pine.BSF.4.20.0012171547290.35309-100000@mx.webgiro.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, 16 Dec 2000, Jonathan M. Bresler wrote:

> 
> Andrzej,
> 
> 	did you receive a response regarding your email the  <Intel
> Pro 10/100B/100+ Ethernet> being unresponsive after running windows?
> i seem to have the same problem.

Yes and no. The answer provided by dg (I think)  was that Win powered
it down, and our apm doesn't know how to restore it. But no fix was
forthcoming, as far as my knowledge goes..

For me, it helps when I power-cycle - soft reboot sometimes helps as well.

Andrzej Bialecki

//  <abial@webgiro.com> WebGiro AB, Sweden (http://www.webgiro.com)
// -------------------------------------------------------------------
// ------ FreeBSD: The Power to Serve. http://www.freebsd.org --------
// --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ----




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


From owner-freebsd-current  Sun Dec 17  8:57:54 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 17 08:57:51 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from ns5.pacific.net.au (ns5.pacific.net.au [203.143.252.30])
	by hub.freebsd.org (Postfix) with ESMTP id CA56E37B698
	for <current@freebsd.org>; Sun, 17 Dec 2000 08:57:49 -0800 (PST)
Received: from dungeon.home (ppp220.dyn249.pacific.net.au [203.143.249.220])
	by ns5.pacific.net.au (8.9.0/8.9.1) with ESMTP id DAA08045;
	Mon, 18 Dec 2000 03:57:44 +1100 (EST)
Received: from dungeon.home (localhost [127.0.0.1])
	by dungeon.home (8.11.1/8.9.3) with ESMTP id eBHGwGW24109;
	Mon, 18 Dec 2000 02:58:16 +1000 (EST)
	(envelope-from mckay)
Message-Id: <200012171658.eBHGwGW24109@dungeon.home>
To: "Donald J . Maddox" <dmaddox@sc.rr.com>
Cc: current@freebsd.org, mckay@thehub.com.au
Subject: Re: Is compatibility for old aout binaries broken? 
References: <20001216161756.A6370@cae88-102-101.sc.rr.com>
In-Reply-To: <20001216161756.A6370@cae88-102-101.sc.rr.com>
    from "Donald J . Maddox" at "Sat, 16 Dec 2000 21:17:57 +0000"
Date: Mon, 18 Dec 2000 02:58:16 +1000
From: Stephen McKay <mckay@thehub.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Saturday, 16th December 2000, "Donald J . Maddox" wrote:

>The other day, on a whim, I decided to try running an old binary
>of SimCity (the same one found in the 'commerce' directory on
>many FBSD cds), and it failed in a odd way...

You and I may be the only people in the world that run old binaries.
This has been broken for new users for some time. :-(  Those of us
upgrading from source have been immune to this problem, because we
retain the old a.out ld.so binary.

>/usr/libexec/ld.so: Undefined symbol "___error" called from sim:/usr/X11R6/lib
>/aout/libX11.so.6.1 at 0x20160644

When errno became a function that returns a pointer (previously it was
a simple integer variable), recompiled libraries became incompatable with
old binaries.  So, I hacked the a.out loader (ld.so).  The fix was in 3.0.
Well, Nate called it a horrible hack, so maybe I should say "the hack was
in 3.0".

>Am I overlooking something obvious here, or is something actually
>broken with respect to running old aout binaries?

I found that rtld-aout won't compile.  That's kinda broken.
(It's probably something simple.  Looks like the a.out version of
a pic library just isn't around any more).  I'll try harder later.
What's certain is that it isn't compiled by default.

I poked about with my old FreeBSD CD collection and found that
version 3.0 through 3.2 have a fully functioning (fully hack enabled)
ld.so, but an older binary has been substituted in 3.3 and onward,
including 4.0 and 4.1, and most likely 4.2 also.

I can only guess that some anonymous release engineer (nobody we know :-)
picked the wrong CD at some point to get the master copy of ld.so once
it stopped compiling.  (Or at least stopped being easily compiled.)

Ideally, rtld-aout would be compiled fresh for every release.  Until then,
you can repair your system by retrieving ld.so from a 3.3 CD (in the
compat22 section), or from a 3.2 live filesystem CD.

Stephen.


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


From owner-freebsd-current  Sun Dec 17 10:54:37 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 17 10:54:34 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from cae88-102-101.sc.rr.com (cae88-102-101.sc.rr.com [24.88.102.101])
	by hub.freebsd.org (Postfix) with ESMTP id F17AA37B400
	for <current@FreeBSD.ORG>; Sun, 17 Dec 2000 10:54:33 -0800 (PST)
Received: (from dmaddox@localhost)
	by cae88-102-101.sc.rr.com (8.11.1/8.11.1) id eBHIsVR09927;
	Sun, 17 Dec 2000 13:54:31 -0500 (EST)
	(envelope-from dmaddox)
Date: Sun, 17 Dec 2000 13:54:31 -0500
From: "Donald J . Maddox" <dmaddox@sc.rr.com>
To: Stephen McKay <mckay@thehub.com.au>
Cc: "Donald J . Maddox" <dmaddox@sc.rr.com>, current@FreeBSD.ORG
Subject: Re: Is compatibility for old aout binaries broken?
Message-ID: <20001217135431.C9721@cae88-102-101.sc.rr.com>
Reply-To: dmaddox@sc.rr.com
Mail-Followup-To: Stephen McKay <mckay@thehub.com.au>,
	"Donald J . Maddox" <dmaddox@sc.rr.com>, current@FreeBSD.ORG
References: <20001216161756.A6370@cae88-102-101.sc.rr.com> <200012171658.eBHGwGW24109@dungeon.home>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <200012171658.eBHGwGW24109@dungeon.home>; from mckay@thehub.com.au on Mon, Dec 18, 2000 at 02:58:16AM +1000
Return-Receipt-To: dmaddox@sc.rr.com
Sender: dmaddox@cae88-102-101.sc.rr.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Ok, thanks for a very enlightening explanation :)

Under the circumstances, it seems silly to have aout conpat
bits installed at all, seeing as how they cannot work.

Like you, I normally upgrade from source --  This box has
been -current ever since 2.0.5 or so was -current, but I
had to reinstall from scratch a while back by installing
4.2-RELEASE and then cvsupping back to -current, so I
guess I lost my working aout ld.so in the process.  Bummer :(

On Mon, Dec 18, 2000 at 02:58:16AM +1000, Stephen McKay wrote:
> On Saturday, 16th December 2000, "Donald J . Maddox" wrote:
> 
> >The other day, on a whim, I decided to try running an old binary
> >of SimCity (the same one found in the 'commerce' directory on
> >many FBSD cds), and it failed in a odd way...
> 
> You and I may be the only people in the world that run old binaries.
> This has been broken for new users for some time. :-(  Those of us
> upgrading from source have been immune to this problem, because we
> retain the old a.out ld.so binary.
> 
> >/usr/libexec/ld.so: Undefined symbol "___error" called from sim:/usr/X11R6/lib
> >/aout/libX11.so.6.1 at 0x20160644
> 
> When errno became a function that returns a pointer (previously it was
> a simple integer variable), recompiled libraries became incompatable with
> old binaries.  So, I hacked the a.out loader (ld.so).  The fix was in 3.0.
> Well, Nate called it a horrible hack, so maybe I should say "the hack was
> in 3.0".
> 
> >Am I overlooking something obvious here, or is something actually
> >broken with respect to running old aout binaries?
> 
> I found that rtld-aout won't compile.  That's kinda broken.
> (It's probably something simple.  Looks like the a.out version of
> a pic library just isn't around any more).  I'll try harder later.
> What's certain is that it isn't compiled by default.
> 
> I poked about with my old FreeBSD CD collection and found that
> version 3.0 through 3.2 have a fully functioning (fully hack enabled)
> ld.so, but an older binary has been substituted in 3.3 and onward,
> including 4.0 and 4.1, and most likely 4.2 also.
> 
> I can only guess that some anonymous release engineer (nobody we know :-)
> picked the wrong CD at some point to get the master copy of ld.so once
> it stopped compiling.  (Or at least stopped being easily compiled.)
> 
> Ideally, rtld-aout would be compiled fresh for every release.  Until then,
> you can repair your system by retrieving ld.so from a 3.3 CD (in the
> compat22 section), or from a 3.2 live filesystem CD.
> 
> Stephen.
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message


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


From owner-freebsd-current  Sun Dec 17 11:23:54 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 17 11:23:44 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147])
	by hub.freebsd.org (Postfix) with ESMTP id F136E37B402
	for <current@freebsd.org>; Sun, 17 Dec 2000 11:23:43 -0800 (PST)
Received: from critter (localhost [127.0.0.1])
	by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eBHJNhf20745
	for <current@freebsd.org>; Sun, 17 Dec 2000 20:23:43 +0100 (CET)
	(envelope-from phk@critter.freebsd.dk)
To: current@freebsd.org
Subject: test/review: /dev/console logging patch
From: Poul-Henning Kamp <phk@freebsd.org>
Date: Sun, 17 Dec 2000 20:23:43 +0100
Message-ID: <20743.977081023@critter>
Sender: phk@critter.freebsd.dk
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


This patch is for the printf(9), log(9) & /dev/console stuff.
The result is that you can watch the output from /etc/rc in
your /var/log/messages.

Poul-Henning


1. Replace logwakeup() with msgbuftrigger++;  There is little
   point in calling a function to set a flag.

2. Keep better track of the syslog FAC/PRI code and try to DTRT
   if they mingle.

3. Log all writes to /dev/console to syslog with <console.info>
   priority.



Index: kern/subr_log.c
===================================================================
RCS file: /home/ncvs/src/sys/kern/subr_log.c,v
retrieving revision 1.41
diff -u -r1.41 subr_log.c
--- kern/subr_log.c	2000/12/15 21:23:32	1.41
+++ kern/subr_log.c	2000/12/17 10:41:09
@@ -56,7 +56,6 @@
 
 #define LOG_ASYNC	0x04
 #define LOG_RDWAIT	0x08
-#define LOG_NEEDWAKEUP	0x10
 
 static	d_open_t	logopen;
 static	d_close_t	logclose;
@@ -186,22 +185,13 @@
 	return (revents);
 }
 
-void
-logwakeup(void)
-{
-
-	if (!log_open)
-		return;
-	logsoftc.sc_state |= LOG_NEEDWAKEUP;
-}
-
 static void
 logtimeout(void *arg)
 {
 
-	if ((logsoftc.sc_state & LOG_NEEDWAKEUP) == 0)
+	if (msgbuftrigger == 0)
 		return;
-	logsoftc.sc_state &= ~LOG_NEEDWAKEUP;
+	msgbuftrigger = 0;
 	if (!log_open)
 		return;
 	selwakeup(&logsoftc.sc_selp);
Index: kern/subr_prf.c
===================================================================
RCS file: /home/ncvs/src/sys/kern/subr_prf.c,v
retrieving revision 1.66
diff -u -r1.66 subr_prf.c
--- kern/subr_prf.c	2000/11/26 20:35:18	1.66
+++ kern/subr_prf.c	2000/12/17 19:11:02
@@ -48,6 +48,7 @@
 #include <sys/tty.h>
 #include <sys/syslog.h>
 #include <sys/cons.h>
+#include <sys/uio.h>
 
 /*
  * Note that stdarg.h and the ANSI style va_start macro is used for both
@@ -64,6 +65,7 @@
 
 struct putchar_arg {
 	int	flags;
+	int	pri;
 	struct	tty *tty;
 };
 
@@ -72,11 +74,13 @@
 	size_t	remain;
 };
 
+extern	int log_open;
+
 struct	tty *constty;			/* pointer to console "window" tty */
 
 static void (*v_putc)(int) = cnputc;	/* routine to putc on virtual console */
-static void  logpri __P((int level));
-static void  msglogchar(int c, void *dummyarg);
+static void  msglogchar(int c, int pri);
+static void  msgaddchar(int c, void *dummy);
 static void  putchar __P((int ch, void *arg));
 static char *ksprintn __P((char *nbuf, u_long num, int base, int *len));
 static char *ksprintqn __P((char *nbuf, u_quad_t num, int base, int *len));
@@ -84,13 +88,13 @@
 
 static int consintr = 1;		/* Ok to handle console interrupts? */
 static int msgbufmapped;		/* Set when safe to use msgbuf */
+int msgbuftrigger = 0;
 
 /*
  * Warn that a system table is full.
  */
 void
-tablefull(tab)
-	const char *tab;
+tablefull(const char *tab)
 {
 
 	log(LOG_ERR, "%s: table is full\n", tab);
@@ -133,10 +137,8 @@
 	struct putchar_arg pca;
 	int retval;
 
-	if (pri != -1) {
-		logpri(pri);
+	if (pri != -1)
 		flags |= TOLOG;
-	}
 	if (p->p_flag & P_CONTROLT && p->p_session->s_ttyvp) {
 		SESSHOLD(p->p_session);
 		shld++;
@@ -145,6 +147,7 @@
 			tp = p->p_session->s_ttyp;
 		}
 	}
+	pca.pri = pri;
 	pca.tty = tp;
 	pca.flags = flags;
 	va_start(ap, fmt);
@@ -152,7 +155,7 @@
 	va_end(ap);
 	if (shld)
 		SESSRELE(p->p_session);
-	logwakeup();
+	msgbuftrigger++;
 }
 
 /*
@@ -175,8 +178,6 @@
 	return retval;
 }
 
-extern	int log_open;
-
 /*
  * Log writes to the log buffer, and guarantees not to sleep (so can be
  * called by interrupt routines).  If there is no process reading the
@@ -185,41 +186,61 @@
 void
 log(int level, const char *fmt, ...)
 {
-	int s;
 	va_list ap;
 	int retval;
+	struct putchar_arg pca;
 
-	s = splhigh();
-	if (level != -1)
-		logpri(level);
-	va_start(ap, fmt);
+	pca.tty = NULL;
+	pca.pri = level;
+	pca.flags = log_open ? TOLOG : TOCONS;
 
-	retval = kvprintf(fmt, msglogchar, NULL, 10, ap);
+	va_start(ap, fmt);
+	retval = kvprintf(fmt, putchar, &pca, 10, ap);
 	va_end(ap);
 
-	splx(s);
-	if (!log_open) {
-		struct putchar_arg pca;
-		va_start(ap, fmt);
-		pca.tty = NULL;
-		pca.flags = TOCONS;
-		retval += kvprintf(fmt, putchar, &pca, 10, ap);
-		va_end(ap);
-	}
-	logwakeup();
+	msgbuftrigger++;
 }
 
-static void
-logpri(level)
-	int level;
-{
-	char nbuf[MAXNBUF];
-	char *p;
+#define CONSCHUNK 128
 
-	msglogchar('<', NULL);
-	for (p = ksprintn(nbuf, (u_long)level, 10, NULL); *p;)
-		msglogchar(*p--, NULL);
-	msglogchar('>', NULL);
+void
+log_console(struct uio *uio)
+{
+	int c, i, error, iovlen, nl;
+	struct uio muio;
+	struct iovec *miov = NULL;
+	char *consbuffer;
+	int pri;
+
+	pri = LOG_INFO | LOG_CONSOLE;
+	muio = *uio;
+	iovlen = uio->uio_iovcnt * sizeof (struct iovec);
+	MALLOC(miov, struct iovec *, iovlen, M_TEMP, M_WAITOK);
+	MALLOC(consbuffer, char *, CONSCHUNK, M_TEMP, M_WAITOK);
+	bcopy((caddr_t)muio.uio_iov, (caddr_t)miov, iovlen);
+	muio.uio_iov = miov;
+	uio = &muio;
+
+	nl = 0;
+	while (uio->uio_resid > 0) {
+		c = imin(uio->uio_resid, CONSCHUNK);
+		error = uiomove(consbuffer, c, uio);
+		if (error != 0)
+			return;
+		for (i = 0; i < c; i++) {
+			msglogchar(consbuffer[i], pri);
+			if (consbuffer[i] == '\n')
+				nl = 1;
+			else
+				nl = 0;
+		}
+	}
+	if (!nl)
+		msglogchar('\n', pri);
+	msgbuftrigger++;
+	FREE(miov, M_TEMP);
+	FREE(consbuffer, M_TEMP);
+	return;
 }
 
 int
@@ -235,10 +256,11 @@
 	va_start(ap, fmt);
 	pca.tty = NULL;
 	pca.flags = TOCONS | TOLOG;
+	pca.pri = -1;
 	retval = kvprintf(fmt, putchar, &pca, 10, ap);
 	va_end(ap);
 	if (!panicstr)
-		logwakeup();
+		msgbuftrigger++;
 	consintr = savintr;		/* reenable interrupts */
 	return retval;
 }
@@ -254,9 +276,10 @@
 	consintr = 0;
 	pca.tty = NULL;
 	pca.flags = TOCONS | TOLOG;
+	pca.pri = -1;
 	retval = kvprintf(fmt, putchar, &pca, 10, ap);
 	if (!panicstr)
-		logwakeup();
+		msgbuftrigger++;
 	consintr = savintr;		/* reenable interrupts */
 	return retval;
 }
@@ -282,7 +305,7 @@
 	    (flags & TOCONS) && tp == constty)
 		constty = NULL;
 	if ((flags & TOLOG))
-		msglogchar(c, NULL);
+		msglogchar(c, ap->pri);
 	if ((flags & TOCONS) && constty == NULL && c != '\0')
 		(*v_putc)(c);
 }
@@ -703,23 +726,58 @@
 }
 
 /*
- * Put character in log buffer.
+ * Put character in log buffer with a particular priority.
  */
 static void
-msglogchar(int c, void *dummyarg)
+msglogchar(int c, int pri)
 {
-	struct msgbuf *mbp;
+	static int lastpri = -1;
+	static int dangling;
+	char nbuf[MAXNBUF];
+	char *p;
 
-	if (c != '\0' && c != '\r' && c != 0177 && msgbufmapped) {
-		mbp = msgbufp;
-		mbp->msg_ptr[mbp->msg_bufx++] = c;
-		if (mbp->msg_bufx >= mbp->msg_size)
-			mbp->msg_bufx = 0;
-		/* If the buffer is full, keep the most recent data. */
-		if (mbp->msg_bufr == mbp->msg_bufx) {
-			if (++mbp->msg_bufr >= mbp->msg_size)
-				mbp->msg_bufr = 0;
+	if (!msgbufmapped)
+		return;
+	if (c == '\0' || c == '\r')
+		return;
+	if (pri != -1 && pri != lastpri) {
+		if (dangling) {
+			msgaddchar('\n', NULL);
+			dangling = 0;
 		}
+		msgaddchar('<', NULL);
+		for (p = ksprintn(nbuf, (u_long)pri, 10, NULL); *p;)
+			msgaddchar(*p--, NULL);
+		msgaddchar('>', NULL);
+		lastpri = pri;
+	}
+	msgaddchar(c, NULL);
+	if (c == '\n') {
+		dangling = 0;
+		lastpri = -1;
+	} else {
+		dangling = 1;
+	}
+}
+
+/*
+ * Put char in log buffer
+ */
+static void
+msgaddchar(int c, void *dummy)
+{
+	struct msgbuf *mbp;
+
+	if (!msgbufmapped)
+		return;
+	mbp = msgbufp;
+	mbp->msg_ptr[mbp->msg_bufx++] = c;
+	if (mbp->msg_bufx >= mbp->msg_size)
+		mbp->msg_bufx = 0;
+	/* If the buffer is full, keep the most recent data. */
+	if (mbp->msg_bufr == mbp->msg_bufx) {
+		if (++mbp->msg_bufr >= mbp->msg_size)
+			mbp->msg_bufr = 0;
 	}
 }
 
@@ -730,7 +788,7 @@
 
 	pos = oldp->msg_bufr;
 	while (pos != oldp->msg_bufx) {
-		msglogchar(oldp->msg_ptr[pos], NULL);
+		msglogchar(oldp->msg_ptr[pos], -1);
 		if (++pos >= oldp->msg_size)
 			pos = 0;
 	}
Index: kern/tty_cons.c
===================================================================
RCS file: /home/ncvs/src/sys/kern/tty_cons.c,v
retrieving revision 1.87
diff -u -r1.87 tty_cons.c
--- kern/tty_cons.c	2000/12/12 21:20:48	1.87
+++ kern/tty_cons.c	2000/12/13 11:28:56
@@ -353,6 +353,7 @@
 		dev = constty->t_dev;
 	else
 		dev = cn_tab->cn_dev;
+	log_console(uio);
 	return ((*devsw(dev)->d_write)(dev, uio, flag));
 }
 
Index: sys/msgbuf.h
===================================================================
RCS file: /home/ncvs/src/sys/sys/msgbuf.h,v
retrieving revision 1.14
diff -u -r1.14 msgbuf.h
--- sys/msgbuf.h	2000/01/29 15:29:11	1.14
+++ sys/msgbuf.h	2000/12/17 10:38:45
@@ -47,7 +47,7 @@
 };
 
 #ifdef _KERNEL
-extern int	msgbufmapped;
+extern int	msgbuftrigger;
 extern struct	msgbuf *msgbufp;
 void	msgbufinit	__P((void *ptr, size_t size));
 
Index: sys/systm.h
===================================================================
RCS file: /home/ncvs/src/sys/sys/systm.h,v
retrieving revision 1.130
diff -u -r1.130 systm.h
--- sys/systm.h	2000/12/06 07:09:08	1.130
+++ sys/systm.h	2000/12/17 10:37:24
@@ -107,7 +107,7 @@
 int	kvprintf __P((char const *, void (*)(int, void*), void *, int,
 		      _BSD_VA_LIST_)) __printflike(1, 0);
 void	log __P((int, const char *, ...)) __printflike(2, 3);
-void	logwakeup __P((void));
+void	log_console __P((struct uio *));
 int	printf __P((const char *, ...)) __printflike(1, 2);
 int	snprintf __P((char *, size_t, const char *, ...)) __printflike(3, 4);
 int	sprintf __P((char *buf, const char *, ...)) __printflike(2, 3);
--
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.


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


From owner-freebsd-current  Sun Dec 17 12: 0: 3 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 17 12:00:01 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229])
	by hub.freebsd.org (Postfix) with ESMTP id 745A737B400
	for <current@freebsd.org>; Sun, 17 Dec 2000 12:00:00 -0800 (PST)
Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1])
	by winston.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBHJxww07673
	for <current@freebsd.org>; Sun, 17 Dec 2000 11:59:59 -0800 (PST)
	(envelope-from jkh@winston.osd.bsdi.com)
To: current@freebsd.org
Subject: Build failure in -current
Date: Sun, 17 Dec 2000 11:59:58 -0800
Message-ID: <7670.977083198@winston.osd.bsdi.com>
From: Jordan Hubbard <jkh@winston.osd.bsdi.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

sh ../../conf/newvers.sh BOOTMFS 
cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions -ansi  -nostdinc -I-  -I. -I../.. -I../../dev -I../../../include -I../../contrib/dev/acpica/Subsystem/Include  -D_KERNEL -include opt_global.h -elf  -mpreferred-stack-boundary=2  vers.c
linking BOOTMFS
ffs_inode.o: In function `ffs_truncate':
ffs_inode.o(.text+0x2e5): undefined reference to `softdep_slowdown'
ufs_lookup.o: In function `ufs_dirremove':
ufs_lookup.o(.text+0x1175): undefined reference to `softdep_slowdown'
*** Error code 1


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


From owner-freebsd-current  Sun Dec 17 13:15:46 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 17 13:15:43 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1545C37B400; Sun, 17 Dec 2000 13:15:43 -0800 (PST)
Received: from gorean.org (Studded@master [10.0.0.2])
	by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id NAA23080;
	Sun, 17 Dec 2000 13:15:42 -0800 (PST)
	(envelope-from DougB@gorean.org)
Sender: doug@dt051n37.san.rr.com
Message-ID: <3A3D2CFD.8572F575@gorean.org>
Date: Sun, 17 Dec 2000 13:15:41 -0800
From: Doug Barton <DougB@gorean.org>
Organization: Triborough Bridge & Tunnel Authority
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Poul-Henning Kamp <phk@freebsd.org>
Cc: current@freebsd.org
Subject: Re: test/review: /dev/console logging patch
References: <20743.977081023@critter>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Poul-Henning Kamp wrote:
> 
> This patch is for the printf(9), log(9) & /dev/console stuff.
> The result is that you can watch the output from /etc/rc in
> your /var/log/messages.

	This works spectacularly for me on a UP -current with up to date
sources. The only nit I have is that it doesn't understand lines that
don't end in a newline very well (such as echo -n, or a printf with no
\n), so it produces log output like this:

Dec 17 13:00:24 <console.info> Master /boot/kernel/kernel: /dev/da1s1a: 
Dec 17 13:00:24 <console.info> Master /boot/kernel/kernel: FILESYSTEM
CLEAN; SKIPPING CHECKS
Dec 17 13:00:24 <console.info> Master /boot/kernel/kernel: /dev/da1s1a: 
Dec 17 13:00:24 <console.info> Master /boot/kernel/kernel: clean, 42202
free 
Dec 17 13:00:24 <console.info> Master /boot/kernel/kernel: (154 frags,
5256 blocks, 0.2% fragmentation)

and

Dec 17 13:00:26 <console.info> Master /boot/kernel/kernel: Doing
additional network setup:
Dec 17 13:00:26 <console.info> Master /boot/kernel/kernel: ntpdate
Dec 17 13:00:26 <console.info> Master /boot/kernel/kernel: ntpd
Dec 17 13:00:27 <console.info> Master /boot/kernel/kernel: portmap
Dec 17 13:00:27 <console.info> Master /boot/kernel/kernel: .

	Now, the first isn't a big deal, but the second is a little confusing.
Would there be any harm to changing the dots to something more
meaningful, like "Done with additional network setup" on its own line? I
seriously considered that when I was working on the echo's last night,
but I didn't want to be too revolutionary. :)

Doug
-- 
    "The most difficult thing in the world is to know how to do a thing
and
     to watch someone else do it wrong without comment."
                     -- Theodore H. White

	Do YOU Yahoo!?


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


From owner-freebsd-current  Sun Dec 17 14:29: 6 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 17 14:29:02 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from postoffice.aims.com.au (advanc2.lnk.telstra.net [139.130.119.73])
	by hub.freebsd.org (Postfix) with ESMTP id 9AE2337B402
	for <freebsd-current@FreeBSD.ORG>; Sun, 17 Dec 2000 14:28:59 -0800 (PST)
Received: from postoffice.aims.com.au (nts-ts1.aims.private [192.168.10.2])
	by postoffice.aims.com.au  with ESMTP id JAA66752
	for <freebsd-current@FreeBSD.ORG>; Mon, 18 Dec 2000 09:28:56 +1100 (EST)
	(envelope-from chris@aims.com.au)
Received: from ntsts1 by aims.com.au
	with SMTP (MDaemon.v3.5.0.R)
	for <freebsd-current@FreeBSD.ORG>; Mon, 18 Dec 2000 09:28:12 +1100
Reply-To: <chris@aims.com.au>
From: "Chris Knight" <chris@aims.com.au>
To: <freebsd-current@FreeBSD.ORG>
Cc: <jkh@FreeBSD.ORG>
Subject: RE: Build failure in -current
Date: Mon, 18 Dec 2000 09:28:11 +1100
Message-ID: <000601c06878$a417a0b0$020aa8c0@aims.private>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0007_01C068D4.D78818B0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
In-Reply-To: <7670.977083198@winston.osd.bsdi.com>
Importance: Normal
X-Return-Path: chris@aims.com.au
X-MDaemon-Deliver-To: freebsd-current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01C068D4.D78818B0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Howdy,

I've been noticing this on my daily builds for the last five days. I've just
tried the attached patch, which works for me.

Regards,
Chris Knight
Systems Administrator
AIMS Independent Computer Professionals
Tel: +61 3 6334 6664  Fax: +61 3 6331 7032  Mob: +61 419 528 795
Web: http://www.aims.com.au



> -----Original Message-----
> From: owner-freebsd-current@FreeBSD.ORG
> [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Jordan Hubbard
> Sent: Monday, 18 December 2000 7:00
> To: current@FreeBSD.ORG
> Subject: Build failure in -current
>
>
> sh ../../conf/newvers.sh BOOTMFS
> cc -c -O -Wall -Wredundant-decls -Wnested-externs
> -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith
> -Winline -Wcast-qual  -fformat-extensions -ansi  -nostdinc
> -I-  -I. -I../.. -I../../dev -I../../../include
> -I../../contrib/dev/acpica/Subsystem/Include  -D_KERNEL
> -include opt_global.h -elf  -mpreferred-stack-boundary=2  vers.c
> linking BOOTMFS
> ffs_inode.o: In function `ffs_truncate':
> ffs_inode.o(.text+0x2e5): undefined reference to `softdep_slowdown'
> ufs_lookup.o: In function `ufs_dirremove':
> ufs_lookup.o(.text+0x1175): undefined reference to `softdep_slowdown'
> *** Error code 1
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>

------=_NextPart_000_0007_01C068D4.D78818B0
Content-Type: application/octet-stream;
	name="dokern.sh.diff"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="dokern.sh.diff"

--- release/scripts/dokern.sh.orig	Sun Dec 17 22:07:41 2000=0A=
+++ release/scripts/dokern.sh	Sun Dec 17 22:08:17 2000=0A=
@@ -51,7 +51,6 @@=0A=
 	-e '/PROCFS/d' \=0A=
 	-e '/KTRACE/d' \=0A=
 	-e '/SYSVMSG/d' \=0A=
-	-e '/SOFTUPDATES/d' \=0A=
 	-e '/MFS/d' \=0A=
 	-e '/NFS_ROOT/d' \=0A=
 	-e '/pcm/d' \=0A=
@@ -79,7 +78,6 @@=0A=
 	-e '/PROCFS/d' \=0A=
 	-e '/KTRACE/d' \=0A=
 	-e '/SYSVMSG/d' \=0A=
-	-e '/SOFTUPDATES/d' \=0A=
 	-e '/MFS/d' \=0A=
 	-e '/NFS_ROOT/d' \=0A=
 	-e '/ncr/d' \=0A=
@@ -125,7 +123,6 @@=0A=
 	-e '/SYSV/d' \=0A=
 	-e '/P1003_1B/d' \=0A=
 	-e '/_KPOSIX_PRIORITY_SCHEDULING/d' \=0A=
-	-e '/SOFTUPDATES/d' \=0A=
 	-e '/MFS/d' \=0A=
 	-e '/NFS_ROOT/d' \=0A=
 	-e '/MSDOSFS/d' \=0A=

------=_NextPart_000_0007_01C068D4.D78818B0--




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


From owner-freebsd-current  Sun Dec 17 14:59:34 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 17 14:59:32 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82])
	by hub.freebsd.org (Postfix) with ESMTP
	id BBA0037B400; Sun, 17 Dec 2000 14:59:31 -0800 (PST)
Received: from rfx-64-6-211-149.users.reflexcom.com ([64.6.211.149]) by mailhost01.reflexnet.net  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Sun, 17 Dec 2000 14:57:52 -0800
Received: (from cjc@localhost)
	by rfx-64-6-211-149.users.reflexcom.com (8.11.0/8.11.0) id eBHMxIA44390;
	Sun, 17 Dec 2000 14:59:18 -0800 (PST)
	(envelope-from cjc)
Date: Sun, 17 Dec 2000 14:59:18 -0800
From: "Crist J. Clark" <cjclark@reflexnet.net>
To: Doug Barton <DougB@gorean.org>
Cc: Poul-Henning Kamp <phk@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: test/review: /dev/console logging patch
Message-ID: <20001217145918.K96105@149.211.6.64.reflexcom.com>
Reply-To: cjclark@alum.mit.edu
References: <20743.977081023@critter> <3A3D2CFD.8572F575@gorean.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <3A3D2CFD.8572F575@gorean.org>; from DougB@gorean.org on Sun, Dec 17, 2000 at 01:15:41PM -0800
Sender: cjc@rfx-64-6-211-149.users.reflexcom.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, Dec 17, 2000 at 01:15:41PM -0800, Doug Barton wrote:
> Poul-Henning Kamp wrote:
> > 
> > This patch is for the printf(9), log(9) & /dev/console stuff.
> > The result is that you can watch the output from /etc/rc in
> > your /var/log/messages.
> 
> 	This works spectacularly for me on a UP -current with up to date
> sources. The only nit I have is that it doesn't understand lines that
> don't end in a newline very well (such as echo -n, or a printf with no
> \n), so it produces log output like this:
> 
> Dec 17 13:00:24 <console.info> Master /boot/kernel/kernel: /dev/da1s1a: 
> Dec 17 13:00:24 <console.info> Master /boot/kernel/kernel: FILESYSTEM
> CLEAN; SKIPPING CHECKS
> Dec 17 13:00:24 <console.info> Master /boot/kernel/kernel: /dev/da1s1a: 
> Dec 17 13:00:24 <console.info> Master /boot/kernel/kernel: clean, 42202
> free 
> Dec 17 13:00:24 <console.info> Master /boot/kernel/kernel: (154 frags,
> 5256 blocks, 0.2% fragmentation)
> 
> and
> 
> Dec 17 13:00:26 <console.info> Master /boot/kernel/kernel: Doing
> additional network setup:
> Dec 17 13:00:26 <console.info> Master /boot/kernel/kernel: ntpdate
> Dec 17 13:00:26 <console.info> Master /boot/kernel/kernel: ntpd
> Dec 17 13:00:27 <console.info> Master /boot/kernel/kernel: portmap
> Dec 17 13:00:27 <console.info> Master /boot/kernel/kernel: .
> 
> 	Now, the first isn't a big deal, but the second is a little confusing.
> Would there be any harm to changing the dots to something more
> meaningful, like "Done with additional network setup" on its own line? I
> seriously considered that when I was working on the echo's last night,
> but I didn't want to be too revolutionary. :)

  s/\./(done)/

Or maybe '(finished)'?
-- 
Crist J. Clark                           cjclark@alum.mit.edu


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


From owner-freebsd-current  Sun Dec 17 15: 6: 9 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 17 15:06:07 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222])
	by hub.freebsd.org (Postfix) with ESMTP
	id 258A137B402; Sun, 17 Dec 2000 15:06:07 -0800 (PST)
Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137])
	by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eBHN5lE86558;
	Sun, 17 Dec 2000 15:05:47 -0800 (PST)
	(envelope-from jhb@foo.osd.bsdi.com)
Received: (from jhb@localhost)
	by foo.osd.bsdi.com (8.11.1/8.11.0) id eBHN4uM74462;
	Sun, 17 Dec 2000 15:04:56 -0800 (PST)
	(envelope-from jhb)
Message-ID: <XFMail.001217150456.jhb@FreeBSD.org>
X-Mailer: XFMail 1.4.0 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <20743.977081023@critter>
Date: Sun, 17 Dec 2000 15:04:56 -0800 (PST)
Organization: BSD, Inc.
From: John Baldwin <jhb@FreeBSD.ORG>
To: Poul-Henning Kamp <phk@FreeBSD.ORG>
Subject: RE: test/review: /dev/console logging patch
Cc: current@FreeBSD.ORG
Sender: jhb@foo.osd.bsdi.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 17-Dec-00 Poul-Henning Kamp wrote:
> 
> This patch is for the printf(9), log(9) & /dev/console stuff.
> The result is that you can watch the output from /etc/rc in
> your /var/log/messages.
> 
> Poul-Henning
> 
> 
> 1. Replace logwakeup() with msgbuftrigger++;  There is little
>    point in calling a function to set a flag.

Abstraction to keep other code from having to know the iternals of the log(9)
device?  Maybe use a #define for logwakeup() that does the msgbuftrigger++ to
keep the abstraction w/o the overhead?

-- 

John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/


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


From owner-freebsd-current  Sun Dec 17 15: 7:54 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 17 15:07:51 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222])
	by hub.freebsd.org (Postfix) with ESMTP
	id D097237B400; Sun, 17 Dec 2000 15:07:50 -0800 (PST)
Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137])
	by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eBHN7VE86583;
	Sun, 17 Dec 2000 15:07:31 -0800 (PST)
	(envelope-from jhb@foo.osd.bsdi.com)
Received: (from jhb@localhost)
	by foo.osd.bsdi.com (8.11.1/8.11.0) id eBHN6eu74498;
	Sun, 17 Dec 2000 15:06:40 -0800 (PST)
	(envelope-from jhb)
Message-ID: <XFMail.001217150640.jhb@FreeBSD.org>
X-Mailer: XFMail 1.4.0 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <3A3D2CFD.8572F575@gorean.org>
Date: Sun, 17 Dec 2000 15:06:40 -0800 (PST)
Organization: BSD, Inc.
From: John Baldwin <jhb@FreeBSD.ORG>
To: Doug Barton <DougB@gorean.org>
Subject: Re: test/review: /dev/console logging patch
Cc: current@FreeBSD.ORG, Poul-Henning Kamp <phk@FreeBSD.ORG>
Sender: jhb@foo.osd.bsdi.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 17-Dec-00 Doug Barton wrote:
> Poul-Henning Kamp wrote:
>> 
>> This patch is for the printf(9), log(9) & /dev/console stuff.
>> The result is that you can watch the output from /etc/rc in
>> your /var/log/messages.
> 
>       This works spectacularly for me on a UP -current with up to date
> sources. The only nit I have is that it doesn't understand lines that
> don't end in a newline very well (such as echo -n, or a printf with no
> \n), so it produces log output like this:
> 
> Dec 17 13:00:24 <console.info> Master /boot/kernel/kernel: /dev/da1s1a: 
> Dec 17 13:00:24 <console.info> Master /boot/kernel/kernel: FILESYSTEM
> CLEAN; SKIPPING CHECKS
> Dec 17 13:00:24 <console.info> Master /boot/kernel/kernel: /dev/da1s1a: 
> Dec 17 13:00:24 <console.info> Master /boot/kernel/kernel: clean, 42202
> free 
> Dec 17 13:00:24 <console.info> Master /boot/kernel/kernel: (154 frags,
> 5256 blocks, 0.2% fragmentation)
> 
> and
> 
> Dec 17 13:00:26 <console.info> Master /boot/kernel/kernel: Doing
> additional network setup:
> Dec 17 13:00:26 <console.info> Master /boot/kernel/kernel: ntpdate
> Dec 17 13:00:26 <console.info> Master /boot/kernel/kernel: ntpd
> Dec 17 13:00:27 <console.info> Master /boot/kernel/kernel: portmap
> Dec 17 13:00:27 <console.info> Master /boot/kernel/kernel: .
> 
>       Now, the first isn't a big deal, but the second is a little confusing.
> Would there be any harm to changing the dots to something more
> meaningful, like "Done with additional network setup" on its own line? I
> seriously considered that when I was working on the echo's last night,
> but I didn't want to be too revolutionary. :)

The '.'s are simple and not too cluttery.  Fixing the console to line buffer
what it sends to log(9) is a better fix, IMO.

-- 

John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/


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


From owner-freebsd-current  Sun Dec 17 15:19:26 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 17 15:19:22 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27])
	by hub.freebsd.org (Postfix) with ESMTP
	id BAD2F37B404; Sun, 17 Dec 2000 15:19:20 -0800 (PST)
Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1])
	by netau1.alcanet.com.au (8.9.3 (PHNE_18979)/8.9.3) with ESMTP id KAA18082;
	Mon, 18 Dec 2000 10:19:16 +1100 (EDT)
Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au
 (PMDF V5.2-32 #37640) with ESMTP id <01JXUH3CQ2B4909A0Z@cim.alcatel.com.au>;
 Mon, 18 Dec 2000 10:19:14 +1100
Received: (from jeremyp@localhost)	by gsmx07.alcatel.com.au (8.11.0/8.11.0)
 id eBHNJBr54500; Mon, 18 Dec 2000 10:19:11 +1100 (EST envelope-from jeremyp)
Content-return: prohibited
Date: Mon, 18 Dec 2000 10:19:11 +1100
From: Peter Jeremy <peter.jeremy@alcatel.com.au>
Subject: Re: test/review: /dev/console logging patch
In-reply-to: <XFMail.001217150640.jhb@FreeBSD.org>; from jhb@FreeBSD.ORG on
 Sun, Dec 17, 2000 at 03:06:40PM -0800
To: John Baldwin <jhb@FreeBSD.ORG>
Cc: Doug Barton <DougB@gorean.org>, current@FreeBSD.ORG,
	Poul-Henning Kamp <phk@FreeBSD.ORG>
Mail-followup-to: John Baldwin <jhb@FreeBSD.ORG>,
 Doug Barton <DougB@gorean.org>, current@FreeBSD.ORG,
 Poul-Henning Kamp <phk@FreeBSD.ORG>
Message-id: <20001218101910.O83523@gsmx07.alcatel.com.au>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-disposition: inline
User-Agent: Mutt/1.2.5i
References: <3A3D2CFD.8572F575@gorean.org> <XFMail.001217150640.jhb@FreeBSD.org>
Sender: jeremyp@gsmx07.alcatel.com.au
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On 2000-Dec-17 15:06:40 -0800, John Baldwin <jhb@FreeBSD.ORG> wrote:
>
>On 17-Dec-00 Doug Barton wrote:
>> Would there be any harm to changing the dots to something more
>> meaningful, like "Done with additional network setup" on its own line?
>
>The '.'s are simple and not too cluttery.

Agreed.  I think the current display looks reasonable on the console.
I'd prefer to fix the logging patch, rather than clutter up the
display.

>  Fixing the console to line buffer
>what it sends to log(9) is a better fix, IMO.

I'm not offering code right now, but how about using a `newline or
timeout' approach?  If there's a partial line and there's been no
console output for some number of seconds, forward the line to log(9).

Peter


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


From owner-freebsd-current  Sun Dec 17 15:54:35 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 17 15:54:33 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229])
	by hub.freebsd.org (Postfix) with ESMTP
	id DB6BB37B400; Sun, 17 Dec 2000 15:54:32 -0800 (PST)
Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1])
	by winston.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBHNsKw08574;
	Sun, 17 Dec 2000 15:54:21 -0800 (PST)
	(envelope-from jkh@winston.osd.bsdi.com)
To: chris@aims.com.au
Cc: freebsd-current@freebsd.org, jkh@freebsd.org
Subject: Re: Build failure in -current 
In-Reply-To: Message from "Chris Knight" <chris@aims.com.au> 
   of "Mon, 18 Dec 2000 09:28:11 +1100." <000601c06878$a417a0b0$020aa8c0@aims.private> 
Date: Sun, 17 Dec 2000 15:54:20 -0800
Message-ID: <8570.977097260@winston.osd.bsdi.com>
From: Jordan Hubbard <jkh@winston.osd.bsdi.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> I've been noticing this on my daily builds for the last five days. I've just
> tried the attached patch, which works for me.

Well, that's a fix, just not the right one. :)  There should be no
"dangling references" to soft updates if SOFTUPDATES is not defined.

- Jordan


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


From owner-freebsd-current  Sun Dec 17 16: 1:50 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 17 16:01:49 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from assaris.sics.se (dyna225-150.nada.kth.se [130.237.225.150])
	by hub.freebsd.org (Postfix) with ESMTP
	id 76ED237B402; Sun, 17 Dec 2000 16:01:48 -0800 (PST)
Received: (from assar@localhost)
	by assaris.sics.se (8.9.3/8.9.3) id BAA67192;
	Mon, 18 Dec 2000 01:01:40 +0100 (CET)
	(envelope-from assar)
Sender: assar@assaris.sics.se
From: assar@FreeBSD.ORG
To: <chris@aims.com.au>
Cc: <freebsd-current@FreeBSD.ORG>, <jkh@FreeBSD.ORG>
Subject: Re: Build failure in -current
References: <000601c06878$a417a0b0$020aa8c0@aims.private>
Date: 18 Dec 2000 01:01:40 +0100
In-Reply-To: "Chris Knight"'s message of "Mon, 18 Dec 2000 09:28:11 +1100"
Message-ID: <5llmtebnrv.fsf@assaris.sics.se>
Lines: 9
User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

"Chris Knight" <chris@aims.com.au> writes:
> I've been noticing this on my daily builds for the last five days. I've just
> tried the attached patch, which works for me.

But it does only solve the problem for `make release'.  Please upgrade
so that you have sys/ufs/ffs/ffs_softdep_stub.c 1.15 which should
solve the problem in a more general way.

/assar


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


From owner-freebsd-current  Sun Dec 17 16:10: 2 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 17 16:09:58 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55])
	by hub.freebsd.org (Postfix) with ESMTP
	id D00C637B400; Sun, 17 Dec 2000 16:09:57 -0800 (PST)
Received: from gorean.org (Studded@master [10.0.0.2])
	by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id QAA24524;
	Sun, 17 Dec 2000 16:09:51 -0800 (PST)
	(envelope-from DougB@gorean.org)
Sender: doug@dt051n37.san.rr.com
Message-ID: <3A3D55CF.17DD11DA@gorean.org>
Date: Sun, 17 Dec 2000 16:09:51 -0800
From: Doug Barton <DougB@gorean.org>
Organization: Triborough Bridge & Tunnel Authority
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Peter Jeremy <peter.jeremy@alcatel.com.au>
Cc: John Baldwin <jhb@FreeBSD.ORG>, current@FreeBSD.ORG,
	Poul-Henning Kamp <phk@FreeBSD.ORG>
Subject: Re: test/review: /dev/console logging patch
References: <3A3D2CFD.8572F575@gorean.org> <XFMail.001217150640.jhb@FreeBSD.org> <20001218101910.O83523@gsmx07.alcatel.com.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Peter Jeremy wrote:
> 
> On 2000-Dec-17 15:06:40 -0800, John Baldwin <jhb@FreeBSD.ORG> wrote:
> >
> >On 17-Dec-00 Doug Barton wrote:
> >> Would there be any harm to changing the dots to something more
> >> meaningful, like "Done with additional network setup" on its own line?
> >
> >.
> 
> Agreed.  I think the current display looks reasonable on the console.
> I'd prefer to fix the logging patch, rather than clutter up the
> display.

	... Which is why I didn't bother changing it. I agree that, "The '.'s
are simple and not too cluttery," for someone that has looked at them
for years and knows what they mean. They have absolutely no meaning at
all to someone who is new to freebsd. I didn't really understand what
the different lines and characters signified till I started hacking on
rc*, and I'm of somewhat above average intelligence. 

	I will however withdraw my request to change it now, since when the
netbsd stuff gets imported things will look much different anyway. 

> >  Fixing the console to line buffer
> >what it sends to log(9) is a better fix, IMO.

	Personally I regard these as seperate issues. If someone wants to "fix"
the console logger to better respect input with no newline at the end,
that is also a desirable goal of course. 

Doug
-- 
    "The most difficult thing in the world is to know how to do a thing
and
     to watch someone else do it wrong without comment."
                     -- Theodore H. White

	Do YOU Yahoo!?


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


From owner-freebsd-current  Sun Dec 17 16:33:59 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 17 16:33:57 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from postoffice.aims.com.au (advanc2.lnk.telstra.net [139.130.119.73])
	by hub.freebsd.org (Postfix) with ESMTP id 14F7F37B402
	for <freebsd-current@FreeBSD.ORG>; Sun, 17 Dec 2000 16:33:55 -0800 (PST)
Received: from postoffice.aims.com.au (nts-ts1.aims.private [192.168.10.2])
	by postoffice.aims.com.au  with ESMTP id LAA66999
	for <freebsd-current@FreeBSD.ORG>; Mon, 18 Dec 2000 11:33:48 +1100 (EST)
	(envelope-from chris@aims.com.au)
Received: from ntsts1 by aims.com.au
	with SMTP (MDaemon.v3.5.0.R)
	for <freebsd-current@FreeBSD.ORG>; Mon, 18 Dec 2000 11:33:46 +1100
Reply-To: <chris@aims.com.au>
From: "Chris Knight" <chris@aims.com.au>
To: <freebsd-current@FreeBSD.ORG>
Cc: <jkh@FreeBSD.ORG>
Subject: RE: Build failure in -current
Date: Mon, 18 Dec 2000 11:33:44 +1100
Message-ID: <000e01c0688a$2e2ed2d0$020aa8c0@aims.private>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
In-Reply-To: <8570.977097260@winston.osd.bsdi.com>
Importance: Normal
X-Return-Path: chris@aims.com.au
X-MDaemon-Deliver-To: freebsd-current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Howdy,

> -----Original Message-----
> From: owner-freebsd-current@FreeBSD.ORG
> [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Jordan Hubbard
> Sent: Monday, 18 December 2000 10:54
> To: chris@aims.com.au
> Cc: freebsd-current@FreeBSD.ORG; jkh@FreeBSD.ORG
> Subject: Re: Build failure in -current
>
>
> > I've been noticing this on my daily builds for the last
> five days. I've just
> > tried the attached patch, which works for me.
>
> Well, that's a fix, just not the right one. :)  There should be no
> "dangling references" to soft updates if SOFTUPDATES is not defined.
>
I realise that. I always use soft updates, so it wasn't a problem for me. It
took less time to add it into the boot floppies than work out what a
non-softupdates softdep_slowdown should return.

> - Jordan
>
Regards,
Chris Knight
Systems Administrator
AIMS Independent Computer Professionals
Tel: +61 3 6334 6664  Fax: +61 3 6331 7032  Mob: +61 419 528 795
Web: http://www.aims.com.au




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


From owner-freebsd-current  Sun Dec 17 16:42:36 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 17 16:42:34 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from postoffice.aims.com.au (advanc2.lnk.telstra.net [139.130.119.73])
	by hub.freebsd.org (Postfix) with ESMTP id 645FF37B400
	for <freebsd-current@FreeBSD.ORG>; Sun, 17 Dec 2000 16:42:30 -0800 (PST)
Received: from postoffice.aims.com.au (nts-ts1.aims.private [192.168.10.2])
	by postoffice.aims.com.au  with ESMTP id LAA67027
	for <freebsd-current@FreeBSD.ORG>; Mon, 18 Dec 2000 11:42:28 +1100 (EST)
	(envelope-from chris@aims.com.au)
Received: from ntsts1 by aims.com.au
	with SMTP (MDaemon.v3.5.0.R)
	for <freebsd-current@FreeBSD.ORG>; Mon, 18 Dec 2000 11:41:37 +1100
Reply-To: <chris@aims.com.au>
From: "Chris Knight" <chris@aims.com.au>
To: <freebsd-current@FreeBSD.ORG>
Cc: <assar@FreeBSD.ORG>
Subject: RE: Build failure in -current
Date: Mon, 18 Dec 2000 11:41:36 +1100
Message-ID: <001001c0688b$476ecb00$020aa8c0@aims.private>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
In-Reply-To: <5llmtebnrv.fsf@assaris.sics.se>
Importance: Normal
X-Return-Path: chris@aims.com.au
X-MDaemon-Deliver-To: freebsd-current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Howdy,

You beat me to it. I was just about to send a patch that did exactly the
same thing.

Regards,
Chris Knight
Systems Administrator
AIMS Independent Computer Professionals
Tel: +61 3 6334 6664  Fax: +61 3 6331 7032  Mob: +61 419 528 795
Web: http://www.aims.com.au



> -----Original Message-----
> From: assar@assaris.sics.se [mailto:assar@assaris.sics.se]On Behalf Of
> assar@FreeBSD.ORG
> Sent: Monday, 18 December 2000 11:02
> To: chris@aims.com.au
> Cc: freebsd-current@FreeBSD.ORG; jkh@FreeBSD.ORG
> Subject: Re: Build failure in -current
>
>
> "Chris Knight" <chris@aims.com.au> writes:
> > I've been noticing this on my daily builds for the last
> five days. I've just
> > tried the attached patch, which works for me.
>
> But it does only solve the problem for `make release'.  Please upgrade
> so that you have sys/ufs/ffs/ffs_softdep_stub.c 1.15 which should
> solve the problem in a more general way.
>
> /assar
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>




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


From owner-freebsd-current  Sun Dec 17 17: 5:51 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 17 17:05:46 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55])
	by hub.freebsd.org (Postfix) with ESMTP id D7DDB37B400
	for <freebsd-current@freebsd.org>; Sun, 17 Dec 2000 17:05:45 -0800 (PST)
Received: from gorean.org (Studded@master [10.0.0.2])
	by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id RAA24820
	for <freebsd-current@freebsd.org>; Sun, 17 Dec 2000 17:05:44 -0800 (PST)
	(envelope-from DougB@gorean.org)
Sender: doug@dt051n37.san.rr.com
Message-ID: <3A3D62E8.4453C765@gorean.org>
Date: Sun, 17 Dec 2000 17:05:44 -0800
From: Doug Barton <DougB@gorean.org>
Organization: Triborough Bridge & Tunnel Authority
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-current@freebsd.org
Subject: Panic with fairly up to date -current, seems NFS related
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

	I built -current world and kernel around 3am PST sunday morning with up
to date sources. Later that same day I added Poul-Henning's console
logging patch. Just a few minutes ago I had a lockup and panic that
thankfully produced a kernel core to work with. It looks like this is
not related to phk's patch, but rather to an NFS issue that I've seen
before. I was copying a 23M file over NFS (mounted via amd) when this
lockup and panic happened. 

	My workstation is the NFS client, running -current. The NFS server is
running FreeBSD 3.5.1-STABLE-1014 #0: Mon Oct 16 00:00:13 PDT 2000. If
anyone wants me to do more debugging with this, let me know. I'm going
out in a bit, but I will likely be available later tonight or tomorrow. 

Doug

(kgdb) core-file vmcore.1
IdlePTD 3956736
initial pcb at 3298e0
panicstr: page fault
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0x30
fault code              = supervisor read, page not present
instruction pointer     = 0x8:0xc019e887
stack pointer           = 0x10:0xc7bdeefc
frame pointer           = 0x10:0xc7bdef18
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, def32 1, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 12 (swi6: clock)
trap number             = 12
panic: page fault

syncing disks... 350 350 336 336 333 333 333 333 333 333 333 333 333 333
333 333 333 333 33
3 333 333 333 333 333 
done
Uptime: 3h41m22s

dumping to dev da1s1b, offset 262168
dump 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111
110 109 108 107 10
6 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85
84 83 82 81 80 79 78
 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54
53 52 51 50 49 48 
47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24
23 22 21 20 19 18 1
7 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 
---
#0  dumpsys () at /usr/src/sys/kern/kern_shutdown.c:477
477             if (dumping++) {


(kgdb) bt
#0  dumpsys () at /usr/src/sys/kern/kern_shutdown.c:477
#1  0xc018d910 in boot (howto=256) at
/usr/src/sys/kern/kern_shutdown.c:320
#2  0xc018dce5 in panic (fmt=0xc02c8a8f "page fault")
    at /usr/src/sys/kern/kern_shutdown.c:570
#3  0xc0282e27 in trap_fatal (frame=0xc7bdeebc, eva=48)
    at /usr/src/sys/i386/i386/trap.c:946
#4  0xc0282b71 in trap_pfault (frame=0xc7bdeebc, usermode=0, eva=48)
    at /usr/src/sys/i386/i386/trap.c:860
#5  0xc0282543 in trap (frame={tf_fs = -1066205168, tf_es = 16, tf_ds =
-1066205168, 
      tf_edi = 0, tf_esi = 0, tf_ebp = -943853800, tf_isp = -943853848,
tf_ebx = 4, 
      tf_edx = -1061221134, tf_ecx = 0, tf_eax = 4, tf_trapno = 12,
tf_err = 0, 
      tf_eip = -1072043897, tf_cs = 8, tf_eflags = 66067, tf_esp =
-1061106688, 
      tf_ss = -932128640}) at /usr/src/sys/i386/i386/trap.c:442
#6  0xc019e887 in tprintf (p=0x0, pri=6, fmt=0xc02ba7e8 "nfs server %s:
%s\n")
    at /usr/src/sys/kern/subr_prf.c:140
#7  0xc021c857 in nfs_msg (p=0x0, server=0xc0bf0cf2 "slave:/usr/home", 
    msg=0xc02ba748 "not responding") at
/usr/src/sys/nfs/nfs_socket.c:1972
#8  0xc021b742 in nfs_timer (arg=0x0) at
/usr/src/sys/nfs/nfs_socket.c:1424
#9  0xc01956d8 in softclock (dummy=0x0) at
/usr/src/sys/kern/kern_timeout.c:141
#10 0xc01834f4 in sithd_loop (dummy=0x0) at
/usr/src/sys/kern/kern_intr.c:227


Here are the results from a previous similar experience on 11/29 that I
neglected to pass on. They are eerily similar, which is why I really
don't think phk's patch is involved. 

(kgdb) core-file vmcore.0
IdlePTD 3887104
initial pcb at 326820
panicstr: page fault
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0x30
fault code              = supervisor read, page not present
instruction pointer     = 0x8:0xc019a005
stack pointer           = 0x10:0xc7be4eec
frame pointer           = 0x10:0xc7be4f04
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, def32 1, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 12 (swi6: clock)
trap number             = 12
panic: page fault

syncing disks... 371 371 371 371 371 371 371 371 371 371 371 371 371 371
371 371 371 371 37
1 371 
done
Uptime: 19h40m18s

dumping to dev da1s1b, offset 262168
dump 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111
110 109 108 107 10
6 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85
84 83 82 81 80 79 78
 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54
53 52 51 50 49 48 
47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24
23 22 21 20 19 18 1
7 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 
---
#0  dumpsys () at /usr/src/sys/kern/kern_shutdown.c:477
warning: Source file is more recent than executable.

477             if (dumping++) {
(kgdb) bt
#0  dumpsys () at /usr/src/sys/kern/kern_shutdown.c:477
#1  0xc018936e in boot (howto=256) at
/usr/src/sys/kern/kern_shutdown.c:320
#2  0xc01897bd in panic (fmt=0xc02cdeef "page fault")
    at /usr/src/sys/kern/kern_shutdown.c:568
#3  0xc0282413 in trap_fatal (frame=0xc7be4eac, eva=48)
    at /usr/src/sys/i386/i386/trap.c:941
#4  0xc028215d in trap_pfault (frame=0xc7be4eac, usermode=0, eva=48)
    at /usr/src/sys/i386/i386/trap.c:855
#5  0xc0281ba7 in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16,
tf_edi = 0, 
      tf_esi = 0, tf_ebp = -943829244, tf_isp = -943829288, tf_ebx = 4,
tf_edx = 4854, 
      tf_ecx = -1069436948, tf_eax = 4852, tf_trapno = 12, tf_err = 0, 
      tf_eip = -1072062459, tf_cs = 8, tf_eflags = 66178, tf_esp =
-1061285632, 
      tf_ss = -932070752}) at /usr/src/sys/i386/i386/trap.c:438
#6  0xc019a005 in tprintf (p=0x0, pri=6, fmt=0xc02bb488 "nfs server %s:
%s\n")
    at /usr/src/sys/kern/subr_prf.c:139
#7  0xc02166a7 in nfs_msg (p=0x0, server=0xc0be2cf2 "slave:/usr/home", 
    msg=0xc02bb3e8 "not responding") at
/usr/src/sys/nfs/nfs_socket.c:1972
#8  0xc02155fa in nfs_timer (arg=0x0) at
/usr/src/sys/nfs/nfs_socket.c:1424
#9  0xc0190e0d in softclock (dummy=0x0) at
/usr/src/sys/kern/kern_timeout.c:141
#10 0xc017f536 in sithd_loop (dummy=0x0) at
/usr/src/sys/kern/kern_intr.c:227


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


From owner-freebsd-current  Sun Dec 17 17:17:23 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 17 17:17:21 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222])
	by hub.freebsd.org (Postfix) with ESMTP id 2232437B400
	for <freebsd-current@FreeBSD.org>; Sun, 17 Dec 2000 17:17:21 -0800 (PST)
Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241])
	by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eBI1GuE89169;
	Sun, 17 Dec 2000 17:16:56 -0800 (PST)
	(envelope-from jhb@FreeBSD.org)
Message-ID: <XFMail.001217171721.jhb@FreeBSD.org>
X-Mailer: XFMail 1.4.0 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <3A3D62E8.4453C765@gorean.org>
Date: Sun, 17 Dec 2000 17:17:21 -0800 (PST)
From: John Baldwin <jhb@FreeBSD.org>
To: Doug Barton <DougB@gorean.org>
Subject: RE: Panic with fairly up to date -current, seems NFS related
Cc: freebsd-current@FreeBSD.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 18-Dec-00 Doug Barton wrote:
>       I built -current world and kernel around 3am PST sunday morning with up
> to date sources. Later that same day I added Poul-Henning's console
> logging patch. Just a few minutes ago I had a lockup and panic that
> thankfully produced a kernel core to work with. It looks like this is
> not related to phk's patch, but rather to an NFS issue that I've seen
> before. I was copying a 23M file over NFS (mounted via amd) when this
> lockup and panic happened. 
> 
>       My workstation is the NFS client, running -current. The NFS server is
> running FreeBSD 3.5.1-STABLE-1014 #0: Mon Oct 16 00:00:13 PDT 2000. If
> anyone wants me to do more debugging with this, let me know. I'm going
> out in a bit, but I will likely be available later tonight or tomorrow. 
> 
> Doug

Grog had a similar panic on IRC the other day:

>#7  0xc021c857 in nfs_msg (p=0x0, server=0xc0bf0cf2 "slave:/usr/home", 
>     msg=0xc02ba748 "not responding") at

The 'p' parameter is a process that is supposed to be making the request, and
thus is going to receive a console message to its tty about the server going
away.  Note that 'p' is NULL.  This leads to a NULL dereference in tprintf(). 
The 'p' comes from some type of NFS request structure.  That is as far as I
could take it however..

> /usr/src/sys/nfs/nfs_socket.c:1972
>#8  0xc021b742 in nfs_timer (arg=0x0) at
> /usr/src/sys/nfs/nfs_socket.c:1424
>#9  0xc01956d8 in softclock (dummy=0x0) at
> /usr/src/sys/kern/kern_timeout.c:141
>#10 0xc01834f4 in sithd_loop (dummy=0x0) at
> /usr/src/sys/kern/kern_intr.c:227

-- 

John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/


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


From owner-freebsd-current  Sun Dec 17 17:59:21 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 17 17:59:18 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from assaris.sics.se (dyna225-150.nada.kth.se [130.237.225.150])
	by hub.freebsd.org (Postfix) with ESMTP
	id 655EB37B400; Sun, 17 Dec 2000 17:59:17 -0800 (PST)
Received: (from assar@localhost)
	by assaris.sics.se (8.9.3/8.9.3) id CAA67849;
	Mon, 18 Dec 2000 02:59:26 +0100 (CET)
	(envelope-from assar)
Sender: assar@assaris.sics.se
From: assar@FreeBSD.ORG
To: John Baldwin <jhb@FreeBSD.ORG>
Cc: Doug Barton <DougB@gorean.org>, freebsd-current@FreeBSD.ORG
Subject: Re: Panic with fairly up to date -current, seems NFS related
References: <XFMail.001217171721.jhb@FreeBSD.org>
Date: 18 Dec 2000 02:59:25 +0100
In-Reply-To: John Baldwin's message of "Sun, 17 Dec 2000 17:17:21 -0800 (PST)"
Message-ID: <5lpuiqa3r6.fsf@assaris.sics.se>
Lines: 33
User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

John Baldwin <jhb@FreeBSD.ORG> writes:
> Grog had a similar panic on IRC the other day:
> 
> >#7  0xc021c857 in nfs_msg (p=0x0, server=0xc0bf0cf2 "slave:/usr/home", 
> >     msg=0xc02ba748 "not responding") at
> 
> The 'p' parameter is a process that is supposed to be making the request, and
> thus is going to receive a console message to its tty about the server going
> away.  Note that 'p' is NULL.  This leads to a NULL dereference in tprintf(). 
> The 'p' comes from some type of NFS request structure.  That is as far as I
> could take it however..

Since proc can be NULL and most of the other code in nfs_socket
handles it I do think this actually is the right thing to do.
Comments?

/assar

Index: nfs_socket.c
===================================================================
RCS file: /home/ncvs/src/sys/nfs/nfs_socket.c,v
retrieving revision 1.62
diff -u -w -u -w -r1.62 nfs_socket.c
--- nfs_socket.c	2000/11/26 20:35:21	1.62
+++ nfs_socket.c	2000/12/18 01:58:46
@@ -1969,6 +1969,7 @@
 	char *server, *msg;
 {
 
+	if (p != NULL)
 	tprintf(p, LOG_INFO, "nfs server %s: %s\n", server, msg);
 	return (0);
 }


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


From owner-freebsd-current  Sun Dec 17 18:21: 5 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 17 18:21:03 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from field.videotron.net (field.videotron.net [205.151.222.108])
	by hub.freebsd.org (Postfix) with ESMTP
	id 6F4A737B402; Sun, 17 Dec 2000 18:21:03 -0800 (PST)
Received: from modemcable213.3-201-24.mtl.mc.videotron.ca ([24.201.3.213])
 by field.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8)
 with ESMTP id <0G5Q00L0CRUWYX@field.videotron.net>; Sun, 17 Dec 2000 21:20:56 -0500 (EST)
Date: Sun, 17 Dec 2000 21:21:44 -0500 (EST)
From: Bosko Milekic <bmilekic@technokratis.com>
Subject: Re: Panic with fairly up to date -current, seems NFS related
In-reply-to: <5lpuiqa3r6.fsf@assaris.sics.se>
To: assar@FreeBSD.ORG
Cc: John Baldwin <jhb@FreeBSD.ORG>, Doug Barton <DougB@gorean.org>,
	freebsd-current@FreeBSD.ORG
Message-id: <Pine.BSF.4.21.0012172119180.430-100000@jehovah.technokratis.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 18 Dec 2000 assar@FreeBSD.ORG wrote:

> Since proc can be NULL and most of the other code in nfs_socket
> handles it I do think this actually is the right thing to do.
> Comments?

	I'm more concerned with whether it's actually normal for the process
  pointer to be NULL in the first place. Is this the case? And if so, why
  is nfs_msg() being called with this pointer being passed in in the first
  place?

> /assar
> 
[...]

  Regards,
  Bosko Milekic
  bmilekic@technokratis.com




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


From owner-freebsd-current  Sun Dec 17 18:25: 2 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 17 18:24:59 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from assaris.sics.se (dyna225-150.nada.kth.se [130.237.225.150])
	by hub.freebsd.org (Postfix) with ESMTP
	id 40D3237B400; Sun, 17 Dec 2000 18:24:58 -0800 (PST)
Received: (from assar@localhost)
	by assaris.sics.se (8.9.3/8.9.3) id DAA67943;
	Mon, 18 Dec 2000 03:25:01 +0100 (CET)
	(envelope-from assar)
Sender: assar@assaris.sics.se
From: assar@FreeBSD.ORG
To: Bosko Milekic <bmilekic@technokratis.com>
Cc: John Baldwin <jhb@FreeBSD.ORG>, Doug Barton <DougB@gorean.org>,
	freebsd-current@FreeBSD.ORG
Subject: Re: Panic with fairly up to date -current, seems NFS related
References: <Pine.BSF.4.21.0012172119180.430-100000@jehovah.technokratis.com>
Date: 18 Dec 2000 03:25:00 +0100
In-Reply-To: Bosko Milekic's message of "Sun, 17 Dec 2000 21:21:44 -0500 (EST)"
Message-ID: <5ly9xe8o03.fsf@assaris.sics.se>
Lines: 15
User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Bosko Milekic <bmilekic@technokratis.com> writes:
> 	I'm more concerned with whether it's actually normal for the process
>   pointer to be NULL in the first place. Is this the case?

One example (which I don't know if that what's happening here) is when
following symbolic links.  namei() calls VOP_READLINK with proc == NULL.

>   And if so, why is nfs_msg() being called with this pointer being
>   passed in in the first place?

Because the code doesn't check?  I thought it was easier to have the
check in nfs_msg, but it's only called in two places so doing the
check there should also work.

/assar


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


From owner-freebsd-current  Sun Dec 17 21:58: 8 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 17 21:58:06 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55])
	by hub.freebsd.org (Postfix) with ESMTP
	id 2AA0537B400; Sun, 17 Dec 2000 21:58:06 -0800 (PST)
Received: from gorean.org (Studded@master [10.0.0.2])
	by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id VAA27026;
	Sun, 17 Dec 2000 21:58:04 -0800 (PST)
	(envelope-from DougB@gorean.org)
Sender: doug@dt051n37.san.rr.com
Message-ID: <3A3DA76B.FB6944B4@gorean.org>
Date: Sun, 17 Dec 2000 21:58:04 -0800
From: Doug Barton <DougB@gorean.org>
Organization: Triborough Bridge & Tunnel Authority
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: assar@FreeBSD.ORG
Cc: Bosko Milekic <bmilekic@technokratis.com>,
	John Baldwin <jhb@FreeBSD.ORG>, freebsd-current@FreeBSD.ORG
Subject: Re: Panic with fairly up to date -current, seems NFS related
References: <Pine.BSF.4.21.0012172119180.430-100000@jehovah.technokratis.com> <5ly9xe8o03.fsf@assaris.sics.se>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

assar@FreeBSD.ORG wrote:
> 
> Bosko Milekic <bmilekic@technokratis.com> writes:
> >       I'm more concerned with whether it's actually normal for the process
> >   pointer to be NULL in the first place. Is this the case?
> 
> One example (which I don't know if that what's happening here) is when
> following symbolic links.  namei() calls VOP_READLINK with proc == NULL.

	What a coincidence, there is a symbolic link involved here. I have a
workstation, and a gateway/fileserver machine. I export /usr on the
fileserver (slave) and use amd to mount individual directories under
/usr in /mnt/slave/ on the workstation. Scattered throughout the
workstation are symbolic links to /mnt/slave/foo, which kick amd in
gear, and make those directories available where I want them. 

	I realize that this is not an ideal situation, but it's also very
common, so if someone is going to find a bug this way, it might as well
be me. :)

Doug
-- 
    "The most difficult thing in the world is to know how to do a thing
and
     to watch someone else do it wrong without comment."
                     -- Theodore H. White

	Do YOU Yahoo!?


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


From owner-freebsd-current  Sun Dec 17 22:35:28 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 17 22:35:27 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147])
	by hub.freebsd.org (Postfix) with ESMTP
	id 2562C37B400; Sun, 17 Dec 2000 22:35:26 -0800 (PST)
Received: from critter (localhost [127.0.0.1])
	by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eBI6ZOf25630;
	Mon, 18 Dec 2000 07:35:24 +0100 (CET)
	(envelope-from phk@critter.freebsd.dk)
To: John Baldwin <jhb@FreeBSD.ORG>
Cc: Doug Barton <DougB@gorean.org>, current@FreeBSD.ORG
Subject: Re: test/review: /dev/console logging patch 
In-Reply-To: Your message of "Sun, 17 Dec 2000 15:06:40 PST."
             <XFMail.001217150640.jhb@FreeBSD.org> 
Date: Mon, 18 Dec 2000 07:35:24 +0100
Message-ID: <25628.977121324@critter>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>>> 
>>> This patch is for the printf(9), log(9) & /dev/console stuff.
>>> The result is that you can watch the output from /etc/rc in
>>> your /var/log/messages.
>> 
>> Dec 17 13:00:26 <console.info> Master /boot/kernel/kernel: Doing
>> additional network setup:
>> Dec 17 13:00:26 <console.info> Master /boot/kernel/kernel: ntpdate
>> Dec 17 13:00:26 <console.info> Master /boot/kernel/kernel: ntpd
>> Dec 17 13:00:27 <console.info> Master /boot/kernel/kernel: portmap
>> Dec 17 13:00:27 <console.info> Master /boot/kernel/kernel: .
>
>The '.'s are simple and not too cluttery.  Fixing the console to line buffer
>what it sends to log(9) is a better fix, IMO.

I specifically decided not to do this because I want to be able to
see stuff like:

	echo -n "Press return to avoid disaster: " > /dev/console
	read < /dev/console

Of course one could add timeouts and what's not, but then imagine
the case of two programs writing on /dev/console at the same time...

--
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.


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


From owner-freebsd-current  Sun Dec 17 22:36:59 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 17 22:36:57 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147])
	by hub.freebsd.org (Postfix) with ESMTP
	id 09CD637B400; Sun, 17 Dec 2000 22:36:56 -0800 (PST)
Received: from critter (localhost [127.0.0.1])
	by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eBI6atf25653;
	Mon, 18 Dec 2000 07:36:55 +0100 (CET)
	(envelope-from phk@critter.freebsd.dk)
To: John Baldwin <jhb@FreeBSD.ORG>
Cc: current@FreeBSD.ORG
Subject: Re: test/review: /dev/console logging patch 
In-Reply-To: Your message of "Sun, 17 Dec 2000 15:04:56 PST."
             <XFMail.001217150456.jhb@FreeBSD.org> 
Date: Mon, 18 Dec 2000 07:36:55 +0100
Message-ID: <25651.977121415@critter>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <XFMail.001217150456.jhb@FreeBSD.org>, John Baldwin writes:
>
>On 17-Dec-00 Poul-Henning Kamp wrote:
>> 
>> This patch is for the printf(9), log(9) & /dev/console stuff.
>> The result is that you can watch the output from /etc/rc in
>> your /var/log/messages.
>> 
>> Poul-Henning
>> 
>> 
>> 1. Replace logwakeup() with msgbuftrigger++;  There is little
>>    point in calling a function to set a flag.
>
>Abstraction to keep other code from having to know the iternals of the log(9)
>device?  Maybe use a #define for logwakeup() that does the msgbuftrigger++ to
>keep the abstraction w/o the overhead?

But it was actually the other way around now :-)  It was the log
device which had obfuscated the log/printf code because it needed
it's assistance to call selwakeup.

I want the log/printf code to be as simple as possible, and to have
the smallest stack footprint possible...

--
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.


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


From owner-freebsd-current  Sun Dec 17 22:38: 3 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 17 22:38:01 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147])
	by hub.freebsd.org (Postfix) with ESMTP
	id 4036837B400; Sun, 17 Dec 2000 22:38:00 -0800 (PST)
Received: from critter (localhost [127.0.0.1])
	by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eBI6bqf25676;
	Mon, 18 Dec 2000 07:37:52 +0100 (CET)
	(envelope-from phk@critter.freebsd.dk)
To: Peter Jeremy <peter.jeremy@alcatel.com.au>
Cc: John Baldwin <jhb@FreeBSD.ORG>, Doug Barton <DougB@gorean.org>,
	current@FreeBSD.ORG
Subject: Re: test/review: /dev/console logging patch 
In-Reply-To: Your message of "Mon, 18 Dec 2000 10:19:11 +1100."
             <20001218101910.O83523@gsmx07.alcatel.com.au> 
Date: Mon, 18 Dec 2000 07:37:52 +0100
Message-ID: <25674.977121472@critter>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <20001218101910.O83523@gsmx07.alcatel.com.au>, Peter Jeremy writes:

>
>I'm not offering code right now, but how about using a `newline or
>timeout' approach?  If there's a partial line and there's been no
>console output for some number of seconds, forward the line to log(9).

I played with this, and I was not happy with the result, if somebody
else can do it better, I'm open for patches...

--
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.


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


From owner-freebsd-current  Sun Dec 17 22:40:53 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 17 22:40:50 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from ns5.pacific.net.au (ns5.pacific.net.au [203.143.252.30])
	by hub.freebsd.org (Postfix) with ESMTP id CE98137B400
	for <current@FreeBSD.ORG>; Sun, 17 Dec 2000 22:40:48 -0800 (PST)
Received: from dungeon.home (ppp171.dyn248.pacific.net.au [203.143.248.171])
	by ns5.pacific.net.au (8.9.0/8.9.1) with ESMTP id RAA16845;
	Mon, 18 Dec 2000 17:40:44 +1100 (EST)
Received: from dungeon.home (localhost [127.0.0.1])
	by dungeon.home (8.11.1/8.9.3) with ESMTP id eBI6fH607564;
	Mon, 18 Dec 2000 16:41:17 +1000 (EST)
	(envelope-from mckay)
Message-Id: <200012180641.eBI6fH607564@dungeon.home>
To: dmaddox@sc.rr.com
Cc: Stephen McKay <mckay@thehub.com.au>, current@FreeBSD.ORG
Subject: Re: Is compatibility for old aout binaries broken? 
References: <20001216161756.A6370@cae88-102-101.sc.rr.com> <200012171658.eBHGwGW24109@dungeon.home> <20001217135431.C9721@cae88-102-101.sc.rr.com>
In-Reply-To: <20001217135431.C9721@cae88-102-101.sc.rr.com>
    from "Donald J . Maddox" at "Sun, 17 Dec 2000 13:54:31 -0500"
Date: Mon, 18 Dec 2000 16:41:17 +1000
From: Stephen McKay <mckay@thehub.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sunday, 17th December 2000, "Donald J . Maddox" wrote:

>Under the circumstances, it seems silly to have aout conpat
>bits installed at all, seeing as how they cannot work.

Old programs that don't depend on recompiled libraries are fine.  I can't
guess at the percentages though.  Also, nearly everybody has recompiled
for elf, where this problem never occurred.

>Like you, I normally upgrade from source --  This box has
>been -current ever since 2.0.5 or so was -current, but I
>had to reinstall from scratch a while back by installing
>4.2-RELEASE and then cvsupping back to -current, so I
>guess I lost my working aout ld.so in the process.  Bummer :(

I expected some build tool expert to say "Just compile with these
options".  But they haven't.  So I'll see if the bits have rotted,
or whether we can keep building ld.so instead of just including
an age old binary.

Stephen.


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


From owner-freebsd-current  Sun Dec 17 22:47: 3 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 17 22:47:01 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from cae88-102-101.sc.rr.com (cae88-102-101.sc.rr.com [24.88.102.101])
	by hub.freebsd.org (Postfix) with ESMTP id 6601637B400
	for <current@FreeBSD.ORG>; Sun, 17 Dec 2000 22:47:01 -0800 (PST)
Received: (from dmaddox@localhost)
	by cae88-102-101.sc.rr.com (8.11.1/8.11.1) id eBI6kuR17498;
	Mon, 18 Dec 2000 01:46:56 -0500 (EST)
	(envelope-from dmaddox)
Date: Mon, 18 Dec 2000 01:46:56 -0500
From: "Donald J . Maddox" <dmaddox@sc.rr.com>
To: Stephen McKay <mckay@thehub.com.au>
Cc: dmaddox@sc.rr.com, current@FreeBSD.ORG
Subject: Re: Is compatibility for old aout binaries broken?
Message-ID: <20001218014656.A17483@cae88-102-101.sc.rr.com>
Reply-To: dmaddox@sc.rr.com
Mail-Followup-To: Stephen McKay <mckay@thehub.com.au>, dmaddox@sc.rr.com,
	current@FreeBSD.ORG
References: <20001216161756.A6370@cae88-102-101.sc.rr.com> <200012171658.eBHGwGW24109@dungeon.home> <20001217135431.C9721@cae88-102-101.sc.rr.com> <200012180641.eBI6fH607564@dungeon.home>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <200012180641.eBI6fH607564@dungeon.home>; from mckay@thehub.com.au on Mon, Dec 18, 2000 at 04:41:17PM +1000
Return-Receipt-To: dmaddox@sc.rr.com
Sender: dmaddox@cae88-102-101.sc.rr.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Well, if you do manage to uncover the lost magic, please let me
know :)

On Mon, Dec 18, 2000 at 04:41:17PM +1000, Stephen McKay wrote:
> 
> I expected some build tool expert to say "Just compile with these
> options".  But they haven't.  So I'll see if the bits have rotted,
> or whether we can keep building ld.so instead of just including
> an age old binary.
> 
> Stephen.


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


From owner-freebsd-current  Sun Dec 17 22:47:26 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 17 22:47:23 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1ABD937B400; Sun, 17 Dec 2000 22:47:23 -0800 (PST)
Received: from gorean.org (Studded@master [10.0.0.2])
	by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id WAA27290;
	Sun, 17 Dec 2000 22:45:39 -0800 (PST)
	(envelope-from DougB@gorean.org)
Sender: doug@dt051n37.san.rr.com
Message-ID: <3A3DB292.B297D5C2@gorean.org>
Date: Sun, 17 Dec 2000 22:45:38 -0800
From: Doug Barton <DougB@gorean.org>
Organization: Triborough Bridge & Tunnel Authority
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
Cc: John Baldwin <jhb@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: test/review: /dev/console logging patch
References: <25628.977121324@critter>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Poul-Henning Kamp wrote:
> 
> >>>
> >>> This patch is for the printf(9), log(9) & /dev/console stuff.
> >>> The result is that you can watch the output from /etc/rc in
> >>> your /var/log/messages.
> >>
> >> Dec 17 13:00:26 <console.info> Master /boot/kernel/kernel: Doing
> >> additional network setup:
> >> Dec 17 13:00:26 <console.info> Master /boot/kernel/kernel: ntpdate
> >> Dec 17 13:00:26 <console.info> Master /boot/kernel/kernel: ntpd
> >> Dec 17 13:00:27 <console.info> Master /boot/kernel/kernel: portmap
> >> Dec 17 13:00:27 <console.info> Master /boot/kernel/kernel: .
> >
> >The '.'s are simple and not too cluttery.  Fixing the console to line buffer
> >what it sends to log(9) is a better fix, IMO.
> 
> I specifically decided not to do this because I want to be able to
> see stuff like:
> 
>         echo -n "Press return to avoid disaster: " > /dev/console
>         read < /dev/console
> 
> Of course one could add timeouts and what's not, but then imagine
> the case of two programs writing on /dev/console at the same time...

	*nod* I wasn't sure that the buffering was the best suggestion, which
is why I preferred making the messages from /etc/rc* more meaningful. :)

Doug
-- 
    "The most difficult thing in the world is to know how to do a thing
and
     to watch someone else do it wrong without comment."
                     -- Theodore H. White

	Do YOU Yahoo!?


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


From owner-freebsd-current  Sun Dec 17 22:49:30 2000
From owner-freebsd-current@FreeBSD.ORG  Sun Dec 17 22:49:27 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147])
	by hub.freebsd.org (Postfix) with ESMTP
	id ED2B137B400; Sun, 17 Dec 2000 22:49:26 -0800 (PST)
Received: from critter (localhost [127.0.0.1])
	by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eBI6nNf26102;
	Mon, 18 Dec 2000 07:49:23 +0100 (CET)
	(envelope-from phk@critter.freebsd.dk)
To: Doug Barton <DougB@gorean.org>
Cc: John Baldwin <jhb@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: test/review: /dev/console logging patch 
In-Reply-To: Your message of "Sun, 17 Dec 2000 22:45:38 PST."
             <3A3DB292.B297D5C2@gorean.org> 
Date: Mon, 18 Dec 2000 07:49:23 +0100
Message-ID: <26100.977122163@critter>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <3A3DB292.B297D5C2@gorean.org>, Doug Barton writes:

>> >The '.'s are simple and not too cluttery.  Fixing the console to line buffer
>> >what it sends to log(9) is a better fix, IMO.
>> 
>> I specifically decided not to do this because I want to be able to
>> see stuff like:
>> 
>>         echo -n "Press return to avoid disaster: " > /dev/console
>>         read < /dev/console
>> 
>> Of course one could add timeouts and what's not, but then imagine
>> the case of two programs writing on /dev/console at the same time...
>
>	*nod* I wasn't sure that the buffering was the best suggestion, which
>is why I preferred making the messages from /etc/rc* more meaningful. :)

Just for the record: There is no support for green "OK" messages in
my patch :-)

--
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.


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


From owner-freebsd-current  Mon Dec 18  1:50:18 2000
From owner-freebsd-current@FreeBSD.ORG  Mon Dec 18 01:50:06 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from bbnmg1.net.external.hp.com (bbnmg1.net.external.hp.com [192.6.76.73])
	by hub.freebsd.org (Postfix) with ESMTP id 15D8737B400
	for <current@freebsd.org>; Mon, 18 Dec 2000 01:50:05 -0800 (PST)
Received: from hpbbn.bbn.hp.com (hpbbn.bbn.hp.com [15.138.8.14])
	by bbnmg1.net.external.hp.com (Postfix) with ESMTP id CDDED333
	for <current@freebsd.org>; Mon, 18 Dec 2000 10:49:35 +0100 (MET)
Received: from tmbbobmc.bbn.hp.com (tmbbobmc.bbn.hp.com [15.136.123.54])
	by hpbbn.bbn.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit6.0.6) with ESMTP id KAA12906
	for <current@freebsd.org>; Mon, 18 Dec 2000 10:50:02 +0100 (MET)
Received: from hp.com (localhost [127.0.0.1])
	by tmbbobmc.bbn.hp.com (8.11.1/8.11.1) with ESMTP id eBI9nxG01859
	for <current@freebsd.org>; Mon, 18 Dec 2000 10:50:00 +0100 (CET)
	(envelope-from michael_class@hp.com)
Sender: michaelc@tmbbobmc.bbn.hp.com
Message-ID: <3A3DDDC7.6F2540B7@hp.com>
Date: Mon, 18 Dec 2000 10:49:59 +0100
From: Michael Class <michael_class@hp.com>
Organization: Hewlett-Packard GmbH
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: current@freebsd.org
Subject: Network performance-problem 
Content-Type: multipart/mixed;
 boundary="------------0E44BFA6BBAA0D2613828BB4"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

This is a multi-part message in MIME format.
--------------0E44BFA6BBAA0D2613828BB4
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello,

i am seeing a problem with 5.0-current (from 14.12.00) and a 3COM
3CCFE575CT Lancard (pc-cardbus) using the xl-driver. It goes as follows:

I am using the 3COM-card in a 10MB-switched network. Occasionally 
someone is doing big network installs via multicast IP-packets. This
is done with almost the full 10MB-Bandwidth. On all the other computers
I have, I do see a big network-performance degration during that times,
but they are still somewhat usable. This is true for HPUX 10.20 , 11.0
and NT 4.0 machines. My Laptop (HP OB4150) unfortunately is network-
wise totally blocked during these times. In addition I am getting 
messages like:

xl0: watchdog timeout
xl0: watchdog timeout
xl0: no carrier - transceiver cable problem?
xl0: watchdog timeout
xl0: watchdog timeout
xl0: no carrier - transceiver cable problem?

Why behaves my FreeBSD-machines worse then the other boxes? Any Ideas?

TIA

Michael


Attached are the Kernel-Config-file and the dmesg output.
-- 
___________________________________________________________________________
Michael Class                            E-Mail: michael_class@hp.com
E-Business Solution Division             Phone:  +49 7031 14-3707
                                         Fax:    +49 7031 14-4505
___________________________________________________________________________
Hewlett-Packard GmbH, PO Box 1430, Mailstop ESD2, 71004 Boeblingen
Managing Directors: Rainer Geissel (Chairman),Rainer Erlat, Heribert
                    Schmitz, Hans-Jochen Lueckefett, Fritz Schuller
Chairman of the Supervisory Board: Joerg Menno Harms
Commercial register: Amtsgericht Boeblingen HRB 4081
___________________________________________________________________________
--------------0E44BFA6BBAA0D2613828BB4
Content-Type: text/plain; charset=us-ascii;
 name="dmesg.out"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="dmesg.out"

Copyright (c) 1992-2000 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
	The Regents of the University of California. All rights reserved.
FreeBSD 5.0-CURRENT #2: Thu Dec 14 11:13:18 CET 2000
    michaelc@tmbbobmc.bbn.hp.com:/usr/src/sys/compile/MCOBTEST
Timecounter "i8254"  frequency 1193182 Hz
CPU: Pentium II/Pentium II Xeon/Celeron (397.05-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x66a  Stepping = 10
  Features=0x183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR>
real memory  = 201326592 (196608K bytes)
avail memory = 191971328 (187472K bytes)
Preloaded elf kernel "kernel" at 0xc03a5000.
Pentium Pro MTRR support enabled
md0: Malloc disk
Using $PIR table, 6 entries at 0xc00fdf60
apm0: <APM BIOS> on motherboard
apm0: found APM BIOS v1.2, connected at v1.2
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Intel 82443BX (440 BX) host to PCI bridge> at pcibus 0 on motherboard
pci0: <PCI bus> on pcib0
pcib1: <PCI-PCI bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
vga_pci0: <VGA-compatible display device> mem 0xfec00000-0xfecfffff,0xfe800000-0xfebfffff,0xfd000000-0xfdffffff irq 9 at device 0.0 on pci1
pci1: <multimedia, audio> at 0.1 (no driver attached)
pccbb0: <TI1220 PCI-CardBus Bridge> at device 4.0 on pci0
pccbb0: PCI Memory allocated: 18020000
pci_cfgintr_unique: hard-routed to irq 10
pci_cfgintr: 0:4 INTA routed to irq 10
cardbus0: <Cardbus bus (newcard)> on pccbb0
pccard0: <16-bit PCCard bus> on pccbb0
pccbb1: <TI1220 PCI-CardBus Bridge> at device 4.1 on pci0
pccbb1: PCI Memory allocated: 18021000
pci_cfgintr_unique: hard-routed to irq 10
pci_cfgintr: 0:4 INTB routed to irq 10
cardbus1: <Cardbus bus (newcard)> on pccbb1
pccard1: <16-bit PCCard bus> on pccbb1
isab0: <PCI-ISA bridge> at device 7.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel PIIX4 ATA33 controller> port 0xfcf0-0xfcff at device 7.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
uhci0: <Intel 82371AB/EB (PIIX4) USB controller> irq 10 at device 7.2 on pci0
uhci0: Could not map ports
device_probe_and_attach: uhci0 attach returned 6
pci0: <bridge, PCI-unknown> at 7.3 (no driver attached)
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
sc0: <System console> on isa0
sc0: VGA <16 virtual consoles, flags=0x200>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1: configured irq 3 not in bitmap of probed irqs 0
pmtimer0 on isa0
unknown: <PNP0303> can't assign resources
unknown: <PNP0501> can't assign resources
pcm0: <Neomagic 256AV (non-ac97)> at port 0x220-0x22f,0x530-0x537,0x388-0x38f,0x120-0x121 irq 5 drq 0,1 on isa0
unknown: <PNP0f13> can't assign resources
unknown: <PNP0700> can't assign resources
IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, unlimited logging
ata1-slave: ata_command: timeout waiting for intr
ata1-slave: identify failed
ad0: 9590MB <IBM-DCXA-210000> [19485/16/63] at ata0-master UDMA33
acd0: DVD-ROM <TOSHIBA DVD-ROM SD-C2202> at ata1-master using PIO4
Mounting root from ufs:/dev/ad0s1a
pccbb0: card inserted: event=0x00000000, state=30000820
pccbb0: pccbb_power: CARD_VCC_0V and CARD_VPP_0V [44]
pccbb0: pccbb_power: CARD_VCC_3V and CARD_VPP_VCC [11]
TUPLE: LINKTARGET [3]: 43 49 53
Manufacturer ID: 01015752
TUPLE: CONFIG_CB [6]: 03 01 00 00 00 00
TUPLE: CFTABLE_ENTRY_CB [13]: 41 9a 01 b5 1e 01 b5 1e 02 30 ff ff 01
cardbus0: Opening BAR: type=IO, bar=10, len=0040
Product version: 5.0
Product name: 3Com Corporation | 3CCFE575CT | LAN Cardbus Card | 004 | 
Functions: Network Adaptor, Memory
xl0: <3Com 3c575C Fast Etherlink XL> port 0x3000-0x307f mem 0x18040000-0x1805ffff,0x18022080-0x180220ff,0x18022000-0x1802207f irq 10 at device 0.0 on cardbus0
xl0: Ethernet address: 00:00:86:5b:96:ea
miibus0: <MII bus> on xl0
ukphy0: <Generic IEEE 802.3u media interface> on miibus0
ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pccbb1: removal of nonexistant card!
/dev/vmmon: Module vmmon: registered with major=200 minor=0 tag=$Name: build-570 $
/dev/vmmon: Module vmmon: initialized
xl0: watchdog timeout
xl0: watchdog timeout
xl0: no carrier - transceiver cable problem?
xl0: watchdog timeout
xl0: watchdog timeout
xl0: no carrier - transceiver cable problem?

--------------0E44BFA6BBAA0D2613828BB4
Content-Type: text/plain; charset=us-ascii;
 name="MCOBTEST"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="MCOBTEST"

#
# MCOB4150 -- Generic kernel configuration file for FreeBSD/i386
#
# For more information on this file, please read the handbook section on
# Kernel Configuration Files:
#
#    http://www.FreeBSD.org/handbook/kernelconfig-config.html
#
# The handbook is also available locally in /usr/share/doc/handbook
# if you've installed the doc distribution, otherwise always see the
# FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the
# latest information.
#
# An exhaustive list of options and more detailed explanations of the
# device lines is also present in the ./LINT configuration file. If you are
# in doubt as to the purpose or necessity of a line, check first in LINT.
#
# $FreeBSD: src/sys/i386/conf/GENERIC,v 1.262 2000/06/25 09:18:07 markm Exp $

machine		i386
#cpu		I386_CPU
#cpu		I486_CPU
#cpu		I586_CPU
cpu		I686_CPU
ident		MCOBTEST
maxusers	64

hints		"MCOB4150.hints"	#Default places to look for devices.

makeoptions	DEBUG=-g		#Build kernel with gdb(1) debug symbols

#options 	MATH_EMULATE		#Support for x87 emulation
options 	INET			#InterNETworking
#options 	INET6			#IPv6 communications protocols
options 	FFS			#Berkeley Fast Filesystem
options 	FFS_ROOT		#FFS usable as root device [keep this!]
options 	SOFTUPDATES		#Enable FFS soft updates support
options 	MFS			#Memory Filesystem
options 	MD_ROOT			#MD is a potential root device
options 	NFS			#Network Filesystem
options 	NFS_ROOT		#NFS usable as root device, NFS required
options 	MSDOSFS			#MSDOS Filesystem
options 	CD9660			#ISO 9660 Filesystem
options 	CD9660_ROOT		#CD-ROM usable as root, CD9660 required
options 	PROCFS			#Process filesystem
options 	COMPAT_43		#Compatible with BSD 4.3 [KEEP THIS!]
#options 	SCSI_DELAY=15000	#Delay (in ms) before probing SCSI
options 	UCONSOLE		#Allow users to grab the console
#options 	USERCONFIG		#boot -c editor
#options 	VISUAL_USERCONFIG	#visual boot -c editor
options 	KTRACE			#ktrace(1) support
options 	SYSVSHM			#SYSV-style shared memory
options 	SYSVMSG			#SYSV-style message queues
options 	SYSVSEM			#SYSV-style semaphores
options 	P1003_1B		#Posix P1003_1B real-time extensions
options 	_KPOSIX_PRIORITY_SCHEDULING
options 	KBD_INSTALL_CDEV	# install a CDEV entry in /dev
#options 	DEVFS

# To make an SMP kernel, the next two are needed
#options 	SMP			# Symmetric MultiProcessor Kernel
#options 	APIC_IO			# Symmetric (APIC) I/O
# Optionally these may need tweaked, (defaults shown):
#options 	NCPU=2			# number of CPUs
#options 	NBUS=8			# number of busses
#options 	NAPIC=1			# number of IO APICs
#options 	NINTR=24		# number of INTs

device		isa
#device		eisa
device		pci
device 		pccard
#options 	COMPAT_OLDISA		# compatability shims for lnc, fe, le
#options 	COMPAT_OLDPCI		# compatability shims for lnc, vx

# Floppy drives
device		fdc

# ATA and ATAPI devices
device		ata
device		atadisk			# ATA disk drives
device		atapicd			# ATAPI CDROM drives
#device		atapifd			# ATAPI floppy drives
#device		atapist			# ATAPI tape drives
options 	ATA_STATIC_ID		#Static device numbering
#options 	ATA_ENABLE_ATAPI_DMA	#Enable DMA on ATAPI devices

# SCSI Controllers
#device		ahb		# EISA AHA1742 family
#device		ahc		# AHA2940 and onboard AIC7xxx devices
#device		amd		# AMD 53C974 (Teckram DC-390(T))
#device		dpt		# DPT Smartcache - See LINT for options!
#device		isp		# Qlogic family
#device		ncr		# NCR/Symbios Logic
#device		sym		# NCR/Symbios Logic (newer chipsets)

#device		adv
#device		adw
#device		bt
#device		aha	1
#device		aic

# SCSI peripherals
#device		scbus		# SCSI bus (required)
#device		da		# Direct Access (disks)
#device		sa		# Sequential Access (tape etc)
#device		cd		# CD
#device		pass		# Passthrough device (direct SCSI access)

# RAID controllers
#device		ida		# Compaq Smart RAID
#device		amr		# AMI MegaRAID
#device		mlx		# Mylex DAC960 family

# atkbdc0 controls both the keyboard and the PS/2 mouse
device		atkbdc	1
device		atkbd
device		psm

device		vga

# splash screen/screen saver
device		splash

# syscons is the default console driver, resembling an SCO console
device		sc	1

# Enable this for the pcvt (VT220 compatible) console driver
#device		vt
#options 	XSERVER			# support for X server on a vt console
#options 	FAT_CURSOR		# start with block cursor
# If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines
#options 	PCVT_SCANSET=2		# IBM keyboards are non-std

# Floating point support - do not disable.
device		npx

# Power management support (see LINT for more options)
device		apm
device		pmtimer

# PCCARD (PCMCIA) support
#device		card
#device		pcic
device  	cardbus
device 		pccbb

# Serial (COM) ports
device		sio

# Parallel port
device		ppc
device		ppbus		# Parallel port bus (required)
device		lpt		# Printer
#device		plip		# TCP/IP over parallel
#device		ppi		# Parallel port interface device
#device		vpo		# Requires scbus and da


# PCI Ethernet NICs.
#device		de		# DEC/Intel DC21x4x (``Tulip'')
#device		fxp		# Intel EtherExpress PRO/100B (82557, 82558)
#device		tx		# SMC 9432TX (83c170 ``EPIC'')
#device		vx		# 3Com 3c590, 3c595 (``Vortex'')
#device		wx		# Intel Gigabit Ethernet Card (``Wiseman'')

# PCI Ethernet NICs that use the common MII bus controller code.
device		miibus		# MII bus support
#device		dc		# DEC/Intel 21143 and various workalikes
#device		rl		# RealTek 8129/8139
#device		sf		# Adaptec AIC-6915 (``Starfire'')
#device		sis		# Silicon Integrated Systems SiS 900/SiS 7016
#device		ste		# Sundance ST201 (D-Link DFE-550TX)
#device		tl		# Texas Instruments ThunderLAN
#device		vr		# VIA Rhine, Rhine II
#device		wb		# Winbond W89C840F
device		xl		# 3Com 3c90x (``Boomerang'', ``Cyclone'')

# ISA Ethernet NICs.
#device		ed
#device		ex
#device		ep
#device		cs
#device		sn
# WaveLAN/IEEE 802.11 wireless NICs. Note: the WaveLAN/IEEE really
# exists only as a PCMCIA device, so there is no ISA attatement needed
# and resources will always be dynamically assigned by the pccard code.
#device		wi
# Aironet 4500/4800 802.11 wireless NICs. Note: the declaration below will
# work for PCMCIA and PCI cards, as well as ISA cards set to ISA PnP
# mode (the factory default). If you set the switches on your ISA
# card for a manually chosen I/O address and IRQ, you must specify
# those paremeters here.
#device		an
# BayStack 660 and others
#device		awi
# Xircom pccard ethernet
#device		xe
# The probe order of these is presently determined by i386/isa/isa_compat.c.
#device		ie
#device		fe
#device		le
#device		lnc

# Pseudo devices - the number indicates how many units to allocated.
device		loop		# Network loopback
device		ether		# Ethernet support
#device		sl		# Kernel SLIP
#device		ppp	1	# Kernel PPP
device		tun		# Packet tunnel.
device		pty		# Pseudo-ttys (telnet etc)
device		md		# Memory "disks"
device 		random
#device		gif	4	# IPv6 and IPv4 tunneling
#device		faith	1	# IPv6-to-IPv4 relaying (translation)

# The `bpf' device enables the Berkeley Packet Filter.
# Be aware of the administrative consequences of enabling this!
device		bpf		# Berkeley packet filter

# USB support
device		uhci		# UHCI PCI->USB interface
device		ohci		# OHCI PCI->USB interface
device		usb		# USB Bus (required)
#device		udbp		# USB Double Bulk Pipe devices
device		ugen		# Generic
device		uhid		# "Human Interface Devices"
device		ukbd		# Keyboard
device		ulpt		# Printer
#device		umass		# Disks/Mass storage - Requires scbus and da
device		ums		# Mouse
device		urio		# Diamond Rio 500 MP3 player
# USB Ethernet, requires mii
device		aue		# ADMtek USB ethernet
device		cue		# CATC USB ethernet
device		kue		# Kawasaki LSI USB ethernet


# local configurations:

#options         IPSEC                   #IP security
#options         IPSEC_ESP               #IP security (crypto; define w/ IPSEC)
#options         IPSEC_DEBUG             #debug for IP security
options		MSGBUF_SIZE=65536
options 	USER_LDT                #allow user-level control of i386 ldt
#options 	COMPAT_LINUX
options 	IPFIREWALL              #firewall
options 	IPFIREWALL_VERBOSE      #print information about
                                        # dropped packets
options 	IPFIREWALL_FORWARD      #enable xparent proxy support
#options	IPFIREWALL_VERBOSE_LIMIT=100 #limit verbosity
options 	IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default
options 	IPDIVERT                #divert sockets
#options 	DUMMYNET
#options 	BRIDGE
options 	DDB
options         DDB_UNATTENDED  


#SOUND:
device 		pcm
device 		vn  		#Vnode driver (turns a file into a device)

# for oracle:
options         SHMMAXPGS=10000
options         SHMMNI=100
options         SHMSEG=10
options         SEMMNS=200
options         SEMMNI=70
options         SEMMSL=61


#device       smbus
#device       iicbus
#device       iicbb
#device       intpm
#device       smb


--------------0E44BFA6BBAA0D2613828BB4--



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


From owner-freebsd-current  Mon Dec 18  6:58:35 2000
From owner-freebsd-current@FreeBSD.ORG  Mon Dec 18 06:58:33 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.189])
	by hub.freebsd.org (Postfix) with SMTP id C2BA237B400
	for <current@FreeBSD.org>; Mon, 18 Dec 2000 06:58:30 -0800 (PST)
Received: (qmail 5454 invoked by uid 1000); 18 Dec 2000 14:57:33 -0000
Date: Mon, 18 Dec 2000 16:57:32 +0200
From: Peter Pentchev <roam@orbitel.bg>
To: Mike Smith <msmith@FreeBSD.org>
Cc: current@FreeBSD.org
Subject: dev/acpica/acpi.c - minor patch for cleaner poweroff
Message-ID: <20001218165732.A5418@ringworld.oblivion.bg>
Mail-Followup-To: Peter Pentchev <roam@orbitel.bg>,
	Mike Smith <msmith@FreeBSD.org>, current@FreeBSD.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

I think you're the main maintainer of the ACPICA codebase (and yes, I know
that parts of it is imported from Intel).  Attached is a trivial patch which
makes for cleaner testing for RB_POWEROFF in acpi_shutdown_final() - I've had
various kernel/userland routines invoke reboot sequences where the howto had
more bits set than RB_POWEROFF, e.g. RB_NOSYNC.  With this patch, shutdown -p
works for me :)

Thanks for all the work on ACPICA :)

G'luck,
Peter

PS. Please CC: me in replies as I'm not on -current.

-- 
If I had finished this sentence,

Index: acpi.c
===================================================================
RCS file: /home/ncvs/src/sys/dev/acpica/acpi.c,v
retrieving revision 1.7
diff -u -r1.7 acpi.c
--- acpi.c	2000/12/12 14:20:27	1.7
+++ acpi.c	2000/12/18 14:55:43
@@ -657,7 +657,7 @@
 {
     ACPI_STATUS	status;
 
-    if (howto == RB_POWEROFF) {
+    if (howto & RB_POWEROFF) {
 	printf("Power system off using ACPI...\n");
 	if ((status = AcpiSetSystemSleepState(ACPI_STATE_S5)) != AE_OK) {
 	    printf("ACPI power-off failed - %s\n", acpi_strerror(status));


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


From owner-freebsd-current  Mon Dec 18  7: 0: 5 2000
From owner-freebsd-current@FreeBSD.ORG  Mon Dec 18 07:00:02 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from ns5.pacific.net.au (ns5.pacific.net.au [203.143.252.30])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1546937B400; Mon, 18 Dec 2000 06:59:58 -0800 (PST)
Received: from dungeon.home (ppp2.dyn249.pacific.net.au [203.143.249.2])
	by ns5.pacific.net.au (8.9.0/8.9.1) with ESMTP id BAA07219;
	Tue, 19 Dec 2000 01:59:54 +1100 (EST)
Received: from dungeon.home (localhost [127.0.0.1])
	by dungeon.home (8.11.1/8.9.3) with ESMTP id eBIF0S612182;
	Tue, 19 Dec 2000 01:00:28 +1000 (EST)
	(envelope-from mckay)
Message-Id: <200012181500.eBIF0S612182@dungeon.home>
To: dmaddox@sc.rr.com
Cc: current@freebsd.org, mckay@thehub.com.au, jkh@freebsd.org
Subject: Re: Is compatibility for old aout binaries broken? 
References: <20001216161756.A6370@cae88-102-101.sc.rr.com> <200012171658.eBHGwGW24109@dungeon.home> <20001217135431.C9721@cae88-102-101.sc.rr.com> <200012180641.eBI6fH607564@dungeon.home> <20001218014656.A17483@cae88-102-101.sc.rr.com>
In-Reply-To: <20001218014656.A17483@cae88-102-101.sc.rr.com>
    from "Donald J . Maddox" at "Mon, 18 Dec 2000 01:46:56 -0500"
Date: Tue, 19 Dec 2000 01:00:28 +1000
From: Stephen McKay <mckay@thehub.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Monday, 18th December 2000, "Donald J . Maddox" wrote:

>On Mon, Dec 18, 2000 at 04:41:17PM +1000, Stephen McKay wrote:
>> 
>> I expected some build tool expert to say "Just compile with these
>> options".  But they haven't.  So I'll see if the bits have rotted,
>> or whether we can keep building ld.so instead of just including
>> an age old binary.

>Well, if you do manage to uncover the lost magic, please let me know :)

It's getting a little more magic every day to generate a.out stuff,
but not all that bad.  Basically I built lib/csu/i386, gnu/lib/libgcc,
lib/libc and libexec/rtld-aout, in order, with these settings:

    NOMAN=yup DESTDIR="" OBJFORMAT=aout MAKEOBJDIRPREFIX=/usr/obj/aout

In each directory, I used make obj, make, make install.  (By the way,
there are a lot of twisty little passages in /usr/share/mk.  One of
them required me to add DESTDIR="", which should be a NOP.)

The generated ld.so has bloated a bit :-) but works fine.  So we could
in principle build ld.so for every release.  It's just a question of
whether we should.  I think we should.  But it might be just as easy
to copy it off the 3.3 CD every time.  It's dead end stuff after all.

Does the release engineer have an opinion?

Stephen.


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


From owner-freebsd-current  Mon Dec 18  8:23:41 2000
From owner-freebsd-current@FreeBSD.ORG  Mon Dec 18 08:23:38 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from ns5.pacific.net.au (ns5.pacific.net.au [203.143.252.30])
	by hub.freebsd.org (Postfix) with ESMTP
	id 156DA37B400; Mon, 18 Dec 2000 08:23:36 -0800 (PST)
Received: from dungeon.home (ppp6.dyn249.pacific.net.au [203.143.249.6])
	by ns5.pacific.net.au (8.9.0/8.9.1) with ESMTP id DAA10758;
	Tue, 19 Dec 2000 03:23:31 +1100 (EST)
Received: from dungeon.home (localhost [127.0.0.1])
	by dungeon.home (8.11.1/8.9.3) with ESMTP id eBIGN4613389;
	Tue, 19 Dec 2000 02:23:04 +1000 (EST)
	(envelope-from mckay)
Message-Id: <200012181623.eBIGN4613389@dungeon.home>
To: dmaddox@sc.rr.com
Cc: current@freebsd.org, jkh@freebsd.org, mckay@thehub.com.au
Subject: Re: Is compatibility for old aout binaries broken? 
References: <20001216161756.A6370@cae88-102-101.sc.rr.com> <200012171658.eBHGwGW24109@dungeon.home> <20001217135431.C9721@cae88-102-101.sc.rr.com> <200012180641.eBI6fH607564@dungeon.home> <20001218014656.A17483@cae88-102-101.sc.rr.com> <200012181500.eBIF0S612182@dungeon.home>
In-Reply-To: <200012181500.eBIF0S612182@dungeon.home>
    from Stephen McKay at "Tue, 19 Dec 2000 01:00:28 +1000"
Date: Tue, 19 Dec 2000 02:23:04 +1000
From: Stephen McKay <mckay@thehub.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tuesday, 19th December 2000, Stephen McKay wrote:

>But it might be just as easy to copy it off the 3.3 CD every time.

Oops!  As I wrote earlier, 3.3 and onward have the broken ld.so.  Good
copies are found on 3.0 though to 3.2.

Sorry for veering off the road there. :-)

Stephen.


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


From owner-freebsd-current  Mon Dec 18  8:33:44 2000
From owner-freebsd-current@FreeBSD.ORG  Mon Dec 18 08:33:30 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from fms317.biglobe.ne.jp (rcpt-expgw.biglobe.ne.jp [210.147.6.231])
	by hub.freebsd.org (Postfix) with ESMTP
	id 215B337B400; Mon, 18 Dec 2000 08:33:30 -0800 (PST)
Received: from smtp-gw.biglobe.ne.jp
	by rcpt-expgw.biglobe.ne.jp (8.9.3+3.2W/3.7W-00120811) with ESMTP id BAA29050;
	Tue, 19 Dec 2000 01:33:28 +0900 (JST)
X-Biglobe-Sender: <mogemoge@msi.biglobe.ne.jp>
Received: from u1l9y1 (202.247.110.109 [202.247.110.109]) by smtp-gw.biglobe.ne.jp
	id BBVMCAE158D0; Tue, 19 Dec 2000 01:33:20 +0900 (JST)
From: "masaya" <mogemoge@msi.biglobe.ne.jp>
To: <mogemoge@msi.biglobe.ne.jp>
Subject: =?iso-2022-jp?B?GyRCPi8kNyROJCo2YiRHQmc2YiQsPGokS0Z+JGshKiEqGyhC?=
Date: Tue, 19 Dec 2000 01:40:21 +0900
Message-ID: <MABBJOGPIJGEFDEDJEACIEFHDKAA.mogemoge@msi.biglobe.ne.jp>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

$BFMA3$N%a!<%k$9$_$^$;$s(B
$B:G=i$G:G8e$G$9!#=EJ#$7$?J}$O!"K\Ev$K?=$7Lu$4$6$$$^$;$s!#(B
$B$"$kF|;d$N=j$K0J2<$h$&$J!V(B4000$B1_$GBg6b$,<j$KF~$k!W(B
$B$H$$$&%a!<%k$,Mh$^$7$?!#(B
$B$h!<$/FI$s$G$=$N$7$/$_$K46?4!"G<F@$7$?$N$G;22C$9$k$3$H$K$7$^$7$?!#(B
$B6=L#$N$"$kJ}$O;22C$7$^$;$s$+!)FI$s$G$_$k2ACM$O$"$j$^$9!*!*(B
$B$^$5$K!"3$O7$GBd$rD`$k$G$9$h!#!J>P!K(B
$B$3$l$O!"F~$i$J$-$cB;$G$9$h!#Ii$1$F$P$C$+$j$N%Q%A%s%3$d%.%c%s%V%k(B
$B$r!"$d$k$h$j$O$?$C$?0l2s$N?69~$_$@$1$G!"$"$J$?$N?M@8>P$$$C$Q$J$7(B
$BFI$s$G$_$k2ACM$O$"$k$H;W$$$^$9$h!#(B

$B$4LBOG$G$7$?$i>C$7$F$/$@$5$$(B

----------$B!c;22C<T$N@<#1!d(B-------------------------------

$BK\Ev$K$*6b$,M_$7$+$C$?$i!"@dBP$K%*%9%9%a$G$9!*(B
$B;d$NM'?M$b#3=54V$G#5#0K|6a$/2T$$$G$$$^$7$?$+$i!*!*(B
$B#4#0#0#01_$,K\Ev$KBg6b$K$J$C$?!*!J=;=jL$8x3+!K(B

----------$B!c;22C<T$N@<#2!d(B-------------------------------
$B$3$l$O!"%^%8$G$9$4$$$G$9!#26$b$O$8$a$O!"$3$&$$$&$N$O?.$8$F$J$+$C$?(B
$B$@$1$I!"6b$bM_$7$+$C$?$7!"#4#0#0#01_$J$s$F!"$=$s$JBg6b$8$c$J$$$+$i(B
$B$@$^$5$l$F$b!"Ju$/$8Gc$C$?$H;W$C$F$d$C$F$_$?$i@h7n#47n$O9g7W#1#2#6K|(B
$B?6$j9~$^$l$^$7$?(B($B!0(B-$B!0(B)
$B$3$N%a!<%kAw$C$F!"JV?.$7$F$/$k?M$K$"$J$?$bHo32<T$G$9!#(B
$B$3$l0J>eHo32<T$r(B
$BA}$d$5$J$$$G2<$5$$$C$F8@$o$l$k$s$@$1$I!"26<+?HHo32$O<u$1$F$J$$$7!"(B
$B26$@$1$*$$$7$$;W$$$7$F$k$H$O;W$o$J$$$s$@$h$M!#(B
$B26$,;22C$7$F#1#2#6K|$-$?$s$@$+$iA0$N?M$d$b$&(B
$B8}:B$,>C$($F$7$^$C$??M$K$bF1$8$0$i$$$N6b$,Mh$F$k$s$@$m$&$H;W$&$s$@$h(B

$B8e$m$N?M$,Ho32<u$1$k$N$+$J!)$H$b9M$($?$s$@$1$I(B
$B26$b$O$8$a$O!"0lHV8e$m$@$C$?!*!*!*(B
$B7k6I:G8e$O!"8}:B$,>C$($F$^$?EPO?$9$k;~$O0lHV8e$K$J$k!#(B
$B9T$-$D$1$PA0$b8e$m$b$J$$$s$@$h$M!#(B
$B$G26$O!"#47n$N;q6b$G$^$?%A%c%l%s%8!*(B
$B$?$^$C$?6b$G?7<V$G$bGc$*$&$H$*$b$C$F$^$9!#(B
$B%"%d%7%$$@$m$&$1$I2<$NFI$s$G9M$($F$_$F$h(B(^o^)/$B$R$m$7(B

----------$B!c%2!<%`$N>R2p!d(B-------------------------------

$B9gK!E*$GLY$+$k%^%M!<%2!<%`EP>l(B
$B4JC1$G$9!#>/$J$$;qK\6b$GBg6b$,<j$KF~$j$^$9!#(B
$B0lEY!"L\$rDL$7$F$_$F$/$@$5$$!#FI$^$J$$$HB;$G$9$h!#(B

$B!v$H$K$+$/LY$+$k!"4JC1$G3N<B$J%^%M!<%2!<%`!v(B
$B@dBP3N<B!">/;qK\$GG|Bg$JMx1W$G$9!#!*!*(B
$B#4#0#0#01_$N;qK\$G@($$Bg6b$,<j$KF~$j$^$9!#(B
$BHf3SE*MF0W$K;q6b$,F~$C$F$/$k!"$H$$$&%a!<%k$,$"$kF|FO$-$^$7$?!#(B
$BFbMF$rFI$s$G$_$k$H!"#4?M$N%j%9%H$K#1#0#0#01_$:$D$rAw$k$@$1$G(B
$BEj;q3[0J>e$NBg6b!J#1#0#0K|1_0J>e!K$r<j$K$9$k$3$H$,=PMh$k$H$$$&(B
$BJ*$G$7$?!#(B
$B!X$=$s$J4E$$OC$,$"$k$+$$$J!Y$=$l$,:G=i$N46A[$G$7$?!#(B
$BEvA3$G$7$g$&!#$G$b!"$h!<$/FI$s$G$_$k$HG<F@$G$-$kFbMF$@$C$?$7!"(B
$B$O$:$l$F$P$+$j$$$kJu$/$8$KHf$Y$?$i3NN($Ot#$K9b$$$+$b!"$H;W$((B
$B$?$N$G;n$7$K;22C$7$F$_$k;v$K$7$^$7$?!#(B
$B$=$7$FH>?.H>5?$GBT$C$F$$$k$H!"MbF|$K#17o$N?69~$,M-$j$^$7$?!#(B
$B<!$NF|$K$O#37o$N?69~!"$=$7$F#27o!"?t7o$N?69~$,#1=54V$/$i$$B3$-(B
$B$^$7$?!##2=54V$r2a$.$?:"$+$i(B50$B7o0J>e$N?69~$,!"KhF|!"B+$K$J$C$F(B
$BMh$kMM$K$J$j$^$7$?!#(B

$BGO</GO</$7$$$H;W$o$J$$$G2<$5$$!#(B
$B?t%v7n8e$K$O!">/$J$/$H$b5.J}$NG/<}$h$j$bB?$/$J$k$O$:!D!#(B
$B$3$l$G?M@8JQ$o$k$+$b!*M7$S?4$r$*;}$A$NJ}$@$1@'Hs;22C$7$F2<$5$$(B

$BK!N'E*$K$OA4$/LdBj$"$j$^$;$s!J8e=R$7$^$9$,?7J9;fLL$G$b<h$j>e$2$i$l$F$^$9!#(B


-------------------------------------------------------------

$B"#;22CJ}K!!J$3$N%2!<%`$N$7$/$_>R2p4^$`!K"#(B

$B#1!"$^$:!"2<5-#4?M$N8}:B$K$*6b$r?6$j9~$s$G$/$@$5$$!#(B
$B!J6d9T$N<+F0?69~5!$G?6$j9~$_$^$9!##4?M$N8}:B$NItJ,$r(B
$B0u:~$7$F$$$/$H3Z$G$9!#!K(B

$B#2!"<!$K!"$3$N%a!<%k$r$=$N$^$^;H$C$F!JJT=8$O<+M3$G$9$,!K%j%9%H(B
$B$K$"$k#4$D$N8}:B$N0lHV>e$N?M$r:o=|$7$^$9!#!J0lHV>e$N8}:B$r:o=|$9$k$+$i!"(B
$BK!N'$K?($l$J$$$G:Q$`$N$G$9!#$=$l$@$1$O@dBP$K<i$C$F$/$@$5$$!#!K(B
$B$=$7$F!"(B
$B%j%9%H$N0lHV2<$K$"$J$?$N8}:B$r=q$-$^$9(B
$B$"$H$O!"HV9f$r>e$+$i=g$K?6$j$J$*$7$^$9!#(B
$B!J$3$&$7$F=gHV$K>e$N?M$,H4$1$F$$$/$N$G0cK!@-$O$J$$!"$H$$$&(B
$BJ[8n;N$NJ}$N@bL@$,$"$j$^$7$?!#!K(B

$B#3!"$=$l$r!"$G$-$k$@$1$?$/$5$s%$%s%?!<%M%C%H$N7G<(HD$N%"%I%l%9(B
$B$KAw$C$F$/$@$5$$!#$=$&$9$l$P!"$"$H$O$=$l$r<u$1<h$C$??M$,$I$s(B
$B$I$sF1$8$h$&$K?6$j$3$s$G$/$l$^$9!#:G>e0L$N?M$N8"Mx$,>C$($k$7(B
$B$/$_$J$N$G2<$N?M$d8e$+$i;22C$7$??M$,ITMx$H$$$&$o$1$G$O$J$/>r7o(B
$B$,A4$/F1$8$J$N$G$9!#:G=i$N#1=54V$G#1#07o0J>e$N?69~$,L5$$>l9g(B
$B$O$b$&%R%H%U%s%P%j$7$^$9!#(B

$B#4!"8e$O!"8=6b!o#1!$#0#0#01_$,?69~$^$l$k$N$rBT$D$@$1$G$9!#(B

$B"#%j%9%H"#(B

1  $B%+%H%&%f%-%3!!==O;6d9T!!BgA>:,;YE9(B
      $BIaDL#1#1#4#7#6#9#1(B

2$B!!%$%H%&%3%&%$%A%m%&!!D+F|?.MQ6b8K!!@>Hx5W;YE9(B
    $B!!IaDL#2#1#1#6#0#1(B

3$B!!%J%+%`%i%?%/%d!!KLMN6d9T!!;%KZ1XFn8};YE9(B
$B!!!!!!IaDL#3#5#2#5#5#1#7(B

4$B!!%+%o%@%^%5%d!!El3$6d9T!!<FED;YE9(B
$B!!!!!!IaDL#1#2#6#4#3#0#2(B


$B"($*6b$rAw$i$J$$$G%j%9%H$K<+J,$NL>A0$r:\$;$k$H!"(B
$B>e0L$N?M$N?69~$_3NG'$G$P$l$FAJ$($i$l$?$j!"(B
$B$$$m$$$m$J967b$r<u$1$F$7$^$$$^$9!#(B
$BNI?4$r;}$C$F;22C$9$k$3$H$G$_$J$5$s$,F1>r7o$G<}1W$r4|BT(B
$B$G$-$k$N$G$9$+$i!#;22C$7$F#2=54V$r2a$.$?:"$+$iJ?6Q$7$FA}2C$7(B
$B$F$/$k$H$$$&OC$G$9!#KhF|8}:B;D9b$r3NG'$9$k$N$,3Z$7$/$J$kL4$N(B
$B$h$&$J%2!=%`$K;22C$7$F!"@:?@E*$K4r$7$/$J$kF|!9$rAw$j$^$;$s$+(B
$B:#$9$0%3%T!=$7$F!"5.J}$b;22C$7$FL4$r<B8=$7$^$7$g$&!#(B

$B"(MQ?4?<$$J}$O$h$/D4$Y$F$_$F$/$@$5$$!#9gK!E*$G$"$k$H$$$&$3$H(B
$B$,$4M}2rD:$1$k$O$:$G$9!#(B
$B?7J9;fLL$GJ[8n;N$5$s$b9gK!$@$H$$$C$F$$$^$7$?!#(B
$B$3$N%A%c%s%9!"CN$C$F$F$d$i$J$$<j$O$"$j$^$;$s!*K\Ev$K$@$^$5$l(B
$B$?$H;W$C$F:#$9$09TF0$7$F$_$F$/$@$5$$!#(B
$B$9$4$$3[$K$J$C$FJV$C$F$-$^$9!#(B

$B"(;22CHqMQ$@$H;W$C$F#4#0#0#01_$/$i$$%Q!<%C$HAw$j$^$7$g$&!#(B
$B$@$$$?$$#4$+$i#5=54V$G#1#0#0K|$[$I$K$J$j$^$9!#(B
$B$=$7$F!"$*6b$,ES@Z$l$F$-$?(B
$B$+$J$H;W$C$?$i>e5-$N9TF0$r7+$jJV$;$P$$$$$N$G$9!#(B

$B"';29M"'(B
-------------$B$3$N%2!<%`$,!X0cK!!Y$H;W$o$l$F$$$kJ}$X!#(B----------

$B$3$N%2!<%`$O0cK!$G$O$"$j$^$;$s!#(B
$B;d$b0l1~;22C$9$k$KEv$C$F!"Hs9gK!$J%2!<%`$G$"$l$P(B
$BEvA3HH:a$G$"$k$H9M$(!"EE;R%a!<%k$r;H$C$FK?J[8n;N(B
$B$5$s$H!"$3$NFbMF$K$D$$$FAjCL$5$;$F$$$?$@$-$^$7$?!#(B
$B$=$NOC$7$N7k2L$r!"$3$A$i$K$^$H$a$^$9!#(B
$B!zL58BO":?9V!JDL>N!'$M$:$_9V!K$K$D$$$F!#(B
$B>rJ8$K$h$l$P!"(B
-------------------------------------------
$B$3$NK!N'$K$*$$$F!VL58BO":?9V!W$H$O!"6bIJ$r=P$($s(B
$B$9$k2CF~<T$,L58B$KA}2C$9$k$b$N$G$"$k$H$7$F!"@h$K(B
$B2CF~$7$?<T$,@h=g0L<T!"0J2<$3$l$KO":?$7$FCJ3,E*$K(B
$BFs0J>e$NG\N($r$b$D$FA}2C$9$k8eB3$N2CF~<T$,$=$l$>(B
$B$l$NCJ3,$K1~$8$?8e=g0L<T$H$J$j!"=g<!@h=g0L<T$,8e(B
$B=g0L<T$N=P$($s$9$k6bIJ$+$i<+8J$N=P$($s$7$?6bIJ$N(B
$B2A3[Kt$O?tNL$r>e2s$k2A3[Kt$O?tNL$N6bIJ$r<uNN$9$k(B
$B$3$H$rFbMF$H$9$k6bIJ$NG[EvAH?%$r$$$&!#!W(B
-------------------------------------------
$B$H$"$j$^$9!#MW$9$k$K!"8e=g0L<T$,F~$k$3$H$K$h$j@h(B
$B=g0L<T$,=g<!$=$N%7%9%F%`$N;22C8"Mx$,$J$/$J$k$H$$(B
$B$&%7%9%F%`$G$"$l$P!"$=$N;22C<T$,L58B$KA}2C$7$J$$(B
$B$N$G!"$3$N%7%9%F%`$@$H!XL58BO":?9V$NKI;_$K4X$9$k(B
$BK!N'!Y$K$O?($l$J$$$H$$$&;v$K$J$j$^$9!#(B
$B"(;d$,>R2p$7$F$$$k%7%9%F%`$O!"@h$K;22C$7$?J}!J=g0L<T!K(B
$B$,H4$1$k%7%9%F%`$J$N$GLdBj$O$J$$MM$G$9!#(B
-------------------------------------------

$B!|8f?4G[$JJ}$N$?$a$K!"4X785-;v$r5-$7$F$*$-$^$9!#(B

$B!cJ[8n;N$N0U8+!d(B
$B$3$l$O$h$/8@$o$l$k%M%:%_9V$d%^%k%A>&K!$G$O$"$j$^$;$s!#(B
$B0J2<$K=q$+$l$F$$$^$9$h$&$K2q0w$rAM;;<0$K3HBg$5$;$k$3$H$r>r7o$H(B
$B$9$kL58BO":?9V$dO":?HNGd<h0z$G$O$J$/!"=gHV$K>e$N?M$,H4$1$F$$$/(B
$B$N$G0cK!@-$O$"$j$^$;$s!#(B

$B$M$:$_!>$3$&!ZAM9V![!E%+%&(B
$B2q0w$rAM;;<0$K3HBg$5$;$k$3$H$r>r7o$H$7$F!"2CF~<T$KBP$7$F2CF~6b(B
$B3[0J>e$N6bA,$=$NB>$N7P:Q>e$NMx1W$rM?$($k0l<o$N6bM;AH?%!#Ej5!@-(B
$B$,6/$$$N$GK!N'$G6X;_!#O":?G[EvAH?%!#L58BO":?9V!#(B

$B%^%k%A!>$7$g$&$[$&!Z!=>&K!![!E%7%d%&%O%U(B
(multilevelmarketingplan)$B>&IJHNGdJ}K!$N0l!#(B
$BJ*IJHNGd6H<T$H$=$N>&IJ$r:FHNGd$9$k<T$,<!!9$KB>$N<T$r:FHNGdAH?%(B
$B$K2CLA$5$;$F!"AH?%Fb$G$NCO0L>:?J$+$iF@$i$l$kMx1W$r1B$K>&IJ$N9X(B
$BF~$d<h0zNA$N;YJ'$NIiC4$rLsB+$5$;$k7A$G$9$k>&IJ$NHNGd<h0z!#AM9V(B
$B<0HNGdK!$H$b8F$P$l!"Ej5!@-$,6/$/J@32$,Bg$-$$$N$GK!N'$G87$7$/(B
$B5,@)!#O":?HNGd<h0z!#!J9-<-1qBh;MHG$h$j0zMQ!K(B

-------------------------------------------
$B:G8e$^$GFI$s$GD:$-$"$j$,$H$&$4$6$$$^$7$?(B







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


From owner-freebsd-current  Mon Dec 18  8:47:50 2000
From owner-freebsd-current@FreeBSD.ORG  Mon Dec 18 08:47:49 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from air.linkclub.or.jp (air.linkclub.or.jp [210.155.117.20])
	by hub.freebsd.org (Postfix) with ESMTP id ED4A337B400
	for <current@FreeBSD.org>; Mon, 18 Dec 2000 08:47:47 -0800 (PST)
Received: from localhost.jp.FreeBSD.org (kumagaya2-193.ppp-1.dion.ne.jp [210.198.151.193])
	by air.linkclub.or.jp (8.9.3/3.7W) with ESMTP id BAA00372
	for <current@FreeBSD.org>; Tue, 19 Dec 2000 01:47:39 +0900 (JST)
Date: Tue, 19 Dec 2000 00:43:43 +0900 (JST)
Message-Id: <200012181543.AAA89316.toshi@jp.FreeBSD.org>
From: Toshihiko ARAI <toshi@jp.FreeBSD.org>
To: current@FreeBSD.ORG
Subject: HEADSUP: Linksys cards need flag.
X-Mailer: VM 5.96 (beta) / Mule 2.3 (SUETSUMUHANA) based on 19.34.1
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi folks, for mobile users.

Linksys Fast Ethernet PCCARD cards supported by the ed driver now
require the addition of flag 0x80000 to their config line in
pccard.conf(5).  This flag is not optional.  These Linksys cards will
not be recognized without it.

The old code tried to automatically probe for these cards.  However,
these probes sometimes caused non-Linksys cards to hang.
I wanted to avoid introducing a new flag if I could, but I had no
other solution.

The description in pccard.conf(5) should be as follows:

card "corega" "FEther PCC-TXF"
        config  auto "ed" ? 0x80000

I fixed all the entries for the Linksys type card that I could find in
etc/defaults/pccard.conf.

Please notify me if I have missed any.

--
Toshihiko ARAI / toshi@FreeBSD.org
http://www.jp.FreeBSD.org/PAO/LAPTOP_SURVEY/index.html


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


From owner-freebsd-current  Mon Dec 18  9:42:26 2000
From owner-freebsd-current@FreeBSD.ORG  Mon Dec 18 09:42:24 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222])
	by hub.freebsd.org (Postfix) with ESMTP id 6289837B400
	for <current@FreeBSD.ORG>; Mon, 18 Dec 2000 09:42:24 -0800 (PST)
Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137])
	by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eBIHgNE12260;
	Mon, 18 Dec 2000 09:42:23 -0800 (PST)
	(envelope-from jhb@foo.osd.bsdi.com)
Received: (from jhb@localhost)
	by foo.osd.bsdi.com (8.11.1/8.11.0) id eBIHfAY82453;
	Mon, 18 Dec 2000 09:41:10 -0800 (PST)
	(envelope-from jhb)
Message-ID: <XFMail.001218094110.jhb@FreeBSD.org>
X-Mailer: XFMail 1.4.0 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <25651.977121415@critter>
Date: Mon, 18 Dec 2000 09:41:10 -0800 (PST)
Organization: BSD, Inc.
From: John Baldwin <jhb@FreeBSD.ORG>
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
Subject: Re: test/review: /dev/console logging patch
Cc: current@FreeBSD.ORG
Sender: jhb@foo.osd.bsdi.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 18-Dec-00 Poul-Henning Kamp wrote:
> In message <XFMail.001217150456.jhb@FreeBSD.org>, John Baldwin writes:
>>
>>On 17-Dec-00 Poul-Henning Kamp wrote:
>>> 
>>> This patch is for the printf(9), log(9) & /dev/console stuff.
>>> The result is that you can watch the output from /etc/rc in
>>> your /var/log/messages.
>>> 
>>> Poul-Henning
>>> 
>>> 
>>> 1. Replace logwakeup() with msgbuftrigger++;  There is little
>>>    point in calling a function to set a flag.
>>
>>Abstraction to keep other code from having to know the iternals of the log(9)
>>device?  Maybe use a #define for logwakeup() that does the msgbuftrigger++ to
>>keep the abstraction w/o the overhead?
> 
> But it was actually the other way around now :-)  It was the log
> device which had obfuscated the log/printf code because it needed
> it's assistance to call selwakeup.
> 
> I want the log/printf code to be as simple as possible, and to have
> the smallest stack footprint possible...

Ok, works for me. :)

-- 

John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/


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


From owner-freebsd-current  Mon Dec 18 10: 1:37 2000
From owner-freebsd-current@FreeBSD.ORG  Mon Dec 18 10:01:35 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mail.jocose.org (mail.jocose.org [199.199.226.71])
	by hub.freebsd.org (Postfix) with SMTP id 29CC637B400
	for <current@freebsd.org>; Mon, 18 Dec 2000 10:01:35 -0800 (PST)
Received: (qmail 13079 invoked by uid 1013); 18 Dec 2000 18:01:19 -0000
Date: Mon, 18 Dec 2000 12:01:19 -0600
From: Peter Schultz <pete@jocose.org>
To: current@freebsd.org
Subject: debug build of libc_r
Message-ID: <20001218120119.A13062@jocose.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: pete@mail.jocose.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

I'm seeing a crash related to libc_r.
Could someone please instruct me as
to how to build a debug version.

Thanks,
Pete...



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


From owner-freebsd-current  Mon Dec 18 10: 3:44 2000
From owner-freebsd-current@FreeBSD.ORG  Mon Dec 18 10:03:41 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38])
	by hub.freebsd.org (Postfix) with ESMTP id 5AB1F37B402
	for <current@freebsd.org>; Mon, 18 Dec 2000 10:03:41 -0800 (PST)
Received: from dragon.nuxi.com (Ipittythefoolthattrustsident@trang.nuxi.com [209.152.133.57])
	by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id KAA02644;
	Mon, 18 Dec 2000 10:03:39 -0800 (PST)
	(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
	by dragon.nuxi.com (8.11.1/8.11.1) id eBII3GF67759;
	Mon, 18 Dec 2000 10:03:16 -0800 (PST)
	(envelope-from obrien)
Date: Mon, 18 Dec 2000 10:03:15 -0800
From: "David O'Brien" <obrien@freebsd.org>
To: Stephen McKay <mckay@thehub.com.au>
Cc: dmaddox@sc.rr.com, current@freebsd.org
Subject: Re: Is compatibility for old aout binaries broken?
Message-ID: <20001218100315.A67679@dragon.nuxi.com>
Reply-To: current@freebsd.org
References: <20001216161756.A6370@cae88-102-101.sc.rr.com> <200012171658.eBHGwGW24109@dungeon.home> <20001217135431.C9721@cae88-102-101.sc.rr.com> <200012180641.eBI6fH607564@dungeon.home> <20001218014656.A17483@cae88-102-101.sc.rr.com> <200012181500.eBIF0S612182@dungeon.home>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <200012181500.eBIF0S612182@dungeon.home>; from mckay@thehub.com.au on Tue, Dec 19, 2000 at 01:00:28AM +1000
X-Operating-System: FreeBSD 5.0-CURRENT
Organization: The NUXI BSD group
X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3  90 76 5D 69 58 D9 98 7A
X-Pgp-Rsa-Keyid: 1024/34F9F9D5
Sender: obrien@NUXI.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, Dec 19, 2000 at 01:00:28AM +1000, Stephen McKay wrote:
> So we could in principle build ld.so for every release.

I would say "no".  The building of a.out bits is getting harder as more
and more framework pieces are removed.  I don't quite fully understand
the problem yet.  Do you have a binary that shows the problem other than
SimCity from a 3.x release CDROM?  I don't have any 3.x CDROMs any more,
so I'd have to wait a while until I can find one at the office.

-- 
-- David  (obrien@FreeBSD.org)
          GNU is Not Unix / Linux Is Not UniX


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


From owner-freebsd-current  Mon Dec 18 10:12:37 2000
From owner-freebsd-current@FreeBSD.ORG  Mon Dec 18 10:12:35 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from cae88-102-101.sc.rr.com (cae88-102-101.sc.rr.com [24.88.102.101])
	by hub.freebsd.org (Postfix) with ESMTP id DC43D37B404
	for <current@freebsd.org>; Mon, 18 Dec 2000 10:12:34 -0800 (PST)
Received: (from dmaddox@localhost)
	by cae88-102-101.sc.rr.com (8.11.1/8.11.1) id eBIICcM63940
	for current@freebsd.org; Mon, 18 Dec 2000 13:12:38 -0500 (EST)
	(envelope-from dmaddox)
Date: Mon, 18 Dec 2000 13:12:38 -0500
From: "Donald J . Maddox" <dmaddox@sc.rr.com>
To: current@freebsd.org
Subject: Re: Is compatibility for old aout binaries broken?
Message-ID: <20001218131237.A56550@cae88-102-101.sc.rr.com>
Reply-To: dmaddox@sc.rr.com
Mail-Followup-To: current@freebsd.org
References: <20001216161756.A6370@cae88-102-101.sc.rr.com> <200012171658.eBHGwGW24109@dungeon.home> <20001217135431.C9721@cae88-102-101.sc.rr.com> <200012180641.eBI6fH607564@dungeon.home> <20001218014656.A17483@cae88-102-101.sc.rr.com> <200012181500.eBIF0S612182@dungeon.home> <20001218100315.A67679@dragon.nuxi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20001218100315.A67679@dragon.nuxi.com>; from obrien@freebsd.org on Mon, Dec 18, 2000 at 10:03:15AM -0800
Return-Receipt-To: dmaddox@sc.rr.com
Sender: dmaddox@cae88-102-101.sc.rr.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

You don't need a CDROM...  You can get it from:

ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current/commerce/games/SimCity/SimCity-3.6b.tgz

On Mon, Dec 18, 2000 at 10:03:15AM -0800, David O'Brien wrote:
> On Tue, Dec 19, 2000 at 01:00:28AM +1000, Stephen McKay wrote:
> > So we could in principle build ld.so for every release.
> 
> I would say "no".  The building of a.out bits is getting harder as more
> and more framework pieces are removed.  I don't quite fully understand
> the problem yet.  Do you have a binary that shows the problem other than
> SimCity from a 3.x release CDROM?  I don't have any 3.x CDROMs any more,
> so I'd have to wait a while until I can find one at the office.
> 
> -- 
> -- David  (obrien@FreeBSD.org)
>           GNU is Not Unix / Linux Is Not UniX


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


From owner-freebsd-current  Mon Dec 18 10:36:53 2000
From owner-freebsd-current@FreeBSD.ORG  Mon Dec 18 10:36:52 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from magnesium.net (toxic.magnesium.net [207.154.84.15])
	by hub.freebsd.org (Postfix) with SMTP id 4B5CE37B402
	for <current@freebsd.org>; Mon, 18 Dec 2000 10:36:52 -0800 (PST)
Received: (qmail 73935 invoked by uid 1142); 18 Dec 2000 18:36:49 -0000
Date: 18 Dec 2000 10:36:49 -0800
Date: Mon, 18 Dec 2000 10:36:42 -0800
From: Jason Evans <jasone@canonware.com>
To: Peter Schultz <pete@jocose.org>
Cc: current@freebsd.org
Subject: Re: debug build of libc_r
Message-ID: <20001218103642.C2312@canonware.com>
References: <20001218120119.A13062@jocose.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20001218120119.A13062@jocose.org>; from pete@jocose.org on Mon, Dec 18, 2000 at 12:01:19PM -0600
Sender: jasone@magnesium.net
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, Dec 18, 2000 at 12:01:19PM -0600, Peter Schultz wrote:
> Hi,
> 
> I'm seeing a crash related to libc_r.
> Could someone please instruct me as
> to how to build a debug version.

cd /usr/src/lib/libc_r
make clean
DEBUG_FLAGS=-g3 make
make install

Jason


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


From owner-freebsd-current  Mon Dec 18 11:40: 5 2000
From owner-freebsd-current@FreeBSD.ORG  Mon Dec 18 11:40:02 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from dirty.research.bell-labs.com (dirty.research.bell-labs.com [204.178.16.6])
	by hub.freebsd.org (Postfix) with SMTP id D416237B400
	for <freebsd-current@freeBSD.ORG>; Mon, 18 Dec 2000 11:40:01 -0800 (PST)
Received: from scummy.research.bell-labs.com ([135.104.2.10]) by dirty; Mon Dec 18 14:39:38 EST 2000
Received: from zydeco.research.bell-labs.com ([135.104.120.150]) by scummy; Mon Dec 18 14:39:37 EST 2000
Received: (from jkf@localhost)
	by zydeco.research.bell-labs.com (8.9.1/8.9.1) id OAA19012
	for freebsd-current@freeBSD.ORG; Mon, 18 Dec 2000 14:39:37 -0500 (EST)
Date: Mon, 18 Dec 2000 14:39:37 -0500 (EST)
From: Jeff Fellin <jkf@research.bell-labs.com>
Message-Id: <200012181939.OAA19012@zydeco.research.bell-labs.com>
To: freebsd-current@freeBSD.ORG
Subject: Kernel Buffer overwrite debugging
X-Sun-Charset: US-ASCII
Sender: jkf@zydeco.research.bell-labs.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


I am having a problem with a device driver that uses physio
to transfer data to a SCSI adapter. Some times the after 
passing the buffer to the CAM system, via xpt_action, the
buffer contents are modified. I've traced my driver and cannot
determine how this could be happening. I am running on a single
CPU Pentium II system with all system config defaults.

What I would like to do is to dynamically set a watch point
on the buffer used by the write system call for the duration
of sending the data to the SCSI adapter. I want to do this
dynamically instead of manually setting a breakpoint in the
code and manually setting the watch point, because the problem
occurs around the 90'th time, and I don't want SCSI bus timeouts
while typing the watch address.

I've examined the ddb code, and thought that if I emulated the
steps in db_trap() for the command of setting a watchpoint it
would work. However, it doesn't appear to be working.

What I've done is:

	/* possible on data xfer >= 512 bytes */
	if (condition for problem) {

		db_watchpoint_cmd(bp->bio_addr, bp->bio_addr,
			bp->bio_count, &"rw");
		db_continue_cmd(0, 0, 0, &"w"):
		db_restart_at_pc(FALSE);
	}

When the buffer is done transmitting I do the following:

	db_clear_watchpoints();
	db_deletewatch_cmd(bp->bio_addr, bp->cio_addr,
		bp->cio_count, &"rw");
	db_continue_cmd(0, 0, 0, &"w");
	db_restart_at_pc(FALSE);

My driver trace printf's show the data  at bp->bio_addr was
changed from 0x601000a3 to 0x0. Additional traces show the 
data from the first 200+ bytes is changed to zero.

Any guidance on how to use the ddb functions to debug this
problem are appreciated. Also, alternative methods to determine
what is overwriting the buffer. In looking at the data on a
SCSI bus analyzer, the entire buffer has been zero'ed out.

Thank you in advance for your help.

	Jeff Fellin
	MH 2A-352
	(908) 582-7673
	fellin@lucent.com



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


From owner-freebsd-current  Mon Dec 18 12:31:49 2000
From owner-freebsd-current@FreeBSD.ORG  Mon Dec 18 12:31:47 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229])
	by hub.freebsd.org (Postfix) with ESMTP
	id 210DE37B400; Mon, 18 Dec 2000 12:31:46 -0800 (PST)
Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1])
	by winston.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBIKVUw12586;
	Mon, 18 Dec 2000 12:31:30 -0800 (PST)
	(envelope-from jkh@winston.osd.bsdi.com)
To: Stephen McKay <mckay@thehub.com.au>
Cc: dmaddox@sc.rr.com, current@freebsd.org, jkh@freebsd.org
Subject: Re: Is compatibility for old aout binaries broken? 
In-Reply-To: Message from Stephen McKay <mckay@thehub.com.au> 
   of "Tue, 19 Dec 2000 01:00:28 +1000." <200012181500.eBIF0S612182@dungeon.home> 
Date: Mon, 18 Dec 2000 12:31:30 -0800
Message-ID: <12581.977171490@winston.osd.bsdi.com>
From: Jordan Hubbard <jkh@winston.osd.bsdi.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> The generated ld.so has bloated a bit :-) but works fine.  So we could
> in principle build ld.so for every release.  It's just a question of
> whether we should.  I think we should.  But it might be just as easy
> to copy it off the 3.3 CD every time.  It's dead end stuff after all.
> 
> Does the release engineer have an opinion?

If it's just for the compat3x distribution, I say check it into that
part of lib/compat and be done with it.  Uudecoding it each time is a
lot easier than building it.  Or are we talking about ld.so in some
different context?

- Jordan


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


From owner-freebsd-current  Mon Dec 18 14:39:58 2000
From owner-freebsd-current@FreeBSD.ORG  Mon Dec 18 14:39:57 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47])
	by hub.freebsd.org (Postfix) with ESMTP id BFFD037B400
	for <freebsd-current@FreeBSD.ORG>; Mon, 18 Dec 2000 14:39:56 -0800 (PST)
Received: from localhost (dwhite@localhost)
	by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id eBIMdpm65538;
	Mon, 18 Dec 2000 14:39:52 -0800 (PST)
Date: Mon, 18 Dec 2000 14:39:51 -0800 (PST)
From: Doug White <dwhite@resnet.uoregon.edu>
To: John Miller <johnmiller@pcimedia.com>
Cc: "Freebsd-Current (E-mail)" <freebsd-current@FreeBSD.ORG>
Subject: Re: Bridging NT4 subnets
In-Reply-To: <000201c0653b$cefdf6c0$01000001@MILLER1>
Message-ID: <Pine.BSF.4.21.0012181439400.59300-100000@resnet.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, 13 Dec 2000, John Miller wrote:

> 
> I am having trouble setting up bridge between 2 subnets with NT4 servers on
> either side.  Both subnets are behind different firewalls for external
> access.
> Static Routes have been setup on each subnets firewalls to route traffic
> through the bridge.

Use WINS and save yourself the pain. Really.

Doug White                    |  FreeBSD: The Power to Serve
dwhite@resnet.uoregon.edu     |  www.FreeBSD.org



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


From owner-freebsd-current  Mon Dec 18 16:27: 3 2000
From owner-freebsd-current@FreeBSD.ORG  Mon Dec 18 16:27:01 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.66])
	by hub.freebsd.org (Postfix) with ESMTP id 549C237B400
	for <current@FreeBSD.ORG>; Mon, 18 Dec 2000 16:27:00 -0800 (PST)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.11.0/8.11.0) with ESMTP id eBJ0Qts10072;
	Mon, 18 Dec 2000 17:26:55 -0700 (MST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA95776; Mon, 18 Dec 2000 17:26:53 -0700 (MST)
Message-Id: <200012190026.RAA95776@harmony.village.org>
To: Michael Class <michael_class@hp.com>
Subject: Re: Network performance-problem 
Cc: current@FreeBSD.ORG
In-reply-to: Your message of "Mon, 18 Dec 2000 10:49:59 +0100."
		<3A3DDDC7.6F2540B7@hp.com> 
References: <3A3DDDC7.6F2540B7@hp.com>  
Date: Mon, 18 Dec 2000 17:26:53 -0700
From: Warner Losh <imp@village.org>
Sender: imp@harmony.village.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <3A3DDDC7.6F2540B7@hp.com> Michael Class writes:
: xl0: no carrier - transceiver cable problem?
: Why behaves my FreeBSD-machines worse then the other boxes? Any Ideas?

My 3CCFE575CT doesn't have this problem, except when I'm using it with
a bad cable.  Maybe that's the problem?

Warner


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


From owner-freebsd-current  Mon Dec 18 16:28:36 2000
From owner-freebsd-current@FreeBSD.ORG  Mon Dec 18 16:28:34 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.66])
	by hub.freebsd.org (Postfix) with ESMTP id 789F837B400
	for <current@FreeBSD.ORG>; Mon, 18 Dec 2000 16:28:32 -0800 (PST)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.11.0/8.11.0) with ESMTP id eBJ0SUs10089;
	Mon, 18 Dec 2000 17:28:30 -0700 (MST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA95806; Mon, 18 Dec 2000 17:28:29 -0700 (MST)
Message-Id: <200012190028.RAA95806@harmony.village.org>
To: Toshihiko ARAI <toshi@jp.FreeBSD.org>
Subject: Re: HEADSUP: Linksys cards need flag. 
Cc: current@FreeBSD.ORG
In-reply-to: Your message of "Tue, 19 Dec 2000 00:43:43 +0900."
		<200012181543.AAA89316.toshi@jp.FreeBSD.org> 
References: <200012181543.AAA89316.toshi@jp.FreeBSD.org>  
Date: Mon, 18 Dec 2000 17:28:29 -0700
From: Warner Losh <imp@village.org>
Sender: imp@harmony.village.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <200012181543.AAA89316.toshi@jp.FreeBSD.org> Toshihiko ARAI writes:
: Linksys Fast Ethernet PCCARD cards supported by the ed driver now
: require the addition of flag 0x80000 to their config line in
: pccard.conf(5).  This flag is not optional.  These Linksys cards will
: not be recognized without it.

I've added the above text to the UPDATING file.

I should add that mergemaster will automatically upgrade their
machines will have this fixed automatically.

Warner


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


From owner-freebsd-current  Mon Dec 18 17:15: 9 2000
From owner-freebsd-current@FreeBSD.ORG  Mon Dec 18 17:15:07 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from leaf.lumiere.net (leaf.lumiere.net [208.44.192.100])
	by hub.freebsd.org (Postfix) with ESMTP id DE4E637B400
	for <freebsd-current@freebsd.org>; Mon, 18 Dec 2000 17:15:07 -0800 (PST)
Received: by leaf.lumiere.net (Postfix, from userid 1069)
	id BE7E8CCF4; Mon, 18 Dec 2000 17:15:07 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by leaf.lumiere.net (Postfix) with ESMTP id BD1773B28
	for <freebsd-current@freebsd.org>; Mon, 18 Dec 2000 17:15:07 -0800 (PST)
Date: Mon, 18 Dec 2000 17:15:07 -0800 (PST)
From: Dave Gustafson <dave@lumiere.net>
To: freebsd-current@freebsd.org
Subject: subscribe
Message-ID: <Pine.BSF.4.21.0012181714570.95839-100000@leaf.lumiere.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG




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


From owner-freebsd-current  Mon Dec 18 20:38:41 2000
From owner-freebsd-current@FreeBSD.ORG  Mon Dec 18 20:38:39 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from ns5.pacific.net.au (ns5.pacific.net.au [203.143.252.30])
	by hub.freebsd.org (Postfix) with ESMTP id 8ED3537B402
	for <current@freebsd.org>; Mon, 18 Dec 2000 20:38:37 -0800 (PST)
Received: from dungeon.home (ppp117.dyn249.pacific.net.au [203.143.249.117])
	by ns5.pacific.net.au (8.9.0/8.9.1) with ESMTP id PAA19821;
	Tue, 19 Dec 2000 15:38:32 +1100 (EST)
Received: from dungeon.home (localhost [127.0.0.1])
	by dungeon.home (8.11.1/8.9.3) with ESMTP id eBJ4d4o10165;
	Tue, 19 Dec 2000 14:39:04 +1000 (EST)
	(envelope-from mckay)
Message-Id: <200012190439.eBJ4d4o10165@dungeon.home>
To: Jordan Hubbard <jkh@winston.osd.bsdi.com>
Cc: current@freebsd.org, mckay@thehub.com.au
Subject: Re: Is compatibility for old aout binaries broken? 
References: <200012181500.eBIF0S612182@dungeon.home> <12581.977171490@winston.osd.bsdi.com>
In-Reply-To: <12581.977171490@winston.osd.bsdi.com>
    from Jordan Hubbard at "Mon, 18 Dec 2000 20:31:30 +0000"
Date: Tue, 19 Dec 2000 14:39:04 +1000
From: Stephen McKay <mckay@thehub.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Monday, 18th December 2000, Jordan Hubbard wrote:

>> The generated ld.so has bloated a bit :-) but works fine.  So we could
>> in principle build ld.so for every release.  It's just a question of
>> whether we should.  I think we should.  But it might be just as easy
>> to copy it off the 3.3 CD every time.  It's dead end stuff after all.
>> 
>> Does the release engineer have an opinion?
>
>If it's just for the compat3x distribution, I say check it into that
>part of lib/compat and be done with it.  Uudecoding it each time is a
>lot easier than building it.  Or are we talking about ld.so in some
>different context?

I hadn't noticed all the uuencoded things in lib/compat before.  This
is obviously the way to fix it.

By the way, it's the compat22 distribution that needs fixing, and, as
previously noted, it's the 3.2 CD that has the last fully working ld.so.

I'll get onto committing a fix.

Stephen.


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


From owner-freebsd-current  Mon Dec 18 20:52:19 2000
From owner-freebsd-current@FreeBSD.ORG  Mon Dec 18 20:52:17 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mta03.mail.mel.aone.net.au (mta03.mail.au.uu.net [203.2.192.83])
	by hub.freebsd.org (Postfix) with ESMTP id B821537B400
	for <current@freebsd.org>; Mon, 18 Dec 2000 20:52:16 -0800 (PST)
Received: from camtech.net.au ([203.28.1.144])
          by mta03.mail.mel.aone.net.au with ESMTP
          id <20001219045214.TWZO4972.mta03.mail.mel.aone.net.au@camtech.net.au>;
          Tue, 19 Dec 2000 15:52:14 +1100
Sender: me@FreeBSD.ORG
Message-ID: <3A3EEA08.E63EC165@camtech.net.au>
Date: Tue, 19 Dec 2000 15:24:32 +1030
From: Matthew Thyer <thyerm@camtech.net.au>
X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Michael Class <michael_class@hp.com>
Cc: current@freebsd.org
Subject: Re: Network performance-problem
References: <3A3DDDC7.6F2540B7@hp.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Michael Class wrote:
> 
> Hello,
> 
> i am seeing a problem with 5.0-current (from 14.12.00) and a 3COM
> 3CCFE575CT Lancard (pc-cardbus) using the xl-driver.

[snip]

> Why behaves my FreeBSD-machines worse then the other boxes? Any Ideas?

Make sure you are running with the TCP/IP NewReno optimisation turned
off.  There are bugs in the TCP/IP NewReno code that result in bad
packets and hence lots of retransmission with generally reduced network
performance.

I think its meant to be the default now in -CURRENT (to have NewReno off)
but I'm not sure if PHK has disabled it yet.

$ cat /usr/local/etc/rc.d/nonewreno.sh 
#!/bin/sh
sysctl -w net.inet.tcp.newreno=0
echo -n " no_newreno"

$ sysctl net.inet.tcp.newreno
net.inet.tcp.newreno: 0

One day hopefully NewReno may be fixed as it sounded worthwhile.

See Poul's messages in the freebsd-current archives.


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


From owner-freebsd-current  Mon Dec 18 20:55:53 2000
From owner-freebsd-current@FreeBSD.ORG  Mon Dec 18 20:55:51 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mta04.mail.mel.aone.net.au (mta04.mail.au.uu.net [203.2.192.84])
	by hub.freebsd.org (Postfix) with ESMTP id 0983637B400
	for <current@freebsd.org>; Mon, 18 Dec 2000 20:55:50 -0800 (PST)
Received: from camtech.net.au ([203.28.1.144])
          by mta04.mail.mel.aone.net.au with ESMTP
          id <20001219045548.NUJP19873.mta04.mail.mel.aone.net.au@camtech.net.au>;
          Tue, 19 Dec 2000 15:55:48 +1100
Sender: me@FreeBSD.ORG
Message-ID: <3A3EEADE.3924E4E6@camtech.net.au>
Date: Tue, 19 Dec 2000 15:28:06 +1030
From: Matthew Thyer <thyerm@camtech.net.au>
X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Michael Class <michael_class@hp.com>
Cc: current@freebsd.org
Subject: Re: Network performance-problem
References: <3A3DDDC7.6F2540B7@hp.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Michael Class wrote:
> 
> Hello,
> 
> i am seeing a problem with 5.0-current (from 14.12.00) and a 3COM
> 3CCFE575CT Lancard (pc-cardbus) using the xl-driver.

[snip]

> Why behaves my FreeBSD-machines worse then the other boxes? Any Ideas?

Make sure you are running with the TCP/IP NewReno optimisation turned
off.  There are bugs in the TCP/IP NewReno code that result in bad
packets and hence lots of retransmission with generally reduced network
performance.

I think its meant to be the default now in -CURRENT (to have NewReno off)
but I'm not sure if PHK has disabled it yet.

$ cat /usr/local/etc/rc.d/nonewreno.sh 
#!/bin/sh
sysctl -w net.inet.tcp.newreno=0
echo -n " no_newreno"

$ sysctl net.inet.tcp.newreno
net.inet.tcp.newreno: 0

One day hopefully NewReno may be fixed as it sounded worthwhile.

See Poul's messages in the freebsd-current archives.


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


From owner-freebsd-current  Mon Dec 18 23:27: 8 2000
From owner-freebsd-current@FreeBSD.ORG  Mon Dec 18 23:27:07 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 664)
	id 11F5037B400; Mon, 18 Dec 2000 23:27:07 -0800 (PST)
Date: Mon, 18 Dec 2000 23:27:07 -0800
From: David O'Brien <obrien@FreeBSD.ORG>
To: Stephen McKay <mckay@thehub.com.au>
Cc: current@freebsd.org
Subject: Re: Is compatibility for old aout binaries broken?
Message-ID: <20001218232706.A90914@hub.freebsd.org>
Reply-To: obrien@freebsd.org
References: <20001216161756.A6370@cae88-102-101.sc.rr.com> <200012171658.eBHGwGW24109@dungeon.home> <20001217135431.C9721@cae88-102-101.sc.rr.com> <200012180641.eBI6fH607564@dungeon.home> <20001218014656.A17483@cae88-102-101.sc.rr.com> <200012181500.eBIF0S612182@dungeon.home> <20001218100315.A67679@dragon.nuxi.com> <200012190508.eBJ58Po10495@dungeon.home>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <200012190508.eBJ58Po10495@dungeon.home>; from mckay@thehub.com.au on Tue, Dec 19, 2000 at 03:08:25PM +1000
X-Operating-System: FreeBSD 4.2-STABLE
Organization: The NUXI BSD group
X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3  90 76 5D 69 58 D9 98 7A
X-Pgp-Rsa-Keyid: 1024/34F9F9D5
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, Dec 19, 2000 at 03:08:25PM +1000, Stephen McKay wrote:
> Our current problem is that an older ld.so has somehow been made part
> of compat22.  I'm now attempting to determine whether the ld.so on
> the 3.2 CD contains the fix in rev 1.57 of rtld-aout/rtld.c, and if
> so I'll just commit it in the compat22 directory.

Please delay committing -- since it is UUENCODED, it is a bit repo bloat
if we don't get it right.  It doesn't seem right to put 3.x bits into the
compat22 dist.  By definition they are the wrong bits.  My internet
connection is down for the past day, and I only have limited connectivity
right now.   But I would like to look into this before anything is
committed.

- 
-- David    (obrien@FreeBSD.org)


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


From owner-freebsd-current  Mon Dec 18 23:36: 8 2000
From owner-freebsd-current@FreeBSD.ORG  Mon Dec 18 23:36:04 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from dante.naver.co.id (unknown [202.155.86.82])
	by hub.freebsd.org (Postfix) with ESMTP id 66A5D37B400
	for <freebsd-current@freebsd.org>; Mon, 18 Dec 2000 23:36:03 -0800 (PST)
Received: by dante.naver.co.id (Postfix, from userid 1000)
	id 61E1360E0A; Tue, 19 Dec 2000 14:35:54 +0700 (JAVT)
Date: Tue, 19 Dec 2000 14:35:54 +0700
From: John Indra <john@naver.co.id>
To: freebsd-current@freebsd.org
Subject: Recent -CURRENT kernel build problem...
Message-ID: <20001219143553.B525@naver.co.id>
Mail-Followup-To: freebsd-current@freebsd.org
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="BOKacYhQ+x31HxR3"
Content-Disposition: inline
X-Mailer: Mutt 1.2.5i on FreeBSD 5.0-CURRENT i386
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


--BOKacYhQ+x31HxR3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Dear all...

Has anyone noticed this problem? Or is it just happening to me?
On make buildkernel (with -CURRENT just cvsuped a few minutes ago) and the
generic config KERNEL; make depend; make; cycle, the kernel build failed
with this message:

--

cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual
-fformat-extensions -ansi  -nostdinc -I-  -I. -I../.. -I../../dev
-I../../../include -I../../contrib/dev/acpica/Subsystem/Include  -D_KERNEL
-include opt_global.h -elf  -mpreferred-stack-boundary=2  vers.c
linking kernel
agp_amd.o: In function `agp_amd_alloc_gatt':
agp_amd.o(.text+0x67): undefined reference to `M_AGP'
agp_amd.o(.text+0x89): undefined reference to `M_AGP'
agp_amd.o(.text+0xd5): undefined reference to `M_AGP'
agp_amd.o(.text+0x105): undefined reference to `M_AGP'
agp_amd.o(.text+0x112): undefined reference to `M_AGP'
agp_amd.o(.text+0x234): more undefined references to `M_AGP' follow
*** Error code 1
 
Stop in /usr/src/sys/compile/DANTE.

--

Please help, my kernel and userland is badly not in sync ;)
Attached is my kernel config file.

Thank you...

Regards,
John


--BOKacYhQ+x31HxR3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename=DANTE

ident		DANTE
machine		i386
cpu		I686_CPU
maxusers	256

options 	INET
options 	FFS
options 	FFS_ROOT
options 	SOFTUPDATES
options 	COMPAT_43
options 	UCONSOLE
options 	USERCONFIG
options 	VISUAL_USERCONFIG
options 	KTRACE
options 	SYSVSHM
options 	SYSVMSG
options 	SYSVSEM
options		SHMMAX=33554432
options		SHMALL=16384
options 	P1003_1B
options 	_KPOSIX_PRIORITY_SCHEDULING
options 	KBD_INSTALL_CDEV
options 	ATA_STATIC_ID
options 	ATA_ENABLE_ATAPI_DMA
options		USER_LDT
options		IPFILTER
options		IPFILTER_LOG
options		TCP_DROP_SYNFIN
options		TCP_RESTRICT_RST
options		VESA
options		NMBCLUSTERS=16384
options		SC_DISABLE_REBOOT
options 	NOBLOCKRANDOM

device		isa
device		pci
device		fdc
device		ata
device		atadisk
device		atapicd
device		atkbdc	1
device		atkbd
device		psm
device		vga
device		splash
device		sc	1
device		npx
device		apm
device		sio
device		ppc
device		ppbus
device		lpt
device		plip
device		ppi
device		miibus
device		xl
device		random
device		loop
device		ether
device		tun
device		pty
device		md
device		bpf
device		vn
device		snp
device		pcm
device		agp

--BOKacYhQ+x31HxR3--


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


From owner-freebsd-current  Tue Dec 19  0:17: 6 2000
From owner-freebsd-current@FreeBSD.ORG  Tue Dec 19 00:17:02 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65])
	by hub.freebsd.org (Postfix) with ESMTP
	id 60BD637B402; Tue, 19 Dec 2000 00:16:55 -0800 (PST)
Received: (from ru@localhost)
	by whale.sunbay.crimea.ua (8.11.0/8.11.0) id eBJ8G2e50770;
	Tue, 19 Dec 2000 10:16:02 +0200 (EET)
	(envelope-from ru)
Date: Tue, 19 Dec 2000 10:16:01 +0200
From: Ruslan Ermilov <ru@FreeBSD.ORG>
To: John Indra <john@naver.co.id>
Cc: freebsd-current@FreeBSD.ORG, Poul-Henning Kamp <phk@FreeBSD.ORG>
Subject: Re: Recent -CURRENT kernel build problem...
Message-ID: <20001219101601.H48238@sunbay.com>
Mail-Followup-To: John Indra <john@naver.co.id>,
	freebsd-current@FreeBSD.ORG, Poul-Henning Kamp <phk@FreeBSD.org>
References: <20001219143553.B525@naver.co.id>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20001219143553.B525@naver.co.id>; from john@naver.co.id on Tue, Dec 19, 2000 at 02:35:54PM +0700
Sender: ru@whale.sunbay.crimea.ua
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

If I remeber correctly, someone else reported this was caused by
phk's change staticizing something...  Sorry, I do not recall this
in details, and I don't have a fresh -CURRENT.

On Tue, Dec 19, 2000 at 02:35:54PM +0700, John Indra wrote:
> Dear all...
> 
> Has anyone noticed this problem? Or is it just happening to me?
> On make buildkernel (with -CURRENT just cvsuped a few minutes ago) and the
> generic config KERNEL; make depend; make; cycle, the kernel build failed
> with this message:
> 
> --
> 
> cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
> -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual
> -fformat-extensions -ansi  -nostdinc -I-  -I. -I../.. -I../../dev
> -I../../../include -I../../contrib/dev/acpica/Subsystem/Include  -D_KERNEL
> -include opt_global.h -elf  -mpreferred-stack-boundary=2  vers.c
> linking kernel
> agp_amd.o: In function `agp_amd_alloc_gatt':
> agp_amd.o(.text+0x67): undefined reference to `M_AGP'
> agp_amd.o(.text+0x89): undefined reference to `M_AGP'
> agp_amd.o(.text+0xd5): undefined reference to `M_AGP'
> agp_amd.o(.text+0x105): undefined reference to `M_AGP'
> agp_amd.o(.text+0x112): undefined reference to `M_AGP'
> agp_amd.o(.text+0x234): more undefined references to `M_AGP' follow
> *** Error code 1
>  
> Stop in /usr/src/sys/compile/DANTE.
> 
> --
> 
> Please help, my kernel and userland is badly not in sync ;)
> Attached is my kernel config file.
> 
> Thank you...
> 
> Regards,
> John
> 

> ident		DANTE
> machine		i386
> cpu		I686_CPU
> maxusers	256
> 
> options 	INET
> options 	FFS
> options 	FFS_ROOT
> options 	SOFTUPDATES
> options 	COMPAT_43
> options 	UCONSOLE
> options 	USERCONFIG
> options 	VISUAL_USERCONFIG
> options 	KTRACE
> options 	SYSVSHM
> options 	SYSVMSG
> options 	SYSVSEM
> options		SHMMAX=33554432
> options		SHMALL=16384
> options 	P1003_1B
> options 	_KPOSIX_PRIORITY_SCHEDULING
> options 	KBD_INSTALL_CDEV
> options 	ATA_STATIC_ID
> options 	ATA_ENABLE_ATAPI_DMA
> options		USER_LDT
> options		IPFILTER
> options		IPFILTER_LOG
> options		TCP_DROP_SYNFIN
> options		TCP_RESTRICT_RST
> options		VESA
> options		NMBCLUSTERS=16384
> options		SC_DISABLE_REBOOT
> options 	NOBLOCKRANDOM
> 
> device		isa
> device		pci
> device		fdc
> device		ata
> device		atadisk
> device		atapicd
> device		atkbdc	1
> device		atkbd
> device		psm
> device		vga
> device		splash
> device		sc	1
> device		npx
> device		apm
> device		sio
> device		ppc
> device		ppbus
> device		lpt
> device		plip
> device		ppi
> device		miibus
> device		xl
> device		random
> device		loop
> device		ether
> device		tun
> device		pty
> device		md
> device		bpf
> device		vn
> device		snp
> device		pcm
> device		agp


-- 
Ruslan Ermilov		Oracle Developer/DBA,
ru@sunbay.com		Sunbay Software AG,
ru@FreeBSD.org		FreeBSD committer,
+380.652.512.251	Simferopol, Ukraine

http://www.FreeBSD.org	The Power To Serve
http://www.oracle.com	Enabling The Information Age


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


From owner-freebsd-current  Tue Dec 19  0:23:13 2000
From owner-freebsd-current@FreeBSD.ORG  Tue Dec 19 00:23:10 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from assaris.sics.se (h122n4fls32o892.telia.com [213.64.47.122])
	by hub.freebsd.org (Postfix) with ESMTP id 3937D37B402
	for <freebsd-current@FreeBSD.ORG>; Tue, 19 Dec 2000 00:23:09 -0800 (PST)
Received: (from assar@localhost)
	by assaris.sics.se (8.9.3/8.9.3) id JAA80087;
	Tue, 19 Dec 2000 09:22:58 +0100 (CET)
	(envelope-from assar)
Sender: assar@assaris.sics.se
From: assar@FreeBSD.ORG
To: John Indra <john@naver.co.id>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: Recent -CURRENT kernel build problem...
References: <20001219143553.B525@naver.co.id>
Date: 19 Dec 2000 09:22:57 +0100
In-Reply-To: John Indra's message of "Tue, 19 Dec 2000 14:35:54 +0700"
Message-ID: <5lk88wes66.fsf@assaris.sics.se>
Lines: 36
User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

John Indra <john@naver.co.id> writes:
> cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
> -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual
> -fformat-extensions -ansi  -nostdinc -I-  -I. -I../.. -I../../dev
> -I../../../include -I../../contrib/dev/acpica/Subsystem/Include  -D_KERNEL
> -include opt_global.h -elf  -mpreferred-stack-boundary=2  vers.c
> linking kernel
> agp_amd.o: In function `agp_amd_alloc_gatt':
> agp_amd.o(.text+0x67): undefined reference to `M_AGP'
> agp_amd.o(.text+0x89): undefined reference to `M_AGP'
> agp_amd.o(.text+0xd5): undefined reference to `M_AGP'
> agp_amd.o(.text+0x105): undefined reference to `M_AGP'
> agp_amd.o(.text+0x112): undefined reference to `M_AGP'
> agp_amd.o(.text+0x234): more undefined references to `M_AGP' follow
> *** Error code 1

Can you try the appended patch and tell us how it goes?

/assar

Index: agp.c
===================================================================
RCS file: /home/ncvs/src/sys/pci/agp.c,v
retrieving revision 1.9
diff -u -w -u -w -r1.9 agp.c
--- agp.c	2000/12/12 20:24:36	1.9
+++ agp.c	2000/12/19 08:22:01
@@ -59,7 +59,7 @@
 
 MODULE_VERSION(agp, 1);
 
-static MALLOC_DEFINE(M_AGP, "agp", "AGP data structures");
+MALLOC_DEFINE(M_AGP, "agp", "AGP data structures");
 
 #define CDEV_MAJOR	148
 				/* agp_drv.c */


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


From owner-freebsd-current  Tue Dec 19  0:43:38 2000
From owner-freebsd-current@FreeBSD.ORG  Tue Dec 19 00:43:36 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from dante.naver.co.id (unknown [202.155.86.82])
	by hub.freebsd.org (Postfix) with ESMTP id 5FDA137B402
	for <freebsd-current@FreeBSD.ORG>; Tue, 19 Dec 2000 00:43:35 -0800 (PST)
Received: by dante.naver.co.id (Postfix, from userid 1000)
	id 930E560E0A; Tue, 19 Dec 2000 15:43:30 +0700 (JAVT)
Date: Tue, 19 Dec 2000 15:43:30 +0700
From: John Indra <john@naver.co.id>
To: freebsd-current@FreeBSD.ORG
Subject: Re: Recent -CURRENT kernel build problem...
Message-ID: <20001219154330.D525@naver.co.id>
Mail-Followup-To: freebsd-current@FreeBSD.ORG
References: <20001219143553.B525@naver.co.id> <20001219101601.H48238@sunbay.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20001219101601.H48238@sunbay.com>; from ru@FreeBSD.ORG on Tue, Dec 19, 2000 at 10:16:01AM +0200
X-Mailer: Mutt 1.2.5i on FreeBSD 5.0-CURRENT i386
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, Dec 19, 2000 at 10:16:01AM +0200, Ruslan Ermilov wrote:

>If I remeber correctly, someone else reported this was caused by
>phk's change staticizing something...  Sorry, I do not recall this
>in details, and I don't have a fresh -CURRENT.

OK then...
Any workaround or fix coming shortly to overcome this guys?

BTW... I am very interested to become one of you guys, the FreeBSD
committers. I mean it. I am ready to devote my life to FreeBSD (if this
phrase is not too much :) ). Now I am still trying to finish my Bachelor
degree. In the mean time I am working as a Network Administrator for a
company in Indonesia. Soon after I finish my school, I will have plenty of
time to study C and maybe try to understand piece by piece FreeBSD codes,
maybe not in all section, and if I am qualified enough, I'd like to
contribute something to FreeBSD.

What I need now is a guidance. I think I'm not a very novice programmer. For
my bachelor degree, I'm trying to make a Natural Language enabled (at
semantic level) search engine. Planning to use Perl to build the beast :)
Where can I start to dig more information about OS, efficient programming
with C, etc. to help me get what I want?

Sorry, I think this is becoming out of topic, but I'm very glad to have said
my wish :)

Thanks a lot...

Regards,
John



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


From owner-freebsd-current  Tue Dec 19  1: 4:39 2000
From owner-freebsd-current@FreeBSD.ORG  Tue Dec 19 01:04:37 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from dante.naver.co.id (unknown [202.155.86.82])
	by hub.freebsd.org (Postfix) with ESMTP id A41E237B400
	for <freebsd-current@FreeBSD.ORG>; Tue, 19 Dec 2000 01:04:36 -0800 (PST)
Received: by dante.naver.co.id (Postfix, from userid 1000)
	id 8446A60E0A; Tue, 19 Dec 2000 16:04:34 +0700 (JAVT)
Date: Tue, 19 Dec 2000 16:04:34 +0700
From: John Indra <john@naver.co.id>
To: freebsd-current@FreeBSD.ORG
Subject: Re: Recent -CURRENT kernel build problem...
Message-ID: <20001219160434.A468@naver.co.id>
Mail-Followup-To: freebsd-current@FreeBSD.ORG
References: <20001219143553.B525@naver.co.id> <5lk88wes66.fsf@assaris.sics.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5lk88wes66.fsf@assaris.sics.se>; from assar@FreeBSD.ORG on Tue, Dec 19, 2000 at 09:22:57AM +0100
X-Mailer: Mutt 1.2.5i on FreeBSD 5.0-CURRENT i386
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, Dec 19, 2000 at 09:22:57AM +0100, assar@FreeBSD.ORG wrote:

>Can you try the appended patch and tell us how it goes?

Yeah... finally, my world is in sync with the kernel, what a joy :)
Until know... the system is pretty stable.
Will this be committed to the tree soon?

Thank you very much...

Regards,
John



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


From owner-freebsd-current  Tue Dec 19  1:10: 7 2000
From owner-freebsd-current@FreeBSD.ORG  Tue Dec 19 01:10:02 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from smtp.alcove.fr (smtp.alcove.fr [212.155.209.139])
	by hub.freebsd.org (Postfix) with ESMTP
	id F019C37B400; Tue, 19 Dec 2000 01:10:01 -0800 (PST)
Received: from wiliam.alcove-int ([10.16.110.19])
	by smtp.alcove.fr with esmtp (Exim 3.12 #1 (Debian))
	id 148ImW-0002NK-00; Tue, 19 Dec 2000 10:10:00 +0100
Received: from nsouch by wiliam.alcove-int with local (Exim 3.12 #1 (Debian))
	id 148ImV-0002w9-00; Tue, 19 Dec 2000 10:09:59 +0100
Date: Tue, 19 Dec 2000 10:09:59 +0100
From: Nicolas Souchu <nsouch@alcove.fr>
To: freebsd-current@freebsd.org
Cc: freebsd-multimedia@freebsd.org
Subject: Various VGA, VGL, FB questions
Message-ID: <20001219100959.A11249@wiliam.alcove-int>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.4i
Organization: =?iso-8859-1?Q?Alc=F4ve=2C_http:=2F=2Fwww=2Ealcove=2Efr?=
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Dear hackers,

Why is there the same VGA code in dev/fb/vga.c and libvgl? I think
especially of the set_palette routines.

As a more general rule, what's the philosophy for the future of
libvgl and framebuffer? Should VGL drawing routines be moved to
dev/fb/vga.c?

Also, there are some drawing routines enclosed with notyet defines. What
are there state? bogus?

Finally, is someone working on this part of the tree currently?

Nicholas

-- 
Nicolas.Souchu@alcove.fr
Alcôve - Open Source Software Engineer - http://www.alcove.fr


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


From owner-freebsd-current  Tue Dec 19  1:22:41 2000
From owner-freebsd-current@FreeBSD.ORG  Tue Dec 19 01:22:36 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mass.osd.bsdi.com (adsl-63-202-177-107.dsl.snfc21.pacbell.net [63.202.177.107])
	by hub.freebsd.org (Postfix) with ESMTP
	id E9A9B37B400; Tue, 19 Dec 2000 01:22:35 -0800 (PST)
Received: from mass.osd.bsdi.com (localhost [127.0.0.1])
	by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBJ9WlQ11219;
	Tue, 19 Dec 2000 01:32:47 -0800 (PST)
	(envelope-from msmith@mass.osd.bsdi.com)
Message-Id: <200012190932.eBJ9WlQ11219@mass.osd.bsdi.com>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Nicolas Souchu <nsouch@alcove.fr>
Cc: freebsd-current@freebsd.org, freebsd-multimedia@freebsd.org
Subject: Re: Various VGA, VGL, FB questions 
In-reply-to: Your message of "Tue, 19 Dec 2000 10:09:59 +0100."
             <20001219100959.A11249@wiliam.alcove-int> 
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Date: Tue, 19 Dec 2000 01:32:47 -0800
From: Mike Smith <msmith@freebsd.org>
Sender: msmith@mass.osd.bsdi.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Why is there the same VGA code in dev/fb/vga.c and libvgl? I think
> especially of the set_palette routines.

The framebuffer code is a newer addition.  Libvgl was done quite a while =

ago as more or less a proof-of-concept.

> As a more general rule, what's the philosophy for the future of
> libvgl and framebuffer? Should VGL drawing routines be moved to
> dev/fb/vga.c?

The framebuffer should grow a set of drawing primitives, yes.  Exactly =

what these primitives is is probably open to discussion.  A good idea =

might be to look at the GGI project, which is producing =

BSD-license-compatible kernel-side graphics code.

> Finally, is someone working on this part of the tree currently?

You would want to check with Soren and Kazu, but I have not seen any =

activity recently.

-- =

=2E.. every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
           V I C T O R Y   N O T   V E N G E A N C E




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


From owner-freebsd-current  Tue Dec 19  1:56:45 2000
From owner-freebsd-current@FreeBSD.ORG  Tue Dec 19 01:56:39 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from smtp.alcove.fr (smtp.alcove.fr [212.155.209.139])
	by hub.freebsd.org (Postfix) with ESMTP
	id CF94F37B400; Tue, 19 Dec 2000 01:56:37 -0800 (PST)
Received: from wiliam.alcove-int ([10.16.110.19])
	by smtp.alcove.fr with esmtp (Exim 3.12 #1 (Debian))
	id 148JVb-0002lT-00; Tue, 19 Dec 2000 10:56:35 +0100
Received: from nsouch by wiliam.alcove-int with local (Exim 3.12 #1 (Debian))
	id 148JVb-00031Q-00; Tue, 19 Dec 2000 10:56:35 +0100
Date: Tue, 19 Dec 2000 10:56:34 +0100
From: Nicolas Souchu <nsouch@alcove.fr>
To: Mike Smith <msmith@freebsd.org>
Cc: freebsd-current@freebsd.org, freebsd-multimedia@freebsd.org
Subject: Re: Various VGA, VGL, FB questions
Message-ID: <20001219105634.B11249@wiliam.alcove-int>
References: <20001219100959.A11249@wiliam.alcove-int> <200012190932.eBJ9WlQ11219@mass.osd.bsdi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.4i
In-Reply-To: <200012190932.eBJ9WlQ11219@mass.osd.bsdi.com>; from msmith@freebsd.org on Tue, Dec 19, 2000 at 01:32:47AM -0800
Organization: =?iso-8859-1?Q?Alc=F4ve=2C_http:=2F=2Fwww=2Ealcove=2Efr?=
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, Dec 19, 2000 at 01:32:47AM -0800, Mike Smith wrote:
> > Why is there the same VGA code in dev/fb/vga.c and libvgl? I think
> > especially of the set_palette routines.
> 
> The framebuffer code is a newer addition.  Libvgl was done quite a while 
> ago as more or less a proof-of-concept.
> 
> > As a more general rule, what's the philosophy for the future of
> > libvgl and framebuffer? Should VGL drawing routines be moved to
> > dev/fb/vga.c?
> 
> The framebuffer should grow a set of drawing primitives, yes.  Exactly 
> what these primitives is is probably open to discussion.  A good idea 
> might be to look at the GGI project, which is producing 
> BSD-license-compatible kernel-side graphics code.

I'm currently porting GGI ;) This is why I'm interested in kernel graphic
support. I have already something done which is based on the VGL library
(keyboard and display in VGA modes -- the mouse is the standard linux-mouse
of GGI on top of /dev/sysmouse). It's already in the GGI library source package.

I can't hide much longer that my project is to get KGI ported to FreeBSD. But
that's another huge part. First, I'd like to have a clean overview of VGA/VESA/FB
support in FreeBSD. I think that with some efforts in the newbus direction, I'd
get rapidly this overview, isn't it?

Actually I moved to GGI / FreeBSD considerations because we need, in my company,
some proof of our capability to integrate low level stuff in open source kernels.
The second point is that I personaly think that FreeBSD has some lacks in graphic
support and that XFree is something to heavy.

I'd really love... a graphic boot. Yes, I know, that's not a priority for FreeBSD
headquarters :) For this I'll need graphic very early in the boot stages and I'll
certainly ask you more about this soon or later.

Nicholas

-- 
Nicolas.Souchu@alcove.fr
Alcôve - Open Source Software Engineer - http://www.alcove.fr


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


From owner-freebsd-current  Tue Dec 19  2: 3:46 2000
From owner-freebsd-current@FreeBSD.ORG  Tue Dec 19 02:03:44 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from assaris.sics.se (h122n4fls32o892.telia.com [213.64.47.122])
	by hub.freebsd.org (Postfix) with ESMTP id AA8BF37B400
	for <freebsd-current@FreeBSD.ORG>; Tue, 19 Dec 2000 02:03:43 -0800 (PST)
Received: (from assar@localhost)
	by assaris.sics.se (8.9.3/8.9.3) id LAA80358;
	Tue, 19 Dec 2000 11:03:38 +0100 (CET)
	(envelope-from assar)
Sender: assar@assaris.sics.se
From: assar@FreeBSD.ORG
To: John Indra <john@naver.co.id>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: Recent -CURRENT kernel build problem...
References: <20001219143553.B525@naver.co.id> <5lk88wes66.fsf@assaris.sics.se> <20001219160434.A468@naver.co.id>
Date: 19 Dec 2000 11:03:36 +0100
In-Reply-To: John Indra's message of "Tue, 19 Dec 2000 16:04:34 +0700"
Message-ID: <5lofy8budj.fsf@assaris.sics.se>
Lines: 8
User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

John Indra <john@naver.co.id> writes:
> Yeah... finally, my world is in sync with the kernel, what a joy :)
> Until know... the system is pretty stable.
> Will this be committed to the tree soon?

It has been comitted, I just wanted to test building first.

/assar


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


From owner-freebsd-current  Tue Dec 19  2:15: 4 2000
From owner-freebsd-current@FreeBSD.ORG  Tue Dec 19 02:15:03 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from borg.xsinet.co.za (borg.xsinet.co.za [196.25.196.69])
	by hub.freebsd.org (Postfix) with SMTP id 1B64237B402
	for <freebsd-current@FreeBSD.org>; Tue, 19 Dec 2000 02:15:01 -0800 (PST)
Received: (qmail 12924 invoked from network); 19 Dec 2000 12:15:04 -0200
Received: from unknown (HELO xsinet.co.za) (192.168.2.1)
  by 0 with SMTP; 19 Dec 2000 12:15:04 -0200
Sender: root@FreeBSD.ORG
Message-ID: <3A3E0001.FF5C169E@xsinet.co.za>
Date: Mon, 18 Dec 2000 14:16:01 +0200
From: Patrick <patrick@xsinet.co.za>
Reply-To: patrick@xsinet.co.za
Organization: XSInet
X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-current@FreeBSD.org
Subject: (no subject)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

 subscribe freebsd-current
 subscribe cvs-all



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


From owner-freebsd-current  Tue Dec 19  2:16: 5 2000
From owner-freebsd-current@FreeBSD.ORG  Tue Dec 19 02:16:01 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from cornholio.gagarinclub.ru (unknown [212.16.8.8])
	by hub.freebsd.org (Postfix) with ESMTP id 1160037B400
	for <current@freebsd.org>; Tue, 19 Dec 2000 02:16:01 -0800 (PST)
Received: from cr-fgpmkbd5aqvh (nick [10.20.25.2])
	by cornholio.gagarinclub.ru (8.11.1/8.11.1) with SMTP id eBJAFxw53373
	for <current@freebsd.org>; Tue, 19 Dec 2000 13:15:59 +0300 (MSK)
	(envelope-from nick)
Message-Id: <200012191015.eBJAFxw53373@cornholio.gagarinclub.ru>
From: "Globex" <globex@bsim.ru>
To: <current@freebsd.org>
Subject: Globex
Date: Tue, 19 Dec 2000 13:14:36 Ìîñêîâñêîå âðåìÿ (çèìà)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="windows-1251"
Content-Transfer-Encoding: 8bit
X-Priority: 1
X-MSMail-Priority: High
X-Mailer: 
Sender: nick@cornholio.gagarinclub.ru
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

ÓÂÀÆÀÅÌÛÅ ÄÀÌÛ È ÃÎÑÏÎÄÀ!
Ñïåøèì ïîçäðàâèòü Âàñ ñ íàñòóïàþùèì Ðîæäåñòâîì è Íîâûì 2001 ãîäîì! 
Æåëàåì Âàì óäà÷è è ïðîöâåòàíèÿ, ÷òî ïðàêòè÷åñêè íåâîçìîæíî áåç íàøåãî ó÷àñòèÿ!

Ãîòîâÿñü ê íîâîìó òûñÿ÷åëåòèþ, ìû òùàòåëüíî ïðîðàáîòàëè öåíîâóþ ïîëèòèêó êîìïàíèè 
è ïîäãîòîâèëè íîâîå ïðåäëîæåíèå ïî ïåðåâîçêå íåáîëüøèõ ãðóçîâ èç Åâðîïû àâòîòðàíñïîðòîì 
÷åðåç êîíñîëèäàöèþ íà ñêëàäàõ â Ãåðìàíèè è Èòàëèè.
Çàíèìàÿñü îðãàíèçàöèåé è êîíòðîëåì äâèæåíèÿ ãðóçîâ èç Ãåðìàíèè è Èòàëèè, 
ìû äîáèëèñü ñóùåñòâåííîãî ñíèæåíèÿ òðàíñïîðòíûõ çàòðàò íàøèõ êëèåíòîâ 
è èìååì âîçìîæíîñòü ïðèíèìàòü ê ïåðåâîçêå ãðóçû îò 1 êîðîáêè äî åâðîôóðû. 

ÎÁÙÀß ÑÒÎÈÌÎÑÒÜ ÎÁÑËÓÆÈÂÀÍÈß ÃÐÓÇÎÂ 

ÏÎ ÃÅÐÌÀÍÈÈ (ÌÞÍÕÅÍ, ÁÅÐËÈÍ)    
MIN - 250$
1 - 5 êáì - 240$/êáì
6 - 10 êáì - 230$/êáì
11 - 15 êáì - 220$/êáì
16 - 20 êáì - 210$/êáì
21 - 40 êáì - 200$/êáì
41 - 60 êáì - 195$/êáì
ñâûøå 61 êáì - 185$/êáì MIN - 280$

ÏÎ ÈÒÀËÈÈ (ÏÀÄÎÂÀ, ÌÈËÀÍ, ÔÀÍÎ) 
1 - 5 êáì - 270$/êáì
6 - 10 êáì - 260$/êáì
11 - 15 êáì - 250$/êáì
16 - 20 êáì - 240$/êáì
21 - 40 êáì - 230$/êáì
41 - 60 êáì - 220$/êáì
ñâûøå 61 êáì - 210$/êáì


Ñòðàõîâàíèå - 0.55% îò ñòîèìîñòè ãðóçà ïî ôàêòóðàì
Îôîðìëåíèå êàæäîé ôàêòóðû - 40$
Äîñòàâêà â ïðåäåëàõ Åâðîïû - îò 80$ äî 600$ (â çàâèñèìîñòè îò îáúåìà ãðóçà è ðàññòîÿíèÿ îò ìåñòà ïîãðóçêè äî ñêëàäà)
Äîñòàâêà ïî Ìîñêâå îò 40$ 

Ñðîêè äîñòàâêè "door to door" ñêëàäûâàþòñÿ èç ñëåäóþùèõ ôàêòîðîâ:
Ñ ìîìåíòà ïîëó÷åíèÿ çàÿâêè äî ìîìåíòà ôàêòè÷åñêîãî çàáîðà ãðóçà - 2-4 ðàáî÷èõ äíÿ
Ñðîêè äîñòàâêè ãðóçîâ â ïðåäåëàõ Åâðîïû - 2-7 ðàáî÷èõ äíåé
Ñðîê õðàíåíèÿ ãðóçà íà ñêëàäå äî áëèæàéøåé ìàøèíû:
! 2-5 ðàáî÷èõ äíåé ïî Èòàëèè
! 3-7 ðàáî÷èõ äíåé ïî Ãåðìàíèè
Ñðîê ïåðåâîçêè ãðóçà ïî ìàðøðóòó ñêëàä-Ìîñêâà:
! 7-9 êàëåíäàðíûõ äíåé èç Ãåðìàíèè
! 8-10 êàëåíäàðíûõ äíåé èç Èòàëèè

Ìû òàêæå ïðåäëàãàåì ñëåäóþùèå óñëóãè:
! Àâèàïåðåâîçêè ãðóçîâ èç ëþáîé òî÷êè ìèðà â ëþáîé àýðîïîðò. 
! Òàìîæåííîå îôîðìëåíèå ãðóçîâ â Øåðåìåòüåâî.
! Ñòðàõîâàíèå ãðóçîâ íà ëþáûõ óñëîâèÿõ.
! Îôîðìëåíèå òîâàðîñîïðîâîäèòåëüíîé äîêóìåíòàöèè ïåðåâîçèìûõ íàìè ãðóçîâ.
! Äîñòàâêà ïåðåâîçèìûõ íàìè ãðóçîâ ïî Ìîñêâå è â ðåãèîíû.
! Îðãàíèçàöèÿ äîñòàâêè ãðóçîâ ïî Ìîñêâå è â ðåãèîíû â ðåæèìå ÂÒÒ.
! Îðãàíèçàöèÿ ïåðåâîçêè ãðóçîâ âíóòðè Åâðîïû.
! Ñîäåéñòâèå â ðåøåíèè ïðîáëåìíûõ âîïðîñîâ â Øåðåìåòüåâñêîé òàìîæíå.
! Ðåãèñòðàöèÿ ïðåäïðèÿòèé â òàìîæåííûõ îðãàíàõ Øåðåìåòüåâî äëÿ âåäåíèÿ ÂÝÄ.
! Ïîìîùü â îðãàíèçàöèè ÂÝÄ.
! Ðàçðàáîòêà îïòèìàëüíûõ ñõåì äîñòàâêè Âàøèõ ãðóçîâ â çàâèñèìîñòè îò âèäà ãðóçà è ìåñòà åãî íàõîæäåíèÿ.
! Êîíñóëüòèðîâàíèå ïî ðàçëè÷íûì âîïðîñàì ÂÝÄ.

Òåëåôîíû : 147-6502; 147-6403; 147-4409. Ôàêñ: 147-7016. E-MAIL:  globex@bsim.ru 

Ñ óâàæåíèåì,
Êîëëåêòèâ êîìïàíèè "Globex".



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


From owner-freebsd-current  Tue Dec 19  3:33: 9 2000
From owner-freebsd-current@FreeBSD.ORG  Tue Dec 19 03:33:06 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from bbnrel4.net.external.hp.com (bbnrel4.net.external.hp.com [155.208.254.68])
	by hub.freebsd.org (Postfix) with ESMTP id 7004F37B400
	for <current@freebsd.org>; Tue, 19 Dec 2000 03:33:06 -0800 (PST)
Received: from tmbbmcc3.bbn.hp.com (tmbbmcc3.bbn.hp.com [15.136.126.78])
	by bbnrel4.net.external.hp.com (Postfix) with ESMTP
	id 562161CE7C; Tue, 19 Dec 2000 12:33:00 +0100 (MET)
Received: from hp.com (michaelc@tmbbwmc.bbn.hp.com [15.136.124.25]) by tmbbmcc3.bbn.hp.com with ESMTP (8.8.6 (PHNE_17190)/8.8.6 SMKit7.02) id MAA20423; Tue, 19 Dec 2000 12:32:58 +0100 (MET)
Sender: michaelc@tmbbmcc3.bbn.hp.com
Message-ID: <3A3F476A.9FA98FCC@hp.com>
Date: Tue, 19 Dec 2000 12:32:58 +0100
From: Michael Class <michael_class@hp.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; HP-UX B.10.20 9000/777)
X-Accept-Language: en
MIME-Version: 1.0
To: Matthew Thyer <thyerm@camtech.net.au>
Cc: current@freebsd.org
Subject: Re: Network performance-problem
References: <3A3DDDC7.6F2540B7@hp.com> <3A3EEA08.E63EC165@camtech.net.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Matthew Thyer wrote:
> 
> Michael Class wrote:
> > i am seeing a problem with 5.0-current (from 14.12.00) and a 3COM
> > 3CCFE575CT Lancard (pc-cardbus) using the xl-driver.
> 
> > Why behaves my FreeBSD-machines worse then the other boxes? Any Ideas?
> 
> Make sure you are running with the TCP/IP NewReno optimisation turned
> off.  There are bugs in the TCP/IP NewReno code that result in bad
> packets and hence lots of retransmission with generally reduced network
> performance.

It seems that NewReno is switched on by default in current.
Unfortunately switching off NewReno does not change the problem. In
times of very high network-traffic I am still unable to use the network.
The system does not even respond to a ping where as all other systems I
have (HPUX 10.20, 11.0 and NT4) behave as expected: slow response-times,
but still working and ping-able.

At home I am using this Laptop in a 100MB-Network and am able to almost
saturate the link without any problems. Could it be that this is just
happening for multicast-packets (that's what the high network-traffic
is)?

Anything else I could check?

TIA

Michael 


-- 
___________________________________________________________________________
Michael Class                            E-Mail: michael_class@hp.com
E-Business Solution Division             Phone:  +49 7031 14-3707
                                         Fax:    +49 7031 14-4505
___________________________________________________________________________
Hewlett-Packard GmbH, PO Box 1430, Mailstop ESD2, 71004 Boeblingen
Managing Directors: Rainer Geissel (Chairman),Rainer Erlat, Heribert
                    Schmitz, Hans-Jochen Lueckefett, Fritz Schuller
Chairman of the Supervisory Board: Joerg Menno Harms
Commercial register: Amtsgericht Boeblingen HRB 4081
___________________________________________________________________________


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


From owner-freebsd-current  Tue Dec 19  7:36:16 2000
From owner-freebsd-current@FreeBSD.ORG  Tue Dec 19 07:36:13 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5C88637B404; Tue, 19 Dec 2000 07:36:11 -0800 (PST)
Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92])
	by tasogare.imasy.or.jp (8.11.1+3.4W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id eBJFa6k74959;
	Wed, 20 Dec 2000 00:36:06 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
To: roam@orbitel.bg
Cc: msmith@FreeBSD.org, current@FreeBSD.org
Subject: Re: dev/acpica/acpi.c - minor patch for cleaner poweroff
In-Reply-To: <20001218165732.A5418@ringworld.oblivion.bg>
References: <20001218165732.A5418@ringworld.oblivion.bg>
X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20001220003605D.iwasaki@jp.FreeBSD.org>
Date: Wed, 20 Dec 2000 00:36:05 +0900
From: Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org>
X-Dispatcher: imput version 20000228(IM140)
Lines: 43
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

> I think you're the main maintainer of the ACPICA codebase (and yes, I know
> that parts of it is imported from Intel).  Attached is a trivial patch which
> makes for cleaner testing for RB_POWEROFF in acpi_shutdown_final() - I've had
> various kernel/userland routines invoke reboot sequences where the howto had
> more bits set than RB_POWEROFF, e.g. RB_NOSYNC.  With this patch, shutdown -p
> works for me :)

Thanks, this patch looks good.  I'll fix this soon.
I'm sure mike will agree on it :-)

> Thanks for all the work on ACPICA :)
> 
> G'luck,
> Peter
> 
> PS. Please CC: me in replies as I'm not on -current.
> 
> -- 
> If I had finished this sentence,
> 
> Index: acpi.c
> ===================================================================
> RCS file: /home/ncvs/src/sys/dev/acpica/acpi.c,v
> retrieving revision 1.7
> diff -u -r1.7 acpi.c
> --- acpi.c	2000/12/12 14:20:27	1.7
> +++ acpi.c	2000/12/18 14:55:43
> @@ -657,7 +657,7 @@
>  {
>      ACPI_STATUS	status;
>  
> -    if (howto == RB_POWEROFF) {
> +    if (howto & RB_POWEROFF) {
>  	printf("Power system off using ACPI...\n");
>  	if ((status = AcpiSetSystemSleepState(ACPI_STATE_S5)) != AE_OK) {
>  	    printf("ACPI power-off failed - %s\n", acpi_strerror(status));
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
> 


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


From owner-freebsd-current  Tue Dec 19  9:20:11 2000
From owner-freebsd-current@FreeBSD.ORG  Tue Dec 19 09:20:00 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from [210.236.11.88] (unknown [211.12.232.171])
	by hub.freebsd.org (Postfix) with ESMTP
	id F1EEB37B400; Tue, 19 Dec 2000 09:19:59 -0800 (PST)
Received: from pcvlx50g (210.235.163.111) by [210.236.11.88] with SMTP (Eudora
 Internet Mail Server 2.2.2); Wed, 20 Dec 2000 01:39:51 +0900
Message-ID: <000d01c069da$7fdf46e0$6fa3ebd2@pcvlx50g>
From: "T.Ishikawa" <oruto55@mybook.to>
To: <Undisclosed-Recipient:;@FreeBSD.ORG>
Subject: =?iso-2022-jp?B?GyRCPnBKc0hOR2QkTiQqQ04kaSQ7JEckORsoQg==?=
Date: Wed, 20 Dec 2000 01:32:16 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

$B!!$O$8$a$^$7$F!"!V#J#o#u#h#o!]#Y#A!*!W$N@P@n$H?=$7$^$9!#(B
$B!!FMA3$N%a!<%k$NG[?.@?$K<:Ni$$$?$7$^$7$?!#(B
$B!!6=L#$r$*;}$A$G$J$$>l9g$O!"@?$K62$lF~$j$^$9$,:o=|$/$@$5$$!#(B
$B!!@h$K!"$3$N$h$&$J#D#M$r?4$+$iK>$^$J$$J}$K$b$*Aw$j$7$?$3$H$r?<$/$*OM$S?=$7>e$2$^$9!#(B

$B!!EvJ}!"%M%C%H>e$GN">pJs$NHNGd$r9T$C$F$*$j$^$9!#(B
$B!!K\>&IJ$O!"$I$l$b3N<B$GM-NO$J>pJs$P$+$j$G$9!#6=L#$N$"$kJ}$OI,$:K~B-$7$F$$$?$@$1$k$O$:$G$9!#(B
$B!!FbMF$H$7$^$7$F$O!"0J2<$N$H$*$j$G$9!#(B

$B"!"!(,(,(,N">pJs(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,"!"!(B

$B!!!!%A%1%C%H$NEEOCM=Ls!!N">pJs2r@b(B
$B!!!!(BAAA$B5i$N%9!<%Q!<%3%T!<%V%i%s%I$N8D?M$G;EF~$l$kJ}K!(B
$B!!!!7HBSEEOC>pJs!*(BDoCoMo F502i$B!!(BDoCoMo P501i$B$NN"5;(B 
$B!!!!56B$%V%i%s%I>&IJ$N8+J,$1J}(B
$B!!!!<V$r6H<T2A3J$GGc$(!"@G6b$b@aLs=PMh$k8EJ*>&LH5v$N<hF@$N$7$+$?(B
$B!!!!%?%P%3$,$?$@$G<j$KF~$j!"$7$+$b?t@i1_$r<j$K$9$kJ}K!(B
$B!!!!?7IJEE2=@=IJ$rDj2A$N#5!A#63d0z$GGc$&J}K!(B
$B!!!!<+Bp$K$$$k$@$1$G!"8+CN$i$L=w@-$+$i$N%i%V%3!<%k$r<u$1$kJ}K!(B
$B!!!!40A4%V%i%C%/$G$bA4$F%A%c%i$K$9$kJ}K!(B
$B!!!!%/%l%8%C%H2CLAE9$N0E>'HV9f2rFIJ}K!(B
$B!!!!%9!<%Q!<$G#2#0#01_$/$i$$$GGc$($k9gK!%I%i%C%0(B
$B!!!!ITF0;:EP5-NA$rBgI}$K0B$/$9$kN"5;(B
$B!!!!M9JX6I!&;d@_$N;d=qH"0J30$KL5NA$GM9JXJ*$r<u<h$k2M6u$NJL=;=j$r;}$DJ}K!(B
$B!!!!N%:'Nr$r8M@R$+$i>C$9N"5;(B
$B!!!!3$30N99T$NGc$$J*$r%?%@$K$9$k(B 
$B!!!!IwB/>n$HM'C#$K$J$l!"$=$N>eKh7n$*>.;H$$$r$b$i$&J}K!(B
$B!!!!;D6H$r%+%C%H$5$l$F$b5kNA$N<j<h$j3[$r:#$^$G$NF13[$H$9$kJ}K!(B
$B!!!!2HDB#3K|!A#6K|1_$G!"El5~ETFb$N#3#D#K$N%^%s%7%g%s$KF~5o$9$kJ}K!(B
$B!!!!B?3[$N<Z6b$N:DL3@0M}$r$9$kJ}K!$r>\$7$/2r@b(B
$B!!!!#3#3%I%k$G309q$N5.B2$K$J$l$kJ}K!(B
$B!!!!;R6!$N=P;:HqMQ$r%?%@$K$9$kJ}K!(B 
$B!!!!<V$N%J%s%P!<Iu0u$r=}$rIU$1$:$K4JC1$K30$9J}K!(B
$B!!!!56L>$G%[%s%b%N$N<R2qJ]81>Z$r:n@.$9$kJ}K!(B
$B!!!!B>?ML>5A$G%[%s%b%N$N<R2qJ]81>Z$r:n@.$9$kJ}K!(B
$B!!!!L2$C$?$i5/$-$J$$!"$=$N4V$N5-21$,Ht$V%/%9%j:n@.J}K!(B
$B!!!!%D!<%7%g%C%H9b3[@A5a:>5=$N<j8}(B
$B!!!!Ht9T5!$G%(%3%N%_!<2A3J$G9gK!E*$K%U%!!<%9%H%/%i%9$K>h$kJ}K!(B
$B!!!!BpG[JXBe6b$,%?%@$K$J$k>e!"$*6b$^$GLc$($kJ}K!(B
$B!!!!%3%s%S%K$GGc$($kJ*$@$1K\3JGzCF$r:n$kJ}K!(B
$B!!!!85<j#5K|1_$G6bM;20$r3+6H$9$kJ}K!(B
$B!!!!%N!<%H(BPC$B$rGc$C$F3N<B$K?7IJ$b$&0lBf%?%@$GLc$&J}K!(B
$B!!!!85<j#1#0K|1_$GIwB/E9$r3+6H$9$kJ}K!(B
$B!!!!B>?ML>5A$G%5%i6b$+$i6b$r<Z$j$kJ}K!(B

$B"!"!(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,"!"!(B


$B!!>e5-$N>pJs$O!"$^$@$[$s$N0lIt$G$9(B
$B!!$"$H!"$*$^$1$H$7$F7]G=?M$N=;=jO?(B92$BL>!"=P?H9;JP:9CM(B130$BL>J,!"(B
$B!!%a!<%k%"%I%l%9(B300$BL>J,!!?76==!65$K2CF~$7$F$$$k(B200$BL>(B
$B!!$N%j%9%H$b$*IU$1$$$?$7$^$9!#(B
$B!!(B
$B!!9g7W(B300$BE@$H$*$^$1N">pJs$r(B3000$B1_$GHNGd$$$?$7$^$9!#$3$l$@$1$N>pJs$r$3$N2A3J$G$O!"(B
$B!!$[$+$G$O$^$:<j$KF~$j$^$;$s!#>pJs$H2A3J$K$O!"<+?.$r;}$C$F$$$^$9!#(B

$B!!$"$H!"$3$N>pJs$rE>Gd$5$l$k$J$I$9$l$P!"%5%$%I%S%8%M%9$N$*Lr$K$bN)$D$+$H;W$$$^$9!#(B

$B!!6=L#$r$b$?$l$?J}$O!"7oL>$r!V>pJs4uK>!W$H$7$F!"$*L>A0!J?69~$_?M3NG'$N$?$a$G$956L>$G$b$+$^$$$^$;$s!K(B
$B!!$r=q$+$l$?%a!<%k$r(B roais@vmail.vcc.ne.jp$B!!$K2<$5$l$P(B
  $B@^$jJV$7?69~$_8}:B!">\:Y$K$D$$$F=q$$$?%a!<%k$r$*Aw$j$7$^$9!#(B

$B!!>pJs$NG[?.J}K!$O!"#H#T#M#L7A<0$N%U%!%$%k$r%a!<%k$KE:IU!"$b$7$/$O#U#R#L$+$i$4Mw$K$J$C$F(B
$B!!D:$-$^$9!#(B

$B!!(B
$B!!:G8e$^$G$4Mw$K$J$C$F$$$?$@$-!"$I$&$b$"$j$,$H$&8f:B$$$^$7$?!#(B


$B!!"#"""#"""#"""#"""#"""#"""#"""#""(B

 $B!!!!@P@n!!F)!!!J(BIshikawa$B!!(BTohru$B!K(B
$B!!!!!!(Broais@vmail.vcc.ne.jp
  $B"#"""#"""#"""#"""#"""#"""#"""#""(B







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


From owner-freebsd-current  Tue Dec 19  9:50:23 2000
From owner-freebsd-current@FreeBSD.ORG  Tue Dec 19 09:50:18 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200])
	by hub.freebsd.org (Postfix) with ESMTP
	id 01ABA37B400; Tue, 19 Dec 2000 09:50:12 -0800 (PST)
Received: from shidahara1.planet.sci.kobe-u.ac.jp (localhost [127.0.0.1])
	by shidahara1.planet.sci.kobe-u.ac.jp (8.9.3/8.9.3) with ESMTP id CAA50228;
	Wed, 20 Dec 2000 02:50:25 +0900 (JST)
	(envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp)
Message-Id: <200012191750.CAA50228@shidahara1.planet.sci.kobe-u.ac.jp>
To: current@freebsd.org, hackers@freebsd.org
Subject: Call for review:PECOFF(Win32 Execution format) module.
Date: Wed, 20 Dec 2000 02:50:25 +0900
From: Takanori Watanabe <takawata@shidahara1.planet.sci.kobe-u.ac.jp>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi, I want to commit pecoff module under sys/compat/.
The code is at

http://people.freebsd.org/~takawata/pecoff.tar.gz

This is kernel part of PEACE(http://chiharu.haun.org/peace/),that is 
announced as NewFeature of NetBSD1.5.
Currently one more kernel module is needed to use PEACE in FreeBSD.

If there is no objection, I will commit it. 
Thanks.

Takanori Watanabe
<a href="http://www.planet.sci.kobe-u.ac.jp/~takawata/key.html">
Public Key</a>
Key fingerprint =  2C 51 E2 78 2C E1 C5 2D  0F F1 20 A3 11 3A 62 2A 



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


From owner-freebsd-current  Tue Dec 19 10:20:54 2000
From owner-freebsd-current@FreeBSD.ORG  Tue Dec 19 10:20:52 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from cae88-102-101.sc.rr.com (cae88-102-101.sc.rr.com [24.88.102.101])
	by hub.freebsd.org (Postfix) with ESMTP id 685FC37B404
	for <current@freebsd.org>; Tue, 19 Dec 2000 10:20:51 -0800 (PST)
Received: (from dmaddox@localhost)
	by cae88-102-101.sc.rr.com (8.11.1/8.11.1) id eBJIKvM01370
	for current@freebsd.org; Tue, 19 Dec 2000 13:20:57 -0500 (EST)
	(envelope-from dmaddox)
Date: Tue, 19 Dec 2000 13:20:57 -0500
From: "Donald J . Maddox" <dmaddox@sc.rr.com>
To: current@freebsd.org
Subject: Interesting new messages in logs
Message-ID: <20001219132057.A1338@cae88-102-101.sc.rr.com>
Reply-To: dmaddox@sc.rr.com
Mail-Followup-To: current@freebsd.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Return-Receipt-To: dmaddox@sc.rr.com
Sender: dmaddox@cae88-102-101.sc.rr.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

After my latest update, I am getting LOTS of the following in my logs:

Dec 19 12:21:04 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP ::0001:25 from ::0001:1286
Dec 19 12:24:08 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP ::0001:25 from ::0001:1299
Dec 19 12:27:13 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP ::0001:25 from ::0001:1308
Dec 19 12:39:28 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP ::0001:25 from ::0001:1336

Obviously, this machine is using log_in_vain, and it appears obvious
that these are local smtp transactions.  It is _not_ obvious, at
least to me, why they are now being logged as if port 25 was not
open.  Also, why the odd format in the addresses?


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


From owner-freebsd-current  Tue Dec 19 10:38:11 2000
From owner-freebsd-current@FreeBSD.ORG  Tue Dec 19 10:38:09 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from sol.cc.u-szeged.hu (sol.cc.u-szeged.hu [160.114.8.24])
	by hub.freebsd.org (Postfix) with ESMTP id 27A3B37B400
	for <current@freebsd.org>; Tue, 19 Dec 2000 10:38:08 -0800 (PST)
Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.3+Sun/SMI-SVR4)
	id TAA08747; Tue, 19 Dec 2000 19:36:58 +0100 (MET)
Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 3.12 #1 (Debian))
	id 148Ra9-0005X2-00
	for <current@freebsd.org>; Tue, 19 Dec 2000 19:33:49 +0100
Date: Tue, 19 Dec 2000 19:33:49 +0100
From: Szilveszter Adam <sziszi@petra.hos.u-szeged.hu>
To: current@freebsd.org
Subject: Re: Interesting new messages in logs
Message-ID: <20001219193349.E15002@petra.hos.u-szeged.hu>
Mail-Followup-To: Szilveszter Adam <sziszi@petra.hos.u-szeged.hu>,
	current@freebsd.org
References: <20001219132057.A1338@cae88-102-101.sc.rr.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20001219132057.A1338@cae88-102-101.sc.rr.com>; from dmaddox@sc.rr.com on Tue, Dec 19, 2000 at 01:20:57PM -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, Dec 19, 2000 at 01:20:57PM -0500, Donald J . Maddox wrote:
> After my latest update, I am getting LOTS of the following in my logs:
> 
> Dec 19 12:21:04 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP ::0001:25 from ::0001:1286
> Dec 19 12:24:08 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP ::0001:25 from ::0001:1299
> Dec 19 12:27:13 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP ::0001:25 from ::0001:1308
> Dec 19 12:39:28 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP ::0001:25 from ::0001:1336
> 
> Obviously, this machine is using log_in_vain, and it appears obvious
> that these are local smtp transactions.  It is _not_ obvious, at
> least to me, why they are now being logged as if port 25 was not
> open.  Also, why the odd format in the addresses?

Key might be: IPv6.:-) (At least for the addresses.) Check your
configuration if you are listening on port 25 for IPv6 or not...

That's off the top of my head though so yell at me if I am talking
nonsense:-)
 
-- 
Regards:

Szilveszter ADAM
Szeged University
Szeged Hungary


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


From owner-freebsd-current  Tue Dec 19 10:48:43 2000
From owner-freebsd-current@FreeBSD.ORG  Tue Dec 19 10:48:41 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from cae88-102-101.sc.rr.com (cae88-102-101.sc.rr.com [24.88.102.101])
	by hub.freebsd.org (Postfix) with ESMTP id BDCB937B400
	for <current@FreeBSD.ORG>; Tue, 19 Dec 2000 10:48:40 -0800 (PST)
Received: (from dmaddox@localhost)
	by cae88-102-101.sc.rr.com (8.11.1/8.11.1) id eBJIlxs01525;
	Tue, 19 Dec 2000 13:47:59 -0500 (EST)
	(envelope-from dmaddox)
Date: Tue, 19 Dec 2000 13:47:59 -0500
From: "Donald J . Maddox" <dmaddox@sc.rr.com>
To: Szilveszter Adam <sziszi@petra.hos.u-szeged.hu>
Cc: current@FreeBSD.ORG
Subject: Re: Interesting new messages in logs
Message-ID: <20001219134758.A1497@cae88-102-101.sc.rr.com>
Reply-To: dmaddox@sc.rr.com
Mail-Followup-To: Szilveszter Adam <sziszi@petra.hos.u-szeged.hu>,
	current@FreeBSD.ORG
References: <20001219132057.A1338@cae88-102-101.sc.rr.com> <20001219193349.E15002@petra.hos.u-szeged.hu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20001219193349.E15002@petra.hos.u-szeged.hu>; from sziszi@petra.hos.u-szeged.hu on Tue, Dec 19, 2000 at 07:33:49PM +0100
Return-Receipt-To: dmaddox@sc.rr.com
Sender: dmaddox@cae88-102-101.sc.rr.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, Dec 19, 2000 at 07:33:49PM +0100, Szilveszter Adam wrote:
> On Tue, Dec 19, 2000 at 01:20:57PM -0500, Donald J . Maddox wrote:
> > After my latest update, I am getting LOTS of the following in my logs:
> > 
> > Dec 19 12:21:04 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP ::0001:25 from ::0001:1286
> > Dec 19 12:24:08 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP ::0001:25 from ::0001:1299
> > Dec 19 12:27:13 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP ::0001:25 from ::0001:1308
> > Dec 19 12:39:28 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP ::0001:25 from ::0001:1336
> > 
> > Obviously, this machine is using log_in_vain, and it appears obvious
> > that these are local smtp transactions.  It is _not_ obvious, at
> > least to me, why they are now being logged as if port 25 was not
> > open.  Also, why the odd format in the addresses?
> 
> Key might be: IPv6.:-) (At least for the addresses.) Check your
> configuration if you are listening on port 25 for IPv6 or not...
> 
> That's off the top of my head though so yell at me if I am talking
> nonsense:-)

Nope, no nonsense, you're right on the money :)

In the previous kernel I didn't have IPV6 enabled, and in this one
it is enabled.

Thanks for helping clear this up for me :)


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


From owner-freebsd-current  Tue Dec 19 10:51:12 2000
From owner-freebsd-current@FreeBSD.ORG  Tue Dec 19 10:51:11 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16])
	by hub.freebsd.org (Postfix) with ESMTP id 9001C37B400
	for <current@FreeBSD.ORG>; Tue, 19 Dec 2000 10:51:09 -0800 (PST)
Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2])
	by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id NAA14078;
	Tue, 19 Dec 2000 13:51:04 -0500 (EST)
Message-Id: <200012191851.NAA14078@cs.rpi.edu>
To: dmaddox@sc.rr.com
Cc: current@FreeBSD.ORG
Subject: Re: Interesting new messages in logs 
In-Reply-To: Message from "Donald J . Maddox" <dmaddox@sc.rr.com> 
   of "Tue, 19 Dec 2000 13:20:57 EST." <20001219132057.A1338@cae88-102-101.sc.rr.com> 
Date: Tue, 19 Dec 2000 13:51:04 -0500
From: Hasan Azam Diwan <diwanh@cs.rpi.edu>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

To answer your first question, a port need not be open in order to receive 
connections. To answer your second, these appear to be IPv4 addresses 
encapsulated as IPv6 addresses. 
> Dec 19 12:21:04 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP 
> ::0001:25 from ::0001:1286
> Dec 19 12:24:08 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP 
> ::0001:25 from ::0001:1299
> Dec 19 12:27:13 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP 
> ::0001:25 from ::0001:1308
> Dec 19 12:39:28 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP 
> ::0001:25 from ::0001:1336
> Obviously, this machine is using log_in_vain, and it appears obvious
> that these are local smtp transactions.  It is _not_ obvious, at
> least to me, why they are now being logged as if port 25 was not
> open.  Also, why the odd format in the addresses?


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


From owner-freebsd-current  Tue Dec 19 10:55:18 2000
From owner-freebsd-current@FreeBSD.ORG  Tue Dec 19 10:55:16 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from field.videotron.net (field.videotron.net [205.151.222.108])
	by hub.freebsd.org (Postfix) with ESMTP id C28A037B400
	for <current@FreeBSD.ORG>; Tue, 19 Dec 2000 10:55:15 -0800 (PST)
Received: from modemcable213.3-201-24.mtl.mc.videotron.ca ([24.201.3.213])
 by field.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8)
 with ESMTP id <0G5T00G12WJYHF@field.videotron.net> for current@FreeBSD.ORG; Tue, 19 Dec 2000 13:55:10 -0500 (EST)
Date: Tue, 19 Dec 2000 13:56:02 -0500 (EST)
From: Bosko Milekic <bmilekic@technokratis.com>
Subject: Re: Network performance-problem
In-reply-to: <3A3F476A.9FA98FCC@hp.com>
To: Michael Class <michael_class@hp.com>
Cc: current@FreeBSD.ORG
Message-id: <Pine.BSF.4.21.0012191354110.8500-100000@jehovah.technokratis.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On Tue, 19 Dec 2000, Michael Class wrote:

> It seems that NewReno is switched on by default in current.
> Unfortunately switching off NewReno does not change the problem. In
> times of very high network-traffic I am still unable to use the network.
> The system does not even respond to a ping where as all other systems I
> have (HPUX 10.20, 11.0 and NT4) behave as expected: slow response-times,
> but still working and ping-able.

	What is your NMBCLUSTERS set to? And in cases of "high traffic," what
  does `netstat -m' show for number of clusters and mbufs "in use?" How
  much of mb_map (%) is in use? If any of these are relatively close to
  exhaustion, try increasing NMBCLUSTERS in your kernel configuration and
  rebuilding. 

> At home I am using this Laptop in a 100MB-Network and am able to almost
> saturate the link without any problems. Could it be that this is just
> happening for multicast-packets (that's what the high network-traffic
> is)?
> 
> Anything else I could check?
> 
> TIA
> 
> Michael 
> 
> 
> -- 
> ___________________________________________________________________________
> Michael Class                            E-Mail: michael_class@hp.com
> E-Business Solution Division             Phone:  +49 7031 14-3707
>                                          Fax:    +49 7031 14-4505
> ___________________________________________________________________________
> Hewlett-Packard GmbH, PO Box 1430, Mailstop ESD2, 71004 Boeblingen
> Managing Directors: Rainer Geissel (Chairman),Rainer Erlat, Heribert
>                     Schmitz, Hans-Jochen Lueckefett, Fritz Schuller
> Chairman of the Supervisory Board: Joerg Menno Harms
> Commercial register: Amtsgericht Boeblingen HRB 4081
> ___________________________________________________________________________
> 

  Cheers,
  Bosko Milekic
  bmilekic@technokratis.com




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


From owner-freebsd-current  Tue Dec 19 11: 4:19 2000
From owner-freebsd-current@FreeBSD.ORG  Tue Dec 19 11:04:16 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from cae88-102-101.sc.rr.com (cae88-102-101.sc.rr.com [24.88.102.101])
	by hub.freebsd.org (Postfix) with ESMTP id 993F537B400
	for <current@FreeBSD.ORG>; Tue, 19 Dec 2000 11:04:15 -0800 (PST)
Received: (from dmaddox@localhost)
	by cae88-102-101.sc.rr.com (8.11.1/8.11.1) id eBJJ4OL01638;
	Tue, 19 Dec 2000 14:04:24 -0500 (EST)
	(envelope-from dmaddox)
Date: Tue, 19 Dec 2000 14:04:24 -0500
From: "Donald J . Maddox" <dmaddox@sc.rr.com>
To: Hasan Azam Diwan <diwanh@cs.rpi.edu>
Cc: dmaddox@sc.rr.com, current@FreeBSD.ORG
Subject: Re: Interesting new messages in logs
Message-ID: <20001219140424.A1572@cae88-102-101.sc.rr.com>
Reply-To: dmaddox@sc.rr.com
Mail-Followup-To: Hasan Azam Diwan <diwanh@cs.rpi.edu>, dmaddox@sc.rr.com,
	current@FreeBSD.ORG
References: <dmaddox@sc.rr.com> <200012191851.NAA14078@cs.rpi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <200012191851.NAA14078@cs.rpi.edu>; from diwanh@cs.rpi.edu on Tue, Dec 19, 2000 at 01:51:04PM -0500
Return-Receipt-To: dmaddox@sc.rr.com
Sender: dmaddox@cae88-102-101.sc.rr.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

You're right that the answer to my question was IPV6 (I didn't have
it compiled into the previous kernel).  You're wrong that a port
need not be open to  receive connections.  You will note in the
log excerpt below that these are connection *attempts*, not actual
connections.

On Tue, Dec 19, 2000 at 01:51:04PM -0500, Hasan Azam Diwan wrote:
> To answer your first question, a port need not be open in order to receive 
> connections. To answer your second, these appear to be IPv4 addresses 
> encapsulated as IPv6 addresses. 
> > Dec 19 12:21:04 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP 
> > ::0001:25 from ::0001:1286
> > Dec 19 12:24:08 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP 
> > ::0001:25 from ::0001:1299
> > Dec 19 12:27:13 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP 
> > ::0001:25 from ::0001:1308
> > Dec 19 12:39:28 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP 
> > ::0001:25 from ::0001:1336
> > Obviously, this machine is using log_in_vain, and it appears obvious
> > that these are local smtp transactions.  It is _not_ obvious, at
> > least to me, why they are now being logged as if port 25 was not
> > open.  Also, why the odd format in the addresses?
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message


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


From owner-freebsd-current  Tue Dec 19 11:30:21 2000
From owner-freebsd-current@FreeBSD.ORG  Tue Dec 19 11:30:18 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from nettaxi.com (modem161.dock.net [207.113.51.18])
	by hub.freebsd.org (Postfix) with SMTP id A15E937B6A2
	for <current@freebsd.org>; Tue, 19 Dec 2000 11:30:17 -0800 (PST)
From: Benefitsall@nettaxi.com
Reply-To: Benefitsall@nettaxi.com
To: current@freebsd.org
Subject: Donation to your organization 121900
Message-Id: <20001219193017.A15E937B6A2@hub.freebsd.org>
Date: Tue, 19 Dec 2000 11:30:17 -0800 (PST)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Dear Friend  

Help your organization raise money in a painless way

Cash rebates of up to 30% from BenefitsAll become welcome donations to your organization when your members shop online with Lands End, Disney, Dell, Gap, Esprit and 300 plus retailers through our web site.

Widely endorsed, socially responsible site offers no obligation, free rebate program for members. See how easy it is for your charity to earn substantial cash back for every online, shopping purchase made.

To find out more information from BenefitsAll click on reply and we will contact you shortly. Please put "MORE INFO"  in the subject box. If you prefer call us toll free at  866 961 2468. Ask for customer service extension 1

To remove you from this list type " REMOVE"  in the subject box and click reply.



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


From owner-freebsd-current  Tue Dec 19 14:10:20 2000
From owner-freebsd-current@FreeBSD.ORG  Tue Dec 19 14:10:17 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from freebsd.netcom.com (freebsd.netcom.com [198.211.79.3])
	by hub.freebsd.org (Postfix) with ESMTP id 8E59137B402
	for <freebsd-current@freebsd.org>; Tue, 19 Dec 2000 14:10:16 -0800 (PST)
Received: (from bugs@localhost)
	by freebsd.netcom.com (8.8.8+Sun/8.8.8) id QAA28118
	for freebsd-current@freebsd.org; Tue, 19 Dec 2000 16:10:11 -0600 (CST)
From: Mark Hittinger <bugs@freebsd.netcom.com>
Message-Id: <200012192210.QAA28118@freebsd.netcom.com>
Subject: -current "almost" hanging after boot
To: freebsd-current@freebsd.org
Date: Tue, 19 Dec 2000 16:10:11 -0600 (CST)
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


I've had a problem with -current for a couple weeks that appeared to be a
boot hang at first glace.  I compiled the kernel with ddb and was able to
break into the debugger when things appeared to hang.  After the kernel
starts up /sbin/init the OS will pause for a second and then begin spewing
the microuptime() went backwards stuff.   The kernel isn't really hanging
it is just being really slow about some things.

A few months ago we had a problem with the XL driver where an UNLOCK had
been mistakenly coded as a LOCK.  The problem feels very simlar to that.

Does anyone have any hints for what to look at when I break in to the
debugger?   Is anyone else seeing this behavior?

Later

Mark Hittinger
Earthlink
bugs@freebsd.netcom.com


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


From owner-freebsd-current  Tue Dec 19 15: 8:17 2000
From owner-freebsd-current@FreeBSD.ORG  Tue Dec 19 15:08:14 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from clmboh1-smtp3.columbus.rr.com (unknown [65.24.0.112])
	by hub.freebsd.org (Postfix) with ESMTP
	id 6D02737B400; Tue, 19 Dec 2000 15:08:13 -0800 (PST)
Received: from zoomer (dzerkel@dhcp065-024-166-103.columbus.rr.com [65.24.166.103])
	by clmboh1-smtp3.columbus.rr.com (8.9.3/8.9.3) with SMTP id SAA29297;
	Tue, 19 Dec 2000 18:05:56 -0500 (EST)
From: "Danny J. Zerkel" <dzerkel@columbus.rr.com>
Organization: Zerkular Software
To: Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org>, roam@orbitel.bg
Subject: Re: dev/acpica/acpi.c - minor patch for cleaner poweroff
Date: Tue, 19 Dec 2000 18:07:59 -0500
X-Mailer: KMail [version 1.1.99]
Content-Type: text/plain;
  charset="us-ascii"
Cc: msmith@FreeBSD.ORG, current@FreeBSD.ORG
References: <20001218165732.A5418@ringworld.oblivion.bg> <20001220003605D.iwasaki@jp.FreeBSD.org>
In-Reply-To: <20001220003605D.iwasaki@jp.FreeBSD.org>
MIME-Version: 1.0
Message-Id: <00121918075900.00425@zoomer>
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

This patch works for me on a P2B-DS, previously I had to power off by
hand.

Thanks!

Danny

On Tuesday 19 December 2000 10:36, Mitsuru IWASAKI wrote:
> Hi,
>
> > I think you're the main maintainer of the ACPICA codebase (and yes, I
> > know that parts of it is imported from Intel).  Attached is a trivial
> > patch which makes for cleaner testing for RB_POWEROFF in
> > acpi_shutdown_final() - I've had various kernel/userland routines invoke
> > reboot sequences where the howto had more bits set than RB_POWEROFF, e.g.
> > RB_NOSYNC.  With this patch, shutdown -p works for me :)
>
> Thanks, this patch looks good.  I'll fix this soon.
> I'm sure mike will agree on it :-)
>
> > Thanks for all the work on ACPICA :)
> >
> > G'luck,
> > Peter
> >
> > PS. Please CC: me in replies as I'm not on -current.
> >
> > --
> > If I had finished this sentence,
> >
> > Index: acpi.c
> > ===================================================================
> > RCS file: /home/ncvs/src/sys/dev/acpica/acpi.c,v
> > retrieving revision 1.7
> > diff -u -r1.7 acpi.c
> > --- acpi.c	2000/12/12 14:20:27	1.7
> > +++ acpi.c	2000/12/18 14:55:43
> > @@ -657,7 +657,7 @@
> >  {
> >      ACPI_STATUS	status;
> >
> > -    if (howto == RB_POWEROFF) {
> > +    if (howto & RB_POWEROFF) {
> >  	printf("Power system off using ACPI...\n");
> >  	if ((status = AcpiSetSystemSleepState(ACPI_STATE_S5)) != AE_OK) {
> >  	    printf("ACPI power-off failed - %s\n", acpi_strerror(status));
> >
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-current" in the body of the message
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message

-- 
------------------
dzerkel@columbus.rr.com


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


From owner-freebsd-current  Tue Dec 19 15:10: 8 2000
From owner-freebsd-current@FreeBSD.ORG  Tue Dec 19 15:10:07 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252])
	by hub.freebsd.org (Postfix) with ESMTP id D4BC937B404
	for <current@freebsd.org>; Tue, 19 Dec 2000 15:10:03 -0800 (PST)
Received: (from uucp@localhost)
	by frmug.org (8.9.3/frmug-2.7/nospam) with UUCP id AAA02802
	for current@freebsd.org; Wed, 20 Dec 2000 00:09:56 +0100 (CET)
	(envelope-from roberto@keltia.freenix.fr)
Received: by keltia.freenix.fr (Postfix/TLS, from userid 101)
	id 1295D8810; Tue, 19 Dec 2000 21:56:36 +0100 (CET)
Date: Tue, 19 Dec 2000 21:56:36 +0100
From: Ollivier Robert <roberto@keltia.freenix.fr>
To: current@freebsd.org
Subject: Re: Interesting new messages in logs
Message-ID: <20001219215636.A49561@keltia.freenix.fr>
Mail-Followup-To: current@freebsd.org
References: <20001219132057.A1338@cae88-102-101.sc.rr.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <20001219132057.A1338@cae88-102-101.sc.rr.com>; from dmaddox@sc.rr.com on Tue, Dec 19, 2000 at 01:20:57PM -0500
X-Operating-System: FreeBSD 5.0-CURRENT K6-3D/266 & 2x PPro/200 SMP
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

According to Donald J . Maddox:
> open.  Also, why the odd format in the addresses?

Looks like some kind of IPv6 address...
-- 
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr
FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun  4 22:44:19 CEST 2000



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


From owner-freebsd-current  Tue Dec 19 15:19:34 2000
From owner-freebsd-current@FreeBSD.ORG  Tue Dec 19 15:19:32 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from cae88-102-101.sc.rr.com (cae88-102-101.sc.rr.com [24.88.102.101])
	by hub.freebsd.org (Postfix) with ESMTP id 13B3337B400
	for <current@FreeBSD.ORG>; Tue, 19 Dec 2000 15:19:32 -0800 (PST)
Received: (from dmaddox@localhost)
	by cae88-102-101.sc.rr.com (8.11.1/8.11.1) id eBJNJLV61767;
	Tue, 19 Dec 2000 18:19:21 -0500 (EST)
	(envelope-from dmaddox)
Date: Tue, 19 Dec 2000 18:19:20 -0500
From: "Donald J . Maddox" <dmaddox@sc.rr.com>
To: Ollivier Robert <roberto@keltia.freenix.fr>
Cc: current@FreeBSD.ORG
Subject: Re: Interesting new messages in logs
Message-ID: <20001219181920.B61697@cae88-102-101.sc.rr.com>
Reply-To: dmaddox@sc.rr.com
Mail-Followup-To: Ollivier Robert <roberto@keltia.freenix.fr>,
	current@FreeBSD.ORG
References: <20001219132057.A1338@cae88-102-101.sc.rr.com> <20001219215636.A49561@keltia.freenix.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20001219215636.A49561@keltia.freenix.fr>; from roberto@keltia.freenix.fr on Tue, Dec 19, 2000 at 09:56:36PM +0100
Return-Receipt-To: dmaddox@sc.rr.com
Sender: dmaddox@cae88-102-101.sc.rr.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, Dec 19, 2000 at 09:56:36PM +0100, Ollivier Robert wrote:
> According to Donald J . Maddox:
> > open.  Also, why the odd format in the addresses?
> 
> Looks like some kind of IPv6 address...

You're right.  I compiled the new kernel with IPV6 enabled.  I
didn't have IPV6 in my previous kernel...  Thanks :)


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


From owner-freebsd-current  Tue Dec 19 15:27:32 2000
From owner-freebsd-current@FreeBSD.ORG  Tue Dec 19 15:27:28 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from cae88-102-101.sc.rr.com (cae88-102-101.sc.rr.com [24.88.102.101])
	by hub.freebsd.org (Postfix) with ESMTP id 2C87837B400
	for <current@FreeBSD.ORG>; Tue, 19 Dec 2000 15:27:28 -0800 (PST)
Received: (from dmaddox@localhost)
	by cae88-102-101.sc.rr.com (8.11.1/8.11.1) id eBJNRdI61830
	for current@FreeBSD.ORG; Tue, 19 Dec 2000 18:27:39 -0500 (EST)
	(envelope-from dmaddox)
Date: Tue, 19 Dec 2000 18:27:39 -0500
From: "Donald J . Maddox" <dmaddox@sc.rr.com>
To: current@FreeBSD.ORG
Subject: No cable modems??
Message-ID: <20001219182739.C61697@cae88-102-101.sc.rr.com>
Reply-To: dmaddox@sc.rr.com
Mail-Followup-To: current@FreeBSD.ORG
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="opJtzjQTFsWo+cga"
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Return-Receipt-To: dmaddox@sc.rr.com
Sender: dmaddox@cae88-102-101.sc.rr.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


--opJtzjQTFsWo+cga
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Sorry to post this to -current, but (as should be obvious from
the below) it's the only way I can get Ollivier to see it :(

Why are you (or your ISP) refusing to accept mail from people
with cable modems?  Enquiring minds want to know... ;-)

--opJtzjQTFsWo+cga
Content-Type: message/rfc822
Content-Disposition: inline

Return-Path: <MAILER-DAEMON>
Received: from localhost (localhost)
	by cae88-102-101.sc.rr.com (8.11.1/8.11.1) id eBJNJiU61769;
	Tue, 19 Dec 2000 18:19:44 -0500 (EST)
	(envelope-from MAILER-DAEMON)
Date: Tue, 19 Dec 2000 18:19:44 -0500 (EST)
From: Mail Delivery Subsystem <MAILER-DAEMON>
Message-Id: <200012192319.eBJNJiU61769@cae88-102-101.sc.rr.com>
To: dmaddox
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
	boundary="eBJNJiU61769.977267984/cae88-102-101.sc.rr.com"
Subject: Returned mail: see transcript for details
Auto-Submitted: auto-generated (failure)

This is a MIME-encapsulated message

--eBJNJiU61769.977267984/cae88-102-101.sc.rr.com

The original message was received at Tue, 19 Dec 2000 18:19:21 -0500 (EST)
from dmaddox@localhost

   ----- The following addresses had permanent fatal errors -----
roberto@keltia.freenix.fr
    (reason: 550 no cable modems here)

   ----- Transcript of session follows -----
... while talking to frmug.org.:
>>> MAIL From:<dmaddox@cae88-102-101.sc.rr.com>
<<< 550 no cable modems here
554 5.0.0 roberto@keltia.freenix.fr... Service unavailable

--eBJNJiU61769.977267984/cae88-102-101.sc.rr.com
Content-Type: message/delivery-status

Reporting-MTA: dns; cae88-102-101.sc.rr.com
Arrival-Date: Tue, 19 Dec 2000 18:19:21 -0500 (EST)

Final-Recipient: RFC822; roberto@keltia.freenix.fr
Action: failed
Status: 5.0.0
Diagnostic-Code: SMTP; 550 no cable modems here
Last-Attempt-Date: Tue, 19 Dec 2000 18:19:38 -0500 (EST)

--eBJNJiU61769.977267984/cae88-102-101.sc.rr.com
Content-Type: message/rfc822

Return-Path: <dmaddox>
Received: (from dmaddox@localhost)
	by cae88-102-101.sc.rr.com (8.11.1/8.11.1) id eBJNJLV61767;
	Tue, 19 Dec 2000 18:19:21 -0500 (EST)
	(envelope-from dmaddox)
Date: Tue, 19 Dec 2000 18:19:20 -0500
From: "Donald J . Maddox" <dmaddox@sc.rr.com>
To: Ollivier Robert <roberto@keltia.freenix.fr>
Cc: current@FreeBSD.ORG
Subject: Re: Interesting new messages in logs
Message-ID: <20001219181920.B61697@cae88-102-101.sc.rr.com>
Reply-To: dmaddox@sc.rr.com
Mail-Followup-To: Ollivier Robert <roberto@keltia.freenix.fr>,
	current@FreeBSD.ORG
References: <20001219132057.A1338@cae88-102-101.sc.rr.com> <20001219215636.A49561@keltia.freenix.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20001219215636.A49561@keltia.freenix.fr>; from roberto@keltia.freenix.fr on Tue, Dec 19, 2000 at 09:56:36PM +0100
Return-Receipt-To: dmaddox@sc.rr.com

On Tue, Dec 19, 2000 at 09:56:36PM +0100, Ollivier Robert wrote:
> According to Donald J . Maddox:
> > open.  Also, why the odd format in the addresses?
> 
> Looks like some kind of IPv6 address...

You're right.  I compiled the new kernel with IPV6 enabled.  I
didn't have IPV6 in my previous kernel...  Thanks :)

--eBJNJiU61769.977267984/cae88-102-101.sc.rr.com--


--opJtzjQTFsWo+cga--


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


From owner-freebsd-current  Tue Dec 19 21:18:24 2000
From owner-freebsd-current@FreeBSD.ORG  Tue Dec 19 21:18:22 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from ns5.pacific.net.au (ns5.pacific.net.au [203.143.252.30])
	by hub.freebsd.org (Postfix) with ESMTP id 5A85137B404
	for <current@freebsd.org>; Tue, 19 Dec 2000 21:18:20 -0800 (PST)
Received: from dungeon.home (ppp101.dyn249.pacific.net.au [203.143.249.101])
	by ns5.pacific.net.au (8.9.0/8.9.1) with ESMTP id QAA02396;
	Wed, 20 Dec 2000 16:18:16 +1100 (EST)
Received: from dungeon.home (localhost [127.0.0.1])
	by dungeon.home (8.11.1/8.9.3) with ESMTP id eBK5IsB15659;
	Wed, 20 Dec 2000 15:18:54 +1000 (EST)
	(envelope-from mckay)
Message-Id: <200012200518.eBK5IsB15659@dungeon.home>
To: "Donald J . Maddox" <dmaddox@sc.rr.com>
Cc: current@freebsd.org, mckay@thehub.com.au
Subject: Re: No cable modems?? 
References: <20001219182739.C61697@cae88-102-101.sc.rr.com>
In-Reply-To: <20001219182739.C61697@cae88-102-101.sc.rr.com>
    from "Donald J . Maddox" at "Tue, 19 Dec 2000 23:27:39 +0000"
Date: Wed, 20 Dec 2000 15:18:54 +1000
From: Stephen McKay <mckay@thehub.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tuesday, 19th December 2000, "Donald J . Maddox" wrote:

>Why are you (or your ISP) refusing to accept mail from people
>with cable modems?  Enquiring minds want to know... ;-)

>   ----- Transcript of session follows -----
>... while talking to frmug.org.:
>>>> MAIL From:<dmaddox@cae88-102-101.sc.rr.com>
><<< 550 no cable modems here
>554 5.0.0 roberto@keltia.freenix.fr... Service unavailable

It's a spam reduction move.  I'm surprised hub.freebsd.org accepts your
mail!  You should funnel your mail through your ISP's central mail hub.

Followups to -chat, I think.

Stephen.


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


From owner-freebsd-current  Tue Dec 19 22:19:54 2000
From owner-freebsd-current@FreeBSD.ORG  Tue Dec 19 22:19:53 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from gratis.grondar.za (grouter.grondar.za [196.7.18.65])
	by hub.freebsd.org (Postfix) with ESMTP id C17FC37B400
	for <current@FreeBSD.ORG>; Tue, 19 Dec 2000 22:19:49 -0800 (PST)
Received: from grondar.za (root@gratis.grondar.za [196.7.18.133])
	by gratis.grondar.za (8.11.1/8.11.1) with ESMTP id eBK6JSk78542;
	Wed, 20 Dec 2000 08:19:31 +0200 (SAST)
	(envelope-from mark@grondar.za)
Message-Id: <200012200619.eBK6JSk78542@gratis.grondar.za>
To: dmaddox@sc.rr.com
Cc: current@FreeBSD.ORG
Subject: Re: No cable modems?? 
References: <20001219182739.C61697@cae88-102-101.sc.rr.com> 
In-Reply-To: <20001219182739.C61697@cae88-102-101.sc.rr.com> ; from "Donald J . Maddox" <dmaddox@sc.rr.com>  "Tue, 19 Dec 2000 18:27:39 EST."
Date: Wed, 20 Dec 2000 08:19:34 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

This is offtopic! If you need to discuss it, please take it to
-chat.

<OFFTOPIC>
> Sorry to post this to -current, but (as should be obvious from
> the below) it's the only way I can get Ollivier to see it :(
> 
> Why are you (or your ISP) refusing to accept mail from people
> with cable modems?  Enquiring minds want to know... ;-)

:

>    ----- The following addresses had permanent fatal errors -----
> roberto@keltia.freenix.fr
>     (reason: 550 no cable modems here)

Many ISP's consider cable modem pools and DSL pools as the same sort
of "animal" as dialup users.

Very many ISPs will refuse to receive mail from all three of those
user-classes, because of the "direct-to-MX" spam issue. The solution
is to use your ISP's SMTP "smarthost" for your mail.

See http://mail-abuse.org/dul/
</OFFTOPIC>

M
--
Mark Murray
Warning: this .sig is umop ap!sdn


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


From owner-freebsd-current  Tue Dec 19 22:28: 8 2000
From owner-freebsd-current@FreeBSD.ORG  Tue Dec 19 22:28:05 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from cae88-102-101.sc.rr.com (cae88-102-101.sc.rr.com [24.88.102.101])
	by hub.freebsd.org (Postfix) with ESMTP id 7CF0A37B400
	for <current@FreeBSD.ORG>; Tue, 19 Dec 2000 22:28:04 -0800 (PST)
Received: (from dmaddox@localhost)
	by cae88-102-101.sc.rr.com (8.11.1/8.11.1) id eBK6Rw101632;
	Wed, 20 Dec 2000 01:27:58 -0500 (EST)
	(envelope-from dmaddox)
Date: Wed, 20 Dec 2000 01:27:58 -0500
From: "Donald J . Maddox" <dmaddox@sc.rr.com>
To: Mark Murray <mark@grondar.za>
Cc: current@FreeBSD.ORG
Subject: Re: No cable modems??
Message-ID: <20001220012758.A1606@cae88-102-101.sc.rr.com>
Reply-To: dmaddox@sc.rr.com
Mail-Followup-To: Mark Murray <mark@grondar.za>, current@FreeBSD.ORG
References: <20001219182739.C61697@cae88-102-101.sc.rr.com> <200012200619.eBK6JSk78542@gratis.grondar.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <200012200619.eBK6JSk78542@gratis.grondar.za>; from mark@grondar.za on Wed, Dec 20, 2000 at 08:19:34AM +0200
Return-Receipt-To: dmaddox@sc.rr.com
Sender: dmaddox@cae88-102-101.sc.rr.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I apologized in advance, and I do again, but I have no way of
knowing if Ollivier is subscribed to -chat.  Thanks for
understanding.  Further discssion has been moved to chat.

On Wed, Dec 20, 2000 at 08:19:34AM +0200, Mark Murray wrote:
> This is offtopic! If you need to discuss it, please take it to
> -chat.
> 
> <OFFTOPIC>
> > Sorry to post this to -current, but (as should be obvious from
> > the below) it's the only way I can get Ollivier to see it :(
> > 
> > Why are you (or your ISP) refusing to accept mail from people
> > with cable modems?  Enquiring minds want to know... ;-)
> 
> :
> 
> >    ----- The following addresses had permanent fatal errors -----
> > roberto@keltia.freenix.fr
> >     (reason: 550 no cable modems here)
> 
> Many ISP's consider cable modem pools and DSL pools as the same sort
> of "animal" as dialup users.
> 
> Very many ISPs will refuse to receive mail from all three of those
> user-classes, because of the "direct-to-MX" spam issue. The solution
> is to use your ISP's SMTP "smarthost" for your mail.
> 
> See http://mail-abuse.org/dul/
> </OFFTOPIC>
> 
> M
> --
> Mark Murray
> Warning: this .sig is umop ap!sdn


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


From owner-freebsd-current  Wed Dec 20  0:51:18 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 00:51:15 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38])
	by hub.freebsd.org (Postfix) with ESMTP id 16AC237B402
	for <current@freebsd.org>; Wed, 20 Dec 2000 00:51:10 -0800 (PST)
Received: from dragon.nuxi.com (Ipittythefoolthattrustsident@trang.nuxi.com [209.152.133.57])
	by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id AAA12195;
	Wed, 20 Dec 2000 00:51:09 -0800 (PST)
	(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
	by dragon.nuxi.com (8.11.1/8.11.1) id eBK8p6H42255;
	Wed, 20 Dec 2000 00:51:06 -0800 (PST)
	(envelope-from obrien)
Date: Wed, 20 Dec 2000 00:51:06 -0800
From: "David O'Brien" <obrien@freebsd.org>
To: Stephen McKay <mckay@thehub.com.au>
Cc: "Donald J . Maddox" <dmaddox@sc.rr.com>, current@freebsd.org
Subject: Re: Is compatibility for old aout binaries broken?
Message-ID: <20001220005106.F41741@dragon.nuxi.com>
Reply-To: obrien@freebsd.org
References: <20001216161756.A6370@cae88-102-101.sc.rr.com> <200012171658.eBHGwGW24109@dungeon.home>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <200012171658.eBHGwGW24109@dungeon.home>; from mckay@thehub.com.au on Mon, Dec 18, 2000 at 02:58:16AM +1000
X-Operating-System: FreeBSD 5.0-CURRENT
Organization: The NUXI BSD group
X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3  90 76 5D 69 58 D9 98 7A
X-Pgp-Rsa-Keyid: 1024/34F9F9D5
Sender: obrien@NUXI.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, Dec 18, 2000 at 02:58:16AM +1000, Stephen McKay wrote:
> >The other day, on a whim, I decided to try running an old binary
> >of SimCity (the same one found in the 'commerce' directory on
> >many FBSD cds), and it failed in a odd way...

Does anyone have any old a.out binaries other than SimCity that they have
problems with?  I've installed the SimCity package, compat20 and compat21
dists, but cannot get it to run:

    Starting SimCity ... 
    SimCity Classic - UNIX / Tcl & Tk Toolkit version 3.6b - Mattes
    Adding a player on dragon:0.0 ...
    Display Visual = truecolor
    Display Depth = 24
    SimCity can't find an 8 bit color or 1 bit monochrome display on
    "dragon:0.0".
    SimCity: error in TCL code: bad window path name ".head0"

-- 
-- David  (obrien@FreeBSD.org)
          GNU is Not Unix / Linux Is Not UniX


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


From owner-freebsd-current  Wed Dec 20  0:56:58 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 00:56:56 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mail7.sc.rr.com (fe7.southeast.rr.com [24.93.67.54])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5B54137B400; Wed, 20 Dec 2000 00:56:56 -0800 (PST)
Received: from sc.rr.com ([24.88.102.101]) by mail7.sc.rr.com  with Microsoft SMTPSVC(5.5.1877.537.53);
	 Wed, 20 Dec 2000 03:56:53 -0500
Received: (from dmaddox@localhost)
	by sc.rr.com (8.11.1/8.11.1) id eBK8v7g03934;
	Wed, 20 Dec 2000 03:57:07 -0500 (EST)
	(envelope-from dmaddox)
Date: Wed, 20 Dec 2000 03:57:07 -0500
From: "Donald J . Maddox" <dmaddox@sc.rr.com>
To: "David O'Brien" <obrien@freebsd.org>
Cc: Stephen McKay <mckay@thehub.com.au>,
	"Donald J . Maddox" <dmaddox@sc.rr.com>, current@freebsd.org
Subject: Re: Is compatibility for old aout binaries broken?
Message-ID: <20001220035707.B3783@cae88-102-101.sc.rr.com>
Reply-To: dmaddox@sc.rr.com
Mail-Followup-To: David O'Brien <obrien@freebsd.org>,
	Stephen McKay <mckay@thehub.com.au>,
	"Donald J . Maddox" <dmaddox@sc.rr.com>, current@freebsd.org
References: <20001216161756.A6370@cae88-102-101.sc.rr.com> <200012171658.eBHGwGW24109@dungeon.home> <20001220005106.F41741@dragon.nuxi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20001220005106.F41741@dragon.nuxi.com>; from obrien@freebsd.org on Wed, Dec 20, 2000 at 12:51:06AM -0800
Return-Receipt-To: dmaddox@sc.rr.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Looks like you got a lot farther than I did with it...  Are you
sure you don't have an old aout ld.so on that machine?  Here's
what I get:

>dmaddox> SimCity
Starting SimCity ... 
SimCity Classic - UNIX / Tcl & Tk Toolkit version 3.6b - Mattes
/usr/libexec/ld.so: Undefined symbol "___error" called from sim:/usr/X11R6/lib/aout/libX11.so.6.1 at 0x20160644
>dmaddox> 

BTW - That 'commerce' directory has more old aout binaries in
it I bet...

Also, it looks to me like SimCity would probably run just
fine for you if you started X on an 8-bit display...

On Wed, Dec 20, 2000 at 12:51:06AM -0800, David O'Brien wrote:
> On Mon, Dec 18, 2000 at 02:58:16AM +1000, Stephen McKay wrote:
> > >The other day, on a whim, I decided to try running an old binary
> > >of SimCity (the same one found in the 'commerce' directory on
> > >many FBSD cds), and it failed in a odd way...
> 
> Does anyone have any old a.out binaries other than SimCity that they have
> problems with?  I've installed the SimCity package, compat20 and compat21
> dists, but cannot get it to run:
> 
>     Starting SimCity ... 
>     SimCity Classic - UNIX / Tcl & Tk Toolkit version 3.6b - Mattes
>     Adding a player on dragon:0.0 ...
>     Display Visual = truecolor
>     Display Depth = 24
>     SimCity can't find an 8 bit color or 1 bit monochrome display on
>     "dragon:0.0".
>     SimCity: error in TCL code: bad window path name ".head0"
> 
> -- 
> -- David  (obrien@FreeBSD.org)
>           GNU is Not Unix / Linux Is Not UniX


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


From owner-freebsd-current  Wed Dec 20  1:43: 7 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 01:43:05 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38])
	by hub.freebsd.org (Postfix) with ESMTP id 200C037B400
	for <current@freebsd.org>; Wed, 20 Dec 2000 01:43:04 -0800 (PST)
Received: from dragon.nuxi.com (Ipittythefoolthattrustsident@trang.nuxi.com [209.152.133.57])
	by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id BAA12340;
	Wed, 20 Dec 2000 01:43:02 -0800 (PST)
	(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
	by dragon.nuxi.com (8.11.1/8.11.1) id eBK9h0S42653;
	Wed, 20 Dec 2000 01:43:00 -0800 (PST)
	(envelope-from obrien)
Date: Wed, 20 Dec 2000 01:42:59 -0800
From: "David O'Brien" <obrien@freebsd.org>
To: Stephen McKay <mckay@thehub.com.au>
Cc: "Donald J . Maddox" <dmaddox@sc.rr.com>, current@freebsd.org
Subject: Re: Is compatibility for old aout binaries broken?
Message-ID: <20001220014259.G41741@dragon.nuxi.com>
Reply-To: obrien@freebsd.org
References: <20001216161756.A6370@cae88-102-101.sc.rr.com> <200012171658.eBHGwGW24109@dungeon.home>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <200012171658.eBHGwGW24109@dungeon.home>; from mckay@thehub.com.au on Mon, Dec 18, 2000 at 02:58:16AM +1000
X-Operating-System: FreeBSD 5.0-CURRENT
Organization: The NUXI BSD group
X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3  90 76 5D 69 58 D9 98 7A
X-Pgp-Rsa-Keyid: 1024/34F9F9D5
Sender: obrien@NUXI.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, Dec 18, 2000 at 02:58:16AM +1000, Stephen McKay wrote:
> This has been broken for new users for some time. :-(  Those of us
> upgrading from source have been immune to this problem, because we
> retain the old a.out ld.so binary.
> 
> >/usr/libexec/ld.so: Undefined symbol "___error" called from
> >sim:/usr/X11R6/lib /aout/libX11.so.6.1 at 0x20160644
>
> When errno became a function that returns a pointer (previously it was
> a simple integer variable), recompiled libraries became incompatable with
> old binaries.  So, I hacked the a.out loader (ld.so).  The fix was in 3.0.
> Well, Nate called it a horrible hack, so maybe I should say "the hack was
> in 3.0".

src/lib/libc/sys/__error.c suggests this was the case for 2.2.7+.

What is out of sync is the X11 a.out libs.  They are probably built on a
2.2.7 or 2.2.8 box, thus they refer to `___error' vs. `errno'.  These
libs are wrong for the SimCity binary.  They are a.out yes, but not
proper for compat20 use.  Since SimCity needs `libgcc.so.261', I'll
assume it was built that long ago.

The problem isn't as much ld.so, as it should match the libc.so, et.al.
you are using from the compat2[01] dist (needed to satisfy ``ldd
lib/SimCity/res/sim'').  And `ld.so' and the shared libs would be
consistent on the system the a.out program was built on.

What I would feel most comfortable with, is doing a MFC to RELENG_2_2 of
the rtld-aout changes since then, building a new `ld.so' and putting that
in the compat2? dists.  Problem is I don't have access to a 2.2-STABLE
box.


> I poked about with my old FreeBSD CD collection and found that
> version 3.0 through 3.2 have a fully functioning (fully hack enabled)
> ld.so, but an older binary has been substituted in 3.3 and onward,
> including 4.0 and 4.1, and most likely 4.2 also.

Are you sure?  src/lib/compat/compat2[012]/ld.so.gz.uu are all at
rev 1.1.  So there has been no change to them over the lifetime of their
existence.  All three are identical -- having the same MD5 checksum.
Well, looking at the release tags compat22/ld.so was in 3.2.
compat2[01]/ld.so was added for 3.3.

> I can only guess that some anonymous release engineer (nobody we know :-)
> picked the wrong CD at some point to get the master copy of ld.so once
> it stopped compiling.  (Or at least stopped being easily compiled.)

Not quite.  I seem to remember that JKH was makeing a tarball of a.out
libs from what ever was on his box at the time (thus probably the last
a.out ld.so just before E-day on 3-CURRENT).  When I committed the
compat2? bits, I took ld.so from a 2.2.x release as this is the compat2?
dist, not compat3.aout dist.  Which is what you're suggesting should have
been done.

-- 
-- David  (obrien@FreeBSD.org)
          GNU is Not Unix / Linux Is Not UniX


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


From owner-freebsd-current  Wed Dec 20  1:50:41 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 01:50:38 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mail7.sc.rr.com (fe7.southeast.rr.com [24.93.67.54])
	by hub.freebsd.org (Postfix) with ESMTP
	id 09A3C37B400; Wed, 20 Dec 2000 01:50:38 -0800 (PST)
Received: from sc.rr.com ([24.88.102.101]) by mail7.sc.rr.com  with Microsoft SMTPSVC(5.5.1877.537.53);
	 Wed, 20 Dec 2000 04:50:34 -0500
Received: (from dmaddox@localhost)
	by sc.rr.com (8.11.1/8.11.1) id eBK9omT04531;
	Wed, 20 Dec 2000 04:50:48 -0500 (EST)
	(envelope-from dmaddox)
Date: Wed, 20 Dec 2000 04:50:48 -0500
From: "Donald J . Maddox" <dmaddox@sc.rr.com>
To: "David O'Brien" <obrien@freebsd.org>
Cc: Stephen McKay <mckay@thehub.com.au>,
	"Donald J . Maddox" <dmaddox@sc.rr.com>, current@freebsd.org
Subject: Re: Is compatibility for old aout binaries broken?
Message-ID: <20001220045048.A4495@cae88-102-101.sc.rr.com>
Reply-To: dmaddox@sc.rr.com
Mail-Followup-To: David O'Brien <obrien@freebsd.org>,
	Stephen McKay <mckay@thehub.com.au>,
	"Donald J . Maddox" <dmaddox@sc.rr.com>, current@freebsd.org
References: <20001216161756.A6370@cae88-102-101.sc.rr.com> <200012171658.eBHGwGW24109@dungeon.home> <20001220014259.G41741@dragon.nuxi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20001220014259.G41741@dragon.nuxi.com>; from obrien@freebsd.org on Wed, Dec 20, 2000 at 01:42:59AM -0800
Return-Receipt-To: dmaddox@sc.rr.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Actually, the aout libs I am using when I get the ___error undefined
are the ones from the XFree86-3.3.6 distribution, compiled for 
FreeBSD 3.x.  Originally I was using the aout X libs I built myself
when building the XFree86-3.3.6 port.  Using those, I still got an
undefined symbol, but it wasn't ___error, and I don't remember
exactly what it was, just that it started with 3 underscores too.

On Wed, Dec 20, 2000 at 01:42:59AM -0800, David O'Brien wrote:
> 
> src/lib/libc/sys/__error.c suggests this was the case for 2.2.7+.
> 
> What is out of sync is the X11 a.out libs.  They are probably built on a
> 2.2.7 or 2.2.8 box, thus they refer to `___error' vs. `errno'.  These
> libs are wrong for the SimCity binary.  They are a.out yes, but not
> proper for compat20 use.  Since SimCity needs `libgcc.so.261', I'll
> assume it was built that long ago.
> 
> The problem isn't as much ld.so, as it should match the libc.so, et.al.
> you are using from the compat2[01] dist (needed to satisfy ``ldd
> lib/SimCity/res/sim'').  And `ld.so' and the shared libs would be
> consistent on the system the a.out program was built on.
> 
> What I would feel most comfortable with, is doing a MFC to RELENG_2_2 of
> the rtld-aout changes since then, building a new `ld.so' and putting that
> in the compat2? dists.  Problem is I don't have access to a 2.2-STABLE
> box.
> 
> 
> > I poked about with my old FreeBSD CD collection and found that
> > version 3.0 through 3.2 have a fully functioning (fully hack enabled)
> > ld.so, but an older binary has been substituted in 3.3 and onward,
> > including 4.0 and 4.1, and most likely 4.2 also.
> 
> Are you sure?  src/lib/compat/compat2[012]/ld.so.gz.uu are all at
> rev 1.1.  So there has been no change to them over the lifetime of their
> existence.  All three are identical -- having the same MD5 checksum.
> Well, looking at the release tags compat22/ld.so was in 3.2.
> compat2[01]/ld.so was added for 3.3.
> 
> > I can only guess that some anonymous release engineer (nobody we know :-)
> > picked the wrong CD at some point to get the master copy of ld.so once
> > it stopped compiling.  (Or at least stopped being easily compiled.)
> 
> Not quite.  I seem to remember that JKH was makeing a tarball of a.out
> libs from what ever was on his box at the time (thus probably the last
> a.out ld.so just before E-day on 3-CURRENT).  When I committed the
> compat2? bits, I took ld.so from a 2.2.x release as this is the compat2?
> dist, not compat3.aout dist.  Which is what you're suggesting should have
> been done.
> 
> -- 
> -- David  (obrien@FreeBSD.org)
>           GNU is Not Unix / Linux Is Not UniX
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message


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


From owner-freebsd-current  Wed Dec 20  1:52:33 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 01:52:31 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38])
	by hub.freebsd.org (Postfix) with ESMTP id C075837B400
	for <current@freebsd.org>; Wed, 20 Dec 2000 01:52:30 -0800 (PST)
Received: from dragon.nuxi.com (Ipittythefoolthattrustsident@trang.nuxi.com [209.152.133.57])
	by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id BAA12359;
	Wed, 20 Dec 2000 01:52:29 -0800 (PST)
	(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
	by dragon.nuxi.com (8.11.1/8.11.1) id eBK9qNU42713;
	Wed, 20 Dec 2000 01:52:23 -0800 (PST)
	(envelope-from obrien)
Date: Wed, 20 Dec 2000 01:52:23 -0800
From: "David O'Brien" <obrien@freebsd.org>
To: "Donald J . Maddox" <dmaddox@sc.rr.com>
Cc: Stephen McKay <mckay@thehub.com.au>, current@freebsd.org
Subject: Re: Is compatibility for old aout binaries broken?
Message-ID: <20001220015223.H41741@dragon.nuxi.com>
Reply-To: freebsd-current@freebsd.org
References: <20001216161756.A6370@cae88-102-101.sc.rr.com> <200012171658.eBHGwGW24109@dungeon.home> <20001220005106.F41741@dragon.nuxi.com> <20001220035707.B3783@cae88-102-101.sc.rr.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20001220035707.B3783@cae88-102-101.sc.rr.com>; from dmaddox@sc.rr.com on Wed, Dec 20, 2000 at 03:57:07AM -0500
X-Operating-System: FreeBSD 5.0-CURRENT
Organization: The NUXI BSD group
X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3  90 76 5D 69 58 D9 98 7A
X-Pgp-Rsa-Keyid: 1024/34F9F9D5
Sender: obrien@NUXI.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Dec 20, 2000 at 03:57:07AM -0500, Donald J . Maddox wrote:
> Looks like you got a lot farther than I did with it...  Are you
> sure you don't have an old aout ld.so on that machine?

Nope.  This is a box that was a virgin install of 5-CURRENT a month ago.
I had to install the compat20 and compat21 dists, along with doing a
``pkg_add -r XFree86-aoutlibs''.  The Tk is 8.0.5.

> Here's what I get:
> 
> >dmaddox> SimCity
> Starting SimCity ... 
> SimCity Classic - UNIX / Tcl & Tk Toolkit version 3.6b - Mattes
> /usr/libexec/ld.so: Undefined symbol "___error" called from sim:/usr/X11R6/lib/aout/libX11.so.6.1 at 0x20160644

Actually you're probably getting farther than I am.  I believe I'm
bombing so early in starting Tk, I'm not really getting to the point you
are.  What does `ldd /usr/local/lib/SimCity/res/sim'' report?

> Also, it looks to me like SimCity would probably run just
> fine for you if you started X on an 8-bit display...

Maybe, but I'm not going to dink with my X server config. ;-)
Mabye I'll try to find another box to try this on.
 
-- 
-- David  (obrien@FreeBSD.org)
          GNU is Not Unix / Linux Is Not UniX


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


From owner-freebsd-current  Wed Dec 20  2: 8: 7 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 02:08:06 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5])
	by hub.freebsd.org (Postfix) with ESMTP id 37EE737B402
	for <freebsd-current@FreeBSD.ORG>; Wed, 20 Dec 2000 02:07:57 -0800 (PST)
Received: from C992631-A.pinol1.sfba.home.com (C992631-A.pinol1.sfba.home.com [24.12.58.155])
	by shale.csir.co.za (8.9.3/8.9.3) with ESMTP id MAA71988
	for <freebsd-current@FreeBSD.ORG>; Wed, 20 Dec 2000 12:07:38 +0200 (SAT)
	(envelope-from reg@shale.csir.co.za)
Received: (from reg@localhost)
	by C992631-A.pinol1.sfba.home.com (8.11.0/8.11.0) id eBKA5Kb40501
	for freebsd-current@FreeBSD.ORG; Wed, 20 Dec 2000 02:05:20 -0800 (PST)
	(envelope-from reg)
Date: Wed, 20 Dec 2000 02:05:20 -0800
From: Jeremy Lea <reg@FreeBSD.ORG>
To: freebsd-current@FreeBSD.ORG
Subject: Re: Is compatibility for old aout binaries broken?
Message-ID: <20001220020520.P79112@shale.csir.co.za>
Mail-Followup-To: Jeremy Lea <reg@FreeBSD.org>, freebsd-current@FreeBSD.ORG
References: <20001216161756.A6370@cae88-102-101.sc.rr.com> <200012171658.eBHGwGW24109@dungeon.home> <20001220005106.F41741@dragon.nuxi.com> <20001220035707.B3783@cae88-102-101.sc.rr.com> <20001220015223.H41741@dragon.nuxi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20001220015223.H41741@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Wed, Dec 20, 2000 at 01:52:23AM -0800
Sender: reg@shale.csir.co.za
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

On Wed, Dec 20, 2000 at 01:52:23AM -0800, David O'Brien wrote:
> Nope.  This is a box that was a virgin install of 5-CURRENT a month ago.
> I had to install the compat20 and compat21 dists, along with doing a
> ``pkg_add -r XFree86-aoutlibs''.  The Tk is 8.0.5.

The XFree86-aoutlibs are especially from XFree86-3.3.3.  This was
because of unstable behaviour from Netscape with later aout libs.

They are obtained from:
ftp://ftp.xfree86.org/pub/XFree86/3.3.3/binaries/FreeBSD-2.2.x/Xbin.tgz

Regards,
 -Jeremy

-- 
FreeBSD - Because the best things in life are free...
                                           http://www.freebsd.org/


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


From owner-freebsd-current  Wed Dec 20  2: 9:49 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 02:09:44 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mail5.sc.rr.com (fe5.southeast.rr.com [24.93.67.52])
	by hub.freebsd.org (Postfix) with ESMTP
	id 731F537B402; Wed, 20 Dec 2000 02:09:44 -0800 (PST)
Received: from sc.rr.com ([24.88.102.101]) by mail5.sc.rr.com  with Microsoft SMTPSVC(5.5.1877.537.53);
	 Wed, 20 Dec 2000 05:09:32 -0500
Received: (from dmaddox@localhost)
	by sc.rr.com (8.11.1/8.11.1) id eBKA9jG04619;
	Wed, 20 Dec 2000 05:09:45 -0500 (EST)
	(envelope-from dmaddox)
Date: Wed, 20 Dec 2000 05:09:45 -0500
From: "Donald J . Maddox" <dmaddox@sc.rr.com>
To: freebsd-current@freebsd.org
Cc: "Donald J . Maddox" <dmaddox@sc.rr.com>,
	Stephen McKay <mckay@thehub.com.au>, current@freebsd.org
Subject: Re: Is compatibility for old aout binaries broken?
Message-ID: <20001220050945.C4495@cae88-102-101.sc.rr.com>
Reply-To: dmaddox@sc.rr.com
Mail-Followup-To: freebsd-current@freebsd.org,
	"Donald J . Maddox" <dmaddox@sc.rr.com>,
	Stephen McKay <mckay@thehub.com.au>, current@freebsd.org
References: <20001216161756.A6370@cae88-102-101.sc.rr.com> <200012171658.eBHGwGW24109@dungeon.home> <20001220005106.F41741@dragon.nuxi.com> <20001220035707.B3783@cae88-102-101.sc.rr.com> <20001220015223.H41741@dragon.nuxi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20001220015223.H41741@dragon.nuxi.com>; from obrien@freebsd.org on Wed, Dec 20, 2000 at 01:52:23AM -0800
Return-Receipt-To: dmaddox@sc.rr.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Dec 20, 2000 at 01:52:23AM -0800, David O'Brien wrote:
> On Wed, Dec 20, 2000 at 03:57:07AM -0500, Donald J . Maddox wrote:
> > Looks like you got a lot farther than I did with it...  Are you
> > sure you don't have an old aout ld.so on that machine?
> 
> Nope.  This is a box that was a virgin install of 5-CURRENT a month ago.
> I had to install the compat20 and compat21 dists, along with doing a
> ``pkg_add -r XFree86-aoutlibs''.  The Tk is 8.0.5.
> 
> > Here's what I get:
> > 
> > >dmaddox> SimCity
> > Starting SimCity ... 
> > SimCity Classic - UNIX / Tcl & Tk Toolkit version 3.6b - Mattes
> > /usr/libexec/ld.so: Undefined symbol "___error" called from sim:/usr/X11R6/lib/aout/libX11.so.6.1 at 0x20160644
> 
> Actually you're probably getting farther than I am.  I believe I'm
> bombing so early in starting Tk, I'm not really getting to the point you
> are.  What does `ldd /usr/local/lib/SimCity/res/sim'' report?

>res> ldd sim
sim:
	-lXext.6 => /usr/X11R6/lib/aout/libXext.so.6.3 (0x200c5000)
	-lX11.6 => /usr/X11R6/lib/aout/libX11.so.6.1 (0x200cf000)
	-lc.2 => /usr/lib/compat/aout/libc.so.2.2 (0x20166000)
	-lm.2 => /usr/lib/compat/aout/libm.so.2.0 (0x201cb000)
	-lgcc.261 => /usr/lib/compat/aout/libgcc.so.261.0 (0x201e5000)
>res> 

> > Also, it looks to me like SimCity would probably run just
> > fine for you if you started X on an 8-bit display...
> 
> Maybe, but I'm not going to dink with my X server config. ;-)
> Mabye I'll try to find another box to try this on.

Heh :)  You don't have to dink around with your config...  Just do
'startx -- -bpp 8'.


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


From owner-freebsd-current  Wed Dec 20  2: 9:49 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 02:09:44 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mail5.sc.rr.com (fe5.southeast.rr.com [24.93.67.52])
	by hub.freebsd.org (Postfix) with ESMTP
	id 731F537B402; Wed, 20 Dec 2000 02:09:44 -0800 (PST)
Received: from sc.rr.com ([24.88.102.101]) by mail5.sc.rr.com  with Microsoft SMTPSVC(5.5.1877.537.53);
	 Wed, 20 Dec 2000 05:09:32 -0500
Received: (from dmaddox@localhost)
	by sc.rr.com (8.11.1/8.11.1) id eBKA9jG04619;
	Wed, 20 Dec 2000 05:09:45 -0500 (EST)
	(envelope-from dmaddox)
Date: Wed, 20 Dec 2000 05:09:45 -0500
From: "Donald J . Maddox" <dmaddox@sc.rr.com>
To: freebsd-current@freebsd.org
Cc: "Donald J . Maddox" <dmaddox@sc.rr.com>,
	Stephen McKay <mckay@thehub.com.au>, current@freebsd.org
Subject: Re: Is compatibility for old aout binaries broken?
Message-ID: <20001220050945.C4495@cae88-102-101.sc.rr.com>
Reply-To: dmaddox@sc.rr.com
Mail-Followup-To: freebsd-current@freebsd.org,
	"Donald J . Maddox" <dmaddox@sc.rr.com>,
	Stephen McKay <mckay@thehub.com.au>, current@freebsd.org
References: <20001216161756.A6370@cae88-102-101.sc.rr.com> <200012171658.eBHGwGW24109@dungeon.home> <20001220005106.F41741@dragon.nuxi.com> <20001220035707.B3783@cae88-102-101.sc.rr.com> <20001220015223.H41741@dragon.nuxi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20001220015223.H41741@dragon.nuxi.com>; from obrien@freebsd.org on Wed, Dec 20, 2000 at 01:52:23AM -0800
Return-Receipt-To: dmaddox@sc.rr.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Dec 20, 2000 at 01:52:23AM -0800, David O'Brien wrote:
> On Wed, Dec 20, 2000 at 03:57:07AM -0500, Donald J . Maddox wrote:
> > Looks like you got a lot farther than I did with it...  Are you
> > sure you don't have an old aout ld.so on that machine?
> 
> Nope.  This is a box that was a virgin install of 5-CURRENT a month ago.
> I had to install the compat20 and compat21 dists, along with doing a
> ``pkg_add -r XFree86-aoutlibs''.  The Tk is 8.0.5.
> 
> > Here's what I get:
> > 
> > >dmaddox> SimCity
> > Starting SimCity ... 
> > SimCity Classic - UNIX / Tcl & Tk Toolkit version 3.6b - Mattes
> > /usr/libexec/ld.so: Undefined symbol "___error" called from sim:/usr/X11R6/lib/aout/libX11.so.6.1 at 0x20160644
> 
> Actually you're probably getting farther than I am.  I believe I'm
> bombing so early in starting Tk, I'm not really getting to the point you
> are.  What does `ldd /usr/local/lib/SimCity/res/sim'' report?

>res> ldd sim
sim:
	-lXext.6 => /usr/X11R6/lib/aout/libXext.so.6.3 (0x200c5000)
	-lX11.6 => /usr/X11R6/lib/aout/libX11.so.6.1 (0x200cf000)
	-lc.2 => /usr/lib/compat/aout/libc.so.2.2 (0x20166000)
	-lm.2 => /usr/lib/compat/aout/libm.so.2.0 (0x201cb000)
	-lgcc.261 => /usr/lib/compat/aout/libgcc.so.261.0 (0x201e5000)
>res> 

> > Also, it looks to me like SimCity would probably run just
> > fine for you if you started X on an 8-bit display...
> 
> Maybe, but I'm not going to dink with my X server config. ;-)
> Mabye I'll try to find another box to try this on.

Heh :)  You don't have to dink around with your config...  Just do
'startx -- -bpp 8'.


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


From owner-freebsd-current  Wed Dec 20  2:24:35 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 02:24:33 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38])
	by hub.freebsd.org (Postfix) with ESMTP id 1752737B400
	for <freebsd-current@freebsd.org>; Wed, 20 Dec 2000 02:24:33 -0800 (PST)
Received: from dragon.nuxi.com (Ipittythefoolthattrustsident@trang.nuxi.com [209.152.133.57])
	by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id CAA12819;
	Wed, 20 Dec 2000 02:24:27 -0800 (PST)
	(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
	by dragon.nuxi.com (8.11.1/8.11.1) id eBKAOQJ43072;
	Wed, 20 Dec 2000 02:24:26 -0800 (PST)
	(envelope-from obrien)
Date: Wed, 20 Dec 2000 02:24:26 -0800
From: "David O'Brien" <obrien@freebsd.org>
To: "Donald J . Maddox" <dmaddox@sc.rr.com>
Cc: freebsd-current@freebsd.org, Stephen McKay <mckay@thehub.com.au>
Subject: Re: Is compatibility for old aout binaries broken?
Message-ID: <20001220022425.A43025@dragon.nuxi.com>
Reply-To: nobody@freebsd.org
References: <20001216161756.A6370@cae88-102-101.sc.rr.com> <200012171658.eBHGwGW24109@dungeon.home> <20001220005106.F41741@dragon.nuxi.com> <20001220035707.B3783@cae88-102-101.sc.rr.com> <20001220015223.H41741@dragon.nuxi.com> <20001220050945.C4495@cae88-102-101.sc.rr.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20001220050945.C4495@cae88-102-101.sc.rr.com>; from dmaddox@sc.rr.com on Wed, Dec 20, 2000 at 05:09:45AM -0500
X-Operating-System: FreeBSD 5.0-CURRENT
Organization: The NUXI BSD group
X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3  90 76 5D 69 58 D9 98 7A
X-Pgp-Rsa-Keyid: 1024/34F9F9D5
Sender: obrien@NUXI.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Dec 20, 2000 at 05:09:45AM -0500, Donald J . Maddox wrote:
> >res> ldd sim
> sim:
> 	-lXext.6 => /usr/X11R6/lib/aout/libXext.so.6.3 (0x200c5000)
> 	-lX11.6 => /usr/X11R6/lib/aout/libX11.so.6.1 (0x200cf000)
> 	-lc.2 => /usr/lib/compat/aout/libc.so.2.2 (0x20166000)
> 	-lm.2 => /usr/lib/compat/aout/libm.so.2.0 (0x201cb000)
> 	-lgcc.261 => /usr/lib/compat/aout/libgcc.so.261.0 (0x201e5000)
> >res> 

Looks good.  Can you install the XFree896-aoutlib port?  You may have
seen were someone posted the a.out libs from 3.3.6 are known to not be
the the best to use for compatibility use.
 
> Heh :)  You don't have to dink around with your config...  Just do
> 'startx -- -bpp 8'.

You assume I'm using an XFree86 server ;-) -- I am not.

-- 
-- David  (obrien@FreeBSD.org)
          GNU is Not Unix / Linux Is Not UniX
          Disclaimer: Not speaking for FreeBSD, just expressing my own opinion.


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


From owner-freebsd-current  Wed Dec 20  2:28:38 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 02:28:35 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mail7.sc.rr.com (mail7.southeast.rr.com [24.93.67.54])
	by hub.freebsd.org (Postfix) with ESMTP
	id 6E47637B400; Wed, 20 Dec 2000 02:28:35 -0800 (PST)
Received: from sc.rr.com ([24.88.102.101]) by mail7.sc.rr.com  with Microsoft SMTPSVC(5.5.1877.537.53);
	 Wed, 20 Dec 2000 05:28:31 -0500
Received: (from dmaddox@localhost)
	by sc.rr.com (8.11.1/8.11.1) id eBKASjW04832;
	Wed, 20 Dec 2000 05:28:45 -0500 (EST)
	(envelope-from dmaddox)
Date: Wed, 20 Dec 2000 05:28:45 -0500
From: "Donald J . Maddox" <dmaddox@sc.rr.com>
To: nobody@freebsd.org
Cc: "Donald J . Maddox" <dmaddox@sc.rr.com>,
	freebsd-current@freebsd.org, Stephen McKay <mckay@thehub.com.au>
Subject: Re: Is compatibility for old aout binaries broken?
Message-ID: <20001220052845.A4813@cae88-102-101.sc.rr.com>
Reply-To: dmaddox@sc.rr.com
Mail-Followup-To: nobody@freebsd.org,
	"Donald J . Maddox" <dmaddox@sc.rr.com>,
	freebsd-current@freebsd.org, Stephen McKay <mckay@thehub.com.au>
References: <20001216161756.A6370@cae88-102-101.sc.rr.com> <200012171658.eBHGwGW24109@dungeon.home> <20001220005106.F41741@dragon.nuxi.com> <20001220035707.B3783@cae88-102-101.sc.rr.com> <20001220015223.H41741@dragon.nuxi.com> <20001220050945.C4495@cae88-102-101.sc.rr.com> <20001220022425.A43025@dragon.nuxi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20001220022425.A43025@dragon.nuxi.com>; from obrien@freebsd.org on Wed, Dec 20, 2000 at 02:24:26AM -0800
Return-Receipt-To: dmaddox@sc.rr.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Dec 20, 2000 at 02:24:26AM -0800, David O'Brien wrote:
> On Wed, Dec 20, 2000 at 05:09:45AM -0500, Donald J . Maddox wrote:
> > >res> ldd sim
> > sim:
> > 	-lXext.6 => /usr/X11R6/lib/aout/libXext.so.6.3 (0x200c5000)
> > 	-lX11.6 => /usr/X11R6/lib/aout/libX11.so.6.1 (0x200cf000)
> > 	-lc.2 => /usr/lib/compat/aout/libc.so.2.2 (0x20166000)
> > 	-lm.2 => /usr/lib/compat/aout/libm.so.2.0 (0x201cb000)
> > 	-lgcc.261 => /usr/lib/compat/aout/libgcc.so.261.0 (0x201e5000)
> > >res> 
> 
> Looks good.  Can you install the XFree896-aoutlib port?  You may have
> seen were someone posted the a.out libs from 3.3.6 are known to not be
> the the best to use for compatibility use.

Ok, I'll try that now...

> > Heh :)  You don't have to dink around with your config...  Just do
> > 'startx -- -bpp 8'.
> 
> You assume I'm using an XFree86 server ;-) -- I am not.

How can you be using the same X libs as me, and not be using
XFree86?  And if you're not, doesn't that put a crimp in your
testing? ;-)


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


From owner-freebsd-current  Wed Dec 20  2:47:18 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 02:47:14 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mail7.sc.rr.com (mail7.southeast.rr.com [24.93.67.54])
	by hub.freebsd.org (Postfix) with ESMTP
	id C03B037B404; Wed, 20 Dec 2000 02:47:13 -0800 (PST)
Received: from sc.rr.com ([24.88.102.101]) by mail7.sc.rr.com  with Microsoft SMTPSVC(5.5.1877.537.53);
	 Wed, 20 Dec 2000 05:45:43 -0500
Received: (from dmaddox@localhost)
	by sc.rr.com (8.11.1/8.11.1) id eBKAjvh05874;
	Wed, 20 Dec 2000 05:45:57 -0500 (EST)
	(envelope-from dmaddox)
Date: Wed, 20 Dec 2000 05:45:57 -0500
From: "Donald J . Maddox" <dmaddox@sc.rr.com>
To: freebsd-current@freebsd.org, Stephen McKay <mckay@thehub.com.au>
Cc: obrien@freebsd.org
Subject: Re: Is compatibility for old aout binaries broken?
Message-ID: <20001220054556.A5851@cae88-102-101.sc.rr.com>
Reply-To: dmaddox@sc.rr.com
Mail-Followup-To: freebsd-current@freebsd.org,
	Stephen McKay <mckay@thehub.com.au>, obrien@freebsd.org
References: <20001216161756.A6370@cae88-102-101.sc.rr.com> <200012171658.eBHGwGW24109@dungeon.home> <20001220005106.F41741@dragon.nuxi.com> <20001220035707.B3783@cae88-102-101.sc.rr.com> <20001220015223.H41741@dragon.nuxi.com> <20001220050945.C4495@cae88-102-101.sc.rr.com> <20001220022425.A43025@dragon.nuxi.com> <20001220052845.A4813@cae88-102-101.sc.rr.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20001220052845.A4813@cae88-102-101.sc.rr.com>; from dmaddox@sc.rr.com on Wed, Dec 20, 2000 at 05:28:45AM -0500
Return-Receipt-To: dmaddox@sc.rr.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Interesting.  After I installed the XFree86-aoutlibs port, SimCity
works fine for me (on an 8-bit display)...

It didn't work with the X libs built by the port when aout libs
are requested, and it didn't work with the X libs from 3.3.6, but
it works with these.

> > Looks good.  Can you install the XFree896-aoutlib port?  You may have
> > seen were someone posted the a.out libs from 3.3.6 are known to not be
> > the the best to use for compatibility use.


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


From owner-freebsd-current  Wed Dec 20  5:15:43 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 05:15:39 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from ns5.pacific.net.au (ns5.pacific.net.au [203.143.252.30])
	by hub.freebsd.org (Postfix) with ESMTP
	id 38C8C37B400; Wed, 20 Dec 2000 05:15:37 -0800 (PST)
Received: from dungeon.home (ppp228.dyn250.pacific.net.au [203.143.250.228])
	by ns5.pacific.net.au (8.9.0/8.9.1) with ESMTP id AAA25854;
	Thu, 21 Dec 2000 00:15:32 +1100 (EST)
Received: from dungeon.home (localhost [127.0.0.1])
	by dungeon.home (8.11.1/8.9.3) with ESMTP id eBKDFtB24592;
	Wed, 20 Dec 2000 23:15:55 +1000 (EST)
	(envelope-from mckay)
Message-Id: <200012201315.eBKDFtB24592@dungeon.home>
X-Mailer: exmh version 2.1.1 1999-10-15
To: obrien@freebsd.org
Cc: "Donald J . Maddox" <dmaddox@sc.rr.com>, current@freebsd.org,
	mckay@thehub.com.au
Subject: Re: Is compatibility for old aout binaries broken? 
In-Reply-To: Message from "David O'Brien" <obrien@freebsd.org> 
   of "Wed, 20 Dec 2000 01:42:59 PST." <20001220014259.G41741@dragon.nuxi.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 20 Dec 2000 23:15:55 +1000
From: Stephen McKay <mckay@thehub.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wednesday, 20th December 2000, "David O'Brien" wrote:

>On Mon, Dec 18, 2000 at 02:58:16AM +1000, Stephen McKay wrote:
>> This has been broken for new users for some time. :-(  Those of us
>> upgrading from source have been immune to this problem, because we
>> retain the old a.out ld.so binary.
>> 
>> >/usr/libexec/ld.so: Undefined symbol "___error" called from
>> >sim:/usr/X11R6/lib /aout/libX11.so.6.1 at 0x20160644
>>
>> When errno became a function that returns a pointer (previously it was
>> a simple integer variable), recompiled libraries became incompatable with
>> old binaries.  So, I hacked the a.out loader (ld.so).  The fix was in 3.0.
>> Well, Nate called it a horrible hack, so maybe I should say "the hack was
>> in 3.0".
>
>src/lib/libc/sys/__error.c suggests this was the case for 2.2.7+.

No, you want rev 1.10 of sys/sys/errno.h.  That was when it affected all
a.out binaries.  Until then it was just threaded binaries, a vanishingly
small proportion.  Rev 1.10 was in 3.0.  Rev 1.5 was in the 2.2.x releases.

>What is out of sync is the X11 a.out libs.  They are probably built on a
>2.2.7 or 2.2.8 box, thus they refer to `___error' vs. `errno'.  These
>libs are wrong for the SimCity binary.  They are a.out yes, but not
>proper for compat20 use.  Since SimCity needs `libgcc.so.261', I'll
>assume it was built that long ago.

Correcting slightly for your slightly off assumption: The X11 libs were 
probably
built on a 3.x box.  Their problem is that being newer than libc.so.2.2 (or was
it libc.so.3.0) they use ___error but libc does not supply it.  My patches
to rtld-aout (that first appeared in FreeBSD 3.0) supply ___error in this case.
This is the only full fix for this situation.

>The problem isn't as much ld.so, as it should match the libc.so, et.al.
>you are using from the compat2[01] dist (needed to satisfy ``ldd
>lib/SimCity/res/sim'').  And `ld.so' and the shared libs would be
>consistent on the system the a.out program was built on.

There was an enormous thread in -current (I think) at the time (mid 1998).
The end result was that the ld.so hack was the only solution other than
mandating a major bump to every library in existence.  Nobody liked either
of those solutions :-) but I put the ld.so hack in and the problem disappeared.
Emphasis again: the workaround ld.so was only found in 3.0 and onward, so
just using a 2.2.x ld.so isn't enough.

>What I would feel most comfortable with, is doing a MFC to RELENG_2_2 of
>the rtld-aout changes since then, building a new `ld.so' and putting that
>in the compat2? dists.  Problem is I don't have access to a 2.2-STABLE
>box.

I have built a binary on 4.2-RELEASE.  I think I prefer that because any
security fixes in libc (or whatever) will be reflected in the resulting
ld.so.  In fact, I think we should build ld.so from source until such
time as a.out building capability is removed (5.0 perhaps).

On the other hand, merging back to 2.2.x and rebuilding should provide
a working (and hack enabled) ld.so that has no more problems than the
old binaries it is supporting.

>> I poked about with my old FreeBSD CD collection and found that
>> version 3.0 through 3.2 have a fully functioning (fully hack enabled)
>> ld.so, but an older binary has been substituted in 3.3 and onward,
>> including 4.0 and 4.1, and most likely 4.2 also.
>
>Are you sure?  src/lib/compat/compat2[012]/ld.so.gz.uu are all at
>rev 1.1.  So there has been no change to them over the lifetime of their
>existence.  All three are identical -- having the same MD5 checksum.
>Well, looking at the release tags compat22/ld.so was in 3.2.
>compat2[01]/ld.so was added for 3.3.

This very fact is bothering me a lot.  Get out your 3.2 disks and verify
that they do not match these uuencoded binaries.  Check the 3.0 and 3.1
disk 2 (live file system) and see that they don't match them either.

>> I can only guess that some anonymous release engineer (nobody we know :-)
>> picked the wrong CD at some point to get the master copy of ld.so once
>> it stopped compiling.  (Or at least stopped being easily compiled.)
>
>Not quite.  I seem to remember that JKH was makeing a tarball of a.out
>libs from what ever was on his box at the time (thus probably the last
>a.out ld.so just before E-day on 3-CURRENT).

Something like this must have happened up to and including the 3.2 release.

>When I committed the
>compat2? bits, I took ld.so from a 2.2.x release as this is the compat2?
>dist, not compat3.aout dist.  Which is what you're suggesting should have
>been done.

You missed the fact that fixes were added to ld.so after those releases
even though the purpose of ld.so is to run binaries that date from those
releases.  The existence of later, recompiled libraries requires this.

Stephen.

PS In just a few hours, I'll be out of the picture for 4 or 5 days.
   I hope I've given you a complete understanding of the situation
   in the event that I don't get to commit anything.



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


From owner-freebsd-current  Wed Dec 20  5:29:51 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 05:29:49 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from ns5.pacific.net.au (ns5.pacific.net.au [203.143.252.30])
	by hub.freebsd.org (Postfix) with ESMTP
	id 9CDC737B400; Wed, 20 Dec 2000 05:29:46 -0800 (PST)
Received: from dungeon.home (ppp228.dyn250.pacific.net.au [203.143.250.228])
	by ns5.pacific.net.au (8.9.0/8.9.1) with ESMTP id AAA26394;
	Thu, 21 Dec 2000 00:29:43 +1100 (EST)
Received: from dungeon.home (localhost [127.0.0.1])
	by dungeon.home (8.11.1/8.9.3) with ESMTP id eBKDULB24697;
	Wed, 20 Dec 2000 23:30:21 +1000 (EST)
	(envelope-from mckay)
Message-Id: <200012201330.eBKDULB24697@dungeon.home>
X-Mailer: exmh version 2.1.1 1999-10-15
To: "Donald J . Maddox" <dmaddox@sc.rr.com>
Cc: freebsd-current@freebsd.org, mckay@thehub.com.au,
	obrien@freebsd.org
Subject: Re: Is compatibility for old aout binaries broken? 
In-Reply-To: Message from "Donald J . Maddox" <dmaddox@sc.rr.com> 
   of "Wed, 20 Dec 2000 05:45:57 EST." <20001220054556.A5851@cae88-102-101.sc.rr.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 20 Dec 2000 23:30:21 +1000
From: Stephen McKay <mckay@thehub.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wednesday, 20th December 2000, "Donald J . Maddox" wrote:
>> > Looks good.  Can you install the XFree896-aoutlib port?  You may have
>> > seen were someone posted the a.out libs from 3.3.6 are known to not be
>> > the the best to use for compatibility use.
>
>Interesting.  After I installed the XFree86-aoutlibs port, SimCity
>works fine for me (on an 8-bit display)...
>
>It didn't work with the X libs built by the port when aout libs
>are requested, and it didn't work with the X libs from 3.3.6, but
>it works with these.

If the XFree896-aoutlib libraries are old enough, they will not call ___error.
That is sufficient to solve your particular problem, but not to solve the
general case.  

I'm now wondering if the reason that people don't like the XFree86 3.3.6
a.out libraries is the problem with ___error and the older ld.so supplied
with recent FreeBSD releases.

Stephen.



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


From owner-freebsd-current  Wed Dec 20  9:18:26 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 09:18:24 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42])
	by hub.freebsd.org (Postfix) with ESMTP id 8E62737B402
	for <current@freebsd.org>; Wed, 20 Dec 2000 09:18:20 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by updraft.jp.freebsd.org (8.11.1+3.4W/8.11.1) with ESMTP/inet id eBKHIG844354
	for <current@freebsd.org>; Thu, 21 Dec 2000 02:18:16 +0900 (JST)
	(envelope-from matusita@jp.FreeBSD.org)
X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu
 e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0
 P\):.2}8jo-BiZ?X&t$V
X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Peisino,Ak(B)
X-FaceAnim: (-O_O-)(O_O- )(_O-  )(O-   )(-   -)(   -O)(  -O_)( -O_O)(-O_O-)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Dispatcher: imput version 20000228(IM140)
Lines: 10
From: Makoto MATSUSHITA <matusita@jp.FreeBSD.org>
To: current@freebsd.org
Subject: Why 'lnc.ko' instead of 'if_lnc.ko' ?
Date: Thu, 21 Dec 2000 02:18:01 +0900
Message-Id: <20001221021801G.matusita@jp.FreeBSD.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Recently, we have a module of 'lnc' ethernet. Maybe it's the last
ethernet driver converted to newbus framework IIRC. Very thank you.

However, this kernel module is named as 'lnc.ko'. Other ethernet
driver modules are named as 'if_XXX.ko'; why lnc doesn't obey this
name convension? Typo, or a new name scheme is used instead?

-- -
Makoto `MAR' MATSUSHITA


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


From owner-freebsd-current  Wed Dec 20 10: 5: 6 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 10:05:04 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.66])
	by hub.freebsd.org (Postfix) with ESMTP id 57A8B37B402
	for <current@FreeBSD.ORG>; Wed, 20 Dec 2000 10:05:03 -0800 (PST)
Received: from billy-club.village.org (billy-club.village.org [10.0.0.3])
	by rover.village.org (8.11.0/8.11.0) with ESMTP id eBKI52s20091;
	Wed, 20 Dec 2000 11:05:02 -0700 (MST)
	(envelope-from imp@billy-club.village.org)
Received: from billy-club.village.org (localhost [127.0.0.1]) by billy-club.village.org (8.11.1/8.8.3) with ESMTP id eBKI5is41536; Wed, 20 Dec 2000 11:05:44 -0700 (MST)
Message-Id: <200012201805.eBKI5is41536@billy-club.village.org>
To: Makoto MATSUSHITA <matusita@jp.FreeBSD.org>
Subject: Re: Why 'lnc.ko' instead of 'if_lnc.ko' ? 
Cc: current@FreeBSD.ORG
In-reply-to: Your message of "Thu, 21 Dec 2000 02:18:01 +0900."
		<20001221021801G.matusita@jp.FreeBSD.org> 
References: <20001221021801G.matusita@jp.FreeBSD.org>  
Date: Wed, 20 Dec 2000 11:05:44 -0700
From: Warner Losh <imp@village.org>
Sender: imp@billy-club.village.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <20001221021801G.matusita@jp.FreeBSD.org>
Makoto MATSUSHITA-san writes:
: However, this kernel module is named as 'lnc.ko'. Other ethernet
: driver modules are named as 'if_XXX.ko'; why lnc doesn't obey this
: name convension? Typo, or a new name scheme is used instead?

Typo, I think.  The module needs to be named if_XXX.ko for the
automatic kldload in ifconfig to work.

Warner


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


From owner-freebsd-current  Wed Dec 20 10:10:35 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 10:10:33 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97])
	by hub.freebsd.org (Postfix) with ESMTP id 5EC9C37B400
	for <current@freebsd.org>; Wed, 20 Dec 2000 10:10:33 -0800 (PST)
Received: by freesbee.wheel.dk (Postfix, from userid 1001)
	id 3135F3E4B; Wed, 20 Dec 2000 19:10:32 +0100 (CET)
Date: Wed, 20 Dec 2000 19:10:32 +0100
From: Jesper Skriver <jesper@skriver.dk>
To: Matthew Thyer <thyerm@camtech.net.au>
Cc: Michael Class <michael_class@hp.com>, current@freebsd.org
Subject: Re: Network performance-problem
Message-ID: <20001220191031.C64470@skriver.dk>
References: <3A3DDDC7.6F2540B7@hp.com> <3A3EEADE.3924E4E6@camtech.net.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <3A3EEADE.3924E4E6@camtech.net.au>; from thyerm@camtech.net.au on Tue, Dec 19, 2000 at 03:28:06PM +1030
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, Dec 19, 2000 at 03:28:06PM +1030, Matthew Thyer wrote:
> Michael Class wrote:
> > 
> > Hello,
> > 
> > i am seeing a problem with 5.0-current (from 14.12.00) and a 3COM
> > 3CCFE575CT Lancard (pc-cardbus) using the xl-driver.
> 
> [snip]
> 
> > Why behaves my FreeBSD-machines worse then the other boxes? Any Ideas?
> 
> Make sure you are running with the TCP/IP NewReno optimisation turned
> off.  There are bugs in the TCP/IP NewReno code that result in bad
> packets and hence lots of retransmission with generally reduced network
> performance.
> 
> I think its meant to be the default now in -CURRENT (to have NewReno off)
> but I'm not sure if PHK has disabled it yet.
> 
> $ cat /usr/local/etc/rc.d/nonewreno.sh 
> #!/bin/sh
> sysctl -w net.inet.tcp.newreno=0
> echo -n " no_newreno"

A

echo "net.inet.tcp.newreno=0" >> /etc/sysctl.conf

would be easier ;-)

/Jesper

-- 
Jesper Skriver, jesper(at)skriver(dot)dk  -  CCIE #5456
Work:    Network manager @ AS3292 (Tele Danmark DataNetworks)
Private: Geek            @ AS2109 (A much smaller network ;-)

One Unix to rule them all, One Resolver to find them,
One IP to bring them all and in the zone to bind them.


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


From owner-freebsd-current  Wed Dec 20 10:14:20 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 10:14:14 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38])
	by hub.freebsd.org (Postfix) with ESMTP id D17C637B404
	for <current@freebsd.org>; Wed, 20 Dec 2000 10:14:13 -0800 (PST)
Received: from dragon.nuxi.com (Ipittythefoolthattrustsident@trang.nuxi.com [209.152.133.57])
	by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id KAA14457;
	Wed, 20 Dec 2000 10:14:12 -0800 (PST)
	(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
	by dragon.nuxi.com (8.11.1/8.11.1) id eBKIEAc09063;
	Wed, 20 Dec 2000 10:14:10 -0800 (PST)
	(envelope-from obrien)
Date: Wed, 20 Dec 2000 10:14:09 -0800
From: "David O'Brien" <obrien@freebsd.org>
To: Stephen McKay <mckay@thehub.com.au>
Cc: current@freebsd.org
Subject: Re: Is compatibility for old aout binaries broken?
Message-ID: <20001220101409.B8849@dragon.nuxi.com>
Reply-To: freebsd-current@freebsd.org
References: <obrien@freebsd.org> <200012201315.eBKDFtB24592@dungeon.home>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <200012201315.eBKDFtB24592@dungeon.home>; from mckay@thehub.com.au on Wed, Dec 20, 2000 at 11:15:55PM +1000
X-Operating-System: FreeBSD 5.0-CURRENT
Organization: The NUXI BSD group
X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3  90 76 5D 69 58 D9 98 7A
X-Pgp-Rsa-Keyid: 1024/34F9F9D5
Sender: obrien@NUXI.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Dec 20, 2000 at 11:15:55PM +1000, Stephen McKay wrote:
> Correcting slightly for your slightly off assumption: The X11 libs were
> probably built on a 3.x box.  Their problem is that being newer than
> libc.so.2.2 (or was it libc.so.3.0) they use ___error but libc does not
> supply it.  My patches to rtld-aout (that first appeared in FreeBSD
> 3.0) supply ___error in this case.  This is the only full fix for this
> situation.

Why is not changing the XFree86-aoutlibs port to offer libs built on
2.2.x not the right fix?


> Emphasis again: the workaround ld.so was only found in 3.0 and onward, so
> just using a 2.2.x ld.so isn't enough.

I am very uncomfortable putting in a ld.so built on 3.0 into the compat2?
dists.  I'm painfully aware of all the un-thought of issues that can come
up when changing dynamic linking methods, etc.. just look at the two
opposing threads in the past month about how to handle libcc and dynamic
[and threaded] libs and binaries.


> In fact, I think we should build ld.so from source until such time as
> a.out building capability is removed (5.0 perhaps).

Fine BUT IT ISN'T compat2?.  PLEASE think about the issues for a moment.
You are mixing bits that are not consistent.  Maybe it fixes this one
case, but what about all the other cases.  What we need to do is offer
a.out bits so users can duplicate the system the binary was built on.

4.2 a.out bits != 2.2.x a.out bits.  There are two issues here -- binary
format (a.out vs. ELF), _and_ library versions.


> On the other hand, merging back to 2.2.x and rebuilding should provide
> a working (and hack enabled) ld.so that has no more problems than the
> old binaries it is supporting.

And is consistent with the binaries and libs of that release.


> >Are you sure?  src/lib/compat/compat2[012]/ld.so.gz.uu are all at
> >rev 1.1.  So there has been no change to them over the lifetime of their
> >existence.  All three are identical -- having the same MD5 checksum.
> >Well, looking at the release tags compat22/ld.so was in 3.2.
> >compat2[01]/ld.so was added for 3.3.
> 
> This very fact is bothering me a lot.  Get out your 3.2 disks and verify
> that they do not match these uuencoded binaries.  Check the 3.0 and 3.1
> disk 2 (live file system) and see that they don't match them either.

I'm sure they don't -- I just wrote above I didn't add ld.so to the
compat2? dists until 3.2 and 3.3.  So of course the 3.0 and 3.1 a.out
bits are different.


> You missed the fact that fixes were added to ld.so after those releases
> even though the purpose of ld.so is to run binaries that date from those
> releases.  The existence of later, recompiled libraries requires this.

No, you're missing the fact that these are comat2? bits, not a.out bits.
If you want 3.x a.out bits then a compat3x.aout dist should be created.

-- 
-- David  (obrien@FreeBSD.org)
          GNU is Not Unix / Linux Is Not UniX


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


From owner-freebsd-current  Wed Dec 20 10:29: 1 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 10:28:57 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42])
	by hub.freebsd.org (Postfix) with ESMTP id C5FB037B402
	for <current@FreeBSD.ORG>; Wed, 20 Dec 2000 10:28:56 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by updraft.jp.freebsd.org (8.11.1+3.4W/8.11.1) with ESMTP/inet id eBKISr844856;
	Thu, 21 Dec 2000 03:28:53 +0900 (JST)
	(envelope-from matusita@jp.FreeBSD.org)
Cc: imp@village.org
In-Reply-To: <200012201805.eBKI5is41536@billy-club.village.org>
References: <20001221021801G.matusita@jp.FreeBSD.org>
	<200012201805.eBKI5is41536@billy-club.village.org>
X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu
 e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0
 P\):.2}8jo-BiZ?X&t$V
X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Peisino,Ak(B)
X-FaceAnim: (-O_O-)(O_O- )(_O-  )(O-   )(-   -)(   -O)(  -O_)( -O_O)(-O_O-)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Dispatcher: imput version 20000228(IM140)
Lines: 33
From: Makoto MATSUSHITA <matusita@jp.FreeBSD.org>
To: current@FreeBSD.ORG
Subject: Re: Why 'lnc.ko' instead of 'if_lnc.ko' ? 
Date: Thu, 21 Dec 2000 03:28:46 +0900
Message-Id: <20001221032846U.matusita@jp.FreeBSD.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


imp> Typo, I think.  The module needs to be named if_XXX.ko for the
imp> automatic kldload in ifconfig to work.

OK, attached below is a (trivial) patch to fix this.

-- -
Makoto `MAR' MATSUSHITA

Index: Makefile
===================================================================
RCS file: /lab/FreeBSD/FreeBSD.cvs/src/sys/modules/lnc/Makefile,v
retrieving revision 1.1
diff -c -r1.1 Makefile
*** Makefile	2000/12/16 01:47:37	1.1
--- Makefile	2000/12/20 18:19:11
***************
*** 1,7 ****
  # $FreeBSD: src/sys/modules/lnc/Makefile,v 1.1 2000/12/16 01:47:37 paul Exp $
  
  .PATH:	${.CURDIR}/../../dev/lnc
! KMOD	= lnc
  SRCS	= if_lnc.c if_lnc_pci.c if_lnc_isa.c if_lnc_pc98.c
  SRCS	+= opt_inet.h device_if.h bus_if.h isa_if.h pci_if.h
  #SRCS	+= miibus_if.h
--- 1,7 ----
  # $FreeBSD: src/sys/modules/lnc/Makefile,v 1.1 2000/12/16 01:47:37 paul Exp $
  
  .PATH:	${.CURDIR}/../../dev/lnc
! KMOD	= if_lnc
  SRCS	= if_lnc.c if_lnc_pci.c if_lnc_isa.c if_lnc_pc98.c
  SRCS	+= opt_inet.h device_if.h bus_if.h isa_if.h pci_if.h
  #SRCS	+= miibus_if.h


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


From owner-freebsd-current  Wed Dec 20 10:30:35 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 10:30:33 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mail5.sc.rr.com (fe5.southeast.rr.com [24.93.67.52])
	by hub.freebsd.org (Postfix) with ESMTP id 32AD937B698
	for <freebsd-current@freebsd.org>; Wed, 20 Dec 2000 10:30:33 -0800 (PST)
Received: from sc.rr.com ([24.88.102.101]) by mail5.sc.rr.com  with Microsoft SMTPSVC(5.5.1877.537.53);
	 Wed, 20 Dec 2000 13:29:50 -0500
Received: (from dmaddox@localhost)
	by sc.rr.com (8.11.1/8.11.1) id eBKIU3C07466;
	Wed, 20 Dec 2000 13:30:03 -0500 (EST)
	(envelope-from dmaddox)
Date: Wed, 20 Dec 2000 13:30:03 -0500
From: "Donald J . Maddox" <dmaddox@sc.rr.com>
To: freebsd-current@freebsd.org
Cc: Stephen McKay <mckay@thehub.com.au>
Subject: Re: Is compatibility for old aout binaries broken?
Message-ID: <20001220133003.B7333@cae88-102-101.sc.rr.com>
Reply-To: dmaddox@sc.rr.com
Mail-Followup-To: freebsd-current@freebsd.org,
	Stephen McKay <mckay@thehub.com.au>
References: <obrien@freebsd.org> <200012201315.eBKDFtB24592@dungeon.home> <20001220101409.B8849@dragon.nuxi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20001220101409.B8849@dragon.nuxi.com>; from obrien@freebsd.org on Wed, Dec 20, 2000 at 10:14:09AM -0800
Return-Receipt-To: dmaddox@sc.rr.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Dec 20, 2000 at 10:14:09AM -0800, David O'Brien wrote:
> On Wed, Dec 20, 2000 at 11:15:55PM +1000, Stephen McKay wrote:
> > Correcting slightly for your slightly off assumption: The X11 libs were
> > probably built on a 3.x box.  Their problem is that being newer than
> > libc.so.2.2 (or was it libc.so.3.0) they use ___error but libc does not
> > supply it.  My patches to rtld-aout (that first appeared in FreeBSD
> > 3.0) supply ___error in this case.  This is the only full fix for this
> > situation.
> 
> Why is not changing the XFree86-aoutlibs port to offer libs built on
> 2.2.x not the right fix?

I was under the impression that this was already the case...  The libs
in the XFree86-aoutlibs port ARE from 2.2.x.  My problem was that I
was using libs built on 3.x.



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


From owner-freebsd-current  Wed Dec 20 10:43:48 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 10:43:46 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5A40D37B400; Wed, 20 Dec 2000 10:43:46 -0800 (PST)
Received: from dragon.nuxi.com (Ipittythefoolthattrustsident@trang.nuxi.com [209.152.133.57])
	by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id KAA14674;
	Wed, 20 Dec 2000 10:43:40 -0800 (PST)
	(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
	by dragon.nuxi.com (8.11.1/8.11.1) id eBKIhdA09539;
	Wed, 20 Dec 2000 10:43:39 -0800 (PST)
	(envelope-from obrien)
Date: Wed, 20 Dec 2000 10:43:39 -0800
From: "David O'Brien" <obrien@freebsd.org>
To: "Donald J . Maddox" <dmaddox@sc.rr.com>
Cc: nobody@freebsd.org, freebsd-current@freebsd.org,
	Stephen McKay <mckay@thehub.com.au>
Subject: Re: Is compatibility for old aout binaries broken?
Message-ID: <20001220104338.E9294@dragon.nuxi.com>
Reply-To: nobody@freebsd.org
References: <20001216161756.A6370@cae88-102-101.sc.rr.com> <200012171658.eBHGwGW24109@dungeon.home> <20001220005106.F41741@dragon.nuxi.com> <20001220035707.B3783@cae88-102-101.sc.rr.com> <20001220015223.H41741@dragon.nuxi.com> <20001220050945.C4495@cae88-102-101.sc.rr.com> <20001220022425.A43025@dragon.nuxi.com> <20001220052845.A4813@cae88-102-101.sc.rr.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20001220052845.A4813@cae88-102-101.sc.rr.com>; from dmaddox@sc.rr.com on Wed, Dec 20, 2000 at 05:28:45AM -0500
X-Operating-System: FreeBSD 5.0-CURRENT
Organization: The NUXI BSD group
X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3  90 76 5D 69 58 D9 98 7A
X-Pgp-Rsa-Keyid: 1024/34F9F9D5
Sender: obrien@NUXI.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Dec 20, 2000 at 05:28:45AM -0500, Donald J . Maddox wrote:
> > > Heh :)  You don't have to dink around with your config...  Just do
> > > 'startx -- -bpp 8'.
> > You assume I'm using an XFree86 server ;-) -- I am not.
> 
> How can you be using the same X libs as me, and not be using
> XFree86?

XFree86 has many components to it -- binaries (such as Xterm), libs (such
as libX11.{so,a}, and X servers.  I use all the XFree86 bits except for
the X server.  I use a mix of Metrolink's and Xi Graphics servers.

-- 
-- David  (obrien@FreeBSD.org)
          GNU is Not Unix / Linux Is Not UniX


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


From owner-freebsd-current  Wed Dec 20 11: 7:45 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 11:07:42 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mail8.sc.rr.com (fe8.southeast.rr.com [24.93.67.55])
	by hub.freebsd.org (Postfix) with ESMTP
	id E3FC637B400; Wed, 20 Dec 2000 11:07:41 -0800 (PST)
Received: from sc.rr.com ([24.88.102.101]) by mail8.sc.rr.com  with Microsoft SMTPSVC(5.5.1877.537.53);
	 Wed, 20 Dec 2000 14:06:02 -0500
Received: (from dmaddox@localhost)
	by sc.rr.com (8.11.1/8.11.1) id eBKJ7dS07657;
	Wed, 20 Dec 2000 14:07:39 -0500 (EST)
	(envelope-from dmaddox)
Date: Wed, 20 Dec 2000 14:07:39 -0500
From: "Donald J . Maddox" <dmaddox@sc.rr.com>
To: "David O'Brien" <obrien@freebsd.org>
Cc: dmaddox@sc.rr.com, freebsd-current@freebsd.org
Subject: Re: Is compatibility for old aout binaries broken?
Message-ID: <20001220140739.C7333@cae88-102-101.sc.rr.com>
Reply-To: dmaddox@sc.rr.com
Mail-Followup-To: David O'Brien <obrien@freebsd.org>, dmaddox@sc.rr.com,
	freebsd-current@freebsd.org
References: <20001216161756.A6370@cae88-102-101.sc.rr.com> <200012171658.eBHGwGW24109@dungeon.home> <20001220005106.F41741@dragon.nuxi.com> <20001220035707.B3783@cae88-102-101.sc.rr.com> <20001220015223.H41741@dragon.nuxi.com> <20001220050945.C4495@cae88-102-101.sc.rr.com> <20001220022425.A43025@dragon.nuxi.com> <20001220052845.A4813@cae88-102-101.sc.rr.com> <20001220104338.E9294@dragon.nuxi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20001220104338.E9294@dragon.nuxi.com>; from obrien@freebsd.org on Wed, Dec 20, 2000 at 10:43:39AM -0800
Return-Receipt-To: dmaddox@sc.rr.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Dec 20, 2000 at 10:43:39AM -0800, David O'Brien wrote:
> On Wed, Dec 20, 2000 at 05:28:45AM -0500, Donald J . Maddox wrote:
> > 
> > How can you be using the same X libs as me, and not be using
> > XFree86?
> 
> XFree86 has many components to it -- binaries (such as Xterm), libs (such
> as libX11.{so,a}, and X servers.  I use all the XFree86 bits except for
> the X server.  I use a mix of Metrolink's and Xi Graphics servers.

I see.  I was thinking that the Xserver would need to use the installed
X libs, but I see that is not the case, even with XF86:

>dmaddox> ldd /usr/X11R6/bin/XF86_SVGA
/usr/X11R6/bin/XF86_SVGA:
        libxpg4.so.3 => /usr/lib/libxpg4.so.3 (0x2830b000)
        libz.so.2 => /usr/lib/libz.so.2 (0x2830d000)
        libm.so.2 => /usr/lib/libm.so.2 (0x2831a000)
        libc.so.5 => /usr/lib/libc.so.5 (0x28336000)
>dmaddox>



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


From owner-freebsd-current  Wed Dec 20 11:42: 7 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 11:42:05 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.66])
	by hub.freebsd.org (Postfix) with ESMTP id 60F4C37B400
	for <current@FreeBSD.ORG>; Wed, 20 Dec 2000 11:42:04 -0800 (PST)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.11.0/8.11.0) with ESMTP id eBKJg2s20585;
	Wed, 20 Dec 2000 12:42:03 -0700 (MST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA10802; Wed, 20 Dec 2000 12:42:01 -0700 (MST)
Message-Id: <200012201942.MAA10802@harmony.village.org>
To: Makoto MATSUSHITA <matusita@jp.FreeBSD.org>
Subject: Re: Why 'lnc.ko' instead of 'if_lnc.ko' ? 
Cc: current@FreeBSD.ORG
In-reply-to: Your message of "Thu, 21 Dec 2000 03:28:46 +0900."
		<20001221032846U.matusita@jp.FreeBSD.org> 
References: <20001221032846U.matusita@jp.FreeBSD.org>  <20001221021801G.matusita@jp.FreeBSD.org> <200012201805.eBKI5is41536@billy-club.village.org> 
Date: Wed, 20 Dec 2000 12:42:01 -0700
From: Warner Losh <imp@village.org>
Sender: imp@harmony.village.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <20001221032846U.matusita@jp.FreeBSD.org> Makoto MATSUSHITA writes:
: imp> Typo, I think.  The module needs to be named if_XXX.ko for the
: imp> automatic kldload in ifconfig to work.
: 
: OK, attached below is a (trivial) patch to fix this.

This is a good start at a fix.  However, all the attachments for the
lnc device also need to be called if_lnc.  And they need to share the
same devclass_t so that unit numbers don't go wonky on you (eg, if you
have a isa and a pci lnc card in the same system, you might get two
lnc0's).

The ed driver has this problem as well.  The ep driver doesn't.  The
ep driver is wrong in that its name is ep rather than if_ep.  The sn
driver I think gets these both right, but I think its dependence on
pcic is bogus.

Warner


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


From owner-freebsd-current  Wed Dec 20 13:13:20 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 13:13:18 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from external.conexus.co.uk (unknown [193.129.253.169])
	by hub.freebsd.org (Postfix) with ESMTP id AFB2937B400
	for <current@freebsd.org>; Wed, 20 Dec 2000 13:13:17 -0800 (PST)
Received: from mx16.quickstockpower.com ([63.57.73.51])
          by external.conexus.co.uk (Lotus Domino Release 5.0.3 (Intl))
          with SMTP id 2000122021195712:6737 ;
          Wed, 20 Dec 2000 21:19:57 +0000 
Subject: I LOVE YOU AND I DON'T WANT YOU TO DIE!!.
Date: Wed, 20 Dec 2000 12:36:56 -0500
From: achambergal@quickstockpower.com
To: quickstockpower@home.com
Received: from mx16.quickstockpower.com [192.168.222.13] by 6qbv1.mx16.quickstockpower.com with SMTP; Wed, 20 Dec 2000 12:36:56 -0500
Cc: current@home.com, current@home.com, current@home.com,
	current@home.com, current@home.com, current@home.com
X-Mailer: Mozilla 4.7 [en] (Win95; U)
Message-Id: <013wwas7ri3j11.55sa3r8uuw7h5rhfph@mx16.quickstockpower.com>
X-MIMETrack: Itemize by SMTP Server on WebDB2/Servers/Conexus(Release 5.0.3 (Intl)|21
 March 2000) at 20/12/2000 21:19:58,
	Serialize by Router on WebDB2/Servers/Conexus(Release 5.0.3 (Intl)|21 March
 2000) at 20/12/2000 21:20:34
MIME-Version: 1.0
Content-Type: text/html;
	 charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: philbare57@quickstockpower.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

<HTML>

<head>
<title></title>
</head>

<body bgcolor=3D"#00FFFF">

<p><b>We've already paid out over a cool <font color=3D"#FF0000"> MILLION=20
DOLLARS</font> to
<font color=3D"#FF0000"> WINNERS</font> just like YOU.<br>
<br>
Enter the Finest, Highest Paying Casino Online<br>
<br>
<font color=3D"#FF0000">$25,000 WINNERS</font> are cashing in at our casino=
=20
DAILY.
Grab YOUR share of this wealth pool and open an account now. We'll bring th=
e=20
finest, most secure, highest paying casino on the Net right to your desktop.
<br>
<br>
We deliver the best games, like <font color=3D"#FF0000"> REAL LAS VEGAS STY=
LE=20
BLACKJACK</font> plus Caribbean Stud, Draw Poker and LOTS of the loosest Sl=
ot=20
Machines you'll ever find. You're just a click away from High Paying Winnin=
g=20
Action.<br>
<br>
FREE $10 SIGN UP for EVERY new player.<br>
<a href=3D"http://www3.quickstockpower.com/casino"><font size=3D"5">CLICK=20
HERE</font></a> To Enter The Casino and Win Big Now<br>
<br>
3D JAVA &amp; Muti-Player.<br>
<br>
Play the best online Casino in the world right now.<br>
<br>
NO DOWNLOADS necessary.<br>
<br>
INSTANT ACCESS<br>
<br>
High quality, totally secure and private CASINO FUN, right on your computer=
=20
in the comfort and privacy of home.<br>
<br>
PLAY WITH A PROVEN GAMING ORGANIZATION.<br>
<br>
Your privacy is taken very seriously and is assured.<br>
<br>
WIN BIG at our Virtual Tables and Cash Out Instantly!<br>
<br>
<br>
To Be Removed From Future Mailings: <a href=3D"http://www3.quickstockpower.
com/remove"> CLICK HERE</a><br>
</b></p>
</HTML>



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


From owner-freebsd-current  Wed Dec 20 13:49:46 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 13:49:44 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from genesis.k.pl (genesis.korbank.pl [195.117.162.253])
	by hub.freebsd.org (Postfix) with ESMTP id 5035D37B402
	for <freebsd-current@freebsd.org>; Wed, 20 Dec 2000 13:49:42 -0800 (PST)
Received: (from ns88@localhost)
	by genesis.k.pl (8.11.1/8.11.1) id eBKLnBm99261
	for freebsd-current@freebsd.org; Wed, 20 Dec 2000 22:49:11 +0100 (CET)
	(envelope-from ns88)
Date: Wed, 20 Dec 2000 22:49:11 +0100
From: Tomasz Paszkowski <ns88@k.pl>
To: freebsd-current@freebsd.org
Subject: open in kernelspace
Message-ID: <20001220224911.A43437@genesis.k.pl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Sender: ns88@genesis.k.pl
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


 How to open && read file from kernel space. I have seen VOP_[READ,OPEN]
 but i think there's something easiest ?

-- 
   _     _    _   _    _ 
  /  \  | | / /  / \  / \  ---------- Tomasz Paszkowski --- NS88-6BONE --------
  | |\ \| | \ \ |/ \||/ \| === BSD is for people who love Unix ================
 /_/  \__/  /_/  \_/  \_/  --- Linux is for people who hate Microsoft ---------



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


From owner-freebsd-current  Wed Dec 20 13:52:52 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 13:52:51 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147])
	by hub.freebsd.org (Postfix) with ESMTP id 6F87837B400
	for <freebsd-current@FreeBSD.ORG>; Wed, 20 Dec 2000 13:52:50 -0800 (PST)
Received: from critter (localhost [127.0.0.1])
	by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eBKLq5f56944;
	Wed, 20 Dec 2000 22:52:05 +0100 (CET)
	(envelope-from phk@critter.freebsd.dk)
To: Tomasz Paszkowski <ns88@k.pl>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: open in kernelspace 
In-Reply-To: Your message of "Wed, 20 Dec 2000 22:49:11 +0100."
             <20001220224911.A43437@genesis.k.pl> 
Date: Wed, 20 Dec 2000 22:52:05 +0100
Message-ID: <56942.977349125@critter>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <20001220224911.A43437@genesis.k.pl>, Tomasz Paszkowski writes:
>
> How to open && read file from kernel space. I have seen VOP_[READ,OPEN]
> but i think there's something easiest ?

VOP_* is the way to go.

--
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.


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


From owner-freebsd-current  Wed Dec 20 14: 7:52 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 14:07:51 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from genesis.k.pl (genesis.korbank.pl [195.117.162.253])
	by hub.freebsd.org (Postfix) with ESMTP id 0B76037B400
	for <freebsd-current@freebsd.org>; Wed, 20 Dec 2000 14:07:49 -0800 (PST)
Received: (from ns88@localhost)
	by genesis.k.pl (8.11.1/8.11.1) id eBKM2LA96081;
	Wed, 20 Dec 2000 23:02:21 +0100 (CET)
	(envelope-from ns88)
Date: Wed, 20 Dec 2000 23:02:21 +0100
From: Tomasz Paszkowski <ns88@k.pl>
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
Cc: freebsd-current@freebsd.org
Subject: Re: open in kernelspace
Message-ID: <20001220230221.A66954@genesis.k.pl>
References: <20001220224911.A43437@genesis.k.pl> <56942.977349125@critter>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <56942.977349125@critter>; from phk@critter.freebsd.dk on Wed, Dec 20, 2000 at 10:52:05PM +0100
Sender: ns88@genesis.k.pl
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Dec 20, 2000 at 10:52:05PM +0100, Poul-Henning Kamp wrote:
> > How to open && read file from kernel space. I have seen VOP_[READ,OPEN]
> > but i think there's something easiest ?
> 
> VOP_* is the way to go.

 :(( So I'll have a long night

-- 
   _     _    _   _    _ 
  /  \  | | / /  / \  / \  ---------- Tomasz Paszkowski --- NS88-6BONE --------
  | |\ \| | \ \ |/ \||/ \| === BSD is for people who love Unix ================
 /_/  \__/  /_/  \_/  \_/  --- Linux is for people who hate Microsoft ---------



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


From owner-freebsd-current  Wed Dec 20 14:11: 6 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 14:11:04 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147])
	by hub.freebsd.org (Postfix) with ESMTP id EB48437B400
	for <freebsd-current@FreeBSD.ORG>; Wed, 20 Dec 2000 14:11:03 -0800 (PST)
Received: from critter (localhost [127.0.0.1])
	by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eBKMArf57112;
	Wed, 20 Dec 2000 23:10:53 +0100 (CET)
	(envelope-from phk@critter.freebsd.dk)
To: Tomasz Paszkowski <ns88@k.pl>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: open in kernelspace 
In-Reply-To: Your message of "Wed, 20 Dec 2000 23:02:21 +0100."
             <20001220230221.A66954@genesis.k.pl> 
Date: Wed, 20 Dec 2000 23:10:53 +0100
Message-ID: <57110.977350253@critter>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <20001220230221.A66954@genesis.k.pl>, Tomasz Paszkowski writes:
>On Wed, Dec 20, 2000 at 10:52:05PM +0100, Poul-Henning Kamp wrote:
>> > How to open && read file from kernel space. I have seen VOP_[READ,OPEN]
>> > but i think there's something easiest ?
>> 
>> VOP_* is the way to go.
>
> :(( So I'll have a long night

Sorry, yes...

ktrace, various accounting and of course open(2) will be the best 
places to start.

In all likely hood you're trying to do something the wrong way
though...

--
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.


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


From owner-freebsd-current  Wed Dec 20 14:37:50 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 14:37:48 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from genesis.k.pl (genesis.korbank.pl [195.117.162.253])
	by hub.freebsd.org (Postfix) with ESMTP id 46CE237B400
	for <freebsd-current@freebsd.org>; Wed, 20 Dec 2000 14:37:47 -0800 (PST)
Received: (from ns88@localhost)
	by genesis.k.pl (8.11.1/8.11.1) id eBKMXir34431;
	Wed, 20 Dec 2000 23:33:44 +0100 (CET)
	(envelope-from ns88)
Date: Wed, 20 Dec 2000 23:33:44 +0100
From: Tomasz Paszkowski <ns88@k.pl>
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
Cc: freebsd-current@freebsd.org
Subject: Re: open in kernelspace
Message-ID: <20001220233344.A66282@genesis.k.pl>
References: <20001220230221.A66954@genesis.k.pl> <57110.977350253@critter>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <57110.977350253@critter>; from phk@critter.freebsd.dk on Wed, Dec 20, 2000 at 11:10:53PM +0100
Sender: ns88@genesis.k.pl
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Dec 20, 2000 at 11:10:53PM +0100, Poul-Henning Kamp wrote:
> Sorry, yes...
> 
> ktrace, various accounting and of course open(2) will be the best 
> places to start.
> 
> In all likely hood you're trying to do something the wrong way
> though...

I'm trying to open file located on /, from kernel module. I have tried
with open, but this function require arguments from user space.

I have find sth easiest vn_open, but still If someone know how to use
open in krenel space please tell me.

-- 
   _     _    _   _    _ 
  /  \  | | / /  / \  / \  ---------- Tomasz Paszkowski --- NS88-6BONE --------
  | |\ \| | \ \ |/ \||/ \| === BSD is for people who love Unix ================
 /_/  \__/  /_/  \_/  \_/  --- Linux is for people who hate Microsoft ---------



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


From owner-freebsd-current  Wed Dec 20 17:26:27 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 17:26:25 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42])
	by hub.freebsd.org (Postfix) with ESMTP id D552237B402
	for <current@FreeBSD.ORG>; Wed, 20 Dec 2000 17:26:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by updraft.jp.freebsd.org (8.11.1+3.4W/8.11.1) with ESMTP/inet id eBL1QH849050;
	Thu, 21 Dec 2000 10:26:18 +0900 (JST)
	(envelope-from matusita@jp.FreeBSD.org)
Cc: current@FreeBSD.ORG
In-Reply-To: <200012201942.MAA10802@harmony.village.org>
References: <20001221021801G.matusita@jp.FreeBSD.org>
	<200012201805.eBKI5is41536@billy-club.village.org>
	<200012201942.MAA10802@harmony.village.org>
X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu
 e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0
 P\):.2}8jo-BiZ?X&t$V
X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Peisino,Ak(B)
X-FaceAnim: (-O_O-)(O_O- )(_O-  )(O-   )(-   -)(   -O)(  -O_)( -O_O)(-O_O-)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Dispatcher: imput version 20000228(IM140)
Lines: 20
From: Makoto MATSUSHITA <matusita@jp.FreeBSD.org>
To: imp@village.org
Subject: Re: Why 'lnc.ko' instead of 'if_lnc.ko' ? 
Date: Thu, 21 Dec 2000 10:26:12 +0900
Message-Id: <20001221102612F.matusita@jp.FreeBSD.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


imp> This is a good start at a fix.  However, all the attachments for the
imp> lnc device also need to be called if_lnc.  And they need to share the
imp> same devclass_t so that unit numbers don't go wonky on you (eg, if you
imp> have a isa and a pci lnc card in the same system, you might get two
imp> lnc0's).

Hmm, fixing these are beyond my skill...

***

BTW, are there anybody working on 'pcn' (yet another lance driver) to
work with VMware ? Current 5-current installation floppy makes VMware
panic (caution: FreeBSD doesn't panic), and it is maybe caused by pcn
driver when it knocks VMware pseudo ethernet device in 32bit mode.
Note that FreeBSD 4-stable works well with VMware, so maybe there are
hints in the differences between 4-stable and 5-current.

-- -
Makoto `MAR' MATSUSHITA


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


From owner-freebsd-current  Wed Dec 20 17:33:16 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 17:33:12 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from ns5.pacific.net.au (ns5.pacific.net.au [203.143.252.30])
	by hub.freebsd.org (Postfix) with ESMTP
	id 70C8437B400; Wed, 20 Dec 2000 17:33:10 -0800 (PST)
Received: from dungeon.home (ppp201.dyn248.pacific.net.au [203.143.248.201])
	by ns5.pacific.net.au (8.9.0/8.9.1) with ESMTP id MAA02102;
	Thu, 21 Dec 2000 12:33:06 +1100 (EST)
Received: from dungeon.home (localhost [127.0.0.1])
	by dungeon.home (8.11.1/8.9.3) with ESMTP id eBL1XfA10222;
	Thu, 21 Dec 2000 11:33:41 +1000 (EST)
	(envelope-from mckay)
Message-Id: <200012210133.eBL1XfA10222@dungeon.home>
X-Mailer: exmh version 2.1.1 1999-10-15
To: "Donald J . Maddox" <dmaddox@sc.rr.com>
Cc: freebsd-current@freebsd.org, mckay@thehub.com.au,
	"David O'Brien" <obrien@freebsd.org>
Subject: Re: Is compatibility for old aout binaries broken? 
In-Reply-To: Message from "Donald J . Maddox" <dmaddox@sc.rr.com> 
   of "Wed, 20 Dec 2000 13:30:03 EST." <20001220133003.B7333@cae88-102-101.sc.rr.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 21 Dec 2000 11:33:41 +1000
From: Stephen McKay <mckay@thehub.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wednesday, 20th December 2000, "Donald J . Maddox" wrote:

>On Wed, Dec 20, 2000 at 10:14:09AM -0800, David O'Brien wrote:
>> On Wed, Dec 20, 2000 at 11:15:55PM +1000, Stephen McKay wrote:
>> > Correcting slightly for your slightly off assumption: The X11 libs were
>> > probably built on a 3.x box.  Their problem is that being newer than
>> > libc.so.2.2 (or was it libc.so.3.0) they use ___error but libc does not
>> > supply it.  My patches to rtld-aout (that first appeared in FreeBSD
>> > 3.0) supply ___error in this case.  This is the only full fix for this
>> > situation.
>> 
>> Why is not changing the XFree86-aoutlibs port to offer libs built on
>> 2.2.x not the right fix?
>
>I was under the impression that this was already the case...  The libs
>in the XFree86-aoutlibs port ARE from 2.2.x.  My problem was that I
>was using libs built on 3.x.

(I think I can save a lot of typing by replying to this message.  I'm just
about to leave town.)

My whole point is that generating a.out binaries and libraries didn't stop
the instant that 3.0 hit the streets.  To support the mixture of old binary
plus new library you need a hacked ld.so.  We have to supply it somehow,
or simply say we don't care about certain binaries dying with obscure
error messages.  This XFree86-aoutlibs vs libs built on 3.x example supports
my theme.

I can't reconcile your naming convention (ie compat22 bits originated on
a 2.2.x box) with my version (compat22 is used to support 2.2.x binaries).

I'm also not afraid that a binary generated on 4.2 would have hidden
defects.  I'm more worried that one generated on 2.2.x would have defects
we've forgotten about.

If you don't mind pausing the whole argument for about 4 days, I can
rejoin.  :-)

Stephen.



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


From owner-freebsd-current  Wed Dec 20 17:42:43 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 17:42:41 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.66])
	by hub.freebsd.org (Postfix) with ESMTP id C1D6C37B400
	for <current@FreeBSD.ORG>; Wed, 20 Dec 2000 17:42:40 -0800 (PST)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.11.0/8.11.0) with ESMTP id eBL1gds22483;
	Wed, 20 Dec 2000 18:42:39 -0700 (MST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA13073; Wed, 20 Dec 2000 18:42:39 -0700 (MST)
Message-Id: <200012210142.SAA13073@harmony.village.org>
To: Makoto MATSUSHITA <matusita@jp.FreeBSD.org>
Subject: Re: Why 'lnc.ko' instead of 'if_lnc.ko' ? 
Cc: current@FreeBSD.ORG
In-reply-to: Your message of "Thu, 21 Dec 2000 10:26:12 +0900."
		<20001221102612F.matusita@jp.FreeBSD.org> 
References: <20001221102612F.matusita@jp.FreeBSD.org>  <20001221021801G.matusita@jp.FreeBSD.org> <200012201805.eBKI5is41536@billy-club.village.org> <200012201942.MAA10802@harmony.village.org> 
Date: Wed, 20 Dec 2000 18:42:39 -0700
From: Warner Losh <imp@village.org>
Sender: imp@harmony.village.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <20001221102612F.matusita@jp.FreeBSD.org> Makoto MATSUSHITA writes:
: Hmm, fixing these are beyond my skill...

I'll go ahead and fix it, or make sure it does.

: BTW, are there anybody working on 'pcn' (yet another lance driver) to
: work with VMware ? Current 5-current installation floppy makes VMware
: panic (caution: FreeBSD doesn't panic), and it is maybe caused by pcn
: driver when it knocks VMware pseudo ethernet device in 32bit mode.
: Note that FreeBSD 4-stable works well with VMware, so maybe there are
: hints in the differences between 4-stable and 5-current.

Can't help you on that.

Warner


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


From owner-freebsd-current  Wed Dec 20 19:11:54 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 19:11:52 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from citusc.usc.edu (citusc.usc.edu [128.125.38.123])
	by hub.freebsd.org (Postfix) with ESMTP
	id EB02137B400; Wed, 20 Dec 2000 19:11:47 -0800 (PST)
Received: (from kris@localhost)
	by citusc.usc.edu (8.9.3/8.9.3) id TAA23190;
	Wed, 20 Dec 2000 19:13:05 -0800
Date: Wed, 20 Dec 2000 19:13:05 -0800
From: Kris Kennaway <kris@FreeBSD.ORG>
To: Jeremy Lea <reg@FreeBSD.ORG>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: Is compatibility for old aout binaries broken?
Message-ID: <20001220191305.A23070@citusc.usc.edu>
References: <20001216161756.A6370@cae88-102-101.sc.rr.com> <200012171658.eBHGwGW24109@dungeon.home> <20001220005106.F41741@dragon.nuxi.com> <20001220035707.B3783@cae88-102-101.sc.rr.com> <20001220015223.H41741@dragon.nuxi.com> <20001220020520.P79112@shale.csir.co.za>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
	protocol="application/pgp-signature"; boundary="ikeVEW9yuYc//A+q"
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <20001220020520.P79112@shale.csir.co.za>; from reg@FreeBSD.ORG on Wed, Dec 20, 2000 at 02:05:20AM -0800
Sender: kris@citusc.usc.edu
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


--ikeVEW9yuYc//A+q
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Dec 20, 2000 at 02:05:20AM -0800, Jeremy Lea wrote:
> Hi,
>=20
> On Wed, Dec 20, 2000 at 01:52:23AM -0800, David O'Brien wrote:
> > Nope.  This is a box that was a virgin install of 5-CURRENT a month ago.
> > I had to install the compat20 and compat21 dists, along with doing a
> > ``pkg_add -r XFree86-aoutlibs''.  The Tk is 8.0.5.
>=20
> The XFree86-aoutlibs are especially from XFree86-3.3.3.  This was
> because of unstable behaviour from Netscape with later aout libs.
>=20
> They are obtained from:
> ftp://ftp.xfree86.org/pub/XFree86/3.3.3/binaries/FreeBSD-2.2.x/Xbin.tgz

Argh. I'm going to have to mark that port FORBIDDEN, then, because old
versions of the X libraries have remote vulnerabilities.

Kris

--ikeVEW9yuYc//A+q
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE6QXVBWry0BWjoQKURAlujAJ4yItXF6Sf+6+prQFvGst++JDdGngCg0Qg8
sK8edDMwHMZ2thwsPzSkZrw=
=5BIG
-----END PGP SIGNATURE-----

--ikeVEW9yuYc//A+q--


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


From owner-freebsd-current  Wed Dec 20 22:14:19 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 22:14:17 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5])
	by hub.freebsd.org (Postfix) with ESMTP
	id B38A337B402; Wed, 20 Dec 2000 22:14:09 -0800 (PST)
Received: from C992631-A.pinol1.sfba.home.com (C992631-A.pinol1.sfba.home.com [24.12.58.155])
	by shale.csir.co.za (8.9.3/8.9.3) with ESMTP id IAA80873;
	Thu, 21 Dec 2000 08:13:48 +0200 (SAT)
	(envelope-from reg@shale.csir.co.za)
Received: (from reg@localhost)
	by C992631-A.pinol1.sfba.home.com (8.11.0/8.11.0) id eBL6BXU45389;
	Wed, 20 Dec 2000 22:11:33 -0800 (PST)
	(envelope-from reg)
Date: Wed, 20 Dec 2000 22:11:33 -0800
From: Jeremy Lea <reg@FreeBSD.ORG>
To: Kris Kennaway <kris@FreeBSD.ORG>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: Is compatibility for old aout binaries broken?
Message-ID: <20001220221132.S79112@shale.csir.co.za>
Mail-Followup-To: Jeremy Lea <reg@FreeBSD.org>,
	Kris Kennaway <kris@FreeBSD.ORG>, freebsd-current@FreeBSD.ORG
References: <20001216161756.A6370@cae88-102-101.sc.rr.com> <200012171658.eBHGwGW24109@dungeon.home> <20001220005106.F41741@dragon.nuxi.com> <20001220035707.B3783@cae88-102-101.sc.rr.com> <20001220015223.H41741@dragon.nuxi.com> <20001220020520.P79112@shale.csir.co.za> <20001220191305.A23070@citusc.usc.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20001220191305.A23070@citusc.usc.edu>; from kris@FreeBSD.ORG on Wed, Dec 20, 2000 at 07:13:05PM -0800
Sender: reg@shale.csir.co.za
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

On Wed, Dec 20, 2000 at 07:13:05PM -0800, Kris Kennaway wrote:
> Argh. I'm going to have to mark that port FORBIDDEN, then, because old
> versions of the X libraries have remote vulnerabilities.

Hmmm...  Are there patches available to just fix the security problems? 
We can't move much beyond 3.3.3 because Netscape's released aout
binaries have workarounds for bugs from before then, which cause them to
be unstable when those bugs are fixed.

Else, I guess we are stuck with netscape-linux or mozilla...  And people
keep breaking mozilla...

Regards,
 -Jeremy

-- 
FreeBSD - Because the best things in life are free...
                                           http://www.freebsd.org/


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


From owner-freebsd-current  Wed Dec 20 22:35:28 2000
From owner-freebsd-current@FreeBSD.ORG  Wed Dec 20 22:35:25 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0B9BF37B402; Wed, 20 Dec 2000 22:35:16 -0800 (PST)
Received: (from jhay@localhost)
	by zibbi.icomtek.csir.co.za (8.11.0/8.11.0) id eBL6Z7e95656;
	Thu, 21 Dec 2000 08:35:07 +0200 (SAT)
	(envelope-from jhay)
From: John Hay <jhay@icomtek.csir.co.za>
Message-Id: <200012210635.eBL6Z7e95656@zibbi.icomtek.csir.co.za>
Subject: Re: Is compatibility for old aout binaries broken?
In-Reply-To: <20001220221132.S79112@shale.csir.co.za> from Jeremy Lea at "Dec 20, 2000 10:11:33 pm"
To: reg@FreeBSD.ORG (Jeremy Lea)
Date: Thu, 21 Dec 2000 08:35:07 +0200 (SAT)
Cc: kris@FreeBSD.ORG (Kris Kennaway), freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: jhay@zibbi.icomtek.csir.co.za
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 
> On Wed, Dec 20, 2000 at 07:13:05PM -0800, Kris Kennaway wrote:
> > Argh. I'm going to have to mark that port FORBIDDEN, then, because old
> > versions of the X libraries have remote vulnerabilities.
> 
> Hmmm...  Are there patches available to just fix the security problems? 
> We can't move much beyond 3.3.3 because Netscape's released aout
> binaries have workarounds for bugs from before then, which cause them to
> be unstable when those bugs are fixed.

Maybe we should find out who the good guy is that is building the FreeBSD
versions of Netscape and help him upgrade his version of FreeBSD or get
him a new machine with FreeBSD 4.2 on it?

> 
> Else, I guess we are stuck with netscape-linux or mozilla...  And people
> keep breaking mozilla...

Well there is the bsdi version too...

John
-- 
John Hay -- John.Hay@icomtek.csir.co.za


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


From owner-freebsd-current  Thu Dec 21 12:35:33 2000
From owner-freebsd-current@FreeBSD.ORG  Thu Dec 21 12:35:31 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mail.interware.hu (mail.interware.hu [195.70.32.130])
	by hub.freebsd.org (Postfix) with ESMTP id 1835137B400
	for <current@freebsd.org>; Thu, 21 Dec 2000 12:35:30 -0800 (PST)
Received: from pretoria-57.budapest.interware.hu ([195.70.53.121] helo=elischer.org)
	by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian))
	id 149CQx-00005V-00
	for <current@freebsd.org>; Thu, 21 Dec 2000 21:35:27 +0100
Sender: julian@FreeBSD.ORG
Message-ID: <3A425F75.77443BCD@elischer.org>
Date: Thu, 21 Dec 2000 11:52:21 -0800
From: Julian Elischer <julian@elischer.org>
X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386)
X-Accept-Language: en, hu
MIME-Version: 1.0
To: current@freebsd.org
Subject: vi ! command broken by tcsh?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In vi it is no longer convenient to call processign filters on text being
written because something has changed..

For example to adjust the formatting of the paragraph you are presently in, you
would type !}fmt and the paragraph would be piped out to fmt and the resulting
output would be brought back and would replace the original. Very useful. for
example you can sort a list of items  with !}sort .

Unfortunatly something is trying to do an 'stty' command on the pipe, and the
result now always includes the line:
stty: stdin isn't a terminal
followed by the formatted text..

{after some more experimentation}
it appears to be the new csh.
(tcsh)

the old csh worked, and if I set teh shell to be sh it works.
It's only tcsh that doesn't like this.

This is to say the least, a pain because after you hve deleted the bad line you
cannot use '.'
to format the next paragraph...

I'll add a PR tomorow if there is no quick answer.. I don't know if it's in 4.x
as well...

-- 
      __--_|\  Julian Elischer
     /       \ julian@elischer.org
    (   OZ    ) World tour 2000
---> X_.---._/  presently in:  Budapest
            v



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


From owner-freebsd-current  Thu Dec 21 13:39:19 2000
From owner-freebsd-current@FreeBSD.ORG  Thu Dec 21 13:39:16 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mail.interware.hu (mail.interware.hu [195.70.32.130])
	by hub.freebsd.org (Postfix) with ESMTP id 8561C37B402
	for <current@freebsd.org>; Thu, 21 Dec 2000 13:39:15 -0800 (PST)
Received: from pretoria-57.budapest.interware.hu ([195.70.53.121] helo=elischer.org)
	by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian))
	id 149DQf-0006AT-00; Thu, 21 Dec 2000 22:39:14 +0100
Sender: julian@FreeBSD.ORG
Message-ID: <3A42784E.88091BD9@elischer.org>
Date: Thu, 21 Dec 2000 13:38:22 -0800
From: Julian Elischer <julian@elischer.org>
X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386)
X-Accept-Language: en, hu
MIME-Version: 1.0
To: Brooks Davis <brooks@one-eyed-alien.net>, current@freebsd.org
Subject: Re: vi ! command broken by tcsh?
References: <3A425F75.77443BCD@elischer.org> <20001221132123.B25427@Odin.AC.HMC.Edu>
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Brooks Davis wrote:
> 
[my stupid stuff deleted]
> 
> It sounds like you've got an stty command in your .{,t}cshrc.  There
> aren't any in the default dot files.  It should be fine if you move it
> to your .login instead.  If that's the case, this might still be a bug
> though.  It !}fmt works fine for me with /bin/tcsh as my shell with a
> Nov 21 -current.

THANKYOU!!!!

I just completely forgot that .cshrc would be used up by this sort of thing.

I've moved it to .login
pilot error I guess.....

send that pointy hat over here to Budapest!



-- 
      __--_|\  Julian Elischer
     /       \ julian@elischer.org
    (   OZ    ) World tour 2000
---> X_.---._/  presently in:  Budapest
            v


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


From owner-freebsd-current  Thu Dec 21 13:57:29 2000
From owner-freebsd-current@FreeBSD.ORG  Thu Dec 21 13:57:26 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from falla.videotron.net (falla.videotron.net [205.151.222.106])
	by hub.freebsd.org (Postfix) with ESMTP id 5452A37B400
	for <freebsd-current@freebsd.org>; Thu, 21 Dec 2000 13:57:26 -0800 (PST)
Received: from modemcable213.3-201-24.mtl.mc.videotron.ca ([24.201.3.213])
 by falla.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8)
 with ESMTP id <0G5X00G4RUBNTK@falla.videotron.net> for freebsd-current@freebsd.org; Thu,
 21 Dec 2000 16:57:23 -0500 (EST)
Date: Thu, 21 Dec 2000 16:58:20 -0500 (EST)
From: Bosko Milekic <bmilekic@technokratis.com>
Subject: mini HEADS-UP: M_WAIT renamed to M_TRYWAIT
To: freebsd-current@freebsd.org
Message-id: <Pine.BSF.4.21.0012211651330.20908-100000@jehovah.technokratis.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


 Hello, this is a mini-HEADSUP mainly targeted at those working on the
 kernel source in FreeBSD-CURRENT.

In short, for the mbuf subsystem:

  M_WAIT is now deprecated and M_TRYWAIT should be used in its place.


Summary:

  	This ONLY applies to allocations for the "mbuf subsystem" and NOT any
  allocations with malloc() or any other subsystems:
  
  The M_WAIT flag has been renamed to M_TRYWAIT. The commit message
  explains the reason for the rename. It basically has to do with the
  developer needing to check whether calls to m_get(), m_gethdr() (and
  their macro equivalents MGET and MGETHDR) as well as calls to the mbuf
  cluster allocation routines and macros return a NULL pointer. In other
  words, even calls with M_(TRYWAIT) may fail in allocating mbufs or mbuf
  clusters and therefore must be accompanied by a check for that failure.

  This has been the case for a while and the time spent blocking/waiting
  for resources is tunable with the kern.ipc.mbuf_wait sysctl. The flag
  name has been changed in an effort to "communicate the right message" to
  developers, especially those porting code from NetBSD and OpenBSD where
  M_WAIT means "block indefinetely if you can't get me anything."

  M_WAIT is now deprecated and M_TRYWAIT should be used in its place.

  Happy Holidays!

  Bosko Milekic
  bmilekic@technokratis.com




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


From owner-freebsd-current  Fri Dec 22  6: 1:30 2000
From owner-freebsd-current@FreeBSD.ORG  Fri Dec 22 06:01:28 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id EE80637B400; Fri, 22 Dec 2000 06:01:27 -0800 (PST)
Received: from sunfin.Finland.Sun.COM ([129.159.101.10])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA00290;
	Fri, 22 Dec 2000 06:01:25 -0800 (PST)
Received: from ultrahot.Finland.Sun.COM (ultrahot [129.159.101.87])
	by sunfin.Finland.Sun.COM (8.8.8+Sun/8.8.8/ENSMAIL,v1.9) with ESMTP id QAA12352;
	Fri, 22 Dec 2000 16:01:06 +0200 (EET)
Received: (from tomppa@localhost)
	by ultrahot.Finland.Sun.COM (8.9.3/8.9.3) id QAA06592;
	Fri, 22 Dec 2000 16:01:05 +0200 (EET)
From: Tomi Vainio - Sun Finland - <Tomi.Vainio@Sun.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14915.24225.318167.916886@ultrahot.Finland.Sun.COM>
Date: Fri, 22 Dec 2000 16:01:05 +0200
To: freebsd-current@FreeBSD.ORG
Cc: msmith@FreeBSD.ORG
Subject: ffs_valloc: dup alloc panics with stable/current
In-Reply-To: <14896.15612.659070.165662@ultrahot.Finland.Sun.COM>
References: <14896.15612.659070.165662@ultrahot.Finland.Sun.COM>
X-Mailer: VM 6.76 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
Reply-To: Tomi.Vainio@Sun.COM
Sender: Tomi.Vainio@finland.sun.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Tomi Vainio - Sun Finland - writes:
 > 
 > We got old Mylex DAC960PD-Ultra-raid-adapter and have tried to use it
 > with FreeBSD 4.2-stable and 5.0-current. Adapter is configured with
 > three luns 5+5*9G, 8+8*9G (raid5) and 1+1*2G (mirrored boot disk).
 > All 9G disks are quite old Seagate Barracuda 9 disks ST19171W.  System
 > is working quite well but under heavier load we start to get scsi
 > errors from luns.
 > This is not so bad but 5-30 minutes after this command system will
 > always panic.
 > cd /uu ; dump 0buf 126 - /w | restore xbf 126 -
 > 
 > mode = 0100644, inum = 720391, fs = /uu
 > panic: ffs_valloc: dup alloc
 >
Hi,

I wrote about these problems two weeks ago.  After this we had done
lot of testing with this system and last 4 days system has been up and
running.  We still get scsi errors but it doesn't seem to harm system
drives.  Panic problem hasn't appeared since we changed mylex config.
Now we are running only 8 disks on two channels and one raid5 system
drive on both.  Any thoughts why this works better than the old
configuration?

  Tomppa
-- 
SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland
Tomi Vainio (System Support Engineer)     +358 9 52556300 hotline
email: Tomi.Vainio@Sun.COM                +358 9 52556252 fax


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


From owner-freebsd-current  Fri Dec 22  9:12: 1 2000
From owner-freebsd-current@FreeBSD.ORG  Fri Dec 22 09:11:55 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mail.vc-net.ne.jp (vs03.vc-net.ne.jp [210.255.128.10])
	by hub.freebsd.org (Postfix) with ESMTP
	id E6BD037B400; Fri, 22 Dec 2000 09:11:53 -0800 (PST)
Received: from computer (1Cust92.tnt1.kakogawa.jp.da.uu.net [63.12.94.92])
	by mail.vc-net.ne.jp (8.9.3/3.7W+vc-net_2.1) with SMTP id AAA24506;
	Sat, 23 Dec 2000 00:14:47 +0900 (JST)
Message-ID: <006d01c06c2b$36873cc0$5c5e0c3f@computer>
From: "grace" <grace@vc-net.ne.jp>
To: <Undisclosed-Recipient:;;@FreeBSD.ORG>
Subject: =?iso-2022-jp?B?GyRCIVYlYSE8JWslIiVJJWwlOUcvS3YlLSVjJXMlWiE8JXMhVxsoQg==?=
Date: Sat, 23 Dec 2000 00:08:50 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

$BFMA3$N%a!<%k@?$K<:NiCW$7$^$9(B
 $B6=L#$r$*;}$A$G$J$$>l9g$O!"@?$K62$lF~$j$^$9$,!":o=|$/$@$5$$(B
 $B$"$J$?$N!"%$%s%?!<%M%C%H%S%8%M%9$,!"$h$jHtLv$9$k$3$H$N<j=u$1$K$J$l$P$H!"(B
 $B:#2s$3$N$h$&$J>pJs$rAw$i$;$F$$$?$@$-$^$7$?(B

$B%$%s%?!<%M%C%H%a!<%k$O(B,$B$3$l$+$i$N%S%8%M%9$r?d?J$7$F$$$/$N$K(B
$BI,MWIT2D7g$J$b$N$G$9!#(B
$B%S%8%M%9$K8zN($h$/MxMQ$9$k$K$O!"BgNL$N!V%a!<%k%"%I%l%9!W(B
$B$,I,MW$H$J$j$^$9!#!!%$%s%?!<%M%C%H#D#M$N>l9g$O!"M9Aw$N#D#M(B
$B$KHf$Y$FHf3S$K$J$i$J$$$[$IHqMQ$,$+$+$j$^$;$s!#(B
$BM9Aw$N#D#M$G$O:N;;$,9g$o$J$$$H$"$-$i$a$F$$$kJ}$O!"$<$R(B
$B%$%s%?!<%M%C%H#D#M$r$48!F$2<$5$$!#(B
$B$-$C$H?7$7$$HNO)$,3+$+$l$k$H;W$$$^$9!#!!!!(B

$B8=:_!"!V%a!<%k%"%I%l%9G/Kv%-%c%s%Z!<%s!W$r9T$C$F$$$^$9!#(B

$B$3$N4|4VCf!"2<5-$N2A3J$G7c0BHNGd$5$;$F$$$?$@$$$F$$$^$9!#(B

 +++++++++++++++++++++++
$B!!(B  $B#1#2K|7o(B $B!!#1K|1_!!(B
    $B#2#5K|7o(B $B!!#2K|1_!!(B
    $B#5#0K|7o(B $B!!#3K|1_!!(B
$B!!#1#0#0K|7o!!(B $B#5K|1_(B
  $B#1#5#0K|7o!!(B $B#6K|1_(B
+++++++++++++++++++++++

$B$<$R$3$N5!2q$K$*Gc$$5a$a2<$5$$!#(B

$B!y(B $B9XF~4uK>$NJ}$O!V%a!<%k%"%I%l%9G/Kv%-%c%s%Z!<%s4uK>!W$H$7$F(B
$B!!!!!!%a!<%kKt$O#F#A#X!J(B0794-23-0601$B!K$K$F$*Ld$$9g$o$;2<$5$$!#(B
$B!!!!!!!!!!(Brevival@twics.com
$B!!!!!!!J$=$N$H$-$K!"7o?t!&2A3J$r$*CN$i$;2<$5$$!K(B
$B$4F~6bJ}K!!&>&IJ0z$-EO$7J}K!$J$I$r$*CN$i$;$$$?$7$^$9!#(B

$B!!!!!!!!!!!!!!!!!!!!!!!!!!!!J<8K8)2C8E@n;T2C8E@nD.2O86(B
$B!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!%j%P%$%P%k%M%C%H%o!<%/(B
$B!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!(B0794-23-0601




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


From owner-freebsd-current  Fri Dec 22 11:42:50 2000
From owner-freebsd-current@FreeBSD.ORG  Fri Dec 22 11:42:46 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from bps.eca-mail.org (c115139.upc-c.chello.nl [212.187.115.139])
	by hub.freebsd.org (Postfix) with ESMTP
	id EE54337B400; Fri, 22 Dec 2000 11:42:44 -0800 (PST)
Received: (from joost@localhost)
	by bps.eca-mail.org (8.11.1/8.11.1) id eBMJggO05347;
	Fri, 22 Dec 2000 20:42:42 +0100 (CET)
	(envelope-from joost)
Date: Fri, 22 Dec 2000 20:42:42 +0100 (CET)
From: Joost Bekkers <joost@bps.eca-mail.org>
Message-Id: <200012221942.eBMJggO05347@bps.eca-mail.org>
To: FreeBSD-gnats-submit@freebsd.org, FreeBSD-current@freebsd.org,
	joost@bps.eca-mail.org
Subject: bridge code doesn't work like the man page says
Reply-To: joost@bps.eca-mail.org
X-send-pr-version: 3.2
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


>Submitter-Id:   current-users
>Originator:     Joost Bekkers
>Organization:   
>Confidential:   no 
>Synopsis:       bridge/firewall doesn't work as in bridge(4)
>Severity:       serious
>Priority:       medium
>Category:       kern
>Release:        FreeBSD 4.2-RELEASE i386
>Class:          sw-bug
>Environment: 

	4.2 RELEASE with the options BRIDGE and IPFIREWALL.

>Description: 

	When using a kernel with BRIDGE and IPFIREWALL and not
	IPFIREWALL_DEFAULT_TO_ACCEPT, bridge(4) states all non-ip
	packets will not be forwarded. This is not true! All non-ip
	packets will be forwarded regardless of the firewall.

>How-To-Repeat: 

	make a kernel with BRIDGE and IPFIREWALL. generate non-ip
	(like arp or ipx) traffic and notice how it passes through
	the bridge.

>Fix: 

I've added some options to make the bridge/firewall combo usefull.

# $FreeBSD: src/sys/conf/options,v 1.191.2.20 2000/11/16 17:28:30 archie Exp $
*** conf/options~	Thu Dec 21 20:06:38 2000
--- conf/options	Thu Dec 21 13:04:05 2000
***************
*** 220,225 ****
--- 220,228 ----
  BOOTP_NFSV3		opt_bootp.h
  BOOTP_WIRED_TO		opt_bootp.h
  BRIDGE			opt_bdg.h
+ BRIDGE_IP_ONLY		opt_bdg.h
+ BRIDGE_ALLOW_ARP	opt_bdg.h
+ BRIDGE_ALLOW_RARP	opt_bdg.h
  ETHER_II		opt_ef.h
  ETHER_8023		opt_ef.h
  ETHER_8022		opt_ef.h



 * $FreeBSD: src/sys/net/bridge.c,v 1.16.2.6 2000/09/25 17:30:01 nsayer Exp $
*** net/bridge.c~	Thu Dec 21 20:04:45 2000
--- net/bridge.c	Thu Dec 21 20:44:41 2000
***************
*** 56,61 ****
--- 56,71 ----
   *    option BRIDGE
   * and then at runtime set the sysctl variable to enable bridging.
   *
+  * If you want to combine a bridge with a firewall:
+  *    option IPFIREWALL
+  * and since it usualy doesn't make a lot of sense to block ip and
+  * let all the other protocols pass freely, use
+  *    option BRIDGE_IP_ONLY
+  * And because arp (and sometimes rarp) can be extremely usefull in
+  * an ip network
+  *    option BRIDGE_ALLOW_ARP
+  *    option BRIDGE_ALLOW_RARP
+  *
   * Only one interface is supposed to have addresses set (but
   * there are no problems in practice if you set addresses for more
   * than one interface).
***************
*** 91,96 ****
--- 101,107 ----
  
  #include "opt_ipfw.h" 
  #include "opt_ipdn.h" 
+ #include "opt_bdg.h"
  
  #if defined(IPFIREWALL)
  #include <net/route.h>
***************
*** 445,450 ****
--- 456,474 ----
      bzero(ifp2sc, BDG_MAX_PORTS * sizeof(struct bdg_softc) );
  
      bzero(&bdg_stats, sizeof(bdg_stats) );
+ /* added by bps */
+     printf("BRIDGING ENABLED"
+ #ifdef BRIDGE_IP_ONLY
+            " protocols ip"  
+ #ifdef BRIDGE_ALLOW_ARP
+            ",arp"  
+ #endif
+ #ifdef BRIDGE_ALLOW_RARP
+            ",rarp"  
+ #endif
+            " only"
+ #endif
+ 	   "\n");
      bdgtakeifaces();
      bdg_timeout(0);
      do_bridge=0;
***************
*** 658,663 ****
--- 682,688 ----
  	struct ip_fw_chain *rule = NULL ;
  	int off;
  	struct ip *ip ;
+ 	u_short frame_type;
  
  	m = *m0 ;
  #ifdef DUMMYNET
***************
*** 678,685 ****
--- 703,729 ----
  	    goto forward ;
  	if (src == NULL)
  	    goto forward ; /* do not apply to packets from ether_output */
+ 	frame_type=ntohs(eh->ether_type);
+ #ifdef BRIDGE_ALLOW_ARP
+ 	if (frame_type == ETHERTYPE_ARP)
+ 	    goto forward ; /* BRIDGE_ALLOW_ARP is defined, so forward arp */
+ #endif
+ #ifdef BRIDGE_ALLOW_RARP
+ 	if (frame_type == ETHERTYPE_REVARP)
+ 	    goto forward ; /* BRIDGE_ALLOW_RARP is defined, so forward rarp */
+ #endif
  	if (ntohs(eh->ether_type) != ETHERTYPE_IP)
+ #ifdef BRIDGE_IP_ONLY	/* we're bridging IP (and maybe arp/rarp) only */
+ 	    {
+ 		if (canfree) {
+ 		    m_freem(*m0) ;
+ 		    *m0 = NULL ;
+ 		}
+ 		return 0;
+ 	    }
+ #else			/* we're bridging everything */
  	    goto forward ; /* not an IP packet, ipfw is not appropriate */
+ #endif
  	/*
  	 * In this section, canfree=1 means m is the same as *m0.
  	 * canfree==0 means m is a copy. We need to make a copy here


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


From owner-freebsd-current  Fri Dec 22 21: 6:39 2000
From owner-freebsd-current@FreeBSD.ORG  Fri Dec 22 21:06:37 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from pozo.com (pozo.com [216.101.162.50])
	by hub.freebsd.org (Postfix) with ESMTP id EF7D237B400
	for <current@freebsd.org>; Fri, 22 Dec 2000 21:06:36 -0800 (PST)
Received: from dual.pozo.com (dual.pozo.com [216.101.162.51])
	by pozo.com (8.11.1/8.11.1) with ESMTP id eBN56UI00293
	for <current@freebsd.org>; Fri, 22 Dec 2000 21:06:36 -0800 (PST)
	(envelope-from null@pozo.com)
Message-Id: <5.0.2.1.2.20001222210049.00a76558@pozo.com>
X-Sender: null@pozo.com
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Fri, 22 Dec 2000 21:06:29 -0800
To: current@freebsd.org
From: Manfred Antar <null@pozo.com>
Subject: New PCM changes cause panic
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

New changes to the sound system PCM
cause a panic on current kernel when using the rsynth port.

Fatal trap 18: integer divide fault while in kernel mode
cpuid = 1; lapic.id = 0c000000
instruction pointer     = 0x8:0xc01714d1
stack pointer           = 0x10:0xcb06fd90
frame pointer           = 0x10:0xcb06fdb0
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, def32 1, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 295 (say)
trap number             = 18
panic: integer divide fault
cpuid = 1; lapic.id = 0c000000
boot() called on cpu#1

syncing disks... 
Machine is frozen at this point.
Manual reset needed
Manfred


==================================
||      null@pozo.com           ||
||      Ph. (415) 681-6235      ||
==================================



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


From owner-freebsd-current  Fri Dec 22 21: 8:22 2000
From owner-freebsd-current@FreeBSD.ORG  Fri Dec 22 21:08:15 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from dsl081-020-229-sea1.dsl-isp.net (dsl081-020-229-sea1.dsl-isp.net [64.81.20.229])
	by hub.freebsd.org (Postfix) with ESMTP id B71D337B400
	for <current@FreeBSD.ORG>; Fri, 22 Dec 2000 21:08:14 -0800 (PST)
Received: (from tomdean@localhost)
	by dsl081-020-229-sea1.dsl-isp.net (8.11.1/8.11.1) id eBN58ER02749;
	Fri, 22 Dec 2000 21:08:14 -0800 (PST)
	(envelope-from tomdean@speakeasy.org)
Date: Fri, 22 Dec 2000 21:08:14 -0800 (PST)
Message-Id: <200012230508.eBN58ER02749@dsl081-020-229-sea1.dsl-isp.net>
X-Authentication-Warning: dsl081-020-229-sea1.dsl-isp.net: tomdean set sender to tomdean@speakeasy.org using -f
From: "Thomas D. Dean" <tomdean@speakeasy.org>
To: current@FreeBSD.ORG
Subject: Repeatable Hang -current SMP and lpd
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I tried to post this before, but, I think it got lost.

I have a repeatable hang with -current when attempting to print a
region from emacs.  This happened after 2 1/2 days uptime.  The system
is frozen.  The mouse does not move the pointer.  The keyboard does
nothing - pressing Caps Lock does not turn on the LED.

On reboot, the system halts with a fatal trap 12,
when lpd starts.  The system will not get past lpd starting until I
manually remove the files from /var/spool/lpd.  Several empty err
files are generated in /var/spool/lpd.

I am running -current SMP.

# uname -a
FreeBSD celebris 5.0-CURRENT FreeBSD 5.0-CURRENT #0: \
  Mon Dec 18 21:55:43 PST 2000 \
  root@celebris:/usr/src/sys/compile/CELEBRIS-SMP  i386

# uptime
 9:06PM  up 1 day,  9:44, 5 users, load averages: 0.00, 0.05, 0.08

Dmesg and my kernel config are attached.  What can I do to provide
more information?

tomdean

=== dmesg ===================
Copyright (c) 1992-2000 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
	The Regents of the University of California. All rights reserved.
FreeBSD 5.0-CURRENT #0: Mon Dec 18 21:55:43 PST 2000
    root@celebris:/usr/src/sys/compile/CELEBRIS-SMP
Timecounter "i8254"  frequency 1193023 Hz
CPU: Pentium/P54C (122.66-MHz 586-class CPU)
  Origin = "GenuineIntel"  Id = 0x525  Stepping = 5
  Features=0x3bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,APIC>
real memory  = 100663296 (98304K bytes)
avail memory = 94666752 (92448K bytes)
Programming 16 pins in IOAPIC #0
IOAPIC #0 intpin 2 -> irq 0
FreeBSD/SMP: Multiprocessor motherboard
 cpu0 (BSP): apic id:  0, version: 0x00030010, at 0xfee00000
 cpu1 (AP):  apic id:  1, version: 0x00030010, at 0xfee00000
 io0 (APIC): apic id:  2, version: 0x000f0011, at 0xfec00000
Preloaded elf kernel "kernel" at 0xc0322000.
Preloaded userconfig_script "/boot/kernel.conf" at 0xc03220a8.
Intel Pentium detected, installing workaround for F00F bug
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Host to PCI bridge> at pcibus 0 on motherboard
pci0: <PCI bus> on pcib0
ncr0: <ncr 53c810 fast10 scsi> port 0xec00-0xecff mem 0xfedfbf00-0xfedfbfff irq 11 at device 1.0 on pci0
isab0: <PCI-ISA bridge> at device 2.0 on pci0
isa0: <ISA bus> on isab0
vga_pci0: <VGA-compatible display device> mem 0xfe000000-0xfe7fffff,0xfedfc000-0xfedfffff irq 9 at device 6.0 on pci0
de0: <Digital 21041 Ethernet> port 0xe880-0xe8ff mem 0xfedfbe80-0xfedfbeff irq 10 at device 8.0 on pci0
de0: DEC DE450-CA 21041 [10Mb/s] pass 1.1
de0: address 00:00:f8:02:76:db
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
sc0: <System console> on isa0
sc0: VGA <16 virtual consoles, flags=0x200>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
unknown: <IBM Enhanced (101/102-key) KC> can't assign resources
unknown: <Microsoft PS/2 Mouse> can't assign resources
unknown: <16550 compatible COM device> can't assign resources
unknown: <16550 compatible COM device> can't assign resources
unknown: <LPT printer port> can't assign resources
unknown: <Floppy Controller> can't assign resources
APIC_IO: Testing 8254 interrupt delivery
APIC_IO: routing 8254 via IOAPIC #0 intpin 2
Waiting 10 seconds for SCSI devices to settle
de0: enabling 10baseT port
cd0 at ncr0 bus 0 target 5 lun 0
cd0: <TOSHIBA CD-ROM XM-5401TA 3605> Removable CD-ROM SCSI-2 device 
cd0: 4.237MB/s transfers (4.237MHz, offset 8)
cd0: cd present [329507 x 2048 byte records]
da2 at ncr0 bus 0 target 2 lun 0
da2: <QUANTUM FIREBALL ST3.2S 0F0C> Fixed Direct Access SCSI-2 device 
da2: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled
da2: 3090MB (6328861 512 byte sectors: 255H 63S/T 393C)
da0 at ncr0 bus 0 target 0 lun 0
da0: <QUANTUM FIREBALL1080S 1Q09> Fixed Direct Access SCSI-2 device 
da0: 10.000MB/s transfers (10.000MHz, offset 8)
da0: 1042MB (2134305 512 byte sectors: 255H 63S/T 132C)
Mounting root from ufs:/dev/da1s1a
da1 at ncr0 bus 0 target 1 lun 0
da1: <IBM DNES-309170 SAH0> Fixed Direct Access SCSI-3 device 
da1: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled
da1: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C)
WARNING: / was not properly dismounted
SMP: AP CPU #1 Launched!
de0: enabling 10baseT port
microuptime() went backwards (74920.124631 -> 74920.-694771956)

=== conifg ===========
machine		i386
cpu		I586_CPU
ident		CELEBRIS
hints		"CELEBRIS.hints"
maxusers	50
# SMP kernel config file options:

# Required:
options         SMP                     # Symmetric MultiProcessor Kernel
options         APIC_IO                 # Symmetric (APIC) I/O

# Lets always enable the kernel debugger for SMP.
options		DDB
#makeoptions	DEBUG=-g


##################################################################

options		INET			#InterNETworking
options		FFS			#Berkeley Fast Filesystem
options		FFS_ROOT		#FFS usable as root device
options		NFS			#Network Filesystem
options		MSDOSFS			#MSDOS Filesystem
options		"CD9660"		#ISO 9660 Filesystem
options		PROCFS			#Process filesystem
options		"COMPAT_43"		#Compatible with BSD 4.3 [KEEP THIS!]
options		SCSI_DELAY=10000	#Be pessimistic about Joe SCSI device
options		UCONSOLE		#Allow users to grab the console

options		MSGBUF_SIZE=(10*PAGE_SIZE) #System Message Buffer Size

options		SYSVSHM			# for X11
options		SYSVSEM			# for X11
options		SYSVMSG			# for X11

options         CLK_USE_I8254_CALIBRATION

device          random			#entropy device

#options	PSM_CHECKSYNC		# resync when switch console modes

#config		kernel	root on da1

device	isa
device	pci
#options         COMPAT_OLDPCI   #Use PCI shims and glue for old drivers


device	fdc
#
# FDC_DEBUG enables floppy debugging.  Since the debug output is huge, you
# gotta turn it actually on by setting the variable fd_debug with DDB,
# however.
options         FDC_DEBUG

#tape		ft0	at fdc0 drive 2

device	ncr

device	scbus

device		da	# SCSI Direct Access Device

device		sa	# SCSI Tape

device		cd	#Only need one of these, the code dynamically grows

# The keyboard device; it controlls the keyboard and the PS/2 mouse.
device	atkbdc

# The AT keyboard
device		atkbd

# `flags' for atkbd:
#       0x01    Force detection of keyboard, else we always assume a keyboard
#       0x02    Don't reset keyboard, useful for some newer ThinkPads
#       0x04    Old-style (XT) keyboard support, useful for older ThinkPads

device	psm

# The video card driver.
device		vga

# Splash screen at start up!  Screen savers require this too.
device	splash

# syscons is the default console driver, resembling an SCO console
device		sc

device		npx

device		sio

# Parallel-Port Bus
# nlpt	Parallel Printer
device	ppbus
device	lpt
device	ppc


device de	# DEC DC21040 Ethernet Adapter

device	loop
device	ether
device	tun	1
device  bpf	4      #Berkeley packet filter
device	vn		#Vnode driver (turns a file into a device)
device	pty	16
device	gzip		# Exec gzipped a.out's

# KTRACE enables the system-call tracing facility ktrace(2).
# This adds 4 KB bloat to your kernel, and slightly increases
# the costs of each syscall.
options		KTRACE		#kernel tracing


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


From owner-freebsd-current  Fri Dec 22 21:27:14 2000
From owner-freebsd-current@FreeBSD.ORG  Fri Dec 22 21:27:12 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
	by hub.freebsd.org (Postfix) with ESMTP id BBFFE37B400
	for <current@freebsd.org>; Fri, 22 Dec 2000 21:27:08 -0800 (PST)
Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71])
	by feral.com (8.9.3/8.9.3) with ESMTP id VAA24751
	for <current@freebsd.org>; Fri, 22 Dec 2000 21:27:17 -0800
Date: Fri, 22 Dec 2000 21:27:08 -0800 (PST)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: current@freebsd.org
Subject: is it possible to have a NULL procp for an NFS request?
Message-ID: <Pine.LNX.4.21.0012222125180.11318-100000@zeppo.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


I had a panic just now:

db> t
tprintf() at tprintf+0x7c
nfs_msg() at nfs_msg+0x28
nfs_timer() at nfs_timer+0x1fc
softclock() at softclock+0x4f4
sithd_loop() at sithd_loop+0x18c
exception_return() at exception_return


This is where it's saying the server isn't responding... and as best as I can
decode the assembly, the first argument to tprintf is NULL (a null
procp) which is passed straight through as rep->r_procp in
nfs_msg.

-matt




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


From owner-freebsd-current  Fri Dec 22 22: 3:23 2000
From owner-freebsd-current@FreeBSD.ORG  Fri Dec 22 22:03:21 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from assaris.sics.se (h122n4fls32o892.telia.com [213.64.47.122])
	by hub.freebsd.org (Postfix) with ESMTP id F145537B400
	for <current@FreeBSD.ORG>; Fri, 22 Dec 2000 22:03:20 -0800 (PST)
Received: (from assar@localhost)
	by assaris.sics.se (8.9.3/8.9.3) id HAA04149;
	Sat, 23 Dec 2000 07:03:11 +0100 (CET)
	(envelope-from assar)
Sender: assar@assaris.sics.se
To: mjacob@feral.com
Cc: current@FreeBSD.ORG
Subject: Re: is it possible to have a NULL procp for an NFS request?
References: <Pine.LNX.4.21.0012222125180.11318-100000@zeppo.feral.com>
From: Assar Westerlund <assar@FreeBSD.ORG>
Date: 23 Dec 2000 07:03:10 +0100
In-Reply-To: Matthew Jacob's message of "Fri, 22 Dec 2000 21:27:08 -0800 (PST)"
Message-ID: <5lelyzsmht.fsf@assaris.sics.se>
Lines: 32
User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Matthew Jacob <mjacob@feral.com> writes:
> I had a panic just now:
> 
> db> t
> tprintf() at tprintf+0x7c
> nfs_msg() at nfs_msg+0x28
> nfs_timer() at nfs_timer+0x1fc
> softclock() at softclock+0x4f4
> sithd_loop() at sithd_loop+0x18c
> exception_return() at exception_return

Yes, this is possible, (at least) when following symbolic links.  This
was discussed here on -current some time ago and I proposed the
appended simple patch, but I didn't get any feedback on it.

/assar

Index: nfs_socket.c
===================================================================
RCS file: /home/ncvs/src/sys/nfs/nfs_socket.c,v
retrieving revision 1.62
diff -u -w -u -w -r1.62 nfs_socket.c
--- nfs_socket.c	2000/11/26 20:35:21	1.62
+++ nfs_socket.c	2000/12/23 05:59:51
@@ -1969,6 +1969,7 @@
 	char *server, *msg;
 {
 
+	if (p != NULL)
 	tprintf(p, LOG_INFO, "nfs server %s: %s\n", server, msg);
 	return (0);
 }


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


From owner-freebsd-current  Fri Dec 22 23:30:50 2000
From owner-freebsd-current@FreeBSD.ORG  Fri Dec 22 23:30:47 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id D2BF437B400; Fri, 22 Dec 2000 23:30:45 -0800 (PST)
Received: from beppo (beppo [192.67.166.79])
	by feral.com (8.9.3/8.9.3) with ESMTP id XAA24952;
	Fri, 22 Dec 2000 23:30:54 -0800
Date: Fri, 22 Dec 2000 23:30:45 -0800 (PST)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: Assar Westerlund <assar@FreeBSD.ORG>
Cc: current@FreeBSD.ORG
Subject: Re: is it possible to have a NULL procp for an NFS request?
In-Reply-To: <5lelyzsmht.fsf@assaris.sics.se>
Message-ID: <Pine.BSF.4.21.0012222323430.74029-100000@beppo.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Hmm. The client wasn't following symlinks. The patch seems
simple enough, but it probably shouldn't just swallow the
error.

It looks like the last phk simplification lost some of the
functionality of the previous code- that I can fix.



On 23 Dec 2000, Assar Westerlund wrote:

> Matthew Jacob <mjacob@feral.com> writes:
> > I had a panic just now:
> > 
> > db> t
> > tprintf() at tprintf+0x7c
> > nfs_msg() at nfs_msg+0x28
> > nfs_timer() at nfs_timer+0x1fc
> > softclock() at softclock+0x4f4
> > sithd_loop() at sithd_loop+0x18c
> > exception_return() at exception_return
> 
> Yes, this is possible, (at least) when following symbolic links.  This
> was discussed here on -current some time ago and I proposed the
> appended simple patch, but I didn't get any feedback on it.
> 
> /assar
> 
> Index: nfs_socket.c
> ===================================================================
> RCS file: /home/ncvs/src/sys/nfs/nfs_socket.c,v
> retrieving revision 1.62
> diff -u -w -u -w -r1.62 nfs_socket.c
> --- nfs_socket.c	2000/11/26 20:35:21	1.62
> +++ nfs_socket.c	2000/12/23 05:59:51
> @@ -1969,6 +1969,7 @@
>  	char *server, *msg;
>  {
>  
> +	if (p != NULL)
>  	tprintf(p, LOG_INFO, "nfs server %s: %s\n", server, msg);
>  	return (0);
>  }
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
> 



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


From owner-freebsd-current  Fri Dec 22 23:44:27 2000
From owner-freebsd-current@FreeBSD.ORG  Fri Dec 22 23:44:25 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from assaris.sics.se (h122n4fls32o892.telia.com [213.64.47.122])
	by hub.freebsd.org (Postfix) with ESMTP id BF9E437B400
	for <current@FreeBSD.ORG>; Fri, 22 Dec 2000 23:44:24 -0800 (PST)
Received: (from assar@localhost)
	by assaris.sics.se (8.9.3/8.9.3) id IAA04670;
	Sat, 23 Dec 2000 08:44:20 +0100 (CET)
	(envelope-from assar)
Sender: assar@assaris.sics.se
To: mjacob@feral.com
Cc: current@FreeBSD.ORG
Subject: Re: is it possible to have a NULL procp for an NFS request?
References: <Pine.BSF.4.21.0012222323430.74029-100000@beppo.feral.com>
From: Assar Westerlund <assar@FreeBSD.ORG>
Date: 23 Dec 2000 08:44:19 +0100
In-Reply-To: Matthew Jacob's message of "Fri, 22 Dec 2000 23:30:45 -0800 (PST)"
Message-ID: <5lu27vlgz0.fsf@assaris.sics.se>
Lines: 13
User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Matthew Jacob <mjacob@feral.com> writes:
> Hmm. The client wasn't following symlinks.

You sure?  What happens is when you queue up an nfs operation provoked
by following a symlink.  I couldn't figure any other way of making
that happen.

> The patch seems simple enough, but it probably shouldn't just
> swallow the error.

Yeah, your patch to subr_prf.c is better.

/assar


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


From owner-freebsd-current  Fri Dec 22 23:56:57 2000
From owner-freebsd-current@FreeBSD.ORG  Fri Dec 22 23:56:55 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id E1BF037B400; Fri, 22 Dec 2000 23:56:54 -0800 (PST)
Received: from beppo (beppo [192.67.166.79])
	by feral.com (8.9.3/8.9.3) with ESMTP id XAA25014;
	Fri, 22 Dec 2000 23:57:03 -0800
Date: Fri, 22 Dec 2000 23:56:54 -0800 (PST)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: Assar Westerlund <assar@FreeBSD.ORG>
Cc: current@FreeBSD.ORG
Subject: Re: is it possible to have a NULL procp for an NFS request?
In-Reply-To: <5lu27vlgz0.fsf@assaris.sics.se>
Message-ID: <Pine.BSF.4.21.0012222356080.74167-100000@beppo.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


I'm pretty sure that the server had no symlinks in that filesystem.

On 23 Dec 2000, Assar Westerlund wrote:

> Matthew Jacob <mjacob@feral.com> writes:
> > Hmm. The client wasn't following symlinks.
> 
> You sure?  What happens is when you queue up an nfs operation provoked
> by following a symlink.  I couldn't figure any other way of making
> that happen.
> 
> > The patch seems simple enough, but it probably shouldn't just
> > swallow the error.
> 
> Yeah, your patch to subr_prf.c is better.

Well, it covers more. Sigh. Just pluggin' holes....



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


From owner-freebsd-current  Sat Dec 23  0: 0:25 2000
From owner-freebsd-current@FreeBSD.ORG  Sat Dec 23 00:00:21 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135])
	by hub.freebsd.org (Postfix) with ESMTP
	id 7FA5A37B400; Sat, 23 Dec 2000 00:00:21 -0800 (PST)
Received: (from dillon@localhost)
	by earth.backplane.com (8.11.1/8.9.3) id eBN80Le93546;
	Sat, 23 Dec 2000 00:00:21 -0800 (PST)
	(envelope-from dillon)
Date: Sat, 23 Dec 2000 00:00:21 -0800 (PST)
From: Matt Dillon <dillon@earth.backplane.com>
Message-Id: <200012230800.eBN80Le93546@earth.backplane.com>
To: Assar Westerlund <assar@FreeBSD.ORG>
Cc: mjacob@feral.com, current@FreeBSD.ORG
Subject: Re: is it possible to have a NULL procp for an NFS request?
References: <Pine.BSF.4.21.0012222323430.74029-100000@beppo.feral.com> <5lu27vlgz0.fsf@assaris.sics.se>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


:Matthew Jacob <mjacob@feral.com> writes:
:> Hmm. The client wasn't following symlinks.
:
:You sure?  What happens is when you queue up an nfs operation provoked
:by following a symlink.  I couldn't figure any other way of making
:that happen.
:
:> The patch seems simple enough, but it probably shouldn't just
:> swallow the error.
:
:Yeah, your patch to subr_prf.c is better.
:
:/assar

    Looking at the cvs logs it looks like Poul forgot to check for 
    p == NULL in his new simplified tprintf() API.   The 'sess' based
    tprintf did check for NULL.  The proc based tprintf does not.

    So fixing it in tprintf() itself, in subr_prf.c, is the right move.

						-Matt



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


From owner-freebsd-current  Sat Dec 23  0:24:53 2000
From owner-freebsd-current@FreeBSD.ORG  Sat Dec 23 00:24:52 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135])
	by hub.freebsd.org (Postfix) with ESMTP id E3B5637B400
	for <freebsd-current@freebsd.org>; Sat, 23 Dec 2000 00:24:51 -0800 (PST)
Received: (from dillon@localhost)
	by earth.backplane.com (8.11.1/8.9.3) id eBN8OpS93741;
	Sat, 23 Dec 2000 00:24:51 -0800 (PST)
	(envelope-from dillon)
Date: Sat, 23 Dec 2000 00:24:51 -0800 (PST)
From: Matt Dillon <dillon@earth.backplane.com>
Message-Id: <200012230824.eBN8OpS93741@earth.backplane.com>
To: freebsd-current@freebsd.org
Subject: Problem building -current kernel with read-only /usr/src.
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

    While trying to run 'make depend' in /usr/src/sys/compile/BLAH I got:

===> 3dfx
@ -> /FreeBSD/FreeBSD-current/src/sys
ln: @: Read-only file system
*** Error code 1

Stop in /FreeBSD/FreeBSD-current/src/sys/modules/3dfx.
*** Error code 1

    It looks like it's trying to mess around with something in /usr/src,
    which is a read-only NFS mount.  Needless to say we do not want to
    break being able to have a read-only /usr/src!

    Anyone been messing with the 3dfx module recently ?

						-Matt



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


From owner-freebsd-current  Sat Dec 23  0:50:45 2000
From owner-freebsd-current@FreeBSD.ORG  Sat Dec 23 00:50:43 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82])
	by hub.freebsd.org (Postfix) with ESMTP id C8F8C37B400
	for <freebsd-current@freebsd.org>; Sat, 23 Dec 2000 00:50:43 -0800 (PST)
Received: from rfx-64-6-211-149.users.reflexcom.com ([64.6.211.149]) by mailhost01.reflexnet.net  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Sat, 23 Dec 2000 00:49:05 -0800
Received: (from cjc@localhost)
	by rfx-64-6-211-149.users.reflexcom.com (8.11.0/8.11.0) id eBN8oft16937;
	Sat, 23 Dec 2000 00:50:41 -0800 (PST)
	(envelope-from cjc)
Date: Sat, 23 Dec 2000 00:50:41 -0800
From: "Crist J. Clark" <cjclark@reflexnet.net>
To: Matt Dillon <dillon@earth.backplane.com>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: Problem building -current kernel with read-only /usr/src.
Message-ID: <20001223005041.O96105@149.211.6.64.reflexcom.com>
Reply-To: cjclark@alum.mit.edu
References: <200012230824.eBN8OpS93741@earth.backplane.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <200012230824.eBN8OpS93741@earth.backplane.com>; from dillon@earth.backplane.com on Sat, Dec 23, 2000 at 12:24:51AM -0800
Sender: cjc@rfx-64-6-211-149.users.reflexcom.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, Dec 23, 2000 at 12:24:51AM -0800, Matt Dillon wrote:
>     While trying to run 'make depend' in /usr/src/sys/compile/BLAH I got:
> 
> ===> 3dfx
> @ -> /FreeBSD/FreeBSD-current/src/sys
> ln: @: Read-only file system
> *** Error code 1
> 
> Stop in /FreeBSD/FreeBSD-current/src/sys/modules/3dfx.
> *** Error code 1
> 
>     It looks like it's trying to mess around with something in /usr/src,
>     which is a read-only NFS mount.  Needless to say we do not want to
>     break being able to have a read-only /usr/src!
> 
>     Anyone been messing with the 3dfx module recently ?

Myself and a few others found debris in our /usr/src/sys
recently. Looks like it might be what you have there. None of us were
sure if it was us messing it up or trouble somewhere else.

Do a 'make cleandir' in your _source tree_ and try the build again.
-- 
Crist J. Clark                           cjclark@alum.mit.edu


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


From owner-freebsd-current  Sat Dec 23  4:23:34 2000
From owner-freebsd-current@FreeBSD.ORG  Sat Dec 23 04:23:33 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mass.osd.bsdi.com (adsl-63-202-177-107.dsl.snfc21.pacbell.net [63.202.177.107])
	by hub.freebsd.org (Postfix) with ESMTP id D44F937B404
	for <freebsd-current@freebsd.org>; Sat, 23 Dec 2000 04:23:32 -0800 (PST)
Received: from mass.osd.bsdi.com (localhost [127.0.0.1])
	by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBNCYKj10745;
	Sat, 23 Dec 2000 04:34:21 -0800 (PST)
	(envelope-from msmith@mass.osd.bsdi.com)
Message-Id: <200012231234.eBNCYKj10745@mass.osd.bsdi.com>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Matt Dillon <dillon@earth.backplane.com>
Cc: freebsd-current@freebsd.org
Subject: Re: Problem building -current kernel with read-only /usr/src. 
In-reply-to: Your message of "Sat, 23 Dec 2000 00:24:51 PST."
             <200012230824.eBN8OpS93741@earth.backplane.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 23 Dec 2000 04:34:20 -0800
From: Mike Smith <msmith@freebsd.org>
Sender: msmith@mass.osd.bsdi.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>     While trying to run 'make depend' in /usr/src/sys/compile/BLAH I got:
> 
> ===> 3dfx
> @ -> /FreeBSD/FreeBSD-current/src/sys
> ln: @: Read-only file system
> *** Error code 1
> 
> Stop in /FreeBSD/FreeBSD-current/src/sys/modules/3dfx.
> *** Error code 1
> 
>     It looks like it's trying to mess around with something in /usr/src,
>     which is a read-only NFS mount.  Needless to say we do not want to
>     break being able to have a read-only /usr/src!
> 
>     Anyone been messing with the 3dfx module recently ?

All the modules do this.  Remove "MODULES_WITH_WORLD" from your 
/etc/make.conf; they're not compatible with a read-only source tree.

-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
           V I C T O R Y   N O T   V E N G E A N C E




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


From owner-freebsd-current  Sat Dec 23  5: 7:32 2000
From owner-freebsd-current@FreeBSD.ORG  Sat Dec 23 05:07:31 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from peitho.fxp.org (peitho.fxp.org [209.26.95.40])
	by hub.freebsd.org (Postfix) with ESMTP id 0B5FD37B400
	for <freebsd-current@freebsd.org>; Sat, 23 Dec 2000 05:07:31 -0800 (PST)
Received: from earth.causticlabs.com (oca-c1s1-40.mfi.net [209.26.94.41])
	by peitho.fxp.org (Postfix) with ESMTP
	id 021A513612; Sat, 23 Dec 2000 08:07:29 -0500 (EST)
Received: by earth.causticlabs.com (Postfix, from userid 1000)
	id 81F071F5B; Sat, 23 Dec 2000 08:07:22 -0500 (EST)
Date: Sat, 23 Dec 2000 08:07:22 -0500
From: Chris Faulhaber <jedgar@fxp.org>
To: Matt Dillon <dillon@earth.backplane.com>
Cc: freebsd-current@freebsd.org
Subject: Re: Problem building -current kernel with read-only /usr/src.
Message-ID: <20001223080722.A28858@earth.causticlabs.com>
Mail-Followup-To: Chris Faulhaber <jedgar@fxp.org>,
	Matt Dillon <dillon@earth.backplane.com>, freebsd-current@freebsd.org
References: <200012230824.eBN8OpS93741@earth.backplane.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <200012230824.eBN8OpS93741@earth.backplane.com>; from dillon@earth.backplane.com on Sat, Dec 23, 2000 at 12:24:51AM -0800
Sender: jedgar@earth.causticlabs.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, Dec 23, 2000 at 12:24:51AM -0800, Matt Dillon wrote:
>     While trying to run 'make depend' in /usr/src/sys/compile/BLAH I got:
> 
> ===> 3dfx
> @ -> /FreeBSD/FreeBSD-current/src/sys
> ln: @: Read-only file system
> *** Error code 1
> 

Wouldn't using the buildkernel/installkernel targets be more appropriate
for a read-only source-tree?

-- 
Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org
--------------------------------------------------------
FreeBSD: The Power To Serve   -   http://www.FreeBSD.org


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


From owner-freebsd-current  Sat Dec 23  9:43:39 2000
From owner-freebsd-current@FreeBSD.ORG  Sat Dec 23 09:43:38 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135])
	by hub.freebsd.org (Postfix) with ESMTP id 89FB437B400
	for <freebsd-current@freebsd.org>; Sat, 23 Dec 2000 09:43:37 -0800 (PST)
Received: (from dillon@localhost)
	by earth.backplane.com (8.11.1/8.9.3) id eBNHhT797660;
	Sat, 23 Dec 2000 09:43:29 -0800 (PST)
	(envelope-from dillon)
Date: Sat, 23 Dec 2000 09:43:29 -0800 (PST)
From: Matt Dillon <dillon@earth.backplane.com>
Message-Id: <200012231743.eBNHhT797660@earth.backplane.com>
To: Chris Faulhaber <jedgar@fxp.org>
Cc: freebsd-current@freebsd.org
Subject: Re: Problem building -current kernel with read-only /usr/src.
References: <200012230824.eBN8OpS93741@earth.backplane.com> <20001223080722.A28858@earth.causticlabs.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


:
:On Sat, Dec 23, 2000 at 12:24:51AM -0800, Matt Dillon wrote:
:>     While trying to run 'make depend' in /usr/src/sys/compile/BLAH I got:
:> 
:> ===> 3dfx
:> @ -> /FreeBSD/FreeBSD-current/src/sys
:> ln: @: Read-only file system
:> *** Error code 1
:> 
:
:Wouldn't using the buildkernel/installkernel targets be more appropriate
:for a read-only source-tree?
:
:-- 
:Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org

    Tried using the buildkernel target, doesn't work either.

    I don't have MODULES_WITH_WORLD set in /etc/make.conf.

    I tried 'make cleandir' in /usr/src and that does not fix the problem
    either.

    Something got broken in the last week or two, it never did this sort
    of thing before.

						-Matt



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


From owner-freebsd-current  Sat Dec 23 10:42:23 2000
From owner-freebsd-current@FreeBSD.ORG  Sat Dec 23 10:42:21 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mail.jocose.org (mail.jocose.org [199.199.226.71])
	by hub.freebsd.org (Postfix) with SMTP id C8BE037B400
	for <freebsd-current@freebsd.org>; Sat, 23 Dec 2000 10:42:20 -0800 (PST)
Received: (qmail 25920 invoked by uid 1013); 23 Dec 2000 18:42:18 -0000
Date: Sat, 23 Dec 2000 12:42:18 -0600
From: Peter Schultz <pete@jocose.org>
To: freebsd-current@freebsd.org
Subject: gcc-devel and 5.0-current
Message-ID: <20001223124218.A25761@jocose.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: pete@mail.jocose.org
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

Just wondering if anyone has gotten make world
to work with this combo.  It is expected that
gcc 3.0 will become the default compiler for
FreeBSD 5.0?

Thanks,
Pete...



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


From owner-freebsd-current  Sat Dec 23 11:16:20 2000
From owner-freebsd-current@FreeBSD.ORG  Sat Dec 23 11:16:18 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135])
	by hub.freebsd.org (Postfix) with ESMTP
	id 13D6137B400; Sat, 23 Dec 2000 11:16:18 -0800 (PST)
Received: (from dillon@localhost)
	by earth.backplane.com (8.11.1/8.9.3) id eBNJGHV97973;
	Sat, 23 Dec 2000 11:16:17 -0800 (PST)
	(envelope-from dillon)
Date: Sat, 23 Dec 2000 11:16:17 -0800 (PST)
From: Matt Dillon <dillon@earth.backplane.com>
Message-Id: <200012231916.eBNJGHV97973@earth.backplane.com>
To: Mike Smith <msmith@FreeBSD.ORG>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: Problem building -current kernel with read-only /usr/src. 
References:  <200012231234.eBNCYKj10745@mass.osd.bsdi.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


:
:>     While trying to run 'make depend' in /usr/src/sys/compile/BLAH I got:
:> 
:> ===> 3dfx
:> @ -> /FreeBSD/FreeBSD-current/src/sys
:> ln: @: Read-only file system
:> *** Error code 1
:> 
:> Stop in /FreeBSD/FreeBSD-current/src/sys/modules/3dfx.
:> *** Error code 1
:> 
:>     It looks like it's trying to mess around with something in /usr/src,
:>     which is a read-only NFS mount.  Needless to say we do not want to
:>     break being able to have a read-only /usr/src!
:> 
:>     Anyone been messing with the 3dfx module recently ?
:
:All the modules do this.  Remove "MODULES_WITH_WORLD" from your 
:/etc/make.conf; they're not compatible with a read-only source tree.

    I've partially tracked it down to the ILINKS target in kmod.mk being
    run while in the wrong directory.  It SHOULD be in
    /FreeBSD/FreeBSD-current/src/sys/compile/TEST4/modules/3dfx 
    (aka /usr/src/sys/compile/TEST4/modules/3dfx).  But instead,
    when I echo `pwd` in the ILINKS target it appears to be cd'd into
    the main modules source directory:

mv -f .newdep .depend
find ../../modules -type d -a ! -name CVS  | sed -e "s|../../modules|modules|g" | xargs mkdir -p ;  cd ../../modules ; env MAKEOBJDIRPREFIX=/FreeBSD/FreeBSD-current/src/sys/compile/TEST4/modules KMODDIR=/boot/kernel make depend
===> 3dfx
@ -> /FreeBSD/FreeBSD-current/src/sys
/FreeBSD/FreeBSD-current/src/sys/modules/3dfx   <<<<<<<<<<<<<<<<<<<<<<<<<<<<
ln: @: Read-only file system
*** Error code 1

Stop in /FreeBSD/FreeBSD-current/src/sys/modules/3dfx.
*** Error code 1

Stop in /FreeBSD/FreeBSD-current/src/sys/modules.
    
    This is not right.  Someone did something to change the compile dir 
    as of the time the dependancies are run.  The cd in the 'find' sequence
    is correct

    It looks like someone blew up the making of the object directories under
    compile/TEST4/modules.  Under 4.x I had paths like this:

	/usr/src/sys/compile/TEST4/modules/FreeBSD/FreeBSD-current/usr/src/sys/modules/tx/....

    Under -current they are like this:

	/usr/src/sys/compile/TEST4/modules/tx/...

    The 'make' program can't find the object module directory any more.  Ahh..
    so maybe I should remake the make program, eh?  Tried that, doesn't work.

    Whoever 'fixed' object directory creation under /usr/src/sys/compile/BLAH
    for modules broke it instead.

						-Matt



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


From owner-freebsd-current  Sat Dec 23 11:24:53 2000
From owner-freebsd-current@FreeBSD.ORG  Sat Dec 23 11:24:51 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135])
	by hub.freebsd.org (Postfix) with ESMTP
	id B38C537B400; Sat, 23 Dec 2000 11:24:50 -0800 (PST)
Received: (from dillon@localhost)
	by earth.backplane.com (8.11.1/8.9.3) id eBNJOo798006;
	Sat, 23 Dec 2000 11:24:50 -0800 (PST)
	(envelope-from dillon)
Date: Sat, 23 Dec 2000 11:24:50 -0800 (PST)
From: Matt Dillon <dillon@earth.backplane.com>
Message-Id: <200012231924.eBNJOo798006@earth.backplane.com>
To: Mike Smith <msmith@FreeBSD.ORG>
Cc: freebsd-current@FreeBSD.ORG
Subject: found the fragger.  Re: Problem building -current kernel with read-only /usr/src. 
References:  <200012231234.eBNCYKj10745@mass.osd.bsdi.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

    Ok, I found it.  /usr/src/sys/conf/Makefile.i386 is broken.  It looks
    like either you or David O'Brien (I'm guessing, your guys names are 
    prominent in the CVS logs but I haven't tracked it down exactly)
    screwed up the object directory creation while trying to optimize it.

    It looks like it is trying to create short object directory names.
    But the make program can't find them when looking for object directories.

    This breaks MAKEOBJDIRPREFIX.  The 'make' program looks in:

                1.   ${MAKEOBJDIRPREFIX}/`pwd`
                2.   ${MAKEOBJDIR}
                3.   obj.${MACHINE}
                4.   obj
                5.   /usr/obj/`pwd`

		(taken from the 'make' man page)

    And NONE of these is the object path you create in the Makefile.

    This causes the make system to revert to tring to create the files
    in the source directory rather then the object directory.

						-Matt



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


From owner-freebsd-current  Sat Dec 23 11:40:14 2000
From owner-freebsd-current@FreeBSD.ORG  Sat Dec 23 11:40:11 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178])
	by hub.freebsd.org (Postfix) with ESMTP id 7408337B400
	for <freebsd-current@freebsd.org>; Sat, 23 Dec 2000 11:40:11 -0800 (PST)
Received: by peorth.iteration.net (Postfix, from userid 1001)
	id 9D0FF5749C; Sat, 23 Dec 2000 13:40:21 -0600 (CST)
Date: Sat, 23 Dec 2000 13:40:21 -0600
From: "Michael C . Wu" <keichii@iteration.net>
To: Peter Schultz <pete@jocose.org>
Cc: freebsd-current@freebsd.org
Subject: Re: gcc-devel and 5.0-current
Message-ID: <20001223134021.A79058@peorth.iteration.net>
Reply-To: "Michael C . Wu" <keichii@peorth.iteration.net>
Mail-Followup-To: "Michael C . Wu" <keichii@iteration.net>,
	Peter Schultz <pete@jocose.org>, freebsd-current@freebsd.org
References: <20001223124218.A25761@jocose.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20001223124218.A25761@jocose.org>; from pete@jocose.org on Sat, Dec 23, 2000 at 12:42:18PM -0600
X-PGP-Fingerprint: 5025 F691 F943 8128 48A8  5025 77CE 29C5 8FA1 2E20
X-PGP-Key-ID: 0x8FA12E20
Sender: keichii@peorth.iteration.net
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, Dec 23, 2000 at 12:42:18PM -0600, Peter Schultz scribbled:
| Just wondering if anyone has gotten make world
| to work with this combo.  It is expected that

No, and gcc-2.96 is broken enough.  In addition, we need wchar*
for gcc-3.  Even -O3 in gcc-2.95 is not supported/recommended.
You would be a brave soul to try this.

/me flees

| gcc 3.0 will become the default compiler for
| FreeBSD 5.0?

I highly doubt the feasibility of that.  Look at Redhat's blunder
with gcc-2.95.  The latest is not always the best, IMHO.

-- 
+------------------------------------------------------------------+
| keichii@peorth.iteration.net         | keichii@bsdconspiracy.net |
| http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. |
+------------------------------------------------------------------+


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


From owner-freebsd-current  Sat Dec 23 11:58:37 2000
From owner-freebsd-current@FreeBSD.ORG  Sat Dec 23 11:58:35 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1FBB137B402
	for <freebsd-current@freebsd.org>; Sat, 23 Dec 2000 11:58:35 -0800 (PST)
Received: from netcabo.pt (mail.netcabo.pt [212.113.161.135])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 55ECB6E2A2E
	for <freebsd-current@freebsd.org>; Sat, 23 Dec 2000 11:55:49 -0800 (PST)
Received: from netcabo.pt ([213.22.0.81]) by netcabo.pt  with Microsoft SMTPSVC(5.5.1877.537.53);
	 Sat, 23 Dec 2000 19:52:35 +0000
Sender: root@mx1.FreeBSD.org
Message-ID: <3A450339.A9CFDE8D@netcabo.pt>
Date: Sat, 23 Dec 2000 19:55:37 +0000
From: Joao Fernandes <OpsyDopsy@netcabo.pt>
Reply-To: OpsyDopsy@netcabo.pt
X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.0-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-current@freebsd.org
Subject: Kernel make depend error after CVSup
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

After having used CVSup for upgrading my 4.0-stable sources, I built the
world with no problems, but at making the depend for the new kernel
(using the GENERIC config file) it exited with error.

Here`s my CVSup config file:
*default host=cvsup.pt.FreeBSD.org
*default base=/usr
*default prefix=/usr
*default release=cvs tag=RELENG_4
*default delete use-rel-suffix
*default compress

Here`s the error it exited with:
===> accf_http
===> agp
make: don't know how to make agp_if.c. Stop
*** Error code 2
Stop in /usr/src/sys/modules.
*** Error code 1
Stop in /usr/src/sys/compile/GENERIC.

Can anyone help?

Thanks.

Joao Fernandes



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


From owner-freebsd-current  Sat Dec 23 12: 7:59 2000
From owner-freebsd-current@FreeBSD.ORG  Sat Dec 23 12:07:58 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38])
	by hub.freebsd.org (Postfix) with ESMTP id D223D37B400
	for <freebsd-current@FreeBSD.ORG>; Sat, 23 Dec 2000 12:07:57 -0800 (PST)
Received: from dragon.nuxi.com (Ipittythefoolthattrustsident@trang.nuxi.com [209.152.133.57])
	by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id MAA33708;
	Sat, 23 Dec 2000 12:07:57 -0800 (PST)
	(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
	by dragon.nuxi.com (8.11.1/8.11.1) id eBNK7u737164;
	Sat, 23 Dec 2000 12:07:56 -0800 (PST)
	(envelope-from obrien)
Date: Sat, 23 Dec 2000 12:07:55 -0800
From: "David O'Brien" <obrien@FreeBSD.ORG>
To: Matt Dillon <dillon@earth.backplane.com>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: found the fragger.  Re: Problem building -current kernel with read-only /usr/src.
Message-ID: <20001223120755.A37109@dragon.nuxi.com>
Reply-To: nobody@FreeBSD.ORG
References: <200012231234.eBNCYKj10745@mass.osd.bsdi.com> <200012231924.eBNJOo798006@earth.backplane.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <200012231924.eBNJOo798006@earth.backplane.com>; from dillon@earth.backplane.com on Sat, Dec 23, 2000 at 11:24:50AM -0800
X-Operating-System: FreeBSD 5.0-CURRENT
Organization: The NUXI BSD group
X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3  90 76 5D 69 58 D9 98 7A
X-Pgp-Rsa-Keyid: 1024/34F9F9D5
Sender: obrien@NUXI.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, Dec 23, 2000 at 11:24:50AM -0800, Matt Dillon wrote:
>     like either you or David O'Brien (I'm guessing, your guys names are 

I will fix it today.


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


From owner-freebsd-current  Sat Dec 23 12:35:44 2000
From owner-freebsd-current@FreeBSD.ORG  Sat Dec 23 12:35:43 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from tkk.att.ne.jp (tkk.att.ne.jp [165.76.176.5])
	by hub.freebsd.org (Postfix) with ESMTP id 257EA37B400
	for <current@freebsd.org>; Sat, 23 Dec 2000 12:35:39 -0800 (PST)
Received: from tkk.att.ne.jp (182.pool1.ipctokyo.att.ne.jp [165.76.245.182]) by tkk.att.ne.jp (8.8.8+Spin/3.6W-CONS(10/06/00)) id FAA20333; Sun, 24 Dec 2000 05:35:37 +0900 (JST)
Date: Sun, 24 Dec 2000 05:35:37 +0900 (JST)
Message-Id: <200012232035.FAA20333@tkk.att.ne.jp>
To: current@freebsd.org
Subject: =?ISO-2022-JP?B?GyRCJCIkSiQ/JEAkMSRLISYhJhsoQg==?=
From: Santa Claus <tosisan@tkk.att.ne.jp>
Mime-Version: 1.0
Content-Type: text/plain; Charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


$B$$$D$b7G<(HD!&=P2q$$7O!&%a!<%k%U%l%s%I%5%$%H$r$4MxMQBW$-(B
$BM-$jFq$&$4$6$$$^$9!#(B

$BK\F|$O!%!%!%!!$"$J$?$@$1$K(B
$B?7$7$$%5%$%H$N$40FFb$r$5$;$F$$$?$@$-$^$9!#(B

      http://cuz.power.ne.jp/aiko/

$B$b$7!"$4ITMW$G$7$?$i:o=|$7$F2<$5$$!#(B
$B:#8e!"$3$N%a!<%k$,$4ITMW$J>l9g$O!"(B
$B$*<j?t$G$9$,JV?.$^$?$O(B tosisan@tkk.att.ne.jp $B08(B
$B$*Aw$jBW$1$l$P!"<!2s$h$j:o=|CW$7$^$9!#(B
$B!J;~4V:9$K$h$j=EJ#$9$k>l9g$,$"$j$^$9!K(B

tosisan@tkk.att.ne.jp


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


From owner-freebsd-current  Sat Dec 23 13: 6:17 2000
From owner-freebsd-current@FreeBSD.ORG  Sat Dec 23 13:06:16 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82])
	by hub.freebsd.org (Postfix) with ESMTP id EFD6E37B400
	for <freebsd-current@freebsd.org>; Sat, 23 Dec 2000 13:06:15 -0800 (PST)
Received: from rfx-64-6-211-149.users.reflexcom.com ([64.6.211.149]) by mailhost01.reflexnet.net  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Sat, 23 Dec 2000 13:04:37 -0800
Received: (from cjc@localhost)
	by rfx-64-6-211-149.users.reflexcom.com (8.11.0/8.11.0) id eBNL6DR25185;
	Sat, 23 Dec 2000 13:06:13 -0800 (PST)
	(envelope-from cjc)
Date: Sat, 23 Dec 2000 13:06:13 -0800
From: "Crist J. Clark" <cjclark@reflexnet.net>
To: Matt Dillon <dillon@earth.backplane.com>
Cc: Chris Faulhaber <jedgar@fxp.org>, freebsd-current@FreeBSD.ORG
Subject: Re: Problem building -current kernel with read-only /usr/src.
Message-ID: <20001223130613.R96105@149.211.6.64.reflexcom.com>
Reply-To: cjclark@alum.mit.edu
References: <200012230824.eBN8OpS93741@earth.backplane.com> <20001223080722.A28858@earth.causticlabs.com> <200012231743.eBNHhT797660@earth.backplane.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <200012231743.eBNHhT797660@earth.backplane.com>; from dillon@earth.backplane.com on Sat, Dec 23, 2000 at 09:43:29AM -0800
Sender: cjc@rfx-64-6-211-149.users.reflexcom.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, Dec 23, 2000 at 09:43:29AM -0800, Matt Dillon wrote:

[snip]

>     I tried 'make cleandir' in /usr/src and that does not fix the problem
>     either.

Sorry, I was not clear enough. You need to do,

  # cd /usr/src/sys/modules
  # make cleandir

A 'cleandir' from /usr/src will not climb up into the modules.
-- 
Crist J. Clark                           cjclark@alum.mit.edu


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


From owner-freebsd-current  Sat Dec 23 13:21:37 2000
From owner-freebsd-current@FreeBSD.ORG  Sat Dec 23 13:21:36 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5C13E37B400; Sat, 23 Dec 2000 13:21:36 -0800 (PST)
Received: (from dillon@localhost)
	by earth.backplane.com (8.11.1/8.9.3) id eBNLLaw98370;
	Sat, 23 Dec 2000 13:21:36 -0800 (PST)
	(envelope-from dillon)
Date: Sat, 23 Dec 2000 13:21:36 -0800 (PST)
From: Matt Dillon <dillon@earth.backplane.com>
Message-Id: <200012232121.eBNLLaw98370@earth.backplane.com>
To: "David O'Brien" <obrien@FreeBSD.ORG>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: found the fragger.  Re: Problem building -current kernel with read-only /usr/src.
References: <200012231234.eBNCYKj10745@mass.osd.bsdi.com> <200012231924.eBNJOo798006@earth.backplane.com> <20001223120755.A37109@dragon.nuxi.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


:I will fix it today.
:

    Thanks a lot Dave!

					-Matt


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


From owner-freebsd-current  Sat Dec 23 14: 0:31 2000
From owner-freebsd-current@FreeBSD.ORG  Sat Dec 23 14:00:29 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5])
	by hub.freebsd.org (Postfix) with ESMTP id 3B6AA37B400
	for <freebsd-current@FreeBSD.ORG>; Sat, 23 Dec 2000 14:00:26 -0800 (PST)
Received: from C992631-A.pinol1.sfba.home.com (C992631-A.pinol1.sfba.home.com [24.12.58.155])
	by shale.csir.co.za (8.9.3/8.9.3) with ESMTP id AAA07632;
	Sun, 24 Dec 2000 00:00:16 +0200 (SAT)
	(envelope-from reg@shale.csir.co.za)
Received: (from reg@localhost)
	by C992631-A.pinol1.sfba.home.com (8.11.1/8.11.1) id eBNM0Ea98228;
	Sat, 23 Dec 2000 14:00:14 -0800 (PST)
	(envelope-from reg)
Date: Sat, 23 Dec 2000 14:00:13 -0800
From: Jeremy Lea <reg@FreeBSD.ORG>
To: Matt Dillon <dillon@earth.backplane.com>
Cc: Chris Faulhaber <jedgar@fxp.org>, freebsd-current@FreeBSD.ORG
Subject: Re: Problem building -current kernel with read-only /usr/src.
Message-ID: <20001223140013.A85385@shale.csir.co.za>
Mail-Followup-To: Jeremy Lea <reg@FreeBSD.org>,
	Matt Dillon <dillon@earth.backplane.com>,
	Chris Faulhaber <jedgar@fxp.org>, freebsd-current@FreeBSD.ORG
References: <200012230824.eBN8OpS93741@earth.backplane.com> <20001223080722.A28858@earth.causticlabs.com> <200012231743.eBNHhT797660@earth.backplane.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <200012231743.eBNHhT797660@earth.backplane.com>; from dillon@earth.backplane.com on Sat, Dec 23, 2000 at 09:43:29AM -0800
Sender: reg@shale.csir.co.za
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

On Sat, Dec 23, 2000 at 09:43:29AM -0800, Matt Dillon wrote:
>     Something got broken in the last week or two, it never did this sort
>     of thing before.

David's speedup commits to sys/conf/Makefile.*.  I informed him of the
problem, and asked him to back out the hacks, but he wants the
speedup...

Regards,
 -Jeremy

-- 
FreeBSD - Because the best things in life are free...
                                           http://www.freebsd.org/


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


From owner-freebsd-current  Sat Dec 23 14:33:33 2000
From owner-freebsd-current@FreeBSD.ORG  Sat Dec 23 14:33:30 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mailhub.iastate.edu (mailhub.iastate.edu [129.186.1.102])
	by hub.freebsd.org (Postfix) with ESMTP id 1F20A37B402
	for <freebsd-current@freebsd.org>; Sat, 23 Dec 2000 14:33:30 -0800 (PST)
Received: from iastate.edu ([129.186.232.231])
	by mailhub.iastate.edu (8.9.3/8.9.3) with ESMTP id QAA31371;
	Sat, 23 Dec 2000 16:33:22 -0600
Sender: ccsanady@iastate.edu
Message-ID: <3A452832.2D9B6C0E@iastate.edu>
Date: Sat, 23 Dec 2000 16:33:22 -0600
From: Chris <ccsanady@iastate.edu>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Matt Dillon <dillon@earth.backplane.com>
Cc: freebsd-current@freebsd.org
Subject: Re: Problem building -current kernel with read-only /usr/src.
References: <200012230824.eBN8OpS93741@earth.backplane.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Actually, last time I checked, I think stable did not install with a RO
/usr/src either.  Anyone know if this is still the case?

Chris

>     It looks like it's trying to mess around with something in /usr/src,
>     which is a read-only NFS mount.  Needless to say we do not want to
>     break being able to have a read-only /usr/src!
> 
>     Anyone been messing with the 3dfx module recently ?
> 
>                                                 -Matt
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message


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


From owner-freebsd-current  Sat Dec 23 15: 1:55 2000
From owner-freebsd-current@FreeBSD.ORG  Sat Dec 23 15:01:54 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162])
	by hub.freebsd.org (Postfix) with SMTP id 93C6037B400
	for <freebsd-current@freebsd.org>; Sat, 23 Dec 2000 15:01:53 -0800 (PST)
Received: (qmail 60350 invoked by uid 1001); 23 Dec 2000 23:01:50 +0000 (GMT)
To: ccsanady@iastate.edu
Cc: dillon@earth.backplane.com, freebsd-current@freebsd.org
Subject: Re: Problem building -current kernel with read-only /usr/src.
From: sthaug@nethelp.no
In-Reply-To: Your message of "Sat, 23 Dec 2000 16:33:22 -0600"
References: <3A452832.2D9B6C0E@iastate.edu>
X-Mailer: Mew version 1.05+ on Emacs 19.34.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Date: Sun, 24 Dec 2000 00:01:50 +0100
Message-ID: <60348.977612510@verdi.nethelp.no>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Actually, last time I checked, I think stable did not install with a RO
> /usr/src either.  Anyone know if this is still the case?

I have installed -stable many times with /usr/src mounted readonly
via NFS.

Steinar Haug, Nethelp consulting, sthaug@nethelp.no


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


From owner-freebsd-current  Sat Dec 23 16:14:39 2000
From owner-freebsd-current@FreeBSD.ORG  Sat Dec 23 16:14:38 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135])
	by hub.freebsd.org (Postfix) with ESMTP id 50F7137B400
	for <freebsd-current@freebsd.org>; Sat, 23 Dec 2000 16:14:38 -0800 (PST)
Received: (from dillon@localhost)
	by earth.backplane.com (8.11.1/8.9.3) id eBO0E3998784;
	Sat, 23 Dec 2000 16:14:03 -0800 (PST)
	(envelope-from dillon)
Date: Sat, 23 Dec 2000 16:14:03 -0800 (PST)
From: Matt Dillon <dillon@earth.backplane.com>
Message-Id: <200012240014.eBO0E3998784@earth.backplane.com>
To: sthaug@nethelp.no
Cc: ccsanady@iastate.edu, freebsd-current@freebsd.org
Subject: Re: Problem building -current kernel with read-only /usr/src.
References: <3A452832.2D9B6C0E@iastate.edu> <60348.977612510@verdi.nethelp.no>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


:
:> Actually, last time I checked, I think stable did not install with a RO
:> /usr/src either.  Anyone know if this is still the case?
:
:I have installed -stable many times with /usr/src mounted readonly
:via NFS.
:
:Steinar Haug, Nethelp consulting, sthaug@nethelp.no

   Yah, -stable is fine.  I've done the same.  Most recently two days ago.

					-Matt



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


From owner-freebsd-current  Sat Dec 23 16:20: 9 2000
From owner-freebsd-current@FreeBSD.ORG  Sat Dec 23 16:20:04 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from ns.internet.dk (ns.internet.dk [194.19.140.1])
	by hub.freebsd.org (Postfix) with ESMTP id BA74C37B402
	for <freebsd-current@FreeBSD.ORG>; Sat, 23 Dec 2000 16:20:03 -0800 (PST)
Received: (from uucp@localhost)
	by ns.internet.dk (8.11.1/8.11.1) with UUCP id eBO0K1x47686
	for freebsd-current@FreeBSD.ORG; Sun, 24 Dec 2000 01:20:01 +0100 (CET)
	(envelope-from leifn@neland.dk)
Received: from gina (gina.neland.dk [192.168.0.14])
	by arnold.neland.dk (8.11.0/8.11.0) with SMTP id eBO0Jiw71382
	for <freebsd-current@FreeBSD.ORG>; Sun, 24 Dec 2000 01:19:45 +0100 (CET)
	(envelope-from leifn@neland.dk)
Message-ID: <01b401c06d3f$99f7e060$0e00a8c0@neland.dk>
Reply-To: "Leif Neland" <leif@neland.dk>
From: "Leif Neland" <leifn@neland.dk>
To: <freebsd-current@FreeBSD.ORG>
Subject: making sendmail with milter and sasl
Date: Sun, 24 Dec 2000 01:21:59 +0100
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Can I make make world make sendmail with milter and sasl / smtp auth just by
adding to make.conf?

If so, how?

Leif





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


From owner-freebsd-current  Sat Dec 23 18:25:28 2000
From owner-freebsd-current@FreeBSD.ORG  Sat Dec 23 18:25:26 2000
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mail.westbend.net (ns1.westbend.net [209.224.254.131])
	by hub.freebsd.org (Postfix) with ESMTP id 364F937B400
	for <freebsd-current@FreeBSD.ORG>; Sat, 23 Dec 2000 18:25:26 -0800 (PST)
Received: from admin.westbend.net (admin.westbend.net [209.224.254.141])
	(authenticated)
	by mail.westbend.net (8.11.1/8.11.1) with ESMTP id eBO2POM01922;
	Sat, 23 Dec 2000 20:25:24 -0600 (CST)
	(envelope-from hetzels@westbend.net)
Message-ID: <001801c06d50$a49037a0$8dfee0d1@westbend.net>
From: "Scot W. Hetzel" <hetzels@westbend.net>
To: "Leif Neland" <leif@neland.dk>, <freebsd-current@FreeBSD.ORG>
References: <01b401c06d3f$99f7e060$0e00a8c0@neland.dk>
Subject: Re: making sendmail with milter and sasl
Date: Sat, 23 Dec 2000 20:24:28 -0600
Organization: West Bend Interent
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

From: "Leif Neland" <leifn@neland.dk>
> Can I make make world make sendmail with milter and sasl / smtp auth just
by
> adding to make.conf?
>
> If so, how?
>
Currently, you need to a patch to enable the building and installing of
libmilter, libsmutil, and the header files needed to build a Milter daemon.

I just sent PR 23811 that contains the patch to enable Milter on both STABLE
and CURRENT (minor fuzziness).

    http://www.freebsd.org/cgi/query-pr.cgi?pr=23811

So after applying the patch, add the following into your make.conf

# See security/cyrus-sasl/files/Sendmail.README
#
SENDMAIL_CFLAGS=-I/usr/local/include/sasl -DSASL -D_FFR_UNSAFE_SASL
SENDMAIL_LDFLAGS=-L/usr/local/lib
SENDMAIL_LDADD=-lsasl
#SENDMAIL_DPADD=
#
SENDMAIL_MILTER=        yes

I have also put this patch at:

ftp://www.westbend.net/pub/sendmail/milter.patch

When you build your milter daemons you can use either a shared  (-lmilter)
or a static (/usr/lib/libmilter.a) libmilter library.

    cc -I/usr/include/sendmail -o sample sample.c -lmilter
/usr/lib/libsmutil.a -pthread

After you build your milter daemons, you will need to create a shell script
that will start/stop the milter daemons.  This script needs to be placed in
PREFIX/etc/rc.milter (see src/lib/libmilter/sample.sh).

Scot W. Hetzel



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