From owner-freebsd-hackers  Sun Feb  2 01:21:14 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id BAA09966
          for hackers-outgoing; Sun, 2 Feb 1997 01:21:14 -0800 (PST)
Received: from sax.sax.de (sax.sax.de [193.175.26.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id BAA09960
          for <freebsd-hackers@freebsd.org>; Sun, 2 Feb 1997 01:21:11 -0800 (PST)
Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA12702 for freebsd-hackers@freebsd.org; Sun, 2 Feb 1997 10:21:09 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id KAA25568; Sun, 2 Feb 1997 10:18:50 +0100 (MET)
Message-ID: <Mutt.19970202101850.j@uriah.heep.sax.de>
Date: Sun, 2 Feb 1997 10:18:50 +0100
From: j@uriah.heep.sax.de (J Wunsch)
To: freebsd-hackers@freebsd.org
Subject: Re: Mounting CD-ROM when data not on first track
References: <Mutt.19970202011243.j@uriah.heep.sax.de> <199702020055.RAA07106@phaeton.artisoft.com>
X-Mailer: Mutt 0.55-PL10
Mime-Version: 1.0
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <199702020055.RAA07106@phaeton.artisoft.com>; from Terry Lambert on Feb 1, 1997 17:55:19 -0700
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

As Terry Lambert wrote:

> I think I lean more towards "the first data track of any session is the
> first track of the session".

While this sentence is self-contradictionary, i get your point.

> > Because it always starts at the beginning, and covers the entire data
> > area.  You could look at it as if it were a huge sparse file in this
> > special situation: seek to the right location, and you'll be able to
> > read the data.
> 
> But it's not a data area... or rather, it's not a 'data' area.

Doesn't matter.  Disk frame numbers don't distinguish between data or
audio areas.  Things like the CD9660 code are meant in terms of disk
frame numbers however, so you have to hole out the !data areas.  They
are valid frame numbers (block numbers in the SCSI sense), it's only
that you cannot READ them.

> Does anyone else have this CD?  Do you have a MacOS or SunOS or older
> Windows box with ASPI or proprietary CDROM driver you can try it in?
> If the non-Joliet aware OS recognizes it, I'd think that the FreeBSD
> interpretation is probably wrong.

FreeBSD doesn't have any interpretation at all by now, so you don't
need this contest.  Its only `interpretation' by now is ``all the
world's a data disk from the beginning through the end, and we assume
the directory tree won't touch outside the disk area''.

> The software we run on our mastering burners here knows about writing
> additional sessions.

We are looking forward to your submission.  Please, contact
ports@freebsd.org to make it a new port.

Uh, it's not available in source form?  Too bad. :-)]

>   It seems that
> Microsoft (stupidly) can not force a program image to be entirely
> resident in memory, and will blue-screen if the image is from a disc
> that has been removed, and it wants to page from it.

Why do you call this `stupid'?  That's the same way every Unix does.
It's only that they probably miss the mount philosophy, so they could
have locked the medium until it will no longer be required for paging.

> Why would you need 99 sub-devices?

Because it's the most logical way.  I don't wanna enforce a policy
(like ISO-9660) in the device driver, since that's a matter of the
filesystem code.  A non-CD9660 CD for example might contain up to 99
UFS filesystems, one per each track, which are fully self-contained
(i.e., with block numbers relative to the start of the track, as any
UFS used to have).

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

From owner-freebsd-hackers  Sun Feb  2 02:32:15 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA11908
          for hackers-outgoing; Sun, 2 Feb 1997 02:32:15 -0800 (PST)
Received: from math.uni-muenster.de (ESCHER.UNI-MUENSTER.DE [128.176.182.85])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id CAA11903
          for <hackers@freebsd.org>; Sun, 2 Feb 1997 02:32:11 -0800 (PST)
Received: from charlie.uni-muenster.de by math.uni-muenster.de (SMI-8.6/SMI-SVR4/OBjP1.13-s)
	id LAA03184; Sun, 2 Feb 1997 11:32:05 +0100
Received: (from pundtt@localhost) by charlie.uni-muenster.de (8.7.5/8.6.9) id LAA01310; Sun, 2 Feb 1997 11:30:06 +0100
Message-ID: <XFMail.970202113006.pundtt@math.uni-muenster.de>
X-Mailer: XFMail 1.1-alpha [p0] on Linux
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="_=XFMail.1.1-alpha.p0.Linux:970202113006:1277=_"
In-Reply-To: <XFMail.970201165834.Shimon@i-Connect.Net>
Date: Sun, 02 Feb 1997 11:20:51 +0100 (MET)
X-Face: Qbvq0<-<<WKbwO=h7:cJ)a})]7I6BY7@T6xe0qJb]U;XVtWfMsFt+C]HE-m(GW(J5{CCj`)
 jD-NJ)\Gn{oLEls7eaQ&Mhm0y^yL>,#/(6w/v\n|F0m?INEfHo]x.v|I1QkVq$LI}bLdhveQBab.a?
 I%*PBhG5L;J}v2{]T=0AN}6=8IA~)@JexMU<mOg@[rNO5.$c-|Asp$]u~.PatM*?h2
Organization: WWU Muenster
From: Thomas Pundt <pundtt@ESCHER.UNI-MUENSTER.DE>
To: Simon Shapiro <Shimon@i-Connect.Net>
Subject: RE: Very Strange Mail Problem
Cc: djb-qmail@koobera.math.uic.edu, xfmail@Burka.NetVision.net.il,
        hackers@freebsd.org
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

This message is in MIME format
--_=XFMail.1.1-alpha.p0.Linux:970202113006:1277=_
Content-Type: text/plain; charset=iso-8859-1


On 02-Feb-97 Simon Shapiro wrote:
| Attached are two pieces of email.  If I feed either one of them to xfmail
| 1.0 (or later, did not try older) all is well.
| 
| If I concatenate them, xfmail dumps core on sig 11.
[...]
| I have no clue why this happens, except that the Subject:  line appears
| long.  So, if any of you can help, I will appreciate it very much.

it's an XFMail bug, indeed caused by the long "Subject:" line; attached is a
patch that fixes the problem.

Thomas

Thomas Pundt ------------------------ http://wwwmath.uni-muenster.de/~pundtt/
Westfaelische Wilhelms-Universitaet | pundtt@math.uni-muenster.de
Einsteinstr. 62, D-48149 Muenster   | Edith-Stein-Str. 9, D-48149 Muenster
(+49) 251 - 83 33747                | privat: (+49) 251 - 273305

--_=XFMail.1.1-alpha.p0.Linux:970202113006:1277=_
Content-Disposition: attachment; filename="diff"
Content-Transfer-Encoding: 7bit
Content-Description: diff
Content-Type: text/plain; charset=us-ascii; name=diff; SizeOnDisk=343

diff -urN xfmail/ui/xfmail.c xfmail~/ui/xfmail.c
--- xfmail/ui/xfmail.c	Mon Dec 30 17:40:13 1996
+++ xfmail~/ui/xfmail.c	Sun Feb  2 11:18:47 1997
@@ -178,7 +178,7 @@
  va_start(ap);
 #endif
 
- vsprintf(buf, fmt, ap);
+ vsnprintf(buf, 255, fmt, ap);
 
  if ((flags == MSG_FATAL) || (flags == MSG_WARN)) 	{
 #if defined(_AIX) || defined(SunOS)

--_=XFMail.1.1-alpha.p0.Linux:970202113006:1277=_--
End of MIME message

From owner-freebsd-hackers  Sun Feb  2 02:58:10 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA13578
          for hackers-outgoing; Sun, 2 Feb 1997 02:58:10 -0800 (PST)
Received: from diablo.ppp.de (diablo.ppp.de [193.141.101.34])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id CAA13563
          for <hackers@freebsd.org>; Sun, 2 Feb 1997 02:58:06 -0800 (PST)
Received: from freebie.lemis.de by diablo.ppp.de with smtp
	(Smail3.1.28.1 #1) id m0vqzcW-000Qa5C; Sun, 2 Feb 97 11:58 MET
Received: (grog@localhost) by freebie.lemis.de (8.8.4/8.6.12) 
       id LAA10731; Sun, 2 Feb 1997 11:29:48 +0100 (MET)
From: grog@lemis.de
Message-Id: <199702021029.LAA10731@freebie.lemis.de>
Subject: Re: bisdn
In-Reply-To: <199702020005.RAA06968@phaeton.artisoft.com> from Terry Lambert at "Feb 1, 97 05:05:42 pm"
To: terry@lambert.org (Terry Lambert)
Date: Sun, 2 Feb 1997 11:29:48 +0100 (MET)
Cc: hackers@freebsd.org (FreeBSD Hackers)
Organisation: 	LEMIS, Schellnhausen 2, 36325 Feldatal, Germany
Phone: +49-6637-919123
Fax: +49-6637-919122
Reply-to: grog@lemis.de (Greg Lehey)
WWW-Home-Page: http://www.FreeBSD.org/~grog
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Terry Lambert writes:
>>>  At least I don't know of any ISP's that offer other ways for
>>>  TCP/IP connection.
>>
>>  There aren't too many in the USA.  That doesn't mean that there
>>  shouldn't be.  I believe most ISDN routers can be set up to run
>>  without PPP.  Certainly the ISPs over here, nearly all of who offer
>>  transparent HDLC, use the same routers as are used in the USA.
>
> The default hardware in the US doesn't do the HDLC for you.  

Oh really?  Do you get D channels?  What do you do with them?

> Think about what hardware the phone company provides for an ISDN
> user over there, but doesn't provide for an ISDN user over here...

An NT1?  It doesn't do HDLC.

Greg

From owner-freebsd-hackers  Sun Feb  2 07:40:56 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id HAA22880
          for hackers-outgoing; Sun, 2 Feb 1997 07:40:56 -0800 (PST)
Received: from chai.plexuscom.com (chai.plexuscom.com [207.87.46.100])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA22874
          for <hackers@FreeBSD.ORG>; Sun, 2 Feb 1997 07:40:52 -0800 (PST)
Received: from chai.plexuscom.com (localhost [127.0.0.1]) by chai.plexuscom.com (8.8.4/8.6.12) with ESMTP id KAA21607; Sun, 2 Feb 1997 10:39:52 -0500 (EST)
Message-Id: <199702021539.KAA21607@chai.plexuscom.com>
To: "Eric J. Chet" <ejc@gargoyle.bazzle.com>
Cc: Terry Lambert <terry@lambert.org>, hackers@FreeBSD.ORG
Subject: Re: g++, STL and -frepo on FreeBSD-2.2-Beta 
In-reply-to: Your message of "Fri, 31 Jan 1997 23:42:36 EST."
             <Pine.BSF.3.95.970131231640.15472A-100000@gargoyle.bazzle.com> 
Date: Sun, 02 Feb 1997 10:39:52 -0500
From: Bakul Shah <bakul@torrentnet.com>
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Terry Lambert writes:

> > g++ -frepo -c x.cc		<========== this succeeds
> > g++ -frepo -o x x.o		<========== this fails
	...
> Clearly, the template class definition
> 
> 	template <class Type>
> 	class list ... {
> 		...
> 	};
> 
> is not in scope.  The header files you have included are apparently
> not sufficient.

If this were the case the compile phase would fail but it does not.
The <stl.h> file includes a file where the list template is defined.

> 	The -frepo patches don't work on our version of the g++ and 
> ld.  I assume ld is the problem.  I haven't had the time to take a look 
> to see what needs to be changed. The -frepo patch from Cygnus when
> applied, should create a set of *.ii one for each source file complied 
> from g++.  The *.ii files specify all templates that need to be 
> instantiated before linking can take place.  I believe there is a collect2
> module that performs the instantiations task.  

I started with the *stock* gcc-2.7.2 distribution (+ 2.7.2-2.7.2.1
diff), not the one in the FreeBSD source tree.

The -frepo patch generates a .rpo file.  In the test case I posted
this .rpo file contains lines like

A -frepo -c
...
O distance_type__FRCQ2t4list1Zi8iterator
O splice__t4list1ZiGQ2t4list1Zi8iteratorRt4list1ZiT1T1
O splice__t4list1ZiGQ2t4list1Zi8iteratorRt4list1ZiT1
O splice__t4list1ZiGQ2t4list1Zi8iteratorRt4list1Zi
...

The ld in /usr/local/lib/gcc-lib/i386-unknown-freebsd2.2/2.7.2.1/ is
apparently the collect2 module, which, I presume, looks at the
.rpo files to find out what classes need to be instantiated.  At
I indicated earlier, g++ -v shows this is the ld called.  Perhaps
this ld fails?  That is where I will look next.

> 	I do know that if you build g++ with John Polstra's ELF patches
> and the -frepo patches.  Then template repository works as advertised.

Where do I find John's ELF patches?

> 	On the other hand, the only thing you lose by not having the
> repository with our native compiler is executable size.  The compiler
> will instantiated every template used in a object file and include it in
> that object file.  Meaning, you can have duplicate template instantiations
> across different object files.

This appears not to be the case.  Are there any flags which make
this possible?  Does libg++-2.7.1 have to be compiled with any
special flags or defines?

Thanks for your responses.

-- bakul

From owner-freebsd-hackers  Sun Feb  2 07:41:30 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id HAA22918
          for hackers-outgoing; Sun, 2 Feb 1997 07:41:30 -0800 (PST)
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA22913
          for <hackers@freebsd.org>; Sun, 2 Feb 1997 07:41:29 -0800 (PST)
Received: from terminator.informatik.ba-stuttgart.de (terminator.informatik.ba-stuttgart.de [141.31.1.21])
          by who.cdrom.com (8.7.5/8.6.11) with ESMTP id HAA10928
          for <hackers@freebsd.org>; Sun, 2 Feb 1997 07:41:26 -0800 (PST)
Received: from helbig.informatik.ba-stuttgart.de (helbig.informatik.ba-stuttgart.de [141.31.166.22]) by terminator.informatik.ba-stuttgart.de (8.7.6/8.7.3) with ESMTP id PAA03685 for <hackers@freebsd.org>; Sun, 2 Feb 1997 15:30:20 +0100
Received: (from helbig@localhost)
          by helbig.informatik.ba-stuttgart.de (8.8.5/8.8.4)
	  id QAA00202 for hackers@freebsd.org; Sun, 2 Feb 1997 16:30:47 +0100 (MET)
From: Wolfgang Helbig <helbig@MX.BA-Stuttgart.De>
Message-Id: <199702021530.QAA00202@helbig.informatik.ba-stuttgart.de>
Subject: CMD640b flaw workaround
To: hackers@freebsd.org
Date: Sun, 2 Feb 1997 16:30:46 +0100 (MET)
X-Mailer: ELM [version 2.4ME+ PL30 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi,

This is a patch for wd.c to make the broken CMD640b work with both
IDE channels under FreeBSD.
I tested it with ATAPI-CDROM - HD's on both channels and also with
HD's an both channels.

You have to put
	options		"CMD640"
in your kernel configuration file to enable the needed serialization
for the CMD640. Sorry Jörg, I know I should have used the driver flags,
but this is a snapshot anyway. I guess the best way to enable this code
is to use the pci-probing. It does recognize the CMD640.

Please test this patch and tell about the results.

Wolfgang Helbig            


Index: wd.c
===================================================================
RCS file: /usr/cvsroot/src/sys/i386/isa/wd.c,v
retrieving revision 1.122
diff -r1.122 wd.c
130a131,132
> #define PRIMARY		0
> 
239a242,245
> #ifdef CMD640
> static int 	wdcports[NWDC]; 
> static int      atapictrlr;
> #endif
362a369,372
> #ifdef CMD640
> 	if (dvp->id_unit == PRIMARY)
> 		TAILQ_INIT( &wdtab[PRIMARY].controller_queue);
> #else
363a374
> #endif
385a397,399
> #ifdef CMD640
> 		wdcports[du->dk_ctrlr] = du->dk_port;
> #endif
470c484,490
< 		atapi_attach (dvp->id_unit, unit, dvp->id_iobase);
---
> 		if (atapi_attach (dvp->id_unit, unit, dvp->id_iobase)) {
> #ifdef CMD640
> 			wdcports[unit] = dvp->id_iobase;
> 			atapictrlr = dvp->id_unit;
> 			printf("wd: atapictrlr = %d\n", atapictrlr);
> #endif
> 		}
476a497,499
> #ifdef CMD640
> 	wdtab[PRIMARY].b_active = 2;
> #else
477a501
> #endif
551a576,578
> #ifdef CMD640
> 	if (wdtab[PRIMARY].b_active == 0)
> #else
552a580
> #endif
613a642,644
> #ifdef CMD640
> 	TAILQ_INSERT_TAIL( &wdtab[PRIMARY].controller_queue, bp, b_act);
> #else
614a646
> #endif
639a672,677
> #ifdef CMD640 
> 	if (wdtab[PRIMARY].b_active == 2)
> 		wdtab[PRIMARY].b_active = 0;
> 	if (wdtab[PRIMARY].b_active)
> 		return;
> #else
644d681
< #endif
645a683,687
> #endif
> #endif
> #ifdef CMD640
> 	bp = wdtab[PRIMARY].controller_queue.tqh_first;
> #else
646a689
> #endif
648a692,694
> #ifdef CMD640
> 		if (atapi_start && atapi_start (atapictrlr))
> #else
649a696
> #endif
650a698,700
> #ifdef CMD640
> 			wdtab[PRIMARY].b_active = 3;
> #else
652a703
> #endif
707a759,761
> #ifdef CMD640
> 	wdtab[PRIMARY].b_active = 1;	/* mark controller active */
> #else
708a763
> #endif
719a775,777
> #ifdef CDM640
> 		if (wdtab[PRIMARY].b_errcnt && (bp->b_flags & B_READ) == 0)
> #else
720a779
> #endif
866c925,929
< 
---
> #ifdef CMD640
> 	if (wdtab[PRIMARY].b_active == 2)
> 		return;		/* intr in wdflushirq() */
> 	if (!wdtab[PRIMARY].b_active) {
> #else
869a933
> #endif
880a945,947
> #ifdef CMD640
> 	if (wdtab[PRIMARY].b_active == 3) {
> #else
881a949
> #endif
886a955,957
> #ifdef CMD640
> 		wdtab[PRIMARY].b_active = 0;
> #else
887a959
> #endif
891a964,966
> #ifdef CMD640
> 	bp = wdtab[PRIMARY].controller_queue.tqh_first;
> #else
892a968
> #endif
902a979,981
> #ifdef CMD640
> 		wdtab[PRIMARY].b_active = 0;
> #else
903a983
> #endif
944a1025,1028
> #ifdef CMD640
> 			if (++wdtab[PRIMARY].b_errcnt < RETRIES) {
> 				wdtab[PRIMARY].b_active = 0;
> #else
946a1031
> #endif
959a1045,1047
> #ifdef CMD640
> 	    && wdtab[PRIMARY].b_active) {
> #else
960a1049
> #endif
1001a1091,1093
> #ifdef CMD640
> 	if (wdtab[PRIMARY].b_active) {
> #else
1002a1095
> #endif
1004a1098,1102
> #ifdef CMD640
> 			if (wdtab[PRIMARY].b_errcnt)
> 				wderror(bp, du, "soft error");
> 			wdtab[PRIMARY].b_errcnt = 0;
> #else
1007a1106
> #endif
1012a1112,1114
> #ifdef CMD640
> 					wdtab[PRIMARY].b_active = 0;
> #else
1013a1116
> #endif 
1023a1127,1129
> #ifdef CMD640
> 				wdtab[PRIMARY].b_active = 0;
> #else
1024a1131
> #endif 
1032a1140,1143
> #ifdef CMD640
> 		TAILQ_REMOVE(&wdtab[PRIMARY].controller_queue, bp, b_act);
> 		wdtab[PRIMARY].b_errcnt = 0;
> #else
1034a1146
> #endif
1046a1159,1161
> #ifdef CMD640
> 	wdtab[PRIMARY].b_active = 0;
> #else
1047a1163
> #endif  
1053a1170,1172
> #ifdef CMD640
> 	if (wdtab[PRIMARY].controller_queue.tqh_first)
> #else
1054a1174
> #endif  
1076a1197,1200
> #ifdef CMD640
> 	if (wdtab[PRIMARY].b_active == 2)
> 		wdtab[PRIMARY].b_active = 0;
> #else
1078a1203
> #endif
1247a1373,1375
> #ifdef CMD640
> 		wdtab[PRIMARY].b_active = 1;
> #else
1248a1377
> #endif
1261a1391,1393
> #ifdef CMD640
> 			if (++wdtab[PRIMARY].b_errcnt < RETRIES)
> #else
1262a1395
> #endif
1267a1401,1403
> #ifdef CMD640
> 		wdtab[PRIMARY].b_errcnt = 0;
> #else
1268a1405
> #endif
1375a1513,1515
> #ifdef CMD640 
> 		wdtab[PRIMARY].b_errcnt += RETRIES;
> #else
1376a1517
> #endif
1753,1756d1893
< #if 0
< 	/* Mark controller active for if we panic during the dump. */
< 	wdtab[du->dk_ctrlr].b_active = 1;
< #endif
1902a2040,2045
> #ifdef CMD640
> 	wdtab[PRIMARY].b_active = 2;
> 	splx(old_ipl);
> 	(void)splbio();
> 	wdtab[PRIMARY].b_active = 0;
> #else
1906a2050
> #endif  
1945a2090,2093
> #ifdef CMD640
> 	while (wdtab[PRIMARY].b_active)
> 		tsleep((caddr_t)&wdtab[PRIMARY].b_active, PZERO - 1, wmesg, 1);
> #else
1947a2096
> #endif
2022a2172,2201
> #ifdef CMD640
> int   
> cmd640_wait(int port)
> {
> 	int port2;
> 	int timeout;
> 	u_char status;
> 
> 	return (0);
> 	if (NWDC == 1)
> 		return (0);
> 
> 	if (wdcports[0] == port) 
> 		port2 = wdcports[1];
> 	else
> 		port2 = wdcports[0];
> 	if (port2 == 0)
> 		return (0);
> 	for (timeout = TIMEOUT; timeout > 0; timeout--) {
> 		status = inb(port2 + wd_status);
> 		if (!(status & WDCS_BUSY))
> 			return (0);
> 		DELAY (1000);
> 		printf("called by port %x\n",port);
> 	}
> 	printf("wd: timeout on port %x\n", port2);
> 	return (-1);
> }
> #endif
> 
2032a2212,2216
> 
> #ifdef CMD640
> 	if (cmd640_wait(wdc) != 0)
> 		return (-1);
> #endif


From owner-freebsd-hackers  Sun Feb  2 08:01:12 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id IAA23461
          for hackers-outgoing; Sun, 2 Feb 1997 08:01:12 -0800 (PST)
Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA23456
          for <freebsd-hackers@freefall.FreeBSD.org>; Sun, 2 Feb 1997 08:01:09 -0800 (PST)
Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12)
	with ESMTP id RAA02957 for <freebsd-hackers@freefall.FreeBSD.org>; Sun, 2 Feb 1997 17:01:10 +0100 (MET)
Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.8.4/8.6.9) id RAA00260 for freebsd-hackers@freefall.cdrom.com; Sun, 2 Feb 1997 17:04:14 +0100 (MET)
Date: Sun, 2 Feb 1997 17:04:14 +0100 (MET)
From: Christoph Kukulies <kuku@gilberto.physik.rwth-aachen.de>
Message-Id: <199702021604.RAA00260@gilberto.physik.rwth-aachen.de>
To: freebsd-hackers@freefall.FreeBSD.org
Subject: squid 1.1.4
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


I'm in the urgent need of getting squid (1.1.4) running to serve some
Win95 weenies hanging in a 192.168.1 network to let them do webbrowsing.

My FreeBSD 3.0-current machine acts as an ISDN router, and is runnig
the squid daemon as well as an apache httpd.

If anyone out there experienced with this could he conatct me please.

It looks like the squid daemon is running fine. Only when I try to 
connect via squid to the outside world I'm getting this:
      
isdn-kuku> tail -f /usr/local/squid/logs/access.log
854896136.897   6655 192.168.1.126 ERR_CONNECT_FAIL/400 837 GET http://www.freebsd.org/ - SINGLE_PARENT/www-proxy.informatik.rwth-aachen.de -
854898046.079    269 192.168.1.126 ERR_CONNECT_FAIL/400 842 GET http://www.freebsd.org/ - SINGLE_PARENT/www-proxy.informatik.rwth-aachen.de -              

The webbroswer on the Win95 machine is always giving (61) Connection refused.

This message is generated by squid. So the proxy mechanism to squid in the
local network seems to work.


--Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de


From owner-freebsd-hackers  Sun Feb  2 08:28:32 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id IAA24177
          for hackers-outgoing; Sun, 2 Feb 1997 08:28:32 -0800 (PST)
Received: from csd.cs.technion.ac.il (csd.cs.technion.ac.il [132.68.32.8])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id IAA24170
          for <hackers@FreeBSD.ORG>; Sun, 2 Feb 1997 08:28:22 -0800 (PST)
Received: from localhost (nadav@localhost) by csd.cs.technion.ac.il (8.6.11/8.6.10) with SMTP id SAA22968; Sun, 2 Feb 1997 18:23:55 +0200
X-Authentication-Warning: csd.cs.technion.ac.il: nadav owned process doing -bs
Date: Sun, 2 Feb 1997 18:23:54 +0200 (IST)
From: Nadav Eiron <nadav@cs.technion.ac.il>
X-Sender: nadav@csd
To: Wolfgang Helbig <helbig@MX.BA-Stuttgart.De>
cc: hackers@FreeBSD.ORG
Subject: Re: CMD640b flaw workaround
In-Reply-To: <199702021530.QAA00202@helbig.informatik.ba-stuttgart.de>
Message-ID: <Pine.GSO.3.95-heb-2.07.970202182140.22764B-100000@csd>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-8
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by freefall.freebsd.org id IAA24173
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk



On Sun, 2 Feb 1997, Wolfgang Helbig wrote:

> Hi,
> 
> This is a patch for wd.c to make the broken CMD640b work with both
> IDE channels under FreeBSD.
> I tested it with ATAPI-CDROM - HD's on both channels and also with
> HD's an both channels.
> 
> You have to put
> 	options		"CMD640"
> in your kernel configuration file to enable the needed serialization
> for the CMD640. Sorry Jörg, I know I should have used the driver flags,
> but this is a snapshot anyway. I guess the best way to enable this code
> is to use the pci-probing. It does recognize the CMD640.
> 
> Please test this patch and tell about the results.
> 
> Wolfgang Helbig            
> 
> 
    [patch snipped]

Cool! Will this work under 2.1.6R (yeah, I know, but it's a "production"
machine, and while we are working on an upgrade to SCSI, it currently has
a CMD640)?

Nadav


From owner-freebsd-hackers  Sun Feb  2 09:03:29 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA25266
          for hackers-outgoing; Sun, 2 Feb 1997 09:03:29 -0800 (PST)
Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA25259
          for <hackers@freebsd.org>; Sun, 2 Feb 1997 09:03:25 -0800 (PST)
Received: from dbws.etinc.com (dbws.etinc.com [204.141.95.130]) by etinc.com (8.8.3/8.6.9) with SMTP id MAA27368; Sun, 2 Feb 1997 12:07:02 -0500 (EST)
Message-Id: <3.0.32.19970202121809.00697048@etinc.com>
X-Sender: dennis@etinc.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Sun, 02 Feb 1997 12:18:10 -0500
To: Julian Elischer <julian@whistle.com>
From: dennis <dennis@etinc.com>
Subject: Re: Device Driver: Almost home(?)
Cc: hackers@freebsd.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

At 10:12 PM 2/1/97 -0800, you wrote:
>OK,
>here is a shell script that writes a pseudo device driver 
>and integrates it into your kernel.
>I also attach a real device driver writing script that does the same
>thing
>
>they both use the GENERIC config as a starting point..
>you run them as:

I prefer the:

Copy_a_similar_driver && search_and_replace_in_vi  method.....

Please, for the sake of sanity, make a pledge to keep the script up to
date...LINUX has
a "skeleton" driver that (at one point) was just enough out of date to
drive anyone using
it a little crazy!

Dennis

From owner-freebsd-hackers  Sun Feb  2 09:16:07 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA25572
          for hackers-outgoing; Sun, 2 Feb 1997 09:16:07 -0800 (PST)
Received: from eldorado.net-tel.co.uk ([193.122.171.253])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA25567
          for <hackers@freebsd.org>; Sun, 2 Feb 1997 09:16:02 -0800 (PST)
From: Andrew.Gordon@net-tel.co.uk
Received: (from root@localhost) by eldorado.net-tel.co.uk (8.6.12/8.6.10) id RAA24004 for hackers@freebsd.org; Sun, 2 Feb 1997 17:15:27 GMT
Received: from "/PRMD=NET-TEL/ADMD=GOLD 400/C=GB/" by net-tel.co.uk
        (Route400-RFCGate); Sun,  2 Feb 97 17:14:48 +0000
X400-Received: by mta "eldorado" in "/PRMD=net-tel/ADMD=gold 400/C=gb/"; 
        Relayed; Sun,  2 Feb 97 17:14:48 +0000
X400-Received: by mta "net-tel cambridge" in "/PRMD=net-tel/ADMD=gold 400/C=gb/";
         Relayed; Sun,  2 Feb 97 17:14:47 +0000
X400-Received: by "/PRMD=NET-TEL/ADMD=Gold 400/C=GB/"; Relayed; 
        Sun,  2 Feb 97 17:14:47 +0000
X400-MTS-Identifier: 
        ["/PRMD=NET-TEL/ADMD=Gold 400/C=GB/";hst:8655-970202171447-7D08]
X400-Content-Type: P2-1984 (2)
X400-Originator: Andrew.Gordon@net-tel.co.uk
Original-Encoded-Information-Types: IA5-Text
X400-Recipients: hackers@freebsd.org
Date: Sun,  2 Feb 97 17:14:47 +0000
X400-Content-Identifier: Re(2): bisdn
Message-Id: <"7527-970202171433-7459*/G=Andrew/S=Gordon/O=NET-TEL Computer
 Systems Ltd/PRMD=NET-TEL/ADMD=Gold 400/C=GB/"@MHS>
To: hackers@freebsd.org
In-Reply-To: <199702020005.RAA06968@phaeton.artisoft.com>
Subject: Re(2): bisdn
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > > At least I don't know of any ISP's that offer other ways for
> > > TCP/IP connection.
> > 
> > There aren't too many in the USA.  That doesn't mean that there
> > shouldn't be.  I believe most ISDN routers can be set up to run
> > without PPP.  Certainly the ISPs over here, nearly all of who offer
> > transparent HDLC, use the same routers as are used in the USA.
> 
> The default hardware in the US doesn't do the HDLC for you.  Think
> about what hardware the phone company provides for an ISDN user
> over there, but doesn't provide for an ISDN user over here...

Nor does the hardware provided for you in Europe; the HDLC in question
is done by the TA.  In the case of the Teles/Creatix/AVM cards
supported by BISDN, there are two chips of consequence on the card:
one (PEB2085) does clock generation etc. to demultiplex the 3
channels, and also does HDLC decoding for the D channel; the other
(82525) is a two-channel HDLC controller used to run the B channels
(it can also be put in a byte-clocked mode for doing voice calls,
which are one of the few things that aren't HDLC).

If you do Sync PPP, those PPP packets are themselves encapsulated
in HDLC frames.

Even if you insist on treating the TAs like modems and running
async PPP transparently over V.120 (or SLIP likewise), V.120
itself encapsulates your async data in HDLC frames (so you would
have been better off doing sync PPP as you have now got double
the framing overhead and increased latency).

From owner-freebsd-hackers  Sun Feb  2 09:31:25 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA26174
          for hackers-outgoing; Sun, 2 Feb 1997 09:31:25 -0800 (PST)
Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA26167
          for <hackers@FreeBSD.ORG>; Sun, 2 Feb 1997 09:31:18 -0800 (PST)
Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33])
          by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP
	  id SAA14996 for <hackers@FreeBSD.ORG>; Sun, 2 Feb 1997 18:30:58 +0100
Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id SAA28183 for hackers@FreeBSD.ORG; Sun, 2 Feb 1997 18:30:45 +0100
Received: (from roberto@localhost) by keltia.freenix.fr (8.8.5/keltia-uucp-2.9) id SAA18071;
          Sun, 2 Feb 1997 18:13:26 +0100 (CET)
Message-ID: <19970202181325.OW45132@keltia.freenix.fr>
Date: Sun, 2 Feb 1997 18:13:25 +0100
From: roberto@keltia.freenix.fr (Ollivier Robert)
To: hackers@FreeBSD.ORG
Subject: Re: g++, STL and -frepo on FreeBSD-2.2-Beta
References: <Pine.BSF.3.95.970131231640.15472A-100000@gargoyle.bazzle.com> <199702021539.KAA21607@chai.plexuscom.com>
X-Mailer: Mutt 0.60,1-3,9
Mime-Version: 1.0
X-Operating-System: FreeBSD 3.0-CURRENT ctm#2997
In-Reply-To: <199702021539.KAA21607@chai.plexuscom.com>; from Bakul Shah on Feb 2, 1997 10:39:52 -0500
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

According to Bakul Shah:
> > 	I do know that if you build g++ with John Polstra's ELF patches
> > and the -frepo patches.  Then template repository works as advertised.
> 
> Where do I find John's ELF patches?

<URL:ftp://ftp.polstra.com/pub/FreeBSD/elfkit/elfkit-1.2.1.tar.gz>

Works fine although it would be nice to have gdb recognizing ELF
binaries...

213 [18:11] roberto@keltia:/build/mutt-0.60> gdb ./mutt
GDB is free software and you are welcome to distribute copies of it
 under certain conditions; type "show copying" to see the conditions.
There is absolutely no warranty for GDB; type "show warranty" for details.
GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation,
Inc...

"/work/build/mutt-0.60/./mutt": not in executable format: File format not
recognized

208 [18:10] roberto@keltia:/build/mutt-0.60> elf-objdump --private-headers
mutt 

mutt:     file format elf32-i386

Program Header:
    PHDR off    0x00000034 vaddr 0x08048034 paddr 0x08048034 align 2**2
         filesz 0x000000a0 memsz 0x000000a0 flags r-x
  INTERP off    0x000000d4 vaddr 0x080480d4 paddr 0x080480d4 align 2**0
         filesz 0x00000019 memsz 0x00000019 flags r--
    LOAD off    0x00000000 vaddr 0x08048000 paddr 0x08048000 align 2**12
         filesz 0x0002a593 memsz 0x0002a593 flags r-x
    LOAD off    0x0002a598 vaddr 0x08073598 paddr 0x08073598 align 2**12
         filesz 0x0000230c memsz 0x00005109 flags rw-
 DYNAMIC off    0x0002c814 vaddr 0x08075814 paddr 0x08075814 align 2**2
         filesz 0x00000090 memsz 0x00000090 flags rw-

Dynamic Section:
  NEEDED      libncurses.so
  NEEDED      libc.so.1
  INIT        0x80496d0
  FINI        0x806bee4
  HASH        0x80480f0
  STRTAB      0x8048e58
  SYMTAB      0x8048548
  STRSZ       0x478
  SYMENT      0x10
  DEBUG       0x0
  PLTGOT      0x807561c
  PLTRELSZ    0x3d8
  PLTREL      0x11
  JMPREL      0x80492f8
  REL         0x80492d0
  RELSZ       0x28
  RELENT      0x8

-- 
Ollivier ROBERT    -=- The daemon is FREE! -=-    roberto@keltia.freenix.fr
  FreeBSD keltia.freenix.fr 3.0-CURRENT #37: Mon Jan 27 23:21:10 CET 1997

From owner-freebsd-hackers  Sun Feb  2 09:35:18 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA26387
          for hackers-outgoing; Sun, 2 Feb 1997 09:35:18 -0800 (PST)
Received: from news.IAEhv.nl (root@news.IAEhv.nl [194.151.64.4])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA26381
          for <hackers@freebsd.org>; Sun, 2 Feb 1997 09:35:15 -0800 (PST)
Received: from oasis.IAEhv.nl (uucp@localhost) 
          by news.IAEhv.nl (8.6.13/1.63) with IAEhv.nl; pid 2171
          on Sun, 2 Feb 1997 18:09:07 +0100; id SAA02171
          efrom: volf@oasis.IAEhv.nl; eto: freebsd.org!hackers
Received: from LOCAL (volf@localhost) 
          by oasis.IAEhv.nl (8.8.5/1.63); pid 1035 
          on Sun, 2 Feb 1997 16:23:23 +0100 (MET); id QAA01035
          efrom: volf; eto: hackers@freebsd.org
From: volf@oasis.IAEhv.nl (Frank Volf)
Message-Id: <199702021523.QAA01035@oasis.IAEhv.nl>
Subject: FreeBSD 2.1.6 and CTM
To: hackers@freebsd.org
Date: Sun, 2 Feb 1997 16:23:23 +0100 (MET)
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Hi,

Yesterday I finally got my 2.1.6 cdrom. To my disappointment the CDROMs did
not contain a base CTM delta for cvs-cur. This is not a problem, since the
CVS tree tar files are on disk 1. Unfortunately I can't find out which
cvs-cur delta this tree is (i.e. what the first delta is that should be
applied to the tree). Can anyone help?

Regards,

             Frank

p.s.: It would be nice for the 2.2 RELEASE cd to put the delta number in the
      readme file

 ----------------------------------------------------------------------------
       Frank Volf - Internet Access Eindhoven - Digitale Stad Eindhoven 
 ----------------------------------------------------------------------------
  ||  volf@oasis.IAEhv.nl - use for personal mail                         ||
  ||  volf@IAEhv.nl - use for Internet Access Eindhoven related mail      ||
  ||  volf@dse.dse.nl - use for Digital City of Eindhoven related mail    ||
 ----------------------------------------------------------------------------
    IAE Public Access Unix System - Dial +31.40.2439436 and login as new.  
 ----------------------------------------------------------------------------

From owner-freebsd-hackers  Sun Feb  2 09:39:28 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA26492
          for hackers-outgoing; Sun, 2 Feb 1997 09:39:28 -0800 (PST)
Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA26485
          for <hackers@FreeBSD.ORG>; Sun, 2 Feb 1997 09:39:21 -0800 (PST)
Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id MAA02624; Sun, 2 Feb 1997 12:36:01 -0500
From: Bill Paul <wpaul@skynet.ctr.columbia.edu>
Message-Id: <199702021736.MAA02624@skynet.ctr.columbia.edu>
Subject: Re: slow ypserv problem
To: proff@suburbia.net
Date: Sun, 2 Feb 1997 12:36:00 -0500 (EST)
Cc: hackers@FreeBSD.ORG
In-Reply-To: <19970202074803.4702.qmail@suburbia.net> from "proff@suburbia.net" at Feb 2, 97 06:48:03 pm
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Of all the gin joints in all the towns in all the world, 
proff@suburbia.net had to walk into mine and say:

> > Of all the gin joints in all the towns in all the world, Tom Samplonius 
> > had to walk into mine and say:
> > 
> > > 
> > > On Sat, 1 Feb 1997, Steve wrote:
> > > 
> > > > On Sat, 1 Feb 1997, Tom Samplonius wrote:
> > > > >   Bill knows.
> > > > > 
> > > > >   ypserv was completely re-written for 2.2.
> > 
> > Darn straight.
> 
> (etc)
> 
> What happened to the NIS+ support someone posted to here
> a few months ago?

Er... I don't know what you're talking about. I'm still working on NIS+,
but first I have to deal with Secure RPC. Lately I've been hampered a bit
by Real Work (tm) though. (Getting my backup system working reliably with
my new DLT tape drive holds a slightly higher priority. :)

What I've done so far is put together a libnisdb database backend for
the NIS+ server, created a few pieces of the nislib client support,
and started work on rpc.nisd. Mostly I've been testing my rpc.nisd
with a slowlaris machine to see what sort things slowlaris expects the
server to do (it's not always obvious from the protocol definition).
I reached the point where I can create, modify, lookup and destroy
NIS+ directories, and create, lookup and destroy NIS+ tables. I also
have rudimentary support for callbacks, although I need to do some more
work to make the callback mechanism work correctly. (It was while playing
with callbacks that I realized just how thread-oriented NIS+ is supposed
to be. It is possible that a client may initiate a callback which will
cause the server to transmit a stream or records, one at a time. This
is actually done 'backwards' by having rpc.nisd do a clnt_call() to set
up a new connection to the client program and transmit records with
clnt_call(). But clnt_call() actually does two things: it sends a request,
then it waits for an answer. It is the client's responsibility to send
an answer for each request, but it doesn't always send an answer right
away. For example, in the nis_list() case, the client may get a record
from rpc.nisd, then turn around and use the data from that record to make
_another_ NIS+ call to the server. But the server is still waiting for
the client to send a reply to its callback, hence it will be unable to
service the client's other request, and the server and client will become
deadlocked. Sun's solution for this is to handle callbacks in a seperate
thread. My solution, which is still only half implemented, is to essentially
split the clnt_call() in half: the first part of the call (transmitting
the record) is done right away, then it returns and the socket from the
CLIENT handle is added to the descriptor list monitored by the select()
loop in svc_run(). This lets the server handle the replies asynchronously
and avoids blocking without the use of threads.)

There's still one puzzle I haven't completely solved yet, which has to
do with entry attributes. An entry in a table is supposed to posess its
own attributes, like owner, creation time, modification time, and time to 
live (ttl) value. But the entry_obj structure in the NIS+ protocol
definition does not have fields to suppor this: it only has fields for
the per-column data and an en_type field for the object type. An entry
can have extra attributes _if_ it is encapsulated in an nis_object
structure, but entries are not stored by the database backend as nis_objects.
This being the case, where does the server store this extra per-entry
attribute information? My half-assed solution for this is to abuse the
en_type field to hold the data in a specially encoded form (the entry type
is always the same as the table type anyway, so you can always fudge it
back up before returning the entry to the client). But something tells
me there's a better way.

Anyway. I still have to implement the transaction logging, the public key
updating routines, and the replication handling. I also need to make sure
the security model (access rights, etc...) actually works the way Sun
says it should. Hopefully I can fill in the rest of the client library
at the same time. Then I can do nis_cachemgr and all the damned command
line utilities. Lastly, Sun implements 'DNS forwarding' as a seperate 
process (rpc.nisd_resolv). I'm not sure I want to do it this way. We'll see.

-Bill

-- 
=============================================================================
-Bill Paul            (212) 854-6020 | System Manager, Master of Unix-Fu
Work:         wpaul@ctr.columbia.edu | Center for Telecommunications Research
Home:  wpaul@skynet.ctr.columbia.edu | Columbia University, New York City
=============================================================================
 "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness"
=============================================================================

From owner-freebsd-hackers  Sun Feb  2 09:51:15 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA27013
          for hackers-outgoing; Sun, 2 Feb 1997 09:51:15 -0800 (PST)
Received: from sax.sax.de (sax.sax.de [193.175.26.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA26998
          for <hackers@FreeBSD.ORG>; Sun, 2 Feb 1997 09:51:08 -0800 (PST)
Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id SAA24031; Sun, 2 Feb 1997 18:50:33 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id SAA02125; Sun, 2 Feb 1997 18:33:59 +0100 (MET)
Message-ID: <Mutt.19970202183359.j@uriah.heep.sax.de>
Date: Sun, 2 Feb 1997 18:33:59 +0100
From: j@uriah.heep.sax.de (J Wunsch)
To: nadav@cs.technion.ac.il (Nadav Eiron)
Cc: hackers@FreeBSD.ORG
Subject: Re: CMD640b flaw workaround
References: <199702021530.QAA00202@helbig.informatik.ba-stuttgart.de> <Pine.GSO.3.95-heb-2.07.970202182140.22764B-100000@csd>
X-Mailer: Mutt 0.55-PL10
Mime-Version: 1.0
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <Pine.GSO.3.95-heb-2.07.970202182140.22764B-100000@csd>; from Nadav Eiron on Feb 2, 1997 18:23:54 +0200
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

As Nadav Eiron wrote:

> Cool! Will this work under 2.1.6R (yeah, I know, but it's a "production"
> machine, and while we are working on an upgrade to SCSI, it currently has
> a CMD640)?

If you run a ``production machine'' with a broken disk interface
chipset, you don't need to worry running GAMMA quality software on it
(FreeBSD 2.2) either. :-]  I think your chipset is way more broken
than FreeBSD 2.2 is. ;)

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

From owner-freebsd-hackers  Sun Feb  2 10:22:03 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id KAA29093
          for hackers-outgoing; Sun, 2 Feb 1997 10:22:03 -0800 (PST)
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA29088
          for <hackers@freefall.freebsd.org>; Sun, 2 Feb 1997 10:22:01 -0800 (PST)
Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121])
          by who.cdrom.com (8.7.5/8.6.11) with ESMTP id KAA11111
          for <hackers@freefall.freebsd.org>; Sun, 2 Feb 1997 10:21:57 -0800 (PST)
Received: from localhost (narvi@localhost)
          by haldjas.folklore.ee (8.8.4/8.8.4) with SMTP
	  id UAA13651; Sun, 2 Feb 1997 20:20:55 +0200 (EET)
Date: Sun, 2 Feb 1997 20:20:55 +0200 (EET)
From: Narvi <narvi@haldjas.folklore.ee>
To: Terry Lambert <terry@lambert.org>
cc: gurney_j@resnet.uoregon.edu, hackers@freefall.freebsd.org
Subject: Re: performance puzzler
In-Reply-To: <199702012151.OAA06709@phaeton.artisoft.com>
Message-ID: <Pine.BSF.3.95.970202201858.13473A-100000@haldjas.folklore.ee>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk



On Sat, 1 Feb 1997, Terry Lambert wrote:

> > > Your bus on the 120 is 3MHz slower than the bus on the 66.  What you
> > > are doing is not I/O bound, it is CPU bound.
> > 
> > umm... this usually isn't true...  most of the non 33mhz bus speeds (for
> > 486 based chips) are actually 40 mhz or 50mhz...  the amd-486/120dx4 is
> > actually a 40mhz bus multiplied by 3...  it's kinda like the Intel
> > 486/100dx4...  the chip is actually 3x bus speed (33mhz)...
> 
> Memory bus, or I/O bus?
> 
> The PCI and EISA standards specify 33MHz as their top end.
> 

Where did I read about 66Mhz revision/mode for PCI? Was it in a dream or
just a "not supported by anybody yet" possibility as is the 64bit card
width. Or was it all just a dream or erroneus news article?

	Sander

> 
> 
> 					Terry Lambert
> 					terry@lambert.org
> ---
> Any opinions in this posting are my own and not those of my present
> or previous employers.
> 


From owner-freebsd-hackers  Sun Feb  2 10:52:34 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id KAA00838
          for hackers-outgoing; Sun, 2 Feb 1997 10:52:34 -0800 (PST)
Received: from amadeus.informatik.ba-stuttgart.de (amadeus.informatik.ba-stuttgart.de [141.31.11.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA00833
          for <hackers@freebsd.org>; Sun, 2 Feb 1997 10:52:31 -0800 (PST)
Received: (from helbig@localhost) by amadeus.informatik.ba-stuttgart.de (8.7.3/8.7.1) id TAA03678; Sun, 2 Feb 1997 19:46:07 +0100 (MET)
From: Wolfgang Helbig <helbig@BA-Stuttgart.De>
Message-Id: <199702021846.TAA03678@amadeus.informatik.ba-stuttgart.de>
Subject: Re: CMD640b flaw workaround
To: nadav@cs.technion.ac.il (Nadav Eiron)
Date: Sun, 02 Feb 1997 19:46:07 MET
Cc: hackers@freebsd.org
In-Reply-To: <Pine.GSO.3.95-heb-2.07.970202182140.22764B-100000@csd>; from "Nadav Eiron" at Feb 2, 97 6:23 pm
X-Mailer: Elm [revision: 112.2]
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 
> Cool! Will this work under 2.1.6R (yeah, I know, but it's a "production"
> machine, and while we are working on an upgrade to SCSI, it currently has
> a CMD640)?
> 
> Nadav
> 
> 

Sorry, but the diff is against revision 1.122 of wd.c , whereas
you have revision 1.81.4.2 in FreeBSD 2.1.6.1 . So the patch will not
work. I tried to produce the diff from 1.122 to 1.81.4.2  and applying
a patch with it to my version of wd.c but there were to many rejects.

So maybe you should upgrade to FreeBSD 2.2 and test then.

Much luck

Wolfgang


From owner-freebsd-hackers  Sun Feb  2 11:54:58 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA07656
          for hackers-outgoing; Sun, 2 Feb 1997 11:54:58 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA07649
          for <hackers@freefall.freebsd.org>; Sun, 2 Feb 1997 11:54:52 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA08288; Sun, 2 Feb 1997 12:51:35 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702021951.MAA08288@phaeton.artisoft.com>
Subject: Re: performance puzzler
To: narvi@haldjas.folklore.ee (Narvi)
Date: Sun, 2 Feb 1997 12:51:35 -0700 (MST)
Cc: terry@lambert.org, gurney_j@resnet.uoregon.edu,
        hackers@freefall.freebsd.org
In-Reply-To: <Pine.BSF.3.95.970202201858.13473A-100000@haldjas.folklore.ee> from "Narvi" at Feb 2, 97 08:20:55 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > The PCI and EISA standards specify 33MHz as their top end.
> 
> Where did I read about 66Mhz revision/mode for PCI? Was it in a dream or
> just a "not supported by anybody yet" possibility as is the 64bit card
> width. Or was it all just a dream or erroneus news article?

The PCI SIG has been discussing this.  Obviously, the 64bit version
can't use the same edge connector because there aren't 32 free lines;
all this "64bit PCI card" hype claimed by video vendors is on-card
data path, not bus data path.

The 66MHz has also been discussed, but requires a way to key the bus
as to which type of card is present so it can introduce a wait state
per cycle for older cards.

One problem with the design is that the bus chaining used in current
Intel chip designs won't work: you can't send 66MHz signals down a bus
if you have 33MHz cards potentially listening or attempting to master
the bus.  This basically means that the Intel PCI bus chips can't
tie all the slots to the same chip lines, if you are going to try
to use the same card connector.  This is a win, in that it means that
we will finally get over the 4 slot limit imposed by the line drivers
(which doesn't exist in the Motorola and Apple PCI chipsets because
they were not lazy in their design).  It's bad, because it means
new motherboard designs, and PCI has just settled down from the last
minor revision to the spec..  8-(.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Sun Feb  2 12:04:25 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA08222
          for hackers-outgoing; Sun, 2 Feb 1997 12:04:25 -0800 (PST)
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA08216
          for <freebsd-hackers@freebsd.org>; Sun, 2 Feb 1997 12:04:19 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by who.cdrom.com (8.7.5/8.6.11) with SMTP id MAA11232
          for <freebsd-hackers@freebsd.org>; Sun, 2 Feb 1997 12:04:18 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA08336; Sun, 2 Feb 1997 13:02:42 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702022002.NAA08336@phaeton.artisoft.com>
Subject: Re: Mounting CD-ROM when data not on first track
To: joerg_wunsch@uriah.heep.sax.de
Date: Sun, 2 Feb 1997 13:02:42 -0700 (MST)
Cc: freebsd-hackers@freebsd.org
In-Reply-To: <Mutt.19970202101850.j@uriah.heep.sax.de> from "J Wunsch" at Feb 2, 97 10:18:50 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > But it's not a data area... or rather, it's not a 'data' area.
> 
> Doesn't matter.  Disk frame numbers don't distinguish between data or
> audio areas.  Things like the CD9660 code are meant in terms of disk
> frame numbers however, so you have to hole out the !data areas.  They
> are valid frame numbers (block numbers in the SCSI sense), it's only
> that you cannot READ them.

It matters, in that this disc is not mountable by FreeBSD.  We need to
blame FreeBSD, not the disc... "be generous in what you accept,
conservative in what you generate".

> > Does anyone else have this CD?  Do you have a MacOS or SunOS or older
> > Windows box with ASPI or proprietary CDROM driver you can try it in?
> > If the non-Joliet aware OS recognizes it, I'd think that the FreeBSD
> > interpretation is probably wrong.
> 
> FreeBSD doesn't have any interpretation at all by now, so you don't
> need this contest.  Its only `interpretation' by now is ``all the
> world's a data disk from the beginning through the end, and we assume
> the directory tree won't touch outside the disk area''.

FreeBSD is interpreting audio data as 'data'.  Perhaps it should not
be doing this.  Yes, this causes problems for the CD player and audio
data reading code, which is why I suggested the c/d "slices".


> > The software we run on our mastering burners here knows about writing
> > additional sessions.
> 
> We are looking forward to your submission.  Please, contact
> ports@freebsd.org to make it a new port.
> 
> Uh, it's not available in source form?  Too bad. :-)]

Uh, it's commercial software we didn't write which runs only on
Windows95.

> >   It seems that
> > Microsoft (stupidly) can not force a program image to be entirely
> > resident in memory, and will blue-screen if the image is from a disc
> > that has been removed, and it wants to page from it.
> 
> Why do you call this `stupid'?  That's the same way every Unix does.
> It's only that they probably miss the mount philosophy, so they could
> have locked the medium until it will no longer be required for paging.

Uh, "sticky bit"... I can solve the problem in UNIX.  The DDK says I
can resolve this problem in Windows95 as well, but the procedure
described (marking the segments "preload") doesn't work.

> > Why would you need 99 sub-devices?
> 
> Because it's the most logical way.  I don't wanna enforce a policy
> (like ISO-9660) in the device driver, since that's a matter of the
> filesystem code.  A non-CD9660 CD for example might contain up to 99
> UFS filesystems, one per each track, which are fully self-contained
> (i.e., with block numbers relative to the start of the track, as any
> UFS used to have).

Heh.  Then you probably want to impose a "partitioning schema" outside
the scope of the physical device driver.  You'd do this using devfs
and a logical-to-physical translation layer that knew to break it up
into one device per track.


					Regards,
					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Sun Feb  2 12:09:23 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA08423
          for hackers-outgoing; Sun, 2 Feb 1997 12:09:23 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA08417
          for <hackers@freebsd.org>; Sun, 2 Feb 1997 12:09:14 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA08382; Sun, 2 Feb 1997 13:07:39 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702022007.NAA08382@phaeton.artisoft.com>
Subject: Re: bisdn
To: grog@lemis.de
Date: Sun, 2 Feb 1997 13:07:39 -0700 (MST)
Cc: terry@lambert.org, hackers@freebsd.org
In-Reply-To: <199702021029.LAA10731@freebie.lemis.de> from "grog@lemis.de" at Feb 2, 97 11:29:48 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Oh really?  Do you get D channels?  What do you do with them?

Basic rate:	2B+D
US West:	2D+B

> > Think about what hardware the phone company provides for an ISDN
> > user over there, but doesn't provide for an ISDN user over here...
> 
> An NT1?  It doesn't do HDLC.

No, but it much more standardized for transport encapsulation than
what we have over here.

We have places using "ISDN" without NT1 at all.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Sun Feb  2 12:13:47 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA08658
          for hackers-outgoing; Sun, 2 Feb 1997 12:13:47 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA08650
          for <hackers@FreeBSD.ORG>; Sun, 2 Feb 1997 12:13:38 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA08403; Sun, 2 Feb 1997 13:10:51 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702022010.NAA08403@phaeton.artisoft.com>
Subject: Re: g++, STL and -frepo on FreeBSD-2.2-Beta
To: bakul@torrentnet.com (Bakul Shah)
Date: Sun, 2 Feb 1997 13:10:50 -0700 (MST)
Cc: ejc@gargoyle.bazzle.com, terry@lambert.org, hackers@FreeBSD.ORG
In-Reply-To: <199702021539.KAA21607@chai.plexuscom.com> from "Bakul Shah" at Feb 2, 97 10:39:52 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > 	I do know that if you build g++ with John Polstra's ELF patches
> > and the -frepo patches.  Then template repository works as advertised.
> 
> Where do I find John's ELF patches?

I don't know how current they are, etc.  You combined two peoples
messages; the material that is validly attributable to me is only
the first quoted region; sorry.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Sun Feb  2 12:50:44 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA12410
          for hackers-outgoing; Sun, 2 Feb 1997 12:50:44 -0800 (PST)
Received: from sax.sax.de (sax.sax.de [193.175.26.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA12402
          for <freebsd-hackers@freebsd.org>; Sun, 2 Feb 1997 12:50:41 -0800 (PST)
Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA02138 for freebsd-hackers@freebsd.org; Sun, 2 Feb 1997 21:50:39 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id VAA08569; Sun, 2 Feb 1997 21:44:55 +0100 (MET)
Message-ID: <Mutt.19970202214454.j@uriah.heep.sax.de>
Date: Sun, 2 Feb 1997 21:44:54 +0100
From: j@uriah.heep.sax.de (J Wunsch)
To: freebsd-hackers@freebsd.org
Subject: Re: Mounting CD-ROM when data not on first track
References: <Mutt.19970202101850.j@uriah.heep.sax.de> <199702022002.NAA08336@phaeton.artisoft.com>
X-Mailer: Mutt 0.55-PL10
Mime-Version: 1.0
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <199702022002.NAA08336@phaeton.artisoft.com>; from Terry Lambert on Feb 2, 1997 13:02:42 -0700
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

As Terry Lambert wrote:

> > > But it's not a data area... or rather, it's not a 'data' area.
> > 
> > Doesn't matter.

> It matters, in that this disc is not mountable by FreeBSD.

But that's not due to the fact that FreeBSD doesn't start to remap the
block/frame numbers, but due to the fact that FreeBSD's cd9660
filesystem stuff doesn't care for the TOC at all.

Don't try to `fix' something by uglifying it.

> blame FreeBSD, not the disc...

Nobody has ever claimed that FreeBSD would DTRT.

> FreeBSD is interpreting audio data as 'data'.

No, it isn't interpreting it at all.  It doesn't care for the d*mn TOC
yet.

> > Why do you call this `stupid'?  That's the same way every Unix does.
> > It's only that they probably miss the mount philosophy, so they could
> > have locked the medium until it will no longer be required for paging.
> 
> Uh, "sticky bit"... I can solve the problem in UNIX.

Sticky bit?  Terry, you're riding your time-machine again, you're
currently some ten years back.

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

From owner-freebsd-hackers  Sun Feb  2 12:59:59 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA13172
          for hackers-outgoing; Sun, 2 Feb 1997 12:59:59 -0800 (PST)
Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA13164
          for <hackers@freefall.freebsd.org>; Sun, 2 Feb 1997 12:59:57 -0800 (PST)
Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.7.3) with ESMTP id MAA02138; Sun, 2 Feb 1997 12:57:58 -0800 (PST)
Message-Id: <199702022057.MAA02138@rah.star-gate.com>
X-Mailer: exmh version 1.6.9 8/22/96
To: Narvi <narvi@haldjas.folklore.ee>
cc: Terry Lambert <terry@lambert.org>, gurney_j@resnet.uoregon.edu,
        hackers@freefall.freebsd.org
Subject: Re: performance puzzler 
In-reply-to: Your message of "Sun, 02 Feb 1997 20:20:55 +0200."
             <Pine.BSF.3.95.970202201858.13473A-100000@haldjas.folklore.ee> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 02 Feb 1997 12:57:58 -0800
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>From The Desk Of Narvi :

> Where did I read about 66Mhz revision/mode for PCI? Was it in a dream or
> just a "not supported by anybody yet" possibility as is the 64bit card
> width. Or was it all just a dream or erroneus news article?

PCI 2.0 specifies a new 66MHz mode which has been implemented
I believe by SUN. I would look into DEC's Alpha also.

	Amancio


 



From owner-freebsd-hackers  Sun Feb  2 13:28:46 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA15391
          for hackers-outgoing; Sun, 2 Feb 1997 13:28:46 -0800 (PST)
Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA15385
          for <freebsd-hackers@freefall.freebsd.org>; Sun, 2 Feb 1997 13:28:39 -0800 (PST)
Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id IAA25120; Mon, 3 Feb 1997 08:31:24 +1100 (EST)
Date: Mon, 3 Feb 1997 08:31:23 +1100 (EST)
From: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
To: Christoph Kukulies <kuku@gilberto.physik.rwth-aachen.de>
cc: freebsd-hackers@freefall.freebsd.org
Subject: Re: squid 1.1.4
In-Reply-To: <199702021604.RAA00260@gilberto.physik.rwth-aachen.de>
Message-ID: <Pine.BSF.3.91.970203083036.263d-100000@panda.hilink.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk



On Sun, 2 Feb 1997, Christoph Kukulies wrote:

> It looks like the squid daemon is running fine. Only when I try to 
> connect via squid to the outside world I'm getting this:
>       
> isdn-kuku> tail -f /usr/local/squid/logs/access.log
> 854896136.897   6655 192.168.1.126 ERR_CONNECT_FAIL/400 837 GET http://www.freebsd.org/ - SINGLE_PARENT/www-proxy.informatik.rwth-aachen.de -
> 854898046.079    269 192.168.1.126 ERR_CONNECT_FAIL/400 842 GET http://www.freebsd.org/ - SINGLE_PARENT/www-proxy.informatik.rwth-aachen.de -              

Have you tried running with no neighbours/parents to start with?  It 
looks like you are not connecting with your parent.

Danny

From owner-freebsd-hackers  Sun Feb  2 13:48:27 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA16974
          for hackers-outgoing; Sun, 2 Feb 1997 13:48:27 -0800 (PST)
Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA16962;
          Sun, 2 Feb 1997 13:48:17 -0800 (PST)
Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.7.3) with ESMTP id NAA02400; Sun, 2 Feb 1997 13:48:13 -0800 (PST)
Message-Id: <199702022148.NAA02400@rah.star-gate.com>
X-Mailer: exmh version 1.6.9 8/22/96
To: "Kenneth P. Stox" <ken@stox.pr.mcs.net>
cc: multimedia@freebsd.org, hackers@freebsd.org
Subject: Hardware for video
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 02 Feb 1997 13:48:13 -0800
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk



It is kind of tricky to get a fast PC nowdays. The issues are 
memory bandwith and PCI bus implementation. The Triton seems to
be well implemented where as the Natoma, found in PPRO, I have
my doubts about.

For instance, I have a P100 / Triton chipset over here and a
PPRO 200MHz / Natoma chipset.

On the PPRO 200MHz , I get a few dma errors while capturing where as
in the P100 I get less dma errors . The condition of both implementations
with respect to video is that I get a better image capture/display at
640x480 32bits 30fps on the P100 than on the PPRO 200MHz.


The PPROs 200MHz are nice for number crunching for instance, metgrab
( http://www.ishiboo.com/~nirva/Projects/metgrab/ )  is a cool
video capture application which does real time video effects however
you need a PPRO for this baby. For applications such as metgrab, 
the more memory bandwith available to the system the better it is.
Unfortunalty, the Natoma chipset does not offer support for SDRAM
and the best that we can do is get 50ns EDO ram.
So for Pentium systems the fastest memory for video operations is
SDRAM. For Pentium PRos with Natoma chipset is 50 ns EDO.

For video capture to disk, is a little bit more tricky because I am not
up to date with the fastest scsi disks. It is almost a safe bet that you 
will need ccd (concatenated disk driver) and more than one disk. You always can 
do "man ccd" to find out more about it.

On the video display side you want something like an S3 968  PCI based
card with VRAM -- a fast video controller coupled with fast memory.

Playing with video applications you can eat up your color palette pretty
quickly so must of the time I run at 32bits with a resolution of 
1024x768 with my Diamond Stealth 64 video (s3 968) with 4MB of memory of VRAM.

Corrections of comments are welcomed.

	Enjoy,
	Amancio






From owner-freebsd-hackers  Sun Feb  2 13:50:45 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA17137
          for hackers-outgoing; Sun, 2 Feb 1997 13:50:45 -0800 (PST)
Received: from relay.nuxi.com (nuxi.ucdavis.edu [128.120.37.176])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA17118;
          Sun, 2 Feb 1997 13:50:41 -0800 (PST)
Received: from dragon.nuxi.com (reqd-042.ucdavis.edu [128.120.251.162]) by relay.nuxi.com (8.8.4/8.6.12) with ESMTP id NAA06290; Sun, 2 Feb 1997 13:50:47 -0800 (PST)
Received: (from obrien@localhost) by dragon.nuxi.com (8.8.4/8.7.3) id NAA20378; Sun, 2 Feb 1997 13:50:50 -0800 (PST)
Message-ID: <19970202135048.PN07710@dragon.nuxi.com>
Date: Sun, 2 Feb 1997 13:50:48 -0800
From: obrien@NUXI.com (David O'Brien)
To: freebsd-ports@freebsd.org (FreeBSD ports list)
Cc: hackers@freebsd.org
Subject: conditionally including <sys/param.h>
References: <199701280143.RAA06503@freefall.freebsd.org> <Pine.OSF.3.95q.970127210526.2115E-100000@uplink.eng.umd.edu>
X-Mailer: Mutt 0.59-PL19
Mime-Version: 1.0
Organization: The NUXI *BSD group
X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3  90 76 5D 69 58 D9 98 7A
X-Pgp-Keyid: 34F9F9D5
In-Reply-To: <Pine.OSF.3.95q.970127210526.2115E-100000@uplink.eng.umd.edu>; from Chuck Robey on Jan 27, 1997 21:08:40 -0500
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Sorry to have to bring this back to light...
I was under the impression that we had agreed that
"#if (defined(__unix__) || defined(unix))" was the best way to
conditionally include <sys/param.h>.  However, this email from Chuck,
implies that this is a Bad Thing.

So to re-hash this, what does the list think is the best way to have an
easy way to include <sys/param.h>?  Even thought I don't have all the
*BSD folks in my grips like I did at USENIX, I'm still not above trying
to get a new cpp symbol added (like __44bsd__ or something).

Chuck Robey writes:
> > obrien      97/01/27 17:43:23
> >   Modified:    share/doc/handbook  porting.sgml
> >   Document the "#if (defined(__unix__) || defined(unix))" way of including
> >   sys/param.h.  Change _HAVE_PARAM_H to "HAVE_SYS_PARAM_H" for those who
> >   still like this method -- leading underscores are in the compiler/library
> >   name space and the Ollivier says to follow GNU Autoconf anyway.
> 
> That test is completely bogus, cause it passes for all sysv systems,
> which _don't_ have sys/param.h.  It's a completely useless test, and
> someone justified it by saying that "most systems have a sys/param.h
> anyhow".
> 
> What (in my own opinion) should have been done is to detect:
> 
> #ifdef FreeBSD || NetBSD || OpenBSD
> 
> that would have worked for those variants.  Would be able to find out the
> one for BSDi systems, then we'd have a great deal of the important ones.
> That's how X11R6 does it.

-- 
-- David	(obrien@NUXI.com  -or-  obrien@FreeBSD.org)

From owner-freebsd-hackers  Sun Feb  2 14:25:10 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA18408
          for hackers-outgoing; Sun, 2 Feb 1997 14:25:10 -0800 (PST)
Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA18403
          for <hackers@freebsd.org>; Sun, 2 Feb 1997 14:25:05 -0800 (PST)
Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5])
          by mail.cdsnet.net (8.8.4/8.7.3) with SMTP id OAA14601;
          Sun, 2 Feb 1997 14:24:59 -0800 (PST)
Date: Sun, 2 Feb 1997 14:24:57 -0800 (PST)
From: Jaye Mathisen  <mrcpu@cdsnet.net>
To: Michael Beckmann <petzi@apfel.de>
cc: hackers@freebsd.org
Subject: Re: 2.2-BETA: options MAXMEM not working (fwd)
In-Reply-To: <v03010d01af185b3c28e5@[195.52.251.6]>
Message-ID: <Pine.NEB.3.95.970202142426.13493B-100000@mail.cdsnet.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Hmmm, the same box that I was referring to uses ccd as well.  The 3940
driver has problems, but they haven't been memory related.

On Sat, 1 Feb 1997, Michael Beckmann wrote:

> >Hmmm, I have a 2.2 box with 256MB RAM, and it sees it all just fine using
> >the kernel option.
> 
> My kernel has the ccd enabled. I think there was another problem report
> about an interference with ccd...
> 
> Cheers,
> 
> Michael
> 
> 


From owner-freebsd-hackers  Sun Feb  2 16:31:19 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id QAA24583
          for hackers-outgoing; Sun, 2 Feb 1997 16:31:19 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id QAA24569
          for <freebsd-hackers@FreeBSD.ORG>; Sun, 2 Feb 1997 16:31:16 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA09896; Sun, 2 Feb 1997 17:29:32 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702030029.RAA09896@phaeton.artisoft.com>
Subject: Re: Mounting CD-ROM when data not on first track
To: joerg_wunsch@uriah.heep.sax.de
Date: Sun, 2 Feb 1997 17:29:32 -0700 (MST)
Cc: freebsd-hackers@FreeBSD.ORG
In-Reply-To: <Mutt.19970202214454.j@uriah.heep.sax.de> from "J Wunsch" at Feb 2, 97 09:44:54 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > > > But it's not a data area... or rather, it's not a 'data' area.
> > > 
> > > Doesn't matter.
> 
> > It matters, in that this disc is not mountable by FreeBSD.
> 
> But that's not due to the fact that FreeBSD doesn't start to remap the
> block/frame numbers, but due to the fact that FreeBSD's cd9660
> filesystem stuff doesn't care for the TOC at all.
> 
> Don't try to `fix' something by uglifying it.

You mean, like putting in partition recognition code in the kernel
instead of putting it in the FS instead (like you are suggesting here)?

I have to disagree with you.  They are all members of the same class
of logical device creation...

> > > Why do you call this `stupid'?  That's the same way every Unix does.
> > > It's only that they probably miss the mount philosophy, so they could
> > > have locked the medium until it will no longer be required for paging.
> > 
> > Uh, "sticky bit"... I can solve the problem in UNIX.
> 
> Sticky bit?  Terry, you're riding your time-machine again, you're
> currently some ten years back.

If you will recall, I've requested the ability to force images totally
into local cache on a per FS basis by attributing the FS as "nonlocal".
The default behaviour would not do this, but in the case of a large
number of diskless machines waiting for a server reboot, it would be
a generally "Good Thing".  In the case of the sticky bit on an
single executable, if the ability to force into local cache existed,
then the force should be done.

The force should be done in any case for FS objects being used as
backing store which have been removed, so that the reference does
not go out of scope... otherwise, it will be impossible to implement
"savestate" type "shutdowns".

So you recall the discussion on how to make an install occur in about
30 seconds by restoring a running installation session and making a
tiny number of tweaks?

In any case, it is a generally useful enabling technology.  Having the
machine not barf when running from CD is just an extra bonus.


					Regards,
					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Sun Feb  2 17:50:39 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA00413
          for hackers-outgoing; Sun, 2 Feb 1997 17:50:39 -0800 (PST)
Received: from dg-rtp.dg.com ([128.222.1.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id RAA00406
          for <hackers@FreeBSD.ORG>; Sun, 2 Feb 1997 17:50:37 -0800 (PST)
Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02)
	id AA22124; Sun, 2 Feb 1997 20:50:04 -0500
Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Sun,  2 Feb 1997 20:50 EST
Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id UAA02990; Sun, 2 Feb 1997 20:17:54 -0500 (EST)
Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id UAA18377; Sun, 2 Feb 1997 20:22:10 -0500 (EST)
Date: Sun, 2 Feb 1997 20:22:10 -0500 (EST)
From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
Message-Id: <199702030122.UAA18377@lakes.water.net>
To: ponds!FreeBSD.ORG!hackers, ponds!NUXI.com!obrien
Subject: Re: conditionally including <sys/param.h>
Content-Type: text
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 
> Sorry to have to bring this back to light...
> I was under the impression that we had agreed that
> "#if (defined(__unix__) || defined(unix))" was the best way to
> conditionally include <sys/param.h>.  However, this email from Chuck,
> implies that this is a Bad Thing.

Unfortunately the symbols:
	unix
	FreeBSD
	NetBSD
	OpenBSD

violate the user's name space.  For example, I have programs
that define some of these on the command line.  If these were defined
elsewhere things would break.  [Of course, such things do break
on other hosts; e.g. SunOS 4.x defines "unix".]

I would suggest using:
	__unix__
	__FreeBSD__
	__NetBSD__
	__OpenBSD__

as identifiers beginning with "_" are reserved (per ANSI) for the
implementation.

	- Dave Rivers -


> 
> So to re-hash this, what does the list think is the best way to have an
> easy way to include <sys/param.h>?  Even thought I don't have all the
> *BSD folks in my grips like I did at USENIX, I'm still not above trying
> to get a new cpp symbol added (like __44bsd__ or something).
> 
> Chuck Robey writes:
> > > obrien      97/01/27 17:43:23
> > >   Modified:    share/doc/handbook  porting.sgml
> > >   Document the "#if (defined(__unix__) || defined(unix))" way of including
> > >   sys/param.h.  Change _HAVE_PARAM_H to "HAVE_SYS_PARAM_H" for those who
> > >   still like this method -- leading underscores are in the compiler/library
> > >   name space and the Ollivier says to follow GNU Autoconf anyway.
> > 
> > That test is completely bogus, cause it passes for all sysv systems,
> > which _don't_ have sys/param.h.  It's a completely useless test, and
> > someone justified it by saying that "most systems have a sys/param.h
> > anyhow".
> > 
> > What (in my own opinion) should have been done is to detect:
> > 
> > #ifdef FreeBSD || NetBSD || OpenBSD
> > 
> > that would have worked for those variants.  Would be able to find out the
> > one for BSDi systems, then we'd have a great deal of the important ones.
> > That's how X11R6 does it.
> 
> -- 
> -- David	(obrien@NUXI.com  -or-  obrien@FreeBSD.org)
> 

From owner-freebsd-hackers  Sun Feb  2 18:35:12 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id SAA02164
          for hackers-outgoing; Sun, 2 Feb 1997 18:35:12 -0800 (PST)
Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA02156
          for <hackers@freebsd.org>; Sun, 2 Feb 1997 18:35:07 -0800 (PST)
Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id NAA01680; Mon, 3 Feb 1997 13:04:15 +1030 (CST)
From: Michael Smith <msmith@atrad.adelaide.edu.au>
Message-Id: <199702030234.NAA01680@genesis.atrad.adelaide.edu.au>
Subject: Re: Jukka Ukkonen: POSIX.4 - scheduler once more (as you requested)
In-Reply-To: <199701311230.HAA12655@hda.hda.com> from Peter Dufault at "Jan 31, 97 07:30:49 am"
To: dufault@hda.com (Peter Dufault)
Date: Mon, 3 Feb 1997 13:04:14 +1030 (CST)
Cc: jkh@time.cdrom.com, hackers@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Peter Dufault stands accused of saying:
> One quick observation:
> 
> > X * 5. The source code must be available for anyone who wishes to have it.
> 
> What do people think of packaging this up as a user library against
> an LKM'd pseudo /dev/realtime driver?  I have the skeleton to do

How does this help the posix.4 scheduling model though?  Does having it as
an LKM still allow this to work "as expected"?

> that.  My reasoning is I'd like to be able to have different realtime
> facilities, for example, process migration to an attached embedded
> processor that would "fault" back as soon as you tried to do
> something in that environment.  It also gives you a way to have
> realtime user or group protection.

Sounds reasonable (and interesting).  Do you have more words on this 
somewhere?

> Peter Dufault (dufault@hda.com)   Realtime Machine Control and Simulation

-- 
]] Mike Smith, Software Engineer        msmith@gsoft.com.au             [[
]] Genesis Software                     genesis@gsoft.com.au            [[
]] High-speed data acquisition and      (GSM mobile)     0411-222-496   [[
]] realtime instrument control.         (ph)          +61-8-8267-3493   [[
]] Unix hardware collector.             "Where are your PEZ?" The Tick  [[

From owner-freebsd-hackers  Sun Feb  2 19:27:37 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA04683
          for hackers-outgoing; Sun, 2 Feb 1997 19:27:37 -0800 (PST)
Received: from labs.usn.blaze.net.au (labs.usn.blaze.net.au [203.17.53.30])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA04665;
          Sun, 2 Feb 1997 19:27:29 -0800 (PST)
Received: (from davidn@localhost)
	by labs.usn.blaze.net.au (8.8.5/8.8.5) id OAA15793;
	Mon, 3 Feb 1997 14:27:17 +1100 (EST)
Message-ID: <19970203142717.VR58445@usn.blaze.net.au>
Date: Mon, 3 Feb 1997 14:27:17 +1100
From: davidn@unique.usn.blaze.net.au (David Nugent)
To: obrien@NUXI.com (David O'Brien)
Cc: freebsd-ports@FreeBSD.ORG (FreeBSD ports list), hackers@FreeBSD.ORG
Subject: Re: conditionally including <sys/param.h>
References: <199701280143.RAA06503@freefall.freebsd.org> <Pine.OSF.3.95q.970127210526.2115E-100000@uplink.eng.umd.edu> <19970202135048.PN07710@dragon.nuxi.com>
X-Mailer: Mutt 0.59.1
Mime-Version: 1.0
In-Reply-To: <19970202135048.PN07710@dragon.nuxi.com>; from David O'Brien on Feb 2, 1997 13:50:48 -0800
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

David O'Brien writes:
> Sorry to have to bring this back to light...
> I was under the impression that we had agreed that
> "#if (defined(__unix__) || defined(unix))" was the best way to
> conditionally include <sys/param.h>.  However, this email from Chuck,
> implies that this is a Bad Thing.
~
> > That test is completely bogus, cause it passes for all sysv systems,
> > which _don't_ have sys/param.h.  It's a completely useless test, and
> > someone justified it by saying that "most systems have a sys/param.h
> > anyhow".

I said exactly this some weeks back and was told I was wrong,
contrary to my own experience of many years working with
sysv r3's. Oh well. :-)

svr4 apparently does have it, but not sysv before that. Most
if not all of those do predefine unix or __unix__.


Regards,

David Nugent - Unique Computing Pty Ltd - Melbourne, Australia
Voice +61-3-9791-9547  Data/BBS +61-3-9792-3507  3:632/348@fidonet
davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/

From owner-freebsd-hackers  Sun Feb  2 19:49:38 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA05591
          for hackers-outgoing; Sun, 2 Feb 1997 19:49:38 -0800 (PST)
Received: from Clifford.LiveNet.Net (root@Clifford.LiveNet.Net [206.156.5.13])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA05586
          for <hackers@FreeBSD.ORG>; Sun, 2 Feb 1997 19:49:36 -0800 (PST)
Received: from samantha (Manimal@Silver.Colours.LiveNet.Net [206.156.5.120]) by Clifford.LiveNet.Net (8.7.6/8.6.9) with ESMTP id WAA27251; Sun, 2 Feb 1997 22:54:45 -0500 (EST)
Message-Id: <199702030354.WAA27251@Clifford.LiveNet.Net>
From: "Joseph I. Arias" <BigDaddy@LiveNet.Net>
To: <terry@lambert.org>
Cc: <hackers@FreeBSD.ORG>
Subject: I can't install from dos partition
Date: Sun, 2 Feb 1997 22:50:02 -0800
X-MSMail-Priority: Normal
X-Priority: 3
X-Mailer: Microsoft Internet Mail 4.70.1155
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Hi I have a Pentium 133 
32 megs ram
1.1 gig c:\
2.7 gig cut down the middle making:
1.35 D:\
1.35 E:\

and I have a 2.1 GIG FREE for Unix

I have given this drive to Unix completely and have ran the boot install
I selected to give the whole drive to unix
I partitioned it this way
50M /
100M SWAP
200M /var
16??M /usr  ?? meaning the rest of the disk space

I start the install and it dies and give me this error:

Error mounting /dev/wd1s2 on /dos: invalid argument (22)

/dev/wd1s2 I believe would be drive E:\  and that is the drive I have
FreeBSD in. In the E:\FREEBSD directory

I was told it wouldn't work in a windows inviroment so I formated C:\ and
installed Dos version 6.22 and got the same message. I rawrite boot4.flp to
disk and boot off it I did all the installation option Novice , Quick, and
Expert with I found to be the easy of the all because of the fact that you
can go back and recheck your setting before comiting to anything I also
tryed to tell it to do exsisting file and pointed to them and it didn't
work... Now I have dont the operation without telling it to copy any files
and it does the partition corectly and all but it says I can't boot off
this drive because no files were installed.. I hope this will help you with
my problem I'm lost.

Thanks Joe

From owner-freebsd-hackers  Sun Feb  2 21:35:01 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA09669
          for hackers-outgoing; Sun, 2 Feb 1997 21:35:01 -0800 (PST)
Received: from k8lt.ampr.org (balrog.mv.com [199.125.64.248])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id VAA09656
          for <hackers@freefall.freebsd.org>; Sun, 2 Feb 1997 21:34:57 -0800 (PST)
Received: by k8lt.ampr.org (Smail3.1.27.1 #9)
	id m0vrH2J-000OGMC; Mon, 3 Feb 97 00:33 EST
Message-Id: <m0vrH2J-000OGMC@k8lt.ampr.org>
X-Mailer: exmh version 1.6.2 7/18/95
To: Narvi <narvi@haldjas.folklore.ee>
cc: hackers@freefall.freebsd.org
Subject: Re: performance puzzler 
In-reply-to: Your message of "Sun, 02 Feb 1997 20:20:55 +0200."
             <Pine.BSF.3.95.970202201858.13473A-100000@haldjas.folklore.ee> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 03 Feb 1997 00:33:47 -0500
From: "Gary L. Grebus" <glg@balrog.k8lt.ampr.org>
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> Where did I read about 66Mhz revision/mode for PCI? Was it in a dream or
> just a "not supported by anybody yet" possibility as is the 64bit card
> width. Or was it all just a dream or erroneus news article?
> 

Revision 2.0 of the PCI Specification added both 64 bit wide and 66 MHz versions of the bus.  I'm not aware of any shipping 66 MHz PCI, but most of the current Digital Alpha systems (and I think some 3rd party Alpha motherboards) include 64 bit slots.  

FWIW, the spec requires that 64 bit cards work when plugged into 32 bit slots, and 32 bit cards work when plugged into 64 bit slots.

Regards,

/gary

Gary L. Grebus		Home:  glg@k8lt.ampr.org
Brookline, NH           Work:  grebus@zk3.dec.com



From owner-freebsd-hackers  Mon Feb  3 00:12:18 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id AAA14572
          for hackers-outgoing; Mon, 3 Feb 1997 00:12:18 -0800 (PST)
Received: from diablo.ppp.de (diablo.ppp.de [193.141.101.34])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id AAA14567
          for <hackers@freebsd.org>; Mon, 3 Feb 1997 00:12:13 -0800 (PST)
Received: from freebie.lemis.de by diablo.ppp.de with smtp
	(Smail3.1.28.1 #1) id m0vrJVZ-000Qa8C; Mon, 3 Feb 97 09:12 MET
Received: (grog@localhost) by freebie.lemis.de (8.8.4/8.6.12) 
       id HAA22553; Mon, 3 Feb 1997 07:52:41 +0100 (MET)
From: grog@lemis.de
Message-Id: <199702030652.HAA22553@freebie.lemis.de>
Subject: Re: bisdn
In-Reply-To: <199702022007.NAA08382@phaeton.artisoft.com> from Terry Lambert at "Feb 2, 97 01:07:39 pm"
To: terry@lambert.org (Terry Lambert)
Date: Mon, 3 Feb 1997 07:52:40 +0100 (MET)
Cc: hackers@freebsd.org (FreeBSD Hackers)
Organisation: 	LEMIS, Schellnhausen 2, 36325 Feldatal, Germany
Phone: +49-6637-919123
Fax: +49-6637-919122
Reply-to: grog@lemis.de (Greg Lehey)
WWW-Home-Page: http://www.FreeBSD.org/~grog
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Terry Lambert writes:
>>  Oh really?  Do you get D channels?  What do you do with them?
>
> Basic rate:	2B+D

OK.  Note the second question: what do you do with them?

> US West:	2D+B

Really?  I find that hard to believe.  I suppose the question is
doubly relevant here: What do you do with them?

>>>  Think about what hardware the phone company provides for an ISDN
>>>  user over there, but doesn't provide for an ISDN user over here...
>>
>>  An NT1?  It doesn't do HDLC.
>
> No, but it much more standardized for transport encapsulation than
> what we have over here.
>
> We have places using "ISDN" without NT1 at all.

You still haven't realized the real error of your statement.  D
channels are signalling channels, and they use LAP-D, which bases on
HDLC.

Greg


From owner-freebsd-hackers  Mon Feb  3 00:50:37 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id AAA15935
          for hackers-outgoing; Mon, 3 Feb 1997 00:50:37 -0800 (PST)
Received: from sax.sax.de (sax.sax.de [193.175.26.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id AAA15930
          for <freebsd-hackers@FreeBSD.ORG>; Mon, 3 Feb 1997 00:50:33 -0800 (PST)
Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA24138 for freebsd-hackers@FreeBSD.ORG; Mon, 3 Feb 1997 09:50:30 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id JAA12593; Mon, 3 Feb 1997 09:30:55 +0100 (MET)
Message-ID: <Mutt.19970203093055.j@uriah.heep.sax.de>
Date: Mon, 3 Feb 1997 09:30:55 +0100
From: j@uriah.heep.sax.de (J Wunsch)
To: freebsd-hackers@FreeBSD.ORG
Subject: Re: Mounting CD-ROM when data not on first track
References: <Mutt.19970202214454.j@uriah.heep.sax.de> <199702030029.RAA09896@phaeton.artisoft.com>
X-Mailer: Mutt 0.55-PL10
Mime-Version: 1.0
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <199702030029.RAA09896@phaeton.artisoft.com>; from Terry Lambert on Feb 2, 1997 17:29:32 -0700
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

As Terry Lambert wrote:

> > Don't try to `fix' something by uglifying it.
> 
> You mean, like putting in partition recognition code in the kernel
> instead of putting it in the FS instead (like you are suggesting here)?

No.  These dreaded CD-ROM tracks have one thing different from normal
partitions: the filesystem code in it still references the disk by
absolute frame (block) numbers.  Filesystems that live in partitions
do not do this, they describe the filesystem relative to the start of
the partition.

The CD code needs both.  The one-partition-per-track is needed for
things like putting up to 99 UFS filesystems on a disk.  As i wrote,
i've once got a sample implementation for this, but later realized
that this is not very useful because it's not what ISO-9660 is using.

The one large partition covering everything (and leaving holes for the
audio tracks) is what we've already got by now.  It is the model that
underlies ISO-9660.  So the only thing that is needed is to find out
about the position of the root directory is to see what's the track to
read this from.  You can learn this from the CD-ROM TOC.  Reading the
TOC (CD-ROM metadata) as part of the normal CD-ROM data stream doesn't
fit into the model.  Mapping the TOC at the beginning of the data
stream (and offset all data blocks) would be terrible, and defeats the
idea of being able to test an ISO-9660 image e.g. on a vn device, even
if it's not multi-session.  Mapping the TOC into negative device
offsets isn't more elegant either.

So in the end, i found that this _is_ a cd9660 matter infact (and not
true device partitioning), so it doesn't violate the layering idea too
much to have the cd9660 filesystem code doing the investigation of its
own -- by calling the CD-ROM ioctl.  Sure, you lose for an ISO-9660
``multi-session'' image on a vn device, but i don't have an idea how
to solve this, other than by allowing an explicit block number to be
passed to the mount_cd9660 command to tell it where to look for the
directory.

> > > Uh, "sticky bit"... I can solve the problem in UNIX.
> > 
> > Sticky bit?  Terry, you're riding your time-machine again, you're
> > currently some ten years back.
> 
> If you will recall, I've requested the ability to force images totally
> into local cache on a per FS basis by attributing the FS as "nonlocal".

Sorry, i misread your comment and thought you were referring to
something that does already exist.

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

From owner-freebsd-hackers  Mon Feb  3 01:10:05 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id BAA16647
          for hackers-outgoing; Mon, 3 Feb 1997 01:10:05 -0800 (PST)
Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA16613
          for <hackers@freebsd.org>; Mon, 3 Feb 1997 01:09:57 -0800 (PST)
Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.5/CET-v2.1) with SMTP id JAA08741; Mon, 3 Feb 1997 09:09:46 GMT
Date: Mon, 3 Feb 1997 18:09:46 +0900 (JST)
From: Michael Hancock <michaelh@cet.co.jp>
To: grog@lemis.de
cc: Terry Lambert <terry@lambert.org>, FreeBSD Hackers <hackers@freebsd.org>
Subject: Re: bisdn
In-Reply-To: <199702030652.HAA22553@freebie.lemis.de>
Message-ID: <Pine.SV4.3.95.970203180631.8689A-100000@parkplace.cet.co.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Mon, 3 Feb 1997 grog@lemis.de wrote:

> Terry Lambert writes:
> >
> > Basic rate:	2B+D
> 
> OK.  Note the second question: what do you do with them?
> 
> > US West:	2D+B
> 
> Really?  I find that hard to believe.  I suppose the question is
> doubly relevant here: What do you do with them?

I find this hard to believe too, 2D channels is wierd.  The D-channel is
for out-of-band signaling.  It's why you get 64K instead of 56K. 

Regards,


Mike Hancock


From owner-freebsd-hackers  Mon Feb  3 01:47:56 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id BAA18094
          for hackers-outgoing; Mon, 3 Feb 1997 01:47:56 -0800 (PST)
Received: from weblin (root@www.ExtraNet.RU [194.84.75.4])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA18085
          for <hackers@freebsd.org>; Mon, 3 Feb 1997 01:47:46 -0800 (PST)
Received: by weblin
	via sendmail with stdio
	id <m0vrKvF-0001ZbC@weblin>
	for hackers@freebsd.org; Mon, 3 Feb 1997 12:42:45 +0300 (MSK)
	(Smail-3.2 1996-Jul-4 #2 built 1996-Sep-25)
Message-Id: <m0vrKvF-0001ZbC@weblin>
Date: Mon, 3 Feb 97 12:38:50 +0700
From: Dmitry Romanov <DRomanov@ExtraNet.RU>
To: hackers@freebsd.org
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

LIST
HELP

Sincerely,
Dmitry. (DRomanov@extranet.ru)


From owner-freebsd-hackers  Mon Feb  3 01:50:58 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id BAA18255
          for hackers-outgoing; Mon, 3 Feb 1997 01:50:58 -0800 (PST)
Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA18244
          for <freebsd-hackers@freefall.freebsd.org>; Mon, 3 Feb 1997 01:50:50 -0800 (PST)
Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12)
	with ESMTP id KAA14935; Mon, 3 Feb 1997 10:50:46 +0100 (MET)
Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.8.4/8.6.9) id KAA06952; Mon, 3 Feb 1997 10:52:29 +0100 (MET)
Message-ID: <Mutt.19970203105228.kuku@gil.physik.rwth-aachen.de>
Date: Mon, 3 Feb 1997 10:52:28 +0100
From: kuku@gilberto.physik.rwth-aachen.de (Christoph Kukulies)
To: danny@panda.hilink.com.au (Daniel O'Callaghan)
Cc: kuku@gilberto.physik.rwth-aachen.de (Christoph Kukulies),
        freebsd-hackers@freefall.freebsd.org
Subject: Re: squid 1.1.4
References: <Pine.BSF.3.91.970203083036.263d-100000@panda.hilink.com.au> <199702021604.RAA00260@gilberto.physik.rwth-aachen.de>
X-Mailer: Mutt 0.58e
Mime-Version: 1.0
In-Reply-To: <Pine.BSF.3.91.970203083036.263d-100000@panda.hilink.com.au>; from Daniel O'Callaghan on Feb 3, 1997 08:31:23 +1100
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Daniel O'Callaghan writes:
> 
> 
> On Sun, 2 Feb 1997, Christoph Kukulies wrote:
> 
> > It looks like the squid daemon is running fine. Only when I try to 
> > connect via squid to the outside world I'm getting this:
> >       
> > isdn-kuku> tail -f /usr/local/squid/logs/access.log
> > 854896136.897   6655 192.168.1.126 ERR_CONNECT_FAIL/400 837 GET http://www.freebsd.org/ - SINGLE_PARENT/www-proxy.informatik.rwth-aachen.de -
> > 854898046.079    269 192.168.1.126 ERR_CONNECT_FAIL/400 842 GET http://www.freebsd.org/ - SINGLE_PARENT/www-proxy.informatik.rwth-aachen.de -              
> 
> Have you tried running with no neighbours/parents to start with?  It 
> looks like you are not connecting with your parent.

Yes, that had been the problem. It works now (see prev posting).

> 
> Danny

-- 
--Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de

From owner-freebsd-hackers  Mon Feb  3 02:21:39 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA20965
          for hackers-outgoing; Mon, 3 Feb 1997 02:21:39 -0800 (PST)
Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA20947
          for <hackers@freebsd.org>; Mon, 3 Feb 1997 02:21:26 -0800 (PST)
Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id VAA28876; Mon, 3 Feb 1997 21:24:46 +1100 (EST)
Date: Mon, 3 Feb 1997 21:24:45 +1100 (EST)
From: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
To: Michael Hancock <michaelh@cet.co.jp>
cc: grog@lemis.de, Terry Lambert <terry@lambert.org>,
        FreeBSD Hackers <hackers@freebsd.org>
Subject: Re: bisdn
In-Reply-To: <Pine.SV4.3.95.970203180631.8689A-100000@parkplace.cet.co.jp>
Message-ID: <Pine.BSF.3.91.970203212237.25849D-100000@panda.hilink.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk



On Mon, 3 Feb 1997, Michael Hancock wrote:

> I find this hard to believe too, 2D channels is wierd.  The D-channel is
> for out-of-band signaling.  It's why you get 64K instead of 56K. 

Oh?  According to the ISDN specs I've read basic rate ISDN is 2B+D, as 
2 * 64 + 1 * 16.  Do the Japanese use American ISDN?

Danny

From owner-freebsd-hackers  Mon Feb  3 02:26:44 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA21422
          for hackers-outgoing; Mon, 3 Feb 1997 02:26:44 -0800 (PST)
Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA20986
          for <hackers@freefall.freebsd.org>; Mon, 3 Feb 1997 02:21:52 -0800 (PST)
Received: from localhost (narvi@localhost)
          by haldjas.folklore.ee (8.8.4/8.8.4) with SMTP
	  id MAA17655; Mon, 3 Feb 1997 12:19:16 +0200 (EET)
Date: Mon, 3 Feb 1997 12:19:16 +0200 (EET)
From: Narvi <narvi@haldjas.folklore.ee>
Reply-To: Narvi <narvi@haldjas.folklore.ee>
To: Terry Lambert <terry@lambert.org>
cc: gurney_j@resnet.uoregon.edu, hackers@freefall.freebsd.org
Subject: Re: performance puzzler
In-Reply-To: <199702021951.MAA08288@phaeton.artisoft.com>
Message-ID: <Pine.BSF.3.95.970203111947.16664A-100000@haldjas.folklore.ee>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk



On Sun, 2 Feb 1997, Terry Lambert wrote:

> > > The PCI and EISA standards specify 33MHz as their top end.
> > 
> > Where did I read about 66Mhz revision/mode for PCI? Was it in a dream or
> > just a "not supported by anybody yet" possibility as is the 64bit card
> > width. Or was it all just a dream or erroneus news article?
> 
> The PCI SIG has been discussing this.  Obviously, the 64bit version
> can't use the same edge connector because there aren't 32 free lines;
> all this "64bit PCI card" hype claimed by video vendors is on-card
> data path, not bus data path.

I know. The graphics chip (and it's data path) can be of arbitary width.
There are at least also 128 bit ones. This is at least one thing I am
never confusing :-) Well, at the time (or about the time) PCI came out,
there definately was talk about 64 bit PCI slots.

> 
> The 66MHz has also been discussed, but requires a way to key the bus
> as to which type of card is present so it can introduce a wait state
> per cycle for older cards.

Well - the "obvious way" would be making different color connectors and
saying - You wanted it you got it. No slower than 66Mhz cards in the
<insert a colour here> slots. But it seems that (fortunately) PCI is no
longer a PC thing. 

> 
> One problem with the design is that the bus chaining used in current
> Intel chip designs won't work: you can't send 66MHz signals down a bus
> if you have 33MHz cards potentially listening or attempting to master
> the bus.  This basically means that the Intel PCI bus chips can't
> tie all the slots to the same chip lines, if you are going to try
> to use the same card connector.  This is a win, in that it means that
> we will finally get over the 4 slot limit imposed by the line drivers
> (which doesn't exist in the Motorola and Apple PCI chipsets because
> they were not lazy in their design).  It's bad, because it means
> new motherboard designs, and PCI has just settled down from the last
> minor revision to the spec..  8-(.

Well, the obvious way of doing things would have the main CPU to PCI
controller (provided we are going to have such a beast instead of say two
independent ones on the motherboard) to be 66Mhz/64 bit one wich would:

	a) export some (if any) 64 bit/66Mhz PCI slots
	b) act as a backbone for PCI bridges being 64 bit/66Mhz on one
	   side and having some number of "odinary" slots on the other.

b) is of help in the cases of any kind of concurent activity on the PCI
bus - both high speed/bandwidth cards and cards making large transfers to
each other over the PCI bus. Say I wanted to have in my computer a
PCI frame grabber, a PCI graphics board, PCI fast etrhernet adapter, a DSP
board, an Adaptec 3940 (well, this is already 5 cards on one PCI bus). It
may most efficent if the frame grabber sent its data directlt to the DSP
board or the graphics borad (making there be a constant flow of ~27 MB/sec
in the case of 640x480x30fps@24bits). 

Yes, it all is "high end" stuff. But I don't want to get stuck in the next
ISA bus witch will just become obsolete and remain still in use for long
time.

	Sander

> 
> 
> 					Terry Lambert
> 					terry@lambert.org
> ---
> Any opinions in this posting are my own and not those of my present
> or previous employers.
> 



From owner-freebsd-hackers  Mon Feb  3 02:30:33 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA21898
          for hackers-outgoing; Mon, 3 Feb 1997 02:30:33 -0800 (PST)
Received: from calvino.alaska.net (ice@calvino.alaska.net [206.149.65.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA21892
          for <Freebsd-Hackers@Freebsd.Org>; Mon, 3 Feb 1997 02:30:29 -0800 (PST)
Received: (from ice@localhost) by calvino.alaska.net (8.8.0/8.7.3) 
	id BAA01579 for Freebsd-Hackers@Freebsd.Org; Mon, 3 Feb 1997 01:30:26 -0900 (AKST)
X-Authentication-Warning: calvino.alaska.net: ice set sender to ice-bbs!steve.howe using -f
>Received: by ice-bbs.net (0.99.950303)
  id AA04021; 03 Feb 97 01:27:32 -0900
From: Steve.Howe@ice-bbs.net (Steve Howe)
Date: 03 Feb 97 01:26:43 -0900
Subject: un-ethical isp
Message-ID: <293_9702030127@ice-bbs.net>
Organization: ICE BBS Network Internet Gateway
To: Freebsd-Hackers@Freebsd.Org
Content-Type: text
Sender: owner-hackers@Freebsd.Org
X-Loop: FreeBSD.org
Precedence: bulk


Dear FreeBSDers,

because of your excellent OS and superb knowledge, i/we decided to use
FreeBSD in projects for the government subcontracting starting about 2
years ago.  an associate and boss became upset due to their fear of
UNIX and a sort of conspiracy developed ...

anyway - unbeknownst to me, the owners of my isp (alaska.net) were former
associates this vengeful/ignorant co-worker and boss, and together
(as i came close to finishing a project way ahead of their NT
project) they (isp) engaged in ping flooding all my machines
on my networks, grinding all my work to a complete halt for
a week, and additionally, after tracing the source of the
pinging and sending some nasty email, my isp transferred
all my email i had ever written on my personal/private
account to my boss and co-worker for review, ie, they
were looking for some goodies to get rid of me.
they hired private investigators, etc. but i
was squeaky clean, although things have
become miserable enough to quit. :)

ANYWAY - my question is, although my lawyer says my isp may be
liable for slander, is there any other recourse i can take for
them giving 2 1/2 years of my email from my personal/private
account to my boss and co-workers?  i wouldn't want laws,
but i despise un-ethical behaviour such as this!

it included health information related to my family,
love letters :), thoughts, etc.  all kinds of stuff
you'd never want anyone to see!

(pgp? - well not everyone i wrote to can use it!)

thanks ...  please mail to hmmm@ice-bbs.net.
a friend/co-worker is allowing me use of this
account as i have no isp currently ...
--
| Standard disclaimer: The views of the users are strictly their own.
| ICE BBS Network  +1-907-346-2371 (ANSI, 28.8k, FREE E-MAIL!).


From owner-freebsd-hackers  Mon Feb  3 02:43:13 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA22312
          for hackers-outgoing; Mon, 3 Feb 1997 02:43:13 -0800 (PST)
Received: from svr1.spark.net.hk (svr1.spark.net.hk [202.76.13.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA22305
          for <hackers@freebsd.org>; Mon, 3 Feb 1997 02:43:09 -0800 (PST)
Received: from svr1.spark.net.hk (william@svr1.spark.net.hk [202.76.13.1])
          by svr1.spark.net.hk (8.8.5/8.8.4) with SMTP
	  id SAA23519 for <hackers@freebsd.org>; Mon, 3 Feb 1997 18:42:31 +0800 (HKT)
Date: Mon, 3 Feb 1997 18:42:30 +0800 (HKT)
From: william <william@spark.net.hk>
To: hackers@freebsd.org
Subject: 2.2-BETA_A and popen
Message-ID: <Pine.BSF.3.91.970203181909.23445C-100000@svr1.spark.net.hk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


	I write a small cgi program which runs fine on 2.16 but it
fails to work on my 2.2-BETA_A. In the web server log - "malformed
header from script". If I comment out popen()..pclose(), then it works.
I am wondering if it's something wrong with the popen in 2.2-BETA or 
I'm doing it in a wrong way. I'm using apache web server. 

	The poppassd also fails to work on my 2.2-BETA too. 

----cgi program--
#include <stdlib.h>
#include <fcntl.h>
#include <stdio.h>

main (void )
{
    FILE *f;
    printf("Content-type: text/html%c%c",10,10);
    printf("<html><body><pre>\n");
    f = popen("/bin/ed test", "w");
    fprintf(f, "/%s\nd\nwq\n", "william");
    pclose(f);
    printf("</pre><br>End</body></html>");   
}
---end--


Best Regards,
william
--------------------------------------------------------


From owner-freebsd-hackers  Mon Feb  3 02:53:26 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA22737
          for hackers-outgoing; Mon, 3 Feb 1997 02:53:26 -0800 (PST)
Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA22727
          for <hackers@freebsd.org>; Mon, 3 Feb 1997 02:53:23 -0800 (PST)
Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.5/CET-v2.1) with SMTP id KAA09376; Mon, 3 Feb 1997 10:51:51 GMT
Date: Mon, 3 Feb 1997 19:51:51 +0900 (JST)
From: Michael Hancock <michaelh@cet.co.jp>
To: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
cc: grog@lemis.de, Terry Lambert <terry@lambert.org>,
        FreeBSD Hackers <hackers@freebsd.org>
Subject: Re: bisdn
In-Reply-To: <Pine.BSF.3.91.970203212237.25849D-100000@panda.hilink.com.au>
Message-ID: <Pine.SV4.3.95.970203194254.9350A-100000@parkplace.cet.co.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Mon, 3 Feb 1997, Daniel O'Callaghan wrote:

> On Mon, 3 Feb 1997, Michael Hancock wrote:
> 
> > I find this hard to believe too, 2D channels is wierd.  The D-channel is
> > for out-of-band signaling.  It's why you get 64K instead of 56K. 
> 
> Oh?  According to the ISDN specs I've read basic rate ISDN is 2B+D, as 
> 2 * 64 + 1 * 16.  Do the Japanese use American ISDN?
> 
> Danny

I'm talking about a single B channel.  Japan has the standard 2B+D.

In the states there exists ISDN service with in-band signaling and you get
56K per channel.

Mike Hancock


From owner-freebsd-hackers  Mon Feb  3 03:23:29 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id DAA23706
          for hackers-outgoing; Mon, 3 Feb 1997 03:23:29 -0800 (PST)
Received: from narcissus.ml.org (root@brosenga.Pitzer.edu [134.173.120.201])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA23700
          for <Freebsd-Hackers@FreeBSD.ORG>; Mon, 3 Feb 1997 03:23:25 -0800 (PST)
Received: (from ben@localhost) by narcissus.ml.org (8.7.5/8.7.3) id DAA05150; Mon, 3 Feb 1997 03:23:16 -0800 (PST)
Date: Mon, 3 Feb 1997 03:23:16 -0800 (PST)
From: Stranger Bone <ben@narcissus.ml.org>
To: Steve Howe <hmmm@ice-bbs.net>
cc: Freebsd-Hackers@FreeBSD.ORG
Subject: Re: un-ethical isp
In-Reply-To: <293_9702030127@ice-bbs.net>
Message-ID: <Pine.BSF.3.91.970203031642.5124A-100000@narcissus.ml.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On 3 Feb 1997, Steve Howe wrote:

> 
> Dear FreeBSDers,
> 
> because of your excellent OS and superb knowledge, i/we decided to use
> FreeBSD in projects for the government subcontracting starting about 2
> years ago.  an associate and boss became upset due to their fear of
> UNIX and a sort of conspiracy developed ...

Ack!
 
> anyway - unbeknownst to me, the owners of my isp (alaska.net) were former
> associates this vengeful/ignorant co-worker and boss, and together
> (as i came close to finishing a project way ahead of their NT
> project) they (isp) engaged in ping flooding all my machines
> on my networks, grinding all my work to a complete halt for
> a week, and additionally, after tracing the source of the
> pinging and sending some nasty email, my isp transferred
> all my email i had ever written on my personal/private
> account to my boss and co-worker for review, ie, they
> were looking for some goodies to get rid of me.
> they hired private investigators, etc. but i
> was squeaky clean, although things have
> become miserable enough to quit. :)

I'll bet.

> ANYWAY - my question is, although my lawyer says my isp may be
> liable for slander, is there any other recourse i can take for
> them giving 2 1/2 years of my email from my personal/private
> account to my boss and co-workers?  i wouldn't want laws,
> but i despise un-ethical behaviour such as this!

Laws are good sometimes.  Look up privacy laws, but I think the whole 'net
thing is too new for any laws to have been passed on it.  Check state
laws. 

I would suggest you write some mail to alternet, which is alaska.net's
provider (if I read my traceroute output correctly).  Mention how much
grief alaska.net has caused you and casually let drop the fact that you've
retained a lawyer.  I wouldn't be surprised if alaska.net shortly finds
itself without an IP feed. 

You can probably get alaska.net for the ping attacks under some computer 
vandalism law, I think there's a federal law that'll help you.

Also, hire a better lawyer.  He or she should know this stuff, I'm just a 
college student and I could probably find you several grounds for suit.

> it included health information related to my family,
> love letters :), thoughts, etc.  all kinds of stuff
> you'd never want anyone to see!

My sympathy goes out to you.

> (pgp? - well not everyone i wrote to can use it!)
> 
> thanks ...  please mail to hmmm@ice-bbs.net.

(Use a reply-to header!)

> a friend/co-worker is allowing me use of this
> account as i have no isp currently ...

Mail me privately about setting you up a telnet-accessible account on my 
machine, at least you'll have a mail drop of your own.  Doesn't cost.

> --
> | Standard disclaimer: The views of the users are strictly their own.
> | ICE BBS Network  +1-907-346-2371 (ANSI, 28.8k, FREE E-MAIL!).
> 
> 



 Ben

The views expressed above are not those of the Worker's Compensation 
Board of Queensland, Australia.



From owner-freebsd-hackers  Mon Feb  3 03:37:18 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id DAA24261
          for hackers-outgoing; Mon, 3 Feb 1997 03:37:18 -0800 (PST)
Received: from methan.chemie.fu-berlin.de (methan.chemie.fu-berlin.de [160.45.22.81])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id DAA24256
          for <hackers@freebsd.org>; Mon, 3 Feb 1997 03:37:14 -0800 (PST)
Received: by methan.chemie.fu-berlin.de (Smail3.1.29.1)
	  id <m0vrMhz-0009oLC>; Mon, 3 Feb 97 12:37 MET
Received: (from dirk@localhost)
          by hal.IN-Berlin.DE (8.8.4/8.8.4)
	  id MAA02421; Mon, 3 Feb 1997 12:35:26 +0100 (MET)
Message-ID: <Mutt.19970203123525.dirk@hal.IN-Berlin.DE>
Date: Mon, 3 Feb 1997 12:35:25 +0100
From: dirk@hal.IN-Berlin.DE (Dirk Froemberg)
To: hackers@freebsd.org
Subject: Booting FreeBSD from solid-state-disk
X-Mailer: Mutt 0.55-PL15
Mime-Version: 1.0
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Dear hackers!

I'm trying to boot FreeBSD from a solid-state-disk.

The first 4K of the card is a bios extension mapping access to drive 80 (C:)
via the bios to the memory on the card.

My first approach

	cat bios-extension rawboot kernel-with-mfs-in-it > "/dev/card"	.

was successfull on the first shot... 8) Unfortunally the mfs within the
kernel lacks of the kernel itself, unless one doesn't want to duplicate
it. So ps, netstat, ... are useless.

Another idea was to put a real filesystem with boot1, boot2, partition-table,
disklabel, ... on the disk and mount the memory of the card similar to a mfs
(card is jumpered to D000:0000, 1020 * 1024 is the size of the filesystem):

*** /sys/ufs/mfs/mfs_vfsops.c.dist	Fri Dec 27 20:44:10 1996
--- /sys/ufs/mfs/mfs_vfsops.c	Sun Feb  2 17:32:29 1997
***************
*** 107,114 ****
--- 107,119 ----
  
  #ifdef MFS_ROOT
  
+ u_char *mfs_root = 0xd0000 + 0x1000;
+ u_char *end_mfs_root = 0xd0000 + 0x1000 + 1020 * 1024;
+ 
+ #if 0
  static u_char mfs_root[MFS_ROOT*1024] = "MFS Filesystem goes here";
  static u_char end_mfs_root[] = "MFS Filesystem had better STOP here";
+ #endif
  
  #ifdef MFS_AUTOLOAD
  /*

The kernel-config-file has "options MFS; options MFS_ROOT=0" in it.
The kernel boots up still fine but when mounting the root-filesystem
a panic occurs:

Fatal trap 12: page fault while in kernel mode
fault virtual address	= 0xd355c
fault code		= supervisor read, page not present
instruction pointer	= 0x8:0xf01469b3
stack pointer		= 0x10:0xefbffecc
frame pointer		= 0x10:0xefbfff50
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		= 0 (swapper)
interrupt mask		=
panic: page fault


Any ideas?

	Best regards Dirk

-- 
e-mail: dirk@hal.in-berlin.de		PGP-Public-Key available

"Arbeiten ist nicht vergasen - erschiessen - haengen - irgendwie
toeten!"
		-- Klaus Scheurenberg, "Ich will leben"

From owner-freebsd-hackers  Mon Feb  3 05:32:55 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id FAA28362
          for hackers-outgoing; Mon, 3 Feb 1997 05:32:55 -0800 (PST)
Received: from po2.glue.umd.edu (root@po2.glue.umd.edu [129.2.128.45])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA28357
          for <FreeBSD-Hackers@FreeBSD.org>; Mon, 3 Feb 1997 05:32:52 -0800 (PST)
Received: from gilligan.eng.umd.edu (gilligan.eng.umd.edu [129.2.103.21]) by po2.glue.umd.edu (8.8.5/8.7.3) with ESMTP id IAA09871 for <FreeBSD-Hackers@FreeBSD.org>; Mon, 3 Feb 1997 08:32:49 -0500 (EST)
Received: from localhost (chuckr@localhost) by gilligan.eng.umd.edu (8.8.5/8.7.3) with SMTP id IAA03459 for <FreeBSD-Hackers@FreeBSD.org>; Mon, 3 Feb 1997 08:32:48 -0500 (EST)
X-Authentication-Warning: gilligan.eng.umd.edu: chuckr owned process doing -bs
Date: Mon, 3 Feb 1997 08:32:48 -0500 (EST)
From: Chuck Robey <chuckr@glue.umd.edu>
X-Sender: chuckr@gilligan.eng.umd.edu
To: FreeBSD-Hackers <FreeBSD-Hackers@FreeBSD.org>
Subject: Re: conditionally including <sys/param.h>
Message-ID: <Pine.OSF.3.95q.970203083034.3201H-100000@gilligan.eng.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

[reposted -- my mailer couldn't handle Thomas David Rivers ucbvax address]
On Sun, 2 Feb 1997, Thomas David Rivers wrote:

> > 
> > Sorry to have to bring this back to light...
> > I was under the impression that we had agreed that
> > "#if (defined(__unix__) || defined(unix))" was the best way to
> > conditionally include <sys/param.h>.  However, this email from Chuck,
> > implies that this is a Bad Thing.
> 
> Unfortunately the symbols:
> 	unix
> 	FreeBSD
> 	NetBSD
> 	OpenBSD
> 
> violate the user's name space.  For example, I have programs
> that define some of these on the command line.  If these were defined
> elsewhere things would break.  [Of course, such things do break
> on other hosts; e.g. SunOS 4.x defines "unix".]
> 
> I would suggest using:
> 	__unix__
> 	__FreeBSD__
> 	__NetBSD__
> 	__OpenBSD__
> 
> as identifiers beginning with "_" are reserved (per ANSI) for the
> implementation.

__unix__ seems unneeded, but __FreeBSD__, __NetBSD__, and __OpenBSD__ are
already used successfully by X11 (see /usr/X11R6/lib/X11/Imake.cf) and I
think they'll work fine for us.  We can add specific additional names, one
by one, as we get specific requests from other systems.  I'd like this.


----------------------------+-----------------------------------------------
Chuck Robey                 | Interests include any kind of voice or data 
chuckr@eng.umd.edu          | communications topic, C programming, and Unix.
9120 Edmonston Ct #302      |
Greenbelt, MD 20770         | I run Journey2 and picnic, both FreeBSD
(301) 220-2114              | version 3.0 current -- and great FUN!
----------------------------+-----------------------------------------------


From owner-freebsd-hackers  Mon Feb  3 06:08:10 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id GAA29715
          for hackers-outgoing; Mon, 3 Feb 1997 06:08:10 -0800 (PST)
Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id GAA29708
          for <hackers@freefall.freebsd.org>; Mon, 3 Feb 1997 06:08:06 -0800 (PST)
Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id JAA03379; Mon, 3 Feb 1997 09:06:08 -0500
Date: Mon, 3 Feb 1997 09:06:07 -0500 (EST)
From: "Ron G. Minnich" <rminnich@Sarnoff.COM>
X-Sender: rminnich@terra
To: Narvi <narvi@haldjas.folklore.ee>
cc: Terry Lambert <terry@lambert.org>, gurney_j@resnet.uoregon.edu,
        hackers@freefall.freebsd.org
Subject: Re: performance puzzler
In-Reply-To: <Pine.BSF.3.95.970202201858.13473A-100000@haldjas.folklore.ee>
Message-ID: <Pine.SUN.3.91.970203090455.3325C-100000@terra>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Sun, 2 Feb 1997, Narvi wrote:
> On Sat, 1 Feb 1997, Terry Lambert wrote:
> > The PCI and EISA standards specify 33MHz as their top end.
> Where did I read about 66Mhz revision/mode for PCI? Was it in a dream or
> just a "not supported by anybody yet" possibility as is the 64bit card
> width. Or was it all just a dream or erroneus news article?

chapter 7 of the pci rev 2.1 spec discusses the 66 mhz. spec. Also 64 
bits has been in forever. 

ron

From owner-freebsd-hackers  Mon Feb  3 06:27:02 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id GAA00505
          for hackers-outgoing; Mon, 3 Feb 1997 06:27:02 -0800 (PST)
Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id GAA00500
          for <freebsd-hackers@FreeBSD.ORG>; Mon, 3 Feb 1997 06:27:00 -0800 (PST)
Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id JAA03581; Mon, 3 Feb 1997 09:26:23 -0500
Date: Mon, 3 Feb 1997 09:26:22 -0500 (EST)
From: "Ron G. Minnich" <rminnich@Sarnoff.COM>
X-Sender: rminnich@terra
To: freebsd-hackers@FreeBSD.ORG
Subject: Re: Re(2): Using rfork() / threads
In-Reply-To: <Pine.SV4.3.95.970201101003.12751A-100000@parkplace.cet.co.jp>
Message-ID: <Pine.SUN.3.91.970203092205.3325F-100000@terra>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Sat, 1 Feb 1997, Michael Hancock wrote:
> The Vahalia book mentions shared memory locks for 4.4BSD that worked
> essentially the same way.  They were named mset, mwait, or something like
> that.

yeah, but recall that I did this stuff 9/94. mset etc. were not around 
then, and appear to still not be. 

> Fastlock sounds cool, but shared memory locks are supposed to be fast. 
It's a bit more complex than shared memory locks. The problem is making
shared memory locks between heavyweight processes that are efficient and 
in particular never do a system call unless needed. 

> I prefer the mxxx conventions to categorize it with the
> mmap calls. 

works for me. 

this lock question keeps coming up. I have some old messages that 
describe the operation of fastlock that I will forward to this list. The 
experience of the last 2.5 years leads me to believe fastlock will be in 
openbsd much sooner than freebsd (chuck cranor pointed out to me 
yesterday that minherit() is in openbsd now ...) assuming it ever gets 
into freebsd ...

ron

From owner-freebsd-hackers  Mon Feb  3 06:30:44 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id GAA00655
          for hackers-outgoing; Mon, 3 Feb 1997 06:30:44 -0800 (PST)
Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id GAA00639
          for <freebsd-hackers@freebsd.org>; Mon, 3 Feb 1997 06:30:41 -0800 (PST)
Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id JAA03664; Mon, 3 Feb 1997 09:30:10 -0500
Date: Mon, 3 Feb 1997 09:30:09 -0500 (EST)
From: "Ron G. Minnich" <rminnich@Sarnoff.COM>
X-Sender: rminnich@terra
To: freebsd-hackers@freebsd.org
Subject: OK, here goes fastlock: (fwd)
Message-ID: <Pine.SUN.3.91.970203093001.3325G-100000@terra>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk



Ron Minnich                |"Failure is not an option" -- Gene Kranz
rminnich@sarnoff.com       | -- except, of course, on Microsoft products
(609)-734-3120             |
ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html 


---------- Forwarded message ----------
Date: Tue, 2 Jul 1996 09:50:01 -0400 (EDT)
From: Ron G. Minnich <rminnich@Sarnoff.COM>
To: hackers@freebsd.org
Subject: OK, here goes fastlock:

Here's a simple test-and-set function for the 386 (tested and works):

int
tset(int *i, int lockval, int unlockval)
{
  int j = 0;
        asm("movl 16(%ebp), %eax");
        asm("movl 8(%ebp),%ecx");
        asm("movl 12(%ebp),%edx");
        asm("cmpxchg %edx, (%ecx)");
        asm("jne failed");
        asm("movl %eax, -4(%ebp)");
        asm("jmp done");
        asm("failed: movl %eax, -4(%ebp)");
        asm("done:");
  return j;
}

This will run a bit faster than a file lock system call :-). But what about 
contention? notice that this function, if it fails, fails. so we need a 
retry strategy. IF you fail, should you spin forever? NO! Do that, and 
you eat the processor doing nothing. You ought to have a reasonable way 
to, say, spin one or two more times, then go to a more heavyweight sleep. 

SO: here's the fastlock library call (#ifdef USEMOD is for LKM )

void
fastlock(int *address, int lockval, int unlockval)
{
        int testval;
#ifdef USEMOD
	static int syscallnum = -1;
        if (syscallnum < 0)
                syscallnum = syscallfind("fastlock");
        if (syscallnum < 0) {
                perror("fastlock syscallfind");
                return;
        }
#endif

  testval = tset(address, lockval, unlockval);
  if (testval == unlockval) {
#ifdef FASTLOCKDEBUG
        printf("(%d)fastlock quickout\n", getpid());
#endif
        return;
  }
  /* attempt to lock failed. test then wait in kernel sleep() */
  while (1)
    {
      /* set the high-order bit. This tells the unlocker to do the system
       * call and free up the lock.
       */
      (void) tset(address, testval|0x80000000,testval);
#ifdef FASTLOCKDEBUG
      printf("(%d)hang in there\n", getpid());
#endif
      /* we should be checking here to make sure that high-order bit is 
       * set. But this second tset fails only 
       * in the event of contention, in which case 
       * someone else has set the high-order
       * bit too ... seems pointless, esp. given that fastlock has a timeout
       */
      syscall(syscallnum, 1, address, unlockval);
      testval = tset(address, lockval, unlockval);
      if (testval == unlockval)
        return;
    }
  
}

So what are we doing? We're doing the tset. If it fails, then we do one 
more tset, to set the high order bit, then drop into the fastlock system 
call. Once we return from that, we try to tset the variable again. If 
that fails, we drop once again into the system call. 

Here's fastunlock: 
void
fastunlock(int *address, int unlockval)
{
  int dosyscall = 0;
  static int syscallnum = -1; /* this is really in the file */
#ifdef USEMOD
        if (syscallnum < 0)
                syscallnum = syscallfind("fastlock");
        if (syscallnum < 0) {
                perror("fastunlock syscallfind");
                return;
        }
#endif
  if (*address & 0x80000000)
    dosyscall = 1;
  *address = unlockval;
#ifdef FASTLOCKDEBUG
  printf("(%d)fastunlock dosyscall is %d\n", getpid(), dosyscall);
  if (dosyscall) printf("conflict %d\n", getpid());
  fflush(stdout);
#endif
  if (dosyscall)
    syscall(syscallnum, 0, address, unlockval);
}

Ok, this one tests to see if it needs to wake any sleepers, clears the 
memory variable, then drops into the kernel if needed (if (dosyscall) ...)

Here's the system call. Note several things: 
1) the definition of 'unlocked' is passed in to the system call for the 
final test, not assumed to be zero. 
2) The 'address' argument does NOT NEED TO BE AN ADDRESS. it's a number
   that all the procs have to agree on, that is all.
3) if you accidently awake more than one sleeper, the loop in fastlock
   handles that properly
4) This system call handles both waking up and sleeping
5) For my measurements, this thing is a whole lot faster than anything
   else available on (e.g.) freebsd. Questions to me. 

int
fastlock(p, uap, retval)
        struct proc *p;
        struct flu *uap;
        int retval[];
{
        extern int hz;
        retval[0] = 0;
/*
        printf("fastlockunlock: com %d address 0x%x unlocked %d\n",
                uap->com, uap->address, uap->unlocked);
 */
        if (uap->com == 0) /* unlock */
                wakeup((void *) uap->address);
        else
                {
                        /* last chance */
			/* try one last time to see if it is unlocked */
                        int curval = fuword((void *) uap->address);
                        if (curval == uap->unlocked)
                                return;
                        tsleep((void *) uap->address, PUSER, NULL, 10*hz);
                }
        return 0;
}



Ron Minnich                |"Inferno runs on MIPS ..., Intel ..., and AMD's
rminnich@sarnoff.com       |29-kilobit-per-second chip-based architectures ..."
(609)-734-3120             |  Comm. week, may 13, pg. 4. 
ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html 




From owner-freebsd-hackers  Mon Feb  3 07:15:03 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id HAA02558
          for hackers-outgoing; Mon, 3 Feb 1997 07:15:03 -0800 (PST)
Received: from hda.hda.com (ip95-max1-fitch.ziplink.net [199.232.245.95])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id HAA02546
          for <hackers@FreeBSD.ORG>; Mon, 3 Feb 1997 07:14:57 -0800 (PST)
Received: (from dufault@localhost) by hda.hda.com (8.6.12/8.6.12) id JAA19438; Mon, 3 Feb 1997 09:48:58 -0500
From: Peter Dufault <dufault@hda.com>
Message-Id: <199702031448.JAA19438@hda.hda.com>
Subject: Re: Jukka Ukkonen: POSIX.4 - scheduler once more (as you requested)
In-Reply-To: <199702030234.NAA01680@genesis.atrad.adelaide.edu.au> from Michael Smith at "Feb 3, 97 01:04:14 pm"
To: msmith@atrad.adelaide.edu.au (Michael Smith)
Date: Mon, 3 Feb 1997 09:48:58 -0500 (EST)
Cc: dufault@hda.com, jkh@time.cdrom.com, hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL25 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> Peter Dufault stands accused of saying:
> > One quick observation:
> > 
> > > X * 5. The source code must be available for anyone who wishes to have it.
> > 
> > What do people think of packaging this up as a user library against
> > an LKM'd pseudo /dev/realtime driver?  I have the skeleton to do
> 
> How does this help the posix.4 scheduling model though?  Does having it as
> an LKM still allow this to work "as expected"?

I have an LKM skeleton that includes scheduling.  I have to decide if I like
it or not.  Everything funnels through an ioctl, though it is set up to be
installed as system calls if that is preferred.  I've been thinking about a
dispatch through system calls that is redirected from the default if you have
the device open since I think that works as the best of both worlds.

> > that.  My reasoning is I'd like to be able to have different realtime
> > facilities, for example, process migration to an attached embedded
> > processor that would "fault" back as soon as you tried to do
> > something in that environment.  It also gives you a way to have
> > realtime user or group protection.
> 
> Sounds reasonable (and interesting).  Do you have more words on this 
> somewhere?

I have too many words on it.  Maybe at the end of the week I'll proofread it and
put it someplace public.

-- 
Peter Dufault (dufault@hda.com)   Realtime Machine Control and Simulation
HD Associates, Inc.               Voice: 508 433 6936

From owner-freebsd-hackers  Mon Feb  3 07:56:58 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id HAA04446
          for hackers-outgoing; Mon, 3 Feb 1997 07:56:58 -0800 (PST)
Received: from eldorado.net-tel.co.uk ([193.122.171.253])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id HAA04435
          for <freebsd-hackers@FreeBSD.ORG>; Mon, 3 Feb 1997 07:56:52 -0800 (PST)
From: Andrew.Gordon@net-tel.co.uk
Received: (from root@localhost) by eldorado.net-tel.co.uk (8.6.12/8.6.10) id PAA25467; Mon, 3 Feb 1997 15:55:34 GMT
Received: from "/PRMD=NET-TEL/ADMD=GOLD 400/C=GB/" by net-tel.co.uk
        (Route400-RFCGate); Mon,  3 Feb 97 15:53:27 +0000
X400-Received: by mta "eldorado" in "/PRMD=net-tel/ADMD=gold 400/C=gb/"; 
        Relayed; Mon,  3 Feb 97 15:53:27 +0000
X400-Received: by mta "net-tel cambridge" in "/PRMD=net-tel/ADMD=gold 400/C=gb/";
         Relayed; Mon,  3 Feb 97 15:53:25 +0000
X400-Received: by "/PRMD=NET-TEL/ADMD=Gold 400/C=GB/"; Relayed; 
        Mon,  3 Feb 97 15:53:25 +0000
X400-MTS-Identifier: 
        ["/PRMD=NET-TEL/ADMD=Gold 400/C=GB/";hst:8655-970203155325-43F7]
X400-Content-Type: P2-1984 (2)
X400-Originator: Andrew.Gordon@net-tel.co.uk
Original-Encoded-Information-Types: IA5-Text
X400-Recipients: non-disclosure:;
Date: Mon,  3 Feb 97 15:53:25 +0000
X400-Content-Identifier: Re: OK, here goe
Message-Id: <"3a14-970203154823-6178*/G=Andrew/S=Gordon/O=NET-TEL Computer
 Systems Ltd/PRMD=NET-TEL/ADMD=Gold 400/C=GB/"@MHS>
To: rminnich@Sarnoff.COM
Cc: freebsd-hackers@FreeBSD.ORG
In-Reply-To: <Pine.SUN.3.91.970203093001.3325G-100000@terra>
Subject: Re: OK, here goes fastlock: (fwd)
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

[debug ifdefs removed from quoted section for brevity]
> fastunlock(int *address, int unlockval)
> {
>   int dosyscall = 0;
>   static int syscallnum = -1; /* this is really in the file */
>   if (*address & 0x80000000)  /***/
>     dosyscall = 1;
>   *address = unlockval;
>   if (dosyscall)
>     syscall(syscallnum, 0, address, unlockval);
> }

Isn't there a race here?  If the process holding the lock happens to
get descheduled at the point marked /***/ and another process blocks
waiting for the lock, the syscall doesn't get called and the second
process continues to block until the 10 second timeout in the syscall.

This can no doubt be fixed with another tset of some sort when releasing
the lock.

> 2) The 'address' argument does NOT NEED TO BE AN ADDRESS. it's a number
>    that all the procs have to agree on, that is all.

You seem to be assuming that it _is_ an address in this implementation
however:

>                         int curval = fuword((void *) uap->address);
>                         if (curval == uap->unlocked)
>                                 return;

From owner-freebsd-hackers  Mon Feb  3 08:36:51 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id IAA06721
          for hackers-outgoing; Mon, 3 Feb 1997 08:36:51 -0800 (PST)
Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id IAA06716
          for <freebsd-hackers@FreeBSD.ORG>; Mon, 3 Feb 1997 08:36:48 -0800 (PST)
Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id LAA04463; Mon, 3 Feb 1997 11:35:21 -0500
Date: Mon, 3 Feb 1997 11:35:20 -0500 (EST)
From: "Ron G. Minnich" <rminnich@Sarnoff.COM>
X-Sender: rminnich@terra
To: Andrew.Gordon@net-tel.co.uk
cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: OK, here goes fastlock: (fwd)
In-Reply-To: <"3a14-970203154823-6178*/G=Andrew/S=Gordon/O=NET-TEL Computer Systems Ltd/PRMD=NET-TEL/ADMD=Gold 400/C=GB/"@MHS>
Message-ID: <Pine.SUN.3.91.970203111656.3325P-100000@terra>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > fastunlock(int *address, int unlockval)
> > {
> >   int dosyscall = 0;
> >   static int syscallnum = -1; /* this is really in the file */
> >   if (*address & 0x80000000)  /***/
> >     dosyscall = 1;
> >   *address = unlockval;
> >   if (dosyscall)
> >     syscall(syscallnum, 0, address, unlockval);
> > }
> 
> Isn't there a race here?  If the process holding the lock happens to
> get descheduled at the point marked /***/ and another process blocks
> waiting for the lock, the syscall doesn't get called and the second
> process continues to block until the 10 second timeout in the syscall.

You're right there is a race. It's not wide, and I have never hit it, 
but it's certainly there. What I should have done, but mistakenly did 
not do, was use an indivisible sequence of instructions for unlock as 
well. Mea culpa. 

What it seems to me I should have done: 
	let's assume for example I successfully fastlocked()'ed 
            and we set the lockword to 0x1. 

	We come to the unlock code: 
	If there is contention, the value will be 0x80000001
	For the first unlock attempt, 
	assume no contention: test and set with the test value 
	of 1 (our lock value) and the set value of 0. 

	IF the tset succeeds, the we have indivisibly unlocked it; done.

	If the tset fails, then there is contention. So test and set
	with the value 0x80000001. At this point this should have 
	succeeded. Then call the system call. 

Both tset sequences on the unlock are indivisible, eliminating the race. 

Does this look right now? 

> > 2) The 'address' argument does NOT NEED TO BE AN ADDRESS. it's a number
> >    that all the procs have to agree on, that is all.
> You seem to be assuming that it _is_ an address in this implementation
> however:
> >                         int curval = fuword((void *) uap->address);

Ouch, foolish me. Obviously I've never used it as 'not an address'. 
Sorry about that!

Thanks for the comments! But now i've got something to fix!
ron




From owner-freebsd-hackers  Mon Feb  3 09:22:54 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA09173
          for hackers-outgoing; Mon, 3 Feb 1997 09:22:54 -0800 (PST)
Received: from post-ofc04.srv.cis.pitt.edu (post-ofc04.srv.cis.pitt.edu [136.142.185.11])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA09167
          for <Freebsd-Hackers@FreeBSD.ORG>; Mon, 3 Feb 1997 09:22:50 -0800 (PST)
Received: from ehdup-o-3.rmt.net.pitt.edu (ehdup-o-3.rmt.net.pitt.edu [136.142.22.53])
          by post-ofc04.srv.cis.pitt.edu with SMTP (8.8.5/cispo-2.0.1.7)
          ID <MAA15522@post-ofc04.srv.cis.pitt.edu>;
          Mon, 3 Feb 1997 12:11:15 -0500 (EST)
Message-ID: <32F5D5C1.41C67EA6@pitt.edu>
Date: Mon, 03 Feb 1997 07:10:41 -0500
From: John David Duncan <jddst19+@pitt.edu>
Organization: hopeless
X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2-BETA_A i386)
MIME-Version: 1.0
To: Steve Howe <Steve.Howe@ice-bbs.net>
CC: Freebsd-Hackers@FreeBSD.ORG
Subject: Re: un-ethical isp
References: <293_9702030127@ice-bbs.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Which version of FreeBSD were you running, just out of curiosity.
Supposedly, because of an interesting set of bugs in the pingd, vers
2.1.5 and above are assumed stable vs. the ping-o-death.

Anyhow, you have to look at the license that your isp gave you (they
gave you a license, right?) when you started using them. If they said
anything about the privacy or assumed privacy of your communications,
as far as the control of such issues is in the hands of the isp itself,
that is, not the insecurity of the isp from outside invasion, but
rather the security of your messages vs. the maturity of the provider,
then you will certainly have to take that license to a lawyer and find
out if there are laws in your state that prohibit the denial of certain
express or implied rights that such a license would remove.

If there is no material on this subject, then one could say that the
isp does not own the messages, they only own the medium, and that they
had no right to copy and divert your intellectual property to anyone
else but its intended recipient. But this sort of thing has not
necessarily been worked out.

The US mail, for example, has the right to open and inspect a package
for reasons of customs, taxes, dangerous items, or bad addressing, but
they don't have the right to, say, divert the package to the govern-
ment, then to your boss, then to the freemasonry, then to its recipient.
And I think that law, at least, interstate commerce law, prohibits,
say, UPS from doing similar things. I am not, also, allowed to tap your
wire, or sniff your packets, or whatever.

Furthermore, no phone company is allowed to listen in on your conver-
sations without the express warrant by a court--despite the fact that,
if you live in Pennsylvania like I do (I know you don't), then Bell
Atlantic will have your information in one of their exchanges and
on the wires that they own. It would not be fair if they were to have
that ability.

The government is not even allowed to sit on potentially unstable sites,
like ftp.freebsd.org, to find out whether the secure and eBones sources
are being distributed either purposefully or accidentally into another
country, but they do have the right to get a court's warrant to sieze
the logs at walnut creek and demonstrate that a copy of DES made it
to france. 

I figure that the same goes for the internet carrier. I don't think
that they can imply that by using their smtp server to bounce your
messages to others that they suddenly own your messages. They would,
by that respect, be able to publish one of your poems, etc.

To really screw with them, attach "Copyright 1997 Steve Howe. All
Rights Reserved." to all of your messages that you expect to be
bounced, and you can hit them with federal copyright infringement
allegations (although, in two years, without the copyright being
registered, you would lose that right.) If they deleted those lines,
they would also pay penalties for perjury....

Oh, so much fun.

Just remember, with law, and a good lawyer, you can have just about
as much fun as going postal, so don't bother buying the shotgun.

-John

--
Such opinions are not the intellectual property of NBC. For proof,
watch "Dateline/NBC"

Steve Howe wrote:
> 
> Dear FreeBSDers,
> 
> because of your excellent OS and superb knowledge, i/we decided to use
> FreeBSD in projects for the government subcontracting starting about 2
> years ago.  an associate and boss became upset due to their fear of
> UNIX and a sort of conspiracy developed ...
> 
> anyway - unbeknownst to me, the owners of my isp (alaska.net) were former
> associates this vengeful/ignorant co-worker and boss, and together
> (as i came close to finishing a project way ahead of their NT
> project) they (isp) engaged in ping flooding all my machines
> on my networks, grinding all my work to a complete halt for
> a week, and additionally, after tracing the source of the
> pinging and sending some nasty email, my isp transferred
> all my email i had ever written on my personal/private
> account to my boss and co-worker for review, ie, they
> were looking for some goodies to get rid of me.
> they hired private investigators, etc. but i
> was squeaky clean, although things have
> become miserable enough to quit. :)
> 
> ANYWAY - my question is, although my lawyer says my isp may be
> liable for slander, is there any other recourse i can take for
> them giving 2 1/2 years of my email from my personal/private
> account to my boss and co-workers?  i wouldn't want laws,
> but i despise un-ethical behaviour such as this!
> 
> it included health information related to my family,
> love letters :), thoughts, etc.  all kinds of stuff
> you'd never want anyone to see!
> 
> (pgp? - well not everyone i wrote to can use it!)
> 
> thanks ...  please mail to hmmm@ice-bbs.net.
> a friend/co-worker is allowing me use of this
> account as i have no isp currently ...
> --
> | Standard disclaimer: The views of the users are strictly their own.
> | ICE BBS Network  +1-907-346-2371 (ANSI, 28.8k, FREE E-MAIL!).

From owner-freebsd-hackers  Mon Feb  3 10:06:44 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id KAA11574
          for hackers-outgoing; Mon, 3 Feb 1997 10:06:44 -0800 (PST)
Received: from fog.xinside.com (fog.xinside.com [199.164.187.39])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA11567
          for <hackers@freebsd.org>; Mon, 3 Feb 1997 10:06:38 -0800 (PST)
Received: (from smap@localhost) by fog.xinside.com (8.8.3/8.7.3) id LAA16449; Mon, 3 Feb 1997 11:06:36 -0700 (MST)
X-Authentication-Warning: fog.xinside.com: smap set sender to <patrick@chon.xinside.com> using -f
Received: from chon.xinside.com(199.164.187.134) by fog.xinside.com via smap (V1.3)
	id sma016447; Mon Feb  3 11:06:34 1997
Received: (from patrick@localhost) by chon.xinside.com (8.7.5/8.6.12) id LAA06948; Mon, 3 Feb 1997 11:06:29 -0700 (MST)
Date: Mon, 3 Feb 1997 11:06:29 -0700 (MST)
Message-Id: <199702031806.LAA06948@chon.xinside.com>
From: Patrick Giagnocavo <support@xinside.com>
To: hackers@freebsd.org, hmmm@ice-bbs.net
Subject: Re: un-ethical isp
In-Reply-To: <32F5D5C1.41C67EA6@pitt.edu>
References: <293_9702030127@ice-bbs.net>
	<32F5D5C1.41C67EA6@pitt.edu>
Reply-To: patrick@xinside.com
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

-snipped--
 > > a week, and additionally, after tracing the source of the
 > > pinging and sending some nasty email, my isp transferred
 > > all my email i had ever written on my personal/private
 > > account to my boss and co-worker for review, ie, they
 > > were looking for some goodies to get rid of me.

 > > ANYWAY - my question is, although my lawyer says my isp may be
 > > liable for slander, is there any other recourse i can take for
 > > them giving 2 1/2 years of my email from my personal/private
 > > account to my boss and co-workers?  i wouldn't want laws,
 > > but i despise un-ethical behaviour such as this!
 > > 
 > > it included health information related to my family,
 > > love letters :), thoughts, etc.  all kinds of stuff
 > > you'd never want anyone to see!
 > > 
 > > (pgp? - well not everyone i wrote to can use it!)
 > > 
 > > thanks ...  please mail to hmmm@ice-bbs.net.
 > > a friend/co-worker is allowing me use of this
 > > account as i have no isp currently ...

<my opinions only, mind you>

There is a federal statute that covers this sort of thing.  Basically
it is illegal to interfere with the delivery of electronic mail, and
there are criminal consequences to those who do so.  Two ways you can
get these folks is that a) they interfered with the operation of the
email system itself by ping flooding, b) they transferred email to
someone else when it was not addressed to them.  In the case of Steve
Jackson Games vs. the Gov't (I believe it was the Secret Service) the
judge found for Steve Jackson Games once they pointed this out.  This
was a couple years ago, so there is case law and precedent that you
can depend on.

They are (based on the info you have given) in violation of the
Electronic Communications and Privacy Act. (ECPA)  Even BBS's which
are not connected to the Net full time receive protection under this
act. 

My first suggestion is that you get in contact with the Electronic
Freedom Foundation (http://www.eff.org/).  They are sort of like the
ACLU for Net users.  If they can't help you directly they can probably
point you in the right direction.

Cordially,

Patrick Giagnocavo

From owner-freebsd-hackers  Mon Feb  3 11:09:38 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA14081
          for hackers-outgoing; Mon, 3 Feb 1997 11:09:38 -0800 (PST)
Received: from sendero.i-connect.net ([206.190.144.100])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA14056
          for <hackers@freebsd.org>; Mon, 3 Feb 1997 11:09:01 -0800 (PST)
Received: (from shimon@localhost)
          by sendero.i-connect.net (8.8.5/8.8.4)
	  id MAA01622; Mon, 3 Feb 1997 12:07:37 -0800 (PST)
Message-ID: <XFMail.970203120737.Shimon@i-Connect.Net>
X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD
Content-Type: text/plain; charset=iso-8859-8
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <14120.854650859@time.cdrom.com>
Date: Mon, 03 Feb 1997 10:58:55 -0800 (PST)
Organization: iConnect Corp.
From: Simon Shapiro <Shimon@i-Connect.Net>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Subject: RE: Jukka Ukkonen: POSIX.4 - scheduler once more (as you request
Cc: hackers@freebsd.org
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Hi Jordan K. Hubbard;  On 30-Jan-97 you wrote: 
> Any interest in this?  I'd like a few more reviewers, if possible.

Sure.  I'll try.  Apply it to 2.2-BETA /usr/src/sys and compile new kernel?

Simon

> 
> ------- Forwarded Message
> 
> From: jau@iki.fi (Jukka Ukkonen)
> Latin-Date: Miercuri XXIX Ianuarie a.d. MCMXCVII
> Organization: Private person
> Phone: +358-9-6215280 (home)
> Reply-To: jau@iki.fi (Jukka Ukkonen)
> Content-Conversion: prohibited
> X-Mailer: ELM [version 2.4 PL25+pgp]
> MIME-Version: 1.0
> Content-Type: text/plain; charset=iso-8859-1
> Content-Transfer-Encoding: 8bit
> 
> 
>       Greetings from Helsinki,
> 
>       You said earlier that you did not dare to publish my POSIX
>       sched-package before I send you the correct version once more,
>       because previously I had sent you an old version.

From owner-freebsd-hackers  Mon Feb  3 11:43:59 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA16125
          for hackers-outgoing; Mon, 3 Feb 1997 11:43:59 -0800 (PST)
Received: from browncow.com (ch_asc1_p33.taconic.net [205.231.28.35])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA16117
          for <hackers@freefall.freebsd.org>; Mon, 3 Feb 1997 11:43:52 -0800 (PST)
Received: by browncow.com (951211.SGI.8.6.12.PATCH1042/940406.SGI)
	 id OAA18041; Mon, 3 Feb 1997 14:42:02 -0500
Date: Mon, 3 Feb 1997 14:42:02 -0500
From: kish@browncow.com (Bill Kish)
Message-Id: <199702031942.OAA18041@browncow.com>
To: hackers@freefall.freebsd.org
Subject: kernel malloc options
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


Hi,

 I'm working on a a Network related module which performs a function
similar to Network Address Translation. This module needs to
dynamically allocate small (~40 byte) structures to keep track of
currently established TCP connections between machines on the "inside"
and "outside" networks.

 Currently, I'm malloc()ing these structures as needed using the
following parameters:

 malloc((u_long)sizeof(*conxn), M_TEMP, M_NOWAIT)

 This appears to work fine in my initial lightly loaded tests,
however, I'm concerned about what will happen when the system is under
heavy load. I have the following questions and would appreciate any
advice offered!

 1) Is malloc() a reasonable allocator for small highly dynamic
   objects?

 2) Is M_TEMP a good choice? Does it make a difference?

 3) Are there any config options that affect the amount of pinned
    kernel memory available for malloc? The system will be doing
    little else besides dealing with these packets...

 

                Thanks In Advance,

                  -BK
--

From owner-freebsd-hackers  Mon Feb  3 11:50:14 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA16454
          for hackers-outgoing; Mon, 3 Feb 1997 11:50:14 -0800 (PST)
Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA16444
          for <hackers@freebsd.org>; Mon, 3 Feb 1997 11:50:08 -0800 (PST)
Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5])
          by mail.cdsnet.net (8.8.4/8.7.3) with SMTP id LAA02738
          for <hackers@freebsd.org>; Mon, 3 Feb 1997 11:50:07 -0800 (PST)
Date: Mon, 3 Feb 1997 11:50:06 -0800 (PST)
From: Jaye Mathisen  <mrcpu@cdsnet.net>
To: hackers@freebsd.org
Subject: How to build the whole tree -static?
Message-ID: <Pine.NEB.3.95.970203114938.13493E-100000@mail.cdsnet.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk



I have space to burn on 1 box.  Is there an easy way to tweak the build
process to make it compile the whole darn thing non-shared?


From owner-freebsd-hackers  Mon Feb  3 12:42:14 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA18664
          for hackers-outgoing; Mon, 3 Feb 1997 12:42:14 -0800 (PST)
Received: from narcissus.ml.org (root@brosenga.Pitzer.edu [134.173.120.201])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA18659
          for <hackers@freebsd.org>; Mon, 3 Feb 1997 12:42:13 -0800 (PST)
Received: (from ben@localhost) by narcissus.ml.org (8.7.5/8.7.3) id MAA06801; Mon, 3 Feb 1997 12:41:35 -0800 (PST)
Date: Mon, 3 Feb 1997 12:41:34 -0800 (PST)
From: Stranger Bone <ben@narcissus.ml.org>
To: Jaye Mathisen <mrcpu@cdsnet.net>
cc: hackers@freebsd.org
Subject: Re: How to build the whole tree -static?
In-Reply-To: <Pine.NEB.3.95.970203114938.13493E-100000@mail.cdsnet.net>
Message-ID: <Pine.BSF.3.91.970203123927.6759C-100000@narcissus.ml.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Mon, 3 Feb 1997, Jaye Mathisen wrote:

> 
> 
> I have space to burn on 1 box.  Is there an easy way to tweak the build
> process to make it compile the whole darn thing non-shared?
> 

Ha!  I only found the answer to this last night.

You need to edit /usr/share/mk/sys.mk.  There's a line that reads

CFLAGS          ?=      -O

Change it to 

CFLAGS          ?=      -O -static


 Ben

The views expressed above are not those of the Worker's Compensation 
Board of Queensland, Australia.



From owner-freebsd-hackers  Mon Feb  3 12:58:57 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA19677
          for hackers-outgoing; Mon, 3 Feb 1997 12:58:57 -0800 (PST)
Received: from iidpwr.com ([204.33.177.5])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA19658
          for <hackers@freebsd.org>; Mon, 3 Feb 1997 12:58:52 -0800 (PST)
Received: from tam.ee.iidpwr.com ([204.33.177.99]) by mail.iidpwr.com with SMTP id <15360>; Mon, 3 Feb 1997 12:59:46 -0800
Message-ID: <32F651D0.167EB0E7@iidpwr.com>
Date: Mon, 3 Feb 1997 13:00:00 -0800
From: Tony Tam <ttam@mail.iidpwr.com>
Organization: Imperial Irrigation District
X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.1.6-RELEASE i386)
MIME-Version: 1.0
To: hackers@freebsd.org
Subject: unsubscribe
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

unsubscribe

-- 
Yours truly,

-------------------------------------------------------------------------
| Tony Tam                      | Tel: 619-339-9454                    
|
| Imperial Irrigation District  | FAX: 619-339-9189                    
|
| Imperial, CA 92251, USA       | E-Mail: ttam@iidpwr.com              
|
-------------------------------------------------------------------------

From owner-freebsd-hackers  Mon Feb  3 13:14:07 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA20600
          for hackers-outgoing; Mon, 3 Feb 1997 13:14:07 -0800 (PST)
Received: from gargoyle.bazzle.com (gargoyle.bazzle.com [206.103.246.190])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA20593
          for <hackers@FreeBSD.ORG>; Mon, 3 Feb 1997 13:13:57 -0800 (PST)
Received: from gargoyle.bazzle.com (net2.bazzle.com [206.103.246.189]) by gargoyle.bazzle.com (8.8.4/8.6.12) with SMTP id QAA05056; Mon, 3 Feb 1997 16:13:35 -0500 (EST)
Date: Mon, 3 Feb 1997 16:13:35 -0500 (EST)
From: "Eric J. Chet" <ejc@gargoyle.bazzle.com>
To: Bakul Shah <bakul@torrentnet.com>
cc: hackers@FreeBSD.ORG
Subject: Re: g++, STL and -frepo on FreeBSD-2.2-Beta 
In-Reply-To: <199702021539.KAA21607@chai.plexuscom.com>
Message-ID: <Pine.BSF.3.95.970203155742.4919A-100000@gargoyle.bazzle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > 	The -frepo patches don't work on our version of the g++ and 
> > ld.  I assume ld is the problem.  I haven't had the time to take a look 
> > to see what needs to be changed. The -frepo patch from Cygnus when
> > applied, should create a set of *.ii one for each source file complied 
> > from g++.  The *.ii files specify all templates that need to be 
> > instantiated before linking can take place.  I believe there is a collect2
> > module that performs the instantiations task.  
> 
> I started with the *stock* gcc-2.7.2 distribution (+ 2.7.2-2.7.2.1
> diff), not the one in the FreeBSD source tree.
> 
> The -frepo patch generates a .rpo file.  In the test case I posted
> this .rpo file contains lines like

Oops, *.rpo files I use the EDG complier at work it generates *.ii files,
same idea.

> > 	On the other hand, the only thing you lose by not having the
> > repository with our native compiler is executable size.  The compiler
> > will instantiated every template used in a object file and include it in
> > that object file.  Meaning, you can have duplicate template instantiations
> > across different object files.
> 
> This appears not to be the case.  Are there any flags which make
> this possible?  Does libg++-2.7.1 have to be compiled with any
> special flags or defines?
> 

Works for me, -current g++ compiler.

--
ejc@gargoyle: cat list1.cpp
#include <iostream.h>
#include <stl.h>
 
int array1 [] = { 9, 16, 36 };
int array2 [] = { 1, 4 };
 
int main ()
{
  list<int> l1 (array1, array1 + 3);
  list<int> l2 (array2, array2 + 2);
  list<int>::iterator i1 = l1.begin ();
  l1.splice (i1, l2);
  list<int>::iterator i2 = l1.begin ();
  while (i2 != l1.end ())
    cout << *i2++ << endl;
  return 0;
}
ejc@gargoyle: g++ -o list1 list1.cpp
ejc@gargoyle: ./list1               
1
4
9
16
36
ejc@gargoyle: 
--

I have been using stl under our current compiler for a while without any
problems, other than the known bugs.  Just waiting for g++ 2.8.0
template member functions, static template member data, default 
template member parameters and sgi_stl.  Life is good.

                                              Eric J. Chet
					       - ejc@naserver1.cb.lucent.com
                                               - ejc@bazzle.com



From owner-freebsd-hackers  Mon Feb  3 13:41:41 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA22419
          for hackers-outgoing; Mon, 3 Feb 1997 13:41:41 -0800 (PST)
Received: from main.gbdata.com (tel_ppp0005.livingston.net [207.22.211.14])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA22396
          for <hackers@freebsd.org>; Mon, 3 Feb 1997 13:41:24 -0800 (PST)
Received: (from gclarkii@localhost) by main.gbdata.com (8.7.5/8.6.9) id PAA06850; Mon, 3 Feb 1997 15:41:07 -0600 (CST)
From: Gary Clark II <gclarkii@main.gbdata.com>
Message-Id: <199702032141.PAA06850@main.gbdata.com>
Subject: Re: How to build the whole tree -static?
To: ben@narcissus.ml.org (Stranger Bone)
Date: Mon, 3 Feb 1997 15:41:03 -0600 (CST)
Cc: mrcpu@cdsnet.net, hackers@freebsd.org
In-Reply-To: <Pine.BSF.3.91.970203123927.6759C-100000@narcissus.ml.org> from Stranger Bone at "Feb 3, 97 12:41:34 pm"
X-Mailer: ELM [version 2.4ME+ PL22 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Stranger Bone wrote:
> On Mon, 3 Feb 1997, Jaye Mathisen wrote:
> 
> > 
> > 
> > I have space to burn on 1 box.  Is there an easy way to tweak the build
> > process to make it compile the whole darn thing non-shared?
> > 
> 
> Change it to 
> 
> CFLAGS          ?=      -O -static
I don't belive that this would work right.  I should be a linker
flag...

> 
> 
>  Ben
> 
You should also be able to set the env variable NOSHARED and get the
same effect.  Thats why I added this. 

Gary

-- 
Gary Clark II   (N5VMF) |    I speak only for myself and "maybe" my company 
gclarkii@GBData.COM     |          Member of the FreeBSD Doc Team 
  Providing Internet and ISP startups mail info@GBData.COM for information
   FreeBSD FAQ at ftp://ftp.FreeBSD.ORG/pub/FreeBSD/docs/freebsd-faq.ascii 

From owner-freebsd-hackers  Mon Feb  3 13:42:35 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA22484
          for hackers-outgoing; Mon, 3 Feb 1997 13:42:35 -0800 (PST)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA22478
          for <hackers@freebsd.org>; Mon, 3 Feb 1997 13:42:31 -0800 (PST)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id OAA23359; Mon, 3 Feb 1997 14:42:12 -0700 (MST)
Date: Mon, 3 Feb 1997 14:42:12 -0700 (MST)
Message-Id: <199702032142.OAA23359@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Jaye Mathisen  <mrcpu@cdsnet.net>
Cc: hackers@freebsd.org
Subject: Re: How to build the whole tree -static?
In-Reply-To: <Pine.NEB.3.95.970203114938.13493E-100000@mail.cdsnet.net>
References: <Pine.NEB.3.95.970203114938.13493E-100000@mail.cdsnet.net>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> I have space to burn on 1 box.  Is there an easy way to tweak the build
> process to make it compile the whole darn thing non-shared?

# setenv NOSHARED
# cd /usr/src
# make world


Nate

From owner-freebsd-hackers  Mon Feb  3 14:04:53 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA23601
          for hackers-outgoing; Mon, 3 Feb 1997 14:04:53 -0800 (PST)
Received: from narcissus.ml.org (root@brosenga.Pitzer.edu [134.173.120.201])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA23595
          for <hackers@freebsd.org>; Mon, 3 Feb 1997 14:04:48 -0800 (PST)
Received: (from ben@localhost) by narcissus.ml.org (8.7.5/8.7.3) id OAA12080; Mon, 3 Feb 1997 14:04:39 -0800 (PST)
Date: Mon, 3 Feb 1997 14:04:38 -0800 (PST)
From: Stranger Bone <ben@narcissus.ml.org>
To: Nate Williams <nate@mt.sri.com>
cc: Jaye Mathisen <mrcpu@cdsnet.net>, hackers@freebsd.org
Subject: Re: How to build the whole tree -static?
In-Reply-To: <199702032142.OAA23359@rocky.mt.sri.com>
Message-ID: <Pine.BSF.3.91.970203140408.11389A-100000@narcissus.ml.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Mon, 3 Feb 1997, Nate Williams wrote:

> > I have space to burn on 1 box.  Is there an easy way to tweak the build
> > process to make it compile the whole darn thing non-shared?
> 
> # setenv NOSHARED
> # cd /usr/src
> # make world
> 

Perhaps this only works within the tree, not within ports?

narcissus:{/usr/ports/misc/fd}% setenv NOSHARED
narcissus:{/usr/ports/misc/fd}% make
<snip>
cc -O -DFD -DFREEBSD -DDEFRUNCOM=\"/usr/local/etc/fdrc\" -O -c term.c
cc -O -DFD -DFREEBSD -DDEFRUNCOM=\"/usr/local/etc/fdrc\" -O -c pathname.c
cc -O -DFD -DFREEBSD -DDEFRUNCOM=\"/usr/local/etc/fdrc\" -O -c libc.c
<I see no -static flag here -- am I missing something?>
<snip>
narcissus:{/usr/ports/misc/fd}% cd work/FD-1.01/
narcissus:{/usr/ports/misc/fd/work/FD-1.01}% file fd
fd: FreeBSD/i386 demand paged dynamically linked executable not stripped
			      ^^^^^^^^^^^^^^^^^^


> 
> Nate
> 



 Ben

The views expressed above are not those of the Worker's Compensation 
Board of Queensland, Australia.



From owner-freebsd-hackers  Mon Feb  3 14:06:10 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA23702
          for hackers-outgoing; Mon, 3 Feb 1997 14:06:10 -0800 (PST)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA23689
          for <hackers@freebsd.org>; Mon, 3 Feb 1997 14:06:05 -0800 (PST)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id PAA23462; Mon, 3 Feb 1997 15:06:00 -0700 (MST)
Date: Mon, 3 Feb 1997 15:06:00 -0700 (MST)
Message-Id: <199702032206.PAA23462@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Stranger Bone <ben@narcissus.ml.org>
Cc: hackers@freebsd.org
Subject: Re: How to build the whole tree -static?
In-Reply-To: <Pine.BSF.3.91.970203140408.11389A-100000@narcissus.ml.org>
References: <199702032142.OAA23359@rocky.mt.sri.com>
	<Pine.BSF.3.91.970203140408.11389A-100000@narcissus.ml.org>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > > process to make it compile the whole darn thing non-shared?
> > 
> > # setenv NOSHARED
> > # cd /usr/src
> > # make world
> > 
> 
> Perhaps this only works within the tree, not within ports?

I know *nothing* about ports.  You'd need to take to Satoshi, Chuck, or
others about that.


Nate

From owner-freebsd-hackers  Mon Feb  3 14:22:07 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA24500
          for hackers-outgoing; Mon, 3 Feb 1997 14:22:07 -0800 (PST)
Received: from sax.sax.de (sax.sax.de [193.175.26.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA24480
          for <hackers@freebsd.org>; Mon, 3 Feb 1997 14:21:08 -0800 (PST)
Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA11871; Mon, 3 Feb 1997 23:20:43 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id XAA14281; Mon, 3 Feb 1997 23:17:12 +0100 (MET)
Message-ID: <Mutt.19970203231712.j@uriah.heep.sax.de>
Date: Mon, 3 Feb 1997 23:17:12 +0100
From: j@uriah.heep.sax.de (J Wunsch)
To: ben@narcissus.ml.org (Stranger Bone)
Cc: mrcpu@cdsnet.net (Jaye Mathisen), hackers@freebsd.org
Subject: Re: How to build the whole tree -static?
References: <Pine.NEB.3.95.970203114938.13493E-100000@mail.cdsnet.net> <Pine.BSF.3.91.970203123927.6759C-100000@narcissus.ml.org>
X-Mailer: Mutt 0.55-PL10
Mime-Version: 1.0
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <Pine.BSF.3.91.970203123927.6759C-100000@narcissus.ml.org>; from Stranger Bone on Feb 3, 1997 12:41:34 -0800
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

As Stranger Bone wrote:

> > I have space to burn on 1 box.  Is there an easy way to tweak the build
> > process to make it compile the whole darn thing non-shared?
> > 
> 
> Ha!  I only found the answer to this last night.
> 
> You need to edit /usr/share/mk/sys.mk.

But of course, editing /etc/make.conf would have sufficed as well.

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

From owner-freebsd-hackers  Mon Feb  3 14:40:17 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA25370
          for hackers-outgoing; Mon, 3 Feb 1997 14:40:17 -0800 (PST)
Received: from po2.glue.umd.edu (root@po2.glue.umd.edu [129.2.128.45])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA25364
          for <hackers@freebsd.org>; Mon, 3 Feb 1997 14:40:11 -0800 (PST)
Received: from uplink.eng.umd.edu (uplink.eng.umd.edu [129.2.98.181]) by po2.glue.umd.edu (8.8.5/8.7.3) with ESMTP id RAA29696; Mon, 3 Feb 1997 17:40:05 -0500 (EST)
Received: from localhost (chuckr@localhost) by uplink.eng.umd.edu (8.8.5/8.7.3) with SMTP id RAA13738; Mon, 3 Feb 1997 17:40:05 -0500 (EST)
X-Authentication-Warning: uplink.eng.umd.edu: chuckr owned process doing -bs
Date: Mon, 3 Feb 1997 17:40:05 -0500 (EST)
From: Chuck Robey <chuckr@glue.umd.edu>
X-Sender: chuckr@uplink.eng.umd.edu
To: Nate Williams <nate@mt.sri.com>
cc: Stranger Bone <ben@narcissus.ml.org>, hackers@freebsd.org
Subject: Re: How to build the whole tree -static?
In-Reply-To: <199702032206.PAA23462@rocky.mt.sri.com>
Message-ID: <Pine.OSF.3.95q.970203173756.12858L-100000@uplink.eng.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Mon, 3 Feb 1997, Nate Williams wrote:

> > > > process to make it compile the whole darn thing non-shared?
> > > 
> > > # setenv NOSHARED
> > > # cd /usr/src
> > > # make world
> > > 
> > 
> > Perhaps this only works within the tree, not within ports?
> 
> I know *nothing* about ports.  You'd need to take to Satoshi, Chuck, or
> others about that.

I'd be kinda interested in just how BIG building the tree non-shared is,
but I hate to say that there isn't any reliable way to build all the ports
non-shared.  Just adding -static to your CFLAGS would get some of it, but
not all by a long shot.

> 
> 
> Nate
> 

----------------------------+-----------------------------------------------
Chuck Robey                 | Interests include any kind of voice or data 
chuckr@eng.umd.edu          | communications topic, C programming, and Unix.
9120 Edmonston Ct #302      |
Greenbelt, MD 20770         | I run Journey2 and picnic, both FreeBSD
(301) 220-2114              | version 3.0 current -- and great FUN!
----------------------------+-----------------------------------------------


From owner-freebsd-hackers  Mon Feb  3 14:50:33 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA25769
          for hackers-outgoing; Mon, 3 Feb 1997 14:50:33 -0800 (PST)
Received: from merix.merix.com (merix.merix.com [198.145.172.40])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA25727
          for <freebsd-hackers@freebsd.org>; Mon, 3 Feb 1997 14:50:29 -0800 (PST)
Received: from sandy.merix.com by merix.merix.com with SMTP
	(1.38.110.45/16.2) id AA074970666; Mon, 3 Feb 1997 14:57:46 -0800
Received: by sandy.merix.com (4.1/8.0)
	id AA02205; Mon, 3 Feb 97 14:46:56 PST
Date: Mon, 3 Feb 97 14:46:56 PST
Subject: Two-way pipe possible without C/perl?
To: freebsd-hackers@freebsd.org
From: Troy Curtiss <troyc@sandy.merix.com>
Message-Id: <troyc-9701032246.AA0002700@sandy>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi,
  I am looking for a very quick and dirty way to have my FreeBSD
box page me when certain systems go down at work.  The easiest way
I can think of is to create a 2-way pipe between a chat command and
the cu command.  Something like:

chat " '' ATZ OK ATDT1800PAGER# CONNECT 'PIN12345' Sent ATH" <->
  cu -l /dev/cuaa0 -s 300

in a shell script or etc...  Is there a shell (sh, csh, tcsh, bash)
mechanism to wire process A's stdin to process B's stdout, and vice-
versa, or am I going to have to use perl/expect/C (more time-consuming)?
No big deal, but if anybody has a good idea, I'd appreciate it.

Cheers,
Troy


--
 /-----------------------------------------------------------\
| Troy Curtiss, HW/SW Engineer | Email: troyc@merix.com       |
| Merix Corporation, CL-302    | Phone: (970) 203-6643        |
| Loveland, CO 80537           | Fax  : (970) 203-6610        |
 \-----------------------------------------------------------/

From owner-freebsd-hackers  Mon Feb  3 15:10:45 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA26690
          for hackers-outgoing; Mon, 3 Feb 1997 15:10:45 -0800 (PST)
Received: from mail.bb.cc.wa.us ([208.8.136.10])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA26680
          for <hackers@FreeBSD.org>; Mon, 3 Feb 1997 15:10:38 -0800 (PST)
Received: (from chris@localhost) by mail.bb.cc.wa.us (8.8.3/8.8.3) id XAA05341; Mon, 3 Feb 1997 23:11:02 GMT
Date: Mon, 3 Feb 1997 23:11:02 +0000 ()
From: Chris Coleman <chris@mail.bb.cc.wa.us>
To: Mark Tinguely <tinguely@plains.nodak.edu>
cc: avalon@coombs.anu.edu.au, brian@awfulhak.demon.co.uk, hackers@FreeBSD.org
Subject: Re: IPFILTER
In-Reply-To: <199701132218.QAA13145@plains.nodak.edu>
Message-ID: <Pine.BSF.3.91.970203230922.5318A-100000@mail.bb.cc.wa.us>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

Darren, All is well, Everything is still running just Great.

Now, I need to set up the FTP proxy agent.

I am assuming this is what I need to do becuase FTP will not work.

So where do I get general Instructions for Setting one of these up.

Just point me in the right Direction, Is there a FAQ or DOC somewhere?

Thanks

From owner-freebsd-hackers  Mon Feb  3 15:15:59 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA26953
          for hackers-outgoing; Mon, 3 Feb 1997 15:15:59 -0800 (PST)
Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA26911
          for <freebsd-hackers@freebsd.org>; Mon, 3 Feb 1997 15:15:42 -0800 (PST)
Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id KAA02113; Tue, 4 Feb 1997 10:19:29 +1100 (EST)
Date: Tue, 4 Feb 1997 10:19:29 +1100 (EST)
From: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
To: Troy Curtiss <troyc@sandy.merix.com>
cc: freebsd-hackers@freebsd.org
Subject: Re: Two-way pipe possible without C/perl?
In-Reply-To: <troyc-9701032246.AA0002700@sandy>
Message-ID: <Pine.BSF.3.91.970204101827.25849M-100000@panda.hilink.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk



On Mon, 3 Feb 1997, Troy Curtiss wrote:

> Hi,
>   I am looking for a very quick and dirty way to have my FreeBSD
> box page me when certain systems go down at work.  The easiest way
> I can think of is to create a 2-way pipe between a chat command and
> the cu command.  Something like:
> 
> chat " '' ATZ OK ATDT1800PAGER# CONNECT 'PIN12345' Sent ATH" <->
>   cu -l /dev/cuaa0 -s 300

stty -f /dev/cuaa0 300
 chat " '' ATZ OK ATDT1800PAGER# CONNECT 'PIN12345' Sent ATH" \
    < /dev/cuaa0 > /dev/cuaa0


cheers,

Danny

From owner-freebsd-hackers  Mon Feb  3 15:17:41 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA27132
          for hackers-outgoing; Mon, 3 Feb 1997 15:17:41 -0800 (PST)
Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA27105
          for <freebsd-hackers@freebsd.org>; Mon, 3 Feb 1997 15:16:50 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
          by hydrogen.nike.efn.org (8.8.4/8.8.4) with SMTP
	  id PAA19187; Mon, 3 Feb 1997 15:16:36 -0800 (PST)
Date: Mon, 3 Feb 1997 15:16:33 -0800 (PST)
From: John-Mark Gurney <jmg@nike.efn.org>
Reply-To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
To: Troy Curtiss <troyc@sandy.merix.com>
cc: freebsd-hackers@freebsd.org
Subject: Re: Two-way pipe possible without C/perl?
In-Reply-To: <troyc-9701032246.AA0002700@sandy>
Message-ID: <Pine.NEB.3.95.970203151149.27974E-100000@hydrogen.nike.efn.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Mon, 3 Feb 1997, Troy Curtiss wrote:

> Hi,
>   I am looking for a very quick and dirty way to have my FreeBSD
> box page me when certain systems go down at work.  The easiest way
> I can think of is to create a 2-way pipe between a chat command and
> the cu command.  Something like:
> 
> chat " '' ATZ OK ATDT1800PAGER# CONNECT 'PIN12345' Sent ATH" <->
>   cu -l /dev/cuaa0 -s 300
> 
> in a shell script or etc...  Is there a shell (sh, csh, tcsh, bash)
> mechanism to wire process A's stdin to process B's stdout, and vice-
> versa, or am I going to have to use perl/expect/C (more time-consuming)?
> No big deal, but if anybody has a good idea, I'd appreciate it.

why not just do something like this:
chat -f file < /dev/cuaa0 > /dev/cuaa0

and if you need uucp locking do something like this:
if shlock -p $$ -f /var/log/LCK.ttyd0; then
	chat -f file < /dev/cuaa0 > /dev/cuaa0
else
	echo someone else has the modem
fi

hope this helps...

John-Mark

gurney_j@efn.org
http://resnet.uoregon.edu/~gurney_j/
Modem/FAX: (541) 683-6954   (FreeBSD Box)

Live in Peace, destroy Micro$oft, support free software, run FreeBSD (unix)


From owner-freebsd-hackers  Mon Feb  3 15:55:37 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA28770
          for hackers-outgoing; Mon, 3 Feb 1997 15:55:37 -0800 (PST)
Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA28763
          for <freebsd-hackers@FreeBSD.ORG>; Mon, 3 Feb 1997 15:55:29 -0800 (PST)
Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.5/CET-v2.1) with SMTP id XAA13730 for <freebsd-hackers@FreeBSD.ORG>; Mon, 3 Feb 1997 23:55:23 GMT
Date: Tue, 4 Feb 1997 08:55:23 +0900 (JST)
From: Michael Hancock <michaelh@cet.co.jp>
To: freebsd-hackers@FreeBSD.ORG
Subject: mset, mclear, msleep, mwakeup (was Re: Using rfork() / threads)
In-Reply-To: <Pine.SUN.3.91.970203092205.3325F-100000@terra>
Message-ID: <Pine.SV4.3.95.970204084303.13628A-100000@parkplace.cet.co.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Mon, 3 Feb 1997, Ron G. Minnich wrote:

> On Sat, 1 Feb 1997, Michael Hancock wrote:
> > The Vahalia book mentions shared memory locks for 4.4BSD that worked
> > essentially the same way.  They were named mset, mwait, or something like
> > that.
> 
> yeah, but recall that I did this stuff 9/94. mset etc. were not around 
> then, and appear to still not be. 
> 
> > Fastlock sounds cool, but shared memory locks are supposed to be fast. 
> It's a bit more complex than shared memory locks. The problem is making
> shared memory locks between heavyweight processes that are efficient and 
> in particular never do a system call unless needed. 
> 
> > I prefer the mxxx conventions to categorize it with the
> > mmap calls. 
> 
> works for me. 
> 

This is how Vahalia describes it.  On the newsgroups John Dyson said he
remembers seeing a document in 4.4Lite somewhere describing it. 

Can you work with these interfaces?  Maybe you can submit them to John for
review or colloborate with him on rewriting it.

mset() and mclear() must be user level functions on architectures that
have atomic test-and-set.  You don't do a system call unless necessary.

value = mset(sem, wait);

	sem is a pointer to a semaphore value
	wait is a boolean that is set to true if you want to block
	value is zero if the semaphore has been acquired

mclear(sem);

If you want to block and unblock use the following:

msleep(sem);

mwakeup(sem);

Wakes up at least one process blocked on this semaphore or does nothing if
there are no blocked semaphores.

Regards,


Mike Hancock


From owner-freebsd-hackers  Mon Feb  3 15:56:55 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA28848
          for hackers-outgoing; Mon, 3 Feb 1997 15:56:55 -0800 (PST)
Received: from jason.garman.net (pm106-18.dialip.mich.net [192.195.231.220])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA28837
          for <hackers@freebsd.org>; Mon, 3 Feb 1997 15:56:47 -0800 (PST)
Resent-From: garman@jason.garman.net
Received: (qmail 1380 invoked by uid 1000); 3 Feb 1997 23:57:08 -0000
Resent-Message-ID: <19970203235708.1379.qmail@jason.garman.net>
Message-ID: <Mutt.19970202231453.garman@jason.garman.net>
Date: Sun, 2 Feb 1997 23:14:53 -0500
From: garman@jason.garman.net (Jason Garman)
To: helbig@BA-Stuttgart.De (Wolfgang Helbig)
Subject: Re: CMD640b flaw workaround
References: <Pine.GSO.3.95-heb-2.07.970202182140.22764B-100000@csd> <199702021846.TAA03678@amadeus.informatik.ba-stuttgart.de>
X-Mailer: Mutt 0.58
Mime-Version: 1.0
Reply-To: garman@phs.k12.ar.us
X-Phase-Of-Moon: The Moon is Waning Crescent (26% of Full)
X-Operating-System: FreeBSD/i386 2.1.5-RELEASE
In-Reply-To: <199702021846.TAA03678@amadeus.informatik.ba-stuttgart.de>; from Wolfgang Helbig on Feb 2, 1997 19:04:49 +0100
Resent-Date: Mon, 3 Feb 1997 18:57:07 -0500
Resent-To: hackers@freebsd.org
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

First, thanks for the patch!

Wolfgang Helbig writes:
> So maybe you should upgrade to FreeBSD 2.2 and test then.
> 
Well, (unrelated) I tried to do that through my ppp connection, but the
2.2-BETA kernel on the install floppy (just downloaded tonight from
ftp.freebsd.org) refuses to recognize my modem (sio1)

I turned on verbose probe using flags 0x80 and it tells me:

sio1: probe test 5 failed
sio1: probe test 6 failed
sio1 not found at 0x2f8

My working 2.1.5-RELEASE kernel reports:

sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16450

(yes, it is a cheap 14.4 internal card w/a 16540 :-/)

I was sure to disable all possibly conflicting devices in the 2.2 visual
configuration, btw.  I'm guessing that it's just not allowing the card
enough time to reply; is there a way to increase the delay from the
configuration interface?

So close, yet so far... (trying to backport the patch to 2.1.5 was a
futile exercise :-))

Thanks,
-- 
Jason Garman                             http://www.nesc.k12.ar.us/~garman/
Student, Eleanor Roosevelt High School                 garman@phs.k12.ar.us

From owner-freebsd-hackers  Mon Feb  3 17:01:07 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA03804
          for hackers-outgoing; Mon, 3 Feb 1997 17:01:07 -0800 (PST)
Received: from aries.bb.cc.wa.us (root@[208.8.136.11])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA03796
          for <freebsd-hackers@FreeBSD.ORG>; Mon, 3 Feb 1997 17:01:03 -0800 (PST)
Received: from localhost (chris@localhost) by aries.bb.cc.wa.us (8.8.3/8.6.9) with SMTP id RAA01280; Mon, 3 Feb 1997 17:01:18 -0800 (PST)
Date: Mon, 3 Feb 1997 17:01:18 -0800 (PST)
From: Chris Coleman <chris@bb.cc.wa.us>
To: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
cc: Troy Curtiss <troyc@sandy.merix.com>, freebsd-hackers@FreeBSD.ORG
Subject: Re: Two-way pipe possible without C/perl?
In-Reply-To: <Pine.BSF.3.91.970204101827.25849M-100000@panda.hilink.com.au>
Message-ID: <Pine.NEB.3.94.970203170016.1262A-100000@aries.bb.cc.wa.us>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

I like this, alot.  But how are you monitoring these system so FreeBSD
knows when to send you a message?

I have a pager and am very interested in this.

Thanks.

Christopher J. Coleman (chris@aries.bb.cc.wa.us)
Computer Support Technician I  (509)-766-8873
Big Bend Community College  Internet Instructor
FreeBSD Book Project:  http://www.bb.cc.wa.us/~chris/book.html
Death is life's way of telling you you're fired.


From owner-freebsd-hackers  Mon Feb  3 17:09:49 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA04534
          for hackers-outgoing; Mon, 3 Feb 1997 17:09:49 -0800 (PST)
Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA04484
          for <hackers@freebsd.org>; Mon, 3 Feb 1997 17:09:21 -0800 (PST)
Received: from awfulhak.demon.co.uk (localhost.coverform.lan [127.0.0.1]) by awfulhak.demon.co.uk (8.8.4/8.7.3) with ESMTP id AAA24492; Tue, 4 Feb 1997 00:41:55 GMT
Message-Id: <199702040041.AAA24492@awfulhak.demon.co.uk>
X-Mailer: exmh version 1.6.9 8/22/96
To: Ari Suutari <ari.suutari@ps.carel.fi>
cc: "'cmott@srv.net'" <cmott@srv.net>, hackers@freebsd.org,
        Eivind Eklund <eivind@dimaga.com>, brian@utell.co.uk
Subject: Re: Single socket version of natd 
In-reply-to: Your message of "Mon, 03 Feb 1997 11:18:56 +0200."
             <01BC11C5.638A78A0@sodium.ps.carel.fi> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 04 Feb 1997 00:41:54 +0000
From: Brian Somers <brian@awfulhak.demon.co.uk>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Hi,
> 
> 	I fixed the core dump - it was a silly-almost-typing mistake.
> 	About using /etc/services for the port numbers: I was already
> 	putting it when I started to think should it be natd/tcp or
> 	natd/udp or something else (since the sockets are not
> 	tcp or udp sockets). Any opinions on that ?
> 
> 		Ari S.
> 
> -----Original Message-----
> From:	Brian Somers [SMTP:brian@awfulhak.demon.co.uk]
> Sent:	1. helmikuuta 1997 5:35
> To:	Ari Suutari
> Cc:	'cmott@srv.net'
> Subject:	Re: Single socket version of natd 
> 
> The -l and -a options always core-dump.  I havn't looked into what's causing
> this.  I've passed the -a option "10.0.1.254" and "raffles.coverform.lan",
> both without the quotes and both resolvable on my machine.
> 
> The -a option could do with checking for a name from /etc/services rather than
> defaulting to 32000.
> 

I received your fix for the coredumps - I'll test them tomorrow evening.
Thanks.

I've had a look at the getservbyname stuff.... it's possible to call
getservbyname( ..., "raw" ) and have an entry in /etc/services saying

    masqd 6668/raw  # This is a raw socket

I think this is the best option - is there any reason why this shouldn't
be so (cc to hackers@freebsd.org) ?  It seems more appropriate than putting
"untrue" stuff in here.  Maybe "divert" would be more appropriate ?

BTW, Charles/Elvind - what's the score with the code that attempts to "keep"
the source port ?  This idea is growing on me ;)  I've tested 1.9 (http ref
from www.srv.net/~cmott to Elvind's page) and it seems good.  It's gettin'
*real* close to 2.2-GAMMA now - it would be *really* nice to have this code
make it to 2.2 :-O
-- 
Brian <brian@awfulhak.demon.co.uk>, <brian@freebsd.org>
      <http://www.awfulhak.demon.co.uk/>
Don't _EVER_ lose your sense of humour....



From owner-freebsd-hackers  Mon Feb  3 17:14:45 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA04893
          for hackers-outgoing; Mon, 3 Feb 1997 17:14:45 -0800 (PST)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA04880
          for <hackers@freefall.freebsd.org>; Mon, 3 Feb 1997 17:14:38 -0800 (PST)
Received: from current1.whistle.com (current1.whistle.com [207.76.205.22])
          by alpo.whistle.com (8.8.5/8.8.4) with SMTP
	  id RAA22981; Mon, 3 Feb 1997 17:11:19 -0800 (PST)
Message-ID: <32F68C4F.3F54BC7E@whistle.com>
Date: Mon, 03 Feb 1997 17:09:35 -0800
From: Julian Elischer <julian@whistle.com>
Organization: Whistle Communications
X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386)
MIME-Version: 1.0
To: Bill Kish <kish@browncow.com>
CC: hackers@freefall.freebsd.org
Subject: Re: kernel malloc options
References: <199702031942.OAA18041@browncow.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Bill Kish wrote:

>  I'm working on a a Network related module which performs a function
> similar to Network Address Translation. This module needs to
> dynamically allocate small (~40 byte) structures to keep track of
> currently established TCP connections between machines on the "inside"
> and "outside" networks.

Wow, a couple of months ago we had no address translation, now we
have *4* different ones.. :)

> 
>  Currently, I'm malloc()ing these structures as needed using the
> following parameters:
> 
>  malloc((u_long)sizeof(*conxn), M_TEMP, M_NOWAIT)
> 
>  This appears to work fine in my initial lightly loaded tests,
> however, I'm concerned about what will happen when the system is under
> heavy load. I have the following questions and would appreciate any
> advice offered!
What I do is cache a certain number of these..
I keep a free_thing list which
will hold a maximum of N items

If I ever free more than N then I start actually doing  "free(x,
M_TEMP)",
but until then I just keep them locally, this usually means that if the
number of
items is gradually increasing I'm doing malloc's, but with 
small scale fluctuations, they are satisfied from the cache.

of course malloc/free are not all that expensive
in general..


> 
>  1) Is malloc() a reasonable allocator for small highly dynamic
>    objects?
> 
>  2) Is M_TEMP a good choice? Does it make a difference?
it's fine. to use any other, you'd have to edit malloc.h
and for LKM stuff that's not an option.

> 
>  3) Are there any config options that affect the amount of pinned
>     kernel memory available for malloc? The system will be doing
>     little else besides dealing with these packets...
> 
> 
> 
>                 Thanks In Advance,
> 
>                   -BK
> --

From owner-freebsd-hackers  Mon Feb  3 18:09:56 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id SAA08338
          for hackers-outgoing; Mon, 3 Feb 1997 18:09:56 -0800 (PST)
Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id SAA08325
          for <hackers@freebsd.org>; Mon, 3 Feb 1997 18:09:51 -0800 (PST)
Received: by sovcom.kiae.su id AA22754
  (5.65.kiae-1  for hackers@freebsd.org); Tue, 4 Feb 1997 04:48:40 +0300
Received: by sovcom.KIAE.su (UUMAIL/2.0); Tue,  4 Feb 97 04:48:40 +0300
Received:  from gate.phantom.ru by router.phantom.ru (UUPC/extended 1.12o) with UUCP
           for hackers@freebsd.org; Tue, 04 Feb 1997 03:52:34 +0300
Received: by gate.phantom.ru (FIDO2UU 2.11c [OS/2,C++ Set]) with FTN; Tue,  4 Feb 1997 03:52:34 +0300
To: hackers@freebsd.org
Message-Id: <32F6F8D2@gate.phantom.ru>
Date: Mon,  3 Feb 1997 21:36:12 +0300
From: Ilmar Habibulin <Ilmar_Habibulin@p777.f691.n5020.z2.fidonet.org>
Reply-To: Ilmar Habibulin <Ilmar_Habibulin@p777.f691.n5020.z2.fidonet.org>
Subject: Need some help or advice
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Dear Sirs.

    I have a hobby. Simply it is the computer security and related topics. 
2 months ago i've got a Walnut Creek FreeBSD 2.1.0 CDROM distribution 
willing to design and implement MAC(mandatory access control) according to 
Bell-LaPadula model or something like that. I choose FreeBSD because of 
free avaliable source. But the problem is, that breaking through megabytes 
of kernel routines i've got a terriblre headache. :( I don't know where to 
look at. What kernel structures can i modify and what i should recompile 
next to get it work. ( After my "modifications" the kernel stops with bus 
error ;-))
Where can i find information of kernel internals such as processes and 
user credits, IPC, VOP_ stuff, v-nodes and its relations with i-nodes, the 
most complete info on how does this thing works inside.

I'll want to buy a book "4.4BSD design and implementation". Is it enough?

I read manuals and faqs. It said that You may be interested in such stuff. 
I have no much time, but i want to try.

thanks for advice.

                                       Certainly Yours, Ilmar.
                                       Moscow, Russia.

PS. Sorry for bad English if any mistakes have been made. I have no 
English-speaking practice for a long time, only English-reading. ;-)


    AKA ~The~Blue~Glasses~ ö8-)
--- ... If I only had a brain ...
 * Origin: Genuine INTEL - ligent Gentelman (2:5020/691.777)


From owner-freebsd-hackers  Mon Feb  3 18:37:35 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id SAA10443
          for hackers-outgoing; Mon, 3 Feb 1997 18:37:35 -0800 (PST)
Received: from darkstar (ras511.srv.net [205.180.127.11])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id SAA10436
          for <hackers@freebsd.org>; Mon, 3 Feb 1997 18:37:31 -0800 (PST)
Received: (from cmott@localhost) by darkstar (8.6.12/8.6.12) id TAA07768; Mon, 3 Feb 1997 19:36:38 -0700
Date: Mon, 3 Feb 1997 19:36:36 -0700 (MST)
From: Charles Mott <cmott@srv.net>
X-Sender: cmott@darkstar
To: Brian Somers <brian@awfulhak.demon.co.uk>
cc: Ari Suutari <ari.suutari@ps.carel.fi>, hackers@freebsd.org,
        Eivind Eklund <eivind@dimaga.com>, brian@utell.co.uk
Subject: Re: Single socket version of natd 
In-Reply-To: <199702040041.AAA24492@awfulhak.demon.co.uk>
Message-ID: <Pine.BSF.3.91.970203185849.7428C-100000@darkstar>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > The -l and -a options always core-dump.  I havn't looked into what's causing
> > this.  I've passed the -a option "10.0.1.254" and "raffles.coverform.lan",
> > both without the quotes and both resolvable on my machine.

The -l option may core dump, or give a segmentation error, because of an 
error that crept into alias_db.c after version 1.6.  It has been fixed in
ppp+pktAlias1.9-gamma.tar.gz at http://www.srv.net/~cmott/alias.html.

Eivind has these updates and has integrated them into his codebase, 
which he is continuing to work on.  He writes that he has changed some of 
the compile options (ALIAS_ALLOW_INCOMING, ALIAS_SAME_PORTS, etc.) to ppp 
commands.  


> BTW, Charles/Elvind - what's the score with the code that attempts to "keep"
> the source port ?  This idea is growing on me ;)  I've tested 1.9 (http ref
> from www.srv.net/~cmott to Elvind's page) and it seems good.  It's gettin'
> *real* close to 2.2-GAMMA now - it would be *really* nice to have this code
> make it to 2.2 :-O

It has been working for a week or two now.


Charles Mott

From owner-freebsd-hackers  Mon Feb  3 20:44:08 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA17589
          for hackers-outgoing; Mon, 3 Feb 1997 20:44:08 -0800 (PST)
Received: from elysium.uwa.edu.au (elysium.uwa.edu.au [130.95.128.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA17583
          for <hackers@freebsd.org>; Mon, 3 Feb 1997 20:44:03 -0800 (PST)
Received: from fenrus.rattus.uwa.edu.au (trojanrat.civil.uwa.edu.au [130.95.140.60]) by elysium.uwa.edu.au (8.8.2/8.8.0) with ESMTP id MAA22441 for <hackers@freebsd.org>; Tue, 4 Feb 1997 12:43:55 +0800 (WST)
Received: (from smap@localhost) by fenrus.rattus.uwa.edu.au (8.7.5/8.7.3) id MAA05328 for <hackers@freebsd.org>; Tue, 4 Feb 1997 12:22:26 +0800 (WST)
Received: from ratbox.rattus.uwa.edu.au(192.168.1.2) by fenrus.rattus.uwa.edu.au via smap (V1.3)
	id sma005326; Tue Feb  4 12:22:01 1997
Received: from ratbox.rattus.uwa.edu.au (packrat@localhost [127.0.0.1]) by ratbox.rattus.uwa.edu.au (8.7.5/8.6.11) with ESMTP id MAA03517 for <hackers@freebsd.org>; Tue, 4 Feb 1997 12:43:01 +0800
Message-Id: <199702040443.MAA03517@ratbox.rattus.uwa.edu.au>
To: hackers@freebsd.org
Subject: ping(8)
Reply-To: packrat@iinet.net.au
Date: Tue, 04 Feb 1997 12:42:59 +0800
From: Bruce Murphy <packrat@iinet.net.au>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Having just had to edit the ping binary by hand (for the nth time but
I never keep them around) so that I could use it to diagnose a remote
problem. (well actually some idiot walking into the room and pulling
the terminator off my test run of thinnet and staring at it) I thought
ask the list whether anyone had any religious objections to me adding
an option to ping(8) so that it emitted a bell character on every
packet reciept.

Something like '-a': audible tone for pings.

I haven't been keeping current the last few months so I apologize if
anyone has already made the change. If there aren't any major
objections, if someone could tell me where to mail a patch (And the
format they'd prefer), I'll make one up against -current this weekend.

Cheers,
Bruce.
--
Packrat (BSc/BE;COSO;Wombat II Designer)
Nihil illegitemi carborvndvm.

From owner-freebsd-hackers  Mon Feb  3 21:02:14 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA18314
          for hackers-outgoing; Mon, 3 Feb 1997 21:02:14 -0800 (PST)
Received: from jason.garman.net (pm106-15.dialip.mich.net [192.195.231.217])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id VAA18290
          for <hackers@freebsd.org>; Mon, 3 Feb 1997 21:01:26 -0800 (PST)
Received: (qmail 279 invoked by uid 1000); 4 Feb 1997 05:01:19 -0000
Message-ID: <Mutt.19970204000118.garman@jason.garman.net>
Date: Tue, 4 Feb 1997 00:01:18 -0500
From: garman@jason.garman.net (Jason Garman)
To: helbig@BA-Stuttgart.De (Wolfgang Helbig)
Cc: nadav@cs.technion.ac.il (Nadav Eiron), hackers@freebsd.org
Subject: Re: CMD640b flaw workaround
References: <Pine.GSO.3.95-heb-2.07.970202182140.22764B-100000@csd> <199702021846.TAA03678@amadeus.informatik.ba-stuttgart.de>
X-Mailer: Mutt 0.58
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="tb47fdMN=vveGnh="
Reply-To: garman@phs.k12.ar.us
X-Phase-Of-Moon: The Moon is Waning Crescent (17% of Full)
X-Operating-System: FreeBSD/i386 2.1.5-RELEASE
In-Reply-To: <199702021846.TAA03678@amadeus.informatik.ba-stuttgart.de>; from Wolfgang Helbig on Feb 2, 1997 19:04:49 +0100
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


--tb47fdMN=vveGnh=

Wolfgang Helbig writes:
> Sorry, but the diff is against revision 1.122 of wd.c , whereas
> you have revision 1.81.4.2 in FreeBSD 2.1.6.1 . So the patch will not
> work. I tried to produce the diff from 1.122 to 1.81.4.2  and applying
> a patch with it to my version of wd.c but there were to many rejects.
> 
After some hacking, I've produced a patch that seems to work for me
(FreeBSD 2.1.5-RELEASE).  Attached are the patches (it looked like i had
to patch atapi.c so atapi_attach could return a value)

I don't know if this is the Right Way[tm] of doing this, or if my
modifications introduce bugs in the code, but it works for me (after a
whopping 5 minutes of testing)

Hopefully this helps those stuck with these cmd chips on 2.1.x machines...

Enjoy,
-- 
Jason Garman                             http://www.nesc.k12.ar.us/~garman/
Student, Eleanor Roosevelt High School                 garman@phs.k12.ar.us

--tb47fdMN=vveGnh=
Content-Disposition: attachment; filename="wd.c.diffs"

--- wd.old.c	Mon Dec  2 23:32:06 1996
+++ wd.c	Mon Feb  3 23:49:46 1997
@@ -190,6 +190,8 @@
 #define	RECAL		2	/* doing restore */
 #define	OPEN		3	/* done with open */
 
+#define PRIMARY		0
+
 /*
  * Disk geometry.  A small part of struct disklabel.
  * XXX disklabel.5 contains an old clone of disklabel.h.
@@ -277,6 +279,11 @@
 	wdprobe, wdattach, "wdc",
 };
 
+#ifdef CMD640
+static int wdcports[NWDC];
+static int atapictrlr;
+#endif
+
 /*
  * Probe for controller.
  */
@@ -296,6 +303,10 @@
 	du->dk_ctrlr = dvp->id_unit;
 	du->dk_port = dvp->id_iobase;
 
+#ifdef CMD640
+	wdcports[du->dk_ctrlr] = du->dk_port;
+#endif
+
 	wdc_registerdev(dvp);
 
 	/* check if we have registers that work */
@@ -415,6 +426,10 @@
 		du->dk_lunit = lunit;
 		du->dk_port = dvp->id_iobase;
 
+#ifdef CMD640
+		wdcports[du->dk_ctrlr] = du->dk_port;
+#endif
+
 		/*
 		 * Use the individual device flags or the controller
 		 * flags.
@@ -491,16 +506,26 @@
 			if (wddrives[lunit]->dk_ctrlr == dvp->id_unit &&
 			    wddrives[lunit]->dk_unit == unit)
 				goto next;
-		atapi_attach (dvp->id_unit, unit, dvp->id_iobase,
-			&kdc_wdc[dvp->id_unit]);
+		if (atapi_attach (dvp->id_unit, unit, dvp->id_iobase,
+			&kdc_wdc[dvp->id_unit]) == 1) {
+		/* 2.1.5's atapi_attach does not return a value */
+#ifdef CMD640
+			wdcports[unit] = dvp->id_iobase;
+			atapictrlr = dvp->id_unit;
+			printf ("wd: atapictrlr = %d\n", atapictrlr);
+#endif
+		}
 next:   }
 #endif
 	/*
 	 * Discard any interrupts generated by wdgetctlr().  wdflushirq()
 	 * doesn't work now because the ambient ipl is too high.
 	 */
+#ifdef CMD640
+	wdtab[PRIMARY].b_active = 2;
+#else
 	wdtab[dvp->id_unit].b_active = 2;
-
+#endif
 	return (1);
 }
 
@@ -576,7 +601,11 @@
 		du->dk_state = WANTOPEN;
 	}
 
+#ifdef CMD640
+	if (wdtab[PRIMARY].b_active == 0)
+#else
 	if (wdtab[du->dk_ctrlr].b_active == 0)
+#endif
 		wdstart(du->dk_ctrlr);	/* start controller */
 
 	if (du->dk_dkunit >= 0) {
@@ -638,13 +667,21 @@
 	dp->b_actf = bp->b_actf;
 	bp->b_actf = NULL;
 	/* link onto controller queue */
+#ifdef CMD640
+	if (wdtab[PRIMARY].b_actf == NULL) {
+		wdtab[PRIMARY].b_actf = bp;
+	} else {
+		*wdtab[PRIMARY].b_actb = bp;
+	}
+	wdtab[PRIMARY].b_actb = &bp->b_actf;
+#else
 	if (wdtab[ctrlr].b_actf == NULL) {
 		wdtab[ctrlr].b_actf = bp;
 	} else {
 		*wdtab[ctrlr].b_actb = bp;
 	}
 	wdtab[ctrlr].b_actb = &bp->b_actf;
-
+#endif
 	/* mark the drive unit as busy */
 	dp->b_active = 1;
 }
@@ -670,20 +707,40 @@
 	int	count;
 
 #ifdef ATAPI
+#ifdef CMD640
+	if (wdtab[PRIMARY].b_active == 2)
+		wdtab[PRIMARY].b_active = 0;
+	if (wdtab[PRIMARY].b_active)
+		return;
+#else
 	if (wdtab[ctrlr].b_active == 2)
 		wdtab[ctrlr].b_active = 0;
 	if (wdtab[ctrlr].b_active)
 		return;
 #endif
+#endif
+
 loop:
 	/* is there a drive for the controller to do a transfer with? */
+#ifdef CMD640
+	bp = wdtab[PRIMARY].b_actf;
+#else
 	bp = wdtab[ctrlr].b_actf;
+#endif
 	if (bp == NULL) {
 #ifdef ATAPI
+#ifdef CMD640
+		if (atapi_start (atapictrlr))
+#else
 		if (atapi_start (ctrlr))
+#endif
 			/* mark controller active in ATAPI mode */
+#ifdef CMD640
+			wdtab[PRIMARY].b_active = 3;
+#else
 			wdtab[ctrlr].b_active = 3;
 #endif
+#endif
 		return;
 	}
 
@@ -739,7 +796,11 @@
 				     blknum - ds_offset) + ds_offset;
 	}
 
+#ifdef CMD640
+	wdtab[PRIMARY].b_active = 1;
+#else
 	wdtab[ctrlr].b_active = 1;	/* mark controller active */
+#endif
 
 	/* if starting a multisector transfer, or doing single transfers */
 	if (du->dk_skip == 0 || (du->dk_flags & DKFL_SINGLE)) {
@@ -751,7 +812,11 @@
 		head = (blknum % secpercyl) / secpertrk;
 		sector = blknum % secpertrk;
 
+#ifdef CMD640
+		if (wdtab[PRIMARY].b_errcnt && (bp->b_flags & B_READ) == 0)
+#else
 		if (wdtab[ctrlr].b_errcnt && (bp->b_flags & B_READ) == 0)
+#endif
 			du->dk_bc += DEV_BSIZE;
 		count = howmany( du->dk_bc, DEV_BSIZE);
 
@@ -898,9 +963,15 @@
 	register struct	disk *du;
 	register struct buf *bp, *dp;
 
+#ifdef CMD640
+	if (wdtab[PRIMARY].b_active == 2)
+		return;
+	if (!wdtab[PRIMARY].b_active) {
+#else
 	if (wdtab[unit].b_active == 2)
 		return;		/* intr in wdflushirq() */
 	if (!wdtab[unit].b_active) {
+#endif
 #ifdef WDDEBUG
 		/*
 		 * These happen mostly because the power-mgt part of the
@@ -911,19 +982,29 @@
 #endif
 		return;
 	}
-#ifdef ATAPI
+#ifdef CMD640
+	if (wdtab[PRIMARY].b_active == 3) {
+#else
 	if (wdtab[unit].b_active == 3) {
+#endif
 		/* process an ATAPI interrupt */
 		if (atapi_intr (unit))
 			/* ATAPI op continues */
 			return;
 		/* controller is free, start new op */
+#ifdef CMD640
+		wdtab[PRIMARY].b_active = 0;
+#else
 		wdtab[unit].b_active = 0;
+#endif
 		wdstart (unit);
 		return;
 	}
-#endif
+#ifdef CMD640
+	bp = wdtab[PRIMARY].b_actf;
+#else
 	bp = wdtab[unit].b_actf;
+#endif
 	du = wddrives[dkunit(bp->b_dev)];
 	dp = &wdutab[du->dk_lunit];
 	du->dk_timeout = 0;
@@ -935,7 +1016,11 @@
 
 	/* is it not a transfer, but a control operation? */
 	if (du->dk_state < OPEN) {
+#ifdef CMD640
+		wdtab[PRIMARY].b_active = 0;
+#else
 		wdtab[unit].b_active = 0;
+#endif
 		switch (wdcontrol(bp)) {
 		case 0:
 			return;
@@ -977,8 +1062,13 @@
 			bp->b_error = EIO;
 			bp->b_flags |= B_ERROR;
 		} else if (du->dk_status & WDCS_ERR) {
+#ifdef CMD640
+			if (++wdtab[PRIMARY].b_errcnt < RETRIES) {
+				wdtab[PRIMARY].b_active = 0;
+#else
 			if (++wdtab[unit].b_errcnt < RETRIES) {
 				wdtab[unit].b_active = 0;
+#endif
 			} else {
 				wderror(bp, du, "hard error");
 				bp->b_error = EIO;
@@ -992,7 +1082,11 @@
 	 * If this was a successful read operation, fetch the data.
 	 */
 	if (((bp->b_flags & (B_READ | B_ERROR)) == B_READ)
+#ifdef CMD640
+	    && wdtab[PRIMARY].b_active) {
+#else
 	    && wdtab[unit].b_active) {
+#endif
 		int	chk, dummy, multisize;
 		multisize = chk = du->dk_currentiosize * DEV_BSIZE;
 		if( du->dk_bc < chk) {
@@ -1034,18 +1128,32 @@
 	}
 
 outt:
+#ifdef CMD640
+	if (wdtab[PRIMARY].b_active) {
+#else
 	if (wdtab[unit].b_active) {
+#endif
 		if ((bp->b_flags & B_ERROR) == 0) {
 			du->dk_skip += du->dk_currentiosize;/* add to successful sectors */
+#ifdef CMD640
+			if (wdtab[PRIMARY].b_errcnt)
+				wderror(bp, du, "soft error");
+			wdtab[PRIMARY].b_errcnt = 0;
+#else
 			if (wdtab[unit].b_errcnt)
 				wderror(bp, du, "soft error");
 			wdtab[unit].b_errcnt = 0;
+#endif
 
 			/* see if more to transfer */
 			if (du->dk_bc > 0 && (du->dk_flags & DKFL_ERROR) == 0) {
 				if( (du->dk_flags & DKFL_SINGLE) ||
 					((bp->b_flags & B_READ) == 0)) {
+#ifdef CMD640
+					wdtab[PRIMARY].b_active = 0;
+#else
 					wdtab[unit].b_active = 0;
+#endif
 					wdstart(unit);
 				} else {
 					du->dk_timeout = 1 + 3;
@@ -1056,7 +1164,11 @@
 				du->dk_skip = 0;
 				du->dk_flags &= ~DKFL_ERROR;
 				du->dk_flags |= DKFL_SINGLE;
+#ifdef CMD640
+				wdtab[PRIMARY].b_active = 0;
+#else
 				wdtab[unit].b_active = 0;
+#endif
 				wdstart(unit);
 				return;	/* redo xfer sector by sector */
 			}
@@ -1065,8 +1177,13 @@
 done: ;
 		/* done with this transfer, with or without error */
 		du->dk_flags &= ~DKFL_SINGLE;
+#ifdef CMD640
+		wdtab[PRIMARY].b_actf = bp->b_actf;
+		wdtab[PRIMARY].b_errcnt = 0;
+#else
 		wdtab[unit].b_actf = bp->b_actf;
 		wdtab[unit].b_errcnt = 0;
+#endif
 		bp->b_resid = bp->b_bcount - du->dk_skip * DEV_BSIZE;
 		dp->b_active = 0;
 		dp->b_errcnt = 0;
@@ -1079,15 +1196,23 @@
 	}
 
 	/* controller idle */
+#ifdef CMD640
+	wdtab[PRIMARY].b_active = 0;
+#else
 	wdtab[unit].b_active = 0;
+#endif
 
 	/* anything more on drive queue? */
 	wdustart(du);
 	/* anything more for controller to do? */
 #ifndef ATAPI
 	/* This is not valid in ATAPI mode. */
+#ifdef CMD640
+	if (wdtab[PRIMARY].b_actf)
+#else
 	if (wdtab[unit].b_actf)
 #endif
+#endif
 		wdstart(unit);
 }
 
@@ -1112,8 +1237,13 @@
 		return (ENXIO);
 
 	/* Finish flushing IRQs left over from wdattach(). */
+#ifdef CMD640
+	if (wdtab[PRIMARY].b_active == 2)
+		wdtab[PRIMARY].b_active = 0;
+#else
 	if (wdtab[du->dk_ctrlr].b_active == 2)
 		wdtab[du->dk_ctrlr].b_active = 0;
+#endif
 
 	du->dk_flags &= ~DKFL_BADSCAN;
 
@@ -1285,7 +1415,11 @@
 	switch (du->dk_state) {
 	case WANTOPEN:
 tryagainrecal:
+#ifdef CMD640
+		wdtab[PRIMARY].b_active = 1;
+#else
 		wdtab[ctrlr].b_active = 1;
+#endif
 		if (wdcommand(du, 0, 0, 0, 0, WDCC_RESTORE | WD_STEP) != 0) {
 			wderror(bp, du, "wdcontrol: wdcommand failed");
 			goto maybe_retry;
@@ -1299,13 +1433,21 @@
 			if (du->dk_status & WDCS_ERR)
 				wdunwedge(du);
 			du->dk_state = WANTOPEN;
+#ifdef CMD640
+			if (++wdtab[PRIMARY].b_errcnt < RETRIES)
+#else
 			if (++wdtab[ctrlr].b_errcnt < RETRIES)
+#endif
 				goto tryagainrecal;
 			bp->b_error = ENXIO;	/* XXX needs translation */
 			bp->b_flags |= B_ERROR;
 			return (2);
 		}
+#ifdef CMD640
+		wdtab[PRIMARY].b_errcnt = 0;
+#else
 		wdtab[ctrlr].b_errcnt = 0;
+#endif
 		du->dk_state = OPEN;
 		/*
 		 * The rest of the initialization can be done by normal
@@ -1389,7 +1531,11 @@
 		error = 1;
 	}
 	if (error) {
+#ifdef CMD640
+		wdtab[PRIMARY].b_errcnt += RETRIES;
+#else
 		wdtab[du->dk_ctrlr].b_errcnt += RETRIES;
+#endif
 		return (1);
 	}
 	if (wdcommand(du, du->dk_dd.d_ncylinders, du->dk_dd.d_ntracks - 1, 0,
@@ -1766,6 +1912,8 @@
 
 #if 0
 	/* Mark controller active for if we panic during the dump. */
+	/* does it really matter if we delete this chunk to fix the CMD
+	   bug?  The dump should be the only thing happening anyhow... */
 	wdtab[du->dk_ctrlr].b_active = 1;
 #endif
 	wddoingadump = 1;
@@ -1914,10 +2062,17 @@
 static void
 wdflushirq(struct disk *du, int old_ipl)
 {
+#ifdef CMD640
+	wdtab[PRIMARY].b_active = 2;
+	splx (old_ipl);
+	(void) splbio();
+	wdtab[PRIMARY].b_active = 0;
+#else
 	wdtab[du->dk_ctrlr].b_active = 2;
 	splx(old_ipl);
 	(void)splbio();
 	wdtab[du->dk_ctrlr].b_active = 0;
+#endif
 }
 
 /*
@@ -1956,8 +2111,14 @@
 static void
 wdsleep(int ctrlr, char *wmesg)
 {
+/* is the splbio/splx pair needed from the 2.2 sources? */
+#ifdef CMD640
+	while (wdtab[PRIMARY].b_active)
+		tsleep((caddr_t)&wdtab[PRIMARY].b_active, PZERO - 1, wmesg, 1);
+#else
 	while (wdtab[ctrlr].b_active)
 		tsleep((caddr_t)&wdtab[ctrlr].b_active, PZERO - 1, wmesg, 1);
+#endif
 }
 
 static void
@@ -2032,6 +2193,36 @@
 static int min_retries[NWDC];
 #endif
 
+#ifdef CMD640
+int   
+cmd640_wait(int port)
+{
+       int port2;
+       int timeout;
+       u_char status;
+
+       return (0);
+       if (NWDC == 1)
+               return (0);
+
+       if (wdcports[0] == port) 
+               port2 = wdcports[1];
+       else
+               port2 = wdcports[0];
+       if (port2 == 0)
+               return (0);
+       for (timeout = TIMEOUT; timeout > 0; timeout--) {
+               status = inb(port2 + wd_status);
+               if (!(status & WDCS_BUSY))
+                       return (0);
+               DELAY (1000);
+               printf("called by port %x\n",port);
+       }
+       printf("wd: timeout on port %x\n", port2);
+       return (-1);
+}
+#endif
+
 static int
 wdwait(struct disk *du, u_char bits_wanted, int timeout)
 {
@@ -2042,6 +2233,11 @@
 
 	wdc = du->dk_port;
 	timeout += POLLING;
+
+#ifdef CMD640
+	if (cmd640_wait (wdc) != 0)
+		return (-1);
+#endif
 
 /*
  * This delay is really too long, but does not impact the performance

--tb47fdMN=vveGnh=
Content-Disposition: attachment; filename="atapi.h.diffs"

--- atapi.old.h	Fri Sep 29 20:11:16 1995
+++ atapi.h	Mon Feb  3 23:50:29 1997
@@ -193,7 +193,7 @@
 #ifdef KERNEL
 struct atapi;
 struct kern_devconf;
-void atapi_attach (int ctlr, int unit, int port, struct kern_devconf*);
+int atapi_attach (int ctlr, int unit, int port, struct kern_devconf*);
 int atapi_start (int ctrlr);
 int atapi_intr (int ctrlr);
 void atapi_debug (struct atapi *ata, int on);

--tb47fdMN=vveGnh=
Content-Disposition: attachment; filename="atapi.c.diffs"

--- atapi.old.c	Mon Feb  3 23:48:29 1997
+++ atapi.c	Mon Feb  3 23:51:30 1997
@@ -168,7 +168,7 @@
 
 extern int wdstart (int ctrlr);
 
-void atapi_attach (int ctlr, int unit, int port, struct kern_devconf *parent)
+int atapi_attach (int ctlr, int unit, int port, struct kern_devconf *parent)
 {
 	struct atapi *ata = atapitab + ctlr;
 	struct atapi_params *ap;
@@ -179,7 +179,7 @@
 	print (("atapi%d.%d at 0x%x: attach called\n", ctlr, unit, port));
 	ap = atapi_probe (port, unit);
 	if (! ap)
-		return;
+		return 0;
 
 	bcopy (ap->model, buf, sizeof(buf)-1);
 	buf[sizeof(buf)-1] = 0;
@@ -245,7 +245,7 @@
 		printf ("wdc%d: unit %d: unknown ATAPI protocol=%d\n",
 			ctlr, unit, ap->proto);
 		free (ap, M_TEMP);
-		return;
+		return 0;
 	}
 	switch (ap->devtype) {
 	default:
@@ -265,7 +265,7 @@
 				break;
 		}
 		/* Device attached successfully. */
-		return;
+		return 1;
 #else
 		printf ("wdc%d: ATAPI CD-ROMs not configured\n", ctlr);
 		break;
@@ -289,6 +289,7 @@
 	}
 	/* Attach failed. */
 	free (ap, M_TEMP);
+	return 0;
 }
 
 static void bswap (char *buf, int len)

--tb47fdMN=vveGnh=--

From owner-freebsd-hackers  Mon Feb  3 21:59:47 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA20459
          for hackers-outgoing; Mon, 3 Feb 1997 21:59:47 -0800 (PST)
Received: from paris.CS.Berkeley.EDU (paris.CS.Berkeley.EDU [128.32.34.47])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA20451
          for <hackers@freebsd.org>; Mon, 3 Feb 1997 21:59:43 -0800 (PST)
Received: from paris.CS.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by paris.CS.Berkeley.EDU (8.8.3/8.8.2) with ESMTP id VAA08584 for <hackers@freebsd.org>; Mon, 3 Feb 1997 21:59:40 -0800 (PST)
From: Josh MacDonald <jmacd@CS.Berkeley.EDU>
Message-Id: <199702040559.VAA08584@paris.CS.Berkeley.EDU>
To: hackers@freebsd.org
Subject: Re: g++, STL and -frepo on FreeBSD-2.2-Beta 
In-reply-to: Your message of "Fri, 31 Jan 1997 18:14:33."
             <199702010114.SAA03677@phaeton.artisoft.com> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8577.855035973.1@paris.CS.Berkeley.EDU>
Date: Mon, 03 Feb 1997 21:59:35 -0800
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

[code deleted]

On Fri, 31 Jan 1997, Terry Lambert wrote:

> It can't call the constructor, used implicitly in the list1 auto
> declarator.  It can't call the destructor, called implicily when the
> list1 auto storage goes out of scope of main().  It can't call the
> push_back member function, which is explicitly called.
> 
> 
> Clearly, the template class definition
> 
> 	template <class Type>
> 	class list ... {
> 		...
> 	};
> 
> is not in scope.  The header files you have included are apparently
> not sufficient.
> 
> Perhaps you meant "List" instead of "list"???

Clearly, you have no idea what you're talking about.  You should be a 
bit more careful with your use of "clearly", it makes me wonder how
much of the rest of your mail to this list (which I rarely understand)
is correct.

-josh

From owner-freebsd-hackers  Tue Feb  4 00:25:34 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id AAA29860
          for hackers-outgoing; Tue, 4 Feb 1997 00:25:34 -0800 (PST)
Received: from korin.warman.org.pl (korin.warman.org.pl [148.81.160.10])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA29843
          for <freebsd-hackers@freebsd.org>; Tue, 4 Feb 1997 00:25:23 -0800 (PST)
Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.3/8.7.3) with SMTP id JAA11265; Tue, 4 Feb 1997 09:23:42 +0100 (MET)
Date: Tue, 4 Feb 1997 09:23:41 +0100 (MET)
From: Andrzej Bialecki <abial@korin.warman.org.pl>
To: Chris Coleman <chris@bb.cc.wa.us>
cc: "Daniel O'Callaghan" <danny@panda.hilink.com.au>,
        Troy Curtiss <troyc@sandy.merix.com>, freebsd-hackers@freebsd.org
Subject: Re: Two-way pipe possible without C/perl?
In-Reply-To: <Pine.NEB.3.94.970203170016.1262A-100000@aries.bb.cc.wa.us>
Message-ID: <Pine.NEB.3.95.970204090727.11238A-100000@korin.warman.org.pl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Mon, 3 Feb 1997, Chris Coleman wrote:

> I like this, alot.  But how are you monitoring these system so FreeBSD
> knows when to send you a message?
> 
> I have a pager and am very interested in this.
> 

Hello!
I currently use the following setup - maybe it's a little simplistic, but
it works.
(Assuming that your paging company allows you to send messages via modem.)

* I wrote several scripts on the machines I want to monitor. They check
all the parameters I'm interested in, and come out with a one-line
summary. They give the total status there as well (i.e "ok" || "FIRE!!!").
I run it in crontab as often as needed.
* Then there is the main script on my managing machine, which collects
output from the scripts (I use `ssh -l name machine 'do_the_job.sh'`,
just to be sure that sensitive data go to me only). It is also run in
crontab, let's say every half an hour (some people say here: your mileage
may vary :-). If it detects something unusual, it sends me a message.
* How? I'm using "expect". It took me one day to grasp the basics, and
another one to cut&paste one of the example scripts to do what I want.
Basically, I telnet to my Xylogics Annex and use one of its modems to dial
out & connect to the paging company. Then I send a message and voila! It's
Sunday 3:00am and your whole family is listening to wonderfully
excruciating
"beep, beep, beep"...

Hope this helps a bit.

Andy

+-------------------------------------------------------------------------+
Andrzej Bialecki <abial@warman.org.pl>    _)    _)   _)_)   _)_)_) _)  _)
---------------------------------------   _)_)  _) _)    _) _)_)   _)_)
Research and Academic Network in Poland   _)  _)_) _)_)_)_)     _) _) _)
Bartycka 18, 00-716 Warsaw, Poland        _)    _) _)    _) _)_)_) _)  _)
+-------------------------------------------------------------------------+



From owner-freebsd-hackers  Tue Feb  4 01:39:24 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id BAA05655
          for hackers-outgoing; Tue, 4 Feb 1997 01:39:24 -0800 (PST)
Received: from nic.follonett.no (nic.follonett.no [194.198.43.10])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA05649
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 01:39:20 -0800 (PST)
Received: (from uucp@localhost) by nic.follonett.no (8.8.5/8.8.3) with UUCP id KAA10138; Tue, 4 Feb 1997 10:36:20 +0100 (MET)
Received: from oo7 (oo7.dimaga.com [192.0.0.65]) by dimaga.com (8.7.5/8.7.2) with SMTP id KAA10537; Tue, 4 Feb 1997 10:37:31 +0100 (MET)
Message-Id: <3.0.32.19970204103732.00ac3a30@dimaga.com>
X-Sender: eivind@dimaga.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Tue, 04 Feb 1997 10:37:33 +0100
To: Charles Mott <cmott@srv.net>
From: Eivind Eklund <eivind@dimaga.com>
Subject: Re: Single socket version of natd 
Cc: Brian Somers <brian@awfulhak.demon.co.uk>,
        Ari Suutari <ari.suutari@ps.carel.fi>, hackers@freebsd.org,
        brian@utell.co.uk
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

At 07:36 PM 2/3/97 -0700, Charles Mott wrote:
>Eivind has these updates and has integrated them into his codebase, 
>which he is continuing to work on.  He writes that he has changed some of 
>the compile options (ALIAS_ALLOW_INCOMING, ALIAS_SAME_PORTS, etc.) to ppp 
>commands.  

Not some - all.  User level programs really shouldn't require recompile, IMHO.
At least, no editing of the Makefiles.

>> BTW, Charles/Elvind - what's the score with the code that attempts to
"keep"
>> the source port ?  This idea is growing on me ;)  I've tested 1.9 (http ref
>> from www.srv.net/~cmott to Elvind's page) and it seems good.  It's gettin'
>> *real* close to 2.2-GAMMA now - it would be *really* nice to have this code
>> make it to 2.2 :-O
>
>It has been working for a week or two now.

And all the other really nescessary code-changes are done - everything is
changed to ANSI style, and integrated with PPP from -current patched with
#ifdef's to make it compile and work on all versions from 2.1.0 to
-current,  with an extra command 'alias' that set alias options.

The only thing left before it could be integrated into 2.2 is documentation
(the two different README.alias files should be integrated, and the new PPP
commands should be documented) and testing.  If anybody want a source
snapshot or want to do the documentation, just yell.  If not, I'll try to
have everything ready sometime on thursday.

I really would like to lower the complexity of alias_db.c (it seems to have
a lot of duplicated code because it doesn't defer decisions long enough) -
but that can wait.



Eivind Eklund / perhaps@yes.no / http://maybe.yes.no/perhaps/

From owner-freebsd-hackers  Tue Feb  4 02:04:12 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA06626
          for hackers-outgoing; Tue, 4 Feb 1997 02:04:12 -0800 (PST)
Received: from logues.rhn.orst.edu (logues.RHN.ORST.EDU [128.193.139.116])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA06576;
          Tue, 4 Feb 1997 02:03:52 -0800 (PST)
Received: from logues.rhn.orst.edu (localhost [127.0.0.1])
          by logues.rhn.orst.edu (8.8.4/8.8.4) with SMTP
	  id CAA04584; Tue, 4 Feb 1997 02:03:44 -0800 (PST)
Message-ID: <32F7097D.41C67EA6@engr.orst.edu>
Date: Tue, 04 Feb 1997 02:03:41 -0800
From: Steve Logue <logue@engr.orst.edu>
X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2-970201-GAMMA0 i386)
MIME-Version: 1.0
Newsgroups: comp.protocols.time.ntp,comp.unix.bsd.freebsd.misc
To: Harlan Stenn <stenn@whimsy.udel.edu>
CC: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org,
        freebsd-stable@freebsd.org
Subject: xntp3-5.89.2 & FreeBSD 2.2-GAMMA won't compile
References: <o4pvyj3gge.fsf@whimsy.udel.edu>
Content-Type: multipart/mixed; boundary="------------446B9B3D2781E494167EB0E7"
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

This is a multi-part message in MIME format.

--------------446B9B3D2781E494167EB0E7
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

There has been a long stream of problems with XNTPD, and FreeBSD.  This
may have been going on longer than I am aware however, I have checked
from 3-5.88.0 - 3-5.89.2, and they all give me the same problem.  It
appears that on my system, there are two symbols that are undefined in
the file ntp_loopfilter.c, lines 330 and 335: STA_FLL and STA_FREQHOLD. 
Near as I can tell, these things are supposed to be defined in my
system's timex.h file?  From my understanding, XNTPD needs a framework
in the kernel to work correct?  How do I go about updating my kernel
sources with the latest XNTPD kernel stuff.  Or better yet, get it fixed
with the FreeBSD project?

There is a timex.h file that comes with the XNTP distribution, and if I
edit ntp_loopfilter.c to include that instead, everything builds fine,
and xntpd runs fine, but when I try to use ntpq with the pe command I
get nothing.  My "make" output is attached.

Thank You,
Steve Logue

--------------446B9B3D2781E494167EB0E7
Content-Type: text/plain; charset=us-ascii; name="make.out"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; filename="make.out"

make all-recursive
for subdir in include  libntp	 libparse	 authstuff	 ntpdate	 ntpq	 ntptrace	 parseutil	 xntpd	 xntpdc	 adjtimed	 clockstuff	 kernel	 util; do		 target=`echo all-recursive | sed s/-recursive//`;  echo making $target in $subdir;	 (cd $subdir && make $target)	 || case " " in *k*) fail=yes;; *) exit 1;; esac;  done && test -z "$fail"
making all in include
making all in libntp
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe adjtime.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe atoint.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe atolfp.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe atouint.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe auth12crypt.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe authdecrypt.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe authdes.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe authencrypt.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe authkeys.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe authparity.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe authreadkeys.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe authusekey.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe buftvtots.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe caljulian.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe calleapwhen.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe caltontp.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe calyearstart.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe clocktime.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe dofptoa.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe dolfptoa.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe emalloc.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe fptoa.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe fptoms.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe getopt.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe hextoint.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe hextolfp.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe humandate.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe inttoa.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe lib_strbuf.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe memmove.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe mfptoa.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe mfptoms.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe modetoa.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe mstolfp.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe msutotsf.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe numtoa.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe refnumtoa.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe numtohost.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe octtoint.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe prettydate.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe ranny.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe tsftomsu.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe tstotv.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe tvtoa.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe tvtots.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe uglydate.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe uinttoa.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe utvtoa.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe machines.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe clocktypes.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe md5.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe a_md5encrypt.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe a_md5decrypt.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe a_md512crypt.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe decodenetnum.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe systime.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe msyslog.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe syssignal.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe findconfig.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe netof.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe statestr.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe mexit.c
rm -f libntp.a
ar cru libntp.a adjtime.o atoint.o atolfp.o atouint.o auth12crypt.o  authdecrypt.o authdes.o authencrypt.o authkeys.o authparity.o  authreadkeys.o authusekey.o buftvtots.o caljulian.o calleapwhen.o  caltontp.o calyearstart.o clocktime.o dofptoa.o dolfptoa.o emalloc.o  fptoa.o fptoms.o getopt.o hextoint.o hextolfp.o humandate.o inttoa.o  lib_strbuf.o memmove.o mfptoa.o mfptoms.o modetoa.o mstolfp.o  msutotsf.o numtoa.o refnumtoa.o numtohost.o octtoint.o prettydate.o  ranny.o tsftomsu.o tstotv.o tvtoa.o tvtots.o uglydate.o uinttoa.o  utvtoa.o machines.o clocktypes.o md5.o a_md5encrypt.o a_md5decrypt.o  a_md512crypt.o decodenetnum.o systime.o msyslog.o syssignal.o  findconfig.o netof.o statestr.o mexit.o 
ranlib libntp.a
making all in libparse
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../kernel  -g -O2 -Wall -pipe parse_conf.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../kernel  -g -O2 -Wall -pipe clk_meinberg.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../kernel  -g -O2 -Wall -pipe clk_schmid.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../kernel  -g -O2 -Wall -pipe parse.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../kernel  -g -O2 -Wall -pipe clk_rawdcf.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../kernel  -g -O2 -Wall -pipe clk_trimtsip.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../kernel  -g -O2 -Wall -pipe clk_dcf7000.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../kernel  -g -O2 -Wall -pipe clk_trimtaip.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../kernel  -g -O2 -Wall -pipe clk_rcc8000.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../kernel  -g -O2 -Wall -pipe clk_hopf6021.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../kernel  -g -O2 -Wall -pipe clk_computime.c
rm -f libparse.a
ar cru libparse.a parse_conf.o clk_meinberg.o clk_schmid.o parse.o  clk_rawdcf.o clk_trimtsip.o clk_dcf7000.o clk_trimtaip.o clk_rcc8000.o  clk_hopf6021.o clk_computime.o 
ranlib libparse.a
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../kernel  -g -O2 -Wall -pipe kparse_conf.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../kernel  -g -O2 -Wall -pipe kparse.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../kernel  -g -O2 -Wall -pipe kclk_rawdcf.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../kernel  -g -O2 -Wall -pipe kclk_trimtsip.c
rm -f libparse_kernel.a
ar cru libparse_kernel.a kparse_conf.o clk_meinberg.o clk_schmid.o  kparse.o kclk_rawdcf.o kclk_trimtsip.o clk_dcf7000.o clk_trimtaip.o  clk_rcc8000.o clk_hopf6021.o clk_computime.o 
ranlib libparse_kernel.a
making all in authstuff
making all in ntpdate
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe ntpdate.c
../scripts/mkversion ntpdate 5.89.2
Version ntpdate 5.89.2 Tue Feb  4 01:00:11 PST 1997 (1)
gcc -g -O2 -Wall -pipe -c version.c
gcc  -o ntpdate ntpdate.o version.o ../libntp/libntp.a -lkvm
making all in ntpq
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe ntpq.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe ntpq_ops.c
../scripts/mkversion ntpq 5.89.2
Version ntpq 5.89.2 Tue Feb  4 01:00:22 PST 1997 (1)
gcc -g -O2 -Wall -pipe -c version.c
gcc  -o ntpq ntpq.o ntpq_ops.o version.o ../libntp/libntp.a -lkvm
making all in ntptrace
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe ntptrace.c
../scripts/mkversion ntptrace 5.89.2
Version ntptrace 5.89.2 Tue Feb  4 01:00:26 PST 1997 (1)
gcc -g -O2 -Wall -pipe -c version.c
gcc  -o ntptrace ntptrace.o version.o ../libntp/libntp.a -lkvm
making all in parseutil
making all in xntpd
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe map_vme.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe ntp_config.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe ntp_control.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe ntp_io.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe ntp_leap.c
gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -I../include  -g -O2 -Wall -pipe ntp_loopfilter.c
ntp_loopfilter.c: In function `local_clock':
ntp_loopfilter.c:330: `STA_FLL' undeclared (first use this function)
ntp_loopfilter.c:330: (Each undeclared identifier is reported only once
ntp_loopfilter.c:330: for each function it appears in.)
ntp_loopfilter.c:330: `STA_FREQHOLD' undeclared (first use this function)
*** Error code 1

Stop.
*** Error code 1

Stop.
*** Error code 1

Stop.

--------------446B9B3D2781E494167EB0E7--


From owner-freebsd-hackers  Tue Feb  4 02:10:39 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA06879
          for hackers-outgoing; Tue, 4 Feb 1997 02:10:39 -0800 (PST)
Received: from mail13.digital.com (mail13.digital.com [192.208.46.30])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA06874
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 02:10:32 -0800 (PST)
From: garyj@frt.dec.com
Received: from cssmuc.frt.dec.com by mail13.digital.com (8.7.5/UNX 1.5/1.0/WV)
	id FAA15501; Tue, 4 Feb 1997 05:04:21 -0500 (EST)
Received: from localhost by cssmuc.frt.dec.com; (5.65v3.2/1.1.8.2/14Nov95-0232PM)
	id AA23035; Tue, 4 Feb 1997 11:04:16 +0100
Message-Id: <9702041004.AA23035@cssmuc.frt.dec.com>
X-Mailer: exmh version 1.6.4 10/10/95
To: packrat@iinet.net.au
Cc: hackers@freebsd.org
In-Reply-To: Message from Bruce Murphy <packrat@iinet.net.au>  of Tue, 04 Feb 
 97 12:42:59 +0800.
Reply-To: gjennejohn@frt.dec.com
Subject: Re: ping(8) 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 04 Feb 97 11:04:16 +0100
X-Mts: smtp
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


packrat@iinet.net.au writes:
> Having just had to edit the ping binary by hand (for the nth time but
> I never keep them around) so that I could use it to diagnose a remote
> problem. (well actually some idiot walking into the room and pulling
> the terminator off my test run of thinnet and staring at it) I thought
> ask the list whether anyone had any religious objections to me adding
> an option to ping(8) so that it emitted a bell character on every
> packet reciept.
> 
> Something like '-a': audible tone for pings.
> 

seems resaonable to me. Why not '-b' for "bell" ? Seems more
intuitive somwhow.

---
Gary Jennejohn				(work) gjennejohn@frt.dec.com
					(home) Gary.Jennejohn@munich.netsurf.de
					(play) gj@freebsd.org



From owner-freebsd-hackers  Tue Feb  4 02:10:51 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA06897
          for hackers-outgoing; Tue, 4 Feb 1997 02:10:51 -0800 (PST)
Received: from pdx1.world.net (pdx1.world.net [192.243.32.18])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA06892
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 02:10:47 -0800 (PST)
From: proff@suburbia.net
Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id CAA23690 for <hackers@freebsd.org>; Tue, 4 Feb 1997 02:12:10 -0800 (PST)
Received: (qmail 12483 invoked by uid 110); 4 Feb 1997 10:10:20 -0000
Message-ID: <19970204101020.12479.qmail@suburbia.net>
Subject: linux net killer or no idea? (fwd)
To: hackers@freebsd.org
Date: Tue, 4 Feb 1997 21:10:20 +1100 (EST)
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>From richard@a42.deep-thought.org Mon Feb 03 23:36:52 1997
Return-Path: <richard@a42.deep-thought.org>
Delivered-To: proff@suburbia.net
Received: (qmail 24578 invoked from network); 3 Feb 1997 23:36:51 -0000
Received: from a42.deep-thought.org (203.4.184.227)
  by suburbia.net with SMTP; 3 Feb 1997 23:36:51 -0000
Received: from a42.deep-thought.org ([127.0.0.1]) by a42.deep-thought.org
  with esmtp id m0vrXwh-0024w0C
	(Debian Smail-3.2 1996-Jul-4 #2); Tue, 4 Feb 1997 10:37:07 +1100 (EST)
Message-Id: <m0vrXwh-0024w0C@a42.deep-thought.org>
X-Mailer: exmh version 1.6.9 8/22/96
To: proff@suburbia.net
Subject: linux net killer or no idea?
Date: Tue, 04 Feb 1997 10:37:07 +1100
From: Richard Jones <richard@a42.deep-thought.org>


------- Forwarded Message

Return-Path: owner-linux-net-outgoing@vger.rutgers.edu
Return-Path: <owner-linux-net-outgoing@vger.rutgers.edu>
Received: from suburbia.net ([203.4.184.1]) by a42.deep-thought.org
	 with smtp id m0vrXBE-0024w0a
	(Debian Smail-3.2 1996-Jul-4 #2); Tue, 4 Feb 1997 09:48:04 +1100 (EST)
Received: (qmail 3224 invoked from network); 3 Feb 1997 21:47:35 -0000
Received: from nic.funet.fi (128.214.248.6)
  by suburbia.net with SMTP; 3 Feb 1997 21:47:35 -0000
Received: from vger.rutgers.edu ([128.6.190.2]) by nic.funet.fi with ESMTP id 
<55330-6926>; Mon, 3 Feb 1997 18:50:20 +0200
Received: by vger.rutgers.edu id <214100-245>; Mon, 3 Feb 1997 11:35:54 -0500
To:	linux-net@vger.rutgers.edu
Cc:	dash@linpro.no
Subject: The file that kills linux tcp
From:	Arnt Gulbrandsen <agulbra@troll.no>
Date:	03 Feb 1997 17:37:24 +0100
Message-ID: <m3ohe13kxn.fsf@lupinella.troll.no>
Lines: 43
X-Mailer: Gnus v5.2.25/XEmacs 19.14
Sender: owner-linux-net@vger.rutgers.edu
Precedence: bulk

This is the weirdest problem I've ever, ever seen.  Or so it feels
like.

I've just seen machines running linux/2.0.27, linux/2.1.24 and
freebsd/3.0-current freeze after downloading 144540 bytes of this
file:

	ftp://ftp.troll.no/contrib/xppp1B-x86-ELF.tar.gz

Many clients can download this file just fine, many others can not.
Those who can't all freeze after exactly 144540 bytes.  A file of the
same size but with different contents works.  The same file with a
different name does not work.  The same file recompressed (zcat | gzip
- -9) to be 600 bytes smaller can be downloaded by everyone as far as I
can test.  The same file recompressed (-5) to be 2100 bytes larger
too.

The FTP daemon is troll-ftpd 1.20 running on linux 2.0.26 and then on
2.0.28.  The same file _can_ be downloaded from the same version of
troll-ftpd running on a different linux box, which runs 2.0.27.  There
are no tcp-related changes between .27 and .28, as far as I can see.

A huge tcpdump packet trace showing first a successful transfer of a
384604-byte file, then the one which freezes is available at

	ftp://ftp.troll.no/tmp/thud

The two transfers look much the same to me, except that there appears
to be a single packet loss while the window is wide-open, and the
connection never recovers if this crucial file is being transferred.

I don't know which of several netstat lines -t correspond to the
packet trace.  The most likely one shows a send queue of 43880 bytes,
the others are similar.

I don't know whether the file, the ftpd or the packet trace helps.
Should anyone feel like tracing something so weird and need other
data, or access to the box, do write.

(Please cc any replies to me - I don't read linux-net right now,
and probably won't for another two weeks or so.)

- --Arnt

------- End of Forwarded Message





From owner-freebsd-hackers  Tue Feb  4 02:11:38 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA06934
          for hackers-outgoing; Tue, 4 Feb 1997 02:11:38 -0800 (PST)
Received: from gw-nl1.philips.com (gw-nl1.philips.com [192.68.44.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA06925
          for <freebsd-hackers@freebsd.org>; Tue, 4 Feb 1997 02:11:31 -0800 (PST)
Received: (from nobody@localhost) 
	by gw-nl1.philips.com (8.6.10/8.6.10-0.994n-08Nov95) id LAA23539
	for <freebsd-hackers@freebsd.org>; Tue, 4 Feb 1997 11:11:23 +0100
Received: from unknown(130.139.36.3) by gw-nl1.philips.com via smap (V1.3+ESMTP) with ESMTP
	id sma023349; Tue Feb  4 11:10:42 1997
Received: from giga.lss.cp.philips.com (giga.lss.cp.philips.com [130.144.199.31]) 
	by smtprelay.nl.cis.philips.com (8.6.10/8.6.10-1.2.1m-970131) with SMTP id LAA25598
	for <freebsd-hackers@freebsd.org>; Tue, 4 Feb 1997 11:10:35 +0100
Received: by giga.lss.cp.philips.com (8.8.5/1.63)
    id LAA27440; Tue, 4 Feb 1997 11:10:35 +0100 (MET)
From: W.Belgers@nl.cis.philips.com (Walter Belgers)
Message-Id: <199702041010.LAA27440@giga.lss.cp.philips.com>
Subject: NIS/uids
To: freebsd-hackers@freebsd.org
Date: Tue, 4 Feb 1997 11:10:35 +0100 (MET)
Organisation: Origin IT Systems Management /Nederland B.V.
X-URL: http://giga.lss.cp.philips.com/cgi-bin/walter.cgi
X-Mailer: ELM [version 2.4ME+ PL19 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi,

I hope this is the right place to tell my story.

I run FreeBSD 2.1.5. On my system are a bunch of local users but I also
have users from the NIS database on another system (an HP). In my
password file the users are defined as follows:

+user::::::::/home/john:/usr/local/bin/tcsh

So I override the homedir and shell.

The problem now is that the security on my system has become dependant
on that of the NIS server. If I am root on the NIS server I can change
the uid of "user" into any user including root and make use of it on my
system. Even if you can only become root using su you can easily first
become a user in wheel and then root.

The obvious solution is to override the uid in the password file:

+user::1234:1234:::::/home/john:/usr/local/bin/tcsh

But now I have another problem... the userid is not mapped to the
username any more.

1) 

[~] root@giga> grep user /etc/master.passwd
+user::::::::/home/john:/usr/local/bin/tcsh
[~] root@giga> ypmatch user passwd
user:$1xOC/SMM4ss.:1234:1234:John Doe:/home/john:/usr/local/bin/tcsh
[~] root@giga> su - user
[~] user@giga> id
uid=1234(user) gid=1234 groups=1234

2) 

[~] root@giga> grep user /etc/master.passwd
+user::1234:1234:::::/home/walter:/usr/local/bin/tcsh
[~] root@giga> ypmatch user passwd
user:$1xOC/SMM4ss.:1234:1234:John Doe:/home/john:/usr/local/bin/tcsh
[~] root@giga> su - user
[~] user@giga> id
uid=1234 gid=1234 groups=1234

The fact that "user" now is only known as uid 1234 and not as user
"user" gives rise to a lot of problems.

Is this a bug or am I overlooking something?

Walter.
-- 
Ir. W.H.B. Belgers, Internet Security Specialist        phone: +31 40 2782753
Origin IT Syst.Man. /Nederland bv, Bldg VN-513   email:   fax: +31 40 2784697
P.O. Box 218, 5600 MD Eindhoven, Netherlands     W.Belgers@nl.cis.philips.com
non-business-email: walter@giga.nl   -web: http://www.IAEhv.nl/users/gigawalt

From owner-freebsd-hackers  Tue Feb  4 02:35:44 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA08087
          for hackers-outgoing; Tue, 4 Feb 1997 02:35:44 -0800 (PST)
Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA08043;
          Tue, 4 Feb 1997 02:35:27 -0800 (PST)
Received: (from jhay@localhost)
	by zibbi.mikom.csir.co.za (8.8.5/8.8.5) id MAA13094;
	Tue, 4 Feb 1997 12:34:18 +0200 (SAT)
From: John Hay <jhay@zibbi.mikom.csir.co.za>
Message-Id: <199702041034.MAA13094@zibbi.mikom.csir.co.za>
Subject: Re: xntp3-5.89.2 & FreeBSD 2.2-GAMMA won't compile
In-Reply-To: <32F7097D.41C67EA6@engr.orst.edu> from Steve Logue at "Feb 4, 97 02:03:41 am"
To: logue@engr.orst.edu (Steve Logue)
Date: Tue, 4 Feb 1997 12:34:18 +0200 (SAT)
Cc: stenn@whimsy.udel.edu, freebsd-hackers@freebsd.org,
        freebsd-questions@freebsd.org, freebsd-stable@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL24 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> There has been a long stream of problems with XNTPD, and FreeBSD.  This
> may have been going on longer than I am aware however, I have checked
> from 3-5.88.0 - 3-5.89.2, and they all give me the same problem.  It
> appears that on my system, there are two symbols that are undefined in
> the file ntp_loopfilter.c, lines 330 and 335: STA_FLL and STA_FREQHOLD. 
> Near as I can tell, these things are supposed to be defined in my
> system's timex.h file?  From my understanding, XNTPD needs a framework
> in the kernel to work correct?  How do I go about updating my kernel
> sources with the latest XNTPD kernel stuff.  Or better yet, get it fixed
> with the FreeBSD project?
> 
> There is a timex.h file that comes with the XNTP distribution, and if I
> edit ntp_loopfilter.c to include that instead, everything builds fine,
> and xntpd runs fine, but when I try to use ntpq with the pe command I
> get nothing.  My "make" output is attached.
> 

I have fixed it in FreeBSD-current, but weren't sure if it should go into
2.2. Any opinions anyone? It has been in -current from December 31 and
nobody has complained yet. Three files are effected sys/sys/timex.h,
sys/kern/kern_ntptime.c and sys/kern/kern_clock.c.

If somebody from the 2.2 release team give the go-ahead I would be
happy to put it in 2.2.

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

From owner-freebsd-hackers  Tue Feb  4 02:58:08 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA09423
          for hackers-outgoing; Tue, 4 Feb 1997 02:58:08 -0800 (PST)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA09418
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 02:58:05 -0800 (PST)
Received: from current1.whistle.com (current1.whistle.com [207.76.205.22])
          by alpo.whistle.com (8.8.5/8.8.4) with SMTP
	  id CAA00349; Tue, 4 Feb 1997 02:51:49 -0800 (PST)
Message-ID: <32F7144B.2781E494@whistle.com>
Date: Tue, 04 Feb 1997 02:49:47 -0800
From: Julian Elischer <julian@whistle.com>
Organization: Whistle Communications
X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386)
MIME-Version: 1.0
To: Eivind Eklund <eivind@dimaga.com>
CC: Charles Mott <cmott@srv.net>, Brian Somers <brian@awfulhak.demon.co.uk>,
        Ari Suutari <ari.suutari@ps.carel.fi>, hackers@freebsd.org,
        brian@utell.co.uk
Subject: Re: Single socket version of natd
References: <3.0.32.19970204103732.00ac3a30@dimaga.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Eivind Eklund wrote:
> 
> At 07:36 PM 2/3/97 -0700, Charles Mott wrote:
> >Eivind has these updates and has integrated them into his codebase,
> >which he is continuing to work on.  He writes that he has changed some of
> >the compile options (ALIAS_ALLOW_INCOMING, ALIAS_SAME_PORTS, etc.) to ppp
> >commands.
> 
So are we talking about ppp, or natd here?
teh subject line says natd..
but sounds like that's not the case...
(or has someone abstracted out the alias code to
a separate module that can be used for both?

julian

From owner-freebsd-hackers  Tue Feb  4 03:06:11 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id DAA09877
          for hackers-outgoing; Tue, 4 Feb 1997 03:06:11 -0800 (PST)
Received: from news.IAEhv.nl (root@news.IAEhv.nl [194.151.64.4])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id DAA09866
          for <freebsd-hackers@freebsd.org>; Tue, 4 Feb 1997 03:06:05 -0800 (PST)
Received: from truk.brandinnovators.com (uucp@localhost) 
          by news.IAEhv.nl (8.6.13/1.63) with IAEhv.nl; pid 18127
          on Tue, 4 Feb 1997 12:02:16 +0100; id MAA18127
          efrom: hans@truk.brandinnovators.com; eto: UNKNOWN
Received: by truk.brandinnovators.com (8.7.5/BI96070101) 
    for <> id LAA15551; Tue, 4 Feb 1997 11:28:16 +0100 (MET)
Message-Id: <199702041028.LAA15551@truk.brandinnovators.com>
From: hans@brandinnovators.com (Hans Zuidam)
Subject: Re: Two-way pipe possible without C/perl?
To: troyc@sandy.merix.com (Troy Curtiss)
Date: Tue, 4 Feb 1997 11:28:16 +0100 (MET)
Cc: freebsd-hackers@freebsd.org
In-Reply-To: <troyc-9701032246.AA0002700@sandy> from Troy Curtiss at "Feb 3, 97 02:46:56 pm"
X-Mailer: ELM [version 2.4ME+ PL22 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Troy Curtiss wrote:
>   I am looking for a very quick and dirty way to have my FreeBSD
> box page me when certain systems go down at work.

You may also care to take a look at "The Internet Message: Closing the book
with electronic mail", by Marshall Rose.  He shows some scripts that filter
e-mail and create a pager message from the subject and the body of the
message.

Regards,
				Hans

-- 
H. Zuidam                        E-Mail: hans@brandinnovators.com
Brand Innovators B.V.            P-Mail: P.O. Box 1377
de Pinckart 54                   5602 BJ Eindhoven, The Netherlands
5674 CC Nuenen                   Tel. +31 40 2631134, Fax. +31 40 2831138

From owner-freebsd-hackers  Tue Feb  4 03:14:37 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id DAA10435
          for hackers-outgoing; Tue, 4 Feb 1997 03:14:37 -0800 (PST)
Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA10429
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 03:14:33 -0800 (PST)
Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.7.3) with ESMTP id DAA27970; Tue, 4 Feb 1997 03:13:58 -0800 (PST)
Message-Id: <199702041113.DAA27970@rah.star-gate.com>
X-Mailer: exmh version 1.6.9 8/22/96
To: proff@suburbia.net
cc: hackers@freebsd.org
Subject: Re: linux net killer or no idea? (fwd) 
In-reply-to: Your message of "Tue, 04 Feb 1997 21:10:20 +1100."
             <19970204101020.12479.qmail@suburbia.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 04 Feb 1997 03:13:57 -0800
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Sorry no freeze over here, with ftp or ncftp.

	Amancio



From owner-freebsd-hackers  Tue Feb  4 03:15:35 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id DAA10508
          for hackers-outgoing; Tue, 4 Feb 1997 03:15:35 -0800 (PST)
Received: from ravenock.cybercity.dk (ravenock.cybercity.dk [194.16.57.32])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA10503
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 03:15:23 -0800 (PST)
Received: (from sos@localhost) by ravenock.cybercity.dk (8.8.5/8.7.3) id MAA23479; Tue, 4 Feb 1997 12:16:20 +0100 (MET)
From: Søren Schmidt <sos@ravenock.cybercity.dk>
Message-Id: <199702041116.MAA23479@ravenock.cybercity.dk>
Subject: Re: linux net killer or no idea? (fwd)
In-Reply-To: <19970204101020.12479.qmail@suburbia.net> from "proff@suburbia.net" at "Feb 4, 97 09:10:20 pm"
To: proff@suburbia.net
Date: Tue, 4 Feb 1997 12:16:19 +0100 (MET)
Cc: hackers@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL30 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In reply to proff@suburbia.net who wrote:

I've tried this and it works just fine:

ftp> get xppp1B-x86-ELF.tar.gz
local: xppp1B-x86-ELF.tar.gz remote: xppp1B-x86-ELF.tar.gz
200 Connected to 194.16.57.32 port 40033
150 Opening data connection
226-File written successfully
226 67.196 seconds (measured here), 4.85 Kbytes per second
384604 bytes received in 71.53 seconds (5.25 Kbytes/s)
ftp> 

Seems Linux has a problem :) :)

> 
> This is the weirdest problem I've ever, ever seen.  Or so it feels
> like.
> 
> I've just seen machines running linux/2.0.27, linux/2.1.24 and
> freebsd/3.0-current freeze after downloading 144540 bytes of this
> file:
> 
> 	ftp://ftp.troll.no/contrib/xppp1B-x86-ELF.tar.gz
> 
> Many clients can download this file just fine, many others can not.
> Those who can't all freeze after exactly 144540 bytes.  A file of the
> same size but with different contents works.  The same file with a
> different name does not work.  The same file recompressed (zcat | gzip
> - -9) to be 600 bytes smaller can be downloaded by everyone as far as I
> can test.  The same file recompressed (-5) to be 2100 bytes larger
> too.
> 
> The FTP daemon is troll-ftpd 1.20 running on linux 2.0.26 and then on
> 2.0.28.  The same file _can_ be downloaded from the same version of
> troll-ftpd running on a different linux box, which runs 2.0.27.  There
> are no tcp-related changes between .27 and .28, as far as I can see.
> 
> A huge tcpdump packet trace showing first a successful transfer of a
> 384604-byte file, then the one which freezes is available at
> 
> 	ftp://ftp.troll.no/tmp/thud
> 
> The two transfers look much the same to me, except that there appears
> to be a single packet loss while the window is wide-open, and the
> connection never recovers if this crucial file is being transferred.
> 
> I don't know which of several netstat lines -t correspond to the
> packet trace.  The most likely one shows a send queue of 43880 bytes,
> the others are similar.
> 
> I don't know whether the file, the ftpd or the packet trace helps.
> Should anyone feel like tracing something so weird and need other
> data, or access to the box, do write.
> 
> (Please cc any replies to me - I don't read linux-net right now,
> and probably won't for another two weeks or so.)
> 
> - --Arnt
> 
> ------- End of Forwarded Message
> 
> 
> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Søren Schmidt               (sos@FreeBSD.org)               FreeBSD Core Team
                Even more code to hack -- will it ever end
..

From owner-freebsd-hackers  Tue Feb  4 03:17:59 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id DAA10604
          for hackers-outgoing; Tue, 4 Feb 1997 03:17:59 -0800 (PST)
Received: from root.com (implode.root.com [198.145.90.17])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA10599
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 03:17:56 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id DAA00348; Tue, 4 Feb 1997 03:17:20 -0800 (PST)
Message-Id: <199702041117.DAA00348@root.com>
X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol
To: proff@suburbia.net
cc: hackers@freebsd.org, Richard Jones <richard@a42.deep-thought.org>
Subject: Re: linux net killer or no idea? (fwd) 
In-reply-to: Your message of "Tue, 04 Feb 1997 21:10:20 +1100."
             <19970204101020.12479.qmail@suburbia.net> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Tue, 04 Feb 1997 03:17:20 -0800
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>I've just seen machines running linux/2.0.27, linux/2.1.24 and
>freebsd/3.0-current freeze after downloading 144540 bytes of this
>file:
>
>	ftp://ftp.troll.no/contrib/xppp1B-x86-ELF.tar.gz

   This is a not-too-uncommon problem in the Internet that is caused by a
faulty CSU/DSU or by a problem with the wire it is attached to. You'll find
that there is a specific bit pattern that one of the hops involved can't deal
with, and that bit pattern just happens to be present near offset 144540 in
the above file.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project

From owner-freebsd-hackers  Tue Feb  4 03:19:45 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id DAA10653
          for hackers-outgoing; Tue, 4 Feb 1997 03:19:45 -0800 (PST)
Received: from root.com (implode.root.com [198.145.90.17])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA10648
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 03:19:40 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id DAA00348; Tue, 4 Feb 1997 03:17:20 -0800 (PST)
Message-Id: <199702041117.DAA00348@root.com>
X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol
To: proff@suburbia.net
cc: hackers@freebsd.org, Richard Jones <richard@a42.deep-thought.org>
Subject: Re: linux net killer or no idea? (fwd) 
In-reply-to: Your message of "Tue, 04 Feb 1997 21:10:20 +1100."
             <19970204101020.12479.qmail@suburbia.net> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Tue, 04 Feb 1997 03:17:20 -0800
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>I've just seen machines running linux/2.0.27, linux/2.1.24 and
>freebsd/3.0-current freeze after downloading 144540 bytes of this
>file:
>
>	ftp://ftp.troll.no/contrib/xppp1B-x86-ELF.tar.gz

   This is a not-too-uncommon problem in the Internet that is caused by a
faulty CSU/DSU or by a problem with the wire it is attached to. You'll find
that there is a specific bit pattern that one of the hops involved can't deal
with, and that bit pattern just happens to be present near offset 144540 in
the above file.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project

From owner-freebsd-hackers  Tue Feb  4 03:34:03 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id DAA11308
          for hackers-outgoing; Tue, 4 Feb 1997 03:34:03 -0800 (PST)
Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id DAA11303
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 03:34:01 -0800 (PST)
Received: from amadeus.informatik.ba-stuttgart.de by agora.rdrop.com with smtp
	(Smail3.1.29.1 #17) id m0vrj5U-0008xhC; Tue, 4 Feb 97 03:30 PST
Received: (from helbig@localhost) by amadeus.informatik.ba-stuttgart.de (8.7.3/8.7.1) id JAA26420; Tue, 4 Feb 1997 09:35:45 +0100 (MET)
From: Wolfgang Helbig <helbig@BA-Stuttgart.De>
Message-Id: <199702040835.JAA26420@amadeus.informatik.ba-stuttgart.de>
Subject: Re: CMD640b flaw workaround
To: garman@phs.k12.ar.us
Date: Tue, 04 Feb 1997 9:35:45 MET
Cc: hackers@freebsd.org
In-Reply-To: <Mutt.19970203190906.garman@jason.garman.net>; from "Jason Garman" at Feb 3, 97 7:09 pm
X-Mailer: Elm [revision: 112.2]
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi Jason,

Very good! I think your patch for 2.1.5 should also be working for
2.1.6.1 so Nadav might give it a try.
It is working for me for 2 days (and nights) now, with a hd and cd on
the primary channel and a hd on the secondary. The wd0-disk is my
root disk containing /etc, /var and swap and the wd2-disk contains
/usr. Building kernels and "make world" did not crash the system.
X-Window and Netscape did not crash the system, so I believe it is
pretty save. Maybe disklabeling does not work, but I cannot test
that one, since both disks are essential to me.

During testing I experienced, either it works at once and for ever
or not at all, and luckily it never corrupted any data!

Is there any one else (besides Jason, Nadav and me) with a CMD640b?

Wolfgang

From owner-freebsd-hackers  Tue Feb  4 03:34:52 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id DAA11410
          for hackers-outgoing; Tue, 4 Feb 1997 03:34:52 -0800 (PST)
Received: from ui-gate.utell.co.uk (ui-gate.utell.co.uk [194.200.4.253])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA11404
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 03:34:49 -0800 (PST)
Received: from dibble.utell.net (dibble.utell.net [97.3.0.10]) by ui-gate.utell.co.uk (8.7.6/8.7.3) with ESMTP id LAA23749; Tue, 4 Feb 1997 11:33:36 GMT
Message-Id: <199702041133.LAA23749@ui-gate.utell.co.uk>
From: "Brian Somers" <brian@utell.co.uk>
To: "Julian Elischer" <julian@whistle.com>,
        "Eivind Eklund" <eivind@dimaga.com>
Cc: "Charles Mott" <cmott@srv.net>,
        "Brian Somers" <brian@awfulhak.demon.co.uk>,
        "Ari Suutari" <ari.suutari@ps.carel.fi>, <hackers@freebsd.org>
Subject: Re: Single socket version of natd
Date: Tue, 4 Feb 1997 11:28:53 -0000
X-MSMail-Priority: Normal
X-Priority: 3
X-Mailer: Microsoft Internet Mail 4.70.1155
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

You guessed it - Charles originally wrote the code so.  Eventually, I'd
like to
remove the -alias switch from ppp and have the only implementation being
in the natd code.

Brian <brian@awfulhak.demon.co.uk> <brian@freebsd.org> <brian@utell.co.uk>
      <http://www.awfulhak.demon.co.uk>
Don't _EVER_ lose your sense of humour

----------
> From: Julian Elischer <julian@whistle.com>
> To: Eivind Eklund <eivind@dimaga.com>
> Cc: Charles Mott <cmott@srv.net>; Brian Somers
<brian@awfulhak.demon.co.uk>; Ari Suutari <ari.suutari@ps.carel.fi>;
hackers@freebsd.org; brian@utell.co.uk
> Subject: Re: Single socket version of natd
> Date: 04 February 1997 10:49
> 
> Eivind Eklund wrote:
> > 
> > At 07:36 PM 2/3/97 -0700, Charles Mott wrote:
> > >Eivind has these updates and has integrated them into his codebase,
> > >which he is continuing to work on.  He writes that he has changed some
of
> > >the compile options (ALIAS_ALLOW_INCOMING, ALIAS_SAME_PORTS, etc.) to
ppp
> > >commands.
> > 
> So are we talking about ppp, or natd here?
> teh subject line says natd..
> but sounds like that's not the case...
> (or has someone abstracted out the alias code to
> a separate module that can be used for both?
> 
> julian

From owner-freebsd-hackers  Tue Feb  4 04:42:22 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id EAA14255
          for hackers-outgoing; Tue, 4 Feb 1997 04:42:22 -0800 (PST)
Received: from nic.follonett.no (nic.follonett.no [194.198.43.10])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA14250
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 04:42:18 -0800 (PST)
Received: (from uucp@localhost) by nic.follonett.no (8.8.5/8.8.3) with UUCP id NAA12248; Tue, 4 Feb 1997 13:38:57 +0100 (MET)
Received: from oo7 (oo7.dimaga.com [192.0.0.65]) by dimaga.com (8.7.5/8.7.2) with SMTP id MAA11837; Tue, 4 Feb 1997 12:48:53 +0100 (MET)
Message-Id: <3.0.32.19970204124852.00959660@dimaga.com>
X-Sender: eivind@dimaga.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Tue, 04 Feb 1997 12:48:53 +0100
To: Julian Elischer <julian@whistle.com>
From: Eivind Eklund <eivind@dimaga.com>
Subject: Re: Single socket version of natd
Cc: Charles Mott <cmott@srv.net>, Brian Somers <brian@awfulhak.demon.co.uk>,
        Ari Suutari <ari.suutari@ps.carel.fi>, hackers@freebsd.org,
        brian@utell.co.uk
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

At 02:49 AM 2/4/97 -0800, Julian Elischer wrote:
>Eivind Eklund wrote:
>> 
>> At 07:36 PM 2/3/97 -0700, Charles Mott wrote:
>> >Eivind has these updates and has integrated them into his codebase,
>> >which he is continuing to work on.  He writes that he has changed some of
>> >the compile options (ALIAS_ALLOW_INCOMING, ALIAS_SAME_PORTS, etc.) to ppp
>> >commands.
>> 
>So are we talking about ppp, or natd here?
>teh subject line says natd..
>but sounds like that's not the case...
>(or has someone abstracted out the alias code to
>a separate module that can be used for both?

The code is abstracted to a single set of files.  We're talking both PPP
and natd when talking of the aliasing code.  (When talking about what to
include in 2.2, I believe it is the latest version of PPP+pktAlias that is
in question - it is finished, but I don't believe I'll have time to update
the docs before thursday.  I'll if I can get it done tonight, though.)



Eivind Eklund / perhaps@yes.no / http://maybe.yes.no/perhaps/

From owner-freebsd-hackers  Tue Feb  4 06:43:22 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id GAA18631
          for hackers-outgoing; Tue, 4 Feb 1997 06:43:22 -0800 (PST)
Received: from toth.ferginc.com (toth.ferginc.com [205.139.23.69])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA18626
          for <freebsd-hackers@FreeBSD.org>; Tue, 4 Feb 1997 06:43:19 -0800 (PST)
Received: from toth.hq.ferg.com by toth.ferginc.com (You/Wish) with SMTP id JAA28534; Tue, 4 Feb 1997 09:42:59 -0500 (EST)
Posted-Date: Tue, 4 Feb 1997 09:42:59 -0500 (EST)
Date: Tue, 4 Feb 1997 09:42:54 -0500 (EST)
From: Branson Matheson <branson@ferginc.com>
X-Sender: branson@toth.hq.ferg.com
Reply-To: branson.matheson@ferginc.com
To: Walter Belgers <W.Belgers@nl.cis.philips.com>
cc: freebsd-hackers@FreeBSD.org
Subject: Re: NIS/uids
In-Reply-To: <199702041010.LAA27440@giga.lss.cp.philips.com>
Message-ID: <Pine.BSF.3.91.970204090156.19773L-100000@toth.hq.ferg.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

On Tue, 4 Feb 1997, Walter Belgers wrote:

> Hi,
> 
> I hope this is the right place to tell my story.
> 
> I run FreeBSD 2.1.5. On my system are a bunch of local users but I also
> have users from the NIS database on another system (an HP). In my
> password file the users are defined as follows:
> 
> +user::::::::/home/john:/usr/local/bin/tcsh
> 
> So I override the homedir and shell.
> 
> The problem now is that the security on my system has become dependant
> on that of the NIS server. If I am root on the NIS server I can change
> the uid of "user" into any user including root and make use of it on my
> system. Even if you can only become root using su you can easily first
> become a user in wheel and then root.

 That is a fact.  because you are using that information from an NIS
 server, you will _always_ have a security risk from that server. 
 Anyone that has root on that server can modify a yp'd entry on that
 server, change the uid to 0 and become root on your system very
 easily. So by definition, you _have_ to trust your yp servers. 
> 
> The obvious solution is to override the uid in the password file:
> +user::1234:1234:::::/home/john:/usr/local/bin/tcsh

You can do that .. but at this point the only win you have over
seperate entries in the PW file is a single global password.

> But now I have another problem... the userid is not mapped to the
> username any more.
> 
> The fact that "user" now is only known as uid 1234 and not as user
> "user" gives rise to a lot of problems.
> 
> Is this a bug or am I overlooking something?

 I was able to reproduce this.. it is probably a bug in the login
 sequence. I looked at login it self.. but could not find anything
 obvious... can somone more experienced look at this?

  -branson
=============================================================================
 Branson Matheson     | Ferguson Enterprises  | If you're falling off a  
 System Administrator | W: (804) 874-7795     | mountian, you might as well
 Unix, Perl, WWW      | branson@ferginc.com   | attempt to fly.  -Delenn


From owner-freebsd-hackers  Tue Feb  4 06:47:55 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id GAA18779
          for hackers-outgoing; Tue, 4 Feb 1997 06:47:55 -0800 (PST)
Received: from gw-nl1.philips.com (gw-nl1.philips.com [192.68.44.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA18772
          for <freebsd-hackers@FreeBSD.org>; Tue, 4 Feb 1997 06:47:47 -0800 (PST)
Received: (from nobody@localhost) 
	by gw-nl1.philips.com (8.6.10/8.6.10-0.994n-08Nov95) id PAA23972; Tue, 4 Feb 1997 15:47:31 +0100
Received: from unknown(130.139.36.3) by gw-nl1.philips.com via smap (V1.3+ESMTP) with ESMTP
	id sma023781; Tue Feb  4 15:46:43 1997
Received: from giga.lss.cp.philips.com (giga.lss.cp.philips.com [130.144.199.31]) 
	by smtprelay.nl.cis.philips.com (8.6.10/8.6.10-1.2.1m-970131) with SMTP id PAA16217; Tue, 4 Feb 1997 15:46:42 +0100
Received: by giga.lss.cp.philips.com (8.8.5/1.63)
    id PAA04101; Tue, 4 Feb 1997 15:46:41 +0100 (MET)
From: W.Belgers@nl.cis.philips.com (Walter Belgers)
Message-Id: <199702041446.PAA04101@giga.lss.cp.philips.com>
Subject: Re: NIS/uids
To: branson.matheson@ferginc.com
Date: Tue, 4 Feb 1997 15:46:41 +0100 (MET)
Cc: freebsd-hackers@FreeBSD.org
In-Reply-To: <Pine.BSF.3.91.970204090156.19773L-100000@toth.hq.ferg.com> from Branson Matheson at "Feb 4, 97 09:42:54 am"
Organisation: Origin IT Systems Management /Nederland B.V.
X-URL: http://giga.lss.cp.philips.com/cgi-bin/walter.cgi
X-Mailer: ELM [version 2.4ME+ PL19 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

Branson Matheson writes:
> 
> > +user::::::::/home/john:/usr/local/bin/tcsh
> > 
> > The problem now is that the security on my system has become dependant
> > on that of the NIS server.
> 
>  That is a fact.  because you are using that information from an NIS
>  server, you will _always_ have a security risk from that server. 

I know. Normally, one would have the same system administrator for the
server and all clients, so it would be no problem at all. In this
particular case, I only use NIS to keep the passwords synchronised, the
NIS server is not controlled by me.

> > The obvious solution is to override the uid in the password file:
> > +user::1234:1234:::::/home/john:/usr/local/bin/tcsh
> 
> You can do that .. but at this point the only win you have over
> seperate entries in the PW file is a single global password.

That's just what I want.

>   -branson

Cheers,
Walter.
-- 
Ir. W.H.B. Belgers, Internet Security Specialist        phone: +31 40 2782753
Origin IT Syst.Man. /Nederland bv, Bldg VN-513   email:   fax: +31 40 2784697
P.O. Box 218, 5600 MD Eindhoven, Netherlands     W.Belgers@nl.cis.philips.com
non-business-email: walter@giga.nl   -web: http://www.IAEhv.nl/users/gigawalt

From owner-freebsd-hackers  Tue Feb  4 07:02:54 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id HAA19569
          for hackers-outgoing; Tue, 4 Feb 1997 07:02:54 -0800 (PST)
Received: from plains.nodak.edu (tinguely@plains.NoDak.edu [134.129.111.64])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA19564
          for <hackers@FreeBSD.org>; Tue, 4 Feb 1997 07:02:49 -0800 (PST)
Received: (from tinguely@localhost) by plains.nodak.edu (8.8.4/8.8.3) id JAA12296; Tue, 4 Feb 1997 09:02:32 -0600 (CST)
Date: Tue, 4 Feb 1997 09:02:32 -0600 (CST)
From: Mark Tinguely <tinguely@plains.nodak.edu>
Message-Id: <199702041502.JAA12296@plains.nodak.edu>
To: chris@mail.bb.cc.wa.us
Subject: Re: IPFILTER
Cc: hackers@FreeBSD.org
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

I used the ftp proxy that comes with the FireWall Tool Kit (FWTK).
The FWTK's ftp proxy does not allow for local ftp connections, so
I placed the proxy at port 1026 and left the standard ftpd at port 21.

I added to /etc/services:

ftp-gw		1026/tcp	#File Transfer [Control]
ftp-gw		1026/udp	#File Transfer [Control]

I changed the NAT rules to:

# file known as /etc/nat_rule
#
map ppp0 10.1.0.0/24 -> XXXXXXXX/32 portmap tcpudp 1027:20000
#
# Redirection is triggered for input packets.
# For example, to redirect FTP connections through this box, to the local ftp
# port, forcing them to connect through a proxy, you would use:
#
rdr ed0 0.0.0.0/0 port ftp -> 127.0.0.1 port 1026

in this way, I can ftp to the NAT machine from the internet all the time
and from the hidden net whenever NAT is not active.

to get the FWTK:

echo "send" | mail fwtk-request@tis.com

this will respond with a time sensitive ftp directory from which you can
download the software.

--mark.

From owner-freebsd-hackers  Tue Feb  4 07:16:35 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id HAA20576
          for hackers-outgoing; Tue, 4 Feb 1997 07:16:35 -0800 (PST)
Received: from chai.plexuscom.com (chai.plexuscom.com [207.87.46.100])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA20570
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 07:16:31 -0800 (PST)
Received: from chai.plexuscom.com (localhost [127.0.0.1]) by chai.plexuscom.com (8.8.4/8.6.12) with ESMTP id KAA08583; Tue, 4 Feb 1997 10:16:26 -0500 (EST)
Message-Id: <199702041516.KAA08583@chai.plexuscom.com>
To: Josh MacDonald <jmacd@CS.Berkeley.EDU>
Cc: hackers@freebsd.org
Reply-to: chat@freebsd.org
Subject: Re: g++, STL and -frepo on FreeBSD-2.2-Beta 
In-reply-to: Your message of "Mon, 03 Feb 1997 21:59:35 PST."
             <199702040559.VAA08584@paris.CS.Berkeley.EDU> 
Date: Tue, 04 Feb 1997 10:16:25 -0500
From: Bakul Shah <bakul@torrentnet.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Clearly, you have no idea what you're talking about.  You should be a 
> bit more careful with your use of "clearly", it makes me wonder how
> much of the rest of your mail to this list (which I rarely understand)
> is correct.

Since Terry responded to something I had posted, I feel obliged to
respond.

His use of `clearly' made his erroneous response a bit amusing so I
didn't mind it at all!  Terry made a mistake.  Big deal.  We all do
(like my mixing up his response with someone else's).  Most of us
want to make the most efficient use of whatever free time we have
and at times we respond without reading other people's messages
carefully enough.  When someone else does so and makes a mistake,
it is best to
  a) keep silent,
  b) correct them gently (because you can be in their place in future!), or
  c) take the discussion beyond just a simple correction.

Generalizations like `you have no idea what you are talking about'
*clearly* do not belong on a technical group.

Now it would be nice if all of Terry's posts were crystal clear --
I confess I understand may be 80% of what he writes (even when I
think I agree with what he says I am not 100% sure :-) -- but his
contributions do enrich various discussions and I often learn new
things from his posts.

On the g++, STL, -frepo front, the good news is that once I stopped
doing things the hardway (that is, once I started using the FreeBSD
g++ without any fancy flags), the program actually compiled and
linked.  The bad news is that it segfaults on even simple Verilog
module definitions.  So for now this mini project has been ^Z'ed
(put on hold).  Thanks to all the people who responded with helpful
hints (even if wrong:-).

-- bakul

From owner-freebsd-hackers  Tue Feb  4 07:41:06 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id HAA21968
          for hackers-outgoing; Tue, 4 Feb 1997 07:41:06 -0800 (PST)
Received: from gargoyle.bazzle.com (gargoyle.bazzle.com [206.103.246.190])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA21962
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 07:41:03 -0800 (PST)
Received: from gargoyle.bazzle.com (net2.bazzle.com [206.103.246.189]) by gargoyle.bazzle.com (8.8.4/8.6.12) with SMTP id KAA10606; Tue, 4 Feb 1997 10:40:45 -0500 (EST)
Date: Tue, 4 Feb 1997 10:40:45 -0500 (EST)
From: "Eric J. Chet" <ejc@gargoyle.bazzle.com>
To: proff@suburbia.net
cc: hackers@freebsd.org
Subject: Re: linux net killer or no idea? (fwd)
In-Reply-To: <19970204101020.12479.qmail@suburbia.net>
Message-ID: <Pine.BSF.3.95.970204103911.10599A-100000@gargoyle.bazzle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


On Tue, 4 Feb 1997 proff@suburbia.net wrote:

> 	ftp://ftp.troll.no/contrib/xppp1B-x86-ELF.tar.gz
> 
> Many clients can download this file just fine, many others can not.
> Those who can't all freeze after exactly 144540 bytes.  A file of the
> same size but with different contents works.  The same file with a
> different name does not work.  The same file recompressed (zcat | gzip
> - -9) to be 600 bytes smaller can be downloaded by everyone as far as I
> can test.  The same file recompressed (-5) to be 2100 bytes larger
> too.

-current as of a week ago.

fetch ftp://ftp.troll.no/contrib/xppp1B-x86-ELF.tar.gz
Receiving xppp1B-x86-ELF.tar.gz (384604 bytes): 100%
384604 bytes transfered in 126.8 seconds  (2.96 K/s)

                                              Eric J. Chet
					       - ejc@naserver1.cb.lucent.com
                                               - ejc@bazzle.com



From owner-freebsd-hackers  Tue Feb  4 08:28:33 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id IAA25182
          for hackers-outgoing; Tue, 4 Feb 1997 08:28:33 -0800 (PST)
Received: from darkstar (dialin2.anlw.anl.gov [141.221.252.102])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id IAA25163
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 08:28:28 -0800 (PST)
Received: (from cmott@localhost) by darkstar (8.6.12/8.6.12) id JAA08728; Tue, 4 Feb 1997 09:28:09 -0700
Date: Tue, 4 Feb 1997 09:28:08 -0700 (MST)
From: Charles Mott <cmott@srv.net>
X-Sender: cmott@darkstar
To: Brian Somers <brian@utell.co.uk>
cc: Julian Elischer <julian@whistle.com>, Eivind Eklund <eivind@dimaga.com>,
        Brian Somers <brian@awfulhak.demon.co.uk>,
        Ari Suutari <ari.suutari@ps.carel.fi>, hackers@freebsd.org
Subject: Re: Single socket version of natd
In-Reply-To: <199702041133.LAA23749@ui-gate.utell.co.uk>
Message-ID: <Pine.BSF.3.91.970204091518.8654A-100000@darkstar>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

The one situation I think is difficult for natd to handle is is when ppp 
is running in -auto mode, and it reconnects on each dial-in with a 
different dynamcially assigned address.

At the moment, natd can do device address lookup at startup, but to 
handle the above mentioned case, it would have to do a device address 
lookup for every packet.  Is it possible to do this?

I personally like having both ppp -alias as well as natd.  Having the 
software embedded in ppp and enabled with the -alias switch makes life 
very easy for a great number of less sophisticated users.

Charles Mott


On Tue, 4 Feb 1997, Brian Somers wrote:

> You guessed it - Charles originally wrote the code so.  Eventually, I'd
> like to
> remove the -alias switch from ppp and have the only implementation being
> in the natd code.
> 
> Brian <brian@awfulhak.demon.co.uk> <brian@freebsd.org> <brian@utell.co.uk>
>       <http://www.awfulhak.demon.co.uk>
> Don't _EVER_ lose your sense of humour
> 
> ----------
> > From: Julian Elischer <julian@whistle.com>
> > To: Eivind Eklund <eivind@dimaga.com>
> > Cc: Charles Mott <cmott@srv.net>; Brian Somers
> <brian@awfulhak.demon.co.uk>; Ari Suutari <ari.suutari@ps.carel.fi>;
> hackers@freebsd.org; brian@utell.co.uk
> > Subject: Re: Single socket version of natd
> > Date: 04 February 1997 10:49
> > 
> > Eivind Eklund wrote:
> > > 
> > > At 07:36 PM 2/3/97 -0700, Charles Mott wrote:
> > > >Eivind has these updates and has integrated them into his codebase,
> > > >which he is continuing to work on.  He writes that he has changed some
> of
> > > >the compile options (ALIAS_ALLOW_INCOMING, ALIAS_SAME_PORTS, etc.) to
> ppp
> > > >commands.
> > > 
> > So are we talking about ppp, or natd here?
> > teh subject line says natd..
> > but sounds like that's not the case...
> > (or has someone abstracted out the alias code to
> > a separate module that can be used for both?
> > 
> > julian
> 

From owner-freebsd-hackers  Tue Feb  4 09:00:29 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA28001
          for hackers-outgoing; Tue, 4 Feb 1997 09:00:29 -0800 (PST)
Received: from ui-gate.utell.co.uk (ui-gate.utell.co.uk [194.200.4.253])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA27977
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 09:00:24 -0800 (PST)
Received: from dibble.utell.net (dibble.utell.net [97.3.0.10]) by ui-gate.utell.co.uk (8.7.6/8.7.3) with ESMTP id QAA00486; Tue, 4 Feb 1997 16:59:00 GMT
Message-Id: <199702041659.QAA00486@ui-gate.utell.co.uk>
From: "Brian Somers" <brian@utell.co.uk>
To: "Charles Mott" <cmott@srv.net>
Cc: "Julian Elischer" <julian@whistle.com>,
        "Eivind Eklund" <eivind@dimaga.com>,
        "Brian Somers" <brian@awfulhak.demon.co.uk>,
        "Ari Suutari" <ari.suutari@ps.carel.fi>, <hackers@freebsd.org>
Subject: Re: Single socket version of natd
Date: Tue, 4 Feb 1997 16:58:58 -0000
X-MSMail-Priority: Normal
X-Priority: 3
X-Mailer: Microsoft Internet Mail 4.70.1155
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

That's a good point.

If we leave it in both ppp & natd, can we add a (third) arg to
PacketAlias{In,Out}() that tells it not to do anything with the
ip_sum ?  If it's reading raw packets from a wire (with ppp),
the sum may be wrong (this has been discussed before) and
we want to leave incorrect the sum alone, but with natd, it's a
terrible waste to have the kernel code zero the sum, have natd
re-calculate it, have PacketAliasIn() check it, and then probably
re-calculate it again (if anything's changed).

With a "leave the sum alone option", natd could pass the packet
with the zero'd ip_sum to PacketAliasIn() and know that it has
to calculate it itself afterwards....

Cheers.

Brian <brian@awfulhak.demon.co.uk> <brian@freebsd.org> <brian@utell.co.uk>
      <http://www.awfulhak.demon.co.uk>
Don't _EVER_ lose your sense of humour

----------
> From: Charles Mott <cmott@srv.net>
> To: Brian Somers <brian@utell.co.uk>
> Cc: Julian Elischer <julian@whistle.com>; Eivind Eklund
<eivind@dimaga.com>; Brian Somers <brian@awfulhak.demon.co.uk>; Ari Suutari
<ari.suutari@ps.carel.fi>; hackers@freebsd.org
> Subject: Re: Single socket version of natd
> Date: 04 February 1997 16:28
> 
> The one situation I think is difficult for natd to handle is is when ppp 
> is running in -auto mode, and it reconnects on each dial-in with a 
> different dynamcially assigned address.
> 
> At the moment, natd can do device address lookup at startup, but to 
> handle the above mentioned case, it would have to do a device address 
> lookup for every packet.  Is it possible to do this?
> 
> I personally like having both ppp -alias as well as natd.  Having the 
> software embedded in ppp and enabled with the -alias switch makes life 
> very easy for a great number of less sophisticated users.
> 
> Charles Mott
> 
> 
> On Tue, 4 Feb 1997, Brian Somers wrote:
> 
> > You guessed it - Charles originally wrote the code so.  Eventually, I'd
> > like to
> > remove the -alias switch from ppp and have the only implementation
being
> > in the natd code.
> > 
> > Brian <brian@awfulhak.demon.co.uk> <brian@freebsd.org>
<brian@utell.co.uk>
> >       <http://www.awfulhak.demon.co.uk>
> > Don't _EVER_ lose your sense of humour
> > 
> > ----------
> > > From: Julian Elischer <julian@whistle.com>
> > > To: Eivind Eklund <eivind@dimaga.com>
> > > Cc: Charles Mott <cmott@srv.net>; Brian Somers
> > <brian@awfulhak.demon.co.uk>; Ari Suutari <ari.suutari@ps.carel.fi>;
> > hackers@freebsd.org; brian@utell.co.uk
> > > Subject: Re: Single socket version of natd
> > > Date: 04 February 1997 10:49
> > > 
> > > Eivind Eklund wrote:
> > > > 
> > > > At 07:36 PM 2/3/97 -0700, Charles Mott wrote:
> > > > >Eivind has these updates and has integrated them into his
codebase,
> > > > >which he is continuing to work on.  He writes that he has changed
some
> > of
> > > > >the compile options (ALIAS_ALLOW_INCOMING, ALIAS_SAME_PORTS, etc.)
to
> > ppp
> > > > >commands.
> > > > 
> > > So are we talking about ppp, or natd here?
> > > teh subject line says natd..
> > > but sounds like that's not the case...
> > > (or has someone abstracted out the alias code to
> > > a separate module that can be used for both?
> > > 
> > > julian
> > 

From owner-freebsd-hackers  Tue Feb  4 09:11:17 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA28815
          for hackers-outgoing; Tue, 4 Feb 1997 09:11:17 -0800 (PST)
Received: from logues.rhn.orst.edu (logues.RHN.ORST.EDU [128.193.139.116])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA28762;
          Tue, 4 Feb 1997 09:10:56 -0800 (PST)
Received: from localhost (stevel@localhost)
          by logues.rhn.orst.edu (8.8.4/8.8.4) with SMTP
	  id JAA05171; Tue, 4 Feb 1997 09:10:29 -0800 (PST)
Date: Tue, 4 Feb 1997 09:10:29 -0800 (PST)
From: stevel <stevel@logues.rhn.orst.edu>
To: John Hay <jhay@zibbi.mikom.csir.co.za>
cc: Steve Logue <logue@engr.orst.edu>, stenn@whimsy.udel.edu,
        freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org,
        freebsd-stable@freebsd.org
Subject: Re: xntp3-5.89.2 & FreeBSD 2.2-GAMMA won't compile
In-Reply-To: <199702041034.MAA13094@zibbi.mikom.csir.co.za>
Message-ID: <Pine.BSF.3.95.970204090827.5166A-100000@logues.rhn.orst.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk



On Tue, 4 Feb 1997, John Hay wrote:

> I have fixed it in FreeBSD-current, but weren't sure if it should go into
> 2.2. Any opinions anyone? It has been in -current from December 31 and
> nobody has complained yet. Three files are effected sys/sys/timex.h,
> sys/kern/kern_ntptime.c and sys/kern/kern_clock.c.
> 
> If somebody from the 2.2 release team give the go-ahead I would be
> happy to put it in 2.2.

What if they don't?  I still need it.  Can you describe the changes that
you applied.  I'm sure it isn't as simple as copying these files into the
kernel src tree, and recompiling, or is it?

Thanks -STEVEl



From owner-freebsd-hackers  Tue Feb  4 09:18:40 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA29278
          for hackers-outgoing; Tue, 4 Feb 1997 09:18:40 -0800 (PST)
Received: from darkstar (dialin2.anlw.anl.gov [141.221.252.102])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA29269
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 09:18:37 -0800 (PST)
Received: (from cmott@localhost) by darkstar (8.6.12/8.6.12) id KAA08767; Tue, 4 Feb 1997 10:17:46 -0700
Date: Tue, 4 Feb 1997 10:17:41 -0700 (MST)
From: Charles Mott <cmott@srv.net>
X-Sender: cmott@darkstar
To: Brian Somers <brian@utell.co.uk>
cc: Julian Elischer <julian@whistle.com>, Eivind Eklund <eivind@dimaga.com>,
        Brian Somers <brian@awfulhak.demon.co.uk>,
        Ari Suutari <ari.suutari@ps.carel.fi>, hackers@freebsd.org
Subject: Re: Single socket version of natd
In-Reply-To: <199702041659.QAA00486@ui-gate.utell.co.uk>
Message-ID: <Pine.BSF.3.91.970204100202.8654C-100000@darkstar>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> If we leave it in both ppp & natd, can we add a (third) arg to
> PacketAlias{In,Out}() that tells it not to do anything with the
> ip_sum ?  If it's reading raw packets from a wire (with ppp),
> the sum may be wrong (this has been discussed before) and
> we want to leave incorrect the sum alone, but with natd, it's a
> terrible waste to have the kernel code zero the sum, have natd
> re-calculate it, have PacketAliasIn() check it, and then probably
> re-calculate it again (if anything's changed).
> 
> With a "leave the sum alone option", natd could pass the packet
> with the zero'd ip_sum to PacketAliasIn() and know that it has
> to calculate it itself afterwards....

Why does the kernel zero the checksum?

IP checksum has never been much of a problem, because it is only 20 bytes
or so.  It is the TCP, UDP and ICMP layers where efficiency pays off. 

In any event, all IP checksums modifications in alias*.c are now
differential, so calculations are only made for packet data which has been
altered.  Unlike older versions, there is no checking and recomputation of
the complete IP header. 

Charles Mott

From owner-freebsd-hackers  Tue Feb  4 09:54:30 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA01334
          for hackers-outgoing; Tue, 4 Feb 1997 09:54:30 -0800 (PST)
Received: from darkstar (dialin2.anlw.anl.gov [141.221.252.102])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA01329
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 09:54:24 -0800 (PST)
Received: (from cmott@localhost) by darkstar (8.6.12/8.6.12) id KAA08796; Tue, 4 Feb 1997 10:53:53 -0700
Date: Tue, 4 Feb 1997 10:53:52 -0700 (MST)
From: Charles Mott <cmott@srv.net>
X-Sender: cmott@darkstar
To: Eivind Eklund <eivind@dimaga.com>
cc: Brian Somers <brian@awfulhak.demon.co.uk>,
        Ari Suutari <ari.suutari@ps.carel.fi>, hackers@freebsd.org,
        brian@utell.co.uk
Subject: Re: Single socket version of natd 
In-Reply-To: <3.0.32.19970204103732.00ac3a30@dimaga.com>
Message-ID: <Pine.BSF.3.91.970204104216.8654E-100000@darkstar>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Tue, 4 Feb 1997, Eivind Eklund wrote:

> And all the other really nescessary code-changes are done - everything is
> changed to ANSI style, and integrated with PPP from -current patched with
> #ifdef's to make it compile and work on all versions from 2.1.0 to
> -current,  with an extra command 'alias' that set alias options.

Do the alias options default the way they have in the past, or does the 
user have to explicitly set them?

Can packet aliasing be enabled a ppp command as well as the -alias 
command line option?  If so, is this a good idea?  My concern here is 
that users be able to use the same ppp.conf file with and without packet 
aliasing.

Charles Mott


From owner-freebsd-hackers  Tue Feb  4 10:15:33 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id KAA02268
          for hackers-outgoing; Tue, 4 Feb 1997 10:15:33 -0800 (PST)
Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA02260
          for <freebsd-hackers@FreeBSD.org>; Tue, 4 Feb 1997 10:15:27 -0800 (PST)
Received: from deputy.pavilion.co.uk (deputy.pavilion.co.uk [194.242.128.24])
	by florence.pavilion.net (8.8.5/8.8.5) with ESMTP id SAA26193;
	Tue, 4 Feb 1997 18:14:48 GMT
From: Josef Karthauser <jlk@pavilion.co.uk>
Received: (from jlk@localhost)
          by deputy.pavilion.co.uk (8.8.3/8.8.4)
	  id SAA00858; Tue, 4 Feb 1997 18:14:48 GMT
Message-Id: <199702041814.SAA00858@deputy.pavilion.co.uk>
Subject: Re: probing scsi bus after boot?
To: dufault@hda.com (Peter Dufault)
Date: Tue, 4 Feb 1997 18:14:48 +0000 (GMT)
Cc: jkh@time.cdrom.com, joerg_wunsch@uriah.heep.sax.de,
        freebsd-hackers@FreeBSD.org, jlk@pavilion.co.uk
In-Reply-To: <199611011028.FAA07666@hda.hda.com> from "Peter Dufault" at Nov 1, 96 05:28:54 am
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

Sorry to bring up an old thread, but I've got a scsi tape drive that
I need to use across many machines to back their file systems up.
I can think of two ways to do it.
Either I use rmt, but I've not found a way of rmt'ing as root on the
remote site (please someone let me out of my misery.)

The other way is to plug the tape drive into the machine that I'm
backing up.  I've compiled the super scsi driver into my 2.1.6 kernel
(controller ssc), but I still get:
	# scsi -f /dev/rst0 -p
	scsi: unable to open device /dev/rst0: Device not configured

I guess that I might have to do this on the /dev/scsi/super device,
but /dev/MAKEDEV doesn't build it!

Any hints would be greatly appreciated.

Cheers,
Joe.
> 
> > Huh?  I just do this on /dev/sd0 or some other - it works great!
> > I use it to detect my scanner after power-up all the time.
> 
> The super SCSI device is needed when nothing is on the bus at boot
> - you then need a way into the system for that case.  Try putting
> your scanner on its own bus with no SCSI devices (I forgot - you
> NEVER have a system with no SCSI devices).  The super SCSI device
> should support bus configuration (such as reprobe) and "device
> target" types of calls ("become this SCSI NEXUS").  It is essentially
> a SCSI bus device.
> 
> I added it when I was doing some work with a prototype device on
> a dedicated bus that was frequently not powered up.
> 
> IMHO super SCSI should be left working this way, maybe renamed to
> be a bus device.  The SCSI user code should be ripped out with
> extreme prejudice - it is superceded by the newer configuration
> code.
> 
> The code suffers from no use and no test.
> 
> Peter
> 
> -- 
> Peter Dufault               Real-Time Machine Control and Simulation
> HD Associates, Inc.         Voice: 508 433 6936
> dufault@hda.com             Fax:   508 433 5267
> 


-- 
Josef Karthauser        (joe@pavilion.net)
Technical Manager       [Tel: +44 1273 607072  Fax: +44 1273 607073]
Pavilion Internet plc.  ._ .. _. _  ._.. .. .._. .  __. ._. ._ _. _..


From owner-freebsd-hackers  Tue Feb  4 10:39:08 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id KAA03606
          for hackers-outgoing; Tue, 4 Feb 1997 10:39:08 -0800 (PST)
Received: from ui-gate.utell.co.uk (ui-gate.utell.co.uk [194.200.4.253])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA03592
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 10:39:02 -0800 (PST)
Received: from dibble.utell.net (dibble.utell.net [97.3.0.10]) by ui-gate.utell.co.uk (8.7.6/8.7.3) with ESMTP id SAA02367; Tue, 4 Feb 1997 18:37:30 GMT
Message-Id: <199702041837.SAA02367@ui-gate.utell.co.uk>
From: "Brian Somers" <brian@utell.co.uk>
To: "Charles Mott" <cmott@srv.net>
Cc: "Julian Elischer" <julian@whistle.com>,
        "Eivind Eklund" <eivind@dimaga.com>,
        "Brian Somers" <brian@awfulhak.demon.co.uk>,
        "Ari Suutari" <ari.suutari@ps.carel.fi>, <hackers@freebsd.org>
Subject: Re: Single socket version of natd
Date: Tue, 4 Feb 1997 18:37:30 -0000
X-MSMail-Priority: Normal
X-Priority: 3
X-Mailer: Microsoft Internet Mail 4.70.1155
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I don't know specifically without checking the code, but I recall seeing a
comment in the -current sources (I've just checked SNAP-961014, nothing
about it there) about using the ip_sum to differentiate between incoming
and outgoing packets.....  It *WAS* commented as being a HACK :(

I'll check the code out this evening when I get home (-current machine)
and tell you.

Brian <brian@awfulhak.demon.co.uk> <brian@freebsd.org> <brian@utell.co.uk>
      <http://www.awfulhak.demon.co.uk>
Don't _EVER_ lose your sense of humour

----------
> From: Charles Mott <cmott@srv.net>
> To: Brian Somers <brian@utell.co.uk>
> Cc: Julian Elischer <julian@whistle.com>; Eivind Eklund
<eivind@dimaga.com>; Brian Somers <brian@awfulhak.demon.co.uk>; Ari Suutari
<ari.suutari@ps.carel.fi>; hackers@freebsd.org
> Subject: Re: Single socket version of natd
> Date: 04 February 1997 17:17
> 
> > If we leave it in both ppp & natd, can we add a (third) arg to
> > PacketAlias{In,Out}() that tells it not to do anything with the
> > ip_sum ?  If it's reading raw packets from a wire (with ppp),
> > the sum may be wrong (this has been discussed before) and
> > we want to leave incorrect the sum alone, but with natd, it's a
> > terrible waste to have the kernel code zero the sum, have natd
> > re-calculate it, have PacketAliasIn() check it, and then probably
> > re-calculate it again (if anything's changed).
> > 
> > With a "leave the sum alone option", natd could pass the packet
> > with the zero'd ip_sum to PacketAliasIn() and know that it has
> > to calculate it itself afterwards....
> 
> Why does the kernel zero the checksum?
> 
> IP checksum has never been much of a problem, because it is only 20 bytes
> or so.  It is the TCP, UDP and ICMP layers where efficiency pays off. 
> 
> In any event, all IP checksums modifications in alias*.c are now
> differential, so calculations are only made for packet data which has
been
> altered.  Unlike older versions, there is no checking and recomputation
of
> the complete IP header. 
> 
> Charles Mott

From owner-freebsd-hackers  Tue Feb  4 10:46:40 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id KAA04191
          for hackers-outgoing; Tue, 4 Feb 1997 10:46:40 -0800 (PST)
Received: from nic.follonett.no (nic.follonett.no [194.198.43.10])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA04166
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 10:46:34 -0800 (PST)
Received: (from uucp@localhost) by nic.follonett.no (8.8.5/8.8.3) with UUCP id TAA16901; Tue, 4 Feb 1997 19:42:15 +0100 (MET)
Received: from oo7 (oo7.dimaga.com [192.0.0.65]) by dimaga.com (8.7.5/8.7.2) with SMTP id TAA16632; Tue, 4 Feb 1997 19:44:55 +0100 (MET)
Message-Id: <3.0.32.19970204194456.00bbae30@dimaga.com>
X-Sender: eivind@dimaga.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Tue, 04 Feb 1997 19:44:57 +0100
To: Charles Mott <cmott@srv.net>
From: Eivind Eklund <eivind@dimaga.com>
Subject: Re: Single socket version of natd 
Cc: Brian Somers <brian@awfulhak.demon.co.uk>,
        Ari Suutari <ari.suutari@ps.carel.fi>, hackers@freebsd.org,
        brian@utell.co.uk
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

At 10:53 AM 2/4/97 -0700, Charles Mott wrote:
>On Tue, 4 Feb 1997, Eivind Eklund wrote:
>
>> And all the other really nescessary code-changes are done - everything is
>> changed to ANSI style, and integrated with PPP from -current patched with
>> #ifdef's to make it compile and work on all versions from 2.1.0 to
>> -current,  with an extra command 'alias' that set alias options.
>
>Do the alias options default the way they have in the past, or does the 
>user have to explicitly set them?

They default the same way, yeah.  I'll drop the source at you later tonight.

>Can packet aliasing be enabled a ppp command as well as the -alias 
>command line option?

Yep.

>If so, is this a good idea?  My concern here is that users be able to use
the >same ppp.conf file with and without packet aliasing.

My concern is that I should be able to make all users on the LAN (all of
them have access to setting up a PPP connection) remember to enable
aliasing.  If I had not wanted it in all cases, I'd just drop putting the
command in the config file.  Nothing lost in my case, at least.

However, a way of giving the user 100% control again might be to add a
-noalias keyword to completely block packet aliasing.  This would take one
more bit from mode in IIJ-PPP, though.  Besides, as an admin I'm not
certain I would want the users to have that control.



Eivind Eklund / perhaps@yes.no / http://maybe.yes.no/perhaps/

From owner-freebsd-hackers  Tue Feb  4 10:52:56 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id KAA04643
          for hackers-outgoing; Tue, 4 Feb 1997 10:52:56 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA04635
          for <freebsd-hackers@freebsd.org>; Tue, 4 Feb 1997 10:52:49 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA12897; Tue, 4 Feb 1997 11:50:12 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702041850.LAA12897@phaeton.artisoft.com>
Subject: Re: Mounting CD-ROM when data not on first track
To: joerg_wunsch@uriah.heep.sax.de
Date: Tue, 4 Feb 1997 11:50:12 -0700 (MST)
Cc: freebsd-hackers@freebsd.org
In-Reply-To: <Mutt.19970203093055.j@uriah.heep.sax.de> from "J Wunsch" at Feb 3, 97 09:30:55 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > You mean, like putting in partition recognition code in the kernel
> > instead of putting it in the FS instead (like you are suggesting here)?
> 
> No.  These dreaded CD-ROM tracks have one thing different from normal
> partitions: the filesystem code in it still references the disk by
> absolute frame (block) numbers.  Filesystems that live in partitions
> do not do this, they describe the filesystem relative to the start of
> the partition.

This puts a nasty spin on things.

On the other hand, supporting a logical-to-physical mapping layer
that implemented bad144 would have similar issues.  I think the
device specific code could export the block relativity interface,
while still enforcing range checking.  We'd have to be able to
access this to veto install on a partition which was below C 1024
but which contained a replacement block above C 1024.

Ah, the vagries of PC manufacturer implementation of "standards"
applies to ISO9660 as well, it seems.  8-(.

> > > Sticky bit?  Terry, you're riding your time-machine again, you're
> > > currently some ten years back.
> > 
> > If you will recall, I've requested the ability to force images totally
> > into local cache on a per FS basis by attributing the FS as "nonlocal".
> 
> Sorry, i misread your comment and thought you were referring to
> something that does already exist.

Heh... through no fault of my own, you might add...


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Tue Feb  4 10:55:38 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id KAA04773
          for hackers-outgoing; Tue, 4 Feb 1997 10:55:38 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA04759
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 10:55:34 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA12911; Tue, 4 Feb 1997 11:53:13 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702041853.LAA12911@phaeton.artisoft.com>
Subject: Re: bisdn
To: grog@lemis.de
Date: Tue, 4 Feb 1997 11:53:13 -0700 (MST)
Cc: terry@lambert.org, hackers@freebsd.org
In-Reply-To: <199702030652.HAA22553@freebie.lemis.de> from "Greg Lehey" at Feb 3, 97 07:52:40 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> >>  Oh really?  Do you get D channels?  What do you do with them?
> >
> > Basic rate:	2B+D
> 
> OK.  Note the second question: what do you do with them?
> 
> > US West:	2D+B
> 
> Really?  I find that hard to believe.  I suppose the question is
> doubly relevant here: What do you do with them?

Heh.  Nothing.  We avoid buying them and complain bitterly about
the lack of ISP Frame Relay support in the area, mostly.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Tue Feb  4 10:57:05 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id KAA04891
          for hackers-outgoing; Tue, 4 Feb 1997 10:57:05 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA04878
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 10:56:59 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA12924; Tue, 4 Feb 1997 11:53:48 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702041853.LAA12924@phaeton.artisoft.com>
Subject: Re: bisdn
To: michaelh@cet.co.jp (Michael Hancock)
Date: Tue, 4 Feb 1997 11:53:48 -0700 (MST)
Cc: grog@lemis.de, terry@lambert.org, hackers@freebsd.org
In-Reply-To: <Pine.SV4.3.95.970203180631.8689A-100000@parkplace.cet.co.jp> from "Michael Hancock" at Feb 3, 97 06:09:46 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > > Basic rate:	2B+D
> > 
> > OK.  Note the second question: what do you do with them?
> > 
> > > US West:	2D+B
> > 
> > Really?  I find that hard to believe.  I suppose the question is
> > doubly relevant here: What do you do with them?
> 
> I find this hard to believe too, 2D channels is wierd.  The D-channel is
> for out-of-band signaling.  It's why you get 64K instead of 56K. 

See www.uswest.com.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Tue Feb  4 10:58:09 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id KAA04982
          for hackers-outgoing; Tue, 4 Feb 1997 10:58:09 -0800 (PST)
Received: from diablo.ppp.de (diablo.ppp.de [193.141.101.34])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA04972
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 10:58:06 -0800 (PST)
Received: from freebie.lemis.de by diablo.ppp.de with smtp
	(Smail3.1.28.1 #1) id m0vrq3z-000QZlC; Tue, 4 Feb 97 19:57 MET
Received: (grog@localhost) by freebie.lemis.de (8.8.4/8.6.12) 
       id TAA15699; Tue, 4 Feb 1997 19:57:33 +0100 (MET)
From: grog@lemis.de
Message-Id: <199702041857.TAA15699@freebie.lemis.de>
Subject: Re: bisdn
In-Reply-To: <199702041853.LAA12911@phaeton.artisoft.com> from Terry Lambert at "Feb 4, 97 11:53:13 am"
To: terry@lambert.org (Terry Lambert)
Date: Tue, 4 Feb 1997 19:57:33 +0100 (MET)
Cc: hackers@freebsd.org (FreeBSD Hackers)
Organisation: 	LEMIS, Schellnhausen 2, 36325 Feldatal, Germany
Phone: +49-6637-919123
Fax: +49-6637-919122
Reply-to: grog@lemis.de (Greg Lehey)
WWW-Home-Page: http://www.FreeBSD.org/~grog
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Terry Lambert writes:
>>>>   Oh really?  Do you get D channels?  What do you do with them?
>>>
>>>  Basic rate:	2B+D
>>
>>  OK.  Note the second question: what do you do with them?
>>
>>>  US West:	2D+B
>>
>>  Really?  I find that hard to believe.  I suppose the question is
>>  doubly relevant here: What do you do with them?
>
> Heh.  Nothing.  We avoid buying them and complain bitterly about
> the lack of ISP Frame Relay support in the area, mostly.

Speak for yourself.  Plenty of people in the USA use ISDN.  And while
you're at it, how about admitting (like other people do from time to
time) that you screwed up?

Greg

From owner-freebsd-hackers  Tue Feb  4 11:14:16 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA06143
          for hackers-outgoing; Tue, 4 Feb 1997 11:14:16 -0800 (PST)
Received: from diablo.ppp.de (diablo.ppp.de [193.141.101.34])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA06138
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 11:14:13 -0800 (PST)
Received: from freebie.lemis.de by diablo.ppp.de with smtp
	(Smail3.1.28.1 #1) id m0vrqJm-000QZvC; Tue, 4 Feb 97 20:14 MET
Received: (grog@localhost) by freebie.lemis.de (8.8.4/8.6.12) 
       id TAA15750 for hackers@freebsd.org; Tue, 4 Feb 1997 19:59:44 +0100 (MET)
From: grog@lemis.de
Message-Id: <199702041859.TAA15750@freebie.lemis.de>
Subject: Re: bisdn
In-Reply-To: <199702041853.LAA12924@phaeton.artisoft.com> from Terry Lambert at "Feb 4, 97 11:53:48 am"
To: terry@lambert.org (Terry Lambert)
Date: Tue, 4 Feb 1997 19:59:18 +0100 (MET)
Organisation: 	LEMIS, Schellnhausen 2, 36325 Feldatal, Germany
Phone: +49-6637-919123
Fax: +49-6637-919122
Reply-to: grog@lemis.de (Greg Lehey)
WWW-Home-Page: http://www.FreeBSD.org/~grog
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Terry Lambert writes:
>>>>  Basic rate:	2B+D
>>>
>>>  OK.  Note the second question: what do you do with them?
>>>
>>>>  US West:	2D+B
>>>
>>>  Really?  I find that hard to believe.  I suppose the question is
>>>  doubly relevant here: What do you do with them?
>>
>>  I find this hard to believe too, 2D channels is wierd.  The D-channel is
>>  for out-of-band signaling.  It's why you get 64K instead of 56K.
>
> See www.uswest.com.

The whole page doesn't mention ISDN.  Can you give a more specific
URL?

If they claim 2D+1B, you can be sure that it's a typo.

Greg


From owner-freebsd-hackers  Tue Feb  4 11:21:10 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA06429
          for hackers-outgoing; Tue, 4 Feb 1997 11:21:10 -0800 (PST)
Received: from csd.cs.technion.ac.il (csd.cs.technion.ac.il [132.68.32.8])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA06421
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 11:20:58 -0800 (PST)
Received: from localhost (nadav@localhost) by csd.cs.technion.ac.il (8.6.11/8.6.10) with SMTP id VAA29914; Tue, 4 Feb 1997 21:09:42 +0200
X-Authentication-Warning: csd.cs.technion.ac.il: nadav owned process doing -bs
Date: Tue, 4 Feb 1997 21:09:42 +0200 (IST)
From: Nadav Eiron <nadav@cs.technion.ac.il>
X-Sender: nadav@csd
To: Wolfgang Helbig <helbig@BA-Stuttgart.De>
cc: garman@phs.k12.ar.us, hackers@freebsd.org
Subject: Re: CMD640b flaw workaround
In-Reply-To: <199702040835.JAA26420@amadeus.informatik.ba-stuttgart.de>
Message-ID: <Pine.GSO.3.95-heb-2.07.970204210307.29771A-100000@csd>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk



On Tue, 4 Feb 1997, Wolfgang Helbig wrote:

> Hi Jason,
> 
> Very good! I think your patch for 2.1.5 should also be working for
> 2.1.6.1 so Nadav might give it a try.
> It is working for me for 2 days (and nights) now, with a hd and cd on
> the primary channel and a hd on the secondary. The wd0-disk is my
> root disk containing /etc, /var and swap and the wd2-disk contains
> /usr. Building kernels and "make world" did not crash the system.
> X-Window and Netscape did not crash the system, so I believe it is
> pretty save. Maybe disklabeling does not work, but I cannot test
> that one, since both disks are essential to me.
> 
> During testing I experienced, either it works at once and for ever
> or not at all, and luckily it never corrupted any data!
> 
> Is there any one else (besides Jason, Nadav and me) with a CMD640b?
> 
> Wolfgang
> 

I tried installing the patches on my troubled 2.1.5R system, and it
doesn't cure my problem. I think I should describe my problem once again,
as it's not the classical CMD640 bug. I have a machine with a hard disk
(Quantum FireBall) and a CD (Creative x4), both on the primary channel.
The problem is that CD access is unreliable. It's most commonly seen when
I try to serve a CD directly via apache. Under heavy load, some of the
Apace processes will hang while accessing the CD like so:

gatekeeper: {102} ps auxw | grep http | grep D
apache     253  0.0  2.3   660  512  ??  D     8:49PM    0:00.08 /usr/local/apache/ssl.1.3_apache.1.1.1/httpsd -f /usr/local/apache
apache     279  0.0  2.3   672  512  ??  D     8:50PM    0:00.06 /usr/local/apache/ssl.1.3_apache.1.1.1/httpsd -f /usr/local/apache
apache     281  0.0  2.3   672  512  ??  D     8:51PM    0:00.06 /usr/local/apache/ssl.1.3_apache.1.1.1/httpsd -f /usr/local/apache

until after some time the whole machine will hang. I don't have this
problem when running with an ATAPI CD (also from Creative, but a newer
model) on a machine that does not have the CMD640, but it may still be
unrelated. There is nothing to indicate a problem on the console (or dmesg
output). The machine will simply hang, and those Apache processes will
never recover.

As I said before, the patch didn't solve this problem. I asked once on
-questions if anybody had similar experience, and got no replies. Anyone
here knows what's going on?

Thanks for the patch anyhow. I'm sure it will turn out to be useful
someday. When I first installed FreeBSD I spent a month (!) trying to
figure out why it always hangs, until I've heard of the CMD640 problem.
It's comforting to know no new users will have to go through that again.

Nadav


From owner-freebsd-hackers  Tue Feb  4 11:33:48 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA07043
          for hackers-outgoing; Tue, 4 Feb 1997 11:33:48 -0800 (PST)
Received: from darkstar (dialin2.anlw.anl.gov [141.221.252.102])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA07038
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 11:33:42 -0800 (PST)
Received: (from cmott@localhost) by darkstar (8.6.12/8.6.12) id MAA09041; Tue, 4 Feb 1997 12:33:17 -0700
Date: Tue, 4 Feb 1997 12:33:16 -0700 (MST)
From: Charles Mott <cmott@srv.net>
X-Sender: cmott@darkstar
To: Eivind Eklund <eivind@dimaga.com>
cc: Brian Somers <brian@awfulhak.demon.co.uk>,
        Ari Suutari <ari.suutari@ps.carel.fi>, hackers@freebsd.org,
        brian@utell.co.uk
Subject: Re: Single socket version of natd 
In-Reply-To: <3.0.32.19970204194456.00bbae30@dimaga.com>
Message-ID: <Pine.BSF.3.91.970204115817.9014A-100000@darkstar>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> My concern is that I should be able to make all users on the LAN (all of
> them have access to setting up a PPP connection) remember to enable
> aliasing.  If I had not wanted it in all cases, I'd just drop putting the
> command in the config file.  Nothing lost in my case, at least.
> 
> However, a way of giving the user 100% control again might be to add a
> -noalias keyword to completely block packet aliasing.  This would take one
> more bit from mode in IIJ-PPP, though.  Besides, as an admin I'm not
> certain I would want the users to have that control.
> 

I agree that a -noalias keyword is a not a good idea. 

The way Eivind is doing things sounds good to me.  The "out-of-the-box" 
software for home users will be simple to set up and have standard
defaults that do not typically have to be changed, but there will also be
a level of control that an admin wants. 


Charles Mott

From owner-freebsd-hackers  Tue Feb  4 11:53:37 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA08260
          for hackers-outgoing; Tue, 4 Feb 1997 11:53:37 -0800 (PST)
Received: from mole.mole.org (marmot.mole.org [204.216.57.191])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA08254
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 11:53:33 -0800 (PST)
Received: (from mail@localhost) by mole.mole.org (8.6.12/8.6.12) id TAA06309; Tue, 4 Feb 1997 19:53:20 GMT
Received: from meerkat.mole.org(206.197.192.110) by mole.mole.org via smap (V1.3)
	id sma006305; Tue Feb  4 19:53:02 1997
Received: (from mrm@localhost) by meerkat.mole.org (8.6.11/8.6.9) id LAA29465; Tue, 4 Feb 1997 11:52:03 -0800
Date: Tue, 4 Feb 1997 11:52:03 -0800
From: "M.R.Murphy" <mrm@Mole.ORG>
Message-Id: <199702041952.LAA29465@meerkat.mole.org>
To: terry@lambert.org
Subject: Re: bisdn
Cc: hackers@freebsd.org
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> From owner-freebsd-hackers@freefall.freebsd.org Tue Feb  4 11:46:59 1997
> From: Terry Lambert <terry@lambert.org>
> Subject: Re: bisdn
> To: michaelh@cet.co.jp (Michael Hancock)
> Date: Tue, 4 Feb 1997 11:53:48 -0700 (MST)
> Cc: grog@lemis.de, terry@lambert.org, hackers@freebsd.org
>
> > > > Basic rate:	2B+D
> > > 
> > > OK.  Note the second question: what do you do with them?
> > > 
> > > > US West:	2D+B
> > > 
> > > Really?  I find that hard to believe.  I suppose the question is
> > > doubly relevant here: What do you do with them?
> > 
> > I find this hard to believe too, 2D channels is wierd.  The D-channel is
> > for out-of-band signaling.  It's why you get 64K instead of 56K. 
>
> See www.uswest.com.
>

>From http://www.uswest.com/atwork/interprise/isdn/isdn_htm/isdn_s2.html

  The architecture of Single Line Service can be expressed as 2B+D
  -- in other words, two B (or Bearer) channels plus one D
     (or Delta) channel.

Where'd you get the reference to 2D+B?

--
Mike Murphy  mrm@Mole.ORG  +1 619 598 5874
Better is the enemy of Good

From owner-freebsd-hackers  Tue Feb  4 11:57:07 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA08486
          for hackers-outgoing; Tue, 4 Feb 1997 11:57:07 -0800 (PST)
Received: from sax.sax.de (sax.sax.de [193.175.26.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA08476
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 11:56:53 -0800 (PST)
Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA12799; Tue, 4 Feb 1997 20:56:33 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id UAA28710; Tue, 4 Feb 1997 20:45:27 +0100 (MET)
Message-ID: <Mutt.19970204204527.j@uriah.heep.sax.de>
Date: Tue, 4 Feb 1997 20:45:27 +0100
From: j@uriah.heep.sax.de (J Wunsch)
To: Ilmar_Habibulin@p777.f691.n5020.z2.fidonet.org (Ilmar Habibulin)
Cc: hackers@freebsd.org
Subject: Re: Need some help or advice
References: <32F6F8D2@gate.phantom.ru>
X-Mailer: Mutt 0.55-PL10
Mime-Version: 1.0
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <32F6F8D2@gate.phantom.ru>; from Ilmar Habibulin on Feb 3, 1997 21:36:12 +0300
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

As Ilmar Habibulin wrote:

> Where can i find information of kernel internals such as processes and 
> user credits, IPC, VOP_ stuff, v-nodes and its relations with i-nodes, the 
> most complete info on how does this thing works inside.
> 
> I'll want to buy a book "4.4BSD design and implementation". Is it enough?

I think that's at the very least a good start.

We've also started to document kernel internal APIs, in section 9 of
the manual.  But it's still only sparsely populated.

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

From owner-freebsd-hackers  Tue Feb  4 12:04:53 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA08849
          for hackers-outgoing; Tue, 4 Feb 1997 12:04:53 -0800 (PST)
Received: from mailhost2.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA08837
          for <freebsd-hackers@freebsd.org>; Tue, 4 Feb 1997 12:04:47 -0800 (PST)
Received: from ns1.BayNetworks.COM ([134.177.1.107]) 
	by mailhost2.BayNetworks.COM (8.8.5/BNET-96/12/06-E) with ESMTP
	id MAA07673; Tue, 4 Feb 1997 12:01:57 -0800 (PST)
	for <freebsd-hackers@freebsd.org>
Received: from pobox.engeast.BayNetworks.COM (pobox.corpeast.baynetworks.com [192.32.151.199]) 
	by ns1.BayNetworks.COM (8.8.3/BNET-97/01/07-I) with ESMTP
	id MAA07252; Tue, 4 Feb 1997 12:04:12 -0800 (PST)
	for <freebsd-hackers@freebsd.org>
Posted-Date: Tue, 4 Feb 1997 12:04:12 -0800 (PST)
Received: from tuva.engeast.baynetworks.com (tuva [192.32.180.119])
	by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-SVR4-S) with ESMTP
	id PAA25822; Tue, 4 Feb 1997 15:04:14 -0500
	for <freebsd-hackers@freebsd.org>
Received: from tuva.engeast.baynetworks.com (localhost [127.0.0.1]) by tuva.engeast.baynetworks.com (8.7.5/8.7.3) with ESMTP id PAA05554 for <freebsd-hackers@freebsd.org>; Tue, 4 Feb 1997 15:04:13 -0500 (EST)
Message-Id: <199702042004.PAA05554@tuva.engeast.baynetworks.com>
X-Mailer: exmh version 1.6.9 8/22/96
To: freebsd-hackers@freebsd.org
Subject: 2.1.6 -- AMD still broken?
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 04 Feb 1997 15:04:13 -0500
From: Robert Withrow <bwithrow@BayNetworks.COM>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

It seems like AMD/NFS is still broken in 2.1.6 in the same way
in 2.1.5 and 2.1.  There were patches available for 2.1 that I
thought would make it into 2.1.5, and patches for 2.1.5 that
I was sure would make it into 2.1.6.  Alas, no.

Does anyone have patches for NFS in 2.1.6 that make AMD direct
mounts work?

Thanks.

-- 
Robert Withrow -- (+1 508 436 8256)
BWithrow@BayNetworks.com



From owner-freebsd-hackers  Tue Feb  4 12:25:34 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA09946
          for hackers-outgoing; Tue, 4 Feb 1997 12:25:34 -0800 (PST)
Received: from jason.garman.net (pm106-00.dialip.mich.net [192.195.231.202])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA09935
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 12:25:29 -0800 (PST)
Received: (qmail 2801 invoked by uid 1000); 4 Feb 1997 20:25:25 -0000
Message-ID: <Mutt.19970204152524.garman@jason.garman.net>
Date: Tue, 4 Feb 1997 15:25:24 -0500
From: garman@jason.garman.net (Jason Garman)
To: nadav@cs.technion.ac.il (Nadav Eiron)
Cc: helbig@BA-Stuttgart.De (Wolfgang Helbig), hackers@freebsd.org
Subject: Re: CMD640b flaw workaround
References: <199702040835.JAA26420@amadeus.informatik.ba-stuttgart.de> <Pine.GSO.3.95-heb-2.07.970204210307.29771A-100000@csd>
X-Mailer: Mutt 0.58
Mime-Version: 1.0
Reply-To: garman@phs.k12.ar.us
X-Phase-Of-Moon: The Moon is Waning Crescent (12% of Full)
X-Operating-System: FreeBSD/i386 2.1.5-RELEASE
In-Reply-To: <Pine.GSO.3.95-heb-2.07.970204210307.29771A-100000@csd>; from Nadav Eiron on Feb 4, 1997 21:09:42 +0200
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Nadav Eiron writes:
> I tried installing the patches on my troubled 2.1.5R system, and it
> doesn't cure my problem. I think I should describe my problem once again,
> as it's not the classical CMD640 bug. I have a machine with a hard disk
> (Quantum FireBall) and a CD (Creative x4), both on the primary channel.
> The problem is that CD access is unreliable. It's most commonly seen when
> I try to serve a CD directly via apache. Under heavy load, some of the
> Apace processes will hang while accessing the CD like so:
> 
That's weird.  You're right, the patch won't fix this.  I have a CD and hd
on my first channel, and it works fine here...

I know this isn't a really good `solution,' but how about switching the cd
onto the second channel?

Enjoy,
-- 
Jason Garman                             http://www.nesc.k12.ar.us/~garman/
Student, Eleanor Roosevelt High School                 garman@phs.k12.ar.us

From owner-freebsd-hackers  Tue Feb  4 14:32:54 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA18794
          for hackers-outgoing; Tue, 4 Feb 1997 14:32:54 -0800 (PST)
Received: from sax.sax.de (sax.sax.de [193.175.26.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA18779
          for <freebsd-hackers@freebsd.org>; Tue, 4 Feb 1997 14:32:47 -0800 (PST)
Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA21548; Tue, 4 Feb 1997 23:32:27 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id VAA29001; Tue, 4 Feb 1997 21:36:51 +0100 (MET)
Message-ID: <Mutt.19970204213651.j@uriah.heep.sax.de>
Date: Tue, 4 Feb 1997 21:36:51 +0100
From: j@uriah.heep.sax.de (J Wunsch)
To: jhay@zibbi.mikom.csir.co.za (John Hay)
Cc: logue@engr.orst.edu (Steve Logue), stenn@whimsy.udel.edu,
        freebsd-hackers@freebsd.org
Subject: Re: xntp3-5.89.2 & FreeBSD 2.2-GAMMA won't compile
References: <32F7097D.41C67EA6@engr.orst.edu> <199702041034.MAA13094@zibbi.mikom.csir.co.za>
X-Mailer: Mutt 0.55-PL10
Mime-Version: 1.0
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <199702041034.MAA13094@zibbi.mikom.csir.co.za>; from John Hay on Feb 4, 1997 12:34:18 +0200
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

As John Hay wrote:

(xtnp problems)

> I have fixed it in FreeBSD-current, but weren't sure if it should go into
> 2.2. Any opinions anyone?

> If somebody from the 2.2 release team give the go-ahead I would be
> happy to put it in 2.2.

Barring any objections from other partys in say, the next couple of
days, go ahead.  (Do you know how to do branch commits?)

Please, see also PR # bin/2469.  I think the designated solution to
the problem was to introduce a LOG_NTP facility.  Somebody needs to
track this, or it will be forgotten.  (I really need it, right now,
i've hacked xntpd locally to log the annoying messages at LOG_DEBUG
level.)

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

From owner-freebsd-hackers  Tue Feb  4 14:35:21 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA18968
          for hackers-outgoing; Tue, 4 Feb 1997 14:35:21 -0800 (PST)
Received: from sax.sax.de (sax.sax.de [193.175.26.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA18962
          for <freebsd-hackers@FreeBSD.org>; Tue, 4 Feb 1997 14:35:18 -0800 (PST)
Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA21630; Tue, 4 Feb 1997 23:35:10 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id WAA29207; Tue, 4 Feb 1997 22:58:53 +0100 (MET)
Message-ID: <Mutt.19970204225853.j@uriah.heep.sax.de>
Date: Tue, 4 Feb 1997 22:58:53 +0100
From: j@uriah.heep.sax.de (J Wunsch)
To: freebsd-hackers@FreeBSD.org
Cc: jlk@pavilion.co.uk (Josef Karthauser)
Subject: Re: probing scsi bus after boot?
References: <199611011028.FAA07666@hda.hda.com> <199702041814.SAA00858@deputy.pavilion.co.uk>
X-Mailer: Mutt 0.55-PL10
Mime-Version: 1.0
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <199702041814.SAA00858@deputy.pavilion.co.uk>; from Josef Karthauser on Feb 4, 1997 18:14:48 +0000
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

As Josef Karthauser wrote:

> Either I use rmt, but I've not found a way of rmt'ing as root on the
> remote site (please someone let me out of my misery.)

~root/.rhost

It would be neat to see ssh support for this, though.

> 	# scsi -f /dev/rst0 -p
> 	scsi: unable to open device /dev/rst0: Device not configured

Chicken-and-egg problem.  Don't use -p btw., use -r.  But still, you
need at least one device that has been successfully probed on your
SCSI bus before, in order to hook the `rescan' ioctl into the kernel
(any device fits, so you could pick /dev/rsd0.ctl).

NB: this used to hang your machine with various SCSI adapters in the
past, but recent 2.2 (and -current) systems seem to work well with it.

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

From owner-freebsd-hackers  Tue Feb  4 14:44:34 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA19380
          for hackers-outgoing; Tue, 4 Feb 1997 14:44:34 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA19375
          for <hackers@freefall.freebsd.org>; Tue, 4 Feb 1997 14:44:31 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA13265; Tue, 4 Feb 1997 15:41:33 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702042241.PAA13265@phaeton.artisoft.com>
Subject: Re: kernel malloc options
To: kish@browncow.com (Bill Kish)
Date: Tue, 4 Feb 1997 15:41:33 -0700 (MST)
Cc: hackers@freefall.freebsd.org
In-Reply-To: <199702031942.OAA18041@browncow.com> from "Bill Kish" at Feb 3, 97 02:42:02 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>  Currently, I'm malloc()ing these structures as needed using the
> following parameters:
> 
>  malloc((u_long)sizeof(*conxn), M_TEMP, M_NOWAIT)
> 
>  This appears to work fine in my initial lightly loaded tests,
> however, I'm concerned about what will happen when the system is under
> heavy load. I have the following questions and would appreciate any
> advice offered!
> 
>  1) Is malloc() a reasonable allocator for small highly dynamic
>    objects?

No.  Establish a freelist.

>  2) Is M_TEMP a good choice? Does it make a difference?

Not if there is a high turnover, or sporadic growth/decline in
usage over a short time.  You should establish a new pool ID;
probably, we should establish a mechanism for allocating pools,
and preallocate the ones with mainifest constants to match the
constants, and then let users deal with them from there (ie: you
would not be guaranteed initialization order, so you would have
to code your stuff to use an integer instead of a constant, and
eat whatever overhead that caused).

>  3) Are there any config options that affect the amount of pinned
>     kernel memory available for malloc? The system will be doing
>     little else besides dealing with these packets...

John or David would have to answer this... I believe, though, that
the kernel address space is fixed.  The amount of pinned memory
would depend on the physical backing stor, and how much fragmentation
exists at the time you ask (I think).


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Tue Feb  4 14:55:03 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA19793
          for hackers-outgoing; Tue, 4 Feb 1997 14:55:03 -0800 (PST)
Received: from spoon.beta.com (root@[199.165.180.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA19785;
          Tue, 4 Feb 1997 14:54:59 -0800 (PST)
Received: from spoon.beta.com (mcgovern@localhost [127.0.0.1]) by spoon.beta.com (8.8.4/8.6.9) with ESMTP id RAA02641; Tue, 4 Feb 1997 17:54:56 -0500 (EST)
Message-Id: <199702042254.RAA02641@spoon.beta.com>
To: questions@freebsd.org, hackers@freebsd.org
Subject: Cyclades driver causes kernel panic
Date: Tue, 04 Feb 1997 17:54:56 -0500
From: "Brian J. McGovern" <mcgovern@spoon.beta.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Well, its back, and I'm pulling my hair out of my head. It appears
that on HPs, Dells, Eclipse machines, and a handful of others,
the Cyclades driver causes a RAM parity error, causing the kernel
to panic, and the system to reboot. I've sen this on at least
a half dozen systems. And I've found about two that work.

Has anyone seen this? Worked around it? I'm kind of at a crunch
to get some multi-port serial cards working, and I could use all
the help I can get.

The machines are HP 586/133s and 166s. The dells are Dell 586/100s. The
only machine I've see it work in for any length of time was a AMD clone 586/100.

I don't think its a RAM parity error, simply because a half-dozen
machines with EDO Ram can't all be wrong (or i'd see it elsewhere),
and the DOS drivers tend to get the card up and working on multiple
ports with no problems.

Any suggestions?
	-Brian

From owner-freebsd-hackers  Tue Feb  4 15:04:05 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA20383
          for hackers-outgoing; Tue, 4 Feb 1997 15:04:05 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA20349
          for <hackers@FreeBSD.ORG>; Tue, 4 Feb 1997 15:04:00 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA13316; Tue, 4 Feb 1997 16:01:22 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702042301.QAA13316@phaeton.artisoft.com>
Subject: Re: g++, STL and -frepo on FreeBSD-2.2-Beta
To: jmacd@CS.Berkeley.EDU (Josh MacDonald)
Date: Tue, 4 Feb 1997 16:01:22 -0700 (MST)
Cc: hackers@FreeBSD.ORG
In-Reply-To: <199702040559.VAA08584@paris.CS.Berkeley.EDU> from "Josh MacDonald" at Feb 3, 97 09:59:35 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > Clearly, the template class definition
> > 
> > 	template <class Type>
> > 	class list ... {
> > 		...
> > 	};
> > 
> > is not in scope.  The header files you have included are apparently
> > not sufficient.
> > 
> > Perhaps you meant "List" instead of "list"???
> 
> Clearly, you have no idea what you're talking about.  You should be a 
> bit more careful with your use of "clearly", it makes me wonder how
> much of the rest of your mail to this list (which I rarely understand)
> is correct.

If the linker can not resolve the symbol, the symbol:

A)	Is not in scope
B)	Is not there, period
C)	Was not created in scope because you want the linker to
	"magically" share template implementation between class
	specific template instantiations.

If you want the linker to "magically" share template implementations
by providing cast stub headers and passing around void pointers so
you don't have to actually reimplemnt the code...

Well, it's won't do it.  This is a new thing, and the a.out linker
is not being actively maintained.

As people pointed out in other responses, you can download John
Polstra's "ELFKit" and use it instead of the FreeBSD default a.out
g++ compiler and linker, and it will then work.

If you want it to work with the current code, you need to define the
template class in scope before you use it so that the functions
are actually statically instantiated in the module where they are
declaratively referenced.  This is because historically, the template
implementations have not been shared betwen class types.


					Regards,
					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Tue Feb  4 15:11:02 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA21318
          for hackers-outgoing; Tue, 4 Feb 1997 15:11:02 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA21296
          for <freebsd-hackers@FreeBSD.org>; Tue, 4 Feb 1997 15:10:54 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA13339; Tue, 4 Feb 1997 16:06:53 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702042306.QAA13339@phaeton.artisoft.com>
Subject: Re: NIS/uids
To: branson.matheson@ferginc.com
Date: Tue, 4 Feb 1997 16:06:53 -0700 (MST)
Cc: W.Belgers@nl.cis.philips.com, freebsd-hackers@FreeBSD.org
In-Reply-To: <Pine.BSF.3.91.970204090156.19773L-100000@toth.hq.ferg.com> from "Branson Matheson" at Feb 4, 97 09:42:54 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> > The problem now is that the security on my system has become dependant
> > on that of the NIS server. If I am root on the NIS server I can change
> > the uid of "user" into any user including root and make use of it on my
> > system. Even if you can only become root using su you can easily first
> > become a user in wheel and then root.
> 
>  That is a fact.  because you are using that information from an NIS
>  server, you will _always_ have a security risk from that server. 
>  Anyone that has root on that server can modify a yp'd entry on that
>  server, change the uid to 0 and become root on your system very
>  easily. So by definition, you _have_ to trust your yp servers. 

Yes.  You have established a trust relationship within a "secure zone",
and you have *defined* the NIS client and server to both be inside this
zone.

However...

It makes sense to me that "sensitive" user and group ID's perhaps
should not be honored when they come in via NFS... ie: user root
or bin, etc., or group bin or kmem.

The problem is that there is no tag you can specify to indicate
to NFS which user or group ID's are "sensitive", and which are not.

This would provide NIS honoring protection similar to NFS not
honoring "root" from a "semi-trusted" host.


					Regards,
					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Tue Feb  4 15:30:39 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA23884
          for hackers-outgoing; Tue, 4 Feb 1997 15:30:39 -0800 (PST)
Received: from po2.glue.umd.edu (root@po2.glue.umd.edu [129.2.128.45])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA23879
          for <hackers@FreeBSD.ORG>; Tue, 4 Feb 1997 15:30:34 -0800 (PST)
Received: from baud.eng.umd.edu (baud.eng.umd.edu [129.2.98.183]) by po2.glue.umd.edu (8.8.5/8.7.3) with ESMTP id SAA05531; Tue, 4 Feb 1997 18:30:22 -0500 (EST)
Received: from localhost (chuckr@localhost) by baud.eng.umd.edu (8.8.5/8.7.3) with SMTP id SAA01181; Tue, 4 Feb 1997 18:30:21 -0500 (EST)
X-Authentication-Warning: baud.eng.umd.edu: chuckr owned process doing -bs
Date: Tue, 4 Feb 1997 18:30:21 -0500 (EST)
From: Chuck Robey <chuckr@glue.umd.edu>
X-Sender: chuckr@baud.eng.umd.edu
To: Terry Lambert <terry@lambert.org>
cc: Josh MacDonald <jmacd@CS.Berkeley.EDU>, hackers@FreeBSD.ORG
Subject: Re: g++, STL and -frepo on FreeBSD-2.2-Beta
In-Reply-To: <199702042301.QAA13316@phaeton.artisoft.com>
Message-ID: <Pine.OSF.3.95q.970204182559.1349A-100000@baud.eng.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Tue, 4 Feb 1997, Terry Lambert wrote:

> > > Clearly, the template class definition
> > > 
> > > 	template <class Type>
> > > 	class list ... {
> > > 		...
> > > 	};
> > > 
> > > is not in scope.  The header files you have included are apparently
> > > not sufficient.
> > > 
> > > Perhaps you meant "List" instead of "list"???
> > 
> > Clearly, you have no idea what you're talking about.  You should be a 
> > bit more careful with your use of "clearly", it makes me wonder how
> > much of the rest of your mail to this list (which I rarely understand)
> > is correct.
> 
> If the linker can not resolve the symbol, the symbol:
> 
> A)	Is not in scope
> B)	Is not there, period
> C)	Was not created in scope because you want the linker to
> 	"magically" share template implementation between class
> 	specific template instantiations.

I'm not sure this is apropos, but maybe... while I was porting
octave-2.0.1, I had a lot of trouble with template functions that were
compiled -fno-external-templates.  Seems like the virtual tables were
being created as local symbols only, so no other functions compiled in
other files could see the tables.  I ended up having to remove the
-fno-external-templates from every file that used the tables, so they'd
instantiate their own virtual tables.  Made the code size larger, but I
couldn't find a way to fix it.  Neither could JW Eaton, Octave's author,
who worked with me for a while.

The problem has been papered over, but not fixed.  Is this possibly
something like you're discussing above?

----------------------------+-----------------------------------------------
Chuck Robey                 | Interests include any kind of voice or data 
chuckr@eng.umd.edu          | communications topic, C programming, and Unix.
9120 Edmonston Ct #302      |
Greenbelt, MD 20770         | I run Journey2 and picnic, both FreeBSD
(301) 220-2114              | version 3.0 current -- and great FUN!
----------------------------+-----------------------------------------------


From owner-freebsd-hackers  Tue Feb  4 15:30:49 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA23910
          for hackers-outgoing; Tue, 4 Feb 1997 15:30:49 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA23902
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 15:30:47 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA13402; Tue, 4 Feb 1997 16:28:23 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702042328.QAA13402@phaeton.artisoft.com>
Subject: Re: bisdn
To: grog@lemis.de
Date: Tue, 4 Feb 1997 16:28:23 -0700 (MST)
Cc: terry@lambert.org, hackers@freebsd.org
In-Reply-To: <199702041857.TAA15699@freebie.lemis.de> from "Greg Lehey" at Feb 4, 97 07:57:33 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> >>>>   Oh really?  Do you get D channels?  What do you do with them?
> >>>
> >>>  Basic rate:	2B+D
> >>
> >>  OK.  Note the second question: what do you do with them?
> >>
> >>>  US West:	2D+B
> >>
> >>  Really?  I find that hard to believe.  I suppose the question is
> >>  doubly relevant here: What do you do with them?
> >
> > Heh.  Nothing.  We avoid buying them and complain bitterly about
> > the lack of ISP Frame Relay support in the area, mostly.
> 
> Speak for yourself.  Plenty of people in the USA use ISDN.  And while
> you're at it, how about admitting (like other people do from time to
> time) that you screwed up?

Please see the list archives.  I've probably admitted to screwing
up, when I do it, more than any other poster to these lists.  I
simply don't have an emotional investment in always being right.
You'll also notice that I don't take attacks on instances of my
code as attacks on me personally (though style issues, which I
believe are irrelevant, and the values of the ideas which the code
embodies, are different matters -- I don't care how an idea is
implemented, as long as it's The Right Idea being implemented).

Now please read my followup refuting the ability to actually *get*
ISDN, as opposed to getting a *description* of ISDN from a company
that doesn't actually *provide* ISDN.  Feel free to contact US West;
I live in the 795 prefix, which is not attached to the single 5ESS
in Tucson.  If you can get me real ISDN, I will be happy to buy it
from them.  But you can't, because I can't, because they can't.


					Regards,
					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Tue Feb  4 15:35:48 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA24192
          for hackers-outgoing; Tue, 4 Feb 1997 15:35:48 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA24185
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 15:35:45 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA13439; Tue, 4 Feb 1997 16:32:03 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702042332.QAA13439@phaeton.artisoft.com>
Subject: Re: bisdn
To: mrm@Mole.ORG (M.R.Murphy)
Date: Tue, 4 Feb 1997 16:32:03 -0700 (MST)
Cc: terry@lambert.org, hackers@freebsd.org
In-Reply-To: <199702041952.LAA29465@meerkat.mole.org> from "M.R.Murphy" at Feb 4, 97 11:52:03 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > See www.uswest.com.
> 
> From http://www.uswest.com/atwork/interprise/isdn/isdn_htm/isdn_s2.html
> 
>   The architecture of Single Line Service can be expressed as 2B+D
>   -- in other words, two B (or Bearer) channels plus one D
>      (or Delta) channel.
> 
> Where'd you get the reference to 2D+B?

>From the US West sales representative in Tucson, Arizona, who stated I
could not get 2B+D.

Look, this is not a discussion I want to have on this list.  US West
Interact Service, where they are available, implement their Internet
connections using FreeBSD systems.

Suffice it to say that they sell real 2B+D in a few places, but they
don't sell it in any exchange I've ever had a phone.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Tue Feb  4 15:56:51 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA25233
          for hackers-outgoing; Tue, 4 Feb 1997 15:56:51 -0800 (PST)
Received: from spoon.beta.com (root@[199.165.180.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA25224
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 15:56:47 -0800 (PST)
Received: from spoon.beta.com (mcgovern@localhost [127.0.0.1]) by spoon.beta.com (8.8.4/8.6.9) with ESMTP id SAA02856; Tue, 4 Feb 1997 18:56:08 -0500 (EST)
Message-Id: <199702042356.SAA02856@spoon.beta.com>
To: "John S. Dyson" <toor@dyson.iquest.net>
cc: hackers@freebsd.org, questions@freebsd.orgb
Subject: Re: Cyclades driver causes kernel panic (more info) 
In-reply-to: Your message of "Tue, 04 Feb 1997 18:50:37 EST."
             <199702042350.SAA06377@dyson.iquest.net> 
Date: Tue, 04 Feb 1997 18:56:08 -0500
From: "Brian J. McGovern" <mcgovern@spoon.beta.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Just a couple of FYI's I think I may have left out. Firstly, these are the PCI
version cards. Secondly, it appears (having thought more on the drive
home) that the delimitation between 'works' and 'doesnt work' seems to be
around the 16MB barrier (for instance, my home pentium, were it does work,
is a P100 that reports (between base and XMS) just _UNDER 16MB_. I'm assuming
its due to the fact that its remapping part of it for other uses. All
the machines that don't seem to work have more (usually 32+MB), or report
16MB on startup (doesn't seem to remap memory). Then again, this could be
hogwash.
	-Brian

From owner-freebsd-hackers  Tue Feb  4 16:07:59 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id QAA25901
          for hackers-outgoing; Tue, 4 Feb 1997 16:07:59 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id QAA25882;
          Tue, 4 Feb 1997 16:07:55 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA13528; Tue, 4 Feb 1997 17:05:28 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702050005.RAA13528@phaeton.artisoft.com>
Subject: Re: g++, STL and -frepo on FreeBSD-2.2-Beta
To: chat@freebsd.org
Date: Tue, 4 Feb 1997 17:05:28 -0700 (MST)
Cc: jmacd@CS.Berkeley.EDU, hackers@freebsd.org
In-Reply-To: <199702041516.KAA08583@chai.plexuscom.com> from "Bakul Shah" at Feb 4, 97 10:16:25 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Since Terry responded to something I had posted, I feel obliged to
> respond.
> 
> His use of `clearly' made his erroneous response a bit amusing so I
> didn't mind it at all!  Terry made a mistake.  Big deal.  We all do
> (like my mixing up his response with someone else's).

Urg.  As always, if it can be proven to my satisfaction that I have
actually made a mistake, I will post a retraction; now you have me
wondering, since you are generally reliable as a sanity-check... 8-(.

Are you saying that there is a condition in which the linker
will not be able to find a symbol that is really there?  I was
under the impression that if the template declaration was in
scope, the function implementation would be instanced in scope:

	"C++ Primer Plus, Second Edition"
	Stephan Prata
	_Waite Group Press_
	ISBN 1-878739-74-3

	Pg. 580

	Templates provide _parameterized types_, that is, the
	capability of passing a type name as an argument to an
	algorithm for building a class or a function.  By feeding
	the type name _int_ into a queue template, for example,
	you can get the compiler to construct a queue class for
	queueing _int_s.

Note: ..."get _the compiler_ <emphasis mine> to construct a queue
class"...

	Pg. 581

	When a template is invoked, _Type_ will be replaced with
	a specific type value, such as _int_ or _String_.

I was under the impression that "invocation" was not possible at
runtime.  If it were possible (it is, in theory, if you pass
around void instances of the object and explicity invoke the copy
constructors, etc., of the base type), it would require a working
RTTI implementation, IMO, as well as the cooperation of the linker,
aw well as compiler cooperation in treating a template definition
as a two pass declaration, since RTTI only works for classes with
pure virtual functions.  The compiler would have to implictly
provide it's own abstract interface type.

	Pg. 582

	Because the templates aren't functions, they can't be
	compiled seperately.  Templates have to be used in
	conjunction with requets for particular instantiations
	of templates.  The simplest way to make this work is to
	place all of the template information in a header file
	and to include the header file in the file that will use
	the templates.

Which would, of course, cause the template definition to be in
scope at the time the instantiation occurs, causing (in the base
case) an _actualization_ (also Pg. 582) of the template to be
created in scope at compile time.

Now unless the compiler is performing some form of "Type" magic,
where it converts references to pointers and provides a stub
class for you, and casts to void for a singe instantiation of
a given template class, I don't think I've made a mistake.

If it is, tell me, and I will admit the mistake.  Then I will
point out that this probably requires the cooperation of the
linker, and that the FreeBSD a.out linker is not being (very)
actively maintained... and, as was pointed out, it works with
John Polstra's "ELFKit"... consider upgrading.  Otherwise, it's
unreasonable to expect the "magic" to work elsewhere, so it's
poor style, no matter how you cut it.


> The bad news is that it segfaults on even simple Verilog
> module definitions.  So for now this mini project has been ^Z'ed
> (put on hold).  Thanks to all the people who responded with helpful
> hints (even if wrong:-).

I have been implementing COM and DCOM objects using pure abstract
virtual base classes for interface definitions, using the FreeBSD g++
compiler in -current.  If you could give a code fragment which
triggers the error, I might be able to help out.


					Regards,
					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Tue Feb  4 16:22:09 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id QAA26997
          for hackers-outgoing; Tue, 4 Feb 1997 16:22:09 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id QAA26989
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 16:22:05 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA13562; Tue, 4 Feb 1997 17:19:10 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702050019.RAA13562@phaeton.artisoft.com>
Subject: Re: g++, STL and -frepo on FreeBSD-2.2-Beta
To: chuckr@glue.umd.edu (Chuck Robey)
Date: Tue, 4 Feb 1997 17:19:09 -0700 (MST)
Cc: terry@lambert.org, jmacd@CS.Berkeley.EDU, hackers@freebsd.org
In-Reply-To: <Pine.OSF.3.95q.970204182559.1349A-100000@baud.eng.umd.edu> from "Chuck Robey" at Feb 4, 97 06:30:21 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> I'm not sure this is apropos, but maybe... while I was porting
> octave-2.0.1, I had a lot of trouble with template functions that were
> compiled -fno-external-templates.  Seems like the virtual tables were
> being created as local symbols only, so no other functions compiled in
> other files could see the tables.  I ended up having to remove the
> -fno-external-templates from every file that used the tables, so they'd
> instantiate their own virtual tables.  Made the code size larger, but I
> couldn't find a way to fix it.  Neither could JW Eaton, Octave's author,
> who worked with me for a while.
> 
> The problem has been papered over, but not fixed.  Is this possibly
> something like you're discussing above?

I thought so; however, Bakul's recent post has me doubting my own
sanity.  I have replied to him, siting references, in case the g++
implementation does things differently.  If it does, I'll be happy
to admit my error.  If it doesn't, I'll still believe it's "Pilot
Error" causing the problem.

I'm pretty sure that external templates *can't* work as anything
other than code/class reinstantiations (to avoid static redeclaration,
like you describe).  I'm also pretty sure the a.out linker can't handle
agregating multiple instnatiations into a single interface.  ELF
could, though, because it could establish an identity tag for the
ELF segment based on the class derivation, and link only the first
segment with the tag into the resulting executable, throwing all
the others away.  Whether ELF actually *does* this is another matter,
since it would mean you effecitevly compile one source file into
several object files which you place in a single ELF file... then
link it.

The problem being discussed *seems* to me to be a case of where they
want only a single code instance for all template member functions,
regardless of the derived type.  In theory you can do this using
an RTTI implementation, but I'll be damned if anyone has built such
a thing yet (they'ed need the RTTI first, for starters).

Also, for certain, this would require some method of identifier
definition agregation, which I'm not sure it's even possible to do
without segment attribution.  Maybe you could discard duplicate
symbols, but I'm pretty sure the a.out linker is too stupid to
be able to discard *pieces* of object modules, since the addresses
are relative, and I don't believe the .o files build a proper
internal symbol dependency graph.

The short version is "you can't get there from here".  8-(.


					Regards,
					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Tue Feb  4 16:25:04 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id QAA27277
          for hackers-outgoing; Tue, 4 Feb 1997 16:25:04 -0800 (PST)
Received: from louie.udel.edu (louie.udel.edu [128.175.1.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id QAA27260
          for <freebsd-hackers@freebsd.org>; Tue, 4 Feb 1997 16:24:55 -0800 (PST)
Received: from snow-white.ee.udel.edu by louie.udel.edu id aa00375;
          4 Feb 97 19:05 EST
Received: from louie.udel.edu by snow-white.ee.udel.edu id aa23407;
          4 Feb 97 19:05 EST
To: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de>
cc: John Hay <jhay@zibbi.mikom.csir.co.za>, Steve Logue <logue@engr.orst.edu>,
        freebsd-hackers@freebsd.org
Subject: Re: xntp3-5.89.2 & FreeBSD 2.2-GAMMA won't compile 
In-reply-to: Your message of "Tue, 04 Feb 1997 21:36:51 +0100."
             <Mutt.19970204213651.j@uriah.heep.sax.de> 
Date: Tue, 04 Feb 1997 19:01:59 -0500
From: stenn@whimsy.udel.edu
Message-ID:  <9702041901.aa26048@whimsy.udel.edu>
Source-Info:  From (or Sender) name not authenticated.
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

It looks like I'll need to add this patch to the sys/timex.h file in the
xntpd distribution:

--- timex.h-	Sat Jul 15 04:06:10 1995
+++ timex.h	Sun Feb  2 02:56:21 1997
@@ -284,6 +284,17 @@
 };
 #ifdef __FreeBSD__
 
+/*
+ * sysctl identifiers underneath kern.ntp_pll
+ */
+#define NTP_PLL_GETTIME	1	/* used by ntp_gettime() */
+#define NTP_PLL_MAXID	2	/* number of valid ids */
+
+#define NTP_PLL_NAMES { \
+			  { 0, 0 }, \
+			  { "gettime", CTLTYPE_STRUCT }, \
+		      }
+
 #ifndef KERNEL
 #include <sys/cdefs.h>

Is there anything else I should add to the xntpd distribution to make
life easier for us?

Harlan

From owner-freebsd-hackers  Tue Feb  4 16:41:32 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id QAA29381
          for hackers-outgoing; Tue, 4 Feb 1997 16:41:32 -0800 (PST)
Received: from po2.glue.umd.edu (root@po2.glue.umd.edu [129.2.128.45])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA29370
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 16:41:27 -0800 (PST)
Received: from baud.eng.umd.edu (baud.eng.umd.edu [129.2.98.183]) by po2.glue.umd.edu (8.8.5/8.7.3) with ESMTP id TAA07225; Tue, 4 Feb 1997 19:40:52 -0500 (EST)
Received: from localhost (chuckr@localhost) by baud.eng.umd.edu (8.8.5/8.7.3) with SMTP id TAA00927; Tue, 4 Feb 1997 19:40:51 -0500 (EST)
X-Authentication-Warning: baud.eng.umd.edu: chuckr owned process doing -bs
Date: Tue, 4 Feb 1997 19:40:51 -0500 (EST)
From: Chuck Robey <chuckr@glue.umd.edu>
X-Sender: chuckr@baud.eng.umd.edu
To: Terry Lambert <terry@lambert.org>
cc: jmacd@CS.Berkeley.EDU, hackers@freebsd.org
Subject: Re: g++, STL and -frepo on FreeBSD-2.2-Beta
In-Reply-To: <199702050019.RAA13562@phaeton.artisoft.com>
Message-ID: <Pine.OSF.3.95q.970204193602.1349B-100000@baud.eng.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Tue, 4 Feb 1997, Terry Lambert wrote:

> > I'm not sure this is apropos, but maybe... while I was porting
> > octave-2.0.1, I had a lot of trouble with template functions that were
> > compiled -fno-external-templates.  Seems like the virtual tables were
> > being created as local symbols only, so no other functions compiled in
> > other files could see the tables.  I ended up having to remove the
> > -fno-external-templates from every file that used the tables, so they'd
> > instantiate their own virtual tables.  Made the code size larger, but I
> > couldn't find a way to fix it.  Neither could JW Eaton, Octave's author,
> > who worked with me for a while.
> > 
> > The problem has been papered over, but not fixed.  Is this possibly
> > something like you're discussing above?
> 
> I thought so; however, Bakul's recent post has me doubting my own
> sanity.  I have replied to him, siting references, in case the g++
> implementation does things differently.  If it does, I'll be happy
> to admit my error.  If it doesn't, I'll still believe it's "Pilot
> Error" causing the problem.

Terry, I'm not sure you're right.  The virtual tables show up (using nm on
the obj files) as "t" objects, not "T", meaning local text objects.  The
way I understand from JW Eaton, under Linux (where he wrote it natively)
the symbols in the obj files for these virtual tables instatiated for
templates are global, not local.  There is one of these tables made for
each template type, correctly, but they're coming up local.  This seems to
be to point to an error source in the compiler, not the linking process.

FWIW, the symbols make it into the library, but as local symbols, not
global.  Am I confused about this?

> I'm pretty sure that external templates *can't* work as anything
> other than code/class reinstantiations (to avoid static redeclaration,
> like you describe).  I'm also pretty sure the a.out linker can't handle
> agregating multiple instnatiations into a single interface.  ELF
> could, though, because it could establish an identity tag for the
> ELF segment based on the class derivation, and link only the first
> segment with the tag into the resulting executable, throwing all
> the others away.  Whether ELF actually *does* this is another matter,
> since it would mean you effecitevly compile one source file into
> several object files which you place in a single ELF file... then
> link it.

----------------------------+-----------------------------------------------
Chuck Robey                 | Interests include any kind of voice or data 
chuckr@eng.umd.edu          | communications topic, C programming, and Unix.
9120 Edmonston Ct #302      |
Greenbelt, MD 20770         | I run Journey2 and picnic, both FreeBSD
(301) 220-2114              | version 3.0 current -- and great FUN!
----------------------------+-----------------------------------------------


From owner-freebsd-hackers  Tue Feb  4 16:43:37 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id QAA29571
          for hackers-outgoing; Tue, 4 Feb 1997 16:43:37 -0800 (PST)
Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA29509
          for <freebsd-hackers@freebsd.org>; Tue, 4 Feb 1997 16:43:14 -0800 (PST)
Received: from awfulhak.demon.co.uk (localhost.coverform.lan [127.0.0.1]) by awfulhak.demon.co.uk (8.8.4/8.7.3) with ESMTP id XAA27675; Tue, 4 Feb 1997 23:42:21 GMT
Message-Id: <199702042342.XAA27675@awfulhak.demon.co.uk>
X-Mailer: exmh version 1.6.9 8/22/96
cc: Terry Lambert <terry@lambert.org>, dk+@ua.net, shocking@mailbox.uq.edu.au,
        freebsd-hackers@freebsd.org
Subject: Re: Setting MTU from userland ppp 
In-reply-to: Your message of "Thu, 30 Jan 1997 23:42:32 GMT."
             <199701302342.XAA20718@awfulhak.demon.co.uk> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 04 Feb 1997 23:42:21 +0000
From: Brian Somers <brian@awfulhak.demon.co.uk>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > > set mtu 576
> > > 
> > > in /etc/ppp/ppp.conf
> > > 
> > > works for me.
> > > 
> > > This would specify your _tranimission_ size.  To change it on the other
> > > side, change the other end's setup.
> > > 
> > > Don't use 256 as your MTU.  (violates the RFC)
> > 
> > Any chance of having the software *enforce* the RFC, then?
> 
> I'll have a look at the RFC.  It currently checks that 100 <= M[TR]U <= 2000.
> 

As Warner said, nothing about the MTU in the rfc.... I don't think there's
anything wrong with the way it is.
-- 
Brian <brian@awfulhak.demon.co.uk>, <brian@freebsd.org>
      <http://www.awfulhak.demon.co.uk/>
Don't _EVER_ lose your sense of humour....



From owner-freebsd-hackers  Tue Feb  4 17:02:50 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA03458
          for hackers-outgoing; Tue, 4 Feb 1997 17:02:50 -0800 (PST)
Received: from vdp01.vailsystems.com (root@vdp01.vailsystems.com [207.152.98.18])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA03439
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 17:02:46 -0800 (PST)
Received: from crocodile.vale.com (crocodile [204.117.217.147]) by vdp01.vailsystems.com (8.8.3/8.7.3) with ESMTP id TAA27004 for <hackers@freebsd.org>; Tue, 4 Feb 1997 19:02:45 -0600 (CST)
Received: from jaguar (jaguar.vale.com [204.117.217.146]) by crocodile.vale.com (8.8.3/8.7.3) with SMTP id TAA14910 for <hackers@freebsd.org>; Tue, 4 Feb 1997 19:02:44 -0600 (CST)
Message-ID: <32F7DC34.73D5@vailsys.com>
Date: Tue, 04 Feb 1997 19:02:44 -0600
From: Hal Snyder <hal@vailsys.com>
Reply-To: hal@vailsys.com
Organization: Vail Systems, Inc.
X-Mailer: Mozilla 3.0 (WinNT; I)
MIME-Version: 1.0
To: hackers@freebsd.org
Subject: ibcs2: Alarm clock?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Running the COFF binary of Sybase System 10.x isql on a FreeBSD 2.1.5-R
system with ibcs2 enabled causes the program to exit immediately (less
than 1/4 second) with
  Alarm clock

Any ideas?  Is ibcs2 networking binary compatibility a pipedream?

I can tell the program looks for a valid entry in $SYBASE/interfaces
because it will report an invalid server if one is specified that's not
in the interface file.

I'd *really* like to run Sybase client apps from FreeBSD instead of toy
OS's like NT and SCO.  :(

From owner-freebsd-hackers  Tue Feb  4 17:12:22 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA05282
          for hackers-outgoing; Tue, 4 Feb 1997 17:12:22 -0800 (PST)
Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA05259
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 17:12:16 -0800 (PST)
Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5])
          by mail.cdsnet.net (8.8.4/8.7.3) with SMTP id RAA12153
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 17:12:09 -0800 (PST)
Date: Tue, 4 Feb 1997 17:12:08 -0800 (PST)
From: Jaye Mathisen  <mrcpu@cdsnet.net>
To: hackers@freebsd.org
Subject: Something broke, and no idea where...
Message-ID: <Pine.NEB.3.95.970204170540.8451d-100000@mail.cdsnet.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk



I use feedinfo to keep track of some log files.  The box it was running on 
was a p120, using perl5.003, and 2.2 supped sometime in August.

feedinfo ran fine.

Taking the same script to my -current box, and with the same input,
same version of perl, results in Illegal division by zero.

For grins, I copied the old binaries and stuff to my box and ran them, and
it doesn't work either.  Copying my binaries from -current to the other
box has no effect, it works fine.

I realize this is not a very complete bug report, but if anybody has any
suspicions, I'd be interested.

There's no coredump, plenty of RAM, limits have been checked.  The only
difference between my box and the other besides OS version is that mine is
a P6 vs a P5-120.


From owner-freebsd-hackers  Tue Feb  4 17:19:58 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA06615
          for hackers-outgoing; Tue, 4 Feb 1997 17:19:58 -0800 (PST)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id RAA06558;
          Tue, 4 Feb 1997 17:19:45 -0800 (PST)
Received: from rover.village.org [127.0.0.1] 
	by rover.village.org with esmtp (Exim 0.56 #1)
	id E0vrw19-0000Ho-00; Tue, 4 Feb 1997 18:19:19 -0700
To: davidn@unique.usn.blaze.net.au (David Nugent)
Subject: Re: conditionally including <sys/param.h> 
Cc: obrien@NUXI.com (David O'Brien),
        freebsd-ports@freebsd.org (FreeBSD ports list), hackers@freebsd.org
In-reply-to: Your message of "Mon, 03 Feb 1997 14:27:17 +1100."
		<19970203142717.VR58445@usn.blaze.net.au> 
References: <19970203142717.VR58445@usn.blaze.net.au>  <199701280143.RAA06503@freefall.freebsd.org> <Pine.OSF.3.95q.970127210526.2115E-100000@uplink.eng.umd.edu> <19970202135048.PN07710@dragon.nuxi.com> 
Date: Tue, 04 Feb 1997 18:19:19 -0700
From: Warner Losh <imp@village.org>
Message-Id: <E0vrw19-0000Ho-00@rover.village.org>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <19970203142717.VR58445@usn.blaze.net.au> David Nugent writes:
: > "#if (defined(__unix__) || defined(unix))" was the best way to

#if (defined(unix) || defined(__unix__)) && !defined(USG)
#include <sys/param.h>
#endif

was how the discussion ended (at least in private mail), since USG was
defined on SYS V and SYS III systems *AND* usually you want to tell if
you are on a modern BSD system, so it doesn't hurt to exclude some SYS
V systems.

: I said exactly this some weeks back and was told I was wrong,
: contrary to my own experience of many years working with
: sysv r3's. Oh well. :-)

That's true.  I think I (mistakenly) told you that.

: svr4 apparently does have it, but not sysv before that. Most
: if not all of those do predefine unix or __unix__.

sysvr4 does have it, but nothing earlier.  Most V7 and later systems
define unix or __unix__.

Just my two cents (a little late) to the discussion.

Warner

From owner-freebsd-hackers  Tue Feb  4 17:20:50 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA06843
          for hackers-outgoing; Tue, 4 Feb 1997 17:20:50 -0800 (PST)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id RAA06771;
          Tue, 4 Feb 1997 17:20:34 -0800 (PST)
Received: from rover.village.org [127.0.0.1] 
	by rover.village.org with esmtp (Exim 0.56 #1)
	id E0vrw2G-0000I7-00; Tue, 4 Feb 1997 18:20:28 -0700
To: obrien@NUXI.com (David O'Brien)
Subject: Re: conditionally including <sys/param.h> 
Cc: freebsd-ports@freebsd.org (FreeBSD ports list), hackers@freebsd.org
In-reply-to: Your message of "Sun, 02 Feb 1997 13:50:48 PST."
		<19970202135048.PN07710@dragon.nuxi.com> 
References: <19970202135048.PN07710@dragon.nuxi.com>  <199701280143.RAA06503@freefall.freebsd.org> <Pine.OSF.3.95q.970127210526.2115E-100000@uplink.eng.umd.edu> 
Date: Tue, 04 Feb 1997 18:20:28 -0700
From: Warner Losh <imp@village.org>
Message-Id: <E0vrw2G-0000I7-00@rover.village.org>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <19970202135048.PN07710@dragon.nuxi.com> David O'Brien writes:
: to get a new cpp symbol added (like __44bsd__ or something).

This is a bad idea, since it has lost a lot of its potential meaning
with so many 44bsd derived systems that pick and chose between 4.4 and
4.4 Lite 2.

Warner

From owner-freebsd-hackers  Tue Feb  4 17:23:49 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA07224
          for hackers-outgoing; Tue, 4 Feb 1997 17:23:49 -0800 (PST)
Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA07214
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 17:23:45 -0800 (PST)
Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id LAA18295; Wed, 5 Feb 1997 11:48:39 +1030 (CST)
From: Michael Smith <msmith@atrad.adelaide.edu.au>
Message-Id: <199702050118.LAA18295@genesis.atrad.adelaide.edu.au>
Subject: Re: Cyclades driver causes kernel panic (more info)
In-Reply-To: <199702042356.SAA02856@spoon.beta.com> from "Brian J. McGovern" at "Feb 4, 97 06:56:08 pm"
To: mcgovern@spoon.beta.com (Brian J. McGovern)
Date: Wed, 5 Feb 1997 11:48:39 +1030 (CST)
Cc: toor@dyson.iquest.net, hackers@freebsd.org, questions@freebsd.orgb
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Brian J. McGovern stands accused of saying:
> Just a couple of FYI's I think I may have left out. Firstly, these are the PCI
> version cards. Secondly, it appears (having thought more on the drive
> home) that the delimitation between 'works' and 'doesnt work' seems to be
> around the 16MB barrier (for instance, my home pentium, were it does work,
> is a P100 that reports (between base and XMS) just _UNDER 16MB_. I'm assuming
> its due to the fact that its remapping part of it for other uses. All
> the machines that don't seem to work have more (usually 32+MB), or report
> 16MB on startup (doesn't seem to remap memory). Then again, this could be
> hogwash.

There was some chatter about this a while back.  Where do you have the 
memory aperture for the cards mapped?  Also make sure you have all the
'shadow' and 'cacheable' stuff turned off for the memory region(s) where
you have the cards mapped.

I also seem to recall a commit recently to do with the PCI Cyclades, but
I can't find it in the logs, so perhaps my brain is failing 8(

> 	-Brian

-- 
]] Mike Smith, Software Engineer        msmith@gsoft.com.au             [[
]] Genesis Software                     genesis@gsoft.com.au            [[
]] High-speed data acquisition and      (GSM mobile)     0411-222-496   [[
]] realtime instrument control.         (ph)          +61-8-8267-3493   [[
]] Unix hardware collector.             "Where are your PEZ?" The Tick  [[

From owner-freebsd-hackers  Tue Feb  4 17:30:38 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA08114
          for hackers-outgoing; Tue, 4 Feb 1997 17:30:38 -0800 (PST)
Received: from logues.rhn.orst.edu (logues.RHN.ORST.EDU [128.193.139.116])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA08105
          for <freebsd-hackers@freebsd.org>; Tue, 4 Feb 1997 17:30:35 -0800 (PST)
Received: from logues.rhn.orst.edu (localhost [127.0.0.1])
          by logues.rhn.orst.edu (8.8.4/8.8.4) with SMTP
	  id RAA06078; Tue, 4 Feb 1997 17:30:18 -0800 (PST)
Message-ID: <32F7E2AA.59E2B600@engr.orst.edu>
Date: Tue, 04 Feb 1997 17:30:18 -0800
From: Steve Logue <logue@engr.orst.edu>
X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2-970201-GAMMA0 i386)
MIME-Version: 1.0
To: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de>
CC: John Hay <jhay@zibbi.mikom.csir.co.za>, stenn@whimsy.udel.edu,
        freebsd-hackers@freebsd.org
Subject: Re: xntp3-5.89.2 & FreeBSD 2.2-GAMMA won't compile
References: <32F7097D.41C67EA6@engr.orst.edu> <199702041034.MAA13094@zibbi.mikom.csir.co.za> <Mutt.19970204213651.j@uriah.heep.sax.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

J Wunsch wrote:
> 
> As John Hay wrote:
> 
> (xtnp problems)
> 
> > I have fixed it in FreeBSD-current, but weren't sure if it should go into
> > 2.2. Any opinions anyone?
> 
> > If somebody from the 2.2 release team give the go-ahead I would be
> > happy to put it in 2.2.
> 
> Barring any objections from other partys in say, the next couple of
> days, go ahead.  (Do you know how to do branch commits?)
> 
> Please, see also PR # bin/2469.  I think the designated solution to
> the problem was to introduce a LOG_NTP facility.  Somebody needs to
> track this, or it will be forgotten.  (I really need it, right now,
> i've hacked xntpd locally to log the annoying messages at LOG_DEBUG
> level.)
> 

What about all the xntpd 3.4e code in the src of FreeBSD - that needs to
be replace while we're at it?  Thanks -STEVEl

> cheers, J"org
> 
> joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
> Never trust an operating system you don't have sources for. ;-)

From owner-freebsd-hackers  Tue Feb  4 17:30:51 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA08161
          for hackers-outgoing; Tue, 4 Feb 1997 17:30:51 -0800 (PST)
Received: from spooky.rwwa.com (rwwa.com [198.115.177.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA08141
          for <freebsd-hackers@FreeBSD.org>; Tue, 4 Feb 1997 17:30:44 -0800 (PST)
Received: from spooky.rwwa.com (localhost.rwwa.com [127.0.0.1]) by spooky.rwwa.com (8.7.5/8.7.3) with ESMTP id UAA11415 for <freebsd-hackers@FreeBSD.org>; Tue, 4 Feb 1997 20:30:14 -0500 (EST)
Message-Id: <199702050130.UAA11415@spooky.rwwa.com>
X-Mailer: exmh version 1.6.9 8/22/96
To: freebsd-hackers@FreeBSD.org
Subject: Re: 2.1.6 -- AMD still broken? 
In-reply-to: Your message of "Tue, 04 Feb 1997 15:04:13 EST."
             <199702042004.PAA05554@tuva.engeast.baynetworks.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 04 Feb 1997 20:30:14 -0500
From: Robert Withrow <witr@rwwa.com>
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk


bwithrow@BayNetworks.COM said:
> Does anyone have patches for NFS in 2.1.6 that make AMD direct mounts 
> work? 

Actually, I checked the CVS repository and discovered that the
2.1.6 sources are identical to the 2.1.5 sources (for the
ones that get patched) so the 2.1.5 patches work on 2.1.6.

Will 2.2 be fixed in this regard?  If it isn't and it is still
possible to get it fixed, could we please?  This is very annoying
here because we have to make everone patch and re-build for
every upgrade/install.

-----------------------------------------------------------------------------
Robert Withrow, Tel: +1 617 592 8935, Net: witr@rwwa.COM



From owner-freebsd-hackers  Tue Feb  4 17:37:51 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA08856
          for hackers-outgoing; Tue, 4 Feb 1997 17:37:51 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id RAA08850
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 17:37:48 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id SAA13752; Tue, 4 Feb 1997 18:34:51 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702050134.SAA13752@phaeton.artisoft.com>
Subject: Re: g++, STL and -frepo on FreeBSD-2.2-Beta
To: chuckr@glue.umd.edu (Chuck Robey)
Date: Tue, 4 Feb 1997 18:34:51 -0700 (MST)
Cc: terry@lambert.org, jmacd@CS.Berkeley.EDU, hackers@freebsd.org
In-Reply-To: <Pine.OSF.3.95q.970204193602.1349B-100000@baud.eng.umd.edu> from "Chuck Robey" at Feb 4, 97 07:40:51 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Terry, I'm not sure you're right.  The virtual tables show up (using nm on
> the obj files) as "t" objects, not "T", meaning local text objects.  The
> way I understand from JW Eaton, under Linux (where he wrote it natively)
> the symbols in the obj files for these virtual tables instatiated for
> templates are global, not local.  There is one of these tables made for
> each template type, correctly, but they're coming up local.  This seems to
> be to point to an error source in the compiler, not the linking process.
> 
> FWIW, the symbols make it into the library, but as local symbols, not
> global.  Am I confused about this?

Well... you are, or I am.  8-).

Riddle me this: if the compiler makes a 't' reference to a real 'T'
somewhere... how can it generate the real 'T'?  It can't just pick
one of the files at random an put it there.  I might be compiling
incrementally.


EXAMPLE: Say I have TFifoQ.h:

	template <class Type>
	struct FifoQueueElement {
		friend class FifoQueue<Type>;
	private:
		const Type		*m_pItem;
		FifoQueueElement<Type>	*m_pNext;
	};


	template <class T>
	class FifoQueue
	{
	private:
		FifoQueueElement<Type>	*m_head;
		FifoQueueElement<Type>	*m_tail;
	public:
		void Insert( const Type *pItem);
		Queue() { head = tail = NULL; }
	};

	template <class Type>
	void
	FifoQueue<Type>::Insert( const Type *pItem)
	{
		FifoQueueElement<Type> *pQE = new FifoQueueElement<Type>;

		pQE->m_pItem = pItem;
		pQE->m_pNext = NULL;
		if( m_tail == NULL)
			m_head = pQE;
		else	m_tail->pNext = pQE;
		m_tail = pQE;
	}

and I have foo.cc:

	#include "TFifoQ.h"

	// instantiate global int queue using template...
	Queue<int>	foointqueue;

	... stuff ...

and I have fee.cc:

	#include "TFifoQ.h"

	// instantiate global int queue using template...
	Queue<int>	feeintqueue;

	... stuff ...

...do you expect the code to implement the Insert method for a FifoQueue
of int to go into foo.o or fee.o?

Here's what I expect:

a.out:
---------
Personally, I expect it to be generated static in *both* of them, with
no global reference, in the a.out case.  Anything else is an error.  If
you run a new g++ with the a.out ld for FreeBSD, it's pilot error.

Alternately, you could have a compiler flag that was applied to
fee..  that said "don't generate code for templates" so it only
made a reference, and you would *not* use that flag when compiling
foo.cc so it would generate the real thing.  Then, when you linked,
there would be one instance and multiple references.  If you used
the flag on everone who actualized the template class by instantiating
it, you wouldn't get a real instance of the code.  Again, you'd be
guilty of pilot error.


ELF:
---------
In the ELF case, I expect it will either do waht a.out does, OR if
they were clever and used ELF for what it is good for, it will
generate the template instance for an queue of integers in *both*
fee.o and foo.o, *BUT* in different ELF segments than the rest of
the code in foo.o and fee.o, and then when it links, it will bring
in only once (probably from whichever is first in the linker argument
list).

Alternately, you *could* have the same compiler flag for ELF, too,
and have the same possibility for pilot error, while creating only
a single instantiation at compile time.


Godlike compiler writer magic:
---------
If, on the other hand, they were truly *godlike*, they would provide
a method of implementing a precompiled template instantiation, and
generate one of those an an object file.  Inside, it would use RTTI
(run time type identification) to decide what kind of object it was
referring to, and the compiled template code would not enforce the
object type.  The compiler would compile fee.cc and foo.cc, and
*not* generate the code for the template.  But it would rigidly
enforce *at compile time* type checking *as if it had*.  Then, when
it generated any references for the "FifoQueue of int's" public
member functions or data, it would generate them *without* the
linker glue for link time type checking, and rely solely on the RTTI
to enable the class to "do the right thing".


I find this last one extremely unlikely.  But if they are doing it,
then the symbols are right, I am wrong.  And it's still pilot error,
since if ther pilot did the right thing, there would be: (1) an object
module with the type-stripped class instance, (2) multiple object
modules with refernces to the type stripped references, and (3) an
RTTI interface, which I don't believe currently exists in a form
suitable for use in doing this sort of thing by hacking up the compiler
for the special case where it is compiling a template file to generate
an object with type-non-specific 'this' and private member data
references.


---------

If I'm wrong (the declaration didn't need to be in scope), then
it's probably that they are incorrectly applying the "don't generate
template" flag when they shouldn't be, not creating a template
instance object seperate from the rest of their objects, like they
should be, or relying on linker tricks which require multiple
instantiations to be coalesced to a single instance, which the a.out
linker is too stupid to do, and the ELF linker is probably currently
too stupid to do, even though ELF could support it.

Feel free to correct me, though... I'd rather know the right answer
than just think I knew the right answer.  If there's another way for
me to be wrong, let me know.


					Regards,
					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Tue Feb  4 18:19:44 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id SAA14041
          for hackers-outgoing; Tue, 4 Feb 1997 18:19:44 -0800 (PST)
Received: from root.com (implode.root.com [198.145.90.17])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA14017;
          Tue, 4 Feb 1997 18:19:37 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id SAA03221; Tue, 4 Feb 1997 18:19:39 -0800 (PST)
Message-Id: <199702050219.SAA03221@root.com>
X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol
To: "Brian J. McGovern" <mcgovern@spoon.beta.com>
cc: questions@freebsd.org, hackers@freebsd.org
Subject: Re: Cyclades driver causes kernel panic 
In-reply-to: Your message of "Tue, 04 Feb 1997 17:54:56 EST."
             <199702042254.RAA02641@spoon.beta.com> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Tue, 04 Feb 1997 18:19:39 -0800
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>Well, its back, and I'm pulling my hair out of my head. It appears
>that on HPs, Dells, Eclipse machines, and a handful of others,
>the Cyclades driver causes a RAM parity error, causing the kernel
>to panic, and the system to reboot. I've sen this on at least
>a half dozen systems. And I've found about two that work.
>
>Has anyone seen this? Worked around it? I'm kind of at a crunch
>to get some multi-port serial cards working, and I could use all
>the help I can get.
>
>The machines are HP 586/133s and 166s. The dells are Dell 586/100s. The
>only machine I've see it work in for any length of time was a AMD clone 586/100.
>
>I don't think its a RAM parity error, simply because a half-dozen
>machines with EDO Ram can't all be wrong (or i'd see it elsewhere),
>and the DOS drivers tend to get the card up and working on multiple
>ports with no problems.

   Install the attached patch...it has fixed the problem for other people.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project

Index: locore.s
===================================================================
RCS file: /home/ncvs/src/sys/i386/i386/locore.s,v
retrieving revision 1.52.4.5
diff -c -r1.52.4.5 locore.s
*** locore.s	1996/11/14 15:55:40	1.52.4.5
--- locore.s	1997/01/30 20:17:10
***************
*** 613,619 ****
  	movl    _KPTphys-KERNBASE,%ebx		/* base of kernel page tables */
  	lea     (0xa0 * PTESIZE)(%ebx),%ebx	/* hardwire ISA hole at KERNBASE + 0xa0000 */
  	movl	$0x100-0xa0,%ecx		/* for this many pte s, */
! 	movl	$(0xa0000|PG_V|PG_KW|PG_N),%eax	/* valid, kernel read/write, non-cacheable */
  	movl	%ebx,_atdevphys-KERNBASE	/* save phys addr of ptes */
  	fillkpt
  
--- 613,619 ----
  	movl    _KPTphys-KERNBASE,%ebx		/* base of kernel page tables */
  	lea     (0xa0 * PTESIZE)(%ebx),%ebx	/* hardwire ISA hole at KERNBASE + 0xa0000 */
  	movl	$0x100-0xa0,%ecx		/* for this many pte s, */
! 	movl	$(0xa0000|PG_V|PG_KW),%eax	/* valid, kernel read/write, non-cacheable */
  	movl	%ebx,_atdevphys-KERNBASE	/* save phys addr of ptes */
  	fillkpt
  
Index: pmap.c
===================================================================
RCS file: /home/ncvs/src/sys/i386/i386/pmap.c,v
retrieving revision 1.58.4.6
diff -c -r1.58.4.6 pmap.c
*** pmap.c	1996/06/26 06:18:10	1.58.4.6
--- pmap.c	1997/01/23 22:14:19
***************
*** 2043,2049 ****
  
  	for (tmpva = va; size > 0;) {
  		pte = vtopte(tmpva);
! 		*pte = (pt_entry_t) ((int) (pa | PG_RW | PG_V | PG_N));
  		size -= PAGE_SIZE;
  		tmpva += PAGE_SIZE;
  		pa += PAGE_SIZE;
--- 2043,2049 ----
  
  	for (tmpva = va; size > 0;) {
  		pte = vtopte(tmpva);
! 		*pte = (pt_entry_t) ((int) (pa | PG_RW | PG_V));
  		size -= PAGE_SIZE;
  		tmpva += PAGE_SIZE;
  		pa += PAGE_SIZE;

From owner-freebsd-hackers  Tue Feb  4 18:20:36 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id SAA14287
          for hackers-outgoing; Tue, 4 Feb 1997 18:20:36 -0800 (PST)
Received: from logues.rhn.orst.edu (logues.RHN.ORST.EDU [128.193.139.116])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA14273
          for <freebsd-hackers@freebsd.org>; Tue, 4 Feb 1997 18:20:32 -0800 (PST)
Received: from logues.rhn.orst.edu (localhost [127.0.0.1])
          by logues.rhn.orst.edu (8.8.4/8.8.4) with SMTP
	  id SAA06250; Tue, 4 Feb 1997 18:20:20 -0800 (PST)
Message-ID: <32F7EE64.1CFBAE39@engr.orst.edu>
Date: Tue, 04 Feb 1997 18:20:20 -0800
From: Steve Logue <logue@engr.orst.edu>
X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2-970201-GAMMA0 i386)
MIME-Version: 1.0
To: stenn@whimsy.udel.edu
CC: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de>,
        John Hay <jhay@zibbi.mikom.csir.co.za>, freebsd-hackers@freebsd.org
Subject: Re: xntp3-5.89.2 & FreeBSD 2.2-GAMMA won't compile
References: <9702041901.aa26048@whimsy.udel.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

stenn@whimsy.udel.edu wrote:
> 
> It looks like I'll need to add this patch to the sys/timex.h file in the
> xntpd distribution:
> 
> --- timex.h-    Sat Jul 15 04:06:10 1995
> +++ timex.h     Sun Feb  2 02:56:21 1997
> @@ -284,6 +284,17 @@
>  };
>  #ifdef __FreeBSD__
> 
> +/*
> + * sysctl identifiers underneath kern.ntp_pll
> + */
> +#define NTP_PLL_GETTIME        1       /* used by ntp_gettime() */
> +#define NTP_PLL_MAXID  2       /* number of valid ids */
> +
> +#define NTP_PLL_NAMES { \
> +                         { 0, 0 }, \
> +                         { "gettime", CTLTYPE_STRUCT }, \
> +                     }
> +
>  #ifndef KERNEL
>  #include <sys/cdefs.h>
> 
> Is there anything else I should add to the xntpd distribution to make
> life easier for us?
> 
> Harlan

We must have gotten off on the wrong foot here.  XNTPD's timex.h isn't
the problem,  FreeBSD's timex.h is.  The currently shipping timex.h with
xntp will compile when included in ntp_loopfilter.c instead of FreeBSD's
timex.h, unaltered.  

Problems still lye somewhere else with regards to ntpq not working.  I
recompiled with this patch, and #include "../kernel/sys/timex.h" in
ntp_loopfilter.c, but it still isn't talking to ntpq.

Is this business of just magically changing to xntp's timex.h instead of
FBSD's even prudent?

From owner-freebsd-hackers  Tue Feb  4 18:23:53 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id SAA15111
          for hackers-outgoing; Tue, 4 Feb 1997 18:23:53 -0800 (PST)
Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA15066
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 18:23:48 -0800 (PST)
Received: from awfulhak.demon.co.uk (localhost.coverform.lan [127.0.0.1]) by awfulhak.demon.co.uk (8.8.4/8.7.3) with ESMTP id BAA29931 for <hackers@freebsd.org>; Wed, 5 Feb 1997 01:59:56 GMT
Message-Id: <199702050159.BAA29931@awfulhak.demon.co.uk>
X-Mailer: exmh version 1.6.9 8/22/96
To: hackers@freebsd.org
Subject: pppd
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 05 Feb 1997 01:59:56 +0000
From: Brian Somers <brian@awfulhak.demon.co.uk>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Is anyone responsible for pppd at the moment ?
I have a patch (submitted by Lars Fredriksen <fredriks@Mcs.Net>) that logs
connection times - seems like a good idea to me.
-- 
Brian <brian@awfulhak.demon.co.uk>, <brian@freebsd.org>
      <http://www.awfulhak.demon.co.uk/>
Don't _EVER_ lose your sense of humour....



From owner-freebsd-hackers  Tue Feb  4 18:24:11 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id SAA15205
          for hackers-outgoing; Tue, 4 Feb 1997 18:24:11 -0800 (PST)
Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA15182
          for <hackers@freefall.freebsd.org>; Tue, 4 Feb 1997 18:24:04 -0800 (PST)
Received: from awfulhak.demon.co.uk (localhost.coverform.lan [127.0.0.1]) by awfulhak.demon.co.uk (8.8.4/8.7.3) with ESMTP id BAA29896; Wed, 5 Feb 1997 01:51:56 GMT
Message-Id: <199702050151.BAA29896@awfulhak.demon.co.uk>
X-Mailer: exmh version 1.6.9 8/22/96
To: Julian Elischer <julian@whistle.com>
cc: Bill Kish <kish@browncow.com>, hackers@freefall.freebsd.org
Subject: Re: kernel malloc options 
In-reply-to: Your message of "Mon, 03 Feb 1997 17:09:35 PST."
             <32F68C4F.3F54BC7E@whistle.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 05 Feb 1997 01:51:56 +0000
From: Brian Somers <brian@awfulhak.demon.co.uk>
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


> Wow, a couple of months ago we had no address translation, now we
> have *4* different ones.. :)

A mere flux !  It'll stabilise !
-- 
Brian <brian@awfulhak.demon.co.uk>, <brian@freebsd.org>
      <http://www.awfulhak.demon.co.uk/>
Don't _EVER_ lose your sense of humour....



From owner-freebsd-hackers  Tue Feb  4 18:28:57 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id SAA16282
          for hackers-outgoing; Tue, 4 Feb 1997 18:28:57 -0800 (PST)
Received: from po1.glue.umd.edu (root@po1.glue.umd.edu [129.2.128.44])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA16271
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 18:28:54 -0800 (PST)
Received: from baud.eng.umd.edu (baud.eng.umd.edu [129.2.98.183]) by po1.glue.umd.edu (8.8.5/8.7.3) with ESMTP id VAA19927; Tue, 4 Feb 1997 21:28:51 -0500 (EST)
Received: from localhost (chuckr@localhost) by baud.eng.umd.edu (8.8.5/8.7.3) with SMTP id VAA00998; Tue, 4 Feb 1997 21:28:49 -0500 (EST)
X-Authentication-Warning: baud.eng.umd.edu: chuckr owned process doing -bs
Date: Tue, 4 Feb 1997 21:28:48 -0500 (EST)
From: Chuck Robey <chuckr@glue.umd.edu>
X-Sender: chuckr@baud.eng.umd.edu
To: Terry Lambert <terry@lambert.org>
cc: jmacd@CS.Berkeley.EDU, hackers@freebsd.org
Subject: Re: g++, STL and -frepo on FreeBSD-2.2-Beta
In-Reply-To: <199702050134.SAA13752@phaeton.artisoft.com>
Message-ID: <Pine.OSF.3.95q.970204211959.1889B-100000@baud.eng.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Tue, 4 Feb 1997, Terry Lambert wrote:

> > Terry, I'm not sure you're right.  The virtual tables show up (using nm on
> > the obj files) as "t" objects, not "T", meaning local text objects.  The
> > way I understand from JW Eaton, under Linux (where he wrote it natively)
> > the symbols in the obj files for these virtual tables instatiated for
> > templates are global, not local.  There is one of these tables made for
> > each template type, correctly, but they're coming up local.  This seems to
> > be to point to an error source in the compiler, not the linking process.
> > 
> > FWIW, the symbols make it into the library, but as local symbols, not
> > global.  Am I confused about this?
> 
> Well... you are, or I am.  8-).
> 
> Riddle me this: if the compiler makes a 't' reference to a real 'T'
> somewhere... how can it generate the real 'T'?  It can't just pick
> one of the files at random an put it there.  I might be compiling
> incrementally.
[large code example elided]
> 
> ...do you expect the code to implement the Insert method for a FifoQueue
> of int to go into foo.o or fee.o?

In the interests of keeping this to some reasonable legnth, I took a lot
out, but the comments are valid.  One point, tho -- this seems to work
correctly under Linux/ELF.  This is the first time I really wish I had
access to a Linux machine to check the visibility of the virtual tables.
The code pieces do seem to be made global under FreeBSD, it's just the
virtual tables that are local, and so invisible to other modules.

You said you don't think ELF DTRT, altho it could.  Maybe it is?  My
workaround is to have the virtual tables instantiated everywhere, and it
works, but I wish it worked the way it's supposed to, with just one copy
of the code (and virtual tables, which are the real bogie here, I think).
The object modules corresponding to your fee.C example are there, but the
virtual tables in fee.o are local.

> 
> Here's what I expect:
> 
> a.out:
> ---------
[a.out explanation elided]
> 
> ELF:
> ---------
[ELF explanation elided]

> 
> If I'm wrong (the declaration didn't need to be in scope), then
> it's probably that they are incorrectly applying the "don't generate
> template" flag when they shouldn't be, not creating a template
> instance object seperate from the rest of their objects, like they
> should be, or relying on linker tricks which require multiple
> instantiations to be coalesced to a single instance, which the a.out
> linker is too stupid to do, and the ELF linker is probably currently
> too stupid to do, even though ELF could support it.
> 
> Feel free to correct me, though... I'd rather know the right answer
> than just think I knew the right answer.  If there's another way for
> me to be wrong, let me know.
> 
> 
> 					Regards,
> 					Terry Lambert
> 					terry@lambert.org
> ---
> Any opinions in this posting are my own and not those of my present
> or previous employers.
> 

----------------------------+-----------------------------------------------
Chuck Robey                 | Interests include any kind of voice or data 
chuckr@eng.umd.edu          | communications topic, C programming, and Unix.
9120 Edmonston Ct #302      |
Greenbelt, MD 20770         | I run Journey2 and picnic, both FreeBSD
(301) 220-2114              | version 3.0 current -- and great FUN!
----------------------------+-----------------------------------------------


From owner-freebsd-hackers  Tue Feb  4 18:34:28 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id SAA17564
          for hackers-outgoing; Tue, 4 Feb 1997 18:34:28 -0800 (PST)
Received: from awfulhak.demon.co.uk (raffles.demon.co.uk [158.152.17.201])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA17538
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 18:34:22 -0800 (PST)
Received: from awfulhak.demon.co.uk (localhost.coverform.lan [127.0.0.1]) by awfulhak.demon.co.uk (8.8.4/8.7.3) with ESMTP id BAA29882; Wed, 5 Feb 1997 01:49:01 GMT
Message-Id: <199702050149.BAA29882@awfulhak.demon.co.uk>
X-Mailer: exmh version 1.6.9 8/22/96
To: "Brian Somers" <brian@utell.co.uk>
cc: "Charles Mott" <cmott@srv.net>, "Julian Elischer" <julian@whistle.com>,
        "Eivind Eklund" <eivind@dimaga.com>,
        "Ari Suutari" <ari.suutari@ps.carel.fi>, hackers@freebsd.org
Subject: Re: Single socket version of natd 
In-reply-to: Your message of "Tue, 04 Feb 1997 18:37:30 GMT."
             <199702041837.SAA02367@ui-gate.utell.co.uk> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 05 Feb 1997 01:49:00 +0000
From: Brian Somers <brian@awfulhak.demon.co.uk>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> I don't know specifically without checking the code, but I recall seeing a
> comment in the -current sources (I've just checked SNAP-961014, nothing
> about it there) about using the ip_sum to differentiate between incoming
> and outgoing packets.....  It *WAS* commented as being a HACK :(
> 
> I'll check the code out this evening when I get home (-current machine)
> and tell you.
[.....]

I was lying.  There's no such comments !

Does anyone know of a reason (besides the divert(4) man page) that the
sum on incoming packets is zero'd ?
The code says:

[.....]
        if (hlen == sizeof(struct ip)) {
                ip->ip_sum = in_cksum_hdr(ip);
        } else {
                ip->ip_sum = in_cksum(m, hlen);
        }
        if (ip->ip_sum) {
                ipstat.ips_badsum++;
                goto bad;
        }
[.....]

Is there any problems with changing this to

        u_short sum;
.....
        if (hlen == sizeof(struct ip)) {
                sum = in_cksum_hdr(ip);
        } else {
                sum = in_cksum(m, hlen);
        }
        if (sum) {
                ipstat.ips_badsum++;
                goto bad;
        }

(and updating divert(4)) ?
-- 
Brian <brian@awfulhak.demon.co.uk>, <brian@freebsd.org>
      <http://www.awfulhak.demon.co.uk/>
Don't _EVER_ lose your sense of humour....



From owner-freebsd-hackers  Tue Feb  4 19:30:13 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA25113
          for hackers-outgoing; Tue, 4 Feb 1997 19:30:13 -0800 (PST)
Received: from nyx.pr.mcs.net (nyx.pr.mcs.net [204.95.55.81])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA25107
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 19:30:08 -0800 (PST)
Received: from nyx.pr.mcs.net (localhost [127.0.0.1])
          by nyx.pr.mcs.net (8.8.5/8.8.4) with ESMTP
	  id VAA03510; Tue, 4 Feb 1997 21:30:18 -0600 (CST)
Message-Id: <199702050330.VAA03510@nyx.pr.mcs.net>
X-Mailer: exmh version 2.0beta 12/23/96
To: Brian Somers <brian@awfulhak.demon.co.uk>
cc: hackers@freebsd.org
Subject: Re: pppd 
In-reply-to: Your message of Wed, 05 Feb 1997 01:59:56 +0000.
             <199702050159.BAA29931@awfulhak.demon.co.uk> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 04 Feb 1997 21:30:18 -0600
From: Chris Csanady <ccsanady@nyx.pr.mcs.net>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


>Is anyone responsible for pppd at the moment ?
>I have a patch (submitted by Lars Fredriksen <fredriks@Mcs.Net>) that logs
>connection times - seems like a good idea to me.

Speaking of this..  I am using ppp(userland), and need time my connections.
The problem is that there is a ppp.linkup that can be executed, but no
ppp.linkdown or such.  Any ideas?  I need some of the features in the
userland version..

Chris
>-- 
>Brian <brian@awfulhak.demon.co.uk>, <brian@freebsd.org>
>      <http://www.awfulhak.demon.co.uk/>
>Don't _EVER_ lose your sense of humour....
>
>








From owner-freebsd-hackers  Tue Feb  4 19:53:21 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA27123
          for hackers-outgoing; Tue, 4 Feb 1997 19:53:21 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id TAA27117
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 19:53:19 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id UAA14160; Tue, 4 Feb 1997 20:50:19 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702050350.UAA14160@phaeton.artisoft.com>
Subject: Re: g++, STL and -frepo on FreeBSD-2.2-Beta
To: chuckr@glue.umd.edu (Chuck Robey)
Date: Tue, 4 Feb 1997 20:50:19 -0700 (MST)
Cc: terry@lambert.org, jmacd@CS.Berkeley.EDU, hackers@freebsd.org
In-Reply-To: <Pine.OSF.3.95q.970204211959.1889B-100000@baud.eng.umd.edu> from "Chuck Robey" at Feb 4, 97 09:28:48 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> You said you don't think ELF DTRT, altho it could.  Maybe it is?  My
> workaround is to have the virtual tables instantiated everywhere, and it
> works, but I wish it worked the way it's supposed to, with just one copy
> of the code (and virtual tables, which are the real bogie here, I think).
> The object modules corresponding to your fee.C example are there, but the
> virtual tables in fee.o are local.

ELF's only a neat tool.

There are a lot of clever things you could do with ELF.  I bet most
of them aren't being done, mostly because I don't see them being
done, and it is Not The Nature Of Free Software to do these things.
For instance, there still isn't a way to ABI-attribute ELF binaries
being generated by the linker, even when people have complained
about it for nearly a year now.

There is a level of architectural complexity that free software never
seems to exceed... sort of a "free software glass ceiling".

The ELF hack I'm talking about is an obvious link-time version of
a load-time optimization, but it's only obvious because I've dealt
with code on an ELF machine that deals with segment coloring.  I
could page in only one instance of the ELF module for all my
callers, even though I had multiple real instances in the binary.
This type of thing only works with segment coloring to distinguish
treatment of one code segment from treatment of another in a binary.
This is basically link-time segment coloring with object agregation
by color.

I frankly don't think the G++ people are up for this type of thing
yet because of the environments in which they run... but like I
said, I could be wrong.  If I was wrong in my scoping argument,
it was because I assumed that the pilot error was somewhere other
than where it was, not because I assumed pilot error existed.  Not
a good consolation, but at least I'm not totally off my rocker.  8-).


Another clever thing for ELF: put the libkvm code in an ELF segment
in the kernel image so it can be accessed by 'ps', 'w', and the
kernel debuggers, alike.  Then make it operate only on published
externals instead of the entire kvm, and make 'ps', 'w', and company
operate on exported externals instead of kvm symbols.  Reduce the
set of kernel interface to make it more modular.  Agregate the
interface with those exported by existing loadable kernel modules
so the name space is entirely transparent.


How about agregation of authentication objects, so that I can have
one library routine linked that can look up account information
from the local password file, the NIS, radiusd, the CISCO thing,
LDAP, NDS, or whatever else I wanted to agregate into the thing?


There's literally hundreds of these types of things, and they
almost all depend on OS support, either to implement them, or
to make them obvious.


In any case, I'd like to see them do this kind of clever thing,
but it requires that we OS geeks cooperate, or it will never occur
to them because they won't have an execution environment that could
use the changes.


					Regards,
					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Tue Feb  4 19:55:32 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA27497
          for hackers-outgoing; Tue, 4 Feb 1997 19:55:32 -0800 (PST)
Received: from paris.CS.Berkeley.EDU (paris.CS.Berkeley.EDU [128.32.34.47])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA27478
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 19:55:28 -0800 (PST)
Received: (from jmacd@localhost) by paris.CS.Berkeley.EDU (8.8.3/8.8.2) id TAA11238; Tue, 4 Feb 1997 19:55:18 -0800 (PST)
Date: Tue, 4 Feb 1997 19:55:18 -0800 (PST)
From: Josh MacDonald <jmacd@CS.Berkeley.EDU>
Message-Id: <199702050355.TAA11238@paris.CS.Berkeley.EDU>
To: hackers@freebsd.org, terry@lamber.org, terry@lambert.org
Subject: Re: g++, STL and -frepo on FreeBSD-2.2-Beta 
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


As far as I know, the following is true:

a) No one implements any of the fancy methods of template instanciation
you suggest.  I know little about ELF, but I've been fighting with g++
templates for over a year now on many different platforms and I've never
run into any mention of the optimization you suggest.  As to the god-like
optimization you suggest, I think its impractical even if they could 
implement it.  It would be a pretty big performance hit, for the most
part.  You don't want every function and/or operator call inside each
function to have to switch on the object type, which it potentially
would come down to, plus the fact that the size of the type in question
would not be known until run time leaves many compiler optimizations
invalid.  Since you'd still be duplicating code, I don't see its being
very useful anyway.

b) The way you suggest of telling the compiler not to generate templates
automatically works as follows (in g++):

Specify -fno-implicit-templates for all source files you compile.  In
the source module containing the template methods (or perhaps 
multiple source files if the template methods are spread out, though
I haven't tested this) you add a line _after_ all the template 
methods have been defined.  So, 

in file foo.h:

#include <stdio.h>
template<class T> 
class Foo 
{
public: 
   Foo<T>(T i) { printf ("%d\n", i); }
   virtual void foo();
};

in file foo.cc:

#include "foo.h"

template <class T> void Foo<T>::foo() { }

template class Foo<int>;
template class Foo<char>;

in file bar.cc:

#include "foo.h"
void main() { Foo<int> a(9); Foo<int> b('f'); }

Compiles with -fno-implicit-templates (or without) and links correctly.

c) Many compilers take the following course of action (The only two
I actually have experience with are Sun CC 4.2 and g++).  Generate
a file containing enough data to generate the template at link-time.
This is what the repo patches are for.  To my knowledge, it works
by modifying the collect2 phase of linking.  As we all know, it doesn't
work without ELFkit.

d) RTTI is not working very well in g++.

I'm fairly interested in seeing that FreeBSD stays a viable C++ development
platform.  I wonder if Chuck could better describe the problem with 
Octave?

Now concerning the virtual tables, I'm not sure I understand, when I
compile the two source files above with -fno-implicit-templates, I get:

axis-~ $ nm bar.o | c++filt
00000000 t ___gnu_compiled_cplusplus
         U ___main
         U Foo<int>::Foo(int)
00000000 T _main
00000000 t gcc2_compiled.

That seems to be missing a symbol, is something broken?  Where'd 
Foo<char>::Foo(char) go?  It gets called when I run it.

axis-~ $ nm foo.o | c++filt
00000078 T Foo<char>::operator=(Foo<char> const &)
000000b8 T Foo<int>::operator=(Foo<int> const &)
00000000 t ___gnu_compiled_cplusplus
0000009c T Foo<char>::Foo(Foo<char> const &)
00000030 T Foo<char>::Foo(char)
000000dc T Foo<int>::Foo(Foo<int> const &)
00000004 T Foo<int>::Foo(int)
000000f8 T Foo<char> virtual table
00000108 T Foo<int> virtual table
00000068 T Foo<char>::foo(void)
00000070 T Foo<int>::foo(void)
         U _printf
00000000 t gcc2_compiled.

As you can see, the virtual tables have extenral linkage and the
template methods for int and char were only generated once.

> Riddle me this: if the compiler makes a 't' reference to a real 'T'
> somewhere... how can it generate the real 'T'?  It can't just pick
> one of the files at random an put it there.  I might be compiling
> incrementally.

Often you choose the complication unit containing the first virtual
function, for example, to place the virtual table in, you can use the
ordering of the class methods/decls for this purpose.  If everything
is in the header file, you lose.  People have been pointing out
for years that the UNIX compile/link proceedure is inadequate for
C++ and templates, ever since cfront invented the template repository.
You can use a pragma as well, these are all documented in the GCC info
pages (as well as the fact that Boreland solved the problem with the 
ELF trick you suggest).

[Lots of code deleted]

> a.out:
> ---------
> Personally, I expect it to be generated static in *both* of them, with
> no global reference, in the a.out case.  Anything else is an error.  If
> you run a new g++ with the a.out ld for FreeBSD, it's pilot error.
> 
> Alternately, you could have a compiler flag that was applied to
> fee..  that said "don't generate code for templates" so it only
> made a reference, and you would *not* use that flag when compiling
> foo.cc so it would generate the real thing.  Then, when you linked,
> there would be one instance and multiple references.  If you used
> the flag on everone who actualized the template class by instantiating
> it, you wouldn't get a real instance of the code.  Again, you'd be
> guilty of pilot error.

The syntax I show above has made it into the C++ standard.  See 
section 14.7.2 in a recent draft.

> Godlike compiler writer magic:
> ---------
> If, on the other hand, they were truly *godlike*, they would provide
> a method of implementing a precompiled template instantiation, and
> generate one of those an an object file.  Inside, it would use RTTI
> (run time type identification) to decide what kind of object it was
> referring to, and the compiled template code would not enforce the
> object type.  The compiler would compile fee.cc and foo.cc, and
> *not* generate the code for the template.  But it would rigidly
> enforce *at compile time* type checking *as if it had*.  Then, when
> it generated any references for the "FifoQueue of int's" public
> member functions or data, it would generate them *without* the
> linker glue for link time type checking, and rely solely on the RTTI
> to enable the class to "do the right thing".

"do the right thing slowly".  There's still lots of problems you've
ignored like where to put the static template members (something
that's pretty difficult to accomplish in eveyr c++ compiler I've
used).  The chances of actually saving space this way are small,
the overhead of making one general purpose code section would be
large, I think.  I wouldn't call it godlike, maybe impressive software
engineering.

> I find this last one extremely unlikely.  But if they are doing it,
> then the symbols are right, I am wrong.  And it's still pilot error,
> since if ther pilot did the right thing, there would be: (1) an object
> module with the type-stripped class instance, (2) multiple object
> modules with refernces to the type stripped references, and (3) an
> RTTI interface, which I don't believe currently exists in a form
> suitable for use in doing this sort of thing by hacking up the compiler
> for the special case where it is compiling a template file to generate
> an object with type-non-specific 'this' and private member data
> references.

> If I'm wrong (the declaration didn't need to be in scope), then
> it's probably that they are incorrectly applying the "don't generate
> template" flag when they shouldn't be, not creating a template
> instance object seperate from the rest of their objects, like they
> should be, or relying on linker tricks which require multiple
> instantiations to be coalesced to a single instance, which the a.out
> linker is too stupid to do, and the ELF linker is probably currently
> too stupid to do, even though ELF could support it.

The original problem had to do with the repo patches, nothing to
do with scopes.  The repo patches don't work, that's the problem.
They *should* generate all the required template code and isnert
them into a REPOsitory at link-time, but they don't so symbols
were missing, not pilot error.

> Feel free to correct me, though... I'd rather know the right answer
> than just think I knew the right answer.  If there's another way for
> me to be wrong, let me know.
> 
> 
> 					Regards,
> 					Terry Lambert
> 					terry@lambert.org
> ---
> Any opinions in this posting are my own and not those of my present
> or previous employers.

-josh

From owner-freebsd-hackers  Tue Feb  4 19:58:30 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA28022
          for hackers-outgoing; Tue, 4 Feb 1997 19:58:30 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id TAA28017
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 19:58:28 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id UAA14199; Tue, 4 Feb 1997 20:55:30 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702050355.UAA14199@phaeton.artisoft.com>
Subject: Re: g++, STL and -frepo on FreeBSD-2.2-Beta
To: terry@phaeton.artisoft.com (Terry Lambert)
Date: Tue, 4 Feb 1997 20:55:29 -0700 (MST)
Cc: chuckr@glue.umd.edu, terry@lambert.org, jmacd@CS.Berkeley.EDU,
        hackers@freebsd.org
In-Reply-To: <199702050350.UAA14160@phaeton.artisoft.com> from "Terry Lambert" at Feb 4, 97 08:50:19 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> ELF's only a neat tool.

[ ... ]


Sorry for the "SPAM".  I thought I was replaying to a mail that was off
the list...


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Tue Feb  4 21:17:47 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA02475
          for hackers-outgoing; Tue, 4 Feb 1997 21:17:47 -0800 (PST)
Received: from logues.rhn.orst.edu (logues.RHN.ORST.EDU [128.193.139.116])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA02469;
          Tue, 4 Feb 1997 21:17:45 -0800 (PST)
Received: from localhost (stevel@localhost)
          by logues.rhn.orst.edu (8.8.4/8.8.4) with SMTP
	  id VAA06571; Tue, 4 Feb 1997 21:17:44 -0800 (PST)
Date: Tue, 4 Feb 1997 21:17:44 -0800 (PST)
From: stevel <stevel@logues.rhn.orst.edu>
To: freebsd-questions@freebsd.org
cc: freebsd-hackers@freebsd.org
Subject: UPS daemon
Message-ID: <Pine.BSF.3.95.970204210718.6543A-100000@logues.rhn.orst.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Is there anyone working on a generic UPS daemon?  I know someone is
working on one specifically for APC Smart UPS's, but this isn't usefull to
the majority of people.  We mostly have "non-smart", TrippLite's and APC
out there right?  Tripplite BC series, OmniPro series / APC BackUPS
series.

I would like to write a UPSd in C++, but I don't have enough knowledge of
serial programming yet.  Also, I would like some input about how the
FreeBSD startup, and shutdown events happen.  I am very familiar with the
SYSV style startup/shutdown as implemented in RedHat Linux, and how
sysvinit supports power event signals.  What is the corollary in BSD?  As
far as I'm concerned, I don't even want to have to mess with init.  I'd
like to do my own shutdowns, and cancelations?

-STEVEl






From owner-freebsd-hackers  Tue Feb  4 21:50:51 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA05508
          for hackers-outgoing; Tue, 4 Feb 1997 21:50:51 -0800 (PST)
Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id VAA05503
          for <freebsd-hackers@freebsd.org>; Tue, 4 Feb 1997 21:50:48 -0800 (PST)
Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02)
	id AA07471; Wed, 5 Feb 1997 00:50:12 -0500
Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Wed,  5 Feb 1997 00:50 EST
Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id VAA25506; Tue, 4 Feb 1997 21:43:06 -0500 (EST)
Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id VAA23395; Tue, 4 Feb 1997 21:47:32 -0500 (EST)
Date: Tue, 4 Feb 1997 21:47:32 -0500 (EST)
From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
Message-Id: <199702050247.VAA23395@lakes.water.net>
To: patrick@xinside.com, ponds!freebsd.org!freebsd-hackers
Subject: Re: [Fwd: freebsd performance.]
Content-Type: text
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


Patrick Giagnocavo writes:

> Julian Elischer writes:
> 
>  > The posix regex library is VERY VERY slow.
>  > 
>  > I have a program that uses a large regex to parse some input.
>  > 
>  > I have a version in perl and a version in C++ using the freebsd posix
>  > regex library.
>  > 
>  > The perl version is 100X faster that the C++ version.
>  > 
>  > gprof on the C++ version shows 99% of the spend in:
>  > 
>  >  91.53     46.17    46.17  1152366     0.04     0.04  lstep
>  >   6.52     49.46     3.29    98497     0.03     0.47  lslow
> 
> I am surprised that some of our more erudite members on the list have
> not jumped on this.  So, a definitely non-erudite person will.
> 
	...
> 
> There are two different 'engines' - NFA (nondeterministic finite
> automaton) and DFA (deterministic finite automaton).  Perl is
> 'traditional NFA' according to Mr. Friedl, while POSIX leans towards
> DFA-like behavior in all cases (always returns 'leftmost-longest' that
> matches - perl returns I believe the first part that matches).
 
 Ah, but you should remember that all NFAs are convertable to DFAs.

> 
> Also, Perl does not 'do' POSIX IIRC; so the results can actually be
> different when using the same regex string.  Perl does however have
> some very powerful features for its regex - covered in the book. 

 This could be part of the reason for a performance difference;
if they are not performing the same operation - you're comparing apples
and oranges.


	- Dave Rivers -

From owner-freebsd-hackers  Tue Feb  4 22:34:54 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id WAA07677
          for hackers-outgoing; Tue, 4 Feb 1997 22:34:54 -0800 (PST)
Received: from pdx1.world.net (pdx1.world.net [192.243.32.18])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA07666
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 22:34:51 -0800 (PST)
Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id WAA11020 for <hackers@freebsd.org>; Tue, 4 Feb 1997 22:36:02 -0800 (PST)
Received: (qmail 28573 invoked by uid 110); 5 Feb 1997 06:33:51 -0000
MBOX-Line: From owner-netdev@roxanne.nuclecu.unam.mx Wed Feb 05 04:34:48 1997 remote from suburbia.net
Delivered-To: proff@suburbia.net
Received: (qmail 4637 invoked from network); 5 Feb 1997 04:17:35 -0000
Received: from roxanne.nuclecu.unam.mx (132.248.29.2)
  by suburbia.net with SMTP; 5 Feb 1997 04:17:35 -0000
Received: (from root@localhost) by roxanne.nuclecu.unam.mx (8.6.12/8.6.11) id WAA23063 for netdev-outgoing; Tue, 4 Feb 1997 22:08:17 -0600
Received: from caipfs.rutgers.edu (caipfs.rutgers.edu [128.6.155.100]) by roxanne.nuclecu.unam.mx (8.6.12/8.6.11) with ESMTP id WAA23058; Tue, 4 Feb 1997 22:08:04 -0600
Received: from jenolan.caipgeneral (jenolan.rutgers.edu [128.6.111.5]) by caipfs.rutgers.edu (8.7.6/8.7.3) with SMTP id XAA11274; Tue, 4 Feb 1997 23:05:25 -0500 (EST)
Received: by jenolan.caipgeneral (SMI-8.6/SMI-SVR4)
	id XAA03584; Tue, 4 Feb 1997 23:05:08 -0500
Date: Tue, 4 Feb 1997 23:05:08 -0500
Message-Id: <199702050405.XAA03584@jenolan.caipgeneral>
From: "David S. Miller" <davem@jenolan.rutgers.edu>
To: netdev@roxanne.nuclecu.unam.mx
CC: smpdev@roxanne.nuclecu.unam.mx
Subject: paper I stumbled across
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


vger.rutgers.edu:/pub/linux/SMP/papers/netlocking.ps.gz

It discusses the parallelization of the xkernel network protocol code
for shared memory multiprocessors.  It includes analysis of various
simulations that the authors ran over their implementation using
various traces of tcp and udp connection sets.  They also explore
strategies, payoff, and the overhead of the locking itself on the
operations that need to be performed.


From owner-freebsd-hackers  Tue Feb  4 22:46:26 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id WAA08004
          for hackers-outgoing; Tue, 4 Feb 1997 22:46:26 -0800 (PST)
Received: from root.com (implode.root.com [198.145.90.17])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA07999
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 22:46:23 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id WAA05126 for <hackers@freebsd.org>; Tue, 4 Feb 1997 22:46:29 -0800 (PST)
Message-Id: <199702050646.WAA05126@root.com>
X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol
To: hackers@freebsd.org
Subject: release of ipsec for freebsd (forwarded)
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Tue, 04 Feb 1997 22:46:29 -0800
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


------- Forwarded Message

Return-Path: owner-freebsd-security@freefall.freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.18]) by root.com (8.7.6/8.6.5) with ESMTP id PAA02587 for <dg@root.com>; Tue, 4 Feb 1997 15:31:37 -0800 (PST)
Received: from localhost (daemon@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA20937;
          Tue, 4 Feb 1997 15:07:46 -0800 (PST)
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA20871
          for security-outgoing; Tue, 4 Feb 1997 15:07:12 -0800 (PST)
Received: from cs.pdx.edu (root@cs.pdx.edu [204.203.64.22])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA20856
          for <freebsd-security@FreeBSD.org>; Tue, 4 Feb 1997 15:07:08 -0800 (PST)
Received: from sirius.cs.pdx.edu (root@sirius.cs.pdx.edu [204.203.64.13])
	by cs.pdx.edu (8.8.5/8.8.5) with ESMTP id PAA23337
	for <freebsd-security@FreeBSD.org>; Tue, 4 Feb 1997 15:07:01 -0800 (PST)
Received: from localhost (jrb@localhost [127.0.0.1])
	by sirius.cs.pdx.edu (8.8.5/8.8.5) with ESMTP id PAA18695
	for <freebsd-security@FreeBSD.org>; Tue, 4 Feb 1997 15:06:59 -0800 (PST)
Message-Id: <199702042306.PAA18695@sirius.cs.pdx.edu>
To: freebsd-security@FreeBSD.ORG
Subject: release of ipsec for freebsd
In-reply-to: Your message of "Tue, 13 Aug 1996 09:48:47 +0200."
             <199608130748.AA198942528@euro.eurocontrol.fr> 
Date: Tue, 04 Feb 1997 15:06:58 -0800
From: Jim Binkley <jrb@cs.pdx.edu>
Sender: owner-security@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


If anyone should be interested in the IP Security WG efforts (IPSEC wg),
we have made a port of last summer's NRL/ipsec code for IPv4 (not v6)
into freebsd 2.1.0, which is our current Mobile-IP kernel src base.
This is NOT just mobile-ip oriented, but is aimed at more general network
security.  The src includes some test apps,  some but not all NRL
supplied utilities, some test apps of our own, and complete kernel src.
In order to get the release, please see
the web page: http://www.cs.pdx.edu/research/SMN/index.html,
and page down to  
"PSU IPSEC/FreeBSD port".  

You have to grab two gzip'ed tar archives, one at PSU, 
and one at MIT.  The latter is for the "export controlled" portion.  

a few feature (or lack thereof) points:

1. for IPv4, not IPv6
2. experimental!.  you must be a kernel hacker
3. NRL's ipsec was transport (socket) oriented.  We kept that
	and added a 1st cut routing binding too (you can view
	this as a virtual private network mechanism).
4. routes using route(8) or arp(8) can have a ESP/DES binding
	(and RSN will have an AH/<md5, etc> binding too).
5. our virtual tunnel driver which is part of our MIP implementation
	but is crucial to the IPSEC stuff too.
6. our Mobile-IP (MIP) kernel routing hacks which don't hurt anything normal 
	and can be ignored if you don't care about Mobile-IP.
7. a couple of simple tcp/udp apps to test and demo the 
	transport (socket) IPSEC bindings.
8. btw, the NRL key(8) utility has been renamed as ipkey(8), as 
	key() already existed.
9. includes (obviousally) NRL's key socket in its form as of last summer.

We are starting a majordomo mailing list at PSU.  the list
name is: freebsd-ipsec@cs.pdx.edu,  majordomo@cs.pdx.edu to join.

We do not guarantee to "maintain" this or fix bugs or whatever.  
We are however in the process of improving it and are hoping
to finish some parts, and fix some bugs in another release in
a few months.

				Jim Binkley
				jrb@cs.pdx.edu
	


------- End of Forwarded Message


From owner-freebsd-hackers  Tue Feb  4 23:29:12 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA09950
          for hackers-outgoing; Tue, 4 Feb 1997 23:29:12 -0800 (PST)
Received: from lassie.eunet.fi (lassie.eunet.fi [192.26.119.7])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id XAA09933
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 23:29:09 -0800 (PST)
Received: from tahko.lpr.carel.fi ([192.46.69.100]) by lassie.eunet.fi with SMTP id AA26859
  (5.67a/IDA-1.5 for <hackers@freebsd.org>); Wed, 5 Feb 1997 09:29:06 +0200
Received: from mercury.ps.carel.fi by tahko.lpr.carel.fi with ESMTP
	(8.7.5/1.1) id JAA06408; Wed, 5 Feb 1997 09:22:06 +0200 (EET)
Received: from sodium.ps.carel.fi (sodium.ps.carel.fi [194.137.216.111]) by mercury.ps.carel.fi (8.8.2/8.8.2) with SMTP id KAA13173; Wed, 5 Feb 1997 10:18:00 +0200 (EET)
Received: by sodium.ps.carel.fi with Microsoft Mail
	id <01BC1348.A65D80D0@sodium.ps.carel.fi>; Wed, 5 Feb 1997 09:40:40 +0200
Message-Id: <01BC1348.A65D80D0@sodium.ps.carel.fi>
From: Ari Suutari <ari.suutari@ps.carel.fi>
To: "'Charles Mott'" <cmott@srv.net>
Cc: Julian Elischer <julian@whistle.com>, Eivind Eklund
	 <eivind@dimaga.com>,
        Brian Somers <brian@awfulhak.demon.co.uk>,
        "hackers@freebsd.org" <hackers@freebsd.org>
Subject: RE: Single socket version of natd
Date: Wed, 5 Feb 1997 09:36:52 +0200
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi,

	Checking device address for each packet might be too slow.
	Maybe kill -HUP signal to natd could be used to force a device
	address lookup again. 

	Anyway, also I think that currently it might be good to
	have aliasing as a built-in feature of ppp also.

		Ari S.

	

-----Original Message-----
From:	Charles Mott [SMTP:cmott@srv.net]
Sent:	4. helmikuuta 1997 18:28
To:	Brian Somers
Cc:	Julian Elischer; Eivind Eklund; Brian Somers; Ari Suutari; hackers@freebsd.org
Subject:	Re: Single socket version of natd

The one situation I think is difficult for natd to handle is is when ppp 
is running in -auto mode, and it reconnects on each dial-in with a 
different dynamcially assigned address.

At the moment, natd can do device address lookup at startup, but to 
handle the above mentioned case, it would have to do a device address 
lookup for every packet.  Is it possible to do this?

I personally like having both ppp -alias as well as natd.  Having the 
software embedded in ppp and enabled with the -alias switch makes life 
very easy for a great number of less sophisticated users.

Charles Mott


From owner-freebsd-hackers  Wed Feb  5 00:06:49 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id AAA13753
          for hackers-outgoing; Wed, 5 Feb 1997 00:06:49 -0800 (PST)
Received: from csd.cs.technion.ac.il (csd.cs.technion.ac.il [132.68.32.8])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id AAA13736
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 00:06:39 -0800 (PST)
Received: from localhost (nadav@localhost) by csd.cs.technion.ac.il (8.6.11/8.6.10) with SMTP id KAA19592; Wed, 5 Feb 1997 10:04:59 +0200
X-Authentication-Warning: csd.cs.technion.ac.il: nadav owned process doing -bs
Date: Wed, 5 Feb 1997 10:04:58 +0200 (IST)
From: Nadav Eiron <nadav@cs.technion.ac.il>
X-Sender: nadav@csd
To: garman@phs.k12.ar.us
cc: Wolfgang Helbig <helbig@BA-Stuttgart.De>, hackers@freebsd.org
Subject: Re: CMD640b flaw workaround
In-Reply-To: <Mutt.19970204152524.garman@jason.garman.net>
Message-ID: <Pine.GSO.3.95-heb-2.07.970205100326.19548A-100000@csd>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk



On Tue, 4 Feb 1997, Jason Garman wrote:

> Nadav Eiron writes:
> > I tried installing the patches on my troubled 2.1.5R system, and it
> > doesn't cure my problem. I think I should describe my problem once again,
> > as it's not the classical CMD640 bug. I have a machine with a hard disk
> > (Quantum FireBall) and a CD (Creative x4), both on the primary channel.
> > The problem is that CD access is unreliable. It's most commonly seen when
> > I try to serve a CD directly via apache. Under heavy load, some of the
> > Apace processes will hang while accessing the CD like so:
> > 
> That's weird.  You're right, the patch won't fix this.  I have a CD and hd
> on my first channel, and it works fine here...
> 
> I know this isn't a really good `solution,' but how about switching the cd
> onto the second channel?

I haven't tried (it wasn't an option until the patch was available).
However, I suspect that 2.1.5 won't even recognize the CD there. I might
try it if I have the time, but I guess we *will* upgrade this machine to
SCSI and be over it once and for all. It simply doesn't have a free slot,
so upgrading to SCSI means replacing the whole thing...

> 
> Enjoy,
> -- 
> Jason Garman                             http://www.nesc.k12.ar.us/~garman/
> Student, Eleanor Roosevelt High School                 garman@phs.k12.ar.us
> 
Nadav


From owner-freebsd-hackers  Wed Feb  5 00:34:20 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id AAA17740
          for hackers-outgoing; Wed, 5 Feb 1997 00:34:20 -0800 (PST)
Received: from relay.nuxi.com (nuxi.ucdavis.edu [128.120.37.176])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA17722;
          Wed, 5 Feb 1997 00:34:17 -0800 (PST)
Received: from dragon.nuxi.com (reqa-024.ucdavis.edu [128.120.251.24]) by relay.nuxi.com (8.8.4/8.6.12) with ESMTP id AAA20376; Wed, 5 Feb 1997 00:34:31 -0800 (PST)
Received: (from obrien@localhost) by dragon.nuxi.com (8.8.4/8.7.3) id AAA02002; Wed, 5 Feb 1997 00:33:46 -0800 (PST)
Message-ID: <19970205003343.YB13323@dragon.nuxi.com>
Date: Wed, 5 Feb 1997 00:33:43 -0800
From: obrien@NUXI.com (David O'Brien)
To: imp@village.org (Warner Losh)
Cc: freebsd-ports@FreeBSD.ORG (FreeBSD ports list), hackers@FreeBSD.ORG
Subject: Re: conditionally including <sys/param.h>
References: <19970202135048.PN07710@dragon.nuxi.com> <199701280143.RAA06503@freefall.freebsd.org> <Pine.OSF.3.95q.970127210526.2115E-100000@uplink.eng.umd.edu> <E0vrw2G-0000I7-00@rover.village.org>
X-Mailer: Mutt 0.59-PL19
Mime-Version: 1.0
Organization: The NUXI *BSD group
X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3  90 76 5D 69 58 D9 98 7A
X-Pgp-Keyid: 34F9F9D5
In-Reply-To: <E0vrw2G-0000I7-00@rover.village.org>; from Warner Losh on Feb 4, 1997 18:20:28 -0700
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Warner Losh writes:
> In message <19970202135048.PN07710@dragon.nuxi.com> David O'Brien writes:
> : to get a new cpp symbol added (like __44bsd__ or something).
> 
> This is a bad idea, since it has lost a lot of its potential meaning
> with so many 44bsd derived systems that pick and chose between 4.4 and
> 4.4 Lite 2.

Then what would you suggest?  Are they really more different than all the
various sysVr4 that define __svr4__?  How close is Solaris, UnixWare, and
Irix?

I'm just trying to find something that will cover all the 4.4BSD derived
OS's.  What are the big divergances from each other that __44bsd__
wouldn't cover (from an application standpoint)?  Remember I'm trying to
catch things like sys_errlist[], termios, /var/mail, /usr/sbin/sendmail,
etc.  

Everyone will acknowlege that for kernel stuff __FreeBSD__, etc.
should be used.  But I still think __44bsd__ is fine where we would
already do the #if (BSD > xyx) test or defined(__FreeBSD__) ||
defined(__NetBSD__) ,etc.

-- 
-- David	(obrien@NUXI.com  -or-  obrien@FreeBSD.org)

From owner-freebsd-hackers  Wed Feb  5 00:59:01 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id AAA23810
          for hackers-outgoing; Wed, 5 Feb 1997 00:59:01 -0800 (PST)
Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA23748
          for <FreeBSD-hackers@FreeBSD.ORG>; Wed, 5 Feb 1997 00:58:49 -0800 (PST)
Received: (from jhay@localhost)
	by zibbi.mikom.csir.co.za (8.8.5/8.8.5) id KAA28087;
	Wed, 5 Feb 1997 10:55:28 +0200 (SAT)
From: John Hay <jhay@zibbi.mikom.csir.co.za>
Message-Id: <199702050855.KAA28087@zibbi.mikom.csir.co.za>
Subject: Re: xntp3-5.89.2 & FreeBSD 2.2-GAMMA won't compile
In-Reply-To: <32F7E2AA.59E2B600@engr.orst.edu> from Steve Logue at "Feb 4, 97 05:30:18 pm"
To: logue@engr.orst.edu (Steve Logue)
Date: Wed, 5 Feb 1997 10:55:28 +0200 (SAT)
Cc: joerg_wunsch@uriah.heep.sax.de, FreeBSD-hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL24 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 
> What about all the xntpd 3.4e code in the src of FreeBSD - that needs to
> be replace while we're at it?  Thanks -STEVEl
> 

Well xntpd 3.5.xx is still changing so frequently that I don't think it
is usefull to put it in the FreeBSD tree yet. And it isn't as if v 3.4e
is lacking some serious feature, or am I missing something?

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

From owner-freebsd-hackers  Wed Feb  5 01:23:18 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id BAA27381
          for hackers-outgoing; Wed, 5 Feb 1997 01:23:18 -0800 (PST)
Received: from sax.sax.de (sax.sax.de [193.175.26.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id BAA27342
          for <freebsd-hackers@freebsd.org>; Wed, 5 Feb 1997 01:23:05 -0800 (PST)
Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA01582; Wed, 5 Feb 1997 10:20:19 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id KAA09915; Wed, 5 Feb 1997 10:08:54 +0100 (MET)
Message-ID: <Mutt.19970205100854.j@uriah.heep.sax.de>
Date: Wed, 5 Feb 1997 10:08:54 +0100
From: j@uriah.heep.sax.de (J Wunsch)
To: stevel@logues.rhn.orst.edu (stevel)
Cc: freebsd-hackers@freebsd.org, upsd-list@ww.net
Subject: Re: UPS daemon
References: <Pine.BSF.3.95.970204210718.6543A-100000@logues.rhn.orst.edu>
X-Mailer: Mutt 0.55-PL10
Mime-Version: 1.0
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <Pine.BSF.3.95.970204210718.6543A-100000@logues.rhn.orst.edu>; from stevel on Feb 4, 1997 21:17:44 -0800
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

As stevel wrote:

> Is there anyone working on a generic UPS daemon?  I know someone is
> working on one specifically for APC Smart UPS's, but this isn't usefull to
> the majority of people.

Andrey Stesin's upsd was designed to be a generic UPSd, but i think it
only ever evolved to get the APC Smart UPS module.

It got very silent lately on the upsd mailing list, too bad.

You should be able to find that stuff on ftp://ftp.ww.net/.

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

From owner-freebsd-hackers  Wed Feb  5 02:01:27 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA04338
          for hackers-outgoing; Wed, 5 Feb 1997 02:01:27 -0800 (PST)
Received: from gw-nl1.philips.com (gw-nl1.philips.com [192.68.44.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA04326
          for <freebsd-hackers@freebsd.org>; Wed, 5 Feb 1997 02:01:19 -0800 (PST)
Received: (from nobody@localhost) 
	by gw-nl1.philips.com (8.6.10/8.6.10-0.994n-08Nov95) id LAA08789
	for <freebsd-hackers@freebsd.org>; Wed, 5 Feb 1997 11:01:12 +0100
Received: from unknown(130.139.36.3) by gw-nl1.philips.com via smap (V1.3+ESMTP) with ESMTP
	id sma008604; Wed Feb  5 11:00:14 1997
Received: from giga.lss.cp.philips.com (giga.lss.cp.philips.com [130.144.199.31]) 
	by smtprelay.nl.cis.philips.com (8.6.10/8.6.10-1.2.1m-970131) with SMTP id LAA27209
	for <freebsd-hackers@freebsd.org>; Wed, 5 Feb 1997 11:00:13 +0100
Received: by giga.lss.cp.philips.com (8.8.5/1.63)
    id LAA27316; Wed, 5 Feb 1997 11:00:12 +0100 (MET)
From: W.Belgers@nl.cis.philips.com (Walter Belgers)
Message-Id: <199702051000.LAA27316@giga.lss.cp.philips.com>
Subject: Re: NIS/uids
To: freebsd-hackers@freebsd.org
Date: Wed, 5 Feb 1997 11:00:12 +0100 (MET)
In-Reply-To: <199702042306.QAA13339@phaeton.artisoft.com> from Terry Lambert at "Feb 4, 97 04:06:53 pm"
Organisation: Origin IT Systems Management /Nederland B.V.
X-URL: http://giga.lss.cp.philips.com/cgi-bin/walter.cgi
X-Mailer: ELM [version 2.4ME+ PL19 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Terry Lambert writes:
> > > The problem now is that the security on my system has become dependant
> > > on that of the NIS server. If I am root on the NIS server I can change
> > > the uid of "user" into any user including root and make use of it on my
> > > system.
> > 
> It makes sense to me that "sensitive" user and group ID's perhaps
> should not be honored when they come in via NFS... ie: user root
> or bin, etc., or group bin or kmem.

This has turned out to become a discussion about whether or not you
should trust your NIS server, but that's not what I wanted to know.
Let's assume I do not trust the uid's coming from the NIS server but I
still do want to use NIS (for passwd/homedir/gecos/whatever).

Why does FreeBSD give me troubles when I override the uid in the local
password file?

a) taking uid from NIS:
[/] root@giga# grep john /etc/master.passwd
+john:::::0:0:John Doe:/home/john:/usr/local/bin/tcsh
[/] root@giga# ypmatch john passwd
john::1234:1234:John Doe:/home/john:/bin/tcsh
[/] root@giga# su - john
> id
uid=1234(john) gid=1234 groups=1234
> from
>From walter Wed Feb  5 09:49:57 1997
>


b) overriding the uid:
[/] root@giga# grep john /etc/master.passwd
+john::1234:1234::0:0:John Doe:/home/john:/usr/local/bin/tcsh
[/] root@giga# ypmatch john passwd
john::1234:1234:John Doe:/home/john:/bin/tcsh
[/] root@giga# su - john
> id
uid=1234 gid=1234 groups=1234
> from
from: no password file entry for you.
>


Walter.
-- 
Ir. W.H.B. Belgers, Internet Security Specialist        phone: +31 40 2782753
Origin IT Syst.Man. /Nederland bv, Bldg VN-513   email:   fax: +31 40 2784697
P.O. Box 218, 5600 MD Eindhoven, Netherlands     W.Belgers@nl.cis.philips.com
non-business-email: walter@giga.nl   -web: http://www.IAEhv.nl/users/gigawalt

From owner-freebsd-hackers  Wed Feb  5 02:55:33 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA07063
          for hackers-outgoing; Wed, 5 Feb 1997 02:55:33 -0800 (PST)
Received: from pcpsj.pfcs.com (eZEESXsQrsQ/RLajsDK7oNNwaLnWNrZG@harlan.fred.net [205.252.219.31])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id CAA07058
          for <FreeBSD-hackers@FreeBSD.ORG>; Wed, 5 Feb 1997 02:55:28 -0800 (PST)
Received: from mumps.pfcs.com (mumps.pfcs.com [192.52.69.11]) by pcpsj.pfcs.com (8.6.12/8.6.9) with SMTP id FAA00762; Wed, 5 Feb 1997 05:55:23 -0500
Received: from localhost by mumps.pfcs.com with SMTP id AA21688
  (5.67b/IDA-1.5); Wed, 5 Feb 1997 05:55:22 -0500
To: John Hay <jhay@zibbi.mikom.csir.co.za>
Cc: logue@engr.orst.edu (Steve Logue), joerg_wunsch@uriah.heep.sax.de,
        FreeBSD-hackers@FreeBSD.ORG
Subject: Re: xntp3-5.89.2 & FreeBSD 2.2-GAMMA won't compile 
In-Reply-To: Your message of "Sat, 05 Feb 1997 10:55:28 +0200."
             <199702050855.KAA28087@zibbi.mikom.csir.co.za> 
Date: Wed, 05 Feb 1997 05:55:21 -0500
Message-Id: <21686.855140121@mumps.pfcs.com>
From: Harlan Stenn <Harlan.Stenn@pfcs.com>
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The problem with "older" releases of xntpd are that they have many
serious bugs which affect how well they keep time between peers and how
they handle reference clocks.

The 3-5.x stuff does change frequently, however (although not as often
as I've seen lsof change!).

I'd say we're in late-beta with xntpd.  We'll be at gamma as soon as we
can find and fix the race condition some folks are seeing on some
platforms, with a production release soon after.  Even then, Dave Mills
doesn't think xntp4 is all that far off.

H

From owner-freebsd-hackers  Wed Feb  5 03:19:40 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id DAA07836
          for hackers-outgoing; Wed, 5 Feb 1997 03:19:40 -0800 (PST)
Received: from whale.gu.kiev.ua (proxy.gu.kiev.ua [194.93.190.4])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA07824
          for <freebsd-hackers@freebsd.org>; Wed, 5 Feb 1997 03:19:31 -0800 (PST)
Received: from trifork.gu.net (trifork.gu.net [194.93.190.194]) by whale.gu.kiev.ua (8.8.5/8.7.3) with SMTP id NAA45702; Wed, 5 Feb 1997 13:16:56 +0200
Date: Wed, 5 Feb 1997 15:16:11 +0200 (EET)
From: Andrew Stesin <stesin@gu.net>
Reply-To: stesin@gu.net
To: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de>
cc: stevel <stevel@logues.rhn.orst.edu>, freebsd-hackers@freebsd.org,
        upsd-list@ww.net
Subject: Re: UPS daemon
In-Reply-To: <Mutt.19970205100854.j@uriah.heep.sax.de>
Message-ID: <Pine.BSF.3.95.970205151521.2322A-100000@trifork.gu.net>
X-NCC-Reg-ID: ua.gu
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


On Wed, 5 Feb 1997, J Wunsch wrote:

> Andrey Stesin's upsd

	Sorry Jorg, that wasn't me -- it was Alex Yushin who wrote
	it.

> You should be able to find that stuff on ftp://ftp.ww.net/.
                                           ^^^^^^^^^^^^^^^^^
	Yep.

Best regards,
Andrew Stesin

nic-hdl: ST73-RIPE



From owner-freebsd-hackers  Wed Feb  5 04:29:29 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id EAA10647
          for hackers-outgoing; Wed, 5 Feb 1997 04:29:29 -0800 (PST)
Received: from narcissus.ml.org (root@brosenga.Pitzer.edu [134.173.120.201])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA10642
          for <freebsd-hackers@freebsd.org>; Wed, 5 Feb 1997 04:29:27 -0800 (PST)
Received: (from ben@localhost) by narcissus.ml.org (8.7.5/8.7.3) id EAA25057; Wed, 5 Feb 1997 04:29:26 -0800 (PST)
Date: Wed, 5 Feb 1997 04:29:26 -0800 (PST)
From: Stranger Bone <ben@narcissus.ml.org>
To: Walter Belgers <W.Belgers@nl.cis.philips.com>
cc: freebsd-hackers@freebsd.org
Subject: Re: NIS/uids
In-Reply-To: <199702051000.LAA27316@giga.lss.cp.philips.com>
Message-ID: <Pine.BSF.3.91.970205042802.25052A-100000@narcissus.ml.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hmm, this message confused my copy of Pine mightily.  It got split into 
two messages:

>From W.Belgers@nl.cis.philips.comWed Feb  5 04:27:49 1997
Date: Wed, 5 Feb 1997 11:00:12 +0100 (MET)
From: Walter Belgers <W.Belgers@nl.cis.philips.com>
To: freebsd-hackers@freebsd.org
Subject: Re: NIS/uids

Terry Lambert writes:
> > > The problem now is that the security on my system has become dependant
> > > on that of the NIS server. If I am root on the NIS server I can change
> > > the uid of "user" into any user including root and make use of it on my
> > > system.
> > 
> It makes sense to me that "sensitive" user and group ID's perhaps
> should not be honored when they come in via NFS... ie: user root
> or bin, etc., or group bin or kmem.

This has turned out to become a discussion about whether or not you
should trust your NIS server, but that's not what I wanted to know.
Let's assume I do not trust the uid's coming from the NIS server but I
still do want to use NIS (for passwd/homedir/gecos/whatever).

Why does FreeBSD give me troubles when I override the uid in the local
password file?

a) taking uid from NIS:
[/] root@giga# grep john /etc/master.passwd
+john:::::0:0:John Doe:/home/john:/usr/local/bin/tcsh
[/] root@giga# ypmatch john passwd
john::1234:1234:John Doe:/home/john:/bin/tcsh
[/] root@giga# su - john
> id
uid=1234(john) gid=1234 groups=1234
> from

And the next one:

>From the-concourse-on-highWed Feb  5 04:27:54 1997


b) overriding the uid:
[/] root@giga# grep john /etc/master.passwd
+john::1234:1234::0:0:John Doe:/home/john:/usr/local/bin/tcsh
[/] root@giga# ypmatch john passwd
john::1234:1234:John Doe:/home/john:/bin/tcsh
[/] root@giga# su - john
> id
uid=1234 gid=1234 groups=1234
> from
from: no password file entry for you.
>


Walter.
-- 
Ir. W.H.B. Belgers, Internet Security Specialist        phone: +31 40 2782753
Origin IT Syst.Man. /Nederland bv, Bldg VN-513   email:   fax: +31 40 2784697
P.O. Box 218, 5600 MD Eindhoven, Netherlands     W.Belgers@nl.cis.philips.com
non-business-email: walter@giga.nl   -web: http://www.IAEhv.nl/users/gigawalt


I'm guessing that that "from" did the trick.



 Ben

"You have your mind on computers, it seems."


From owner-freebsd-hackers  Wed Feb  5 05:17:31 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id FAA14124
          for hackers-outgoing; Wed, 5 Feb 1997 05:17:31 -0800 (PST)
Received: from po1.glue.umd.edu (root@po1.glue.umd.edu [129.2.128.44])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA14105;
          Wed, 5 Feb 1997 05:17:26 -0800 (PST)
Received: from gilligan.eng.umd.edu (gilligan.eng.umd.edu [129.2.103.21]) by po1.glue.umd.edu (8.8.5/8.7.3) with ESMTP id IAA01610; Wed, 5 Feb 1997 08:17:19 -0500 (EST)
Received: from localhost (chuckr@localhost) by gilligan.eng.umd.edu (8.8.5/8.7.3) with SMTP id IAA12559; Wed, 5 Feb 1997 08:17:18 -0500 (EST)
X-Authentication-Warning: gilligan.eng.umd.edu: chuckr owned process doing -bs
Date: Wed, 5 Feb 1997 08:17:18 -0500 (EST)
From: Chuck Robey <chuckr@glue.umd.edu>
X-Sender: chuckr@gilligan.eng.umd.edu
To: "David O'Brien" <obrien@NUXI.com>
cc: Warner Losh <imp@village.org>,
        FreeBSD ports list <freebsd-ports@freebsd.org>, hackers@freebsd.org
Subject: Re: conditionally including <sys/param.h>
In-Reply-To: <19970205003343.YB13323@dragon.nuxi.com>
Message-ID: <Pine.OSF.3.95q.970205081326.9802A-100000@gilligan.eng.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Wed, 5 Feb 1997, David O'Brien wrote:

> Warner Losh writes:
> > In message <19970202135048.PN07710@dragon.nuxi.com> David O'Brien writes:
> > : to get a new cpp symbol added (like __44bsd__ or something).
> > 
> > This is a bad idea, since it has lost a lot of its potential meaning
> > with so many 44bsd derived systems that pick and chose between 4.4 and
> > 4.4 Lite 2.
> 
> Then what would you suggest?  Are they really more different than all the
> various sysVr4 that define __svr4__?  How close is Solaris, UnixWare, and
> Irix?
> 
> I'm just trying to find something that will cover all the 4.4BSD derived
> OS's.  What are the big divergances from each other that __44bsd__
> wouldn't cover (from an application standpoint)?  Remember I'm trying to
> catch things like sys_errlist[], termios, /var/mail, /usr/sbin/sendmail,
> etc.  
> 
> Everyone will acknowlege that for kernel stuff __FreeBSD__, etc.
> should be used.  But I still think __44bsd__ is fine where we would
> already do the #if (BSD > xyx) test or defined(__FreeBSD__) ||
> defined(__NetBSD__) ,etc.

David, I don't understand why you don't want to use __FreeBSD__,
__NetBSD__, and __OpenBSD__ for non-kernel stuff.  The __44bsd__ thing
doesn't exist, and if you start it, 75% of FreeBSD folks and ALL of
everyone else in NetBSD and OpenBSD will be out in the cold.

I probably misunderstand part, but what functionality will be gained from
adding __44bsd__?  I want to note that the approach I'm pushing works now
for Xfree86 just fine.

----------------------------+-----------------------------------------------
Chuck Robey                 | Interests include any kind of voice or data 
chuckr@eng.umd.edu          | communications topic, C programming, and Unix.
9120 Edmonston Ct #302      |
Greenbelt, MD 20770         | I run Journey2 and picnic, both FreeBSD
(301) 220-2114              | version 3.0 current -- and great FUN!
----------------------------+-----------------------------------------------


From owner-freebsd-hackers  Wed Feb  5 06:04:36 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id GAA16060
          for hackers-outgoing; Wed, 5 Feb 1997 06:04:36 -0800 (PST)
Received: from lupin.csv.warwick.ac.uk (lupin.csv.warwick.ac.uk [137.205.192.14])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA16046
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 06:04:20 -0800 (PST)
From: Mr M P Searle <csubl@csv.warwick.ac.uk>
Message-Id: <25973.199702051403@lupin.csv.warwick.ac.uk>
Received: by lupin.csv.warwick.ac.uk
	id OAA25973; Wed, 5 Feb 1997 14:03:40 GMT
Subject: What happened to the splash screen?
To: hackers@freebsd.org
Date: Wed, 5 Feb 1997 14:03:37 +0000 (GMT)
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

There was a discussion on this list a while ago about a possible
'splash screen' while booting - I remember a lot of suggestions
about it, but did it ever get done? (if so, can someone send me
the patches?)

Thanks, Michael.
 

From owner-freebsd-hackers  Wed Feb  5 06:38:37 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id GAA17911
          for hackers-outgoing; Wed, 5 Feb 1997 06:38:37 -0800 (PST)
Received: from spoon.beta.com (root@[199.165.180.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA17906
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 06:38:33 -0800 (PST)
Received: from spoon.beta.com (mcgovern@localhost [127.0.0.1]) by spoon.beta.com (8.8.4/8.6.9) with ESMTP id JAA08103; Wed, 5 Feb 1997 09:38:23 -0500 (EST)
Message-Id: <199702051438.JAA08103@spoon.beta.com>
To: dg@root.com
cc: hackers@freebsd.org
Subject: Re: Cyclades driver causes kernel panic 
In-reply-to: Your message of "Tue, 04 Feb 1997 20:00:33 PST."
             <199702050400.UAA03566@root.com> 
Date: Wed, 05 Feb 1997 09:38:23 -0500
From: "Brian J. McGovern" <mcgovern@spoon.beta.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

David,
	Could you please tell me what version those patches are
based against? I tried throwing them up against 2.2-BETA,and at least
2 hunks failed (one in locore.s, and one on pmap.c). I don't mind
switching versions, as long as I know which to use.

	Anyhow, I tried hand editing the files, and removing PG_N where it
occured, and it didn't fix the problem. Just thoug htyou might like to know.

Thanks for the help. I'm going to keep tinkering.
	-Brian

From owner-freebsd-hackers  Wed Feb  5 06:43:27 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id GAA18119
          for hackers-outgoing; Wed, 5 Feb 1997 06:43:27 -0800 (PST)
Received: from ravenock.cybercity.dk (ravenock.cybercity.dk [194.16.57.32])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA18113
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 06:43:23 -0800 (PST)
Received: (from sos@localhost) by ravenock.cybercity.dk (8.8.5/8.7.3) id PAA00531; Wed, 5 Feb 1997 15:45:03 +0100 (MET)
From: Søren Schmidt <sos@ravenock.cybercity.dk>
Message-Id: <199702051445.PAA00531@ravenock.cybercity.dk>
Subject: Re: What happened to the splash screen?
In-Reply-To: <25973.199702051403@lupin.csv.warwick.ac.uk> from Mr M P Searle at "Feb 5, 97 02:03:37 pm"
To: csubl@csv.warwick.ac.uk (Mr M P Searle)
Date: Wed, 5 Feb 1997 15:44:54 +0100 (MET)
Cc: hackers@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL30 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In reply to Mr M P Searle who wrote:
> There was a discussion on this list a while ago about a possible
> 'splash screen' while booting - I remember a lot of suggestions
> about it, but did it ever get done? (if so, can someone send me
> the patches?)

Uhm, the basic support has been added to syscons, all that is needed
is a function to read the actual image and put it into the videomemory
depending on what mode has been chosen.

If you define SC_SPLASH_SCREEN syscons will show the splashscreen
(a 320x200 picture containing whatever noise was in video memory)
on boot, you can then toggle between the splash and normal screen
with NumLock (a hack for now is configurable via the keymap).

There is work under way to get it finished....

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Søren Schmidt               (sos@FreeBSD.org)               FreeBSD Core Team
                Even more code to hack -- will it ever end
..

From owner-freebsd-hackers  Wed Feb  5 06:44:54 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id GAA18221
          for hackers-outgoing; Wed, 5 Feb 1997 06:44:54 -0800 (PST)
Received: from root.com (implode.root.com [198.145.90.17])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA18215
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 06:44:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id GAA08599; Wed, 5 Feb 1997 06:44:53 -0800 (PST)
Message-Id: <199702051444.GAA08599@root.com>
X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol
To: "Brian J. McGovern" <mcgovern@spoon.beta.com>
cc: hackers@freebsd.org
Subject: Re: Cyclades driver causes kernel panic 
In-reply-to: Your message of "Wed, 05 Feb 1997 09:38:23 EST."
             <199702051438.JAA08103@spoon.beta.com> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Wed, 05 Feb 1997 06:44:53 -0800
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>David,
>	Could you please tell me what version those patches are
>based against? I tried throwing them up against 2.2-BETA,and at least
>2 hunks failed (one in locore.s, and one on pmap.c). I don't mind
>switching versions, as long as I know which to use.
>
>	Anyhow, I tried hand editing the files, and removing PG_N where it
>occured, and it didn't fix the problem. Just thoug htyou might like to know.

   Damn. Yes, just removing  PG_N from pmap.c and locore.s is sufficient. I'm
a little surprised by this news since it seemed to fix it for someone else.
Next idea: Can you get the "CYTEST.EXE" program from Cyclades ftp site and
change the memory area that it uses to the >1MB setting? (You'll need to
boot DOS, sorry). It defaults to 640K-1MB area, and there is a slight chance
that this might be part of the problem. Just a wild idea, but worth a try.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project

From owner-freebsd-hackers  Wed Feb  5 07:16:20 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id HAA25457
          for hackers-outgoing; Wed, 5 Feb 1997 07:16:20 -0800 (PST)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id HAA25341;
          Wed, 5 Feb 1997 07:16:10 -0800 (PST)
Received: from rover.village.org [127.0.0.1] 
	by rover.village.org with esmtp (Exim 0.56 #1)
	id E0vs94u-0000u5-00; Wed, 5 Feb 1997 08:16:04 -0700
To: obrien@NUXI.com (David O'Brien)
Subject: Re: conditionally including <sys/param.h> 
Cc: freebsd-ports@freebsd.org (FreeBSD ports list), hackers@freebsd.org
In-reply-to: Your message of "Wed, 05 Feb 1997 00:33:43 PST."
		<19970205003343.YB13323@dragon.nuxi.com> 
References: <19970205003343.YB13323@dragon.nuxi.com>  <19970202135048.PN07710@dragon.nuxi.com> <199701280143.RAA06503@freefall.freebsd.org> <Pine.OSF.3.95q.970127210526.2115E-100000@uplink.eng.umd.edu> <E0vrw2G-0000I7-00@rover.village.org> 
Date: Wed, 05 Feb 1997 08:16:03 -0700
From: Warner Losh <imp@village.org>
Message-Id: <E0vs94u-0000u5-00@rover.village.org>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <19970205003343.YB13323@dragon.nuxi.com> David O'Brien writes:
: Then what would you suggest?  Are they really more different than all the
: various sysVr4 that define __svr4__?  How close is Solaris, UnixWare, and
: Irix?

Ummm, they don't all define svr4 in all versions.  Solaris didn't
define it until at least the 3.0 release of the C compilers.  I'm not
sure if the current gnu tools define this for all of these systems.
And they all have sys/param.h :-

: I'm just trying to find something that will cover all the 4.4BSD derived
: OS's.  What are the big divergances from each other that __44bsd__
: wouldn't cover (from an application standpoint)?  Remember I'm trying to
: catch things like sys_errlist[], termios, /var/mail, /usr/sbin/sendmail,
: etc

Better to include sys/param.h, from a portability standpoint, and
check to see if BSD is defined and larger than a certain value.  The
hard part is knowing if sys/param.h will be there.

: Everyone will acknowlege that for kernel stuff __FreeBSD__, etc.
: should be used.  But I still think __44bsd__ is fine where we would
: already do the #if (BSD > xyx) test or defined(__FreeBSD__) ||
: defined(__NetBSD__) ,etc.

Yes, but there are enough "dusty deck" systems out there that software
authors will still need to do other checks.  It would be better to
find a foolproof way of knowing when sys/param.h is available (or at
least when it generally isn't).

Most of the examples that you sighted can be handled better by other
means.  Don't declare sys_errlist at all, rather use strerror() or
#include <errno.h> (which is fairly standard).  Don't use hard wired
path names, but rather the standard ones defined in pathnames.h.
You'll likely have to have a fallback for that strategy as well.

Also, as time moves forward, some new systems will adopt parts of the
4.4 tree.  Do you really want to have things like:

#if defined(__bsd44__) || (defined(SOLARIS) && SOLARIS >= 207) ...

in the sources?  They quickly get out of hand.

Many of the ports have 2-3 lines of ifdefs to include stdlib.h, when
instead they should have a single #ifdef __STDC__ in its place.

Had BSD 4.4 come out with this symbol, things would be a little
different.  However, it didn't think that it would be worth the
portibility hassles at this point, since it would take time for this
symbol to propigate to all flavors of BSD.  2.2 is almost out the
door, OpenBSD 2.0 is on the streets (and will be for a while).  Netbsd
1.2 is also on the streets and likely will be for a while too.

I guess I'm just showing my years of riding heard on the OI/uib source
tree which was generally portable to the point that the compile time
(45 minutes to an hour) usually dominated the porting time (well, and
sometimes it was the licenese manager third party code too).

Warner

From owner-freebsd-hackers  Wed Feb  5 08:20:46 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id IAA01578
          for hackers-outgoing; Wed, 5 Feb 1997 08:20:46 -0800 (PST)
Received: from Mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA01523
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 08:20:38 -0800 (PST)
Received: from Mars.mcs.net (ljo@Mars.mcs.com [192.160.127.85]) by Mailbox.mcs.com (8.8.5/8.8.2) with ESMTP id KAA28504; Wed, 5 Feb 1997 10:20:37 -0600 (CST)
Received: (from ljo@localhost) by Mars.mcs.net (8.8.5/8.8.2) id KAA25043; Wed, 5 Feb 1997 10:20:36 -0600 (CST)
From: Lars Jonas Olsson <ljo@mcs.net>
Message-Id: <199702051620.KAA25043@Mars.mcs.net>
Subject: sigwait and threads?
To: hackers@freebsd.org
Date: Wed, 5 Feb 1997 10:20:35 -0600 (CST)
Cc: ljo@mcs.net
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

 The "Threads primer" book by Lewis and Berg recommends using sigwait
for signal handling in multi-threaded applications. FreeBSD doesn't
have a sigwait though. Should we get one? Or is another method for
signal handling recommended?

 I've got a multi-threaded application that currently runs on SCO
UnixWare 2.1 that I also want to be able to run on FreeBSD. This
application uses sigwait and no signal handlers.

Jonas

From owner-freebsd-hackers  Wed Feb  5 09:14:25 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA29936
          for hackers-outgoing; Wed, 5 Feb 1997 09:14:25 -0800 (PST)
Received: from spoon.beta.com (root@[199.165.180.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA29829
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 09:14:17 -0800 (PST)
Received: from spoon.beta.com (mcgovern@localhost [127.0.0.1]) by spoon.beta.com (8.8.4/8.6.9) with ESMTP id MAA08778; Wed, 5 Feb 1997 12:14:11 -0500 (EST)
Message-Id: <199702051714.MAA08778@spoon.beta.com>
To: dg@root.com, hackers@freebsd.org, support@cyclades.com
Subject: Re: Cyclades driver causes kernel panic 
In-reply-to: Your message of "Wed, 05 Feb 1997 07:18:17 PST."
             <199702051518.HAA08985@root.com> 
Date: Wed, 05 Feb 1997 12:14:10 -0500
From: "Brian J. McGovern" <mcgovern@spoon.beta.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

David,
	The machine I'm trying to run the Cyclades card won't run in 
'deturbo', or if I disable caching. I noticed an entry for "ISA shared
memory" in the PNP setup area. It had a size from 16K to 96K, starting
at C8000, incrementing both size and start by 16K chunks. I've tinkered
with it, and put the Cyclades card below 1MB to try to get it to map in to this
range, but it didn't help. Also, in some configurations, it took out my Adaptec 2940
(when the range I defined got too high). Anyhow, just thought you'd like the
stream of info.
	-Brian

From owner-freebsd-hackers  Wed Feb  5 09:20:28 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA05397
          for hackers-outgoing; Wed, 5 Feb 1997 09:20:28 -0800 (PST)
Received: from hda.hda.com (ip57-max1-fitch.ziplink.net [199.232.245.57])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA05327
          for <freebsd-hackers@freebsd.org>; Wed, 5 Feb 1997 09:20:23 -0800 (PST)
Received: (from dufault@localhost) by hda.hda.com (8.6.12/8.6.12) id MAA01169; Wed, 5 Feb 1997 12:14:35 -0500
From: Peter Dufault <dufault@hda.com>
Message-Id: <199702051714.MAA01169@hda.hda.com>
Subject: Re: probing scsi bus after boot?
In-Reply-To: <Mutt.19970204225853.j@uriah.heep.sax.de> from J Wunsch at "Feb 4, 97 10:58:53 pm"
To: joerg_wunsch@uriah.heep.sax.de
Date: Wed, 5 Feb 1997 12:14:34 -0500 (EST)
Cc: freebsd-hackers@freebsd.org, jlk@pavilion.co.uk
X-Mailer: ELM [version 2.4ME+ PL25 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> As Josef Karthauser wrote:
> 
> > Either I use rmt, but I've not found a way of rmt'ing as root on the
> > remote site (please someone let me out of my misery.)
> 
> ~root/.rhost
> 
> It would be neat to see ssh support for this, though.
> 
> > 	# scsi -f /dev/rst0 -p
> > 	scsi: unable to open device /dev/rst0: Device not configured
> 
> Chicken-and-egg problem.  Don't use -p btw., use -r.  But still, you
> need at least one device that has been successfully probed on your
> SCSI bus before, in order to hook the `rescan' ioctl into the kernel
> (any device fits, so you could pick /dev/rsd0.ctl).
> 
> NB: this used to hang your machine with various SCSI adapters in the
> past, but recent 2.2 (and -current) systems seem to work well with it.

Once you've compiled with ssc:

> device      ssc0 at scbus? #SCSI control device

Make the scsi control device (minor number 49:

> mknod c 49 0 /dev/scsi.ctl

And apply a "probe all" to it:

> scsi -f /dev/scsi.ctl -p

Once in the past it would have reprobed all devices
on your SCSI bus.  I'm building a kernel to find out what it does
today.

-- 
Peter Dufault (dufault@hda.com)   Realtime Machine Control and Simulation
HD Associates, Inc.               Voice: 508 433 6936

From owner-freebsd-hackers  Wed Feb  5 09:23:09 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA10186
          for hackers-outgoing; Wed, 5 Feb 1997 09:23:09 -0800 (PST)
Received: from Guard.Polynet.Lviv.UA ([194.44.138.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA09106
          for <FreeBSD-hackers@FreeBSD.org>; Wed, 5 Feb 1997 09:22:33 -0800 (PST)
Received: (from smap@localhost) by Guard.Polynet.Lviv.UA (8.8.4/8.6.12) id TAA14360; Wed, 5 Feb 1997 19:19:55 +0200 (EET)
Received: from netsurfer.lp.lviv.ua(192.168.0.3) by Guard.Polynet.Lviv.UA via smap (V2.0beta)
	id xma014357; Wed, 5 Feb 97 19:19:49 +0200
Received: (from smap@localhost) by NetSurfer.lp.lviv.ua (8.8.5/8.6.12) id TAA18357; Wed, 5 Feb 1997 19:19:44 +0200 (EET)
Message-Id: <199702051719.TAA18357@NetSurfer.lp.lviv.ua>
Received: from ws37.lp.lviv.ua(192.168.0.37) by NetSurfer.lp.lviv.ua via smap (V2.0beta)
	id xma018353; Wed, 5 Feb 97 19:19:25 +0200
Comments: Authenticated sender is <ts@postoffice.lp.lviv.ua>
From: "Slavik Terletsky" <ts@polynet.lviv.ua>
Organization: State University "Lvivska Polytechnika"
To: stevel@logues.rhn.orst.edu
Date: Wed, 5 Feb 1997 19:21:54 +0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: UPS daemon
Reply-to: ts@polynet.lviv.ua
CC: FreeBSD-hackers@FreeBSD.org
Priority: normal
X-mailer: Pegasus Mail for Windows (v2.42a)
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

Hello
I managed to hack upsd. As most of ppl who has APC Smart UPS I use
it in a dumb mode (I had no info on the cabling UPS to my box).
You may change it the way you want to get your UPS work,
it is written in C.
Wanna deep your knowledge in ups daemons ? Then drop a note to
Harvey J. Stein <hjstein@math.huji.ac.il>, he made a "UPS HOWTO".
(I don't remember the http URL for this).
So, here it is:

UPS daemon for FreeBSD (2.1.5 - tested).
Interacts with APC Smart-UPS 1400 in a dumb mode.

Connection scheme:

UPS (pin, signal name)		PC (pin, signal name)
----------------------		---------------------
1 Shutdown		>----------->	4 Data Terminal Ready
2 Line Failed		>----------->	8 Clear To Send
4 Common		>----------->	5 Ground
5 Battery Low		>--------+-->	1 Data Carrier Detector
8 Battery (+24V)	>--|10K|-+


UPSD DESCRIPTION

usage: upsd <device> [wait [script]]

device	- device name upsd interacts thru (e.g. /dev/cuaa1)
wait	- time (secs) to wait before running script, (default value 0 sec).
script	- system shutdown script (default /etc/rc.shutdown).

Actions:
upsd logs all the changes of UPS status (power {up,down}, battery {low,ok}).
When "power down" and "battery low" upsd activates UPS SHUTDOWN signal, waits
for a <wait> seconds, and then runs system shutdown script - <script>.

Script sample:

#!/bin/sh
# Script is executed when system is going down.

PATH=/sbin:/bin:/usr/sbin:/usr/bin

echo "System is going DOWN right NOW" | wall

reboot


Upsd source:
/* UPS daemon
 * Copyright 1997 Slavik Terletsky. All rights reserved.
 * Author: Slavik Terletsky <ts@polynet.lviv.ua>
 * System: FreeBSD
 */
#include <stdio.h>
#include <stdlib.h>
#include <signal.h>
#include <syslog.h>
#include <unistd.h>
#include <varargs.h>
#include <fcntl.h>
#include <errno.h>
#include <sys/uio.h>
#include <sys/types.h>
#include <sys/ioctl.h>
#include <sys/ttycom.h>

int status;
int wait = 0;
FILE *fd;
char *scr = "/etc/rc.shutdown";
char *idf = "/var/run/upsd.pid";

void upsterm();
void upsdown(int);

int main(int argc, char *argv[]) {
 int pd;
 int zero = 0;
 char d5, d6, d7;
 char low = 0;
 char pow = 1;

 /* check arguments */
 switch(argc) {
 case  4:
 scr = argv[3];
 case  3:
 wait = atoi(argv[2]);
 case  2:
 break;
 default:
 fprintf(stderr, "usage: %s <device> [wait [script]]\n", argv[0]);
 exit(1);
 }

 /* check if script exists */
 if(!(fd = fopen(scr, "r"))) {
 fprintf(stderr, "fopen: %s: %s\n", scr, sys_errlist[errno]);
 exit(1);
 }
 fclose(fd);

 /* check if upsd is already running */
 if(fd = fopen(idf, "r")) {
 fprintf(stderr, "fopen: %s: File already exists\n", idf);
 exit(1);
 }

 /* become a daemon */
 switch(fork()) {
 case -1:	/* error */
 fprintf(stderr, "fork: %s\n", sys_errlist[errno]);
 exit(1);
 case  0:	/* child */
 break;
 default:	/* parent */
 exit(0);
 }

 /* save the pid */
 if(!(fd = fopen(idf, "w"))) {
 fprintf(stderr, "fopen: %s: %s\n", idf, sys_errlist[errno]);
 exit(1);
 }
 fprintf(fd, "%d\n", (int)getpid());
 fclose(fd);

 /* open monitor device */
 if((pd = open(argv[1], O_RDWR | O_NDELAY)) < 0) {
 fprintf(stderr, "open: %s: %s\n", argv[1], sys_errlist[errno]);
 exit(1);
 }

 /* daemon is alive */
 openlog("upsd", LOG_PID, LOG_DAEMON);
 syslog(LOG_INFO, "daemon started");

 /* signal reaction */
 (void)signal(SIGTERM, upsterm);

 /* monitor device */
 while(1) {
 /* clear bits */
 if(ioctl(pd, TIOCMSET, &zero) < 0) {
  fprintf(stderr, "ioctl: %s\n", sys_errlist[errno]);
  exit(1);
 }

 /* get device status */
 if(ioctl(pd, TIOCMGET, &status) < 0) {
  fprintf(stderr, "ioctl: %s\n", sys_errlist[errno]);
  exit(1);
 }

 /* determin status */
 d5 = status & 0x20;
 d6 = status & 0x40;
 d7 = status & 0x80;

 /* power up */
 if(!(d7 + d5)) {
  if(!pow) {
   syslog(LOG_CRIT, "power up");
   pow = 1;
  }
 /* power down */
 } else {
  if(pow) {
   syslog(LOG_CRIT, "power down");
   pow = 0;
  }
 }

 /* battery low */
 if(!d6 && !low) {
  syslog(LOG_ALERT, "battery low");
  low = 1;

  /* down ups */
  if(!pow) {
   upsdown(pd);
  }
 }

 /* battery ok */
 if(d6 && low) {
  syslog(LOG_CRIT, "battery ok");
  low = 0;
 }

 sleep(1);
 }

 /* not reached */
 return 0;

}

void upsterm() {
 /* log termination message */
 syslog(LOG_INFO, "daemon terminated");

 /* remove pid file */
 unlink(idf);

 exit(0);
}

void upsdown(int pd) {
 /* log shutdown message */
 syslog(LOG_ALERT, "system is going down");

 /* remove pid file */
 unlink(idf);

 /* save our filesystem */
 system("/bin/sync");
 system("/bin/sync");
 system("/bin/sync");

 /* shutdown ups */
 status = TIOCM_DTR;
 if(ioctl(pd, TIOCMSET, &status) < 0) {
 fprintf(stderr, "ioctl: %s\n", sys_errlist[errno]);
 exit(1);
 }

 /* wait and then run script */
 sleep(wait);
 system(scr);
}


# Slavik Terletsky      # University "Lvivska Poytechnika" #
# Network Administrator # mailto:ts@polynet.lviv.ua        #

From owner-freebsd-hackers  Wed Feb  5 09:46:52 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA17601
          for hackers-outgoing; Wed, 5 Feb 1997 09:46:52 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA17497;
          Wed, 5 Feb 1997 09:46:45 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id EAA12664; Thu, 6 Feb 1997 04:45:24 +1100
Date: Thu, 6 Feb 1997 04:45:24 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199702051745.EAA12664@godzilla.zeta.org.au>
To: imp@village.org, obrien@NUXI.com
Subject: Re: conditionally including <sys/param.h>
Cc: freebsd-ports@FreeBSD.ORG, hackers@FreeBSD.ORG
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>Most of the examples that you sighted can be handled better by other
>means.  Don't declare sys_errlist at all, rather use strerror() or
>#include <errno.h> (which is fairly standard).  Don't use hard wired

strerror() doesn't exist on old systems.

>Also, as time moves forward, some new systems will adopt parts of the
>4.4 tree.  Do you really want to have things like:
>
>#if defined(__bsd44__) || (defined(SOLARIS) && SOLARIS >= 207) ...

NOOOO! :-)

>Many of the ports have 2-3 lines of ifdefs to include stdlib.h, when
>instead they should have a single #ifdef __STDC__ in its place.

This is wrong.  __STDC__ has very little to do with the existence of
standard headers.  It has more to do with the ANSI conformance of the
current invocation of the compiler.  E.g., it is not defined for
`gcc -traditional', but running the compiler with different flags
does not make standard headers go away.

I think we should just use `#ifdef __FreeBSD__' and <sys/param.h> in
ports.  Original authors should use a better method to suit themselves.

Bruce

From owner-freebsd-hackers  Wed Feb  5 09:48:55 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA19911
          for hackers-outgoing; Wed, 5 Feb 1997 09:48:55 -0800 (PST)
Received: from hda.hda.com (ip57-max1-fitch.ziplink.net [199.232.245.57])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA19841
          for <freebsd-hackers@freebsd.org>; Wed, 5 Feb 1997 09:48:51 -0800 (PST)
Received: (from dufault@localhost) by hda.hda.com (8.6.12/8.6.12) id MAA01252; Wed, 5 Feb 1997 12:43:08 -0500
From: Peter Dufault <dufault@hda.com>
Message-Id: <199702051743.MAA01252@hda.hda.com>
Subject: Re: probing scsi bus after boot?
In-Reply-To: <199702051714.MAA01169@hda.hda.com> from Peter Dufault at "Feb 5, 97 12:14:34 pm"
To: dufault@hda.com (Peter Dufault)
Date: Wed, 5 Feb 1997 12:43:07 -0500 (EST)
Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@freebsd.org,
        jlk@pavilion.co.uk
X-Mailer: ELM [version 2.4ME+ PL25 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Re: Reprobe with no devices

> Once you've compiled with ssc:
> 
> > device      ssc0 at scbus? #SCSI control device

More like:

> device      su0  # Fixed entry devices
> device      ssc0 # SCSI control device

(...)

> And apply a "probe all" to it:
> 
> > scsi -f /dev/scsi.ctl -p

And it will find the devices on the bus and panic with a corrupt stack.

-- 
Peter Dufault (dufault@hda.com)   Realtime Machine Control and Simulation
HD Associates, Inc.               Voice: 508 433 6936

From owner-freebsd-hackers  Wed Feb  5 09:52:55 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA24179
          for hackers-outgoing; Wed, 5 Feb 1997 09:52:55 -0800 (PST)
Received: from zwei.siemens.at (zwei.siemens.at [193.81.246.12])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA24046
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 09:52:48 -0800 (PST)
Received: from sol1.gud.siemens.co.at (root@[10.1.143.100]) by zwei.siemens.at (8.7.5/8.7.3) with SMTP id SAA15895 for <hackers@freebsd.org>; Wed, 5 Feb 1997 18:53:40 +0100 (MET)
Received: from ws2301.gud.siemens.co.at by sol1.gud.siemens.co.at with smtp
	(Smail3.1.28.1 #7 for <hackers@freebsd.org>) 
	id m0vsBVr-00021LC; Wed, 5 Feb 97 18:52 MET
Received: by ws2301.gud.siemens.co.at (1.37.109.16/1.37)
	id AA254324944; Wed, 5 Feb 1997 18:49:04 +0100
From: "Hr.Ladavac" <lada@ws2301.gud.siemens.co.at>
Message-Id: <199702051749.AA254324944@ws2301.gud.siemens.co.at>
Subject: Re: sigwait and threads?
To: ljo@mcs.net (Lars Jonas Olsson)
Date: Wed, 5 Feb 1997 18:49:04 +0100 (MEZ)
Cc: hackers@freebsd.org, ljo@mcs.net
In-Reply-To: <199702051620.KAA25043@Mars.mcs.net> from "Lars Jonas Olsson" at Feb 5, 97 10:20:35 am
X-Mailer: ELM [version 2.4 PL24 ME8a]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

E-mail message from Lars Jonas Olsson contained:
> 
>  The "Threads primer" book by Lewis and Berg recommends using sigwait
> for signal handling in multi-threaded applications. FreeBSD doesn't
> have a sigwait though. Should we get one? Or is another method for
> signal handling recommended?
> 
>  I've got a multi-threaded application that currently runs on SCO
> UnixWare 2.1 that I also want to be able to run on FreeBSD. This
> application uses sigwait and no signal handlers.

sigwait() is a DCE-ism, or better yet, pthread Draft 4-ism.  At that
stage they had no support for per thread sigaction() nor signal()--as a
matter of fact, one was not allowed to use them.

Pthread Draft 7 introduced per-thread sigaction and signal semantics, and
I believe the Draft 10 and Standard have thrown the whole sigwait mess out.

AFAIK, the libc_r implements pthread Standard; you should be able to 
use sigaction instead.  It might be possible to write a wrapper around
it to implement sigwait for the DCE compatibility.  Andy(?) Birrell may
have further comments.

Another difference that DCE requires and Draft 8 has thrown out is 
pthread_detach().

/Marino
> 
> Jonas
> 


From owner-freebsd-hackers  Wed Feb  5 10:22:03 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id KAA22987
          for hackers-outgoing; Wed, 5 Feb 1997 10:22:03 -0800 (PST)
Received: from sax.sax.de (sax.sax.de [193.175.26.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA22951
          for <freebsd-hackers@freebsd.org>; Wed, 5 Feb 1997 10:21:58 -0800 (PST)
Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id TAA13776; Wed, 5 Feb 1997 19:20:33 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id TAA11325; Wed, 5 Feb 1997 19:06:21 +0100 (MET)
Message-ID: <Mutt.19970205190620.j@uriah.heep.sax.de>
Date: Wed, 5 Feb 1997 19:06:20 +0100
From: j@uriah.heep.sax.de (J Wunsch)
To: stesin@gu.net
Cc: stevel@logues.rhn.orst.edu (stevel), freebsd-hackers@freebsd.org,
        upsd-list@ww.net
Subject: Re: UPS daemon
References: <Mutt.19970205100854.j@uriah.heep.sax.de> <Pine.BSF.3.95.970205151521.2322A-100000@trifork.gu.net>
X-Mailer: Mutt 0.55-PL10
Mime-Version: 1.0
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <Pine.BSF.3.95.970205151521.2322A-100000@trifork.gu.net>; from Andrew Stesin on Feb 5, 1997 15:16:11 +0200
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

As Andrew Stesin wrote:

> > Andrey Stesin's upsd
> 
> 	Sorry Jorg, that wasn't me -- it was Alex Yushin who wrote
> 	it.

Yep, i've been confusing this -- sorry.

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

From owner-freebsd-hackers  Wed Feb  5 10:28:55 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id KAA03793
          for hackers-outgoing; Wed, 5 Feb 1997 10:28:55 -0800 (PST)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA03668
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 10:28:51 -0800 (PST)
Received: from rover.village.org [127.0.0.1] 
	by rover.village.org with esmtp (Exim 0.56 #1)
	id E0vsBzD-0001Sy-00; Wed, 5 Feb 1997 11:22:23 -0700
To: Michael Hancock <michaelh@cet.co.jp>
Subject: Re: bisdn 
Cc: grog@lemis.de, Terry Lambert <terry@lambert.org>,
        FreeBSD Hackers <hackers@freebsd.org>
In-reply-to: Your message of "Mon, 03 Feb 1997 18:09:46 +0900."
		<Pine.SV4.3.95.970203180631.8689A-100000@parkplace.cet.co.jp> 
References: <Pine.SV4.3.95.970203180631.8689A-100000@parkplace.cet.co.jp>  
Date: Wed, 05 Feb 1997 11:22:23 -0700
From: Warner Losh <imp@village.org>
Message-Id: <E0vsBzD-0001Sy-00@rover.village.org>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

: > > US West:	2D+B

US West in Colorado is 2B+D.  Flat rate of $70/mo/end.  $70 install
fee.  Unless you live in an area served by an older switch, then all
bets are off.  Guess which area I live in :-(.

Warner

From owner-freebsd-hackers  Wed Feb  5 10:31:15 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id KAA08249
          for hackers-outgoing; Wed, 5 Feb 1997 10:31:15 -0800 (PST)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA08206
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 10:31:12 -0800 (PST)
Received: from rover.village.org [127.0.0.1] 
	by rover.village.org with esmtp (Exim 0.56 #1)
	id E0vsC7b-0001UL-00; Wed, 5 Feb 1997 11:31:03 -0700
To: Terry Lambert <terry@lambert.org>
Subject: Re: bisdn 
Cc: michaelh@cet.co.jp (Michael Hancock), grog@lemis.de, hackers@freebsd.org
In-reply-to: Your message of "Tue, 04 Feb 1997 11:53:48 MST."
		<199702041853.LAA12924@phaeton.artisoft.com> 
References: <199702041853.LAA12924@phaeton.artisoft.com>  
Date: Wed, 05 Feb 1997 11:31:03 -0700
From: Warner Losh <imp@village.org>
Message-Id: <E0vsC7b-0001UL-00@rover.village.org>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <199702041853.LAA12924@phaeton.artisoft.com> Terry Lambert writes:
: See www.uswest.com.

Hmmm.  They must be wrong. :-)  The ISDN line we have into the office
that I'm typing this on has 2B+D.

Warner

From owner-freebsd-hackers  Wed Feb  5 10:37:52 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id KAA17178
          for hackers-outgoing; Wed, 5 Feb 1997 10:37:52 -0800 (PST)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA17017;
          Wed, 5 Feb 1997 10:37:43 -0800 (PST)
Received: from rover.village.org [127.0.0.1] 
	by rover.village.org with esmtp (Exim 0.56 #1)
	id E0vsCDt-0001VI-00; Wed, 5 Feb 1997 11:37:33 -0700
To: obrien@NUXI.com (David O'Brien)
Subject: Re: conditionally including <sys/param.h> 
Cc: freebsd-ports@freebsd.org (FreeBSD ports list), hackers@freebsd.org
In-reply-to: Your message of "Wed, 05 Feb 1997 00:33:43 PST."
		<19970205003343.YB13323@dragon.nuxi.com> 
References: <19970205003343.YB13323@dragon.nuxi.com>  <19970202135048.PN07710@dragon.nuxi.com> <199701280143.RAA06503@freefall.freebsd.org> <Pine.OSF.3.95q.970127210526.2115E-100000@uplink.eng.umd.edu> <E0vrw2G-0000I7-00@rover.village.org> 
Date: Wed, 05 Feb 1997 11:37:32 -0700
From: Warner Losh <imp@village.org>
Message-Id: <E0vsCDt-0001VI-00@rover.village.org>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <19970205003343.YB13323@dragon.nuxi.com> David O'Brien writes:
: Then what would you suggest?  Are they really more different than all the
: various sysVr4 that define __svr4__?  How close is Solaris, UnixWare, and
: Irix?

BTW, Solaris 2.5.1 with Sun Soft's 4.0 compiler doesn't define
__svr4__.  It defines __SVR4.

Warner

From owner-freebsd-hackers  Wed Feb  5 11:01:51 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA01920
          for hackers-outgoing; Wed, 5 Feb 1997 11:01:51 -0800 (PST)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA01915
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 11:01:44 -0800 (PST)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id LAA24428; Wed, 5 Feb 1997 11:01:07 -0800 (PST)
Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3)
	id sma024426; Wed Feb  5 11:00:53 1997
Received: (from archie@localhost) by bubba.whistle.com (8.7.5/8.6.12) id LAA23732; Wed, 5 Feb 1997 11:00:53 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199702051900.LAA23732@bubba.whistle.com>
Subject: Re: Single socket version of natd
In-Reply-To: <Pine.BSF.3.91.970204100202.8654C-100000@darkstar> from Charles Mott at "Feb 4, 97 10:17:41 am"
To: cmott@srv.net (Charles Mott)
Date: Wed, 5 Feb 1997 11:00:53 -0800 (PST)
Cc: brian@utell.co.uk, julian@whistle.com, eivind@dimaga.com,
        brian@awfulhak.demon.co.uk, ari.suutari@ps.carel.fi,
        hackers@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL25 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


> > With a "leave the sum alone option", natd could pass the packet
> > with the zero'd ip_sum to PacketAliasIn() and know that it has
> > to calculate it itself afterwards....
> 
> Why does the kernel zero the checksum?

The kernel leaves the checksum zero because:

 (a) When a packet comes in, the way the checksum is verified
     is to checksum the packet as is and replace the checksum.
     If the original checksum was valid, then the new checksum
     will be zero. So the checksum field is already zero before
     the divert code even gets the packet.

 (b) Packets being diverted are often mangled, so the checksum
     has to be recomputed anyway. So having the divert code
     recompute the checksum before sending it up would just
     be useless extra work.

The "right" thing to do would be to modify the kernel so that
checking checksums does not replace the original packet checksum.
This should be easy enough.

-Archie

___________________________________________________________________________
Archie Cobbs   *   Whistle Communications, Inc.  *   http://www.whistle.com

From owner-freebsd-hackers  Wed Feb  5 11:02:46 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA02061
          for hackers-outgoing; Wed, 5 Feb 1997 11:02:46 -0800 (PST)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA02047
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 11:02:38 -0800 (PST)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id LAA24435; Wed, 5 Feb 1997 11:02:07 -0800 (PST)
Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3)
	id sma024431; Wed Feb  5 11:01:57 1997
Received: (from archie@localhost) by bubba.whistle.com (8.7.5/8.6.12) id LAA23740; Wed, 5 Feb 1997 11:01:57 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199702051901.LAA23740@bubba.whistle.com>
Subject: Re: Single socket version of natd
In-Reply-To: <199702050149.BAA29882@awfulhak.demon.co.uk> from Brian Somers at "Feb 5, 97 01:49:00 am"
To: brian@awfulhak.demon.co.uk (Brian Somers)
Date: Wed, 5 Feb 1997 11:01:57 -0800 (PST)
Cc: brian@utell.co.uk, cmott@srv.net, julian@whistle.com, eivind@dimaga.com,
        ari.suutari@ps.carel.fi, hackers@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL25 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


> Does anyone know of a reason (besides the divert(4) man page) that the
> sum on incoming packets is zero'd ?
> The code says:
> 
> [.....]
>         if (hlen == sizeof(struct ip)) {
>                 ip->ip_sum = in_cksum_hdr(ip);
>         } else {
>                 ip->ip_sum = in_cksum(m, hlen);
>         }
>         if (ip->ip_sum) {
>                 ipstat.ips_badsum++;
>                 goto bad;
>         }
> [.....]
> 
> Is there any problems with changing this to
> 
>         u_short sum;
> .....
>         if (hlen == sizeof(struct ip)) {
>                 sum = in_cksum_hdr(ip);
>         } else {
>                 sum = in_cksum(m, hlen);
>         }
>         if (sum) {
>                 ipstat.ips_badsum++;
>                 goto bad;
>         }
> 
> (and updating divert(4)) ?

Please do!

-Archie

___________________________________________________________________________
Archie Cobbs   *   Whistle Communications, Inc.  *   http://www.whistle.com

From owner-freebsd-hackers  Wed Feb  5 11:12:18 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA02863
          for hackers-outgoing; Wed, 5 Feb 1997 11:12:18 -0800 (PST)
Received: from csd.cs.technion.ac.il (csd.cs.technion.ac.il [132.68.32.8])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA02787
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 11:11:57 -0800 (PST)
Received: from localhost (nadav@localhost) by csd.cs.technion.ac.il (8.6.11/8.6.10) with SMTP id VAA28383; Wed, 5 Feb 1997 21:09:05 +0200
X-Authentication-Warning: csd.cs.technion.ac.il: nadav owned process doing -bs
Date: Wed, 5 Feb 1997 21:09:04 +0200 (IST)
From: Nadav Eiron <nadav@cs.technion.ac.il>
X-Sender: nadav@csd
To: garman@phs.k12.ar.us
cc: Wolfgang Helbig <helbig@BA-Stuttgart.De>, hackers@freebsd.org
Subject: Re: CMD640b flaw workaround
In-Reply-To: <Mutt.19970204152524.garman@jason.garman.net>
Message-ID: <Pine.GSO.3.95-heb-2.07.970205210708.28189B-100000@csd>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk



On Tue, 4 Feb 1997, Jason Garman wrote:

> Nadav Eiron writes:
> > I tried installing the patches on my troubled 2.1.5R system, and it
> > doesn't cure my problem. I think I should describe my problem once again,
> > as it's not the classical CMD640 bug. I have a machine with a hard disk
> > (Quantum FireBall) and a CD (Creative x4), both on the primary channel.
> > The problem is that CD access is unreliable. It's most commonly seen when
> > I try to serve a CD directly via apache. Under heavy load, some of the
> > Apace processes will hang while accessing the CD like so:
> > 
> That's weird.  You're right, the patch won't fix this.  I have a CD and hd
> on my first channel, and it works fine here...
> 
> I know this isn't a really good `solution,' but how about switching the cd
> onto the second channel?

Strange enough, it seems to be working! I now have a disk on one channel
and the CD on the other and they seem to be getting along. I'll leave it
like that for a couple of days and then either I'll try adding a disk or
upgrade to 2.1.6 - whichever I feel is more important :-). I guess I can't
expect the CD to get along with another disk on the secondary channel, so
if I get another disk I'll probably try two disks on the primary channel
and the CD alone on the secondary.

Thanks again,

> 
> Enjoy,
> -- 
> Jason Garman                             http://www.nesc.k12.ar.us/~garman/
> Student, Eleanor Roosevelt High School                 garman@phs.k12.ar.us
> 
Nadav


From owner-freebsd-hackers  Wed Feb  5 11:19:33 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA03389
          for hackers-outgoing; Wed, 5 Feb 1997 11:19:33 -0800 (PST)
Received: from relay.nuxi.com (nuxi.ucdavis.edu [128.120.37.176])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA03372;
          Wed, 5 Feb 1997 11:19:23 -0800 (PST)
Received: from dragon.nuxi.com (reqf-022.ucdavis.edu [128.120.253.142]) by relay.nuxi.com (8.8.4/8.6.12) with ESMTP id LAA25441; Wed, 5 Feb 1997 11:19:26 -0800 (PST)
Received: (from obrien@localhost) by dragon.nuxi.com (8.8.4/8.7.3) id LAA07180; Wed, 5 Feb 1997 11:19:14 -0800 (PST)
Message-ID: <19970205111913.YS06559@dragon.nuxi.com>
Date: Wed, 5 Feb 1997 11:19:13 -0800
From: obrien@NUXI.com (David O'Brien)
To: imp@village.org (Warner Losh)
Cc: freebsd-ports@FreeBSD.ORG (FreeBSD ports list), hackers@FreeBSD.ORG
Subject: Re: conditionally including <sys/param.h>
References: <19970205003343.YB13323@dragon.nuxi.com> <19970202135048.PN07710@dragon.nuxi.com> <199701280143.RAA06503@freefall.freebsd.org> <Pine.OSF.3.95q.970127210526.2115E-100000@uplink.eng.umd.edu> <E0vrw2G-0000I7-00@rover.village.org> <E0vs94u-0000u5-00@rover.village.org>
X-Mailer: Mutt 0.59-PL19
Mime-Version: 1.0
Organization: The NUXI *BSD group
X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3  90 76 5D 69 58 D9 98 7A
X-Pgp-Keyid: 34F9F9D5
In-Reply-To: <E0vs94u-0000u5-00@rover.village.org>; from Warner Losh on Feb 5, 1997 08:16:03 -0700
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Warner Losh writes:
> In message <19970205003343.YB13323@dragon.nuxi.com> David O'Brien writes:
> : I'm just trying to find something that will cover all the 4.4BSD derived
> : OS's.  What are the big divergances from each other that __44bsd__
> : wouldn't cover (from an application standpoint)?  Remember I'm trying to
> : catch things like sys_errlist[], termios, /var/mail, /usr/sbin/sendmail,
> : etc
> 
> Better to include sys/param.h, from a portability standpoint, and
> check to see if BSD is defined and larger than a certain value.  The
> hard part is knowing if sys/param.h will be there.

RIGHT.  That is *why* I want __44bsd__, to know it is safe to included
<sys/param.h>.  I'm not saying __44bsd__ has to be a replacement for the
BSD macro.  Although for the easy stuff, why not.

On a side note, the BSD macro isn't that helpful.  I know of few people
that really know if a feature we have has been around since Net/2, or
4.4Lite.  So most people take a wild stab at it.  So would __44bsd__ be
any worse?

> It would be better to find a foolproof way of knowing when sys/param.h
> is available (or at least when it generally isn't).

Right, which is what I am trying to do.
 
> Most of the examples that you sighted can be handled better by other
> means.  Don't declare sys_errlist at all, rather use strerror() or
> #include <errno.h> (which is fairly standard).  Don't use hard wired
> path names, but rather the standard ones defined in pathnames.h.

Remeber what I'm trying to do here, this is for the ports collection.
I'm trying to solve a problem I come across quite often in making a port.
I don't think I can get an author to accept that big of a change to his
code.  With your solution, I would have to worry that some Unix doesn't
have the macro that I want to use from pathnames.h.

If _I_ where writing the application/package, then things would yes be a
little different.

> You'll likely have to have a fallback for that strategy as well.
 
> Also, as time moves forward, some new systems will adopt parts of the
> 4.4 tree.  Do you really want to have things like:
> #if defined(__bsd44__) || (defined(SOLARIS) && SOLARIS >= 207) ...
> in the sources?  They quickly get out of hand.

When other Unixes took parts from BSD in the past, they dont' define our
macro.  System V to my knowledge (which took many things from BSD),
doesn't define BSD.  So there is little to no reason to expect the above
to happen.
 
> Many of the ports have 2-3 lines of ifdefs to include stdlib.h, when
> instead they should have a single #ifdef __STDC__ in its place.

Because, GCC will define __STDC__ because the compiler can handle it.
BUT that doens't mean GCC found stdlib.h when it fixed up the headers.
GCC on SunOS defines __STDC__, but you will find it's native headers
(which GCC uses), aren't.
 
> Had BSD 4.4 come out with this symbol, things would be a little
> different.  However, it didn't think that it would be worth the
> portibility hassles at this point, since it would take time for this
> symbol to propigate to all flavors of BSD.  2.2 is almost out the
> door, OpenBSD 2.0 is on the streets (and will be for a while).  Netbsd
> 1.2 is also on the streets and likely will be for a while too.
> 
> I guess I'm just showing my years of riding heard on the OI/uib source
> tree which was generally portable to the point that the compile time
> (45 minutes to an hour) usually dominated the porting time (well, and
> sometimes it was the licenese manager third party code too).
> 
> Warner

-- 
-- David	(obrien@NUXI.com  -or-  obrien@FreeBSD.org)

From owner-freebsd-hackers  Wed Feb  5 11:26:20 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA03976
          for hackers-outgoing; Wed, 5 Feb 1997 11:26:20 -0800 (PST)
Received: from relay.nuxi.com (nuxi.ucdavis.edu [128.120.37.176])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA03969;
          Wed, 5 Feb 1997 11:26:14 -0800 (PST)
Received: from dragon.nuxi.com (reqf-022.ucdavis.edu [128.120.253.142]) by relay.nuxi.com (8.8.4/8.6.12) with ESMTP id LAA25462; Wed, 5 Feb 1997 11:26:16 -0800 (PST)
Received: (from obrien@localhost) by dragon.nuxi.com (8.8.4/8.7.3) id LAA07202; Wed, 5 Feb 1997 11:26:04 -0800 (PST)
Message-ID: <19970205112604.AI13761@dragon.nuxi.com>
Date: Wed, 5 Feb 1997 11:26:04 -0800
From: obrien@NUXI.com (David O'Brien)
To: chuckr@glue.umd.edu (Chuck Robey)
Cc: freebsd-ports@freebsd.org (FreeBSD ports list), hackers@freebsd.org
Subject: Re: conditionally including <sys/param.h>
References: <19970205003343.YB13323@dragon.nuxi.com> <Pine.OSF.3.95q.970205081326.9802A-100000@gilligan.eng.umd.edu>
X-Mailer: Mutt 0.59-PL19
Mime-Version: 1.0
Organization: The NUXI *BSD group
X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3  90 76 5D 69 58 D9 98 7A
X-Pgp-Keyid: 34F9F9D5
In-Reply-To: <Pine.OSF.3.95q.970205081326.9802A-100000@gilligan.eng.umd.edu>; from Chuck Robey on Feb 5, 1997 08:17:18 -0500
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Chuck Robey writes:
> On Wed, 5 Feb 1997, David O'Brien wrote:
> 
> David, I don't understand why you don't want to use __FreeBSD__,
> __NetBSD__, and __OpenBSD__ for non-kernel stuff.  

> The __44bsd__ thing doesn't exist, and if you start it, 75% of FreeBSD
> folks and ALL of everyone else in NetBSD and OpenBSD will be out in the
> cold.

True.  But I would only go down this route with the assurance from the
other camps that they would do the same.  When I started this I was with
them all at USENIX and I had easy access to convence them this is a Good
Thing.  Since both NetBSD and OpenBSD pretty much use our ports (and I
think they like not having to throw resources on them), it would be in
their best interests for the return they get.

> I probably misunderstand part, but what functionality will be gained from
> adding __44bsd__?  I want to note that the approach I'm pushing works now
> for Xfree86 just fine.

(note for others, Chuck's approach is use __FreeBSD__, __NetBSD__, and
__OpenBSD__)  Your approach is fine.  I'm just trying to follow the
guidence of the handbook.  I'm thinking of ripping out the verbage on not
using these macros.  They seem to be the only true way of dealing with
this.  If anyone knows who wrote those words, I'd love to start a dialog
with them.
 
-- 
-- David	(obrien@NUXI.com  -or-  obrien@FreeBSD.org)

From owner-freebsd-hackers  Wed Feb  5 11:27:30 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA04082
          for hackers-outgoing; Wed, 5 Feb 1997 11:27:30 -0800 (PST)
Received: from dawn.ww.net (root@dawn.ww.net [193.124.73.50])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA04070
          for <freebsd-hackers@freebsd.org>; Wed, 5 Feb 1997 11:27:16 -0800 (PST)
Received: (from alexis@localhost)
	by dawn.ww.net (8.7.5/alexis 2.5)  id WAA02074
	for freebsd-hackers@freebsd.org; Wed, 5 Feb 1997 22:26:32 +0300 (MSK)
Message-Id: <199702051926.WAA02074@dawn.ww.net>
Subject: sio11 64 events for device without tp related problem?
To: freebsd-hackers@freebsd.org
Date: Wed, 5 Feb 1997 22:26:31 +0300 (MSK)
From: Alexis Yushin <alexis@dawn.ww.net>
Reply-To: alexis@ww.net (Alexis Yushin)
X-Office-Phone: +380 65 2 26.1410
X-Home-Phone: +380 65 2 27.0747
X-NIC-Handle: AY23
X-RIPE-Handle: AY6-RIPE
X-Mailer: ELM [version 2.4ME+ PL17 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Evening,

	It started with syslogd writes out initial kernel messages
(those, generated before the first process starts) and stumbles into
siobi state. Sometimes it does not. (I mean after some reboots)
Sometimes other process end up like that. slattach and more often
/usr/bin/su. Sometimes not. But always right after kernel boots
two messages 'sio11 64 events for device without tp' is generated.
(I can get them with dmesg) Someone told me it is something well
known and obvious. Of course I am investigating, but if it is
please let me know. Thanks in advance,
							alexis
-- 
		It's all the same, only the names will change

From owner-freebsd-hackers  Wed Feb  5 11:47:50 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA06700
          for hackers-outgoing; Wed, 5 Feb 1997 11:47:50 -0800 (PST)
Received: from nic.follonett.no (nic.follonett.no [194.198.43.10])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA06691
          for <hackers@FreeBSD.ORG>; Wed, 5 Feb 1997 11:47:40 -0800 (PST)
Received: (from uucp@localhost) by nic.follonett.no (8.8.5/8.8.3) with UUCP id UAA03411; Wed, 5 Feb 1997 20:44:33 +0100 (MET)
Received: from oo7 (oo7.dimaga.com [192.0.0.65]) by dimaga.com (8.7.5/8.7.2) with SMTP id UAA20084; Wed, 5 Feb 1997 20:43:45 +0100 (MET)
Message-Id: <3.0.32.19970205204345.009f05a0@dimaga.com>
X-Sender: eivind@dimaga.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Wed, 05 Feb 1997 20:43:46 +0100
To: Chris Csanady <ccsanady@nyx.pr.mcs.net>
From: Eivind Eklund <eivind@dimaga.com>
Subject: Re: pppd 
Cc: Brian Somers <brian@awfulhak.demon.co.uk>, hackers@FreeBSD.ORG
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

At 09:30 PM 2/4/97 -0600, Chris Csanady wrote:
>Speaking of this..  I am using ppp(userland), and need time my connections.
>The problem is that there is a ppp.linkup that can be executed, but no
>ppp.linkdown or such.  Any ideas?  I need some of the features in the
>userland version..

/var/log/ppp.log already contains up and down events for me, at least.
And I haven't modified that part of PPP, as far as I can remember.
(If I have, my appologies to those that will be running ppp+pktAlias1.9 - I
can only remember adding extra security patches apart from the things
mentioned in the README file.)



Eivind Eklund / perhaps@yes.no / http://maybe.yes.no/perhaps/

From owner-freebsd-hackers  Wed Feb  5 11:51:41 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA06961
          for hackers-outgoing; Wed, 5 Feb 1997 11:51:41 -0800 (PST)
Received: from sax.sax.de (sax.sax.de [193.175.26.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA06953
          for <FreeBSD-hackers@freebsd.org>; Wed, 5 Feb 1997 11:51:33 -0800 (PST)
Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA15545; Wed, 5 Feb 1997 20:51:05 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id UAA11573; Wed, 5 Feb 1997 20:48:15 +0100 (MET)
Message-ID: <Mutt.19970205204815.j@uriah.heep.sax.de>
Date: Wed, 5 Feb 1997 20:48:15 +0100
From: j@uriah.heep.sax.de (J Wunsch)
To: ts@polynet.lviv.ua
Cc: stevel@logues.rhn.orst.edu, FreeBSD-hackers@freebsd.org
Subject: Re: UPS daemon
References: <199702051719.TAA18357@NetSurfer.lp.lviv.ua>
X-Mailer: Mutt 0.55-PL10
Mime-Version: 1.0
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <199702051719.TAA18357@NetSurfer.lp.lviv.ua>; from Slavik Terletsky on Feb 5, 1997 19:21:54 +0000
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

As Slavik Terletsky wrote:

> I managed to hack upsd. As most of ppl who has APC Smart UPS I use
> it in a dumb mode (I had no info on the cabling UPS to my box).

Ummm.  You've reinvented the wheel.  There's already a nice upsd
available, and it does indeed use the Smart UPS in smart mode (which
is *way* preferable over dumb mode, since those beasts are really
verbose in their reporting).

See ftp.ww.net.

Also, sorry to beat at you, but your program has many style violations
(not so terrible) and even some more serious problems.

> char *scr = "/etc/rc.shutdown";

Don't use this.  Expect /etc/rc.shutdown to become a standard
component of FreeBSD anytime soon, to be called by init before
shutting down the system.

>  /* check if script exists */
>  if(!(fd = fopen(scr, "r"))) {
>  fprintf(stderr, "fopen: %s: %s\n", scr, sys_errlist[errno]);
>  exit(1);
>  }
>  fclose(fd);

`fd' translates to `file descriptor' for many people, which is
something very different from an stdio file handle (of type `FILE *').

Use access(2) or stat(2) to see if a file exists, abusing stdio is
overkill.

Better use the err(3) function family instead of hacking your own.
Code using sys_errlist[] all over the place is probably stylistically
bad.  (If at all, use a centralized error handling function for better
portability.)


>  /* become a daemon */
>  switch(fork()) {
>  case -1:	/* error */
>  fprintf(stderr, "fork: %s\n", sys_errlist[errno]);
>  exit(1);
>  case  0:	/* child */
>  break;
>  default:	/* parent */
>  exit(0);
>  }

Hmm, but you don't actually become a daemon.  This would require
calling setsid(2).

>  /* monitor device */
>  while(1) {
...
>  sleep(1);
>  }

Uh-oh.  This is indeed a system hog.  You examine the line status
once every second, thus preventing that daemon from being swapped.

A much better way is to have it making the line its controlling tty,
and arrange for the external logic dropping DCD to get the attention
of the process (i.e., when power fails).  This way, the daemon can
sleep all the time (and can be swapped), but will be signalled with a
SIGHUP to wakeup.

>  /* save our filesystem */
>  system("/bin/sync");
>  system("/bin/sync");
>  system("/bin/sync");

Hmpf. :-)  Did you ever look into /bin/sync?  All it does is calling
sync(2).  Anyway, there's no need to call it at all.  Leave this to
init.  ``Thou shalt sync thrice.'' is a very old myth, but it's pure
religion, nothing else. ;-)

>  /* wait and then run script */
>  sleep(wait);
>  system(scr);

Also, send the appropriate signal to init instead.


Again, sorry for hacking on your code, please take my ramblings as
constructive criticism, not as offense.

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

From owner-freebsd-hackers  Wed Feb  5 11:56:39 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA07260
          for hackers-outgoing; Wed, 5 Feb 1997 11:56:39 -0800 (PST)
Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA07253
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 11:56:32 -0800 (PST)
Received: from localhost (mark@localhost) by vinyl.quickweb.com (8.7.5/8.6.12) with SMTP id OAA28055 for <hackers@freebsd.org>; Wed, 5 Feb 1997 14:56:57 -0500 (EST)
Date: Wed, 5 Feb 1997 14:56:56 -0500 (EST)
From: Mark Mayo <mark@quickweb.com>
To: hackers@freebsd.org
Subject: Samba survey
Message-ID: <Pine.BSF.3.94.970205145305.28031A-100000@vinyl.quickweb.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi all - I just checked out the Samba survey page (URL below) and noticed
that there are only 28 sites running samba according to the stats! This
seems *really* low to me, so I was wondering if people have filled out the
survey...

It always helps to have a strong showing with 'products' like Samba, which
are perceived as server goods. I'm sure there must be more FreeBSD Samba
servers out there!! I also really hate to see Linux as the No. 1 SMB
server OS.... ugh.

http://lake.canberra.edu.au/pub/samba/survey/

-Mark

----------------------------------------------------------------------------
 Mark Mayo		  				mark@quickweb.com       
 RingZero Comp.  	  		   http://vinyl.quickweb.com/mark 
----------------------------------------------------------------------------
	"I prefer tongue-tied knowledge to ignorant loquacity."
						Cicero (106-43 B.C.)


From owner-freebsd-hackers  Wed Feb  5 12:39:08 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA09892
          for hackers-outgoing; Wed, 5 Feb 1997 12:39:08 -0800 (PST)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA09859;
          Wed, 5 Feb 1997 12:38:53 -0800 (PST)
Received: from rover.village.org [127.0.0.1] 
	by rover.village.org with esmtp (Exim 0.56 #1)
	id E0vsE7A-0001fr-00; Wed, 5 Feb 1997 13:38:44 -0700
To: obrien@NUXI.com (David O'Brien)
Subject: Re: conditionally including <sys/param.h> 
Cc: freebsd-ports@freebsd.org (FreeBSD ports list), hackers@freebsd.org
In-reply-to: Your message of "Wed, 05 Feb 1997 11:19:13 PST."
		<19970205111913.YS06559@dragon.nuxi.com> 
References: <19970205111913.YS06559@dragon.nuxi.com>  <19970205003343.YB13323@dragon.nuxi.com> <19970202135048.PN07710@dragon.nuxi.com> <199701280143.RAA06503@freefall.freebsd.org> <Pine.OSF.3.95q.970127210526.2115E-100000@uplink.eng.umd.edu> <E0vrw2G-0000I7-00@rover.village.org> <E0vs94u-0000u5-00@rover.village.org> 
Date: Wed, 05 Feb 1997 13:38:43 -0700
From: Warner Losh <imp@village.org>
Message-Id: <E0vsE7A-0001fr-00@rover.village.org>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <19970205111913.YS06559@dragon.nuxi.com> David O'Brien writes:
: RIGHT.  That is *why* I want __44bsd__, to know it is safe to included
: <sys/param.h>.  I'm not saying __44bsd__ has to be a replacement for the
: BSD macro.  Although for the easy stuff, why not.

Maybe we should be defining the _BSD* macros that posix mandates :-).
Or rather suggests.

: On a side note, the BSD macro isn't that helpful.  I know of few people
: that really know if a feature we have has been around since Net/2, or
: 4.4Lite.  So most people take a wild stab at it.  So would __44bsd__ be
: any worse?

But this is a knowable thing.  __44bsd__ would likely be abused for
things it has no business controlling.

: > It would be better to find a foolproof way of knowing when sys/param.h
: > is available (or at least when it generally isn't).
: 
: Right, which is what I am trying to do.

But your way is too exclusive.  It cuts out too many systems that have
sys/param.h that could be used to know things.

: Remeber what I'm trying to do here, this is for the ports collection.
: I'm trying to solve a problem I come across quite often in making a port.
: I don't think I can get an author to accept that big of a change to his
: code.  With your solution, I would have to worry that some Unix doesn't
: have the macro that I want to use from pathnames.h.

Yes.  I understand that.  It is easy enough to #include pathnames.h,
and then do #ifndef's.  You'll likely have to carry along a seprate
pathnames.h for the application that would be tailored to each OS that
doesn't define these for you.  That's a little larger change to the
ports, but still a fairly minor one since it buys extra portibility.

: When other Unixes took parts from BSD in the past, they dont' define our
: macro.  System V to my knowledge (which took many things from BSD),
: doesn't define BSD.  So there is little to no reason to expect the above
: to happen.

I believe that SYSVr4 does define the BSD macro.  Solaris certainly
does since Solaris 2.0 ( well, SunOS has at least since 4.0, and I
think since 3.x).

: > Many of the ports have 2-3 lines of ifdefs to include stdlib.h, when
: > instead they should have a single #ifdef __STDC__ in its place.
: 
: Because, GCC will define __STDC__ because the compiler can handle it.
: BUT that doens't mean GCC found stdlib.h when it fixed up the headers.
: GCC on SunOS defines __STDC__, but you will find it's native headers
: (which GCC uses), aren't.

But those headers *ARE* there when __STDC__ is defined.  At least on
the last SunOS system that I checked gcc adds them.  This was in
2.5.8 of gcc, so this has been happening for a long time.  That's what
__STDC__ means: that I implement the ANSI standard.  There are some
compilers that do define it to be non-standard values, but they are
mostly ancient versions of compilers for the PC, Amiga or Mac.

However, as Bruce pointed out, there are other reasons for not doing
this.  I think that they aren't necessarily valid in the context we're
talking about (since we don't compile the ports -traditional), but it
may make a difference on some platforms.

Just so that we're on the same page,  are you suggesting that we do

#ifdef _BSD44
#include <sys/param.h>
#endif

instead?

Warner

From owner-freebsd-hackers  Wed Feb  5 12:44:40 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA10474
          for hackers-outgoing; Wed, 5 Feb 1997 12:44:40 -0800 (PST)
Received: from werple.net.au (melb.werple.net.au [203.9.190.18])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA10429
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 12:44:10 -0800 (PST)
Received: (qmail 11912 invoked by uid 5); 5 Feb 1997 20:44:04 -0000
MBOX-Line: From jb@freebsd1.cimlogic.com.au  Thu Feb  6 07:33:01 1997
Received: (from jb@localhost) by freebsd1.cimlogic.com.au (8.7.5/8.7.3) id HAA02946; Thu, 6 Feb 1997 07:33:01 +1100 (EST)
From: John Birrell <jb@cimlogic.com.au>
Message-Id: <199702052033.HAA02946@freebsd1.cimlogic.com.au>
Subject: Re: sigwait and threads?
To: ljo@Mcs.Net (Lars Jonas Olsson)
Date: Thu, 6 Feb 1997 07:33:00 +1100 (EST)
Cc: hackers@freebsd.org
In-Reply-To: <199702051620.KAA25043@Mars.mcs.net> from Lars Jonas Olsson at "Feb 5, 97 10:20:35 am"
X-Mailer: ELM [version 2.4ME+ PL22 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Lars Jonas Olsson wrote:
>  The "Threads primer" book by Lewis and Berg recommends using sigwait
> for signal handling in multi-threaded applications. FreeBSD doesn't
> have a sigwait though. Should we get one? Or is another method for
> signal handling recommended?

According to 1003.1c, there should be a sigwait function in libc_r.

POSIX 1003.1c has a poor (IMHO) signal model. It is a committee design
used to justify entrenched positions. The rationale in P1003.1c/D10 says:

"Compromise reached:

 The signal model of this standard contains:

     (1)  per-thread signal masks,
     (2)  per-process signal vectors,
     (3)  single delivery of each signal

 The compromise satisfies as many of the sometimes conflicting goals as the
 working group felt possible..."

It is (2) that I don't like. libc_r currently does not comply with that.
It does per-thread signal vectors. This will change when I can figure out
a way to allow the current behavio[u]r as an extension.

> 
>  I've got a multi-threaded application that currently runs on SCO
> UnixWare 2.1 that I also want to be able to run on FreeBSD. This
> application uses sigwait and no signal handlers.

Yuk. Oh well, I'll add a sigwait to the bunch of updates I'm working on.

> 
> Jonas
> 

Regards,

-- 
John Birrell                                CIMlogic Pty Ltd
jb@cimlogic.com.au; jb@netbsd.org           119 Cecil Street
Ph  +61  3 9690 6900                        South Melbourne Vic 3205
Fax +61  3 9690 6650                        Australia
Mob +61 18  353  137

From owner-freebsd-hackers  Wed Feb  5 12:44:42 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA10475
          for hackers-outgoing; Wed, 5 Feb 1997 12:44:42 -0800 (PST)
Received: from werple.net.au (melb.werple.net.au [203.9.190.18])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA10431
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 12:44:10 -0800 (PST)
Received: (qmail 11917 invoked by uid 5); 5 Feb 1997 20:44:05 -0000
MBOX-Line: From jb@freebsd1.cimlogic.com.au  Thu Feb  6 07:37:02 1997
Received: (from jb@localhost) by freebsd1.cimlogic.com.au (8.7.5/8.7.3) id HAA02960; Thu, 6 Feb 1997 07:37:02 +1100 (EST)
From: John Birrell <jb@cimlogic.com.au>
Message-Id: <199702052037.HAA02960@freebsd1.cimlogic.com.au>
Subject: Re: sigwait and threads?
To: lada@ws2301.gud.siemens.co.at (Hr.Ladavac)
Date: Thu, 6 Feb 1997 07:37:01 +1100 (EST)
Cc: ljo@Mcs.Net, hackers@freebsd.org
In-Reply-To: <199702051749.AA254324944@ws2301.gud.siemens.co.at> from "Hr.Ladavac" at "Feb 5, 97 06:49:04 pm"
X-Mailer: ELM [version 2.4ME+ PL22 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hr.Ladavac wrote:
> sigwait() is a DCE-ism, or better yet, pthread Draft 4-ism.  At that
> stage they had no support for per thread sigaction() nor signal()--as a
> matter of fact, one was not allowed to use them.
> 
> Pthread Draft 7 introduced per-thread sigaction and signal semantics, and
> I believe the Draft 10 and Standard have thrown the whole sigwait mess out.

sigwait *is* in draft 10.

> 
> AFAIK, the libc_r implements pthread Standard; you should be able to 
> use sigaction instead.  It might be possible to write a wrapper around
> it to implement sigwait for the DCE compatibility.  Andy(?) Birrell may
> have further comments.
> 
> Another difference that DCE requires and Draft 8 has thrown out is 
> pthread_detach().

pthread_detach is in draft 10, too.

> 
> /Marino

Regards,

-- 
John Birrell                                CIMlogic Pty Ltd
jb@cimlogic.com.au; jb@netbsd.org           119 Cecil Street
Ph  +61  3 9690 6900                        South Melbourne Vic 3205
Fax +61  3 9690 6650                        Australia
Mob +61 18  353  137

From owner-freebsd-hackers  Wed Feb  5 13:03:08 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA11721
          for hackers-outgoing; Wed, 5 Feb 1997 13:03:08 -0800 (PST)
Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA11707
          for <hackers@FreeBSD.ORG>; Wed, 5 Feb 1997 13:03:01 -0800 (PST)
Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.7.3) with ESMTP id MAA19654; Wed, 5 Feb 1997 12:59:22 -0800 (PST)
Message-Id: <199702052059.MAA19654@rah.star-gate.com>
X-Mailer: exmh version 1.6.9 8/22/96
To: Mark Mayo <mark@quickweb.com>
cc: hackers@FreeBSD.ORG
Subject: Re: Samba survey 
In-reply-to: Your message of "Wed, 05 Feb 1997 14:56:56 EST."
             <Pine.BSF.3.94.970205145305.28031A-100000@vinyl.quickweb.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 05 Feb 1997 12:59:21 -0800
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Is there a configuration tool which aids a new user like me to setup 
samba?

	Tnks,
	Amancio

>From The Desk Of Mark Mayo :
> Hi all - I just checked out the Samba survey page (URL below) and noticed
> that there are only 28 sites running samba according to the stats! This
> seems *really* low to me, so I was wondering if people have filled out the
> survey...
> 
> It always helps to have a strong showing with 'products' like Samba, which
> are perceived as server goods. I'm sure there must be more FreeBSD Samba
> servers out there!! I also really hate to see Linux as the No. 1 SMB
> server OS.... ugh.
> 
> http://lake.canberra.edu.au/pub/samba/survey/
> 
> -Mark
> 
> ----------------------------------------------------------------------------
>  Mark Mayo		  				mark@quickweb.com      
 
>  RingZero Comp.  	  		   http://vinyl.quickweb.com/mark 
> ----------------------------------------------------------------------------
> 	"I prefer tongue-tied knowledge to ignorant loquacity."
> 						Cicero (106-43 B.C.)
> 
> 



From owner-freebsd-hackers  Wed Feb  5 13:04:16 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA11791
          for hackers-outgoing; Wed, 5 Feb 1997 13:04:16 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA11784
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 13:04:06 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA15505; Wed, 5 Feb 1997 13:59:51 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702052059.NAA15505@phaeton.artisoft.com>
Subject: Re: g++, STL and -frepo on FreeBSD-2.2-Beta
To: jmacd@CS.Berkeley.EDU (Josh MacDonald)
Date: Wed, 5 Feb 1997 13:59:51 -0700 (MST)
Cc: hackers@freebsd.org, terry@lamber.org, terry@lambert.org
In-Reply-To: <199702050355.TAA11238@paris.CS.Berkeley.EDU> from "Josh MacDonald" at Feb 4, 97 07:55:18 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


[ ... g++ implementation level issues ... ]

I replied to this one off the list...


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Wed Feb  5 13:11:46 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA12191
          for hackers-outgoing; Wed, 5 Feb 1997 13:11:46 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA12174;
          Wed, 5 Feb 1997 13:11:31 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA15536; Wed, 5 Feb 1997 14:05:42 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702052105.OAA15536@phaeton.artisoft.com>
Subject: Re: conditionally including <sys/param.h>
To: obrien@NUXI.com (David O'Brien)
Date: Wed, 5 Feb 1997 14:05:42 -0700 (MST)
Cc: imp@village.org, freebsd-ports@FreeBSD.ORG, hackers@FreeBSD.ORG
In-Reply-To: <19970205003343.YB13323@dragon.nuxi.com> from "David O'Brien" at Feb 5, 97 00:33:43 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > : to get a new cpp symbol added (like __44bsd__ or something).
> > 
> > This is a bad idea, since it has lost a lot of its potential meaning
> > with so many 44bsd derived systems that pick and chose between 4.4 and
> > 4.4 Lite 2.
> 
> Then what would you suggest?  Are they really more different than all the
> various sysVr4 that define __svr4__?  How close is Solaris, UnixWare, and
> Irix?

When DMR sent his "jeremiad" to the ANSI C committee, I sent in my
own in support of a couple of his points.  I also suggested "#ifclude"
or something similar be used to conditionally include a header file
if it existed.  Unfortunately, I guess it just didn't make the cut,
or was lost in the glare from other commentary...  8-(.

#ifclude <sys/param.h>


					Regards,
					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Wed Feb  5 13:15:44 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA12421
          for hackers-outgoing; Wed, 5 Feb 1997 13:15:44 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA12413
          for <freebsd-hackers@freebsd.org>; Wed, 5 Feb 1997 13:15:35 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA15553; Wed, 5 Feb 1997 14:12:46 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702052112.OAA15553@phaeton.artisoft.com>
Subject: Re: NIS/uids
To: W.Belgers@nl.cis.philips.com (Walter Belgers)
Date: Wed, 5 Feb 1997 14:12:46 -0700 (MST)
Cc: freebsd-hackers@freebsd.org
In-Reply-To: <no.id> from "Walter Belgers" at Feb 5, 97 11:00:12 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > > > The problem now is that the security on my system has become dependant
> > > > on that of the NIS server. If I am root on the NIS server I can change
> > > > the uid of "user" into any user including root and make use of it on my
> > > > system.
> >
> > It makes sense to me that "sensitive" user and group ID's perhaps
> > should not be honored when they come in via NFS... ie: user root
> > or bin, etc., or group bin or kmem.
> 
> This has turned out to become a discussion about whether or not you
> should trust your NIS server, but that's not what I wanted to know.
> Let's assume I do not trust the uid's coming from the NIS server but I
> still do want to use NIS (for passwd/homedir/gecos/whatever).

Then you have the same problem, this time with associating a
particular password with a particular name.  All you have done is
trade the association with uid for an association with name.  There
is nothing the prevents me, as an NIS server, from returning the
password "frobozz" (encrypted, of course) for every user, regardless
of their real password.

Now you have the same security hole: you locally enforce the name/id
mapping, but I can log in as any name on your machine (and therefore,
and user id) using the password "frobozz".


> Why does FreeBSD give me troubles when I override the uid in the local
> password file?

It wasn't a case which was considered to ever be anything someone would
want to do, I believe.  Mostly because if I compromise the NIS server,
then I can force you to accept any password for any user/password pair,
and thereby become any user/id pair, so it doesn't give you the protection
you are trying to get it to give you.

PS: Do not start a line with a naked "From".  I think that's what screwed
up the other guy's mail filter for his Pine.


					Regards,
					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Wed Feb  5 13:20:29 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA12733
          for hackers-outgoing; Wed, 5 Feb 1997 13:20:29 -0800 (PST)
Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA12704;
          Wed, 5 Feb 1997 13:20:12 -0800 (PST)
Received: from x14.mi.uni-koeln.de (annexr2-37.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA11639
  (5.67b/IDA-1.5); Wed, 5 Feb 1997 22:19:38 +0100
Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id VAA06016; Wed, 5 Feb 1997 21:52:45 +0100 (CET)
Message-Id: <19970205215125.EX35606@x14.mi.uni-koeln.de>
Date: Wed, 5 Feb 1997 21:51:25 +0100
From: se@freebsd.org (Stefan Esser)
To: Andrew.Gordon@net-tel.co.uk
Cc: se@freebsd.org, hackers@freebsd.org
Subject: Re: PCI LKM: How to find object file from PCI ID ...
References: <19970131213621.EQ13588@x14.mi.uni-koeln.de> <"271-970131231413-CE37*/G=Andrew/S=Gordon/O=NET-TEL Computer Systems Ltd/PRMD=NET-TEL/ADMD=Gold 400/C=GB/"@MHS>
X-Mailer: Mutt 0.60-PL0
Mime-Version: 1.0
In-Reply-To: <"271-970131231413-CE37*/G=Andrew/S=Gordon/O=NET-TEL Computer Systems Ltd/PRMD=NET-TEL/ADMD=Gold 400/C=GB/"@MHS>; from Andrew.Gordon@net-tel.co.uk on Jan 31, 1997 23:14:22 +0000
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Jan 31, Andrew.Gordon@net-tel.co.uk wrote:
> Note that CardBus is essentially PCI squeezed into a PCMCIA card shape,
> so this stuff will also affect pccardd in due course.
> 
> As people have been posting in the past few days about re-writing pccardd
> and its config file format, perhaps this aspect needs considering
> sooner rather than later?

My amount of spare time is (still) rather limited, but
I actually do agree, that all bus types that can be 
probed by directly asking a device for its ID (as is
true for at least EISA, PCI and USB, but AFAIK also
for PCMCIA in all its incarnations) should be dealt 
with by the same generic probe/attach loop.

Bus types that support hot-pluggable devices will need
special support, but that should not hurt for the other
buses ...

My current concept for a revised PCI bus driver has a
loop over all possible device "positions" (with some 
short-cuts to reduce the name space :) and builds a
linear list of devices found.

After this list has been built, it can be handed over
to the user_config code, and after leaving that, the
attach will just try to initialize the driver that has
already been identified to apply to the device in the
probe() loop.

At any later time (either because of an external event,
or periodically polled) the bus can be re-scanned for
new or removed devices. (This is not required for the
PCI bus, which does not even try to support insertion
or removeal of cards in operation).

After new devices have been found with no driver attached,
some user-land program should be notified, which will then
obtain a list of devices with no driver, and will try to
load an LKM for each one that might need it.

An automatic driver shutdown on device removal is much
harder to implement than the driver loading, but it is
not too har dto support from the point of view of a 
generic bus driver. The hard part is left for the device
driver's shutdown() procedure ...


Regards, STefan

From owner-freebsd-hackers  Wed Feb  5 13:21:39 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA12786
          for hackers-outgoing; Wed, 5 Feb 1997 13:21:39 -0800 (PST)
Received: from bmcgover-pc.cisco.com (bmcgover-pc.cisco.com [171.69.104.147])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA12776
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 13:21:33 -0800 (PST)
Received: from bmcgover-pc.cisco.com (bmcgover@localhost.cisco.com [127.0.0.1]) by bmcgover-pc.cisco.com (8.8.2/8.8.2) with ESMTP id QAA00687; Wed, 5 Feb 1997 16:18:53 -0500 (EST)
Message-Id: <199702052118.QAA00687@bmcgover-pc.cisco.com>
To: dg@root.com, support@cyclades.com
cc: hackers@freebsd.org
Subject: Cyclades Parity error (useful info)
Date: Wed, 05 Feb 1997 16:18:53 -0500
From: Brian McGovern <bmcgover@cisco.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I've installed a handful of printf's to see where the parity error is
being caught. In 2.2-GAMMA, it appears to be in /usr/src/sys/pci/cy_pci.c,
in cy_attach, where it states:

/*
 * Enable the "local" interrupt input to generate a
 * PCI interrupt.
 */

outw(ioport + CY_PLX_ICS, inw(CY_PLX_ICS) | 
	CY_PLX_ICS_IENABLE | CY_PLX_ICS_LOCAL_IENABLE);

Unfortunately, I don't have the docs (and haven't dove in to the code far
enough) to see what this is supposed to do, or what its doing wrong. Perhaps,
IMHO, what its trying to do is generate an interrupt, but what its really
doing is either a.) causing a parity interrupt (wouldn't understand why, tho),
or the interrupt its generating looks to the machine like a parity interrupt.


Let me know if this is helpful, or you'd like me to try something else.
	-Brian

From owner-freebsd-hackers  Wed Feb  5 13:29:38 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA13127
          for hackers-outgoing; Wed, 5 Feb 1997 13:29:38 -0800 (PST)
Received: from bmcgover-pc.cisco.com (bmcgover-pc.cisco.com [171.69.104.147])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA13120;
          Wed, 5 Feb 1997 13:29:29 -0800 (PST)
Received: from bmcgover-pc.cisco.com (bmcgover@localhost.cisco.com [127.0.0.1]) by bmcgover-pc.cisco.com (8.8.2/8.8.2) with ESMTP id QAA00718; Wed, 5 Feb 1997 16:26:58 -0500 (EST)
Message-Id: <199702052126.QAA00718@bmcgover-pc.cisco.com>
To: dg@root.com, support@freebsd.org
cc: hackers@freebsd.org
Subject: Stomp the bug!!!! (Was cyclades bug)
Date: Wed, 05 Feb 1997 16:26:57 -0500
From: Brian McGovern <bmcgover@cisco.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Boy, I hate when things are obvious.

The line:

outw(ioport + CY_PLX_ICS, inw(CY_PLX_ICS) | 
	CY_PLX_ICS_IENABLE | CY_PLX_ICS_LOCAL_IENABLE);

is wrong. The inw doesn't have the ioport offset, and should read:

outw(ioport + CY_PLX_ICS, inw(ioport + CY_PLX_ICS) | 
	CY_PLX_ICS_IENABLE | CY_PLX_ICS_LOCAL_IENABLE);


Otherwise, the inw doesn't read from the same register as you outw to. If
someome would like me to diff this up, let me know. Otherwise, I'll assume
the change will get committed?

Gee, I feel good. My first bug fix.

	-Brian


From owner-freebsd-hackers  Wed Feb  5 13:46:09 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA14349
          for hackers-outgoing; Wed, 5 Feb 1997 13:46:09 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA14331
          for <hackers@FreeBSD.ORG>; Wed, 5 Feb 1997 13:45:55 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA15633; Wed, 5 Feb 1997 14:41:57 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702052141.OAA15633@phaeton.artisoft.com>
Subject: Re: sigwait and threads?
To: lada@ws2301.gud.siemens.co.at (Hr.Ladavac)
Date: Wed, 5 Feb 1997 14:41:56 -0700 (MST)
Cc: ljo@Mcs.Net, hackers@FreeBSD.ORG
In-Reply-To: <199702051749.AA254324944@ws2301.gud.siemens.co.at> from "Hr.Ladavac" at Feb 5, 97 06:49:04 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> Another difference that DCE requires and Draft 8 has thrown out is 
> pthread_detach().

Ouch.  This sucks bad.


I have four threading models available, each with a different level
of concurrency.  I'll use the Microsoft names for them, and draw a
better picture than Microsoft has ever drawn for them.  Microsoft
can pay me to use my picture, if they want it.  8-).

Key:

[1]   Caller 1

(a)   Context a

,----.
|A   | Thread A
`----'


         Call Flow                  Concurrency model
-----------------------------    -----------------------------

1.	Single threaded
	o	One object for all caller instances
	o	Object is not multithreaded
	o	Object is not thread reentrant
	o	Threads are not context reentrant
	o	Calls are serialized, not concurrent
          ____________
[1] \    |            |              [1]-->
     v   |   ,----.   |
[2]->O-->|---|A(a)|-->|-->                 [2]-->
     ^   |   `----'   |
[3] /    |____________|                          [3]-->


2.	Apartment threaded
	o	One object for all caller instances
	o	One thread per caller instance
	o	Object is multithreaded
	o	Object is not thread reentrant
	o	Threads are not context reentrant
	o	Calls are serialized, but appear concurrent
          ____________
         |            |
         |   ,----.   |
[1]->O-->|---|A(a)|-->|-->           [1]-->
         |   `----'   |
         |   ,----.   |
[2]->O-->|---|B(b)|-->|-->           [2]-->
         |   `----'   |
         |   ,----.   |
[3]->O-->|---|C(c)|-->|-->           [3]-->
         |   `----'   |
         |____________|

3.	Rental Threaded
	o	One object for all caller instances
	o	Threads are not instanced per caller instance
	o	Object is multithreaded
	o	Object is thread reentrant
	o	Threads are not context reentrant
	o	Calls are thread concurrent; for N callers of M
		threads, where N > M, serialization is N div M
          ____________
         |            |
         |   ,----.   |
[1]->O-->|---|A(a)|-->|-->           [1]-->
         |   `----'   |
         |   ,----.   |
[2]->O-->|---|B(b)|-->|-->           [2]-->
         |   `----'   |
         |   ,----.   |
[3]->O-->|---|A(c)|-->|-->                 [3]-->
         |   `----'   |
         |____________|

4.	Free Threaded
	o	One object for all caller instances
	o	Threads are not instanced per caller instance
	o	Object is multithreaded
	o	Object is thread reentrant
	o	Threads are context reentrant
	o	Calls are context concurrent to the ability of a
		thread to process multiple blocking operations
		by making the call and reentring on another context
          ____________
         |            |
         |   ,----.   |
[1]->O-->|---|A(a)|-->|-->           [1]-->
         |   `----'   |
         |   ,----.   |
[2]->O-->|---|B(b)|-->|-->           [2]-->
         |   `----'   |
         |   ,----.   |
[3]->O-->|---|A(c)|-->|-->           [3]-->
         |   `----'   |
         |____________|

Without thread attach/detach notification, I can't implement my
callable objects as being Rental or Free threaded.


					Regards,
					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Wed Feb  5 14:00:45 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA15350
          for hackers-outgoing; Wed, 5 Feb 1997 14:00:45 -0800 (PST)
Received: from root.com (implode.root.com [198.145.90.17])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA15345;
          Wed, 5 Feb 1997 14:00:42 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id OAA11374; Wed, 5 Feb 1997 14:00:50 -0800 (PST)
Message-Id: <199702052200.OAA11374@root.com>
X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol
To: Brian McGovern <bmcgover@cisco.com>
cc: support@freebsd.org, hackers@freebsd.org
Subject: Re: Stomp the bug!!!! (Was cyclades bug) 
In-reply-to: Your message of "Wed, 05 Feb 1997 16:26:57 EST."
             <199702052126.QAA00718@bmcgover-pc.cisco.com> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Wed, 05 Feb 1997 14:00:50 -0800
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>Boy, I hate when things are obvious.
>
>The line:
>
>outw(ioport + CY_PLX_ICS, inw(CY_PLX_ICS) | 
>	CY_PLX_ICS_IENABLE | CY_PLX_ICS_LOCAL_IENABLE);
>
>is wrong. The inw doesn't have the ioport offset, and should read:
>
>outw(ioport + CY_PLX_ICS, inw(ioport + CY_PLX_ICS) | 
>	CY_PLX_ICS_IENABLE | CY_PLX_ICS_LOCAL_IENABLE);
>
>
>Otherwise, the inw doesn't read from the same register as you outw to. If
>someome would like me to diff this up, let me know. Otherwise, I'll assume
>the change will get committed?
>
>Gee, I feel good. My first bug fix.

   THANKS!!! Yes, that is indeed a stupid bug and likely causes all sorts of
bad things to happen.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project

From owner-freebsd-hackers  Wed Feb  5 14:04:21 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA15581
          for hackers-outgoing; Wed, 5 Feb 1997 14:04:21 -0800 (PST)
Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA15569
          for <freebsd-hackers@FreeBSD.ORG>; Wed, 5 Feb 1997 14:04:11 -0800 (PST)
Received: by iafnl.es.iaf.nl with UUCP id AA11943
  (5.67b/IDA-1.5 for freebsd-hackers@FreeBSD.ORG); Wed, 5 Feb 1997 23:03:41 +0100
Received: (from wilko@localhost) by yedi.iaf.nl (8.7.5/8.6.12) id WAA00359; Wed, 5 Feb 1997 22:56:03 +0100 (MET)
From: Wilko Bulte <wilko@yedi.iaf.nl>
Message-Id: <199702052156.WAA00359@yedi.iaf.nl>
Subject: Re: probing scsi bus after boot?
To: dufault@hda.com (Peter Dufault)
Date: Wed, 5 Feb 1997 22:56:03 +0100 (MET)
Cc: dufault@hda.com, joerg_wunsch@uriah.heep.sax.de,
        freebsd-hackers@FreeBSD.ORG, jlk@pavilion.co.uk
In-Reply-To: <199702051743.MAA01252@hda.hda.com> from "Peter Dufault" at Feb 5, 97 12:43:07 pm
X-Mailer: ELM [version 2.4 PL24 ME8a]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

As Peter Dufault wrote...

> > And apply a "probe all" to it:
> > 
> > > scsi -f /dev/scsi.ctl -p
> 
> And it will find the devices on the bus and panic with a corrupt stack.

Just tried this on a 2.1.5R system with 2 NCR810. Same/similar panic.

Observation: if bus 1 (second NCR) had a device on tgt 0 the
probe continued (successfully detecting devices) until it reached the
last target and paniced.

If tgt 0 was not present there was an immediate panic without even 
trying tgt IDs >0

Wilko
_     ____________________________________________________________________
 |   / o / /  _  Bulte  email: wilko@yedi.iaf.nl - Arnhem, The Netherlands
 |/|/ / / /( (_) 	Do, or do not. There is no 'try' - Yoda
--------------------------------------------------------------------------

From owner-freebsd-hackers  Wed Feb  5 14:52:55 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA19410
          for hackers-outgoing; Wed, 5 Feb 1997 14:52:55 -0800 (PST)
Received: from sax.sax.de (sax.sax.de [193.175.26.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA19387
          for <freebsd-hackers@freebsd.org>; Wed, 5 Feb 1997 14:52:48 -0800 (PST)
Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA19847; Wed, 5 Feb 1997 23:52:09 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id XAA14564; Wed, 5 Feb 1997 23:47:03 +0100 (MET)
Message-ID: <Mutt.19970205234703.j@uriah.heep.sax.de>
Date: Wed, 5 Feb 1997 23:47:03 +0100
From: j@uriah.heep.sax.de (J Wunsch)
To: alexis@ww.net (Alexis Yushin)
Cc: freebsd-hackers@freebsd.org
Subject: Re: sio11 64 events for device without tp related problem?
References: <199702051926.WAA02074@dawn.ww.net>
X-Mailer: Mutt 0.55-PL10
Mime-Version: 1.0
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <199702051926.WAA02074@dawn.ww.net>; from Alexis Yushin on Feb 5, 1997 22:26:31 +0300
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

As Alexis Yushin wrote:

> two messages 'sio11 64 events for device without tp' is generated.

I think that's basically stray interrupts being assigned to the
sio driver.

Does your sio11 perchance use irq 7?

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

From owner-freebsd-hackers  Wed Feb  5 14:54:13 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA19516
          for hackers-outgoing; Wed, 5 Feb 1997 14:54:13 -0800 (PST)
Received: from werple.net.au (melb.werple.net.au [203.9.190.18])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA19503
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 14:54:06 -0800 (PST)
Received: (qmail 23255 invoked by uid 5); 5 Feb 1997 22:54:03 -0000
MBOX-Line: From jb@freebsd1.cimlogic.com.au  Thu Feb  6 09:54:22 1997
Received: (from jb@localhost) by freebsd1.cimlogic.com.au (8.7.5/8.7.3) id JAA03545; Thu, 6 Feb 1997 09:54:22 +1100 (EST)
From: John Birrell <jb@cimlogic.com.au>
Message-Id: <199702052254.JAA03545@freebsd1.cimlogic.com.au>
Subject: Re: sigwait and threads?
To: terry@lambert.org (Terry Lambert)
Date: Thu, 6 Feb 1997 09:54:21 +1100 (EST)
Cc: lada@ws2301.gud.siemens.co.at, ljo@Mcs.Net, hackers@freebsd.org
In-Reply-To: <199702052141.OAA15633@phaeton.artisoft.com> from Terry Lambert at "Feb 5, 97 02:41:56 pm"
X-Mailer: ELM [version 2.4ME+ PL22 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Terry Lambert wrote:
> > Another difference that DCE requires and Draft 8 has thrown out is 
> > pthread_detach().
> 
> Ouch.  This sucks bad.

[... tries to imagine Terry sucking on a POSIX standard. 8-)]

Forget draft 8. Draft 10 was the one that was approved.

[...]
> 
> Without thread attach/detach notification, I can't implement my
> callable objects as being Rental or Free threaded.

Try this...

           ____________
          |            |
          |   ,----.   |
 [R]->E-->|---|L(A)|-->|-->           [X]-->
          |   `----'   |
          |            |
          |   ,----.   |
 [T]->E-->|---|R(R)|-->|-->           [Y]-->
          |   `----'   |
          |____________|

8-).

Regards,

-- 
John Birrell                                CIMlogic Pty Ltd
jb@cimlogic.com.au; jb@netbsd.org           119 Cecil Street
Ph  +61  3 9690 6900                        South Melbourne Vic 3205
Fax +61  3 9690 6650                        Australia
Mob +61 18  353  137

From owner-freebsd-hackers  Wed Feb  5 15:51:13 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA24347
          for hackers-outgoing; Wed, 5 Feb 1997 15:51:13 -0800 (PST)
Received: from news.IAEhv.nl (root@news.IAEhv.nl [194.151.64.4])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA24318
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 15:51:05 -0800 (PST)
Received: from LOCAL (uucp@localhost) 
          by news.IAEhv.nl (8.6.13/1.63) with IAEhv.nl; pid 19023
          on Thu, 6 Feb 1997 00:47:08 +0100; id AAA19023
          efrom: peter@grendel.IAEhv.nl; eto: hackers@freebsd.org
Received: (from peter@localhost)
          by grendel.IAEhv.nl (8.8.4/8.8.4)
	  id CAA00888; Wed, 5 Feb 1997 02:30:15 +0100 (MET)
Message-ID: <Mutt.19970205023015.peter@grendel.>
Date: Wed, 5 Feb 1997 02:30:15 +0100
From: peter@hw.nl (Peter Korsten)
To: hackers@freebsd.org
Subject: pppd (used to be: bisdn)
X-Mailer: Mutt 0.58-PL15
Mime-Version: 1.0
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

It's nice to see that my original question (is someone working on
PPP-support for bisdn-0.97?) resulted in a whole thread about how
many B and D channels one can have, why one would want to run PPP
over an ISDN line (authentification sounds like a good one to me)
and more.

By the way, it's working. I can dial in with PPP over HDLC. Thanks
to Andrew, whose last name eludes me at this moment. BUT:

The PPP patches patch pppd and make isdnpppd out of it. This is
some ISDN-specific stuff and really hasn't got much to do with
authentification. So, the small problem that I still have is a
pppd problem (not even a specific FreeBSD-problem, I guess).

Pppd expects my machine name as the first word on a line in the
pap-secrets file (I found that out with debug statements in the
isdnppd code). It tries to authenticate with that and then my ISP
tells me in polite terms to buzz off, because he wants my usercode
with a 'P' prepended. BTW, isdnpppd won't use the options file.

Therefore, I use the '+ua' option, but the man page states that
that option is 'obsolecent', so I'd like some solution that's
more future-aware. Am I doing something obviously wrong? I asked
Alta Vista, freebsd-questions and the yellow pages, but nothing
much came out.

- Peter
-- 
Peter Korsten  |  peter@grendel.IAEhv.nl (UUCP)  |  peterk@IAEhv.nl
C/C++/Perl/Java hacker

From owner-freebsd-hackers  Wed Feb  5 15:51:27 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA24386
          for hackers-outgoing; Wed, 5 Feb 1997 15:51:27 -0800 (PST)
Received: from news.IAEhv.nl (root@news.IAEhv.nl [194.151.64.4])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA24373
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 15:51:21 -0800 (PST)
Received: from LOCAL (uucp@localhost) 
          by news.IAEhv.nl (8.6.13/1.63) with IAEhv.nl; pid 19022
          on Thu, 6 Feb 1997 00:47:03 +0100; id AAA19022
          efrom: peter@grendel.IAEhv.nl; eto: UNKNOWN
Received: (from peter@localhost)
          by grendel.IAEhv.nl (8.8.4/8.8.4)
	  id CAA00861; Wed, 5 Feb 1997 02:06:34 +0100 (MET)
Message-ID: <Mutt.19970205020633.peter@grendel.>
Date: Wed, 5 Feb 1997 02:06:33 +0100
From: peter@hw.nl (Peter Korsten)
To: BigDaddy@LiveNet.Net (Joseph I. Arias)
Cc: hackers@freebsd.org
Subject: Re: Installing from DOS partition
References: <Mutt.19970201213010.j@uriah.heep.sax.de> <199702011809.NAA09929@Clifford.LiveNet.Net>
X-Mailer: Mutt 0.58-PL15
Mime-Version: 1.0
In-Reply-To: <Mutt.19970201213010.j@uriah.heep.sax.de>; from J Wunsch on Feb 1, 1997 21:30:10 +0100
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

J Wunsch shared with us:
> As Joseph I. Arias wrote:
> 
> > Should I download FreeBSD 2.2? I'm a beginger to Unix is 2.2 stable enough
> > for me to pratic on?
> 
> It's probably 20 times more stable than Win 3.1, and 5 times more
> stable than Win 95. :-)

I disagree. It's far more stable than that. It did help, though,
to throw the OPTI-087 ISA video board out and replace it with a
S3 PCI. Now Windows 95 doesn't hang at random when a rectangle
pops up.

But a my current and my previous job, FreeBSD is *very* stable,
unless you're doing very heavy ISP stuff. We reboot our machines
once a month, just out of habit.

> No offense intended, but i think somebody who's going to be serious
> about ISP business won't even install a DOS partition at all first.
> Waste of space.  You even didn't learn how to give your mail a subject
> line yet... how are you going to teach your customers about Internet
> Netiquette?

Said previous employer, an ISP, just bought a box with 30 ISDN/V34
connections. Primary rate in, 100 Mbit Ehternet out. That thing
costs almost 1,5 as much as I earn in a year, before taxes. You
simply can't compete, money-wise and knowledge-wise (concerning
system maintainance etc.) with the established ISP's. Even if you
could throw in a couple of 100,000's, you would have a hard time.

- Peter
-- 
Peter Korsten  |  peter@grendel.IAEhv.nl (UUCP)  |  peterk@IAEhv.nl
C/C++/Perl/Java hacker

From owner-freebsd-hackers  Wed Feb  5 16:50:32 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id QAA29481
          for hackers-outgoing; Wed, 5 Feb 1997 16:50:32 -0800 (PST)
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA29473
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 16:50:30 -0800 (PST)
Received: from werple.net.au (melb.werple.net.au [203.9.190.18])
          by who.cdrom.com (8.7.5/8.6.11) with SMTP id QAA17500
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 16:50:28 -0800 (PST)
Received: (qmail 5176 invoked by uid 5); 6 Feb 1997 00:49:47 -0000
MBOX-Line: From jb@freebsd1.cimlogic.com.au  Thu Feb  6 11:50:17 1997
Received: (from jb@localhost) by freebsd1.cimlogic.com.au (8.7.5/8.7.3) id LAA03861 for hackers@freebsd.org; Thu, 6 Feb 1997 11:50:17 +1100 (EST)
From: John Birrell <jb@cimlogic.com.au>
Message-Id: <199702060050.LAA03861@freebsd1.cimlogic.com.au>
Subject: fcntl, F_SETFL, O_NONBLOCK & /dev/null
To: hackers@freebsd.org
Date: Thu, 6 Feb 1997 11:50:16 +1100 (EST)
X-Mailer: ELM [version 2.4ME+ PL22 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

G'day,

I can open /dev/null with O_NONBLOCK. If I open /dev/null without
O_NONBLOCK and then try to fcntl F_SETFL to change the file descriptor
to non-blocking, I get ENODEV returned. Can someone tell me why?

Regards,

-- 
John Birrell                                CIMlogic Pty Ltd
jb@cimlogic.com.au; jb@netbsd.org           119 Cecil Street
Ph  +61  3 9690 6900                        South Melbourne Vic 3205
Fax +61  3 9690 6650                        Australia
Mob +61 18  353  137

From owner-freebsd-hackers  Wed Feb  5 17:08:15 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA00710
          for hackers-outgoing; Wed, 5 Feb 1997 17:08:15 -0800 (PST)
Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA00695
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 17:08:08 -0800 (PST)
Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.7.3) with ESMTP id RAA23763 for <hackers@freebsd.org>; Wed, 5 Feb 1997 17:08:24 -0800 (PST)
Message-Id: <199702060108.RAA23763@rah.star-gate.com>
X-Mailer: exmh version 1.6.9 8/22/96
To: hackers@freebsd.org
Subject: ACE and FreeBSD
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 05 Feb 1997 17:08:24 -0800
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


I have had moderate success with ACE and will post the patches early
next week. Mostly because I am going to be out of town for the rest 
of the week.

At any rate, you will need the latest pthread lib which 
John Birrell <jb@cimlogic.com.au> was kind to upgrade to support ACE.
The pthread patches should be in 3.0-current by the time that I post
my patches for ACE.


	Enjoy,
	Amancio

	





From owner-freebsd-hackers  Wed Feb  5 17:08:51 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA00761
          for hackers-outgoing; Wed, 5 Feb 1997 17:08:51 -0800 (PST)
Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA00755
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 17:08:43 -0800 (PST)
Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id LAA28587; Thu, 6 Feb 1997 11:38:24 +1030 (CST)
From: Michael Smith <msmith@atrad.adelaide.edu.au>
Message-Id: <199702060108.LAA28587@genesis.atrad.adelaide.edu.au>
Subject: Re: Samba survey
In-Reply-To: <199702052059.MAA19654@rah.star-gate.com> from Amancio Hasty at "Feb 5, 97 12:59:21 pm"
To: hasty@rah.star-gate.com (Amancio Hasty)
Date: Thu, 6 Feb 1997 11:38:23 +1030 (CST)
Cc: mark@quickweb.com, hackers@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Amancio Hasty stands accused of saying:
> Is there a configuration tool which aids a new user like me to setup 
> samba?

Not AFAIK.  (I have a meta-tool that could be used to make it fairly easy,
but it's not going anywhere at the moment.)

I usually find that the average samba site setup requires little more than
boilerplate duplication of the examples in the docco; it's really very
simple.


-- 
]] Mike Smith, Software Engineer        msmith@gsoft.com.au             [[
]] Genesis Software                     genesis@gsoft.com.au            [[
]] High-speed data acquisition and      (GSM mobile)     0411-222-496   [[
]] realtime instrument control.         (ph)          +61-8-8267-3493   [[
]] Unix hardware collector.             "Where are your PEZ?" The Tick  [[

From owner-freebsd-hackers  Wed Feb  5 17:31:23 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA03060
          for hackers-outgoing; Wed, 5 Feb 1997 17:31:23 -0800 (PST)
Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA03051
          for <hackers@FreeBSD.ORG>; Wed, 5 Feb 1997 17:31:12 -0800 (PST)
Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id MAA28813; Thu, 6 Feb 1997 12:01:08 +1030 (CST)
From: Michael Smith <msmith@atrad.adelaide.edu.au>
Message-Id: <199702060131.MAA28813@genesis.atrad.adelaide.edu.au>
Subject: Re: fcntl, F_SETFL, O_NONBLOCK & /dev/null
In-Reply-To: <199702060050.LAA03861@freebsd1.cimlogic.com.au> from John Birrell at "Feb 6, 97 11:50:16 am"
To: jb@cimlogic.com.au (John Birrell)
Date: Thu, 6 Feb 1997 12:01:07 +1030 (CST)
Cc: hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

John Birrell stands accused of saying:
> 
> I can open /dev/null with O_NONBLOCK. If I open /dev/null without
> O_NONBLOCK and then try to fcntl F_SETFL to change the file descriptor
> to non-blocking, I get ENODEV returned. Can someone tell me why?

Probably because the ioctl handler for /dev/null doesn't understand
F_SETFL.  I can't find the sucker, so I can't actually give you an
authorative answer 8(

> John Birrell                                CIMlogic Pty Ltd

-- 
]] Mike Smith, Software Engineer        msmith@gsoft.com.au             [[
]] Genesis Software                     genesis@gsoft.com.au            [[
]] High-speed data acquisition and      (GSM mobile)     0411-222-496   [[
]] realtime instrument control.         (ph)          +61-8-8267-3493   [[
]] Unix hardware collector.             "Where are your PEZ?" The Tick  [[

From owner-freebsd-hackers  Wed Feb  5 17:51:48 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA03979
          for hackers-outgoing; Wed, 5 Feb 1997 17:51:48 -0800 (PST)
Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id RAA03941
          for <freebsd-hackers@freebsd.org>; Wed, 5 Feb 1997 17:50:53 -0800 (PST)
Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02)
	id AA20758; Wed, 5 Feb 1997 20:50:14 -0500
Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Wed,  5 Feb 1997 20:50 EST
Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id UAA28238; Wed, 5 Feb 1997 20:20:04 -0500 (EST)
Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id UAA25717; Wed, 5 Feb 1997 20:24:34 -0500 (EST)
Date: Wed, 5 Feb 1997 20:24:34 -0500 (EST)
From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
Message-Id: <199702060124.UAA25717@lakes.water.net>
To: ponds!lakes.water.net!rivers, ponds!lambert.org!terry
Subject: Re: [Fwd: freebsd performance.]
Cc: ponds!freebsd.org!freebsd-hackers, ponds!xinside.com!patrick
Content-Type: text
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > > There are two different 'engines' - NFA (nondeterministic finite
> > > automaton) and DFA (deterministic finite automaton).  Perl is
> > > 'traditional NFA' according to Mr. Friedl, while POSIX leans towards
> > > DFA-like behavior in all cases (always returns 'leftmost-longest' that
> > > matches - perl returns I believe the first part that matches).
> >  
> >  Ah, but you should remember that all NFAs are convertable to DFAs.
> 
> What?  What?  You've solved the "machine translation of natural
> languages" problem?!?!  Why wasn't I told?!?!
> 
> 
> 					Terry Lambert
> 					terry@lambert.org

 Nope - elementary automata theory - NFAs are convertable to DFAs (in fact,
it's on page 17 of Hopcroft and Ullman's "Introduction to Automata Theory,
Languages, and Computation" - one of the very elementary ideas.)

 The key to remember here is the FA part (Finite Automata) - they are just
regular languages.  Regular languages are regular languages; rather DFA or
NFA.

 The basic idea for the equivalence proof is that:
	
	1) All DFAs are NFAs (of course)
	2) Any NFA can be represented as a DFA where the states of
	    the DFA tuples of the states of the NFA.  [Think about
	    how you would write an NFA simulator; you'd have N
	    possible states moving from transition to transition.]

 So, DFA <-> NFA.

 Unfortunately, this has very little to do with natural languages.

 For a thorough understanding of automata theory and computation theory;
I would recommend that Hopcroft and Ullman text, published by Addison Wesley.
[I'm not sure it's still in print, however.]  Unfortunately, most
compiler courses in Universities these days no longer bother with
automata theory...

	 - Dave Rivers -



From owner-freebsd-hackers  Wed Feb  5 18:13:21 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id SAA04986
          for hackers-outgoing; Wed, 5 Feb 1997 18:13:21 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA04981
          for <hackers@FreeBSD.org>; Wed, 5 Feb 1997 18:13:14 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id NAA32068; Thu, 6 Feb 1997 13:08:24 +1100
Date: Thu, 6 Feb 1997 13:08:24 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199702060208.NAA32068@godzilla.zeta.org.au>
To: hackers@FreeBSD.org, jb@cimlogic.com.au
Subject: Re: fcntl, F_SETFL, O_NONBLOCK & /dev/null
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>I can open /dev/null with O_NONBLOCK. If I open /dev/null without
>O_NONBLOCK and then try to fcntl F_SETFL to change the file descriptor
>to non-blocking, I get ENODEV returned. Can someone tell me why?

fcntl(fd, F_SETFL, O_NONBLOCK) is translated to an FIONBIO ioctl, and
the device driver for /dev/null doesn't support this ioctl.  None of
the memory devices support it.

Another problem with the translation is that the flag is supposed to
be per-file, but if the FIONBIO ioctl actually does anything, then
the flag is sort of per device - a per-file flag is kept in all cases,
but it may be inconsistent with the device state.

One way to fix this is to remove the FIONBIO calls from fcntl().
This isn't quite right, since it should be possible for drivers to reject
O_NONBLOCK (or maybe !O_NONBLOCK).  However, in practice most drivers
are too stupid to check for O_NONBLOCK in their open routine and too
stupid to support FIONBIO in their ioctl routine.  This results in the
stupid behaviour that you observed.

Bruce

From owner-freebsd-hackers  Wed Feb  5 18:21:42 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id SAA05314
          for hackers-outgoing; Wed, 5 Feb 1997 18:21:42 -0800 (PST)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id SAA05283;
          Wed, 5 Feb 1997 18:21:32 -0800 (PST)
Received: from rover.village.org [127.0.0.1] 
	by rover.village.org with esmtp (Exim 0.56 #1)
	id E0vsJSi-0002aD-00; Wed, 5 Feb 1997 19:21:20 -0700
To: Bruce Evans <bde@zeta.org.au>
Subject: Re: conditionally including <sys/param.h> 
Cc: obrien@NUXI.com, freebsd-ports@freebsd.org, hackers@freebsd.org
In-reply-to: Your message of "Thu, 06 Feb 1997 04:45:24 +1100."
		<199702051745.EAA12664@godzilla.zeta.org.au> 
References: <199702051745.EAA12664@godzilla.zeta.org.au>  
Date: Wed, 05 Feb 1997 19:21:19 -0700
From: Warner Losh <imp@village.org>
Message-Id: <E0vsJSi-0002aD-00@rover.village.org>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <199702051745.EAA12664@godzilla.zeta.org.au> Bruce Evans writes:
: strerror() doesn't exist on old systems.

True.  But how old is old?

: I think we should just use `#ifdef __FreeBSD__' and <sys/param.h> in
: ports.  Original authors should use a better method to suit themselves.

Yes, but this whole thing got started because the #ifdef __FreeBSD__
was slowly turning into
	#if defined(__OpenBSD__) || defined(__NetBSD__) || defined(__FreeBSD__)
in a bunch of places due to those projects riding along on the FreeBSD
port's coat tails.

Warner

From owner-freebsd-hackers  Wed Feb  5 18:26:08 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id SAA05567
          for hackers-outgoing; Wed, 5 Feb 1997 18:26:08 -0800 (PST)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id SAA05543;
          Wed, 5 Feb 1997 18:25:59 -0800 (PST)
Received: from rover.village.org [127.0.0.1] 
	by rover.village.org with esmtp (Exim 0.56 #1)
	id E0vsJWO-0002dq-00; Wed, 5 Feb 1997 19:25:08 -0700
To: obrien@NUXI.com (David O'Brien)
Subject: Re: conditionally including <sys/param.h> 
Cc: chuckr@glue.umd.edu (Chuck Robey),
        freebsd-ports@freebsd.org (FreeBSD ports list), hackers@freebsd.org
In-reply-to: Your message of "Wed, 05 Feb 1997 11:26:04 PST."
		<19970205112604.AI13761@dragon.nuxi.com> 
References: <19970205112604.AI13761@dragon.nuxi.com>  <19970205003343.YB13323@dragon.nuxi.com> <Pine.OSF.3.95q.970205081326.9802A-100000@gilligan.eng.umd.edu> 
Date: Wed, 05 Feb 1997 19:25:07 -0700
From: Warner Losh <imp@village.org>
Message-Id: <E0vsJWO-0002dq-00@rover.village.org>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <19970205112604.AI13761@dragon.nuxi.com> David O'Brien writes:
: Thing.  Since both NetBSD and OpenBSD pretty much use our ports (and I
: think they like not having to throw resources on them), it would be in
: their best interests for the return they get.

Ummm, there is some effort in doing that for things that need to
change on FreeBSD, since they likely need to change for OpenBSD and
NetBSD as well.

: using these macros.  They seem to be the only true way of dealing with
: this.  If anyone knows who wrote those words, I'd love to start a dialog
: with them.

I strongly disagree with this.  I think that the BSD macro method
works well enough, and with the slight tweaks that we've talked about
here it works almost perfectly.  It is close enough to perfect that
most software authors will take the changes back into their source
trees and things will be solved for all the BSDs, not just Free,Open
and Net (oh, and BSDi too).

Warner


From owner-freebsd-hackers  Wed Feb  5 19:00:47 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA07441
          for hackers-outgoing; Wed, 5 Feb 1997 19:00:47 -0800 (PST)
Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA07433
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 19:00:42 -0800 (PST)
Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id NAA29537; Thu, 6 Feb 1997 13:29:07 +1030 (CST)
From: Michael Smith <msmith@atrad.adelaide.edu.au>
Message-Id: <199702060259.NAA29537@genesis.atrad.adelaide.edu.au>
Subject: Re: What happened to the splash screen?
In-Reply-To: <199702051445.PAA00531@ravenock.cybercity.dk> from =?ISO-8859-1?Q?S=F8ren_Schmidt?= at "Feb 5, 97 03:44:54 pm"
To: sos@ravenock.cybercity.dk (Søren Schmidt)
Date: Thu, 6 Feb 1997 13:29:05 +1030 (CST)
Cc: csubl@csv.warwick.ac.uk, hackers@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Søren Schmidt stands accused of saying:
> In reply to Mr M P Searle who wrote:
> > There was a discussion on this list a while ago about a possible
> > 'splash screen' while booting - I remember a lot of suggestions
> > about it, but did it ever get done? (if so, can someone send me
> > the patches?)
> 
> Uhm, the basic support has been added to syscons, all that is needed
> is a function to read the actual image and put it into the videomemory
> depending on what mode has been chosen.

There's code to do 320x200x256 .bmp files if that's any help.  Soren
was looking for some code to do 640x480x16 images; I just need to 
extract the digit and rewrite my (wrong) 4-plane pixel-set routine.

There was also a problem with VGA font corruption; did that get fixed
Soren?  The last difficulty is that during device probes, interrupts are
turned off so you can't hotkey between the splash and the probe display.

> Søren Schmidt               (sos@FreeBSD.org)               FreeBSD Core Team

-- 
]] Mike Smith, Software Engineer        msmith@gsoft.com.au             [[
]] Genesis Software                     genesis@gsoft.com.au            [[
]] High-speed data acquisition and      (GSM mobile)     0411-222-496   [[
]] realtime instrument control.         (ph)          +61-8-8267-3493   [[
]] Unix hardware collector.             "Where are your PEZ?" The Tick  [[

From owner-freebsd-hackers  Wed Feb  5 19:14:33 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA00342
          for hackers-outgoing; Wed, 5 Feb 1997 19:14:33 -0800 (PST)
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA00292;
          Wed, 5 Feb 1997 19:14:26 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by who.cdrom.com (8.7.5/8.6.11) with ESMTP id TAA17659
          ; Wed, 5 Feb 1997 19:02:51 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id OAA01390; Thu, 6 Feb 1997 14:00:30 +1100
Date: Thu, 6 Feb 1997 14:00:30 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199702060300.OAA01390@godzilla.zeta.org.au>
To: bde@zeta.org.au, imp@village.org
Subject: Re: conditionally including <sys/param.h>
Cc: freebsd-ports@freebsd.org, hackers@freebsd.org, obrien@NUXI.com
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>: strerror() doesn't exist on old systems.
>
>True.  But how old is old?

Orphaned systems still don't have it.

>: I think we should just use `#ifdef __FreeBSD__' and <sys/param.h> in
>: ports.  Original authors should use a better method to suit themselves.
>
>Yes, but this whole thing got started because the #ifdef __FreeBSD__
>was slowly turning into
>	#if defined(__OpenBSD__) || defined(__NetBSD__) || defined(__FreeBSD__)
>in a bunch of places due to those projects riding along on the FreeBSD
>port's coat tails.

Maybe include <sys/param.h> unconditionally?  I'm not sure why I mentioned
the __FreeBSD__ ifdef above.  I've never liked ifdefing on the OS -
it isn't necessary for one OS and gives too-large ifdefs for more than
2 OS's.  You'll still need large ifdefs if configuration depends on the
value of `BSD' and the value is OS-dependent.

Bruce

From owner-freebsd-hackers  Wed Feb  5 19:17:21 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA00660
          for hackers-outgoing; Wed, 5 Feb 1997 19:17:21 -0800 (PST)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id TAA00624;
          Wed, 5 Feb 1997 19:17:11 -0800 (PST)
Received: from rover.village.org [127.0.0.1] 
	by rover.village.org with esmtp (Exim 0.56 #1)
	id E0vsKKV-00030G-00; Wed, 5 Feb 1997 20:16:55 -0700
To: Bruce Evans <bde@zeta.org.au>
Subject: Re: conditionally including <sys/param.h> 
Cc: freebsd-ports@freebsd.org, hackers@freebsd.org, obrien@NUXI.com
In-reply-to: Your message of "Thu, 06 Feb 1997 14:00:30 +1100."
		<199702060300.OAA01390@godzilla.zeta.org.au> 
References: <199702060300.OAA01390@godzilla.zeta.org.au>  
Date: Wed, 05 Feb 1997 20:16:55 -0700
From: Warner Losh <imp@village.org>
Message-Id: <E0vsKKV-00030G-00@rover.village.org>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <199702060300.OAA01390@godzilla.zeta.org.au> Bruce Evans writes:
: Maybe include <sys/param.h> unconditionally?  I'm not sure why I mentioned
: the __FreeBSD__ ifdef above.  I've never liked ifdefing on the OS -
: it isn't necessary for one OS and gives too-large ifdefs for more than
: 2 OS's.  You'll still need large ifdefs if configuration depends on the
: value of `BSD' and the value is OS-dependent.

True.  However, the current handbook recommends including this if unix
is defined and USG isn't defined.  This seems the best compromize for
the moment.  Generally, USG is defined on the old, musty SYS III and
SYS V machines, so this works well.

Warner

From owner-freebsd-hackers  Wed Feb  5 19:44:10 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA02290
          for hackers-outgoing; Wed, 5 Feb 1997 19:44:10 -0800 (PST)
Received: from w2xo.pgh.pa.us (w2xo.pgh.pa.us [206.210.70.5])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA02235
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 19:43:44 -0800 (PST)
Received: from w2xo.pgh.pa.us (localhost [127.0.0.1])
          by w2xo.pgh.pa.us (8.8.4/8.8.4) with SMTP
	  id WAA24229 for <hackers@freebsd.org>; Wed, 5 Feb 1997 22:43:33 -0500 (EST)
Message-ID: <32F95364.2781E494@w2xo.pgh.pa.us>
Date: Wed, 05 Feb 1997 22:43:32 -0500
From: Jim Durham <durham@w2xo.pgh.pa.us>
Organization: Dis-
X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.1.6-RELEASE i386)
MIME-Version: 1.0
To: hackers@freebsd.org
Subject: DOS partition trouble
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Twice now, I have removed a DOS partition
from a disk with both DOS and FreeBSD
partitions and been unable to boot FreeBSD.

In the case today, it was partition 1 that
was a DOS fat type partition. I wanted to
remove that and use it for FreeBSD.

Upon removing the partition with DOS FDISK,
I was no longer able to boot the FreeBSD partition.
The boot code appeared to be jumping off to nowhere.
The boot manager menu would appear, then , when it
tried to proceed with the boot, it would crash and reboot.

After fooling with this for a couple of hours, I finally
decided to try putting the DOS partition back, so I deleted
the new FreeBSD partition and replaced it with a DOS partition.
I formatted this and had no trouble booting DOS. I then ran the
partition editor in sysinstall and wrote out a new boot
Block. Voila! Now I can boot the FreeBSD (and the DOS) partitions.
Why?

I had tried running the partition editor when I had no DOS
partition and it gave all indications of sucessfully writing
out the boot block, but would not boot until I remade the
DOS partition. Trying to mount the root directory from the MFS
on the boot floppy gave a "bad super block" error.

I thought I understood what was going on with the partition
scheme, but I guess not. Can someone please proffer an
explanation of this behavior?

thanks
Jim Durham

From owner-freebsd-hackers  Wed Feb  5 19:54:47 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA02794
          for hackers-outgoing; Wed, 5 Feb 1997 19:54:47 -0800 (PST)
Received: from sendero.i-connect.net ([206.190.144.100])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA02789;
          Wed, 5 Feb 1997 19:54:42 -0800 (PST)
Received: (from shimon@localhost)
          by sendero.i-connect.net (8.8.5/8.8.4)
	  id UAA06804; Wed, 5 Feb 1997 20:53:54 -0800 (PST)
Message-ID: <XFMail.970205205354.Shimon@i-Connect.Net>
X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD
Content-Type: text/plain; charset=iso-8859-8
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Date: Wed, 05 Feb 1997 19:33:54 -0800 (PST)
Organization: iConnect Corp.
From: Simon Shapiro <Shimon@i-Connect.Net>
To: freebsd-scsi@freebsd.org, freebsd-hackers@freebsd.org
Subject: Contigious (spelling?) allocation in kernel
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I need to allocate a contigious (one piece :-) block of memory for a DMA
scatter/gather list.  The HBA knows how to do scatter gather, but wants a
single pointer to a single block of memory that hoslds the entire list.
The SG structure is very plain, 32bits for length and 32bits for physical
address; 8 bytes.  The thing is capable of up to 8192 entries, which give
us a possible list of 64KB per request list.

As each HBA can have up to 256 concurrent requests, with who knows how
many more in the driver's queue, the list can grow quite impressively.
Since most requests are smaller, it seems very wasteful to allocate all
this memory upfront.  So malloc is in order, but what are the options?

Thanx,

Simon

From owner-freebsd-hackers  Wed Feb  5 20:50:37 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA06413
          for hackers-outgoing; Wed, 5 Feb 1997 20:50:37 -0800 (PST)
Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id UAA06404
          for <freebsd-hackers@freefall.FreeBSD.org>; Wed, 5 Feb 1997 20:50:34 -0800 (PST)
Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02)
	id AA29717; Wed, 5 Feb 1997 23:50:02 -0500
Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Wed,  5 Feb 1997 23:50 EST
Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id XAA01655 for <freebsd-hackers@freefall.cdrom.com>; Wed, 5 Feb 1997 23:22:55 -0500 (EST)
Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id XAA26120 for freebsd-hackers@freefall.cdrom.com; Wed, 5 Feb 1997 23:27:26 -0500 (EST)
Date: Wed, 5 Feb 1997 23:27:26 -0500 (EST)
From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
Message-Id: <199702060427.XAA26120@lakes.water.net>
To: ponds!freefall.cdrom.com!freebsd-hackers
Subject: 2.2-GAMMA panic during installation (just after newfs of /)
Content-Type: text
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


Just to try and stay ahead of the game, I down loaded the 
floppies from 2.2-GAMMA as of 2/5/97.

Unfortunately; I still get the same panic during the newfs of
/dev/rsd0a during install.

  panic: ffs_valloc: dup alloc


Particulars on this machine (and I note that I've seen this
panic on two sets of hardware at this point; both of which are 386dx-s)

   387dx-33 w/387, 12meg memory, aha1542B, ~500meg micropolis 1588 disk,
   hercules monochrome; NE2000 clone card, 2.2-GAMMA #0 kernel.

The geometry of the disk is 636cyls/64 heads/32 sectors (as mapped by
the 1542B).

I chosen the "Use entire disk" option, which gives me 3 partitions
(in the DOS sense of the word):

  Offset      Size      End   Name  PType      Desc Subtype  Flags
       0        32       31      -      6    unused       0
      32   1302496  1302527  sd0s1      3   freebsd     165     C
 1302528      1524  1304051      -      6    unused       0

I don't touch the boot record.

I then label the disk as:


  sd0s1a  /	     100MB  UFS
  sd0s1b  <none>      50MB  SWAP
  sd0s1e  /usr       485MB  UFS

[Just / and /usr...]  If I use other sizes, I can avoid this panic.

According to the debugging info on VTY-2, the / filesystem is created 
with the default newfs options:

   -b 8192 -f 1024 /dev/sd0s1a

Then, again according to the debugging info on VTY-2; the newfs succeeds.

The volume is mounted and a couple of mkdir commands get executed;
then - whamo, panic.


	- Dave Rivers -


From owner-freebsd-hackers  Wed Feb  5 20:50:39 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA06426
          for hackers-outgoing; Wed, 5 Feb 1997 20:50:39 -0800 (PST)
Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id UAA06411
          for <freebsd-hackers@freebsd.org>; Wed, 5 Feb 1997 20:50:35 -0800 (PST)
Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02)
	id AA29733; Wed, 5 Feb 1997 23:50:04 -0500
Received: from lambert.org by dg-rtp.dg.com.rtp.dg.com; Wed,  5 Feb 1997 23:50 EST
Received: from dg-rtp.UUCP (uucp@localhost) by ponds.water.net (8.8.3/8.7.3) with UUCP id XAA01678 for freebsd.org!freebsd-hackers; Wed, 5 Feb 1997 23:23:36 -0500 (EST)
Received: from reggae.ncren.net by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02)
	id AA10021; Wed, 5 Feb 1997 21:30:43 -0500
Received: from mcnc.UUCP by reggae.ncren.net (5.65/tas-reggae/may94)
	id AA11827; Wed, 5 Feb 97 21:30:04 -0500
Received: from ncnoc.ncren.net by reggae.ncren.net (5.65/tas-reggae/may94)
	id AA11576; Wed, 5 Feb 97 21:06:19 -0500
Received: from stingray.mcnc.org (stingray.mcnc.org [128.109.130.74]) by ncnoc.ncren.net (8.7.4/8.7.3) with ESMTP id VAA02664; Wed, 5 Feb 1997 21:05:56 -0500 (EST)
Received: from relay3.UU.NET by stingray.mcnc.org (8.8.4/MCNC/CIS - 1.0 - 012297)
	id VAA17127; Wed, 5 Feb 1997 21:03:19 -0500 (EST)
Received: from phaeton.artisoft.com by relay3.UU.NET with SMTP 
	(peer crosschecked as: phaeton.Artisoft.COM [198.17.250.211])
	id QQcbqu25522; Wed, 5 Feb 1997 21:05:48 -0500 (EST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id TAA16316; Wed, 5 Feb 1997 19:01:10 -0700
Posted-Date: Wed, 5 Feb 1997 21:03:19 -0500 (EST)
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702060201.TAA16316@phaeton.artisoft.com>
Subject: Re: [Fwd: freebsd performance.]
To: ponds!ponds!rivers (Thomas David Rivers)
Date: Wed, 5 Feb 1997 19:01:10 -0700 (MST)
Cc: ponds!uunet.UU.NET!ponds!lakes.water.net!rivers,
        ponds!uunet.UU.NET!ponds!lambert.org!terry,
        ponds!uunet.UU.NET!ponds!freebsd.org!freebsd-hackers,
        ponds!uunet.UU.NET!ponds!xinside.com!patrick
In-Reply-To: <199702060124.UAA25717@lakes.water.net> from "Thomas David Rivers" at Feb 5, 97 08:24:34 pm
X-Mailer: ELM [version 2.4 PL24]
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>  The basic idea for the equivalence proof is that:
> 	
> 	1) All DFAs are NFAs (of course)
> 	2) Any NFA can be represented as a DFA where the states of
> 	    the DFA tuples of the states of the NFA.  [Think about
> 	    how you would write an NFA simulator; you'd have N
> 	    possible states moving from transition to transition.]
> 
>  So, DFA <-> NFA.

Cheater... "non-finite" != "infinite" in this definition.

BTW: The "machine translation of natural languages" question was asked
tongue-in-cheek... I suppose I need to add "8-)"'s.  8-(.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Wed Feb  5 20:50:41 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA06444
          for hackers-outgoing; Wed, 5 Feb 1997 20:50:41 -0800 (PST)
Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id UAA06424
          for <freebsd-hackers@freefall.FreeBSD.org>; Wed, 5 Feb 1997 20:50:38 -0800 (PST)
Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02)
	id AA29768; Wed, 5 Feb 1997 23:50:07 -0500
Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Wed,  5 Feb 1997 23:50 EST
Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id XAA01887; Wed, 5 Feb 1997 23:31:22 -0500 (EST)
Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id XAA26215; Wed, 5 Feb 1997 23:35:54 -0500 (EST)
Date: Wed, 5 Feb 1997 23:35:54 -0500 (EST)
From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
Message-Id: <199702060435.XAA26215@lakes.water.net>
To: ponds!freefall.cdrom.com!freebsd-hackers, ponds!xinside.com!patrick,
        ponds!lambert.org!terry
Subject: Re: [Fwd: freebsd performance.]
Content-Type: text
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 
> >  The basic idea for the equivalence proof is that:
> > 	
> > 	1) All DFAs are NFAs (of course)
> > 	2) Any NFA can be represented as a DFA where the states of
> > 	    the DFA tuples of the states of the NFA.  [Think about
> > 	    how you would write an NFA simulator; you'd have N
> > 	    possible states moving from transition to transition.]
> > 
> >  So, DFA <-> NFA.
> 
> Cheater... "non-finite" != "infinite" in this definition.
> 
> BTW: The "machine translation of natural languages" question was asked
> tongue-in-cheek... I suppose I need to add "8-)"'s.  8-(.
> 
> 
> 					Terry Lambert

 Err, umm,  in the context of regular expressions; (recall the original
discussion was the speed of regex vs. pearl):

   NFA is
      Non-deterministic _Finite_ Automata
   DFA is
      Deterministic _Finite_ Automata

 Determinism is quite a different idea from finite/infinite.

 We haven't crossed over into the "infinite" yet :-)  It's rather
interesting to banty around the idea infinite automata, and possible 
ramifications on a G.O.D. (General Omniscient Device), much less our
own existence; especially over some beer :-)

	- Dave Rivers -


From owner-freebsd-hackers  Wed Feb  5 20:50:43 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA06465
          for hackers-outgoing; Wed, 5 Feb 1997 20:50:43 -0800 (PST)
Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id UAA06439
          for <hackers@FreeBSD.ORG>; Wed, 5 Feb 1997 20:50:40 -0800 (PST)
Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02)
	id AA29785; Wed, 5 Feb 1997 23:50:08 -0500
Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Wed,  5 Feb 1997 23:50 EST
Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id XAA01897; Wed, 5 Feb 1997 23:35:36 -0500 (EST)
Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id XAA26231; Wed, 5 Feb 1997 23:40:07 -0500 (EST)
Date: Wed, 5 Feb 1997 23:40:07 -0500 (EST)
From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
Message-Id: <199702060440.XAA26231@lakes.water.net>
To: ponds!zeta.org.au!bde, imp@village.org
Subject: Re: conditionally including <sys/param.h>
Cc: ponds!FreeBSD.ORG!freebsd-ports, ponds!FreeBSD.ORG!hackers,
        ponds!NUXI.com!obrien
Content-Type: text
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


Warner Losh writes:
> 
> In message <199702051745.EAA12664@godzilla.zeta.org.au> Bruce Evans writes:
> : strerror() doesn't exist on old systems.
> 
> True.  But how old is old?

 This is a good point; and brings up one of 

   Dave's Portable Programing Axioms

     If a standard function is missing; provide it in a compatibility
     library - avoid kludges such as #ifdef's.  You'll have greatly
     improved legibility of the source, while helping future portability.

 As a case in point, in one of my older compatibility libraries, you 
can find strerror(). I believe it was missing on SunOS 3.5, some time
ago :-)

	- Dave Rivers -

From owner-freebsd-hackers  Wed Feb  5 20:50:50 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA06507
          for hackers-outgoing; Wed, 5 Feb 1997 20:50:50 -0800 (PST)
Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id UAA06495
          for <hackers@FreeBSD.ORG>; Wed, 5 Feb 1997 20:50:47 -0800 (PST)
Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02)
	id AA29838; Wed, 5 Feb 1997 23:50:15 -0500
Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Wed,  5 Feb 1997 23:50 EST
Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id XAA01906; Wed, 5 Feb 1997 23:38:33 -0500 (EST)
Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id XAA26253; Wed, 5 Feb 1997 23:43:05 -0500 (EST)
Date: Wed, 5 Feb 1997 23:43:05 -0500 (EST)
From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
Message-Id: <199702060443.XAA26253@lakes.water.net>
To: msmith@atrad.adelaide.edu.au, ponds!ravenock.cybercity.dk!sos
Subject: Re: What happened to the splash screen?
Cc: ponds!csv.warwick.ac.uk!csubl, ponds!FreeBSD.ORG!hackers
Content-Type: text
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> S=F8ren Schmidt stands accused of saying:
> > In reply to Mr M P Searle who wrote:
> > > There was a discussion on this list a while ago about a possible
> > > 'splash screen' while booting - I remember a lot of suggestions
> > > about it, but did it ever get done? (if so, can someone send me
> > > the patches?)
> >=20
> > Uhm, the basic support has been added to syscons, all that is needed
> > is a function to read the actual image and put it into the videomemory
> > depending on what mode has been chosen.
> 
> There's code to do 320x200x256 .bmp files if that's any help.  Soren
> was looking for some code to do 640x480x16 images; I just need to=20
> extract the digit and rewrite my (wrong) 4-plane pixel-set routine.
> 
> There was also a problem with VGA font corruption; did that get fixed
> Soren?  The last difficulty is that during device probes, interrupts are
> turned off so you can't hotkey between the splash and the probe display.

 I'm just curious; if this were to get "put in" - would it do
something meaningful on monochrome (i.e. Hercules compatible) displays?

> 
> > S=F8ren Schmidt               (sos@FreeBSD.org)               FreeBSD C=
> ore Team
> 

	- Dave R. -

From owner-freebsd-hackers  Wed Feb  5 20:53:44 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA06818
          for hackers-outgoing; Wed, 5 Feb 1997 20:53:44 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA06811;
          Wed, 5 Feb 1997 20:53:40 -0800 (PST)
Received: (from jkh@localhost) by time.cdrom.com (8.8.5/8.6.9) id UAA27279; Wed, 5 Feb 1997 20:53:38 -0800 (PST)
Date: Wed, 5 Feb 1997 20:53:38 -0800 (PST)
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Message-Id: <199702060453.UAA27279@time.cdrom.com>
To: announce@freebsd.org
Subject: My resignation as president of the FreeBSD Project.
Cc: hackers@freebsd.org
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

This short notice is just to announce my resignation as President
of the FreeBSD Project, effective immediately, coinciding with the
elimination of that position.

This is entirely my own decision and was not prompted by anyone
on the core team - if anything, they will probably be as surprised
as anyone at the news (except for David & John D., with whom I've
already discussed the matter).

I do this for several reasons, all equally important:

1. The position of President has always been somewhat at-odds with
   our democratic core team structure and purely titular since to
   give the president any real "power" would also destroy the carefully
   balanced dynamic of core, and that would hardly be a desirable outcome.

   The reason the position of "President" was originally created at all
   was to give ISVs and other corporate contacts a more official-sounding
   person to talk to, and while this has been valuable to a certain extent
   I don't think that it's quite proven useful enough to justify the
   further existance of the position.  As it is, it only creates the
   illusion of a "super core member", which the president is not, and
   creates false expectations of authority.

2. The president is generally assumed to be talking for FreeBSD at all times,
   depriving the wearer of that particular thorny crown of the right
   to voice strong opinions or otherwise be outspoken without damaging
   the reputation of the project.  I'm not a punch-pulling kind of guy
   (as you no-doubt already guessed) and I almost certainly never will be,
   so it's time for me to have my own voice back and be able to talk to
   people without it being taken as implicit that I'm somehow speaking
   for all of core.  If being "presidential" also means constantly
   turning the other cheek then I'll never be presidential enough and it's 
   just not an adjustment I care to make (I'm not that kind of person) so
   I should step down from that responsibility.

3. Dropping back to core team status will make it easier for me to
   shed additional FreeBSD responsibilities, should I decide that I
   need to do that in the future, and get some semblance of a life
   back.  I've been doing this for 4 years now and I'm tired.  Just how
   tired I will need to evaluate before making any further decisions, but at
   least the burden of this artificial position will no longer be mine.
   It will, in fact, be no ones' and I think this is a vast improvement.

In discussions with David and John, it was also expressed that the
position was never really that popular with the core team and that
my stepping down should coincide with the complete elimination of
an unnecessary and somewhat flawed position, and so it will be.

So, as of now the FreeBSD Project now longer has a President.  It is
run purely by the core team, as it always was in truth, and now
I'm just the PR guy, release engineer and plain old run-of-the-mill
core team member.  As if that wasn't enough. :-)

					Jordan

From owner-freebsd-hackers  Wed Feb  5 20:54:18 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA06903
          for hackers-outgoing; Wed, 5 Feb 1997 20:54:18 -0800 (PST)
Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA06893;
          Wed, 5 Feb 1997 20:54:15 -0800 (PST)
Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id PAA00702; Thu, 6 Feb 1997 15:23:45 +1030 (CST)
From: Michael Smith <msmith@atrad.adelaide.edu.au>
Message-Id: <199702060453.PAA00702@genesis.atrad.adelaide.edu.au>
Subject: Re: Contigious (spelling?) allocation in kernel
In-Reply-To: <XFMail.970205205354.Shimon@i-Connect.Net> from Simon Shapiro at "Feb 5, 97 07:33:54 pm"
To: Shimon@i-Connect.Net (Simon Shapiro)
Date: Thu, 6 Feb 1997 15:23:45 +1030 (CST)
Cc: freebsd-scsi@freebsd.org, freebsd-hackers@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Simon Shapiro stands accused of saying:
> I need to allocate a contigious (one piece :-) block of memory for a DMA
> scatter/gather list.  The HBA knows how to do scatter gather, but wants a
> single pointer to a single block of memory that hoslds the entire list.

That's a bit icky 8)

> The SG structure is very plain, 32bits for length and 32bits for physical
> address; 8 bytes.  The thing is capable of up to 8192 entries, which give
> us a possible list of 64KB per request list.

You might want to check on the s/g limit for block I/O for FreeBSD; it's
quite possible that something like that is far beyond anything that
it's likely to do.  In most cases, I/O is likely to be in page-sized
(4K) chunks, with a limit of 64K (MAXPHYS).

You'd have to ask Bruce or possibly Justin about that; I don't know where
to look to confirm such a limit.

> As each HBA can have up to 256 concurrent requests, with who knows how
> many more in the driver's queue, the list can grow quite impressively.
> Since most requests are smaller, it seems very wasteful to allocate all
> this memory upfront.  So malloc is in order, but what are the options?

I'd start with a small pool of permanently-allocated (get them at
driver startup time) S/G lists of some empirically determined
"adequate" size.  Keep enough of these around so that you can cover
the maximum number of concurrent outstanding transactions (or possibly
just grow your pool as required).  Use the BSD queue macros to
efficiently manage your buffer lists.  If you get a request bigger
than will fit in your "normal" S/G block, allocate one temporarily,
and throw it away when you're done.

As far as actually allocating the suckers goes, contigmalloc() is
probably what you're after; call it contigmalloc(size, M_DEVBUF,
M_NOWAIT, low, high, align), where low and high are the lowest and
highest legal physical addresses, and align is the alignment size for
the structure.  It sounds like you're talking to a PCI device, so 0,
ULONG_MAX and sizeof(u_long) respectively should do the trick.

> Simon

-- 
]] Mike Smith, Software Engineer        msmith@gsoft.com.au             [[
]] Genesis Software                     genesis@gsoft.com.au            [[
]] High-speed data acquisition and      (GSM mobile)     0411-222-496   [[
]] realtime instrument control.         (ph)          +61-8-8267-3493   [[
]] Unix hardware collector.             "Where are your PEZ?" The Tick  [[

From owner-freebsd-hackers  Wed Feb  5 21:09:00 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA08030
          for hackers-outgoing; Wed, 5 Feb 1997 21:09:00 -0800 (PST)
Received: from whale.gu.kiev.ua (proxy.gu.kiev.ua [194.93.190.4])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA08016
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 21:08:53 -0800 (PST)
Received: from creator.gu.kiev.ua (stesin@creator.gu.kiev.ua [194.93.190.3]) by whale.gu.kiev.ua (8.8.5/8.7.3) with SMTP id HAA62926; Thu, 6 Feb 1997 07:08:10 +0200
Date: Thu, 6 Feb 1997 07:08:09 +0200 (EET)
From: Andrew Stesin <stesin@gu.net>
X-Sender: stesin@creator.gu.kiev.ua
To: Michael Smith <msmith@atrad.adelaide.edu.au>
cc: Amancio Hasty <hasty@rah.star-gate.com>, mark@quickweb.com,
        hackers@freebsd.org
Subject: Re: Samba survey
In-Reply-To: <199702060108.LAA28587@genesis.atrad.adelaide.edu.au>
Message-ID: <Pine.BSI.3.95.970206070521.12919M-100000@creator.gu.kiev.ua>
X-NCC-RegID: ua.gu
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


People,

I'm sure I'm missing something, but... Isn't it sysinstall
(Post-Install system config menu) who offers you an option
of configuring Samba? I used it successfully several times.

> Amancio Hasty stands accused of saying:
> > Is there a configuration tool which aids a new user like me to setup 
> > samba?
> 
> Not AFAIK.

--
		Best,
			Andrew Stesin

		nic-hdl: ST73-RIPE


From owner-freebsd-hackers  Wed Feb  5 21:12:16 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA08546
          for hackers-outgoing; Wed, 5 Feb 1997 21:12:16 -0800 (PST)
Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA08524;
          Wed, 5 Feb 1997 21:12:09 -0800 (PST)
Received: (from root@localhost) by dyson.iquest.net (8.8.4/8.6.9) id AAA10010; Thu, 6 Feb 1997 00:12:02 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199702060512.AAA10010@dyson.iquest.net>
Subject: Re: Contigious (spelling?) allocation in kernel
To: Shimon@i-Connect.Net (Simon Shapiro)
Date: Thu, 6 Feb 1997 00:12:02 -0500 (EST)
Cc: freebsd-scsi@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG
In-Reply-To: <XFMail.970205205354.Shimon@i-Connect.Net> from "Simon Shapiro" at Feb 5, 97 07:33:54 pm
X-Mailer: ELM [version 2.4 PL24 ME8]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Take a look at contigmalloc() or vm_page_alloc_contig()
as defined in /sys/vm/vm_page.c.  These are almost
guaranteed NOT to work after the system is fully up.

John

From owner-freebsd-hackers  Wed Feb  5 21:20:43 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA09881
          for hackers-outgoing; Wed, 5 Feb 1997 21:20:43 -0800 (PST)
Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id VAA09865
          for <freebsd-hackers@freefall.FreeBSD.org>; Wed, 5 Feb 1997 21:20:37 -0800 (PST)
Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02)
	id AA03606; Thu, 6 Feb 1997 00:20:05 -0500
Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Thu,  6 Feb 1997 00:20 EST
Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id XAA03409 for <freebsd-hackers@freefall.cdrom.com>; Wed, 5 Feb 1997 23:53:00 -0500 (EST)
Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id XAA26409 for freebsd-hackers@freefall.cdrom.com; Wed, 5 Feb 1997 23:57:32 -0500 (EST)
Date: Wed, 5 Feb 1997 23:57:32 -0500 (EST)
From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
Message-Id: <199702060457.XAA26409@lakes.water.net>
To: ponds!freefall.cdrom.com!freebsd-hackers
Subject: Build an install floppy for 2.1.6???
Content-Type: text
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


Ok -

 I had put together how to do this in 2.1.0; but I just thought that 
my "dup alloc" panic still occurs in 2.1.6 (which I have installed 
on my primary machine.) Perhaps, if I can fix the problem there (or 
at least get some nice diagnostics with some kernel printf()s); it 
would go a long way toward getting it done in 2.2.

 Can just an install floppy be made from the makefiles, or do you 
have make an entire release???

	- Dave Rivers -


From owner-freebsd-hackers  Wed Feb  5 21:20:45 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA09892
          for hackers-outgoing; Wed, 5 Feb 1997 21:20:45 -0800 (PST)
Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id VAA09875
          for <freebsd-hackers@freefall.FreeBSD.org>; Wed, 5 Feb 1997 21:20:41 -0800 (PST)
Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02)
	id AA03716; Thu, 6 Feb 1997 00:20:09 -0500
Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Thu,  6 Feb 1997 00:20 EST
Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id AAA03508; Thu, 6 Feb 1997 00:03:04 -0500 (EST)
Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id AAA26461; Thu, 6 Feb 1997 00:07:36 -0500 (EST)
Date: Thu, 6 Feb 1997 00:07:36 -0500 (EST)
From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
Message-Id: <199702060507.AAA26461@lakes.water.net>
To: ponds!atrad.adelaide.edu.au!msmith
Subject: Re: What happened to the splash screen?
Cc: ponds!csv.warwick.ac.uk!csubl, ponds!freefall.cdrom.com!freebsd-hackers,
        ponds!ravenock.cybercity.dk!sos
Content-Type: text
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Mike Smith writes:

> Thomas David Rivers stands accused of saying:
> > > 
> > > There was also a problem with VGA font corruption; did that get fixed
> > > Soren?  The last difficulty is that during device probes, interrupts are
> > > turned off so you can't hotkey between the splash and the probe display.
> > 
> >  I'm just curious; if this were to get "put in" - would it do
> > something meaningful on monochrome (i.e. Hercules compatible) displays?
> 
> What's "meaningful"?  

 Very good question; actually...  Terry, you wanna field that one? :-) :-)

>                       With a single VGA bitmap in the kernel, the
> bloat for the splash screen runs to about 70K.  Short of having a seperate
> monochrome image, or a F/S dither, it'll just ignore the splash and probe
> as normal.

 Seems fine to me...  I just wanted to make sure we didn't loose
support for the monochrome, or serial consoles just to get some color
up there - but that's covered.  I wouldn't bother with a separate
image, or dithering the other one down to black-and-white.  Usually when
you have one of these it's because your not too interested in such issues.

> 
> > 	- Dave R. -
> 
> -- 
> ]] Mike Smith, Software Engineer        msmith@gsoft.com.au             [[

	- Dave R. -

From owner-freebsd-hackers  Wed Feb  5 21:20:51 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA09920
          for hackers-outgoing; Wed, 5 Feb 1997 21:20:51 -0800 (PST)
Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id VAA09893
          for <hackers@FreeBSD.ORG>; Wed, 5 Feb 1997 21:20:45 -0800 (PST)
Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02)
	id AA03630; Thu, 6 Feb 1997 00:20:06 -0500
Received: from genesis.atrad.adelaide.edu.au by dg-rtp.dg.com.rtp.dg.com; Thu,  6 Feb 1997 00:20 EST
Received: from dg-rtp.UUCP (uucp@localhost) by ponds.water.net (8.8.3/8.7.3) with UUCP id XAA03489 for FreeBSD.ORG!hackers; Wed, 5 Feb 1997 23:57:41 -0500 (EST)
Received: from genesis.atrad.adelaide.edu.au by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02)
	id AA00841; Wed, 5 Feb 1997 23:56:48 -0500
Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id PAA00727; Thu, 6 Feb 1997 15:26:45 +1030 (CST)
From: Michael Smith <msmith@atrad.adelaide.edu.au>
Message-Id: <199702060456.PAA00727@genesis.atrad.adelaide.edu.au>
Subject: Re: What happened to the splash screen?
In-Reply-To: <199702060443.XAA26253@lakes.water.net> from Thomas David Rivers at "Feb 5, 97 11:43:05 pm"
To: ponds!ponds!rivers (Thomas David Rivers)
Date: Thu, 6 Feb 1997 15:26:44 +1030 (CST)
Cc: ponds!atrad.adelaide.edu.au!msmith, ponds!ponds!ravenock.cybercity.dk!sos,
        ponds!ponds!csv.warwick.ac.uk!csubl, ponds!ponds!FreeBSD.ORG!hackers
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Thomas David Rivers stands accused of saying:
> > 
> > There was also a problem with VGA font corruption; did that get fixed
> > Soren?  The last difficulty is that during device probes, interrupts are
> > turned off so you can't hotkey between the splash and the probe display.
> 
>  I'm just curious; if this were to get "put in" - would it do
> something meaningful on monochrome (i.e. Hercules compatible) displays?

What's "meaningful"?  With a single VGA bitmap in the kernel, the
bloat for the splash screen runs to about 70K.  Short of having a seperate
monochrome image, or a F/S dither, it'll just ignore the splash and probe
as normal.

> 	- Dave R. -

-- 
]] Mike Smith, Software Engineer        msmith@gsoft.com.au             [[
]] Genesis Software                     genesis@gsoft.com.au            [[
]] High-speed data acquisition and      (GSM mobile)     0411-222-496   [[
]] realtime instrument control.         (ph)          +61-8-8267-3493   [[
]] Unix hardware collector.             "Where are your PEZ?" The Tick  [[

From owner-freebsd-hackers  Wed Feb  5 21:21:01 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA09963
          for hackers-outgoing; Wed, 5 Feb 1997 21:21:01 -0800 (PST)
Received: from whale.gu.kiev.ua (proxy.gu.kiev.ua [194.93.190.4])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA09907;
          Wed, 5 Feb 1997 21:20:49 -0800 (PST)
Received: from creator.gu.kiev.ua (stesin@creator.gu.kiev.ua [194.93.190.3]) by whale.gu.kiev.ua (8.8.5/8.7.3) with SMTP id HAA34766; Thu, 6 Feb 1997 07:20:42 +0200
Date: Thu, 6 Feb 1997 07:20:42 +0200 (EET)
From: Andrew Stesin <stesin@gu.net>
X-Sender: stesin@creator.gu.kiev.ua
To: questions@freebsd.org, hackers@freebsd.org
Subject: Strange(!!) sio callin/callout behaviour in 2.1.6
Message-ID: <Pine.BSI.3.95.970206070913.12919N-100000@creator.gu.kiev.ua>
X-NCC-RegID: ua.gu
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Hello,

sorry if I'm way too outdated with this, but here the
question  goes... the system is FreeBSD 2.1.6-RELEASE,
installed back in mid-November. sio devices are: com1, com2,
and a MOXA 4-port multiport board.

I observe the following misbehaviours with regard to sio
driver:

1. pppd never seems to receive/handle a SIGHUP from modem.

2. Callout devices behavior screwed... example: say I take the sio
   unit 5, getty active on ttyd5, TR LED on modem is on, then:

   # stty -a -f /dev/ttyd5
   [...a screen of stty's output goes here, Ok...]
   # stty -a -f /dev/cuaa5
   stty: /dev/cuaa5: Device busy
   # cu -l /dev/cuaa5 -s 57600
   cu: /dev/cuaa5: Line in use
   #

   Is it just me so stupid or tired, or a problem _do_ exist
   with either software or hardware?  Would anyone be so keen
   to suggest a fix?  (The above makes the system virtually
   unusable for the purpose it was installed for...)

Thanks!


--
		Best,
			Andrew Stesin

		nic-hdl: ST73-RIPE


From owner-freebsd-hackers  Wed Feb  5 21:33:59 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA11830
          for hackers-outgoing; Wed, 5 Feb 1997 21:33:59 -0800 (PST)
Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA11824;
          Wed, 5 Feb 1997 21:33:54 -0800 (PST)
Received: from narnia (localhost [127.0.0.1]) by narnia.plutotech.com (8.8.5/8.7.3) with ESMTP id VAA00624; Wed, 5 Feb 1997 21:33:58 -0800 (PST)
Message-Id: <199702060533.VAA00624@narnia.plutotech.com>
To: Simon Shapiro <Shimon@i-Connect.Net>
cc: freebsd-scsi@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG
Subject: Re: Contigious (spelling?) allocation in kernel 
In-reply-to: Your message of "Wed, 05 Feb 1997 19:33:54 PST."
             <XFMail.970205205354.Shimon@i-Connect.Net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 05 Feb 1997 21:33:57 -0800
From: "Justin T. Gibbs" <gibbs@narnia.plutotech.com>
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>I need to allocate a contigious (one piece :-) block of memory for a DMA
>scatter/gather list.

If it is more than a page, you must use contigmalloc.  contigmalloc may
only be used close to boot time if you want to ensure it will work.

>The HBA knows how to do scatter gather, but wants a
>single pointer to a single block of memory that holds the entire list.
>The SG structure is very plain, 32bits for length and 32bits for physical
>address; 8 bytes.  The thing is capable of up to 8192 entries, which give
>us a possible list of 64KB per request list.

You really think you're going to ever transfer a full 32MB of data in a single
transaction?  Even if you were, you'd have to do something special to the
kernel since it currently only generates requests of at most 64k (its a silly
restriction and it should die a horrible death).  Assuming you did have a way
to stuff 32MB through all of the layers, you'd probably be better off chopping
that I/O into smaller chunks so as to reduce the amount of SG space you must
allocate.  At anything over 8k, the transaction overhead starts to become an
increasingly small percentage of your I/O time, so dropping even down as low as
1MB per transaction may better utilize your resources.

>As each HBA can have up to 256 concurrent requests, with who knows how
>many more in the driver's queue, the list can grow quite impressively.
>Since most requests are smaller, it seems very wasteful to allocate all
>this memory upfront.  So malloc is in order, but what are the options?

You don't want to continuously malloc your SG list.  This will kill your
performance.  If it is acceptable for the system to run with all 256
requests active at once, you have to be able to deal with all of the requests
being allocated anyway, so you might as well pool them.

>Thanx,
>
>Simon

--
Justin T. Gibbs
===========================================
  FreeBSD: Turning PCs into workstations
===========================================



From owner-freebsd-hackers  Wed Feb  5 21:41:11 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA12448
          for hackers-outgoing; Wed, 5 Feb 1997 21:41:11 -0800 (PST)
Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA12429
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 21:41:06 -0800 (PST)
Received: from localhost (mark@localhost) by vinyl.quickweb.com (8.7.5/8.6.12) with SMTP id AAA00554; Thu, 6 Feb 1997 00:41:18 -0500 (EST)
Date: Thu, 6 Feb 1997 00:41:18 -0500 (EST)
From: Mark Mayo <mark@quickweb.com>
To: Andrew Stesin <stesin@gu.net>
cc: Michael Smith <msmith@atrad.adelaide.edu.au>,
        Amancio Hasty <hasty@rah.star-gate.com>, hackers@freebsd.org
Subject: Re: Samba survey
In-Reply-To: <Pine.BSI.3.95.970206070521.12919M-100000@creator.gu.kiev.ua>
Message-ID: <Pine.BSF.3.94.970206003944.476B-100000@vinyl.quickweb.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Thu, 6 Feb 1997, Andrew Stesin wrote:

> 
> People,
> 
> I'm sure I'm missing something, but... Isn't it sysinstall
> (Post-Install system config menu) who offers you an option
> of configuring Samba? I used it successfully several times.

Yip. Me too. In any case, the default config that comes with the samba
package (or port, or tar from canberra) is very simple, well documented,
and easy to understand. It's really a no-brainer to run Samba - a fact
that has certainly helped boost its popularity..

Mark

> 
> > Amancio Hasty stands accused of saying:
> > > Is there a configuration tool which aids a new user like me to setup 
> > > samba?
> > 
> > Not AFAIK.
> 
> --
> 		Best,
> 			Andrew Stesin
> 
> 		nic-hdl: ST73-RIPE
> 

----------------------------------------------------------------------------
 Mark Mayo		  				mark@quickweb.com       
 RingZero Comp.  	  		   http://vinyl.quickweb.com/mark 
----------------------------------------------------------------------------
	"I prefer tongue-tied knowledge to ignorant loquacity."
						Cicero (106-43 B.C.)


From owner-freebsd-hackers  Wed Feb  5 22:15:30 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id WAA18690
          for hackers-outgoing; Wed, 5 Feb 1997 22:15:30 -0800 (PST)
Received: from logues.rhn.orst.edu (logues.RHN.ORST.EDU [128.193.139.116])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA18650;
          Wed, 5 Feb 1997 22:15:24 -0800 (PST)
Received: from localhost (stevel@localhost)
          by logues.rhn.orst.edu (8.8.4/8.8.4) with SMTP
	  id WAA02515; Wed, 5 Feb 1997 22:15:21 -0800 (PST)
Date: Wed, 5 Feb 1997 22:15:21 -0800 (PST)
From: stevel <stevel@logues.rhn.orst.edu>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: announce@freebsd.org, hackers@freebsd.org
Subject: Re: My resignation as president of the FreeBSD Project.
In-Reply-To: <199702060453.UAA27279@time.cdrom.com>
Message-ID: <Pine.BSF.3.95.970205221316.2490A-100000@logues.rhn.orst.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk



On Wed, 5 Feb 1997, Jordan K. Hubbard wrote:

> This short notice is just to announce my resignation as President
> of the FreeBSD Project, effective immediately, coinciding with the
> elimination of that position.

I think this is a wise choice, and will lead to much simpler relations,
less stress, and most of all less confusion.

Just my 2 cents worth....

-STEVEl



From owner-freebsd-hackers  Wed Feb  5 22:22:24 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id WAA21742
          for hackers-outgoing; Wed, 5 Feb 1997 22:22:24 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA21688
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 22:22:18 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id RAA09563; Thu, 6 Feb 1997 17:16:25 +1100
Date: Thu, 6 Feb 1997 17:16:25 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199702060616.RAA09563@godzilla.zeta.org.au>
To: durham@w2xo.pgh.pa.us, hackers@freebsd.org
Subject: Re: DOS partition trouble
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>Twice now, I have removed a DOS partition
>from a disk with both DOS and FreeBSD
>partitions and been unable to boot FreeBSD.
>...
>I had tried running the partition editor when I had no DOS
>partition and it gave all indications of sucessfully writing
>out the boot block, but would not boot until I remade the
>DOS partition. Trying to mount the root directory from the MFS
>on the boot floppy gave a "bad super block" error.

For SCSI disks with at least ncr controllers, this could be caused
a DOS partition that ends on a cylinder boundary and FreeBSD partition
that doesn't.  When you remove the DOS partition, the controller's BIOS
will have problems determining the disk geometry.

Bruce

From owner-freebsd-hackers  Wed Feb  5 22:45:12 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id WAA06707
          for hackers-outgoing; Wed, 5 Feb 1997 22:45:12 -0800 (PST)
Received: from dawn.ww.net (root@dawn.ww.net [193.124.73.50])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA06509
          for <freebsd-hackers@freebsd.org>; Wed, 5 Feb 1997 22:44:50 -0800 (PST)
Received: (from alexis@localhost)
	by dawn.ww.net (8.7.5/alexis 2.5)  id JAA03430; Thu, 6 Feb 1997 09:44:08 +0300 (MSK)
Message-Id: <199702060644.JAA03430@dawn.ww.net>
Subject: Re: sio11 64 events for device without tp related problem?
To: joerg_wunsch@uriah.heep.sax.de
Date: Thu, 6 Feb 1997 09:44:08 +0300 (MSK)
From: Alexis Yushin <alexis@dawn.ww.net>
Cc: alexis@ww.net, freebsd-hackers@freebsd.org
In-Reply-To: <Mutt.19970205234703.j@uriah.heep.sax.de> from J Wunsch at "Feb 5, 97 11:47:03 pm"
Reply-To: alexis@ww.net (Alexis Yushin)
X-Office-Phone: +380 65 2 26.1410
X-Home-Phone: +380 65 2 27.0747
X-NIC-Handle: AY23
X-RIPE-Handle: AY6-RIPE
X-Mailer: ELM [version 2.4ME+ PL17 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Once J Wunsch wrote:
>> two messages 'sio11 64 events for device without tp' is generated.
>
>I think that's basically stray interrupts being assigned to the
>sio driver.
>
>Does your sio11 perchance use irq 7?

	Well, it is master port for 8 ports multiport and no, it uses
irq 5. Could you elaborate and explain what tp and entire message
means?
								alexis
-- 
		It's all the same, only the names will change

From owner-freebsd-hackers  Wed Feb  5 22:52:15 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id WAA10402
          for hackers-outgoing; Wed, 5 Feb 1997 22:52:15 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA10341;
          Wed, 5 Feb 1997 22:52:09 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id RAA10833; Thu, 6 Feb 1997 17:48:56 +1100
Date: Thu, 6 Feb 1997 17:48:56 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199702060648.RAA10833@godzilla.zeta.org.au>
To: hackers@freebsd.org, questions@freebsd.org, stesin@gu.net
Subject: Re: Strange(!!) sio callin/callout behaviour in 2.1.6
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>I observe the following misbehaviours with regard to sio
>driver:
>
>1. pppd never seems to receive/handle a SIGHUP from modem.

Perhaps the modem never hangs up.

>2. Callout devices behavior screwed... example: say I take the sio
>   unit 5, getty active on ttyd5, TR LED on modem is on, then:
>
>   # stty -a -f /dev/ttyd5
>   [...a screen of stty's output goes here, Ok...]
>   # stty -a -f /dev/cuaa5
>   stty: /dev/cuaa5: Device busy
>   # cu -l /dev/cuaa5 -s 57600
>   cu: /dev/cuaa5: Line in use
>   #

This means that something has /dev/ttyd5 open.  Perhaps getty succeeds
in opening a few microseconds after pppd closes /dev/cuaa5.  getty sleeps
until carrier is present, but no longer, so if the port is shared between
a getty and a dialout program like pppd and the dialout program closes
the dialout port before carrier drops, then the getty will grab the port.
HUPCL on the dialout port and a sufficiently large dtrwait should prevent
this from happening if the modem responds to DTR dropping sufficent quickly.

Bruce

From owner-freebsd-hackers  Wed Feb  5 22:59:45 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id WAA14415
          for hackers-outgoing; Wed, 5 Feb 1997 22:59:45 -0800 (PST)
Received: from relay.nuxi.com (nuxi.ucdavis.edu [128.120.37.176])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA14396;
          Wed, 5 Feb 1997 22:59:41 -0800 (PST)
Received: from dragon.nuxi.com (reqb-061.ucdavis.edu [128.120.254.61]) by relay.nuxi.com (8.8.4/8.6.12) with ESMTP id WAA27282; Wed, 5 Feb 1997 22:59:55 -0800 (PST)
Received: (from obrien@localhost) by dragon.nuxi.com (8.8.4/8.7.3) id WAA21063; Wed, 5 Feb 1997 22:59:28 -0800 (PST)
Message-ID: <19970205225927.LP41225@dragon.nuxi.com>
Date: Wed, 5 Feb 1997 22:59:27 -0800
From: obrien@NUXI.com (David O'Brien)
To: imp@village.org (Warner Losh)
Cc: chuckr@glue.umd.edu (Chuck Robey),
        freebsd-ports@freebsd.org (FreeBSD ports list), hackers@freebsd.org
Subject: Re: conditionally including <sys/param.h>
References: <19970205112604.AI13761@dragon.nuxi.com> <19970205003343.YB13323@dragon.nuxi.com> <Pine.OSF.3.95q.970205081326.9802A-100000@gilligan.eng.umd.edu> <E0vsJWO-0002dq-00@rover.village.org>
X-Mailer: Mutt 0.59-PL19
Mime-Version: 1.0
Organization: The NUXI *BSD group
X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3  90 76 5D 69 58 D9 98 7A
X-Pgp-Keyid: 34F9F9D5
In-Reply-To: <E0vsJWO-0002dq-00@rover.village.org>; from Warner Losh on Feb 5, 1997 19:25:07 -0700
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Warner Losh writes:
> : using these macros.  They seem to be the only true way of dealing with
> : this.  If anyone knows who wrote those words, I'd love to start a dialog
> : with them.
> 
> I think that the BSD macro method works well enough, and with the
> slight tweaks that we've talked about here it works almost perfectly.

Just to make sure we are agreeing on the same thing, can you restate the
tweaks?

-- 
-- David	(obrien@NUXI.com  -or-  obrien@FreeBSD.org)

From owner-freebsd-hackers  Wed Feb  5 23:05:08 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA17147
          for hackers-outgoing; Wed, 5 Feb 1997 23:05:08 -0800 (PST)
Received: from superior.truenorth.org (ppp012-sm2.sirius.com [205.134.231.12])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA17128;
          Wed, 5 Feb 1997 23:05:00 -0800 (PST)
Received: (from jgrosch@localhost) by superior.truenorth.org (8.7.5/8.7.3) id XAA20962; Wed, 5 Feb 1997 23:04:47 -0800 (PST)
From: Josef Grosch <jgrosch@superior.truenorth.org>
Message-Id: <199702060704.XAA20962@superior.truenorth.org>
Subject: Re: My resignation as president of the FreeBSD Project.
In-Reply-To: <199702060453.UAA27279@time.cdrom.com> from "Jordan K. Hubbard" at "Feb 5, 97 08:53:38 pm"
To: jkh@time.cdrom.com (Jordan K. Hubbard)
Date: Wed, 5 Feb 1997 23:04:46 -0800 (PST)
Cc: announce@freebsd.org, hackers@freebsd.org
Reply-To: jgrosch@sirius.com
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>This short notice is just to announce my resignation as President
>of the FreeBSD Project, effective immediately, coinciding with the
>elimination of that position.
>

[ DELETED ]


Very sorry to hear you are stepping down but considering the last couple of
days the image of straw comes to mind. :-(

Three cheers for an outstanding job well done.


Josef

-- 
Josef Grosch       | Laugh while you can, monkey boy ! |    FreeBSD 2.1.6
jgrosch@sirius.com |          - John Warfin -          | UNIX for the masses

From owner-freebsd-hackers  Wed Feb  5 23:26:12 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA24032
          for hackers-outgoing; Wed, 5 Feb 1997 23:26:12 -0800 (PST)
Received: from meter.eng.uci.edu (root@meter.eng.uci.edu [128.200.85.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA24011
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 23:26:09 -0800 (PST)
Received: from newport.ece.uci.edu by meter.eng.uci.edu (8.8.5) id XAA02718; Wed, 5 Feb 1997 23:26:03 -0800 (PST)
Received: from localhost by newport.ece.uci.edu (8.8.5) id XAA22613; Wed, 5 Feb 1997 23:26:02 -0800 (PST)
Message-Id: <199702060726.XAA22613@newport.ece.uci.edu>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: hackers@freebsd.org
Subject: Re: My resignation as president of the FreeBSD Project. 
In-reply-to: Your message of "Wed, 05 Feb 1997 20:53:38 PST."
             <199702060453.UAA27279@time.cdrom.com> 
Date: Wed, 05 Feb 1997 23:26:01 -0800
From: Steven Wallace <swallace@ece.uci.edu>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


So what type of retirement benefits does a FreeBSD president receive?
Are they similar to a U.S. president?

Are you still suppose to be called "Mr. President" even though you
are really an X-"Mr. President"?


From owner-freebsd-hackers  Wed Feb  5 23:30:37 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA25838
          for hackers-outgoing; Wed, 5 Feb 1997 23:30:37 -0800 (PST)
Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA25814
          for <freebsd-hackers@freebsd.org>; Wed, 5 Feb 1997 23:30:33 -0800 (PST)
Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id RAA01956; Thu, 6 Feb 1997 17:59:16 +1030 (CST)
From: Michael Smith <msmith@atrad.adelaide.edu.au>
Message-Id: <199702060729.RAA01956@genesis.atrad.adelaide.edu.au>
Subject: Re: sio11 64 events for device without tp related problem?
In-Reply-To: <199702060644.JAA03430@dawn.ww.net> from Alexis Yushin at "Feb 6, 97 09:44:08 am"
To: alexis@ww.net
Date: Thu, 6 Feb 1997 17:59:15 +1030 (CST)
Cc: joerg_wunsch@uriah.heep.sax.de, alexis@ww.net, freebsd-hackers@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Alexis Yushin stands accused of saying:
> Once J Wunsch wrote:
> >> two messages 'sio11 64 events for device without tp' is generated.
> >
> >I think that's basically stray interrupts being assigned to the
> >sio driver.
> >
> >Does your sio11 perchance use irq 7?
> 
> 	Well, it is master port for 8 ports multiport and no, it uses
> irq 5. Could you elaborate and explain what tp and entire message
> means?

It means that there were 64 events (usually input interrupts) for a
port that's not open.  It usually means that your hardware is
misbehaving.

-- 
]] Mike Smith, Software Engineer        msmith@gsoft.com.au             [[
]] Genesis Software                     genesis@gsoft.com.au            [[
]] High-speed data acquisition and      (GSM mobile)     0411-222-496   [[
]] realtime instrument control.         (ph)          +61-8-8267-3493   [[
]] Unix hardware collector.             "Where are your PEZ?" The Tick  [[

From owner-freebsd-hackers  Wed Feb  5 23:43:29 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA00595
          for hackers-outgoing; Wed, 5 Feb 1997 23:43:29 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA00583
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 23:43:26 -0800 (PST)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id XAA28491; Wed, 5 Feb 1997 23:43:22 -0800 (PST)
To: Steven Wallace <swallace@ece.uci.edu>
cc: hackers@freebsd.org
Subject: Re: My resignation as president of the FreeBSD Project. 
In-reply-to: Your message of "Wed, 05 Feb 1997 23:26:01 PST."
             <199702060726.XAA22613@newport.ece.uci.edu> 
Date: Wed, 05 Feb 1997 23:43:22 -0800
Message-ID: <28487.855215002@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> So what type of retirement benefits does a FreeBSD president receive?
> Are they similar to a U.S. president?

Not really.  I get free news posting privileges and ops on #freebsd
for an additional 6 months so that I can have some last-minute fun
kicking the Linux weenies off, but that's about it.  No secret service
detail, no six-figure deal for my memoirs, no airports or freeway
bridges named after me (there was talk of the Fresno Dept. of Public
Works naming "the Jordan K. Hubbard memorial outflow relief valve #16"
after me, but that fell through when I lost out to Willard Scott in
the final vote).  It's kind of a let-down, really.  No farewell cake,
not even a bran muffin with a candle in it.  Oh well.  Life goes on.

> Are you still suppose to be called "Mr. President" even though you
> are really an X-"Mr. President"?

Actually, at this point my name changes to an obscure glyph that can
only be displayed in the KOI-8 font.  You can just refer to me as "the
core team member formerly known as the president" if it's easier.

				Jordan

From owner-freebsd-hackers  Wed Feb  5 23:49:08 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA02573
          for hackers-outgoing; Wed, 5 Feb 1997 23:49:08 -0800 (PST)
Received: from narcissus.ml.org (root@brosenga.Pitzer.edu [134.173.120.201])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA02478
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 23:48:52 -0800 (PST)
Received: (from ben@localhost) by narcissus.ml.org (8.7.5/8.7.3) id XAA08339; Wed, 5 Feb 1997 23:48:53 -0800 (PST)
Date: Wed, 5 Feb 1997 23:48:53 -0800 (PST)
From: Stranger Bone <ben@narcissus.ml.org>
To: Steven Wallace <swallace@ece.uci.edu>
cc: "Jordan K. Hubbard" <jkh@time.cdrom.com>, hackers@freebsd.org
Subject: Re: My resignation as president of the FreeBSD Project. 
In-Reply-To: <199702060726.XAA22613@newport.ece.uci.edu>
Message-ID: <Pine.BSF.3.91.970205234826.5408D-100000@narcissus.ml.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Wed, 5 Feb 1997, Steven Wallace wrote:

> 
> So what type of retirement benefits does a FreeBSD president receive?
> Are they similar to a U.S. president?
> 
> Are you still suppose to be called "Mr. President" even though you
> are really an X-"Mr. President"?
> 

Do you get Secret-Service daemons following you around, slide rules and 
lint(1) at the ready? 



 Ben

"You have your mind on computers, it seems."


From owner-freebsd-hackers  Wed Feb  5 23:53:10 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA05665
          for hackers-outgoing; Wed, 5 Feb 1997 23:53:10 -0800 (PST)
Received: from whale.gu.kiev.ua (whale.gu.net [194.93.190.4])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA05579
          for <freebsd-hackers@FreeBSD.org>; Wed, 5 Feb 1997 23:52:49 -0800 (PST)
Received: from creator.gu.kiev.ua (stesin@creator.gu.kiev.ua [194.93.190.3]) by whale.gu.kiev.ua (8.8.5/8.7.3) with SMTP id JAA22526; Thu, 6 Feb 1997 09:51:46 +0200
Date: Thu, 6 Feb 1997 09:51:45 +0200 (EET)
From: Andrew Stesin <stesin@gu.net>
X-Sender: stesin@creator.gu.kiev.ua
To: Alexis Yushin <alexis@ww.net>
cc: joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.org
Subject: Re: sio11 64 events for device without tp related problem?
In-Reply-To: <199702060644.JAA03430@dawn.ww.net>
Message-ID: <Pine.BSI.3.95.970206095122.24481B-100000@creator.gu.kiev.ua>
X-NCC-RegID: ua.gu
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk


On Thu, 6 Feb 1997, Alexis Yushin wrote:

> >Does your sio11 perchance use irq 7?
> 
> 	Well, it is master port for 8 ports multiport and no, it uses
> irq 5. Could you elaborate and explain what tp and entire message
> means?

	ISA bus "overload"?

--
		Best,
			Andrew Stesin

		nic-hdl: ST73-RIPE


From owner-freebsd-hackers  Thu Feb  6 00:16:29 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id AAA10187
          for hackers-outgoing; Thu, 6 Feb 1997 00:16:29 -0800 (PST)
Received: from whale.gu.kiev.ua (whale.gu.net [194.93.190.4])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA10129;
          Thu, 6 Feb 1997 00:16:14 -0800 (PST)
Received: from creator.gu.kiev.ua (stesin@creator.gu.kiev.ua [194.93.190.3]) by whale.gu.kiev.ua (8.8.5/8.7.3) with SMTP id KAA36544; Thu, 6 Feb 1997 10:12:19 +0200
Date: Thu, 6 Feb 1997 10:12:18 +0200 (EET)
From: Andrew Stesin <stesin@gu.net>
X-Sender: stesin@creator.gu.kiev.ua
Reply-To: Andrew Stesin <stesin@gu.net>
To: Bruce Evans <bde@zeta.org.au>
cc: hackers@freebsd.org, questions@freebsd.org
Subject: Re: Strange(!!) sio callin/callout behaviour in 2.1.6
In-Reply-To: <199702060648.RAA10833@godzilla.zeta.org.au>
Message-ID: <Pine.BSI.3.95.970206092457.24481A-100000@creator.gu.kiev.ua>
X-NCC-RegID: ua.gu
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hello Bruce,

On Thu, 6 Feb 1997, Bruce Evans wrote:

> >1. pppd never seems to receive/handle a SIGHUP from modem.
> 
> Perhaps the modem never hangs up.

	Can't be an issue. Tried several modems, all with
	"DCD normal" option turned on (&C1). Other modem's
	settings also seem to be appropriate.

> This means that something has /dev/ttyd5 open.  Perhaps getty succeeds
> in opening a few microseconds after pppd closes /dev/cuaa5.

	No pppd in the above example...

	Now after a clean reboot, with a modem but no getty:

# stty -a -f /dev/cuaa1
[... works ...]
# stty -a -f /dev/ttyd1
[... works ...]
# stty -a -f /dev/cuaa1
[... works ...]
# stty -a -f /dev/ttyd1
[... works ...]

	Ok. Now adding getty with :hc: in the gettytab entry for
	this line:

# vi /etc/ttys
[... off -> on ...]
# kill -1 1
[... DTR LED now is "on" at the modem...]
# stty -a -f /dev/cuaa1
[... works ...]
# stty -a -f /dev/ttyd1
[... works ...]
# stty -a -f /dev/cuaa1
stty: /dev/cuaa1: Device busy
[... several attempts within a few minutes, with the same effect ...]
# stty -a -f /dev/ttyd1
[... still works! ...]

	Ok, let's turn getty off back again...

# vi /etc/ttys
[... on->off ...]
# kill -1 1
[... wonder!!! DTR LED on the modem is still on!
     Hey I didn't launch anything but the poor getty!!! ...]
# ps auwx|less
[... thorough investigation of processes -- shows nothing
     neither on ttyd1 nor on cuaa1 ports. =8-?????? ...]
# cu -l /dev/cuaa1 -s 57600
cu: /dev/cuaa1: Line in use
# cu -l /dev/ttyd1  -s 57600
cu: open (/dev/ttyd1): Permission denied
cu:  /dev/ttyd1: Line in use
# id
uid=0(root) gid=0(wheel) [...blah-blah...]

	Ok, powercycle the modem. DTR LED is on back again!
	And still no processes seen...

> getty sleeps until carrier is present,

	Never was in the example above. (BTW: does sio.c pay
	any attention to other modem control lines? DSR i.e.?)

> but no longer, so if the port is shared between
> a getty and a dialout program like pppd

	Plain stty -a -f ... no dialout.

> and the dialout program closes
> the dialout port before carrier drops, then the getty will grab the port.
> HUPCL on the dialout port

	Present

> and a sufficiently large dtrwait should prevent

	dtrwait is 400

> this from happening if the modem responds to DTR dropping sufficent quickly.

	yes it does (this is Motorola Premier 33.6, nice beast)

> 
> Bruce
> 

--
		Best,
			Andrew Stesin

		nic-hdl: ST73-RIPE



From owner-freebsd-hackers  Thu Feb  6 00:18:40 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id AAA10577
          for hackers-outgoing; Thu, 6 Feb 1997 00:18:40 -0800 (PST)
Received: from earth.infinetconsulting.com (earth.infinetconsulting.com [207.23.43.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA10565
          for <freebsd-hackers@freebsd.org>; Thu, 6 Feb 1997 00:18:37 -0800 (PST)
Received: (from lenc@localhost) by earth.infinetconsulting.com (8.8.3/8.6.12) id AAA26604; Thu, 6 Feb 1997 00:31:03 -0800 (PST)
Date: Thu, 6 Feb 1997 00:31:03 -0800 (PST)
From: Leonard Chua <lenc@earth.infinetconsulting.com>
To: freebsd-hackers@freebsd.org, Matt Thomas <matt@lkg.dec.com>, jc@irbs.com
Subject: SMC EtherPower 10/100 (SMC9332BDT, DEC21140A)
Message-ID: <Pine.BSF.3.91.970206001518.26466B-100000@earth.infinetconsulting.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi all,
   considering the de driver support for the "new" 21140A chip is kinda
   in BETA still, here's a quick report:

   We tested two computers with the abovesaid NICs in an isolated network.
   In between was a 3Com intelligent (non-passive) 100BaseTX hub.

   The OS used was FreeBSD 2.2 with the de patch obtained from 
   ftp://ftp.irbs.com/pub/FreeBSD.

   I used netperf with the default scripts, as well as my own little 
   bandwidth testing program (similar to tcpblast). 
   We acheived a maximum performance of 82Mbits/sec using packet and buffer 
   sizes of 16384bytes. (With various packet and buffer sizes, performance 
   varied quite a bit, as expected).
  
   We'll be upgrading to 100BaseTX soon, so I'll keep everyone updated
   of any problems (cross my fingers). :)

Cheers.
Len.

From owner-freebsd-hackers  Thu Feb  6 00:44:11 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id AAA17739
          for hackers-outgoing; Thu, 6 Feb 1997 00:44:11 -0800 (PST)
Received: from gw-nl1.philips.com (gw-nl1.philips.com [192.68.44.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA17701
          for <freebsd-hackers@freebsd.org>; Thu, 6 Feb 1997 00:44:05 -0800 (PST)
Received: (from nobody@localhost) 
	by gw-nl1.philips.com (8.6.10/8.6.10-0.994n-08Nov95) id JAA29556; Thu, 6 Feb 1997 09:42:36 +0100
Received: from unknown(130.139.36.3) by gw-nl1.philips.com via smap (V1.3+ESMTP) with ESMTP
	id sma029505; Thu Feb  6 09:42:09 1997
Received: from giga.lss.cp.philips.com (giga.lss.cp.philips.com [130.144.199.31]) 
	by smtprelay.nl.cis.philips.com (8.6.10/8.6.10-1.2.1m-970131) with SMTP id JAA14528; Thu, 6 Feb 1997 09:42:07 +0100
Received: by giga.lss.cp.philips.com (8.8.5/1.63)
    id JAA26171; Thu, 6 Feb 1997 09:42:07 +0100 (MET)
From: W.Belgers@nl.cis.philips.com (Walter Belgers)
Message-Id: <199702060842.JAA26171@giga.lss.cp.philips.com>
Subject: Re: NIS/uids
To: terry@lambert.org (Terry Lambert)
Date: Thu, 6 Feb 1997 09:42:07 +0100 (MET)
Cc: freebsd-hackers@freebsd.org
In-Reply-To: <199702052112.OAA15553@phaeton.artisoft.com> from Terry Lambert at "Feb 5, 97 02:12:46 pm"
Organisation: Origin IT Systems Management /Nederland B.V.
X-URL: http://giga.lss.cp.philips.com/cgi-bin/walter.cgi
X-Mailer: ELM [version 2.4ME+ PL19 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Terry Lambert writes:
> > Let's assume I do not trust the uid's coming from the NIS server but I
> > still do want to use NIS (for passwd/homedir/gecos/whatever).
> 
> Then you have the same problem, this time with associating a
> particular password with a particular name.  All you have done is
> trade the association with uid for an association with name.  There
> is nothing the prevents me, as an NIS server, from returning the
> password "frobozz" (encrypted, of course) for every user, regardless
> of their real password.

That's right. But at least you could only become one of the NIS users of
which none is in wheel. I can live with people hacking the NIS server
and getting access to my machine, I won't have people becoming root.

> > Why does FreeBSD give me troubles when I override the uid in the local
> > password file?
> 
> It wasn't a case which was considered to ever be anything someone would
> want to do, I believe.

I have to admit it's not something people will normally do. But I would
expect it to work.

> Mostly because if I compromise the NIS server,
> then I can force you to accept any password for any user/password pair,
> and thereby become any user/id pair, so it doesn't give you the protection
> you are trying to get it to give you.

I have no "+" in my password file, only "+user", so you can only hack
those users, not the users that are only locally in my password file. So
it does give the desired protection.

> PS: Do not start a line with a naked "From".  I think that's what screwed
> up the other guy's mail filter for his Pine.

Indeed I think it did. Normally elm would put in a '>' or put in a
Content-length header.

> 					Terry Lambert

Walter.
-- 
Ir. W.H.B. Belgers, Internet Security Specialist        phone: +31 40 2782753
Origin IT Syst.Man. /Nederland bv, Bldg VN-513   email:   fax: +31 40 2784697
P.O. Box 218, 5600 MD Eindhoven, Netherlands     W.Belgers@nl.cis.philips.com
non-business-email: walter@giga.nl   -web: http://www.IAEhv.nl/users/gigawalt

From owner-freebsd-hackers  Thu Feb  6 01:14:09 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id BAA24277
          for hackers-outgoing; Thu, 6 Feb 1997 01:14:09 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA24268
          for <freebsd-hackers@freebsd.org>; Thu, 6 Feb 1997 01:14:05 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id UAA15588; Thu, 6 Feb 1997 20:06:47 +1100
Date: Thu, 6 Feb 1997 20:06:47 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199702060906.UAA15588@godzilla.zeta.org.au>
To: alexis@ww.net, joerg_wunsch@uriah.heep.sax.de
Subject: Re: sio11 64 events for device without tp related problem?
Cc: freebsd-hackers@freebsd.org
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>>> two messages 'sio11 64 events for device without tp' is generated.
>
>	Well, it is master port for 8 ports multiport and no, it uses
>irq 5. Could you elaborate and explain what tp and entire message
>means?

It means that some sio events, probably modem status changes
(actually only one), were detected before the port was first opened.
This shouldn't happen.  Events on sio11 aren't checked for until the
end of the call to the device attach routine for sio11, and they should
not occur afterwards (until the port is opened) because the port is
fully initialized before it is attached.  There is probably a h/w or
s/w bug in the COM_MULTIPORT case.  This is probably harmless.

Bruce

From owner-freebsd-hackers  Thu Feb  6 01:20:30 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id BAA24993
          for hackers-outgoing; Thu, 6 Feb 1997 01:20:30 -0800 (PST)
Received: from freenet.hamilton.on.ca (0@main.freenet.hamilton.on.ca [199.212.94.65])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA24938
          for <hackers@freebsd.org>; Thu, 6 Feb 1997 01:20:12 -0800 (PST)
From: hoek@freenet.hamilton.on.ca
Received: from james.freenet.hamilton.on.ca (james.freenet.hamilton.on.ca [199.212.94.66]) by freenet.hamilton.on.ca (8.7.5/8.7.3) with ESMTP id EAA13333; Thu, 6 Feb 1997 04:20:14 -0500 (EST)
Received: (from ac199@localhost) by james.freenet.hamilton.on.ca (8.7.5/8.7.3) id EAA10754; Thu, 6 Feb 1997 04:22:17 -0500 (EST)
Date: Thu, 6 Feb 1997 04:22:17 -0500 (EST)
Message-Id: <199702060922.EAA10754@james.freenet.hamilton.on.ca>
X-Mailer: slnr v.2.13 as ported to FreeBSD
To: gjennejohn@frt.dec.com
cc: hackers@freebsd.org, packrat@iinet.net.au
Subject: Re: ping(8) 
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In Email, garyj@frt.dec.com wrote:
> packrat@iinet.net.au writes:
> > 
> > Something like '-a': audible tone for pings.
> > 
> 
> seems resaonable to me. Why not '-b' for "bell" ? Seems more
> intuitive somwhow.

printf(1) uses \a for bell, so that could arguably be precedance of some
sort.  OTOH, bc(1) uses a \b for bell, so...  And, of course, there's the
"bell" mode (not "audible" mode) of ftp(1) and "nobeep", not "noaudio" in
csh(1).  Not to forget, either, ex(1)'s "set eb", not "set ea" to turn on
errorbells.  Most incriminating is kbdcontrol(1)'s "-b" option, though... 

"-a" does seem nicer, regardless... 


-- 
tIM...HOEk
"[Your] approach is in error; it is bad engineering methodology."
                              - Terry Lambert.

From owner-freebsd-hackers  Thu Feb  6 02:40:43 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA21205
          for hackers-outgoing; Thu, 6 Feb 1997 02:40:43 -0800 (PST)
Received: from whale.gu.kiev.ua (whale.gu.net [194.93.190.4])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA21151;
          Thu, 6 Feb 1997 02:40:30 -0800 (PST)
Received: from creator.gu.kiev.ua (stesin@creator.gu.kiev.ua [194.93.190.3]) by whale.gu.kiev.ua (8.8.5/8.7.3) with SMTP id MAA62924; Thu, 6 Feb 1997 12:39:46 +0200
Date: Thu, 6 Feb 1997 12:39:46 +0200 (EET)
From: Andrew Stesin <stesin@gu.net>
X-Sender: stesin@creator.gu.kiev.ua
To: Bruce Evans <bde@zeta.org.au>
cc: hackers@freebsd.org, questions@freebsd.org
Subject: Re: Strange(!!) sio callin/callout behaviour in 2.1.6
In-Reply-To: <Pine.BSI.3.95.970206092457.24481A-100000@creator.gu.kiev.ua>
Message-ID: <Pine.BSI.3.95.970206120848.29892F-100000@creator.gu.kiev.ua>
X-NCC-RegID: ua.gu
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


About PPP not hanging up -- sorry people for bothering you,
please take my apologies. I forgot to say a magic
word "modem" to pppd :((((  Dumb me, ogh hell...
Thanks to David Nugent who suggested this.

The other thingies are strange anyway...

--
		Best,
			Andrew Stesin

		nic-hdl: ST73-RIPE


From owner-freebsd-hackers  Thu Feb  6 02:49:36 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA24811
          for hackers-outgoing; Thu, 6 Feb 1997 02:49:36 -0800 (PST)
Received: from relay-7.mail.demon.net (relay-7.mail.demon.net [194.217.242.9])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id CAA24803
          for <hackers@freebsd.org>; Thu, 6 Feb 1997 02:49:30 -0800 (PST)
Received: from runcirc.demon.co.uk ([158.152.9.225]) by relay-6.mail.demon.net
           id aa610208; 6 Feb 97 10:40 GMT
Received: (from roger@localhost) by runcirc.demon.co.uk (8.7.5/8.7.3) id KAA00210; Thu, 6 Feb 1997 10:31:05 GMT
Received: from relay-10.mail.demon.net (punt.demon.co.uk [194.217.242.133]) by runcirc.demon.co.uk (8.7.5/8.7.3) with SMTP id KAA00194 for <roger@runcirc.demon.co.uk>; Thu, 6 Feb 1997 10:30:27 GMT
Received: from relay-9.mail.demon.net by mailstore for roger@runcirc.demon.co.uk
          id 855207389:9:28553:4; Thu, 06 Feb 97 05:36:29 GMT
Received: from etamin.brunel.ac.uk ([134.83.128.61]) by relay-10.mail.demon.net
           id aa1029865; 6 Feb 97 5:36 GMT
Received: from freefall.freebsd.org by etamin.brunel.ac.uk with SMTP (PP);
          Thu, 6 Feb 1997 05:36:00 +0000
Received: from localhost (daemon@localhost) 
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id UAA07119;
          Wed, 5 Feb 1997 20:55:46 -0800 (PST)
Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) 
          id UAA06834 for freebsd-announce-outgoing;
          Wed, 5 Feb 1997 20:53:47 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) 
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA06811;
          Wed, 5 Feb 1997 20:53:40 -0800 (PST)
Received: (from jkh@localhost) by time.cdrom.com (8.8.5/8.6.9) id UAA27279;
          Wed, 5 Feb 1997 20:53:38 -0800 (PST)
Date: Wed, 5 Feb 1997 20:53:38 -0800 (PST)
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Message-Id: <199702060453.UAA27279@time.cdrom.com>
Old-To: announce@FreeBSD.ORG
Subject: My resignation as president of the FreeBSD Project.
Cc: hackers@freebsd.org
Old-X-Loop: FreeBSD.org
X-Loop: roger@runcirc.demon.co.uk
To: r.mccalman@elsevier.co.uk
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

This short notice is just to announce my resignation as President
of the FreeBSD Project, effective immediately, coinciding with the
elimination of that position.

This is entirely my own decision and was not prompted by anyone
on the core team - if anything, they will probably be as surprised
as anyone at the news (except for David & John D., with whom I've
already discussed the matter).

I do this for several reasons, all equally important:

1. The position of President has always been somewhat at-odds with
   our democratic core team structure and purely titular since to
   give the president any real "power" would also destroy the carefully
   balanced dynamic of core, and that would hardly be a desirable outcome.

   The reason the position of "President" was originally created at all
   was to give ISVs and other corporate contacts a more official-sounding
   person to talk to, and while this has been valuable to a certain extent
   I don't think that it's quite proven useful enough to justify the
   further existance of the position.  As it is, it only creates the
   illusion of a "super core member", which the president is not, and
   creates false expectations of authority.

2. The president is generally assumed to be talking for FreeBSD at all times,
   depriving the wearer of that particular thorny crown of the right
   to voice strong opinions or otherwise be outspoken without damaging
   the reputation of the project.  I'm not a punch-pulling kind of guy
   (as you no-doubt already guessed) and I almost certainly never will be,
   so it's time for me to have my own voice back and be able to talk to
   people without it being taken as implicit that I'm somehow speaking
   for all of core.  If being "presidential" also means constantly
   turning the other cheek then I'll never be presidential enough and it's 
   just not an adjustment I care to make (I'm not that kind of person) so
   I should step down from that responsibility.

3. Dropping back to core team status will make it easier for me to
   shed additional FreeBSD responsibilities, should I decide that I
   need to do that in the future, and get some semblance of a life
   back.  I've been doing this for 4 years now and I'm tired.  Just how
   tired I will need to evaluate before making any further decisions, but at
   least the burden of this artificial position will no longer be mine.
   It will, in fact, be no ones' and I think this is a vast improvement.

In discussions with David and John, it was also expressed that the
position was never really that popular with the core team and that
my stepping down should coincide with the complete elimination of
an unnecessary and somewhat flawed position, and so it will be.

So, as of now the FreeBSD Project now longer has a President.  It is
run purely by the core team, as it always was in truth, and now
I'm just the PR guy, release engineer and plain old run-of-the-mill
core team member.  As if that wasn't enough. :-)

					Jordan


From owner-freebsd-hackers  Thu Feb  6 02:50:12 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA24984
          for hackers-outgoing; Thu, 6 Feb 1997 02:50:12 -0800 (PST)
Received: from freenet.hamilton.on.ca (0@main.freenet.hamilton.on.ca [199.212.94.65])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA24965
          for <hackers@freebsd.org>; Thu, 6 Feb 1997 02:50:07 -0800 (PST)
Received: from james.freenet.hamilton.on.ca (james.freenet.hamilton.on.ca [199.212.94.66]) by freenet.hamilton.on.ca (8.7.5/8.7.3) with ESMTP id FAA15518; Thu, 6 Feb 1997 05:50:21 -0500 (EST)
Received: from localhost (ac199@localhost) by james.freenet.hamilton.on.ca (8.7.5/8.7.3) with SMTP id FAA13389; Thu, 6 Feb 1997 05:52:24 -0500 (EST)
X-Authentication-Warning: james.freenet.hamilton.on.ca: ac199 owned process doing -bs
Date: Thu, 6 Feb 1997 05:52:23 -0500 (EST)
From: Tim Vanderhoek <hoek@freenet.hamilton.on.ca>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: hackers@freebsd.org
Subject: Re: My resignation as president of the FreeBSD Project.
In-Reply-To: <199702060453.UAA27279@time.cdrom.com>
Message-ID: <Pine.GSO.3.95.970206054332.13081A-100000@james.freenet.hamilton.on.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Wed, 5 Feb 1997, Jordan K. Hubbard wrote:

> This is entirely my own decision and was not prompted by anyone
> on the core team - if anything, they will probably be as surprised
> as anyone at the news (except for David & John D., with whom I've
> already discussed the matter).

So you have arbitrarily decided to eliminate the position of
President, making the decision on behalf of the democratically-
structured core team.

I'd always wondered how democracies work.

:)



From owner-freebsd-hackers  Thu Feb  6 03:03:07 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id DAA28873
          for hackers-outgoing; Thu, 6 Feb 1997 03:03:07 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA28861
          for <hackers@freebsd.org>; Thu, 6 Feb 1997 03:03:03 -0800 (PST)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id DAA02616; Thu, 6 Feb 1997 03:02:57 -0800 (PST)
To: Tim Vanderhoek <hoek@freenet.hamilton.on.ca>
cc: hackers@freebsd.org
Subject: Re: My resignation as president of the FreeBSD Project. 
In-reply-to: Your message of "Thu, 06 Feb 1997 05:52:23 EST."
             <Pine.GSO.3.95.970206054332.13081A-100000@james.freenet.hamilton.on.ca> 
Date: Thu, 06 Feb 1997 03:02:56 -0800
Message-ID: <2612.855226976@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> On Wed, 5 Feb 1997, Jordan K. Hubbard wrote:
> 
> > This is entirely my own decision and was not prompted by anyone
> > on the core team - if anything, they will probably be as surprised
> > as anyone at the news (except for David & John D., with whom I've
> > already discussed the matter).
> 
> So you have arbitrarily decided to eliminate the position of
> President, making the decision on behalf of the democratically-
> structured core team.

Ah, I probably could have phrased that better. :-)

What I meant by this was that the decision to resign was wholly mine,
the suggestion that the position itself be abolished coming up in
conversation with the 2 other core team members (David & John) I was
discussing my resignation with.  With the 3 of us in agreement, we
knew that at least 2 more core members were a certified yes just based
on past statements (and they duly chimed in afterward saying "good
idea") and that we therefore had a reasonable quorum for just going
ahead and combining the two announcements. :)

					Jordan

From owner-freebsd-hackers  Thu Feb  6 03:03:57 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id DAA29061
          for hackers-outgoing; Thu, 6 Feb 1997 03:03:57 -0800 (PST)
Received: from dawn.ww.net (root@dawn.ww.net [193.124.73.50])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA28920
          for <freebsd-hackers@freebsd.org>; Thu, 6 Feb 1997 03:03:27 -0800 (PST)
Received: (from alexis@localhost)
	by dawn.ww.net (8.7.5/alexis 2.5)  id NAA04467; Thu, 6 Feb 1997 13:59:21 +0300 (MSK)
Message-Id: <199702061059.NAA04467@dawn.ww.net>
Subject: Re: sio11 64 events for device without tp related problem?
To: bde@zeta.org.au (Bruce Evans)
Date: Thu, 6 Feb 1997 13:59:20 +0300 (MSK)
From: Alexis Yushin <alexis@dawn.ww.net>
Cc: alexis@ww.net, joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@freebsd.org
In-Reply-To: <199702060906.UAA15588@godzilla.zeta.org.au> from Bruce Evans at "Feb 6, 97 08:06:47 pm"
Reply-To: alexis@ww.net (Alexis Yushin)
X-Office-Phone: +380 65 2 26.1410
X-Home-Phone: +380 65 2 27.0747
X-NIC-Handle: AY23
X-RIPE-Handle: AY6-RIPE
X-Mailer: ELM [version 2.4ME+ PL17 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Once Bruce Evans wrote:
>>>> two messages 'sio11 64 events for device without tp' is generated.
>>
>>	Well, it is master port for 8 ports multiport and no, it uses
>>irq 5. Could you elaborate and explain what tp and entire message
>>means?
>
>It means that some sio events, probably modem status changes
>(actually only one), were detected before the port was first opened.
>This shouldn't happen.  Events on sio11 aren't checked for until the
>end of the call to the device attach routine for sio11, and they should
>not occur afterwards (until the port is opened) because the port is
>fully initialized before it is attached.  There is probably a h/w or
>s/w bug in the COM_MULTIPORT case.  This is probably harmless.

	Are you sure there is no connection with siobi state hangings?
Well, the machine just arrived to my desk -- will try to produce the
same, then cure it with adding 16M RAM and then, well, then if it
does not help and noone tells me what to will have to investigate :-)

								alexis
-- 
		It's all the same, only the names will change

From owner-freebsd-hackers  Thu Feb  6 04:16:35 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id EAA18074
          for hackers-outgoing; Thu, 6 Feb 1997 04:16:35 -0800 (PST)
Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA18027
          for <freebsd-hackers@freebsd.org>; Thu, 6 Feb 1997 04:16:27 -0800 (PST)
Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id XAA01274; Thu, 6 Feb 1997 23:16:28 +1100 (EST)
Date: Thu, 6 Feb 1997 23:16:27 +1100 (EST)
From: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
To: freebsd-hackers@freebsd.org
Subject: Audible ping response changes to ping.c
Message-ID: <Pine.BSF.3.91.970206231125.427D-100000@panda.hilink.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


The changes to ping.c below are essentially cosmetic, to add 
the ability to create an audible reponse to pings, useful for debugging 
broken ethernets, among other things.  Submitted by Bruce Murphy 
<packrat@iinet.net.au>.  Are there any objections to this being committed 
to -current, and the equivalent to RELENG_2_2?

Danny

*** ping.c.orig	Tue Feb  4 13:29:47 1997
--- ping.c	Tue Feb  4 14:45:59 1997
***************
*** 109,114 ****
--- 109,115 ----
  #define	F_NOLOOP	0x0400
  #define	F_MTTL		0x0800
  #define	F_MIF		0x1000
+ #define	F_AUDIBLE	0x2000
  
  /*
   * MAX_DUP_CHK is the number of bits in received table, i.e. the maximum
***************
*** 185,192 ****
  	preload = 0;
  
  	datap = &outpack[8 + sizeof(struct timeval)];
! 	while ((ch = getopt(argc, argv, "I:LQRT:c:dfh:i:l:np:qrs:v")) != EOF)
  		switch(ch) {
  		case 'c':
  			npackets = atoi(optarg);
  			if (npackets <= 0) {
--- 186,196 ----
  	preload = 0;
  
  	datap = &outpack[8 + sizeof(struct timeval)];
! 	while ((ch = getopt(argc, argv, "I:LQRT:c:adfh:i:l:np:qrs:v")) != EOF)
  		switch(ch) {
+ 		case 'a':
+ 			options |= F_AUDIBLE;
+ 			break;
  		case 'c':
  			npackets = atoi(optarg);
  			if (npackets <= 0) {
***************
*** 619,624 ****
--- 623,630 ----
  				(void)printf(" time=%.3f ms", triptime);
  			if (dupflag)
  				(void)printf(" (DUP!)");
+ 			if (options & F_AUDIBLE)
+ 				(void)printf("\a");
  			/* check the data */
  			cp = (u_char*)&icp->icmp_data[8];
  			dp = &outpack[8 + sizeof(struct timeval)];
***************
*** 1134,1139 ****
  usage()
  {
  	(void)fprintf(stderr,
! 	    "usage: ping [-LQRdfnqrv] [-c count] [-i wait] [-I interface]\n\t[-l preload] [-p pattern] [-s packetsize] [-T ttl] host\n");
  	exit(1);
  }
--- 1140,1145 ----
  usage()
  {
  	(void)fprintf(stderr,
! 	    "usage: ping [-LQRadfnqrv] [-c count] [-i wait] [-I interface]\n\t[-l preload] [-p pattern] [-s packetsize] [-T ttl] host\n");
  	exit(1);
  }



From owner-freebsd-hackers  Thu Feb  6 04:26:11 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id EAA20117
          for hackers-outgoing; Thu, 6 Feb 1997 04:26:11 -0800 (PST)
Received: from profane.iq.org (profane.iq.org [203.4.184.217])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA20098
          for <hackers@freebsd.org>; Thu, 6 Feb 1997 04:26:06 -0800 (PST)
Received: (from proff@localhost)
          by profane.iq.org (8.8.4/8.8.2) id XAA01453
          for hackers@freebsd.org; Thu, 6 Feb 1997 23:23:47 +1100 (EST)
From: Julian Assange <proff@iq.org>
Message-Id: <199702061223.XAA01453@profane.iq.org>
Subject: security issues
To: hackers@freebsd.org
Date: Thu, 6 Feb 1997 23:23:47 +1100 (EST)
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


I'd like to add a voice of reason to this debate; I've had
disagreements with core members commit policy in the past. Although
I still disagree with core on that issue, and felt very hot-blooded
about it at the time I elected not to make a public issue out of
it for a number of reasons, the foremost being that sometimes even
the best of people just disagree with each other. It has became
clear to me by and by that core has "some of the best people".

Core is not a gaggle of project administrators with nothing better
to do, they are programmers; talented or prolific and occasionally
both. Further when discussing my commit disagreements with core I
was struck by the thought, diplomacy and humour core (particularly
Jordon, despite his claims of not being able to pull punches) put into
replying. It is possible to disagree on an issue with people you
respect without loosing your respect for them on all issues and
this is an important point to remember.

Jordon, please don't take the flaming to heart. I truly appreciate
the work you have done even if I have disagreed with you on other
issues from time to time.

--
Prof. Julian Assange  |If you want to build a ship, don't drum up people
		      |together to collect wood and don't assign them tasks
proff@iq.org          |and work, but rather teach them to long for the endless
proff@gnu.ai.mit.edu  |immensity of the sea. -- Antoine de Saint Exupery

From owner-freebsd-hackers  Thu Feb  6 04:45:35 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id EAA26325
          for hackers-outgoing; Thu, 6 Feb 1997 04:45:35 -0800 (PST)
Received: from dawn.ww.net (root@dawn.ww.net [193.124.73.50])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA26294
          for <freebsd-hackers@freebsd.org>; Thu, 6 Feb 1997 04:45:21 -0800 (PST)
Received: (from alexis@localhost)
	by dawn.ww.net (8.7.5/alexis 2.5)  id PAA04773; Thu, 6 Feb 1997 15:31:15 +0300 (MSK)
Message-Id: <199702061231.PAA04773@dawn.ww.net>
Subject: Re: sio11 64 events for device without tp related problem?
To: joerg_wunsch@uriah.heep.sax.de
Date: Thu, 6 Feb 1997 15:31:15 +0300 (MSK)
From: Alexis Yushin <alexis@dawn.ww.net>
Cc: alexis@ww.net, freebsd-hackers@freebsd.org
In-Reply-To: <Mutt.19970205234703.j@uriah.heep.sax.de> from J Wunsch at "Feb 5, 97 11:47:03 pm"
Reply-To: alexis@ww.net (Alexis Yushin)
X-Office-Phone: +380 65 2 26.1410
X-Home-Phone: +380 65 2 27.0747
X-NIC-Handle: AY23
X-RIPE-Handle: AY6-RIPE
X-Mailer: ELM [version 2.4ME+ PL17 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Once J Wunsch wrote:
[...]

	Well, it turned out to be pretty trival. So if another
lamer asks the question like mine tell him he forgotten to include
COM_MULTIPORT option. Thanks to everyone. Goodluck,
								alexis
-- 
		It's all the same, only the names will change

From owner-freebsd-hackers  Thu Feb  6 04:59:02 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id EAA27899
          for hackers-outgoing; Thu, 6 Feb 1997 04:59:02 -0800 (PST)
Received: from mail13.digital.com (mail13.digital.com [192.208.46.30])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA27880
          for <hackers@freebsd.org>; Thu, 6 Feb 1997 04:58:58 -0800 (PST)
From: garyj@frt.dec.com
Received: from cssmuc.frt.dec.com by mail13.digital.com (8.7.5/UNX 1.5/1.0/WV)
	id HAA13401; Thu, 6 Feb 1997 07:54:02 -0500 (EST)
Received: from localhost by cssmuc.frt.dec.com; (5.65v3.2/1.1.8.2/14Nov95-0232PM)
	id AA02265; Thu, 6 Feb 1997 13:53:56 +0100
Message-Id: <9702061253.AA02265@cssmuc.frt.dec.com>
X-Mailer: exmh version 1.6.4 10/10/95
To: hackers@freebsd.org
In-Reply-To: Message from "Daniel O'Callaghan" <danny@panda.hilink.com.au>  of 
 Thu, 06 Feb 97 23:16:27 +1100.
Reply-To: gjennejohn@frt.dec.com
Subject: Re: Audible ping response changes to ping.c 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 06 Feb 97 13:53:55 +0100
X-Mts: smtp
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


danny@panda.hilink.com.au writes:
> 
> The changes to ping.c below are essentially cosmetic, to add 
> the ability to create an audible reponse to pings, useful for debugging 
> broken ethernets, among other things.  Submitted by Bruce Murphy 
> <packrat@iinet.net.au>.  Are there any objections to this being committed 
> to -current, and the equivalent to RELENG_2_2?
> 
> Danny
> 
[patch deleted]

seems reasonable to me. I tested it under 2.1.5 (the only version I have
access to at work) and it works OK.

What about the main page ?

---
Gary Jennejohn				(work) gjennejohn@frt.dec.com
					(home) Gary.Jennejohn@munich.netsurf.de
					(play) gj@freebsd.org



From owner-freebsd-hackers  Thu Feb  6 05:13:53 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id FAA00575
          for hackers-outgoing; Thu, 6 Feb 1997 05:13:53 -0800 (PST)
Received: from ravenock.cybercity.dk (ravenock.cybercity.dk [194.16.57.32])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA00559;
          Thu, 6 Feb 1997 05:13:46 -0800 (PST)
Received: (from sos@localhost) by ravenock.cybercity.dk (8.8.5/8.7.3) id OAA03166; Thu, 6 Feb 1997 14:15:12 +0100 (MET)
From: Søren Schmidt <sos@ravenock.cybercity.dk>
Message-Id: <199702061315.OAA03166@ravenock.cybercity.dk>
Subject: Re: My resignation as president of the FreeBSD Project.
In-Reply-To: <199702060453.UAA27279@time.cdrom.com> from "Jordan K. Hubbard" at "Feb 5, 97 08:53:38 pm"
To: jkh@time.cdrom.com (Jordan K. Hubbard)
Date: Thu, 6 Feb 1997 14:15:03 +0100 (MET)
Cc: announce@freebsd.org, hackers@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL30 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In reply to Jordan K. Hubbard who wrote:
> This short notice is just to announce my resignation as President
> of the FreeBSD Project, effective immediately, coinciding with the
> elimination of that position.

Well, we are in times of changes, I've long wondered how you would
survive this title :)

Wellcome to the "simple core team" member league :)

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Søren Schmidt               (sos@FreeBSD.org)               FreeBSD Core Team
                Even more code to hack -- will it ever end
..

From owner-freebsd-hackers  Thu Feb  6 05:20:07 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id FAA01500
          for hackers-outgoing; Thu, 6 Feb 1997 05:20:07 -0800 (PST)
Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA01429
          for <hackers@freebsd.org>; Thu, 6 Feb 1997 05:19:58 -0800 (PST)
Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id AAA01524; Fri, 7 Feb 1997 00:16:54 +1100 (EST)
Date: Fri, 7 Feb 1997 00:16:53 +1100 (EST)
From: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
To: gjennejohn@frt.dec.com
cc: hackers@freebsd.org
Subject: Re: Audible ping response changes to ping.c 
In-Reply-To: <9702061253.AA02265@cssmuc.frt.dec.com>
Message-ID: <Pine.BSF.3.91.970207001504.427F-100000@panda.hilink.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk



On Thu, 6 Feb 1997 garyj@frt.dec.com wrote:

> 
> danny@panda.hilink.com.au writes:
> > 
> > The changes to ping.c below are essentially cosmetic, to add 
> > the ability to create an audible reponse to pings, useful for debugging 
> > broken ethernets, among other things.  Submitted by Bruce Murphy 
> > <packrat@iinet.net.au>.  Are there any objections to this being committed 
> > to -current, and the equivalent to RELENG_2_2?
> [patch deleted]
> 
> seems reasonable to me. I tested it under 2.1.5 (the only version I have
> access to at work) and it works OK.
> 
> What about the main page ?

I have man page mods for 2.2 and -current also. They'll be committed with 
the code.

Danny

From owner-freebsd-hackers  Thu Feb  6 05:29:31 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id FAA03331
          for hackers-outgoing; Thu, 6 Feb 1997 05:29:31 -0800 (PST)
Received: from mail.id.net (mail.id.net [199.125.1.6])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA03313;
          Thu, 6 Feb 1997 05:29:25 -0800 (PST)
Received: from server.id.net (server.id.net [199.125.2.20]) by mail.id.net (8.7.5/ID-Net) with ESMTP id IAA17365; Thu, 6 Feb 1997 08:35:43 -0500 (EST)
From: Robert Shady <rls@mail.id.net>
Received: (from rls@localhost) by server.id.net (8.8.2/8.7.3) id IAA02342; Thu, 6 Feb 1997 08:29:34 -0500 (EST)
Message-Id: <199702061329.IAA02342@server.id.net>
Subject: Re: My resignation as president of the FreeBSD Project.
In-Reply-To: <199702060453.UAA27279@time.cdrom.com> from "Jordan K. Hubbard" at "Feb 5, 97 08:53:38 pm"
To: jkh@time.cdrom.com (Jordan K. Hubbard)
Date: Thu, 6 Feb 1997 08:29:33 -0500 (EST)
Cc: announce@FreeBSD.ORG, hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL25 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> This short notice is just to announce my resignation as President
> of the FreeBSD Project, effective immediately, coinciding with the
> elimination of that position.

Bravo, I applaude your professionalism and everything you have done to
help with the promotion & distribution of FreeBSD.  I remember when I
first spoke to you just about 4 years ago, and everything you've done
since then.  You've come along way, and I don't think it's unrealistic
to dream about having a 'life', whatever THAT means.. ;)

	-- Rob
===
      _/_/_/_/_/  _/_/_/_/               _/_/    _/  _/_/_/_/_/  _/_/_/_/_/
         _/      _/      _/    _/_/_/   _/  _/  _/  _/_/_/_/        _/
   _/_/_/_/_/  _/_/_/_/               _/      _/  _/_/_/_/_/      _/

                             Innovative Data Services 
                          Serving South-Eastern Michigan 
        Internet Service Provider / Hardware Sales / Consulting Services
       Voice: (810)855-0404 / Fax: (810)855-3268 / Web: http://www.id.net

From owner-freebsd-hackers  Thu Feb  6 05:37:29 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id FAA04441
          for hackers-outgoing; Thu, 6 Feb 1997 05:37:29 -0800 (PST)
Received: from po1.glue.umd.edu (root@po1.glue.umd.edu [129.2.128.44])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA04410;
          Thu, 6 Feb 1997 05:37:22 -0800 (PST)
Received: from modem.eng.umd.edu (modem.eng.umd.edu [129.2.98.187]) by po1.glue.umd.edu (8.8.5/8.7.3) with ESMTP id IAA11402; Thu, 6 Feb 1997 08:37:11 -0500 (EST)
Received: from localhost (chuckr@localhost) by modem.eng.umd.edu (8.8.5/8.7.3) with SMTP id IAA07021; Thu, 6 Feb 1997 08:37:10 -0500 (EST)
X-Authentication-Warning: modem.eng.umd.edu: chuckr owned process doing -bs
Date: Thu, 6 Feb 1997 08:37:10 -0500 (EST)
From: Chuck Robey <chuckr@glue.umd.edu>
X-Sender: chuckr@modem.eng.umd.edu
To: Bruce Evans <bde@zeta.org.au>
cc: imp@village.org, freebsd-ports@freebsd.org, hackers@freebsd.org,
        obrien@NUXI.com
Subject: Re: conditionally including <sys/param.h>
In-Reply-To: <199702060300.OAA01390@godzilla.zeta.org.au>
Message-ID: <Pine.OSF.3.95q.970206083404.5948A-100000@modem.eng.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Thu, 6 Feb 1997, Bruce Evans wrote:

> >: strerror() doesn't exist on old systems.
> >
> >True.  But how old is old?
> 
> Orphaned systems still don't have it.
> 
> >: I think we should just use `#ifdef __FreeBSD__' and <sys/param.h> in
> >: ports.  Original authors should use a better method to suit themselves.
> >
> >Yes, but this whole thing got started because the #ifdef __FreeBSD__
> >was slowly turning into
> >	#if defined(__OpenBSD__) || defined(__NetBSD__) || defined(__FreeBSD__)
> >in a bunch of places due to those projects riding along on the FreeBSD
> >port's coat tails.
> 
> Maybe include <sys/param.h> unconditionally?  I'm not sure why I mentioned
> the __FreeBSD__ ifdef above.  I've never liked ifdefing on the OS -
> it isn't necessary for one OS and gives too-large ifdefs for more than
> 2 OS's.  You'll still need large ifdefs if configuration depends on the
> value of `BSD' and the value is OS-dependent.

No, that wouldn't work.  We're talking about something we'd ask authors of
packages that weren't written for FreeBSD to include (and to include for
NetBSD and OpenBSD) to get their packages to work with ours.  This isn't
just for your own ports use.  Since just including sys/param.h would cause
packages to fail to compile on many platforms, no one outside FreeBSD
would be willing to take our advice on it.  We need something that works
for Free|Net|OpenBSD but isn't fatal for other platforms.

> 
> Bruce
> 

----------------------------+-----------------------------------------------
Chuck Robey                 | Interests include any kind of voice or data 
chuckr@eng.umd.edu          | communications topic, C programming, and Unix.
9120 Edmonston Ct #302      |
Greenbelt, MD 20770         | I run Journey2 and picnic, both FreeBSD
(301) 220-2114              | version 3.0 current -- and great FUN!
----------------------------+-----------------------------------------------


From owner-freebsd-hackers  Thu Feb  6 05:45:05 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id FAA05619
          for hackers-outgoing; Thu, 6 Feb 1997 05:45:05 -0800 (PST)
Received: from dawn.ww.net (root@dawn.ww.net [193.124.73.50])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA05593
          for <freebsd-hackers@freebsd.org>; Thu, 6 Feb 1997 05:44:47 -0800 (PST)
Received: (from alexis@localhost)
	by dawn.ww.net (8.7.5/alexis 2.5)  id QAA05043; Thu, 6 Feb 1997 16:43:30 +0300 (MSK)
Message-Id: <199702061343.QAA05043@dawn.ww.net>
Subject: siobi problem continues
To: alexis@ww.net
Date: Thu, 6 Feb 1997 16:43:27 +0300 (MSK)
From: Alexis Yushin <alexis@dawn.ww.net>
Cc: joerg_wunsch@uriah.heep.sax.de, alexis@ww.net, freebsd-hackers@freebsd.org
In-Reply-To: <199702061231.PAA04773@dawn.ww.net> from Alexis Yushin at "Feb 6, 97 03:31:15 pm"
Reply-To: alexis@ww.net (Alexis Yushin)
X-Office-Phone: +380 65 2 26.1410
X-Home-Phone: +380 65 2 27.0747
X-NIC-Handle: AY23
X-RIPE-Handle: AY6-RIPE
X-Mailer: ELM [version 2.4ME+ PL17 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Once Alexis Yushin wrote:
>	Well, it turned out to be pretty trival. So if another
>lamer asks the question like mine tell him he forgotten to include
>COM_MULTIPORT option. Thanks to everyone. Goodluck,

	Well, not that simple. That solved sio11 problem but not
siobi state problems. Anyone can give me a hint what kind of state
that is and how syslogd manages to get into that state? :-)

								alexis
-- 
		It's all the same, only the names will change

From owner-freebsd-hackers  Thu Feb  6 06:21:09 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id GAA10365
          for hackers-outgoing; Thu, 6 Feb 1997 06:21:09 -0800 (PST)
Received: from bmcgover-pc.cisco.com (bmcgover-pc.cisco.com [171.69.104.147])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA10353
          for <hackers@freebsd.org>; Thu, 6 Feb 1997 06:20:53 -0800 (PST)
Received: from bmcgover-pc.cisco.com (bmcgover@localhost.cisco.com [127.0.0.1]) by bmcgover-pc.cisco.com (8.8.2/8.8.2) with ESMTP id JAA01590; Thu, 6 Feb 1997 09:18:22 -0500 (EST)
Message-Id: <199702061418.JAA01590@bmcgover-pc.cisco.com>
To: dg@root.com
cc: hackers@freebsd.org
Subject: Re: Stomp the bug!!!! (Was cyclades bug) 
In-reply-to: Your message of "Wed, 05 Feb 1997 14:00:50 PST."
             <199702052200.OAA11374@root.com> 
Date: Thu, 06 Feb 1997 09:18:22 -0500
From: Brian McGovern <bmcgover@cisco.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

David,
	One last thought. (BTW, I'm assuming you'll commit the change I sent
in... If not, let me know :) ). If we tinkered with locore.s and pmap.c to
remove the PG_N (?) flag to try to fix this problem, would there be any
reason not to put them back in assuming they would a.) improve performance 
someplace, and b.) not cause additional problems down the road? Again, just
a thought...

	-Brian

From owner-freebsd-hackers  Thu Feb  6 06:48:31 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id GAA14398
          for hackers-outgoing; Thu, 6 Feb 1997 06:48:31 -0800 (PST)
Received: from hda.hda.com (ip3-max1-fitch.ziplink.net [199.232.245.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id GAA14384
          for <freebsd-hackers@freebsd.org>; Thu, 6 Feb 1997 06:48:27 -0800 (PST)
Received: (from dufault@localhost) by hda.hda.com (8.6.12/8.6.12) id JAA00412; Thu, 6 Feb 1997 09:43:27 -0500
From: Peter Dufault <dufault@hda.com>
Message-Id: <199702061443.JAA00412@hda.hda.com>
Subject: Re: Audible ping response changes to ping.c
In-Reply-To: <Pine.BSF.3.91.970206231125.427D-100000@panda.hilink.com.au> from Daniel O'Callaghan at "Feb 6, 97 11:16:27 pm"
To: danny@panda.hilink.com.au (Daniel O'Callaghan)
Date: Thu, 6 Feb 1997 09:43:27 -0500 (EST)
Cc: freebsd-hackers@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL25 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by freefall.freebsd.org id GAA14392
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> The changes to ping.c below are essentially cosmetic, to add 
> the ability to create an audible reponse to pings...
Since this isn't likely to become universal how about what I do:

ping foo | sed 's/$//'

-- 
Peter Dufault (dufault@hda.com)   Realtime Machine Control and Simulation
HD Associates, Inc.               Voice: 508 433 6936

From owner-freebsd-hackers  Thu Feb  6 07:24:43 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id HAA20561
          for hackers-outgoing; Thu, 6 Feb 1997 07:24:43 -0800 (PST)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id HAA20519;
          Thu, 6 Feb 1997 07:24:35 -0800 (PST)
Received: from rover.village.org [127.0.0.1] 
	by rover.village.org with esmtp (Exim 0.56 #1)
	id E0vsVgc-0006YL-00; Thu, 6 Feb 1997 08:24:30 -0700
To: obrien@NUXI.com (David O'Brien)
Subject: Re: conditionally including <sys/param.h> 
Cc: freebsd-ports@freebsd.org (FreeBSD ports list), hackers@freebsd.org
In-reply-to: Your message of "Wed, 05 Feb 1997 22:59:27 PST."
		<19970205225927.LP41225@dragon.nuxi.com> 
References: <19970205225927.LP41225@dragon.nuxi.com>  <19970205112604.AI13761@dragon.nuxi.com> <19970205003343.YB13323@dragon.nuxi.com> <Pine.OSF.3.95q.970205081326.9802A-100000@gilligan.eng.umd.edu> <E0vsJWO-0002dq-00@rover.village.org> 
Date: Thu, 06 Feb 1997 08:24:30 -0700
From: Warner Losh <imp@village.org>
Message-Id: <E0vsVgc-0006YL-00@rover.village.org>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <19970205225927.LP41225@dragon.nuxi.com> David O'Brien writes:
: Just to make sure we are agreeing on the same thing, can you restate the
: tweaks?

Briefly:

#if (defined(unix) || defined(__unix__)) && !defined(USG)
#include <sys/param.h>
#endif

...

#if defined(BSD) && BSD >= 199304
blah
#endif

This casts a wide enough net to include almost all systems that have a
sys/param.h that is likely to define BSD, yet specifically excludes
things that don't work (eg WinNT and old SYS V (pre r4) and SYS III
machines).

While I haven't seen the final text, this is what is currently in the
handbook until we can refine it to be something even better.

Warner

From owner-freebsd-hackers  Thu Feb  6 08:05:57 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id IAA06381
          for hackers-outgoing; Thu, 6 Feb 1997 08:05:57 -0800 (PST)
Received: from croute.com (ishm2.croute.com [199.97.106.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id IAA06344;
          Thu, 6 Feb 1997 08:05:49 -0800 (PST)
Received: from bldg1.croute.com by croute.com (4.1/SMI-4.1)
	id AA17976; Thu, 6 Feb 97 10:05:37 CST
Received: from COMPUROUTE/SpoolDir by bldg1.croute.com (Mercury 1.21);
    6 Feb 97 10:05:37 -0600 (CST)
Received: from SpoolDir by COMPUROUTE (Mercury 1.30); 6 Feb 97 10:05:11 -0600 (CST)
From: "Larry Dolinar" <LARRYD@bldg1.croute.com>
Organization:  CompuRoute, Inc.
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>,
        owner-freebsd-announce@freebsd.org
Date:          Thu, 6 Feb 1997 10:05:09 -0600 CDT
Mime-Version:  1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Subject:       Re: My resignation as president of the FreeBSD Project.
Cc: hackers@freebsd.org
X-Confirm-Reading-To: "Larry Dolinar" <LARRYD@bldg1.croute.com>
X-Pmrqc:       1
Priority: normal
X-Mailer: Pegasus Mail v3.40
Message-Id: <4DB81C1583E@bldg1.croute.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In a way, I'm sorry to hear it, but I'm all for less stress and more 
creativity.  Hope things go well.

best regards,
larry

From owner-freebsd-hackers  Thu Feb  6 08:31:45 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id IAA13809
          for hackers-outgoing; Thu, 6 Feb 1997 08:31:45 -0800 (PST)
Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id IAA13803
          for <hackers@FreeBSD.org>; Thu, 6 Feb 1997 08:31:41 -0800 (PST)
Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM)
	id AA31862; Thu, 6 Feb 1997 08:31:35 -0800
Date: Thu, 6 Feb 1997 08:31:35 -0800 (PST)
From: "Brian N. Handy" <handy@sag.space.lockheed.com>
To: hackers@FreeBSD.org
Cc: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Subject: Re: My resignation as president of the FreeBSD Project.
In-Reply-To: <Pine.BSF.3.95.970205221316.2490A-100000@logues.rhn.orst.edu>
Message-Id: <Pine.OSF.3.94.970206083050.31073A-100000@sag.space.lockheed.com>
X-Files: The truth is out there
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

Jordan:
>> [I resign]
>
Steve:
>I think this is a wise choice, and will lead to much simpler relations,
>less stress, and most of all less confusion.

...And maybe more pithy quotes! :-)

Brian


From owner-freebsd-hackers  Thu Feb  6 09:50:43 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA18473
          for hackers-outgoing; Thu, 6 Feb 1997 09:50:43 -0800 (PST)
Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA18466
          for <freebsd-hackers@freefall.FreeBSD.org>; Thu, 6 Feb 1997 09:50:39 -0800 (PST)
Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02)
	id AA05429; Thu, 6 Feb 1997 12:50:06 -0500
Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Thu,  6 Feb 1997 12:50 EST
Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id HAA14556; Thu, 6 Feb 1997 07:02:56 -0500 (EST)
Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id HAA27288; Thu, 6 Feb 1997 07:07:29 -0500 (EST)
Date: Thu, 6 Feb 1997 07:07:29 -0500 (EST)
From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
Message-Id: <199702061207.HAA27288@lakes.water.net>
To: ponds!current1.whistle.com!julian, ponds!lakes.water.net!rivers
Subject: Re: Build an install floppy for 2.1.6???
Cc: ponds!freefall.cdrom.com!freebsd-hackers
Content-Type: text
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Julian writes:
> 
> I don't know if it still works perfectly,
> but I made a directory in /usr/src/release/floppies
> you need to havedone a "make world"
> after that (if you have vn support) you go to that directory
> and type "make" and it SHOULD make a boot, and fixit floppy..
> I should go check if it's been broken, but it USED to work..
> if it's broken, it at least should be a good starting point..

 Err... - that "make world" part is the portion I'm trying to
avoid.

 I'll look for it in the makefile. I had cobbled together (by hand)
enough to get it to work before, basically by building the stand
portions that go into the kernel image, replacing missing pieces, etc...
Perhaps I can do that again.

	- Thanks -
	- Dave R. -

> 
> 
> On Wed, 5 Feb 1997, Thomas David Rivers wrote:
> 
> > 
> > Ok -
> > 
	...
> > 
> >  Can just an install floppy be made from the makefiles, or do you 
> > have make an entire release???
> > 
> > 	- Dave Rivers -
> > 
> > 
> 
> 


From owner-freebsd-hackers  Thu Feb  6 10:36:49 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id KAA20990
          for hackers-outgoing; Thu, 6 Feb 1997 10:36:49 -0800 (PST)
Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA20983;
          Thu, 6 Feb 1997 10:36:46 -0800 (PST)
Received: by iafnl.es.iaf.nl with UUCP id AA23826
  (5.67b/IDA-1.5); Thu, 6 Feb 1997 19:35:59 +0100
Received: (from wilko@localhost) by yedi.iaf.nl (8.7.5/8.6.12) id TAA00904; Thu, 6 Feb 1997 19:20:43 +0100 (MET)
From: Wilko Bulte <wilko@yedi.iaf.nl>
Message-Id: <199702061820.TAA00904@yedi.iaf.nl>
Subject: Re: My resignation as president of the FreeBSD Project.
To: rls@mail.id.net (Robert Shady)
Date: Thu, 6 Feb 1997 19:20:43 +0100 (MET)
Cc: jkh@time.cdrom.com, announce@FreeBSD.ORG, hackers@FreeBSD.ORG
In-Reply-To: <199702061329.IAA02342@server.id.net> from "Robert Shady" at Feb 6, 97 08:29:33 am
X-Mailer: ELM [version 2.4 PL24 ME8a]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > This short notice is just to announce my resignation as President
> > of the FreeBSD Project, effective immediately, coinciding with the
> > elimination of that position.

As Robert Shady wrote...

[snip]

> help with the promotion & distribution of FreeBSD.  I remember when I
> first spoke to you just about 4 years ago, and everything you've done
> since then.  You've come along way, and I don't think it's unrealistic
> to dream about having a 'life', whatever THAT means.. ;)

In this case it boils down to having time to hug the cats (at least
if I'm well informed 8-)

Wilko
_     ____________________________________________________________________
 |   / o / /  _  Bulte  email: wilko@yedi.iaf.nl - Arnhem, The Netherlands
 |/|/ / / /( (_) 	Do, or do not. There is no 'try' - Yoda
--------------------------------------------------------------------------

From owner-freebsd-hackers  Thu Feb  6 10:53:27 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id KAA21820
          for hackers-outgoing; Thu, 6 Feb 1997 10:53:27 -0800 (PST)
Received: from root.com (implode.root.com [198.145.90.17])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA21810
          for <hackers@freebsd.org>; Thu, 6 Feb 1997 10:53:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id KAA18091; Thu, 6 Feb 1997 10:53:24 -0800 (PST)
Message-Id: <199702061853.KAA18091@root.com>
X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol
To: Brian McGovern <bmcgover@cisco.com>
cc: hackers@freebsd.org
Subject: Re: Stomp the bug!!!! (Was cyclades bug) 
In-reply-to: Your message of "Thu, 06 Feb 1997 09:18:22 EST."
             <199702061418.JAA01590@bmcgover-pc.cisco.com> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Thu, 06 Feb 1997 10:53:24 -0800
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>David,
>	One last thought. (BTW, I'm assuming you'll commit the change I sent
>in... If not, let me know :) ).

   Sorry, yes, I committed it seconds after you told me about it. :-)

> If we tinkered with locore.s and pmap.c to
>remove the PG_N (?) flag to try to fix this problem, would there be any
>reason not to put them back in assuming they would a.) improve performance 
>someplace, and b.) not cause additional problems down the road? Again, just
>a thought...

   Yes, the problem other people were having with occasional panics is
apparantly unrelated to the bug you found in the initialization code. It
is still believed that removing PG_N fixes that problem. There should be
no difference in performance in any case.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project

From owner-freebsd-hackers  Thu Feb  6 10:58:17 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id KAA22071
          for hackers-outgoing; Thu, 6 Feb 1997 10:58:17 -0800 (PST)
Received: from humvee.doit.wisc.edu (humvee.doit.wisc.edu [144.92.9.20])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA22050;
          Thu, 6 Feb 1997 10:58:10 -0800 (PST)
Received: from audumla.students.wisc.edu by humvee.doit.wisc.edu;
          id MAA07578; 8.7.5/50; Thu, 6 Feb 1997 12:58:03 -0600
Received: from gabor-bsd by audumla.students.wisc.edu;
          id MAA64106; 8.6.9W/42; Thu, 6 Feb 1997 12:56:23 -0600
Message-ID: <32FA29A1.41C67EA6@acm.org>
Date: Thu, 06 Feb 1997 12:57:37 -0600
From: Gabor Kincses <gabor@acm.org>
X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.1.5-RELEASE i386)
MIME-Version: 1.0
To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org,
        freebsd-hardware@freebsd.org, freebsd-bugs@freebsd.org
Subject: Panic in probe, but no dump
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I have been trying to get the Voxware 2.90b drivers on 2.1.5 to
recognize my Logitech Soundman Wave card correctly.  I managed to get
the card recognized as Soundblaster Pro 3.1, but unfortunately only one
speaker is working.

So after much searching of FreeBSD and Linux resources on the Net, I
have concluded that this card is in fact a MediaVision Jazz16.  I have
looked at sound.doc and sound_config.h in i386/isa/sound and saw a few
useful-looking options that I added to my kernel config.  One problem I
was faced with is that /usr/sbin/config didn't like option JAZZ16, but
understood option "JAZZ16".  Similarly JAZZ16 was not an acceptable
name, but JAZZ was.  I'm not sure if this is documented anywhere. 
Certain defines are missing for the JAZZ16 and the SM_WAVE options.  It
seems to me that Linux has much newer drivers than FreeBSD, although
this is still to be proven.

The problem I have is to get a dump out of the sound driver probe.  I
pretty much followed the handbook on this.  I have set config root on
wd2 dumps on wd2 in my config file, but no dump occurred (I checked .  I
did savecore -f in single user mode to try to get anything out of the
swap device to no avail.  I managed to locate where the page fault
occurred based on an earlier post by roberto@eurocontrol.fr:
    nm /kernel | sort |grep 0xf01948
The panic was reported at EIP=0xf01948a4 which is _initialize_smw in my
kernel.  I would like to see the actual offending line of code.

So my questions are:
1. Is there a way to load the kernel.debug in gdb and correlate
addresses with lines of code?  (Like on HP-UX w/ xdb: one can use 'td')
2. Why am I not getting a core dump?  Would the disk "rattle" a bit to
save the kernel core, or is it already on the swap device?  Ie. what
macroscopic events would tell me that I got a dump?  (Possibly: "core
dumped" msg on the console :-)
3. I have turned on savecore in /etc/sysconfig, but I have noticed that
the swapon gets executed first in /etc/rc before the savecore.  Wouldn't
this wipe out a core in the swap device?
4. How can one get any description of the I/O registers of a device?
5. Is my only option left is ddb?
6. Is a page fault essentially like a segmentation violation in user
mode?  AFAIK on i386 you have to install a page fault handler, which is
probably what the VM is all about.  Is this true?
7. Why is the "dumps on" feature being deprecated?  How else can we get
a dump if the system crashes before dumpon can be executed?  BTW, My
swapkernel.c looks like this:
#include <sys/param.h>
#include <sys/conf.h>

dev_t   rootdev = makedev(0, 0x00000010);               /* wd2a */
dev_t   dumpdev = makedev(0, 0x00000011);               /* wd2b */

void
setconf()
{
}

Thanks,

-- 
Gabor Kincses
(gabor@acm.org)

From owner-freebsd-hackers  Thu Feb  6 11:51:31 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA00233
          for hackers-outgoing; Thu, 6 Feb 1997 11:51:31 -0800 (PST)
Received: from sergio.lenzi ([200.247.23.106])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA00204
          for <hackers@freebsd.org>; Thu, 6 Feb 1997 11:51:25 -0800 (PST)
Received: (from lenzi@localhost) by sergio.lenzi (8.8.3/8.8.3) id RAA00575; Thu, 6 Feb 1997 17:57:19 GMT
Date: Thu, 6 Feb 1997 17:57:18 +0000 ()
From: "Lenzi, Sergio" <lenzi@bsi.com.br>
X-Sender: lenzi@sergio
To: Mark Mayo <mark@quickweb.com>
cc: hackers@freebsd.org
Subject: Re: Samba survey
In-Reply-To: <Pine.BSF.3.94.970205145305.28031A-100000@vinyl.quickweb.com>
Message-ID: <Pine.BSF.3.91.970206175443.511D-100000@sergio>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Wed, 5 Feb 1997, Mark Mayo wrote:

> Hi all - I just checked out the Samba survey page (URL below) and noticed
> that there are only 28 sites running samba according to the stats! This
> seems *really* low to me, so I was wondering if people have filled out the
> survey...

Hello Mark Mayo...


There are thousands of samba out there..  Every FreeBSD I install I put 
samba on it.  I only did not mention it to the lake.camberra...


Only me, in the 1996 installed 30 to 40 FreeBSD using Samba on windows 
networks and suprise.... it works better than the NT on the same network.



Sergio Lenzi.

Unix consult.


From owner-freebsd-hackers  Thu Feb  6 11:53:33 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA00399
          for hackers-outgoing; Thu, 6 Feb 1997 11:53:33 -0800 (PST)
Received: from red.jnx.com (red.jnx.com [208.197.169.254])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA00390;
          Thu, 6 Feb 1997 11:53:28 -0800 (PST)
Received: (from pst@localhost) by red.jnx.com (8.8.5/8.8.3) id LAA26214; Thu, 6 Feb 1997 11:52:58 -0800 (PST)
Date: Thu, 6 Feb 1997 11:52:58 -0800 (PST)
From: Paul Traina <pst@jnx.com>
Message-Id: <199702061952.LAA26214@red.jnx.com>
To: hackers@freebsd.org
Subject: serial ports at 230k
Cc: bde@freebsd.org
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Does anyone have any experience with running 16550A's at 230kbps under FreeBSD?
Yes, I know, the driver doesn't support it currently, but has anyone played?

From owner-freebsd-hackers  Thu Feb  6 12:01:09 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA00800
          for hackers-outgoing; Thu, 6 Feb 1997 12:01:09 -0800 (PST)
Received: from werple.net.au (melb.werple.net.au [203.9.190.18])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA00788
          for <hackers@freebsd.org>; Thu, 6 Feb 1997 12:01:04 -0800 (PST)
Received: (qmail 1421 invoked by uid 5); 6 Feb 1997 20:01:01 -0000
MBOX-Line: From jb@freebsd1.cimlogic.com.au  Thu Feb  6 13:38:00 1997
Received: (from jb@localhost) by freebsd1.cimlogic.com.au (8.7.5/8.7.3) id NAA04044; Thu, 6 Feb 1997 13:38:00 +1100 (EST)
From: John Birrell <jb@cimlogic.com.au>
Message-Id: <199702060238.NAA04044@freebsd1.cimlogic.com.au>
Subject: Re: fcntl, F_SETFL, O_NONBLOCK & /dev/null
To: bde@zeta.org.au (Bruce Evans)
Date: Thu, 6 Feb 1997 13:37:59 +1100 (EST)
Cc: hackers@freebsd.org
In-Reply-To: <199702060208.NAA32068@godzilla.zeta.org.au> from Bruce Evans at "Feb 6, 97 01:08:24 pm"
X-Mailer: ELM [version 2.4ME+ PL22 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Bruce Evans wrote:
> >I can open /dev/null with O_NONBLOCK. If I open /dev/null without
> >O_NONBLOCK and then try to fcntl F_SETFL to change the file descriptor
> >to non-blocking, I get ENODEV returned. Can someone tell me why?
> 
> fcntl(fd, F_SETFL, O_NONBLOCK) is translated to an FIONBIO ioctl, and
> the device driver for /dev/null doesn't support this ioctl.  None of
> the memory devices support it.
> 
> Another problem with the translation is that the flag is supposed to
> be per-file, but if the FIONBIO ioctl actually does anything, then
> the flag is sort of per device - a per-file flag is kept in all cases,
> but it may be inconsistent with the device state.
> 
> One way to fix this is to remove the FIONBIO calls from fcntl().
> This isn't quite right, since it should be possible for drivers to reject
> O_NONBLOCK (or maybe !O_NONBLOCK).  However, in practice most drivers
> are too stupid to check for O_NONBLOCK in their open routine and too
> stupid to support FIONBIO in their ioctl routine.  This results in the
> stupid behaviour that you observed.

Thanks for the info. This means that libc_r will always have difficulty
dealing with such devices. The library expects to be given non-blocking
behaviour if (when) it asks for it.  So the best I can do is open()
the device with O_NONBLOCK and hope that the driver obeys. If not, an
unexpected wait will occur, without another thread being scheduled in
the meantime. Hmmm, yet another reason for kernel threads...

> 
> Bruce
> 


-- 
John Birrell                                CIMlogic Pty Ltd
jb@cimlogic.com.au; jb@netbsd.org           119 Cecil Street
Ph  +61  3 9690 6900                        South Melbourne Vic 3205
Fax +61  3 9690 6650                        Australia
Mob +61 18  353  137

From owner-freebsd-hackers  Thu Feb  6 12:03:55 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA00937
          for hackers-outgoing; Thu, 6 Feb 1997 12:03:55 -0800 (PST)
Received: from sergio.lenzi ([200.247.23.106])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA00930
          for <hackers@freebsd.org>; Thu, 6 Feb 1997 12:03:49 -0800 (PST)
Received: (from lenzi@localhost) by sergio.lenzi (8.8.3/8.8.3) id SAA00598; Thu, 6 Feb 1997 18:08:14 GMT
Date: Thu, 6 Feb 1997 18:08:12 +0000 ()
From: "Lenzi, Sergio" <lenzi@bsi.com.br>
X-Sender: lenzi@sergio
To: Amancio Hasty <hasty@rah.star-gate.com>
cc: Mark Mayo <mark@quickweb.com>, hackers@freebsd.org
Subject: Re: Samba survey 
In-Reply-To: <199702052059.MAA19654@rah.star-gate.com>
Message-ID: <Pine.BSF.3.91.970206180309.511E-100000@sergio>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Wed, 5 Feb 1997, Amancio Hasty wrote:

> Is there a configuration tool which aids a new user like me to setup 
> samba?
> 
> 	Tnks,
> 	Amancio
> 
OK...

If you need some help.
1) create directories lib locks var under the /usr/local/samba
	owner nobody.
2) put smb.conf under /usr/local/samba/lib
[homes]
	writeable=yes
[printer]
	path=/var/spool/lpd/windows
	writeable=no
	public=yes
	printable=yes
	print command=/usr/local/samba/bin/psfilter < %s | lpr;rm %s
[CDROM]
	path=/cdrom
	writeable=no
	public=true
[UNIX]
	path=/usr/windows
	writeable=yes
	public=true

3) start hmbd
      /usr/local/samba/bin/nmbd -D -G HOME
4) put a line on /etc/inetd.conf...
      netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd smbd
5) restart inetd.....


hope this can help




Sergio Lenzi.

Unix consult.


From owner-freebsd-hackers  Thu Feb  6 12:06:12 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA01098
          for hackers-outgoing; Thu, 6 Feb 1997 12:06:12 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA01084;
          Thu, 6 Feb 1997 12:05:56 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id HAA01985; Fri, 7 Feb 1997 07:03:27 +1100
Date: Fri, 7 Feb 1997 07:03:27 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199702062003.HAA01985@godzilla.zeta.org.au>
To: hackers@freebsd.org, pst@jnx.com
Subject: Re: serial ports at 230k
Cc: bde@freebsd.org
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>Does anyone have any experience with running 16550A's at 230kbps under FreeBSD?
>Yes, I know, the driver doesn't support it currently, but has anyone played?

Not me.  I checked the PC16550D specs recently.  The maximum speed is
1.5Mbps like I remembered.

If you only care about remote gdb throughput to an sio port on a
FreeBSD host, note that the protocol is non-streaming so it is limited
to 1 packet per clock tick (30Kbps effective throughput at best) by the
host's pseudo-DMA timeout routine.

Bruce

From owner-freebsd-hackers  Thu Feb  6 12:18:07 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA01936
          for hackers-outgoing; Thu, 6 Feb 1997 12:18:07 -0800 (PST)
Received: from sendero.i-connect.net ([206.190.144.100])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA01890;
          Thu, 6 Feb 1997 12:17:57 -0800 (PST)
Received: (from shimon@localhost)
          by sendero.i-connect.net (8.8.5/8.8.4)
	  id NAA09330; Thu, 6 Feb 1997 13:17:01 -0800 (PST)
Message-ID: <XFMail.970206131700.Shimon@i-Connect.Net>
X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD
Content-Type: text/plain; charset=iso-8859-8
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <199702060512.AAA10010@dyson.iquest.net>
Date: Thu, 06 Feb 1997 09:55:40 -0800 (PST)
Organization: iConnect Corp.
From: Simon Shapiro <Shimon@i-Connect.Net>
To: "John S. Dyson" <toor@dyson.iquest.net>
Subject: Re: Contigious (spelling?) allocation in kernel
Cc: freebsd-hackers@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


Hi John S. Dyson;  On 06-Feb-97 you wrote: 

> Take a look at contigmalloc() or vm_page_alloc_contig()
> as defined in /sys/vm/vm_page.c.  These are almost
> guaranteed NOT to work after the system is fully up.

Thanx.

If you (or someone else) please elaborate on the last sentence,
please...

I can re-structure the driver a bit (make it more risky), to 
avoid the need for large contigious blocks, but the (obvious)
question is:  Does the kernel malloc guarantee that allocations
smaller than (or equal to) a page are in the same page?

Having a page or less, limits the Scatter/Gather operations in
the kernel, for most hardware, to 512 entries (segments).  
Under high fragmentation, this can result in 256KB-2MB floating
limit.  While not a problem for most applications (mine
included), it is still a limit that is not absolutely necessary.

Any opposing opinions (before I re-code the darn thing :-)?

BACKGROUND:  One of my engineers, who is heavily involved in 
Linux SCSI development is strongly opposed to calling malloc on
demand in a device driver.  He quotes heavy performance
penalties, and worse;  Failure (under heavy load) to obtain the
memory when needed.

Thanx, Simon

From owner-freebsd-hackers  Thu Feb  6 12:18:09 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA01944
          for hackers-outgoing; Thu, 6 Feb 1997 12:18:09 -0800 (PST)
Received: from sendero.i-connect.net ([206.190.144.100])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA01887;
          Thu, 6 Feb 1997 12:17:56 -0800 (PST)
Received: (from shimon@localhost)
          by sendero.i-connect.net (8.8.5/8.8.4)
	  id NAA09327; Thu, 6 Feb 1997 13:17:01 -0800 (PST)
Message-ID: <XFMail.970206131700.Shimon@i-Connect.Net>
X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD
Content-Type: text/plain; charset=iso-8859-8
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <199702060533.VAA00624@narnia.plutotech.com>
Date: Thu, 06 Feb 1997 10:35:32 -0800 (PST)
Organization: iConnect Corp.
From: Simon Shapiro <Shimon@i-Connect.Net>
To: "Justin T. Gibbs" <gibbs@narnia.plutotech.com>
Subject: Re: Contigious (spelling?) allocation in kernel
Cc: freebsd-hackers@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


Hi Justin T. Gibbs;  On 06-Feb-97 you wrote: 

...

> You really think you're going to ever transfer a full 32MB of data in a
single
> transaction?  Even if you were, you'd have to do something special to the
> kernel since it currently only generates requests of at most 64k (its a
silly
> restriction and it should die a horrible death).  

I agree.  It does funny things to tape drives, CD writers, etc.

> Assuming you did have a way
> to stuff 32MB through all of the layers, you'd probably be better off
chopping
> that I/O into smaller chunks so as to reduce the amount of SG space you
must
> allocate.  At anything over 8k, the transaction overhead starts to become
an
> increasingly small percentage of your I/O time, so dropping even down as
low as
> 1MB per transaction may better utilize your resources.

Agree.  The board vendor would like to see these large transfers. But a 1MB
limit is not unreasonable.

...

> You don't want to continuously malloc your SG list.  This will kill your
> performance.  If it is acceptable for the system to run with all 256
> requests active at once, you have to be able to deal with all of the
requests
> being allocated anyway, so you might as well pool them.

I agree.  We never thought to dynamically allocate them, per request.
What I have done is to allocate them, in blocks, into a free list, every
time the free list is empty.  I do not have a mechanism to ever free them,
but that can be added later by comparing the current freelist size with a
usage high water mark.


All this brings me to another question.  How can I create another kernel
thread?  What I am trying to do is have several execution threads in the
kernel, each responsible for a given task.  All I see in the drivers I
read so far is a single thread, associated wit hthe calling user process.
Another thread is invoked by the interrupt handler.  I want a couple more.

One ugly way to do it is to have a ``daemon'' which makes a known system
call (ioctl) which is never returned.  Aside from being ugly, it has a
problem at boot time;  The daemon is not there until way after init has
started.

What I am after is something that could resemble the swapper.
Linux has few of them and they become very handy.  Especially on an SMP
machine.

Thanx,

Simon

From owner-freebsd-hackers  Thu Feb  6 12:20:34 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA02335
          for hackers-outgoing; Thu, 6 Feb 1997 12:20:34 -0800 (PST)
Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA02326
          for <hackers@freebsd.org>; Thu, 6 Feb 1997 12:20:29 -0800 (PST)
Received: from ntws (ntws.etinc.com [204.141.95.142]) by etinc.com (8.8.3/8.6.9) with SMTP id PAA01941 for <hackers@freebsd.org>; Thu, 6 Feb 1997 15:23:35 -0500 (EST)
Message-Id: <3.0.32.19970206152009.00a53100@etinc.com>
X-Sender: dennis@etinc.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Thu, 06 Feb 1997 15:20:11 -0500
To: hackers@freebsd.org
From: dennis <dennis@etinc.com>
Subject: 2.1.6?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Whats with 2.1.6R? What happened to the packages section on
the ftp server?

Dennis

From owner-freebsd-hackers  Thu Feb  6 12:26:24 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA02590
          for hackers-outgoing; Thu, 6 Feb 1997 12:26:24 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA02585;
          Thu, 6 Feb 1997 12:26:20 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id HAA02499; Fri, 7 Feb 1997 07:19:37 +1100
Date: Fri, 7 Feb 1997 07:19:37 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199702062019.HAA02499@godzilla.zeta.org.au>
To: bde@zeta.org.au, chuckr@glue.umd.edu
Subject: Re: conditionally including <sys/param.h>
Cc: freebsd-ports@freebsd.org, hackers@freebsd.org, imp@village.org,
        obrien@NUXI.com
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>> >Yes, but this whole thing got started because the #ifdef __FreeBSD__
>> >was slowly turning into
>> >	#if defined(__OpenBSD__) || defined(__NetBSD__) || defined(__FreeBSD__)
>> >in a bunch of places due to those projects riding along on the FreeBSD
>> >port's coat tails.
>> 
>> Maybe include <sys/param.h> unconditionally?  I'm not sure why I mentioned
>> the __FreeBSD__ ifdef above.  I've never liked ifdefing on the OS -
>> it isn't necessary for one OS and gives too-large ifdefs for more than
>> 2 OS's.  You'll still need large ifdefs if configuration depends on the
>> value of `BSD' and the value is OS-dependent.
>
>No, that wouldn't work.  We're talking about something we'd ask authors of
>packages that weren't written for FreeBSD to include (and to include for
>NetBSD and OpenBSD) to get their packages to work with ours.  This isn't

But they certainly should accept anything with __FooBSD__ or BSD >= mmm
or __FooBSD_version >= nnn.  That would give 100-line ifdefs to support
100 OS's.  It's also useless for communicating what is different in
FooBSD.

Bruce

From owner-freebsd-hackers  Thu Feb  6 12:32:47 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA03179
          for hackers-outgoing; Thu, 6 Feb 1997 12:32:47 -0800 (PST)
Received: from earth.infinetconsulting.com (earth.infinetconsulting.com [207.23.43.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA03167
          for <freebsd-hackers@freebsd.org>; Thu, 6 Feb 1997 12:32:44 -0800 (PST)
Received: (from lenc@localhost) by earth.infinetconsulting.com (8.8.3/8.6.12) id MAA20890; Thu, 6 Feb 1997 12:46:52 -0800 (PST)
Date: Thu, 6 Feb 1997 12:46:52 -0800 (PST)
From: Leonard Chua <lenc@earth.infinetconsulting.com>
To: jkh@tme.cdrom.com, freebsd-hackers@freebsd.org
Subject: Re: My resignation as president of the FreeBSD Project. 
In-Reply-To: <Pine.BSF.3.91.970206124509.20779B-100000@earth.infinetconsulting.com>
Message-ID: <Pine.BSF.3.91.970206124524.20885A-100000@earth.infinetconsulting.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > Are you still suppose to be called "Mr. President" even though you
> > are really an X-"Mr. President"?
> 
> Actually, at this point my name changes to an obscure glyph that can
> only be displayed in the KOI-8 font.  You can just refer to me as "the
> core team member formerly known as the president" if it's easier.
> 				Jordan

And in a couple of months, I suppose you'll be referred to as "the 
member" :)


From owner-freebsd-hackers  Thu Feb  6 12:36:57 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA03472
          for hackers-outgoing; Thu, 6 Feb 1997 12:36:57 -0800 (PST)
Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA03452;
          Thu, 6 Feb 1997 12:36:53 -0800 (PST)
Received: from narnia (localhost [127.0.0.1]) by narnia.plutotech.com (8.8.5/8.7.3) with ESMTP id MAA01871; Thu, 6 Feb 1997 12:36:53 -0800 (PST)
Message-Id: <199702062036.MAA01871@narnia.plutotech.com>
To: Simon Shapiro <Shimon@i-Connect.Net>
cc: "Justin T. Gibbs" <gibbs@plutotech.com>, freebsd-hackers@FreeBSD.ORG,
        freebsd-scsi@FreeBSD.ORG
Subject: Re: Contigious (spelling?) allocation in kernel 
In-reply-to: Your message of "Thu, 06 Feb 1997 10:35:32 PST."
             <XFMail.970206131700.Shimon@i-Connect.Net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 06 Feb 1997 12:36:53 -0800
From: "Justin T. Gibbs" <gibbs@narnia.plutotech.com>
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>Agree.  The board vendor would like to see these large transfers. But a 1MB
>limit is not unreasonable.
>

Okay, so if you can live with 2MB or less per transaction, you'll have at most
a page worth of SG list per transaction, and you can use regular malloc to pool
them as you like.  The aic7xxx driver does this for its SG list already,
allocating a page worth of SG lists each time.  I used to have the SG list
maxed out at 256 (the limit of these controllers), but recently dropped it
down to 32 until the 64k limit goes away (17 would be sufficient for anything
that the kernel does, but I wanted it to be a power of 2 for efficient pooling).

>All this brings me to another question.  How can I create another kernel
>thread?
>

You have a couple choices.  One is to make another in-kernel process like
the page daemon.  Another is to add software interrupt handlers for your
tasks.  This can work well if your workload has clean interdependencies.  For
example, the CAM SCSI code will add another software interrupt handler that
deals with work provided by the controller's interrupt routine at a lower
priority then the hardware interrupts themselves.  This ensures that your
controller interrupt handler is as short as possible (they curently call up
into the mid layer at raised SPL blocking other interrupts) as the current
scheme can be really nasty if you are sharing an interrupt with a device that
requires fast response times (like a Fibre Channel or ethernet card).

>Thanx,
>
>Simon
>

--
Justin T. Gibbs
===========================================
  FreeBSD: Turning PCs into workstations
===========================================



From owner-freebsd-hackers  Thu Feb  6 12:53:00 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA04462
          for hackers-outgoing; Thu, 6 Feb 1997 12:53:00 -0800 (PST)
Received: from red.jnx.com (red.jnx.com [208.197.169.254])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA04451;
          Thu, 6 Feb 1997 12:52:50 -0800 (PST)
Received: from base.jnx.com (base.jnx.com [208.197.169.238]) by red.jnx.com (8.8.5/8.8.3) with ESMTP id MAA01123; Thu, 6 Feb 1997 12:52:14 -0800 (PST)
Received: from base.jnx.com (localhost.jnx.com [127.0.0.1]) by base.jnx.com (8.7.6/8.7.3) with ESMTP id MAA00639; Thu, 6 Feb 1997 12:52:14 -0800 (PST)
Message-Id: <199702062052.MAA00639@base.jnx.com>
To: Bruce Evans <bde@zeta.org.au>
cc: hackers@freebsd.org, bde@freebsd.org
Subject: Re: serial ports at 230k 
In-reply-to: Your message of "Fri, 07 Feb 1997 07:03:27 +1100."
             <199702062003.HAA01985@godzilla.zeta.org.au> 
Date: Thu, 06 Feb 1997 12:52:13 -0800
From: Paul Traina <pst@jnx.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Good guess, but I'm actually trying out a 3COM ISDN TA that runs at 230k.

  From: Bruce Evans <bde@zeta.org.au>
  Subject: Re: serial ports at 230k
  >Does anyone have any experience with running 16550A's at 230kbps under FreeB
>>SD?
  >Yes, I know, the driver doesn't support it currently, but has anyone played?
  
  Not me.  I checked the PC16550D specs recently.  The maximum speed is
  1.5Mbps like I remembered.
  
  If you only care about remote gdb throughput to an sio port on a
  FreeBSD host, note that the protocol is non-streaming so it is limited
  to 1 packet per clock tick (30Kbps effective throughput at best) by the
  host's pseudo-DMA timeout routine.
  
  Bruce

From owner-freebsd-hackers  Thu Feb  6 13:15:44 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA05795
          for hackers-outgoing; Thu, 6 Feb 1997 13:15:44 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA05790
          for <hackers@freebsd.org>; Thu, 6 Feb 1997 13:15:41 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA17832; Thu, 6 Feb 1997 14:11:52 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702062111.OAA17832@phaeton.artisoft.com>
Subject: Re: DOS partition trouble
To: bde@zeta.org.au (Bruce Evans)
Date: Thu, 6 Feb 1997 14:11:52 -0700 (MST)
Cc: durham@w2xo.pgh.pa.us, hackers@freebsd.org
In-Reply-To: <199702060616.RAA09563@godzilla.zeta.org.au> from "Bruce Evans" at Feb 6, 97 05:16:25 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> >Twice now, I have removed a DOS partition
> >from a disk with both DOS and FreeBSD
> >partitions and been unable to boot FreeBSD.
> >...
> >I had tried running the partition editor when I had no DOS
> >partition and it gave all indications of sucessfully writing
> >out the boot block, but would not boot until I remade the
> >DOS partition. Trying to mount the root directory from the MFS
> >on the boot floppy gave a "bad super block" error.
> 
> For SCSI disks with at least ncr controllers, this could be caused
> a DOS partition that ends on a cylinder boundary and FreeBSD partition
> that doesn't.  When you remove the DOS partition, the controller's BIOS
> will have problems determining the disk geometry.

What?  The BIOS examines the disk to get the geometry?

How do you put something on the disk in the first place, then?

I was under the impression that fictitious geometry was *always*
an artifact of the BIOS's idea of geometry, not the oter way around.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Thu Feb  6 13:20:24 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA06192
          for hackers-outgoing; Thu, 6 Feb 1997 13:20:24 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA06182
          for <freebsd-hackers@freebsd.org>; Thu, 6 Feb 1997 13:20:17 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA17845; Thu, 6 Feb 1997 14:16:58 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702062116.OAA17845@phaeton.artisoft.com>
Subject: Re: NIS/uids
To: W.Belgers@nl.cis.philips.com (Walter Belgers)
Date: Thu, 6 Feb 1997 14:16:58 -0700 (MST)
Cc: terry@lambert.org, freebsd-hackers@freebsd.org
In-Reply-To: <199702060842.JAA26171@giga.lss.cp.philips.com> from "Walter Belgers" at Feb 6, 97 09:42:07 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > > Let's assume I do not trust the uid's coming from the NIS server but I
> > > still do want to use NIS (for passwd/homedir/gecos/whatever).
> > 
> > Then you have the same problem, this time with associating a
> > particular password with a particular name.  All you have done is
> > trade the association with uid for an association with name.  There
> > is nothing the prevents me, as an NIS server, from returning the
> > password "frobozz" (encrypted, of course) for every user, regardless
> > of their real password.
> 
> That's right. But at least you could only become one of the NIS users of
> which none is in wheel. I can live with people hacking the NIS server
> and getting access to my machine, I won't have people becoming root.

Couldn't I add the user to "wheel" or "kmem" in the NIS groups file
anyway?

I still like the idea of a list of groups and uids that won't be
honored via NIS.


> > Mostly because if I compromise the NIS server,
> > then I can force you to accept any password for any user/password pair,
> > and thereby become any user/id pair, so it doesn't give you the protection
> > you are trying to get it to give you.
> 
> I have no "+" in my password file, only "+user", so you can only hack
> those users, not the users that are only locally in my password file. So
> it does give the desired protection.

Do you do "+group" in the group file, as well?  I suppose you have to...


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Thu Feb  6 13:30:34 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA06813
          for hackers-outgoing; Thu, 6 Feb 1997 13:30:34 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA06780
          for <freebsd-hackers@freebsd.org>; Thu, 6 Feb 1997 13:30:18 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA17900; Thu, 6 Feb 1997 14:25:46 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702062125.OAA17900@phaeton.artisoft.com>
Subject: Re: Audible ping response changes to ping.c
To: dufault@hda.com (Peter Dufault)
Date: Thu, 6 Feb 1997 14:25:46 -0700 (MST)
Cc: danny@panda.hilink.com.au, freebsd-hackers@freebsd.org
In-Reply-To: <199702061443.JAA00412@hda.hda.com> from "Peter Dufault" at Feb 6, 97 09:43:27 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > The changes to ping.c below are essentially cosmetic, to add 
> > the ability to create an audible reponse to pings...
> Since this isn't likely to become universal how about what I do:
> 
> ping foo | sed 's/$//'

I was thinking of a shell script called "aping":

#!/bin/sh
ping $* | while read x
do
        echo "$x"
done

After all, this is what a tools OS is all about...


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Thu Feb  6 13:35:43 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA07263
          for hackers-outgoing; Thu, 6 Feb 1997 13:35:43 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA07253;
          Thu, 6 Feb 1997 13:35:30 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA17929; Thu, 6 Feb 1997 14:31:48 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702062131.OAA17929@phaeton.artisoft.com>
Subject: Re: serial ports at 230k
To: pst@jnx.com (Paul Traina)
Date: Thu, 6 Feb 1997 14:31:48 -0700 (MST)
Cc: hackers@freebsd.org, bde@freebsd.org
In-Reply-To: <199702061952.LAA26214@red.jnx.com> from "Paul Traina" at Feb 6, 97 11:52:58 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Does anyone have any experience with running 16550A's at 230kbps
> under FreeBSD?
>
> Yes, I know, the driver doesn't support it currently, but has anyone
> played?

The hardware doesn't support it, unless you changeout your clock
crystal (assuming it isn't using an on-board clock generator in
an ASIC containing it and the UART both).

All the driver does is translate manifest conatants to bit patterns,
so it doesn't care if B300 (for instance) really makes the UART go
into 300 baud mode or not.

8-).


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Thu Feb  6 13:40:22 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA07580
          for hackers-outgoing; Thu, 6 Feb 1997 13:40:22 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA07572;
          Thu, 6 Feb 1997 13:40:18 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA17938; Thu, 6 Feb 1997 14:33:25 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702062133.OAA17938@phaeton.artisoft.com>
Subject: Re: conditionally including <sys/param.h>
To: bde@zeta.org.au (Bruce Evans)
Date: Thu, 6 Feb 1997 14:33:25 -0700 (MST)
Cc: bde@zeta.org.au, chuckr@glue.umd.edu, freebsd-ports@freebsd.org,
        hackers@freebsd.org, imp@village.org, obrien@NUXI.com
In-Reply-To: <199702062019.HAA02499@godzilla.zeta.org.au> from "Bruce Evans" at Feb 7, 97 07:19:37 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> But they certainly should accept anything with __FooBSD__ or BSD >= mmm
> or __FooBSD_version >= nnn.  That would give 100-line ifdefs to support
> 100 OS's.  It's also useless for communicating what is different in
> FooBSD.

Too bad "#if defined()" doesn't accept globbing:

#if defined (_*BSD_)


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Thu Feb  6 13:42:57 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA08122
          for hackers-outgoing; Thu, 6 Feb 1997 13:42:57 -0800 (PST)
Received: from red.jnx.com (red.jnx.com [208.197.169.254])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA08097;
          Thu, 6 Feb 1997 13:42:44 -0800 (PST)
Received: from base.jnx.com (base.jnx.com [208.197.169.238]) by red.jnx.com (8.8.5/8.8.3) with ESMTP id NAA03573; Thu, 6 Feb 1997 13:42:13 -0800 (PST)
Received: from base.jnx.com (localhost.jnx.com [127.0.0.1]) by base.jnx.com (8.7.6/8.7.3) with ESMTP id NAA00990; Thu, 6 Feb 1997 13:42:12 -0800 (PST)
Message-Id: <199702062142.NAA00990@base.jnx.com>
To: Terry Lambert <terry@lambert.org>
cc: hackers@freebsd.org, bde@freebsd.org, rgrimes@freebsd.org
Subject: Re: serial ports at 230k 
In-reply-to: Your message of "Thu, 06 Feb 1997 14:31:48 MST."
             <199702062131.OAA17929@phaeton.artisoft.com> 
Date: Thu, 06 Feb 1997 13:42:12 -0800
From: Paul Traina <pst@jnx.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

That's what I thought too,  but everything I read suggests that no special
hardware is actually necessary.  I know the clock divisor goes to 0 at 115k,
so I'm assuming that there's a clock multiplier somewhere else that can
be kicked with relatively modern 550s.

W95, with appropriate prodding, was happy to set my serial port speed to
what it claimed was 230k.

  From: Terry Lambert <terry@lambert.org>
  Subject: Re: serial ports at 230k
  > Does anyone have any experience with running 16550A's at 230kbps
  > under FreeBSD?
  >
  > Yes, I know, the driver doesn't support it currently, but has anyone
  > played?
  
  The hardware doesn't support it, unless you changeout your clock
  crystal (assuming it isn't using an on-board clock generator in
  an ASIC containing it and the UART both).
  
  All the driver does is translate manifest conatants to bit patterns,
  so it doesn't care if B300 (for instance) really makes the UART go
  into 300 baud mode or not.
  
  8-).
  
  
  					Terry Lambert
  					terry@lambert.org
  ---
  Any opinions in this posting are my own and not those of my present
  or previous employers.

From owner-freebsd-hackers  Thu Feb  6 14:09:21 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA09598
          for hackers-outgoing; Thu, 6 Feb 1997 14:09:21 -0800 (PST)
Received: from seabass.progroup.com (catfish.progroup.com [206.24.122.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA09593
          for <hackers@FreeBSD.org>; Thu, 6 Feb 1997 14:09:15 -0800 (PST)
Received: from seabass.progroup.com (seabass.progroup.com [206.24.122.1]) by seabass.progroup.com (8.7.5/8.7.3) with SMTP id OAA11528; Thu, 6 Feb 1997 14:08:21 -0800 (PST)
Message-ID: <32FA5655.3F54BC7E@progroup.com>
Date: Thu, 06 Feb 1997 14:08:21 -0800
From: Craig Shaver <craig@progroup.com>
Organization: Productivity Group, Inc.
X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.1.5-RELEASE i386)
MIME-Version: 1.0
To: hackers@FreeBSD.org
Subject: Re: fcntl, F_SETFL, O_NONBLOCK & /dev/null
References: <199702060238.NAA04044@freebsd1.cimlogic.com.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

John Birrell wrote:
> 
> Bruce Evans wrote:
> > >I can open /dev/null with O_NONBLOCK. If I open /dev/null without
> > >O_NONBLOCK and then try to fcntl F_SETFL to change the file descriptor
> > >to non-blocking, I get ENODEV returned. Can someone tell me why?
> >
> > fcntl(fd, F_SETFL, O_NONBLOCK) is translated to an FIONBIO ioctl, and
> > the device driver for /dev/null doesn't support this ioctl.  None of
> > the memory devices support it.
del ...
> Thanks for the info. This means that libc_r will always have difficulty
> dealing with such devices. The library expects to be given non-blocking
> behaviour if (when) it asks for it.  So the best I can do is open()
> the device with O_NONBLOCK and hope that the driver obeys. If not, an
> unexpected wait will occur, without another thread being scheduled in
> the meantime. Hmmm, yet another reason for kernel threads...
> 
> >
> > Bruce
> >
> 
> --

Is there any work being done for implementing kernel threads?  I would 
think this would be very important for a robust, real-world usable,
thread package.

-- 
Craig Shaver  (craig@progroup.com) (415)390-0654 
Productivity Group POB 60458 Sunnyvale, CA  94088

From owner-freebsd-hackers  Thu Feb  6 14:14:53 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA09920
          for hackers-outgoing; Thu, 6 Feb 1997 14:14:53 -0800 (PST)
Received: from gwa.ericsson.com (gwa.ericsson.com [198.215.127.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA09904;
          Thu, 6 Feb 1997 14:14:30 -0800 (PST)
Received: from mr1.exu.ericsson.se (mr1.exu.ericsson.com [138.85.147.11]) by gwa.ericsson.com (8.8.2/8.8.2) with ESMTP id QAA29640; Thu, 6 Feb 1997 16:13:54 -0600 (CST)
Received: from noah.lmc.ericsson.se (noah.lmc.ericsson.se [142.133.1.1]) by mr1.exu.ericsson.se (8.7.1/NAHUB-MR1.1) with ESMTP id QAA20863; Thu, 6 Feb 1997 16:13:53 -0600 (CST)
Received: from jello.lmc.ericsson.se (jello.lmc.ericsson.se [142.133.28.34]) by noah.lmc.ericsson.se (8.8.3/8.8.3) with ESMTP id RAA08788; Thu, 6 Feb 1997 17:13:51 -0500 (EST)
Received: (from lmcsato@localhost) by jello.lmc.ericsson.se (8.8.3/8.8.3) id RAA02105; Thu, 6 Feb 1997 17:13:55 -0500 (EST)
Message-Id: <199702062213.RAA02105@jello.lmc.ericsson.se>
MIME-Version: 1.0 (OpenStep Mail Solaris OpenStep-1.1b-sparc-05 Nov 1996
	Version 1.1)
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Received: by NeXT.Mailer (Solaris OpenStep-1.1b-sparc-05 Nov 1996 Version 1.1
	.RR)
From: Samy Touati <lmcsato@LMC.Ericsson.SE>
Date: Thu,  6 Feb 97 17:13:54 +0500
To: Terry Lambert <terry@lambert.org>
Subject: Re: serial ports at 230k
cc: pst@jnx.com (Paul Traina), hackers@FreeBSD.ORG, bde@FreeBSD.ORG
References: <199702062131.OAA17929@phaeton.artisoft.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by freefall.freebsd.org id OAA09909
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

So this means that if you put a 16650 UART (it's not a typo) you can still use the same driver and achieve 128k
unstead of just 115,2k ?

Samy


The hardware doesn't support it, unless you changeout your clock
crystal (assuming it isn't using an on-board clock generator in
an ASIC containing it and the UART both).

All the driver does is translate manifest conatants to bit patterns,
so it doesn't care if B300 (for instance) really makes the UART go
into 300 baud mode or not.

8-).


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Thu Feb  6 14:16:50 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA10079
          for hackers-outgoing; Thu, 6 Feb 1997 14:16:50 -0800 (PST)
Received: from smyrno.sol.net (smyrno.sol.net [206.55.64.117])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA10041;
          Thu, 6 Feb 1997 14:16:33 -0800 (PST)
Received: from solaria.sol.net (solaria.sol.net [206.55.65.75]) by smyrno.sol.net (8.8.3/8.8.3) with SMTP id QAA12326; Thu, 6 Feb 1997 16:15:56 -0600 (CST)
Received: from localhost by solaria.sol.net (8.5/8.5)
	id QAA26943; Thu, 6 Feb 1997 16:15:54 -0600
From: Joe Greco <jgreco@solaria.sol.net>
Message-Id: <199702062215.QAA26943@solaria.sol.net>
Subject: Re: serial ports at 230k
To: pst@jnx.com (Paul Traina)
Date: Thu, 6 Feb 97 16:15:53 CST
Cc: hackers@freebsd.org, bde@freebsd.org
In-Reply-To: <199702061952.LAA26214@red.jnx.com> from "Paul Traina" at Feb 6, 97 11:52:58 am
X-Mailer: ELM [version 2.4dev PL65]
MIME-Version: 1.0
Content-Type: text
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Does anyone have any experience with running 16550A's at 230kbps under FreeBSD?
> Yes, I know, the driver doesn't support it currently, but has anyone played?

Yes.  Take a standard serial card and replace the 1.8432MHz crystal with
a 3.6864 MHz crystal..  ;-)  Your "115200" speed will magically run at
230.4Kbps.

I did it a long time ago, and if you're not one for soldering, I may have
a pair of souped up cards if you're interested in buyin' em...  or you can
go get the Hayes ESP serial cards.

... Joe

-------------------------------------------------------------------------------
Joe Greco - Systems Administrator			      jgreco@ns.sol.net
Solaria Public Access UNIX - Milwaukee, WI			   414/342-4847

From owner-freebsd-hackers  Thu Feb  6 14:20:52 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA10432
          for hackers-outgoing; Thu, 6 Feb 1997 14:20:52 -0800 (PST)
Received: from smyrno.sol.net (smyrno.sol.net [206.55.64.117])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA10250
          for <freebsd-hackers@FreeBSD.ORG>; Thu, 6 Feb 1997 14:19:41 -0800 (PST)
Received: from solaria.sol.net (solaria.sol.net [206.55.65.75]) by smyrno.sol.net (8.8.3/8.8.3) with SMTP id QAA12361; Thu, 6 Feb 1997 16:18:53 -0600 (CST)
Received: from localhost by solaria.sol.net (8.5/8.5)
	id QAA26969; Thu, 6 Feb 1997 16:18:52 -0600
From: Joe Greco <jgreco@solaria.sol.net>
Message-Id: <199702062218.QAA26969@solaria.sol.net>
Subject: Re: Audible ping response changes to ping.c
To: terry@lambert.org (Terry Lambert)
Date: Thu, 6 Feb 97 16:18:50 CST
Cc: dufault@hda.com, danny@panda.hilink.com.au, freebsd-hackers@FreeBSD.ORG
In-Reply-To: <199702062125.OAA17900@phaeton.artisoft.com> from "Terry Lambert" at Feb 6, 97 02:25:46 pm
X-Mailer: ELM [version 2.4dev PL65]
MIME-Version: 1.0
Content-Type: text
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> I was thinking of a shell script called "aping":

Uh, no... that loses as a name, at least compared to what I'd call it:

It MUST be called "bping" (think about it).

... JG

From owner-freebsd-hackers  Thu Feb  6 14:21:32 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA10550
          for hackers-outgoing; Thu, 6 Feb 1997 14:21:32 -0800 (PST)
Received: from mailgate.wasantara.net.id ([202.159.65.166])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA10506;
          Thu, 6 Feb 1997 14:21:18 -0800 (PST)
Received: from bandung.wasantara.net.id (bandung.wasantara.net.id [202.159.69.35]) by mailgate.wasantara.net.id (8.6.11/8.6.9) with ESMTP id FAA14083; Fri, 7 Feb 1997 05:28:25 +0700
Date: Fri, 7 Feb 1997 05:28:25 +0700
Received: from BANDUNG/SpoolDir by bandung.wasantara.net.id (Mercury 1.21);
    7 Feb 97 06:11:53 GMT+0700
Received: from SpoolDir by BANDUNG (Mercury 1.21); 7 Feb 97 06:11:35 GMT+0700
Received: from MurdaniDesktop by bandung.wasantara.net.id (Mercury 1.21);
    7 Feb 97 06:11:21 GMT+0700
X-Sender: eka@werty.wasantara.net.id (Unverified)
X-Mailer: Windows Eudora Light Version 1.5.2
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: freebsd-hackers@FreeBSD.org
From: Eka Kelana <eka@werty.wasantara.net.id>
Subject: Need quick answer
Cc: freebsd-bugs@FreeBSD.org, dg@root.com
Message-ID: <1522A71DB9@bandung.wasantara.net.id>
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi..

 I need a good explanation about this code in in_rmx.c:

...
        if (!rt->rt_rmx.rmx_sendpipe && !(rt->rt_rmx.rmx_locks & RTV_SPIPE))
		rt->rt_rmx.rmx_sendpipe = tcp_sendspace;
        if (!rt->rt_rmx.rmx_recvpipe && !(rt->rt_rmx.rmx_locks & RTV_RPIPE))
		rt->rt_rmx.rmx_recvpipe = tcp_recvspace;
...

because this code affect the socket buffer size (sb_hiwat) in tcp_mss()
function. 
I experienced that it wouldn't allow user program to set the socket buffer
size. The code in tcp_mss() function is:

...
#ifdef RTV_RPIPE
	if ((bufsize = rt->rt_rmx.rmx_recvpipe) == 0)
#endif
		bufsize = so->so_rcv.sb_hiwat;
...

                (void)sbreserve(&so->so_rcv, bufsize);
...

Since rt->rt_rmx.rmx_recvpipe is never zeroed (by default, it equals
tcp_sendspace), the line
bufsize = so->so_rcv.sb_hiwat is always jumped over, and tcp_mss() will set
the sb_hiwat value to bufsize.
And further, I've done a performance test. Before I commented out the four
lines in in_rmx.c above, the TCP/IP implementations showed a throughput
around 8.56 Mbps, and after I commented them out and rebuilt the kernel, it
showed a throughput around 8.61 Mbps. Well, not a significant degradation,
but the reason is still not clear to me...


-Eka Kelana-
STTTelkom
     


From owner-freebsd-hackers  Thu Feb  6 14:29:44 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA11103
          for hackers-outgoing; Thu, 6 Feb 1997 14:29:44 -0800 (PST)
Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA11096
          for <freebsd-hackers@FreeBSD.ORG>; Thu, 6 Feb 1997 14:29:39 -0800 (PST)
Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id JAA03851; Fri, 7 Feb 1997 09:28:21 +1100 (EST)
Date: Fri, 7 Feb 1997 09:28:20 +1100 (EST)
From: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
To: Joe Greco <jgreco@solaria.sol.net>
cc: Terry Lambert <terry@lambert.org>, dufault@hda.com,
        freebsd-hackers@FreeBSD.ORG
Subject: Re: Audible ping response changes to ping.c
In-Reply-To: <199702062218.QAA26969@solaria.sol.net>
Message-ID: <Pine.BSF.3.91.970207092419.427J-100000@panda.hilink.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk



On Thu, 6 Feb 1997, Joe Greco wrote:

> > I was thinking of a shell script called "aping":
> 
> Uh, no... that loses as a name, at least compared to what I'd call it:
> 
> It MUST be called "bping" (think about it).

*laugh*

Well, I can take the sed and sh alternatives as an indication that I 
should remove the -z flag from tar, but I think I'll just put the -a flag 
into ping.

Danny

From owner-freebsd-hackers  Thu Feb  6 14:56:23 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA12674
          for hackers-outgoing; Thu, 6 Feb 1997 14:56:23 -0800 (PST)
Received: from gate.lustig.com (ppp-206-170-5-60.rdcy01.pacbell.net [206.170.5.60])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA12660
          for <hackers@freebsd.org>; Thu, 6 Feb 1997 14:56:07 -0800 (PST)
Received: from Lustig.COM (devious.lustig.com [192.168.1.3]) by gate.lustig.com (8.7.6/8.7.3) with ESMTP id OAA07785; Thu, 6 Feb 1997 14:55:53 -0800 (PST)
Received: (from barry@localhost) by Lustig.COM (8.7.3/8.7.3) id OAA19219; Thu, 6 Feb 1997 14:55:54 -0800 (PST)
Message-Id: <199702062255.OAA19219@Lustig.COM>
MIME-Version: 1.0 (NeXT Mail 3.3 v118.2)
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <199702062215.QAA26943@solaria.sol.net>
X-Nextstep-Mailer: Mail 3.3 (Enhance 1.2)
Received: by NeXT.Mailer (1.118.2.RR)
From: Barry Lustig <barry@Lustig.COM>
Date: Thu,  6 Feb 97 14:55:53 -0800
To: Joe Greco <jgreco@solaria.sol.net>
Subject: Re: serial ports at 230k
cc: pst@jnx.com (Paul Traina), hackers@freebsd.org
Reply-To: barry@Lustig.COM
References: <199702062215.QAA26943@solaria.sol.net>
X-Organizations: Barry Lustig & Associates
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by freefall.freebsd.org id OAA12670
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>  > Does anyone have any experience with running 16550A's at 230kbps under
>  FreeBSD?
> Yes, I know, the driver doesn't support it currently, but has
>  anyone played?
>  
>  Yes.  Take a standard serial card and replace the 1.8432MHz crystal with
>  a 3.6864 MHz crystal..  ;-)  Your "115200" speed will magically run at
>  230.4Kbps.
>  
>  I did it a long time ago, and if you're not one for soldering, I may have
>  a pair of souped up cards if you're interested in buyin' em...  or you can
>  go get the Hayes ESP serial cards.
>  

  I know that Zyxel (www.zyxel.com) sells a 2 serial 1 parallel add-on board (16550) with the clock selectable via jumper.  It can do 1X, 2X, or 4X on the clock.  Their ISDN TAs run the DTE at up to 460800, so they needed a solution.


barry

From owner-freebsd-hackers  Thu Feb  6 15:01:04 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA12927
          for hackers-outgoing; Thu, 6 Feb 1997 15:01:04 -0800 (PST)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA12922
          for <freebsd-hackers@freebsd.org>; Thu, 6 Feb 1997 15:01:00 -0800 (PST)
Received: from rover.village.org [127.0.0.1] 
	by rover.village.org with esmtp (Exim 0.56 #1)
	id E0vscoC-0007Am-00; Thu, 6 Feb 1997 16:00:48 -0700
To: Leonard Chua <lenc@earth.infinetconsulting.com>
Subject: Re: My resignation as president of the FreeBSD Project. 
Cc: jkh@tme.cdrom.com, freebsd-hackers@freebsd.org
In-reply-to: Your message of "Thu, 06 Feb 1997 12:46:52 PST."
		<Pine.BSF.3.91.970206124524.20885A-100000@earth.infinetconsulting.com> 
References: <Pine.BSF.3.91.970206124524.20885A-100000@earth.infinetconsulting.com>  
Date: Thu, 06 Feb 1997 16:00:47 -0700
From: Warner Losh <imp@village.org>
Message-Id: <E0vscoC-0007Am-00@rover.village.org>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <Pine.BSF.3.91.970206124524.20885A-100000@earth.infinetconsulting.com> Leonard Chua writes:
: And in a couple of months, I suppose you'll be referred to as "the 
: member" :)

Hmmm, I don't know if I can say this with a strait face:

"Jordan has been a member as long as I've known him."

 :-)

Warner "and all you gotta do to join is sign it the next time it comes
around on the guitar" Losh


From owner-freebsd-hackers  Thu Feb  6 15:02:00 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA12985
          for hackers-outgoing; Thu, 6 Feb 1997 15:02:00 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA12973;
          Thu, 6 Feb 1997 15:01:43 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA18137; Thu, 6 Feb 1997 15:57:30 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702062257.PAA18137@phaeton.artisoft.com>
Subject: Re: serial ports at 230k
To: lmcsato@LMC.Ericsson.SE (Samy Touati)
Date: Thu, 6 Feb 1997 15:57:30 -0700 (MST)
Cc: terry@lambert.org, pst@jnx.com, hackers@FreeBSD.ORG, bde@FreeBSD.ORG
In-Reply-To: <199702062213.RAA02105@jello.lmc.ericsson.se> from "Samy Touati" at Feb 6, 97 05:13:54 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> So this means that if you put a 16650 UART (it's not a typo) you =
> can still use the same driver and achieve 128k
> unstead of just 115,2k ?

If you change out the clock crystal, yes.  If you don't, you only
get the clock crystal frequency, and baud rates from there down from
cutting the frequency in half for each one.

You *can* change out the clock crystal if you are into hardware
hacking; before there were MIDI cards, a lot of MIDI hackers
changed out the crystal to get MIDI speed, and then used a converter
to drive current loop (MIDI is a current loop interface).


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Thu Feb  6 15:03:49 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA13101
          for hackers-outgoing; Thu, 6 Feb 1997 15:03:49 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA13095
          for <hackers@FreeBSD.org>; Thu, 6 Feb 1997 15:03:46 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA18158; Thu, 6 Feb 1997 16:00:06 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702062300.QAA18158@phaeton.artisoft.com>
Subject: Re: fcntl, F_SETFL, O_NONBLOCK & /dev/null
To: craig@progroup.com (Craig Shaver)
Date: Thu, 6 Feb 1997 16:00:06 -0700 (MST)
Cc: hackers@FreeBSD.org
In-Reply-To: <32FA5655.3F54BC7E@progroup.com> from "Craig Shaver" at Feb 6, 97 02:08:21 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> Is there any work being done for implementing kernel threads?  I would 
> think this would be very important for a robust, real-world usable,
> thread package.

None of the patches submitted to move toward kernel multithreading
(thread reeentrancy of kernel code) have been committed by any
of the committers, so far as I know.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Thu Feb  6 15:04:49 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA13169
          for hackers-outgoing; Thu, 6 Feb 1997 15:04:49 -0800 (PST)
Received: from george.lbl.gov (george.lbl.gov [128.3.196.93])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA13156;
          Thu, 6 Feb 1997 15:04:43 -0800 (PST)
Received: (jin@localhost) by george.lbl.gov (8.6.10/8.6.5) id PAA04566; Thu, 6 Feb 1997 15:02:39 -0800
Date: Thu, 6 Feb 1997 15:02:39 -0800
From: "Jin Guojun[ITG]" <jin@george.lbl.gov>
Message-Id: <199702062302.PAA04566@george.lbl.gov>
To: hackers@freebsd.org
Subject: how to find where system hanging?
Cc: bugs@freebsd.org
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I have a ATM driver that works well under 2.1.6-RELEASE or earlier.
However, under 2.2 serial release, it gets hanging frequently.
Before 2.2-BETA, it hangs about once a day or less. Under 2.2-GAMMA,
it gets hanging very often, sometimes it hangs just after booting up.

Is there any way to force coredump when the system is hanging?
Or is there a mechanism to trace where it is hanging.
Any hints what part of the kernel changing would cause this problem.

Please help!

Thanks in advance,

-Jin

From owner-freebsd-hackers  Thu Feb  6 15:11:00 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA13553
          for hackers-outgoing; Thu, 6 Feb 1997 15:11:00 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA13544
          for <freebsd-hackers@FreeBSD.ORG>; Thu, 6 Feb 1997 15:10:54 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA18169; Thu, 6 Feb 1997 16:04:27 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702062304.QAA18169@phaeton.artisoft.com>
Subject: Re: Audible ping response changes to ping.c
To: danny@panda.hilink.com.au (Daniel O'Callaghan)
Date: Thu, 6 Feb 1997 16:04:27 -0700 (MST)
Cc: jgreco@solaria.sol.net, terry@lambert.org, dufault@hda.com,
        freebsd-hackers@FreeBSD.ORG
In-Reply-To: <Pine.BSF.3.91.970207092419.427J-100000@panda.hilink.com.au> from "Daniel O'Callaghan" at Feb 7, 97 09:28:20 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> Well, I can take the sed and sh alternatives as an indication that I 
> should remove the -z flag from tar, but I think I'll just put the -a flag 
> into ping.

The case for the z flag in tar is the installation media argument
when bootstrapping a new system to run FreeBSD for the first time.

Also, the z flag runs an external compressor/decompressor.  By that
logic, you should call an external "beep" program if you are trying to
justify adding the flag using "the "rule of similar existing practice".

8-).



					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Thu Feb  6 15:15:40 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA13778
          for hackers-outgoing; Thu, 6 Feb 1997 15:15:40 -0800 (PST)
Received: from freenet.hamilton.on.ca (0@main.freenet.hamilton.on.ca [199.212.94.65])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA13768
          for <freebsd-hackers@freebsd.org>; Thu, 6 Feb 1997 15:15:37 -0800 (PST)
Received: from james.freenet.hamilton.on.ca (james.freenet.hamilton.on.ca [199.212.94.66]) by freenet.hamilton.on.ca (8.7.5/8.7.3) with ESMTP id SAA25464; Thu, 6 Feb 1997 18:15:17 -0500 (EST)
Received: from localhost (ac199@localhost) by james.freenet.hamilton.on.ca (8.7.5/8.7.3) with SMTP id SAA12077; Thu, 6 Feb 1997 18:17:17 -0500 (EST)
X-Authentication-Warning: james.freenet.hamilton.on.ca: ac199 owned process doing -bs
Date: Thu, 6 Feb 1997 18:17:15 -0500 (EST)
From: Tim Vanderhoek <hoek@freenet.hamilton.on.ca>
To: Leonard Chua <lenc@earth.infinetconsulting.com>
cc: jkh@tme.cdrom.com, freebsd-hackers@freebsd.org
Subject: Re: My resignation as president of the FreeBSD Project. 
In-Reply-To: <Pine.BSF.3.91.970206124524.20885A-100000@earth.infinetconsulting.com>
Message-ID: <Pine.GSO.3.95.970206181426.8426A-100000@james.freenet.hamilton.on.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Thu, 6 Feb 1997, Leonard Chua wrote:

> > Actually, at this point my name changes to an obscure glyph that can
> > only be displayed in the KOI-8 font.  You can just refer to me as "the
> > core team member formerly known as the president" if it's easier.
> > 				Jordan
> 
> And in a couple of months, I suppose you'll be referred to as "the 
> member" :)

"member Jordan"  Or was that "Citizen Jordan", or should it be
"Comrade"...  ?  Uh-oh!  Next we'll have to start filtering all
messages neglecting this single title.  Now where are we headed!
;-) ;-)


--
Outnumbered?  Maybe.  Outspoken?  Never!
tIM...HOEk


From owner-freebsd-hackers  Thu Feb  6 15:16:51 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA13858
          for hackers-outgoing; Thu, 6 Feb 1997 15:16:51 -0800 (PST)
Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA13848
          for <freebsd-hackers@FreeBSD.ORG>; Thu, 6 Feb 1997 15:16:43 -0800 (PST)
Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id KAA04057; Fri, 7 Feb 1997 10:15:34 +1100 (EST)
Date: Fri, 7 Feb 1997 10:15:33 +1100 (EST)
From: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
To: Terry Lambert <terry@lambert.org>
cc: jgreco@solaria.sol.net, terry@lambert.org, dufault@hda.com,
        freebsd-hackers@FreeBSD.ORG
Subject: Re: Audible ping response changes to ping.c
In-Reply-To: <199702062304.QAA18169@phaeton.artisoft.com>
Message-ID: <Pine.BSF.3.91.970207101513.427K-100000@panda.hilink.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk



On Thu, 6 Feb 1997, Terry Lambert wrote:

> > Well, I can take the sed and sh alternatives as an indication that I 
> > should remove the -z flag from tar, but I think I'll just put the -a flag 
> > into ping.
> 
> The case for the z flag in tar is the installation media argument
> when bootstrapping a new system to run FreeBSD for the first time.
> 
> Also, the z flag runs an external compressor/decompressor.  By that
> logic, you should call an external "beep" program if you are trying to
> justify adding the flag using "the "rule of similar existing practice".

Hmmmm. :-)

Danny

From owner-freebsd-hackers  Thu Feb  6 15:17:59 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA13948
          for hackers-outgoing; Thu, 6 Feb 1997 15:17:59 -0800 (PST)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA13913;
          Thu, 6 Feb 1997 15:17:48 -0800 (PST)
Received: from current1.whistle.com (current1.whistle.com [207.76.205.22])
          by alpo.whistle.com (8.8.5/8.8.4) with SMTP
	  id PAA06651; Thu, 6 Feb 1997 15:14:48 -0800 (PST)
Message-ID: <32FA657D.446B9B3D@whistle.com>
Date: Thu, 06 Feb 1997 15:13:01 -0800
From: Julian Elischer <julian@whistle.com>
Organization: Whistle Communications
X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386)
MIME-Version: 1.0
To: Simon Shapiro <Shimon@i-Connect.Net>
CC: "Justin T. Gibbs" <gibbs@narnia.plutotech.com>,
        freebsd-hackers@freebsd.org, freebsd-scsi@freebsd.org
Subject: Re: Contigious (spelling?) allocation in kernel
References: <XFMail.970206131700.Shimon@i-Connect.Net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Simon Shapiro wrote:
> 

> All this brings me to another question.  How can I create another kernel
> thread?  What I am trying to do is have several execution threads in the
> kernel, each responsible for a given task.  All I see in the drivers I
> read so far is a single thread, associated wit hthe calling user process.
> Another thread is invoked by the interrupt handler.  I want a couple more.
> 
> One ugly way to do it is to have a ``daemon'' which makes a known system
> call (ioctl) which is never returned.  Aside from being ugly, it has a
> problem at boot time;  The daemon is not there until way after init has
> started.

you can use timeouts to get schedules kernel activity..
it's not a thread though. We don't really have kernl threads in a 
totally separate context however.

> 
> What I am after is something that could resemble the swapper.
> Linux has few of them and they become very handy.  Especially on an SMP
> machine.

well you could do what the swap daemon does.. it's started from the
kernel..
it's more a kernel PROCESS than a kernel thread.

From owner-freebsd-hackers  Thu Feb  6 15:20:02 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA14199
          for hackers-outgoing; Thu, 6 Feb 1997 15:20:02 -0800 (PST)
Received: from po1.glue.umd.edu (root@po1.glue.umd.edu [129.2.128.44])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA14144;
          Thu, 6 Feb 1997 15:19:51 -0800 (PST)
Received: from skipper.eng.umd.edu (skipper.eng.umd.edu [129.2.103.24]) by po1.glue.umd.edu (8.8.5/8.7.3) with ESMTP id SAA08074; Thu, 6 Feb 1997 18:19:32 -0500 (EST)
Received: from localhost (chuckr@localhost) by skipper.eng.umd.edu (8.8.5/8.7.3) with SMTP id SAA04597; Thu, 6 Feb 1997 18:19:31 -0500 (EST)
X-Authentication-Warning: skipper.eng.umd.edu: chuckr owned process doing -bs
Date: Thu, 6 Feb 1997 18:19:26 -0500 (EST)
From: Chuck Robey <chuckr@glue.umd.edu>
X-Sender: chuckr@skipper.eng.umd.edu
To: Bruce Evans <bde@zeta.org.au>
cc: freebsd-ports@freebsd.org, hackers@freebsd.org, imp@village.org,
        obrien@NUXI.com
Subject: Re: conditionally including <sys/param.h>
In-Reply-To: <199702062019.HAA02499@godzilla.zeta.org.au>
Message-ID: <Pine.OSF.3.95q.970206181522.4477A-100000@skipper.eng.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Fri, 7 Feb 1997, Bruce Evans wrote:

> >> >Yes, but this whole thing got started because the #ifdef __FreeBSD__
> >> >was slowly turning into
> >> >	#if defined(__OpenBSD__) || defined(__NetBSD__) || defined(__FreeBSD__)
> >> >in a bunch of places due to those projects riding along on the FreeBSD
> >> >port's coat tails.
> >> 
> >> Maybe include <sys/param.h> unconditionally?  I'm not sure why I mentioned
> >> the __FreeBSD__ ifdef above.  I've never liked ifdefing on the OS -
> >> it isn't necessary for one OS and gives too-large ifdefs for more than
> >> 2 OS's.  You'll still need large ifdefs if configuration depends on the
> >> value of `BSD' and the value is OS-dependent.
> >
> >No, that wouldn't work.  We're talking about something we'd ask authors of
> >packages that weren't written for FreeBSD to include (and to include for
> >NetBSD and OpenBSD) to get their packages to work with ours.  This isn't
> 
> But they certainly should accept anything with __FooBSD__ or BSD >= mmm
> or __FooBSD_version >= nnn.  That would give 100-line ifdefs to support
> 100 OS's.  It's also useless for communicating what is different in
> FooBSD.

I don't disagree, I'm just saying that flatly including sys/param.h with
no qualifiers means that it will be a fatal error on any machine that
doesn't have a sys/param.h, so that's not acceptable.

The stuff I heard about detecting __unix__ or unix is equally useless,
because such a test passes on all unixes, whether or not there is a
sys/param.h existing or not.  The test we finally recommend has to be
non-fatal in nature to systems without sys/param.h.  The method I suggest
above is messy, but (and _please_ correct me if I'm wrong) it has the sole
benefit of being the only one I've seen that is non-fatal on systems that
don't have a sys/param.h.

> 
> Bruce
> 

----------------------------+-----------------------------------------------
Chuck Robey                 | Interests include any kind of voice or data 
chuckr@eng.umd.edu          | communications topic, C programming, and Unix.
9120 Edmonston Ct #302      |
Greenbelt, MD 20770         | I run Journey2 and picnic, both FreeBSD
(301) 220-2114              | version 3.0 current -- and great FUN!
----------------------------+-----------------------------------------------


From owner-freebsd-hackers  Thu Feb  6 15:33:18 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA14914
          for hackers-outgoing; Thu, 6 Feb 1997 15:33:18 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA14909
          for <freebsd-hackers@freebsd.org>; Thu, 6 Feb 1997 15:33:15 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA19042; Thu, 6 Feb 1997 16:29:25 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702062329.QAA19042@phaeton.artisoft.com>
Subject: Re: My resignation as president of the FreeBSD Project.
To: imp@village.org (Warner Losh)
Date: Thu, 6 Feb 1997 16:29:25 -0700 (MST)
Cc: lenc@earth.infinetconsulting.com, jkh@tme.cdrom.com,
        freebsd-hackers@freebsd.org
In-Reply-To: <E0vscoC-0007Am-00@rover.village.org> from "Warner Losh" at Feb 6, 97 04:00:47 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> : And in a couple of months, I suppose you'll be referred to as "the 
> : member" :)
> 
> Hmmm, I don't know if I can say this with a strait face:
> 
> "Jordan has been a member as long as I've known him."
> 
>  :-)
> 
> Warner "and all you gotta do to join is sign it the next time it comes
> around on the guitar" Losh

Probably, but can you say it with a straight face?


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Thu Feb  6 15:33:38 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA14935
          for hackers-outgoing; Thu, 6 Feb 1997 15:33:38 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA14929
          for <freebsd-hackers@FreeBSD.ORG>; Thu, 6 Feb 1997 15:33:36 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA19017; Thu, 6 Feb 1997 16:27:28 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702062327.QAA19017@phaeton.artisoft.com>
Subject: Re: Audible ping response changes to ping.c
To: danny@panda.hilink.com.au (Daniel O'Callaghan)
Date: Thu, 6 Feb 1997 16:27:28 -0700 (MST)
Cc: terry@lambert.org, jgreco@solaria.sol.net, dufault@hda.com,
        freebsd-hackers@FreeBSD.ORG
In-Reply-To: <Pine.BSF.3.91.970207101513.427K-100000@panda.hilink.com.au> from "Daniel O'Callaghan" at Feb 7, 97 10:15:33 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > > Well, I can take the sed and sh alternatives as an indication that I 
> > > should remove the -z flag from tar, but I think I'll just put the -a flag 
> > > into ping.
> > 
> > The case for the z flag in tar is the installation media argument
> > when bootstrapping a new system to run FreeBSD for the first time.
> > 
> > Also, the z flag runs an external compressor/decompressor.  By that
> > logic, you should call an external "beep" program if you are trying to
> > justify adding the flag using "the "rule of similar existing practice".
> 
> Hmmmm. :-)


Here is a revised version that transparently provides a "-a" option
to the real ping command without adding it to the real ping command:


#!/bin/sh
#
# bping.sh	first version was "aping.sh".  8-).
#
# To use:
#		mv /sbin/ping /sbin/ping.real
#		mv bping.sh /sbin/ping
#		chmod 555 /sbin/ping
#
ARGS=""
BEEP=no
PING=ping.real

# find -a, if specified
while test "x$1" != "x"
do
	if test "x$1" = "x-a"
	then
		BEEP=yes
	else
		ARGS="$ARGS $1"
	fi
	shift
done

# run the beep or non-beep version
if test "$BEEP" = "yes"
then
	$PING $ARGS | while read x
	do
		echo "$x"
	done
	exit $?
else
	$PING $ARGS
	exit $?
fi
# EOF: not reached


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Thu Feb  6 15:40:37 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA15408
          for hackers-outgoing; Thu, 6 Feb 1997 15:40:37 -0800 (PST)
Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA15388;
          Thu, 6 Feb 1997 15:40:30 -0800 (PST)
Received: from narnia (localhost [127.0.0.1]) by narnia.plutotech.com (8.8.5/8.7.3) with ESMTP id PAA02385; Thu, 6 Feb 1997 15:40:13 -0800 (PST)
Message-Id: <199702062340.PAA02385@narnia.plutotech.com>
To: Simon Shapiro <Shimon@i-Connect.Net>
cc: "John S. Dyson" <toor@dyson.iquest.net>, freebsd-hackers@FreeBSD.ORG,
        freebsd-scsi@FreeBSD.ORG
Subject: Re: Contigious (spelling?) allocation in kernel 
In-reply-to: Your message of "Thu, 06 Feb 1997 09:55:40 PST."
             <XFMail.970206131700.Shimon@i-Connect.Net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 06 Feb 1997 15:40:13 -0800
From: "Justin T. Gibbs" <gibbs@narnia.plutotech.com>
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>
>Hi John S. Dyson;  On 06-Feb-97 you wrote: 
>
>> Take a look at contigmalloc() or vm_page_alloc_contig()
>> as defined in /sys/vm/vm_page.c.  These are almost
>> guaranteed NOT to work after the system is fully up.
>
>Thanx.
>
>If you (or someone else) please elaborate on the last sentence,
>please...

Contigmalloc is only guaranteed to work when lots of physical memory
is availible to allocate.  It works a little bit to try to kick stuff
around to make contiguous regions, but to rely on it working all the
time to satisfy your allocation would be deadly.

>I can re-structure the driver a bit (make it more risky), to 
>avoid the need for large contigious blocks, but the (obvious)
>question is:  Does the kernel malloc guarantee that allocations
>smaller than (or equal to) a page are in the same page?

Yes.  A single virtual page always maps to a single physical page.
You must use contigmalloc if you cross page boundaries.

>Having a page or less, limits the Scatter/Gather operations in
>the kernel, for most hardware, to 512 entries (segments).  
>Under high fragmentation, this can result in 256KB-2MB floating
>limit.

Actually, it gives you a floating limit between 2MB->2048GB unless you
are talking about sending things that are not contiguous in the virtual
address space and the granualiry of discontinuity is smaller than a page
size.

>While not a problem for most applications (mine
>included), it is still a limit that is not absolutely necessary.

If you need the space, allocate it up front with contigmalloc.  Contigmalloc
may someday be enhanced to succeed always if physical memory isn't exhausted,
but the cost of such an operation under heavy load is extremely high, so
you wouldn't want to use it often anyway (especially not if you had even
lose real-time constraints).

>Any opposing opinions (before I re-code the darn thing :-)?

You should talk to John Dyson about anything you want to do to contigmalloc.
The VM system is not your standard meat and potatoes and since John has already
done some work on enhancing contigmalloc, he's the expert in this area.

>BACKGROUND:  One of my engineers, who is heavily involved in 
>Linux SCSI development is strongly opposed to calling malloc on
>demand in a device driver.  He quotes heavy performance
>penalties, and worse;  Failure (under heavy load) to obtain the
>memory when needed.

Malloc will always succeed in FreeBSD if you can sleep and have not run out
of physical memory.  The problem is that you don't always have a process
context to sleep on (say your in an interrupt handler).  In the new CAM based
architecture, this isn't a problem since instead of sleeping in the driver
when you run out of resources for some reason, you simply put the request back
into the queue for a retry later.  That retry will either use a resource that
was freed by another transaction completing or its malloc call will succeed
without any waiting involved.  This assumes, of course, that you have
pre-filled your pool with enough resources for the minimal level of performance
so that a failure to malloc every once in a while isn't that big of a deal.
Malloc in the FreeBSD kernel is fairly fast too.

>Thanx, Simon

--
Justin T. Gibbs
===========================================
  FreeBSD: Turning PCs into workstations
===========================================



From owner-freebsd-hackers  Thu Feb  6 15:56:45 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA16085
          for hackers-outgoing; Thu, 6 Feb 1997 15:56:45 -0800 (PST)
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA16071
          for <hackers@freebsd.org>; Thu, 6 Feb 1997 15:56:42 -0800 (PST)
Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98])
          by who.cdrom.com (8.7.5/8.6.11) with ESMTP id PAA19385
          for <hackers@freebsd.org>; Thu, 6 Feb 1997 15:56:12 -0800 (PST)
Received: from ntws (ntws.etinc.com [204.141.95.142]) by etinc.com (8.8.3/8.6.9) with SMTP id SAA03475; Thu, 6 Feb 1997 18:58:00 -0500 (EST)
Message-Id: <3.0.32.19970206185434.00b95db0@etinc.com>
X-Sender: dennis@etinc.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Thu, 06 Feb 1997 18:54:36 -0500
To: barry@Lustig.COM
From: dennis <dennis@etinc.com>
Subject: Re: serial ports at 230k
Cc: hackers@freebsd.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

At 02:55 PM 2/6/97 -0800, you wrote:
>>  > Does anyone have any experience with running 16550A's at 230kbps under
>>  FreeBSD?
>> Yes, I know, the driver doesn't support it currently, but has
>>  anyone played?
>>  
>>  Yes.  Take a standard serial card and replace the 1.8432MHz crystal with
>>  a 3.6864 MHz crystal..  ;-)  Your "115200" speed will magically run at
>>  230.4Kbps.
>>  
>>  I did it a long time ago, and if you're not one for soldering, I may have
>>  a pair of souped up cards if you're interested in buyin' em...  or you can
>>  go get the Hayes ESP serial cards.
>>  
>
>  I know that Zyxel (www.zyxel.com) sells a 2 serial 1 parallel add-on
board (16550) with the clock selectable via jumper.  It can do 1X, 2X, or
4X on the clock.  Their ISDN TAs run the DTE at up to 460800, so they
needed a solution.

The RS-232 designers are turning in their graves about now......

db

From owner-freebsd-hackers  Thu Feb  6 16:18:37 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id QAA17159
          for hackers-outgoing; Thu, 6 Feb 1997 16:18:37 -0800 (PST)
Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA17152
          for <freebsd-hackers@FreeBSD.ORG>; Thu, 6 Feb 1997 16:18:29 -0800 (PST)
Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id LAA04349; Fri, 7 Feb 1997 11:17:32 +1100 (EST)
Date: Fri, 7 Feb 1997 11:17:31 +1100 (EST)
From: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
To: Terry Lambert <terry@lambert.org>
cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: Audible ping response changes to ping.c
In-Reply-To: <199702062327.QAA19017@phaeton.artisoft.com>
Message-ID: <Pine.BSF.3.91.970207111513.427L-100000@panda.hilink.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk



On Thu, 6 Feb 1997, Terry Lambert wrote:

> > > Also, the z flag runs an external compressor/decompressor.  By that
> > > logic, you should call an external "beep" program if you are trying to
> > > justify adding the flag using "the "rule of similar existing practice".
> > 
> > Hmmmm. :-)
> 
> 
> Here is a revised version that transparently provides a "-a" option
> to the real ping command without adding it to the real ping command:

Thanks, Terry, are you going to submit a man page?

Danny

From owner-freebsd-hackers  Thu Feb  6 16:20:38 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id QAA17280
          for hackers-outgoing; Thu, 6 Feb 1997 16:20:38 -0800 (PST)
Received: from sax.sax.de (sax.sax.de [193.175.26.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id QAA17275
          for <freebsd-hackers@freebsd.org>; Thu, 6 Feb 1997 16:20:34 -0800 (PST)
Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id BAA13627 for freebsd-hackers@freebsd.org; Fri, 7 Feb 1997 01:20:32 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id BAA10525; Fri, 7 Feb 1997 01:02:38 +0100 (MET)
Message-ID: <Mutt.19970207010238.j@uriah.heep.sax.de>
Date: Fri, 7 Feb 1997 01:02:38 +0100
From: j@uriah.heep.sax.de (J Wunsch)
To: freebsd-hackers@freebsd.org (FreeBSD hackers)
Subject: Re: What happened to the splash screen?
References: <199702060507.AAA26461@lakes.water.net>
X-Mailer: Mutt 0.55-PL10
Mime-Version: 1.0
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <199702060507.AAA26461@lakes.water.net>; from Thomas David Rivers on Feb 6, 1997 00:07:36 -0500
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

As Thomas David Rivers wrote:

>  Seems fine to me...  I just wanted to make sure we didn't loose
> support for the monochrome, or serial consoles just to get some color
> up there - but that's covered.

No worries. :-)

My scratchbox is using a Hercules monitor, so i will complain loudly
if something breaks there.  And i know of various sites that depend on
the serial consoles.

I would even be tempted to do a stab at serial console installation,
but i still need a good idea how to `switch screens' there.  You know,
we need 4 different screens that can be switched, one for the menus,
one for debug & console messages, one for the EHS, and one for PPP.

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

From owner-freebsd-hackers  Thu Feb  6 16:20:53 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id QAA17336
          for hackers-outgoing; Thu, 6 Feb 1997 16:20:53 -0800 (PST)
Received: from sax.sax.de (sax.sax.de [193.175.26.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id QAA17325
          for <freebsd-hackers@FreeBSD.ORG>; Thu, 6 Feb 1997 16:20:49 -0800 (PST)
Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id BAA13634; Fri, 7 Feb 1997 01:20:37 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id AAA10492; Fri, 7 Feb 1997 00:53:45 +0100 (MET)
Message-ID: <Mutt.19970207005345.j@uriah.heep.sax.de>
Date: Fri, 7 Feb 1997 00:53:45 +0100
From: j@uriah.heep.sax.de (J Wunsch)
To: gabor@acm.org (Gabor Kincses)
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: Panic in probe, but no dump
References: <32FA29A1.41C67EA6@acm.org>
X-Mailer: Mutt 0.55-PL10
Mime-Version: 1.0
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <32FA29A1.41C67EA6@acm.org>; from Gabor Kincses on Feb 6, 1997 12:57:37 -0600
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

(Mailing lists trimmed.  Whenever you feel like posting to more than
one list, you probably feel wrong. ;-)

As Gabor Kincses wrote:

> The problem I have is to get a dump out of the sound driver probe.  I
> pretty much followed the handbook on this.  I have set config root on
> wd2 dumps on wd2 in my config file, but no dump occurred (I checked .  I

Well, the normal sequence is to use `dumpon'.  This is also supported
by /etc/sysconfig.

> 1. Is there a way to load the kernel.debug in gdb and correlate
> addresses with lines of code?  (Like on HP-UX w/ xdb: one can use 'td')

Basically, though a little hard.  Please, read the section about
kernel debugging in the handbook (gdb -k aka. kgdb).

> 2. Why am I not getting a core dump?

No idea.  What did the kernel say?  Did it say ``dumping to ...''?

> save the kernel core, or is it already on the swap device?  Ie. what
> macroscopic events would tell me that I got a dump?  (Possibly: "core
> dumped" msg on the console :-)

Almost.  Dumping to dev ...., followed by the number of outstanding
megabytes to be dumped.

> 3. I have turned on savecore in /etc/sysconfig, but I have noticed that
> the swapon gets executed first in /etc/rc before the savecore.  Wouldn't
> this wipe out a core in the swap device?

No.  The dump is done to the end of the swap partition.

> 5. Is my only option left is ddb?

Your best one.  Note that you can also force a dump from within DDB by
saying `panic' (followed by `c').

> 6. Is a page fault essentially like a segmentation violation in user
> mode?  AFAIK on i386 you have to install a page fault handler, which is
> probably what the VM is all about.  Is this true?

Well, basically.  A page fault normally tries to see if it has to load
a page from secondary storage.  If there's no page to load, it will be
reported.  By a SIGSEGV to a user process, by a panic (or a jump into
DDB) in the kernel.

> 7. Why is the "dumps on" feature being deprecated?  How else can we get
> a dump if the system crashes before dumpon can be executed?  BTW, My

That's where you need `dumps on'.  Apart from this, it's deprecated
since it requires a kernel modfication while dumpon(8) doesn't.

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

From owner-freebsd-hackers  Thu Feb  6 16:21:24 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id QAA17360
          for hackers-outgoing; Thu, 6 Feb 1997 16:21:24 -0800 (PST)
Received: from sax.sax.de (sax.sax.de [193.175.26.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id QAA17354;
          Thu, 6 Feb 1997 16:21:18 -0800 (PST)
Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id BAA13648; Fri, 7 Feb 1997 01:21:12 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id AAA10513; Fri, 7 Feb 1997 00:56:33 +0100 (MET)
Message-ID: <Mutt.19970207005633.j@uriah.heep.sax.de>
Date: Fri, 7 Feb 1997 00:56:33 +0100
From: j@uriah.heep.sax.de (J Wunsch)
To: jin@george.lbl.gov (Jin Guojun[ITG])
Cc: hackers@freebsd.org, bugs@freebsd.org
Subject: Re: how to find where system hanging?
References: <199702062302.PAA04566@george.lbl.gov>
X-Mailer: Mutt 0.55-PL10
Mime-Version: 1.0
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <199702062302.PAA04566@george.lbl.gov>; from Jin Guojun[ITG] on Feb 6, 1997 15:02:39 -0800
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

As Jin Guojun[ITG] wrote:

> Is there any way to force coredump when the system is hanging?
> Or is there a mechanism to trace where it is hanging.

Configure DDB, and see whether the hotkey will still work.  If it
doesn't, it's probably jamming the system with interrupts disabled.
(You could hook a pushbutton to the IOCHCK signal on the ISA bus,
which will generate an NMI.  That should be a condition fatal enough
to go into DDB.)

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

From owner-freebsd-hackers  Thu Feb  6 16:40:50 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id QAA18370
          for hackers-outgoing; Thu, 6 Feb 1997 16:40:50 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id QAA18359
          for <freebsd-hackers@FreeBSD.ORG>; Thu, 6 Feb 1997 16:40:45 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA19187; Thu, 6 Feb 1997 17:36:58 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199702070036.RAA19187@phaeton.artisoft.com>
Subject: Re: Audible ping response changes to ping.c
To: danny@panda.hilink.com.au (Daniel O'Callaghan)
Date: Thu, 6 Feb 1997 17:36:58 -0700 (MST)
Cc: terry@lambert.org, freebsd-hackers@FreeBSD.ORG
In-Reply-To: <Pine.BSF.3.91.970207111513.427L-100000@panda.hilink.com.au> from "Daniel O'Callaghan" at Feb 7, 97 11:17:31 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > > > Also, the z flag runs an external compressor/decompressor.  By that
> > > > logic, you should call an external "beep" program if you are trying to
> > > > justify adding the flag using "the "rule of similar existing practice".
> > > 
> > > Hmmmm. :-)
> > 
> > 
> > Here is a revised version that transparently provides a "-a" option
> > to the real ping command without adding it to the real ping command:
> 
> Thanks, Terry, are you going to submit a man page?

How do you automatically invoke "sed" when someone types "man" to
preprocess a man page?  8-) 8-).


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

From owner-freebsd-hackers  Thu Feb  6 17:07:07 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA19639
          for hackers-outgoing; Thu, 6 Feb 1997 17:07:07 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA19616;
          Thu, 6 Feb 1997 17:07:00 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id JAA06777; Fri, 7 Feb 1997 09:45:47 +1100
Date: Fri, 7 Feb 1997 09:45:47 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199702062245.JAA06777@godzilla.zeta.org.au>
To: Shimon@i-Connect.Net, toor@dyson.iquest.net
Subject: Re: Contigious (spelling?) allocation in kernel
Cc: freebsd-hackers@freebsd.org, freebsd-scsi@freebsd.org
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>> Take a look at contigmalloc() or vm_page_alloc_contig()
>> as defined in /sys/vm/vm_page.c.  These are almost
>> guaranteed NOT to work after the system is fully up.
>...
>If you (or someone else) please elaborate on the last sentence,
>please...

Physical memory gets fragmented after the system has been running
for a little while, so the chance of finding N physically contiguous
is small if N > 1.

>question is:  Does the kernel malloc guarantee that allocations
>smaller than (or equal to) a page are in the same page?

Yes.

>BACKGROUND:  One of my engineers, who is heavily involved in 
>Linux SCSI development is strongly opposed to calling malloc on
>demand in a device driver.  He quotes heavy performance
>penalties, and worse;  Failure (under heavy load) to obtain the
>memory when needed.

Good advice.  The performance penalties for nonblocking mallocs
aren't large under FreeBSD, except when you allocate pages that
would be better used for something else, but failure (under not
so heavy load) is likely if you attempt to allocate more than a
page or two.

Bruce

From owner-freebsd-hackers  Thu Feb  6 17:07:11 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA19657
          for hackers-outgoing; Thu, 6 Feb 1997 17:07:11 -0800 (PST)
Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id RAA19636
          for <hackers@FreeBSD.org>; Thu, 6 Feb 1997 17:07:06 -0800 (PST)
Received: from godzilla.zeta.org.au by agora.rdrop.com with smtp
	(Smail3.1.29.1 #17) id m0vsem9-0008zHC; Thu, 6 Feb 97 17:06 PST
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id IAA05338; Fri, 7 Feb 1997 08:40:19 +1100
Date: Fri, 7 Feb 1997 08:40:19 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199702062140.IAA05338@godzilla.zeta.org.au>
To: bde@zeta.org.au, terry@lambert.org
Subject: Re: DOS partition trouble
Cc: durham@w2xo.pgh.pa.us, hackers@FreeBSD.org
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>> For SCSI disks with at least ncr controllers, this could be caused
>> a DOS partition that ends on a cylinder boundary and FreeBSD partition
>> that doesn't.  When you remove the DOS partition, the controller's BIOS
>> will have problems determining the disk geometry.
>
>What?  The BIOS examines the disk to get the geometry?
>
>How do you put something on the disk in the first place, then?

For disks with a nonexistent or empty partition table, the BIOS
chooses a default (one with <= 1024 cylinders if possible.  This is
always possible for disks with < 63*255*1024 sectors).

>I was under the impression that fictitious geometry was *always*
>an artifact of the BIOS's idea of geometry, not the oter way around.

That would usually fail for disks partitioned under another BIOS,
especially under an old BIOS with a limited number of defaults.

Bruce

From owner-freebsd-hackers  Thu Feb  6 18:13:08 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id SAA23085
          for hackers-outgoing; Thu, 6 Feb 1997 18:13:08 -0800 (PST)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA23078;
          Thu, 6 Feb 1997 18:12:57 -0800 (PST)
Received: from current1.whistle.com (current1.whistle.com [207.76.205.22])
          by alpo.whistle.com (8.8.5/8.8.4) with SMTP
	  id SAA10595; Thu, 6 Feb 1997 18:07:23 -0800 (PST)
Message-ID: <32FA8DF0.3F54BC7E@whistle.com>
Date: Thu, 06 Feb 1997 18:05:36 -0800
From: Julian Elischer <julian@whistle.com>
Organization: Whistle Communications
X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386)
MIME-Version: 1.0
To: Paul Traina <pst@jnx.com>
CC: hackers@freebsd.org, bde@freebsd.org
Subject: Re: serial ports at 230k
References: <199702061952.LAA26214@red.jnx.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Paul Traina wrote:
> 
> Does anyone have any experience with running 16550A's at 230kbps under FreeBSD?
> Yes, I know, the driver doesn't support it currently, but has anyone played?

yes 
I've played but the hard part is getting the hardware..

you need to add a second "mode" to sio.c
that allow it to use a second baud rate table
and somewhere you have to kick the io ports of the device to 
do whatever is needed to make it run in turbo mode..
this is usually machine dependent.

From owner-freebsd-hackers  Thu Feb  6 18:14:47 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id SAA23154
          for hackers-outgoing; Thu, 6 Feb 1997 18:14:47 -0800 (PST)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA23147;
          Thu, 6 Feb 1997 18:14:39 -0800 (PST)
Received: from current1.whistle.com (current1.whistle.com [207.76.205.22])
          by alpo.whistle.com (8.8.5/8.8.4) with SMTP
	  id SAA10621; Thu, 6 Feb 1997 18:09:03 -0800 (PST)
Message-ID: <32FA8E54.FF6D5DF@whistle.com>
Date: Thu, 06 Feb 1997 18:07:16 -0800
From: Julian Elischer <julian@whistle.com>
Organization: Whistle Communications
X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386)
MIME-Version: 1.0
To: Paul Traina <pst@jnx.com>
CC: Bruce Evans <bde@zeta.org.au>, hackers@freebsd.org, bde@freebsd.org
Subject: Re: serial ports at 230k
References: <199702062052.MAA00639@base.jnx.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Paul Traina wrote:
> 
> Good guess, but I'm actually trying out a 3COM ISDN TA that runs at 230k.
> 
>   From: Bruce Evans <bde@zeta.org.au>
>   Subject: Re: serial ports at 230k
>   >Does anyone have any experience with running 16550A's at 230kbps under FreeB
> >>SD?
>   >Yes, I know, the driver doesn't support it currently, but has anyone played?
> 
>   Not me.  I checked the PC16550D specs recently.  The maximum speed is
>   1.5Mbps like I remembered.
> 
>   If you only care about remote gdb throughput to an sio port on a
>   FreeBSD host, note that the protocol is non-streaming so it is limited
>   to 1 packet per clock tick (30Kbps effective throughput at best) by the
>   host's pseudo-DMA timeout routine.
> 
>   Bruce
exactly why I was looking at it
(3COM impact)

From owner-freebsd-hackers  Thu Feb  6 19:06:26 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA26011
          for hackers-outgoing; Thu, 6 Feb 1997 19:06:26 -0800 (PST)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA26005
          for <hackers@freebsd.org>; Thu, 6 Feb 1997 19:06:20 -0800 (PST)
Received: from current1.whistle.com (current1.whistle.com [207.76.205.22])
          by alpo.whistle.com (8.8.5/8.8.4) with SMTP
	  id TAA11820 for <hackers@freebsd.org>; Thu, 6 Feb 1997 19:04:24 -0800 (PST)
Message-ID: <32FA9B4C.41C67EA6@whistle.com>
Date: Thu, 06 Feb 1997 19:02:36 -0800
From: Julian Elischer <julian@whistle.com>
Organization: Whistle Communications
X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386)
MIME-Version: 1.0
To: hackers@freebsd.org
Subject: barracuda jumbers?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

anyone have a good ref on this?
they shipped me one with a hawk manual (!?)


julian

From owner-freebsd-hackers  Thu Feb  6 19:15:26 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA26593
          for hackers-outgoing; Thu, 6 Feb 1997 19:15:26 -0800 (PST)
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA26568
          for <hackers@FreeBSD.ORG>; Thu, 6 Feb 1997 19:15:21 -0800 (PST)
Received: from aries.bb.cc.wa.us (root@[208.8.136.11])
          by who.cdrom.com (8.7.5/8.6.11) with ESMTP id TAA19989
          for <hackers@FreeBSD.ORG>; Thu, 6 Feb 1997 19:00:07 -0800 (PST)
Received: from localhost (chris@localhost) by aries.bb.cc.wa.us (8.8.3/8.6.9) with SMTP id SAA24478; Thu, 6 Feb 1997 18:53:01 -0800 (PST)
Date: Thu, 6 Feb 1997 18:53:01 -0800 (PST)
From: Chris Coleman <chris@bb.cc.wa.us>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: Mark Mayo <mark@quickweb.com>, Julian Elischer <julian@whistle.com>,
        Terry Lambert <terry@lambert.org>, mcgovern@spoon.beta.com,
        msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG
Subject: Re:My Book Project (was: Constructive criticism)
In-Reply-To: <19062.854750336@time.cdrom.com>
Message-ID: <Pine.NEB.3.94.970206184120.24413E-100000@aries.bb.cc.wa.us>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

I have put together a Table of Contents for the Book I am working on. I
had posted a tenative one earlier, now I have made some changes to it and
I think it is ready for open criticism. (Just the Table of Contents) I
have tried to collect all the topics that I had a hard time with over the
last two years of my FreeBSD experience.  I am gearing this towards those
who have relativly no UNIX experience, please keep that in mind when you
look this over.  I feel that more New-To-Unix people are going to be
running FreeBSD to solve network problems as they learn about us, and as
we make the knowledge more accessable to them.

I am looking for constructive criticism, Please check to see that I have:

	1) things in a progressive order.
	2) Included the major stumbling blocks you went though
	3) Am not being too redundant with other published material.

If you criticize anything besides the TOC, please email that to me
personally, and not to the list.  I would like to recieve helpful info
about the rest of the book, but I plan to post a letter like this for each
chapter as I have them ready.  However feel free to email me about any
concern.

Thanks

Christopher J. Coleman (chris@aries.bb.cc.wa.us)
Computer Support Technician I  (509)-766-8873
Big Bend Community College  Internet Instructor
FreeBSD Book Project:  http://www.bb.cc.wa.us/~chris/book.html
Death is life's way of telling you you're fired.


From owner-freebsd-hackers  Thu Feb  6 19:16:12 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA26769
          for hackers-outgoing; Thu, 6 Feb 1997 19:16:12 -0800 (PST)
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA26748;
          Thu, 6 Feb 1997 19:16:07 -0800 (PST)
Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120])
          by who.cdrom.com (8.7.5/8.6.11) with ESMTP id SAA19884
          ; Thu, 6 Feb 1997 18:39:06 -0800 (PST)
Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id NAA09135; Fri, 7 Feb 1997 13:08:13 +1030 (CST)
From: Michael Smith <msmith@atrad.adelaide.edu.au>
Message-Id: <199702070238.NAA09135@genesis.atrad.adelaide.edu.au>
Subject: Re: Contigious (spelling?) allocation in kernel
In-Reply-To: <XFMail.970206131700.Shimon@i-Connect.Net> from Simon Shapiro at "Feb 6, 97 09:55:40 am"
To: Shimon@i-Connect.Net (Simon Shapiro)
Date: Fri, 7 Feb 1997 13:08:12 +1030 (CST)
Cc: toor@dyson.iquest.net, freebsd-hackers@FreeBSD.ORG,
        freebsd-scsi@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Simon Shapiro stands accused of saying:
> 
> > Take a look at contigmalloc() or vm_page_alloc_contig()
> > as defined in /sys/vm/vm_page.c.  These are almost
> > guaranteed NOT to work after the system is fully up.
> 
> Thanx.
> 
> If you (or someone else) please elaborate on the last sentence,
> please...

Er, from my understanding the kva space tends to become fragmented, and
your chances of being able to allocate contiguous memory tend to
be reduced.

> I can re-structure the driver a bit (make it more risky), to 
> avoid the need for large contigious blocks, but the (obvious)
> question is:  Does the kernel malloc guarantee that allocations
> smaller than (or equal to) a page are in the same page?

Can't answer that, sorry.  Look at the source 8)

> Having a page or less, limits the Scatter/Gather operations in
> the kernel, for most hardware, to 512 entries (segments).  
> Under high fragmentation, this can result in 256KB-2MB floating
> limit.  While not a problem for most applications (mine
> included), it is still a limit that is not absolutely necessary.

TBH, a 256K I/O is likely to be bigger than most peripherals can do
anything useful with.  I would be inclined to say that the 
overhead of splitting that into seperate transactions is likely
to be small compared with the size of the transaction.

> BACKGROUND:  One of my engineers, who is heavily involved in 
> Linux SCSI development is strongly opposed to calling malloc on
> demand in a device driver.  He quotes heavy performance
> penalties, and worse;  Failure (under heavy load) to obtain the
> memory when needed.

They're right on the ball; avoid allocating memory on the fly wherever
possible. 8)

> Thanx, Simon

-- 
]] Mike Smith, Software Engineer        msmith@gsoft.com.au             [[
]] Genesis Software                     genesis@gsoft.com.au            [[
]] High-speed data acquisition and      (GSM mobile)     0411-222-496   [[
]] realtime instrument control.         (ph)          +61-8-8267-3493   [[
]] Unix hardware collector.             "Where are your PEZ?" The Tick  [[

From owner-freebsd-hackers  Thu Feb  6 19:16:21 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA26820
          for hackers-outgoing; Thu, 6 Feb 1997 19:16:21 -0800 (PST)
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA26742;
          Thu, 6 Feb 1997 19:16:05 -0800 (PST)
Received: from red.jnx.com (red.jnx.com [208.197.169.254])
          by who.cdrom.com (8.7.5/8.6.11) with ESMTP id SAA19756
          ; Thu, 6 Feb 1997 18:17:12 -0800 (PST)
Received: from base.jnx.com (base.jnx.com [208.197.169.238]) by red.jnx.com (8.8.5/8.8.3) with ESMTP id SAA16403; Thu, 6 Feb 1997 18:16:40 -0800 (PST)
Received: from base.jnx.com (localhost.jnx.com [127.0.0.1]) by base.jnx.com (8.7.6/8.7.3) with ESMTP id SAA01990; Thu, 6 Feb 1997 18:16:40 -0800 (PST)
Message-Id: <199702070216.SAA01990@base.jnx.com>
To: Julian Elischer <julian@whistle.com>
cc: hackers@FreeBSD.ORG, bde@FreeBSD.ORG
Subject: Re: serial ports at 230k 
In-reply-to: Your message of "Thu, 06 Feb 1997 18:05:36 PST."
             <32FA8DF0.3F54BC7E@whistle.com> 
Date: Thu, 06 Feb 1997 18:16:40 -0800
From: Paul Traina <pst@jnx.com>
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


  From: Julian Elischer <julian@whistle.com>
  Subject: Re: serial ports at 230k
  Paul Traina wrote:
  > 
  > Does anyone have any experience with running 16550A's at 230kbps under Free
>>BSD?
  > Yes, I know, the driver doesn't support it currently, but has anyone played
>>?
  
  yes 
  I've played but the hard part is getting the hardware..

Getting?  I haven't seen mention of special hardware in /any/ docs. Sigh.
  
  you need to add a second "mode" to sio.c
  that allow it to use a second baud rate table
  and somewhere you have to kick the io ports of the device to 
  do whatever is needed to make it run in turbo mode..
  this is usually machine dependent.

From owner-freebsd-hackers  Thu Feb  6 19:16:27 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA26848
          for hackers-outgoing; Thu, 6 Feb 1997 19:16:27 -0800 (PST)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA26822
          for <hackers@freebsd.org>; Thu, 6 Feb 1997 19:16:22 -0800 (PST)
Received: from current1.whistle.com (current1.whistle.com [207.76.205.22])
          by alpo.whistle.com (8.8.5/8.8.4) with SMTP
	  id TAA11952 for <hackers@freebsd.org>; Thu, 6 Feb 1997 19:13:06 -0800 (PST)
Message-ID: <32FA9D56.167EB0E7@whistle.com>
Date: Thu, 06 Feb 1997 19:11:18 -0800
From: Julian Elischer <julian@whistle.com>
Organization: Whistle Communications
X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386)
MIME-Version: 1.0
To: hackers@freebsd.org
Subject: PD PDF viewer? was: barracuda jumpers 
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

so I found the jumper info at www.seagate.com (should have
thought of that) 

but it's all in PDF..

so what was the PD program that could do pdf?

I know it's one of them, but which?

From owner-freebsd-hackers  Thu Feb  6 19:31:34 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA27890
          for hackers-outgoing; Thu, 6 Feb 1997 19:31:34 -0800 (PST)
Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA27885
          for <hackers@FreeBSD.ORG>; Thu, 6 Feb 1997 19:31:28 -0800 (PST)
Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id OAA09868; Fri, 7 Feb 1997 14:01:20 +1030 (CST)
From: Michael Smith <msmith@atrad.adelaide.edu.au>
Message-Id: <199702070331.OAA09868@genesis.atrad.adelaide.edu.au>
Subject: Re: barracuda jumbers?
In-Reply-To: <32FA9B4C.41C67EA6@whistle.com> from Julian Elischer at "Feb 6, 97 07:02:36 pm"
To: julian@whistle.com (Julian Elischer)
Date: Fri, 7 Feb 1997 14:01:19 +1030 (CST)
Cc: hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Julian Elischer stands accused of saying:
> anyone have a good ref on this?
> they shipped me one with a hawk manual (!?)

www.seagate.com; they have all their drive references (even the old
CDC Sabre ones) online.

> julian

-- 
]] Mike Smith, Software Engineer        msmith@gsoft.com.au             [[
]] Genesis Software                     genesis@gsoft.com.au            [[
]] High-speed data acquisition and      (GSM mobile)     0411-222-496   [[
]] realtime instrument control.         (ph)          +61-8-8267-3493   [[
]] Unix hardware collector.             "Where are your PEZ?" The Tick  [[

From owner-freebsd-hackers  Thu Feb  6 19:35:29 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA28203
          for hackers-outgoing; Thu, 6 Feb 1997 19:35:29 -0800 (PST)
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA28178;
          Thu, 6 Feb 1997 19:35:19 -0800 (PST)
Received: from sendero.i-connect.net ([206.190.144.100])
          by who.cdrom.com (8.7.5/8.6.11) with ESMTP id TAA20083
          ; Thu, 6 Feb 1997 19:35:16 -0800 (PST)
Received: (from shimon@localhost)
          by sendero.i-connect.net (8.8.5/8.8.4)
	  id UAA15805; Thu, 6 Feb 1997 20:34:41 -0800 (PST)
Message-ID: <XFMail.970206203440.Shimon@i-Connect.Net>
X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD
Content-Type: text/plain; charset=iso-8859-8
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <199702062036.MAA01871@narnia.plutotech.com>
Date: Thu, 06 Feb 1997 18:34:44 -0800 (PST)
Organization: iConnect Corp.
From: Simon Shapiro <Shimon@i-Connect.Net>
To: "Justin T. Gibbs" <gibbs@narnia.plutotech.com>
Subject: Re: Contigious (spelling?) allocation in kernel
Cc: freebsd-scsi@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG,
        "Justin T. Gibbs" <gibbs@plutotech.com>
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


Hi Justin T. Gibbs;  On 06-Feb-97 you wrote: 

...

> Okay, so if you can live with 2MB or less per transaction, you'll have at
most
> a page worth of SG list per transaction, and you can use regular malloc
to pool
> them as you like.  The aic7xxx driver does this for its SG list already,
> allocating a page worth of SG lists each time.  I used to have the SG list
> maxed out at 256 (the limit of these controllers), but recently dropped it
> down to 32 until the 64k limit goes away (17 would be sufficient for
anything
> that the kernel does, but I wanted it to be a power of 2 for efficient
pooling).

I have noticed that.  This driver (aic7xxx) has been very helpful in writing
this beast.  I have pretty much adopted most of what you say.  Except that
we pre-allocate an SG list for every CCB.  It works better for this HBA,
even if it costs more in memory.  I allow the size of the list to be
tunable.
Which brings me to the next question :-))  How do i pass parameters to a
driver at boot time?  Similar to the Linux lilo/insmod stuff.

...

> You have a couple choices.  One is to make another in-kernel process like
> the page daemon.  Another is to add software interrupt handlers for your
> tasks.  This can work well if your workload has clean interdependencies. 
> For example, the CAM SCSI code will add another software interrupt handler
that
> deals with work provided by the controller's interrupt routine at a lower
> priority then the hardware interrupts themselves.  This ensures that your
> controller interrupt handler is as short as possible (they curently call
up
> into the mid layer at raised SPL blocking other interrupts) as the current
> scheme can be really nasty if you are sharing an interrupt with a device
that
> requires fast response times (like a Fibre Channel or ethernet card).

This is EXACTLY what I am after!  For the same reasons.  The DPT can handle
a cache hit in less than a microsecond.  I want to be able to get out of 
the interrupt routine as fast as possible, and hand the rest of the
processing to some other thread.  How do I do that?  Looks to me as if the
software interrupt route is the simplest/best, but what are the semantics
for its calling, etc. ?

Thanx!   Hope I could return these favors one day...

Simon

From owner-freebsd-hackers  Thu Feb  6 19:43:27 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA28930
          for hackers-outgoing; Thu, 6 Feb 1997 19:43:27 -0800 (PST)
Received: from DNS.Lamb.net (root@DNS.Lamb.net [207.90.181.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA28925
          for <hackers@FreeBSD.ORG>; Thu, 6 Feb 1997 19:43:25 -0800 (PST)
Received: from bitch.Melmac.org (ulf@Bitch.Melmac.org [207.90.181.42]) by DNS.Lamb.net (8.8.5/20.74.3.14) with ESMTP id TAA14543; Thu, 6 Feb 1997 19:43:30 -0800 (PST)
Received: (from ulf@localhost) by bitch.Melmac.org (8.8.5/8.7.6) id TAA22178; Thu, 6 Feb 1997 19:43:23 -0800 (PST)
From: Ulf Zimmermann <ulf@Alameda.net>
Message-Id: <199702070343.TAA22178@bitch.Melmac.org>
Subject: Re: barracuda jumbers?
In-Reply-To: <32FA9B4C.41C67EA6@whistle.com> from Julian Elischer at "Feb 6, 97 07:02:36 pm"
To: julian@whistle.com (Julian Elischer)
Date: Thu, 6 Feb 1997 19:43:23 -0800 (PST)
Cc: hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL30 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> anyone have a good ref on this?
> they shipped me one with a hawk manual (!?)
> 
> 
> julian
> 

http://www.seagte.com/ download the pdf or view it online.


Ulf.

--------------------------------------------------------------------------
Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936
           Alameda Networks, Inc. | http://www.Alameda.net

From owner-freebsd-hackers  Thu Feb  6 20:15:22 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA01347
          for hackers-outgoing; Thu, 6 Feb 1997 20:15:22 -0800 (PST)
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA01330
          for <hackers@FreeBSD.ORG>; Thu, 6 Feb 1997 20:15:17 -0800 (PST)
Received: from DNS.Lamb.net (root@DNS.Lamb.net [207.90.181.1])
          by who.cdrom.com (8.7.5/8.6.11) with ESMTP id TAA20137
          for <hackers@freebsd.org>; Thu, 6 Feb 1997 19:45:11 -0800 (PST)
Received: from bitch.Melmac.org (ulf@Bitch.Melmac.org [207.90.181.42]) by DNS.Lamb.net (8.8.5/20.74.3.14) with ESMTP id TAA14555; Thu, 6 Feb 1997 19:45:16 -0800 (PST)
Received: (from ulf@localhost) by bitch.Melmac.org (8.8.5/8.7.6) id TAA22194; Thu, 6 Feb 1997 19:45:09 -0800 (PST)
From: Ulf Zimmermann <ulf@Alameda.net>
Message-Id: <199702070345.TAA22194@bitch.Melmac.org>
Subject: Re: PD PDF viewer? was: barracuda jumpers
In-Reply-To: <32FA9D56.167EB0E7@whistle.com> from Julian Elischer at "Feb 6, 97 07:11:18 pm"
To: julian@whistle.com (Julian Elischer)
Date: Thu, 6 Feb 1997 19:45:09 -0800 (PST)
Cc: hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL30 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> so I found the jumper info at www.seagate.com (should have
> thought of that) 
> 
> but it's all in PDF..
> 
> so what was the PD program that could do pdf?
> 
> I know it's one of them, but which?
> 

Either use xpdf or http://www.seagate.com/support/disc/specs/scsitoc.shtml
for online text "graphics" of the jumpers.


Ulf.

--------------------------------------------------------------------------
Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936
           Alameda Networks, Inc. | http://www.Alameda.net

From owner-freebsd-hackers  Thu Feb  6 20:15:25 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA01364
          for hackers-outgoing; Thu, 6 Feb 1997 20:15:25 -0800 (PST)
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA01332
          for <hackers@FreeBSD.ORG>; Thu, 6 Feb 1997 20:15:18 -0800 (PST)
Received: from hq.icb.chel.su (hq.icb.chel.su [193.125.10.33])
          by who.cdrom.com (8.7.5/8.6.11) with ESMTP id UAA20410
          for <hackers@FreeBSD.ORG>; Thu, 6 Feb 1997 20:07:27 -0800 (PST)
Received: (babkin@localhost) by hq.icb.chel.su (8.8.3/8.6.5) id JAA10568; Fri, 7 Feb 1997 09:07:53 +0500 (ESK)
From: "Serge A. Babkin" <babkin@hq.icb.chel.su>
Message-Id: <199702070407.JAA10568@hq.icb.chel.su>
Subject: Re: barracuda jumbers?
To: julian@whistle.com (Julian Elischer)
Date: Fri, 7 Feb 1997 09:07:52 +0500 (ESK)
Cc: hackers@FreeBSD.ORG
In-Reply-To: <32FA9B4C.41C67EA6@whistle.com> from "Julian Elischer" at Feb 6, 97 07:02:36 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 
> anyone have a good ref on this?
> they shipped me one with a hawk manual (!?)

Narrow model:

J01 (little piece of pins for 3 jumpers at the back side of
drive near to power socket, drive positioned with power
socket up and J01 down)

	Rightmost - Enable Terminator
	Left Two :
		Lower Horizontal - Term power from drive (default)
		Leftmost Vertical - Term power from bus
		Middle Vertical - Term power to bus
		Both vertical - Term power to bus and drive
		
J4 (long line of jumpers near the power socket, drive positioned
with J4 down, power jacket left, jumpers lister left to right)

	ID4
	ID2
	ID1
	Reserved
	Disable parity
	Enable Motor Start (drive waits for START command)
	Delay Motor Start (valid only if NOT Enable Motor Start)
	Write Protect
	Remote LED connector (top - "-", bottom - "+")
	Reserved
	Spindle Sync (top - signal, bottom - ground)


Wide model:

J01 (drive positioned with J01 and J4 down, power socket left)
	
	Right Vertical - Term power from drive
	Lower Horizontal - Term power from bus
	Upper Horizontal - Term power to bus
	Both Horizontal - Term power to bus and drive

J4 (near to J01, jumpers listed left to right)

	Reserved
	Enable Terminator
	Reserved
	Parity Disabled
	Enable Motor Start
	Delay Motor Start
	Write Protect

J5 (between SCSI socket and power socked, drive positioned with
sockets down, jumpers listed left to right)

	
	Spindle Sync (top - signal, bottom - ground)
	Remote LED connector (top - "-", bottom - "+")
	ID8
	ID4
	ID2
	ID1

Differential drives have no internal terminator, narrow differential drive
has slightly different layout of jumpers.

Hope it will help you!

-SB

From owner-freebsd-hackers  Thu Feb  6 20:18:17 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA01943
          for hackers-outgoing; Thu, 6 Feb 1997 20:18:17 -0800 (PST)
Received: from aries.bb.cc.wa.us (root@[208.8.136.11])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA01914
          for <hackers@FreeBSD.ORG>; Thu, 6 Feb 1997 20:18:09 -0800 (PST)
Received: from localhost (chris@localhost) by aries.bb.cc.wa.us (8.8.3/8.6.9) with SMTP id UAA25092; Thu, 6 Feb 1997 20:19:57 -0800 (PST)
Date: Thu, 6 Feb 1997 20:19:57 -0800 (PST)
From: Chris Coleman <chris@bb.cc.wa.us>
To: Julian Elischer <julian@whistle.com>
cc: hackers@FreeBSD.ORG
Subject: Re: barracuda jumbers?
In-Reply-To: <32FA9B4C.41C67EA6@whistle.com>
Message-ID: <Pine.NEB.3.94.970206201929.25085A-100000@aries.bb.cc.wa.us>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

I have a Barracuda and the "right" book. :-)

Christopher J. Coleman (chris@aries.bb.cc.wa.us)
Computer Support Technician I  (509)-766-8873
Big Bend Community College  Internet Instructor
FreeBSD Book Project:  http://www.bb.cc.wa.us/~chris/book.html
Death is life's way of telling you you're fired.

On Thu, 6 Feb 1997, Julian Elischer wrote:

> anyone have a good ref on this?
> they shipped me one with a hawk manual (!?)
> 
> 
> julian
> 


From owner-freebsd-hackers  Thu Feb  6 20:18:33 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA02017
          for hackers-outgoing; Thu, 6 Feb 1997 20:18:33 -0800 (PST)
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA01960;
          Thu, 6 Feb 1997 20:18:21 -0800 (PST)
Received: from sendero.i-connect.net ([206.190.144.100])
          by who.cdrom.com (8.7.5/8.6.11) with ESMTP id TAA20108
          ; Thu, 6 Feb 1997 19:36:23 -0800 (PST)
Received: (from shimon@localhost)
          by sendero.i-connect.net (8.8.5/8.8.4)
	  id UAA15807; Thu, 6 Feb 1997 20:34:41 -0800 (PST)
Message-ID: <XFMail.970206203440.Shimon@i-Connect.Net>
X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD
Content-Type: text/plain; charset=iso-8859-8
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <32FA657D.446B9B3D@whistle.com>
Date: Thu, 06 Feb 1997 18:46:20 -0800 (PST)
Organization: iConnect Corp.
From: Simon Shapiro <Shimon@i-Connect.Net>
To: Julian Elischer <julian@whistle.com>
Subject: Re: Contigious (spelling?) allocation in kernel
Cc: freebsd-scsi@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG,
        "Justin T. Gibbs" <gibbs@narnia.plutotech.com>
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


Hi Julian Elischer;  On 06-Feb-97 you wrote: 

...

> well you could do what the swap daemon does.. it's started from the
> kernel..
> it's more a kernel PROCESS than a kernel thread.

I really do not care.  All I need is something that will allow me to
break the execution thread and resume it in a different time.

A mechanism, like another interrupt handler, software interrupts, etc.
I want to be able to accomplish two things:

1.  Return from xxx_scsi_cmd as fast as possible.
2.  Return from xxx_intr as fast as possible.
3.  Hand over the hardware processing implied by xxx_scsi_cmd to
    another entity so that this routine does not have to block on
    inb, outb and such.  IOW, I want to de-couple the scsi_cmd from
    the hardware.
4.  Hand over the logical (and error) processing implied by xxx_intr
    to another entity.  IOW, de-couple hardware issues (done in the
    intr routine) form logic, error processing, strategy and such.

Much of this work may appear meaningless on a uniprocessor, but on 
an SMP system it has many advantages, as it allows partitioning 
of the workload and running the three layers asynchronously from
each other.

Three Layers:

1.  Accept SCSI command, prepare for execution and queue.
2.  a.  Submit to hardware
    b.  Receive completion notification form hardware
3.  Analyze result, plan response and execute, reply to original
    caller.

Thanx!

Simon

From owner-freebsd-hackers  Thu Feb  6 20:27:02 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA02705
          for hackers-outgoing; Thu, 6 Feb 1997 20:27:02 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA02691;
          Thu, 6 Feb 1997 20:26:58 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id PAA19335; Fri, 7 Feb 1997 15:23:06 +1100
Date: Fri, 7 Feb 1997 15:23:06 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199702070423.PAA19335@godzilla.zeta.org.au>
To: bde@zeta.org.au, chuckr@glue.umd.edu
Subject: Re: conditionally including <sys/param.h>
Cc: freebsd-ports@FreeBSD.org, hackers@FreeBSD.org, imp@village.org,
        obrien@NUXI.com
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>> But they certainly should accept anything with __FooBSD__ or BSD >= mmm
>> or __FooBSD_version >= nnn.  That would give 100-line ifdefs to support
>> 100 OS's.  It's also useless for communicating what is different in
>> FooBSD.
>
>I don't disagree, I'm just saying that flatly including sys/param.h with
>no qualifiers means that it will be a fatal error on any machine that
>doesn't have a sys/param.h, so that's not acceptable.

The application authors should already have a way of handling the possible
nonexistence of sys/param.h, and it is unlikely to be the same as ours.
If not, then they should refuse to add anything involving sys/param.h.

>non-fatal in nature to systems without sys/param.h.  The method I suggest
>above is messy, but (and _please_ correct me if I'm wrong) it has the sole
>benefit of being the only one I've seen that is non-fatal on systems that
>don't have a sys/param.h.

I forget what it is.

The only method that is (almost) guaranteed to work is a test involving
an identifier that is defined outside of the the application, perhaps in
bsd.ports.mk, e.g.,

#ifdef HAVE_SYS_PARAM_H
#include <sys/param.h>
#endif

This breaks if the identifier already has a different meaning to the
application (not likely) and is inconvenient if the application and/or
other supported targets already have a different spelling for the
identifier.

Bruce

From owner-freebsd-hackers  Thu Feb  6 20:41:33 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA03549
          for hackers-outgoing; Thu, 6 Feb 1997 20:41:33 -0800 (PST)
Received: from po1.glue.umd.edu (root@po1.glue.umd.edu [129.2.128.44])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA03532;
          Thu, 6 Feb 1997 20:41:27 -0800 (PST)
Received: from skipper.eng.umd.edu (skipper.eng.umd.edu [129.2.103.24]) by po1.glue.umd.edu (8.8.5/8.7.3) with ESMTP id XAA18669; Thu, 6 Feb 1997 23:41:12 -0500 (EST)
Received: from localhost (chuckr@localhost) by skipper.eng.umd.edu (8.8.5/8.7.3) with SMTP id XAA05269; Thu, 6 Feb 1997 23:41:11 -0500 (EST)
X-Authentication-Warning: skipper.eng.umd.edu: chuckr owned process doing -bs
Date: Thu, 6 Feb 1997 23:41:05 -0500 (EST)
From: Chuck Robey <chuckr@glue.umd.edu>
X-Sender: chuckr@skipper.eng.umd.edu
To: Bruce Evans <bde@zeta.org.au>
cc: freebsd-ports@FreeBSD.org, hackers@FreeBSD.org, imp@village.org,
        obrien@NUXI.com
Subject: Re: conditionally including <sys/param.h>
In-Reply-To: <199702070423.PAA19335@godzilla.zeta.org.au>
Message-ID: <Pine.OSF.3.95q.970206233250.5253C-100000@skipper.eng.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

On Fri, 7 Feb 1997, Bruce Evans wrote:

> >> But they certainly should accept anything with __FooBSD__ or BSD >= mmm
> >> or __FooBSD_version >= nnn.  That would give 100-line ifdefs to support
> >> 100 OS's.  It's also useless for communicating what is different in
> >> FooBSD.
> >
> >I don't disagree, I'm just saying that flatly including sys/param.h with
> >no qualifiers means that it will be a fatal error on any machine that
> >doesn't have a sys/param.h, so that's not acceptable.
> 
> The application authors should already have a way of handling the possible
> nonexistence of sys/param.h, and it is unlikely to be the same as ours.
> If not, then they should refuse to add anything involving sys/param.h.

I've talked to a fair sampling of authors of unix applications, and most
would be overjoyed if we presented them with a method that was both safe
for them to use on any platform, and guaranteed to DTRT on
Free|Open|NetBSD.  If they had a BSD make, it would be simple, likewise if
they used the GNU make, but SYSV make is a backwards child.  I want to
find _something_ that would could use _and_ advertise to the outside
world.  Just making it work under FreeBSD is trivial, because our make
supports the #if exists syntax.

That's the reason I would like the __FreeBSD__, __OpenBSD__, and
__NetBSD__, because it works.  I know it's as elegant as my dirty laundry. 
I haven't seen any other method that works. 

All your comments have been correct, I think, but I still haven't seen
anyone make any other suggestion that works.  Works, I mean, on FreeBSD
and all the other platforms, not just the BSD world.

> 
> >non-fatal in nature to systems without sys/param.h.  The method I suggest
> >above is messy, but (and _please_ correct me if I'm wrong) it has the sole
> >benefit of being the only one I've seen that is non-fatal on systems that
> >don't have a sys/param.h.
> 
> I forget what it is.
> 
> The only method that is (almost) guaranteed to work is a test involving
> an identifier that is defined outside of the the application, perhaps in
> bsd.ports.mk, e.g.,
> 
> #ifdef HAVE_SYS_PARAM_H
> #include <sys/param.h>
> #endif
> 
> This breaks if the identifier already has a different meaning to the
> application (not likely) and is inconvenient if the application and/or
> other supported targets already have a different spelling for the
> identifier.
> 
> Bruce
> 

----------------------------+-----------------------------------------------
Chuck Robey                 | Interests include any kind of voice or data 
chuckr@eng.umd.edu          | communications topic, C programming, and Unix.
9120 Edmonston Ct #302      |
Greenbelt, MD 20770         | I run Journey2 and picnic, both FreeBSD
(301) 220-2114              | version 3.0 current -- and great FUN!
----------------------------+-----------------------------------------------


From owner-freebsd-hackers  Thu Feb  6 20:57:13 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA04309
          for hackers-outgoing; Thu, 6 Feb 1997 20:57:13 -0800 (PST)
Received: from zeus.xtalwind.net (pa3dsp11.x31.infi.net [206.27.115.83])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA04303
          for <hackers@FreeBSD.ORG>; Thu, 6 Feb 1997 20:57:09 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by zeus.xtalwind.net (8.8.5/8.8.5) with SMTP id XAA10872;
	Thu, 6 Feb 1997 23:58:24 -0500 (EST)
Date: Thu, 6 Feb 1997 23:58:24 -0500 (EST)
From: jack <jack@diamond.xtalwind.net>
X-Sender: jack@localhost
To: Julian Elischer <julian@whistle.com>
cc: hackers@FreeBSD.ORG
Subject: Re: barracuda jumbers?
In-Reply-To: <32FA9B4C.41C67EA6@whistle.com>
Message-ID: <Pine.FBS.3.95.970206235800.10788C-100000@localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Thu, 6 Feb 1997, Julian Elischer wrote:

> anyone have a good ref on this?
> they shipped me one with a hawk manual (!?)

http://www.seagate.com/support/disc/specs/scsitoc.shtml

--------------------------------------------------------------------------
Jack O'Neill                    Finger jacko@diamond.xtalwind.net or  
jack@xtalwind.net               http://www.xtalwind.net/~jacko/pubpgp.html
#include <std_disclaimers.h>    for my PGP key.
 PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67   FD 09 E9 3C 5F CC EB CD
--------------------------------------------------------------------------


From owner-freebsd-hackers  Thu Feb  6 21:24:50 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA05678
          for hackers-outgoing; Thu, 6 Feb 1997 21:24:50 -0800 (PST)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA05673
          for <hackers@FreeBSD.ORG>; Thu, 6 Feb 1997 21:24:47 -0800 (PST)
Received: from current1.whistle.com (current1.whistle.com [207.76.205.22])
          by alpo.whistle.com (8.8.5/8.8.4) with SMTP
	  id VAA13840; Thu, 6 Feb 1997 21:13:50 -0800 (PST)
Message-ID: <32FAB9A2.167EB0E7@whistle.com>
Date: Thu, 06 Feb 1997 21:12:02 -0800
From: Julian Elischer <julian@whistle.com>
Organization: Whistle Communications
X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386)
MIME-Version: 1.0
To: "Serge A. Babkin" <babkin@hq.icb.chel.su>
CC: hackers@FreeBSD.ORG
Subject: Re: barracuda jumbers?
References: <199702070407.JAA10568@hq.icb.chel.su>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Serge A. Babkin wrote:
> 
> >
> > anyone have a good ref on this?
> > they shipped me one with a hawk manual (!?)
> 
> Narrow model:
> 
> J01 (little piece of pins for 3 jumpers at the back side of
> drive near to power socket, drive positioned with power
> socket up and J01 down)

etc.

THANKS!

From owner-freebsd-hackers  Thu Feb  6 21:59:55 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA07002
          for hackers-outgoing; Thu, 6 Feb 1997 21:59:55 -0800 (PST)
Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA06991
          for <hackers@FreeBSD.ORG>; Thu, 6 Feb 1997 21:59:38 -0800 (PST)
Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33])
          by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP
	  id GAA30473 for <hackers@FreeBSD.ORG>; Fri, 7 Feb 1997 06:58:53 +0100
Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id GAA14707 for hackers@FreeBSD.ORG; Fri, 7 Feb 1997 06:58:38 +0100
Received: (from roberto@localhost) by keltia.freenix.fr (8.8.5/keltia-uucp-2.9) id GAA15365;
          Fri, 7 Feb 1997 06:53:59 +0100 (CET)
Message-ID: <19970207065358.IU34422@keltia.freenix.fr>
Date: Fri, 7 Feb 1997 06:53:58 +0100
From: roberto@keltia.freenix.fr (Ollivier Robert)
To: hackers@FreeBSD.ORG
Subject: Re: PD PDF viewer? was: barracuda jumpers
References: <32FA9D56.167EB0E7@whistle.com> <199702070345.TAA22194@bitch.Melmac.org>
X-Mailer: Mutt 0.60,1-3,9
Mime-Version: 1.0
X-Operating-System: FreeBSD 3.0-CURRENT ctm#2999
In-Reply-To: <199702070345.TAA22194@bitch.Melmac.org>; from Ulf Zimmermann on Feb 6, 1997 19:45:09 -0800
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

According to Ulf Zimmermann:
> Either use xpdf or http://www.seagate.com/support/disc/specs/scsitoc.shtml
> for online text "graphics" of the jumpers.

The acroread linux binary works pretty well too. See
/usr/ports/print/acroread.
-- 
Ollivier ROBERT    -=- The daemon is FREE! -=-    roberto@keltia.freenix.fr
  FreeBSD keltia.freenix.fr 3.0-CURRENT #39: Sun Feb  2 22:12:44 CET 1997

From owner-freebsd-hackers  Thu Feb  6 22:12:21 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id WAA07817
          for hackers-outgoing; Thu, 6 Feb 1997 22:12:21 -0800 (PST)
Received: from red.jnx.com (red.jnx.com [208.197.169.254])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA07810;
          Thu, 6 Feb 1997 22:12:09 -0800 (PST)
Received: from base.jnx.com (base.jnx.com [208.197.169.238]) by red.jnx.com (8.8.5/8.8.3) with ESMTP id WAA26597; Thu, 6 Feb 1997 22:11:39 -0800 (PST)
Received: from base.jnx.com (localhost.jnx.com [127.0.0.1]) by base.jnx.com (8.7.6/8.7.3) with ESMTP id WAA02843; Thu, 6 Feb 1997 22:11:38 -0800 (PST)
Message-Id: <199702070611.WAA02843@base.jnx.com>
To: Joe Greco <jgreco@solaria.sol.net>
cc: bde@freebsd.org, hackers@freebsd.org
Subject: Re: serial ports at 230k 
In-reply-to: Your message of "Thu, 06 Feb 1997 16:15:53 CST."
             <199702062215.QAA26943@solaria.sol.net> 
Date: Thu, 06 Feb 1997 22:11:38 -0800
From: Paul Traina <pst@jnx.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Thanks Joe... I'll probably just soup up one of my old cards, since the
ESP support under FreeBSD doesn't handle the higher baud rates and I'm
juggling so many balls I don't have time to become an SIO expert.


From owner-freebsd-hackers  Thu Feb  6 22:48:31 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id WAA09112
          for hackers-outgoing; Thu, 6 Feb 1997 22:48:31 -0800 (PST)
Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA09107
          for <Hackers@FreeBSD.ORG>; Thu, 6 Feb 1997 22:48:28 -0800 (PST)
Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.5/CET-v2.1) with SMTP id GAA08001 for <Hackers@FreeBSD.ORG>; Fri, 7 Feb 1997 06:48:24 GMT
Date: Fri, 7 Feb 1997 15:48:24 +0900 (JST)
From: Michael Hancock <michaelh@cet.co.jp>
To: FreeBSD Hackers <Hackers@FreeBSD.ORG>
Subject: Sybase jdbcCONNECT
Message-ID: <Pine.SV4.3.95.970207154124.7984A-100000@parkplace.cet.co.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Sybase has a beta of a jdbc implementation that doesn't require
installation of binary client libs, you only need Java.

They have what looks like a generic Unix version at the following site:

http://www.sybase.com/products/internet/jdbcconnect/jdbcreg.html

It'd be interesting to see if you can access SQL Server directly from a PC
running FreeBSD.

Mike Hancock


From owner-freebsd-hackers  Thu Feb  6 23:18:33 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA10135
          for hackers-outgoing; Thu, 6 Feb 1997 23:18:33 -0800 (PST)
Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA10130
          for <freebsd-hackers@FreeBSD.ORG>; Thu, 6 Feb 1997 23:18:28 -0800 (PST)
Received: (from karpen@localhost) by ocean.campus.luth.se (8.7.5/8.7.3) id IAA13734; Fri, 7 Feb 1997 08:20:35 +0100 (MET)
From: Mikael Karpberg <karpen@ocean.campus.luth.se>
Message-Id: <199702070720.IAA13734@ocean.campus.luth.se>
Subject: Re: Audible ping response changes to ping.c
To: danny@panda.hilink.com.au (Daniel O'Callaghan)
Date: Fri, 7 Feb 1997 08:20:35 +0100 (MET)
Cc: freebsd-hackers@FreeBSD.ORG
In-Reply-To: <Pine.BSF.3.91.970207111513.427L-100000@panda.hilink.com.au> from Daniel O'Callaghan at "Feb 7, 97 11:17:31 am"
X-Mailer: ELM [version 2.4ME+ PL22 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

According to Daniel O'Callaghan:
> 
> 
> On Thu, 6 Feb 1997, Terry Lambert wrote:
> 
> > > > Also, the z flag runs an external compressor/decompressor.  By that
> > > > logic, you should call an external "beep" program if you are trying to
> > > > justify adding the flag using "the "rule of similar existing practice".
> > > 
> > > Hmmmm. :-)
> > 
> > 
> > Here is a revised version that transparently provides a "-a" option
> > to the real ping command without adding it to the real ping command:
> 
> Thanks, Terry, are you going to submit a man page?

Ok, so it's a nice idea to build functionality from small bits, but
this is ridiculous! :-) We're talking excanging about three lines of
C code with a big script. This is just a way too small change not to
be well jusified to go into ping as an option. The latest patch for ping
seemed just fine, although I'd think '-b' would be more logical.
You think "Hmm... now, what option was it that ping beep? Hmm..." and try
"-b". You don't think "What made ping audiable?". :-P

...IMHO.

   /Mikael

From owner-freebsd-hackers  Thu Feb  6 23:46:11 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA11027
          for hackers-outgoing; Thu, 6 Feb 1997 23:46:11 -0800 (PST)
Received: from alcatel.fr (ns.alcatel.fr [194.133.58.131])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA11022
          for <freebsd-hackers@FreeBSD.ORG>; Thu, 6 Feb 1997 23:46:07 -0800 (PST)
Received: from alcatel.fr (gatekeeper-ssn.alcatel.fr [155.132.180.244]) by mailgate.alcatel.fr (8.7.3/8.7.3) with ESMTP id IAA00173; Fri, 7 Feb 1997 08:50:44 +0100
Received: from dnscit.cit.alcatel.fr (dnscit.cit.alcatel.fr [139.54.100.2]) by nsfhh5.alcatel.fr (8.7.3/8.7.3) with SMTP id IAA13607; Fri, 7 Feb 1997 08:45:30 +0100 (MET)
Received: from dnsvz.vz.cit.alcatel.fr by dnscit.cit.alcatel.fr (SMI-8.6/SMI-SVR4)
	id IAA14169; Fri, 7 Feb 1997 08:47:31 +0100
Received: from bcv64s3e.vz.cit.alcatel.fr by dnsvz.vz.cit.alcatel.fr (SMI-8.6/SMI-SVR4)
	id IAA14597; Fri, 7 Feb 1997 08:31:28 +0100
Received: from bcv64wc1.velizy by bcv64s3e.vz.cit.alcatel.fr (SMI-8.6/SMI-SVR4)
	id IAA13872; Fri, 7 Feb 1997 08:43:41 +0100
From: luc.lewy@vz.cit.alcatel.fr (Luc.LEWY)
Message-Id: <199702070743.IAA13872@bcv64s3e.vz.cit.alcatel.fr>
Subject: Re: Audible ping response changes to ping.c
To: karpen@ocean.campus.luth.se (Mikael Karpberg)
Date: Fri, 7 Feb 1997 08:43:39 +0100 (MET)
Cc: danny@panda.hilink.com.au, freebsd-hackers@FreeBSD.ORG
In-Reply-To: <199702070720.IAA13734@ocean.campus.luth.se> from "Mikael Karpberg" at Feb 7, 97 08:20:35 am
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Mikael Karpberg wrote:
> [...] although I'd think '-b' would be more logical.
> You think "Hmm... now, what option was it that ping beep? Hmm..." and try
> "-b". You don't think "What made ping audiable?". :-P
	
	Well, I'm maybe too stupid, but each time I can't remember an
	option, format param, I just type 'man command' .. 
	It's *really* a stupid/bad habit huh ? :p :)
	In fact, I think -b or -a it really doesn't matter...
	This thread make me thinking about usual ones on 'OS1 vs
	OS2'.. something quite a bit .. mm.. sterile :)

> ...IMHO.
	mine too :) .. but very humble :)
>    /Mikael
	fifi...
--
Guezou "fifi..." Philippe		email:	guezou_p@epita.fr
						pguezou@iway.fr
						luc.lewy1@vz.cit.alcatel.fr



From owner-freebsd-hackers  Fri Feb  7 02:45:34 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA17557
          for hackers-outgoing; Fri, 7 Feb 1997 02:45:34 -0800 (PST)
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA17499
          for <freebsd-hackers@FreeBSD.ORG>; Fri, 7 Feb 1997 02:45:28 -0800 (PST)
Received: from hda.hda.com (ip52-max1-fitch.ziplink.net [199.232.245.52])
          by who.cdrom.com (8.7.5/8.6.11) with SMTP id CAA21754
          for <freebsd-hackers@FreeBSD.ORG>; Fri, 7 Feb 1997 02:22:14 -0800 (PST)
Received: (from dufault@localhost) by hda.hda.com (8.6.12/8.6.12) id FAA02234; Fri, 7 Feb 1997 05:17:21 -0500
From: Peter Dufault <dufault@hda.com>
Message-Id: <199702071017.FAA02234@hda.hda.com>
Subject: Re: What happened to the splash screen?
In-Reply-To: <Mutt.19970207010238.j@uriah.heep.sax.de> from J Wunsch at "Feb 7, 97 01:02:38 am"
To: joerg_wunsch@uriah.heep.sax.de
Date: Fri, 7 Feb 1997 05:17:21 -0500 (EST)
Cc: freebsd-hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL25 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> I would even be tempted to do a stab at serial console installation,
> but i still need a good idea how to `switch screens' there.  You know,
> we need 4 different screens that can be switched, one for the menus,
> one for debug & console messages, one for the EHS, and one for PPP.

I have two concept 108s here (man 5 termcap).  They have 8 pages
of screen memory.  It may be a bit expensive to send one off to you,
though.

Peter

-- 
Peter Dufault (dufault@hda.com)   Realtime Machine Control and Simulation
HD Associates, Inc.               Voice: 508 433 6936

From owner-freebsd-hackers  Fri Feb  7 02:45:35 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA17559
          for hackers-outgoing; Fri, 7 Feb 1997 02:45:35 -0800 (PST)
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA17518
          for <hackers@FreeBSD.ORG>; Fri, 7 Feb 1997 02:45:29 -0800 (PST)
From: garyj@frt.dec.com
Received: from mail12.digital.com (mail12.digital.com [192.208.46.20])
          by who.cdrom.com (8.7.5/8.6.11) with ESMTP id CAA21726
          for <hackers@freebsd.org>; Fri, 7 Feb 1997 02:17:17 -0800 (PST)
Received: from cssmuc.frt.dec.com by mail12.digital.com (8.7.5/UNX 1.5/1.0/WV)
	id FAA15160; Fri, 7 Feb 1997 05:12:50 -0500 (EST)
Received: from localhost by cssmuc.frt.dec.com; (5.65v3.2/1.1.8.2/14Nov95-0232PM)
	id AA22010; Fri, 7 Feb 1997 11:12:45 +0100
Message-Id: <9702071012.AA22010@cssmuc.frt.dec.com>
X-Mailer: exmh version 1.6.4 10/10/95
To: hackers@FreeBSD.ORG
In-Reply-To: Message from roberto@keltia.freenix.fr (Ollivier Robert)  of Fri, 
 07 Feb 97 06:53:58 +0100.
Reply-To: gjennejohn@frt.dec.com
Subject: Re: PD PDF viewer? was: barracuda jumpers 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 07 Feb 97 11:12:45 +0100
X-Mts: smtp
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


roberto@keltia.freenix.fr writes:
> According to Ulf Zimmermann:
> > Either use xpdf or http://www.seagate.com/support/disc/specs/scsitoc.shtml
> > for online text "graphics" of the jumpers.
> 
> The acroread linux binary works pretty well too. See
> /usr/ports/print/acroread.

I installed acroread and the linux libraries from ports, but every time
I try to run acroread it catches a segementation fault :( I ktrace'd it,
but can't see exactly where the problem lies.

This under 3.0, BTW.

My LKMs are up-to-date with the kernel and I start the linux emulation
from /etc/rc.i386.

DOOM works, so the linux emulation is obviously also working.

Does acroread need netscape ? I use a rather old version of netscape.

---
Gary Jennejohn				(work) gjennejohn@frt.dec.com
					(home) Gary.Jennejohn@munich.netsurf.de
					(play) gj@freebsd.org



From owner-freebsd-hackers  Fri Feb  7 02:45:36 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA17558
          for hackers-outgoing; Fri, 7 Feb 1997 02:45:36 -0800 (PST)
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA17520
          for <freebsd-hackers@FreeBSD.ORG>; Fri, 7 Feb 1997 02:45:30 -0800 (PST)
Received: from freenet.hamilton.on.ca (main.freenet.hamilton.on.ca [199.212.94.65])
          by who.cdrom.com (8.7.5/8.6.11) with ESMTP id CAA21722
          for <freebsd-hackers@FreeBSD.ORG>; Fri, 7 Feb 1997 02:15:49 -0800 (PST)
Received: from james.freenet.hamilton.on.ca (james.freenet.hamilton.on.ca [199.212.94.66]) by freenet.hamilton.on.ca (8.7.5/8.7.3) with ESMTP id FAA23450; Fri, 7 Feb 1997 05:16:06 -0500 (EST)
Received: from localhost (ac199@localhost) by james.freenet.hamilton.on.ca (8.7.5/8.7.3) with SMTP id FAA11205; Fri, 7 Feb 1997 05:18:08 -0500 (EST)
X-Authentication-Warning: james.freenet.hamilton.on.ca: ac199 owned process doing -bs
Date: Fri, 7 Feb 1997 05:18:08 -0500 (EST)
From: Tim Vanderhoek <hoek@freenet.hamilton.on.ca>
To: "Luc.LEWY" <luc.lewy@vz.cit.alcatel.fr>
cc: Mikael Karpberg <karpen@ocean.campus.luth.se>, danny@panda.hilink.com.au,
        freebsd-hackers@FreeBSD.ORG
Subject: Re: Audible ping response changes to ping.c
In-Reply-To: <199702070743.IAA13872@bcv64s3e.vz.cit.alcatel.fr>
Message-ID: <Pine.GSO.3.95.970207051342.10911A-100000@james.freenet.hamilton.on.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Fri, 7 Feb 1997, Luc.LEWY wrote:

> Mikael Karpberg wrote:
> > [...] although I'd think '-b' would be more logical.
> > You think "Hmm... now, what option was it that ping beep? Hmm..." and try
> > "-b". You don't think "What made ping audiable?". :-P
> 	
> 	Well, I'm maybe too stupid, but each time I can't remember an
> 	option, format param, I just type 'man command' .. 

Other than printf(1), I'd like you to find a single program from
/usr/share/man/man1 which uses an `a' for "bell".  Maybe we
should have a new environment option, or something?  Sort of like
POSIXMEHARDER except it's BEEPMEHARDER?


--
Outnumbered?  Maybe.  Outspoken?  Never!
tIM...HOEk


From owner-freebsd-hackers  Fri Feb  7 02:45:41 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA17605
          for hackers-outgoing; Fri, 7 Feb 1997 02:45:41 -0800 (PST)
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA17556
          for <freebsd-hackers@FreeBSD.ORG>; Fri, 7 Feb 1997 02:45:36 -0800 (PST)
Received: from gw-nl1.philips.com (gw-nl1.philips.com [192.68.44.33])
          by who.cdrom.com (8.7.5/8.6.11) with ESMTP id CAA21738
          for <freebsd-hackers@FreeBSD.ORG>; Fri, 7 Feb 1997 02:18:01 -0800 (PST)
Received: (from nobody@localhost) 
	by gw-nl1.philips.com (8.6.10/8.6.10-0.994n-08Nov95) id LAA05333; Fri, 7 Feb 1997 11:16:24 +0100
Received: from unknown(130.139.36.3) by gw-nl1.philips.com via smap (V1.3+ESMTP) with ESMTP
	id sma005152; Fri Feb  7 11:15:57 1997
Received: from giga.lss.cp.philips.com (giga.lss.cp.philips.com [130.144.199.31]) 
	by smtprelay.nl.cis.philips.com (8.6.10/8.6.10-1.2.1m-970131) with SMTP id LAA22086; Fri, 7 Feb 1997 11:15:53 +0100
Received: by giga.lss.cp.philips.com (8.8.5/1.63)
    id LAA03051; Fri, 7 Feb 1997 11:15:52 +0100 (MET)
From: W.Belgers@nl.cis.philips.com (Walter Belgers)
Message-Id: <199702071015.LAA03051@giga.lss.cp.philips.com>
Subject: Re: NIS/uids
To: terry@lambert.org (Terry Lambert)
Date: Fri, 7 Feb 1997 11:15:52 +0100 (MET)
Cc: freebsd-hackers@FreeBSD.ORG
In-Reply-To: <199702062116.OAA17845@phaeton.artisoft.com> from Terry Lambert at "Feb 6, 97 02:16:58 pm"
Organisation: Origin IT Systems Management /Nederland B.V.
X-URL: http://giga.lss.cp.philips.com/cgi-bin/walter.cgi
X-Mailer: ELM [version 2.4ME+ PL19 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Terry Lambert writes:
> > > > Let's assume I do not trust the uid's coming from the NIS server but I
> > > > still do want to use NIS (for passwd/homedir/gecos/whatever).
> > > 
> Couldn't I add the user to "wheel" or "kmem" in the NIS groups file
> anyway?

If I do not override the gid in the local password file, a user could
indeed put himself in wheel and be in wheel on my local machine as well.

> I still like the idea of a list of groups and uids that won't be
> honored via NIS.

Or maybe make an exception for uid 0.

> > I have no "+" in my password file, only "+user", so you can only hack
> > those users, not the users that are only locally in my password file. So
> > it does give the desired protection.
> 
> Do you do "+group" in the group file, as well?  I suppose you have to...

No, I don't mind wether or not all gids are in the group file. If a NIS
user is in group 999 which doesn't locally exists, so be it.

> 					Terry Lambert

Walter.
-- 
Ir. W.H.B. Belgers, Internet Security Specialist        phone: +31 40 2782753
Origin IT Syst.Man. /Nederland bv, Bldg VN-513   email:   fax: +31 40 2784697
P.O. Box 218, 5600 MD Eindhoven, Netherlands     W.Belgers@nl.cis.philips.com
non-business-email: walter@giga.nl & -web: http://www.IAEhv.nl/users/gigawalt

From owner-freebsd-hackers  Fri Feb  7 04:02:50 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id EAA22579
          for hackers-outgoing; Fri, 7 Feb 1997 04:02:50 -0800 (PST)
Received: from stanton-1-1.quick.net (soil@stanton-1-8.quick.net [207.212.170.108])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA22572
          for <hackers@freebsd.org>; Fri, 7 Feb 1997 04:02:41 -0800 (PST)
Received: from localhost (soil@localhost)
	by stanton-1-1.quick.net (8.8.5/8.8.5) with SMTP id EAA14489
	for <hackers@freebsd.org>; Fri, 7 Feb 1997 04:02:27 -0800 (PST)
X-Authentication-Warning: stanton-1-1.quick.net: soil owned process doing -bs
Date: Fri, 7 Feb 1997 04:02:27 -0800 (PST)
From: Josh Gilliam <soil@quick.net>
To: hackers@freebsd.org
Subject: Announcing the Release of XFree86-3.2A (fwd)
Message-ID: <Pine.BSF.3.95q.970207040111.14157A-100000@stanton-1-1.quick.net>
X-IRC: soil
X-Operating-System: FreeBSD 2.1.6.1-RELEASE i386
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk



---------- Forwarded message ----------

		       Announcing the Release of
		     XFree86[TM] Beta Version 3.2A

		               05 Feb 1997

The XFree86 Project, Inc is proud to release its latest beta version,
XFree86-3.2A, for public beta testing. This is a binary-only release, 
binaries for many popular operating systems are available from 
ftp://ftp.xfree86.org/pub/XFree86/3.2A/, and its mirror sites.

For more details look at the excerpt from the release notes. Detailed 
information on how to install XFree86-3.2A can be found in the full 
release notes at http://www.xfree86.org/3.2A/RELNOTES.html

------------------------------------------------------------------------
Release Notes for XFree86[tm] 3.2A (beta version)



		      Release Notes for XFree86[tm] 3.2A


			   The XFree86 Project, Inc


				25 January 1997



				   Abstract

     This document describes the rationale and conditions of this beta
     release, what is new in the XFree86 beta version 3.2A compared with
     the current release version (3.2), and how to install this beta
     release.



1.  General Information about Beta Releases

This is a beta release of XFree86.  XFree86 beta releases are available to the
public in binary form only.  Source code is available only to registered mem-
bers of the XFree86 beta team.	The main reason for this is that XFree86 beta
versions often contain source code from other sources (such as the X Consor-
tium) which is not yet available for public release.  If you want to test or
work on these releases at the source code level, you can apply for membership
of the XFree86 beta team by sending email to XFree86@XFree86.org.

The X servers included in beta releases have a built-in expiry date.  The rea-
son for this is to try to prevent them from persisting beyond the date of the
next release, and to encourage people to test new beta releases.  The expiry
date for 3.2A is 15 June 1997.

The XFree86 binary beta releases may be freely redistributed providing that
they are not modified in any way, and providing that an unmodified version of
this document and the BetaReport document is included with the distribution.

The reasons for making this beta release publicly available are to give it the
widest possible testing, and also to make support for new hardware available.

The XFree86 Project encourages people to test this beta release, and to send us
a report.  We need both success and failure reports, and we also need people
using already supported hardware to test these beta releases to make sure that
we haven't broken anything while adding support for new hardware.  A template
for the Beta test reports can be found in the file ``BetaReport'' which should
be available from the same place you got this file.  It is also installed in
/usr/X11R6/lib/X11/doc/.  Beta test reports should be sent to
report@XFree86.org.  Please do not send these reports to our usual support
address.

The XFree86 FAQ <URL:http://www.xfree86.org/FAQ> contains a section about the
current beta version.  It includes a regularly updated list of known problems.
If you are having problems with the current beta version, please look here
first.

Note that much of the documentation provided with this release has not been
updated and still refers to 3.2.  If in doubt, check the date shown in the
file(s).


2.  Who are the XFree86 Beta Releases Targeted At?

The XFree86 beta releases are intended for people who are prepared to test
software which might be unstable and which might be buggy, and report the
results of the testing.  These beta releases are not intended for beginners,
but for people who have a basic knowledge of the OS so that they don't require
much support for issues like upgrading system libraries and obtaining necessary
packages.

If you are going to test this software, you should be prepared for the follow-
ing:

   o Installation problems.  The installation procedure for beta releases gets
     only very limited testing prior to release.  You should be prepared for
     problems here, and you should be prepared to upgrade other components of
     your system if it proves necessary.  You should also have facilities to
     backup a previous installation (and preferably your entire system) so that
     it can be restored in case of serious problems.

   o New bugs.	Since each beta version gets only a limited amount of pre-
     release testing, it is likely that a new version will contain new bugs.
     This is unavoidable, because any code change, be it fixing previous bugs
     or adding new features, brings with it the chance that new bugs have been
     introduced.  You should be prepared for the possibility that the new ver-
     sion will have problems with your hardware.  In this situation, you should
     first check the XFree86 FAQ <URL:http://www.xfree86.org/FAQ> to see if it
     is a known problem (possibly with a workaround), and then report the prob-
     lem in detail.

   o Expiry date.  The XFree86 beta servers have a limited lifetime.  Before
     using one, you should be aware of this and what the implications of this
     are.  If you have objections to software that has an expiry date, you
     shouldn't use this beta software.	It is possible that when one version
     expires you may find that the replacement version has problems, or perhaps
     binaries of the replacement are not available for your OS.  If you depend
     on a server for your work/school/etc, you shouldn't be relying on this
     beta software.


3.  XFree86 and X11R6.3

XFree86 releases starting with the this 3.2A beta are based on the X Consor-
tium's X11R6.3 (the final release from the X Consortium).

R6.3 is an update to R6.1, and is intended to be compatible with R6.1 and R6 at
the source and protocol levels.  Binaries should be upward-compatible.	X11R6.3
includes some new Xserver extensions: SECURITY, XC-APPGROUP, XpExtension (print
extension), and an updated, and standardised version of LBX.  X11R6.3 also has
new standards, including RX (X Remote Execution MIME type), and a proxy manage-
ment protocol.	X11R6.3 includes support for gzipped fonts.

R6.1 is an update to R6, and is intended to be compatible with R6 at the source
and protocol levels.  Binaries should be upward-compatible.  X11R6.1 includes
some new Xserver extensions: DOUBLE-BUFFER, XKEYBOARD and RECORD.

What about R6.2?  X11R6.2 is the name given to a subset of X11R6.3, which has
only the print extension and the Xlib implementation of vertical writing and
user-defined character support in addition to those features included in R6.1.


4.  OS issues

Always check the OS specific README files for special requirements or caveats.

Users running Linux/Elf (on Intel platforms) should note that they will need
ld.so-1.7.14.  This can be found at tsx-11.mit.edu:pub/linux/packages/GCC
<URL:ftp://tsx-11.mit.edu/pub/linux/packages/GCC>.

Note: Elf is now the only binary type supported for Linux OSs.	This means that
binaries for ix86/a.out and AXP/ECOFF are not available with this release.


5.  New Features in 3.2A

5.1  General

   o XFree86 3.2A includes the X Consortium's X11R6.3.

5.2  General X server changes

   o The X servers include a new DPMS extension, which was donated by Digital
     Equipment Corporation.  Not all DPMS modes have been implemented by all
     servers yet, but this should improve in the next release.	See the
     XF86Config(4/5) and xset(1) man pages for further details.

   o The LBX extension is included in all the X servers, as part of the update
     to R6.3.

   o A print-only server (Xprt) is included as part of the update to R6.3.

5.3  XF86Setup

   o Some bugs have been fixed, but no major changes have been made to this
     version.

5.4  PC98 Support

   o The XF98_TGUI server includes XAA support, but there are some problems
     with this at the moment.  It can be disabled with the "noaccel" option.

5.5  Alpha (AXP) platform support

   o Support for the S3 ViRGE and ViRGE/VX is now available.

   o Support for "newmmio" is now available for the S3 868/968/Trio64V+.

   o Support for the Matrox Millennium (in the SVGA server) is included.

   o Some problems that showed up with Netscape on some servers have been
     fixed.

   o Various alignment problems have been fixed.

   o NOTE: A recent Linux kernel version is required for most of these servers
     (essential for the Matrox driver).

5.6  XInput Extension

   o Multiple input devices can share the core pointer.

5.7  SVGA server

   o A new general graphics acceleration interface (XFree86 Acceleration Archi-
     tecture - XAA) has been implemented.  It is used to provide relatively
     complete acceleration, at different colour depths, for several chips in
     the SVGA server.  Chips currently making use of this include the Matrox
     Millennium, Tseng ET4000/W32p and ET6000, and several chips from ARK
     Logic, Chips and Technologies, Cirrus, Trident and SiS.

5.8  S3 server

   o Some further S3 968 hardware bugs for lines/text have been worked around.

   o Cursor/pointer pixmaps larger than 64x64 are now supported without the
     need to use the "sw_cursor" option.

   o Preliminary detection/support for the Trio64UV+, Trio64V2 and Aurora64V+
     (86CM65 used in notebooks) is now included.  This support is very new and
     hasn't had much testing, so please send us success/failure reports.

   o Support is now included for the ELSA Winner 2000PRO/X-8.  Please refer to
     the notes for this card in README.S3.

5.9  S3V (ViRGE) server

   o Problems with the Diamond Stealth 3D 3000 are now fixed.

   o The line drawing code has been improved.

   o Preliminary packed 24bpp support is include, but it currently.  has some
     known problems (See README.S3V for details.

   o 32bpp is not supported.

5.10  Mach64 server

   o Support for 3D Rage II based Mach64 cards is included.

   o Various problems with support for some revisions of CT, VT and GT chipsets
     have been fixed.

   o It is strongly recommended that all users with CT, VT, GT and 3D Rage II
     based Mach64 cards upgrade to the 3.2A release due to the problems that
     were fixed.

5.11  Mach32 server

   o A bug that causes problems when running XF86Setup with cards with less
     than 2MB of video memory has been fixed.

5.12  W32 server

   o In this version, the separate W32 server (XF86_W32) has not undergone any
     significant changes. In fact, it is not being developed further. Instead,
     the SVGA server (XF86_SVGA) is now the main focus of new developments. See
     the W32 (SVGA) description.

5.13  I128 server

   o Some preliminary acceleration (for bitblts) is included.  This code is
     very new, and hasn't been extensively tested yet.

5.14  TGA server

   o Preliminary acceleration support is included, using XAA.

   o Various bugs have been fixed.

5.15  Trident driver (SVGA server)

   o Acceleration support has been added for the 9320, 9440 and 96xx chips.

   o Support for the Cyber series of laptop chips has been improved.

5.16  Ark driver (SVGA server)

   o More complete acceleration has been implemented using XAA, including line
     draw, fill, and text acceleration, at different colour depths.

5.17  W32 driver (SVGA server)

   o The SVGA server now supports acceleration for the most recent ET4000W32
     chips. In 3.2A, the ET4000W32p chips are now fully accelerated, and the
     W32p rev C and D also support the higher performing linear memory layout.
     This is the basis for adding hicolor and truecolor support in the future.

5.18  ET6000 driver (SVGA server)

   o The ET6000 driver in the separate W32 server (XF86_W32) has not changed
     significantly.

   o On the other hand, the ET6000 driver in the SVGA server, which already
     existed in XFree 3.2 for all color depths, is now fully accelerated for
     all those color depths. It builds upon the new XAA architecture, which is
     the cornerstone of a new acceleration framework within the XFree86
     servers. It is responsible for the outstanding acceleration performance of
     this release. Of course, since this is a first release of the server using
     this framework, be prepared for some minor problems.

   o Many small problems which existed in the initial 3.2 release have been
     solved. Screen noise, flicker or instability at higher pixel clocks are
     mostly fixed. Some detection problems are gone. Weird behaviour (jumping
     and screen wrap) when panning through large virtual desktops has been
     fixed.

5.19  Alliance ProMotion driver (SVGA server)

   o The driver now recognises the AT24 chipset, but it is treated the same way
     as the AP6422.

5.20  Matrox Millennium driver (SVGA server)

   o More complete acceleration for the MGA2064W.

   o 24 bpp mode tiled pattern problems still present.

   o Support for supports DGA, Sync-on-Green, and DPMS.

   o The "nolinear" option is no longer available.

5.21  Cirrus driver (SVGA server)

   o More complete acceleration for all chips with a BitBLT engine (CL-GD5426,
     5428, 5429, 5430, 5434, 5436, 5440, 5446, 7541, 7543, and 7548).

   o More complete acceleration for Laguna series chips (CL-GD546X).

   o The support for the 754x series of laptop controllers has been improved.

   o The 24bpp mode on the CL-GD5430/40 has been fixed.

5.22  SiS driver (SVGA server)

   o Significant updates have been made to the SiS driver (see README.SiS for
     further details).

   o Acceleration support is included, making use of XAA.

   o Linear addressing is supported.

   o Support has been added for 15/16/24bpp.

   o Support has been added for programmable clocks.

   o HW cursor support is included.

5.23  Chips and Technologies driver (SVGA server)

   o Support has been included for the 65525, 65535, 64200 and 64300

   o Problems relating to blank screen at start-up and text mode restoration
     with the 65550 and 65554 should now be fixed

   o Acceleration support for all chips has improved due to the new XAA archi-
     tecture.

   o Many additional minor fixes and documentation updates (see README.chips
     for further details).

5.24  WD90C24 driver (SVGA server)

   o DPMS support is included (only for "off" mode so far).

5.25  Hercules mono driver

   o The problems with the Hercules mono driver in previous releases has now
     been fixed, and the driver is included in this release.

5.26  Client/Library changes

   o The libraries have been updated to R6.3.  The shared lib version numbers
     for libXext and libICE have been bumped to 6.3.  The others remain the
     same.

   o VT52 emulation has been added to xterm.

   o Some xterm bugs have been fixed, including coloured background exposure
     while selection is active, and missing state changes in the VT100 emula-
     tion.

   o Xterm's memory requirements for colour have been reduced.

   o Emulation of VT220 soft-reset, and non-DEC REP (repeat) control sequence
     has been added to xterm.

   o xset includes support for the DPMS extension.

5.27  SuperProbe

   o Add detection of Alliance Pro Motion chips.

   o Add detection of I128-2.

   o Add detection of S3 Trio64UV+ and Aurora64V+.

   o Add detection of newer Trident chips, including the Cyber series.

5.28  Fonts

   o Gzipped fonts are now supported.





From owner-freebsd-hackers  Fri Feb  7 04:15:53 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id EAA23311
          for hackers-outgoing; Fri, 7 Feb 1997 04:15:53 -0800 (PST)
Received: from dawn.ww.net (root@dawn.ww.net [193.124.73.50])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA23306
          for <freebsd-hackers@freebsd.org>; Fri, 7 Feb 1997 04:15:41 -0800 (PST)
Received: (from alexis@localhost)
	by dawn.ww.net (8.7.5/alexis 2.5)  id PAA09137
	for freebsd-hackers@freebsd.org; Fri, 7 Feb 1997 15:14:54 +0300 (MSK)
Message-Id: <199702071214.PAA09137@dawn.ww.net>
Subject: ipip for FreeBSD
To: freebsd-hackers@freebsd.org
Date: Fri, 7 Feb 1997 15:14:53 +0300 (MSK)
From: Alexis Yushin <alexis@dawn.ww.net>
Reply-To: alexis@ww.net (Alexis Yushin)
X-Office-Phone: +380 65 2 26.1410
X-Home-Phone: +380 65 2 27.0747
X-NIC-Handle: AY23
X-RIPE-Handle: AY6-RIPE
X-Mailer: ELM [version 2.4ME+ PL17 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Greetings,

	Does anyone knows of location of an ipip daemon or other
ip tunnerling software for FreeBSD? Please let me know.
							alexis
-- 
		It's all the same, only the names will change

From owner-freebsd-hackers  Fri Feb  7 04:30:14 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id EAA23986
          for hackers-outgoing; Fri, 7 Feb 1997 04:30:14 -0800 (PST)
Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id EAA23956;
          Fri, 7 Feb 1997 04:30:05 -0800 (PST)
Received: by halloran-eldar.lcs.mit.edu; (5.65v3.2/1.1.8.2/19Aug95-0530PM)
	id AA18092; Fri, 7 Feb 1997 07:29:24 -0500
Date: Fri, 7 Feb 1997 07:29:24 -0500
From: Garrett Wollman <wollman@lcs.mit.edu>
Message-Id: <9702071229.AA18092@halloran-eldar.lcs.mit.edu>
To: Eka Kelana <eka@werty.wasantara.net.id>
Cc: freebsd-hackers@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG, dg@root.com
Subject: Need quick answer
In-Reply-To: <1522A71DB9@bandung.wasantara.net.id>
References: <1522A71DB9@bandung.wasantara.net.id>
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

<<On Fri, 7 Feb 1997 05:28:25 +0700, Eka Kelana <eka@werty.wasantara.net.id> said:

> Hi..
>  I need a good explanation about this code in in_rmx.c:

> ...
>         if (!rt->rt_rmx.rmx_sendpipe && !(rt->rt_rmx.rmx_locks & RTV_SPIPE))
rt-> rt_rmx.rmx_sendpipe = tcp_sendspace;
>         if (!rt->rt_rmx.rmx_recvpipe && !(rt->rt_rmx.rmx_locks & RTV_RPIPE))
rt-> rt_rmx.rmx_recvpipe = tcp_recvspace;
> ...

The reason why that is there is because otherwise tcp_close() won't
save the ssthresh.

> I experienced that it wouldn't allow user program to set the socket buffer
> size. The code in tcp_mss() function is:

This is a bug.  I need to figure out a way to have the user's
selection automatically override the default one in the route, and
(presumably) also prevent tcp_close() from saving the ssthresh in that
case.  If you care to contribute code, I'm fighting other fires right
now and would greatly appreciate it.

-GAWollman

--
Garrett A. Wollman   | O Siem / We are all family / O Siem / We're all the same
wollman@lcs.mit.edu  | O Siem / The fires of freedom 
Opinions not those of| Dance in the burning flame
MIT, LCS, ANA, or NSA|                     - Susan Aglukark and Chad Irschick

From owner-freebsd-hackers  Fri Feb  7 04:42:47 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id EAA24446
          for hackers-outgoing; Fri, 7 Feb 1997 04:42:47 -0800 (PST)
Received: from kremvax.demos.su (kremvax.demos.su [194.87.0.20])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id EAA24441
          for <freebsd-hackers@freebsd.org>; Fri, 7 Feb 1997 04:42:43 -0800 (PST)
Received: by kremvax.demos.su (8.6.13/D) from 0@sinbin.demos.su [194.87.2.95]
          with ESMTP id PAA03472; Fri, 7 Feb 1997 15:41:38 +0300
Received: by sinbin.demos.su id PAA07786;
  (8.6.12/D) Fri, 7 Feb 1997 15:40:57 +0300
From: bag@sinbin.demos.su (Alex G. Bulushev)
Message-Id: <199702071240.PAA07786@sinbin.demos.su>
Subject: Re: ipip for FreeBSD
To: alexis@ww.net
Date: Fri, 7 Feb 1997 15:40:56 +0300 (MSK)
Cc: freebsd-hackers@freebsd.org
In-Reply-To: <199702071214.PAA09137@dawn.ww.net> from "Alexis Yushin" at Feb 7, 97 03:14:53 pm
X-Mailer: ELM [version 2.4 PL24 ME7a]
Content-Type: text
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 
> Greetings,
> 
> 	Does anyone knows of location of an ipip daemon or other
> ip tunnerling software for FreeBSD? Please let me know.
> 							alexis
> -- 
> 		It's all the same, only the names will change
> 

ftp://ftp.ru/pub/hamradio/packet/tcpip/linux/ipip.tar.gz
				       ^^^^^ this is not correct ...
this is port from bsd to linux with original ...
it works fine, i test it under fbsd 2.1.0 & 2.1.5 between two PC
and between PC and cisco ...

   Alex.

From owner-freebsd-hackers  Fri Feb  7 05:21:09 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id FAA25710
          for hackers-outgoing; Fri, 7 Feb 1997 05:21:09 -0800 (PST)
Received: from minas.rosmail.com (minas.rosmail.com [194.87.177.12])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id FAA25705
          for <hackers@freebsd.org>; Fri, 7 Feb 1997 05:21:05 -0800 (PST)
Received: by minas.rosmail.com (8.6.12/SMAIL)
	id QAA00615; Fri, 7 Feb 1997 16:18:23 +0300
Received: by minas.rosmail.com (ITS 2.1); Fri, 07 Feb 97 16:18:23 +0300
Date: Fri, 07 Feb 97 16:18:23 +0300
Message-Id: <970207-161823-00600@minas.rosmail.com>
From: "ðÁÞËÕÒÉÑ" <avianet@minas.rosmail.com>
Subject: X.25
To: hackers@freebsd.org
X-Mailer: ITS [version 2.1]
MIME-Version: 1.0
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 8bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

	Have FreeBSD any support for protocol X.25, for example,
a driver for Eicon-card. We have a telematics Swich, and the clients
X.28 incomming havent E-mail access. What to do?
		Sergey Nikiforov

From owner-freebsd-hackers  Fri Feb  7 05:58:01 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id FAA27757
          for hackers-outgoing; Fri, 7 Feb 1997 05:58:01 -0800 (PST)
Received: from nic.follonett.no (nic.follonett.no [194.198.43.10])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA27751
          for <hackers@freebsd.org>; Fri, 7 Feb 1997 05:57:53 -0800 (PST)
Received: (from uucp@localhost) by nic.follonett.no (8.8.5/8.8.3) with UUCP id OAA28673; Fri, 7 Feb 1997 14:56:05 +0100 (MET)
Received: from oo7 (oo7.dimaga.com [192.0.0.65]) by dimaga.com (8.7.5/8.7.2) with SMTP id OAA07944; Fri, 7 Feb 1997 14:50:17 +0100 (MET)
Message-Id: <3.0.32.19970207145017.00a819c0@dimaga.com>
X-Sender: eivind@dimaga.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Fri, 07 Feb 1997 14:50:18 +0100
To: dennis <dennis@etinc.com>
From: Eivind Eklund <eivind@dimaga.com>
Subject: Re: 2.1.6?
Cc: hackers@freebsd.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

At 03:20 PM 2/6/97 -0500, you wrote:
>
>Whats with 2.1.6R? What happened to the packages section on
>the ftp server?

Security problem which had a lot of people feeling extra threathened
because of the number of binaries it hit - but a security hole is a
security hole until it is patched, and how many different things an
intruder can write at the command line to get root doesn't really matter,
as long as a single patch can fix it.

An extraordinary release 2.1.7 is being rolled within a few days to remove
this hole (and numerous others).  A patch was released recently - check out
http://www.freebsd.org/newsflash.html for more info.
I believe a binary patchkit is also in the works, dropping the need for
full recompile.


Eivind Eklund  perhaps@yes.no  http://maybe.yes.no/perhaps/
eivind@freebsd.org


From owner-freebsd-hackers  Fri Feb  7 07:54:27 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id HAA03376
          for hackers-outgoing; Fri, 7 Feb 1997 07:54:27 -0800 (PST)
Received: from gatekeeper.fsl.noaa.gov (gatekeeper.fsl.noaa.gov [137.75.131.181])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA03371
          for <hackers@FreeBSD.ORG>; Fri, 7 Feb 1997 07:54:25 -0800 (PST)
Received: from cardinal.fsl.noaa.gov (daemon@cardinal.fsl.noaa.gov [137.75.60.101])
	by gatekeeper.fsl.noaa.gov (8.8.5/8.8.5) with ESMTP id PAA13713;
	Fri, 7 Feb 1997 15:54:24 GMT
Received: from auk.fsl.noaa.gov by cardinal.fsl.noaa.gov with SMTP
	(1.40.112.3/16.2) id AA154050863; Fri, 7 Feb 1997 15:54:23 GMT
Message-Id: <32FB502E.3171@fsl.noaa.gov>
Date: Fri, 07 Feb 1997 08:54:22 -0700
From: Sean Kelly <kelly@fsl.noaa.gov>
Organization: CIRA/NOAA
X-Mailer: Mozilla 3.0Gold (X11; I; HP-UX B.10.10 9000/725)
Mime-Version: 1.0
To: Ollivier Robert <roberto@keltia.freenix.fr>
Cc: hackers@FreeBSD.ORG
Subject: Re: PD PDF viewer? was: barracuda jumpers
References: <32FA9D56.167EB0E7@whistle.com> <199702070345.TAA22194@bitch.Melmac.org> <19970207065358.IU34422@keltia.freenix.fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Ollivier Robert wrote:

> The acroread linux binary works pretty well too. See
> /usr/ports/print/acroread.

As does Ghostscript 3.53 on PDF files.

-- 
Sean Kelly                          
NOAA Forecast Systems Laboratory    kelly@fsl.noaa.gov
Boulder Colorado USA                http://www-sdd.fsl.noaa.gov/~kelly/

From owner-freebsd-hackers  Fri Feb  7 08:33:11 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id IAA05368
          for hackers-outgoing; Fri, 7 Feb 1997 08:33:11 -0800 (PST)
Received: from sumatra.americantv.com (sumatra.americantv.com [199.184.181.250])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA05363
          for <hackers@freebsd.org>; Fri, 7 Feb 1997 08:33:08 -0800 (PST)
Received: from right.PCS (right.pcs. [148.105.10.31]) by sumatra.americantv.com (8.7.6/8.7.3) with ESMTP id KAA09299; Fri, 7 Feb 1997 10:50:39 -0600 (CST)
Received: (jlemon@localhost) by right.PCS (8.6.13/8.6.4) id QAA28811; Fri, 7 Feb 1997 16:32:17 GMT
Message-ID: <Mutt.19970207103215.jlemon@right.PCS>
Date: Fri, 7 Feb 1997 10:32:15 -0600
From: jlemon@americantv.com (Jonathan Lemon)
To: kelly@fsl.noaa.gov (Sean Kelly)
Cc: roberto@keltia.freenix.fr (Ollivier Robert), hackers@freebsd.org
Subject: Re: PD PDF viewer? was: barracuda jumpers
References: <32FA9D56.167EB0E7@whistle.com> <199702070345.TAA22194@bitch.Melmac.org> <19970207065358.IU34422@keltia.freenix.fr> <32FB502E.3171@fsl.noaa.gov>
X-Mailer: Mutt 0.56e
Mime-Version: 1.0
In-Reply-To: <32FB502E.3171@fsl.noaa.gov>; from Sean Kelly on Feb 7, 1997 08:54:22 -0700
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Sean Kelly writes:
> Ollivier Robert wrote:
> 
> > The acroread linux binary works pretty well too. See
> > /usr/ports/print/acroread.
> 
> As does Ghostscript 3.53 on PDF files.

Except, AFAIK, neither Ghostscript nor xpdf will deal with 'encoded' PDF
files (like the Intel chip manuals).
--
Jonathan

From owner-freebsd-hackers  Fri Feb  7 08:59:06 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id IAA06438
          for hackers-outgoing; Fri, 7 Feb 1997 08:59:06 -0800 (PST)
Received: from tdc.on.ca (tdc.on.ca [204.92.242.39])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA06426
          for <hackers@FreeBSD.org>; Fri, 7 Feb 1997 08:58:58 -0800 (PST)
Received: (from martin@localhost) by tdc.on.ca (8.7.5/8.6.6) id LAA11990; Fri, 7 Feb 1997 11:57:23 -0500 (EST)
From: Martin Renters <martin@tdc.on.ca>
Message-Id: <199702071657.LAA11990@tdc.on.ca>
Subject: Re: Booting FreeBSD from solid-state-disk
To: dirk@hal.IN-Berlin.DE (Dirk Froemberg)
Date: Fri, 7 Feb 1997 11:57:22 -0500 (EST)
Cc: hackers@FreeBSD.org
In-Reply-To: <Mutt.19970203123525.dirk@hal.IN-Berlin.DE> from "Dirk Froemberg" at Feb 3, 97 12:35:25 pm
X-Mailer: ELM [version 2.4 PL24 ME8a]
Content-Type: text
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> 
> Dear hackers!
> 
> I'm trying to boot FreeBSD from a solid-state-disk.
> 
> The first 4K of the card is a bios extension mapping access to drive 80 (C:)
> via the bios to the memory on the card.
> 
> My first approach
> 
> 	cat bios-extension rawboot kernel-with-mfs-in-it > "/dev/card"	.
> 
> was successfull on the first shot... 8) Unfortunally the mfs within the
> kernel lacks of the kernel itself, unless one doesn't want to duplicate
> it. So ps, netstat, ... are useless.

I got around this by putting a file called 'kernel' in the MFS which
is an empty executable with the symbol table from the real kernel.  netstat
works after you do that.

Martin

From owner-freebsd-hackers  Fri Feb  7 09:10:27 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA07229
          for hackers-outgoing; Fri, 7 Feb 1997 09:10:27 -0800 (PST)
Received: from bmcgover-pc.cisco.com (bmcgover-pc.cisco.com [171.69.104.147])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA07224
          for <hackers@freebsd.org>; Fri, 7 Feb 1997 09:10:23 -0800 (PST)
Received: from bmcgover-pc.cisco.com (localhost.cisco.com [127.0.0.1]) by bmcgover-pc.cisco.com (8.8.5/8.8.2) with ESMTP id BAA00343; Sat, 8 Feb 1997 01:06:57 -0500 (EST)
Message-Id: <199702080606.BAA00343@bmcgover-pc.cisco.com>
To: dg@root.com, support@cyclades.com
cc: waz@cyclades.com, hackers@freebsd.org
Subject: Flow control on Cyclades boards???
Date: Sat, 08 Feb 1997 01:06:57 -0500
From: Brian McGovern <bmcgover@cisco.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Ok. I now have the boards up and running between machines, but I'm having a 
problem with silo overflows almost constantly on all the currently running 
ports. I'm using pppd (options listed below) to set up a number of ppp
sessions between two pentium pro 200s. 

I originally tried to run 32 of them at 115200. It failed miserably. I then
dropped back to 16 at 115200. Then to 16 at 57600. Still got silo
errors constantly.

At this point, I thought it might be a flow-control issue, so I tried to
make some changes to /etc/ppp/options to allow for flow control, but I'm
not getting anywhere. Perhaps someone can give me some more useful information?


/etc/ppp/options
----------------
-bsdcomp 
-defaultroute
persist
crtscts


I've also tried xonxoff as an option (both ends are identical except for
the persist line - only the call negotiator has this).

i've also tried to use /etc/rc.serial to set some initial and lock states
(including most variations on the crtscts, ixon, and ixany flags).

Any help would be appreciated.
	-Brian

From owner-freebsd-hackers  Fri Feb  7 09:39:18 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA08951
          for hackers-outgoing; Fri, 7 Feb 1997 09:39:18 -0800 (PST)
Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA08946
          for <hackers@freebsd.org>; Fri, 7 Feb 1997 09:39:15 -0800 (PST)
Received: from ntws (ntws.etinc.com [204.141.95.142]) by etinc.com (8.8.3/8.6.9) with SMTP id MAA09452; Fri, 7 Feb 1997 12:42:27 -0500 (EST)
Message-Id: <3.0.32.19970207123856.00afe4e0@etinc.com>
X-Sender: dennis@etinc.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Fri, 07 Feb 1997 12:39:01 -0500
To: =?iso-8859-1?Q?=22=F0=C1=DE=CB=D5=D2=C9=D1=22?= <avianet@minas.rosmail.com>,
        hackers@freebsd.org
From: dennis <dennis@etinc.com>
Subject: Re: X.25
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by freefall.freebsd.org id JAA08947
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

At 04:18 PM 2/7/97 +0300, ðÁÞËÕÒÉ wrote:
>	Have FreeBSD any support for protocol X.25, for example,
>a driver for Eicon-card. We have a telematics Swich, and the clients
>X.28 incomming havent E-mail access. What to do?
>		Sergey Nikiforov
>
We've been fiddling with the netccitt stuff to work with our boards...but
its not exactly a priority project.

Dennis

From owner-freebsd-hackers  Fri Feb  7 09:53:24 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA09651
          for hackers-outgoing; Fri, 7 Feb 1997 09:53:24 -0800 (PST)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA09644
          for <freebsd-hackers@freebsd.org>; Fri, 7 Feb 1997 09:53:20 -0800 (PST)
Received: from rover.village.org [127.0.0.1] 
	by rover.village.org with esmtp (Exim 0.56 #1)
	id E0vsuTa-0000cH-00; Fri, 7 Feb 1997 10:52:42 -0700
To: Tim Vanderhoek <hoek@freenet.hamilton.on.ca>
Subject: Re: My resignation as president of the FreeBSD Project. 
Cc: Leonard Chua <lenc@earth.infinetconsulting.com>, jkh@time.cdrom.com,
        freebsd-hackers@freebsd.org
In-reply-to: Your message of "Thu, 06 Feb 1997 18:17:15 EST."
		<Pine.GSO.3.95.970206181426.8426A-100000@james.freenet.hamilton.on.ca> 
References: <Pine.GSO.3.95.970206181426.8426A-100000@james.freenet.hamilton.on.ca>  
Date: Fri, 07 Feb 1997 10:52:42 -0700
From: Warner Losh <imp@village.org>
Message-Id: <E0vsuTa-0000cH-00@rover.village.org>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <Pine.GSO.3.95.970206181426.8426A-100000@james.freenet.hamilton.on.ca> Tim Vanderhoek writes:
: "member Jordan"  Or was that "Citizen Jordan", or should it be

Yes.  "Citizen Jordan," much like "Citizen Kane".  Years from now,
when his BSD empire has crumbled into dust, he'll pass quietly holding
a novelty deamon toy from some Usenix muttering the word "freefall."

Warner

P.S. Bouns points for anybody that can tell me where Orson Wells got
"rosebud" from. :-)

From owner-freebsd-hackers  Fri Feb  7 10:12:42 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id KAA10523
          for hackers-outgoing; Fri, 7 Feb 1997 10:12:42 -0800 (PST)
Received: from vector.jhs.no_domain (slip139-92-4-168.mu.de.ibm.net [139.92.4.168])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA10516
          for <hackers@freebsd.org>; Fri, 7 Feb 1997 10:12:34 -0800 (PST)
Received: (from jhs@localhost) by vector.jhs.no_domain (8.7.5/8.6.9) id OAA01789; Fri, 7 Feb 1997 14:51:39 +0100 (MET)
Date: Fri, 7 Feb 1997 14:51:39 +0100 (MET)
Message-Id: <199702071351.OAA01789@vector.jhs.no_domain>
To: hackers@freebsd.org
Subject:  Anyone know of cheapish Voice Input hard & software ?
From: "Julian H. Stacey" <jhs@freebsd.org>
Reply-To: "Julian H. Stacey" <jhs@freebsd.org>
X-Organization: Vector Systems Ltd.
X-Mailer: EXMH 1.6.7, PGP available
X-Address: Holz Strasse 27d, 80469 Munich, Germany
X-Tel: +49.89.268616
X-Fax: +49.89.2608126
X-ISDN: +49.89.26023276
X-Web: http://www.freebsd.org/~jhs/
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Anyone know of cheapish (ie personal budget) voice input hard & software
we might be able to now or soon attach to FreeBSD ?
  Something where I could speak in my normal voice to a microphone & get some
  Ascii out, even if with a few typos ?  So I could `type up' notes after
  phone calls I make & maybe compose draft docs/email with :-)
PS  Please leave <jhs@freebsd.org> on the CC line, Thanks :-)

Julian
---
Julian H. Stacey	jhs@freebsd.org		http://www.freebsd.org/~jhs/

From owner-freebsd-hackers  Fri Feb  7 10:23:44 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id KAA10998
          for hackers-outgoing; Fri, 7 Feb 1997 10:23:44 -0800 (PST)
Received: from humvee.doit.wisc.edu (humvee.doit.wisc.edu [144.92.9.20])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA10993
          for <freebsd-hackers@FreeBSD.ORG>; Fri, 7 Feb 1997 10:23:42 -0800 (PST)
Received: from audumla.students.wisc.edu by humvee.doit.wisc.edu;
          id MAA78216; 8.7.5/50; Fri, 7 Feb 1997 12:23:35 -0600
Received: from gabor-bsd by audumla.students.wisc.edu;
          id MAA66696; 8.6.9W/42; Fri, 7 Feb 1997 12:21:06 -0600
Message-ID: <32FB72E0.2781E494@acm.org>
Date: Fri, 07 Feb 1997 12:22:24 -0600
From: Gabor Kincses <gabor@acm.org>
X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.1.5-RELEASE i386)
MIME-Version: 1.0
To: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de>
CC: freebsd-hackers@FreeBSD.ORG
Subject: Re: Panic in probe, but no dump
References: <32FA29A1.41C67EA6@acm.org> <Mutt.19970207005345.j@uriah.heep.sax.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

J Wunsch wrote:
> 
> (Mailing lists trimmed.  Whenever you feel like posting to more than
> one list, you probably feel wrong. ;-)

Desperation speeds up the fingers and slows down the gray stuff.

> As Gabor Kincses wrote:
> 
> > The problem I have is to get a dump out of the sound driver probe.  I
> > pretty much followed the handbook on this.  I have set config root on
> > wd2 dumps on wd2 in my config file, but no dump occurred (I checked .  I
> 
> Well, the normal sequence is to use `dumpon'.  This is also supported
> by /etc/sysconfig.

AFAIK that is not an option here, since we are not executing /etc/rc,
yet.

> > 1. Is there a way to load the kernel.debug in gdb and correlate
> > addresses with lines of code?  (Like on HP-UX w/ xdb: one can use 'td')
> 
> Basically, though a little hard.  Please, read the section about
> kernel debugging in the handbook (gdb -k aka. kgdb).

I did.  Before I started all this.  It seems that once I can single step
or have a dump it will print the addresses.  In xdb I can 'td' (toggle
disassembly) and voila I see the machine instructions with line numbers
next to the ones that start a line.  I'm looking for a similar feature.

> > 2. Why am I not getting a core dump?
> 
> No idea.  What did the kernel say?  Did it say ``dumping to ...''?

No, it did not.  I guess there might be a bug in handling the panic.  I
did have a dump device configured.  I will triple-check this one.  No
need to accuse the designer in case of pilot error.

> > save the kernel core, or is it already on the swap device?  Ie. what
> > macroscopic events would tell me that I got a dump?  (Possibly: "core
> > dumped" msg on the console :-)
> 
> Almost.  Dumping to dev ...., followed by the number of outstanding
> megabytes to be dumped.

That is good info, I didn't see anything like that.  The panic message
printed the current EIP, then "waiting 15 seconds to reboot" or
something like that.

> > 3. I have turned on savecore in /etc/sysconfig, but I have noticed that
> > the swapon gets executed first in /etc/rc before the savecore.  Wouldn't
> > this wipe out a core in the swap device?
> 
> No.  The dump is done to the end of the swap partition.
> 
> > 5. Is my only option left is ddb?
> 
> Your best one.  Note that you can also force a dump from within DDB by
> saying `panic' (followed by `c').

20.3. call diediedie().  I'll try that.  ddb looks fairly similar to adb
on HP-UX.  Probably share roots, too.

> > 6. Is a page fault essentially like a segmentation violation in user
> > mode?  AFAIK on i386 you have to install a page fault handler, which is
> > probably what the VM is all about.  Is this true?
> 
> Well, basically.  A page fault normally tries to see if it has to load
> a page from secondary storage.  If there's no page to load, it will be
> reported.  By a SIGSEGV to a user process, by a panic (or a jump into
> DDB) in the kernel.
> 
> > 7. Why is the "dumps on" feature being deprecated?  How else can we get
> > a dump if the system crashes before dumpon can be executed?  BTW, My
> 

Thanks for your help.  DDB here I come!

-- 
Gabor Kincses
(gabor@acm.org)

From owner-freebsd-hackers  Fri Feb  7 10:28:08 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id KAA11180
          for hackers-outgoing; Fri, 7 Feb 1997 10:28:08 -0800 (PST)
Received: from super-g.inch.com (super-g.com [204.178.32.161])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA11175
          for <freebsd-hackers@freebsd.org>; Fri, 7 Feb 1997 10:28:06 -0800 (PST)
Received: from localhost (spork@localhost) by super-g.inch.com (8.8.5/8.6.9) with SMTP id NAA03510; Fri, 7 Feb 1997 13:29:43 -0500 (EST)
Date: Fri, 7 Feb 1997 13:29:42 -0500 (EST)
From: spork <spork@super-g.com>
X-Sender: spork@super-g.inch.com
To: Warner Losh <imp@village.org>
cc: Tim Vanderhoek <hoek@freenet.hamilton.on.ca>,
        Leonard Chua <lenc@earth.infinetconsulting.com>, jkh@time.cdrom.com,
        freebsd-hackers@freebsd.org
Subject: Re: My resignation as president of the FreeBSD Project. 
In-Reply-To: <E0vsuTa-0000cH-00@rover.village.org>
Message-ID: <Pine.BSF.3.95.970207132801.3507A-100000@super-g.inch.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Fri, 7 Feb 1997, Warner Losh wrote:

> 
> P.S. Bouns points for anybody that can tell me where Orson Wells got
> "rosebud" from. :-)
> 

Now I'm not sure on this, but I think it has something to do with a part
of the female anatomy...  I had a Freudian analysis English teacher in
High School, so it might have just been his twisted idea of "correct"...

Charles


From owner-freebsd-hackers  Fri Feb  7 11:02:13 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA12711
          for hackers-outgoing; Fri, 7 Feb 1997 11:02:13 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA12693
          for <hackers@freebsd.org>; Fri, 7 Feb 1997 11:02:10 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id GAA13110; Sat, 8 Feb 1997 06:00:19 +1100
Date: Sat, 8 Feb 1997 06:00:19 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199702071900.GAA13110@godzilla.zeta.org.au>
To: bmcgover@cisco.com, dg@root.com, support@cyclades.com
Subject: Re: Flow control on Cyclades boards???
Cc: hackers@freebsd.org, waz@cyclades.com
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>Ok. I now have the boards up and running between machines, but I'm having a 
>problem with silo overflows almost constantly on all the currently running 
>ports. I'm using pppd (options listed below) to set up a number of ppp
>sessions between two pentium pro 200s. 
>
>I originally tried to run 32 of them at 115200. It failed miserably. I then
>dropped back to 16 at 115200. Then to 16 at 57600. Still got silo
>errors constantly.

The PCI Cyclades driver doesn't support "fast" interrupt handlers yet
(because the PCI interrupt dispatcher doesn't), so at 115200 bps,
each fully active port will get N fifo full's worth of silo overflows
(12 * N characters) whenever the kernel disables tty interrupts for
N milliseconds.  The kernel sometimes disables tty interrupts for
several milliseconds.  This can't be fixed using flow control or any
other configuration option.

Bruce

From owner-freebsd-hackers  Fri Feb  7 11:36:39 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA14914
          for hackers-outgoing; Fri, 7 Feb 1997 11:36:39 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA14906
          for <freebsd-hackers@FreeBSD.ORG>; Fri, 7 Feb 1997 11:36:37 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id GAA14065; Sat, 8 Feb 1997 06:35:14 +1100
Date: Sat, 8 Feb 1997 06:35:14 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199702071935.GAA14065@godzilla.zeta.org.au>
To: gabor@acm.org, joerg_wunsch@uriah.heep.sax.de
Subject: Re: Panic in probe, but no dump
Cc: freebsd-hackers@FreeBSD.ORG
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>> > 1. Is there a way to load the kernel.debug in gdb and correlate
>> > addresses with lines of code?  (Like on HP-UX w/ xdb: one can use 'td')
>> 
>> Basically, though a little hard.  Please, read the section about
>> kernel debugging in the handbook (gdb -k aka. kgdb).
>
>I did.  Before I started all this.  It seems that once I can single step
>or have a dump it will print the addresses.  In xdb I can 'td' (toggle
>disassembly) and voila I see the machine instructions with line numbers
>next to the ones that start a line.  I'm looking for a similar feature.

	display/i $pc
	stepi ...

>No, it did not.  I guess there might be a bug in handling the panic.  I
>did have a dump device configured.  I will triple-check this one.  No
>need to accuse the designer in case of pilot error.
>
>> > save the kernel core, or is it already on the swap device?  Ie. what
>> > macroscopic events would tell me that I got a dump?  (Possibly: "core
>> > dumped" msg on the console :-)
>> 
>> Almost.  Dumping to dev ...., followed by the number of outstanding
>> megabytes to be dumped.
>
>That is good info, I didn't see anything like that.  The panic message
>printed the current EIP, then "waiting 15 seconds to reboot" or
>something like that.

It won't dump unless the driver for the dump device has been configured.
Don't expect dumps to work if a panic occurs in a device driver probe/
attach.

Who needs dumps?  Just use remote gdb or (local) ddb on the running
kernel.  kerneldebug.sgml is a bit out of date - it doesn't mention
remote gdb.

>> Your best one.  Note that you can also force a dump from within DDB by
>> saying `panic' (followed by `c').
>
>20.3. call diediedie().  I'll try that.  ddb looks fairly similar to adb
>on HP-UX.  Probably share roots, too.

Use the builtin panic command.  diediedie() doesn't exist.
kerneldebug.sgml is more than a bit out of date :-).

>> > 7. Why is the "dumps on" feature being deprecated?  How else can we get

Because it may dump in the wrong place on incompletely configured disks.

>> > a dump if the system crashes before dumpon can be executed?  BTW, My

`call setdumpdev(device_number)' in a debugger might work.

Bruce

From owner-freebsd-hackers  Fri Feb  7 11:40:56 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA15138
          for hackers-outgoing; Fri, 7 Feb 1997 11:40:56 -0800 (PST)
Received: from white.dogwood.com (white.dogwood.com [140.174.96.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA15133
          for <freebsd-hackers@freebsd.org>; Fri, 7 Feb 1997 11:40:54 -0800 (PST)
Received: (from dave@localhost)
	by white.dogwood.com (8.8.5/8.8.5) id LAA21204;
	Fri, 7 Feb 1997 11:40:48 -0800 (PST)
From: Dave Cornejo <dave@dogwood.com>
Message-Id: <199702071940.LAA21204@white.dogwood.com>
Subject: Re: My resignation as president of the FreeBSD Project.
In-Reply-To: <Pine.BSF.3.95.970207132801.3507A-100000@super-g.inch.com> from spork at "Feb 7, 97 01:29:42 pm"
To: spork@super-g.com (spork)
Date: Fri, 7 Feb 1997 11:40:47 -0800 (PST)
Cc: freebsd-hackers@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL30 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

spork wrote:
> On Fri, 7 Feb 1997, Warner Losh wrote:
> > P.S. Bouns points for anybody that can tell me where Orson Wells got
> > "rosebud" from. :-)
> 
> Now I'm not sure on this, but I think it has something to do with a part
> of the female anatomy...  I had a Freudian analysis English teacher in
> High School, so it might have just been his twisted idea of "correct"...

Rosebud was the name on the sled which belonged to Kane in the movie
"Citizen Kane" - the flick which made Orson famous.

I think...

-- 
Dave Cornejo - Dogwood Media, Fremont, California

From owner-freebsd-hackers  Fri Feb  7 12:06:53 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA16500
          for hackers-outgoing; Fri, 7 Feb 1997 12:06:53 -0800 (PST)
Received: from iworks.InterWorks.org (deischen@iworks.interworks.org [128.255.18.10])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA16478
          for <freebsd-hackers@FreeBSD.ORG>; Fri, 7 Feb 1997 12:06:42 -0800 (PST)
Received: (from deischen@localhost) by iworks.InterWorks.org (8.7.5/) id OAA28491; Fri, 7 Feb 1997 14:06:33 -0600 (CST)
Message-Id: <199702072006.OAA28491@iworks.InterWorks.org>
Date: Fri, 7 Feb 1997 14:06:33 -0600 (CST)
From: "Daniel M. Eischen" <deischen@iworks.InterWorks.org>
To: imp@village.org, owner-freebsd-hackers@freefall.freebsd.org
Subject: Re: My resignation as president of the FreeBSD Project.
Cc: freebsd-hackers@FreeBSD.ORG, hoek@freenet.hamilton.on.ca,
        jkh@time.cdrom.com, lenc@earth.infinetconsulting.com
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> On Fri, 7 Feb 1997, Warner Losh wrote:
>
> > 
> > P.S. Bouns points for anybody that can tell me where Orson Wells got
> > "rosebud" from. :-)
> > 
> 
> Now I'm not sure on this, but I think it has something to do with a part
> of the female anatomy...  I had a Freudian analysis English teacher in
> High School, so it might have just been his twisted idea of "correct"...
>
> Charles

Yep, Rosebud was the name Randolph Hearst gave to Marion Davies c______s.

[ I cheated and used the Internet Movie Database - since they are
  powered by Apache and FreeBSD, I didn't think anyone would mind ;-) ]

Dan Eischen
deischen@iworks.InterWorks.org

From owner-freebsd-hackers  Fri Feb  7 12:19:06 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA17075
          for hackers-outgoing; Fri, 7 Feb 1997 12:19:06 -0800 (PST)
Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA17069
          for <hackers@freebsd.org>; Fri, 7 Feb 1997 12:19:01 -0800 (PST)
Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33])
          by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP
	  id VAA02211 for <hackers@freebsd.org>; Fri, 7 Feb 1997 21:18:53 +0100
Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id VAA11692 for hackers@freebsd.org; Fri, 7 Feb 1997 21:18:39 +0100
Received: (from roberto@localhost) by keltia.freenix.fr (8.8.5/keltia-uucp-2.9) id TAA17370;
          Fri, 7 Feb 1997 19:08:48 +0100 (CET)
Message-ID: <19970207190847.SA13336@keltia.freenix.fr>
Date: Fri, 7 Feb 1997 19:08:47 +0100
From: roberto@keltia.freenix.fr (Ollivier Robert)
To: hackers@freebsd.org
Subject: Re: PD PDF viewer? was: barracuda jumpers
References: <9702071012.AA22010@cssmuc.frt.dec.com>
X-Mailer: Mutt 0.60,1-3,9
Mime-Version: 1.0
X-Operating-System: FreeBSD 3.0-CURRENT ctm#2999
In-Reply-To: <9702071012.AA22010@cssmuc.frt.dec.com>; from garyj@frt.dec.com on Feb 7, 1997 11:12:45 +0100
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

According to garyj@frt.dec.com:
> I installed acroread and the linux libraries from ports, but every time
> I try to run acroread it catches a segementation fault :( I ktrace'd it,
> but can't see exactly where the problem lies.

A friend of mine also get SEGV when using Linux programs, under 2.2-BETA I
think. I don't know how to fix that as both my work and home machines don't
have this problem.

> This under 3.0, BTW.

Same.

> My LKMs are up-to-date with the kernel and I start the linux emulation
> from /etc/rc.i386.

Same.

> DOOM works, so the linux emulation is obviously also working.
> 
> Does acroread need netscape ? I use a rather old version of netscape.

I don't think it is using it when you run acroread. Netscape is able to run
acroread when fetching a PDF file that's all. FWIW I have 3.0 and 3.01
BSD/OS versions.
-- 
Ollivier ROBERT    -=- The daemon is FREE! -=-    roberto@keltia.freenix.fr
  FreeBSD keltia.freenix.fr 3.0-CURRENT #39: Sun Feb  2 22:12:44 CET 1997

From owner-freebsd-hackers  Fri Feb  7 12:41:30 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA18331
          for hackers-outgoing; Fri, 7 Feb 1997 12:41:30 -0800 (PST)
Received: from sendero.i-connect.net ([206.190.144.100])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA18325;
          Fri, 7 Feb 1997 12:41:26 -0800 (PST)
Received: (from shimon@localhost)
          by sendero.i-connect.net (8.8.5/8.8.4)
	  id NAA20750; Fri, 7 Feb 1997 13:40:32 -0800 (PST)
Message-ID: <XFMail.970207134032.Shimon@i-Connect.Net>
X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD
Content-Type: text/plain; charset=iso-8859-8
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <199702070238.NAA09135@genesis.atrad.adelaide.edu.au>
Date: Fri, 07 Feb 1997 12:24:52 -0800 (PST)
Organization: iConnect Corp.
From: Simon Shapiro <Shimon@i-Connect.Net>
To: Michael Smith <msmith@atrad.adelaide.edu.au>
Subject: Re: Contigious (spelling?) allocation in kernel
Cc: freebsd-scsi@freebsd.org, freebsd-hackers@freebsd.org,
        toor@dyson.iquest.net
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Hi Michael Smith;  On 07-Feb-97 you wrote: 

...

> Er, from my understanding the kva space tends to become fragmented, and
> your chances of being able to allocate contiguous memory tend to
> be reduced.

So failure is defined here as ``refusal to provide resource requested'',
but not ``crash the system or other unexpected result''.
This we can live with.

> > I can re-structure the driver a bit (make it more risky), to 
> > avoid the need for large contigious blocks, but the (obvious)
> > question is:  Does the kernel malloc guarantee that allocations
> > smaller than (or equal to) a page are in the same page?
> 
> Can't answer that, sorry.  Look at the source 8)

I think the answer is yes.

> > Having a page or less, limits the Scatter/Gather operations in
> > the kernel, for most hardware, to 512 entries (segments).  
> > Under high fragmentation, this can result in 256KB-2MB floating
> > limit.  While not a problem for most applications (mine
> > included), it is still a limit that is not absolutely necessary.
> 
> TBH, a 256K I/O is likely to be bigger than most peripherals can do
> anything useful with.  I would be inclined to say that the 
> overhead of splitting that into seperate transactions is likely
> to be small compared with the size of the transaction.

It all depends on the device.  Some high speed tapes, printers,
CD Writers, can use large blocks.  Most O/S's do not know what to do
with large blocks, though...

> > BACKGROUND:  One of my engineers, who is heavily involved in 
> > Linux SCSI development is strongly opposed to calling malloc on
> > demand in a device driver.  He quotes heavy performance
> > penalties, and worse;  Failure (under heavy load) to obtain the
> > memory when needed.
> 
> They're right on the ball; avoid allocating memory on the fly wherever
> possible. 8)

I know, I know... :-)

thanx,

Simon

From owner-freebsd-hackers  Fri Feb  7 12:45:25 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA18575
          for hackers-outgoing; Fri, 7 Feb 1997 12:45:25 -0800 (PST)
Received: from wacky.acet.org.noname ([192.188.104.18])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA18553;
          Fri, 7 Feb 1997 12:45:11 -0800 (PST)
Received: from wacky (localhost.acet.org) by wacky.acet.org.noname (4.1/SMI-4.1)
	id AA05464; Fri, 7 Feb 97 15:44:58 EST
Message-Id: <32FB9449.2781E494@mitre.org>
Date: Fri, 07 Feb 1997 15:44:58 -0500
From: George Uhl <guhl@mitre.org>
X-Mailer: Mozilla 3.01 (X11; I; SunOS 4.1.4 sun4m)
Mime-Version: 1.0
To: freebsd-hackers@FreeBSD.org
Cc: freebsd-bugs@FreeBSD.org
Subject: Interrupt/Terminate Signal causes page fault in kernel mode
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

I'm porting a version of OSI and X.25 from a heavily modified BSDI ver
1.1
to FreeBSD 2.1.6.  I'm running an application with a TP4 socket (OSI's
version of a
reliable, connection-oriented transport-layer socket) that is causing
the kernel
to crash when it is interrupted/killed by a signal (control-c, kill -9,
etc.).

The application is waiting for comm traffic (e.g., is listening for a
connect,
or is connected and waiting for data) and it receives the signal.  Then
the 
kernel crashes with:

Fatal trap 12: page fault while in kernel mode
Fault virtual address		= 0x8
Fault code			= supervisor read, page not present
Instruction pointer		= 0x8:0xf010d620
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			= 259 (tisink)
interrupt mask			=
kernel: type 12 trap. code=0
Stopped at	_exit1+0xc4 [/sys/compile/PORT1/:163]:	movl	0x8(%ebp),%esi

The source code statement (line 163 in /sys/kern/kern_exit.c) from the
kernel is:

if (SESS_LEADER(p)) {

which translates to:

if (p->p_session->s_leader == p) {

At this point register %ebp is NULL. p is the pointer to the process
descriptor for the
application. I've use ddb to examine the registers, when the fdfree
function is called 
from exit1 the ebp register contains a pointer to the kernel stack plus
some offset.
Just prior to leaving fdfree and returning to exit1, ebp is set to
zero.  The fdfree
function does a closef on the socket fd which in turn calls a detach
function in the
OSI TP code.

If I hack the exit1 function and put a statement like a printf or an
if(0); prior to
the call to untimeout or fdfree, the kernel doesn't crash.  This seems
like a timing
problem to me, but I'm not sure who or what is messing around with my
process
descriptor pointer.  The OSI TP detach function releases OSI protocol
data strcutures
(like the TP4 and CLNP protocol control blocks) and frees the socket. I
don't think
the problem is in the detach code.  Does anyone have any ideas?
-- 
George

From owner-freebsd-hackers  Fri Feb  7 12:55:32 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA19269
          for hackers-outgoing; Fri, 7 Feb 1997 12:55:32 -0800 (PST)
Received: from earth.infinetconsulting.com (earth.infinetconsulting.com [207.23.43.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA19250;
          Fri, 7 Feb 1997 12:55:26 -0800 (PST)
Received: (from lenc@localhost) by earth.infinetconsulting.com (8.8.3/8.6.12) id NAA17467; Fri, 7 Feb 1997 13:09:43 -0800 (PST)
Date: Fri, 7 Feb 1997 13:09:43 -0800 (PST)
From: Leonard Chua <lenc@earth.infinetconsulting.com>
To: freebsd-bugs@freebsd.org, freebsd-hackers@freebsd.org
Subject: moused and X11R6
Message-ID: <Pine.BSF.3.91.970207130200.17429A-100000@earth.infinetconsulting.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Anybody tried running moused on 2.2-BETA?
Works beautifully in console mode, 
But when I run X, there seems to be a conflict with X's mouse events.
One reason may be that I have moused doing 2 button microsoft mode 
and X doing 3 button mode. The mouse cursor at X works fine until I press
button 3. Then the mouse no longer responds. The rest of X still works.
A possible fix would be to hack moused to notice an X session and stop 
capturing mouse events then.

Cheers.
Len.


From owner-freebsd-hackers  Fri Feb  7 13:17:30 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA20283
          for hackers-outgoing; Fri, 7 Feb 1997 13:17:30 -0800 (PST)
Received: from root.com (implode.root.com [198.145.90.17])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA20278
          for <hackers@freebsd.org>; Fri, 7 Feb 1997 13:17:27 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id NAA22225; Fri, 7 Feb 1997 13:17:11 -0800 (PST)
Message-Id: <199702072117.NAA22225@root.com>
X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol
To: Brian McGovern <bmcgover@cisco.com>
cc: support@cyclades.com, waz@cyclades.com, hackers@freebsd.org
Subject: Re: Flow control on Cyclades boards??? 
In-reply-to: Your message of "Sat, 08 Feb 1997 01:06:57 EST."
             <199702080606.BAA00343@bmcgover-pc.cisco.com> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Fri, 07 Feb 1997 13:17:11 -0800
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>Ok. I now have the boards up and running between machines, but I'm having a 
>problem with silo overflows almost constantly on all the currently running 
>ports. I'm using pppd (options listed below) to set up a number of ppp
>sessions between two pentium pro 200s. 
>
>I originally tried to run 32 of them at 115200. It failed miserably. I then
>dropped back to 16 at 115200. Then to 16 at 57600. Still got silo
>errors constantly.

   If you don't have the card configured for >1MB memory mapping, you'll want
to set it to that. I found in my testing here that accessing it is *much*
slower when it is mapped in low memory. Use the cytest.exe program from
Cyclades to change it.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project

From owner-freebsd-hackers  Fri Feb  7 13:50:52 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA22028
          for hackers-outgoing; Fri, 7 Feb 1997 13:50:52 -0800 (PST)
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA22018;
          Fri, 7 Feb 1997 13:50:50 -0800 (PST)
Date: Fri, 7 Feb 1997 13:50:50 -0800 (PST)
Message-Id: <199702072150.NAA22018@freefall.freebsd.org>
To: freebsd-hackers
From: Majordomo@FreeBSD.ORG
Subject: Welcome to freebsd-security
Reply-To: Majordomo@FreeBSD.ORG
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

--

Welcome to the freebsd-security mailing list!

If you ever want to remove yourself from this mailing list,
you can send mail to "Majordomo@FreeBSD.ORG" with the following command
in the body of your email message:

    unsubscribe freebsd-security freebsd-hackers

Here's the general information for the list you've
subscribed to, in case you don't already have it:

FREEBSD-SECURITY                Security issues
FreeBSD computer security issues (DES, Kerberos, known security holes and
fixes, etc).

From owner-freebsd-hackers  Fri Feb  7 14:11:16 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA23122
          for hackers-outgoing; Fri, 7 Feb 1997 14:11:16 -0800 (PST)
Received: from vdp01.vailsystems.com (root@vdp01.vailsystems.com [207.152.98.18])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA23105;
          Fri, 7 Feb 1997 14:11:08 -0800 (PST)
Received: from crocodile.vale.com (crocodile [204.117.217.147]) by vdp01.vailsystems.com (8.8.3/8.7.3) with ESMTP id QAA20190; Fri, 7 Feb 1997 16:10:59 -0600 (CST)
Received: from slave1 (slave1.vale.com [204.117.217.100]) by crocodile.vale.com (8.8.3/8.7.3) with ESMTP id QAA03372; Fri, 7 Feb 1997 16:10:58 -0600 (CST)
Message-ID: <32FBA862.5C74@vailsys.com>
Date: Fri, 07 Feb 1997 16:10:42 -0600
From: Dan Riley <driley@vailsys.com>
Reply-To: driley@vailsys.com
X-Sender: Dan Riley <driley@vailsys.com> (Unverified)
X-Mailer: Mozilla 4.0b1 (WinNT; I)
MIME-Version: 1.0
To: Leonard Chua <lenc@earth.infinetconsulting.com>
CC: freebsd-bugs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG
Subject: Re: moused and X11R6
X-Priority: Normal
References: <Pine.BSF.3.91.970207130200.17429A-100000@earth.infinetconsulting.com>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Leonard Chua wrote:
> 
> Anybody tried running moused on 2.2-BETA?
> Works beautifully in console mode,
> But when I run X, there seems to be a conflict with X's mouse events.
> One reason may be that I have moused doing 2 button microsoft mode
> and X doing 3 button mode. The mouse cursor at X works fine until I press
> button 3. Then the mouse no longer responds. The rest of X still works.
> A possible fix would be to hack moused to notice an X session and stop
> capturing mouse events then.
> 
> Cheers.
> Len.

The Xserver on my 2.2-Gamma system will not even start up with moused running, 
although I have no complaints about moused in console mode, it is a very nice 
feature from the linux-world. :)

From owner-freebsd-hackers  Fri Feb  7 14:13:48 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA23319
          for hackers-outgoing; Fri, 7 Feb 1997 14:13:48 -0800 (PST)
Received: (from jmb@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA23312;
          Fri, 7 Feb 1997 14:13:38 -0800 (PST)
From: "Jonathan M. Bresler" <jmb>
Message-Id: <199702072213.OAA23312@freefall.freebsd.org>
Subject: Re: My resignation as president of the FreeBSD Project.
To: imp@village.org (Warner Losh)
Date: Fri, 7 Feb 1997 14:13:36 -0800 (PST)
Cc: hoek@freenet.hamilton.on.ca, lenc@earth.infinetconsulting.com,
        jkh@time.cdrom.com, freebsd-hackers@freebsd.org
In-Reply-To: <E0vsuTa-0000cH-00@rover.village.org> from "Warner Losh" at Feb 7, 97 10:52:42 am
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Warner Losh wrote:
> 
> In message <Pine.GSO.3.95.970206181426.8426A-100000@james.freenet.hamilton.on.ca> Tim Vanderhoek writes:
> : "member Jordan"  Or was that "Citizen Jordan", or should it be
> 
> Yes.  "Citizen Jordan," much like "Citizen Kane".  Years from now,
> when his BSD empire has crumbled into dust, he'll pass quietly holding
> a novelty deamon toy from some Usenix muttering the word "freefall."
> 
> Warner
> 
> P.S. Bouns points for anybody that can tell me where Orson Wells got
> "rosebud" from. :-)
> 
	"rosebud" is tooled into the sled that he used as a child.
	you can see the sled beinug thrown into an incinerator at
	teh end of the movie.  appears to be leather (?) streatched
	across a wooden frame wiht wooden runners.
jmb

From owner-freebsd-hackers  Fri Feb  7 14:32:17 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA27740
          for hackers-outgoing; Fri, 7 Feb 1997 14:32:17 -0800 (PST)
Received: from sumatra.americantv.com (sumatra.americantv.com [199.184.181.250])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA27735
          for <hackers@freebsd.org>; Fri, 7 Feb 1997 14:32:13 -0800 (PST)
Received: from right.PCS (right.pcs. [148.105.10.31]) by sumatra.americantv.com (8.7.6/8.7.3) with ESMTP id QAA10246 for <hackers@freebsd.org>; Fri, 7 Feb 1997 16:50:16 -0600 (CST)
Received: (jlemon@localhost) by right.PCS (8.6.13/8.6.4) id WAA03789; Fri, 7 Feb 1997 22:31:44 GMT
Message-ID: <Mutt.19970207163144.jlemon@right.PCS>
Date: Fri, 7 Feb 1997 16:31:44 -0600
From: jlemon@americantv.com (Jonathan Lemon)
To: hackers@freebsd.org
Subject: Re: Welcome to freebsd-security
References: <199702072150.NAA22018@freefall.freebsd.org>
X-Mailer: Mutt 0.56e
Mime-Version: 1.0
In-Reply-To: <199702072150.NAA22018@freefall.freebsd.org>; from Majordomo@FreeBSD.ORG on Feb 7, 1997 13:50:50 -0800
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Uh, why was -hackers just subscribed to -security?
> 
> Welcome to the freebsd-security mailing list!
> 
> If you ever want to remove yourself from this mailing list,
> you can send mail to "Majordomo@FreeBSD.ORG" with the following command
> in the body of your email message:
> 
--
Jonathan

From owner-freebsd-hackers  Fri Feb  7 14:33:11 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA27821
          for hackers-outgoing; Fri, 7 Feb 1997 14:33:11 -0800 (PST)
Received: from eva.cs.uni-magdeburg.de (eva.cs.uni-magdeburg.de [141.44.21.5])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA27806
          for <hackers@freebsd.org>; Fri, 7 Feb 1997 14:33:01 -0800 (PST)
Received: from pflaume.cs.uni-magdeburg.de (pflaume.cs.uni-magdeburg.de [141.44.21.44]) by eva.cs.uni-magdeburg.de (8.8.2/8.8.2) with SMTP id XAA00791 for <hackers@freebsd.org>; Fri, 7 Feb 1997 23:32:57 +0100 (MET)
Received: by pflaume.cs.uni-magdeburg.de (SMI-8.6/SMI-SVR4)
	id XAA14153; Fri, 7 Feb 1997 23:32:56 +0100
Date: Fri, 7 Feb 1997 23:32:56 +0100
From: jesse@eva.cs.Uni-Magdeburg.DE (Roland Jesse)
Message-Id: <199702072232.XAA14153@pflaume.cs.uni-magdeburg.de>
To: hackers@freebsd.org
Subject: MFS image is invalid
Reply-To: Roland Jesse <jesse@eva.cs.Uni-Magdeburg.DE>
X-Organization: University of Magdeburg
X-Pgp-Fingerprint: 5D 08 5A E3 B4 AA 68 C1  FF 67 06 29 62 DD 9A D7
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


I have upgraded my system to 2.2-GAMMA (from Feb. 5). A new build
kernel panics with a "MFS image is invalid" message.

Is it a bug, a feature ;) or did I missed to compile something new in?
'options MFS' is part of my kernel config file. MFS_ROOT is set to 10.

Any help would be appreciated,
-- 
+-------------
| Roland Jesse <jesse@cs.uni-magdeburg.de>
|  http://www.cs.uni-magdeburg.de/~jesse/  |
                                      -----+

From owner-freebsd-hackers  Fri Feb  7 17:13:24 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA15372
          for hackers-outgoing; Fri, 7 Feb 1997 17:13:24 -0800 (PST)
Received: from wasteland.calbbs.com (wasteland.calbbs.com [207.71.213.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id RAA15365
          for <freebsd-hackers@freefall.freebsd.org>; Fri, 7 Feb 1997 17:13:20 -0800 (PST)
Received: (from brian@localhost) by wasteland.calbbs.com (8.6.12/8.6.12) id RAA09757; Fri, 7 Feb 1997 17:28:05 -0800
Date: Fri, 7 Feb 1997 17:28:03 -0800 (PST)
From: Brian Buchanan <brian@wasteland.calbbs.com>
To: freebsd-hackers@freefall.freebsd.org
Subject: Re: Welcome to freebsd-security
In-Reply-To: <Mutt.19970207163144.jlemon@right.PCS>
Message-ID: <Pine.BSF.3.91.970207171726.9740A-100000@wasteland.calbbs.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk



On Fri, 7 Feb 1997, Jonathan Lemon wrote:

> 
> Uh, why was -hackers just subscribed to -security?
> > 
> > Welcome to the freebsd-security mailing list!
> > 

Looks to me like someone unfamiliar with majordomo tried to subscribe to 
multiple lists with one subscribe command, i.e.,
`subscribe freebsd-security freebsd-hackers', which majordomo would have 
interpreted as "subscribe the email address `freebsd-hackers' to list 
`freebsd-security'."

Brian




From owner-freebsd-hackers  Fri Feb  7 17:30:48 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA15998
          for hackers-outgoing; Fri, 7 Feb 1997 17:30:48 -0800 (PST)
Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA15990
          for <hackers@freebsd.org>; Fri, 7 Feb 1997 17:30:38 -0800 (PST)
Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.6.12) with SMTP id RAA01096 for <hackers@freebsd.org>; Fri, 7 Feb 1997 17:30:30 -0800 (PST)
Date: Fri, 7 Feb 1997 17:30:30 -0800 (PST)
From: Doug White <dwhite@gdi.uoregon.edu>
X-Sender: dwhite@localhost
Reply-To: Doug White <dwhite@resnet.uoregon.edu>
To: hackers@freebsd.org
Subject: ASUS MB panics
Message-ID: <Pine.BSI.3.94.970207095809.229F-100000@localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hello!

I've been having a heck of a time getting an ASUS P/I P55T2P4 motherboard
working with my custom 2.2 kernels.  I think it's related to the serial
hardware somehow, but I need someone to decode this panic and confirm.
I've included the boot info to help locate where it is.  This is captured
from a serial console (-h) output.  The message appears just as the system
would pop up the gettys:

configuring syscons: keyrate.
.
Local package startup: Modula-3 sshd.
starting local daemons:xdm  pcnfsd msqld bb.
Thu Feb  6 18:42:02 PST 1997

Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0x0
fault code              = supervisor read, page not present
instruction pointer     = 0x8:0x0
stack pointer           = 0x10:0xefbffe2c
frame pointer           = 0x10:0xefbffe84
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         = 5 (sh)
interrupt mask          = net tty
panic: page fault

syncing disks... 22 21 19 10 6 done

I can also get this panic (with the _same_ detail) if I exit X (I have a 
serial mouse) or when Kermit quits.  I think it's having trouble closing
the serial port.  

Disabling either port doesn't help.  I can't try disabling both, then I
can't run the apps that force the panic.

Specs on this machine:

ASUS P/I-P55T2P4 motherboard w/ P133 CPU, 32mb RAM
FreeBSD:  2.2-anything
Video: ATI Mach64 GX
SCSI:  NCR 53c815 
Network:  3com 3c900
Audio:  GUS PnP
IDE/Serial/Parallel port board (parallel enabled only)

The machine is otherwise perfectly stable.  

One odd note:  If I run the 2.2-970206-GENERIC kernel, it works fine.  X
complains there's no shared memory or MIT-SHM extensions, but it works.

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major



From owner-freebsd-hackers  Fri Feb  7 17:33:26 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA16132
          for hackers-outgoing; Fri, 7 Feb 1997 17:33:26 -0800 (PST)
Received: from murkwood.gaffaneys.com (dialup17.gaffaneys.com [134.129.252.36])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA16111;
          Fri, 7 Feb 1997 17:33:20 -0800 (PST)
Received: (from zach@localhost)
	by murkwood.gaffaneys.com (8.8.5/8.8.5) id TAA06666;
	Fri, 7 Feb 1997 19:33:36 -0600 (CST)
To: Leonard Chua <lenc@earth.infinetconsulting.com>
Cc: freebsd-bugs@freebsd.org, freebsd-hackers@freebsd.org
Subject: Re: moused and X11R6
References: <Pine.BSF.3.91.970207130200.17429A-100000@earth.infinetconsulting.com>
Mime-Version: 1.0 (generated by tm-edit 7.89)
Content-Type: text/plain; charset=US-ASCII
From: Zach Heilig <zach@blizzard.gaffaneys.com>
Date: 07 Feb 1997 19:33:33 -0600
In-Reply-To: Leonard Chua's message of Fri, 7 Feb 1997 13:09:43 -0800 (PST)
Message-ID: <876804rsia.fsf@murkwood.gaffaneys.com>
Lines: 27
X-Mailer: Gnus v5.3/Emacs 19.34
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Leonard Chua <lenc@earth.infinetconsulting.com> writes:

> Anybody tried running moused on 2.2-BETA?
> Works beautifully in console mode, 
> But when I run X, there seems to be a conflict with X's mouse events.
> One reason may be that I have moused doing 2 button microsoft mode 
> and X doing 3 button mode. The mouse cursor at X works fine until I press
> button 3. Then the mouse no longer responds. The rest of X still works.
> A possible fix would be to hack moused to notice an X session and stop 
> capturing mouse events then.

I just started running X on my 2.2-ALPHA system (saw too many problems
with the beta version :-).  I noticed about half the time I hit the
right button it pastes a 'd' into whatever application is active.  And
when I hit the middle button, it pastes the 'd' and perhaps that
buffer after the 'd' (depending one where the mouse is).  This is
especially annoying when dealing with scroll-bars and other
applications that take the 'd' key to mean something.

I'm not entirely sure what's wrong, but maybe someone else has
noticed.  The system is running moused, XF86_SVGA, and fvwm (and a
whole boatload of xterms and other applications).

-- 
Zach Heilig (zach@blizzard.gaffaneys.com) | ALL unsolicited commercial email
Support bacteria -- it's the only         | is unwelcome.  I avoid dealing
form of culture some people have!         | with companies that email ads.

From owner-freebsd-hackers  Fri Feb  7 17:34:03 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA16263
          for hackers-outgoing; Fri, 7 Feb 1997 17:34:03 -0800 (PST)
Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA16233
          for <hackers@freebsd.org>; Fri, 7 Feb 1997 17:33:56 -0800 (PST)
Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id MAA14698; Sat, 8 Feb 1997 12:03:11 +1030 (CST)
From: Michael Smith <msmith@atrad.adelaide.edu.au>
Message-Id: <199702080133.MAA14698@genesis.atrad.adelaide.edu.au>
Subject: Re: PD PDF viewer? was: barracuda jumpers
In-Reply-To: <Mutt.19970207103215.jlemon@right.PCS> from Jonathan Lemon at "Feb 7, 97 10:32:15 am"
To: jlemon@americantv.com (Jonathan Lemon)
Date: Sat, 8 Feb 1997 12:03:10 +1030 (CST)
Cc: kelly@fsl.noaa.gov, roberto@keltia.freenix.fr, hackers@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Jonathan Lemon stands accused of saying:
> > > The acroread linux binary works pretty well too. See
> > > /usr/ports/print/acroread.
> > 
> > As does Ghostscript 3.53 on PDF files.
> 
> Except, AFAIK, neither Ghostscript nor xpdf will deal with 'encoded' PDF
> files (like the Intel chip manuals).

Ghostscript with the RC4 patch works fine on "encrypted" PDF files.
Unfortunately, it looks like there's a new revision of the PDF format
that people like National Instruments are using (rev 1.2) that neither
xpdf nor Ghostscript 4 can handle.

> Jonathan

-- 
]] Mike Smith, Software Engineer        msmith@gsoft.com.au             [[
]] Genesis Software                     genesis@gsoft.com.au            [[
]] High-speed data acquisition and      (GSM mobile)     0411-222-496   [[
]] realtime instrument control.         (ph)          +61-8-8267-3493   [[
]] Unix hardware collector.             "Where are your PEZ?" The Tick  [[

From owner-freebsd-hackers  Fri Feb  7 17:36:02 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA16505
          for hackers-outgoing; Fri, 7 Feb 1997 17:36:02 -0800 (PST)
Received: from nasu.utsunomiya-u.ac.jp (nasu.utsunomiya-u.ac.jp [160.12.128.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA16476;
          Fri, 7 Feb 1997 17:35:50 -0800 (PST)
Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by nasu.utsunomiya-u.ac.jp (8.8.4+2.7Wbeta4/3.5Wpl3) with ESMTP id KAA11189; Sat, 8 Feb 1997 10:34:40 +0900 (JST)
Received: from zodiac.mech.utsunomiya-u.ac.jp (bf0TKetwxdsN4n3bNA6e7L0F+ouvgbzB@zodiac.mech.utsunomiya-u.ac.jp [160.12.33.1]) by outmail.utsunomiya-u.ac.jp (8.8.4+2.7Wbeta4/3.5Wpl3) with ESMTP id KAA24207; Sat, 8 Feb 1997 10:34:39 +0900 (JST)
Received: from zodiac.mech.utsunomiya-u.ac.jp (zenith.mech.utsunomiya-u.ac.jp [160.12.33.60]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP
	id KAA08565; Sat, 8 Feb 1997 10:38:29 +0900 (JST)
Message-Id: <199702080138.KAA08565@zodiac.mech.utsunomiya-u.ac.jp>
To: driley@vailsys.com
cc: Leonard Chua <lenc@earth.infinetconsulting.com>, freebsd-bugs@freebsd.org,
        freebsd-hackers@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp
Subject: Re: moused and X11R6 
In-reply-to: Your message of "Fri, 07 Feb 1997 16:10:42 CST."
             <32FBA862.5C74@vailsys.com> 
References: <Pine.BSF.3.91.970207130200.17429A-100000@earth.infinetconsulting.com>
	  <32FBA862.5C74@vailsys.com> 
Date: Sat, 08 Feb 1997 10:38:27 +0900
From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


>Leonard Chua wrote:
>> 
>> Anybody tried running moused on 2.2-BETA?
>> Works beautifully in console mode,
>> But when I run X, there seems to be a conflict with X's mouse events.
>> One reason may be that I have moused doing 2 button microsoft mode
>> and X doing 3 button mode. The mouse cursor at X works fine until I press
>> button 3. Then the mouse no longer responds. The rest of X still works.
>> A possible fix would be to hack moused to notice an X session and stop
>> capturing mouse events then.
>> 
>> Cheers.
>> Len.
>
>The Xserver on my 2.2-Gamma system will not even start up with moused running,
> 
>although I have no complaints about moused in console mode, it is a very nice 
>feature from the linux-world. :)

Slight modification was made to moused, between 2.2-BETA and 2.2-GAMMA.
It affects PS/2 and Bus mice only.

Although I am not the one who is maintaining moused, I am interested
in your problems.

Would you give us some more details?

Which type of mouse are you using, Serial, bus, or PS/2?
>From which manufacturer?
How the variables `mousedtype' and `mousedport' are set in `/etc/sysconfig'?
How do your `Device' and `Protocol' lines for the pointing device look 
like in `XF86Config'?

Kazu

From owner-freebsd-hackers  Fri Feb  7 18:20:41 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id SAA18448
          for hackers-outgoing; Fri, 7 Feb 1997 18:20:41 -0800 (PST)
Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA18442
          for <hackers@FreeBSD.ORG>; Fri, 7 Feb 1997 18:20:35 -0800 (PST)
Received: (from root@localhost) by dyson.iquest.net (8.8.4/8.6.9) id VAA14428; Fri, 7 Feb 1997 21:20:12 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199702080220.VAA14428@dyson.iquest.net>
Subject: Re: fcntl, F_SETFL, O_NONBLOCK & /dev/null
To: craig@progroup.com (Craig Shaver)
Date: Fri, 7 Feb 1997 21:20:11 -0500 (EST)
Cc: hackers@FreeBSD.ORG
In-Reply-To: <32FA5655.3F54BC7E@progroup.com> from "Craig Shaver" at Feb 6, 97 02:08:21 pm
X-Mailer: ELM [version 2.4 PL24 ME8]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 
> Is there any work being done for implementing kernel threads?  I would 
> think this would be very important for a robust, real-world usable,
> thread package.
> 
That is one of my interests.  Doug Santry is also interested.  Certainly
don't want to 'claim' the project until I start.  I have some ideas,
and in conjunction with some of Doug's work, I think that we could
have a really good thread's capability.  I have a VM experiment to
do first (relocatable kernel stack, totally shared VM space.)  If
that works, we'll have a start on a really good mechanism.

John

From owner-freebsd-hackers  Fri Feb  7 19:56:30 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA21679
          for hackers-outgoing; Fri, 7 Feb 1997 19:56:30 -0800 (PST)
Received: from cicerone.uunet.ca (root@cicerone.uunet.ca [142.77.1.11])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA21674
          for <freebsd-hackers@freebsd.org>; Fri, 7 Feb 1997 19:56:27 -0800 (PST)
Received: from why.whine.com ([205.150.249.1]) by mail.uunet.ca with ESMTP id <115551-23301>; Fri, 7 Feb 1997 22:56:10 -0500
Received: from why (why [205.150.249.1]) by why.whine.com (8.8.5/8.7.3) with SMTP id WAA01523; Fri, 7 Feb 1997 22:55:35 -0500 (EST)
Date: Fri, 7 Feb 1997 22:55:34 -0500
From: Andrew Herdman <andrew@why.whine.com>
X-Sender: andrew@why
To: "Alex G. Bulushev" <bag@sinbin.demos.su>
cc: alexis@ww.net, freebsd-hackers@freebsd.org
Subject: Re: ipip for FreeBSD
In-Reply-To: <199702071240.PAA07786@sinbin.demos.su>
Message-ID: <Pine.BSF.3.95.970207225341.1517A-100000@why>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Fri, 7 Feb 1997, Alex G. Bulushev wrote:

> > 
> > Greetings,
> > 
> > 	Does anyone knows of location of an ipip daemon or other
> > ip tunnerling software for FreeBSD? Please let me know.
> > 							alexis
> > -- 
> > 		It's all the same, only the names will change
> > 
> 
> ftp://ftp.ru/pub/hamradio/packet/tcpip/linux/ipip.tar.gz
> 				       ^^^^^ this is not correct ...
> this is port from bsd to linux with original ...
> it works fine, i test it under fbsd 2.1.0 & 2.1.5 between two PC
> and between PC and cisco ...
> 
>    Alex.
> 

I grabbed this package and have found the documentation sparse.  I am
trying to build a tunnel between my freebsd box and a cisco router.  I've
spent a lot of time building ipip tunnels between cisco routers, but for
the life of me cannot figure out what to do with the ipip program to get
one working.  I have the tun drivers installed in my kernel.

Any suggestions would be appreciated.

Thanks
  Andrew



From owner-freebsd-hackers  Fri Feb  7 20:06:58 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA22129
          for hackers-outgoing; Fri, 7 Feb 1997 20:06:58 -0800 (PST)
Received: from pdx1.world.net (pdx1.world.net [192.243.32.18])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA22117
          for <hackers@freebsd.org>; Fri, 7 Feb 1997 20:06:52 -0800 (PST)
From: proff@suburbia.net
Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id UAA14939 for <hackers@freebsd.org>; Fri, 7 Feb 1997 20:08:19 -0800 (PST)
Received: (qmail 4057 invoked by uid 110); 8 Feb 1997 04:06:34 -0000
Message-ID: <19970208040634.4056.qmail@suburbia.net>
Subject: Re: Flow control on Cyclades boards???
In-Reply-To: <199702080606.BAA00343@bmcgover-pc.cisco.com> from Brian McGovern at "Feb 8, 97 01:06:57 am"
To: bmcgover@cisco.com (Brian McGovern)
Date: Sat, 8 Feb 1997 15:06:34 +1100 (EST)
Cc: hackers@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Ok. I now have the boards up and running between machines, but I'm having a 
> problem with silo overflows almost constantly on all the currently running 
> ports. I'm using pppd (options listed below) to set up a number of ppp
> sessions between two pentium pro 200s. 
> 
> I originally tried to run 32 of them at 115200. It failed miserably. I then
> dropped back to 16 at 115200. Then to 16 at 57600. Still got silo
> errors constantly.

try removing all your other cards. I had the same problem, and found that
a faulty wd8* card was the culprit.


--
Prof. Julian Assange  |If you want to build a ship, don't drum up people
		      |together to collect wood and don't assign them tasks
proff@iq.org          |and work, but rather teach them to long for the endless
proff@gnu.ai.mit.edu  |immensity of the sea. -- Antoine de Saint Exupery

From owner-freebsd-hackers  Fri Feb  7 20:33:33 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA23165
          for hackers-outgoing; Fri, 7 Feb 1997 20:33:33 -0800 (PST)
Received: from icicle.winternet.com (adm@icicle.winternet.com [198.174.169.5])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA23146;
          Fri, 7 Feb 1997 20:33:25 -0800 (PST)
Received: (from adm@localhost) by icicle.winternet.com (8.7.5/8.7.5) id WAA15834; Fri, 7 Feb 1997 22:33:18 -0600 (CST)
Posted-Date: Fri, 7 Feb 1997 22:33:18 -0600 (CST)
Received: from chaos.ecpnet.com(204.246.64.13) by icicle.winternet.com via smap (V2.0beta)
	id xma015817; Fri, 7 Feb 97 22:32:55 -0600
Received: from localhost (raistlin@localhost) by chaos.ecpnet.com (8.8.5/8.8.3) with SMTP id WAA02156; Fri, 7 Feb 1997 22:31:42 -0600 (CST)
Date: Fri, 7 Feb 1997 22:31:41 -0600 (CST)
From: Justen Stepka <raistlin@ecpnet.com>
To: Zach Heilig <zach@blizzard.gaffaneys.com>
cc: Leonard Chua <lenc@earth.infinetconsulting.com>, freebsd-bugs@freebsd.org,
        freebsd-hackers@freebsd.org
Subject: Re: moused and X11R6
In-Reply-To: <876804rsia.fsf@murkwood.gaffaneys.com>
Message-ID: <Pine.BSF.3.95.970207222919.2151A-100000@chaos.ecpnet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk



On 7 Feb 1997, Zach Heilig wrote:

> Leonard Chua <lenc@earth.infinetconsulting.com> writes:
> 
> > Anybody tried running moused on 2.2-BETA?
> > Works beautifully in console mode, 
> > But when I run X, there seems to be a conflict with X's mouse events.
> > One reason may be that I have moused doing 2 button microsoft mode 
> > and X doing 3 button mode. The mouse cursor at X works fine until I press
> > button 3. Then the mouse no longer responds. The rest of X still works.
> > A possible fix would be to hack moused to notice an X session and stop 
> > capturing mouse events then.
> 
> I just started running X on my 2.2-ALPHA system (saw too many problems
> with the beta version :-).  I noticed about half the time I hit the
> right button it pastes a 'd' into whatever application is active.  And
> when I hit the middle button, it pastes the 'd' and perhaps that
> buffer after the 'd' (depending one where the mouse is).  This is
> especially annoying when dealing with scroll-bars and other
> applications that take the 'd' key to mean something.
> 
> I'm not entirely sure what's wrong, but maybe someone else has
> noticed.  The system is running moused, XF86_SVGA, and fvwm (and a
> whole boatload of xterms and other applications).
> 
> -- 
> Zach Heilig (zach@blizzard.gaffaneys.com) | ALL unsolicited commercial email
> Support bacteria -- it's the only         | is unwelcome.  I avoid dealing
> form of culture some people have!         | with companies that email ads.
> 

I to have noticed a problem similar, I have no problem loading X though.
The problem is when I go to move the mouse it appears as though it's
"drunk" and drags along slowly and in weird patterns. I figured that code
had been changed so I just turned moused off.

Justen Stepka


From owner-freebsd-hackers  Fri Feb  7 20:53:22 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA23794
          for hackers-outgoing; Fri, 7 Feb 1997 20:53:22 -0800 (PST)
Received: from nirvana.genesyslab.com (nirvana.genesyslab.com [204.94.142.4])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA23789
          for <freebsd-hackers@freebsd.org>; Fri, 7 Feb 1997 20:53:07 -0800 (PST)
Received: from zen.genesyslab.com (Zen.genesyslab.com [204.94.142.145]) by nirvana.genesyslab.com (8.7.6/8.7.6) with ESMTP id UAA05705; Fri, 7 Feb 1997 20:54:48 -0800 (PST)
Received: (from dk@localhost) by zen.genesyslab.com (8.8.4/8.7.3) id UAA09228; Fri, 7 Feb 1997 20:53:00 -0800 (PST)
Date: Fri, 7 Feb 1997 20:53:00 -0800 (PST)
From: Dmitry Kohmanyuk <dk@genesyslab.com>
Message-Id: <199702080453.UAA09228@zen.genesyslab.com>
To: freebsd-hackers@freebsd.org
Subject: 2.2 panic in i586_bc1 call from nfs_writerpc()
Cc: dk@farm.org
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


hi,

I got a weird panic today, and I beleive I know why it happened ;-)

(kgdb) bt
#0  boot (howto=256) at ../../kern/kern_shutdown.c:243
#1  0xf0112262 in panic (
    fmt=0xf01b8257 "vm_fault: fault on nofault entry, addr: %lx")
    at ../../kern/kern_shutdown.c:367
#2  0xf01b837e in vm_fault (map=0xf1f77e80, vaddr=4105216000,
    fault_type=1 '\001', change_wiring=0) at ../../vm/vm_fault.c:201
#3  0xf01cd0a4 in trap_pfault (frame=0xefbffc80, usermode=0)
    at ../../i386/i386/trap.c:642
#4  0xf01ccdcf in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -235292624,
      tf_esi = -189751296, tf_ebp = -272630520, tf_isp = -272630616,
      tf_ebx = -235363712, tf_edx = -2147155909, tf_ecx = 2000,
      tf_eax = -45541328, tf_trapno = 12, tf_err = 0, tf_eip = -266552628,
      tf_cs = 8, tf_eflags = 66050, tf_esp = 2000, tf_ss = -189751296})
    at ../../i386/i386/trap.c:311
#5  0xf01cbacc in i586_bc1 ()
#6  0xf01876a8 in nfs_writerpc (vp=0xf24f6680, uiop=0xefbffdf8,
    cred=0xf2753380, iomode=0xefbffdec, must_commit=0xefbffde4)
    at ../../nfs/nfs_vnops.c:1164
#7  0xf01614a8 in nfs_doio (bp=0xf434ecc4, cr=0xf2753380, p=0x0)
    at ../../nfs/nfs_bio.c:973
#8  0xf0180543 in nfssvc_iod (p=0xf23ab600) at ../../nfs/nfs_syscalls.c:781
#9  0xf017f2be in nfssvc (p=0xf23ab600, uap=0xefbfff94, retval=0xefbfff84)
    at ../../nfs/nfs_syscalls.c:202
---Type <return> to continue, or q <return> to quit---
#10 0xf01cd89f in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = -272638320,
      tf_esi = 0, tf_ebp = -272638368, tf_isp = -272629788, tf_ebx = 3,
      tf_edx = 1, tf_ecx = 1, tf_eax = 155, tf_trapno = 12, tf_err = 7,
      tf_eip = 8597, tf_cs = 31, tf_eflags = 582, tf_esp = -272638392,
      tf_ss = 39}) at ../../i386/i386/trap.c:892
#11 0x2195 in ?? ()
Cannot access memory at address 0xefbfde64.

the system was writing over NFS at the moment, and the file size has
hit 2G:

-rw-r--r--   1 backup  wheel  2147516416 Feb  7 17:04 filename

(the reason file is that big is backup included /proc, by mistake, and
Solaris's tar was happily reading all the processes' cores)

the mtime stamp of this file is exactly the time of a crash, so I beleive
that nagative 32-bit offset was the reason for a panic.

there are 2 calls to bcopy() in nfs_vnops.c:nfs_writerpc(), but the logic 
is that only one of them can be executed at one invocation.

(btw, gdb cannot disassemble functions in support.s ;-(  but it's easy
to see that it's within i586_bc1 anyway (next label is i586_global_bcopy,
and that address is higher than fault's).

I have recompiled my world pretty recently (I cvsupped cvs tree, checked
out RELENG_2_2 and compiled from that).  Just for reference, it's
 *      $Id: support.s,v 1.41.2.6 1997/01/25 03:23:09 dyson Exp $
and
 * $Id: nfs_vnops.c,v 1.36.2.2 1997/01/07 06:18:27 wpaul Exp $



From owner-freebsd-hackers  Fri Feb  7 21:44:50 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA25622
          for hackers-outgoing; Fri, 7 Feb 1997 21:44:50 -0800 (PST)
Received: from haywire.DIALix.COM (news@haywire.DIALix.COM [192.203.228.65])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA25598
          for <freebsd-hackers@freebsd.org>; Fri, 7 Feb 1997 21:44:42 -0800 (PST)
Received: (from news@localhost) by haywire.DIALix.COM (8.8.4/8.8.2) id NAA04188 for freebsd-hackers@freebsd.org; Sat, 8 Feb 1997 13:44:32 +0800 (WST)
X-Authentication-Warning: haywire.DIALix.COM: news set sender to usenet-request@haywire.dialix.com using -f
Received: from GATEWAY by haywire.DIALix.COM with netnews
	for freebsd-hackers@freebsd.org (problems to: usenet@haywire.dialix.com)
To: freebsd-hackers@freebsd.org
Date: Sat, 8 Feb 1997 04:25:16 GMT
From: mark@putte.seeware.DIALix.oz.au (Mark Hannon)
Message-ID: <E59oA5.4x4.L.doorway@seeware.DIALix.oz.au>
Organization: Private FreeBSD site
Subject: 2.2-GAMMA improves CDE from Xinside
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi all,

Just a short note to say that I installed the 2.2-GAMMA release
on the machine that I am running CDE from Xinside on.

I got an immediate improvement in the stability of the product.
I've been having a whole number of problems with applications
starting from the front panel and crashing on startup, the
help tool crashing when trying to read the index etc...

After installing 2.2-GAMMA these faults dissapeared!!

Now the most annoying bugs have dissapeared CDE is quite usable.

Regards/Mark

-- 
+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+
| Mark Hannon,| FreeBSD, Free Unix for your PC | mark@seeware.DIALix.oz.au|
| Melbourne,  | PGP key available by fingering | epamha@epa.ericsson.se   |
| Australia   | seeware@melbourne.DIALix.oz.au |                          |
+-=-=-=-=-=-=-+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+

From owner-freebsd-hackers  Fri Feb  7 21:56:48 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA25964
          for hackers-outgoing; Fri, 7 Feb 1997 21:56:48 -0800 (PST)
Received: from labs.usn.blaze.net.au (labs.usn.blaze.net.au [203.17.53.30])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA25938;
          Fri, 7 Feb 1997 21:56:37 -0800 (PST)
Received: (from davidn@localhost)
	by labs.usn.blaze.net.au (8.8.5/8.8.5) id QAA03871;
	Sat, 8 Feb 1997 16:55:56 +1100 (EST)
Message-ID: <19970208165555.12961@usn.blaze.net.au>
Date: Sat, 8 Feb 1997 16:55:55 +1100
From: David Nugent <davidn@labs.usn.blaze.net.au>
To: Justen Stepka <raistlin@ecpnet.com>
Cc: Zach Heilig <zach@blizzard.gaffaneys.com>,
        Leonard Chua <lenc@earth.infinetconsulting.com>,
        freebsd-bugs@freebsd.org, freebsd-hackers@freebsd.org
Subject: Re: moused and X11R6
References: <876804rsia.fsf@murkwood.gaffaneys.com> <Pine.BSF.3.95.970207222919.2151A-100000@chaos.ecpnet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.61
In-Reply-To: <Pine.BSF.3.95.970207222919.2151A-100000@chaos.ecpnet.com>; from Justen Stepka on Feb 02, 1997 at 10:31:41PM
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Feb 02, 1997 at 10:31:41PM, Justen Stepka wrote:
> > I'm not entirely sure what's wrong, but maybe someone else has
> > noticed.  The system is running moused, XF86_SVGA, and fvwm (and a
> > whole boatload of xterms and other applications).
> 
> I to have noticed a problem similar, I have no problem loading X though.
> The problem is when I go to move the mouse it appears as though it's
> "drunk" and drags along slowly and in weird patterns. I figured that code
> had been changed so I just turned moused off.

It would appear that you've configured both X and moused to
access the mouse directly, in which case they're fighting for
control, and certainly you'll see the results that you've
observed. Had X been configured to use /dev/mouse, then the
mouse in X would not have worked at all unless you changed
your X configuration as well.

It works like this:

moused handles the *real* mouse device, and "converts" these
into mousesystems events, then emulates a "real" mouse to
everything that uses it. In the meatime, It can affect the
console device as well if you have mouse actions on via
vidcontrol.

e.g (for a serial mouse):

/dev/cuaa0 -> moused
	      |
	      /dev/mouse
		|
		+-- vidcontrol
		|
		+-- xfree


Regards,

David Nugent - Unique Computing Pty Ltd - Melbourne, Australia
Voice +61-3-9791-9547  Data/BBS +61-3-9792-3507  3:632/348@fidonet
davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/

From owner-freebsd-hackers  Fri Feb  7 22:04:25 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id WAA26275
          for hackers-outgoing; Fri, 7 Feb 1997 22:04:25 -0800 (PST)
Received: from starfire.mn.org (root@starfire.skypoint.net [199.86.32.187])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA26270
          for <hackers@freebsd.org>; Fri, 7 Feb 1997 22:04:20 -0800 (PST)
Received: (from john@localhost)
	by starfire.mn.org (8.8.5/1.1)  id AAA01921; Sat, 8 Feb 1997 00:04:17 -0600 (CST)
Message-ID: <Mutt.19970208000417.john@dexter.starfire.mn.org>
Date: Sat, 8 Feb 1997 00:04:17 -0600
From: john@dexter.starfire.mn.org (John Lind)
To: hackers@freebsd.org
Subject: DES for 2.1.6?
X-Mailer: Mutt 0.53
Mime-Version: 1.0
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I have loaded up a system with a full 2.1.6 and applied the patches
from SA-97:01 and done a make world.  Now I would like to put in
the DES stuff (necessary because I have to share a password database
with Solaris and Unixware), but the 2.1.6 directory is locked (with
good reason, and I understand that).  Can I use the DES source from
2.1.5 that I have tucked away on another machine?  Unfortunately,
I do not have the sources, just the binaries.

I am sure that this whole situation must be very frustrating for
all of you.  I know how you have labored to make FreeBSD a trusted
platform for commercial and other serious development, and to find
something like this, left over from CSRG probably, and no fault of
your own, must be maddening.

		 John Lind, Starfire Consulting Services
E-mail: john@starfire.MN.ORG	    USnail: PO Box 17247, Mpls MN  55417

From owner-freebsd-hackers  Fri Feb  7 22:52:45 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id WAA27429
          for hackers-outgoing; Fri, 7 Feb 1997 22:52:45 -0800 (PST)
Received: from seabass.progroup.com (catfish.progroup.com [206.24.122.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA27424
          for <hackers@FreeBSD.ORG>; Fri, 7 Feb 1997 22:52:41 -0800 (PST)
Received: from seabass.progroup.com (seabass.progroup.com [206.24.122.1]) by seabass.progroup.com (8.7.5/8.7.3) with SMTP id WAA22508; Fri, 7 Feb 1997 22:51:30 -0800 (PST)
Message-ID: <32FC2272.41C67EA6@progroup.com>
Date: Fri, 07 Feb 1997 22:51:30 -0800
From: Craig Shaver <craig@progroup.com>
Organization: Productivity Group, Inc.
X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.1.5-RELEASE i386)
MIME-Version: 1.0
To: "John S. Dyson" <toor@dyson.iquest.net>
CC: hackers@FreeBSD.ORG
Subject: Re: fcntl, F_SETFL, O_NONBLOCK & /dev/null
References: <199702080220.VAA14428@dyson.iquest.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

John S. Dyson wrote:
> 
> >
> > Is there any work being done for implementing kernel threads?  I would
> > think this would be very important for a robust, real-world usable,
> > thread package.
> >
> That is one of my interests.  Doug Santry is also interested.  Certainly
> don't want to 'claim' the project until I start.  I have some ideas,
> and in conjunction with some of Doug's work, I think that we could
> have a really good thread's capability.  I have a VM experiment to
> do first (relocatable kernel stack, totally shared VM space.)  If
> that works, we'll have a start on a really good mechanism.
> 
> John

Do you have a time frame for when this may start?  I could volunteer some
time beginning in March, to develop some test programs, demos, and bench-
marks.  Would this be helpful?  Please let me know.

Thanks for the feedback ...

-- 
Craig Shaver  (craig@progroup.com) (415)390-0654 
Productivity Group POB 60458 Sunnyvale, CA  94088

From owner-freebsd-hackers  Fri Feb  7 23:50:52 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA28981
          for hackers-outgoing; Fri, 7 Feb 1997 23:50:52 -0800 (PST)
Received: from murkwood.gaffaneys.com (dialup14.gaffaneys.com [134.129.252.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA28962;
          Fri, 7 Feb 1997 23:50:45 -0800 (PST)
Received: (from zach@localhost)
	by murkwood.gaffaneys.com (8.8.5/8.8.5) id BAA10244;
	Sat, 8 Feb 1997 01:51:02 -0600 (CST)
To: David Nugent <davidn@labs.usn.blaze.net.au>
Cc: Leonard Chua <lenc@earth.infinetconsulting.com>, freebsd-bugs@freebsd.org,
        freebsd-hackers@freebsd.org
Subject: Re: moused and X11R6
References: <876804rsia.fsf@murkwood.gaffaneys.com>
	<Pine.BSF.3.95.970207222919.2151A-100000@chaos.ecpnet.com>
	<19970208165555.12961@usn.blaze.net.au>
Mime-Version: 1.0 (generated by tm-edit 7.89)
Content-Type: text/plain; charset=US-ASCII
From: Zach Heilig <zach@blizzard.gaffaneys.com>
Date: 08 Feb 1997 01:51:01 -0600
In-Reply-To: David Nugent's message of Sat, 8 Feb 1997 16:55:55 +1100
Message-ID: <87bu9venx6.fsf@murkwood.gaffaneys.com>
Lines: 21
X-Mailer: Gnus v5.3/Emacs 19.34
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

David Nugent <davidn@labs.usn.blaze.net.au> writes:

> It would appear that you've configured both X and moused to
> access the mouse directly, in which case they're fighting for
> control, and certainly you'll see the results that you've
> observed.

Nope, moused used /dev/cuaa0, X used /dev/sysmouse.  What are the
device numbers on /dev/sysmouse supposed to be?  I have:

crw-rw----  1 uucp  dialer   28, 128 Feb  8 01:35 /dev/cuaa0
crw-------  1 root  wheel    12, 128 Feb  8 00:58 /dev/sysmouse

I killed moused, and set the X mouse pointer to /dev/cuaa0.  The
problem seems to have gone away.  Either the above permissions are
wrong, or moused is mildly broken.

-- 
Zach Heilig (zach@blizzard.gaffaneys.com) | ALL unsolicited commercial email
Support bacteria -- it's the only         | is unwelcome.  I avoid dealing
form of culture some people have!         | with companies that email ads.

From owner-freebsd-hackers  Fri Feb  7 23:58:05 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA29137
          for hackers-outgoing; Fri, 7 Feb 1997 23:58:05 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA29132
          for <freebsd-hackers@freebsd.org>; Fri, 7 Feb 1997 23:58:00 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id SAA04049; Sat, 8 Feb 1997 18:53:21 +1100
Date: Sat, 8 Feb 1997 18:53:21 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199702080753.SAA04049@godzilla.zeta.org.au>
To: dk@genesyslab.com, freebsd-hackers@freebsd.org
Subject: Re: 2.2 panic in i586_bc1 call from nfs_writerpc()
Cc: dk@farm.org
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>there are 2 calls to bcopy() in nfs_vnops.c:nfs_writerpc(), but the logic 
>is that only one of them can be executed at one invocation.

Logic is that neither can have got to i586_bc1, since they only copy 8
bytes and i586_bc1 is only used for >= 1024 bytes :-).

>(btw, gdb cannot disassemble functions in support.s ;-(  but it's easy
                  ^^^^^^^^^^^ backtrace
>to see that it's within i586_bc1 anyway (next label is i586_global_bcopy,
>and that address is higher than fault's).

The frame pointer isn't set up for the functions in support.s, so the
backtrace probably skips one function: nfs_writerpc() called something
that called bcopy().

Do you use nfsv3?  v2 obviously won't work properly with files
larger than 2GB or 4GB.  E.g., for v2, nfs_writerpc() uses
txdr_unsigned(uiop->uio_offset) and throws away the high 32 bits of
the offset :-(.

Bruce

From owner-freebsd-hackers  Sat Feb  8 01:39:15 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id BAA02524
          for hackers-outgoing; Sat, 8 Feb 1997 01:39:15 -0800 (PST)
Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA02495
          for <hackers@freebsd.org>; Sat, 8 Feb 1997 01:39:08 -0800 (PST)
Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33])
          by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP
	  id KAA03161 for <hackers@freebsd.org>; Sat, 8 Feb 1997 10:38:58 +0100
Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id KAA03934 for hackers@freebsd.org; Sat, 8 Feb 1997 10:38:29 +0100
Received: (from roberto@localhost) by keltia.freenix.fr (8.8.5/keltia-uucp-2.9) id KAA19844;
          Sat, 8 Feb 1997 10:29:01 +0100 (CET)
Message-ID: <19970208102900.GM22115@keltia.freenix.fr>
Date: Sat, 8 Feb 1997 10:29:00 +0100
From: roberto@keltia.freenix.fr (Ollivier Robert)
To: hackers@freebsd.org
Subject: Re: MFS image is invalid
References: <199702072232.XAA14153@pflaume.cs.uni-magdeburg.de>
X-Mailer: Mutt 0.60,1-3,9
Mime-Version: 1.0
X-Operating-System: FreeBSD 3.0-CURRENT ctm#2999
In-Reply-To: <199702072232.XAA14153@pflaume.cs.uni-magdeburg.de>; from Roland Jesse on Feb 7, 1997 23:32:56 +0100
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

According to Roland Jesse:
> Is it a bug, a feature ;) or did I missed to compile something new in?
> 'options MFS' is part of my kernel config file. MFS_ROOT is set to 10.

Never use MFS_ROOT unless you're building a release. You just told your
kernel that the root filesystem was in memory instead of on your disk..
-- 
Ollivier ROBERT    -=- The daemon is FREE! -=-    roberto@keltia.freenix.fr
  FreeBSD keltia.freenix.fr 3.0-CURRENT #39: Sun Feb  2 22:12:44 CET 1997

From owner-freebsd-hackers  Sat Feb  8 02:20:31 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA04472
          for hackers-outgoing; Sat, 8 Feb 1997 02:20:31 -0800 (PST)
Received: from sax.sax.de (sax.sax.de [193.175.26.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id CAA04466
          for <freebsd-hackers@FreeBSD.ORG>; Sat, 8 Feb 1997 02:20:26 -0800 (PST)
Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id LAA23093; Sat, 8 Feb 1997 11:20:21 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id LAA25406; Sat, 8 Feb 1997 11:13:07 +0100 (MET)
Message-ID: <Mutt.19970208111307.j@uriah.heep.sax.de>
Date: Sat, 8 Feb 1997 11:13:07 +0100
From: j@uriah.heep.sax.de (J Wunsch)
To: gabor@acm.org (Gabor Kincses)
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: Panic in probe, but no dump
References: <32FA29A1.41C67EA6@acm.org> <Mutt.19970207005345.j@uriah.heep.sax.de> <32FB72E0.2781E494@acm.org>
X-Mailer: Mutt 0.55-PL10
Mime-Version: 1.0
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <32FB72E0.2781E494@acm.org>; from Gabor Kincses on Feb 7, 1997 12:22:24 -0600
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

As Gabor Kincses wrote:

> > Well, the normal sequence is to use `dumpon'.  This is also supported
> > by /etc/sysconfig.
> 
> AFAIK that is not an option here, since we are not executing /etc/rc,
> yet.

Right.  In this case, you need the `dumps on' clause.

Hey, btw., you can only dump into a configured and/or active swap
partition.  So, you also need a `swap on' clause!

j@uriah 693% fgrep kernel /sys/i386/conf/URIAH 
config          kernel  root on sd0 swap on sd0 and sd1 dumps on sd1

> I did.  Before I started all this.  It seems that once I can single step
> or have a dump it will print the addresses.  In xdb I can 'td' (toggle
> disassembly) and voila I see the machine instructions with line numbers
> next to the ones that start a line.  I'm looking for a similar feature.

Seems you gotta contribute this to gdb yet.  It shouldn't be too hard,
since gdb can already handle all of the details (see the ``info line''
and ``disas'' commands).  You ``only'' need to combine them.

> That is good info, I didn't see anything like that.  The panic message
> printed the current EIP, then "waiting 15 seconds to reboot" or
> something like that.

That means it didn't find the dumpdev.

> 20.3. call diediedie().  I'll try that.  ddb looks fairly similar to adb
> on HP-UX.  Probably share roots, too.

Maybe.  HP-UX is said to be much BSD inside.

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

From owner-freebsd-hackers  Sat Feb  8 03:21:15 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id DAA06464
          for hackers-outgoing; Sat, 8 Feb 1997 03:21:15 -0800 (PST)
Received: from sax.sax.de (sax.sax.de [193.175.26.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id DAA06459
          for <freebsd-hackers@FreeBSD.ORG>; Sat, 8 Feb 1997 03:21:12 -0800 (PST)
Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id MAA24546 for freebsd-hackers@FreeBSD.ORG; Sat, 8 Feb 1997 12:21:10 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id MAA25683; Sat, 8 Feb 1997 12:05:11 +0100 (MET)
Message-ID: <Mutt.19970208120510.j@uriah.heep.sax.de>
Date: Sat, 8 Feb 1997 12:05:10 +0100
From: j@uriah.heep.sax.de (J Wunsch)
To: freebsd-hackers@FreeBSD.ORG
Subject: Re: What happened to the splash screen?
References: <Mutt.19970207010238.j@uriah.heep.sax.de> <199702071017.FAA02234@hda.hda.com>
X-Mailer: Mutt 0.55-PL10
Mime-Version: 1.0
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <199702071017.FAA02234@hda.hda.com>; from Peter Dufault on Feb 7, 1997 05:17:21 -0500
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

As Peter Dufault wrote:

> > I would even be tempted to do a stab at serial console installation,
> > but i still need a good idea how to `switch screens' there.

> I have two concept 108s here (man 5 termcap).  They have 8 pages
> of screen memory.  It may be a bit expensive to send one off to you,
> though.

This, and it doesn't solve the problem for users of a more mainstream
terminal like a VTxxx one.

I think what we need in this case is something like a library that
opens up to 4 ptys, and allows to hot-key switch between them.  I
don't know `screen', but i think it's doing something like this.  I'm
not sure whether it's possible to combine it with sysinstall though.

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

From owner-freebsd-hackers  Sat Feb  8 03:50:44 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id DAA07301
          for hackers-outgoing; Sat, 8 Feb 1997 03:50:44 -0800 (PST)
Received: from sax.sax.de (sax.sax.de [193.175.26.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id DAA07285
          for <freebsd-hackers@freebsd.org>; Sat, 8 Feb 1997 03:50:40 -0800 (PST)
Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id MAA24858; Sat, 8 Feb 1997 12:50:39 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id MAA25775; Sat, 8 Feb 1997 12:29:45 +0100 (MET)
Message-ID: <Mutt.19970208122945.j@uriah.heep.sax.de>
Date: Sat, 8 Feb 1997 12:29:45 +0100
From: j@uriah.heep.sax.de (J Wunsch)
To: freebsd-hackers@freebsd.org (FreeBSD hackers)
Cc: gabor@acm.org
Subject: Re: Panic in probe, but no dump
References: <199702071935.GAA14065@godzilla.zeta.org.au>
X-Mailer: Mutt 0.55-PL10
Mime-Version: 1.0
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <199702071935.GAA14065@godzilla.zeta.org.au>; from Bruce Evans on Feb 8, 1997 06:35:14 +1100
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

As Bruce Evans wrote:

> Who needs dumps?  Just use remote gdb or (local) ddb on the running
> kernel.  kerneldebug.sgml is a bit out of date - it doesn't mention
> remote gdb.

Julian promised to submit some documentation for it. ;)

> Use the builtin panic command.  diediedie() doesn't exist.
> kerneldebug.sgml is more than a bit out of date :-).

I'll fix this.

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

From owner-freebsd-hackers  Sat Feb  8 03:51:44 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id DAA07397
          for hackers-outgoing; Sat, 8 Feb 1997 03:51:44 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA07379
          for <freebsd-hackers@FreeBSD.ORG>; Sat, 8 Feb 1997 03:51:38 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id WAA09891; Sat, 8 Feb 1997 22:46:09 +1100
Date: Sat, 8 Feb 1997 22:46:09 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199702081146.WAA09891@godzilla.zeta.org.au>
To: gabor@acm.org, j@uriah.heep.sax.de
Subject: Re: Panic in probe, but no dump
Cc: freebsd-hackers@FreeBSD.ORG
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>Right.  In this case, you need the `dumps on' clause.
>
>Hey, btw., you can only dump into a configured and/or active swap
>partition.

Not true.  You can dump on any large enough disk device (at least for
sd and wd disks).  A swap device is just normally used because its
contents are disposable.

So, you also need a `swap on' clause!
>
>j@uriah 693% fgrep kernel /sys/i386/conf/URIAH 
>config          kernel  root on sd0 swap on sd0 and sd1 dumps on sd1

Erm, `swap' is a no-op here.  Swap devices haven't been put in
swapkernel.c for a year ortwo .  The only remaining functionality of
`swap' in the config line is to enable `swapgeneric', and the only
remaining functionality of `swapgeneric' is to enable kernel support
for the -a (ask for root device) boot flag.

Bruce

From owner-freebsd-hackers  Sat Feb  8 04:14:54 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id EAA08402
          for hackers-outgoing; Sat, 8 Feb 1997 04:14:54 -0800 (PST)
Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA08397
          for <hackers@freebsd.org>; Sat, 8 Feb 1997 04:14:46 -0800 (PST)
Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33])
          by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP
	  id NAA03398 for <hackers@freebsd.org>; Sat, 8 Feb 1997 13:14:35 +0100
Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id NAA08462 for hackers@freebsd.org; Sat, 8 Feb 1997 13:14:19 +0100
Received: (from roberto@localhost) by keltia.freenix.fr (8.8.5/keltia-uucp-2.9) id KAA19993;
          Sat, 8 Feb 1997 10:49:17 +0100 (CET)
Message-ID: <19970208104917.FP56746@keltia.freenix.fr>
Date: Sat, 8 Feb 1997 10:49:17 +0100
From: roberto@keltia.freenix.fr (Ollivier Robert)
To: hackers@freebsd.org
Subject: Re: DES for 2.1.6?
References: <Mutt.19970208000417.john@dexter.starfire.mn.org>
X-Mailer: Mutt 0.60,1-3,9
Mime-Version: 1.0
X-Operating-System: FreeBSD 3.0-CURRENT ctm#2999
In-Reply-To: <Mutt.19970208000417.john@dexter.starfire.mn.org>; from John Lind on Feb 8, 1997 00:04:17 -0600
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

According to John Lind:
> good reason, and I understand that).  Can I use the DES source from
> 2.1.5 that I have tucked away on another machine?  Unfortunately,
> I do not have the sources, just the binaries.

I don't think there have been signifiant changes in the DES code between
2.1.5 and 2.1.6. Check the CVS logs on the Web for details.
-- 
Ollivier ROBERT    -=- The daemon is FREE! -=-    roberto@keltia.freenix.fr
  FreeBSD keltia.freenix.fr 3.0-CURRENT #39: Sun Feb  2 22:12:44 CET 1997

From owner-freebsd-hackers  Sat Feb  8 04:22:21 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id EAA08961
          for hackers-outgoing; Sat, 8 Feb 1997 04:22:21 -0800 (PST)
Received: from sax.sax.de (sax.sax.de [193.175.26.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id EAA08953
          for <hackers@FreeBSD.ORG>; Sat, 8 Feb 1997 04:22:12 -0800 (PST)
Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id NAA25264; Sat, 8 Feb 1997 13:22:01 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id MAA25879; Sat, 8 Feb 1997 12:57:52 +0100 (MET)
Message-ID: <Mutt.19970208125752.j@uriah.heep.sax.de>
Date: Sat, 8 Feb 1997 12:57:52 +0100
From: j@uriah.heep.sax.de (J Wunsch)
To: dwhite@resnet.uoregon.edu (Doug White)
Cc: hackers@FreeBSD.ORG
Subject: Re: ASUS MB panics
References: <Pine.BSI.3.94.970207095809.229F-100000@localhost>
X-Mailer: Mutt 0.55-PL10
Mime-Version: 1.0
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <Pine.BSI.3.94.970207095809.229F-100000@localhost>; from Doug White on Feb 7, 1997 17:30:30 -0800
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

As Doug White wrote:

> I've been having a heck of a time getting an ASUS P/I P55T2P4 motherboard
> working with my custom 2.2 kernels.

Just for the record, this board works fine for me.

> Fatal trap 12: page fault while in kernel mode
> fault virtual address   = 0x0
> fault code              = supervisor read, page not present
> instruction pointer     = 0x8:0x0
> stack pointer           = 0x10:0xefbffe2c
> frame pointer           = 0x10:0xefbffe84
> 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         = 5 (sh)
> interrupt mask          = net tty
> panic: page fault

Umm.  It executes a null pointer.  This is hard to track offline.  Can
you configure DDB, and try to look at the stack to learn where it
happens?

(You could also configure remote gdb, but don't ask me for a
documentation of this.)

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

From owner-freebsd-hackers  Sat Feb  8 04:22:44 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id EAA09002
          for hackers-outgoing; Sat, 8 Feb 1997 04:22:44 -0800 (PST)
Received: from sax.sax.de (sax.sax.de [193.175.26.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id EAA08997
          for <hackers@freebsd.org>; Sat, 8 Feb 1997 04:22:40 -0800 (PST)
Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id NAA25273; Sat, 8 Feb 1997 13:22:34 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id NAA25944; Sat, 8 Feb 1997 13:16:18 +0100 (MET)
Message-ID: <Mutt.19970208131618.j@uriah.heep.sax.de>
Date: Sat, 8 Feb 1997 13:16:18 +0100
From: j@uriah.heep.sax.de (J Wunsch)
To: john@dexter.starfire.mn.org (John Lind)
Cc: hackers@freebsd.org
Subject: Re: DES for 2.1.6?
References: <Mutt.19970208000417.john@dexter.starfire.mn.org>
X-Mailer: Mutt 0.55-PL10
Mime-Version: 1.0
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <Mutt.19970208000417.john@dexter.starfire.mn.org>; from John Lind on Feb 8, 1997 00:04:17 -0600
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

As John Lind wrote:

> good reason, and I understand that).  Can I use the DES source from
> 2.1.5 that I have tucked away on another machine?  Unfortunately,
> I do not have the sources, just the binaries.

j@uriah 715% cvs diff -u -kk -rRELENG_2_1_{5,6_1}_RELEASE /usr/src/secure/lib/libcrypt
cvs diff: Diffing /usr/src/secure/lib/libcrypt
cvs diff: Diffing /usr/src/secure/lib/libcrypt/test
j@uriah 716% 

So it looks both versions are identical as far as libcrypt is
concerned.

> I am sure that this whole situation must be very frustrating for
> all of you.  I know how you have labored to make FreeBSD a trusted
> platform for commercial and other serious development, and to find
> something like this, left over from CSRG probably, and no fault of
> your own, must be maddening.

The missing bounds check was CSRG inheritance.  The not yet killed
ENABLE_STARTUP_LOCALE was homegrown.  It was particularly annoying for
two reasons: it affects all binaries, and it served no real purpose at
all.  (It was considered a bad hack later.)

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

From owner-freebsd-hackers  Sat Feb  8 04:51:08 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id EAA11496
          for hackers-outgoing; Sat, 8 Feb 1997 04:51:08 -0800 (PST)
Received: from sax.sax.de (sax.sax.de [193.175.26.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id EAA11466
          for <freebsd-hackers@FreeBSD.ORG>; Sat, 8 Feb 1997 04:51:04 -0800 (PST)
Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id NAA25788 for freebsd-hackers@FreeBSD.ORG; Sat, 8 Feb 1997 13:51:02 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id NAA26015; Sat, 8 Feb 1997 13:24:16 +0100 (MET)
Message-ID: <Mutt.19970208132416.j@uriah.heep.sax.de>
Date: Sat, 8 Feb 1997 13:24:16 +0100
From: j@uriah.heep.sax.de (J Wunsch)
To: freebsd-hackers@FreeBSD.ORG
Subject: Re: Panic in probe, but no dump
References: <199702081146.WAA09891@godzilla.zeta.org.au>
X-Mailer: Mutt 0.55-PL10
Mime-Version: 1.0
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <199702081146.WAA09891@godzilla.zeta.org.au>; from Bruce Evans on Feb 8, 1997 22:46:09 +1100
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

As Bruce Evans wrote:

> Not true.  You can dump on any large enough disk device (at least for
> sd and wd disks).  A swap device is just normally used because its
> contents are disposable.

Ah, i stand corrected.

Btw., i found when code-reviewing that part that it only wants to dump
into partition `b' of some device.  Everything else is silently
discarded:

static void
dumpsys(void)
{

	if (!dodump)
		return;
	if (dumpdev == NODEV)
		return;
	if ((minor(dumpdev)&07) != 1)
	                        ^^^^
		return;

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

From owner-freebsd-hackers  Sat Feb  8 06:15:42 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id GAA13959
          for hackers-outgoing; Sat, 8 Feb 1997 06:15:42 -0800 (PST)
Received: from weenix.guru.org (kmitch@weenix.guru.org [198.82.200.65])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA13954
          for <hackers@freebsd.org>; Sat, 8 Feb 1997 06:15:36 -0800 (PST)
Received: (from kmitch@localhost)
	by weenix.guru.org (8.8.5/8.8.5) id JAA01180
	for hackers@freebsd.org; Sat, 8 Feb 1997 09:15:34 -0500 (EST)
From: Keith Mitchell <kmitch@weenix.guru.org>
Message-Id: <199702081415.JAA01180@weenix.guru.org>
Subject: User Classes in passwd
To: hackers@freebsd.org
Date: Sat, 8 Feb 1997 09:15:34 -0500 (EST)
X-Mailer: ELM [version 2.4ME+ PL30 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I don't know if this was an oversight or not, but it looks like user classes
are implemented everywhere else so I thought I would mention it.

passwd currently doesn't look in the class database to reset a user's
password expiration time when they change their password.  In fact,
in local_password.c there is a comment saying that user classes will
change the default behavior of just setting the expire time to 0.


From owner-freebsd-hackers  Sat Feb  8 06:52:24 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id GAA15050
          for hackers-outgoing; Sat, 8 Feb 1997 06:52:24 -0800 (PST)
Received: from nic.follonett.no (nic.follonett.no [194.198.43.10])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA15028;
          Sat, 8 Feb 1997 06:52:17 -0800 (PST)
Received: (from uucp@localhost) by nic.follonett.no (8.8.5/8.8.3) with UUCP id PAA01479; Sat, 8 Feb 1997 15:50:52 +0100 (MET)
Received: from oo7 (oo7.dimaga.com [192.0.0.65]) by dimaga.com (8.7.5/8.7.2) with SMTP id PAA07161; Sat, 8 Feb 1997 15:54:21 +0100 (MET)
Message-Id: <3.0.32.19970208155420.00aaf720@dimaga.com>
X-Sender: eivind@dimaga.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Sat, 08 Feb 1997 15:54:22 +0100
To: hackers@freebsd.org, current@freebsd.org
From: Eivind Eklund <eivind@dimaga.com>
Subject: Proposed change to dump/restore
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

The suid capability of dump is only used for remote backups.

dump have been known for security holes in the past, and is not a user
level program.  I propose a change of default mode and owner for this
program to
-r-sr-x--- root:operator /sbin/dump
which will disallow anybody not in the operator group from making backups
using dump (which is not too bad a thing, as only members of wheel can
access the harddisks directly, which is needed to be able to use dump
anyway), and only leave dump vulnerable to attacks from an operator :)

Does anybody object to the change?  If not, it'll go into 2.1.7 and -current.



Eivind Eklund  perhaps@yes.no  http://maybe.yes.no/perhaps/
eivind@freebsd.org


From owner-freebsd-hackers  Sat Feb  8 06:56:38 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id GAA15229
          for hackers-outgoing; Sat, 8 Feb 1997 06:56:38 -0800 (PST)
Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA15196
          for <hackers@FreeBSD.ORG>; Sat, 8 Feb 1997 06:56:30 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
          by hydrogen.nike.efn.org (8.8.4/8.8.4) with SMTP
	  id GAA08543; Sat, 8 Feb 1997 06:56:14 -0800 (PST)
Date: Sat, 8 Feb 1997 06:56:13 -0800 (PST)
From: John-Mark Gurney <jmg@nike.efn.org>
Reply-To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
To: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de>
cc: Doug White <dwhite@resnet.uoregon.edu>, hackers@FreeBSD.ORG
Subject: Re: ASUS MB panics
In-Reply-To: <Mutt.19970208125752.j@uriah.heep.sax.de>
Message-ID: <Pine.NEB.3.95.970208064708.362N-100000@hydrogen.nike.efn.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Sat, 8 Feb 1997, J Wunsch wrote:

> > Fatal trap 12: page fault while in kernel mode
> > fault virtual address   = 0x0
> > fault code              = supervisor read, page not present
> > instruction pointer     = 0x8:0x0
> > stack pointer           = 0x10:0xefbffe2c
> > frame pointer           = 0x10:0xefbffe84
> > 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         = 5 (sh)
> > interrupt mask          = net tty
> > panic: page fault
> 
> Umm.  It executes a null pointer.  This is hard to track offline.  Can
> you configure DDB, and try to look at the stack to learn where it
> happens?
> 
> (You could also configure remote gdb, but don't ask me for a
> documentation of this.)

well.. I'm a good friend of his... and last night he was showing me the
message (and I acidentally sent it)... but later that night I worked on
the machine... and had my first experience with kernel debugging...  :) 

basicly it seems that the call to ttyclose at the end of spec_close
manages to overrun the stack... so upon return of spec_close it tries to
"return" to the previous function.. but that return value was overwriten
and so it jumps to the null pointer...

I still have some core's from the system on the hard drive... if you would
like some more info, I can provide it...  ttyl... 

John-Mark

gurney_j@efn.org
http://resnet.uoregon.edu/~gurney_j/
Modem/FAX: (541) 683-6954   (FreeBSD Box)

Live in Peace, destroy Micro$oft, support free software, run FreeBSD (unix)


From owner-freebsd-hackers  Sat Feb  8 07:03:24 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id HAA15510
          for hackers-outgoing; Sat, 8 Feb 1997 07:03:24 -0800 (PST)
Received: from spooky.rwwa.com (rwwa.com [198.115.177.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA15503
          for <freebsd-hackers@freebsd.org>; Sat, 8 Feb 1997 07:03:17 -0800 (PST)
Received: from spooky.rwwa.com (localhost.rwwa.com [127.0.0.1]) by spooky.rwwa.com (8.7.5/8.7.3) with ESMTP id KAA29141 for <freebsd-hackers@freebsd.org>; Sat, 8 Feb 1997 10:02:48 -0500 (EST)
Message-Id: <199702081502.KAA29141@spooky.rwwa.com>
X-Mailer: exmh version 1.6.9 8/22/96
To: freebsd-hackers@freebsd.org
Subject: In what way are shared libs ``shared''?
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 08 Feb 1997 10:02:48 -0500
From: Robert Withrow <witr@rwwa.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Looking at rtld.c I see:

  addr = mmap(0, hdr.a_text + hdr.a_data + hdr.a_bss,
              PROT_READ|PROT_EXEC, MAP_COPY, fd, 0)

>From my understanding of MAP_COPY semantics, this is *not*
a shared mapping.  If I am right about this, then how
are shared libs shared?

-----------------------------------------------------------------------------
Robert Withrow, Tel: +1 617 592 8935, Net: witr@rwwa.COM



From owner-freebsd-hackers  Sat Feb  8 07:49:56 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id HAA17491
          for hackers-outgoing; Sat, 8 Feb 1997 07:49:56 -0800 (PST)
Received: from sax.sax.de (sax.sax.de [193.175.26.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id HAA17480
          for <freebsd-hackers@freebsd.org>; Sat, 8 Feb 1997 07:49:53 -0800 (PST)
Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id QAA29653; Sat, 8 Feb 1997 16:49:51 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id QAA28166; Sat, 8 Feb 1997 16:47:55 +0100 (MET)
Message-ID: <Mutt.19970208164755.j@uriah.heep.sax.de>
Date: Sat, 8 Feb 1997 16:47:55 +0100
From: j@uriah.heep.sax.de (J Wunsch)
To: freebsd-hackers@freebsd.org (FreeBSD hackers)
Cc: dwhite@resnet.uoregon.edu (Doug White)
Subject: Re: ASUS MB panics
References: <Mutt.19970208125752.j@uriah.heep.sax.de> <Pine.NEB.3.95.970208064708.362N-100000@hydrogen.nike.efn.org>
X-Mailer: Mutt 0.55-PL10
Mime-Version: 1.0
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <Pine.NEB.3.95.970208064708.362N-100000@hydrogen.nike.efn.org>; from John-Mark Gurney on Feb 8, 1997 06:56:13 -0800
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

As John-Mark Gurney wrote:

> basicly it seems that the call to ttyclose at the end of spec_close
> manages to overrun the stack... so upon return of spec_close it tries to
> "return" to the previous function.. but that return value was overwriten
> and so it jumps to the null pointer...

A quick glance over the sources yields the clist stuff there as the
most likely culprit.  Maybe Bruce has some more suggestions...

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

From owner-freebsd-hackers  Sat Feb  8 08:41:35 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id IAA19111
          for hackers-outgoing; Sat, 8 Feb 1997 08:41:35 -0800 (PST)
Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA19104
          for <freebsd-hackers@freebsd.org>; Sat, 8 Feb 1997 08:41:31 -0800 (PST)
Received: (from root@localhost) by dyson.iquest.net (8.8.4/8.6.9) id LAA03138; Sat, 8 Feb 1997 11:40:15 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199702081640.LAA03138@dyson.iquest.net>
Subject: Re: In what way are shared libs ``shared''?
To: witr@rwwa.com (Robert Withrow)
Date: Sat, 8 Feb 1997 11:40:15 -0500 (EST)
Cc: freebsd-hackers@freebsd.org
In-Reply-To: <199702081502.KAA29141@spooky.rwwa.com> from "Robert Withrow" at Feb 8, 97 10:02:48 am
X-Mailer: ELM [version 2.4 PL24 ME8]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Looking at rtld.c I see:
> 
>   addr = mmap(0, hdr.a_text + hdr.a_data + hdr.a_bss,
>               PROT_READ|PROT_EXEC, MAP_COPY, fd, 0)
> 
> >From my understanding of MAP_COPY semantics, this is *not*
> a shared mapping.  If I am right about this, then how
> are shared libs shared?
> 
The initial mapping is copy-on-write, subsequently, the
mapping is changed for .data to be writeable, and bss
is remapped to be read/write.

The reason for the initial mapping to include the bss is
so that enough space is reserved for the contiguous
allocation.

The reason that the MAP_COPY (in -current MAP_PRIVATE
is technically more appropriate), is so that when
debuggers are run, and changes are made by the debugger,
that a COW operation will occur (as opposed to modifying
the binary, if MAP_SHARED was used.)

MAP_COPY doesn't really mean much at execution time
(except for data structure set-up) in FreeBSD unless
a write operation occurs.  Until the write operation,
there is full sharing.

John


From owner-freebsd-hackers  Sat Feb  8 09:01:21 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA19925
          for hackers-outgoing; Sat, 8 Feb 1997 09:01:21 -0800 (PST)
Received: from humvee.doit.wisc.edu (humvee.doit.wisc.edu [144.92.9.20])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA19905;
          Sat, 8 Feb 1997 09:01:15 -0800 (PST)
Received: from audumla.students.wisc.edu by humvee.doit.wisc.edu;
          id LAA184646; 8.7.5/50; Sat, 8 Feb 1997 11:01:13 -0600
Received: from gabor-bsd by audumla.students.wisc.edu;
          id LAA27446; 8.6.9W/42; Sat, 8 Feb 1997 11:00:33 -0600
Message-ID: <32FCB17D.794BDF32@acm.org>
Date: Sat, 08 Feb 1997 11:01:49 -0600
From: Gabor Kincses <gabor@acm.org>
X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.1.5-RELEASE i386)
MIME-Version: 1.0
To: freebsd-hardware@FreeBSD.ORG
CC: freebsd-hackers@FreeBSD.ORG
Subject: [Fwd: Re: OSS/Free for FreeBSD]
Content-Type: multipart/mixed; boundary="------------1CFBAE3959E2B60015FB7483"
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

This is a multi-part message in MIME format.

--------------1CFBAE3959E2B60015FB7483
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

The original author of the Voxware sound drivers that are included in
the 2.1.5 source can soon be replaced by the O$$ drivers.  The free
version is to come quite a bit later.  I am not affiliated with this
company in any shape or form, just looking for sound drivers for
FreeBSD.  The linux source code can be downloaded from:
ftp://linux.wauug.org/pub/ossfree/

Happy hacking.  (Sorry for the cross-posts, yet again.)

-- 
Gabor Kincses
(gabor@acm.org)

--------------1CFBAE3959E2B60015FB7483
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Received: from mail.acm.org by audumla.students.wisc.edu;
          id AAA91942; 8.6.9W/42; Sat, 8 Feb 1997 00:43:16 -0600
Received: from bessie.eunet.fi (bessie.eunet.fi [192.26.119.11]) by mail.acm.org (8.8.4/8.7.5) with ESMTP id BAA25512 for <gabor@acm.org>; Sat, 8 Feb 1997 01:42:22 -0500
Received: from savolai.fi (root@voxware.pp.fi [193.66.8.57]) by bessie.eunet.fi (8.8.4/8.8.3) with ESMTP id IAA27359; Sat, 8 Feb 1997 08:43:09 +0200 (EET)
Received: from localhost (hannu@localhost) by savolai.fi (8.7.6/8.7.3) with SMTP id IAA01507; Sat, 8 Feb 1997 08:41:39 +0200
Date: Sat, 8 Feb 1997 08:41:39 +0200 (EET)
From: Hannu Savolainen <hannu@voxware.pp.fi>
X-Sender: hannu@batman
To: Gabor Kincses <gabor@acm.org>
cc: info@4front-tech.com
Subject: Re: OSS/Free for FreeBSD
In-Reply-To: <32FC0435.41C67EA6@acm.org>
Message-ID: <Pine.LNX.3.95.970208083730.679I-100000@batman>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 7 Feb 1997, Gabor Kincses wrote:

> I found info that the FreeBSD port is coming soon.
> What version(s) are going to be supported?   Is
> 2.1.5 in the plans?  I guess if we get the 2.2
> source we can port it back to 2.1.5 ourselves.
OSS/Free for FreeBSD will not be released before late 97 or early 98.

OSS/FreeBSD (the commercial version) will be released soon after the final
FreeBSD 2.2 is available. It will work only with 2.2 (and later). The
exact release date is not known yet.

Best regards,

Hannu
------
Hannu Savolainen (hannu@voxware.pp.fi, hannu@4front-tech.com)
http://www.4Front-Tech.com/oss.html (Open Sound System (OSS))
http://personal.eunet.fi/pp/voxware (OSS Free/TASD/VoxWare)


--------------1CFBAE3959E2B60015FB7483--


From owner-freebsd-hackers  Sat Feb  8 09:27:05 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA20988
          for hackers-outgoing; Sat, 8 Feb 1997 09:27:05 -0800 (PST)
Received: from sax.sax.de (sax.sax.de [193.175.26.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA20981
          for <hackers@freebsd.org>; Sat, 8 Feb 1997 09:26:55 -0800 (PST)
Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id SAA00898 for hackers@freebsd.org; Sat, 8 Feb 1997 18:26:48 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id RAA28393; Sat, 8 Feb 1997 17:16:21 +0100 (MET)
Message-ID: <Mutt.19970208171621.j@uriah.heep.sax.de>
Date: Sat, 8 Feb 1997 17:16:21 +0100
From: j@uriah.heep.sax.de (J Wunsch)
To: hackers@freebsd.org
Subject: Re: Proposed change to dump/restore
References: <3.0.32.19970208155420.00aaf720@dimaga.com>
X-Mailer: Mutt 0.55-PL10
Mime-Version: 1.0
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <3.0.32.19970208155420.00aaf720@dimaga.com>; from Eivind Eklund on Feb 8, 1997 15:54:22 +0100
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

As Eivind Eklund wrote:

> Does anybody object to the change?  If not, it'll go into 2.1.7 and -current.

Go for it!  You've also got the blessing to do this in RELENG_2_2.

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

From owner-freebsd-hackers  Sat Feb  8 09:28:34 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA21073
          for hackers-outgoing; Sat, 8 Feb 1997 09:28:34 -0800 (PST)
Received: from sax.sax.de (sax.sax.de [193.175.26.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA21066
          for <freebsd-hackers@freebsd.org>; Sat, 8 Feb 1997 09:28:31 -0800 (PST)
Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id SAA00903; Sat, 8 Feb 1997 18:27:04 +0100
Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id RAA28382; Sat, 8 Feb 1997 17:15:28 +0100 (MET)
Message-ID: <Mutt.19970208171527.j@uriah.heep.sax.de>
Date: Sat, 8 Feb 1997 17:15:27 +0100
From: j@uriah.heep.sax.de (J Wunsch)
To: witr@rwwa.com (Robert Withrow)
Cc: freebsd-hackers@freebsd.org
Subject: Re: In what way are shared libs ``shared''?
References: <199702081502.KAA29141@spooky.rwwa.com>
X-Mailer: Mutt 0.55-PL10
Mime-Version: 1.0
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <199702081502.KAA29141@spooky.rwwa.com>; from Robert Withrow on Feb 8, 1997 10:02:48 -0500
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

As Robert Withrow wrote:

> Looking at rtld.c I see:
> 
>   addr = mmap(0, hdr.a_text + hdr.a_data + hdr.a_bss,
>               PROT_READ|PROT_EXEC, MAP_COPY, fd, 0)
> 
> >From my understanding of MAP_COPY semantics, this is *not*
> a shared mapping.  If I am right about this, then how
> are shared libs shared?

They are shared.  MAP_COPY is an unsupported name for MAP_PRIVATE, and
the explanation for MAP_PRIVATE says that *modifications* are private
(COW).  Since the mapping is with read and execute permissions only,
the mapping program is not supposed to ever modify something.

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

From owner-freebsd-hackers  Sat Feb  8 09:32:49 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA21393
          for hackers-outgoing; Sat, 8 Feb 1997 09:32:49 -0800 (PST)
Received: from labs.usn.blaze.net.au (labs.usn.blaze.net.au [203.17.53.30])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA21377
          for <hackers@FreeBSD.org>; Sat, 8 Feb 1997 09:32:42 -0800 (PST)
Received: (from davidn@localhost)
	by labs.usn.blaze.net.au (8.8.5/8.8.5) id EAA12161;
	Sun, 9 Feb 1997 04:32:23 +1100 (EST)
Message-ID: <19970209043220.18011@usn.blaze.net.au>
Date: Sun, 9 Feb 1997 04:32:20 +1100
From: David Nugent <davidn@labs.usn.blaze.net.au>
To: Keith Mitchell <kmitch@weenix.guru.org>
Cc: hackers@FreeBSD.org
Subject: Re: User Classes in passwd
References: <199702081415.JAA01180@weenix.guru.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.61
In-Reply-To: <199702081415.JAA01180@weenix.guru.org>; from Keith Mitchell on Feb 02, 1997 at 09:15:34AM
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

On Feb 02, 1997 at 09:15:34AM, Keith Mitchell wrote:
> I don't know if this was an oversight or not, but it looks
> like user classes are implemented everywhere else so I thought
> I would mention it.

No, not "everywhere else" - yet. It isn't complete, and I'm
implementing one step at a time quite deliberately so as not
to create 'urgent' work for myself in multiple places at once
should something break.

It looks at this stage that we'll have to take a longer harder
look at the authentication interface, for example, since "BSDI
compatibility" is no longer possible - they've changed twice
now between the first implementation in BSDI 2.1 and the
(newly or shortly to be released?) 3.0, and look like changing
again for 3.1.


> passwd currently doesn't look in the class database to reset a user's
> password expiration time when they change their password.  In fact,
> in local_password.c there is a comment saying that user classes will
> change the default behavior of just setting the expire time to 0.

Yep. I'll finally modify the passwd(5) manpage when I get to
doing that. :-) It's around 3rd on the todo list, right after
ftpd, so it'll be soon. Most of the remaining items are relatively
trivial or relate to ports.


Regards,

David Nugent - Unique Computing Pty Ltd - Melbourne, Australia
Voice +61-3-9791-9547  Data/BBS +61-3-9792-3507  3:632/348@fidonet
davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/

From owner-freebsd-hackers  Sat Feb  8 11:33:27 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA25400
          for hackers-outgoing; Sat, 8 Feb 1997 11:33:27 -0800 (PST)
Received: from minor.stranger.com (stranger.vip.best.com [204.156.129.250])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA25394
          for <freebsd-hackers@freebsd.org>; Sat, 8 Feb 1997 11:33:20 -0800 (PST)
Received: from dog.farm.org (dog.farm.org [207.111.140.47]) by minor.stranger.com (8.6.12/8.6.12) with ESMTP id LAA04244; Sat, 8 Feb 1997 11:40:38 -0800
Received: (from dk@localhost) by dog.farm.org (8.7.5/dk#3) id LAA14825; Sat, 8 Feb 1997 11:37:11 -0800 (PST)
From: Dmitry Kohmanyuk <dk@dog.farm.org>
Message-Id: <199702081937.LAA14825@dog.farm.org>
Subject: Re: 2.2 panic in i586_bc1 call from nfs_writerpc()
To: bde@zeta.org.au (Bruce Evans)
Date: Sat, 8 Feb 1997 11:37:11 -0800 (PST)
Cc: dk@genesyslab.com, freebsd-hackers@freebsd.org, dk@farm.org
In-Reply-To: <199702080753.SAA04049@godzilla.zeta.org.au> from Bruce Evans at "Feb 8, 97 06:53:21 pm"
Reply-To: dk+@ua.net
X-Class: Fast
X-OS-Of-the-Day: FreeBSD 2.2-960501-SNAP
X-NIC-Handle: DK379
X-Pager-Email: dk@interpage.net
X-Spammers-Killed-to-Date: [fresh update on unsolicited inquiry]
X-Mailer: ELM [version 2.4ME+ PL13 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Quoting Bruce Evans:
> >there are 2 calls to bcopy() in nfs_vnops.c:nfs_writerpc(), but the logic 
> >is that only one of them can be executed at one invocation.
> 
> Logic is that neither can have got to i586_bc1, since they only copy 8
> bytes and i586_bc1 is only used for >= 1024 bytes :-).

yes, I see. morning light helps ;-)

from the line number in nfs_writerpc, it's evident that the call to
bcopy occured from nfsm_uiotombuf() (hidden in the macro nfs_uiotom).
this function has only one call to bcopy().  (and one to copyin()) 

> >(btw, gdb cannot disassemble functions in support.s ;-(  but it's easy
>                   ^^^^^^^^^^^ backtrace
> >to see that it's within i586_bc1 anyway (next label is i586_global_bcopy,
> >and that address is higher than fault's).

well - I type `disas i586_bc1' so I can look up instruction by address,
and gdb refuses to do so.

> The frame pointer isn't set up for the functions in support.s, so the
> backtrace probably skips one function: nfs_writerpc() called something
> that called bcopy().
> 
> Do you use nfsv3?  v2 obviously won't work properly with files
> larger than 2GB or 4GB.  E.g., for v2, nfs_writerpc() uses
> txdr_unsigned(uiop->uio_offset) and throws away the high 32 bits of
> the offset :-(.

yes, the mount was v3 (and probably even TCP).  The NFS server is
NetApp F330, running Data ONTAP 4.0.1c (that's a dedicated NFS server,
essentially a Pentium PC with additional SCSI disk shelves, rackmounted.
The entire OS fits into 1 floppy disk and has a command-line interface
with similarities to Unix command set.  It does up to 1Mb/s for both NFS
writes and reads - I wish FreeBSD can do that.)


From owner-freebsd-hackers  Sat Feb  8 11:41:33 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA25740
          for hackers-outgoing; Sat, 8 Feb 1997 11:41:33 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA25735
          for <freebsd-hackers@FreeBSD.ORG>; Sat, 8 Feb 1997 11:41:30 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id GAA23616; Sun, 9 Feb 1997 06:38:35 +1100
Date: Sun, 9 Feb 1997 06:38:35 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199702081938.GAA23616@godzilla.zeta.org.au>
To: freebsd-hackers@FreeBSD.ORG, j@uriah.heep.sax.de
Subject: Re: Panic in probe, but no dump
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>Btw., i found when code-reviewing that part that it only wants to dump
>into partition `b' of some device.  Everything else is silently
>discarded:
>
>static void
>dumpsys(void)
>{
>
>	if (!dodump)
>		return;
>	if (dumpdev == NODEV)
>		return;
>	if ((minor(dumpdev)&07) != 1)
>	                        ^^^^
>		return;
>

Ugh.  The only excuse for doing that is that the dumpdev that was
carefully checked by setdumpdev() may be stale (if it is on removable
media).  Another reason for using a swap device is that swap devices
can't be stale - they are held open, and if they are removed, then you
have worse problems :-].

Bruce

From owner-freebsd-hackers  Sat Feb  8 12:13:15 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA26839
          for hackers-outgoing; Sat, 8 Feb 1997 12:13:15 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA26832
          for <freebsd-hackers@freebsd.org>; Sat, 8 Feb 1997 12:13:11 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id HAA24173; Sun, 9 Feb 1997 07:02:19 +1100
Date: Sun, 9 Feb 1997 07:02:19 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199702082002.HAA24173@godzilla.zeta.org.au>
To: bde@zeta.org.au, dk+@ua.net
Subject: Re: 2.2 panic in i586_bc1 call from nfs_writerpc()
Cc: dk@farm.org, dk@genesyslab.com, freebsd-hackers@freebsd.org
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>> >(btw, gdb cannot disassemble functions in support.s ;-(  but it's easy
>>                   ^^^^^^^^^^^ backtrace
>> >to see that it's within i586_bc1 anyway (next label is i586_global_bcopy,
>> >and that address is higher than fault's).
>
>well - I type `disas i586_bc1' so I can look up instruction by address,
>and gdb refuses to do so.

gdb handles this poorly, but you can disassemble almost anything (perhaps
not data) by giving absolute start and end addresses, e.g.,
`disas i586_bc1 i586_bc1+123'.

>yes, the mount was v3 (and probably even TCP).  The NFS server is
>NetApp F330, running Data ONTAP 4.0.1c (that's a dedicated NFS server,
>essentially a Pentium PC with additional SCSI disk shelves, rackmounted.
>The entire OS fits into 1 floppy disk and has a command-line interface
>with similarities to Unix command set.  It does up to 1Mb/s for both NFS
>writes and reads - I wish FreeBSD can do that.)

Perhaps it doesn't handle large file offsets right :-).

Bruce

From owner-freebsd-hackers  Sat Feb  8 12:36:55 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA27626
          for hackers-outgoing; Sat, 8 Feb 1997 12:36:55 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA27621;
          Sat, 8 Feb 1997 12:36:52 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id HAA24797; Sun, 9 Feb 1997 07:34:07 +1100
Date: Sun, 9 Feb 1997 07:34:07 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199702082034.HAA24797@godzilla.zeta.org.au>
To: current@freebsd.org, eivind@dimaga.com, hackers@freebsd.org
Subject: Re: Proposed change to dump/restore
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>The suid capability of dump is only used for remote backups.
>
>dump have been known for security holes in the past, and is not a user
>level program.  I propose a change of default mode and owner for this
>program to
>-r-sr-x--- root:operator /sbin/dump

It should be at least -r-sr-xr--.

>which will disallow anybody not in the operator group from making backups
>using dump (which is not too bad a thing, as only members of wheel can
>access the harddisks directly, which is needed to be able to use dump
>anyway), and only leave dump vulnerable to attacks from an operator :)

Don't forget device independence.  If you somehow have a ufs file system
image in a file, then dump will work on it, and dump/restore is one way
to list its contents.  If dump is world readable, then anyone can run a
nonsetuid copy of it to do this, but it's annoying to have to copy it.

Hard disks are not accessible by members of group wheel.  However, they
are readable by group operator.

Why do dump and restore currently have group tty?

Bruce

From owner-freebsd-hackers  Sat Feb  8 13:35:40 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA01285
          for hackers-outgoing; Sat, 8 Feb 1997 13:35:40 -0800 (PST)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA01276
          for <hackers@FreeBSD.ORG>; Sat, 8 Feb 1997 13:35:33 -0800 (PST)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id NAA09446; Sat, 8 Feb 1997 13:34:58 -0800 (PST)
Received: from alpo.whistle.com(207.76.205.1) by whistle.com via smap (V1.3)
	id sma009444; Sat Feb  8 13:34:47 1997
Received: from current1.whistle.com (current1.whistle.com [207.76.205.22])
          by alpo.whistle.com (8.8.5/8.8.4) with SMTP
	  id NAA21559; Sat, 8 Feb 1997 13:35:28 -0800 (PST)
Message-ID: <32FCF0FA.446B9B3D@whistle.com>
Date: Sat, 08 Feb 1997 13:32:42 -0800
From: Julian Elischer <julian@whistle.com>
Organization: Whistle Communications
X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386)
MIME-Version: 1.0
To: "John S. Dyson" <toor@dyson.iquest.net>
CC: Craig Shaver <craig@progroup.com>, hackers@FreeBSD.ORG
Subject: Re: fcntl, F_SETFL, O_NONBLOCK & /dev/null
References: <199702080220.VAA14428@dyson.iquest.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

John S. Dyson wrote:
> 
> >
> > Is there any work being done for implementing kernel threads?  I would
> > think this would be very important for a robust, real-world usable,
> > thread package.
> >
> That is one of my interests.  Doug Santry is also interested.  Certainly
> don't want to 'claim' the project until I start.  I have some ideas,
> and in conjunction with some of Doug's work, I think that we could
> have a really good thread's capability.  I have a VM experiment to
> do first (relocatable kernel stack, totally shared VM space.)  If
> that works, we'll have a start on a really good mechanism.

YES!

that is the crucial point..
(though there are questions about what to do about thread
signal handlers)

making rfork(SHAREED_VM) work is the first important step
that should make 
rfork(RFMEM|RFPROC) blindingly fast ..

MACH simply allocated a separate kernel stack for each
process, with a guard page.. (touch it and the process dies)

From owner-freebsd-hackers  Sat Feb  8 13:51:42 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA02161
          for hackers-outgoing; Sat, 8 Feb 1997 13:51:42 -0800 (PST)
Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA02152
          for <freebsd-hackers@freefall.FreeBSD.org>; Sat, 8 Feb 1997 13:51:15 -0800 (PST)
Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02)
	id AA18800; Sat, 8 Feb 1997 16:50:06 -0500
Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Sat,  8 Feb 1997 16:50 EST
Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id QAA01503 for <freebsd-hackers@freefall.cdrom.com>; Sat, 8 Feb 1997 16:43:31 -0500 (EST)
Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id QAA20465 for freebsd-hackers@freefall.cdrom.com; Sat, 8 Feb 1997 16:47:53 -0500 (EST)
Date: Sat, 8 Feb 1997 16:47:53 -0500 (EST)
From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
Message-Id: <199702082147.QAA20465@lakes.water.net>
To: ponds!freefall.cdrom.com!freebsd-hackers
Subject: News on daily panic, panic: ffs_valloc: dup alloc  (2.1.x and 2.2)
Content-Type: text
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


Ok - 

 I've hacked together a shell script to build boot floppies and
have been trying to determine the cause of the "dup alloc" problem.

 Some high-level items:

	1) It occurs on a new file system; with the second mkdir().

	2) The inode we're allocating is #7680 - it has not been
	    previously allocated.

	3) The number of inodes per group also happens to be 7680, the
	    newfs output is:
 
    /dev/rsd0a:    204800 sectors in 50 cylinders of 1 tracks, 4096 sectors
            100.0MB in 4 cyl groups (16 c/g, 32.00MG/g, 7680 i/g)
                                                        ^^^^^^^^

 Currently, I'm adding printf's to the kernel and rebooting; while
wading through the macros in /sys/ufs/ffs/fs.h to determine if one of 
them has a boundary problem.  [I'm using 2.1.6.1; but this also occurs 
with 2.2-GAMMA.]

 Some things I've discovered:

	1) in ffs_vget; the ip structure is allocated for inode #7680,
		after the bzero, of course ip->i_mode is 0.

	2) After the bread() to get the block from the disk, we assign
		the 'i_din' structure.  At that point; ip->i_mode (a member
		of the i_din structure) is non-zero (in fact, it is 0xc674).

	3) The subsequent test of a non-zero i_mode causes the "dup alloc"
		panic.

Now - I'm investigating the macros to determine if we've either
read the wrong physical block; or if we're not accessing the data in
the block correctly.

 It does seem to be, though; that allocating a inode which happens
to be the same (possibly a multiple) of the inodes/group is the cause
of my panics.

 When I've gathered all the information on how the inoXXX macros evaluate,
I'll post again.  If anyone has any ideas; feel free to chime in.

	- Dave Rivers -


From owner-freebsd-hackers  Sat Feb  8 15:10:05 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA06223
          for hackers-outgoing; Sat, 8 Feb 1997 15:10:05 -0800 (PST)
Received: from werple.net.au (melb.werple.net.au [203.9.190.18])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA06188
          for <hackers@FreeBSD.ORG>; Sat, 8 Feb 1997 15:09:59 -0800 (PST)
Received: (qmail 14558 invoked by uid 5); 8 Feb 1997 23:09:52 -0000
MBOX-Line: From jb@freebsd1.cimlogic.com.au  Sun Feb  9 10:10:22 1997
Received: (from jb@localhost) by freebsd1.cimlogic.com.au (8.7.5/8.7.3) id KAA01471; Sun, 9 Feb 1997 10:10:22 +1100 (EST)
From: John Birrell <jb@cimlogic.com.au>
Message-Id: <199702082310.KAA01471@freebsd1.cimlogic.com.au>
Subject: Re: fcntl, F_SETFL, O_NONBLOCK & /dev/null
To: julian@whistle.com (Julian Elischer)
Date: Sun, 9 Feb 1997 10:10:21 +1100 (EST)
Cc: toor@dyson.iquest.net, craig@ProGroup.COM, hackers@FreeBSD.ORG
In-Reply-To: <32FCF0FA.446B9B3D@whistle.com> from Julian Elischer at "Feb 8, 97 01:32:42 pm"
X-Mailer: ELM [version 2.4ME+ PL22 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Julian Elischer wrote:
> that is the crucial point..
> (though there are questions about what to do about thread
> signal handlers)

And "realtime" signals according to POSIX 1003.1b too, please.

-- 
John Birrell                                CIMlogic Pty Ltd
jb@cimlogic.com.au; jb@netbsd.org           119 Cecil Street
Ph  +61  3 9690 6900                        South Melbourne Vic 3205
Fax +61  3 9690 6650                        Australia
Mob +61 18  353  137

From owner-freebsd-hackers  Sat Feb  8 15:36:19 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA07462
          for hackers-outgoing; Sat, 8 Feb 1997 15:36:19 -0800 (PST)
Received: from alpha.risc.org (trt-on10-45.netcom.ca [207.181.83.173])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA07453
          for <freebsd-hackers@freebsd.org>; Sat, 8 Feb 1997 15:36:14 -0800 (PST)
Received: from localhost (taob@localhost)
          by alpha.risc.org (8.8.4/8.8.4) with SMTP
	  id SAA17617; Sat, 8 Feb 1997 18:34:39 -0500 (EST)
Date: Sat, 8 Feb 1997 18:34:38 -0500 (EST)
From: Brian Tao <taob@risc.org>
To: Terry Lambert <terry@lambert.org>
cc: FREEBSD-HACKERS-L <freebsd-hackers@freebsd.org>
Subject: Re: Mounting CD-ROM when data not on first track
In-Reply-To: <199702020055.RAA07106@phaeton.artisoft.com>
Message-ID: <Pine.BSF.3.95.970208182948.17605B-100000@alpha.risc.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Sat, 1 Feb 1997, Terry Lambert wrote:
> 
> Does anyone else have this CD?  Do you have a MacOS or SunOS or
> older Windows box with ASPI or proprietary CDROM driver you can try
> it in?  If the non-Joliet aware OS recognizes it, I'd think that the
> FreeBSD interpretation is probably wrong.  I suspect they *must*
> have tested it on a Macintosh before they went to press on it...
> Quicktime is a native Mac format.

    The liner notes on the ST:FC disc say it is Windows 3.1, 3.11, 95
and Macintosh compatible.  It also notes that the disc "may not work
on some CD-ROM drives".  I can reboot my machine into DOS with the
NCR-supplied ASPI drivers and mscdex from DOS 6.2 and see if it can
find the data (I suspect so, else WIn 3.1/3.11 would not be supported).
--
Brian Tao (BT300, taob@risc.org)
"Though this be madness, yet there is method in't"


From owner-freebsd-hackers  Sat Feb  8 16:09:06 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id QAA08941
          for hackers-outgoing; Sat, 8 Feb 1997 16:09:06 -0800 (PST)
Received: (from jmb@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id QAA08935;
          Sat, 8 Feb 1997 16:08:59 -0800 (PST)
From: "Jonathan M. Bresler" <jmb>
Message-Id: <199702090008.QAA08935@freefall.freebsd.org>
Subject: Re: Welcome to freebsd-security
To: brian@wasteland.calbbs.com (Brian Buchanan)
Date: Sat, 8 Feb 1997 16:08:58 -0800 (PST)
Cc: freebsd-hackers@freefall.freebsd.org
In-Reply-To: <Pine.BSF.3.91.970207171726.9740A-100000@wasteland.calbbs.com> from "Brian Buchanan" at Feb 7, 97 05:28:03 pm
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Brian Buchanan wrote:
> 
> 
> 
> On Fri, 7 Feb 1997, Jonathan Lemon wrote:
> 
> > 
> > Uh, why was -hackers just subscribed to -security?
> > > 
> > > Welcome to the freebsd-security mailing list!
> > > 
> 
> Looks to me like someone unfamiliar with majordomo tried to subscribe to 
> multiple lists with one subscribe command, i.e.,
> `subscribe freebsd-security freebsd-hackers', which majordomo would have 
> interpreted as "subscribe the email address `freebsd-hackers' to list 
> `freebsd-security'."

	exactly, and then the postmaster failed to notice the error
	and approved the subscription request....ugh.
jmb

From owner-freebsd-hackers  Sat Feb  8 17:34:07 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA13404
          for hackers-outgoing; Sat, 8 Feb 1997 17:34:07 -0800 (PST)
Received: from perki0.connect.com.au (perki0.connect.com.au [192.189.54.85])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA13372;
          Sat, 8 Feb 1997 17:34:00 -0800 (PST)
Received: from nemeton.UUCP (Unemeton@localhost) by perki0.connect.com.au with UUCP id MAA06070
  (8.7.6h/IDA-1.6); Sun, 9 Feb 1997 12:33:52 +1100 (EST)
X-Authentication-Warning: perki0.connect.com.au: Unemeton set sender to giles@nemeton.com.au using -f
Received: from localhost.nemeton.com.au (localhost.nemeton.com.au [127.0.0.1])
	by nemeton.com.au (8.8.5/8.8.5) with SMTP id MAA10440;
	Sun, 9 Feb 1997 12:30:43 +1100 (EST)
Message-Id: <199702090130.MAA10440@nemeton.com.au>
To: Bruce Evans <bde@zeta.org.au>
cc: current@freebsd.org, eivind@dimaga.com, hackers@freebsd.org
Subject: Re: Proposed change to dump/restore 
In-reply-to: <199702082034.HAA24797@godzilla.zeta.org.au> 
Date: Sun, 09 Feb 1997 12:30:42 +1100
From: Giles Lean <giles@nemeton.com.au>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


On Sun, 9 Feb 1997 07:34:07 +1100  Bruce Evans wrote:

> Why do dump and restore currently have group tty?

     n	   Whenever dump requires operator attention, notify all operators in
	   the group ``operator'' by means similar to a wall(1).

Giles

From owner-freebsd-hackers  Sat Feb  8 18:23:26 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id SAA17091
          for hackers-outgoing; Sat, 8 Feb 1997 18:23:26 -0800 (PST)
Received: from pdx1.world.net (pdx1.world.net [192.243.32.18])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA17073
          for <hackers@freebsd.org>; Sat, 8 Feb 1997 18:23:21 -0800 (PST)
From: proff@suburbia.net
Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id SAA03262 for <hackers@freebsd.org>; Sat, 8 Feb 1997 18:24:44 -0800 (PST)
Received: (qmail 24420 invoked by uid 110); 9 Feb 1997 02:22:52 -0000
Message-ID: <19970209022252.24419.qmail@suburbia.net>
Subject: Re: In what way are shared libs ``shared''?
In-Reply-To: <199702081502.KAA29141@spooky.rwwa.com> from Robert Withrow at "Feb 8, 97 10:02:48 am"
To: witr@rwwa.com (Robert Withrow)
Date: Sun, 9 Feb 1997 13:22:51 +1100 (EST)
Cc: hackers@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Looking at rtld.c I see:
> 
>   addr = mmap(0, hdr.a_text + hdr.a_data + hdr.a_bss,
>               PROT_READ|PROT_EXEC, MAP_COPY, fd, 0)
> 
> >From my understanding of MAP_COPY semantics, this is *not*
> a shared mapping.  If I am right about this, then how
> are shared libs shared?
> 
> -----------------------------------------------------------------------------
> Robert Withrow, Tel: +1 617 592 8935, Net: witr@rwwa.COM
> 
> 
> 

My guess would be that this is due to writable statics in library code, so
the library is shared, but copy-on-write.


--
Prof. Julian Assange  |If you want to build a ship, don't drum up people
		      |together to collect wood and don't assign them tasks
proff@iq.org          |and work, but rather teach them to long for the endless
proff@gnu.ai.mit.edu  |immensity of the sea. -- Antoine de Saint Exupery

From owner-freebsd-hackers  Sat Feb  8 18:50:40 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id SAA20490
          for hackers-outgoing; Sat, 8 Feb 1997 18:50:40 -0800 (PST)
Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id SAA20485
          for <freebsd-hackers@freefall.FreeBSD.org>; Sat, 8 Feb 1997 18:50:36 -0800 (PST)
Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02)
	id AA11335; Sat, 8 Feb 1997 21:50:05 -0500
Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Sat,  8 Feb 1997 21:50 EST
Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id VAA06145; Sat, 8 Feb 1997 21:22:13 -0500 (EST)
Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id VAA22081; Sat, 8 Feb 1997 21:26:35 -0500 (EST)
Date: Sat, 8 Feb 1997 21:26:35 -0500 (EST)
From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
Message-Id: <199702090226.VAA22081@lakes.water.net>
To: ponds!root.com!dg, ponds!freefall.cdrom.com!freebsd-hackers,
        ponds!lambert.org!terry
Subject: Copious information on panic: ffs_valloc: dup alloc - IDEAS???
Content-Type: text
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


Ok -

 Here's the evaluation of the panic: ffs_valloc: dup alloc.
When I say evaluation; I mean I've examined all the macros, and
(using kernel printf's) determined what values are being used.
I've written everything down...  Although I can readily do this;
I have no idea if something is erroneous here; I'm just plugging
in values.  Again, this is all with 2.1.6.1 sources.

 But, I'm wondering what the ino_to_fsba() macro [used in the 
bread() to obtain the disk block in ffs_vget] is going to 
do when the inode is the same as fs->fs_ipg (inodes per group).   

 Another interesting item I've discovered is that the fs->cgmask is 
0xffffffff, rendering most of the macro below unused... here's the logic 
I've evaluated.  These macros are in /sys/ufs/ffs/fs.h:

#define ino_to_fsba(fs, x)                                              \
        ((daddr_t)(cgimin(fs, ino_to_cg(fs, x)) +                       \  
            (blkstofrags((fs), (((x) % (fs)->fs_ipg) / INOPB(fs))))))

 Doesn't that become the same as:

   ((daddr_t)(cgimin(fs, ino_to_cg(fs, x)) +
              (blkstofrags((fs), 0)))

[since ((x) % (fs) -> fs_ipg) is zero when x == (fs)->fs_ipg]

  blkstofrags((fs),0) then evaluates to 0; so you get

   ((daddr_t)(cgimin(fs, ino_to_cg(fs, x)))

Now, ino_to_cg is simply ((x) / (fs)->fs_ipg), which is 1 when 
  x == (fs)->fs_ipg.

Giving:
	cgimin(fs, 1)

{This seems write so far; we indicated we want cylinder #1.}

This becomes:
    cgstart(fs, 1) + (fs->fs_iblkno);

which is:
    (cgbase(fs, 1) + ((fs)->fs_cgoffset * 1) & ~((fs)->fs_cgmask)) 
			+ fs->fs_iblockno


Which, in turn is:
	((fs)->fs_fpg * (1) + 
	   ((fs)->fs_cgoffset * 1) & ~((fs)->fs_cgmask)) + fs->fs_blkno;

 or, eliminating the multiplication of 1:
	((fs)->fs_fpg + ((fs)->fs_cgoffset & ~(fs)->fs_cgmask)) 
	   + fs->fs_iblkno

Now - here's a strangeness - fs->cgmask (as evidenced by my printf()s),
is 0xfffffff, the logical compliment of that is 0;  giving: 

	(fs->fs_fpg) + fs->fs_iblkno;

So, the calculation of ino_to_fsba(fs, x)  becomes (fs->fs_fpg + 
fs->fs_iblkno) For some reason; we've lost fs_cgoffset (because the cgmask 
was "strange.")  I'm not sure if that's intended.

Now, the bread() to retrieve the 'din' info from the disk looks like
(from ffs_vfsops.c):

        /* Read in the disk contents for the inode, copy into the inode. */
        error = bread(ump->um_devvp, fsbtodb(fs, ino_to_fsba(fs, ino)),
            (int)fs->fs_bsize, NOCRED, &bp);

Replacing our evaluation of ino_to_fsba(); we have:

	error = bread(ump->um_devvp, fsbtodb(fs, (fs->fs_fpg + fs->fs_iblkno),
            (int)fs->fs_bsize, NOCRED, &bp);

which is:
	error = bread(ump->um_devvp, (fs->fs_fpg + fs->fs_iblkno) << (fs)->fs_fsbtodb),
	    (int)fs->fs_bsize, NOCRED, &bp);

Now, fs->fpg is 0x8000, fs->fs_iblkno is 0x20 and fs->fsbtodb is 1, so 
this give a block number of 0x10040 (65600).



Ok - that's the logic behind what happens; here's the actual
"screen" of the panic - showing my kernel printf()s that

/dev/rsd0a:     20480
        100.0MB in 4 cyl groups (16 c/g, 32.00MB/g, 7680 i/g)
super-block backups (for fsck -b #) at:
 32, 65568, 131104, 196640,
ffs_vget: ip 0xf0765a00 allocated for ino #7680; ip->i_mode = 0x0
ffs_vget: after i_din assigned, ip->i_mode = 0xc674
          fs->fs_cgoffset is 0x800, fs->fs_cgmask is 0xffffffff 
          fs->fs_fsbtodb = 0x1, fs->fs_fpg = 0x8000
          fs->fs_ipg = 7680, fs->fs_inopb = 64
          fs->fs_iblkno = 0x20
          ino_to_cg(fs, 7680) is 0x1
      blkstofrags((fs), (((ino) % (fs)->fs_ipg) / INOPB(fs))) = 0
          ino_to_cg(fs,ino) = 0x1
          cgimin(fs, ino_to-cg(fs,ino)) = 0x8020
          cgbase(fs, 1) = 0x8000
          ino_to_fsba(fs,ino) is 0x8020
          fsbtodb(fs, ino_to_fsba(fs,ino)) is 0x10040
          ino_to-fsbo(fs,ino) is 0
ffs_alloc: VTOI returns ip for #7680, 0xf0765a00

 mode = 0143164, inum = 7680, fs = /mnt
 ip=0xf0765a00ip->i_number=7680, ino=7680


All of this printf() output verifies the evaluation above.

The question is - something is wrong here (because of the
panic: ffs_valloc: dup alloc) - just what is it?   Can some
knowledgable FFS person examine what I've got here and find
something strange?   Is the disk block number (0x10040) anywhere
near right for inode #7680 on this file system?  Does the fact that
the inode number is the same is inodes/group matter?

	 - Thanks -
	- Dave Rivers -


From owner-freebsd-hackers  Sat Feb  8 18:59:08 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id SAA21039
          for hackers-outgoing; Sat, 8 Feb 1997 18:59:08 -0800 (PST)
Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA21029
          for <hackers@freebsd.org>; Sat, 8 Feb 1997 18:59:02 -0800 (PST)
Received: (from root@localhost) by dyson.iquest.net (8.8.4/8.6.9) id VAA06891; Sat, 8 Feb 1997 21:57:11 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199702090257.VAA06891@dyson.iquest.net>
Subject: Re: In what way are shared libs ``shared''?
To: proff@suburbia.net
Date: Sat, 8 Feb 1997 21:57:11 -0500 (EST)
Cc: witr@rwwa.com, hackers@freebsd.org
In-Reply-To: <19970209022252.24419.qmail@suburbia.net> from "proff@suburbia.net" at Feb 9, 97 01:22:51 pm
X-Mailer: ELM [version 2.4 PL24 ME8]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > Looking at rtld.c I see:
> > 
> >   addr = mmap(0, hdr.a_text + hdr.a_data + hdr.a_bss,
> >               PROT_READ|PROT_EXEC, MAP_COPY, fd, 0)
> > 
> > >From my understanding of MAP_COPY semantics, this is *not*
> > a shared mapping.  If I am right about this, then how
> > are shared libs shared?
> > 
> > -----------------------------------------------------------------------------
> > Robert Withrow, Tel: +1 617 592 8935, Net: witr@rwwa.COM
> > 
> > 
> > 
> 
> My guess would be that this is due to writable statics in library code, so
> the library is shared, but copy-on-write.
> 
Note that alot of really broken VM systems immediately copy .data
in order to simplify the COW action.  We don't do that, and it
does complicate the code, but of course, shares more completely.

John

From owner-freebsd-hackers  Sat Feb  8 19:21:46 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA22149
          for hackers-outgoing; Sat, 8 Feb 1997 19:21:46 -0800 (PST)
Received: from pdx1.world.net (pdx1.world.net [192.243.32.18])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA22143
          for <hackers@freebsd.org>; Sat, 8 Feb 1997 19:21:42 -0800 (PST)
From: proff@suburbia.net
Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id TAA04041 for <hackers@freebsd.org>; Sat, 8 Feb 1997 19:23:06 -0800 (PST)
Received: (qmail 25672 invoked by uid 110); 9 Feb 1997 03:21:07 -0000
Message-ID: <19970209032107.25671.qmail@suburbia.net>
Subject: Re: In what way are shared libs ``shared''?
In-Reply-To: <199702090257.VAA06891@dyson.iquest.net> from "John S. Dyson" at "Feb 8, 97 09:57:11 pm"
To: toor@dyson.iquest.net (John S. Dyson)
Date: Sun, 9 Feb 1997 14:21:07 +1100 (EST)
Cc: hackers@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > My guess would be that this is due to writable statics in library code, so
> > the library is shared, but copy-on-write.
> > 
> Note that alot of really broken VM systems immediately copy .data
> in order to simplify the COW action.  We don't do that, and it
> does complicate the code, but of course, shares more completely.
> 
> John
> 

John, is it possible to force this behavior with rfork/mprotect?
i.e if I rfork(RFPROC|RFMEM), and then do inet_ntoa(addr) in
both parent and child, will the child COW the inet_ntoa static
buffer, or will they collide?


--
Prof. Julian Assange  |If you want to build a ship, don't drum up people
		      |together to collect wood and don't assign them tasks
proff@iq.org          |and work, but rather teach them to long for the endless
proff@gnu.ai.mit.edu  |immensity of the sea. -- Antoine de Saint Exupery

From owner-freebsd-hackers  Sat Feb  8 19:46:46 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA23038
          for hackers-outgoing; Sat, 8 Feb 1997 19:46:46 -0800 (PST)
Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA23033
          for <hackers@freebsd.org>; Sat, 8 Feb 1997 19:46:42 -0800 (PST)
Received: (from root@localhost) by dyson.iquest.net (8.8.4/8.6.9) id WAA07026; Sat, 8 Feb 1997 22:45:59 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199702090345.WAA07026@dyson.iquest.net>
Subject: Re: In what way are shared libs ``shared''?
To: proff@suburbia.net
Date: Sat, 8 Feb 1997 22:45:59 -0500 (EST)
Cc: toor@dyson.iquest.net, hackers@freebsd.org
In-Reply-To: <19970209032107.25671.qmail@suburbia.net> from "proff@suburbia.net" at Feb 9, 97 02:21:07 pm
X-Mailer: ELM [version 2.4 PL24 ME8]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > > My guess would be that this is due to writable statics in library code, so
> > > the library is shared, but copy-on-write.
> > > 
> > Note that alot of really broken VM systems immediately copy .data
> > in order to simplify the COW action.  We don't do that, and it
> > does complicate the code, but of course, shares more completely.
> > 
> > John
> > 
> 
> John, is it possible to force this behavior with rfork/mprotect?
> i.e if I rfork(RFPROC|RFMEM), and then do inet_ntoa(addr) in
> both parent and child, will the child COW the inet_ntoa static
> buffer, or will they collide?
> 
After a quick review of the code, the RFMEM
option will cause sharing of the address space (until the
parent or child changes theirs.)  In the case that you have
given, the child will not COW the page (and the memory
will be shared.)

The problem with RFMEM as it is implemented *right now*,
is that the parent's and child's address spaces will not
track.  This hurts the value of threading using rfork.
We will be (hopefully) supporting true address space
sharing soon (by correcting the semantics of RFMEM)
after the Lite/2 merge (which seems to have new
problems everytime I think that it is nearly done.)
The Lite/2 merge works now, and has been for
quite a while, but now the userland interfaces need
to be cleaned up (libs, etc.)

John

From owner-freebsd-hackers  Sat Feb  8 20:34:24 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA25029
          for hackers-outgoing; Sat, 8 Feb 1997 20:34:24 -0800 (PST)
Received: from news1.gtn.com (news1.gtn.com [194.77.0.15])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA25020
          for <hackers@freebsd.org>; Sat, 8 Feb 1997 20:34:20 -0800 (PST)
Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id OAA27941 for hackers@freebsd.org; Sat, 8 Feb 1997 14:20:33 +0100 (MET)
Received: (from andreas@localhost) by klemm.gtn.com (8.8.5/8.8.2) id NAA04710; Sat, 8 Feb 1997 13:54:55 +0100 (MET)
Message-ID: <19970208135454.ZJ37734@klemm.gtn.com>
Date: Sat, 8 Feb 1997 13:54:54 +0100
From: andreas@klemm.gtn.com (Andreas Klemm)
To: hackers@freebsd.org
Subject: should permissions of /usr/bin/login be changed to 0100 ???
X-Mailer: Mutt 0.60-PL0
Mime-Version: 1.0
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>From the OPIE README file:
[...]
        While an almost universal "feature", most people remain unaware that
an intruder can log into a system, then log in again by running the "login"
command from a shell. Because the second login is from the local host, the
utmp entry will not show a remote login host anymore. The OPIE replacement
for /bin/login currently carries on this behavior for compatibility reasons.
If you would like to prevent this from happening, you should change the
permissions of /bin/login to 0100, thus preventing unprivileged users from
executing it. This fix should work on non-OPIE /bin/login programs as well.
[...]

Our /usr/bin/login program has the following permissions:
-r-sr-xr-x  1 root  bin  24576  6 Feb 01:28 /usr/bin/login

Would it be useful to change permissions to 0100 ?

	Andreas ///

-- 
andreas@klemm.gtn.com         /\/\___      Wiechers & Partner Datentechnik GmbH
   Andreas Klemm          ___/\/\/         Support Unix -- andreas.klemm@wup.de
pgp p-key  http://www-swiss.ai.mit.edu/~bal/pks-toplev.html  >>> powered by <<<
ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz  >>>    FreeBSD <<<

From owner-freebsd-hackers  Sat Feb  8 21:27:40 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA28043
          for hackers-outgoing; Sat, 8 Feb 1997 21:27:40 -0800 (PST)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id VAA28038
          for <hackers@freebsd.org>; Sat, 8 Feb 1997 21:27:37 -0800 (PST)
Received: from rover.village.org [127.0.0.1] 
	by rover.village.org with esmtp (Exim 0.56 #1)
	id E0vtRnR-0003M0-00; Sat, 8 Feb 1997 22:27:25 -0700
To: andreas@klemm.gtn.com (Andreas Klemm)
Subject: Re: should permissions of /usr/bin/login be changed to 0100 ??? 
Cc: hackers@freebsd.org
In-reply-to: Your message of "Sat, 08 Feb 1997 13:54:54 +0100."
		<19970208135454.ZJ37734@klemm.gtn.com> 
References: <19970208135454.ZJ37734@klemm.gtn.com>  
Date: Sat, 08 Feb 1997 22:27:24 -0700
From: Warner Losh <imp@village.org>
Message-Id: <E0vtRnR-0003M0-00@rover.village.org>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <19970208135454.ZJ37734@klemm.gtn.com> Andreas Klemm writes:
: Would it be useful to change permissions to 0100 ?

Sounds good to me, iff this also stops the builtin login in csh from
doing the same thing.

Warner

From owner-freebsd-hackers  Sat Feb  8 21:57:22 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA29070
          for hackers-outgoing; Sat, 8 Feb 1997 21:57:22 -0800 (PST)
Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA29064
          for <hackers@freebsd.org>; Sat, 8 Feb 1997 21:57:16 -0800 (PST)
Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id QAA20177; Sun, 9 Feb 1997 16:59:07 +1100 (EST)
Date: Sun, 9 Feb 1997 16:59:07 +1100 (EST)
From: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
To: Andreas Klemm <andreas@klemm.gtn.com>
cc: hackers@freebsd.org
Subject: Re: should permissions of /usr/bin/login be changed to 0100 ???
In-Reply-To: <19970208135454.ZJ37734@klemm.gtn.com>
Message-ID: <Pine.BSF.3.91.970209165445.427E-100000@panda.hilink.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk



On Sat, 8 Feb 1997, Andreas Klemm wrote:

> >From the OPIE README file:
> [...]
>         While an almost universal "feature", most people remain unaware that
> an intruder can log into a system, then log in again by running the "login"
> command from a shell. Because the second login is from the local host, the
> utmp entry will not show a remote login host anymore. The OPIE replacement
> for /bin/login currently carries on this behavior for compatibility reasons.
> If you would like to prevent this from happening, you should change the
> permissions of /bin/login to 0100, thus preventing unprivileged users from
> executing it. This fix should work on non-OPIE /bin/login programs as well.
> [...]
> 
> Our /usr/bin/login program has the following permissions:
> -r-sr-xr-x  1 root  bin  24576  6 Feb 01:28 /usr/bin/login
> 
> Would it be useful to change permissions to 0100 ?

Perhaps better would be to include the following code: 

if ( !geteuid() ) {
	fprintf(stderr, "You must be root to use 'login' on this system.\n");
	exit(-1);
}

Install /bin/login as mode 555 by default, and if a sysadmin wants to, 
s/he can make it 4555 and get the original behaviour.

Danny

From owner-freebsd-hackers  Sat Feb  8 22:25:52 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id WAA00141
          for hackers-outgoing; Sat, 8 Feb 1997 22:25:52 -0800 (PST)
Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA00136
          for <hackers@freebsd.org>; Sat, 8 Feb 1997 22:25:44 -0800 (PST)
Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id RAA20305; Sun, 9 Feb 1997 17:27:15 +1100 (EST)
Date: Sun, 9 Feb 1997 17:27:14 +1100 (EST)
From: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
To: Warner Losh <imp@village.org>
cc: Andreas Klemm <andreas@klemm.gtn.com>, hackers@freebsd.org
Subject: Re: should permissions of /usr/bin/login be changed to 0100 ??? 
In-Reply-To: <E0vtRnR-0003M0-00@rover.village.org>
Message-ID: <Pine.BSF.3.91.970209172608.427G-100000@panda.hilink.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk



On Sat, 8 Feb 1997, Warner Losh wrote:

> In message <19970208135454.ZJ37734@klemm.gtn.com> Andreas Klemm writes:
> : Would it be useful to change permissions to 0100 ?
> 
> Sounds good to me, iff this also stops the builtin login in csh from
> doing the same thing.

Well, a user's csh is not running as root, so it would *have* to use 
/bin/login if it is going to change uid.  

But see my previous posting.

Danny

From owner-freebsd-hackers  Sat Feb  8 22:35:27 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id WAA00549
          for hackers-outgoing; Sat, 8 Feb 1997 22:35:27 -0800 (PST)
Received: from po8.andrew.cmu.edu (PO8.ANDREW.CMU.EDU [128.2.10.108])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA00542
          for <freebsd-hackers@freefall.FreeBSD.org>; Sat, 8 Feb 1997 22:35:18 -0800 (PST)
Received: (from postman@localhost) by po8.andrew.cmu.edu (8.8.2/8.8.2) id BAA08323 for freebsd-hackers@freefall.FreeBSD.org; Sun, 9 Feb 1997 01:35:07 -0500
Received: via switchmail; Sun,  9 Feb 1997 01:35:05 -0500 (EST)
Received: from apriori.cc.cmu.edu via qmail
          ID </afs/andrew.cmu.edu/service/mailqs/q004/QF.0mzKzw:00YVp40O0A=>;
          Sun,  9 Feb 1997 01:34:36 -0500 (EST)
Received: from apriori.cc.cmu.edu via qmail
          ID </afs/andrew.cmu.edu/usr4/rnw/.Outgoing/QF.EmzKzva00YVpIcONdJ>;
          Sun,  9 Feb 1997 01:34:35 -0500 (EST)
Received: from mms.4.60.Jun.27.1996.03.05.56.sun4.41.EzMail.2.0.CUILIB.3.45.SNAP.NOT.LINKED.apriori.cc.cmu.edu.sun4m.412
          via MS.5.6.apriori.cc.cmu.edu.sun4_41;
          Sun,  9 Feb 1997 01:34:34 -0500 (EST)
Message-ID: <smzKzua00YVpEcONQY@andrew.cmu.edu>
Date: Sun,  9 Feb 1997 01:34:34 -0500 (EST)
From: Robert N Watson <rnw+@andrew.cmu.edu>
To: freebsd-hackers@freefall.FreeBSD.org
Subject: Thoughts on upgrade process
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


I've done a few FreeBSD upgrades over the last few years on my main
server, and the only upsetting experience in this has been grabbing
those last few local binaries from previous installations.  E.g., I
usually have a few modified local versions of binaries, and weird binary
names linked against old libraries.  It would be really nice to have a
mechanism for getting console messages when old binaries are used so I
can track them down.  Would it be possible to add a debug line to the
exec implementation that could be turned on in the kernel config/sysctl.
 E.g, kern.warnoldbin or options="WARNOLDBIN".  On exec of an old-linked
(compat linked?) binary, a warning would display.

Alternatively, there may already be a mechanism for doing this :)

Robert Watson 

From owner-freebsd-hackers  Sat Feb  8 22:40:23 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id WAA00942
          for hackers-outgoing; Sat, 8 Feb 1997 22:40:23 -0800 (PST)
Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA00929
          for <hackers@freebsd.org>; Sat, 8 Feb 1997 22:40:19 -0800 (PST)
Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id RAA20370; Sun, 9 Feb 1997 17:42:37 +1100 (EST)
Date: Sun, 9 Feb 1997 17:42:37 +1100 (EST)
From: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
To: Andreas Klemm <andreas@klemm.gtn.com>, hackers@freebsd.org
Subject: Re: should permissions of /usr/bin/login be changed to 0100 ???
In-Reply-To: <Pine.BSF.3.91.970209165445.427E-100000@panda.hilink.com.au>
Message-ID: <Pine.BSF.3.91.970209174043.427H-100000@panda.hilink.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk



On Sun, 9 Feb 1997, Daniel O'Callaghan wrote:

> > 
> > Our /usr/bin/login program has the following permissions:
> > -r-sr-xr-x  1 root  bin  24576  6 Feb 01:28 /usr/bin/login
> > 
> > Would it be useful to change permissions to 0100 ?
> 
> Perhaps better would be to include the following code: 
> 
> if ( !geteuid() ) {
> 	fprintf(stderr, "You must be root to use 'login' on this system.\n");
> 	exit(-1);
> }
> 
> Install /bin/login as mode 555 by default, and if a sysadmin wants to, 
> s/he can make it 4555 and get the original behaviour.

Arrgh!  What a braino!  Below is *much* better.

 if ( geteuid() != 0 ) {
 	fprintf(stderr, "You must be root to use 'login' on this system.\n");
 	exit(-1);
 }

Danny

From owner-freebsd-hackers  Sat Feb  8 23:49:29 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA05112
          for hackers-outgoing; Sat, 8 Feb 1997 23:49:29 -0800 (PST)
Received: from widefw.csl.sony.co.jp (widefw.csl.sony.co.jp [133.138.1.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA05105;
          Sat, 8 Feb 1997 23:49:24 -0800 (PST)
Received: from hotaka.csl.sony.co.jp (hotaka.csl.sony.co.jp [43.27.98.57]) by widefw.csl.sony.co.jp (8.8.3/3.5Wbeta) with ESMTP id HAA29002; Sun, 9 Feb 1997 07:49:11 GMT
Received: from localhost (localhost [127.0.0.1]) by hotaka.csl.sony.co.jp (8.8.4/3.3W3) with ESMTP id QAA29283; Sun, 9 Feb 1997 16:48:55 +0859 (JST)
Message-Id: <199702090749.QAA29283@hotaka.csl.sony.co.jp>
To: Garrett Wollman <wollman@lcs.mit.edu>
cc: Eka Kelana <eka@werty.wasantara.net.id>, freebsd-hackers@FreeBSD.ORG,
        freebsd-bugs@FreeBSD.ORG, dg@root.com
Subject: Re: Need quick answer 
In-reply-to: Your message of "Fri, 07 Feb 1997 07:29:24 EST."
             <9702071229.AA18092@halloran-eldar.lcs.mit.edu> 
Date: Sun, 09 Feb 1997 16:48:54 +0900
From: Kenjiro Cho <kjc@csl.sony.co.jp>
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


<<On Fri, 7 Feb 1997 05:28:25 +0700, Eka Kelana <eka@werty.wasantara.net.id> said:
> I need a good explanation about this code in in_rmx.c:
> ...
> if (!rt->rt_rmx.rmx_sendpipe && !(rt->rt_rmx.rmx_locks & RTV_SPIPE))
rt-> rt_rmx.rmx_sendpipe = tcp_sendspace;
> if (!rt->rt_rmx.rmx_recvpipe && !(rt->rt_rmx.rmx_locks & RTV_RPIPE))
rt-> rt_rmx.rmx_recvpipe = tcp_recvspace;
> ...

>>>>> On Fri, 7 Feb 1997 07:29:24 -0500, Garrett Wollman <wollman@lcs.mit.edu> said:
>> The reason why that is there is because otherwise tcp_close() won't
>> save the ssthresh.

If this is the only reason to set the pipe sizes, I would suggest to
make modifications to
      -	tcp_close to update ssthresh even when the pipe sizes are not
	specified.
      -	in_addroute to leave the pipe sizes unspecified.

Then, ssthresh can be updated in the same manner, but no side-effect.

IMO, if the pipe size is ever set automatically, it should reflect the 
measured throughput * RTT.

--kj

---
Kenjiro Cho
Sony Computer Science Laboratory Inc.