From owner-freebsd-hackers Sun Sep 15 01:21:56 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA09283 for hackers-outgoing; Sun, 15 Sep 1996 01:21:56 -0700 (PDT) Received: from dns2.noc.best.net (dns2.noc.best.net [206.86.0.21]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA09265; Sun, 15 Sep 1996 01:21:51 -0700 (PDT) Received: from shellx.best.com (shellx.best.com [206.86.0.11]) by dns2.noc.best.net (8.6.12/8.6.5) with SMTP id BAA24785; Sun, 15 Sep 1996 01:21:45 -0700 Date: Sun, 15 Sep 1996 01:21:45 -0700 (PDT) From: Amanda Chou To: "Michael L. VanLoon -- HeadCandy.com" cc: questions@freebsd.org, hackers@freebsd.org, hardware@freebsd.org Subject: Re: Q: Tyan Tomcat I with > 64MB RAM In-Reply-To: <199609140341.UAA04018@MindBender.serv.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 13 Sep 1996, Michael L. VanLoon -- HeadCandy.com wrote: > > >Has anyone used Tyan Tomcat I with more than 64MB RAM? We ran into some > >weird problems; it works fine when we just put 64MB EDO RAM, but it got > >panicked at booting or some other random time when we put more than 64MB > >EDO RAM. We followed the manual and changed its jumper setting, added one > >more 32K X 8K SRAM; we changed the Award BIOS to make it able to recongnize > >the memory up to 512MB; we added an option so it'll work with 128MB RAM. > >Any idea? > > I'm not sure I followed everything you just tried to say. Oh, what I tried to say was that we tried _everything_ to make Tyan TomcatI motherboard to be happy with memory more than 64MB. > However, have you tested the memory by itself to make sure you don't > have a bad chip? Yes, we did; I replaced one bad SIMM. Actually we solved the problem already, and the solution is fairly simple (but not terribly obvious). I got those 8 16MB EDO RAMs from two different places: Fry's and Chip Merchant. Fry's get their chips from different suppliers, while Chip Merchant get theirs only from one place. As soon as we put Fry's RAM in lower banks and Chip Merchant's in the higher banks, bingo, it started working! The lesson we learned is: try to get all your memory made from the same factory if you try to build a system with more than 64MB RAM. Amanda From owner-freebsd-hackers Sun Sep 15 03:54:52 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA13951 for hackers-outgoing; Sun, 15 Sep 1996 03:54:52 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA13932; Sun, 15 Sep 1996 03:54:45 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.7.5/8.7.3) id DAA00240; Sun, 15 Sep 1996 03:53:14 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199609151053.DAA00240@GndRsh.aac.dev.com> Subject: Re: Q: Tyan Tomcat I with > 64MB RAM In-Reply-To: from Amanda Chou at "Sep 15, 96 01:21:45 am" To: achou@best.com (Amanda Chou) Date: Sun, 15 Sep 1996 03:53:14 -0700 (PDT) Cc: michaelv@MindBender.serv.net, questions@freebsd.org, hackers@freebsd.org, hardware@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 ... > > Actually we solved the problem already, and the solution is fairly simple > (but not terribly obvious). I got those 8 16MB EDO RAMs from two different > places: Fry's and Chip Merchant. Fry's get their chips from different > suppliers, while Chip Merchant get theirs only from one place. As soon as > we put Fry's RAM in lower banks and Chip Merchant's in the higher banks, > bingo, it started working! Someone at Chip Merchant is not telling you the whole truth. They may be _buying_ all thier memory from the same memory broker, but it comes from all over the place. Just taking a sample of my last 5 orders of 32MB, 8MBx36-60nS FPM 24 chip modules I show these manufactures: LGS on 3rd party LGS with MT parity on Liteon OKI on 3rd party OKI on 3rd party SEC on 3rd party You have a very slim chance of getting the same memory 2 orders in a row from the Chip Merchant, and realize I am a manufacturer who is order in volume once or twice a week. (Okay, so now all your folks know where AAC gets good memory from :-)). > > The lesson we learned is: try to get all your memory made from the same > factory if you try to build a system with more than 64MB RAM. Let me guess that some of this EDO memory is made by someone other than Micron, yea, let me see if I can put my finger on it... could it possibly be Siemens? If so be wary, there is a huge batch of these chips floating around that appear to be marginal. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-hackers Sun Sep 15 07:54:50 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA21932 for hackers-outgoing; Sun, 15 Sep 1996 07:54:50 -0700 (PDT) Received: from cmr.kiev.ua (root@cmr.kiev.ua [193.193.193.50]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA21907 for ; Sun, 15 Sep 1996 07:54:07 -0700 (PDT) Received: (archer@localhost) by cmr.kiev.ua (Sendmail 8.who.cares/5) id OAA03121; Sun, 15 Sep 1996 14:50:55 GMT Date: Sun, 15 Sep 1996 17:50:54 +0300 (EET DST) From: "Litvin Alexander B." To: hackers@freebsd.org Subject: ATM/FreeBSD advise needed! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, All! We need advise on the following problem. We already have ATM-based backbone (or almost already), and we want to use it as a transport for (mainly) TCP/IP. Most of our boxes are FreeBSD. The problem is that we are not so reach so that we can buy any hardware we want. And we have one location which: a) is a place where FreeBSD box connected to Internet is located; b) should definitely be connected to backbone (because it is gateway to Internet ;-); c) has fiber-optic lines, but doesn't have interface (or ATM/Ethernet switch, or something else) to connect FreeBSD box to backbone. The network has the following structure, where "???" is the location mentioned above. ---------------/ Internet ---|Catalyst 3000|--- ^ / ---------------\ E t h e r - | / ------- ---------------------/ ---------------/ n e t -- | ??? |--------| Cisco LightStream |------|Catalyst 3000|--- ------- ---------------------\ ---------------\ connected | \ | \ ---------------/ locations | ---|Catalyst 3000|--- | ---------------\ | | |-------------- ... Is it possible to make FreeBSD server run with ATM card (Cisco LightStream switch)? Which card should it be? Of course, we can set up ATM/Ethernet switch at "???", but we don't want to do it because the place where server should run doesn't need so many Ethernet ports as provided by switch, and it seems that powerful PC with ATM adapter under FreeBSD would be a "bit" cheaper solution (anyway, we have only about $22000). We can move one Catalyst to "???", but it means we should give away connectivity of some other location... What whould you suggest? May be not PC/FreeBSD - than what? Any help/opinion would be appreciated. -- Litvin Alexander From owner-freebsd-hackers Sun Sep 15 08:44:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA23909 for hackers-outgoing; Sun, 15 Sep 1996 08:44:25 -0700 (PDT) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA23904 for ; Sun, 15 Sep 1996 08:44:22 -0700 (PDT) Received: from dialup-usr14.etinc.com (dialup-usr14.etinc.com [204.141.95.130]) by etinc.com (8.6.12/8.6.9) with SMTP id LAA08784; Sun, 15 Sep 1996 11:50:48 -0400 Date: Sun, 15 Sep 1996 11:50:48 -0400 Message-Id: <199609151550.LAA08784@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Sandy Kovshov From: dennis@etinc.com (dennis) Subject: Re: sppp with cisco hdlc bug fix Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Why would you process a packet with an invalid header in the first place? Dennis > Hello guys, > > > Here is little patch for bug in sppp pseudo driver with cisco hdlc protocol. > I've found it when test Riscom/N2 card with Cisco. At unknown reason, > Cisco send 20 byte packet (without ppp header) instead of 18 ;) > With old version it cause line hangup on keepalive timeout. > > >Index: net/if_spppsubr.c >=================================================================== >RCS file: /home/sandy/project/freebsd/cvs/src/sys/net/if_spppsubr.c,v >retrieving revision 1.13 >diff -c -r1.13 if_spppsubr.c >*** if_spppsubr.c 1996/08/30 16:44:36 1.13 >--- if_spppsubr.c 1996/09/15 01:46:31 >*************** >*** 848,854 **** > struct ifaddr *ifa; > struct ifnet *ifp = &sp->pp_if; > >! if (m->m_pkthdr.len != CISCO_PACKET_LEN) { > if (ifp->if_flags & IFF_DEBUG) > printf ("%s%d: invalid cisco packet length: %d bytes\n", > ifp->if_name, ifp->if_unit, m->m_pkthdr.len); >--- 848,854 ---- > struct ifaddr *ifa; > struct ifnet *ifp = &sp->pp_if; > >! if (m->m_pkthdr.len < CISCO_PACKET_LEN) { > if (ifp->if_flags & IFF_DEBUG) > printf ("%s%d: invalid cisco packet length: %d bytes\n", > ifp->if_name, ifp->if_unit, m->m_pkthdr.len); > > > With best regards. >--- >Sandy >E-mail: Internet: sandy@dream.demos.su sandy@www.RoSprint.ru > X.400: (C:USSR,A:SOVMAIL,O:SNUSSR,UN:A.KOVSHOV) > X.400: (C:USA,A:TELEMAIL,O:SPRINTINTL,UN:A.KOVSHOV) > > ---------------------------------------------------------------------------- Emerging Technologies, Inc. http://www.etinc.com Synchronous PC Cards and Routers For Discriminating Tastes. 56k to T1 and beyond. Frame Relay, PPP, HDLC, and X.25 for BSD/OS, FreeBSD and LINUX. From owner-freebsd-hackers Sun Sep 15 15:20:07 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA18268 for hackers-outgoing; Sun, 15 Sep 1996 15:20:07 -0700 (PDT) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [204.214.4.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA18259; Sun, 15 Sep 1996 15:20:04 -0700 (PDT) Received: from bonsai.hiwaay.net by fly.HiWAAY.net; (8.7.5/1.1.8.2/21Sep95-1003PM) id RAA32675; Sun, 15 Sep 1996 17:19:47 -0500 (CDT) Message-ID: <323C80B6.15FB7483@hiwaay.net> Date: Sun, 15 Sep 1996 17:18:30 -0500 From: Steve Price X-Mailer: Mozilla 2.02 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: asami@cs.berkeley.edu CC: hackers@freebsd.org, FreeBSD-gnats-submit@freebsd.org Subject: Re: bin/1095: make's continuation line handling buggy when used with .elif Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Attached is a patch that fixes the problem pointed out in bin/1095. steve[~]$ cat > Makefile1 all: .if defined(foo) @true .elif !defined(foo) && !defined(foo) @echo ok .else @echo not ok .endif steve[~]$ make -f Makefile1 ok steve[~]$ cat > Makefile2 all: .if defined(foo) @true .else .if !defined(foo) && \ !defined(foo) @echo ok .else @echo not ok .endif .endif steve[~]$ make -f Makefile2 ok steve[~]$ cat > Makefile3 all: .if defined(foo) @true .elif !defined(foo) && \ !defined(foo) @echo ok .else @echo not ok .endif steve[~]$ make -f Makefile3 ok steve[~]$ Steve Index: buf.c =================================================================== RCS file: /u/FreeBSD/cvs/src/usr.bin/make/buf.c,v retrieving revision 1.3 diff -u -r1.3 buf.c --- buf.c 1995/05/30 06:31:48 1.3 +++ buf.c 1996/09/14 14:49:25 @@ -434,3 +434,28 @@ } free ((char *)buf); } + +/*- + *----------------------------------------------------------------------- + * Buf_ReplaceLastByte -- + * Replace the last byte in a buffer. + * + * Results: + * None. + * + * Side Effects: + * If the buffer was empty intially, then a new byte will be added. + * Otherwise, the last byte is overwritten. + * + *----------------------------------------------------------------------- + */ +void +Buf_ReplaceLastByte (buf, byte) + Buffer buf; /* buffer to augment */ + Byte byte; /* byte to be written */ +{ + if (buf->inPtr == buf->outPtr) + Buf_AddByte(buf, byte); + else + *(buf->inPtr - 1) = byte; +} Index: buf.h =================================================================== RCS file: /u/FreeBSD/cvs/src/usr.bin/make/buf.h,v retrieving revision 1.2 diff -u -r1.2 buf.h --- buf.h 1995/01/23 21:00:21 1.2 +++ buf.h 1996/09/14 14:36:19 @@ -76,5 +76,6 @@ int Buf_Size __P((Buffer)); Buffer Buf_Init __P((int)); void Buf_Destroy __P((Buffer, Boolean)); +void Buf_ReplaceLastByte __P((Buffer, Byte)); #endif /* _BUF_H */ Index: parse.c =================================================================== RCS file: /u/FreeBSD/cvs/src/usr.bin/make/parse.c,v retrieving revision 1.9 diff -u -r1.9 parse.c --- parse.c 1996/09/12 03:03:25 1.9 +++ parse.c 1996/09/14 14:46:19 @@ -2009,54 +2009,43 @@ int skip; /* Skip lines that don't start with . */ { char *line; - int c, lastc = '\0', lineLength; + int c, lastc, lineLength = 0; Buffer buf; - c = ParseReadc(); + buf = Buf_Init(MAKE_BSIZE); - if (skip) { - /* - * Skip lines until get to one that begins with a - * special char. - */ - while ((c != '.') && (c != EOF)) { - while (((c != '\n') || (lastc == '\\')) && (c != EOF)) - { - /* - * Advance to next unescaped newline - */ - if ((lastc = c) == '\n') { - lineno++; - } - c = ParseReadc(); - } - lineno++; - - lastc = c; - c = ParseReadc (); - } - } - - if (c == EOF) { - Parse_Error (PARSE_FATAL, "Unclosed conditional/for loop"); - return ((char *)NULL); - } - - /* - * Read the entire line into buf - */ - buf = Buf_Init (MAKE_BSIZE); - if (c != '\n') { - do { - Buf_AddByte (buf, (Byte)c); - c = ParseReadc(); - } while ((c != '\n') && (c != EOF)); - } - lineno++; - - Buf_AddByte (buf, (Byte)'\0'); - line = (char *)Buf_GetAll (buf, &lineLength); - Buf_Destroy (buf, FALSE); + do { + Buf_Discard(buf, lineLength); + lastc = '\0'; + + while (((c = ParseReadc()) != '\n' || lastc == '\\') + && c != EOF) { + if (c == '\n') { + Buf_ReplaceLastByte(buf, (Byte)' '); + lineno++; + + while ((c = ParseReadc()) == ' ' || c == '\t'); + + if (c == EOF) + break; + } + + Buf_AddByte(buf, (Byte)c); + lastc = c; + } + + if (c == EOF) { + Parse_Error(PARSE_FATAL, "Unclosed conditional/for loop"); + return((char *)NULL); + } + + lineno++; + Buf_AddByte(buf, (Byte)c); + Buf_AddByte(buf, (Byte)'\0'); + line = (char *)Buf_GetAll(buf, &lineLength); + } while (skip == 1 && line[0] != '.'); + + Buf_Destroy(buf, FALSE); return line; } From owner-freebsd-hackers Sun Sep 15 15:20:09 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA18285 for hackers-outgoing; Sun, 15 Sep 1996 15:20:09 -0700 (PDT) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [204.214.4.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA18265; Sun, 15 Sep 1996 15:20:06 -0700 (PDT) Received: from bonsai.hiwaay.net by fly.HiWAAY.net; (8.7.5/1.1.8.2/21Sep95-1003PM) id RAA16764; Sun, 15 Sep 1996 17:19:58 -0500 (CDT) Message-ID: <323C80C0.59E2B600@hiwaay.net> Date: Sun, 15 Sep 1996 17:18:40 -0500 From: Steve Price X-Mailer: Mozilla 2.02 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: archie@whistle.com CC: hackers@freebsd.org, FreeBSD-gnats-submit@freebsd.org Subject: Re: bin/1230: make ``.for'' loops iterate backwards Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Attached is patch that fixes the problem pointed out in bin/1230. steve[~]$ cat Makefile ORIG= a b c .for VAR in a b c LIST+= ${VAR} .endfor default: @echo ${LIST} ^D steve[~]$ make a b c steve[~]$ Regards, Steve Index: for.c =================================================================== RCS file: /u/FreeBSD/cvs/src/usr.bin/make/for.c,v retrieving revision 1.3 diff -u -r1.3 for.c --- for.c 1995/05/30 06:31:52 1.3 +++ for.c 1996/09/14 00:26:03 @@ -174,7 +174,7 @@ #define ADDWORD() \ Buf_AddBytes(buf, ptr - wrd, (Byte *) wrd), \ Buf_AddByte(buf, (Byte) '\0'), \ - Lst_AtEnd(forLst, (ClientData) Buf_GetAll(buf, &varlen)), \ + Lst_AtFront(forLst, (ClientData) Buf_GetAll(buf, &varlen)), \ Buf_Destroy(buf, FALSE) for (ptr = sub; *ptr && isspace((unsigned char) *ptr); ptr++) From owner-freebsd-hackers Sun Sep 15 15:20:26 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA18322 for hackers-outgoing; Sun, 15 Sep 1996 15:20:26 -0700 (PDT) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [204.214.4.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA18316 for ; Sun, 15 Sep 1996 15:20:23 -0700 (PDT) Received: from bonsai.hiwaay.net by fly.HiWAAY.net; (8.7.5/1.1.8.2/21Sep95-1003PM) id RAA26121; Sun, 15 Sep 1996 17:20:20 -0500 (CDT) Message-ID: <323C80D6.1CFBAE39@hiwaay.net> Date: Sun, 15 Sep 1996 17:19:02 -0500 From: Steve Price X-Mailer: Mozilla 2.02 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: patch to cleanup code generated by yacc(1) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi all, Attached is a patch that -Wall'izes the code generated by yacc(1). Compiling yacc with -Wall still produces scads 'o warnings, but at least the code that it generates is nearly -Wall proof. :) Steve Index: skeleton.c =================================================================== RCS file: /u/FreeBSD/cvs/src/usr.bin/yacc/skeleton.c,v retrieving revision 1.4 diff -u -r1.4 skeleton.c --- skeleton.c 1996/09/03 10:56:32 1.4 +++ skeleton.c 1996/09/14 02:18:32 @@ -55,7 +55,7 @@ char *banner[] = { "#ifndef lint", - "static char yysccsid[] = \"@(#)yaccpar 1.9 (Berkeley) 02/21/93\";", + "static char const yysccsid[] = \"@(#)yaccpar 1.9 (Berkeley) 02/21/93\";", "#endif", "#define YYBYACC 1", "#define YYMAJOR 1", @@ -63,6 +63,23 @@ "#define yyclearin (yychar=(-1))", "#define yyerrok (yyerrflag=0)", "#define YYRECOVERING (yyerrflag!=0)", + "/* cfront 1.2 defines \"c_plusplus\" instead of \"__cplusplus\" */", + "#ifdef c_plusplus", + "#ifndef __cplusplus", + "#define __cplusplus", + "#endif", + "#endif", + "#ifdef __cplusplus", + "extern \"C\" {", + " char *getenv(const char *);", + " int yyparse();", + " int yylex();", + "}", + "#else", + "extern char *getenv();", + "extern int yylex();", + "extern int yyparse();", + "#endif", 0 }; @@ -120,17 +137,6 @@ "#define YYREJECT goto yyabort", "#define YYACCEPT goto yyaccept", "#define YYERROR goto yyerrlab", - "/* cfront 1.2 defines \"c_plusplus\" instead of \"__cplusplus\" */", - "#ifdef c_plusplus", - "#ifndef __cplusplus", - "#define __cplusplus", - "#endif", - "#endif", - "#ifdef __cplusplus", - "extern \"C\" { char *getenv(const char *); }", - "#else", - "extern char *getenv();", - "#endif", "", "int", "yyparse()", @@ -196,12 +202,12 @@ " goto yyreduce;", " }", " if (yyerrflag) goto yyinrecovery;", - "#ifdef lint", + "#if defined(lint) || defined(__GNUC__)", " goto yynewerror;", "#endif", "yynewerror:", " yyerror(\"syntax error\");", - "#ifdef lint", + "#if defined(lint) || defined(__GNUC__)", " goto yyerrlab;", "#endif", "yyerrlab:", From owner-freebsd-hackers Sun Sep 15 15:23:33 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA18478 for hackers-outgoing; Sun, 15 Sep 1996 15:23:33 -0700 (PDT) Received: from orion.webspan.net (root@orion.webspan.net [206.154.70.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA18472 for ; Sun, 15 Sep 1996 15:23:30 -0700 (PDT) Received: from localhost (gpalmer@localhost [127.0.0.1]) by orion.webspan.net (8.7.5/8.6.12) with SMTP id SAA19460; Sun, 15 Sep 1996 18:23:06 -0400 (EDT) X-Authentication-Warning: orion.webspan.net: Host gpalmer@localhost [127.0.0.1] didn't use HELO protocol To: Robin Cutshaw cc: gilham@csl.sri.com (Fred Gilham), freebsd-hackers@FreeBSD.org From: "Gary Palmer" Subject: Re: 2.2-960801-SNAP--Problem with SMC 10/100 card and SMC 100mb `tiger hub' In-reply-to: Your message of "Fri, 13 Sep 1996 21:13:08 EDT." <199609140113.VAA28902@intercore.com> Date: Sun, 15 Sep 1996 18:23:06 -0400 Message-ID: <19457.842826186@orion.webspan.net> Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Robin Cutshaw wrote in message ID <199609140113.VAA28902@intercore.com>: > > > > > > I've noticed that running the 2.2-960801 snap causes the de driver to > > fail to link up to the 100mb SMC tiger hub that we're experimenting > > with. It always reports > > > > de0: enabling 10baseT port > > > > I had to add "link2" to the ifconfig of the device to get it to > switch to 100Mb mode. Autosensing doesn't seem to work. There is a known problem in -current wrt. the if_de code. Apparently David Greenman has a set of patches in his inbox to fix them, but they haven't surfaced yet. On a -current machine here I suspected the driver may have locked up the machine (pure speculation btw), so I dropped the 2.1.5-RELEASE driver in without problems. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-hackers Sun Sep 15 16:04:55 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA20858 for hackers-outgoing; Sun, 15 Sep 1996 16:04:55 -0700 (PDT) Received: from orion.webspan.net (root@orion.webspan.net [206.154.70.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA20842 for ; Sun, 15 Sep 1996 16:04:21 -0700 (PDT) Received: from localhost (gpalmer@localhost [127.0.0.1]) by orion.webspan.net (8.7.5/8.6.12) with SMTP id TAA22907; Sun, 15 Sep 1996 19:03:29 -0400 (EDT) X-Authentication-Warning: orion.webspan.net: Host gpalmer@localhost [127.0.0.1] didn't use HELO protocol To: Tony Kimball cc: avalon@coombs.anu.edu.au, hackers@freebsd.org From: "Gary Palmer" Subject: Re: SYN Resisting (fwd) In-reply-to: Your message of "Thu, 12 Sep 1996 22:34:51 CDT." <199609130334.WAA25622@compound.Think.COM> Date: Sun, 15 Sep 1996 19:03:29 -0400 Message-ID: <22903.842828609@orion.webspan.net> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Tony Kimball wrote in message ID <199609130334.WAA25622@compound.Think.COM>: > Hah, I've seen MCI drop 66% at WillowSprings for hours at a time, > and Sprint drop 50% at MAE-East for similarly protracted times. > It's like tin-cans on yo-yo strings out there. According to something I heard last night that should be changing (for MCI at least). WestOrange.mci.net lost connectivity to Washington.mci.net for a long time yesterday, and when an enquiry was made to the MCI NOC, it seems that it was due to a change-over to OC12 between the two locations, and route flapping and general instability seemed to result for some reason. So all we need now are NAP's that run at (at least) OC3 speeds ... :-( Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-hackers Sun Sep 15 18:33:13 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA01942 for hackers-outgoing; Sun, 15 Sep 1996 18:33:13 -0700 (PDT) Received: from mailbox.neosoft.com (mailbox.neosoft.com [206.109.1.16]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA01934 for ; Sun, 15 Sep 1996 18:32:59 -0700 (PDT) Received: from bonkers.taronga.com (bonkers.neosoft.com [206.109.2.48]) by mailbox.neosoft.com (8.7.5/8.7.3) with SMTP id TAA25374 for ; Sun, 15 Sep 1996 19:09:00 -0500 (CDT) Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id TAA19884; Sun, 15 Sep 1996 19:07:34 -0500 Date: Sun, 15 Sep 1996 19:07:34 -0500 From: peter@taronga.com (Peter da Silva) Message-Id: <199609160007.TAA19884@bonkers.taronga.com> To: hackers@freebsd.org Subject: Re: File System on a tape Newsgroups: taronga.freebsd.hackers In-Reply-To: <199608161557.IAA19105@seagull.rtd.com> References: Organization: none Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [sorry for sending this to doc first time. brain fart] You can get an IDE controller and an IDE CDROM for $60.00. And have any of you guys RUN a file system off a tape? I have. Even with DECTAPE cartridges and a file system designed for file systems it sucks, bigtime. And it's also going to put serious wear on any streaming tape drive... they're not designed to go stop-start like the DECTAPEs were. I suspect it'd be a use-once deal. Afterwards, you throw out the tape drive. Yes, by all means have an install from tape option... but it'd be easier and quicker to do it with a floppy boot to a tmpfs file system loaded off the first file on the tape, then just seek over whole tape files to extract particular options. From owner-freebsd-hackers Mon Sep 16 00:12:52 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA17368 for hackers-outgoing; Mon, 16 Sep 1996 00:12:52 -0700 (PDT) Received: from relay.hp.com (relay.hp.com [15.255.152.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA17360 for ; Mon, 16 Sep 1996 00:12:48 -0700 (PDT) Received: from srmail.sr.hp.com by relay.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA264757966; Mon, 16 Sep 1996 00:12:47 -0700 Received: from hpnmhjw.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA272027965; Mon, 16 Sep 1996 00:12:46 -0700 Received: from mina.sr.hp.com by hpnmhjw.sr.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA113897963; Mon, 16 Sep 1996 00:12:43 -0700 Message-Id: <199609160712.AA113897963@hpnmhjw.sr.hp.com> To: hackers@freefall.freebsd.org Subject: fdisk changes, anyone? Date: Mon, 16 Sep 1996 00:12:43 -0700 From: Darryl Okahata Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I've just mangled fdisk such that partitioning information can now be specified via an optional config file. I've been needing a way to partition a disk from a script (without using expect), and so I mangled fdisk to do just that. I want to write a perl script for adding SCSI disks, and a programmatic fdisk was the only piece missing. An example config file is: # Set geometry to 1019 cylinders, 39 heads, 63 sectors: g c1019 h39 s63 # Set partition 0 to FreeBSD, starting at 1 for 2503871 sectors # (these numbers will get rounded up or down to fall on # head/cylinder boundaries): p 0 165 1 2503871 Another example: # Dedicate entire disk to FreeBSD (this is for a Quantum # Fireball 1280S): f 2503872 Would anyone be interested in the changes (including man page updates)? Should I submit an enhancement request (w/patches), or should I consign these changes to the mists of time? ;-) [ One area of concern is that I'm a bit unclear on the start/end address requirements. Right now, start offsets are being rounded up to an head boundary, but end addresses are being rounded down to major cylinder boundaries (every head*sector chunk). Is this right? ] -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. From owner-freebsd-hackers Mon Sep 16 00:12:54 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA17381 for hackers-outgoing; Mon, 16 Sep 1996 00:12:54 -0700 (PDT) Received: from relay.philips.nl (ns.philips.nl [130.144.65.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA17362 for ; Mon, 16 Sep 1996 00:12:48 -0700 (PDT) Received: (from smap@localhost) by relay.philips.nl (8.6.9/8.6.9-950414) id JAA26225; Mon, 16 Sep 1996 09:11:30 +0200 Received: from unknown(192.26.173.32) by ns.philips.nl via smap (V1.3+ESMTP) with ESMTP id sma026130; Mon Sep 16 09:11:01 1996 Received: from spooky.lss.cp.philips.com (spooky.lss.cp.philips.com [130.144.199.105]) by smtp.nl.cis.philips.com (8.6.10/8.6.10-0.9z-02May95) with ESMTP id JAA26983; Mon, 16 Sep 1996 09:13:56 +0200 Received: (from guido@localhost) by spooky.lss.cp.philips.com (8.6.10/8.6.10-0.991c-08Nov95) id JAA26316; Mon, 16 Sep 1996 09:10:58 +0200 From: Guido van Rooij Message-Id: <199609160710.JAA26316@spooky.lss.cp.philips.com> Subject: Re: vx device broken in 21.1.5? To: ache@nagual.ru (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=) Date: Mon, 16 Sep 1996 09:10:58 +0200 (MET DST) Cc: pb@hsc.fr, Guido.vanRooij@nl.cis.philips.com, freebsd-hackers@freebsd.org Reply-To: Guido.vanRooij@nl.cis.philips.com In-Reply-To: <199609131927.XAA00410@nagual.ru> from "[______ ______]" at "Sep 13, 96 11:27:46 pm" 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 [______ ______] wrote: > > According to Guido van Rooij: > > > I just ported the current Open/NetBSD if_vx driver to FreeBSD 2.1.5 and > > > I am seeeing the exact same problems. > > > > > > I've ben assured that these drivers do work. > > > > I can say that I've experienced similar problems with > > the 2.1.5 vx driver in an installation just a few days ago. > > > > Some of the 3C595 series might be buggy: the vx driver (sometimes > > but not always) prints a "early defective adapter" at boot time. > > In addition to that, the reseller of the card told us that it was to > > be discontinued and replaced with the 3C905... That's all the information > > I have. > > > > We replaced it with a 3C509 and lived happily ever after. > > I have 3C509 and > 1) Have "early defective..." diagnostic too > 2) Hangs on output, ifconfig down/up heals it. > I have a fix now. But it seems at least somethig is broken on my card. Tell me where to put my version of the driver. (which might be buggy though). -Guido From owner-freebsd-hackers Mon Sep 16 00:36:56 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA18496 for hackers-outgoing; Mon, 16 Sep 1996 00:36:56 -0700 (PDT) Received: from relay.philips.nl (ns.philips.nl [130.144.65.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA18490 for ; Mon, 16 Sep 1996 00:36:52 -0700 (PDT) Received: (from smap@localhost) by relay.philips.nl (8.6.9/8.6.9-950414) id JAA29643 for ; Mon, 16 Sep 1996 09:36:19 +0200 Received: from unknown(192.26.173.32) by ns.philips.nl via smap (V1.3+ESMTP) with ESMTP id sma029416; Mon Sep 16 09:35:07 1996 Received: from aonc01.nym.sc.philips.com (aonc01.nym.sc.philips.com [130.144.70.193]) by smtp.nl.cis.philips.com (8.6.10/8.6.10-0.9z-02May95) with ESMTP id JAA00188 for ; Mon, 16 Sep 1996 09:37:58 +0200 Received: from NLNMG01.nym.sc.philips.com (nlnmg01 [130.144.80.6]) by aonc01.nym.sc.philips.com (8.6.10/8.6.10-1.2a-960822) with ESMTP id JAA13987 for ; Mon, 16 Sep 1996 09:35:25 +0200 Received: from NLNMG01/MAILQUEUE by NLNMG01.nym.sc.philips.com (Mercury 1.21); 16 Sep 96 09:35:30 +0100 Received: from MAILQUEUE by NLNMG01 (Mercury 1.21); 16 Sep 96 09:35:23 +0100 From: "Kees Jan Koster" Organization: Philips Semiconductors Nijmegen To: hackers@freebsd.org Date: Mon, 16 Sep 1996 09:35:18 GMT+0100 Subject: 2.1.5 installed, no problem at all! Reply-to: Kees.Koster@nym.sc.philips.com Priority: normal X-mailer: Pegasus Mail for Windows (v2.23) Message-ID: <2421E883DD0@NLNMG01.nym.sc.philips.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hoi Hackers, I just received the 2.1.5-RELEASE cdrom and installed it. Once again, barely 20 minutes install time, including reading the readme's. Great job, thanks. Nice to have xx-a4.tgz and xx-letter.tgz packages. Very useful. Groetjes, Kees Jan From owner-freebsd-hackers Mon Sep 16 02:54:18 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA24394 for hackers-outgoing; Mon, 16 Sep 1996 02:54:18 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA24388 for ; Mon, 16 Sep 1996 02:54:15 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id CAA20505; Mon, 16 Sep 1996 02:50:27 -0700 (PDT) To: Darryl Okahata cc: hackers@freefall.freebsd.org Subject: Re: fdisk changes, anyone? In-reply-to: Your message of "Mon, 16 Sep 1996 00:12:43 PDT." <199609160712.AA113897963@hpnmhjw.sr.hp.com> Date: Mon, 16 Sep 1996 02:50:26 -0700 Message-ID: <20503.842867426@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I've just mangled fdisk such that partitioning information can now > be specified via an optional config file. I've been needing a way to > partition a disk from a script (without using expect), and so I mangled > fdisk to do just that. I want to write a perl script for adding SCSI > disks, and a programmatic fdisk was the only piece missing. An example > config file is: Wouldn't it be more flexible to add this as command-line parsing for fdisk? I like the idea, but making it use a config file means that anything driving fdisk programmatically needs to use a temp file, rather than simply forming a complex fdisk commmand and passing it to system(). Jordan From owner-freebsd-hackers Mon Sep 16 03:51:13 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA27056 for hackers-outgoing; Mon, 16 Sep 1996 03:51:13 -0700 (PDT) Received: from iaehv.IAEhv.nl (root@iaehv.IAEhv.nl [194.151.64.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA27045 for ; Mon, 16 Sep 1996 03:51:07 -0700 (PDT) Received: from LOCAL (wjw@localhost) by iaehv.IAEhv.nl (8.6.13/1.63); pid 11794 on Mon, 16 Sep 1996 12:51:01 +0200; id MAA11794 efrom: wjw; eto: hackers@freebsd.org From: wjw@IAEhv.nl (Willem Jan Withagen) Message-Id: <199609161051.MAA11794@iaehv.IAEhv.nl> Subject: Adding a second NCR 810 controller To: hackers@freebsd.org Date: Mon, 16 Sep 1996 12:51:01 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, What do I need to do to add a second NCR 810 controller to a 2.1.5 system? How do I work the BIOS? How do I work FreeBSD, or does it auto-create ncr1. --WjW -- Internet Access Eindhoven BV., voice: +31-40-2438330, data: +31-40-2439436 P.O. 928, 5600 AX Eindhoven, The Netherlands Full Internet connectivity for only fl 12.95 a month. Call now, and login as 'new'. From owner-freebsd-hackers Mon Sep 16 04:03:10 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA27518 for hackers-outgoing; Mon, 16 Sep 1996 04:03:10 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA27512 for ; Mon, 16 Sep 1996 04:03:08 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id EAA03263 for ; Mon, 16 Sep 1996 04:03:06 -0700 (PDT) To: hackers@freebsd.org Subject: We need resources like these for our own libraries.. Date: Mon, 16 Sep 1996 04:03:05 -0700 Message-ID: <3260.842871785@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Network Programmer's Guide http://sawyer.wustl.edu/du4-docs/AA-PS2WD-TET1_html/netprog1.html The GNU C Library http://cse.unl.edu/cgi-bin/ssis/~ebiederm/info/libc_toc.html The GNU C library page in particular is very well done. Jordan From owner-freebsd-hackers Mon Sep 16 05:20:40 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA00722 for hackers-outgoing; Mon, 16 Sep 1996 05:20:40 -0700 (PDT) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA00716 for ; Mon, 16 Sep 1996 05:20:38 -0700 (PDT) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id IAA26145; Mon, 16 Sep 1996 08:18:15 -0400 Date: Mon, 16 Sep 1996 08:18:15 -0400 (EDT) From: "Ron G. Minnich" X-Sender: rminnich@terra To: "Litvin Alexander B." cc: hackers@FreeBSD.org Subject: Re: ATM/FreeBSD advise needed! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk both openbsd and netbsd have chuck cranor's very nice atm layer and Efficient networks drivers built in, last time i checked. You can get patches to make it work under freebsd. It ought to be built in to freebsd too, IMHO. check out chuck's home page at wustl.edu for more info. ron Ron Minnich |"If you leave out all the killings, D.C. has as rminnich@sarnoff.com | low a crime rate as many cities" -- (609)-734-3120 | D.C. Mayor Marion Barry ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html From owner-freebsd-hackers Mon Sep 16 06:01:07 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA02449 for hackers-outgoing; Mon, 16 Sep 1996 06:01:07 -0700 (PDT) Received: from lassie.eunet.fi (lassie.eunet.fi [192.26.119.7]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA02439; Mon, 16 Sep 1996 06:01:00 -0700 (PDT) Received: from key.hole.fi by lassie.eunet.fi with SMTP id AA28929 (5.67a/IDA-1.5); Mon, 16 Sep 1996 16:01:07 +0300 Received: (from count@localhost) by key.hole.fi (8.7.5/8.6.12) id QAA01383; Mon, 16 Sep 1996 16:00:51 +0300 (EET DST) From: "Bror 'Count' Heinola" Message-Id: <199609161300.QAA01383@key.hole.fi> Subject: Re: ATM/FreeBSD advise needed! In-Reply-To: from "Ron G. Minnich" at "Sep 16, 96 08:18:15 am" To: rminnich@Sarnoff.COM (Ron G. Minnich) Date: Mon, 16 Sep 1996 16:00:51 +0300 (EET DST) Cc: freebsd-hackers@freebsd.org, freebsd-atm@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 Ron G. Minnich taisi sanoa: > both openbsd and netbsd have chuck cranor's very nice atm layer and > Efficient networks drivers built in, last time i checked. You can get > patches to make it work under freebsd. It ought to be built in to freebsd > too, IMHO. ...and if someone does the actual integration to -current, I'm willing to help to test it, since I have access to both cards and ATM LAN. -- Bror 'Count' Heinola % count@key.hole.fi % http://pobox.com/~count/ Isokaari 27 A 2 % IRC: Count NIC: BH271 % FI-00200 HELSINKI % Work: bror@sms.fi % Roads? Where we're going, Cell: +358-40-5533-554 % Santa Monica Software % we don't need roads. From owner-freebsd-hackers Mon Sep 16 06:32:19 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA03734 for hackers-outgoing; Mon, 16 Sep 1996 06:32:19 -0700 (PDT) Received: from zwei.siemens.at (zwei.siemens.at [193.81.246.12]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA03700 for ; Mon, 16 Sep 1996 06:31:58 -0700 (PDT) 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 PAA24739 for ; Mon, 16 Sep 1996 15:30:29 +0200 (MET DST) Received: from ws2301.gud.siemens.co.at by sol1.gud.siemens.co.at with smtp (Smail3.1.28.1 #7 for ) id m0v2dlR-000218C; Mon, 16 Sep 96 15:31 MET DST Received: by ws2301.gud.siemens.co.at (1.37.109.16/1.37) id AA154420380; Mon, 16 Sep 1996 15:26:20 +0200 From: "Hr.Ladavac" Message-Id: <199609161326.AA154420380@ws2301.gud.siemens.co.at> Subject: Re: 2.1.5 installed, no problem at all! To: Kees.Koster@nym.sc.philips.com Date: Mon, 16 Sep 1996 15:26:20 +0200 (MESZ) Cc: hackers@freebsd.org In-Reply-To: <2421E883DD0@NLNMG01.nym.sc.philips.com> from "Kees Jan Koster" at Sep 16, 96 09:35:18 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 Kees Jan Koster contained: > > Hoi Hackers, > > I just received the 2.1.5-RELEASE cdrom and installed it. > Once again, barely 20 minutes install time, including reading > the readme's. Great job, thanks. Interesting... This is not a common error message on this list. Can you elaborate your setup a little--perhaps we can help. > > Nice to have xx-a4.tgz and xx-letter.tgz packages. Very useful. Folks, he actually managed to install the thing. We need some bugs, fast. /Marino P.S. :) for humor impaired. > > Groetjes, > Kees Jan > From owner-freebsd-hackers Mon Sep 16 06:50:05 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA04694 for hackers-outgoing; Mon, 16 Sep 1996 06:50:05 -0700 (PDT) Received: from relay.philips.nl (ns.philips.nl [130.144.65.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA04652 for ; Mon, 16 Sep 1996 06:49:56 -0700 (PDT) Received: (from smap@localhost) by relay.philips.nl (8.6.9/8.6.9-950414) id PAA26656 for ; Mon, 16 Sep 1996 15:49:16 +0200 Received: from unknown(192.26.173.32) by ns.philips.nl via smap (V1.3+ESMTP) with ESMTP id sma025622; Mon Sep 16 15:42:54 1996 Received: from aonc01.nym.sc.philips.com (aonc01.nym.sc.philips.com [130.144.70.193]) by smtp.nl.cis.philips.com (8.6.10/8.6.10-0.9z-02May95) with ESMTP id PAA16732 for ; Mon, 16 Sep 1996 15:45:45 +0200 Received: from NLNMG01.nym.sc.philips.com (nlnmg01 [130.144.80.6]) by aonc01.nym.sc.philips.com (8.6.10/8.6.10-1.2a-960822) with ESMTP id PAA22753 for ; Mon, 16 Sep 1996 15:43:14 +0200 Received: from NLNMG01/MAILQUEUE by NLNMG01.nym.sc.philips.com (Mercury 1.21); 16 Sep 96 15:43:17 +0100 Received: from MAILQUEUE by NLNMG01 (Mercury 1.21); 16 Sep 96 15:42:51 +0100 From: "Kees Jan Koster" Organization: Philips Semiconductors Nijmegen To: hackers@freebsd.org Date: Mon, 16 Sep 1996 15:42:42 GMT+0100 Subject: Re: 2.1.5 installed, no problem at all! Reply-to: Kees.Koster@nym.sc.philips.com Priority: normal X-mailer: Pegasus Mail for Windows (v2.23) Message-ID: <2483ED94D5D@NLNMG01.nym.sc.philips.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > I just received the 2.1.5-RELEASE cdrom and installed it. > > Once again, barely 20 minutes install time, including reading > > the readme's. Great job, thanks. > > Interesting... This is not a common error message on this list. > Can you elaborate your setup a little--perhaps we can help. > Surel, I've got an ATAPI cdrom (Identified by both the bios and FreeBSD as an "iPnoee r"). So the ATAPI stuff _does_ work for some drives. And I've got an AMD 5k86-P100, so those seem to FreeBSD compatible too (could someone mail them the little stickers to put on each of their cpu's?) From owner-freebsd-hackers Mon Sep 16 07:38:12 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA07561 for hackers-outgoing; Mon, 16 Sep 1996 07:38:12 -0700 (PDT) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA07551 for ; Mon, 16 Sep 1996 07:38:08 -0700 (PDT) Received: from ppp-089.etinc.com (ppp-089.etinc.com [204.141.95.148]) by etinc.com (8.6.12/8.6.9) with SMTP id KAA16111; Mon, 16 Sep 1996 10:44:34 -0400 Date: Mon, 16 Sep 1996 10:44:34 -0400 Message-Id: <199609161444.KAA16111@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Kurt Schafer From: dennis@etinc.com (Dennis) Subject: Re: Could use a favor Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I've been having problems getting some 2.1.5-RELEASE systems outputting data >to the net. I've since brought up a machine on 2.1-RELEASE and put a >plain-jane default apache process on the box. > >If people could try resolving http://wave.cyberbeach.net and drop me a >message outlining their success/failure I would be appreciative. Perhaps unrelated....but I've noticed if I configure IP firewalling into the kernel the default seems to be that the system cant do anything. Can anyone outline why that is.... Dennis From owner-freebsd-hackers Mon Sep 16 07:53:43 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA09475 for hackers-outgoing; Mon, 16 Sep 1996 07:53:43 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.252]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA09458; Mon, 16 Sep 1996 07:53:37 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id QAA16046; Mon, 16 Sep 1996 16:53:03 +0200 (MET DST) To: dennis@etinc.com (Dennis) cc: Kurt Schafer , hackers@freebsd.org Subject: Re: Could use a favor In-reply-to: Your message of "Mon, 16 Sep 1996 10:44:34 EDT." <199609161444.KAA16111@etinc.com> Date: Mon, 16 Sep 1996 16:53:03 +0200 Message-ID: <16044.842885583@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199609161444.KAA16111@etinc.com>, Dennis writes: >>I've been having problems getting some 2.1.5-RELEASE systems outputting data >>to the net. I've since brought up a machine on 2.1-RELEASE and put a >>plain-jane default apache process on the box. >> >>If people could try resolving http://wave.cyberbeach.net and drop me a >>message outlining their success/failure I would be appreciative. > >Perhaps unrelated....but I've noticed if I configure IP firewalling into the >kernel >the default seems to be that the system cant do anything. Can anyone outline >why that is.... See the mail-archives for a long discussion on this. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-hackers Mon Sep 16 08:23:22 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA10637 for hackers-outgoing; Mon, 16 Sep 1996 08:23:22 -0700 (PDT) Received: from al.imforei.apana.org.au (pjchilds@al.imforei.apana.org.au [202.12.89.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA10629 for ; Mon, 16 Sep 1996 08:23:07 -0700 (PDT) Received: (from pjchilds@localhost) by al.imforei.apana.org.au (8.7.5/8.7.3) id AAA15503; Tue, 17 Sep 1996 00:52:52 GMT Date: Tue, 17 Sep 1996 00:52:52 GMT From: Peter Childs Message-Id: <199609170052.AAA15503@al.imforei.apana.org.au> To: wjw@IAEhv.nl, freebsd-hackers@freebsd.org Subject: Re: Adding a second NCR 810 controller X-Newsreader: TIN [version 1.2 PL2] Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199609161051.MAA11794@iaehv.IAEhv.nl> you wrote: : Hi, Gday! : What do I need to do to add a second NCR 810 controller to a 2.1.5 system? Just chuck it in. Both cards can be set to INT A, since the interupts are unique for each PCI slot. : How do I work the BIOS? You can only boot off one controller, and the BIOS seems to take the first here. : How do I work FreeBSD, or does it auto-create ncr1. Sure does.. all just works great. If you have a motherboard with a SiS chipset (like the ASUS SP3) you might wanna disable the PCI burst mode options otherwise you may have problems. Another thing with the ASUS motherboards is to set the PCI latency to 32. Heres a extract from my boot messages... Probing for devices on PCI bus 0: chip0 rev 49 on pci0:5 vga0 rev 1 int a irq 9 on pci0:10 ncr0 rev 17 int a irq 12 on pci0:11 ncr0 waiting for scsi devices to settle (ncr0:1:0): "QUANTUM FIREBALL1080S 1Q09" type 0 fixed SCSI 2 sd0(ncr0:1:0): Direct-Access sd0(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 1042MB (2134305 512 byte sectors) (ncr0:5:0): "MICROP 1684-07MB1057403 HSP4" type 0 fixed SCSI 1 sd1(ncr0:5:0): Direct-Access 323MB (663476 512 byte sectors) ncr1 rev 1 int a irq 11 on pci0:12 ncr1 waiting for scsi devices to settle (ncr1:3:0): "SEAGATE ST51080N 0943" type 0 fixed SCSI 2 sd2(ncr1:3:0): Direct-Access sd2(ncr1:3:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 1030MB (2109840 512 byte sectors) (ncr1:6:0): "FUJITSU M2512A 1507" type 7 removable SCSI 2 od0(ncr1:6:0): Optical od0(ncr1:6:0): 200ns (5 Mb/sec) offset 8. 217MB (446325 512 byte sectors) Peter -- Peter Childs --- http://www.imforei.apana.org.au/~pjchilds Finger pjchilds@al.imforei.apana.org.au for public PGP key Drag me, drop me, treat me like an object! From owner-freebsd-hackers Mon Sep 16 08:36:28 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA11342 for hackers-outgoing; Mon, 16 Sep 1996 08:36:28 -0700 (PDT) Received: from rock.anchorage.net (guest@rock.anchorage.net [204.17.241.163]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA11334; Mon, 16 Sep 1996 08:36:22 -0700 (PDT) Received: from jabpc.rtfm.com (jabpc.rtfm.com [199.237.0.200]) by rock.anchorage.net (8.6.12/8.6.9) with SMTP id HAA03810; Mon, 16 Sep 1996 07:31:35 -0300 Received: by jabpc.rtfm.com with Microsoft Mail id <01BBA3A2.11B93340@jabpc.rtfm.com>; Mon, 16 Sep 1996 07:38:36 -0800 Message-ID: <01BBA3A2.11B93340@jabpc.rtfm.com> From: Jeffrey Barber To: "'freebsd-hardware@FreeBSD.org'" , "'hackers@FreeBSD.ORG'" Subject: Very Slow Ethernet Link Date: Mon, 16 Sep 1996 07:38:33 -0800 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 just installed FreeBSD 2.1 and boy this is slow, Example: bash$ ping localhost PING localhost (127.0.0.1): 56 data bytes 64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.356 ms 64 bytes from 127.0.0.1: icmp_seq=1 ttl=255 time=0.342 ms 64 bytes from 127.0.0.1: icmp_seq=2 ttl=255 time=0.362 ms 64 bytes from 127.0.0.1: icmp_seq=3 ttl=255 time=0.349 ms --- localhost.arctic.net ping statistics --- 6 packets transmitted, 6 packets received, 0% packet loss round-trip min/avg/max = 0.342/0.349/0.362 ms bash$ ifconfig -a lp0: flags=8810 mtu 1500 ep0: flags=863 mtu 1500 inet 19.51.13.1 netmask 0xffffff00 broadcast 19.51.13.255 lo0: flags=8009 mtu 16384 inet 127.0.0.1 netmask 0xff000000 sl0: flags=c010 mtu 552 tun0: flags=8010 mtu 1500 On my Linux box I get a ping response of: PING localhost (127.0.0.1): 56 data bytes 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=1.1 ms 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.9 ms 64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.9 ms 64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=1.0 ms Big difference here. Please shed some light on this for me. TIA From owner-freebsd-hackers Mon Sep 16 08:53:45 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA12211 for hackers-outgoing; Mon, 16 Sep 1996 08:53:45 -0700 (PDT) Received: from silver.sms.fi (root@silver.sms.fi [194.111.122.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA12192; Mon, 16 Sep 1996 08:53:35 -0700 (PDT) Received: (from pete@localhost) by silver.sms.fi (8.7.5/8.6.9) id SAA12091; Mon, 16 Sep 1996 18:50:53 +0300 (EET DST) Date: Mon, 16 Sep 1996 18:50:53 +0300 (EET DST) Message-Id: <199609161550.SAA12091@silver.sms.fi> From: Petri Helenius To: Jeffrey Barber Cc: "'freebsd-hardware@FreeBSD.org'" , "'hackers@FreeBSD.ORG'" Subject: Very Slow Ethernet Link In-Reply-To: <01BBA3A2.11B93340@jabpc.rtfm.com> References: <01BBA3A2.11B93340@jabpc.rtfm.com> Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Excuse me, but last time I checked, 0.350 milliseconds is much less than a millisecond? So your LinSux is three times slower to respond to a ping to loopback address. (which is to be expected from the 'design' of the network code) Pete Jeffrey Barber writes: > Ok, I just installed FreeBSD 2.1 and boy this is slow, Example: > > bash$ ping localhost > > PING localhost (127.0.0.1): 56 data bytes > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.356 ms > 64 bytes from 127.0.0.1: icmp_seq=1 ttl=255 time=0.342 ms > 64 bytes from 127.0.0.1: icmp_seq=2 ttl=255 time=0.362 ms > 64 bytes from 127.0.0.1: icmp_seq=3 ttl=255 time=0.349 ms > > --- localhost.arctic.net ping statistics --- > 6 packets transmitted, 6 packets received, 0% packet loss > round-trip min/avg/max = 0.342/0.349/0.362 ms > > bash$ ifconfig -a > > lp0: flags=8810 mtu 1500 > ep0: flags=863 mtu 1500 > inet 19.51.13.1 netmask 0xffffff00 broadcast 19.51.13.255 > lo0: flags=8009 mtu 16384 > inet 127.0.0.1 netmask 0xff000000 > sl0: flags=c010 mtu 552 > tun0: flags=8010 mtu 1500 > > > On my Linux box I get a ping response of: > > PING localhost (127.0.0.1): 56 data bytes > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=1.1 ms > 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.9 ms > 64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.9 ms > 64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=1.0 ms > > Big difference here. Please shed some light on this for me. > > TIA > From owner-freebsd-hackers Mon Sep 16 08:56:40 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA12401 for hackers-outgoing; Mon, 16 Sep 1996 08:56:40 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA12366; Mon, 16 Sep 1996 08:56:28 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA02862; Mon, 16 Sep 1996 09:54:47 -0600 (MDT) Date: Mon, 16 Sep 1996 09:54:47 -0600 (MDT) Message-Id: <199609161554.JAA02862@rocky.mt.sri.com> From: Nate Williams To: Jeffrey Barber Cc: "'freebsd-hardware@FreeBSD.org'" , "'hackers@FreeBSD.ORG'" Subject: Re: Very Slow Ethernet Link In-Reply-To: <01BBA3A2.11B93340@jabpc.rtfm.com> References: <01BBA3A2.11B93340@jabpc.rtfm.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jeffrey Barber writes: > Ok, I just installed FreeBSD 2.1 and boy this is slow, Example: > > bash$ ping localhost > > PING localhost (127.0.0.1): 56 data bytes > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.356 ms vs. > On my Linux box I get a ping response of: > > PING localhost (127.0.0.1): 56 data bytes > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=1.1 ms Hmm, it looks like the Linux box is about 3X slower than FreeBSD. I'm not sure, but in my math class .1 ms is faster than 1ms. Nate From owner-freebsd-hackers Mon Sep 16 09:00:23 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA12618 for hackers-outgoing; Mon, 16 Sep 1996 09:00:23 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA12605; Mon, 16 Sep 1996 09:00:19 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id LAA01123; Mon, 16 Sep 1996 11:00:01 -0500 (EST) From: John Dyson Message-Id: <199609161600.LAA01123@dyson.iquest.net> Subject: Re: Very Slow Ethernet Link To: jab@rock.anchorage.net (Jeffrey Barber) Date: Mon, 16 Sep 1996 11:00:01 -0500 (EST) Cc: freebsd-hardware@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: <01BBA3A2.11B93340@jabpc.rtfm.com> from "Jeffrey Barber" at Sep 16, 96 07:38:33 am Reply-To: dyson@FreeBSD.org 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 > Ok, I just installed FreeBSD 2.1 and boy this is slow, Example: > > bash$ ping localhost > FreeBSD number: > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.356 ms Linux number: > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=1.1 ms Looks like Linux is slower to me... John From owner-freebsd-hackers Mon Sep 16 09:11:15 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA13221 for hackers-outgoing; Mon, 16 Sep 1996 09:11:15 -0700 (PDT) Received: from fullfeed.msn.fullfeed.com (fullfeed.msn.fullfeed.com [199.184.182.42]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA13199; Mon, 16 Sep 1996 09:11:06 -0700 (PDT) Received: from sumatra.americantv.com by fullfeed.msn.fullfeed.com (8.6.9/FF-1.1) id LAA26698; Mon, 16 Sep 1996 11:10:43 -0500 Received: (from uucp@localhost) by sumatra.americantv.com (8.6.12/8.6.12) with UUCP id KAA07019; Mon, 16 Sep 1996 10:38:28 -0500 Received: (jlemon@localhost) by right.PCS (8.6.13/8.6.4) id QAA12775; Mon, 16 Sep 1996 16:07:58 GMT From: Jonathan Lemon Message-Id: <199609161607.QAA12775@right.PCS> Subject: Re: Very Slow Ethernet Link To: jab@rock.anchorage.net (Jeffrey Barber) Date: Mon, 16 Sep 1996 11:07:57 -0500 (CDT) Cc: freebsd-hardware@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: <01BBA3A2.11B93340@jabpc.rtfm.com> from "Jeffrey Barber" at Sep 16, 96 07:38:33 am X-Mailer: ELM [version 2.4 PL21] Content-Type: text Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Ok, I just installed FreeBSD 2.1 and boy this is slow, Example: > 64 bytes from 127.0.0.1: icmp_seq=1 ttl=255 time=0.342 ms > On my Linux box I get a ping response of: > 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.9 ms Umm, 0.342ms < 0.9ms, isn't it? If your question is "why is Linux ~3x slower", then that question might be better asked on a linux mailing list. This assumes similar hardware. Note that different hardware also affects the ping rate: 386/20 w/4MB running 2.2-960612-SNAP: 64 bytes from 127.0.0.1: icmp_seq=4 ttl=255 time=6.563 ms 586/133 w/32M running 2.1.0-RELEASE: 64 bytes from 127.0.0.1: icmp_seq=4 ttl=255 time=0.158 ms -- Jonathan From owner-freebsd-hackers Mon Sep 16 09:11:50 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA13256 for hackers-outgoing; Mon, 16 Sep 1996 09:11:50 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA13032 for ; Mon, 16 Sep 1996 09:08:33 -0700 (PDT) Received: (from narvi@localhost) by haldjas.folklore.ee (8.7.5/8.6.12) id TAA18165; Mon, 16 Sep 1996 19:03:01 +0300 (EET DST) Date: Mon, 16 Sep 1996 19:03:00 +0300 (EET DST) From: Narvi To: Dennis cc: Kurt Schafer , hackers@FreeBSD.org Subject: Re: Could use a favor In-Reply-To: <199609161444.KAA16111@etinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 16 Sep 1996, Dennis wrote: > >I've been having problems getting some 2.1.5-RELEASE systems outputting data > >to the net. I've since brought up a machine on 2.1-RELEASE and put a > >plain-jane default apache process on the box. > > > >If people could try resolving http://wave.cyberbeach.net and drop me a > >message outlining their success/failure I would be appreciative. > > Perhaps unrelated....but I've noticed if I configure IP firewalling into the > kernel > the default seems to be that the system cant do anything. Can anyone outline > why that is.... The only conclusion I have come at is that it is to allow only things that you especially allow to happen... The bad thing is that there is no switch to switch the firewall on/off. You compile a new kernel with the option for firewall and suddenly it accepts nothing over the network. Sander > > Dennis > > From owner-freebsd-hackers Mon Sep 16 09:11:57 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA13285 for hackers-outgoing; Mon, 16 Sep 1996 09:11:57 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA13251 for ; Mon, 16 Sep 1996 09:11:39 -0700 (PDT) Received: (from narvi@localhost) by haldjas.folklore.ee (8.7.5/8.6.12) id TAA18217; Mon, 16 Sep 1996 19:09:49 +0300 (EET DST) Date: Mon, 16 Sep 1996 19:09:49 +0300 (EET DST) From: Narvi To: Jeffrey Barber cc: "'hackers@FreeBSD.ORG'" Subject: Re: Very Slow Ethernet Link In-Reply-To: <01BBA3A2.11B93340@jabpc.rtfm.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk -hardware removed from the cc: list On Mon, 16 Sep 1996, Jeffrey Barber wrote: > Ok, I just installed FreeBSD 2.1 and boy this is slow, Example: Hmm... 2.1 is not te latest release - 2.1.5 is out some time already. > > bash$ ping localhost > > PING localhost (127.0.0.1): 56 data bytes > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.356 ms > 64 bytes from 127.0.0.1: icmp_seq=1 ttl=255 time=0.342 ms > 64 bytes from 127.0.0.1: icmp_seq=2 ttl=255 time=0.362 ms > 64 bytes from 127.0.0.1: icmp_seq=3 ttl=255 time=0.349 ms > Slow? I wouldn't call it too slow. > --- localhost.arctic.net ping statistics --- > 6 packets transmitted, 6 packets received, 0% packet loss > round-trip min/avg/max = 0.342/0.349/0.362 ms > > bash$ ifconfig -a > > lp0: flags=8810 mtu 1500 > ep0: flags=863 mtu 1500 > inet 19.51.13.1 netmask 0xffffff00 broadcast 19.51.13.255 > lo0: flags=8009 mtu 16384 > inet 127.0.0.1 netmask 0xff000000 > sl0: flags=c010 mtu 552 > tun0: flags=8010 mtu 1500 > > > On my Linux box I get a ping response of: > > PING localhost (127.0.0.1): 56 data bytes > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=1.1 ms > 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.9 ms > 64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.9 ms > 64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=1.0 ms > > Big difference here. Please shed some light on this for me. Sure. The linux box is around 3 times slower (3x0.3=0.9). And yes, this I would surely call slow. Were the test made on the same machine? What was the version of Linux? Sander > > TIA > > From owner-freebsd-hackers Mon Sep 16 09:12:54 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA13394 for hackers-outgoing; Mon, 16 Sep 1996 09:12:54 -0700 (PDT) Received: from gatekeeper.fsl.noaa.gov (gatekeeper.fsl.noaa.gov [137.75.131.181]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA13387; Mon, 16 Sep 1996 09:12:50 -0700 (PDT) Received: from emu.fsl.noaa.gov (kelly@emu.fsl.noaa.gov [137.75.60.32]) by gatekeeper.fsl.noaa.gov (8.7.5/8.7.3) with ESMTP id QAA20759; Mon, 16 Sep 1996 16:12:49 GMT Message-Id: <199609161612.QAA20759@gatekeeper.fsl.noaa.gov> Received: by emu.fsl.noaa.gov (1.40.112.4/16.2) id AA284420392; Mon, 16 Sep 1996 10:13:12 -0600 Date: Mon, 16 Sep 1996 10:13:12 -0600 From: Sean Kelly To: jab@rock.anchorage.net Cc: freebsd-hardware@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: <01BBA3A2.11B93340@jabpc.rtfm.com> (message from Jeffrey Barber on Mon, 16 Sep 1996 07:38:33 -0800) Subject: Re: Very Slow Ethernet Link Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >>>>> Jeffrey Barber writes: > Ok, I just installed FreeBSD 2.1 and boy this is slow, Example: > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.356 ms > On my Linux box I get a ping response of: > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=1.1 > Big difference here. Please shed some light on this for me. Yes, there is a big difference: 0.356 ms < 1.1 ms, so your FreeBSD host is faster when ping'ing localhost. Are you saying even though it's faster than Linux, it's still too slow? -- Sean Kelly NOAA Forecast Systems Laboratory kelly@fsl.noaa.gov Boulder Colorado USA http://www-sdd.fsl.noaa.gov/~kelly/ From owner-freebsd-hackers Mon Sep 16 09:19:43 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA14058 for hackers-outgoing; Mon, 16 Sep 1996 09:19:43 -0700 (PDT) Received: from home.winc.com (root@home.winc.com [204.178.182.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA14046; Mon, 16 Sep 1996 09:19:37 -0700 (PDT) Received: from phoenix.aristar.com (slip125.winc.com [204.178.182.125]) by home.winc.com (8.7.1/8.7.3) with SMTP id MAA21070; Mon, 16 Sep 1996 12:18:51 -0400 Message-ID: <323D7E23.31DFF4F5@aristar.com> Date: Mon, 16 Sep 1996 12:19:47 -0400 From: "Matthew A. Gessner" Organization: Aristar, Inc. X-Mailer: Mozilla 3.0b8Gold (X11; I; FreeBSD 2.1.0-RELEASE i386) MIME-Version: 1.0 To: Nate Williams CC: Jeffrey Barber , "'freebsd-hardware@FreeBSD.org'" , "'hackers@FreeBSD.ORG'" Subject: Enough (was Re: Very Slow Ethernet Link) References: <01BBA3A2.11B93340@jabpc.rtfm.com> <199609161554.JAA02862@rocky.mt.sri.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Nate Williams wrote: > > Jeffrey Barber writes: > > Ok, I just installed FreeBSD 2.1 and boy this is slow, Example: > > > > bash$ ping localhost > > > > PING localhost (127.0.0.1): 56 data bytes > > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.356 ms > > vs. > > > On my Linux box I get a ping response of: > > > > PING localhost (127.0.0.1): 56 data bytes > > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=1.1 ms > > Hmm, it looks like the Linux box is about 3X slower than FreeBSD. I'm > not sure, but in my math class .1 ms is faster than 1ms. > > Nate Hey, all, by this time, he probably got the hint. -- Matthew Gessner, Computer Scientist, Aristar, Inc. 302 N. Cleveland-Massillon Rd. Akron, OH 44333 Voice (330) 668-2267, Fax (330) 668-2961 From owner-freebsd-hackers Mon Sep 16 09:26:40 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA14505 for hackers-outgoing; Mon, 16 Sep 1996 09:26:40 -0700 (PDT) Received: from zwei.siemens.at (zwei.siemens.at [193.81.246.12]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA14499; Mon, 16 Sep 1996 09:26:36 -0700 (PDT) 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 SAA28112; Mon, 16 Sep 1996 18:25:30 +0200 (MET DST) Received: from ws2301.gud.siemens.co.at by sol1.gud.siemens.co.at with smtp (Smail3.1.28.1 #7 for ) id m0v2gUl-000218C; Mon, 16 Sep 96 18:26 MET DST Received: by ws2301.gud.siemens.co.at (1.37.109.16/1.37) id AA232580878; Mon, 16 Sep 1996 18:21:18 +0200 From: "Hr.Ladavac" Message-Id: <199609161621.AA232580878@ws2301.gud.siemens.co.at> Subject: Re: Very Slow Ethernet Link To: jab@rock.anchorage.net (Jeffrey Barber) Date: Mon, 16 Sep 1996 18:21:18 +0200 (MESZ) Cc: freebsd-hardware@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: <01BBA3A2.11B93340@jabpc.rtfm.com> from "Jeffrey Barber" at Sep 16, 96 07:38: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 E-mail message from Jeffrey Barber contained: > Ok, I just installed FreeBSD 2.1 and boy this is slow, Example: > > bash$ ping localhost > > PING localhost (127.0.0.1): 56 data bytes > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.356 ms > 64 bytes from 127.0.0.1: icmp_seq=1 ttl=255 time=0.342 ms > 64 bytes from 127.0.0.1: icmp_seq=2 ttl=255 time=0.362 ms > 64 bytes from 127.0.0.1: icmp_seq=3 ttl=255 time=0.349 ms > > --- localhost.arctic.net ping statistics --- > 6 packets transmitted, 6 packets received, 0% packet loss > round-trip min/avg/max = 0.342/0.349/0.362 ms > > bash$ ifconfig -a > > lp0: flags=8810 mtu 1500 > ep0: flags=863 mtu 1500 > inet 19.51.13.1 netmask 0xffffff00 broadcast 19.51.13.255 > lo0: flags=8009 mtu 16384 > inet 127.0.0.1 netmask 0xff000000 > sl0: flags=c010 mtu 552 > tun0: flags=8010 mtu 1500 > > > On my Linux box I get a ping response of: > > PING localhost (127.0.0.1): 56 data bytes > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=1.1 ms > 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.9 ms > 64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.9 ms > 64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=1.0 ms > > Big difference here. Please shed some light on this for me. What would be your point, please? 1) Localhost doesn't even reach the wire; 2) localhost pings on freebsd seem to be 3 times faster than the linux ones (according to your data.) What did you want to ask? Perplexed minds wish to know. BTW, tcpblast on loopback device (localhost) is slow on 2.1 because of the slightly bogus mtu of 16K. Set it to something more reasonable like 1500 /Marino > > TIA > > From owner-freebsd-hackers Mon Sep 16 09:34:12 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA15006 for hackers-outgoing; Mon, 16 Sep 1996 09:34:12 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA14952; Mon, 16 Sep 1996 09:34:06 -0700 (PDT) Message-Id: <199609161634.JAA14952@freefall.freebsd.org> To: Jeffrey Barber cc: "'freebsd-hardware@FreeBSD.org'" , "'hackers@FreeBSD.ORG'" Subject: Re: Very Slow Ethernet Link In-reply-to: Your message of "Mon, 16 Sep 1996 07:38:33 -0800." <01BBA3A2.11B93340@jabpc.rtfm.com> Date: Mon, 16 Sep 1996 09:34:05 -0700 From: "Justin T. Gibbs" Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >Ok, I just installed FreeBSD 2.1 and boy this is slow, Example: > >bash$ ping localhost >64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.356 ms > >On my Linux box I get a ping response of: > >PING localhost (127.0.0.1): 56 data bytes >64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=1.1 ms > >Big difference here. Please shed some light on this for me. > >TIA Last I checked, .356ms was faster than 1.1ms. I think you missed the decimal point. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-hackers Mon Sep 16 09:35:41 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA15213 for hackers-outgoing; Mon, 16 Sep 1996 09:35:41 -0700 (PDT) Received: from gromit.pinpt.com (gromit.pinpt.com [205.179.195.7]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA15207 for ; Mon, 16 Sep 1996 09:35:40 -0700 (PDT) Received: from rover3.pinpt.com (gatemaster.pinpt.com [205.179.195.65]) by gromit.pinpt.com (8.7.5/8.6.12) with SMTP id JAA00327 for ; Mon, 16 Sep 1996 09:34:11 -0700 (PDT) Message-Id: <2.2.32.19960916163342.0091e7c8@wallace.pinpt.com> X-Sender: schluntz@wallace.pinpt.com X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 16 Sep 1996 09:33:42 -0700 To: hackers@freebsd.org From: "Sean J. Schluntz" Subject: Question on Porting Windows software to X Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am sending this to Hackers, 'cuz I figgured that you all would know the answer to this one. Looking at a larger word processing application for windows (16bit not 32) like Word 6, WordPerfict 6 or WordStar. What do would you all think the difficulty level and approximate time would be required to port this app to X if you had the full sources for the orriginal application. Following up, would there be any one out there with the interest to possibly make some royalties by working on such a project? Thanks for your time. -Sean --- Sean J. Schluntz eMail schluntz@pinpt.com Manager Support Services Phone (408) 997-6900 x222 PinPoint Software Corporation Fax (408) 323-2300 http://www.pinpt.com/ From owner-freebsd-hackers Mon Sep 16 09:39:58 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA15494 for hackers-outgoing; Mon, 16 Sep 1996 09:39:58 -0700 (PDT) Received: from fore.com (mailhub.fore.com [192.88.243.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA15475; Mon, 16 Sep 1996 09:39:47 -0700 (PDT) Received: from dolphin.fore.com ([192.88.243.27]) by fore.com (8.7.3/8.6.11) with ESMTP id MAA15894; Mon, 16 Sep 1996 12:35:30 -0400 (EDT) Received: from lamprey.fore.com (lamprey.fore.com [169.144.1.113]) by dolphin.fore.com (8.7.5/8.7.3) with SMTP id MAA27610; Mon, 16 Sep 1996 12:39:00 -0400 (EDT) Message-Id: <199609161639.MAA27610@dolphin.fore.com> To: Jeffrey Barber cc: "'freebsd-hardware@FreeBSD.org'" , "'hackers@FreeBSD.ORG'" Subject: Re: Very Slow Ethernet Link In-reply-to: Message from Jeffrey Barber of "Mon, 16 Sep 1996 07:38:33 -0800." <01BBA3A2.11B93340@jabpc.rtfm.com> Reply-to: rv@fore.com X-Mailer: MH v6.8.3 Date: Mon, 16 Sep 1996 12:38:57 -0400 From: Rajesh Vaidheeswarran Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk unless I don't understand, .356 ms << .9 ms (slightly more than a third) -- using MH template repl.format -- In a previous message, Jeffrey Barber writes: > Ok, I just installed FreeBSD 2.1 and boy this is slow, Example: > > bash$ ping localhost > > PING localhost (127.0.0.1): 56 data bytes > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.356 ms > 64 bytes from 127.0.0.1: icmp_seq=1 ttl=255 time=0.342 ms > 64 bytes from 127.0.0.1: icmp_seq=2 ttl=255 time=0.362 ms > 64 bytes from 127.0.0.1: icmp_seq=3 ttl=255 time=0.349 ms > > --- localhost.arctic.net ping statistics --- > 6 packets transmitted, 6 packets received, 0% packet loss > round-trip min/avg/max = 0.342/0.349/0.362 ms > > bash$ ifconfig -a > > lp0: flags=8810 mtu 1500 > ep0: flags=863 mtu 1500 > inet 19.51.13.1 netmask 0xffffff00 broadcast 19.51.13.255 > lo0: flags=8009 mtu 16384 > inet 127.0.0.1 netmask 0xff000000 > sl0: flags=c010 mtu 552 > tun0: flags=8010 mtu 1500 > > > On my Linux box I get a ping response of: > > PING localhost (127.0.0.1): 56 data bytes > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=1.1 ms > 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.9 ms > 64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.9 ms > 64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=1.0 ms > > Big difference here. Please shed some light on this for me. > > TIA > From owner-freebsd-hackers Mon Sep 16 09:42:40 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA15733 for hackers-outgoing; Mon, 16 Sep 1996 09:42:40 -0700 (PDT) Received: from www.hsc.wvu.edu (www.hsc.wvu.edu [157.182.105.122]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA15713; Mon, 16 Sep 1996 09:42:30 -0700 (PDT) Received: (from jsigmon@localhost) by www.hsc.wvu.edu (8.6.12/8.6.12) id MAA13035; Mon, 16 Sep 1996 12:44:30 -0400 Date: Mon, 16 Sep 1996 12:44:28 -0400 (EDT) From: Jeremy Sigmon To: Jeffrey Barber cc: "'freebsd-hardware@FreeBSD.org'" , "'hackers@FreeBSD.ORG'" Subject: Re: Very Slow Ethernet Link In-Reply-To: <01BBA3A2.11B93340@jabpc.rtfm.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Ok, I just installed FreeBSD 2.1 and boy this is slow, Example: > > PING localhost (127.0.0.1): 56 data bytes > 64 bytes from 127.0.0.1: icmp_seq=3 ttl=255 time=0.349 ms > > On my Linux box I get a ping response of: > > PING localhost (127.0.0.1): 56 data bytes > 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.9 ms > Isn't .349 << .9 ???? =) My FBSD box: PING at-ga1.hsc.wvu.edu (157.182.105.124): 56 data bytes 64 bytes from 157.182.105.124: icmp_seq=0 ttl=255 time=0.305 ms 64 bytes from 157.182.105.124: icmp_seq=1 ttl=255 time=0.177 ms 64 bytes from 157.182.105.124: icmp_seq=2 ttl=255 time=0.169 ms 64 bytes from 157.182.105.124: icmp_seq=3 ttl=255 time=0.165 ms 64 bytes from 157.182.105.124: icmp_seq=4 ttl=255 time=0.166 ms 64 bytes from 157.182.105.124: icmp_seq=5 ttl=255 time=0.167 ms 64 bytes from 157.182.105.124: icmp_seq=6 ttl=255 time=0.168 ms ====================================================================== Jeremy Sigmon B.S. ChE | Web Developer of the Robert C. Byrd Health | Use Sciences Center of West Virginia University | FreeBSD WWW.HSC.WVU.EDU | Now Graduate Student in Computer Science | Office : 293-1060 | From owner-freebsd-hackers Mon Sep 16 09:44:05 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA15833 for hackers-outgoing; Mon, 16 Sep 1996 09:44:05 -0700 (PDT) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA15821 for ; Mon, 16 Sep 1996 09:44:02 -0700 (PDT) Received: from ppp-089.etinc.com (ppp-089.etinc.com [204.141.95.148]) by etinc.com (8.6.12/8.6.9) with SMTP id MAA16892; Mon, 16 Sep 1996 12:50:26 -0400 Date: Mon, 16 Sep 1996 12:50:26 -0400 Message-Id: <199609161650.MAA16892@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Jeffrey Barber From: dennis@etinc.com (Dennis) Subject: Re: Very Slow Ethernet Link Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Apparenlty, Math and communications aren't strong subjects for you! Dennis >Ok, I just installed FreeBSD 2.1 and boy this is slow, Example: > >bash$ ping localhost > >PING localhost (127.0.0.1): 56 data bytes >64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.356 ms >64 bytes from 127.0.0.1: icmp_seq=1 ttl=255 time=0.342 ms >64 bytes from 127.0.0.1: icmp_seq=2 ttl=255 time=0.362 ms >64 bytes from 127.0.0.1: icmp_seq=3 ttl=255 time=0.349 ms > >--- localhost.arctic.net ping statistics --- >6 packets transmitted, 6 packets received, 0% packet loss >round-trip min/avg/max = 0.342/0.349/0.362 ms > >bash$ ifconfig -a > >lp0: flags=8810 mtu 1500 >ep0: flags=863 mtu 1500 > inet 19.51.13.1 netmask 0xffffff00 broadcast 19.51.13.255 >lo0: flags=8009 mtu 16384 > inet 127.0.0.1 netmask 0xff000000 >sl0: flags=c010 mtu 552 >tun0: flags=8010 mtu 1500 > > >On my Linux box I get a ping response of: > >PING localhost (127.0.0.1): 56 data bytes >64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=1.1 ms >64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.9 ms >64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.9 ms >64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=1.0 ms > >Big difference here. Please shed some light on this for me. > >TIA > > > From owner-freebsd-hackers Mon Sep 16 09:49:48 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA16125 for hackers-outgoing; Mon, 16 Sep 1996 09:49:48 -0700 (PDT) Received: from solar.os.com (craigs@solar.os.com [199.232.136.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA16106; Mon, 16 Sep 1996 09:49:42 -0700 (PDT) Received: (from craigs@localhost) by solar.os.com (8.7/8.7.0) id MAA28827; Mon, 16 Sep 1996 12:54:26 -0400 Date: Mon, 16 Sep 1996 12:54:26 -0400 From: Craig Shrimpton Subject: Re: Very Slow Ethernet Link To: Jeffrey Barber cc: "'freebsd-hardware@FreeBSD.org'" , "'hackers@FreeBSD.ORG'" In-Reply-To: <01BBA3A2.11B93340@jabpc.rtfm.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 16 Sep 1996, Jeffrey Barber wrote: > Ok, I just installed FreeBSD 2.1 and boy this is slow, Example: > > bash$ ping localhost > > PING localhost (127.0.0.1): 56 data bytes > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.356 ms > 64 bytes from 127.0.0.1: icmp_seq=1 ttl=255 time=0.342 ms > 64 bytes from 127.0.0.1: icmp_seq=2 ttl=255 time=0.362 ms > 64 bytes from 127.0.0.1: icmp_seq=3 ttl=255 time=0.349 ms You got it backwards. The FreeBSD box is much faster than the Linux box. A return time of .349 is faster than a return time of .9 - Craig +------------------------------------+--------------------------------------+ | Craig Shrimpton | e-mail: craigs@os.com | | Orbit Systems | information: info@os.com | | Worcester, MA 508.753.8776 | http://www.os.com/ | +------------------------------------+--------------------------------------+ _/_/_/_/ _/_/_/_/ _/_/_/_/ _/_/_/_/ _/_/_/_/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/_/_/ _/_/_/_/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/_/_/_/ _/ _/ _/_/_/_/ _/_/_/_/ _/ Strategic Systems From owner-freebsd-hackers Mon Sep 16 10:13:54 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA18267 for hackers-outgoing; Mon, 16 Sep 1996 10:13:54 -0700 (PDT) Received: from hp.com (hp.com [15.255.152.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA18254 for ; Mon, 16 Sep 1996 10:13:48 -0700 (PDT) Received: from srmail.sr.hp.com by hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA186254023; Mon, 16 Sep 1996 10:13:44 -0700 Received: from hpnmhjw.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA253954022; Mon, 16 Sep 1996 10:13:43 -0700 Received: from mina.sr.hp.com by hpnmhjw.sr.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA079274022; Mon, 16 Sep 1996 10:13:42 -0700 Message-Id: <199609161713.AA079274022@hpnmhjw.sr.hp.com> To: "Jordan K. Hubbard" Cc: hackers@freefall.freebsd.org Subject: Re: fdisk changes, anyone? In-Reply-To: Your message of "Mon, 16 Sep 1996 02:50:26 PDT." <20503.842867426@time.cdrom.com> Date: Mon, 16 Sep 1996 10:13:41 -0700 From: Darryl Okahata Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I've just mangled fdisk such that partitioning information can now > > be specified via an optional config file. I've been needing a way to > > partition a disk from a script (without using expect), and so I mangled > > fdisk to do just that. I want to write a perl script for adding SCSI > > disks, and a programmatic fdisk was the only piece missing. An example > > config file is: > > Wouldn't it be more flexible to add this as command-line parsing > for fdisk? I like the idea, but making it use a config file means > that anything driving fdisk programmatically needs to use a temp > file, rather than simply forming a complex fdisk commmand and > passing it to system(). Well, the only real "advantage" is that lines in the config file can be executed as they are parsed (that, and the fact that I hate command lines from h*ll ;-). With config files, you don't have to save the options before executing them. Also, as this is supposed to be used by scripts and not by real humans, I didn't think that making temporary files was all that big a deal. However, I wouldn't mind having these changes added to fdisk. If you (or someone else) are willing to commit these changes, I'll make it use command-line options from h*ll. ;-) -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. From owner-freebsd-hackers Mon Sep 16 10:14:10 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA18294 for hackers-outgoing; Mon, 16 Sep 1996 10:14:10 -0700 (PDT) Received: from Gatekeeper.Lamb.net (ulf@cat-food.Melmac.org [206.169.44.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA18289; Mon, 16 Sep 1996 10:14:08 -0700 (PDT) Received: (from ulf@localhost) by Gatekeeper.Lamb.net (8.7.5/8.7.3) id KAA02093; Mon, 16 Sep 1996 10:14:46 -0700 (PDT) From: Ulf Zimmermann Message-Id: <199609161714.KAA02093@Gatekeeper.Lamb.net> Subject: Re: Very Slow Ethernet Link To: jab@rock.anchorage.net (Jeffrey Barber) Date: Mon, 16 Sep 1996 10:14:45 -0700 (PDT) Cc: freebsd-hardware@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: <01BBA3A2.11B93340@jabpc.rtfm.com> from Jeffrey Barber at "Sep 16, 96 07:38:33 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 > Ok, I just installed FreeBSD 2.1 and boy this is slow, Example: > > bash$ ping localhost > > PING localhost (127.0.0.1): 56 data bytes > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.356 ms > 64 bytes from 127.0.0.1: icmp_seq=1 ttl=255 time=0.342 ms > 64 bytes from 127.0.0.1: icmp_seq=2 ttl=255 time=0.362 ms > 64 bytes from 127.0.0.1: icmp_seq=3 ttl=255 time=0.349 ms > > --- localhost.arctic.net ping statistics --- > 6 packets transmitted, 6 packets received, 0% packet loss > round-trip min/avg/max = 0.342/0.349/0.362 ms > > bash$ ifconfig -a > > lp0: flags=8810 mtu 1500 > ep0: flags=863 mtu 1500 > inet 19.51.13.1 netmask 0xffffff00 broadcast 19.51.13.255 > lo0: flags=8009 mtu 16384 > inet 127.0.0.1 netmask 0xff000000 > sl0: flags=c010 mtu 552 > tun0: flags=8010 mtu 1500 > > > On my Linux box I get a ping response of: > > PING localhost (127.0.0.1): 56 data bytes > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=1.1 ms > 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.9 ms > 64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.9 ms > 64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=1.0 ms > > Big difference here. Please shed some light on this for me. > > TIA > > And it seems you can't read ;-) the FreeBSD is faster then your Linux. Your Linux box gives you ping times of 1 ms and 0.9 ms, while FreeBSD gives you an average of 0.349 ms, since then is that slow ? Ulf. -------------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 Lamb Art Internet Services | http://www.Lamb.net/ | http://www.Alameda.net From owner-freebsd-hackers Mon Sep 16 10:22:12 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA19225 for hackers-outgoing; Mon, 16 Sep 1996 10:22:12 -0700 (PDT) Received: from mh004.infi.net (mh004.infi.net [198.22.1.119]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA19216 for ; Mon, 16 Sep 1996 10:22:08 -0700 (PDT) Received: from cpq-lte.ric.pmu.com by mh004.infi.net with ESMTP (Infinet-S-3.3) id NAA32022; Mon, 16 Sep 1996 13:21:44 -0400 (EDT) Message-Id: <199609161721.NAA32022@mh004.infi.net> From: "Steve Sims" To: "Bruce Evans" Cc: Subject: Re: Problem with sio0 Date: Mon, 16 Sep 1996 13:21:29 -0400 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: quoted-printable Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've stuffed a couple of diagnostic printf's into sio.c and have = empirically proven that the probe on a Compaq LTE/Elite returns 1's in = failures[5] and failures[8]. That is to say, with isa_irq_pending. A couple more minutes under the microscope shows that the sio0 probe is = being called with IRQ=3D0x10, even though the kernel's configed as IRQ4 = (and verified by a boot -c. FWIW: the sio1 probe is called with IRQ = 0x08. Shooting in the dark, I guessed that maybe the plug 'n' pray code might = have stuffed up the works, as sio0 is on the logic board and sio1 is on = a Megahurts X-Jack. I rebuilt the kernel without any PCCARD, APM, = whatever. That didn't change anything. So.... Not knowing ANYTHING, I offer the following question: how / = where does the *dev structure get filled in before being passed into = sioprobe()? It appears that that's where the failure starts, but I'm in = *way* over my head.... Bruce, thanks for the help thus far. ...sjs... ---------- > From: Bruce Evans > To: bde@zeta.org.au; SimsS@Infi.Net > Subject: Re: Problem with sio0 > Date: Wednesday, September 11, 1996 4:33 PM >=20 > >Sorry, Bruce, no joy with the sio.c patches on my Compaq LTE/Elite = 4/75. > >... > >Where do I start to get this one hammered out? >=20 > What happens when you disable the tests in the probe? Some of the = tests > are too fussy. >=20 > Bruce From owner-freebsd-hackers Mon Sep 16 10:30:16 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA19892 for hackers-outgoing; Mon, 16 Sep 1996 10:30:16 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA19874; Mon, 16 Sep 1996 10:30:08 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id TAA16559; Mon, 16 Sep 1996 19:29:38 +0200 (MET DST) To: Jeffrey Barber cc: "'freebsd-hardware@FreeBSD.org'" , "'hackers@FreeBSD.ORG'" Subject: Re: Very Slow Ethernet Link In-reply-to: Your message of "Mon, 16 Sep 1996 07:38:33 -0800." <01BBA3A2.11B93340@jabpc.rtfm.com> Date: Mon, 16 Sep 1996 19:29:38 +0200 Message-ID: <16557.842894978@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In message <01BBA3A2.11B93340@jabpc.rtfm.com>, Jeffrey Barber writes: >Ok, I just installed FreeBSD 2.1 and boy this is slow, Example: > >bash$ ping localhost > >PING localhost (127.0.0.1): 56 data bytes > >round-trip min/avg/max = 0.342/0.349/0.362 ms > >On my Linux box I get a ping response of: > >PING localhost (127.0.0.1): 56 data bytes >64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=1.1 ms >64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.9 ms >64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.9 ms >64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=1.0 ms > >Big difference here. Please shed some light on this for me. Seems to me that FreeBSD is 3 times >faster< on this completely silly benchmark... -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-hackers Mon Sep 16 10:46:23 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA21004 for hackers-outgoing; Mon, 16 Sep 1996 10:46:23 -0700 (PDT) Received: from saguaro.flyingfox.com (saguaro.flyingfox.com [204.188.109.253]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA20998; Mon, 16 Sep 1996 10:46:21 -0700 (PDT) Received: (from jas@localhost) by saguaro.flyingfox.com (8.6.12/8.6.10) id KAA07081; Mon, 16 Sep 1996 10:44:55 -0700 Date: Mon, 16 Sep 1996 10:44:55 -0700 From: Jim Shankland Message-Id: <199609161744.KAA07081@saguaro.flyingfox.com> To: jab@rock.anchorage.net, kelly@fsl.noaa.gov Subject: Re: Very Slow Ethernet Link Cc: freebsd-hardware@FreeBSD.org, hackers@FreeBSD.org Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk OK, so several correspondents have pointed out that 0.356ms (ping RTT for 127.0.0.1 on FreeBSD) is less than 1.1 ms (ping RTT for 127.0.0.1) on Linux. On the assumption that the original mail was not a mis-timed April Fool's prank, let me make two small, additional observations: (1) Packets to 127.0.0.1 will go through the loopback interface, so Ethernet has nothing to do with it. (2) It is possible that jab@rock.anchorage.net was looking at the ttl value rather than the RTT. The ttl was 64 for Linux, 255 for FreeBSD. This has nothing to do with ping times, but rather with the maximum number of hops that a packet can make before it is discarded on the assumption that there is some routing loop. It needs to be larger than the largest number of hops that a packet could legitimately make en route from its source to its destination. 64 is probably sufficient in today's Internet; 255 works, too, and may be a better choice. If ttl is to be the measure of performance, then sysctl -W net.inet.ip.ttl=32 will cause FreeBSD to run circles around Linux :-). Jim Shankland Flying Fox Computer Systems, Inc. From owner-freebsd-hackers Mon Sep 16 10:53:31 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA21608 for hackers-outgoing; Mon, 16 Sep 1996 10:53:31 -0700 (PDT) Received: from persprog.com (persprog.com [204.215.255.203]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA21597; Mon, 16 Sep 1996 10:53:24 -0700 (PDT) Received: by persprog.com (8.7.5/4.10) id MAA26137; Mon, 16 Sep 1996 12:44:13 -0500 Received: from dasa(192.2.2.199) by cerberus.ppi.com via smap (V1.3) id sma026135; Mon Sep 16 13:43:57 1996 Received: from DASA/SpoolDir by dasa.ppi.com (Mercury 1.21); 16 Sep 96 13:43:59 +0500 Received: from SpoolDir by DASA (Mercury 1.30); 16 Sep 96 13:43:43 +0500 From: "David Alderman" Organization: Personalized Programming, Inc To: John Dyson , freebsd-hardware@FreeBSD.org, hackers@FreeBSD.org, jab@rock.anchorage.net Date: Mon, 16 Sep 1996 13:43:40 +0500 Subject: Re: Very Slow Ethernet Link Priority: normal X-mailer: Pegasus Mail for Windows (v2.42a) Message-ID: Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > From: John Dyson > Reply-to: dyson@FreeBSD.org > > Ok, I just installed FreeBSD 2.1 and boy this is slow, Example: > > > > bash$ ping localhost > > > FreeBSD number: > > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.356 ms > > Linux number: > > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=1.1 ms > > Looks like Linux is slower to me... > > John > Is the ping code the same on both Linux and FreeBSD? On older SCO boxes it always says 0ms (and their TCP/IP is not all that great). I would think ftp (or anything else) would be a better test of the TCP/IP stack. I didn't see the original post so please accept my apologies if I'm just blathering. ====================================== When philosophy conflicts with reality, choose reality. Dave Alderman -- dave@persprog.com ====================================== From owner-freebsd-hackers Mon Sep 16 10:58:11 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA22110 for hackers-outgoing; Mon, 16 Sep 1996 10:58:11 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA22097 for ; Mon, 16 Sep 1996 10:58:04 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id KAA05753 for ; Mon, 16 Sep 1996 10:57:40 -0700 (PDT) Message-Id: <199609161757.KAA05753@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: hackers@freebsd.org Subject: where did sys/i386/include/devconf.h go ? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 16 Sep 1996 10:57:40 -0700 From: Amancio Hasty Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Basically, the sound driver 3.5 distribution for the gus pnp includes that file and I was wondering what happen to it. Tnks, Amancio From owner-freebsd-hackers Mon Sep 16 11:05:35 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA22849 for hackers-outgoing; Mon, 16 Sep 1996 11:05:35 -0700 (PDT) Received: from zwei.siemens.at (zwei.siemens.at [193.81.246.12]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA22830 for ; Mon, 16 Sep 1996 11:05:26 -0700 (PDT) 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 UAA29643 for ; Mon, 16 Sep 1996 20:04:17 +0200 (MET DST) Received: from ws2301.gud.siemens.co.at by sol1.gud.siemens.co.at with smtp (Smail3.1.28.1 #7 for ) id m0v2i2N-000218C; Mon, 16 Sep 96 20:04 MET DST Received: by ws2301.gud.siemens.co.at (1.37.109.16/1.37) id AA264216807; Mon, 16 Sep 1996 20:00:07 +0200 From: "Hr.Ladavac" Message-Id: <199609161800.AA264216807@ws2301.gud.siemens.co.at> Subject: Re: Question on Porting Windows software to X To: schluntz@gromit.pinpt.com (Sean J. Schluntz) Date: Mon, 16 Sep 1996 20:00:07 +0200 (MESZ) Cc: hackers@FreeBSD.org In-Reply-To: <2.2.32.19960916163342.0091e7c8@wallace.pinpt.com> from "Sean J. Schluntz" at Sep 16, 96 09:33:42 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 Sean J. Schluntz contained: > I am sending this to Hackers, 'cuz I figgured that you all would know the > answer to this one. > > Looking at a larger word processing application for windows (16bit not 32) > like Word 6, WordPerfict 6 or WordStar. What do would you all think the > difficulty level and approximate time would be required to port this app to > X if you had the full sources for the orriginal application. A long time ago there was a WinApi project which mapped Win16 calls to XView libs. There are also some commercial libs of the similar sort. So, it should be almost a recompile away, but don't count on it :) > > Following up, would there be any one out there with the interest to possibly > make some royalties by working on such a project? Consulting gigs are always welcome :) /Marino From owner-freebsd-hackers Mon Sep 16 11:08:13 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA23167 for hackers-outgoing; Mon, 16 Sep 1996 11:08:13 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA23116 for ; Mon, 16 Sep 1996 11:08:09 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA02580; Mon, 16 Sep 1996 11:05:55 -0700 From: Terry Lambert Message-Id: <199609161805.LAA02580@phaeton.artisoft.com> Subject: Re: attribute/inode caching To: dg@root.com Date: Mon, 16 Sep 1996 11:05:55 -0700 (MST) Cc: terry@lambert.org, bde@zeta.org.au, proff@suburbia.net, freebsd-hackers@FreeBSD.org In-Reply-To: <199609150333.UAA05077@root.com> from "David Greenman" at Sep 14, 96 08:33: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 > >> It could be hung off the vnode for the mounted device. I'm not sure if > >> it isn't already. This problem is secondary. Repeated tree traversals > >> aren't all that common, and you don't really want them to eat the buffer > >> cache (you probably want to buffer precisely the inodes and directories > >> that will be hit again a long time later in the same search, e.g., > >> intermediate directories for a depth-first seach). > > > >It is not hung off the vnode for the device. It probably should not be, > >in any case (there is no "device" for NFS, for instance). > > Inode blocks are hung off the device vnode. I find this hard to believe. This would imply a limitation of the device size of the file size, since the adressable extent for a vnode is smaller than the addressable extent for a device. Which value are you caliming is in error? It seems to me that if inode blocks are hung of the device vnode (so why have the ihash?!?), then it is an error to not limit the device size to the max file size. The fact that the device size was allowed to be larger than the max file size was one of the justifications John Dyson gave for not using caching based on device/extent instead of (in addition to) vnode/extent in order to keep the buffer cache unification of the vnode/extent mapping, but resolve a lot of other issues. For instance, if the device vnode is in fact a device/extent cache, then there is no need for the ihash, since the inodes are determiistically layed out and thus indexable by fault. In addition, the abilit to address device blocks by fault on the device vnode means that vclean is totally unnecessary. I think you might be confusing what I have been arguing for for over a year (a device/extent-based block cache) with reality? > Indirect blocks are hung off the file vnode (using negative block numbers). I knew this already; indirect blocks aren't the issue, since they are per vnode objects in any case (though there are a number of sign extension issues that should be addressed for the 32/64 bit problem). If we had a full 64 bit space, we could use page anonymity protection instead of relying on much-more-costly premapping. 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 Sep 16 11:11:41 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA23667 for hackers-outgoing; Mon, 16 Sep 1996 11:11:41 -0700 (PDT) Received: from night.primate.wisc.edu (night.primate.wisc.edu [144.92.43.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA23648; Mon, 16 Sep 1996 11:11:37 -0700 (PDT) Received: by night.primate.wisc.edu; id NAA28776; 8.6.10/41.8; Mon, 16 Sep 1996 13:12:54 -0500 From: Paul DuBois Message-Id: <199609161812.NAA28776@night.primate.wisc.edu> Subject: Re: Enough (was Re: Very Slow Ethernet Link) To: mgessner@aristar.com (Matthew A. Gessner) Date: Mon, 16 Sep 1996 13:12:54 -0500 (CDT) Cc: freebsd-hardware@freebsd.org, freebsd-hackers@freebsd.org In-Reply-To: <323D7E23.31DFF4F5@aristar.com> from "Matthew A. Gessner" at Sep 16, 96 12:19:47 pm X-Mailer: ELM [version 2.4 PL25] 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 >Hey, all, by this time, he probably got the hint. I figured all the respondents were trying to demonstrate that NO question is too difficult for this list. :-) From owner-freebsd-hackers Mon Sep 16 11:24:44 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA24981 for hackers-outgoing; Mon, 16 Sep 1996 11:24:44 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA24974; Mon, 16 Sep 1996 11:24:41 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id NAA05966; Mon, 16 Sep 1996 13:23:24 -0500 From: Joe Greco Message-Id: <199609161823.NAA05966@brasil.moneng.mei.com> Subject: Re: Very Slow Ethernet Link To: nate@mt.sri.com (Nate Williams) Date: Mon, 16 Sep 1996 13:23:24 -0500 (CDT) Cc: jab@rock.anchorage.net, freebsd-hardware@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: <199609161554.JAA02862@rocky.mt.sri.com> from "Nate Williams" at Sep 16, 96 09:54:47 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Jeffrey Barber writes: > > Ok, I just installed FreeBSD 2.1 and boy this is slow, Example: > > > > bash$ ping localhost > > > > PING localhost (127.0.0.1): 56 data bytes > > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.356 ms > > > On my Linux box I get a ping response of: > > > > PING localhost (127.0.0.1): 56 data bytes > > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=1.1 ms > > Hmm, it looks like the Linux box is about 3X slower than FreeBSD. I'm > not sure, but in my math class .1 ms is faster than 1ms. You guys aren't touching on an important point: This is NOT Ethernet traffic. This is loopback traffic! (see Subject:) Given the same hardware, FreeBSD will generally go faster than Linux for most real networking tests (ok, fine, _all_ of them that _I_ have seen that were executed in an unbiased manner). However, the difference in speed seems to be magnified somewhat on the loopback interface :-) Anyways, the fix to this fellow's problem is obvious: Press the Turbo switch or set your CMOS configuration to start the machine up in non-Turbo mode. Then your FreeBSD box will (probably?) go slower than your Linux box. ( all sorts of :-)'s ) ... JG From owner-freebsd-hackers Mon Sep 16 11:32:47 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA25651 for hackers-outgoing; Mon, 16 Sep 1996 11:32:47 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA25643 for ; Mon, 16 Sep 1996 11:32:44 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.eu.org [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id UAA03770 for ; Mon, 16 Sep 1996 20:32:41 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id UAA12306 for hackers@freebsd.org; Mon, 16 Sep 1996 20:32:28 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.Beta.1/keltia-uucp-2.9) id UAA02690; Mon, 16 Sep 1996 20:18:50 +0200 (MET DST) Message-Id: <199609161818.UAA02690@keltia.freenix.fr> Date: Mon, 16 Sep 1996 20:18:49 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: hackers@freebsd.org Subject: Re: Could use a favor In-Reply-To: <199609161444.KAA16111@etinc.com>; from Dennis on Sep 16, 1996 10:44:34 -0400 References: <199609161444.KAA16111@etinc.com> X-Mailer: Mutt 0.43g Mime-Version: 1.0 X-Operating-System: FreeBSD 2.2-CURRENT ctm#2443 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Dennis: > Perhaps unrelated....but I've noticed if I configure IP firewalling into > the kernel the default seems to be that the system cant do anything. Can > anyone outline why that is.... Uh ? Where you the last months, on the moon ? :-) Poul-Henning rewrote a big part of IPFW, added many things like filters per interfaces, better port handling and other things. He also made the default not to pass anything (so you can open for what you need instead of closing what you don't need). If you want to by wide-open, change firewall to YES in /etc/sysconfig and put a file named rc.firewall in /etc with the following: /etc/rc.firewall ------------------------------------------------------------ # Flush out the list before we begin. /sbin/ipfw -f flush /sbin/ipfw add 65000 pass all from any to any ------------------------------------------------------------ Or you can add you own rules here. See /usr/src/etc/rc.firewall for examples. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #21: Sun Sep 8 14:35:00 MET DST 1996 From owner-freebsd-hackers Mon Sep 16 11:32:54 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA25681 for hackers-outgoing; Mon, 16 Sep 1996 11:32:54 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA25670 for ; Mon, 16 Sep 1996 11:32:50 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.eu.org [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id UAA03772 for ; Mon, 16 Sep 1996 20:32:42 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id UAA12307 for hackers@FreeBSD.org; Mon, 16 Sep 1996 20:32:28 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.Beta.1/keltia-uucp-2.9) id UAA02735; Mon, 16 Sep 1996 20:30:05 +0200 (MET DST) Message-Id: <199609161830.UAA02735@keltia.freenix.fr> Date: Mon, 16 Sep 1996 20:30:04 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: hackers@freebsd.org ('hackers@FreeBSD.ORG') Subject: Re: Very Slow Ethernet Link In-Reply-To: <01BBA3A2.11B93340@jabpc.rtfm.com>; from Jeffrey Barber on Sep 16, 1996 7:38:33 -0800 References: <01BBA3A2.11B93340@jabpc.rtfm.com> X-Mailer: Mutt 0.43g Mime-Version: 1.0 X-Operating-System: FreeBSD 2.2-CURRENT ctm#2443 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [please try to avoid crossposting between hackers and other lists] According to Jeffrey Barber: > Ok, I just installed FreeBSD 2.1 and boy this is slow, Example: [FreeBSD 2.1.0] > PING localhost (127.0.0.1): 56 data bytes > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.356 ms > 64 bytes from 127.0.0.1: icmp_seq=1 ttl=255 time=0.342 ms > 64 bytes from 127.0.0.1: icmp_seq=2 ttl=255 time=0.362 ms > 64 bytes from 127.0.0.1: icmp_seq=3 ttl=255 time=0.349 ms [Linux] > PING localhost (127.0.0.1): 56 data bytes > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=1.1 ms > 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.9 ms > 64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.9 ms > 64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=1.0 ms What am I missing ? From the numbers you gave us, the FreeBSD machine is 3 times *faster* than the Linux one for localhost ??? Anyway, localhost doesn't use ethernet at all. It is all handled into the kernel, packets from/to 127.0.0.1 don't go over the wire... -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #21: Sun Sep 8 14:35:00 MET DST 1996 From owner-freebsd-hackers Mon Sep 16 11:36:30 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA26059 for hackers-outgoing; Mon, 16 Sep 1996 11:36:30 -0700 (PDT) Received: from mh004.infi.net (mh004.infi.net [198.22.1.119]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA26052 for ; Mon, 16 Sep 1996 11:36:28 -0700 (PDT) Received: from cpq-lte.ric.pmu.com by mh004.infi.net with ESMTP (Infinet-S-3.3) id OAA27880; Mon, 16 Sep 1996 14:36:31 -0400 (EDT) Message-Id: <199609161836.OAA27880@mh004.infi.net> From: "Steve Sims" To: Subject: tun0 device Date: Mon, 16 Sep 1996 14:36:17 -0400 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: quoted-printable Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Where's the seminal reference on the tunnel device? =20 `apropos tunnel` yields nada. Ditto for `man tun`. I don't have a *recent* handbook, but the one I have mentions it only in = passing. Muchas Gracias in advance.... ...sjs... From owner-freebsd-hackers Mon Sep 16 12:16:35 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA29660 for hackers-outgoing; Mon, 16 Sep 1996 12:16:35 -0700 (PDT) Received: from FileServ1.MI.Uni-Koeln.DE (FileServ1.MI.Uni-Koeln.DE [134.95.212.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA29651 for ; Mon, 16 Sep 1996 12:16:32 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-41.slip.Uni-Koeln.DE) by FileServ1.MI.Uni-Koeln.DE with SMTP id AA05258 (5.67b/IDA-1.5 for ); Mon, 16 Sep 1996 21:16:29 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id VAA01701; Mon, 16 Sep 1996 21:16:14 +0200 (MET DST) Date: Mon, 16 Sep 1996 21:16:14 +0200 (MET DST) Message-Id: <199609161916.VAA01701@x14.mi.uni-koeln.de> From: Stefan Esser To: Kees.Koster@nym.sc.philips.com Cc: hackers@freebsd.org Subject: Re: 2.1.5 installed, no problem at all! In-Reply-To: <2483ED94D5D@NLNMG01.nym.sc.philips.com> References: <2483ED94D5D@NLNMG01.nym.sc.philips.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Kees Jan Koster writes: > > > > > I just received the 2.1.5-RELEASE cdrom and installed it. > > > Once again, barely 20 minutes install time, including reading > > > the readme's. Great job, thanks. > > > > Interesting... This is not a common error message on this list. > > Can you elaborate your setup a little--perhaps we can help. > > > Surel, I've got an ATAPI cdrom (Identified by both the bios and > FreeBSD as an "iPnoee r"). So the ATAPI stuff _does_ work for some > drives. And I've got an AMD 5k86-P100, so those seem to FreeBSD > compatible too (could someone mail them the little stickers to put on > each of their cpu's?) Hmm, how about some lmbench and/or bytebench results for that CPU ? It is very cheap and should be able to drive the PCI bus at a full 33MHz, and since my main application isn't games :) it most probably is fast enough for a small to medium sized server ... Some performance claims I've seen seem to indicate, that it performs well on 32 bit codes. Regards, STefan From owner-freebsd-hackers Mon Sep 16 12:24:24 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA00567 for hackers-outgoing; Mon, 16 Sep 1996 12:24:24 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA00561 for ; Mon, 16 Sep 1996 12:24:21 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.eu.org [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id VAA03820 for ; Mon, 16 Sep 1996 21:24:11 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id VAA12707 for hackers@FreeBSD.org; Mon, 16 Sep 1996 21:23:49 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.Beta.1/keltia-uucp-2.9) id UAA03226; Mon, 16 Sep 1996 20:56:31 +0200 (MET DST) Message-Id: <199609161856.UAA03226@keltia.freenix.fr> Date: Mon, 16 Sep 1996 20:56:31 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: hackers@FreeBSD.org Subject: Re: Could use a favor In-Reply-To: ; from Narvi on Sep 16, 1996 19:03:00 +0300 References: X-Mailer: Mutt 0.43g Mime-Version: 1.0 X-Operating-System: FreeBSD 2.2-CURRENT ctm#2443 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk According to Narvi: > The only conclusion I have come at is that it is to allow only things > that you especially allow to happen... The bad thing is that there is no > switch to switch the firewall on/off. You compile a new kernel with the > option for firewall and suddenly it accepts nothing over the network. Sure there is: By default all is off. To open (dangerous!!!) ipfw add 65000 pass all from any to any To close it again: ipfw delete 65000 -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #21: Sun Sep 8 14:35:00 MET DST 1996 From owner-freebsd-hackers Mon Sep 16 12:43:56 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA02159 for hackers-outgoing; Mon, 16 Sep 1996 12:43:56 -0700 (PDT) Received: from alpo.whistle.com (s205m1.whistle.com [207.76.205.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA02152; Mon, 16 Sep 1996 12:43:51 -0700 (PDT) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.7.5/8.7.3) with SMTP id MAA18330; Mon, 16 Sep 1996 12:38:31 -0700 (PDT) Message-ID: <323DAC5D.ABD322C@whistle.com> Date: Mon, 16 Sep 1996 12:37:01 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Jeffrey Barber CC: "'freebsd-hardware@FreeBSD.org'" , "'hackers@FreeBSD.ORG'" Subject: Re: Very Slow Ethernet Link References: <01BBA3A2.11B93340@jabpc.rtfm.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Jeffrey Barber wrote: > > Ok, I just installed FreeBSD 2.1 and boy this is slow, Example: OK for a start your FreeBSD times are approximatly 1/3 the times of the linux ones.. 0.3mS vs 1mS secondly, pinging the loopback interface doesn't test the ethernet as the packet never goes anywhere NEAR the ethernet. thirdly, if the ethernet is slow, and you haven't showed that it is, you need to give your hardware configuration. maybe FreeBSD is configured for the wrong interrupt.. that tends to make it slow.. lastly, 2.1 is way old.. you should install 2.1.5 becasue 2.1 is hard to support as everyone has moved on. > > bash$ ping localhost > > PING localhost (127.0.0.1): 56 data bytes > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.356 ms > 64 bytes from 127.0.0.1: icmp_seq=1 ttl=255 time=0.342 ms > 64 bytes from 127.0.0.1: icmp_seq=2 ttl=255 time=0.362 ms > 64 bytes from 127.0.0.1: icmp_seq=3 ttl=255 time=0.349 ms > > --- localhost.arctic.net ping statistics --- > 6 packets transmitted, 6 packets received, 0% packet loss > round-trip min/avg/max = 0.342/0.349/0.362 ms > > bash$ ifconfig -a > > lp0: flags=8810 mtu 1500 > ep0: flags=863 mtu 1500 > inet 19.51.13.1 netmask 0xffffff00 broadcast 19.51.13.255 > lo0: flags=8009 mtu 16384 > inet 127.0.0.1 netmask 0xff000000 > sl0: flags=c010 mtu 552 > tun0: flags=8010 mtu 1500 > > On my Linux box I get a ping response of: > > PING localhost (127.0.0.1): 56 data bytes > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=1.1 ms > 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.9 ms > 64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.9 ms > 64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=1.0 ms > > Big difference here. Please shed some light on this for me. > > TIA From owner-freebsd-hackers Mon Sep 16 13:09:46 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA04044 for hackers-outgoing; Mon, 16 Sep 1996 13:09:46 -0700 (PDT) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA04039 for ; Mon, 16 Sep 1996 13:09:42 -0700 (PDT) Received: from ppp-089.etinc.com (ppp-089.etinc.com [204.141.95.148]) by etinc.com (8.6.12/8.6.9) with SMTP id QAA18119; Mon, 16 Sep 1996 16:16:17 -0400 Date: Mon, 16 Sep 1996 16:16:17 -0400 Message-Id: <199609162016.QAA18119@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: "Matthew A. Gessner" From: dennis@etinc.com (Dennis) Subject: Re: Enough (was Re: Very Slow Ethernet Link) Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Nate Williams wrote: >> >> Jeffrey Barber writes: >> > Ok, I just installed FreeBSD 2.1 and boy this is slow, Example: >> > >> > bash$ ping localhost >> > >> > PING localhost (127.0.0.1): 56 data bytes >> > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.356 ms >> >> vs. >> >> > On my Linux box I get a ping response of: >> > >> > PING localhost (127.0.0.1): 56 data bytes >> > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=1.1 ms >> >> Hmm, it looks like the Linux box is about 3X slower than FreeBSD. I'm >> not sure, but in my math class .1 ms is faster than 1ms. >> >> Nate >Hey, all, by this time, he probably got the hint. C'mon, let us have some fun. We haven't has a colossal blunder like this in a while! db From owner-freebsd-hackers Mon Sep 16 13:19:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA04686 for hackers-outgoing; Mon, 16 Sep 1996 13:19:25 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA04679 for ; Mon, 16 Sep 1996 13:19:23 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA02780; Mon, 16 Sep 1996 13:18:39 -0700 From: Terry Lambert Message-Id: <199609162018.NAA02780@phaeton.artisoft.com> Subject: Re: attribute/inode caching To: bde@zeta.org.au (Bruce Evans) Date: Mon, 16 Sep 1996 13:18:38 -0700 (MST) Cc: bde@zeta.org.au, terry@lambert.org, freebsd-hackers@FreeBSD.org, proff@suburbia.net In-Reply-To: <199609150215.MAA32073@godzilla.zeta.org.au> from "Bruce Evans" at Sep 15, 96 12:15:52 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 > If the buffer cache didn't thrash, then it would be written on the next > sync, much later. If in addition writes were ordered in block order, > then it would be written efficiently together with nearby dirty inodes. > Normally, ffs_sync() writes things in the semi-random vnode list order. > disksort() sorts the into block order, but this only helps if the disk > can't keep up with the i/o requests. > > Another way to look at it: consider traversing my /usr/src, which has > 21097 inodes and 2810 directories. if the cache thrashes (certain) > and the inodes are contiguous on disk (unlikely :-), then there will > be a 2637KB of reads and a whole 351KB of writes to update the atimes. > The write time should be relatively negligible if the cache is working > (more so, because you can schedule delayed writes but reads have to be > synchronous). Well, then, we are back to talking about implementing strategies, like write gathering, to clean up the mess. The problem, of course, is that since the cache is not device/offset (despite the discussion that claims blocks are hung of the device vnode to the contrary), then it is impossible to gather things which are physically contiguous, even though doing so would be a win. 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 Sep 16 13:29:55 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA05668 for hackers-outgoing; Mon, 16 Sep 1996 13:29:55 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA05662 for ; Mon, 16 Sep 1996 13:29:52 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA02806; Mon, 16 Sep 1996 13:28:42 -0700 From: Terry Lambert Message-Id: <199609162028.NAA02806@phaeton.artisoft.com> Subject: Re: Question on Porting Windows software to X To: schluntz@gromit.pinpt.com (Sean J. Schluntz) Date: Mon, 16 Sep 1996 13:28:42 -0700 (MST) Cc: hackers@freebsd.org In-Reply-To: <2.2.32.19960916163342.0091e7c8@wallace.pinpt.com> from "Sean J. Schluntz" at Sep 16, 96 09:33:42 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 am sending this to Hackers, 'cuz I figgured that you all would know the > answer to this one. > > Looking at a larger word processing application for windows (16bit not 32) > like Word 6, WordPerfict 6 or WordStar. What do would you all think the > difficulty level and approximate time would be required to port this app to > X if you had the full sources for the orriginal application. You could use one of at least 3 "porting Windows programs to Motif" packages, one of which is "Willows" (www.willows.com). The actual difficulty in porting depends a lot on what interfaces the software uses that are not Windows-specific interfaces -- ie: you will have to convert INT 21 and other calls manually. So the quick answer is "it depends on the software". 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 Sep 16 13:44:45 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA07023 for hackers-outgoing; Mon, 16 Sep 1996 13:44:45 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA07016; Mon, 16 Sep 1996 13:44:40 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id NAA14600; Mon, 16 Sep 1996 13:44:14 -0700 (PDT) Message-Id: <199609162044.NAA14600@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 to: "'freebsd-hardware@FreeBSD.org'" , "'hackers@FreeBSD.ORG'" Subject: Wait and then Post! (Re: Very Slow Ethernet Link ) In-reply-to: Your message of "Mon, 16 Sep 1996 12:37:01 PDT." <323DAC5D.ABD322C@whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 16 Sep 1996 13:44:14 -0700 From: Amancio Hasty Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Is there a way to throttle responses to dumb posts ? 8) If the answer is obvious, try to wait a little bit before posting a response mostly because I am sure that some will not be able to resist answering the post 8) Cheers, Amancio From owner-freebsd-hackers Mon Sep 16 14:02:40 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA07927 for hackers-outgoing; Mon, 16 Sep 1996 14:02:40 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA07920 for ; Mon, 16 Sep 1996 14:02:36 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id OAA14787 for ; Mon, 16 Sep 1996 14:02:11 -0700 (PDT) Message-Id: <199609162102.OAA14787@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: hackers@freebsd.org Subject: Any Takers ? MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----- =_aaaaaaaaaa0" Content-ID: <14782.842907730.0@rah.star-gate.com> Date: Mon, 16 Sep 1996 14:02:11 -0700 From: Amancio Hasty Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ------- =_aaaaaaaaaa0 Content-Type: text/plain; charset="us-ascii" Content-ID: <14782.842907730.1@rah.star-gate.com> It would be nice if we submitted a couple of papers on the impact FreeBSD. We are somewhat special in that in a sense we have a full OS distribution as supposed to a specialized project. Enjoy, Amancio ------- =_aaaaaaaaaa0 Content-Type: message/rfc822 Return-Path: rem-conf-request@es.net Received: from osi-west.es.net (osi-west.es.net [198.128.3.61]) by rah.star-gate.com (8.7.5/8.7.3) with SMTP id NAA14741 for ; Mon, 16 Sep 1996 13:53:58 -0700 (PDT) Received: from iggy.iwsc.com by osi-west.es.net with ESnet SMTP (PP); Mon, 16 Sep 1996 12:05:27 -0700 Received: from bmeandzija_nt (analog_dell.gi.com [168.84.65.19]) by iggy.iwsc.com (post.office MTA v1.9.3 ID# 10-12202) with SMTP id AAA240 for ; Mon, 16 Sep 1996 12:10:17 +0100 Message-ID: <323DA472.91A@metacomm.com> Date: Mon, 16 Sep 1996 12:03:14 -0700 From: Branislav Meandzija Reply-To: bran@metacomm.com Organization: Meta Communications, Inc. X-Mailer: Mozilla 3.0b8Gold (WinNT; I) MIME-Version: 1.0 To: rem-conf@es.net Subject: Call for Papers - Global Internet - IEEE Communications Magazine Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit CALL FOR PAPERS IEEE COMMUNICATIONS MAGAZINE SPECIAL ISSUE ON THE GLOBAL INTERNET The IEEE Communications Magazine is soliciting original tutorial-style manuscripts for a planned Special Issue on the Global Internet. From its origins as a US government research project, the Internet has grown to become a major component of the global world-wide network infrastructure, linking millions of machines and tens of millions of users around the world. If the Internet were a stock it would be considered a market phenomenon, with sustained double-digit growth and no apparent end in sight to its upward spiral. Over 70 countries have full TCP/IP Internet connectivity, and about 150 have at least e-mail services through IP or via more limited means of connectivity (e.g., UUCP or Fidonet). Given such phenomenal growth, the Global Internet is increasingly viewed as the catalyst for a communications revolution resulting in a plethora of new technological, economic, and social changes. The focus of the special issue is on the technologies of the Internet, the technological changes driven by the emergence of a truly Global Internet, and collateral economic and social issues. Papers are solicited on the following specific subjects: * Internet Applications - information retrieval, directory services, catalogs, search tools and user agents; electronic publishing; education; www; languages; collaborative work environments. * Internet Connectivity Infrastructure - service characteristics ("best effort" vs. guaranteed); reliability (utility); addressing; multicasting; routing; protocols. * Internet Administrative Infrastructure - regulation; public policy; economics; standards. * Internet Security - security technology; export controls; privacy. * Internet Management - protocols; agent technology; standards; platforms. * Internet Commerce - electronic banking; virtual retailing; payment systems. Submitted manuscripts must be no longer than 12 single-spaced pages. The cover page should include the title of the paper, a brief abstract, a list of keywords, and the full name, affiliation, postal address, telephone number, and electronic mail address of each author. Papers may be submitted in postscript format via e-mail or as hardcopy (six copies). Authors should obtain company and government clearances prior to submission of papers. Papers should be submitted by October 31, 1996 to either of the guest co-editors. All papers will go through a peer-review process. They will be judged with respect to their quality and relevance to the Special Issue and the IEEE Communications Magazine. Authors will be notified of acceptance or rejection by December 15, 1996. Final copies of accepted papers will be due by January 31, 1997. Publication is scheduled for May 1997. Please submit manuscripts by October 31 to either: Branislav Meandzija - OR- Lyman Chapin Meta Communications, Inc. BBN CORPORATION 322 North Cleveland Ave., Suite 100 10 Moulton Street Oceanside, CA 92054 USA Cambridge, MA 02138 USA Phone: +1 619 721 6033 Phone: +1 617 873 3133 Fax: +1 619 456 7472 Fax: +1 617 873 3243 e-mail: bran@metacomm.com e-mail: lyman@bbn.com ------- =_aaaaaaaaaa0-- From owner-freebsd-hackers Mon Sep 16 14:03:49 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA08035 for hackers-outgoing; Mon, 16 Sep 1996 14:03:49 -0700 (PDT) Received: from chain.iafrica.com (root@chain.iafrica.com [196.7.74.174]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA07976 for ; Mon, 16 Sep 1996 14:03:11 -0700 (PDT) Received: from localhost (khetan@localhost [127.0.0.1]) by chain.iafrica.com (8.7.5/8.6.12) with SMTP id WAA00537; Mon, 16 Sep 1996 22:40:22 +0200 (SAT) Date: Mon, 16 Sep 1996 22:40:22 +0200 (SAT) From: Khetan Gajjar To: "Sean J. Schluntz" cc: hackers@freebsd.org Subject: Re: Question on Porting Windows software to X In-Reply-To: <2.2.32.19960916163342.0091e7c8@wallace.pinpt.com> Message-ID: X-URL: http://www.iafrica.com/~khetan/ X-Alternate-Address: khetan@uunet.co.za X-Alternate-Address2: kg@iafrica.com X-Alternate-Address3: gjjkhe01@sonnenberg.uct.ac.za X-Alternate-Address4: khetan@chain.iafrica.com X-Comment: Telkom sucks huge! X-IRC-nick: chain MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 16 Sep 1996, Sean J. Schluntz wrote: >Looking at a larger word processing application for windows (16bit not 32) >like Word 6, WordPerfict 6 or WordStar. What do would you all think the Well, afaik, WordPerfect 6 is available for SCO Unix; with the improved ibcs2 in -current, we can run the app fine - it's the ruddy Flex License manager we can't get working. I'd pay for someone to get THAT working! Has there been any progress on that ? Is/Has someone contacted Flex about it ? I tried, but they said sorry, it's for SCO - not BSD. --- Khetan Gajjar [ http://www.iafrica.com/~khetan] I'm a FreeBSD User! [ http://www.freebsd.org] UUNet Internet Africa [0800-030-002 & help@iafrica.com] Fortune : Excellent day for drinking heavily. Spike office water cooler. From owner-freebsd-hackers Mon Sep 16 14:13:00 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA08768 for hackers-outgoing; Mon, 16 Sep 1996 14:13:00 -0700 (PDT) Received: from main.gbdata.com (Main.GBData.COM [207.90.222.20]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA08759 for ; Mon, 16 Sep 1996 14:12:53 -0700 (PDT) Received: (from gclarkii@localhost) by main.gbdata.com (8.7.5/8.6.9) id QAA05640; Mon, 16 Sep 1996 16:11:42 -0500 (CDT) From: Gary Clark II Message-Id: <199609162111.QAA05640@main.gbdata.com> Subject: Re: Could use a favor To: dennis@etinc.com (Dennis) Date: Mon, 16 Sep 1996 16:11:42 -0500 (CDT) Cc: kurt@cyberbeach.net, hackers@FreeBSD.org In-Reply-To: <199609161444.KAA16111@etinc.com> from Dennis at "Sep 16, 96 10:44:34 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 Dennis wrote: > >I've been having problems getting some 2.1.5-RELEASE systems outputting data > >to the net. I've since brought up a machine on 2.1-RELEASE and put a > >plain-jane default apache process on the box. > > > >If people could try resolving http://wave.cyberbeach.net and drop me a > >message outlining their success/failure I would be appreciative. > > Perhaps unrelated....but I've noticed if I configure IP firewalling into the > kernel > the default seems to be that the system cant do anything. Can anyone outline > why that is.... Yes, Because the default rule is to deny all from all. Therefore you have to add rules to let yourself talk to the world. > > Dennis 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 Sep 16 14:19:45 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA09147 for hackers-outgoing; Mon, 16 Sep 1996 14:19:45 -0700 (PDT) Received: from seabass.progroup.com (catfish.progroup.com [206.24.122.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA09138 for ; Mon, 16 Sep 1996 14:19:41 -0700 (PDT) Received: (from craig@localhost) by seabass.progroup.com (8.7.5/8.6.12) id OAA27337 for hackers@FreeBSD.org; Mon, 16 Sep 1996 14:19:25 -0700 (PDT) Message-Id: <199609162119.OAA27337@seabass.progroup.com> Subject: Re: Adding a second NCR 810 controller To: hackers@FreeBSD.org Date: Mon, 16 Sep 1996 14:19:25 -0700 (PDT) From: "Craig Shaver" Reply-To: hackers@FreeBSD.org In-Reply-To: <199609170052.AAA15503@al.imforei.apana.org.au> from "Peter Childs" at Sep 17, 96 00:52:52 am X-Mailer: ELM [version 2.4 PL25 ME8b] 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 > > > In article <199609161051.MAA11794@iaehv.IAEhv.nl> you wrote: > > : Hi, > > Gday! > > : What do I need to do to add a second NCR 810 controller to a 2.1.5 system? > > Just chuck it in. Both cards can be set to INT A, since the interupts > are unique for each PCI slot. > Do you need to rebuild the kernel? In my kernel I added a line for the 2nd NCR controller: controller ncr0 controller ncr1 And then I rebuilt the kernel. Is this an unnecessary step? Thanks, -- Craig Shaver (craig@progroup.com) (415)390-0654 Productivity Group POB 60458 Sunnyvale, CA 94088 From owner-freebsd-hackers Mon Sep 16 15:15:02 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA13068 for hackers-outgoing; Mon, 16 Sep 1996 15:15:02 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA13052 for ; Mon, 16 Sep 1996 15:14:51 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id HAA29847; Tue, 17 Sep 1996 07:29:45 +1000 Date: Tue, 17 Sep 1996 07:29:45 +1000 From: Bruce Evans Message-Id: <199609162129.HAA29847@godzilla.zeta.org.au> To: darrylo@hpnmhjw.sr.hp.com, hackers@freefall.freebsd.org Subject: Re: fdisk changes, anyone? Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >[ One area of concern is that I'm a bit unclear on the start/end address > requirements. Right now, start offsets are being rounded up to an > head boundary, but end addresses are being rounded down to major > cylinder boundaries (every head*sector chunk). Is this right? ] End addressses must be rounded to a cylinder boundary so that the ending h/s values are maximal so that FreeBSD can determine the geometry by looking at the ending h/s values. I don't know of any requirements for rounding start addresses, except that some MBR extensions abuse the usual DOS rounding by taking more than 1 sector. Bruce From owner-freebsd-hackers Mon Sep 16 15:23:15 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA14122 for hackers-outgoing; Mon, 16 Sep 1996 15:23:15 -0700 (PDT) Received: from iaehv.IAEhv.nl (root@iaehv.IAEhv.nl [194.151.64.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA14109 for ; Mon, 16 Sep 1996 15:23:09 -0700 (PDT) Received: from LOCAL (wjw@localhost) by iaehv.IAEhv.nl (8.6.13/1.63); pid 8273 on Tue, 17 Sep 1996 00:20:40 +0200; id AAA08273 efrom: wjw; eto: UNKNOWN From: wjw@IAEhv.nl (Willem Jan Withagen) Message-Id: <199609162220.AAA08273@iaehv.IAEhv.nl> Subject: Re: Second NCR card To: se@zpr.uni-koeln.de (Stefan Esser) Date: Tue, 17 Sep 1996 00:20:39 +0200 (MET DST) Cc: admin@IAEhv.nl, hackers@freebsd.org In-Reply-To: <199609161840.UAA01630@x14.mi.uni-koeln.de> from "Stefan Esser" at Sep 16, 96 08:40:14 pm X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It was all too simple. There'll be a day when you do not even have to think using FreeBSD. :-) You ( Stefan Esser ) write: => > But how do I get a second NCR connected in a BSD system. => => Just plug it into an empty PCI slot :) => => > I can assign a different IRQ to INT A, is that enough to boot the board? => => The PCI interrupts are not connected between slots. => PCI IntA of each slot is usually connected to the => chip set, where it is routed to the ISA interrupt => controller. Since there are not enough free IRQs, => not every PCI bus line can be assigned an unique => IRQ, but PCI supports shared interrupts, and would => work even if all IntA lines happened to trigger the => same IRQ ... => => > Does the kernel need a ncr1 device? => => No, one is sufficient to include the driver, and it => will support any numebr of cards. (Well, there is an => arbitrary limit of 4 cards, but it will only cost => in the order of 4 bytes for each additional card, => so I mightjust rise that limit to 16 or 64 :) => => Let me know if you have any problems with your second => NCR card! No problems at all. Other than the fact that now the second card is considered the first controller. So we had to move the connectors to the new controller. But the system is up and running: ncr0: 1 Conner 1GB 2 XP34000 4Gb Quantums 1 4-16Gb Sony DAT ncr1: 5 CD-roms. => > PS: If ever you get around Eindhoven, drop in to see our ISP shop. => > This will be greatly apriciated. Koeln is not that far away. Well This holds for any serious FreeBSD guru/hacker/friend: Plenty of Coffee => Maybe I'll really come to Eindhoven some day, since => a former colleague is living only some ten kilometers => away ... See you soon. => > Full Internet connectivity for only fl 12.95 a month. => => PS: Full connectivity ? That's a very good price !!! Well that's no T1 connectivity, but you'll get around on the net: Email/WWW/more and even UUCP. 4 hours free of charge, more fl 3,- /hour. (that's the catch :-)) --WjW -- Internet Access Eindhoven BV., voice: +31-40-2438330, data: +31-40-2439436 P.O. 928, 5600 AX Eindhoven, The Netherlands Full Internet connectivity for only fl 12.95 a month. Call now, and login as 'new'. From owner-freebsd-hackers Mon Sep 16 15:29:39 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA14983 for hackers-outgoing; Mon, 16 Sep 1996 15:29:39 -0700 (PDT) Received: from mongoose.bostic.com (bostic@mongoose.BSDI.COM [205.230.230.129]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA14970 for ; Mon, 16 Sep 1996 15:29:34 -0700 (PDT) Received: (from bostic@localhost) by mongoose.bostic.com (8.7.4/8.7.3) id RAA25036; Mon, 16 Sep 1996 17:14:19 -0400 (EDT) Date: Mon, 16 Sep 1996 17:14:19 -0400 (EDT) From: Keith Bostic Message-Id: <199609162114.RAA25036@mongoose.bostic.com> To: bostic@bsdi.com Subject: nex/nvi version 1.76 available Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Version 1.76 of nex/nvi is now available. The changes in nvi 1.76 are entirely bug and compatibility fixes. If you're interested in a further review of the changes that have been made, a complete change log is included with the distribution, in the file docs/changelog. Version 1.76 is available for anonymous ftp from the usual two sites. ftp.cs.berkeley.edu:ucb/4bsd/nvi-1.76.tar.gz ftp.bostic.com:pub/nvi-1.76.tar.gz (The UC Berkeley site is likely to provide faster transfer speeds.) Note that version 1.76 has replaced the previous "stable" version, version 1.71. Please let me know if you have any problems, and thanks for using nvi! --keith From owner-freebsd-hackers Mon Sep 16 15:57:57 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA18127 for hackers-outgoing; Mon, 16 Sep 1996 15:57:57 -0700 (PDT) Received: from zeus.xtalwind.net (h-advance.x31.infi.net [206.27.115.54]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA18117; Mon, 16 Sep 1996 15:57:51 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by zeus.xtalwind.net (8.7.5/8.7.3) with SMTP id SAA01171; Mon, 16 Sep 1996 18:57:26 -0400 (EDT) Date: Mon, 16 Sep 1996 18:57:26 -0400 (EDT) From: jack To: Jeffrey Barber cc: "'freebsd-hardware@FreeBSD.org'" , "'hackers@FreeBSD.ORG'" Subject: Re: Very Slow Ethernet Link In-Reply-To: <01BBA3A2.11B93340@jabpc.rtfm.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 16 Sep 1996, Jeffrey Barber wrote: > Ok, I just installed FreeBSD 2.1 and boy this is slow, Really? >Example: > > bash$ ping localhost > > PING localhost (127.0.0.1): 56 data bytes > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.356 ms > 64 bytes from 127.0.0.1: icmp_seq=1 ttl=255 time=0.342 ms > 64 bytes from 127.0.0.1: icmp_seq=2 ttl=255 time=0.362 ms > 64 bytes from 127.0.0.1: icmp_seq=3 ttl=255 time=0.349 ms > > --- localhost.arctic.net ping statistics --- > 6 packets transmitted, 6 packets received, 0% packet loss > round-trip min/avg/max = 0.342/0.349/0.362 ms > > > On my Linux box I get a ping response of: > > PING localhost (127.0.0.1): 56 data bytes > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=1.1 ms > 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.9 ms > 64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.9 ms > 64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=1.0 ms > > Big difference here. Please shed some light on this for me. FreeBSD averages 0 POINT 349ms Linux averages 0 POINT 95ms. FreeBSD's SLOWEST was 0 POINT 362 ms Linux's FASTEST was 0 POINT 9ms. Let's round FBSD's numbers to the same number of significant digits. FBSD Linux 0.4ms 1.1ms 0.3ms 0.9ms 0.4ms 0.9ms 0.3ms 1.0ms Which one is slow? -------------------------------------------------------------------------- Jack O'Neill Finger jacko@onyx.xtalwind.net or jack@xtalwind.net http://www.xtalwind.net/~jacko/pubpgp.html #include 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 Mon Sep 16 15:58:18 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA18191 for hackers-outgoing; Mon, 16 Sep 1996 15:58:18 -0700 (PDT) Received: from rock.rtfm.com (guest@rock.anchorage.net [204.17.241.163]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA18181; Mon, 16 Sep 1996 15:58:13 -0700 (PDT) Received: from jabpc.rtfm.com (jabpc.rtfm.com [199.237.0.200]) by rock.rtfm.com (8.6.12/8.6.9) with SMTP id OAA05494; Mon, 16 Sep 1996 14:53:31 -0300 Received: by jabpc.rtfm.com with Microsoft Mail id <01BBA3DF.D5124740@jabpc.rtfm.com>; Mon, 16 Sep 1996 15:00:43 -0800 Message-ID: <01BBA3DF.D5124740@jabpc.rtfm.com> From: Jeffrey Barber To: "'freebsd-hardware@FreeBSD.org'" , "'hackers@FreeBSD.ORG'" Subject: Slow Etherlink Date: Mon, 16 Sep 1996 15:00:41 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk OK, If we can get past all the sarcasim bull shit! I realize that the = ping I showed for Linux seems to be slower than FreeBSD but the point is = that I have faster telnet response from Linux than I do FreeBSD. For the = more serious ppl who want to help. Let me rephrase my question: Why = would pinging and telneting to FreeBSD be slower than that of a Linux = box? FreeBSD: bash$ ifconfig -a lp0: flags=3D8810 mtu 1500 ep0: flags=3D863 mtu 1500 inet 19.51.13.1 netmask 0xffffff00 broadcast 19.51.13.255 lo0: flags=3D8009 mtu 16384 inet 127.0.0.1 netmask 0xff000000=20 sl0: flags=3Dc010 mtu 552 tun0: flags=3D8010 mtu 1500 PING localhost (127.0.0.1): 56 data bytes 64 bytes from 127.0.0.1: icmp_seq=3D0 ttl=3D255 time=3D0.356 ms 64 bytes from 127.0.0.1: icmp_seq=3D1 ttl=3D255 time=3D0.342 ms 64 bytes from 127.0.0.1: icmp_seq=3D2 ttl=3D255 time=3D0.362 ms 64 bytes from 127.0.0.1: icmp_seq=3D3 ttl=3D255 time=3D0.349 ms Linux: PING localhost (127.0.0.1): 56 data bytes 64 bytes from 127.0.0.1: icmp_seq=3D0 ttl=3D64 time=3D1.1 ms 64 bytes from 127.0.0.1: icmp_seq=3D1 ttl=3D64 time=3D0.9 ms 64 bytes from 127.0.0.1: icmp_seq=3D2 ttl=3D64 time=3D0.9 ms 64 bytes from 127.0.0.1: icmp_seq=3D3 ttl=3D64 time=3D1.0 ms I have never seen the SIMPLEX entries before on other OS's. Can this be = the problem or no? I have a 3com Etherlink III isa card installed the = FreeBSD system of which I had in a Linux box previously. Comments on trouble shooting this would be nice. Thanks From owner-freebsd-hackers Mon Sep 16 16:05:06 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA18650 for hackers-outgoing; Mon, 16 Sep 1996 16:05:06 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA18644 for ; Mon, 16 Sep 1996 16:05:03 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id JAA00146; Tue, 17 Sep 1996 09:04:29 +1000 Date: Tue, 17 Sep 1996 09:04:29 +1000 From: Bruce Evans Message-Id: <199609162304.JAA00146@godzilla.zeta.org.au> To: bde@zeta.org.au, SimsS@Infi.Net Subject: Re: Problem with sio0 Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I've stuffed a couple of diagnostic printf's into sio.c and have = >empirically proven that the probe on a Compaq LTE/Elite returns 1's in = >failures[5] and failures[8]. That is to say, with isa_irq_pending. This says that the interrupt being tested for arrives late (after it is masked in the UART :-(). >A couple more minutes under the microscope shows that the sio0 probe is = >being called with IRQ=3D0x10, even though the kernel's configed as IRQ4 = >(and verified by a boot -c. FWIW: the sio1 probe is called with IRQ = >0x08. I'm not sure what 3D0x10 is. IRQ4 _is_ 0x10 (see /usr/src/sys/i386/isa/isa.h) so 0x10 is the default. failures[8] says that probing the port probabky caused an IRQ4, so IRQ4 is probably correct. >So.... Not knowing ANYTHING, I offer the following question: how / = >where does the *dev structure get filled in before being passed into = >sioprobe()? It appears that that's where the failure starts, but I'm in = >*way* over my head.... The structure is initialized at compile time and not changed unless you use -c. I don't think the problem is there. Bruce From owner-freebsd-hackers Mon Sep 16 16:16:23 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA19184 for hackers-outgoing; Mon, 16 Sep 1996 16:16:23 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA19178 for ; Mon, 16 Sep 1996 16:16:19 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id QAA18050 for ; Mon, 16 Sep 1996 16:15:52 -0700 (PDT) Message-Id: <199609162315.QAA18050@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: hackers@freebsd.org Subject: BSDI vs. FreeBSD ... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 16 Sep 1996 16:15:51 -0700 From: Amancio Hasty Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is with respect of easing the configuration of pppd on FreeBSD: >I run both BSDi and FreeBSD, and the only reason I use the BSDi is for a >terminal server, since the ppp is easier to setup than FreeBSD's. All my >other servers run FreeBSD. If FreeBSD's ppp was as stable and easy to setup >as BSDi's was, I would drop the BSDi completely, since the scripts between the >two are not that much different as far as maintaining the system. In fact, I >have rewritten most of the scripts on both my FreeBSD and BSDi servers to work >more closely with the way I prefer to work anyway. > >------------------------------------------------------------------------ > Jim Sloan jsloan@livenet.net > Vice President > LiveNet, Inc. > 413 Davis St. Suite 106 Full Service Internet Provider > Virginia Beach VA 23462 Dialup and dedicated connections > Ph: 804-499-9328 Virtual Web, Email, and FTP hosting > http://www.livenet.net info@livenet.net webmaster@livenet.net >--------------------------------------------------------- From owner-freebsd-hackers Mon Sep 16 16:21:45 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA19553 for hackers-outgoing; Mon, 16 Sep 1996 16:21:45 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA19547; Mon, 16 Sep 1996 16:21:42 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id QAA18099; Mon, 16 Sep 1996 16:21:05 -0700 (PDT) Message-Id: <199609162321.QAA18099@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: Jeffrey Barber cc: "'freebsd-hardware@FreeBSD.org'" , "'hackers@FreeBSD.ORG'" Subject: Re: Slow Etherlink In-reply-to: Your message of "Mon, 16 Sep 1996 15:00:41 -0800." <01BBA3DF.D5124740@jabpc.rtfm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 16 Sep 1996 16:21:05 -0700 From: Amancio Hasty Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >From The Desk Of Jeffrey Barber : > OK, If we can get past all the sarcasim bull shit! I realize that the = > ping I showed for Linux seems to be slower than FreeBSD but the point is = Try not to post bull shit posts. If indeed the FreeBSD box is slower than the Linux box I would start by posting the actual measurements which show the results indicating your assumptions. Also, state the configuration of both the Linux box and the FreeBSD box. Amancio From owner-freebsd-hackers Mon Sep 16 16:23:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA19662 for hackers-outgoing; Mon, 16 Sep 1996 16:23:25 -0700 (PDT) Received: (from jmb@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA19656; Mon, 16 Sep 1996 16:23:24 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199609162323.QAA19656@freefall.freebsd.org> Subject: Re: Slow Etherlink To: jab@rock.anchorage.net (Jeffrey Barber) Date: Mon, 16 Sep 1996 16:23:23 -0700 (PDT) Cc: hackers@FreeBSD.org In-Reply-To: <01BBA3DF.D5124740@jabpc.rtfm.com> from "Jeffrey Barber" at Sep 16, 96 03:00:41 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Jeffrey Barber wrote: > > OK, If we can get past all the sarcasim bull shit! I realize that the = > ping I showed for Linux seems to be slower than FreeBSD but the point is = > that I have faster telnet response from Linux than I do FreeBSD. For the = > more serious ppl who want to help. Let me rephrase my question: Why = > would pinging and telneting to FreeBSD be slower than that of a Linux = > box? can your provide more information? you are telneting from a _____ to a _____ (fill in OS). the FreeBSD box is running _____ (fill in with "uname -a") the other box is running ______ you have tcp_extensions turned of of off (please check in /etc/sysconfig for a line that starts "tcp_extensions") alternately run "sysctl -a | grep tcp.rfc" if they both equal 1 they are turned on. we really need more information to answer your question. i am very sorry about the amounct of flak you got. lastly, if you can mail in the output of "dmesg" that would help too. jmb -- Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG FreeBSD--4.4BSD Unix for PC clones, source included. http://www.freebsd.org/ PGP 2.6.2 Fingerprint: 31 57 41 56 06 C1 40 13 C5 1C E3 E5 DC 62 0E FB From owner-freebsd-hackers Mon Sep 16 16:47:06 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA20621 for hackers-outgoing; Mon, 16 Sep 1996 16:47:06 -0700 (PDT) Received: from orion.webspan.net (root@orion.webspan.net [206.154.70.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA20614; Mon, 16 Sep 1996 16:47:02 -0700 (PDT) Received: from localhost (gpalmer@localhost [127.0.0.1]) by orion.webspan.net (8.7.5/8.6.12) with SMTP id TAA28206; Mon, 16 Sep 1996 19:46:27 -0400 (EDT) X-Authentication-Warning: orion.webspan.net: Host gpalmer@localhost [127.0.0.1] didn't use HELO protocol To: Jeffrey Barber cc: "'freebsd-hardware@FreeBSD.org'" , "'hackers@FreeBSD.ORG'" From: "Gary Palmer" Subject: Re: Slow Etherlink In-reply-to: Your message of "Mon, 16 Sep 1996 15:00:41 -0800." <01BBA3DF.D5124740@jabpc.rtfm.com> Date: Mon, 16 Sep 1996 19:46:27 -0400 Message-ID: <28202.842917587@orion.webspan.net> Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Jeffrey Barber wrote in message ID <01BBA3DF.D5124740@jabpc.rtfm.com>: > OK, If we can get past all the sarcasim bull shit! Perhaps you should phrase your questions better and provide more relevant information in that case. Complaining about network speed, and then including results which contradict your problem is BOUND to get sarcastic responses! > I realize that the > ping I showed for Linux seems to be slower than FreeBSD but the point is > that I have faster telnet response from Linux than I do FreeBSD. For the > more serious ppl who want to help. Let me rephrase my question: Why > would pinging and telneting to FreeBSD be slower than that of a Linux > box? Why ask about ethernet speed / response times and provide lo0 (loopback) response times? They are two TOTALLY different interfaces, and are TOTALLY unrelated! (well, not totally, but they follow different code paths in the kernel after a certain point) > PING localhost (127.0.0.1): 56 data bytes > 64 bytes from 127.0.0.1: icmp_seq=3D0 ttl=3D255 time=3D0.356 ms > 64 bytes from 127.0.0.1: icmp_seq=3D1 ttl=3D255 time=3D0.342 ms > 64 bytes from 127.0.0.1: icmp_seq=3D2 ttl=3D255 time=3D0.362 ms > 64 bytes from 127.0.0.1: icmp_seq=3D3 ttl=3D255 time=3D0.349 ms > > Linux: > > PING localhost (127.0.0.1): 56 data bytes > 64 bytes from 127.0.0.1: icmp_seq=3D0 ttl=3D64 time=3D1.1 ms > 64 bytes from 127.0.0.1: icmp_seq=3D1 ttl=3D64 time=3D0.9 ms > 64 bytes from 127.0.0.1: icmp_seq=3D2 ttl=3D64 time=3D0.9 ms > 64 bytes from 127.0.0.1: icmp_seq=3D3 ttl=3D64 time=3D1.0 ms > I have never seen the SIMPLEX entries before on other OS's. Can this be = > the problem or no? I have a 3com Etherlink III isa card installed the = > FreeBSD system of which I had in a Linux box previously. AHA! USEFUL INFORMATION ALERT!!!!! >From the file /sys/i386/conf/LINT: # ep: 3Com 3C509 (buggy) (3c509 == EtherLink III) The driver in FreeBSD isn't up to much I'm afraid, and has been slated for a re-write for a while. Unfortunately, issues such as kernel stability tend to take precidence. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-hackers Mon Sep 16 16:48:03 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA20774 for hackers-outgoing; Mon, 16 Sep 1996 16:48:03 -0700 (PDT) Received: from igw2.watson.ibm.com (igw2.watson.ibm.com [129.34.139.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA20703 for ; Mon, 16 Sep 1996 16:47:59 -0700 (PDT) Received: from mailhub1.watson.ibm.com (mailhub1.watson.ibm.com [9.2.249.31]) by igw2.watson.ibm.com (8.7.4/8.7.1) with ESMTP id TAA17169 for ; Mon, 16 Sep 1996 19:48:21 -0400 Received: from hawpub1.watson.ibm.com (hawpub1.watson.ibm.com [9.2.90.32]) by mailhub1.watson.ibm.com (8.7.1/09-08-96) with SMTP id TAA511449; Mon, 16 Sep 1996 19:47:51 -0400 Received: by hawpub1.watson.ibm.com (AIX 3.2/UCB 5.64/6/25/96) id AA47671; Mon, 16 Sep 1996 19:47:50 -0400 From: kavitha Message-Id: <9609162347.AA47671@hawpub1.watson.ibm.com> Subject: Device Driver resources To: freebsd-hackers@freebsd.org Date: Mon, 16 Sep 1996 19:47:49 -0400 (EDT) Cc: kms@watson.ibm.com, kavitha@watson.ibm.com X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk For a PCMCIA token device driver, I need 2 memory base addresses. Is there any way to specify 2 mem_base address in the configuration file? If not, how do I get a kernel virtual address into which I can map a PCMCIA memory offset? Regards, Krish. From owner-freebsd-hackers Mon Sep 16 17:29:13 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA23504 for hackers-outgoing; Mon, 16 Sep 1996 17:29:13 -0700 (PDT) Received: from solar.os.com (craigs@solar.os.com [199.232.136.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA23480; Mon, 16 Sep 1996 17:29:03 -0700 (PDT) Received: (from craigs@localhost) by solar.os.com (8.7/8.7.0) id UAA30316; Mon, 16 Sep 1996 20:31:05 -0400 Date: Mon, 16 Sep 1996 20:31:04 -0400 From: Craig Shrimpton Subject: Re: Slow Etherlink To: Jeffrey Barber cc: "'freebsd-hardware@FreeBSD.org'" , "'hackers@FreeBSD.ORG'" In-Reply-To: <01BBA3DF.D5124740@jabpc.rtfm.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 16 Sep 1996, Jeffrey Barber wrote: > OK, If we can get past all the sarcasim bull shit! I realize that the ping >I showed for Linux seems to be slower than FreeBSD but the point is that I >have faster telnet response from Linux than I do FreeBSD. For the more >serious ppl who want to help. Let me rephrase my question: Why would >pinging and telneting to FreeBSD be slower than that of a Linux box? Do you mean slower on start up or just plain slower. A ping to the localhost will not tell you anything about telnet performance. They don't even use the same protocols (ICMP vs. TCP). If you mean slower to start, try looking at your IN-ADDR.ARPA setup. Improperly configured reverse DNS can make telnet crawl. One thing I will say about Linux is that it has superior screen display performance. So, if what you are complaining about is screen redraw speed, Linux is much faster than FreeBSD. However, the redraw slowness of FreeBSD does not show up under xterm. Maybe it's the syscons driver, try the other driver and see if that's faster. Do remember though, for routing functions and raw data transfers, FreeBSD blows the doors off of Linux. (and Cisco for that matter) Good Luck, Craig +------------------------------------+--------------------------------------+ | Craig Shrimpton | e-mail: craigs@os.com | | Orbit Systems | information: info@os.com | | Worcester, MA 508.753.8776 | http://www.os.com/ | +------------------------------------+--------------------------------------+ _/_/_/_/ _/_/_/_/ _/_/_/_/ _/_/_/_/ _/_/_/_/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/_/_/ _/_/_/_/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/_/_/_/ _/ _/ _/_/_/_/ _/_/_/_/ _/ Strategic Systems From owner-freebsd-hackers Mon Sep 16 17:34:28 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA23897 for hackers-outgoing; Mon, 16 Sep 1996 17:34:28 -0700 (PDT) Received: from saguaro.flyingfox.com (saguaro.flyingfox.com [204.188.109.253]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA23867; Mon, 16 Sep 1996 17:34:22 -0700 (PDT) Received: (from jas@localhost) by saguaro.flyingfox.com (8.6.12/8.6.10) id RAA07558; Mon, 16 Sep 1996 17:32:55 -0700 Date: Mon, 16 Sep 1996 17:32:55 -0700 From: Jim Shankland Message-Id: <199609170032.RAA07558@saguaro.flyingfox.com> To: gpalmer@FreeBSD.org, jab@rock.anchorage.net Subject: Re: Slow Etherlink Cc: freebsd-hardware@FreeBSD.org, hackers@FreeBSD.org Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > I have never seen the SIMPLEX entries before on other OS's. Can this be = > > the problem or no? I have a 3com Etherlink III isa card installed the = > > FreeBSD system of which I had in a Linux box previously. > > AHA! USEFUL INFORMATION ALERT!!!!! > > >From the file /sys/i386/conf/LINT: > > # ep: 3Com 3C509 (buggy) > > (3c509 == EtherLink III) > > The driver in FreeBSD isn't up to much I'm afraid, and has been slated > for a re-write for a while. Unfortunately, issues such as kernel > stability tend to take precidence. On the other hand, I've been running 4 3C509's in an old 486-DX2/66 box running 2.1.0 for about a year now, and it's been rock-solid. I no longer even have a monitor or keyboard plugged in to the box. >From time to time, it gets unplugged. We just plug it back in, and 45 seconds or so later, it's routing again. To call it stable would be an understatement. No sarcasm here; but I'm still waiting for a coherent description of the problem .... Jim Shankland Flying Fox Computer Systems, Inc. From owner-freebsd-hackers Mon Sep 16 17:48:36 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA24658 for hackers-outgoing; Mon, 16 Sep 1996 17:48:36 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA24649 for ; Mon, 16 Sep 1996 17:48:30 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id KAA27589; Tue, 17 Sep 1996 10:17:57 +0930 From: Michael Smith Message-Id: <199609170047.KAA27589@genesis.atrad.adelaide.edu.au> Subject: Re: Question on Porting Windows software to X To: khetan@iafrica.com (Khetan Gajjar) Date: Tue, 17 Sep 1996 10:17:57 +0930 (CST) Cc: schluntz@gromit.pinpt.com, hackers@FreeBSD.org In-Reply-To: from "Khetan Gajjar" at Sep 16, 96 10:40:22 pm 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 Khetan Gajjar stands accused of saying: > > On Mon, 16 Sep 1996, Sean J. Schluntz wrote: > > >Looking at a larger word processing application for windows (16bit not 32) > >like Word 6, WordPerfict 6 or WordStar. What do would you all think the > > Well, afaik, WordPerfect 6 is available for SCO Unix; with the > improved ibcs2 in -current, we can run the app fine - it's the ruddy Flex > License manager we can't get working. I'd pay for someone to get THAT > working! Has there been any progress on that ? > > Is/Has someone contacted Flex about it ? I tried, but they said sorry, > it's for SCO - not BSD. That's "Globetrotter", not "Flex". And the FlexLM is legendarily difficult to deal with. I've had reasonably helpful words with Globetrotter before, and I expect to again (I hope) later this year when they bring Flex out for Linux. (We use a Linux product that on other platforms is Flex'ed) Having said all that, I believe that the issues with the WP6 license manager were iBCS2 emulation problems, and that they were fixed some time back. (Nate?) > Khetan Gajjar [ http://www.iafrica.com/~khetan] -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Sep 16 18:07:28 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA25401 for hackers-outgoing; Mon, 16 Sep 1996 18:07:28 -0700 (PDT) Received: from Gatekeeper.Lamb.net (ulf@cat-food.Melmac.org [206.169.44.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA25394; Mon, 16 Sep 1996 18:07:25 -0700 (PDT) Received: (from ulf@localhost) by Gatekeeper.Lamb.net (8.7.5/8.7.3) id SAA03263; Mon, 16 Sep 1996 18:08:00 -0700 (PDT) From: Ulf Zimmermann Message-Id: <199609170108.SAA03263@Gatekeeper.Lamb.net> Subject: Re: Slow Etherlink To: jab@rock.anchorage.net (Jeffrey Barber) Date: Mon, 16 Sep 1996 18:08:00 -0700 (PDT) Cc: freebsd-hardware@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: <01BBA3DF.D5124740@jabpc.rtfm.com> from Jeffrey Barber at "Sep 16, 96 03:00:41 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 > OK, If we can get past all the sarcasim bull shit! I realize that the ping I >showed for Linux seems to be slower than FreeBSD but the point is that I have >faster telnet response from Linux than I do FreeBSD. For the more serious ppl >who want to help. Let me rephrase my question: Why would pinging and telneting >to FreeBSD be slower than that of a Linux box? Again, you show only pinging localhost, which is on the FreeBS host faster then on the shown Linux host. Again, pinging localhost DOESN'T go onto the Ethernet cable. > > FreeBSD: > bash$ ifconfig -a > > lp0: flags=8810 mtu 1500 > ep0: flags=863 mtu 1500 > inet 19.51.13.1 netmask 0xffffff00 broadcast 19.51.13.255 > lo0: flags=8009 mtu 16384 > inet 127.0.0.1 netmask 0xff000000 > sl0: flags=c010 mtu 552 > tun0: flags=8010 mtu 1500 > > PING localhost (127.0.0.1): 56 data bytes > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.356 ms > 64 bytes from 127.0.0.1: icmp_seq=1 ttl=255 time=0.342 ms > 64 bytes from 127.0.0.1: icmp_seq=2 ttl=255 time=0.362 ms > 64 bytes from 127.0.0.1: icmp_seq=3 ttl=255 time=0.349 ms > > Linux: > > PING localhost (127.0.0.1): 56 data bytes > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=1.1 ms > 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.9 ms > 64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.9 ms > 64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=1.0 ms > > I have never seen the SIMPLEX entries before on other OS's. Can this be the problem or no? I have a 3com Etherlink III isa card installed the FreeBSD system of which I had in a Linux box previously. > > Comments on trouble shooting this would be nice. How should we help you, if you don't tell what is the real problem ? > > Thanks > > Ulf. -------------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 Lamb Art Internet Services | http://www.Lamb.net/ | http://www.Alameda.net From owner-freebsd-hackers Mon Sep 16 18:48:04 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA27367 for hackers-outgoing; Mon, 16 Sep 1996 18:48:04 -0700 (PDT) Received: from freebsd.netcom.com (freebsd.netcom.com [198.211.79.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA27361 for ; Mon, 16 Sep 1996 18:48:02 -0700 (PDT) Received: by freebsd.netcom.com (8.6.12/SMI-4.1) id UAA29524; Mon, 16 Sep 1996 20:53:34 -0500 From: bugs@freebsd.netcom.com (Mark Hittinger) Message-Id: <199609170153.UAA29524@freebsd.netcom.com> Subject: Re: Slow Etherlink (fwd) To: hackers@freebsd.org Date: Mon, 16 Sep 1996 20:53:34 -0500 (CDT) X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk One extra thing to check is the firmware setting on your 3c5x9 cards. There is a setting for "server mode" and "client mode" on some cards. If you select "server mode" it will artificially throttle the interrupts (to keep a novell server from using all the cycles for packets). In "client mode" the card can interrupt the processor as fast as it needs to. I think it might be a legacy kind of parameter from the days when we just had 386 power. When I set my 3c5x9 cards to "client mode" I was able to obtain very good transfer rates. FYI Mark Hittinger Netcom/Dallas bugs@freebsd.netcom.com From owner-freebsd-hackers Mon Sep 16 19:03:19 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA28113 for hackers-outgoing; Mon, 16 Sep 1996 19:03:19 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id TAA28108; Mon, 16 Sep 1996 19:03:16 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id TAA03421; Mon, 16 Sep 1996 19:02:04 -0700 From: Terry Lambert Message-Id: <199609170202.TAA03421@phaeton.artisoft.com> Subject: Re: Slow Etherlink To: jab@rock.anchorage.net (Jeffrey Barber) Date: Mon, 16 Sep 1996 19:02:04 -0700 (MST) Cc: freebsd-hardware@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: <01BBA3DF.D5124740@jabpc.rtfm.com> from "Jeffrey Barber" at Sep 16, 96 03:00:41 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 > OK, If we can get past all the sarcasim bull shit! I realize that the = > ping I showed for Linux seems to be slower than FreeBSD but the point is = > that I have faster telnet response from Linux than I do FreeBSD. For the = > more serious ppl who want to help. Let me rephrase my question: Why = > would pinging and telneting to FreeBSD be slower than that of a Linux = > box? It shouldn't be. By "slower", do you mean: 1) Slower to make a TCP connection for Telnet? a) Check your rarp setup b) Check your DNS setup c) Check your hosts file d) Back off a version or two of BIND e) Back off a version of sendmail, or reset the sendmail option to prevent it verifying source addresses 2) Slower to fail in the no route to host case? a) Yes, this is because FreeBSD retries rather than giving up. For transient initial loss, this seems slower. The fix is to correct your circuit so you don't get transientinitial loss. b) In the case of a transient failure, the BSD behaviour will not lose the connection, where the Linux will. 3) Slower to respond to pings? a) This could be your source host b) Check your TCP extensions. If you have a bogus TCP/IP implementation that doesn't understand RFC 1323 or RFC 1644, or can't correctly ignore them if they are used, then you should turn them off. 4) Slower to start pinging? a) There is an option that controls "time to live" on packets. Man sysctl. > bash$ ifconfig -a > > lp0: flags=3D8810 mtu 1500 > ep0: flags=3D863 mtu 1500 > inet 19.51.13.1 netmask 0xffffff00 broadcast 19.51.13.255 > > I have never seen the SIMPLEX entries before on other OS's. Can this be = > the problem or no? I have a 3com Etherlink III isa card installed the = > FreeBSD system of which I had in a Linux box previously. It means it can't transmit and receive at the same time. This is a card "feature", and if you haven't seen it before, your other OS has been lying to you (or it's one of the drivers that needs updated). In general, SIMPLEX, if capable of being fixed via a driver interface (usually it is not, as noted above), will only affect unidirectional throughput, generally out of the machine, and generally only for real data transferred (ie: it's not your "ping" problem, whatever your "ping" problem is -- you haven't supplied enough information for us to 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 Mon Sep 16 19:31:19 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA29999 for hackers-outgoing; Mon, 16 Sep 1996 19:31:19 -0700 (PDT) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id TAA29988 for ; Mon, 16 Sep 1996 19:31:15 -0700 (PDT) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id WAA00795; Mon, 16 Sep 1996 22:30:22 -0400 Date: Mon, 16 Sep 1996 22:30:22 -0400 (EDT) From: "Ron G. Minnich" X-Sender: rminnich@terra To: freebsd-hackers@freebsd.org Subject: user-level distributed shared memory available for freebsd Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This system is called ZOUNDS. it's all user mode, no special sysadmin needed to use it, uses TCP, comes with manual and a sample app. It can exploit rfork if you have it in your 2.2+ system, provides a simple shared-file-descriptor rfork loadable module if you have earlier than 2.2, and for most cases doesn't have to have rfork anyways (There's only one specific case where it is helpful but not necessary). bugs to me, of course. ron Ron Minnich |"If you leave out all the killings, D.C. has as rminnich@sarnoff.com | low a crime rate as many cities" -- (609)-734-3120 | D.C. Mayor Marion Barry ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html From owner-freebsd-hackers Mon Sep 16 19:40:33 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA00704 for hackers-outgoing; Mon, 16 Sep 1996 19:40:33 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA00696; Mon, 16 Sep 1996 19:40:25 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id TAA08641; Mon, 16 Sep 1996 19:40:57 -0700 (PDT) Message-Id: <199609170240.TAA08641@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Jeffrey Barber cc: "'freebsd-hardware@FreeBSD.org'" , "'hackers@FreeBSD.ORG'" Subject: Re: Slow Etherlink In-reply-to: Your message of "Mon, 16 Sep 1996 15:00:41 -0800." <01BBA3DF.D5124740@jabpc.rtfm.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 16 Sep 1996 19:40:57 -0700 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >OK, If we can get past all the sarcasim bull shit! I realize that the = >ping I showed for Linux seems to be slower than FreeBSD but the point is = >that I have faster telnet response from Linux than I do FreeBSD. For the = >more serious ppl who want to help. Let me rephrase my question: Why = >would pinging and telneting to FreeBSD be slower than that of a Linux = >box? I'm going to assume that there is a real problem (which can't be infered from the data you provided). One of the common problems with the 3c509 is that it is easy to misconfigure the irq and yet still have the card appear to sort of work. The result is 0-1 _second_ round-trip times. Try pinging another host on your ethernet, and if this is the case, then you have a irq mismatch or conflict. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Mon Sep 16 20:26:15 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA03587 for hackers-outgoing; Mon, 16 Sep 1996 20:26:15 -0700 (PDT) Received: from solar.os.com (craigs@solar.os.com [199.232.136.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA03567; Mon, 16 Sep 1996 20:26:03 -0700 (PDT) Received: (from craigs@localhost) by solar.os.com (8.7/8.7.0) id XAA31028; Mon, 16 Sep 1996 23:33:07 -0400 Date: Mon, 16 Sep 1996 23:33:07 -0400 From: Craig Shrimpton Subject: Re: Slow Etherlink To: Terry Lambert cc: Jeffrey Barber , freebsd-hardware@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <199609170202.TAA03421@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 16 Sep 1996, Terry Lambert wrote: > > It means it can't transmit and receive at the same time. This is a card > "feature", and if you haven't seen it before, your other OS has been > lying to you (or it's one of the drivers that needs updated). > > In general, SIMPLEX, if capable of being fixed via a driver interface > (usually it is not, as noted above), will only affect unidirectional > throughput, generally out of the machine, and generally only for real > data transferred (ie: it's not your "ping" problem, whatever your "ping" > What cards are "synchronous?" I use SMC EtherPower PCI cards (de0) because they are basically plug and play under FreeBSD. I put 3 in a FBSD router box and they all worked first try automagically! Any idea if the SMC drivers are updateable? Craig +------------------------------------+--------------------------------------+ | Craig Shrimpton | e-mail: craigs@os.com | | Orbit Systems | information: info@os.com | | Worcester, MA 508.753.8776 | http://www.os.com/ | +------------------------------------+--------------------------------------+ From owner-freebsd-hackers Mon Sep 16 20:27:31 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA03688 for hackers-outgoing; Mon, 16 Sep 1996 20:27:31 -0700 (PDT) Received: from cssun.mathcs.emory.edu (cssun.mathcs.emory.edu [199.76.28.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA03678; Mon, 16 Sep 1996 20:27:24 -0700 (PDT) Received: (from gshapiro@localhost) by cssun.mathcs.emory.edu (8.7.5/8.6.9-940818.01cssun) id XAA14628; Mon, 16 Sep 1996 23:27:17 -0400 (EDT) From: Gregg Shapiro Message-Id: <199609170327.XAA14628@cssun.mathcs.emory.edu> Subject: automatically initiating apm and CPU idling questions To: freebsd-mobile@freebsd.org, freebsd-hackers@freebsd.org Date: Mon, 16 Sep 1996 23:27:16 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] 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 am running 2.1 on a Micron P166 mini-tower PC and am just about to upgrade to 2.1.5. My questions are: 1 - If I am running X, is there a way to initiate the APM functionality automatically after say my X server places my monitor into suspend mode ? Is this also possible if X is not running ? I can manually run zzz to put the CPU into sleep mode, but it would be great to do it automatically, (kinda like the way Windows 95 does it - sorry if I offended anybody by mentioning a lesser OS) 2 - Is there anyway to enable CPU Idling ? I know my CPU and video hardware support it because it works under Windows 95. But when I boot FreeBSD, it says that it is disabling CPU idling. 3 - Is there a way to automatically power off my PC after shutting down ? I have a "soft ?" power button on my motherboard that, under WIN 95 will turn off the power after exiting. Thanks a lot, Gregg -- Gregg Shapiro Emory University, Atlanta, GA email: gshapiro@mathcs.emory.edu From owner-freebsd-hackers Mon Sep 16 20:33:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA04122 for hackers-outgoing; Mon, 16 Sep 1996 20:33:34 -0700 (PDT) Received: from relay.hp.com (relay.hp.com [15.255.152.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA04117 for ; Mon, 16 Sep 1996 20:33:30 -0700 (PDT) Received: from srmail.sr.hp.com by relay.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA200071193; Mon, 16 Sep 1996 20:33:13 -0700 Received: from hpnmhjw.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA049561192; Mon, 16 Sep 1996 20:33:12 -0700 Received: from mina.sr.hp.com by hpnmhjw.sr.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA235811192; Mon, 16 Sep 1996 20:33:12 -0700 Message-Id: <199609170333.AA235811192@hpnmhjw.sr.hp.com> To: Bruce Evans Cc: hackers@freefall.freebsd.org Subject: Re: fdisk changes, anyone? In-Reply-To: Your message of "Tue, 17 Sep 1996 07:29:45 +1000." <199609162129.HAA29847@godzilla.zeta.org.au> Date: Mon, 16 Sep 1996 20:33:11 -0700 From: Darryl Okahata Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I don't know of any requirements for rounding start addresses, except > that some MBR extensions abuse the usual DOS rounding by taking more > than 1 sector. Thanks for the info. I'm unsure about the start address because the 2.2-snap-960801 /stand/sysinstall can create two different start offsets. If you use the sysinstall partition editor to create regular partitions, the start offset used falls on a cylinder boundary. If you tell sysinstall that you want to dedicate the entire disk to FreeBSD, but to use a standard, "true partition", the start offset falls on an head boundary. -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. From owner-freebsd-hackers Mon Sep 16 20:50:38 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA05101 for hackers-outgoing; Mon, 16 Sep 1996 20:50:38 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA05096 for ; Mon, 16 Sep 1996 20:50:32 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id UAA02458; Mon, 16 Sep 1996 20:50:29 -0700 (PDT) To: "Sean J. Schluntz" cc: hackers@freebsd.org Subject: Re: Question on Porting Windows software to X In-reply-to: Your message of "Mon, 16 Sep 1996 09:33:42 PDT." <2.2.32.19960916163342.0091e7c8@wallace.pinpt.com> Date: Mon, 16 Sep 1996 20:50:29 -0700 Message-ID: <2456.842932229@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Looking at a larger word processing application for windows (16bit not 32) > like Word 6, WordPerfict 6 or WordStar. What do would you all think the > difficulty level and approximate time would be required to port this app to > X if you had the full sources for the orriginal application. Well, having done that exact thing for Lotus's AmiPro word processor, I can say that it's hard. Even harder if the codebase in question is a legacy from some pure-windows shop. Were that the case, you'd almost certainly want to use a transition tool like Willows or Wind/U. That might at least hold X at arm's length while you grappled with the OS dependant bits. Jordan From owner-freebsd-hackers Mon Sep 16 22:08:14 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA08729 for hackers-outgoing; Mon, 16 Sep 1996 22:08:14 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA08721; Mon, 16 Sep 1996 22:08:08 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id OAA10729; Tue, 17 Sep 1996 14:56:00 +1000 Date: Tue, 17 Sep 1996 14:56:00 +1000 From: Bruce Evans Message-Id: <199609170456.OAA10729@godzilla.zeta.org.au> To: craigs@os.com, jab@rock.anchorage.net Subject: Re: Slow Etherlink Cc: freebsd-hardware@freebsd.org, hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >One thing I will say about Linux is that it has superior screen display >performance. So, if what you are complaining about is screen redraw >speed, Linux is much faster than FreeBSD. Really? Linux was 6-12 times slower last time I worked on speeding up syscons. >However, the redraw slowness >of FreeBSD does not show up under xterm. Perhaps you are noticing the redraw fastness of FreeBSD. Redraws for running vi over ethernet connections _seem_ to be very slow because there is a long pause after the data in the first packet is written. The pause is actually caused by delayed ACKs and may be avoided using the undocumented option TCP_ACK_HACK. This option was standard in FreeBSD-2.0 and in FreeBSD-current up to just before the release of 2.0.5. It was disabled because it caused problems with T/TCP. Linux has a similar option CONFIG_TCP_NAGLE_OFF. >Maybe it's the syscons driver, >try the other driver and see if that's faster. ... pcvt is much slower than syscons. Bruce Test notes and output: --- The test simply writes 2000 bytes of printable characters 1000 times. Other methods of writing to the screen are inherently slower (several lines can be written in the time that it takes to format and parse one escape sequence). ISA ET4000: 2.4MB/sec read, 5.9MB/sec write VLB ET4000/W32i: 6.8MB/sec read, 25.5MB/sec write PCI S3/868: 3.5MB/sec read, 23.1MB/sec write -o means stty flag -opost No-scroll: machine video O/S where real user sys speed --------- ------- -------------- --------- ----- ---- ----- ----- DX2/66 VLB ET4000/W32i FreeBSD-rcurrent offscreen-o 1.18 0.01 1.16 1.69 DX2/66 VLB ET4000/W32i FreeBSD-rcurrent onscreen-o 1.19 0.00 1.18 1.68 486/33 ISA ET4000 minix-1.6.25++ offscreen 2 0.01 1.45 1.37 486/33 ISA ET4000 minix-1.6.25++ onscreen 2 0.01 1.60 1.24 DX2/66 VLB ET4000/W32i FreeBSD-bcurrent offscreen 1.62 0.00 1.59 1.23 DX2/66 VLB ET4000/W32i FreeBSD-bcurrent onscreen 1.62 0.02 1.58 1.23 486/33 ISA ET4000 FreeBSD-bcurrent offscreen-o 2.28 0.03 2.24 0.88 486/33 ISA ET4000 FreeBSD-bcurrent onscreen-o 2.34 0.01 2.26 0.85 486/33 ISA ET4000 FreeBSD-current offscreen-o 2.50 0.00 2.46 0.80 486/33 ISA ET4000 FreeBSD-current onscreen-o 2.55 0.02 2.49 0.78 486/33 ISA ET4000 FreeBSD-bcurrent offscreen 3.17 0.00 3.15 0.63 486/33 ISA ET4000 FreeBSD-bcurrent onscreen 3.23 0.03 3.11 0.62 486/33 ISA ET4000 FreeBSD-current offscreen 3.48 0.03 3.41 0.57 486/33 ISA ET4000 FreeBSD-current onscreen 3.55 0.02 3.45 0.56 486/33 ISA ET4000 linux-1.1.36 offscreen 20.80 0.00 20.80 0.10 486/33 ISA ET4000 linux-1.1.36 onscreen 38.34 0.02 38.38 0.05 Scroll: machine video O/S where real user sys speed --------- ------- -------------- --------- ----- ---- ----- ----- 486/33 ISA ET4000 minix-1.6.25++ offscreen 2 0.00 1.70 1.18 486/33 ISA ET4000 minix-1.6.25++ onscreen 2 0.00 1.81 1.10 DX2/66 VLB ET4000/W32i FreeBSD-bcurrent offscreen-o 3.24 0.01 3.21 0.62 DX2/66 VLB ET4000/W32i FreeBSD-bcurrent onscreen-o 3.40 0.01 3.33 0.59 DX2/66 VLB ET4000/W32i FreeBSD-bcurrent offscreen 3.68 0.02 3.63 0.54 DX2/66 VLB ET4000/W32i FreeBSD-bcurrent onscreen 3.97 0.01 3.93 0.50 486/33 ISA ET4000 FreeBSD-bcurrent offscreen-o 5.38 0.02 5.32 0.37 486/33 ISA ET4000 FreeBSD-bcurrent onscreen-o 5.50 0.02 5.38 0.36 486/33 ISA ET4000 FreeBSD-current offscreen-o 5.71 0.02 5.64 0.35 486/33 ISA ET4000 FreeBSD-current onscreen-o 5.72 0.00 5.62 0.35 486/33 ISA ET4000 FreeBSD-bcurrent offscreen 6.42 0.03 6.36 0.31 486/33 ISA ET4000 FreeBSD-bcurrent onscreen 6.39 0.03 6.17 0.31 486/33 ISA ET4000 FreeBSD-current offscreen 6.68 0.02 6.62 0.30 486/33 ISA ET4000 FreeBSD-current onscreen 6.73 0.03 6.54 0.30 486/33 ISA ET4000 linux-1.1.36 offscreen 23.56 0.03 23.60 0.08 486/33 ISA ET4000 linux-1.1.36 onscreen 40.26 0.00 40.27 0.05 From owner-freebsd-hackers Mon Sep 16 22:13:26 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA08982 for hackers-outgoing; Mon, 16 Sep 1996 22:13:26 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA08968 for ; Mon, 16 Sep 1996 22:13:21 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id WAA08889; Mon, 16 Sep 1996 22:12:10 -0700 (PDT) Message-Id: <199609170512.WAA08889@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Terry Lambert cc: bde@zeta.org.au, proff@suburbia.net, freebsd-hackers@FreeBSD.org Subject: Re: attribute/inode caching In-reply-to: Your message of "Mon, 16 Sep 1996 11:05:55 PDT." <199609161805.LAA02580@phaeton.artisoft.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 16 Sep 1996 22:12:10 -0700 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> >> It could be hung off the vnode for the mounted device. I'm not sure if >> >> it isn't already. This problem is secondary. Repeated tree traversals >> >> aren't all that common, and you don't really want them to eat the buffer >> >> cache (you probably want to buffer precisely the inodes and directories >> >> that will be hit again a long time later in the same search, e.g., >> >> intermediate directories for a depth-first seach). >> > >> >It is not hung off the vnode for the device. It probably should not be, >> >in any case (there is no "device" for NFS, for instance). >> >> Inode blocks are hung off the device vnode. > >I find this hard to believe. This would imply a limitation of the device >size of the file size, since the adressable extent for a vnode is smaller >than the addressable extent for a device. Huh? In FreeBSD, the device is refered to via the device vnode. How do you think FFS does the I/O for the inode block? It uses the block device- special vnode. As for any implied size limitation, vnodes don't have any "size" associated with them. Anything (except the VM system) that deals with file offsets deals in 64bit quad_t's, and it doesn't matter if it's a file or a device or whatever. Depending on which version of the merged VM/buffer cache we're talking about, metadata may or may not be stored in VM pages. In all versions, however, it is cached in buffers (buffers can point to either malloced memory or VM pages). >Which value are you caliming is in error? It seems to me that if inode >blocks are hung of the device vnode (so why have the ihash?!?), then it >is an error to not limit the device size to the max file size. I think you're really starting to confuse things. The maximum file size is not a function of vnodes. We do have a problem with representing file offsets in the VM system beyond 31bits worth of pages (43bits total == 8TB), but this is hardly a concern. John may correct me on this, but I believe in the current scheme we do cache inode blocks in VM pages in -current. In 2.1.5, we couldn't because of the vm_page offset limitation. So for 2.1.5, we only cache inode blocks in malloced memory that is attached to buffers. Offsets in buffers are 40 bits large (31bits for signed long to hold the block number which is in units of 512 bytes (9bits)), this effectively limits all operations that involve struct buf's to 1TB, thus neither a device nor a file may be larger than this. We've had no compelling reason to fix this as it is more difficult than just changing the size of a daddr_t, and noone that I know of is using a 1TB filesystem. >The fact that the device size was allowed to be larger than the max file >size was one of the justifications John Dyson gave for not using caching >based on device/extent instead of (in addition to) vnode/extent in order >to keep the buffer cache unification of the vnode/extent mapping, but >resolve a lot of other issues. For instance, if the device vnode is >in fact a device/extent cache, then there is no need for the ihash, since >the inodes are determiistically layed out and thus indexable by fault. In >addition, the abilit to address device blocks by fault on the device vnode >means that vclean is totally unnecessary. I can't parse this. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Mon Sep 16 22:22:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA09432 for hackers-outgoing; Mon, 16 Sep 1996 22:22:34 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA09409; Mon, 16 Sep 1996 22:22:28 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.6.12/8.6.12) with SMTP id WAA13761; Mon, 16 Sep 1996 22:22:27 -0700 Date: Mon, 16 Sep 1996 22:22:26 -0700 (PDT) From: Jaye Mathisen To: hackers@freebsd.org, current@freebsd.org Subject: What bad things happen if I run 2.1 bins with 2.2-current kernel? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is this likely to work OK? I realize programs like ps and stuff will need rebuilding, but what about more "userland" type stuff? From owner-freebsd-hackers Mon Sep 16 23:21:13 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA12818 for hackers-outgoing; Mon, 16 Sep 1996 23:21:13 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA12812 for ; Mon, 16 Sep 1996 23:21:10 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id XAA04657 for ; Mon, 16 Sep 1996 23:20:59 -0700 (PDT) Message-Id: <199609170620.XAA04657@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: hackers@freebsd.org Subject: Win95 + FreeBSD hacker wanted Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 16 Sep 1996 23:20:59 -0700 From: Amancio Hasty Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Currently, I am working for a small startup whose emphasis is in the area of network multimedia and we need a couple of senior level software engineers to help out on both FreeBSD and Win95. We are located in Mountain View, California. Tnks -- Amancio Hasty Tel: 415-495-3046 Fax: 415-495-3046 Cellular: 415-309-8434 e-mail: hasty@star-gate.com Powered by FreeBSD From owner-freebsd-hackers Mon Sep 16 23:48:45 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA14612 for hackers-outgoing; Mon, 16 Sep 1996 23:48:45 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA14606 for ; Mon, 16 Sep 1996 23:48:40 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.7.5/8.7.3) id QAA01858; Tue, 17 Sep 1996 16:48:36 +1000 (EST) Date: Tue, 17 Sep 1996 16:48:34 +1000 (EST) From: "Daniel O'Callaghan" To: freebsd-hackers@freebsd.org Subject: IPFW sysconfig and netstart niceties Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Perhaps some committer who thinks that too many people are tripping over the "IPFW Policy Deny" would like to review the diffs to sysconfig and netstat below. It's only cosmetic, but appearances do count. Thanks, Danny *** sysconfig.orig Tue Sep 17 16:10:12 1996 --- sysconfig Tue Sep 17 16:10:02 1996 *************** *** 196,201 **** --- 196,202 ---- gateway=YES # If you want this host to be a firewall or otherwise filter IP, set to YES. + # If you wish to turn off filtering in the kernel, set to OFF. firewall=NO # Set to YES if you wish to check quotas. ----- *** netstart.orig Tue Sep 17 14:42:40 1996 --- netstart Tue Sep 17 16:08:22 1996 *************** *** 24,31 **** fi # If IP filtering ! if [ -n "$firewall" -a "x$firewall" != "xNO" -a -f /etc/rc.firewall ] ; then sh /etc/rc.firewall fi # --- 24,49 ---- fi # If IP filtering ! /sbin/ipfw flush > /dev/null 2>&1 ! ! if [ $? = 0 ] ; then ! # IPFIREWALL is in kernel ! if [ "x$firewall" = "xYES" -a -f /etc/rc.firewall ] ; then sh /etc/rc.firewall + else + if [ "x$firewall" = "xOFF" ] ; then + /sbin/ipfw add 65000 pass all from any to any + else + echo "Warning: ipfw in kernel not configured - all IP is blocked." + echo " Please read /etc/sysconfig and /etc/rc.firewall" + fi + fi + else + # IPFIREWALL is not in kernel + if [ "x$firewall" = "xYES" ] ; then + echo "Warning: ipfirewall not in kernel - IP filtering is not available." + fi + fi # From owner-freebsd-hackers Tue Sep 17 00:26:01 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA17112 for hackers-outgoing; Tue, 17 Sep 1996 00:26:01 -0700 (PDT) Received: from relay.philips.nl (ns.philips.nl [130.144.65.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA17102 for ; Tue, 17 Sep 1996 00:25:57 -0700 (PDT) Received: (from smap@localhost) by relay.philips.nl (8.6.9/8.6.9-950414) id JAA18441 for ; Tue, 17 Sep 1996 09:25:23 +0200 Received: from unknown(192.26.173.32) by ns.philips.nl via smap (V1.3+ESMTP) with ESMTP id sma017922; Tue Sep 17 09:22:05 1996 Received: from spooky.lss.cp.philips.com (spooky.lss.cp.philips.com [130.144.199.105]) by smtp.nl.cis.philips.com (8.6.10/8.6.10-0.9z-02May95) with ESMTP id JAA09396 for ; Tue, 17 Sep 1996 09:25:00 +0200 Received: (from guido@localhost) by spooky.lss.cp.philips.com (8.6.10/8.6.10-0.991c-08Nov95) id JAA06932 for freebsd-hackers@freebsd.org; Tue, 17 Sep 1996 09:22:02 +0200 From: Guido van Rooij Message-Id: <199609170722.JAA06932@spooky.lss.cp.philips.com> Subject: new if_vx driver on freefall To: freebsd-hackers@freebsd.org Date: Tue, 17 Sep 1996 09:22:01 +0200 (MET DST) Reply-To: Guido.vanRooij@nl.cis.philips.com 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 I've put the two following files on ftp://freefall.freebsd.org:/pub/inccoming: newif_vx.tgz newif_vx.tgz.README Ppl with hanging cards should try them out. There is a gross hack inside but I first need to get sepcs form 3com to identify what's going on. -Guido From owner-freebsd-hackers Tue Sep 17 01:09:44 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA19461 for hackers-outgoing; Tue, 17 Sep 1996 01:09:44 -0700 (PDT) Received: from mailgate ([202.159.65.166]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA19429; Tue, 17 Sep 1996 01:09:09 -0700 (PDT) Received: from manado.wasantara.net.id (manado.wasantara.net.id [202.159.87.163]) by mailgate (8.6.11/8.6.9) with ESMTP id OAA18467; Tue, 17 Sep 1996 14:57:35 +0700 Date: Tue, 17 Sep 1996 14:57:35 +0700 Received: from MANADO/SpoolDir by manado.wasantara.net.id (Mercury 1.21); 17 Sep 96 16:07:30 GMT+0800 Received: from SpoolDir by MANADO (Mercury 1.21); 17 Sep 96 16:07:11 GMT+0800 Received: from bandung.wasantara.net.id by manado.wasantara.net.id (Mercury 1.21); 17 Sep 96 16:07:08 GMT+0800 X-Sender: park@manado.wasantara.net.id (Unverified) X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Majordomo@FreeBSD.ORG From: park@manado.wasantara.net.id (Eka Kelana) Cc: freebsd-hackers@FreeBSD.ORG Message-ID: <2E9A7177A9@manado.wasantara.net.id> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk subscribe freebsd-hackers Eka From owner-freebsd-hackers Tue Sep 17 04:17:05 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA27790 for hackers-outgoing; Tue, 17 Sep 1996 04:17:05 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA27785 for ; Tue, 17 Sep 1996 04:17:01 -0700 (PDT) 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 NAA27924 for ; Tue, 17 Sep 1996 13:16:52 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id NAA29600 for freebsd-hackers@freefall.cdrom.com; Tue, 17 Sep 1996 13:23:51 +0200 Date: Tue, 17 Sep 1996 13:23:51 +0200 From: Christoph Kukulies Message-Id: <199609171123.NAA29600@gilberto.physik.rwth-aachen.de> To: freebsd-hackers@freefall.FreeBSD.org Subject: passing UDP broadcasts Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Is there a way to make FreeBSD pass UDP broadcasts between interfaces as it can be done with certain Cisco routers? I suspect not. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Tue Sep 17 04:31:20 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA28343 for hackers-outgoing; Tue, 17 Sep 1996 04:31:20 -0700 (PDT) Received: from diablo.ppp.de (diablo.ppp.de [193.141.101.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA28319; Tue, 17 Sep 1996 04:31:12 -0700 (PDT) Received: from allegro.lemis.de by diablo.ppp.de with smtp (Smail3.1.28.1 #1) id m0v2yMs-000QjzC; Tue, 17 Sep 96 13:31 MET DST From: grog@lemis.de (Greg Lehey) Organisation: LEMIS, Schellnhausen 2, 36325 Feldatal, Germany Phone: +49-6637-919123 Fax: +49-6637-919122 Received: (grog@localhost) by allegro.lemis.de (8.6.9/8.6.9) id MAA08085; Tue, 17 Sep 1996 12:42:43 +0200 Message-Id: <199609171042.MAA08085@allegro.lemis.de> Subject: Re: Slow Etherlink To: gpalmer@FreeBSD.org (Gary Palmer) Date: Tue, 17 Sep 1996 12:42:43 +0200 (MET DST) Cc: freebsd-hardware@FreeBSD.org (FreeBSD hardware Users), hackers@FreeBSD.org (FreeBSD Hackers) In-Reply-To: <28202.842917587@orion.webspan.net> from "Gary Palmer" at Sep 16, 96 07:46:27 pm X-Mailer: ELM [version 2.4 PL23] 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 Gary Palmer writes: > > Jeffrey Barber wrote in message ID > <01BBA3DF.D5124740@jabpc.rtfm.com>: >> OK, If we can get past all the sarcasim bull shit! > > Perhaps you should phrase your questions better and provide more > relevant information in that case. Complaining about network speed, > and then including results which contradict your problem is BOUND to > get sarcastic responses! I agree that the original poster gave no useful information and made a claim that would raise many FreeBSD users' hackles even if it were proven true, but all this correspondence hasn't done much to identify whether there is a performance problem. Let's summarize: 1. Ping localhost is a nice way to show the length of some of the internal paths through the kernel. Jeffrey seemed to confuse it with Ethernet. 2. The numbers he gave were irrelevant anyway. 3. He claims there are performance problems with telnet and ping. How about ftp? That's usually the clearest indication of ethernet throughput. 4. Gary thinks it might be due to the driver. Possibly that depends on the release, but just by chance I did some tests on Sunday, after installing Slowaris on my Sparc 2. *Those* results are interesting. Here are my results. They weren't really designed to show anything on FreeBSD, and since I only have one FreeBSD box up and running at the moment, they're only an indication. I ftp'd a 9 MB file (kernel with debugging symbols, FWIW) between 3 boxes: a P133 running FreeBSD 2.2-current, a P133 running BSD/OS 2.1, and the SparcStation 2 running SunOS 4.1.3 and Solaris 2.5. Here the results: copy to -> /dev/null /tmp/junk FreeBSD - SunOS 4 1020 kb/s 1020 kb/s FreeBSD - BSD/OS 1030 kb/s 930 kb/s FreeBSD - Solaris 2.5 462 kb/s 462 kb/s I wouldn't complain about the throughput of any of the BSD systems, though it's interesting how badly BSD/OS fared with a copy to a file. This was also the only result which varied significantly (between 835 and 960 kb/s) and may be related to the fact that this machine was also running X and the console on which I did the tests. The real surprise is Solaris 2.5. The SS2 only has 16 MB of memory, but all it was doing was receiving the file, so you'd think it could handle things better than that. Does anybody have any ideas? From owner-freebsd-hackers Tue Sep 17 04:39:46 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA28765 for hackers-outgoing; Tue, 17 Sep 1996 04:39:46 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.252]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA28760; Tue, 17 Sep 1996 04:39:43 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id NAA01084; Tue, 17 Sep 1996 13:39:13 +0200 (MET DST) To: Christoph Kukulies cc: freebsd-hackers@freefall.FreeBSD.org Subject: Re: passing UDP broadcasts In-reply-to: Your message of "Tue, 17 Sep 1996 13:23:51 +0200." <199609171123.NAA29600@gilberto.physik.rwth-aachen.de> Date: Tue, 17 Sep 1996 13:39:13 +0200 Message-ID: <1082.842960353@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199609171123.NAA29600@gilberto.physik.rwth-aachen.de>, Christoph Ku kulies writes: >Is there a way to make FreeBSD pass UDP broadcasts between interfaces >as it can be done with certain Cisco routers? >I suspect not. would vi /sys/netinet/*.c do ? Make it a sysctl while you're there :-) -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-hackers Tue Sep 17 04:41:10 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA28872 for hackers-outgoing; Tue, 17 Sep 1996 04:41:10 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.252]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA28866; Tue, 17 Sep 1996 04:41:06 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id NAA01102; Tue, 17 Sep 1996 13:40:35 +0200 (MET DST) To: grog@lemis.de (Greg Lehey) cc: gpalmer@FreeBSD.org (Gary Palmer), freebsd-hardware@FreeBSD.org (FreeBSD hardware Users), hackers@FreeBSD.org (FreeBSD Hackers) Subject: Re: Slow Etherlink In-reply-to: Your message of "Tue, 17 Sep 1996 12:42:43 +0200." <199609171042.MAA08085@allegro.lemis.de> Date: Tue, 17 Sep 1996 13:40:35 +0200 Message-ID: <1100.842960435@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In message <199609171042.MAA08085@allegro.lemis.de>, Greg Lehey writes: >I ftp'd a 9 MB file (kernel with >debugging symbols, FWIW) between 3 boxes: a P133 running FreeBSD >2.2-current, a P133 running BSD/OS 2.1, and the SparcStation 2 running >SunOS 4.1.3 and Solaris 2.5. Here the results: > > copy to -> /dev/null /tmp/junk > >FreeBSD - SunOS 4 1020 kb/s 1020 kb/s >FreeBSD - BSD/OS 1030 kb/s 930 kb/s >FreeBSD - Solaris 2.5 462 kb/s 462 kb/s > >The real surprise is Solaris 2.5. The SS2 only has 16 MB of memory, >but all it was doing was receiving the file, so you'd think it could >handle things better than that. Does anybody have any ideas? You should try a ss1000 then :-) Luckily it >can< be used as a boat-anchor. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-hackers Tue Sep 17 05:10:52 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA29864 for hackers-outgoing; Tue, 17 Sep 1996 05:10:52 -0700 (PDT) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA29859 for ; Tue, 17 Sep 1996 05:10:50 -0700 (PDT) Message-Id: <199609171210.FAA29859@freefall.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA275652167; Tue, 17 Sep 1996 22:09:27 +1000 From: Darren Reed Subject: Re: passing UDP broadcasts To: kuku@gilberto.physik.rwth-aachen.de (Christoph Kukulies) Date: Tue, 17 Sep 1996 22:09:26 +1000 (EST) Cc: freebsd-hackers@freefall.freebsd.org In-Reply-To: <199609171123.NAA29600@gilberto.physik.rwth-aachen.de> from "Christoph Kukulies" at Sep 17, 96 01:23:51 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In some mail from Christoph Kukulies, sie said: > > Is there a way to make FreeBSD pass UDP broadcasts between interfaces > as it can be done with certain Cisco routers? > I suspect not. have you tried "options DIRECTED_BROADCAST" in your kernel config ? From owner-freebsd-hackers Tue Sep 17 06:40:44 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA08727 for hackers-outgoing; Tue, 17 Sep 1996 06:40:44 -0700 (PDT) Received: (from julian@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA08716 for hackers; Tue, 17 Sep 1996 06:40:42 -0700 (PDT) Date: Tue, 17 Sep 1996 06:40:42 -0700 (PDT) From: Julian Elischer Message-Id: <199609171340.GAA08716@freefall.freebsd.org> To: hackers Subject: What's happenned to SUP5? Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk it seems to have gone away? julian From owner-freebsd-hackers Tue Sep 17 07:47:33 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA14725 for hackers-outgoing; Tue, 17 Sep 1996 07:47:33 -0700 (PDT) Received: from ihgw1.lucent.com (ihgw1.att.com [207.19.48.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA14708 for ; Tue, 17 Sep 1996 07:47:27 -0700 (PDT) Received: from nasvr1.cb.lucent.com by ihig1.firewall.lucent.com (SMI-8.6/EMS-L sol2) id JAA27678; Tue, 17 Sep 1996 09:38:03 -0500 Received: from cbsky.cb.att.com by nasvr1.cb.lucent.com (5.x/EMS-L sol2) id AA11469; Tue, 17 Sep 1996 10:24:53 -0400 Received: by cbsky.cb.att.com (5.x/EMS-1.1 Sol2) id AA08691; Tue, 17 Sep 1996 10:24:41 -0400 Date: Tue, 17 Sep 1996 10:24:41 -0400 Message-Id: <9609171424.AA08691@cbsky.cb.att.com> From: dob@naserver1.cb.lucent.com To: hackers@freebsd.org Cc: jdp@polstra.com Subject: CVSup Help! -- why did I get RCS files? Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm using the new 13.4 version of CVSup to cvsup current. (I believe it supped the wrong file; the RCS file instead of sending and making the update!) The make world following the CVSup showed the following error: cc -O2 -m486 -pipe -DLIBC_RCS -DSYSLIBC_RCS -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/var/usr/src/lib/libc/locale -DYP -c /var/usr/src/lib/libc/net/gethostbydns.c -o gethostbydns.o /var/usr/src/lib/libc/net/gethostbydns.c: In function `gethostanswer': /var/usr/src/lib/libc/net/gethostbydns.c:159: `res_hnok' undeclared (first use this function) /var/usr/src/lib/libc/net/gethostbydns.c:159: (Each undeclared identifier is reported only once /var/usr/src/lib/libc/net/gethostbydns.c:159: for each function it appears in.) /var/usr/src/lib/libc/net/gethostbydns.c:162: `res_dnok' undeclared (first use this function) /var/usr/src/lib/libc/net/gethostbydns.c:253: `res_hnok' used prior to declaration /var/usr/src/lib/libc/net/gethostbydns.c:287: `res_hnok' used prior to declaration /var/usr/src/lib/libc/net/gethostbydns.c:386: `RES_USE_INET6' undeclared (first use this function) /var/usr/src/lib/libc/net/gethostbydns.c: In function `_gethostbydnsname': /var/usr/src/lib/libc/net/gethostbydns.c:417: `IN6ADDRSZ' undeclared (first use this function) /var/usr/src/lib/libc/net/gethostbydns.c:465: `RES_USE_INET6' undeclared (first use this function) /var/usr/src/lib/libc/net/gethostbydns.c: In function `_gethostbydnsaddr': /var/usr/src/lib/libc/net/gethostbydns.c:504: `IN6ADDRSZ' undeclared (first use this function) /var/usr/src/lib/libc/net/gethostbydns.c:594: `RES_USE_INET6' undeclared (first use this function) *** Error code 1 Stop. I focussed on the missing IN6ADDRSZ define and found that it was in a file in /usr/src/include/arpa/nameser.h,v (an RCS file) but not in the nameser.h file itself. When I reviewed the CVSup log I found (when grepping for nameser.h): Checkout src/contrib/bind/include/arpa/nameser.h Create src/include/arpa/nameser.h,v This is my CVSupfile line for includes: src-include release=cvs host=cvsup.FreeBSD.org hostbase=/home base=/usr prefix=/usr compress delete old use-rel-suffix (I received ",v" files for many files in include, but none for anywhere else!) What gives? Why did I receive the RCS file and why didn't CVSup make the update? Thanks, Dan O'Brien (dmobrien@lucent.com) From owner-freebsd-hackers Tue Sep 17 07:55:31 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA15307 for hackers-outgoing; Tue, 17 Sep 1996 07:55:31 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA15296 for ; Tue, 17 Sep 1996 07:55:17 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.5/8.7.3) with ESMTP id HAA16068; Tue, 17 Sep 1996 07:55:11 -0700 (PDT) Message-Id: <199609171455.HAA16068@austin.polstra.com> To: dob@naserver1.cb.lucent.com cc: hackers@freebsd.org Subject: Re: CVSup Help! -- why did I get RCS files? In-reply-to: Your message of "Tue, 17 Sep 1996 10:24:41 EDT." <9609171424.AA08691@cbsky.cb.att.com> Date: Tue, 17 Sep 1996 07:55:11 -0700 From: John Polstra Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk dob@naserver1.cb.lucent.com wrote: > This is my CVSupfile line for includes: > > src-include release=cvs host=cvsup.FreeBSD.org hostbase=/home base=/usr prefix=/usr compress delete old use-rel-suffix > > (I received ",v" files for many files in include, but none for anywhere else!) > > > What gives? Why did I receive the RCS file and why didn't CVSup make the > update? Because you didn't specify the "tag" or "date" keyword in your supfile line. If you don't specify one or both of those, you get the RCS files. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-hackers Tue Sep 17 07:55:45 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA15336 for hackers-outgoing; Tue, 17 Sep 1996 07:55:45 -0700 (PDT) Received: from novell.com (prv-mail20.Provo.Novell.COM [137.65.40.4]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA15308 for ; Tue, 17 Sep 1996 07:55:33 -0700 (PDT) Received: from INET-PRV-Message_Server by novell.com with Novell_GroupWise; Tue, 17 Sep 1996 08:55:34 -0600 Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Tue, 17 Sep 1996 09:03:39 -0600 From: Darren Davis To: schluntz@gromit.pinpt.com, jkh@time.cdrom.com Cc: hackers@freebsd.org Subject: Re: Question on Porting Windows software to X - Reply Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Actually, with Corel's announcment that they will have a Java version of WordPerfect (though with less capability). I would just make sure the Java support in FreeBSD is up to the task of running it. Darren From owner-freebsd-hackers Tue Sep 17 08:14:45 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA16653 for hackers-outgoing; Tue, 17 Sep 1996 08:14:45 -0700 (PDT) Received: from main.gbdata.com (Main.GBData.COM [207.90.222.20]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA16647 for ; Tue, 17 Sep 1996 08:14:39 -0700 (PDT) Received: (from gclarkii@localhost) by main.gbdata.com (8.7.5/8.6.9) id KAA16313 for freebsd-hackers@freebsd.org; Tue, 17 Sep 1996 10:14:32 -0500 (CDT) From: Gary Clark II Message-Id: <199609171514.KAA16313@main.gbdata.com> Subject: Strange error on Freefall To: freebsd-hackers@freebsd.org Date: Tue, 17 Sep 1996 10:14:31 -0500 (CDT) 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 hello, I was on FreeFall earlier and ran into the following problem: freefall:gclarkii# ping srimain.srisoft.com PING srimain.srisoft.com (207.90.208.225): 56 data bytes 64 bytes from 207.90.208.225: icmp_seq=0 ttl=238 time=188.854 ms 64 bytes from 207.90.208.225: icmp_seq=1 ttl=238 time=209.467 ms ^C --- srimain.srisoft.com ping statistics --- 3 packets transmitted, 2 packets received, 33% packet loss round-trip min/avg/max = 188.854/199.160/209.467 ms freefall:gclarkii# telnet srimain.srisoft.com Trying 198.66.103.161... freefall:gclarkii# Why does the DNS return both variables consistly, one to ping and the other to telnet and rlogin??? Any ideas? 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 Tue Sep 17 08:38:37 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA17872 for hackers-outgoing; Tue, 17 Sep 1996 08:38:37 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA17863; Tue, 17 Sep 1996 08:38:32 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.5/8.7.3) with ESMTP id IAA16214; Tue, 17 Sep 1996 08:38:30 -0700 (PDT) Message-Id: <199609171538.IAA16214@austin.polstra.com> To: julian@freefall.freebsd.org Cc: hackers@freefall.freebsd.org Subject: Re: What's happenned to SUP5? In-reply-to: <199609171340.GAA08716@freefall.freebsd.org> Date: Tue, 17 Sep 1996 08:38:30 -0700 From: John Polstra Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > it seems to have gone away? It seems to have gotten renamed to "sup4" and "cvsup2". Also, I noticed that the machine itself was down for an extended time around September 12th. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-hackers Tue Sep 17 08:39:37 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA17955 for hackers-outgoing; Tue, 17 Sep 1996 08:39:37 -0700 (PDT) Received: from rock.rtfm.com (guest@rock.anchorage.net [204.17.241.163]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA17946; Tue, 17 Sep 1996 08:39:31 -0700 (PDT) Received: from jabpc.rtfm.com (jabpc.rtfm.com [199.237.0.200]) by rock.rtfm.com (8.6.12/8.6.9) with SMTP id HAA03125; Tue, 17 Sep 1996 07:34:23 -0300 Received: by jabpc.rtfm.com with Microsoft Mail id <01BBA46B.C28E9240@jabpc.rtfm.com>; Tue, 17 Sep 1996 07:42:21 -0800 Message-ID: <01BBA46B.C28E9240@jabpc.rtfm.com> From: Jeffrey Barber To: "'freebsd-hardware@FreeBSD.org'" , "'hackers@FreeBSD.ORG'" Subject: Very Slow Ethernet Link (FreeBSD v. Linux) Date: Tue, 17 Sep 1996 07:40:28 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Thanks for all the responses but still no luck. I had to put linux on = the system instead. But I did run a ftp test comparing FreeBSD to Linux. = The results: Using FreeBSD 2.1.0: ftp transfer with freebsd 1927427 bytes @ 4.2e+02 seconds 4.4kb/s Removing FreeBSD and Installed Linux 2.0 ftp transfer with Linux 1927427 bytes @ 3.05 seconds (6.2e+02 kb/s) = Wooo Wooo :) Using the exact same configuration and computer, the reults are in the = Linux favor by far. Don't know what the problem was. Thanks again. From owner-freebsd-hackers Tue Sep 17 09:28:52 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA20919 for hackers-outgoing; Tue, 17 Sep 1996 09:28:52 -0700 (PDT) Received: from gromit.pinpt.com (gromit.pinpt.com [205.179.195.7]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA20909 for ; Tue, 17 Sep 1996 09:28:46 -0700 (PDT) Received: from rover3.pinpt.com (gatemaster.pinpt.com [205.179.195.65]) by gromit.pinpt.com (8.7.5/8.6.12) with SMTP id JAA09345; Tue, 17 Sep 1996 09:27:17 -0700 (PDT) Message-Id: <2.2.32.19960917162642.009614e0@wallace.pinpt.com> X-Sender: schluntz@wallace.pinpt.com X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 17 Sep 1996 09:26:42 -0700 To: Darren Davis From: "Sean J. Schluntz" Subject: Re: Question on Porting Windows software to X - Reply Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 09:03 AM 9/17/96 -0600, you wrote: >Actually, with Corel's announcment that they will have a Java version of >WordPerfect (though with less capability). I would just make sure the >Java support in FreeBSD is up to the task of running it. Having worked with the Un*x version of WordPerfect my personal prefrence is to stay as far as possible from it. In my list of applications I only included it so people would understand the size of the application I was attempting to port. What we need is a _good_ WP for Un*x and X. -Sean --- Sean J. Schluntz eMail schluntz@pinpt.com Manager Support Services Phone (408) 997-6900 x222 PinPoint Software Corporation Fax (408) 323-2300 http://www.pinpt.com/ From owner-freebsd-hackers Tue Sep 17 09:35:49 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA21363 for hackers-outgoing; Tue, 17 Sep 1996 09:35:49 -0700 (PDT) Received: from silver.sms.fi (root@silver.sms.fi [194.111.122.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA21341; Tue, 17 Sep 1996 09:35:39 -0700 (PDT) Received: (from pete@localhost) by silver.sms.fi (8.7.5/8.6.9) id TAA14831; Tue, 17 Sep 1996 19:35:17 +0300 (EET DST) Date: Tue, 17 Sep 1996 19:35:17 +0300 (EET DST) Message-Id: <199609171635.TAA14831@silver.sms.fi> From: Petri Helenius To: Jeffrey Barber Cc: "'freebsd-hardware@FreeBSD.org'" , "'hackers@FreeBSD.ORG'" Subject: Very Slow Ethernet Link (FreeBSD v. Linux) In-Reply-To: <01BBA46B.C28E9240@jabpc.rtfm.com> References: <01BBA46B.C28E9240@jabpc.rtfm.com> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jeffrey Barber writes: > Thanks for all the responses but still no luck. I had to put linux on the system instead. But I did run a ftp test comparing FreeBSD to Linux. The results: > > Using FreeBSD 2.1.0: > > ftp transfer with freebsd 1927427 bytes @ 4.2e+02 seconds 4.4kb/s > > Removing FreeBSD and Installed Linux 2.0 > > ftp transfer with Linux 1927427 bytes @ 3.05 seconds (6.2e+02 kb/s) Wooo Wooo :) > > Using the exact same configuration and computer, the reults are in the Linux favor by far. > Don't know what the problem was. > You did a ftp to the loopback-address? This is a known problem with the MTU if you did. Set the MTU to 1500 or something more reasonable. Pete From owner-freebsd-hackers Tue Sep 17 09:40:05 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA21674 for hackers-outgoing; Tue, 17 Sep 1996 09:40:05 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA21616 for ; Tue, 17 Sep 1996 09:39:55 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id LAA07486; Tue, 17 Sep 1996 11:38:45 -0500 From: Joe Greco Message-Id: <199609171638.LAA07486@brasil.moneng.mei.com> Subject: Re: tun0 device To: SimsS@Infi.Net (Steve Sims) Date: Tue, 17 Sep 1996 11:38:44 -0500 (CDT) Cc: hackers@FreeBSD.org In-Reply-To: <199609161836.OAA27880@mh004.infi.net> from "Steve Sims" at Sep 16, 96 02:36:17 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Where's the seminal reference on the tunnel device? =20 > > `apropos tunnel` yields nada. Ditto for `man tun`. > > I don't have a *recent* handbook, but the one I have mentions it only in = > passing. > > Muchas Gracias in advance.... RTFS :-) It's actually quite trivial (at least from my experience) and quite nice: The tun device looks and acts like any other Point to Point network interface. Configure it as such. Open the corresponding /dev/tunX device and you can read packets that the system sent with your program, and/or you can inject packets back into the system's IP processing. It is fairly straightforward from what little I've played with it. ... JG From owner-freebsd-hackers Tue Sep 17 10:22:36 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA23498 for hackers-outgoing; Tue, 17 Sep 1996 10:22:36 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA23493; Tue, 17 Sep 1996 10:22:33 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA04369; Tue, 17 Sep 1996 10:21:18 -0700 From: Terry Lambert Message-Id: <199609171721.KAA04369@phaeton.artisoft.com> Subject: Re: Slow Etherlink To: craigs@os.com (Craig Shrimpton) Date: Tue, 17 Sep 1996 10:21:17 -0700 (MST) Cc: terry@lambert.org, jab@rock.anchorage.net, freebsd-hardware@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: from "Craig Shrimpton" at Sep 16, 96 11:33:07 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 > > It means it can't transmit and receive at the same time. This is a card > > "feature", and if you haven't seen it before, your other OS has been > > lying to you (or it's one of the drivers that needs updated). > > > > In general, SIMPLEX, if capable of being fixed via a driver interface > > (usually it is not, as noted above), will only affect unidirectional > > throughput, generally out of the machine, and generally only for real > > data transferred (ie: it's not your "ping" problem, whatever your "ping" > > > > > What cards are "synchronous?" I use SMC EtherPower PCI cards (de0) > because they are basically plug and play under FreeBSD. I put 3 in a > FBSD router box and they all worked first try automagically! > > Any idea if the SMC drivers are updateable? The drivers are *always* updtatable. However, if the card simply does not have enough memory on board to hold both an inbound and an outbound buffer simultaneously, it *must* remain "simplex" no matter who writes the driver or how well. Just because other OS's don't report the fact doesn't make it any less a fact. 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 Sep 17 10:26:37 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA23755 for hackers-outgoing; Tue, 17 Sep 1996 10:26:37 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA23744 for ; Tue, 17 Sep 1996 10:26:32 -0700 (PDT) Received: from localhost (tom@localhost) by misery.sdf.com (8.7.5/8.7.3) with SMTP id KAA05593; Tue, 17 Sep 1996 10:46:49 -0700 (PDT) Date: Tue, 17 Sep 1996 10:46:48 -0700 (PDT) From: Tom Samplonius To: Gary Clark II cc: freebsd-hackers@freebsd.org Subject: Re: Strange error on Freefall In-Reply-To: <199609171514.KAA16313@main.gbdata.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 17 Sep 1996, Gary Clark II wrote: > hello, > > I was on FreeFall earlier and ran into the following problem: > > freefall:gclarkii# ping srimain.srisoft.com > PING srimain.srisoft.com (207.90.208.225): 56 data bytes > 64 bytes from 207.90.208.225: icmp_seq=0 ttl=238 time=188.854 ms > 64 bytes from 207.90.208.225: icmp_seq=1 ttl=238 time=209.467 ms > ^C > --- srimain.srisoft.com ping statistics --- > 3 packets transmitted, 2 packets received, 33% packet loss > round-trip min/avg/max = 188.854/199.160/209.467 ms > > freefall:gclarkii# telnet srimain.srisoft.com > Trying 198.66.103.161... > freefall:gclarkii# > > Why does the DNS return both variables consistly, one to ping > and the other to telnet and rlogin??? > > Any ideas? > > Gary That system has two addresses. The DNS server will return the address list in a different order for each query. ping uses the first address in the list. telnet tries to be smart and tries to search the list for an address that will work. Tom From owner-freebsd-hackers Tue Sep 17 10:39:32 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA24443 for hackers-outgoing; Tue, 17 Sep 1996 10:39:32 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA24438 for ; Tue, 17 Sep 1996 10:39:28 -0700 (PDT) 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 TAA04831 for ; Tue, 17 Sep 1996 19:39:01 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id TAA00763 for freebsd-hackers@freefall.cdrom.com; Tue, 17 Sep 1996 19:46:06 +0200 Date: Tue, 17 Sep 1996 19:46:06 +0200 From: Christoph Kukulies Message-Id: <199609171746.TAA00763@gilberto.physik.rwth-aachen.de> To: freebsd-hackers@freefall.FreeBSD.org Subject: in.h: direct-broadcast valid oid? Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Just wondering if - signs in oid names are valid? Shouldn't these be _scores? { "directed-broadcast", CTLTYPE_INT }, \ { "intr-queue-maxlen", CTLTYPE_INT }, \ { "intr-queue-drops", CTLTYPE_INT }, \ --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Tue Sep 17 10:45:39 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA24757 for hackers-outgoing; Tue, 17 Sep 1996 10:45:39 -0700 (PDT) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA24750 for ; Tue, 17 Sep 1996 10:45:33 -0700 (PDT) Received: from minnow.render.com (minnow.render.com [193.195.178.1]) by minnow.render.com (8.6.12/8.6.9) with SMTP id SAA24768; Tue, 17 Sep 1996 18:37:56 +0100 Date: Tue, 17 Sep 1996 18:37:55 +0100 (BST) From: Doug Rabson To: Guido van Rooij cc: freebsd-hackers@freebsd.org Subject: Re: new if_vx driver on freefall In-Reply-To: <199609170722.JAA06932@spooky.lss.cp.philips.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 17 Sep 1996, Guido van Rooij wrote: > I've put the two following files on ftp://freefall.freebsd.org:/pub/inccoming: > > newif_vx.tgz > newif_vx.tgz.README > > Ppl with hanging cards should try them out. There is a gross hack inside > but I first need to get sepcs form 3com to identify what's going on. This driver works fine for me but then my card wasn't hanging :-). It didn't build in -current but that was pretty easy to fix. I will try to put together a patch for -current if you want tomorrow. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 734 3761 FAX: +44 171 734 6426 From owner-freebsd-hackers Tue Sep 17 10:54:37 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA25199 for hackers-outgoing; Tue, 17 Sep 1996 10:54:37 -0700 (PDT) Received: from zwei.siemens.at (zwei.siemens.at [193.81.246.12]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA25190; Tue, 17 Sep 1996 10:54:34 -0700 (PDT) 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 TAA21102; Tue, 17 Sep 1996 19:53:26 +0200 (MET DST) Received: from ws2301.gud.siemens.co.at by sol1.gud.siemens.co.at with smtp (Smail3.1.28.1 #7 for ) id m0v34LQ-000218C; Tue, 17 Sep 96 19:54 MET DST Received: by ws2301.gud.siemens.co.at (1.37.109.16/1.37) id AA133682555; Tue, 17 Sep 1996 19:49:15 +0200 From: "Hr.Ladavac" Message-Id: <199609171749.AA133682555@ws2301.gud.siemens.co.at> Subject: Re: Very Slow Ethernet Link (FreeBSD v. Linux) To: jab@rock.anchorage.net (Jeffrey Barber) Date: Tue, 17 Sep 1996 19:49:15 +0200 (MESZ) Cc: freebsd-hardware@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <01BBA46B.C28E9240@jabpc.rtfm.com> from "Jeffrey Barber" at Sep 17, 96 07:40:28 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 Jeffrey Barber contained: > Thanks for all the responses but still no luck. I had to put linux on the system instead. But I did run a ftp test comparing FreeBSD to Linux. The results: > > Using FreeBSD 2.1.0: > > ftp transfer with freebsd 1927427 bytes @ 4.2e+02 seconds 4.4kb/s > > Removing FreeBSD and Installed Linux 2.0 > > ftp transfer with Linux 1927427 bytes @ 3.05 seconds (6.2e+02 kb/s) Wooo Wooo :) > > Using the exact same configuration and computer, the reults are in the Linux favor by far. > Don't know what the problem was. This is usually symptomatic for a misconfigured 3com509 where the kernel does not receive the interrupts (and then it times out and sends a packet per second.) Under FreeBSD these cards have been known to achieve >1000 KB/s, *iff* correctly configured (i.e. PnP turned off, interrupts on the channel where the kernel expects them, no irq conflicts, that sort of things.) /Marino > > Thanks again. > > From owner-freebsd-hackers Tue Sep 17 11:10:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA01039 for hackers-outgoing; Tue, 17 Sep 1996 11:10:25 -0700 (PDT) Received: from sequent.kiae.su (sequent.kiae.su [193.125.152.6]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA01021 for ; Tue, 17 Sep 1996 11:10:20 -0700 (PDT) Received: by sequent.kiae.su id AA08745 (5.65.kiae-2 ); Tue, 17 Sep 1996 22:03:48 +0400 Received: by sequent.KIAE.su (UUMAIL/2.0); Tue, 17 Sep 96 22:03:48 +0400 Received: (from ache@localhost) by nagual.ru (8.7.5/8.7.3) id WAA01753; Tue, 17 Sep 1996 22:01:19 +0400 (MSD) Message-Id: <199609171801.WAA01753@nagual.ru> Subject: Re: new if_vx driver on freefall In-Reply-To: <199609170722.JAA06932@spooky.lss.cp.philips.com> from "Guido van Rooij" at "Sep 17, 96 09:22:01 am" To: Guido.vanRooij@nl.cis.philips.com Date: Tue, 17 Sep 1996 22:01:19 +0400 (MSD) Cc: freebsd-hackers@freebsd.org From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (Andrey A. Chernov) Organization: self X-Class: Fast 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've put the two following files on ftp://freefall.freebsd.org:/pub/inccoming: > > newif_vx.tgz > newif_vx.tgz.README > > Ppl with hanging cards should try them out. There is a gross hack inside > but I first need to get sepcs form 3com to identify what's going on. Nope, I can't compile it in -current, even after removing nonexistent sys/devconf.h include I got: cc -c -O2 -m486 -pipe -W -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Winline -Wunused -Wpointer-arith -nostdinc -I. -I../.. -I../../sys -I../../../include -DI586_CPU -DI686_CPU -DI586_FAST_BCOPY -DCOMPAT_43 -DFFS -DINET -DKERNEL ../../pci/if_vx.c ../../pci/if_vx.c:133: warning: `struct kern_devconf' declared inside parameter list ../../pci/if_vx.c:133: warning: its scope is only this definition or declaration, ../../pci/if_vx.c:133: warning: which is probably not what you want. ../../pci/if_vx.c: In function `vx_pci_shutdown': ../../pci/if_vx.c:135: dereferencing pointer to incomplete type ../../pci/if_vx.c:136: warning: implicit declaration of function `dev_detach' ../../pci/if_vx.c: In function `vx_pci_attach': ../../pci/if_vx.c:234: `IFF_NOTRAILERS' undeclared (first use this function) ../../pci/if_vx.c:234: (Each undeclared identifier is reported only once ../../pci/if_vx.c:234: for each function it appears in.) ../../pci/if_vx.c:238: warning: assignment from incompatible pointer type ../../pci/if_vx.c:244: warning: passing arg 1 of `bpfattach' from incompatible pointer type ../../pci/if_vx.c:244: warning: passing arg 2 of `bpfattach' makes integer from pointer without a cast ../../pci/if_vx.c:244: too many arguments to function `bpfattach' ../../pci/if_vx.c:162: warning: unused variable `p' ../../pci/if_vx.c: At top level: ../../pci/if_vx.c:261: warning: initialization from incompatible pointer type ../../pci/if_vx.c: In function `vxinit': ../../pci/if_vx.c:276: warning: unused variable `j' ../../pci/if_vx.c:276: warning: unused variable `s' ../../pci/if_vx.c: In function `vxstart': ../../pci/if_vx.c:431: `s' undeclared (first use this function) ../../pci/if_vx.c:452: warning: passing arg 1 of `bpf_mtap' from incompatible pointer type ../../pci/if_vx.c: In function `vxintr': ../../pci/if_vx.c:602: warning: unused variable `ret' ../../pci/if_vx.c: In function `vxread': ../../pci/if_vx.c:718: warning: passing arg 1 of `bpf_mtap' from incompatible pointer type ../../pci/if_vx.c: In function `vxreset': ../../pci/if_vx.c:986: warning: unused variable `sc' *** Error code 1 Stop. -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-hackers Tue Sep 17 11:19:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA02504 for hackers-outgoing; Tue, 17 Sep 1996 11:19:25 -0700 (PDT) Received: (from luigi@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA02500 for hackers@freebsd.org; Tue, 17 Sep 1996 11:19:24 -0700 (PDT) Date: Tue, 17 Sep 1996 11:19:24 -0700 (PDT) From: Luigi Rizzo Message-Id: <199609171819.LAA02500@freefall.freebsd.org> To: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk subscribe From owner-freebsd-hackers Tue Sep 17 11:25:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA03701 for hackers-outgoing; Tue, 17 Sep 1996 11:25:34 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA03696 for ; Tue, 17 Sep 1996 11:25:31 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA04481; Tue, 17 Sep 1996 11:16:39 -0700 From: Terry Lambert Message-Id: <199609171816.LAA04481@phaeton.artisoft.com> Subject: Re: attribute/inode caching To: dg@root.com Date: Tue, 17 Sep 1996 11:16:39 -0700 (MST) Cc: terry@lambert.org, bde@zeta.org.au, proff@suburbia.net, freebsd-hackers@FreeBSD.org In-Reply-To: <199609170512.WAA08889@root.com> from "David Greenman" at Sep 16, 96 10:12:10 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 find this hard to believe. This would imply a limitation of the device > >size of the file size, since the adressable extent for a vnode is smaller > >than the addressable extent for a device. > > Huh? In FreeBSD, the device is refered to via the device vnode. How do > you think FFS does the I/O for the inode block? It uses the block device- > special vnode. It dereferences function pointers from the struct fileops, of course (which is itself An Abomination Which Must Be Destroyed). The same routines are not invoked to page from a device as are invoked to page from a file: that arrangement would be recursive when it went to page a file from a device. > As for any implied size limitation, vnodes don't have any > "size" associated with them. Anything (except the VM system) that deals with > file offsets deals in 64bit quad_t's, and it doesn't matter if it's a file > or a device or whatever. Depending on which version of the merged VM/buffer > cache we're talking about, metadata may or may not be stored in VM pages. In > all versions, however, it is cached in buffers (buffers can point to either > malloced memory or VM pages). Ask John Dyson. It has to do with the mapping of the file as a virtual address space. Last time I looked in /a/src-fs/sys/ufs/ffs/ffs_vfsops.c, I saw the following: static int ffs_oldfscompat(fs) struct fs *fs; { ... fs->fs_maxfilesize = (u_quad_t) 1LL << 39; ... A clearly intentional limitation of 39 bit based on the mappable virtual address space. Yes, this is a VM limitation, but since that's how you do file I/O (via faulting of pages mapped in a virtual address space), I can't see how anything could be more relevent. 1) There *IS* a limitation of 2^39 bits on individual file size. 2) There *ISN'T* a limitation of 2^39 bits on device size (ask Satoshi on that, if you don't believe me). 3) Files are mapped as VM objects (ie: have cache on their vnodes). 4) Devices are not mapped as VM objects. I believe devices *should* be mapped as VM objects, and the quad arithmatic overhead should be eaten (or the object references and manipulation should be abstracted, duplicated for 64 and 32 bits, and flagged for reference in the object itself). > >Which value are you caliming is in error? It seems to me that if inode > >blocks are hung of the device vnode (so why have the ihash?!?), then it > >is an error to not limit the device size to the max file size. > > I think you're really starting to confuse things. The maximum file size > is not a function of vnodes. We do have a problem with representing file > offsets in the VM system beyond 31bits worth of pages (43bits total == 8TB), > but this is hardly a concern. John may correct me on this, but I believe in > the current scheme we do cache inode blocks in VM pages in -current. In 2.1.5, > we couldn't because of the vm_page offset limitation. So for 2.1.5, we only > cache inode blocks in malloced memory that is attached to buffers. Offsets > in buffers are 40 bits large (31bits for signed long to hold the block number > which is in units of 512 bytes (9bits)), this effectively limits all operations > that involve struct buf's to 1TB, thus neither a device nor a file may be > larger than this. We've had no compelling reason to fix this as it is more > difficult than just changing the size of a daddr_t, and noone that I know of > is using a 1TB filesystem. Hopefully Satoshi will get his CCD that lage, and then you will no longer be able to ignore the issue. 8-). Personally, I'd like to use page anonymity based protections to establish Chorus-like access priveledge domains for IPC; specifically, for stacks capable of being grown by fault for use by threads. I think the POSIX model is broken: I should not be required to preallocate stack for a thread just because SVR4 and Solaris have bogus architectures (actually, the SVR4 VM does *not* impose this limitation: it is a limitation of the threading code alone. Steve Baumel, the author of the SVR4 VM, and I discussed this at some length when discussing context sharing models that would be useful for the NetWare for UNIX product). The vnodes are, among other things, container objects for cached pages; you could argue that (assuming that most of the other vnode cruft is useless, which it is) their sole purpose in life is to establish address space mappings for FS objects. The problem with this scenario, which I don't seem to be communicating effectively, is that only objects that are contained in the FS are then capable of being cached in the unified cache. I guess it boils down to whether you trust locality of reference or you don't. Clearly, a referenced object can be referenced without existing in the unified cache, as long as there is a page assigned as backing for it. And that is the ihash reference, and the vnode reference to the in core inode, which are not managed as domains on the device at a page boundry resoloution. This implementation fails to "trust" the locality of reference model inherent in all caching systems. > >The fact that the device size was allowed to be larger than the max file > >size was one of the justifications John Dyson gave for not using caching > >based on device/extent instead of (in addition to) vnode/extent in order > >to keep the buffer cache unification of the vnode/extent mapping, but > >resolve a lot of other issues. For instance, if the device vnode is > >in fact a device/extent cache, then there is no need for the ihash, since > >the inodes are determiistically layed out and thus indexable by fault. In > >addition, the abilit to address device blocks by fault on the device vnode > >means that vclean is totally unnecessary. > > I can't parse this. You need ihash because you can't page inodes into cache becuse they aren't in the buffers hung off the device vnode, like you claim. If they were in the buffers hung off the device vnode, like you claim, then they would be, by definition, in the cache, since this mapping is what constitutes the VM/buffer cache unification. As such, ihash would be unnecessary; you could simply directly reference the pages and they would be faulted in; if they were already in core, they would be looked up off the device vnode (just like file pages currently are). I would like to see this happen, but it damn well has not, and the 39 bit limitation (which is not a 42FS compatability hack, despite it's location) is a limitation of *file* size and does not apply to *device* size. 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 Sep 17 11:31:53 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA04136 for hackers-outgoing; Tue, 17 Sep 1996 11:31:53 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA04131; Tue, 17 Sep 1996 11:31:49 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id UAA17532; Tue, 17 Sep 1996 20:05:18 +0200 From: Luigi Rizzo Message-Id: <199609171805.UAA17532@labinfo.iet.unipi.it> Subject: browsing list archives To: hackers@freebsd.org Date: Tue, 17 Sep 1996 20:05:18 +0200 (MET DST) Cc: jkh@freebsd.org X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I am a bit uncomfortable with mailing list archives. I am almost always unable to find the postings I am looking for, and miss a lot the possibility of browsing through the archives myself. I think the latter should not be too hard. After all the archives must be already stored somewhere, all is needed is probably just give access to the relevant directories via the Web, and possibly let some (already established) indexing service (e.g. Altavista, Lycos, etc.) work on them. The latter would have the significant advantage that indexing through the archives would come for free, without having to waste time or resources to provide the indexing service. Luigi From owner-freebsd-hackers Tue Sep 17 11:47:18 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA05200 for hackers-outgoing; Tue, 17 Sep 1996 11:47:18 -0700 (PDT) Received: from korin.warman.org.pl (korin.warman.org.pl [148.81.160.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA05194 for ; Tue, 17 Sep 1996 11:47:12 -0700 (PDT) Received: (from abial@localhost) by korin.warman.org.pl (8.7.5/8.7.3) id UAA16927; Tue, 17 Sep 1996 20:53:05 +0200 (MET DST) Date: Tue, 17 Sep 1996 20:53:05 +0200 (MET DST) From: Andrzej Bialecki To: freebsd-hackers@FreeBSD.ORG Subject: FreeBSD box as a router Message-ID: 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 wonder if somebody did real testing of FreeBSD box with, let's say, two Ethernets and one 2M serial card (or some other hw with equivalent bandwidth), which would act as a router, using e.g. Gated. How well it behaves under heavy traffic? How many packets get dropped/ignored/else? How much memory it requires? How much swap? What is *real* throughput of such a beast? etc... If somebody did it, I would be most interested in results :-) TIA Andy, +-------------------------------------------------------------------------+ Andrzej Bialecki _) _) _)_) _)_)_) _) _) --------------------------------------- _)_) _) _) _) _)_) _)_) Research and Academic Network in Poland _) _)_) _)_)_)_) _) _) _) Bartycka 18, 00-716 Warsaw, Poland _) _) _) _) _)_)_) _) _) +-------------------------------------------------------------------------+ From owner-freebsd-hackers Tue Sep 17 11:51:19 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA05454 for hackers-outgoing; Tue, 17 Sep 1996 11:51:19 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA05446; Tue, 17 Sep 1996 11:51:16 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id LAA07005; Tue, 17 Sep 1996 11:50:37 -0700 (PDT) Message-Id: <199609171850.LAA07005@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: Jeffrey Barber cc: "'freebsd-hardware@FreeBSD.org'" , "'hackers@FreeBSD.ORG'" Subject: Re: Very Slow Ethernet Link (FreeBSD v. Linux) In-reply-to: Your message of "Tue, 17 Sep 1996 07:40:28 -0800." <01BBA46B.C28E9240@jabpc.rtfm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 17 Sep 1996 11:50:37 -0700 From: Amancio Hasty Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >From The Desk Of Jeffrey Barber : > Thanks for all the responses but still no luck. I had to put linux on = > the system instead. But I did run a ftp test comparing FreeBSD to Linux. = > The results:> > Using FreeBSD 2.1.0: > > ftp transfer with freebsd 1927427 bytes @ 4.2e+02 seconds 4.4kb/s > > Removing FreeBSD and Installed Linux 2.0 > > ftp transfer with Linux 1927427 bytes @ 3.05 seconds (6.2e+02 kb/s) = > Wooo Wooo :) > > Using the exact same configuration and computer, the reults are in the = > Linux favor by far. > Don't know what the problem was. > > Thanks again. > > Not welcome... Really, a couple of invididuals have requested your hardware configuration and your kernel configuration. Additionally, it was pointed out that FreeBSD-2.1.0's 3c509 driver was buggy so why are you posting ?? I would have tried a different ethernet card or upgraded the driver or would have indicated an attempt to verify the settings on the 3c509 and ensure that the kernel has the apropiate settings. Go ahead Jeffrey smile , as someone stated they have seen 1000kb/sec on a 3c509 which means that you are at least 1/3 slower than on a properly configured FreeBSD. The only remaining question now is on which CPU or darn we don't know your hardware configuration. So in summary it looks to me like : Jeffrey still has "Very Slow Ethernet" 8) Amancio From owner-freebsd-hackers Tue Sep 17 12:39:20 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA08764 for hackers-outgoing; Tue, 17 Sep 1996 12:39:20 -0700 (PDT) Received: (from jmb@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA08743; Tue, 17 Sep 1996 12:39:16 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199609171939.MAA08743@freefall.freebsd.org> Subject: Re: Very Slow Ethernet Link (FreeBSD v. Linux) To: jab@rock.anchorage.net (Jeffrey Barber) Date: Tue, 17 Sep 1996 12:39:16 -0700 (PDT) Cc: freebsd-hardware@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: <01BBA46B.C28E9240@jabpc.rtfm.com> from "Jeffrey Barber" at Sep 17, 96 07:40:28 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Jeffrey Barber wrote: > > Thanks for all the responses but still no luck. I had to put linux on = > the system instead. But I did run a ftp test comparing FreeBSD to Linux. = Jeff, you have to provide us some information about your system in order for us to help you. if you do not provide information on your system, we must conclude that you are not interested in trying to solve your configuration problem. we routinely get 2.5MB/s (thats bytes, not bits) thru a 100BaseT ethernet connection from wcarchive.cdrom.com to a core router on the internet. jmb -- Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG FreeBSD--4.4BSD Unix for PC clones, source included. http://www.freebsd.org/ PGP 2.6.2 Fingerprint: 31 57 41 56 06 C1 40 13 C5 1C E3 E5 DC 62 0E FB From owner-freebsd-hackers Tue Sep 17 12:52:10 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA10489 for hackers-outgoing; Tue, 17 Sep 1996 12:52:10 -0700 (PDT) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA10483 for ; Tue, 17 Sep 1996 12:52:08 -0700 (PDT) Received: from dialup-usr11.etinc.com (dialup-usr11.etinc.com [204.141.95.132]) by etinc.com (8.6.12/8.6.9) with SMTP id PAA26541; Tue, 17 Sep 1996 15:58:57 -0400 Date: Tue, 17 Sep 1996 15:58:57 -0400 Message-Id: <199609171958.PAA26541@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: "Hr.Ladavac" From: dennis@etinc.com (Dennis) Subject: Re: Very Slow Ethernet Link (FreeBSD v. Linux) Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >E-mail message from Jeffrey Barber contained: >> Thanks for all the responses but still no luck. I had to put linux on the system instead. But I did run a ftp test comparing FreeBSD to Linux. The results: >> >> Using FreeBSD 2.1.0: >> >> ftp transfer with freebsd 1927427 bytes @ 4.2e+02 seconds 4.4kb/s >> >> Removing FreeBSD and Installed Linux 2.0 >> >> ftp transfer with Linux 1927427 bytes @ 3.05 seconds (6.2e+02 kb/s) Wooo Wooo :) >> >> Using the exact same configuration and computer, the reults are in the Linux favor by far. >> Don't know what the problem was. > >This is usually symptomatic for a misconfigured 3com509 where the kernel >does not receive the interrupts (and then it times out and sends a packet >per second.) > >Under FreeBSD these cards have been known to achieve >1000 KB/s, >*iff* correctly configured (i.e. PnP turned off, interrupts on the channel >where the kernel expects them, no irq conflicts, that sort of things.) > >/Marino C'mon now! You can't expect him to do all that, can you? really, an ne2000 on freebsd is faster than a 3com on LINUX! db From owner-freebsd-hackers Tue Sep 17 12:53:26 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA10540 for hackers-outgoing; Tue, 17 Sep 1996 12:53:26 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA10535; Tue, 17 Sep 1996 12:53:22 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id UAA00378; Tue, 17 Sep 1996 20:25:12 +0200 (MET DST) To: Christoph Kukulies cc: freebsd-hackers@freefall.FreeBSD.org Subject: Re: in.h: direct-broadcast valid oid? In-reply-to: Your message of "Tue, 17 Sep 1996 19:46:06 +0200." <199609171746.TAA00763@gilberto.physik.rwth-aachen.de> Date: Tue, 17 Sep 1996 20:25:11 +0200 Message-ID: <376.842984711@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199609171746.TAA00763@gilberto.physik.rwth-aachen.de>, Christoph Ku kulies writes: > >Just wondering if - signs in oid names are valid? > >Shouldn't these be _scores? > > { "directed-broadcast", CTLTYPE_INT }, \ > { "intr-queue-maxlen", CTLTYPE_INT }, \ > { "intr-queue-drops", CTLTYPE_INT }, \ > It's a little inconsistent on this point, but in general new names should be legal 'C' symbols. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-hackers Tue Sep 17 12:55:36 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA10622 for hackers-outgoing; Tue, 17 Sep 1996 12:55:36 -0700 (PDT) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA10615 for ; Tue, 17 Sep 1996 12:55:21 -0700 (PDT) Received: from dialup-usr11.etinc.com (dialup-usr11.etinc.com [204.141.95.132]) by etinc.com (8.6.12/8.6.9) with SMTP id QAA26568; Tue, 17 Sep 1996 16:02:13 -0400 Date: Tue, 17 Sep 1996 16:02:13 -0400 Message-Id: <199609172002.QAA26568@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Andrzej Bialecki From: dennis@etinc.com (Dennis) Subject: Re: FreeBSD box as a router Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Hi all! > >I wonder if somebody did real testing of FreeBSD box with, let's say, two >Ethernets and one 2M serial card (or some other hw with equivalent >bandwidth), which would act as a router, using e.g. Gated. How well it >behaves under heavy traffic? How many packets get dropped/ignored/else? >How much memory it requires? How much swap? What is *real* throughput of >such a beast? etc... The most I know of is 5 T1 (2 frame relay, 3 PTP), 2 ethers (one of which is 100Mbs). Dropped packets? Please! Is gives as good performance as any router on the market. That includes the big-boys. Dennis From owner-freebsd-hackers Tue Sep 17 13:08:43 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA11117 for hackers-outgoing; Tue, 17 Sep 1996 13:08:43 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA11112; Tue, 17 Sep 1996 13:08:39 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id PAA03119; Tue, 17 Sep 1996 15:08:18 -0500 (EST) From: John Dyson Message-Id: <199609172008.PAA03119@dyson.iquest.net> Subject: Re: Very Slow Ethernet Link (FreeBSD v. Linux) To: jmb@freefall.freebsd.org (Jonathan M. Bresler) Date: Tue, 17 Sep 1996 15:08:18 -0500 (EST) Cc: jab@rock.anchorage.net, freebsd-hardware@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: <199609171939.MAA08743@freefall.freebsd.org> from "Jonathan M. Bresler" at Sep 17, 96 12:39:16 pm Reply-To: dyson@FreeBSD.org 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 > > Jeffrey Barber wrote: > > > > Thanks for all the responses but still no luck. I had to put linux on = > > the system instead. But I did run a ftp test comparing FreeBSD to Linux. = > > Jeff, you have to provide us some information about your system > in order for us to help you. > > if you do not provide information on your system, we must conclude > that you are not interested in trying to solve your configuration > problem. > > we routinely get 2.5MB/s (thats bytes, not bits) thru a 100BaseT > ethernet connection from wcarchive.cdrom.com to a core router > on the internet. BTW, that perf is on a machine doing LOTS of ftp's under signficant load. That is certainly not a static test of a single ftp (that being a very degenerate and simple test.) John From owner-freebsd-hackers Tue Sep 17 13:10:07 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA11213 for hackers-outgoing; Tue, 17 Sep 1996 13:10:07 -0700 (PDT) Received: from celebration.net (indy.celebration.net [204.252.46.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA11208; Tue, 17 Sep 1996 13:10:02 -0700 (PDT) Received: (from dyson@localhost) by celebration.net (8.7.5/8.7.3) id PAA07313; Tue, 17 Sep 1996 15:04:28 -0500 (EST) From: "John S. Dyson" Message-Id: <199609172004.PAA07313@celebration.net> Subject: Re: attribute/inode caching To: terry@lambert.org (Terry Lambert) Date: Tue, 17 Sep 1996 15:04:28 -0500 (EST) Cc: dg@Root.COM, terry@lambert.org, bde@zeta.org.au, proff@suburbia.net, freebsd-hackers@freebsd.org, dyson@freebsd.org In-Reply-To: <199609171816.LAA04481@phaeton.artisoft.com> from "Terry Lambert" at Sep 17, 96 11:16:39 am X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk (I am responding from my 'secret' site :-), because this stuff needs clarifying NOW.) > > Ask John Dyson. It has to do with the mapping of the file as a virtual > address space. Last time I looked in /a/src-fs/sys/ufs/ffs/ffs_vfsops.c, > I saw the following: > > > static int > ffs_oldfscompat(fs) > struct fs *fs; > { > ... > fs->fs_maxfilesize = (u_quad_t) 1LL << 39; > ... > > A clearly intentional limitation of 39 bit based on the mappable virtual > address space. > Actually, I think that the max file size is (2^9) * (2^31). The VM code structurally is not limited to that. (Modulo some bugs.) That limitation is due to the DEV_BSIZE addressibility. > > Yes, this is a VM limitation, but since that's how you do file I/O > (via faulting of pages mapped in a virtual address space), I can't > see how anything could be more relevent. > I believe that someone has already found/fixed my bugs in the calcuations causing overflows. The VM code is pretty much limited to 2^31 pages, or (2^31) * (2^12) == 2^43. The 2^40 is due to DEV_BSIZE. Doesn't look like the VM code is structurally the limiting factor. > > 1) There *IS* a limitation of 2^39 bits on individual file size. Yep, it says so in the ffs code, doesn't it? Looks bogus now. > 2) There *ISN'T* a limitation of 2^39 bits on device size (ask > Satoshi on that, if you don't believe me). Nor is there in the VM code. > 3) Files are mapped as VM objects (ie: have cache on their vnodes). Also their indirect blocks. > 4) Devices are not mapped as VM objects. The meta-data has a VMIO object on mounted VBLK filesystems. I haven't changed all of the specfs stuff yet. Right now, if you mount an FFS filesystem, your meta-data will reside in a VM object for the device. > > > I believe devices *should* be mapped as VM objects, and the quad arithmatic > overhead should be eaten (or the object references and manipulation should > be abstracted, duplicated for 64 and 32 bits, and flagged for reference > in the object itself). > The VM system is designed to be capable of supporting 2^31 pages. I changed it in a way so that we don't have to have nasty, inefficient u_quad_t's floating around everywhere. As I said, the infrastructure supports all VBLKS being VMIO directly, but I just haven't enabled it yet. The backing device for a ffs mounted filesystem is currently mapped as a VM object though. (That is where the benefit arises.) > > You need ihash because you can't page inodes into cache becuse they > aren't in the buffers hung off the device vnode, like you claim. > They are!!! (please refer to the code in -current, ignore 2.1.5). The backing VBLK device IS VVMIO (and has been for a few months)!!! > > I would like to see this happen, but it damn well has not, and the 39 > bit limitation (which is not a 42FS compatability hack, despite it's > location) is a limitation of *file* size and does not apply to *device* > size. > It is a file size limitation, and I think gratuitious. John From owner-freebsd-hackers Tue Sep 17 13:12:06 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA11351 for hackers-outgoing; Tue, 17 Sep 1996 13:12:06 -0700 (PDT) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA11344 for ; Tue, 17 Sep 1996 13:12:02 -0700 (PDT) Received: by iafnl.es.iaf.nl with UUCP id AA30888 (5.67b/IDA-1.5 for FreeBSD-hackers@freebsd.org); Tue, 17 Sep 1996 22:11:48 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.6.12/8.6.12) id VAA01391 for FreeBSD-hackers@freebsd.org; Tue, 17 Sep 1996 21:37:00 +0200 From: Wilko Bulte Message-Id: <199609171937.VAA01391@yedi.iaf.nl> Subject: FYI: Syquest removable HDs on FreeBSD To: FreeBSD-hackers@freebsd.org (FreeBSD hackers list) Date: Tue, 17 Sep 1996 21:37:00 +0200 (MET DST) 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 FYI: I just hooked up a removable Syquest HD to my NCR810/2.1R system. Works like a charm (I know, 44Mb is not much...). Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, The Netherlands |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda -------------------------------------------------------------------------- From owner-freebsd-hackers Tue Sep 17 13:28:22 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA12404 for hackers-outgoing; Tue, 17 Sep 1996 13:28:22 -0700 (PDT) Received: from main.gbdata.com (Main.GBData.COM [207.90.222.20]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA12385 for ; Tue, 17 Sep 1996 13:28:08 -0700 (PDT) Received: (from gclarkii@localhost) by main.gbdata.com (8.7.5/8.6.9) id PAA17624; Tue, 17 Sep 1996 15:27:01 -0500 (CDT) From: Gary Clark II Message-Id: <199609172027.PAA17624@main.gbdata.com> Subject: Re: Strange error on Freefall To: tom@sdf.com (Tom Samplonius) Date: Tue, 17 Sep 1996 15:26:59 -0500 (CDT) Cc: freebsd-hackers@FreeBSD.org In-Reply-To: from Tom Samplonius at "Sep 17, 96 10:46:48 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 Tom Samplonius wrote: > > > > That system has two addresses. The DNS server will return the address > list in a different order for each query. ping uses the first address in > the list. telnet tries to be smart and tries to search the list for an > address that will work. Hello, Not unless someone else has been into the nameserver records. I'm the maintainer of that domain... One A record only. On two other machines I got the bad record only. I'm still trying to figure out where this is coming from...:( > > Tom > > 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 Tue Sep 17 13:43:51 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA13307 for hackers-outgoing; Tue, 17 Sep 1996 13:43:51 -0700 (PDT) Received: from gvr.win.tue.nl (root@gvr.win.tue.nl [131.155.210.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA13301 for ; Tue, 17 Sep 1996 13:43:40 -0700 (PDT) Received: by gvr.win.tue.nl (8.6.13/1.53) id WAA06458; Tue, 17 Sep 1996 22:43:03 +0200 From: guido@gvr.win.tue.nl (Guido van Rooij) Message-Id: <199609172043.WAA06458@gvr.win.tue.nl> Subject: Re: new if_vx driver on freefall To: ache@nagual.ru (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=) Date: Tue, 17 Sep 1996 22:43:01 +0200 (MET DST) Cc: Guido.vanRooij@nl.cis.philips.com, freebsd-hackers@freebsd.org In-Reply-To: <199609171801.WAA01753@nagual.ru> from "[______ ______]" at "Sep 17, 96 10:01:19 pm" 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 [______ ______] wrote: > > I've put the two following files on ftp://freefall.freebsd.org:/pub/inccoming: > > > > newif_vx.tgz > > newif_vx.tgz.README > > > > Ppl with hanging cards should try them out. There is a gross hack inside > > but I first need to get sepcs form 3com to identify what's going on. > > Nope, I can't compile it in -current, even after removing nonexistent > sys/devconf.h include I got: > iIt was meant for 2.1.5R..Sorry. -Guido From owner-freebsd-hackers Tue Sep 17 13:45:39 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA13474 for hackers-outgoing; Tue, 17 Sep 1996 13:45:39 -0700 (PDT) Received: from gvr.win.tue.nl (root@gvr.win.tue.nl [131.155.210.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA13465 for ; Tue, 17 Sep 1996 13:45:26 -0700 (PDT) Received: by gvr.win.tue.nl (8.6.13/1.53) id WAA06494; Tue, 17 Sep 1996 22:45:09 +0200 From: guido@gvr.win.tue.nl (Guido van Rooij) Message-Id: <199609172045.WAA06494@gvr.win.tue.nl> Subject: Re: new if_vx driver on freefall To: dfr@render.com (Doug Rabson) Date: Tue, 17 Sep 1996 22:45:08 +0200 (MET DST) Cc: Guido.vanRooij@nl.cis.philips.com, freebsd-hackers@FreeBSD.org In-Reply-To: from Doug Rabson at "Sep 17, 96 06:37:55 pm" 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 Doug Rabson wrote: > On Tue, 17 Sep 1996, Guido van Rooij wrote: > > > I've put the two following files on ftp://freefall.freebsd.org:/pub/inccoming: > > > > newif_vx.tgz > > newif_vx.tgz.README > > > > Ppl with hanging cards should try them out. There is a gross hack inside > > but I first need to get sepcs form 3com to identify what's going on. > > This driver works fine for me but then my card wasn't hanging :-). It > didn't build in -current but that was pretty easy to fix. I will try to > put together a patch for -current if you want tomorrow. If you happen to have a 3c590, could you undef the BROKEN_AVAIL define and see if you card still works after doing a ping -f -s 1000 (as root of course). -Guido From owner-freebsd-hackers Tue Sep 17 13:59:59 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA14069 for hackers-outgoing; Tue, 17 Sep 1996 13:59:59 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA14064; Tue, 17 Sep 1996 13:59:56 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA04771; Tue, 17 Sep 1996 13:56:25 -0700 From: Terry Lambert Message-Id: <199609172056.NAA04771@phaeton.artisoft.com> Subject: Re: attribute/inode caching To: dyson@celebration.net (John S. Dyson) Date: Tue, 17 Sep 1996 13:56:25 -0700 (MST) Cc: terry@lambert.org, dg@Root.COM, bde@zeta.org.au, proff@suburbia.net, freebsd-hackers@freebsd.org, dyson@freebsd.org In-Reply-To: <199609172004.PAA07313@celebration.net> from "John S. Dyson" at Sep 17, 96 03:04:28 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 believe devices *should* be mapped as VM objects, and the quad arithmatic > > overhead should be eaten (or the object references and manipulation should > > be abstracted, duplicated for 64 and 32 bits, and flagged for reference > > in the object itself). > > The VM system is designed to be capable of supporting 2^31 pages. I > changed it in a way so that we don't have to have nasty, inefficient > u_quad_t's floating around everywhere. As I said, the infrastructure > supports all VBLKS being VMIO directly, but I just haven't enabled it > yet. The backing device for a ffs mounted filesystem is currently > mapped as a VM object though. (That is where the benefit arises.) > > > You need ihash because you can't page inodes into cache becuse they > > aren't in the buffers hung off the device vnode, like you claim. > > They are!!! (please refer to the code in -current, ignore 2.1.5). The > backing VBLK device IS VVMIO (and has been for a few months)!!! > > > I would like to see this happen, but it damn well has not, and the 39 > > bit limitation (which is not a 42FS compatability hack, despite it's > > location) is a limitation of *file* size and does not apply to *device* > > size. > > It is a file size limitation, and I think gratuitious. Then there is no reason for vclean. The mapping association which it destroys is no longer applicable, since it is no longer the only reference instance. I have saved the original correspondence (or you can look it up in the -current list archives, which I suggest you do so that there is no question of me biasing the information) where we originally discussed the vclean interface. In it, you claimed that device/extent and vnode/extent mapping were irreconcilable because the device/extent mapping would cause a reduction in the mappable region down to 2^31, the max filesize (clearly, 31 pages == 4096/512 + 31 bits of blocks -- the origin of the 39). The purpose in maintaining it was because there was no way to recover a cache page that was not referenced by vnode because the divorce from the inode lost the base for the relative offset for the cache contents (ie: the vnode/inode data described a virtual address space). However, this current discussion has claimed that pages from a device will have a mapping off the device vnode. Unless somewhow some pages are more equal than others, this should include pages for which a vnode mapping exists. If this is true, then it is now possible to recover cached pages without an associated vnode by device/offset, and the vclean can be eliminated by LRU'ing the device vnode buffer list instead of the list of vnodes without an FS association. The pages are recoverable by making a device reference for any extent from the start of device, right? All that is required is that, now that you claim the device and the file vnode offset are in the same reference units, is to move the vnode offset from being a relative offset to an absolute (device relative instead of vnode relative). Thus vclean is doubley damned, since the operation it performs is to flush out essentially recoverable pages -- WHICH NEED NO LONGER BE FLUSHED, AND WERE ONLY BEING FLUSHED BECAUSE OF THEIR UNRECOVERABILITY. The sole remaining problem is for pseudo devices which span multiple physical devices (like CCD), since the cache must be split among the vnodes for the underlying devices. Unless you claim a CCD device established a mapping for the CCD device layer as well, and the a buffer of a file has three mappings: 1) The mapping to the vnode for the file reference, inherent in the cache unification (vnode/extent caching). 2) The mapping for the device vnode, inherent in your explanation of inode caching (device/extent caching). 3) The additional submapping for the device vnode for the real device as a component of a CCD composite device. Am I mistaken here? What am I missing? I really disliked the move of the fs_maxfilesize into the in core superblock in the first place -- does this mean it can go away entirely, and we can recover Sun FFS layout interoperability? I would be all for that... 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 Sep 17 14:18:42 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA15045 for hackers-outgoing; Tue, 17 Sep 1996 14:18:42 -0700 (PDT) Received: from gargoyle.bazzle.com ([206.103.246.190]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA15037; Tue, 17 Sep 1996 14:18:38 -0700 (PDT) Received: from gargoyle.bazzle.com (localhost [127.0.0.1]) by gargoyle.bazzle.com (8.7.5/8.6.12) with SMTP id RAA15582; Tue, 17 Sep 1996 17:17:16 -0400 (EDT) Date: Tue, 17 Sep 1996 17:17:15 -0400 (EDT) From: "Eric J. Chet" To: Jeffrey Barber cc: "'freebsd-hardware@FreeBSD.org'" , "'hackers@FreeBSD.ORG'" Subject: Re: Very Slow Ethernet Link In-Reply-To: <01BBA3A2.11B93340@jabpc.rtfm.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hello Take a look at your numbers again, I see them a FreeBSD being 3x faster than Linux on a localhost ping. Eric J. Chet - ejc@bazzle.com On Mon, 16 Sep 1996, Jeffrey Barber wrote: > Ok, I just installed FreeBSD 2.1 and boy this is slow, Example: > > bash$ ping localhost > > PING localhost (127.0.0.1): 56 data bytes > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.356 ms > > 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=1.1 ms From owner-freebsd-hackers Tue Sep 17 14:25:47 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA15510 for hackers-outgoing; Tue, 17 Sep 1996 14:25:47 -0700 (PDT) Received: from gw.research.megasoft.com (gw.research.megasoft.com [206.230.35.93]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA15502 for ; Tue, 17 Sep 1996 14:25:35 -0700 (PDT) Received: from goffette.research.megasoft.com (goffette.research.megasoft.com [192.168.1.2]) by gw.research.megasoft.com (8.7.5/8.7.3-cmcurtin) with SMTP id RAA26951; Tue, 17 Sep 1996 17:17:40 -0400 (EDT) Received: by goffette.research.megasoft.com (940816.SGI.8.6.9/940406.SGI) id RAA00608; Tue, 17 Sep 1996 17:17:51 -0400 Date: Tue, 17 Sep 1996 17:17:51 -0400 Message-Id: <199609172117.RAA00608@goffette.research.megasoft.com> From: C Matthew Curtin To: guido@gvr.win.tue.nl (Guido van Rooij) Cc: ache@nagual.ru (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=), dfr@render.com, roberto@keltia.freenix.fr, freebsd-hackers@FreeBSD.org Subject: Re: vx device broken in 21.1.5? In-Reply-To: <199609101858.UAA27144@gvr.win.tue.nl> References: <199609091605.UAA00484@nagual.ru> <199609101858.UAA27144@gvr.win.tue.nl> Reply-To: cmcurtin@research.megasoft.com X-Attribution: mattC Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >>>>> "Guido" == Guido van Rooij writes: >> It not makes things worse, but not help the problem too. My >> problem was not performance decrease but complete card hang until >> reboot. Guido> Try ifconfig vx0 down; ifconfig.vx0 up. Then it works again Guido> ;-() The problem is that there are two versions of the 3c590 board. The FreeBSD driver was written for 3c590, but now all of the 3c590 boards out there are "3c590b"... some small change made the driver not working. -- C Matthew Curtin MEGASOFT, INC Chief Scientist I speak only for myself. Don't whine to anyone but me about anything I say. Hacker Security Firewall Crypto PGP Privacy Unix Perl Java Internet Intranet cmcurtin@research.megasoft.com http://research.megasoft.com/people/cmcurtin/ From owner-freebsd-hackers Tue Sep 17 14:26:05 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA15551 for hackers-outgoing; Tue, 17 Sep 1996 14:26:05 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA15542 for ; Tue, 17 Sep 1996 14:26:00 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id PAA03650; Tue, 17 Sep 1996 15:25:12 -0600 (MDT) Date: Tue, 17 Sep 1996 15:25:12 -0600 (MDT) Message-Id: <199609172125.PAA03650@rocky.mt.sri.com> From: Nate Williams To: Michael Smith Cc: khetan@iafrica.com (Khetan Gajjar), schluntz@gromit.pinpt.com, hackers@freebsd.org Subject: Re: Question on Porting Windows software to X In-Reply-To: <199609170047.KAA27589@genesis.atrad.adelaide.edu.au> References: <199609170047.KAA27589@genesis.atrad.adelaide.edu.au> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Having said all that, I believe that the issues with the WP6 license > manager were iBCS2 emulation problems, and that they were fixed some > time back. (Nate?) Possibly. I haven't heard one way or the other, but if someone were to make a copy available to me I'd do my darndest to try and make it work. In any case, I made some changes recently which may have affected license managers, so it may work right now. Nate From owner-freebsd-hackers Tue Sep 17 15:01:05 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA16821 for hackers-outgoing; Tue, 17 Sep 1996 15:01:05 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA16810 for ; Tue, 17 Sep 1996 15:00:54 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.eu.org [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id AAA06011 for ; Wed, 18 Sep 1996 00:00:48 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id AAA26580 for hackers@FreeBSD.org; Wed, 18 Sep 1996 00:00:32 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.Beta.4/keltia-uucp-2.9) id XAA08862; Tue, 17 Sep 1996 23:53:05 +0200 (MET DST) Message-Id: <199609172153.XAA08862@keltia.freenix.fr> Date: Tue, 17 Sep 1996 23:53:05 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: hackers@FreeBSD.org Subject: Re: browsing list archives In-Reply-To: <199609171805.UAA17532@labinfo.iet.unipi.it>; from Luigi Rizzo on Sep 17, 1996 20:05:18 +0200 References: <199609171805.UAA17532@labinfo.iet.unipi.it> X-Mailer: Mutt 0.43g Mime-Version: 1.0 X-Operating-System: FreeBSD 2.2-CURRENT ctm#2443 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk According to Luigi Rizzo: > The latter would have the significant advantage that indexing through > the archives would come for free, without having to waste time or > resources to provide the indexing service. Check DejaNews or Altavista. Some sites are already gatewaying the lists into newsgroups (I've seen muc.lists.* or muc.freebsd.*). Sprint even distribute them... Look for newsgroups:muc.* -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #21: Sun Sep 8 14:35:00 MET DST 1996 From owner-freebsd-hackers Tue Sep 17 15:03:00 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA16930 for hackers-outgoing; Tue, 17 Sep 1996 15:03:00 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA16914 for ; Tue, 17 Sep 1996 15:02:51 -0700 (PDT) Received: from rover.village.org (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with ESMTP id QAA12496; Tue, 17 Sep 1996 16:01:55 -0600 (MDT) Message-Id: <199609172201.QAA12496@rover.village.org> To: graphix@iastate.edu Subject: Re: OpenBSD <-> FreeBSD Cc: hackers@freebsd.org In-reply-to: Your message of Wed, 11 Sep 1996 19:51:02 CDT Date: Tue, 17 Sep 1996 16:01:55 -0600 From: Warner Losh Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk : Is there anyone tracking the changes that are made to the 4.4 source : in NetBSD/OpenBSD and incorporating the changes into the FreeBSD tree on : a regular basis? If not, what is the common feeling of if this would be Having looked into this problem before I upgraded the size of my disk drive collection.... The kernel sources generally would be hard to do. There are some parts of the kernel that would be easy to do this for, and other parts that would be hard (the vm system comes to mind for the latter). This would be complex and would require more effort than it currently is worth to make it happen. Better to tilt at smaller windmills :-). A smaller windmill might be userland. It should be basically trivial, but it likely isn't at this point. It is a *LOT* of work. There are hacks on all three *BSD systems that need to be reconciled with the 4.4 Lite-2 changes and eachother. OpenBSD, for example, has gone "paranoid" in the use of sprintf due to potential buffer overflow security holes. These would be great to merge into FreeBSD, for example. I know that OpenBSD merges a lot of FreeBSD stuff into it (the ports system, for example) and it would be good to narrow the gap between the *BSDs. A good first step would be to merge in as much of the differences in the user level code as possible. This would take someone a lot of time, and then be a bear to keep in sync between the three. OpenBSD keeps in sync with NetBSD by a brute force approach that involves running diffs, lots of patches and the watchful eyes of the core team. Its a lot of work for them (judging from the timestamps of various messages and such). However, let us say that FreeBSD merges every last change from NetBSD and OpenBSD into its tree. I would maintain that this would be a wasted effort because NetBSD and OpenBSD might not pick them up and we'd still have version skew. Maybe what would work best would be for people in each of the commiter groups to work towards ironing out the differences one at a time. Take /usr/src/bin or something small and make all of those files the same (or as close to it as is sane) and slowly integrated the changes from the other trees. Once there is convergence, then it would be easier to keep things in sync. Once there is a large part of the world that is nearly identical on all the platforms, then it might not be a bad idea to talk of having a Grand Unified Source Tree (GUST, you heard it hear first :-). Until then, I think it will remain a project too large to ever make good headway. In conclusion: Merging from other sources is a good idea. Trying to make all three share parts of their source tree is an idea whose time has not yet arrived. Warner From owner-freebsd-hackers Tue Sep 17 15:04:28 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA17038 for hackers-outgoing; Tue, 17 Sep 1996 15:04:28 -0700 (PDT) Received: from novell.com (prv-mail20.Provo.Novell.COM [137.65.40.4]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA17028 for ; Tue, 17 Sep 1996 15:04:22 -0700 (PDT) Received: from INET-PRV-Message_Server by novell.com with Novell_GroupWise; Tue, 17 Sep 1996 16:04:50 -0600 Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Tue, 17 Sep 1996 16:12:35 -0600 From: Darren Davis To: freebsd-hackers@FreeBSD.org Subject: Caldera posting sources to DR-DOS. Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I don't know if any of you have heard yet, but Caldera has announced that they are going to post the sources to DR-DOS on their Web site first quarter next year. This may be a bit early, but it looks like it would be a potential item to integrate into FreeBSD for DOS compatibility. Any thoughts? Darren R. Davis Senior Software Engineer Novell, Inc. From owner-freebsd-hackers Tue Sep 17 15:18:21 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA17711 for hackers-outgoing; Tue, 17 Sep 1996 15:18:21 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA17704; Tue, 17 Sep 1996 15:18:13 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id RAA03292; Tue, 17 Sep 1996 17:14:42 -0500 (EST) From: "John S. Dyson" Message-Id: <199609172214.RAA03292@dyson.iquest.net> Subject: Re: attribute/inode caching To: terry@lambert.org (Terry Lambert) Date: Tue, 17 Sep 1996 17:14:42 -0500 (EST) Cc: dyson@celebration.net, terry@lambert.org, dg@Root.COM, bde@zeta.org.au, proff@suburbia.net, freebsd-hackers@freebsd.org, dyson@freebsd.org In-Reply-To: <199609172056.NAA04771@phaeton.artisoft.com> from "Terry Lambert" at Sep 17, 96 01:56:25 pm Reply-To: dyson@freebsd.org 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 > > I have saved the original correspondence (or you can look it up in the > -current list archives, which I suggest you do so that there is no question > of me biasing the information) where we originally discussed the vclean > interface. In it, you claimed that device/extent and vnode/extent > mapping were irreconcilable because the device/extent mapping would > cause a reduction in the mappable region down to 2^31, the max filesize > (clearly, 31 pages == 4096/512 + 31 bits of blocks -- the origin of the 39). > maxfilesize is in units of bytes, right? John From owner-freebsd-hackers Tue Sep 17 16:13:02 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA20568 for hackers-outgoing; Tue, 17 Sep 1996 16:13:02 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA20562; Tue, 17 Sep 1996 16:13:00 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA05000; Tue, 17 Sep 1996 16:11:55 -0700 From: Terry Lambert Message-Id: <199609172311.QAA05000@phaeton.artisoft.com> Subject: Re: attribute/inode caching To: dyson@freebsd.org Date: Tue, 17 Sep 1996 16:11:55 -0700 (MST) Cc: terry@lambert.org, dyson@celebration.net, dg@Root.COM, bde@zeta.org.au, proff@suburbia.net, freebsd-hackers@freebsd.org In-Reply-To: <199609172214.RAA03292@dyson.iquest.net> from "John S. Dyson" at Sep 17, 96 05:14:42 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 have saved the original correspondence (or you can look it up in the > > -current list archives, which I suggest you do so that there is no question > > of me biasing the information) where we originally discussed the vclean > > interface. In it, you claimed that device/extent and vnode/extent > > mapping were irreconcilable because the device/extent mapping would > > cause a reduction in the mappable region down to 2^31, the max filesize > > (clearly, 31 pages == 4096/512 + 31 bits of blocks -- the origin of the 39). > > > maxfilesize is in units of bytes, right? Yes. 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 Sep 17 16:20:51 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA20852 for hackers-outgoing; Tue, 17 Sep 1996 16:20:51 -0700 (PDT) Received: from night.primate.wisc.edu (night.primate.wisc.edu [144.92.43.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA20846 for ; Tue, 17 Sep 1996 16:20:47 -0700 (PDT) Received: by night.primate.wisc.edu; id SAA15189; 8.6.10/41.8; Tue, 17 Sep 1996 18:22:19 -0500 From: Paul DuBois Message-Id: <199609172322.SAA15189@night.primate.wisc.edu> Subject: Re: vx device broken in 21.1.5? To: cmcurtin@research.megasoft.com Date: Tue, 17 Sep 1996 18:22:19 -0500 (CDT) Cc: freebsd-hackers@FreeBSD.org In-Reply-To: <199609172117.RAA00608@goffette.research.megasoft.com> from "C Matthew Curtin" at Sep 17, 96 05:17:51 pm X-Mailer: ELM [version 2.4 PL25] 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 >>> It not makes things worse, but not help the problem too. My >>> problem was not performance decrease but complete card hang until >>> reboot. > >Guido> Try ifconfig vx0 down; ifconfig.vx0 up. Then it works again >Guido> ;-() > >The problem is that there are two versions of the 3c590 board. The >FreeBSD driver was written for 3c590, but now all of the 3c590 boards >out there are "3c590b"... some small change made the driver not working. I thought it was the 3c509 (not 3c590) that had the "b" version... From owner-freebsd-hackers Tue Sep 17 16:55:00 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA22696 for hackers-outgoing; Tue, 17 Sep 1996 16:55:00 -0700 (PDT) Received: from mail1.infinet.com (mail1.infinet.com [206.103.240.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA22672 for ; Tue, 17 Sep 1996 16:54:57 -0700 (PDT) Received: from drobina.my.domain (cmh-p100.infinet.com [206.103.242.106]) by mail1.infinet.com (8.7.3/8.7.3) with SMTP id TAA26378 for ; Tue, 17 Sep 1996 19:54:47 -0400 (EDT) Date: Tue, 17 Sep 1996 19:53:51 -0400 (EDT) From: James Drobina X-Sender: jdrobina@drobina.my.domain To: freebsd-hackers@freebsd.org Subject: libc_r and MIT pthreads Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is ther any chance of updating libc_r to use the lastest version of MIT pthreads (pthreads-1_60_beta5)? From owner-freebsd-hackers Tue Sep 17 17:10:27 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA23654 for hackers-outgoing; Tue, 17 Sep 1996 17:10:27 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA23648 for ; Tue, 17 Sep 1996 17:10:25 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id TAA08181; Tue, 17 Sep 1996 19:09:11 -0500 From: Joe Greco Message-Id: <199609180009.TAA08181@brasil.moneng.mei.com> Subject: Re: FreeBSD box as a router To: abial@korin.warman.org.pl (Andrzej Bialecki) Date: Tue, 17 Sep 1996 19:09:10 -0500 (CDT) Cc: freebsd-hackers@freebsd.org In-Reply-To: from "Andrzej Bialecki" at Sep 17, 96 08:53:05 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I wonder if somebody did real testing of FreeBSD box with, let's say, two > Ethernets and one 2M serial card (or some other hw with equivalent > bandwidth), which would act as a router, using e.g. Gated. How well it > behaves under heavy traffic? How many packets get dropped/ignored/else? > How much memory it requires? How much swap? What is *real* throughput of > such a beast? etc... Hi Andy, This sounds pretty familiar.. streeling# ifconfig eth0 eth0: flags=51 mtu 1500 inet 204.95.219.1 --> 204.95.160.43 netmask 0xffffff00 streeling# ifconfig de0 de0: flags=8863 mtu 1500 inet 206.55.64.17 netmask 0xfffffff8 broadcast 206.55.64.23 streeling# ifconfig de1 de1: flags=8863 mtu 1500 inet 206.55.64.1 netmask 0xfffffff8 broadcast 206.55.64.7 If you just need static routing, 8MB is plenty adequate. If you want to use Gated and do BGP4, etc, you will probably need more (since I haven't had to start doing this myself, I don't know how much more). The machine is a 486DX/133 with two Kingston KNE-40T's (DEC 21041) and one of the Emerging Technologies ET-50XX cards running a T1 CSU/DSU. It can saturate all its links simultaneously with bandwidth to spare... unless all the packets are really small. I start seeing lost packets once I get into the 4000 pkts/sec range, IIRC. It is a great router :-) ... JG From owner-freebsd-hackers Tue Sep 17 17:34:11 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA24597 for hackers-outgoing; Tue, 17 Sep 1996 17:34:11 -0700 (PDT) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA24589 for ; Tue, 17 Sep 1996 17:34:08 -0700 (PDT) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <103982(5)>; Tue, 17 Sep 1996 16:25:18 PDT Received: from localhost ([127.0.0.1]) by crevenia.parc.xerox.com with SMTP id <177476>; Tue, 17 Sep 1996 13:46:29 -0700 X-Mailer: exmh version 1.6.7 5/3/96 To: Gary Clark II cc: freebsd-hackers@freebsd.org Subject: Re: Strange error on Freefall In-reply-to: Your message of "Tue, 17 Sep 1996 08:14:31 PDT." <199609171514.KAA16313@main.gbdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 17 Sep 1996 13:46:24 PDT From: Bill Fenner Message-Id: <96Sep17.134629pdt.177476@crevenia.parc.xerox.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199609171514.KAA16313@main.gbdata.com> you write: >Why does the DNS return both variables consistly, one to ping >and the other to telnet and rlogin??? Looks to me like the DNS is round-robining: PING srimain.srisoft.com (198.66.103.161): 56 data bytes PING srimain.srisoft.com (207.90.208.225): 56 data bytes PING srimain.srisoft.com (198.66.103.161): 56 data bytes That was just three ping's right in a row on freefall. Then two telnets in a row: freefall% telnet srimain.srisoft.com Trying 207.90.208.225... ^C freefall% telnet srimain.srisoft.com Trying 198.66.103.161... ^C No deterministic behavior here. Note also that if you let the connection attempt to the 198 address time out, telnet will connect to the 207 address and work: freefall% telnet srimain.srisoft.com Trying 198.66.103.161... telnet: connect to address 198.66.103.161: No route to host Trying 207.90.208.255... Connected to srimain.srisoft.com. Both primary servers for srisoft.com only give out the 207 address. However, the TTL on the records that they are giving out is 3 days, and there are 25 hours left on the 198 address. So it appears likely that the name servers for srisoft.com gave out the 198 address a little less than 2 days ago, and freefall's default name server is caching it. Bill From owner-freebsd-hackers Tue Sep 17 18:32:16 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA28767 for hackers-outgoing; Tue, 17 Sep 1996 18:32:16 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA28757 for ; Tue, 17 Sep 1996 18:32:08 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id LAA02910; Wed, 18 Sep 1996 11:01:51 +0930 From: Michael Smith Message-Id: <199609180131.LAA02910@genesis.atrad.adelaide.edu.au> Subject: Re: Caldera posting sources to DR-DOS. To: darrend@novell.com (Darren Davis) Date: Wed, 18 Sep 1996 11:01:50 +0930 (CST) Cc: freebsd-hackers@FreeBSD.org In-Reply-To: from "Darren Davis" at Sep 17, 96 04:12:35 pm 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 Darren Davis stands accused of saying: > I don't know if any of you have heard yet, but Caldera has announced > that they are going to post the sources to DR-DOS on their Web site > first quarter next year. This may be a bit early, but it looks like > it would be a potential item to integrate into FreeBSD for DOS > compatibility. Any thoughts? No license details, so it's a bit early to get enthused about it just yet, but it would be good to have a "real" DOS (no offence to the FreeDOS people) to run inside the emulator(s). > Darren R. Davis -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Tue Sep 17 18:33:28 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA28871 for hackers-outgoing; Tue, 17 Sep 1996 18:33:28 -0700 (PDT) Received: from pluto.plutotech.com (root@pluto.plutotech.com [206.168.67.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA28862 for ; Tue, 17 Sep 1996 18:33:26 -0700 (PDT) Received: from shane.plutotech.com (durian@shane.plutotech.com [206.168.67.21]) by pluto.plutotech.com (8.7.5/8.7.5) with ESMTP id TAA05262 for ; Tue, 17 Sep 1996 19:33:24 -0600 (MDT) Message-Id: <199609180133.TAA05262@pluto.plutotech.com> From: "Mike Durian" To: freebsd-hackers@freebsd.org Subject: Special Cycles on the PCI bus Date: Tue, 17 Sep 1996 19:33:23 -0600 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We've discovered a strange phenomenon that occurs under FreeBSD, but not Windows 95 (running on the same hardware). It has to do with illegal "Special Cycle" transactions occurring on the PCI bus. The "Special Cycle" is appearing as a "halt" cycle, but because of reasons I don't really understand (this low-level PCI bus stuff is beyond me) they are malformed. I think it has to do with a two cycle delay in the transaction. We have not been able to track down what is generating these cycles. We can reproduce them reliably on two system (that is all we've tested on). The commonality between the two systems is the Triton chipset and an ISA ethernet card (3c509). As for differences, one system is IDE, the other SCSI. The IDE system has a custom made PCI card in it. The SCSI system has a Cyclone PCI card in it. Both these PCI cards use a PLX chip to interface to the PCI bus. Neither of these cards are doing anything. Though we don't know much, we do know the following: 1) The "Special Cycles" only start appearing when the root file system is mounted. We think we've tracked it down to the VOP_OPEN call in ffs_vfsops.c. This happens on both the SCSI and IDE systems. 2) On the IDE system we set breakpoints at the beginning and end of wdcommand. If we run with the breakpoints active the "Special Cycles" do not appear - at least for as long as we were willing to keep typing "c"ontinue, which probably wasn't more than 30 or so cycles. Without breakpoints, they did occur. 3) On an idle system in single user mode and the cable removed from the ethernet card with the PCI bus analyzer set to trigger on "Special Cycles" and interrupts we saw only two types interrupts, these had values 0x20 and 0x28. Their timings appeared to be 10ms and ~8ms appart. From this I'd assume them to be the two system clocks. "Special Cycles" would invariably follow the interrupts approximately 11us later (though sometimes only ~6us). There seemed to be some cause and effect. 4) On a non-idle system the behavior was not as well behaved. "Special Cycles" did not always follow the timer interrupts, sometimes there were other interrupts in between. I'm guessing that perhaps the timer interrupt was interrupted by the other before the code the resulted in the "Special Cycle" was executed, but this is just a guess. 5) According to the databooks we have, none of the chips in the system generate "Special Cycles". Yet they appear. And malformed to boot. We're running a modified 2.1.5 system. The modifications are mostly to the SCSI system and a whole lot of new device drivers. Does anyone have any ideas? mike From owner-freebsd-hackers Tue Sep 17 18:47:23 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA03500 for hackers-outgoing; Tue, 17 Sep 1996 18:47:23 -0700 (PDT) Received: from sasami.jurai.net (root@sasami.jurai.net [206.151.208.162]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA03475 for ; Tue, 17 Sep 1996 18:47:21 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.7.5/8.7.3) with SMTP id UAA15567; Tue, 17 Sep 1996 20:48:21 -0500 (CDT) Date: Tue, 17 Sep 1996 20:48:21 -0500 (CDT) From: "Matthew N. Dodd" To: Andrzej Bialecki cc: freebsd-hackers@FreeBSD.org Subject: Re: FreeBSD box as a router In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 17 Sep 1996, Andrzej Bialecki wrote: > I wonder if somebody did real testing of FreeBSD box with, let's say, two > Ethernets and one 2M serial card (or some other hw with equivalent > bandwidth), which would act as a router, using e.g. Gated. How well it > behaves under heavy traffic? How many packets get dropped/ignored/else? > How much memory it requires? How much swap? What is *real* throughput of > such a beast? etc... I've got a P120/32m with 2 ZNYX 314s in it. 8 ethernet ports total, 5 in use. It works very well. I don't have any hard numbers, but I was ftp'ing from an Ultra1/140 to a P90 across the router and got around 850k/sec transfering a 300 meg tar/gzip file. And the P90 was waiting on the Ultra. Just get a few ZNYX 314s and you'll be ready to go. Have a good one. | Matthew N. Dodd | winter@jurai.net | http://www.jurai.net/~winter | | Technical Manager | mdodd@intersurf.net | http://www.intersurf.net | | InterSurf Online | "Welcome to the net Sir, would you like a handbasket?"| From owner-freebsd-hackers Tue Sep 17 18:57:37 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA09197 for hackers-outgoing; Tue, 17 Sep 1996 18:57:37 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA09157; Tue, 17 Sep 1996 18:57:32 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id UAA03535; Tue, 17 Sep 1996 20:55:45 -0500 (EST) From: "John S. Dyson" Message-Id: <199609180155.UAA03535@dyson.iquest.net> Subject: Re: attribute/inode caching To: terry@lambert.org (Terry Lambert) Date: Tue, 17 Sep 1996 20:55:45 -0500 (EST) Cc: dyson@freebsd.org, terry@lambert.org, dyson@celebration.net, dg@Root.COM, bde@zeta.org.au, proff@suburbia.net, freebsd-hackers@freebsd.org In-Reply-To: <199609172311.QAA05000@phaeton.artisoft.com> from "Terry Lambert" at Sep 17, 96 04:11:55 pm Reply-To: dyson@freebsd.org 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 > > > I have saved the original correspondence (or you can look it up in the > > > -current list archives, which I suggest you do so that there is no question > > > of me biasing the information) where we originally discussed the vclean > > > interface. In it, you claimed that device/extent and vnode/extent > > > mapping were irreconcilable because the device/extent mapping would > > > cause a reduction in the mappable region down to 2^31, the max filesize > > > (clearly, 31 pages == 4096/512 + 31 bits of blocks -- the origin of the 39). > > > > > maxfilesize is in units of bytes, right? > > Yes. > VM system addressibility is (2^31) * PAGE_SIZE = 2^43; I/O system addressibility is (2^31) * DEV_BSIZE = 2^40. There may have been some implementation limitations in the past, but those have been fixed (AFAIK.) John From owner-freebsd-hackers Tue Sep 17 19:45:39 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA26180 for hackers-outgoing; Tue, 17 Sep 1996 19:45:39 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA26127 for ; Tue, 17 Sep 1996 19:45:32 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id MAA03300; Wed, 18 Sep 1996 12:15:13 +0930 From: Michael Smith Message-Id: <199609180245.MAA03300@genesis.atrad.adelaide.edu.au> Subject: Re: Special Cycles on the PCI bus To: durian@plutotech.com (Mike Durian) Date: Wed, 18 Sep 1996 12:15:12 +0930 (CST) Cc: freebsd-hackers@freebsd.org In-Reply-To: <199609180133.TAA05262@pluto.plutotech.com> from "Mike Durian" at Sep 17, 96 07:33:23 pm 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 Mike Durian stands accused of saying: > We have not been able to track down what is generating these > cycles. We can reproduce them reliably on two system (that is > all we've tested on). The commonality between the two systems is > the Triton chipset and an ISA ethernet card (3c509). As for There is regular timer-initiated activity with the 'ep' driver which would appear to correlate with the symptoms you describe below. > Though we don't know much, we do know the following: > 1) The "Special Cycles" only start appearing when the root > file system is mounted. We think we've tracked it down > to the VOP_OPEN call in ffs_vfsops.c. This happens on > both the SCSI and IDE systems. Is there any other activity (eg. starting of timers) which happens at some interval before this? Is it possible that you're arriving here by coincidence or are you breakpointing beforehand? > 3) On an idle system in single user mode and the cable removed from > the ethernet card with the PCI bus analyzer set to trigger > on "Special Cycles" and interrupts we saw only two types > interrupts, these had values 0x20 and 0x28. Their timings > appeared to be 10ms and ~8ms appart. From this I'd assume > them to be the two system clocks. "Special Cycles" would > invariably follow the interrupts approximately 11us later > (though sometimes only ~6us). There seemed to be some cause > and effect. Did you have the 'ep' driver active at this point in time? If you disable the 'ep' driver using userconfig, do these cycles still show up? > 4) On a non-idle system the behavior was not as well behaved. > "Special Cycles" did not always follow the timer interrupts, > sometimes there were other interrupts in between. I'm > guessing that perhaps the timer interrupt was interrupted > by the other before the code the resulted in the "Special Cycle" > was executed, but this is just a guess. There might also be other activity hung off the timer. > 5) According to the databooks we have, none of the chips in the > system generate "Special Cycles". Yet they appear. And > malformed to boot. Are they causing you serious grief? > mike -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Tue Sep 17 19:51:46 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA28361 for hackers-outgoing; Tue, 17 Sep 1996 19:51:46 -0700 (PDT) Received: from veda.is (root@ubiq.veda.is [193.4.230.60]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA28319 for ; Tue, 17 Sep 1996 19:51:41 -0700 (PDT) Received: (from adam@localhost) by veda.is (8.7.5/8.7.3) id CAA11480 for freebsd-hackers@freebsd.org; Wed, 18 Sep 1996 02:51:30 GMT From: Adam David Message-Id: <199609180251.CAA11480@veda.is> Subject: IPFW !IP# To: freebsd-hackers@freebsd.org Date: Wed, 18 Sep 1996 02:51:28 +0000 (GMT) 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 I can implement exclusion of a block of IP addresses at low execution cost. Does anyone dislike this idea? Which flags mask would be more preferred for this purpose, 0xc000 or 0x0003? (does anything already use 0x0003?) Are the unused flags perhaps reserved for something more useful than this? # ipfw add deny all from !${my_network}:${my_netmask} to any out via ${gate_if} # ipfw add deny all from any to !${my_network}:${my_netmask} in via ${gate_if} This set of 2 rules would otherwise take 48 rules to enforce for a class C network with a single domain gateway, for instance. -- Adam David From owner-freebsd-hackers Tue Sep 17 23:20:06 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA26566 for hackers-outgoing; Tue, 17 Sep 1996 23:20:06 -0700 (PDT) Received: from sdev.blaze.net.au (sdev.blaze.net.au [203.17.53.11]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA25968; Tue, 17 Sep 1996 23:18:53 -0700 (PDT) Received: from localhost (davidn@localhost) by sdev.blaze.net.au (8.7.5/8.6.9) with SMTP id QAA04805; Wed, 18 Sep 1996 16:14:39 GMT Date: Wed, 18 Sep 1996 16:14:38 +0000 () From: David Nugent To: Ollivier Robert cc: hackers@freebsd.org, security@freebsd.org Subject: Re: Could use a favor In-Reply-To: <199609161856.UAA03226@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 16 Sep 1996, Ollivier Robert wrote: >> The only conclusion I have come at is that it is to allow only things >> that you especially allow to happen... The bad thing is that there is no >> switch to switch the firewall on/off. You compile a new kernel with the >> option for firewall and suddenly it accepts nothing over the network. > >Sure there is: > >By default all is off. To open (dangerous!!!) > >ipfw add 65000 pass all from any to any > >To close it again: > >ipfw delete 65000 I'm familiar with the theory of firewalls, but have never run one so I lack the experience to fully understand this. But this reply caught my attention. Why is an (effectively) disabled firewall "dangerous"? Is it more "dangerous" or exposed to security problems than a machine that has been configured without a firewall at all? It's just that it seems that limited firewalls are quite usful - particularly for port redirection and so forth, and in particular for preventing outgoing and incoming spam-email abusers. If putting the firewall in place without being full enabled is "dangerous", then I certainly want to know just how dangerous that is before I go ahead and do it. David Nugent, Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-791-9547 Data/BBS +61-3-792-3507 3:632/348@fidonet davidn@blaze.net.au http://www.blaze.net.au/~davidn From owner-freebsd-hackers Tue Sep 17 23:22:01 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA27075 for hackers-outgoing; Tue, 17 Sep 1996 23:22:01 -0700 (PDT) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA26942 for ; Tue, 17 Sep 1996 23:21:44 -0700 (PDT) Message-Id: <199609180621.XAA26942@freefall.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA110847661; Wed, 18 Sep 1996 16:21:01 +1000 From: Darren Reed Subject: Re: IPFW !IP# To: adam@veda.is (Adam David) Date: Wed, 18 Sep 1996 16:21:01 +1000 (EST) Cc: freebsd-hackers@freebsd.org In-Reply-To: <199609180251.CAA11480@veda.is> from "Adam David" at Sep 18, 96 02:51:28 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In some mail from Adam David, sie said: > > I can implement exclusion of a block of IP addresses at low execution cost. > Does anyone dislike this idea? Which flags mask would be more preferred for > this purpose, 0xc000 or 0x0003? (does anything already use 0x0003?) > Are the unused flags perhaps reserved for something more useful than this? > > # ipfw add deny all from !${my_network}:${my_netmask} to any out via ${gate_if} > # ipfw add deny all from any to !${my_network}:${my_netmask} in via ${gate_if} > > This set of 2 rules would otherwise take 48 rules to enforce for a class C > network with a single domain gateway, for instance. This is just rule writing. HOw about: # ipfw add pass all from ${my_network}:${my_netmask} to any out via ${gate_if} # ipfw add pass all from any to ${my_network}:${my_netmask} in via ${gate_if} # ipfw add deny all from any to any out via ${gate_if} # ipfw add deny all from any to any in via ${gate_if} Darren From owner-freebsd-hackers Wed Sep 18 00:56:29 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA19898 for hackers-outgoing; Wed, 18 Sep 1996 00:56:29 -0700 (PDT) Received: from sdev.blaze.net.au (sdev.blaze.net.au [203.17.53.11]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA19206; Wed, 18 Sep 1996 00:55:01 -0700 (PDT) Received: from localhost (davidn@localhost) by sdev.blaze.net.au (8.7.5/8.6.9) with SMTP id RAA05069; Wed, 18 Sep 1996 17:48:57 GMT Date: Wed, 18 Sep 1996 17:48:55 +0000 () From: David Nugent To: Bruce Evans cc: craigs@os.com, jab@rock.anchorage.net, freebsd-hardware@FreeBSD.org, hackers@FreeBSD.org Subject: Re: Slow Etherlink In-Reply-To: <199609170456.OAA10729@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 17 Sep 1996, Bruce Evans wrote: >>One thing I will say about Linux is that it has superior screen display >>performance. So, if what you are complaining about is screen redraw >>speed, Linux is much faster than FreeBSD. > >Really? Linux was 6-12 times slower last time I worked on speeding up >syscons. I can only agree to this. I recently switched from RedHat Linux (running kernel 2.0.10) to FreeBSD on exactly the same hardware, and without having benchmarks at all I'd rate syscons quite noticably faster than Linux's console. When the scree scrolls, for example, I often missed screens of output in the blink of an eye (I'd rarely even see them scroll by!), whereas on Linux I'd have the opportunity to hit ^S to stop the display. Well, at least I learned to use more, more (and more - sic! :-)). One problem I do have with the syscons driver, however, is the cursor. I'm not one who things much of the blocky cursor, especially since porting Crisp as an editor with it's neat ability to change the cursor size over virtual/real spaces - it needs to have the hardware cursor enabled (e.g. vidcontrol -c destructive) so the cursor size can change. The problem is, the screen updates are affected by enabling that, such that when typing at the shell prompt, you often don't see characters that are typed until you hit enter. Is this a known problem? I'm running 2.2-CURRENT if that is relevent, although I noticed the same when I ran 2.1.5-RELEASE as well. Right now I just have the editor enable the destructive cursor while editing, and switch it back off when exiting via the appropriate ANSI sequences. Unfortunately, while that's fine while within that vt (Crisp itself seems unaffected by this 'bug' - it seems only to happen with cooked stdio enabled, or maybe if termios echo enabled since it occurs with tcsh as well; I haven't really experimented all that much) - but the destructive cursor is system wide, so switching to another vt while editing brings the destructive cursor with it. David Nugent, Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-791-9547 Data/BBS +61-3-792-3507 3:632/348@fidonet davidn@blaze.net.au http://www.blaze.net.au/~davidn From owner-freebsd-hackers Wed Sep 18 01:27:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA02389 for hackers-outgoing; Wed, 18 Sep 1996 01:27:25 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA02352; Wed, 18 Sep 1996 01:27:19 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.7.5/8.7.3) id SAA03973; Wed, 18 Sep 1996 18:25:21 +1000 (EST) Date: Wed, 18 Sep 1996 18:25:19 +1000 (EST) From: "Daniel O'Callaghan" To: David Nugent cc: hackers@freebsd.org, security@freebsd.org Subject: Re: Could use a favor In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 18 Sep 1996, David Nugent wrote: > I'm familiar with the theory of firewalls, but have never run > one so I lack the experience to fully understand this. But this > reply caught my attention. > > Why is an (effectively) disabled firewall "dangerous"? Is it more > "dangerous" or exposed to security problems than a machine that > has been configured without a firewall at all? > > It's just that it seems that limited firewalls are quite usful - > particularly for port redirection and so forth, and in particular > for preventing outgoing and incoming spam-email abusers. If > putting the firewall in place without being full enabled is > "dangerous", then I certainly want to know just how dangerous > that is before I go ahead and do it. I think it is simply a matter of if you configure IPFIREWALL into the kernel and then believe you are protected, then it is dangerous. Ugen's ipfw originally had default policy open; Poul-Henning changed this to closed when he did a code revamp. I think Poul-Henning has done the right thing, but it is a bit confusing when one meets a "Permission denied" error when trying to ping another machine. Hence my submission of some minor mods to netstart and sysconfig which tell the user what s/he has done wrong. Danny From owner-freebsd-hackers Wed Sep 18 01:36:17 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA06249 for hackers-outgoing; Wed, 18 Sep 1996 01:36:17 -0700 (PDT) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA06221; Wed, 18 Sep 1996 01:36:12 -0700 (PDT) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id KAA13230; Wed, 18 Sep 1996 10:33:03 +0200 Message-Id: <199609180833.KAA13230@ra.dkuug.dk> Subject: Re: Slow Etherlink To: davidn@sdev.blaze.net.au (David Nugent) Date: Wed, 18 Sep 1996 10:33:02 +0200 (MET DST) Cc: bde@zeta.org.au, craigs@os.com, jab@rock.anchorage.net, freebsd-hardware@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: from "David Nugent" at Sep 18, 96 05:48:55 pm From: sos@FreeBSD.org Reply-to: sos@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In reply to David Nugent who wrote: > > On Tue, 17 Sep 1996, Bruce Evans wrote: > > >>One thing I will say about Linux is that it has superior screen display > >>performance. So, if what you are complaining about is screen redraw > >>speed, Linux is much faster than FreeBSD. > > > >Really? Linux was 6-12 times slower last time I worked on speeding up > >syscons. Syscons is nearly as fast as the PC architecture allows for :) It uses a totally different method of updating the screen than all the other console driver in the "free" world (minix excluded) > One problem I do have with the syscons driver, however, is the > cursor. I'm not one who things much of the blocky cursor, especially > since porting Crisp as an editor with it's neat ability to change > the cursor size over virtual/real spaces - it needs to have the > hardware cursor enabled (e.g. vidcontrol -c destructive) so the > cursor size can change. The problem is, the screen updates are > affected by enabling that, such that when typing at the shell > prompt, you often don't see characters that are typed until you > hit enter. > > Is this a known problem? I'm running 2.2-CURRENT if that is Yes, it is, and it is on my TODO list... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-hackers Wed Sep 18 02:00:59 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA15002 for hackers-outgoing; Wed, 18 Sep 1996 02:00:59 -0700 (PDT) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA14856; Wed, 18 Sep 1996 02:00:36 -0700 (PDT) Received: by sovcom.kiae.su id AA08329 (5.65.kiae-1 ); Wed, 18 Sep 1996 11:55:17 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Wed, 18 Sep 96 11:55:17 +0300 Received: (from ache@localhost) by nagual.ru (8.7.5/8.7.3) id MAA00462; Wed, 18 Sep 1996 12:39:45 +0400 (MSD) Message-Id: <199609180839.MAA00462@nagual.ru> Subject: Re: (was Slow Etherlink) Syscons In-Reply-To: from "David Nugent" at "Sep 18, 96 05:48:55 pm" To: davidn@sdev.blaze.net.au (David Nugent) Date: Wed, 18 Sep 1996 12:39:45 +0400 (MSD) Cc: bde@zeta.org.au, craigs@os.com, jab@rock.anchorage.net, freebsd-hardware@FreeBSD.org, hackers@FreeBSD.org, sos@FreeBSD.org (Soren Schmidt) From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (Andrey A. Chernov) Organization: self X-Class: Fast 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 > One problem I do have with the syscons driver, however, is the > cursor. I'm not one who things much of the blocky cursor, especially > since porting Crisp as an editor with it's neat ability to change > the cursor size over virtual/real spaces - it needs to have the > hardware cursor enabled (e.g. vidcontrol -c destructive) so the > cursor size can change. The problem is, the screen updates are > affected by enabling that, such that when typing at the shell > prompt, you often don't see characters that are typed until you > hit enter. > > Is this a known problem? I'm running 2.2-CURRENT if that is > relevent, although I noticed the same when I ran 2.1.5-RELEASE as > well. Right now I just have the editor enable the destructive > cursor while editing, and switch it back off when exiting via the > appropriate ANSI sequences. Unfortunately, while that's fine > while within that vt (Crisp itself seems unaffected by this 'bug' > - it seems only to happen with cooked stdio enabled, or maybe if > termios echo enabled since it occurs with tcsh as well; I > haven't really experimented all that much) - but the destructive > cursor is system wide, so switching to another vt while editing > brings the destructive cursor with it. Yes, it is known bug, I already report Soren about this thing. It was broken about month ago. The next manifistation of this bug is that scrolling not always occurse when answering to 'rm -i' response at the last line, but it is very hard to catch it. -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-hackers Wed Sep 18 05:27:01 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA08804 for hackers-outgoing; Wed, 18 Sep 1996 05:27:01 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA08775 for ; Wed, 18 Sep 1996 05:26:57 -0700 (PDT) Received: from relay-2.mail.demon.net (disperse.demon.co.uk) by mail.crl.com with SMTP id AA15858 (5.65c/IDA-1.5 for ); Wed, 18 Sep 1996 05:27:19 -0700 Received: from post.demon.co.uk ([(null)]) by relay-2.mail.demon.net id bc13797; 18 Sep 96 12:55 BST Received: from aaaaaaaa.demon.co.uk ([158.152.178.85]) by relay-3.mail.demon.net id aa02323; 18 Sep 96 12:43 BST Received: (from andrew@localhost) by aaaaaaaa.demon.co.uk (8.7.5/8.6.9) id MAA00869; Wed, 18 Sep 1996 12:42:16 +0100 (BST) From: Andrew Wilson Message-Id: <199609181142.MAA00869@aaaaaaaa.demon.co.uk> Subject: new suid binaries after 'make world'... To: hackers@freebsd.org Date: Wed, 18 Sep 1996 12:42:14 +0100 (BST) Cc: Andrew Wilson X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8891-1 Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I'm using CTM to track -STABLE and have all the deltas up to and including src-2.1.0161.gz. I typed 'make world' 'make install' and the system rebuilt itself and installed fine, but that evening's security checking cron job reported the following new setuid scripts. Are these scripts legit, or did something go wrong and grant seteuid to scripts that shouldn't be so endowed. Or does the process of 'make world' 'make install' hose the security checking algorithm? I don't subscribe to hackers@ so a cc would be appreciated ;) , thanks for your time. Cheers, Ay. Andrew.Wilson@cm.cf.ac.uk http://www.cm.cf.ac.uk/User/Andrew.Wilson/ Forwarded message: > From daemon Wed Sep 18 00:06:00 1996 > Date: Wed, 18 Sep 1996 00:04:07 +0100 (BST) > From: Charlie Root > Message-Id: <199609172304.AAA04755@aaaaaaaa.demon.co.uk> > Subject: aaaaaaaa security check output > > checking setuid files and devices: > aaaaaaaa setuid/device diffs: > 1,13c1,13 > < -r-xr-sr-x 1 bin operator 65536 Aug 13 19:29:10 1996 /bin/df > < -r-xr-sr-x 1 bin kmem 159744 Aug 13 19:29:23 1996 /bin/ps > < -r-sr-xr-x 1 root bin 172032 Aug 13 19:29:24 1996 /bin/rcp > < -r-xr-sr-x 1 bin kmem 106496 Aug 13 19:34:36 1996 /sbin/ccdconfig > < -r-xr-sr-x 1 bin kmem 102400 Aug 13 19:34:41 1996 /sbin/dmesg > < -r-sr-sr-x 2 root tty 188416 Aug 13 19:34:42 1996 /sbin/dump > < -r-sr-xr-x 1 root bin 139264 Aug 13 19:35:30 1996 /sbin/mount_msdos > < -r-sr-xr-x 1 root bin 118784 Aug 13 19:35:11 1996 /sbin/ping > < -r-sr-sr-x 2 root tty 188416 Aug 13 19:34:42 1996 /sbin/rdump > < -r-sr-sr-x 2 root tty 204800 Aug 13 19:35:17 1996 /sbin/restore > < -r-sr-xr-x 1 root bin 126976 Aug 13 19:35:18 1996 /sbin/route > < -r-sr-sr-x 2 root tty 204800 Aug 13 19:35:17 1996 /sbin/rrestore > < -r-sr-x--- 1 root operator 135168 Aug 13 19:35:22 1996 /sbin/shutdown > --- > > -r-xr-sr-x 1 bin operator 65536 Sep 17 18:36:34 1996 /bin/df > > -r-xr-sr-x 1 bin kmem 159744 Sep 17 18:36:44 1996 /bin/ps > > -r-sr-xr-x 1 root bin 172032 Sep 17 18:36:46 1996 /bin/rcp > > -r-xr-sr-x 1 bin kmem 106496 Sep 17 18:41:01 1996 /sbin/ccdconfig > > -r-xr-sr-x 1 bin kmem 102400 Sep 17 18:41:04 1996 /sbin/dmesg > > -r-sr-sr-x 2 root tty 188416 Sep 17 18:41:06 1996 /sbin/dump > > -r-sr-xr-x 1 root bin 139264 Sep 17 18:41:49 1996 /sbin/mount_msdos > > -r-sr-xr-x 1 root bin 118784 Sep 17 18:41:32 1996 /sbin/ping > > -r-sr-sr-x 2 root tty 188416 Sep 17 18:41:06 1996 /sbin/rdump > > -r-sr-sr-x 2 root tty 204800 Sep 17 18:41:38 1996 /sbin/restore > > -r-sr-xr-x 1 root bin 126976 Sep 17 18:41:39 1996 /sbin/route > > -r-sr-sr-x 2 root tty 204800 Sep 17 18:41:38 1996 /sbin/rrestore > > -r-sr-x--- 1 root operator 135168 Sep 17 18:41:43 1996 /sbin/shutdown > 20,96c20,96 > < -r-sr-xr-x 4 root bin 20480 Aug 16 06:41:43 1996 /usr/bin/at > < -r-sr-xr-x 4 root bin 20480 Aug 16 06:41:43 1996 /usr/bin/atq > < -r-sr-xr-x 4 root bin 20480 Aug 16 06:41:43 1996 /usr/bin/atrm > < -r-sr-xr-x 4 root bin 20480 Aug 16 06:41:43 1996 /usr/bin/batch > < -r-sr-xr-x 6 root bin 24576 Aug 16 06:41:53 1996 /usr/bin/chfn > < -r-sr-xr-x 6 root bin 24576 Aug 16 06:41:53 1996 /usr/bin/chpass > < -r-sr-xr-x 6 root bin 24576 Aug 16 06:41:53 1996 /usr/bin/chsh > < -r-sr-xr-x 1 root bin 24576 Aug 13 19:41:04 1996 /usr/bin/crontab > < -r-sr-xr-x 1 uucp bin 110592 Aug 13 19:31:23 1996 /usr/bin/cu > < -r-xr-sr-x 1 bin kmem 16384 Aug 16 06:42:19 1996 /usr/bin/fstat > < -r-xr-sr-x 1 bin kmem 16384 Aug 16 06:42:31 1996 /usr/bin/ipcs > < -r-sr-xr-x 1 root bin 12288 Aug 16 06:42:36 1996 /usr/bin/keyinit > < -r-sr-xr-x 1 root bin 12288 Aug 16 06:42:45 1996 /usr/bin/lock > < -r-sr-xr-x 1 root bin 20480 Aug 16 06:42:46 1996 /usr/bin/login > < -r-sr-sr-x 1 root daemon 20480 Aug 13 19:41:20 1996 /usr/bin/lpq > < -r-sr-sr-x 1 root daemon 20480 Aug 13 19:41:20 1996 /usr/bin/lpr > < -r-sr-sr-x 1 root daemon 16384 Aug 13 19:41:21 1996 /usr/bin/lprm > < -r-sr-xr-x 3 root bin 245760 Aug 13 19:42:07 1996 /usr/bin/mailq > < -r-xr-sr-x 1 bin kmem 8192 Aug 16 06:42:59 1996 /usr/bin/modstat > < -r-xr-sr-x 1 bin kmem 57344 Aug 16 06:43:02 1996 /usr/bin/netstat > < -r-sr-xr-x 3 root bin 245760 Aug 13 19:42:07 1996 /usr/bin/newaliases > < -r-xr-sr-x 1 bin kmem 12288 Aug 16 06:43:03 1996 /usr/bin/nfsstat > < -r-sr-xr-x 2 root bin 20480 Aug 16 06:43:07 1996 /usr/bin/passwd > < -r-sr-xr-x 1 root bin 12288 Aug 16 06:43:11 1996 /usr/bin/quota > < -r-sr-xr-x 1 root bin 45056 Aug 16 06:43:13 1996 /usr/bin/rdist > < -r-sr-xr-x 1 root bin 16384 Aug 16 06:43:15 1996 /usr/bin/rlogin > < -r-sr-xr-x 1 root bin 12288 Aug 16 06:43:18 1996 /usr/bin/rsh > < ---s--x--x 2 root bin 290816 Aug 13 19:33:24 1996 /usr/bin/sperl4.036 > < -r-sr-xr-x 1 root bin 12288 Aug 16 06:43:34 1996 /usr/bin/su > < ---s--x--x 2 root bin 290816 Aug 13 19:33:24 1996 /usr/bin/suidperl > < -r-xr-sr-x 1 bin kmem 40960 Aug 16 06:44:21 1996 /usr/bin/systat > < -r-xr-sr-x 2 bin kmem 16384 Aug 16 06:44:04 1996 /usr/bin/uptime > < -r-sr-xr-x 1 uucp bin 81920 Aug 13 19:31:27 1996 /usr/bin/uucp > < -r-sr-xr-x 1 uucp bin 36864 Aug 13 19:31:29 1996 /usr/bin/uuname > < -r-sr-xr-x 1 uucp bin 86016 Aug 13 19:31:30 1996 /usr/bin/uustat > < -r-sr-xr-x 1 uucp bin 81920 Aug 13 19:31:31 1996 /usr/bin/uux > < -r-xr-sr-x 1 bin kmem 20480 Aug 16 06:44:22 1996 /usr/bin/vmstat > < -r-xr-sr-x 2 bin kmem 16384 Aug 16 06:44:04 1996 /usr/bin/w > < -r-xr-sr-x 1 bin tty 12288 Aug 16 06:44:05 1996 /usr/bin/wall > < -r-xr-sr-x 1 bin tty 12288 Aug 16 06:44:12 1996 /usr/bin/write > < -r-sr-xr-x 6 root bin 24576 Aug 16 06:41:53 1996 /usr/bin/ypchfn > < -r-sr-xr-x 6 root bin 24576 Aug 16 06:41:53 1996 /usr/bin/ypchpass > < -r-sr-xr-x 6 root bin 24576 Aug 16 06:41:53 1996 /usr/bin/ypchsh > < -r-sr-xr-x 2 root bin 20480 Aug 16 06:43:07 1996 /usr/bin/yppasswd > < -r-sr-xr-x 1 games bin 12288 Aug 13 19:29:56 1996 /usr/games/dm > < -rws------ 1 games bin 102400 Aug 13 19:29:32 1996 /usr/games/hide/adventure > < -rws------ 1 games bin 12288 Aug 13 19:29:33 1996 /usr/games/hide/arithmetic > < -rws------ 1 games bin 40960 Aug 13 19:29:35 1996 /usr/games/hide/atc > < -rws------ 1 games bin 45056 Aug 13 19:29:36 1996 /usr/games/hide/backgammon > < -rws------ 1 games bin 172032 Aug 13 19:29:39 1996 /usr/games/hide/battlestar > < -rws------ 1 games bin 12288 Aug 13 19:29:40 1996 /usr/games/hide/bcd > < -rws------ 1 games bin 24576 Aug 13 19:29:42 1996 /usr/games/hide/boggle > < -rws------ 1 games bin 28672 Aug 13 19:29:54 1996 /usr/games/hide/canfield > < -rws------ 1 games bin 12288 Aug 13 19:29:55 1996 /usr/games/hide/cfscores > < -rws------ 1 games bin 28672 Aug 13 19:29:56 1996 /usr/games/hide/cribbage > < -rws------ 1 games bin 12288 Aug 13 19:29:58 1996 /usr/games/hide/fish > < -rws------ 1 games bin 212992 Aug 13 19:30:21 1996 /usr/games/hide/hack > < -rws------ 1 games bin 12288 Aug 13 19:30:25 1996 /usr/games/hide/hangman > < -rws------ 1 games bin 135168 Aug 13 19:30:28 1996 /usr/games/hide/larn > < -rws------ 1 games bin 28672 Aug 13 19:30:29 1996 /usr/games/hide/mille > < -rws------ 1 games bin 12288 Aug 13 19:30:31 1996 /usr/games/hide/morse > < -rws------ 1 games bin 77824 Aug 13 19:30:36 1996 /usr/games/hide/phantasia > < -rws------ 1 games bin 8192 Aug 13 19:30:39 1996 /usr/games/hide/ppt > < -rws------ 1 games bin 16384 Aug 13 19:30:41 1996 /usr/games/hide/quiz > < -rws------ 1 games bin 20480 Aug 13 19:30:44 1996 /usr/games/hide/robots > < -rws------ 1 games bin 110592 Aug 13 19:30:45 1996 /usr/games/hide/rogue > < -rws------ 1 games bin 65536 Aug 13 19:30:46 1996 /usr/games/hide/sail > < -rws------ 1 games bin 24576 Aug 13 19:30:48 1996 /usr/games/hide/snake > < -rws------ 1 games bin 8192 Aug 13 19:30:49 1996 /usr/games/hide/snscore > < -rws------ 1 games bin 57344 Aug 13 19:29:38 1996 /usr/games/hide/teachgammon > < -rws------ 1 games bin 20480 Aug 13 19:30:49 1996 /usr/games/hide/tetris > < -rws------ 1 games bin 57344 Aug 13 19:30:50 1996 /usr/games/hide/trek > < -rws------ 1 games bin 12288 Aug 13 19:30:52 1996 /usr/games/hide/worm > < -rws------ 1 games bin 20480 Aug 13 19:30:54 1996 /usr/games/hide/wump > < -r-sr-xr-x 1 root bin 12288 Aug 13 19:34:25 1996 /usr/libexec/mail.local > < -r-sr-xr-x 1 uucp bin 196608 Aug 13 19:31:25 1996 /usr/libexec/uucp/uucico > < -r-sr-x--- 1 uucp uucp 90112 Aug 13 19:31:32 1996 /usr/libexec/uucp/uuxqt > --- > > -r-sr-xr-x 4 root bin 20480 Sep 17 18:44:07 1996 /usr/bin/at > > -r-sr-xr-x 4 root bin 20480 Sep 17 18:44:07 1996 /usr/bin/atq > > -r-sr-xr-x 4 root bin 20480 Sep 17 18:44:07 1996 /usr/bin/atrm > > -r-sr-xr-x 4 root bin 20480 Sep 17 18:44:07 1996 /usr/bin/batch > > -r-sr-xr-x 6 root bin 24576 Sep 17 18:44:15 1996 /usr/bin/chfn > > -r-sr-xr-x 6 root bin 24576 Sep 17 18:44:15 1996 /usr/bin/chpass > > -r-sr-xr-x 6 root bin 24576 Sep 17 18:44:15 1996 /usr/bin/chsh > > -r-sr-xr-x 1 root bin 24576 Sep 17 18:46:47 1996 /usr/bin/crontab > > -r-sr-xr-x 1 uucp bin 110592 Sep 17 18:38:09 1996 /usr/bin/cu > > -r-xr-sr-x 1 bin kmem 16384 Sep 17 18:44:41 1996 /usr/bin/fstat > > -r-xr-sr-x 1 bin kmem 16384 Sep 17 18:44:51 1996 /usr/bin/ipcs > > -r-sr-xr-x 1 root bin 12288 Sep 17 18:44:57 1996 /usr/bin/keyinit > > -r-sr-xr-x 1 root bin 12288 Sep 17 18:45:04 1996 /usr/bin/lock > > -r-sr-xr-x 1 root bin 20480 Sep 17 18:45:05 1996 /usr/bin/login > > -r-sr-sr-x 1 root daemon 20480 Sep 17 18:47:01 1996 /usr/bin/lpq > > -r-sr-sr-x 1 root daemon 20480 Sep 17 18:47:02 1996 /usr/bin/lpr > > -r-sr-sr-x 1 root daemon 16384 Sep 17 18:47:02 1996 /usr/bin/lprm > > -r-sr-xr-x 3 root bin 245760 Sep 17 18:47:42 1996 /usr/bin/mailq > > -r-xr-sr-x 1 bin kmem 8192 Sep 17 18:45:16 1996 /usr/bin/modstat > > -r-xr-sr-x 1 bin kmem 57344 Sep 17 18:45:20 1996 /usr/bin/netstat > > -r-sr-xr-x 3 root bin 245760 Sep 17 18:47:42 1996 /usr/bin/newaliases > > -r-xr-sr-x 1 bin kmem 12288 Sep 17 18:45:20 1996 /usr/bin/nfsstat > > -r-sr-xr-x 2 root bin 20480 Sep 17 18:45:25 1996 /usr/bin/passwd > > -r-sr-xr-x 1 root bin 12288 Sep 17 18:45:29 1996 /usr/bin/quota > > -r-sr-xr-x 1 root bin 45056 Sep 17 18:45:31 1996 /usr/bin/rdist > > -r-sr-xr-x 1 root bin 16384 Sep 17 18:45:33 1996 /usr/bin/rlogin > > -r-sr-xr-x 1 root bin 12288 Sep 17 18:45:35 1996 /usr/bin/rsh > > ---s--x--x 2 root bin 290816 Sep 17 18:39:54 1996 /usr/bin/sperl4.036 > > -r-sr-xr-x 1 root bin 12288 Sep 17 18:45:49 1996 /usr/bin/su > > ---s--x--x 2 root bin 290816 Sep 17 18:39:54 1996 /usr/bin/suidperl > > -r-xr-sr-x 1 bin kmem 40960 Sep 17 18:46:33 1996 /usr/bin/systat > > -r-xr-sr-x 2 bin kmem 16384 Sep 17 18:46:17 1996 /usr/bin/uptime > > -r-sr-xr-x 1 uucp bin 81920 Sep 17 18:38:12 1996 /usr/bin/uucp > > -r-sr-xr-x 1 uucp bin 36864 Sep 17 18:38:13 1996 /usr/bin/uuname > > -r-sr-xr-x 1 uucp bin 86016 Sep 17 18:38:14 1996 /usr/bin/uustat > > -r-sr-xr-x 1 uucp bin 81920 Sep 17 18:38:15 1996 /usr/bin/uux > > -r-xr-sr-x 1 bin kmem 20480 Sep 17 18:46:34 1996 /usr/bin/vmstat > > -r-xr-sr-x 2 bin kmem 16384 Sep 17 18:46:17 1996 /usr/bin/w > > -r-xr-sr-x 1 bin tty 12288 Sep 17 18:46:18 1996 /usr/bin/wall > > -r-xr-sr-x 1 bin tty 12288 Sep 17 18:46:24 1996 /usr/bin/write > > -r-sr-xr-x 6 root bin 24576 Sep 17 18:44:15 1996 /usr/bin/ypchfn > > -r-sr-xr-x 6 root bin 24576 Sep 17 18:44:15 1996 /usr/bin/ypchpass > > -r-sr-xr-x 6 root bin 24576 Sep 17 18:44:15 1996 /usr/bin/ypchsh > > -r-sr-xr-x 2 root bin 20480 Sep 17 18:45:25 1996 /usr/bin/yppasswd > > -r-sr-xr-x 1 games bin 12288 Sep 17 18:37:13 1996 /usr/games/dm > > -rws------ 1 games bin 102400 Sep 17 18:36:56 1996 /usr/games/hide/adventure > > -rws------ 1 games bin 12288 Sep 17 18:36:57 1996 /usr/games/hide/arithmetic > > -rws------ 1 games bin 40960 Sep 17 18:36:58 1996 /usr/games/hide/atc > > -rws------ 1 games bin 45056 Sep 17 18:36:59 1996 /usr/games/hide/backgammon > > -rws------ 1 games bin 172032 Sep 17 18:37:01 1996 /usr/games/hide/battlestar > > -rws------ 1 games bin 12288 Sep 17 18:37:02 1996 /usr/games/hide/bcd > > -rws------ 1 games bin 24576 Sep 17 18:37:03 1996 /usr/games/hide/boggle > > -rws------ 1 games bin 28672 Sep 17 18:37:11 1996 /usr/games/hide/canfield > > -rws------ 1 games bin 12288 Sep 17 18:37:11 1996 /usr/games/hide/cfscores > > -rws------ 1 games bin 28672 Sep 17 18:37:12 1996 /usr/games/hide/cribbage > > -rws------ 1 games bin 12288 Sep 17 18:37:14 1996 /usr/games/hide/fish > > -rws------ 1 games bin 212992 Sep 17 18:37:25 1996 /usr/games/hide/hack > > -rws------ 1 games bin 12288 Sep 17 18:37:26 1996 /usr/games/hide/hangman > > -rws------ 1 games bin 135168 Sep 17 18:37:28 1996 /usr/games/hide/larn > > -rws------ 1 games bin 28672 Sep 17 18:37:29 1996 /usr/games/hide/mille > > -rws------ 1 games bin 12288 Sep 17 18:37:30 1996 /usr/games/hide/morse > > -rws------ 1 games bin 77824 Sep 17 18:37:32 1996 /usr/games/hide/phantasia > > -rws------ 1 games bin 8192 Sep 17 18:37:34 1996 /usr/games/hide/ppt > > -rws------ 1 games bin 16384 Sep 17 18:37:37 1996 /usr/games/hide/quiz > > -rws------ 1 games bin 20480 Sep 17 18:37:39 1996 /usr/games/hide/robots > > -rws------ 1 games bin 110592 Sep 17 18:37:40 1996 /usr/games/hide/rogue > > -rws------ 1 games bin 65536 Sep 17 18:37:41 1996 /usr/games/hide/sail > > -rws------ 1 games bin 24576 Sep 17 18:37:42 1996 /usr/games/hide/snake > > -rws------ 1 games bin 8192 Sep 17 18:37:43 1996 /usr/games/hide/snscore > > -rws------ 1 games bin 57344 Sep 17 18:37:00 1996 /usr/games/hide/teachgammon > > -rws------ 1 games bin 20480 Sep 17 18:37:43 1996 /usr/games/hide/tetris > > -rws------ 1 games bin 57344 Sep 17 18:37:44 1996 /usr/games/hide/trek > > -rws------ 1 games bin 12288 Sep 17 18:37:45 1996 /usr/games/hide/worm > > -rws------ 1 games bin 20480 Sep 17 18:37:47 1996 /usr/games/hide/wump > > -r-sr-xr-x 1 root bin 12288 Sep 17 18:40:50 1996 /usr/libexec/mail.local > > -r-sr-xr-x 1 uucp bin 196608 Sep 17 18:38:11 1996 /usr/libexec/uucp/uucico > > -r-sr-x--- 1 uucp uucp 90112 Sep 17 18:38:16 1996 /usr/libexec/uucp/uuxqt > 104,111c104,111 > < -r-xr-sr-x 1 bin kmem 12288 Aug 13 19:42:45 1996 /usr/sbin/iostat > < -r-xr-sr-x 1 bin daemon 24576 Aug 13 19:41:17 1996 /usr/sbin/lpc > < -rwsr-xr-x 1 root bin 20480 Aug 13 19:41:27 1996 /usr/sbin/mrinfo > < -rwsr-xr-x 1 root bin 28672 Aug 13 19:41:31 1996 /usr/sbin/mtrace > < -r-xr-sr-x 1 bin kmem 28672 Aug 13 19:42:50 1996 /usr/sbin/ncrcontrol > < -r-sr-xr-x 1 root bin 86016 Aug 13 19:41:53 1996 /usr/sbin/ppp > < -r-sr-xr-x 1 root bin 65536 Aug 13 19:41:54 1996 /usr/sbin/pppd > < -r-xr-sr-x 1 bin kmem 12288 Aug 13 19:41:55 1996 /usr/sbin/pppstats > --- > > -r-xr-sr-x 1 bin kmem 12288 Sep 17 18:48:16 1996 /usr/sbin/iostat > > -r-xr-sr-x 1 bin daemon 24576 Sep 17 18:46:59 1996 /usr/sbin/lpc > > -rwsr-xr-x 1 root bin 20480 Sep 17 18:47:07 1996 /usr/sbin/mrinfo > > -rwsr-xr-x 1 root bin 28672 Sep 17 18:47:08 1996 /usr/sbin/mtrace > > -r-xr-sr-x 1 bin kmem 28672 Sep 17 18:48:20 1996 /usr/sbin/ncrcontrol > > -r-sr-xr-x 1 root bin 86016 Sep 17 18:47:31 1996 /usr/sbin/ppp > > -r-sr-xr-x 1 root bin 65536 Sep 17 18:47:32 1996 /usr/sbin/pppd > > -r-xr-sr-x 1 bin kmem 12288 Sep 17 18:47:33 1996 /usr/sbin/pppstats > 121,128c121,128 > < -r-xr-sr-x 2 bin kmem 20480 Aug 13 19:41:56 1996 /usr/sbin/pstat > < -r-sr-xr-x 3 root bin 245760 Aug 13 19:42:07 1996 /usr/sbin/sendmail > < -r-sr-xr-x 1 root bin 16384 Aug 13 19:42:11 1996 /usr/sbin/sliplogin > < -r-xr-sr-x 1 bin kmem 12288 Aug 13 19:42:11 1996 /usr/sbin/slstat > < -r-xr-sr-x 2 bin kmem 20480 Aug 13 19:41:56 1996 /usr/sbin/swapinfo > < -r-sr-xr-x 1 root bin 20480 Aug 13 19:42:19 1996 /usr/sbin/timedc > < -r-sr-xr-x 1 root bin 16384 Aug 13 19:42:20 1996 /usr/sbin/traceroute > < -r-xr-sr-x 1 bin kmem 12288 Aug 13 19:42:21 1996 /usr/sbin/trpt > --- > > -r-xr-sr-x 2 bin kmem 20480 Sep 17 18:47:33 1996 /usr/sbin/pstat > > -r-sr-xr-x 3 root bin 245760 Sep 17 18:47:42 1996 /usr/sbin/sendmail > > -r-sr-xr-x 1 root bin 16384 Sep 17 18:47:46 1996 /usr/sbin/sliplogin > > -r-xr-sr-x 1 bin kmem 12288 Sep 17 18:47:46 1996 /usr/sbin/slstat > > -r-xr-sr-x 2 bin kmem 20480 Sep 17 18:47:33 1996 /usr/sbin/swapinfo > > -r-sr-xr-x 1 root bin 20480 Sep 17 18:47:54 1996 /usr/sbin/timedc > > -r-sr-xr-x 1 root bin 16384 Sep 17 18:47:55 1996 /usr/sbin/traceroute > > -r-xr-sr-x 1 bin kmem 12288 Sep 17 18:47:56 1996 /usr/sbin/trpt > > > checking for uids of 0: > root 0 > fixer 0 > From owner-freebsd-hackers Wed Sep 18 05:50:54 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA21454 for hackers-outgoing; Wed, 18 Sep 1996 05:50:54 -0700 (PDT) Received: from veda.is (root@ubiq.veda.is [193.4.230.60]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA21243 for ; Wed, 18 Sep 1996 05:50:17 -0700 (PDT) Received: (from adam@localhost) by veda.is (8.7.5/8.7.3) id MAA11928; Wed, 18 Sep 1996 12:49:34 GMT From: Adam David Message-Id: <199609181249.MAA11928@veda.is> Subject: Re: IPFW !IP# To: avalon@coombs.anu.edu.au (Darren Reed) Date: Wed, 18 Sep 1996 12:49:31 +0000 (GMT) Cc: freebsd-hackers@freebsd.org In-Reply-To: <199609180621.GAA26166@veda.is> from Darren Reed at "Sep 18, 96 04:21:01 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 > > # ipfw add deny all from !${my_network}:${my_netmask} to any out via ${gate_if} > > # ipfw add deny all from any to !${my_network}:${my_netmask} in via ${gate_if} > > > > This set of 2 rules would otherwise take 48 rules to enforce for a class C > > network with a single domain gateway, for instance. > > This is just rule writing. > > HOw about: > > # ipfw add pass all from ${my_network}:${my_netmask} to any out via ${gate_if} > # ipfw add pass all from any to ${my_network}:${my_netmask} in via ${gate_if} > # ipfw add deny all from any to any out via ${gate_if} > # ipfw add deny all from any to any in via ${gate_if} > > Darren How would you further restrict access to services which match either of these first 2 rules? 1. explicitly deny port ranges which are to be disallowed. 2. change the rule specification so that it is possible to pass a rule for continued checking, but ignore further deny rules of the same granularity. 3. introduce negation of port number logic. ??? -- Adam David From owner-freebsd-hackers Wed Sep 18 06:01:38 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA27504 for hackers-outgoing; Wed, 18 Sep 1996 06:01:38 -0700 (PDT) Received: from central.picker.com (central.picker.com [144.54.31.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA27476 for ; Wed, 18 Sep 1996 06:01:34 -0700 (PDT) Received: from ct.picker.com by central.picker.com with smtp (Smail3.1.28.1 #3) id m0v3M1k-0004skC; Wed, 18 Sep 96 08:46 EDT Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA02089; Wed, 18 Sep 96 08:45:11 EDT Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id IAA13016; Wed, 18 Sep 1996 08:39:13 -0400 From: rhh@ct.picker.com (Randall Hopper) Message-Id: <199609181239.IAA13016@elmer.ct.picker.com> Subject: Re: fdisk changes, anyone? To: darrylo@hpnmhjw.sr.hp.com (Darryl Okahata) Date: Wed, 18 Sep 1996 08:39:13 -0400 (EDT) Cc: hackers@freebsd.org In-Reply-To: <199609160712.AA113897963@hpnmhjw.sr.hp.com> from "Darryl Okahata" at Sep 16, 96 00:12:43 am Reply-To: rhh@ct.picker.com Organization: Picker International, CT Division X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] 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've just mangled fdisk such that partitioning information can now |be specified via an optional config file. I've been needing a way to ... |Would anyone be interested in the changes (including man page updates)? |Should I submit an enhancement request (w/patches), or should I consign |these changes to the mists of time? ;-) | I'd be very interested in this. Sure would beat the fdisk << ! ... ! references I've got in my scripts -- much less dangerous. I have to manually recheck these scripts when I upgrade my system. To Jordan's point about specifying the partition info using command-line options (to avoid having to use a temp file with this method), a compromise solution might be to be able to specify a "-" on the command line for the config file path to allow the config file to be read from stdin. What you have would definitely be useful. Please submit. One nice future that occurs to me might be able to specify the partition info for multiple disk configurations in a single config file, each one identified by a name, analogous to the way disktab is used (e.g. fbsd-ufs-zip-disk:, fbsd-ufs-1.44flop:, etc.). I think it'd be a plus for usability to eventually deliver an /etc file for this updated fdisk with the more commonly used partitioning schemes for common media (removable in particular) in-place, so the user just needs to do: fdisk -c fbsd-ufs-zip-disk This'd make my fdisk/disklabel/newfs script for creating UFS ZIP disks very small and simple. Randall Hopper rhh@ct.picker.com From owner-freebsd-hackers Wed Sep 18 06:18:40 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA07606 for hackers-outgoing; Wed, 18 Sep 1996 06:18:40 -0700 (PDT) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA07562 for ; Wed, 18 Sep 1996 06:18:36 -0700 (PDT) Message-Id: <199609181318.GAA07562@freefall.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA229552684; Wed, 18 Sep 1996 23:18:04 +1000 From: Darren Reed Subject: Re: IPFW !IP# To: adam@veda.is (Adam David) Date: Wed, 18 Sep 1996 23:18:04 +1000 (EST) Cc: avalon@coombs.anu.edu.au, freebsd-hackers@freebsd.org In-Reply-To: <199609181249.MAA11928@veda.is> from "Adam David" at Sep 18, 96 12:49:31 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In some mail from Adam David, sie said: > > > > # ipfw add deny all from !${my_network}:${my_netmask} to any out via ${gate_if} > > > # ipfw add deny all from any to !${my_network}:${my_netmask} in via ${gate_if} > > > > > > This set of 2 rules would otherwise take 48 rules to enforce for a class C > > > network with a single domain gateway, for instance. > > > > This is just rule writing. > > > > HOw about: > > > > # ipfw add pass all from ${my_network}:${my_netmask} to any out via ${gate_if} > > # ipfw add pass all from any to ${my_network}:${my_netmask} in via ${gate_if} > > # ipfw add deny all from any to any out via ${gate_if} > > # ipfw add deny all from any to any in via ${gate_if} > > > > Darren > > How would you further restrict access to services which match either of these > first 2 rules? This is getting back to 1st principals... Put the rule before the case which I want to create an exception for. From owner-freebsd-hackers Wed Sep 18 07:29:51 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA17205 for hackers-outgoing; Wed, 18 Sep 1996 07:29:51 -0700 (PDT) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA17168 for ; Wed, 18 Sep 1996 07:29:41 -0700 (PDT) Received: from dialup-usr11.etinc.com (dialup-usr11.etinc.com [204.141.95.132]) by etinc.com (8.6.12/8.6.9) with SMTP id KAA02942; Wed, 18 Sep 1996 10:35:31 -0400 Date: Wed, 18 Sep 1996 10:35:31 -0400 Message-Id: <199609181435.KAA02942@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Joe Greco From: dennis@etinc.com (Dennis) Subject: Re: FreeBSD box as a router Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk J. Greco writes.... >If you just need static routing, 8MB is plenty adequate. If you want to >use Gated and do BGP4, etc, you will probably need more (since I haven't >had to start doing this myself, I don't know how much more). a LOT! like 48Meg to hold a full table and to handle worst-case situations. > >The machine is a 486DX/133 with two Kingston KNE-40T's (DEC 21041) and >one of the Emerging Technologies ET-50XX cards running a T1 CSU/DSU. >It can saturate all its links simultaneously with bandwidth to spare... >unless all the packets are really small. I start seeing lost packets once >I get into the 4000 pkts/sec range, IIRC. It is a great router :-) > of course this is nothing that some extra memory wouldn't fix. But 4000pps is very high for a single T1. Dennis From owner-freebsd-hackers Wed Sep 18 08:01:03 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA29794 for hackers-outgoing; Wed, 18 Sep 1996 08:01:03 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA29769 for ; Wed, 18 Sep 1996 08:00:57 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id JAA08984; Wed, 18 Sep 1996 09:59:47 -0500 From: Joe Greco Message-Id: <199609181459.JAA08984@brasil.moneng.mei.com> Subject: Re: FreeBSD box as a router To: dennis@etinc.com (Dennis) Date: Wed, 18 Sep 1996 09:59:47 -0500 (CDT) Cc: jgreco@brasil.moneng.mei.com, hackers@freebsd.org In-Reply-To: <199609181435.KAA02942@etinc.com> from "Dennis" at Sep 18, 96 10:35:31 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > J. Greco writes.... > > >If you just need static routing, 8MB is plenty adequate. If you want to > >use Gated and do BGP4, etc, you will probably need more (since I haven't > >had to start doing this myself, I don't know how much more). > > a LOT! like 48Meg to hold a full table and to handle worst-case situations. Hmm, thanks for the hint :-) > >The machine is a 486DX/133 with two Kingston KNE-40T's (DEC 21041) and > >one of the Emerging Technologies ET-50XX cards running a T1 CSU/DSU. > >It can saturate all its links simultaneously with bandwidth to spare... > >unless all the packets are really small. I start seeing lost packets once > >I get into the 4000 pkts/sec range, IIRC. It is a great router :-) > > of course this is nothing that some extra memory wouldn't fix. But 4000pps is > very high for a single T1. No. It runs out of CPU. I suspect that I could even nail a Pentium at some point. However, typical Internet traffic is NOT UDP packets with 1 data byte - my particular stress test. So I do not worry TOOO much about this "limit" :-) ... JG From owner-freebsd-hackers Wed Sep 18 08:09:48 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA03547 for hackers-outgoing; Wed, 18 Sep 1996 08:09:48 -0700 (PDT) Received: from csla.csl.sri.com (csla.csl.sri.com [192.12.33.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA03525 for ; Wed, 18 Sep 1996 08:09:44 -0700 (PDT) Received: from impulse.csl.sri.com (impulse.csl.sri.com [130.107.15.11]) by csla.csl.sri.com (8.7.3/8.7.3) with ESMTP id IAA01780 for ; Wed, 18 Sep 1996 08:09:12 -0700 (PDT) Received: from impulse.csl.sri.com (localhost [127.0.0.1]) by impulse.csl.sri.com (8.7.3/8.7.3) with ESMTP id IAA08619 for ; Wed, 18 Sep 1996 08:06:47 -0700 (PDT) Message-Id: <199609181506.IAA08619@impulse.csl.sri.com> To: hackers@freebsd.org Subject: Re: Very Slow Ethernet Link (FreeBSD v. Linux) In-reply-to: Your message of "Tue, 17 Sep 1996 12:39:16 PDT." <199609171939.MAA08743@freefall.freebsd.org> Date: Wed, 18 Sep 1996 08:06:47 -0700 From: Fred Gilham Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jonathan Bresler writes: we routinely get 2.5MB/s (thats bytes, not bits) thru a 100BaseT ethernet connection from wcarchive.cdrom.com to a core router on the internet. On an unloaded 100TX network I did the following: # time rcp -K hyacinth:/usr/x.tar . 0.2u 5.8s 0:15.84 37.9% 313+415k 5+886io 0pf+0w # ls -la total 55962 drwxr-xr-x 2 root wheel 512 Sep 18 07:58 . drwxr-xr-x 23 root wheel 512 Sep 18 07:26 .. -rw-rw-r-- 1 root wheel 57262080 Sep 18 07:58 x.tar # This is about 3.8 MB/sec. Given that the disk on hyacinth only does about 4.4 MB/sec. I think this is pretty good. -Fred Gilham gilham@csl.sri.com From owner-freebsd-hackers Wed Sep 18 09:10:36 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA01633 for hackers-outgoing; Wed, 18 Sep 1996 09:10:36 -0700 (PDT) Received: from pluto.plutotech.com (pluto.plutotech.com [206.168.67.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA01571 for ; Wed, 18 Sep 1996 09:10:29 -0700 (PDT) Received: from shane.plutotech.com (durian@shane.plutotech.com [206.168.67.21]) by pluto.plutotech.com (8.7.5/8.7.5) with ESMTP id KAA12961; Wed, 18 Sep 1996 10:08:53 -0600 (MDT) Message-Id: <199609181608.KAA12961@pluto.plutotech.com> From: "Mike Durian" To: Michael Smith cc: freebsd-hackers@freebsd.org Subject: Re: Special Cycles on the PCI bus In-reply-to: Your message of "Wed, 18 Sep 1996 12:15:12 +0930." Date: Wed, 18 Sep 1996 10:08:53 -0600 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 18 Sep 1996 12:15:12 +0930, Michael Smith wrote: >Mike Durian stands accused of saying: > >There is regular timer-initiated activity with the 'ep' driver which >would appear to correlate with the symptoms you describe below. I ran the tests again in a system with the ethernet card physically removed. The special cycles still appeared. >Is there any other activity (eg. starting of timers) which happens at >some interval before this? Yes, initclocks() is called before the special cycles appear. In init_main.c:main(), the special cycles appear during the call to (*mountroot)(). >Is it possible that you're arriving here >by coincidence or are you breakpointing beforehand? We localized the problem to VOP_OPEN using DDB and breakpoints. We set a breakpoint before the VOP_OPEN call and after. The special cycles only appeared at the second breakpoint. >Did you have the 'ep' driver active at this point in time? If you >disable the 'ep' driver using userconfig, do these cycles still show up? The special cycles show up even if the 3c509 is removed from the system. >There might also be other activity hung off the timer. True, but we were seeing the special cycles immediately (or rather ~11ms) after both the 10ms clock and the 8ms clock. Not just the 10ms clock which is used for the timeout callbacks. >Are they causing you serious grief? They will. We're building custom hardware that uses 4 PCI busses and *lots* of bandwidth. We want to minimize the PCI bus traffic as much as possible. Since none of the chips we are using claim to produce these special cycles (and certainly not illegal ones), they are most likely being produced by some side effect. Perhaps some code is accidentally writing to an undocumented register in the Triton chipset that causes the special cycles. In any case, the special cycles are most likely symptoms of some software bug that might have other unwanted effects. Even if the special cycles are themselves innocuous, we should at least determine why they are generated. mike From owner-freebsd-hackers Wed Sep 18 09:12:03 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA02419 for hackers-outgoing; Wed, 18 Sep 1996 09:12:03 -0700 (PDT) Received: from ALPHA.IS.TCU.EDU (ALPHA.IS.TCU.EDU [138.237.128.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA02329 for ; Wed, 18 Sep 1996 09:11:57 -0700 (PDT) Received: from riogrande.cs.tcu.edu (TCUCS6.CS.TCU.EDU) by ALPHA.IS.TCU.EDU (PMDF V5.0-5 #15868) id <01I9M89W08KG000VVK@ALPHA.IS.TCU.EDU> for hackers@freefall.freebsd.org; Wed, 18 Sep 1996 08:09:01 -0500 (CDT) Received: from sabine.cs.tcu.edu by riogrande.cs.tcu.edu (4.1/SMI-4.1) id AA14540; Wed, 18 Sep 1996 08:07:38 -0500 (CDT) Received: by sabine.cs.tcu.edu (4.1/SMI-4.1) id AA03023; Wed, 18 Sep 1996 08:07:45 -0500 (CDT) Date: Wed, 18 Sep 1996 08:07:44 -0500 (CDT) From: Tam Weng Seng Subject: Re: Slow Etherlink To: hackers@freefall.freebsd.org Reply-to: tam@riogrande.cs.tcu.edu Message-id: 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 folks, I have followed this thread for a while now, and I just thought that I would share my observation of my 3Com 509(b?) Card. I had put this card in a 486/33 Mhz, and it is now in a 586-133 Mhz (I forgot who made these chips), and in both cases I was able to make transfers of up to 100 Kb/s. What is even stranger is the fact that I was running this under FreeBSD 2.1.0-release (and later current of that period). Subsequently, although I know very little about hardware. I find it hard to understand how the card would work, if the card was misconfigured. I say this because I have always done ftp installs, and because the interupt that my 3 Com card is using is not the default one the kernel expects (Some silly conflict). This means that if I should forget to tell the kernel about it with the -c flag, that the probes will not even find the card. Or maybe I did something else, that is equally dumb. Furthermore, I do not think that it is PnP that is causing his problems either. When my card was put in PnP mode by Win95 (no flames please, I use it to learn how to use the visual compilers), FreeBSD seemed to be unable to use the card. On the other hand, with PnP disabled, it worked a charm. :) Ftp'ing the entire OS from FreeFall, even though we go through the "friendly" SprintLink, still managed transfers between 50-80 KB/s. So I think something else is wrong. Maybe operator error ;). Cause it seems to work very well for me. I guess I will find out when I get a another HDD soon, as I plan to play with Linux, as well as FreeBSD on the 586, with the 3Com card. What do you guys think would be a good benchmark ;) ??? In conclusion, how do you get transfer > 1000 KB/s ??? I have never seen anything over 150 KB/s. Although, I have to admit that do not connect to sites that are on the same ethernet segment, and that all the dormitories (I think), goes trough a Cisco router (don't know the model). Otherwise, I just want to say a big thank you to all the developers for bring me a wanderful learning tool. :) +---------------+----------------------------+---------------+ | Tam Weng Seng | May the source be with you | Tan Yongcheng | +---------------+----------------------------+---------------+ From owner-freebsd-hackers Wed Sep 18 09:16:58 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA04971 for hackers-outgoing; Wed, 18 Sep 1996 09:16:58 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA04921; Wed, 18 Sep 1996 09:16:51 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id SAA00422; Wed, 18 Sep 1996 18:16:17 +0200 (MET DST) To: "Mike Durian" cc: Michael Smith , freebsd-hackers@freebsd.org Subject: Re: Special Cycles on the PCI bus In-reply-to: Your message of "Wed, 18 Sep 1996 10:08:53 MDT." <199609181608.KAA12961@pluto.plutotech.com> Date: Wed, 18 Sep 1996 18:16:16 +0200 Message-ID: <420.843063376@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199609181608.KAA12961@pluto.plutotech.com>, "Mike Durian" writes: Hmm, my best suggestion would be to add code to flip a bit somewhere for instance on lpt0 and narrow down the window as much as you can. Mounting of the root is often the first real disk-access, so it could be related to disk-activity. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-hackers Wed Sep 18 09:26:55 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA09097 for hackers-outgoing; Wed, 18 Sep 1996 09:26:55 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA09065 for ; Wed, 18 Sep 1996 09:26:48 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id JAA12461; Wed, 18 Sep 1996 09:26:50 -0700 (PDT) Message-Id: <199609181626.JAA12461@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: "Mike Durian" cc: Michael Smith , freebsd-hackers@freebsd.org Subject: Re: Special Cycles on the PCI bus In-reply-to: Your message of "Wed, 18 Sep 1996 10:08:53 MDT." <199609181608.KAA12961@pluto.plutotech.com> From: David Greenman Reply-To: dg@root.com Date: Wed, 18 Sep 1996 09:26:50 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>Are they causing you serious grief? > > They will. We're building custom hardware that uses 4 PCI busses and >*lots* of bandwidth. We want to minimize the PCI bus traffic as >much as possible. > Since none of the chips we are using claim to produce these >special cycles (and certainly not illegal ones), they are most likely >being produced by some side effect. Perhaps some code is accidentally >writing to an undocumented register in the Triton chipset that causes >the special cycles. In any case, the special cycles are most likely >symptoms of some software bug that might have other unwanted effects. >Even if the special cycles are themselves innocuous, we should at least >determine why they are generated. Perhaps they are caused by the inb(0x84)'s that are used as time delays in a couple places of the kernel. The inb(0x84) is supposed to be an unused port and thus should take about 1.25us to read from. This isn't always true, however, as people have pointed out in the past. We should probably replace the last few places where these are used with a calibrated wait loop. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Wed Sep 18 09:31:38 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA10823 for hackers-outgoing; Wed, 18 Sep 1996 09:31:38 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA10608 for ; Wed, 18 Sep 1996 09:31:04 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id JAA12503; Wed, 18 Sep 1996 09:31:14 -0700 (PDT) Message-Id: <199609181631.JAA12503@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: tam@riogrande.cs.tcu.edu cc: hackers@freefall.freebsd.org Subject: Re: Slow Etherlink In-reply-to: Your message of "Wed, 18 Sep 1996 08:07:44 CDT." From: David Greenman Reply-To: dg@root.com Date: Wed, 18 Sep 1996 09:31:13 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Hi folks, > I have followed this thread for a while now, and I just thought >that I would share my observation of my 3Com 509(b?) Card. I had put this >card in a 486/33 Mhz, and it is now in a 586-133 Mhz (I forgot who made >these chips), and in both cases I was able to make transfers of up to 100 >Kb/s. What is even stranger is the fact that I was running this under >FreeBSD 2.1.0-release (and later current of that period). > Subsequently, although I know very little about hardware. I find >it hard to understand how the card would work, if the card was >misconfigured. I say this because I have always done ftp installs, and >because the interupt that my 3 Com card is using is not the default one >the kernel expects (Some silly conflict). This means that if I should >forget to tell the kernel about it with the -c flag, that the probes will >not even find the card. Or maybe I did something else, that is equally >dumb. It can work because in addition to the interrupt, there is also a 1 second timer that goes off that checks for any transmit/receive completions. This allows the card to limp along when interrupts aren't working. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Wed Sep 18 09:36:00 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA12376 for hackers-outgoing; Wed, 18 Sep 1996 09:36:00 -0700 (PDT) Received: from ceres.bios.unc.edu (ceres.bios.unc.edu [152.2.94.225]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA12329 for ; Wed, 18 Sep 1996 09:35:52 -0700 (PDT) Received: from localhost (walter@localhost) by ceres.bios.unc.edu (8.7.5/8.6.12) with SMTP id MAA12642 for ; Wed, 18 Sep 1996 12:38:13 -0400 (EDT) X-Authentication-Warning: ceres.bios.unc.edu: walter owned process doing -bs Date: Wed, 18 Sep 1996 12:38:13 -0400 (EDT) From: Bruce Walter To: hackers@freebsd.org Subject: User PPP buffer space Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello all, I remember a thread a while back about user PPP running out of buffer space quickly or with flood pings. If I remember correctly it was due to quench not being issued in response to ENOBUFS. My problem is similar: I have a 28.8 connection which stays nailed up 24/7. After a random (but large, approx. 110,000) number of seconds this error pops up and the link goes phase dead, forcing a kill -9 on ppp and usually the recreation of tun0. I am running 2.2-SNAP-960612 on both machines, but thought this was fixed before then. Sorry if this has been fixed in subsequent snaps (I've been too busy to upgrade). If not, does anyone have any ideas? - Bruce ======================================================================== || Bruce Walter || CB #7400 McGavran-Greenberg Hall || || Information Technology Support || Chapel Hill, NC 27599-7400 || || Department of Biostatistics || Tel: 919-966-7279 || || University of North Carolina || Fax: 919-966-3804 || ======================================================================== || BSD Unix -- It's not just a job, it's a way of life! || ======================================================================== From owner-freebsd-hackers Wed Sep 18 10:47:51 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA17439 for hackers-outgoing; Wed, 18 Sep 1996 10:47:51 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA17412 for ; Wed, 18 Sep 1996 10:47:48 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id KAA27333; Wed, 18 Sep 1996 10:41:26 -0700 (PDT) To: rhh@ct.picker.com cc: darrylo@hpnmhjw.sr.hp.com (Darryl Okahata), hackers@freebsd.org Subject: Re: fdisk changes, anyone? In-reply-to: Your message of "Wed, 18 Sep 1996 08:39:13 EDT." <199609181239.IAA13016@elmer.ct.picker.com> Date: Wed, 18 Sep 1996 10:41:26 -0700 Message-ID: <27331.843068486@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > To Jordan's point about specifying the partition info using > command-line options (to avoid having to use a temp file with this method), > a compromise solution might be to be able to specify a "-" on the command > line for the config file path to allow the config file to be read from > stdin. Hey, that'd work too! :-) Jordan From owner-freebsd-hackers Wed Sep 18 11:09:05 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA28114 for hackers-outgoing; Wed, 18 Sep 1996 11:09:05 -0700 (PDT) Received: from Octopussy (Octopussy.MI.Uni-Koeln.DE [134.95.212.20]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA28062 for ; Wed, 18 Sep 1996 11:08:57 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-45.slip.Uni-Koeln.DE) by Octopussy with SMTP id AA09946 (5.67b/IDA-1.5 for ); Wed, 18 Sep 1996 20:08:48 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id UAA16448; Wed, 18 Sep 1996 20:08:47 +0200 (MET DST) Date: Wed, 18 Sep 1996 20:08:47 +0200 (MET DST) Message-Id: <199609181808.UAA16448@x14.mi.uni-koeln.de> From: Stefan Esser To: hackers@freebsd.org Subject: Re: Adding a second NCR 810 controller In-Reply-To: <199609162119.OAA27337@seabass.progroup.com> References: <199609170052.AAA15503@al.imforei.apana.org.au> <199609162119.OAA27337@seabass.progroup.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Craig Shaver writes: > > > > > > > In article <199609161051.MAA11794@iaehv.IAEhv.nl> you wrote: > > > > : Hi, > > > > Gday! > > > > : What do I need to do to add a second NCR 810 controller to a 2.1.5 system? > > > > Just chuck it in. Both cards can be set to INT A, since the interupts > > are unique for each PCI slot. > > > > Do you need to rebuild the kernel? In my kernel I added a line for the > 2nd NCR controller: > > controller ncr0 > controller ncr1 > > And then I rebuilt the kernel. Is this an unnecessary step? Yes, it is unneccesary, but, well, it does no harm :) In fact you may expect that each PCI device driver can be used for a (near) arbitrary number of cards. The reason for multiple device entries in the config file is usually, that ISA cards need very specific attach addresses, and if you have multiple cards, then each individual one has to be made known to the kernel. PCI cards are auto-configured by the PCI BIOS, and the drivers use whatever the PCI BIOS choose for the card's registers and memory regions. Regards, STefan From owner-freebsd-hackers Wed Sep 18 11:09:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA28316 for hackers-outgoing; Wed, 18 Sep 1996 11:09:34 -0700 (PDT) Received: from glacier.cold.org (glacier.sunrem.com [206.81.134.54]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA28298 for ; Wed, 18 Sep 1996 11:09:32 -0700 (PDT) Received: (from brandon@localhost) by glacier.cold.org (8.7.5/8.7.3) id MAA07942; Wed, 18 Sep 1996 12:11:00 -0600 (MDT) Date: Wed, 18 Sep 1996 12:10:59 -0600 (MDT) From: Brandon Gillespie To: freebsd-hackers@freebsd.org Subject: machine/endian.h: network byte order macros Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Compiling with '-Wall -pedantic' when using these macros (i.e. ntohs) gives the warning: net.c: In function `get_server_socket': net.c:129: warning: ANSI C forbids braced-groups within expressions net.c: In function `io_event_wait': net.c:249: warning: ANSI C forbids braced-groups within expressions net.c: In function `non_blocking_connect': net.c:317: warning: ANSI C forbids braced-groups within expressions Although trivial, the problem can be fixed by just removing '(' ')' from the outside of the macro, leaving '{' '}' there. This likely causes a problem with how its used (as a function), which would then lead one to think perhaps it should just be a function? *shrug* -Brandon Gillespie From owner-freebsd-hackers Wed Sep 18 12:41:09 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA15988 for hackers-outgoing; Wed, 18 Sep 1996 12:41:09 -0700 (PDT) Received: from gizmo.dimension.net (gizmo.dimension.net [206.49.66.101]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA15925 for ; Wed, 18 Sep 1996 12:41:03 -0700 (PDT) Received: (from jaitken@localhost) by gizmo.dimension.net (8.7.5/8.7.3) id PAA03638 for hackers@freebsd.org; Wed, 18 Sep 1996 15:40:06 -0400 (EDT) From: Jeff Aitken Message-Id: <199609181940.PAA03638@gizmo.dimension.net> Subject: AHC question To: hackers@freebsd.org Date: Wed, 18 Sep 1996 15:40:06 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL26 (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 Hello, I recently "upgraded" our main mail/WWW server from Linux 1.8.somethingorother to FreeBSD-2.1.5. Last night the machine hung, and this morning a coworker rebooted it before I could try to log in to the console. The symptoms that he reported were that the machine responded to pings but nothing else. Digging through the syslog, I found this: Sep 17 22:19:29 gizmo /kernel: sd1(ahc0:1:0): timed out in dataout phase, SCSISIGI == 0x0 Sep 17 22:19:32 gizmo /kernel: sd1(ahc0:1:0): BUS DEVICE RESET message queued. Sep 17 22:19:34 gizmo /kernel: Bus Device Reset Message Sent Sep 17 22:19:35 gizmo /kernel: sd1(ahc0:1:0): Bus Device Reset delivered. 2 SCBs aborted Sep 17 22:19:35 gizmo /kernel: sd1(ahc0:1:0): UNIT ATTENTION asc:29,0 Sep 17 22:19:35 gizmo /kernel: sd1(ahc0:1:0): Power on, reset, or bus device reset occurred Sep 17 22:19:35 gizmo /kernel: , retries:4 The very net log entry was the start of the bootup messages, which I've included at the end of this message in the event that they're helpful. I don't know enough to decipher the above messages, other than they certainly seem to point to sd1 (a Micropolis 4221) or the Adaptec 2940 SCSI controller itself. If there's any more information I can provide that will help, please let me know. The only hardware that changed during the upgrade process was the Ethernet card -- the machine had an old 3c590 in it which didn't seem to work with FreeBSD, so I put a brand new SMC EtherPower card in. Any suggestions? I'm going to come under a lot of fire if our server doesn't work reliably when I was the one who pushed for FreeBSD! :-) BTW: Other than this particular problem, which is likely not FreeBSD at all, you guys outdid yourselves yet again. I've installed 2.1.5 a couple times now (including on my box at home) and it seems really rock solid. Thanks for any pointers. Please CC to me since I'm not currently subscribed to -hackers. --Jeff Sep 18 08:34:46 gizmo /kernel: FreeBSD 2.1.5-RELEASE #0: Wed Jul 17 03:09:31 1996 Sep 18 08:34:46 gizmo /kernel: jkh@whisker.cdrom.com:/usr/src/sys/compile/GENERIC Sep 18 08:34:46 gizmo /kernel: CPU: 166-MHz Pentium 735\90 or 815\100 (Pentium-class CPU) Sep 18 08:34:46 gizmo /kernel: Origin = "GenuineIntel" Id = 0x52c Stepping=12 Sep 18 08:34:46 gizmo /kernel: Features=0x1bf Sep 18 08:34:46 gizmo /kernel: real memory = 67108864 (65536K bytes) Sep 18 08:34:47 gizmo /kernel: avail memory = 62840832 (61368K bytes) Sep 18 08:34:47 gizmo /kernel: Probing for devices on PCI bus 0: Sep 18 08:34:47 gizmo /kernel: chip0 rev 2 on pci0:0 Sep 18 08:34:47 gizmo /kernel: chip1 rev 2 on pci0:7:0 Sep 18 08:34:47 gizmo /kernel: chip2 rev 2 on pci0:7:1 Sep 18 08:34:47 gizmo /kernel: vga0 rev 9 on pci0:17 Sep 18 08:34:47 gizmo /kernel: de0 rev 17 int a irq 9 on pci0:18 Sep 18 08:34:47 gizmo /kernel: de0: DC21041 [10Mb/s] pass 1.1 Ethernet address 00:00:c0:80:61:e8 Sep 18 08:34:51 gizmo /kernel: ahc0 rev 0 int a irq 10 on pci0:19 Sep 18 08:34:51 gizmo /kernel: ahc0: aic7880 Single Channel, SCSI Id=7, 16 SCBs Sep 18 08:34:51 gizmo /kernel: ahc0 waiting for scsi devices to settle Sep 18 08:34:51 gizmo /kernel: (ahc0:0:0): "SEAGATE ST15150N 0022" type 0 fixed SCSI 2 Sep 18 08:34:51 gizmo /kernel: sd0(ahc0:0:0): Direct-Access 4095MB (8388315 512 byte sectors) Sep 18 08:34:51 gizmo /kernel: (ahc0:1:0): "MICROP 4221-09MZ Q4D HT02" type 0 fixed SCSI 2 Sep 18 08:34:51 gizmo /kernel: sd1(ahc0:1:0): Direct-Access 1955MB (4004219 512 byte sectors) Sep 18 08:34:51 gizmo /kernel: (ahc0:2:0): "MICROP 4221-09MZ Q4D HT02" type 0 fixed SCSI 2 Sep 18 08:34:51 gizmo /kernel: sd2(ahc0:2:0): Direct-Access 1955MB (4004219 512 byte sectors) ep 18 08:34:51 gizmo /kernel: Probing for devices on the ISA bus: Sep 18 08:34:51 gizmo /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Sep 18 08:34:51 gizmo /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> Sep 18 08:34:51 gizmo /kernel: ed0: disabled, not probed. Sep 18 08:34:51 gizmo /kernel: ed1: disabled, not probed. Sep 18 08:34:51 gizmo /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Sep 18 08:34:51 gizmo /kernel: sio0: type 16550A Sep 18 08:34:51 gizmo /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa Sep 18 08:34:51 gizmo /kernel: sio1: type 16550A Sep 18 08:34:51 gizmo /kernel: sio2: disabled, not probed. Sep 18 08:34:51 gizmo /kernel: sio3: disabled, not probed. Sep 18 08:34:51 gizmo /kernel: lpt0 at 0x378-0x37f irq 7 on isa Sep 18 08:34:51 gizmo /kernel: lpt0: Interrupt-driven port Sep 18 08:34:51 gizmo /kernel: lp0: TCP/IP capable interface Sep 18 08:34:51 gizmo /kernel: lpt1: disabled, not probed. Sep 18 08:34:52 gizmo /kernel: mse0: disabled, not probed. Sep 18 08:34:52 gizmo /kernel: psm0: disabled, not probed. Sep 18 08:34:52 gizmo /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Sep 18 08:34:52 gizmo /kernel: fdc0: NEC 72065B Sep 18 08:34:52 gizmo /kernel: fd0: 1.44MB 3.5in Sep 18 08:34:52 gizmo /kernel: wdc0: disabled, not probed. Sep 18 08:34:52 gizmo /kernel: wdc1: disabled, not probed. Sep 18 08:34:52 gizmo /kernel: bt0: disabled, not probed. Sep 18 08:34:52 gizmo /kernel: uha0: disabled, not probed. Sep 18 08:34:52 gizmo /kernel: aha0: disabled, not probed. Sep 18 08:34:52 gizmo /kernel: aic0: disabled, not probed. Sep 18 08:34:52 gizmo /kernel: nca0: disabled, not probed. Sep 18 08:34:52 gizmo /kernel: nca1: disabled, not probed. Sep 18 08:34:52 gizmo /kernel: sea0: disabled, not probed. Sep 18 08:34:52 gizmo /kernel: wt0: disabled, not probed. Sep 18 08:34:52 gizmo /kernel: mcd0: disabled, not probed. Sep 18 08:34:52 gizmo /kernel: matcdc0: disabled, not probed. Sep 18 08:34:52 gizmo /kernel: scd0: disabled, not probed. Sep 18 08:34:52 gizmo /kernel: ie0: disabled, not probed. Sep 18 08:34:52 gizmo /kernel: ep0: disabled, not probed. Sep 18 08:34:53 gizmo /kernel: ix0: disabled, not probed. Sep 18 08:34:53 gizmo /kernel: le0: disabled, not probed. Sep 18 08:34:53 gizmo /kernel: lnc0: disabled, not probed. Sep 18 08:34:53 gizmo /kernel: ze0: disabled, not probed. Sep 18 08:34:53 gizmo /kernel: zp0: disabled, not probed. Sep 18 08:34:53 gizmo /kernel: npx0 on motherboard Sep 18 08:34:53 gizmo /kernel: npx0: INT 16 interface Sep 18 08:34:53 gizmo /kernel: de0: enabling 10baseT/UTP port Sep 18 08:34:53 gizmo /kernel: changing root device to sd0a Sep 18 08:34:53 gizmo /kernel: WARNING: / was not properly dismounted. Sep 18 08:34:46 gizmo named[70]: starting. named LOCAL-960717.011537 Wed Jul 17 01:15:37 1996 jkh@whisker.cdrom.com:/usr/src/usr.sbin/named Sep 18 08:34:47 gizmo named[71]: Ready to answer queries. Sep 18 08:34:53 gizmo lpd[122]: restarted -- Jeff Aitken jaitken@dimension.net From owner-freebsd-hackers Wed Sep 18 13:47:05 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA17077 for hackers-outgoing; Wed, 18 Sep 1996 13:47:05 -0700 (PDT) Received: from relay.mfa.com (MFA.COM [199.88.143.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA16992; Wed, 18 Sep 1996 13:46:47 -0700 (PDT) Received: from stimpy.mfa.com ([192.168.1.10]) by relay.mfa.com via smtpd (for freefall.FreeBSD.ORG [204.216.27.18]) with SMTP; 18 Sep 1996 20:41:52 UT Received: from fifield-pc (fifield-pc.mfa.com) by stimpy.mfa.com with SMTP (1.37.109.16/16.2) id AA096391449; Wed, 18 Sep 1996 13:30:49 -0500 Message-Id: <324041CA.4806@mfa.com> Date: Wed, 18 Sep 1996 13:39:06 -0500 From: "Daniel C. Fifield" Organization: McHugh Freeman X-Mailer: Mozilla 2.02 (Win16; I) Mime-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-bugs@freebsd.org Subject: [Fwd: Silo Overflows?] Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk X-Mozilla-Status: 0001 Message-ID: <3240417A.6B36@mfa.com> Date: Wed, 18 Sep 1996 13:37:46 -0500 From: "Daniel C. Fifield" Organization: McHugh Freeman X-Mailer: Mozilla 2.02 (Win16; I) MIME-Version: 1.0 To: freebsd-isp@freebsd.org Subject: Silo Overflows? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Help Please, I have read through all the mail archives and tried to adjust my silo trigger down to 8 in sio.c. My server goes crazy and starts reporting silo overflows on all the serial ports on the BOCA 16. I am running 2.1.0 on a P90 with 48MB of ram. I did not see this problem until I switched from user ppp to the kernel ppp. Could this have anything to do with it? I also installed the modified getty to allow direct PAP authentication. Please help! Sincerely, Daniel C. Fifield From owner-freebsd-hackers Wed Sep 18 16:25:31 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA23276 for hackers-outgoing; Wed, 18 Sep 1996 16:25:31 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA23246 for ; Wed, 18 Sep 1996 16:25:28 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id QAA00379 for ; Wed, 18 Sep 1996 16:25:20 -0700 (PDT) Message-Id: <199609182325.QAA00379@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: hackers@freebsd.org Subject: FreeBSD smc program to set smc card? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 18 Sep 1996 16:25:19 -0700 From: Amancio Hasty Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, A little while ago there was a small discussion about the possibility of writing such code for FreeBSD. So where is it ? 8) Tnks, Amancio From owner-freebsd-hackers Wed Sep 18 18:18:54 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA01004 for hackers-outgoing; Wed, 18 Sep 1996 18:18:54 -0700 (PDT) Received: from research.gate.nec.co.jp (research.gate.nec.co.jp [202.32.8.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA00961 for ; Wed, 18 Sep 1996 18:18:50 -0700 (PDT) Received: from sbl-gw.sbl.cl.nec.co.jp by research.gate.nec.co.jp (8.7.5+2.6Wbeta6/950912) with ESMTP id KAA21701; Thu, 19 Sep 1996 10:18:35 +0900 (JST) Received: from sirius.sbl.cl.nec.co.jp by sbl-gw.sbl.cl.nec.co.jp (8.7.5+2.6Wbeta6/3.3W6) with ESMTP id KAA29478; Thu, 19 Sep 1996 10:18:30 +0900 (JST) X-Authentication-Warning: sbl-gw.sbl.cl.nec.co.jp: Host nao@sirius [133.207.68.90] claimed to be sirius.sbl.cl.nec.co.jp Received: by sirius.sbl.cl.nec.co.jp (8.7.5+2.6Wbeta6/3.3W6) with UUCP id KAA11113; Thu, 19 Sep 1996 10:18:30 +0900 (JST) Date: Thu, 19 Sep 1996 10:18:30 +0900 (JST) From: Naoki Hamada Message-Id: <199609190118.KAA11113@sirius.sbl.cl.nec.co.jp> References: <199609172045.WAA06494@gvr.win.tue.nl> To: guido@gvr.win.tue.nl CC: dfr@render.com, Guido.vanRooij@nl.cis.philips.com, freebsd-hackers@freebsd.org In-reply-to: Guido van Rooij's message of "Tue, 17 Sep 1996 22:45:08 +0200 (MET DST)" <199609172045.WAA06494@gvr.win.tue.nl> Subject: Re: new if_vx driver on freefall Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, guys! Guido wrote: >If you happen to have a 3c590, could you undef the BROKEN_AVAIL define and >see if you card still works after doing a ping -f -s 1000 >(as root of course). I ported Guido's new if_vx to 960801-SNAP and tried it. (A patch follows my message.) It works very well with and without BROKEN_AVAIL though my adapter still worked with the old vx driver :-) Anyway, it is far better than our old and broken vx driver, isn't it? -nao --- if_vx.c Tue Sep 17 16:19:42 1996 +++ /sys/pci/if_vx.c Thu Sep 19 09:21:11 1996 @@ -232,7 +232,7 @@ ifp->if_unit = unit; ifp->if_name = "vx"; ifp->if_mtu = ETHERMTU; - ifp->if_flags = IFF_BROADCAST | IFF_SIMPLEX | IFF_NOTRAILERS | IFF_MULTICAST; + ifp->if_flags = IFF_BROADCAST | IFF_SIMPLEX | IFF_MULTICAST; ifp->if_output = ether_output; ifp->if_start = vxstart; ifp->if_ioctl = vxioctl; @@ -242,7 +242,7 @@ ether_ifattach(ifp); #if NBPFILTER > 0 - bpfattach(&ifp->if_bpf, ifp, DLT_EN10MB, sizeof(struct ether_header)); + bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif sc->tx_start_thresh = 20; /* probably a good starting point. */ @@ -397,7 +397,7 @@ { register struct vx_softc *sc = &vx_softc[ifp->if_unit]; register struct mbuf *m, *m0; - int sh, len, pad; + int sh, len, pad, s; /* Don't transmit if interface is busy or not running */ if ((sc->arpcom.ac_if.if_flags & (IFF_RUNNING|IFF_OACTIVE)) != IFF_RUNNING) @@ -449,8 +449,8 @@ (len / 4 + sc->tx_start_thresh)); #if NBPFILTER > 0 - if (ifp->if_bpf) { - bpf_mtap(ifp->if_bpf, m0); + if (sc->arpcom.ac_if.if_bpf) { + bpf_mtap(&sc->arpcom.ac_if, m0); } #endif @@ -715,8 +715,8 @@ * Check if there's a BPF listener on this interface. * If so, hand off the raw packet to BPF. */ - if (ifp->if_bpf) { - bpf_mtap(ifp->if_bpf, m); + if (sc->arpcom.ac_if.if_bpf) { + bpf_mtap(&sc->arpcom.ac_if, m); /* * Note that the interface cannot be in promiscuous mode if From owner-freebsd-hackers Wed Sep 18 18:22:26 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA03198 for hackers-outgoing; Wed, 18 Sep 1996 18:22:26 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA03000 for ; Wed, 18 Sep 1996 18:22:07 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id UAA10192; Wed, 18 Sep 1996 20:20:18 -0500 From: Joe Greco Message-Id: <199609190120.UAA10192@brasil.moneng.mei.com> Subject: Re: FreeBSD smc program to set smc card? To: hasty@rah.star-gate.com (Amancio Hasty) Date: Wed, 18 Sep 1996 20:20:18 -0500 (CDT) Cc: hackers@FreeBSD.org In-Reply-To: <199609182325.QAA00379@rah.star-gate.com> from "Amancio Hasty" at Sep 18, 96 04:25:19 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Hi, > > A little while ago there was a small discussion about the > possibility of writing such code for FreeBSD. So where is it ? 8) > > Tnks, > Amancio Volunteers welcome. When I mentioned it to the LynxOS people, who have such a utility, they hinted that SMC had been helpful in providing details about how to do it. ... JG From owner-freebsd-hackers Wed Sep 18 18:33:54 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA09706 for hackers-outgoing; Wed, 18 Sep 1996 18:33:54 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA09681 for ; Wed, 18 Sep 1996 18:33:50 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id BAA12453; Thu, 19 Sep 1996 01:31:23 GMT Date: Thu, 19 Sep 1996 10:31:23 +0900 (JST) From: Michael Hancock To: Terry Lambert cc: dg@Root.COM, bde@zeta.org.au, proff@suburbia.net, freebsd-hackers@FreeBSD.org Subject: thread stacks and protections (was Re: attribute/inode caching) In-Reply-To: <199609171816.LAA04481@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 17 Sep 1996, Terry Lambert wrote: > Personally, I'd like to use page anonymity based protections to establish > Chorus-like access priveledge domains for IPC; specifically, for stacks > capable of being grown by fault for use by threads. I think the POSIX > model is broken: I should not be required to preallocate stack for a > thread just because SVR4 and Solaris have bogus architectures (actually, > the SVR4 VM does *not* impose this limitation: it is a limitation of > the threading code alone. Steve Baumel, the author of the SVR4 VM, and > I discussed this at some length when discussing context sharing models > that would be useful for the NetWare for UNIX product). > How does one implement a u-area concept on top of Chorus? A lot of stuff that used to be in the u-area has been moved out to the proc and other structures in 4.4BSD. Maybe moving the kernel stack out of the u-area and generalizing the proc and u-cred stuff can be a step toward what your talking about. Regards, Mike Hancock From owner-freebsd-hackers Wed Sep 18 18:59:44 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA24634 for hackers-outgoing; Wed, 18 Sep 1996 18:59:44 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA24598 for ; Wed, 18 Sep 1996 18:59:41 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id BAA12584; Thu, 19 Sep 1996 01:59:37 GMT Date: Thu, 19 Sep 1996 10:59:37 +0900 (JST) From: Michael Hancock To: freebsd-hackers@FreeBSD.ORG cc: tech-kern@netbsd.org Subject: spl models and smp (was Re: Some interesting papers on BSD ...) In-Reply-To: <199607090131.LAA28497@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [Just going through some old mail] I was reviewing some spl and locking models for SMP. SVR4/MP combines locking primitives with spl and Solaris is completely redesigned to the implementation to use kernel threads instead for interrupts so it can use the same locking model as the rest of the code. What does Digital, SGI and Sequent do? Regards, Mike Hancock On Tue, 9 Jul 1996, Bruce Evans wrote: > > http://www.eecs.harvard.edu/~chris/papers/cli.ps > > >Draft of paper discussing different hardware synchronization schemes > >on the x86. It discusses how to avoid talking to the PIC/8259 which > >scheduling critical sections. While it probably won't save much on > >lightly loaded systems, I have to wonder how it would effect heavily > >loaded systems such wcarchive.cdrom.com... > > FreeBSD has never used the PIC for spl*(). I fixed spl*() in > 386BSD-0.0. I wouldn't have considered using the PIC in the first > place. Non-multitasking x86 systems normally use cli/sti to get > essentially only two interrupt priorities (the PIC provides some > priority stuff but it is not much use), and this works OK for multi- > tasking provided the cricial sections are short. > > Even cli/sti has become much slower than the memory-based spl's used > in FreeBSD. On Pentium's, pushfl/cli/popfl takes 14 cycles, while > `s = splhigh(); splx(s);' takes 4 cycles assuming no cache or > branch target buffer misses. > > The effect of fixing the spl's was very large even on unloaded systems. > TCP to localhost speeded up by 25% or so on a 486/33, because it > involves a surprisingly large number of spl's (40000/MB IIRC, but this > seems too surprisingly large) and each spl pair used 26 PIC i/o > instructions under 386BSD-0.0. The speedup would be a factor of about > 10-20 on a fast Pentium (from 1 or 2 MB/s to about 20MB/s). Of course, > a better implementation using the PIC would only involve 2 or 4 i/o > instructions per spl pair. > > spl is probably fundamentally wrong for SMP. I haven't thought much > about what to use instead. > > FreeBSD still uses the PIC for masking in-service interrupts. This > could probably be avoided for edge-sensitive interrupts by depending > on the interrupt signal staying high until the interrupt is dismissed > so that another edge doesn't occur until the next i/o completion. At > worst, the PIC could be used only for noisy interrupts. I haven't > tried this because the benefits would be small. Hardware interrupts > are much rarer than spls. > > Bruce > From owner-freebsd-hackers Wed Sep 18 19:33:58 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA09167 for hackers-outgoing; Wed, 18 Sep 1996 19:33:58 -0700 (PDT) Received: from darling.cs.UMD.EDU (10862@darling.cs.umd.edu [128.8.128.115]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA09146 for ; Wed, 18 Sep 1996 19:33:56 -0700 (PDT) From: rohit@cs.UMD.EDU Received: by darling.cs.UMD.EDU (8.7.5/UMIACS-0.9/04-05-88) id WAA18658; Wed, 18 Sep 1996 22:33:53 -0400 (EDT) Date: Wed, 18 Sep 1996 22:33:53 -0400 (EDT) Message-Id: <199609190233.WAA18658@darling.cs.UMD.EDU> To: freebsd-hackers@FreeBSD.ORG Subject: Giant Sized Ethernet Packets Cc: rohit@cs.UMD.EDU Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, I was wondering if it is possible to send giant sized ethernet packets (>1500 bytes say 1550) using the current 'de' driver for the SMC 10/100 DEC 21140 cards. If not, would somebody know if this is possible with the above h/w at all? Any pointers to other h/w over which giant packets are possible would be appreciated. Thanks in advance. Rohit. (rohit@cs.umd.edu) PS: Please CC any repsonses to rohit@cs.umd.edu. I have limited internet connectivity and therefore am currently not subscribed to the hackers list. From owner-freebsd-hackers Wed Sep 18 20:13:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA25041 for hackers-outgoing; Wed, 18 Sep 1996 20:13:25 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA25012 for ; Wed, 18 Sep 1996 20:13:18 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id UAA00670; Wed, 18 Sep 1996 20:13:12 -0700 (PDT) Message-Id: <199609190313.UAA00670@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: rohit@cs.UMD.EDU cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Giant Sized Ethernet Packets In-reply-to: Your message of "Wed, 18 Sep 1996 22:33:53 EDT." <199609190233.WAA18658@darling.cs.UMD.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 18 Sep 1996 20:13:12 -0700 From: Amancio Hasty Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Sure you can send and receive "giant packets" using the smc 10/100 if memory does not fail me the SMC EtherPower (10mbit only) works event better. Just dig around A NetBSD ftp site for technical info on the DEC chipsets. Julian and I work together on the ability to receive big packets packets upto 15Kb for TRW Financial systems. The system is a FreeBSD box using SMC Etherpower 10/100. Julian made the interesting observation that perhaps with todays fast computers and PCI it is probably not worth the effort to extend ethernet in such a way. Regards, Amancio >From The Desk Of rohit@cs.UMD.EDU : > > Hi, > > I was wondering if it is possible to send giant sized ethernet packets (>1500 > bytes say 1550) using the current 'de' driver for the SMC 10/100 DEC 21140 > cards. > > If not, would somebody know if this is possible with the above h/w > at all? > > Any pointers to other h/w over which giant packets are possible would > be appreciated. > > Thanks in advance. > > Rohit. > (rohit@cs.umd.edu) > > PS: Please CC any repsonses to rohit@cs.umd.edu. I have limited internet > connectivity and therefore am currently not subscribed to the > hackers list. > From owner-freebsd-hackers Wed Sep 18 20:13:55 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA25238 for hackers-outgoing; Wed, 18 Sep 1996 20:13:55 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA25201 for ; Wed, 18 Sep 1996 20:13:49 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id WAA01140; Wed, 18 Sep 1996 22:09:31 -0500 (EST) From: "John S. Dyson" Message-Id: <199609190309.WAA01140@dyson.iquest.net> Subject: Re: thread stacks and protections (was Re: attribute/inode caching) To: michaelh@cet.co.jp (Michael Hancock) Date: Wed, 18 Sep 1996 22:09:31 -0500 (EST) Cc: terry@lambert.org, dg@Root.COM, bde@zeta.org.au, proff@suburbia.net, freebsd-hackers@freebsd.org In-Reply-To: from "Michael Hancock" at Sep 19, 96 10:31:23 am Reply-To: dyson@freebsd.org 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 > On Tue, 17 Sep 1996, Terry Lambert wrote: > > > Personally, I'd like to use page anonymity based protections to establish > > Chorus-like access priveledge domains for IPC; specifically, for stacks > > capable of being grown by fault for use by threads. I think the POSIX > > model is broken: I should not be required to preallocate stack for a > > thread just because SVR4 and Solaris have bogus architectures (actually, > > the SVR4 VM does *not* impose this limitation: it is a limitation of > > the threading code alone. Steve Baumel, the author of the SVR4 VM, and > > I discussed this at some length when discussing context sharing models > > that would be useful for the NetWare for UNIX product). > > > > How does one implement a u-area concept on top of Chorus? A lot of stuff > that used to be in the u-area has been moved out to the proc and other > structures in 4.4BSD. Maybe moving the kernel stack out of the u-area and > generalizing the proc and u-cred stuff can be a step toward what your > talking about. > Additionally, we can move the kernel stack very quickly if needed (but it will always take more memory and kva space.) It is even possible to support a dynamic kernel stack. We have been putting together the infrastructure in vm_glue and in pmap to support this for the last 6mos. Setting up the context to support multiple stacks in a process is even simpler (if we need it), all we need to do is to define "what is a stack and where it is", and I can change it in a few hours -- no problem. Don't let what we have stop you from thinking of implementing new things like this -- our VM stuff is basically very flexible. I would like to think that changes like the above are well thought out before we do them though. :-). John From owner-freebsd-hackers Wed Sep 18 20:40:06 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA05297 for hackers-outgoing; Wed, 18 Sep 1996 20:40:06 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id UAA05264 for ; Wed, 18 Sep 1996 20:40:03 -0700 (PDT) Received: from godzilla.zeta.org.au by mail.crl.com with SMTP id AA03429 (5.65c/IDA-1.5 for ); Wed, 18 Sep 1996 20:40:26 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id MAA23999; Thu, 19 Sep 1996 12:56:47 +1000 Date: Thu, 19 Sep 1996 12:56:47 +1000 From: Bruce Evans Message-Id: <199609190256.MAA23999@godzilla.zeta.org.au> To: brandon@glacier.cold.org, freebsd-hackers@freebsd.org Subject: Re: machine/endian.h: network byte order macros Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Compiling with '-Wall -pedantic' when using these macros (i.e. ntohs) >gives the warning: > >net.c: In function `get_server_socket': >net.c:129: warning: ANSI C forbids braced-groups within expressions This warning is correct. ntohs() depends on gcc statement-expressions, and statement-expressions aren't ANSI. >Although trivial, the problem can be fixed by just removing '(' ')' from >the outside of the macro, leaving '{' '}' there. This likely causes a No, this just breaks the statement-expression. `foo = { bar; } is a syntax error even in gcc. Adding __extension__ before the statement- expression seems to work right. >problem with how its used (as a function), which would then lead one to >think perhaps it should just be a function? *shrug* A (non-inline) function would be slower. Bruce From owner-freebsd-hackers Wed Sep 18 20:52:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA11201 for hackers-outgoing; Wed, 18 Sep 1996 20:52:34 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id UAA11168 for ; Wed, 18 Sep 1996 20:52:29 -0700 (PDT) Received: from root.com (implode.root.com) by mail.crl.com with SMTP id AA06414 (5.65c/IDA-1.5 for ); Wed, 18 Sep 1996 20:53:04 -0700 Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id UAA01225; Wed, 18 Sep 1996 20:50:52 -0700 (PDT) Message-Id: <199609190350.UAA01225@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: rohit@cs.UMD.EDU Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Giant Sized Ethernet Packets In-Reply-To: Your message of "Wed, 18 Sep 1996 22:33:53 EDT." <199609190233.WAA18658@darling.cs.UMD.EDU> From: David Greenman Reply-To: dg@root.com Date: Wed, 18 Sep 1996 20:50:52 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I was wondering if it is possible to send giant sized ethernet packets (>1500 >bytes say 1550) using the current 'de' driver for the SMC 10/100 DEC 21140 >cards. No. >If not, would somebody know if this is possible with the above h/w >at all? The answer to this is complicated, but it basically ends up being "no". I just spent about 15 minutes looking over the DC21140 hardware reference manual. It appears that the chip can except larger frames, but it signals an error condition when this occurs, so I don't think you could do this as a normal mode of operation. It also appears that it is possible to generate larger than 1500 byte packets, but the frames wouldn't be ethernet (the type/length field would not be IEEE 802.3) and you'd have to invent your own encapsulation. ...that's how I read it, anyway. Perhaps Matt Thomas will correct me on this. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Wed Sep 18 21:50:22 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA05844 for hackers-outgoing; Wed, 18 Sep 1996 21:50:22 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA05817 for ; Wed, 18 Sep 1996 21:50:13 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id VAA01049; Wed, 18 Sep 1996 21:49:58 -0700 (PDT) Message-Id: <199609190449.VAA01049@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: dg@Root.COM cc: rohit@cs.UMD.EDU, freebsd-hackers@FreeBSD.ORG Subject: Re: Giant Sized Ethernet Packets In-reply-to: Your message of "Wed, 18 Sep 1996 20:50:52 PDT." <199609190350.UAA01225@root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 18 Sep 1996 21:49:57 -0700 From: Amancio Hasty Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >From The Desk Of David Greenman : > >I was wondering if it is possible to send giant sized ethernet packets (>150 0 > >bytes say 1550) using the current 'de' driver for the SMC 10/100 DEC 21140 > >cards. > > No. Sorry, the answer is yes.... Is just that Julian and I did this on the contractual committment and if anybody knows the procedure to integrate or release the code is Julian. Regards, Amancio From owner-freebsd-hackers Wed Sep 18 22:07:33 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA12050 for hackers-outgoing; Wed, 18 Sep 1996 22:07:33 -0700 (PDT) Received: from mail1.infinet.com (mail1.infinet.com [206.103.240.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA12024 for ; Wed, 18 Sep 1996 22:07:26 -0700 (PDT) Received: from armitage.cylatech.com (cmh-p024.infinet.com [206.103.242.24]) by mail1.infinet.com (8.7.3/8.7.3) with SMTP id BAA15805 for ; Thu, 19 Sep 1996 01:07:11 -0400 (EDT) Message-ID: <3240D55A.2BD86F3B@cylatech.com> Date: Thu, 19 Sep 1996 01:08:42 -0400 From: Wilson MacGyver Organization: CylaTech Inc. X-Mailer: Mozilla 3.0Gold (X11; I; Linux 2.0.0 i586) MIME-Version: 1.0 To: hackers@freebsd.org Subject: the old intel aurora board... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a chance to purchase a Aurora board for $800. It has a P6-200 CPU, ATX Case. I know this board use the old orion chipset, though I also heard that some of the later stepings of the chipset is "fixed". Is this a good deal, or should I fork out the extra and get a Venus Board instead? Thanks -- Wilson MacGyver macgyver@cylatech.com -------------------------------------- Veni, Vidi, Concidi. From owner-freebsd-hackers Wed Sep 18 22:08:41 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA12538 for hackers-outgoing; Wed, 18 Sep 1996 22:08:41 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA12507 for ; Wed, 18 Sep 1996 22:08:35 -0700 (PDT) Received: from root.com (implode.root.com) by mail.crl.com with SMTP id AA18991 (5.65c/IDA-1.5 for ); Wed, 18 Sep 1996 22:09:10 -0700 Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id WAA01346; Wed, 18 Sep 1996 22:07:26 -0700 (PDT) Message-Id: <199609190507.WAA01346@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Amancio Hasty Cc: rohit@cs.UMD.EDU, freebsd-hackers@FreeBSD.ORG Subject: Re: Giant Sized Ethernet Packets In-Reply-To: Your message of "Wed, 18 Sep 1996 21:49:57 PDT." <199609190449.VAA01049@rah.star-gate.com> From: David Greenman Reply-To: dg@root.com Date: Wed, 18 Sep 1996 22:07:26 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>From The Desk Of David Greenman : >> >I was wondering if it is possible to send giant sized ethernet packets (>150 >0 >> >bytes say 1550) using the current 'de' driver for the SMC 10/100 DEC 21140 >> >cards. >> >> No. > >Sorry, the answer is yes.... Is just that Julian and I did this on the >contractual committment and if anybody knows the procedure to integrate >or release the code is Julian. The current 'de' driver does NOT support sending larger than 1500 byte frames. If you have patches or something, then that's another thing - but that's not what was asked. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Wed Sep 18 22:16:07 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA15223 for hackers-outgoing; Wed, 18 Sep 1996 22:16:07 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA15165 for ; Wed, 18 Sep 1996 22:16:02 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id WAA01167; Wed, 18 Sep 1996 22:15:52 -0700 (PDT) Message-Id: <199609190515.WAA01167@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: dg@root.com cc: rohit@cs.UMD.EDU, freebsd-hackers@FreeBSD.ORG Subject: Re: Giant Sized Ethernet Packets In-reply-to: Your message of "Wed, 18 Sep 1996 22:07:26 PDT." <199609190507.WAA01346@root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 18 Sep 1996 22:15:52 -0700 From: Amancio Hasty Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >From The Desk Of David Greenman : > >>From The Desk Of David Greenman : > >> >I was wondering if it is possible to send giant sized ethernet packets (> 150 > >0 > >> >bytes say 1550) using the current 'de' driver for the SMC 10/100 DEC 2114 0 > >> >cards. > >> > >> No. > > > >Sorry, the answer is yes.... Is just that Julian and I did this on the > >contractual committment and if anybody knows the procedure to integrate > >or release the code is Julian. > > The current 'de' driver does NOT support sending larger than 1500 byte > frames. If you have patches or something, then that's another thing - but > that's not what was asked. Hi David, I was basically referring to his second point: -- If not, would somebody know if this is possible with the above h/w at all? -- Which I interpret as if the hardware could at least support such operations in the event that the existing driver does not support such operations . Regards, Amancio From owner-freebsd-hackers Wed Sep 18 22:39:07 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA23589 for hackers-outgoing; Wed, 18 Sep 1996 22:39:07 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA23556 for ; Wed, 18 Sep 1996 22:39:03 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id WAA11811; Wed, 18 Sep 1996 22:38:00 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) by whistle.com via smap (V1.3) id sma011807; Wed Sep 18 22:37:47 1996 Date: Wed, 18 Sep 1996 22:36:14 -0700 (PDT) From: Julian Elischer To: rohit@cs.UMD.EDU cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Giant Sized Ethernet Packets In-Reply-To: <199609190233.WAA18658@darling.cs.UMD.EDU> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk funny you should mentionned that.. we use the above mentionned hardware to produce GIANT packets on a proprietary network.. your packets are basically normal Our packets are 15.5KB. i.e. 10x noraml size. If you look in the DE driver you will see references to #ifdef BIG_PACKET these are for us (TRW) On Wed, 18 Sep 1996 rohit@cs.UMD.EDU wrote: > > Hi, > > I was wondering if it is possible to send giant sized ethernet packets (>1500 > bytes say 1550) using the current 'de' driver for the SMC 10/100 DEC 21140 HAH! call that a giant packet? THIS is a Giant packet... "TRW image system "BP protocol" :) > cards. > > If not, would somebody know if this is possible with the above h/w > at all? > > Any pointers to other h/w over which giant packets are possible would ohhhhh yeaaaahhhhh, 1550? just change the mtu :) Our stuff requires a little differnt programming of the chip. > be appreciated. > > Thanks in advance. > > Rohit. > (rohit@cs.umd.edu) > > PS: Please CC any repsonses to rohit@cs.umd.edu. I have limited internet > connectivity and therefore am currently not subscribed to the > hackers list. > From owner-freebsd-hackers Wed Sep 18 23:29:57 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA21897 for hackers-outgoing; Wed, 18 Sep 1996 23:29:57 -0700 (PDT) Received: from casparc.ppp.net (casparc.ppp.net [194.64.12.35]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA21800 for ; Wed, 18 Sep 1996 23:29:44 -0700 (PDT) Received: from ernie by casparc.ppp.net with uucp (Smail3.1.28.1 #1) id m0v3cBh-000HzcC; Thu, 19 Sep 96 08:02 MET DST Received: by ernie.kts.org (Smail3.1.29.1 #5) id m0v3bgB-00000bC; Thu, 19 Sep 96 07:29 MET DST Message-Id: From: hm@kts.org (Hellmuth Michaelis) Subject: Re: Special Cycles on the PCI bus To: dg@root.com Date: Thu, 19 Sep 1996 07:29:39 +0200 (MET DST) Cc: durian@plutotech.com, msmith@atrad.adelaide.edu.au, freebsd-hackers@FreeBSD.org In-Reply-To: <199609181626.JAA12461@root.com> from "David Greenman" at Sep 18, 96 09:26:50 am Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk David Greenman wrote: > Perhaps they are caused by the inb(0x84)'s that are used as time delays in > a couple places of the kernel. The inb(0x84) is supposed to be an unused port > and thus should take about 1.25us to read from. This isn't always true, > however, as people have pointed out in the past. We should probably replace > the last few places where these are used with a calibrated wait loop. And then the old question appears again - how to do (relatively) precise delays in the range of 1 us ... 10 us. As far as i understood Bruce that time, DELAY isn't able to handle this precisely. Has that changed ? hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe (A)bort, (R)etry, (I)nstall BSD ? From owner-freebsd-hackers Thu Sep 19 00:06:50 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA09902 for hackers-outgoing; Thu, 19 Sep 1996 00:06:50 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA09863 for ; Thu, 19 Sep 1996 00:06:44 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id AAA08708; Thu, 19 Sep 1996 00:06:43 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id AAA07580; Thu, 19 Sep 1996 00:06:24 -0700 (PDT) Message-Id: <199609190706.AAA07580@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Jeff Aitken cc: hackers@freebsd.org Subject: Re: AHC question In-reply-to: Your message of Wed, 18 Sep 96 15:40:06 -0400. <199609181940.PAA03638@gizmo.dimension.net> Date: Thu, 19 Sep 1996 00:06:23 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Sep 17 22:19:29 gizmo /kernel: sd1(ahc0:1:0): timed out in dataout phase, SCSISIGI == 0x0 >Sep 17 22:19:32 gizmo /kernel: sd1(ahc0:1:0): BUS DEVICE RESET message queued. >Sep 17 22:19:34 gizmo /kernel: Bus Device Reset Message Sent >Sep 17 22:19:35 gizmo /kernel: sd1(ahc0:1:0): Bus Device Reset delivered. 2 SCBs aborted >Sep 17 22:19:35 gizmo /kernel: sd1(ahc0:1:0): UNIT ATTENTION asc:29,0 >Sep 17 22:19:35 gizmo /kernel: sd1(ahc0:1:0): Power on, reset, or bus device reset occurred >Sep 17 22:19:35 gizmo /kernel: , retries:4 This kind of output many times indicates marginal cabling or termination (although it could be a hard drive problem, too). How long was this machine running Linux on the same hardware? ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-hackers Thu Sep 19 00:32:09 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA19001 for hackers-outgoing; Thu, 19 Sep 1996 00:32:09 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA18912 for ; Thu, 19 Sep 1996 00:31:57 -0700 (PDT) Received: from root.com (implode.root.com) by mail.crl.com with SMTP id AA09720 (5.65c/IDA-1.5 for ); Thu, 19 Sep 1996 00:32:31 -0700 Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id AAA01730; Thu, 19 Sep 1996 00:30:36 -0700 (PDT) Message-Id: <199609190730.AAA01730@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: hm@kts.org Cc: durian@plutotech.com, msmith@atrad.adelaide.edu.au, freebsd-hackers@FreeBSD.org Subject: Re: Special Cycles on the PCI bus In-Reply-To: Your message of "Thu, 19 Sep 1996 07:29:39 +0200." From: David Greenman Reply-To: dg@root.com Date: Thu, 19 Sep 1996 00:30:36 -0700 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >David Greenman wrote: > >> Perhaps they are caused by the inb(0x84)'s that are used as time delays in >> a couple places of the kernel. The inb(0x84) is supposed to be an unused port >> and thus should take about 1.25us to read from. This isn't always true, >> however, as people have pointed out in the past. We should probably replace >> the last few places where these are used with a calibrated wait loop. > >And then the old question appears again - how to do (relatively) precise >delays in the range of 1 us ... 10 us. As far as i understood Bruce that >time, DELAY isn't able to handle this precisely. Has that changed ? Right, this is one of the problems that needs to be resolved first. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Thu Sep 19 01:01:29 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA04289 for hackers-outgoing; Thu, 19 Sep 1996 01:01:29 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA04266 for ; Thu, 19 Sep 1996 01:01:25 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id BAA09460; Thu, 19 Sep 1996 01:01:34 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id BAA07949; Thu, 19 Sep 1996 01:01:15 -0700 (PDT) Message-Id: <199609190801.BAA07949@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Wilson MacGyver cc: hackers@freebsd.org Subject: Re: the old intel aurora board... In-reply-to: Your message of Thu, 19 Sep 96 01:08:42 -0400. <3240D55A.2BD86F3B@cylatech.com> Date: Thu, 19 Sep 1996 01:01:14 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I have a chance to purchase a Aurora board for $800. It has >a P6-200 CPU, ATX Case. >I know this board use the old orion chipset, though I also >heard that some of the later stepings of the chipset is >"fixed". Is this a good deal, or should I fork out the >extra and get a Venus Board instead? I personally wouldn't buy any Intel board, but that's just MHO... See related discussions on the lists recently for alternatives. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-hackers Thu Sep 19 01:48:20 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA22729 for hackers-outgoing; Thu, 19 Sep 1996 01:48:20 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA22654 for ; Thu, 19 Sep 1996 01:48:11 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id SAA05892; Thu, 19 Sep 1996 18:48:08 +1000 (EST) Date: Thu, 19 Sep 1996 18:48:07 +1000 (EST) From: "Daniel O'Callaghan" To: freebsd-hackers@freebsd.org Subject: TCP extensions breaking TCP. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In /etc/sysconfig there is a comment # # Some broken implementations can't handle the RFC 1323 and RFC 1644 # TCP options. If TCP connections randomly hang, try disabling this, # and bug the vendor of the losing equipment. # tcp_extensions=YES The only times I have found these connections to hang are in connecting to other FreeBSD boxes. Last year, a particular 2.0.5 user could not exchange mail with me, and yesterday, a 2.1.5 user could not establish any TCP connections with any of my 2.0.5 or 2.1.5 machines. In the incident last year, the other party turned off tcp extensions, and all worked. This time, *I* turned off the extensions. Question is: why is this only being seen between FreeBSD boxes? I can quite happily talk amongst a network of around 10 FreeBSD machines with OS versions of 2.0.5, 2.1.0R, 2.1.0-stable, 2.1.5R, but suddenly there is a FreeBSD 2.1.5 machine I can't talk to. Does anyone have any ideas regarding what the other party or I have done wrong to wind up in this state. If people would like to test out the other machine (still has extensions on, I believe) it is at pixel.planetx.com.au - try telnetting to its smtp port. One of my machines which has extensions on, and which won't talk to pixel, is tutu.schools.net.au. If anyone can suggest a cause, I'm happy to attempt to do some debugging on this, if pointed in the right direction. Danny From owner-freebsd-hackers Thu Sep 19 02:15:36 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA03646 for hackers-outgoing; Thu, 19 Sep 1996 02:15:36 -0700 (PDT) Received: from orion.webspan.net (root@orion.webspan.net [206.154.70.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA03632 for ; Thu, 19 Sep 1996 02:15:33 -0700 (PDT) Received: from localhost (gpalmer@localhost [127.0.0.1]) by orion.webspan.net (8.7.5/8.6.12) with SMTP id FAA27180; Thu, 19 Sep 1996 05:15:08 -0400 (EDT) X-Authentication-Warning: orion.webspan.net: Host gpalmer@localhost [127.0.0.1] didn't use HELO protocol To: rohit@cs.UMD.EDU cc: freebsd-hackers@FreeBSD.ORG From: "Gary Palmer" Subject: Re: Giant Sized Ethernet Packets In-reply-to: Your message of "Wed, 18 Sep 1996 22:33:53 EDT." <199609190233.WAA18658@darling.cs.UMD.EDU> Date: Thu, 19 Sep 1996 05:15:07 -0400 Message-ID: <27177.843124507@orion.webspan.net> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk rohit@cs.UMD.EDU wrote in message ID <199609190233.WAA18658@darling.cs.UMD.EDU>: > I was wondering if it is possible to send giant sized ethernet packets (>1500 > bytes say 1550) using the current 'de' driver for the SMC 10/100 DEC 21140 > cards. > If not, would somebody know if this is possible with the above h/w > at all? > Any pointers to other h/w over which giant packets are possible would > be appreciated. You can't without violating the IEE 802.3 specs for Ethernet, from what I remember. To go to larger packet sizes use FDDI. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-hackers Thu Sep 19 02:37:01 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA12762 for hackers-outgoing; Thu, 19 Sep 1996 02:37:01 -0700 (PDT) Received: from orion.webspan.net (root@orion.webspan.net [206.154.70.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA12726 for ; Thu, 19 Sep 1996 02:36:53 -0700 (PDT) Received: from localhost (gpalmer@localhost [127.0.0.1]) by orion.webspan.net (8.7.5/8.6.12) with SMTP id FAA28073; Thu, 19 Sep 1996 05:36:40 -0400 (EDT) X-Authentication-Warning: orion.webspan.net: Host gpalmer@localhost [127.0.0.1] didn't use HELO protocol To: "Daniel O'Callaghan" cc: freebsd-hackers@freebsd.org From: "Gary Palmer" Subject: Re: TCP extensions breaking TCP. In-reply-to: Your message of "Thu, 19 Sep 1996 18:48:07 +1000." Date: Thu, 19 Sep 1996 05:36:39 -0400 Message-ID: <28069.843125799@orion.webspan.net> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "Daniel O'Callaghan" wrote in message ID : > If people would like to test out the other machine (still has extensions > on, I believe) it is at pixel.planetx.com.au - try telnetting to its > smtp port. One of my machines which has extensions on, and which won't > talk to pixel, is tutu.schools.net.au. >From a quick traceroute: 12 webnet.gw.au (139.130.3.222) 285.913 ms 290.420 ms 282.206 ms 13 annex0.webnet.com.au (203.8.105.10) 287.745 ms 310.981 ms 285.721 ms 14 pixel.planetx.com.au (203.16.241.66) 460.288 ms 419.488 ms 421.294 ms (thank God for people with nice naming conventions) Annex's (older) TCP implimentation is known to barf on RFC 1323 and 1644. Either update the OS on the Annex or turn off the TCP options support. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-hackers Thu Sep 19 03:02:50 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA22929 for hackers-outgoing; Thu, 19 Sep 1996 03:02:50 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA22881 for ; Thu, 19 Sep 1996 03:02:43 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id LAA21065; Thu, 19 Sep 1996 11:35:32 +0200 From: Luigi Rizzo Message-Id: <199609190935.LAA21065@labinfo.iet.unipi.it> Subject: Re: TCP extensions breaking TCP. To: danny@panda.hilink.com.au (Daniel O'Callaghan) Date: Thu, 19 Sep 1996 11:35:32 +0200 (MET DST) Cc: freebsd-hackers@FreeBSD.ORG, luigi@labinfo.iet.unipi.it (Luigi Rizzo) In-Reply-To: from "Daniel O'Callaghan" at Sep 19, 96 06:47:48 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > In /etc/sysconfig there is a comment > > # > # Some broken implementations can't handle the RFC 1323 and RFC 1644 > # TCP options. If TCP connections randomly hang, try disabling this, > # and bug the vendor of the losing equipment. > # > tcp_extensions=YES > > The only times I have found these connections to hang are in connecting > to other FreeBSD boxes. Last year, a particular 2.0.5 user could not There are several different problems. + some implementations do not expect options in non-SYN segments, hence consider headers as fixed-size structures and have problems in computing segment sizes correctly. In this case, either segment length or checksum fail causing segments to be rejected. Don't think this is the case of FreeBSD, but some terminal servers (Annex) reportedly had this kind of problems. + some implementations fail to parse options correctly. As an example, I think FreeBSD 2.1R (and probably other versions) do not parse correctly WINDOW SCALE options. This can result in deadlocks because the sender and the receiver have different views on the available window and on the possibility to send data. If you look at data transfers, often the connection ends up in firing PERSIST timeouts trying to reopen the send window, and the receiver will not understand the message. I have not tracked down the bug yet, but have never managed to make FreeBSD work with windows >65535. Also, while implementing SACKs, I have noticed occasional deadlocks, possibly caused by the above problem. I am not able to reproduce the problem anymore, but I believe they were caused by erroneous computation of windows. Hopefully I will find some time to work on the problem in a couple of weeks. Luigi ==================================================================== Luigi Rizzo Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it Universita' di Pisa tel: +39-50-568533 via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 http://www.iet.unipi.it/~luigi/ ==================================================================== From owner-freebsd-hackers Thu Sep 19 03:09:02 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA25407 for hackers-outgoing; Thu, 19 Sep 1996 03:09:02 -0700 (PDT) Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA25370 for ; Thu, 19 Sep 1996 03:08:57 -0700 (PDT) Received: (from imb@localhost) by asstdc.scgt.oz.au (8.7.5/BSD4.4) id UAA25409 Thu, 19 Sep 1996 20:08:49 +1000 (EST) From: michael butler Message-Id: <199609191008.UAA25409@asstdc.scgt.oz.au> Subject: Re: TCP extensions breaking TCP. To: danny@panda.hilink.com.au (Daniel O'Callaghan) Date: Thu, 19 Sep 1996 20:08:48 +1000 (EST) Cc: freebsd-hackers@freebsd.org In-Reply-To: from "Daniel O'Callaghan" at Sep 19, 96 06:48:07 pm X-Mailer: ELM [version 2.4 PL24beta] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Daniel O'Callaghan writes: > If people would like to test out the other machine (still has extensions > on, I believe) it is at pixel.planetx.com.au - try telnetting to its > smtp port. One of my machines which has extensions on, and which won't > talk to pixel, is tutu.schools.net.au. > If anyone can suggest a cause, I'm happy to attempt to do some debugging > on this, if pointed in the right direction. Your problems may be related to the annex that pixel is behind, michael From owner-freebsd-hackers Thu Sep 19 03:19:24 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA29930 for hackers-outgoing; Thu, 19 Sep 1996 03:19:24 -0700 (PDT) Received: from monk.via.net (monk.via.net [140.174.204.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA29910 for ; Thu, 19 Sep 1996 03:19:22 -0700 (PDT) Received: (from joe@localhost) by monk.via.net (8.6.11/8.6.12) id DAA11358; Thu, 19 Sep 1996 03:25:53 -0700 Date: Thu, 19 Sep 1996 03:25:53 -0700 From: Joe McGuckin Message-Id: <199609191025.DAA11358@monk.via.net> To: danny@panda.hilink.com.au Subject: Re: TCP extensions breaking TCP. Cc: freebsd-hackers@freebsd.org X-Sun-Charset: US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've seen the enabled TCP extensions hang with SCO. -joe From owner-freebsd-hackers Thu Sep 19 03:54:39 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA17874 for hackers-outgoing; Thu, 19 Sep 1996 03:54:39 -0700 (PDT) Received: from orion.webspan.net (root@orion.webspan.net [206.154.70.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA17833 for ; Thu, 19 Sep 1996 03:54:30 -0700 (PDT) Received: from orion.webspan.net (scanner@orion.webspan.net [206.154.70.41]) by orion.webspan.net (8.7.5/8.6.12) with SMTP id GAA01617; Thu, 19 Sep 1996 06:54:11 -0400 (EDT) Date: Thu, 19 Sep 1996 06:54:11 -0400 (EDT) From: Scanner To: Joe McGuckin cc: danny@panda.hilink.com.au, freebsd-hackers@freebsd.org Subject: Re: TCP extensions breaking TCP. In-Reply-To: <199609191025.DAA11358@monk.via.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 19 Sep 1996, Joe McGuckin wrote: > > I've seen the enabled TCP extensions hang with SCO. More than likely its because the vendor's are not implementing the extensions right and/or not sticking to the RFC's. Theres a way to prove this from a FreeBSD box running 2.1+ . I beliece 2.1 is when T/TCP went in. It can be shown at least in one OS's implementation that it is not implemented right. The easy way to tell is to finger the machine thats having problems most of the time if the extensions are not implemented right or are broke, the finger will freak out and close before any info is gained. -- ===================================| Webspan Inc., ISP Division. FreeBSD 2.1.5 is available now! | Phone: 908-367-8030 ext. 126 -----------------------------------| 500 West Kennedy Blvd., Lakewood, NJ-08701 Turning PCs into Workstations | E-Mail: scanner@webspan.net http://www.freebsd.org | SysAdmin / Network Engineer / Security ===================================| Member BSDNET team! http://www.bsdnet.org From owner-freebsd-hackers Thu Sep 19 04:45:05 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA08802 for hackers-outgoing; Thu, 19 Sep 1996 04:45:05 -0700 (PDT) Received: from darling.cs.UMD.EDU (10862@darling.cs.umd.edu [128.8.128.115]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA08774 for ; Thu, 19 Sep 1996 04:45:00 -0700 (PDT) Received: by darling.cs.UMD.EDU (8.7.5/UMIACS-0.9/04-05-88) id HAA19867; Thu, 19 Sep 1996 07:44:52 -0400 (EDT) Message-Id: <199609191144.HAA19867@darling.cs.UMD.EDU> To: Julian Elischer cc: rohit@cs.UMD.EDU, freebsd-hackers@FreeBSD.ORG Subject: Re: Giant Sized Ethernet Packets In-reply-to: Your message of "Wed, 18 Sep 1996 22:36:14 PDT." Date: Thu, 19 Sep 1996 07:44:51 -0400 From: Rohit Dube Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 18 Sep 1996 22:36:14 -0700 (PDT) julian@current1.whistle.com writes: => => =>funny you should mentionned that.. =>we use the above mentionned hardware to produce GIANT packets =>on a proprietary network.. your packets are basically normal => =>Our packets are 15.5KB. i.e. 10x noraml size. =>If you look in the DE driver you will see references =>to #ifdef BIG_PACKET =>these are for us (TRW) Would it be possible for you or hasty@rah-stargate.com (Amancio) to send me a patch so that I could add this code to the standard FreeBSD 'de' driver. Note that the packets don't have to be 802.3 compliant as far as size goes. My application requires me to take a standard ethernet packet (which could be upto 1500 bytes) add some extra headers, encapsulate the orignal packet + extra header into another (possibly Giant) ethernet frame and send (receive) it onto (from) the wire. => => =>ohhhhh yeaaaahhhhh, 1550? just change the mtu :) I will give that a shot as soon as my internal network is up. However as dg@root.com (David) mentioned, this could create a problem. => =>Our stuff requires a little differnt programming of the chip. => Thanks a lot for the replies. Rohit. (rohit@cs.umd.edu) PS: Please CC any repsonses to rohit@cs.umd.edu. I have limited internet connectivity and therefore am currently not subscribed to the hackers list. From owner-freebsd-hackers Thu Sep 19 05:15:43 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA20617 for hackers-outgoing; Thu, 19 Sep 1996 05:15:43 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA20585 for ; Thu, 19 Sep 1996 05:15:38 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id FAA01452; Thu, 19 Sep 1996 05:15:29 -0700 (PDT) Message-Id: <199609191215.FAA01452@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: Rohit Dube cc: Julian Elischer , freebsd-hackers@FreeBSD.ORG Subject: Re: Giant Sized Ethernet Packets In-reply-to: Your message of "Thu, 19 Sep 1996 07:44:51 EDT." <199609191144.HAA19867@darling.cs.UMD.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 19 Sep 1996 05:15:29 -0700 From: Amancio Hasty Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >From The Desk Of Rohit Dube : > I will give that a shot as soon as my internal network is up. > However as dg@root.com (David) mentioned, this could create a problem. > Well, about giving away patches thats up to Julian and TRW ... I would start by connecting two FreeBSD boxes using UTP. Because other devices in your network may not be able to support the non-standard 802.3 packet sizes. Just play with the driver if you are under 4kb packets you should be okay -- the dec chipsets for both the 10 mbit and the 10/100 mbit chipset have a bug in that they can't handle buffers greater than 2k for the 10mbit chipset and 4k for the 10/100 mbit chipset-- It is a long story however I am sure Julian can elaborate how to get around this problem if anyone cares to transmit / receive 15kb packets 8) I don't have the code with me -- I usually leave my client's code at their site. Have fun, Amancio P.S.: I may be able to help you next week when my P6 200 gets in -- that is I will have two FreeBSD boxes . From owner-freebsd-hackers Thu Sep 19 05:36:47 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA01405 for hackers-outgoing; Thu, 19 Sep 1996 05:36:47 -0700 (PDT) Received: from itsdsv1.enc.edu (itsdsv1.enc.edu [199.93.252.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA01372 for ; Thu, 19 Sep 1996 05:36:43 -0700 (PDT) Received: from dingo.enc.edu (dingo.enc.edu [199.93.252.229]) by itsdsv1.enc.edu (8.6.12/8.6.9) with SMTP id IAA09373 for ; Thu, 19 Sep 1996 08:36:11 -0400 Date: Thu, 19 Sep 1996 08:36:11 -0400 (EDT) From: Charles Owens To: freebsd-hackers@freebsd.org Subject: Re: TCP extensions breaking TCP. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "Gary Palmer" said: >"Daniel O'Callaghan" wrote in message ID >: >> If people would like to test out the other machine (still has extensions >> on, I believe) it is at pixel.planetx.com.au - try telnetting to its >> smtp port. One of my machines which has extensions on, and which won't >> talk to pixel, is tutu.schools.net.au. > >>From a quick traceroute: > >12 webnet.gw.au (139.130.3.222) 285.913 ms 290.420 ms 282.206 ms >13 annex0.webnet.com.au (203.8.105.10) 287.745 ms 310.981 ms 285.721 ms >14 pixel.planetx.com.au (203.16.241.66) 460.288 ms 419.488 ms 421.294 ms > >(thank God for people with nice naming conventions) > >Annex's (older) TCP implimentation is known to barf on RFC 1323 and >1644. Either update the OS on the Annex or turn off the TCP options >support. Related Question: If I'm running a service that its important that ANY internet host can reach (ex. a mail server), should TCP extensions be turned off to ensure compatibility with any devices that may have older TCP implementations (such as we've seen above) ? Or, are such situations so rare that its better to leave them on? Thanks, --- ------------------------------------------------------------------------- Charles Owens Email: owensc@enc.edu "I read somewhere to learn is to Information Technology Services remember... and I've learned that Eastern Nazarene College we've all forgot..." - King's X ------------------------------------------------------------------------- From owner-freebsd-hackers Thu Sep 19 05:50:08 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA09745 for hackers-outgoing; Thu, 19 Sep 1996 05:50:08 -0700 (PDT) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA09714; Thu, 19 Sep 1996 05:50:04 -0700 (PDT) Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.7.5/8.7.3) with SMTP id IAA27562; Thu, 19 Sep 1996 08:50:02 -0400 (EDT) Message-Id: <199609191250.IAA27562@whizzo.transsys.com> X-Mailer: exmh version 1.6.9 8/22/96 To: "Gary Palmer" cc: rohit@cs.UMD.EDU, freebsd-hackers@freebsd.org From: "Louis A. Mamakos" Subject: Re: Giant Sized Ethernet Packets References: <27177.843124507@orion.webspan.net> In-reply-to: Your message of "Thu, 19 Sep 1996 05:15:07 EDT." <27177.843124507@orion.webspan.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 19 Sep 1996 08:50:02 -0400 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > rohit@cs.UMD.EDU wrote in message ID > <199609190233.WAA18658@darling.cs.UMD.EDU>: > > I was wondering if it is possible to send giant sized ethernet packets (>1500 > > bytes say 1550) using the current 'de' driver for the SMC 10/100 DEC 21140 > > cards. > > > If not, would somebody know if this is possible with the above h/w > > at all? > > > Any pointers to other h/w over which giant packets are possible would > > be appreciated. > > You can't without violating the IEE 802.3 specs for Ethernet, from > what I remember. To go to larger packet sizes use FDDI. Yeah, but if you're in an environment where the links are running full duplex and are connected to a Fast Ethernet switch, then you don't have to worry about the collision domain not working "correctly". Being able to support FDDI MTUs would eliminate needless fragmentation which is very time consuming to perform in routers. I'd love to have FDDI (or larger!) size MTU support in Fast Ethernet VLSI. I think that this is likely going to be part of Gigabit ethernet as it develops, and I think we'll eventually see something for Fast Ethernet too, based on converstations with router vendors. Heck, compare the cost of a small Fast Ethernet switch (like the Bay Networks 58000) with an equivilently sized DEC Gigaswitch. And you can't easily find FDDI that runs full duplex, either. Louis Mamakos From owner-freebsd-hackers Thu Sep 19 06:01:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA16640 for hackers-outgoing; Thu, 19 Sep 1996 06:01:25 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.252]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA16609; Thu, 19 Sep 1996 06:01:20 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id PAA02741; Thu, 19 Sep 1996 15:00:49 +0200 (MET DST) To: "Louis A. Mamakos" cc: "Gary Palmer" , rohit@cs.UMD.EDU, freebsd-hackers@FreeBSD.ORG Subject: Re: Giant Sized Ethernet Packets In-reply-to: Your message of "Thu, 19 Sep 1996 08:50:02 EDT." <199609191250.IAA27562@whizzo.transsys.com> Date: Thu, 19 Sep 1996 15:00:48 +0200 Message-ID: <2739.843138048@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199609191250.IAA27562@whizzo.transsys.com>, "Louis A. Mamakos" writ es: >Being able to support FDDI MTUs would eliminate needless fragmentation >which is very time consuming to perform in routers. I'd love to have >FDDI (or larger!) size MTU support in Fast Ethernet VLSI. I think that >this is likely going to be part of Gigabit ethernet as it develops, and I don't think FDDI MTU is enough. I would expect 9180 to be the next good step, since it allows 8k NFS to stay in one packet for instance. I belive this is the standard for SMDS & ATM and other new media. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-hackers Thu Sep 19 06:01:46 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA16805 for hackers-outgoing; Thu, 19 Sep 1996 06:01:46 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA16780 for ; Thu, 19 Sep 1996 06:01:42 -0700 (PDT) Received: from mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by Kitten.mcs.com (8.8.Beta.4/8.8.Beta.3) with SMTP id IAA21397; Thu, 19 Sep 1996 08:01:32 -0500 (CDT) Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.15) id ; Thu, 19 Sep 96 08:01 CDT Received: (from karl@localhost) by Jupiter.Mcs.Net (8.8.Beta.3/8.8.Beta.3) id IAA24016; Thu, 19 Sep 1996 08:01:31 -0500 (CDT) From: Karl Denninger Message-Id: <199609191301.IAA24016@Jupiter.Mcs.Net> Subject: Re: TCP extensions breaking TCP. To: danny@panda.hilink.com.au (Daniel O'Callaghan) Date: Thu, 19 Sep 1996 08:01:31 -0500 (CDT) Cc: freebsd-hackers@freebsd.org In-Reply-To: from "Daniel O'Callaghan" at Sep 19, 96 06:48:07 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > In /etc/sysconfig there is a comment > > # > # Some broken implementations can't handle the RFC 1323 and RFC 1644 > # TCP options. If TCP connections randomly hang, try disabling this, > # and bug the vendor of the losing equipment. > # > tcp_extensions=YES > > The only times I have found these connections to hang are in connecting > to other FreeBSD boxes. Last year, a particular 2.0.5 user could not > exchange mail with me, and yesterday, a 2.1.5 user could not establish > any TCP connections with any of my 2.0.5 or 2.1.5 machines. > > In the incident last year, the other party turned off tcp extensions, and > all worked. This time, *I* turned off the extensions. Question is: why > is this only being seen between FreeBSD boxes? I can quite happily talk > amongst a network of around 10 FreeBSD machines with OS versions of > 2.0.5, 2.1.0R, 2.1.0-stable, 2.1.5R, but suddenly there is a FreeBSD > 2.1.5 machine I can't talk to. > > Does anyone have any ideas regarding what the other party or I have done > wrong to wind up in this state. > > If people would like to test out the other machine (still has extensions > on, I believe) it is at pixel.planetx.com.au - try telnetting to its > smtp port. One of my machines which has extensions on, and which won't > talk to pixel, is tutu.schools.net.au. > > If anyone can suggest a cause, I'm happy to attempt to do some debugging > on this, if pointed in the right direction. > > Danny Win95 blows chunks if these are enabled and the connection comes in over an Ethernet (say, from an ISDN user). -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1 from $600 monthly; speeds to DS-3 available | 23 Chicagoland Prefixes, 13 ISDN, much more Voice: [+1 312 803-MCS1 x219]| Email to "info@mcs.net" WWW: http://www.mcs.net/ Fax: [+1 312 248-9865] | Home of Chicago's only FULL Clarinet feed! From owner-freebsd-hackers Thu Sep 19 06:18:33 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA26801 for hackers-outgoing; Thu, 19 Sep 1996 06:18:33 -0700 (PDT) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA26757 for ; Thu, 19 Sep 1996 06:18:29 -0700 (PDT) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id IAA11956; Thu, 19 Sep 1996 08:16:40 -0500 Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3) id sma011950; Thu Sep 19 08:16:34 1996 Received: from jake.lodgenet.com (jake.lodgenet.com [204.124.120.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id IAA20856; Thu, 19 Sep 1996 08:17:25 -0500 Received: from localhost (localhost [127.0.0.1]) by jake.lodgenet.com (8.7.5/8.6.12) with SMTP id IAA22700; Thu, 19 Sep 1996 08:17:17 -0500 (CDT) Message-Id: <199609191317.IAA22700@jake.lodgenet.com> X-Authentication-Warning: jake.lodgenet.com: Host localhost [127.0.0.1] didn't use HELO protocol X-Mailer: exmh version 1.6.2 7/18/95 To: Amancio Hasty cc: hackers@freebsd.org Subject: Re: FreeBSD smc program to set smc card? In-reply-to: Your message of "Wed, 18 Sep 1996 16:25:19 PDT." <199609182325.QAA00379@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 19 Sep 1996 08:17:17 -0500 From: "Eric L. Hernes" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Amancio Hasty writes: > > >Hi, > >A little while ago there was a small discussion about the >possibility of writing such code for FreeBSD. So where is it ? 8) > As I remember, someone mentioned that there's some linux utilities to configure ethernet cards at: ftp://cesdis1.gsfc.nasa.gov/pub/linux/setup/ ftp://sunsite.unc.edu/system/Network/management/ewrk3tools-0.20.tar.gz wdsetup-0.6a.tar.gz is the smc setup program. the following sed script does most of the work to get 'em to compile, dunno if they run though. I'll try to test the ones I've got hardware for. sed -e 's:ioperm([^)]*):open("/dev/io", O_RDWR):' \ -e -e 's,asm/io.h,machine/cpufunc.h,' > > Tnks, > Amancio > > > eric. -- erich@lodgenet.com http://rrnet.com/~erich erich@rrnet.com From owner-freebsd-hackers Thu Sep 19 06:27:47 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA02070 for hackers-outgoing; Thu, 19 Sep 1996 06:27:47 -0700 (PDT) Received: from firewall.mc.com (firewall.mc.com [192.148.197.15]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA02033 for ; Thu, 19 Sep 1996 06:27:41 -0700 (PDT) Received: by firewall.mc.com id AA27894 (5.65c/IDA-1.4.4 for ); Thu, 19 Sep 1996 09:27:07 -0400 Received: from jericho.mc.com(192.233.16.4) by firewall via smap (V1.3) id sma027889; Thu Sep 19 09:26:44 1996 Received: from bach (bach [192.233.16.203]) by jericho (8.6.11/8.6.11) with SMTP id JAA10374; Thu, 19 Sep 1996 09:26:43 -0400 From: "Gordon W. Ross" Received: by bach (4.1//ident-1.0) id AA03526; Thu, 19 Sep 96 09:26:42 EDT Date: Thu, 19 Sep 96 09:26:42 EDT Message-Id: <9609191326.AA03526@bach> To: michaelh@cet.co.jp Cc: freebsd-hackers@FreeBSD.ORG, tech-kern@netbsd.org In-Reply-To: (message from Michael Hancock on Thu, 19 Sep 1996 10:59:37 +0900 (JST)) Subject: Re: spl models and smp (was Re: Some interesting papers on BSD ...) Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Date: Thu, 19 Sep 1996 10:59:37 +0900 (JST) > From: Michael Hancock > [Just going through some old mail] > > I was reviewing some spl and locking models for SMP. SVR4/MP combines > locking primitives with spl and Solaris is completely redesigned to the > implementation to use kernel threads instead for interrupts so it can use > the same locking model as the rest of the code. Actually, I'm pretty sure that's not quite true. Here is how it works. The relevant parts of the interface are: /* This is a mutex lock. It MIGHT lock out interrupts. */ kmutex_t driver_mutex; /* Somewhere, during initialization (attach) you do this: */ mutex_init(&driver_mutex, "mcos", MUTEX_DRIVER, (void*)&driver_ibcookie); /* Then, a section that needs atomic actions is wrapped with: */ mutex_enter(&driver_mutex); /* now have exclusive access to the object locked with this mutex. */ mutex_exit(&driver_mutex); /* now others may take the mutex lock. */ The way these block interrupts is: if the driver_ibcookie (which was returned to you when you attached your interrupt handler) is passed to mutex_init, rather than a null pointer, then anyone who does a mutex_enter() on that mutex will raise their spl as needed to block that interrupt, and then spin-wait. The spin-wait will never have to actually spin unless there is another CPU that holds the mutex. When we take the mutex from non-interrupt level, the mutex_enter() will have raised the spl() such that we don't have to worry about deadlocking against our own interrupt handler. Also note that Solaris no longer supports sleep/wakeup in MP drivers. Instead, you use these new functions: /* Here is the equivalent to the old sleep() call: */ status = cv_timedwait_sig(&sp->condvar, &driver_mutex, abst); /* Here is the equivalent to the old wakeup() call: */ cv_signal(&sp->condvar); Note that you MUST hold a mutex lock on some object that has both the mutex and a condition variable, adn the cv_timedwait_sig() does an atomic "block and release the mutex" while making you non-runnable, and later does an atomic "resume and take mutex." Interesting scheme, eh? Gordon From owner-freebsd-hackers Thu Sep 19 06:42:36 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA10060 for hackers-outgoing; Thu, 19 Sep 1996 06:42:36 -0700 (PDT) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA10041; Thu, 19 Sep 1996 06:42:34 -0700 (PDT) Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with ESMTP id GAA07112; Thu, 19 Sep 1996 06:42:33 -0700 (PDT) Received: (proff@localhost) by suburbia.net (8.7.4/Proff-950810) id XAA01275; Thu, 19 Sep 1996 23:42:11 +1000 From: Julian Assange Message-Id: <199609191342.XAA01275@suburbia.net> Subject: Re: Could use a favor To: davidn@sdev.blaze.net.au (David Nugent) Date: Thu, 19 Sep 1996 23:42:11 +1000 (EST) Cc: roberto@keltia.freenix.fr, hackers@FreeBSD.org, security@FreeBSD.org In-Reply-To: from "David Nugent" at Sep 18, 96 04:14:38 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > I'm familiar with the theory of firewalls, but have never run > one so I lack the experience to fully understand this. But this > reply caught my attention. > > Why is an (effectively) disabled firewall "dangerous"? Is it more > "dangerous" or exposed to security problems than a machine that > has been configured without a firewall at all? > > David Nugent, Unique Computing Pty Ltd - Melbourne, Australia > Voice +61-3-791-9547 Data/BBS +61-3-792-3507 3:632/348@fidonet > davidn@blaze.net.au http://www.blaze.net.au/~davidn The problem is that the interface may go up before you have added all your firewall rules creating a window of opportunity for the attacker. -- "Of all tyrannies a tyranny sincerely exercised for the good of its victims may be the most oppressive. It may be better to live under robber barons than under omnipotent moral busybodies, The robber baron's cruelty may sometimes sleep, his cupidity may at some point be satiated; but those who torment us for own good will torment us without end, for they do so with the approval of their own conscience." - C.S. Lewis, _God in the Dock_ +---------------------+--------------------+----------------------------------+ |Julian Assange RSO | PO Box 2031 BARKER | Secret Analytic Guy Union | |proff@suburbia.net | VIC 3122 AUSTRALIA | finger for PGP key hash ID = | |proff@gnu.ai.mit.edu | FAX +61-3-98199066 | 0619737CCC143F6DEA73E27378933690 | +---------------------+--------------------+----------------------------------+ From owner-freebsd-hackers Thu Sep 19 07:13:08 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA25805 for hackers-outgoing; Thu, 19 Sep 1996 07:13:08 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA25756 for ; Thu, 19 Sep 1996 07:13:00 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id AAA11630; Fri, 20 Sep 1996 00:08:58 +1000 Date: Fri, 20 Sep 1996 00:08:58 +1000 From: Bruce Evans Message-Id: <199609191408.AAA11630@godzilla.zeta.org.au> To: erich@lodgenet.com, hasty@rah.star-gate.com Subject: Re: FreeBSD smc program to set smc card? Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >ftp://cesdis1.gsfc.nasa.gov/pub/linux/setup/ >ftp://sunsite.unc.edu/system/Network/management/ewrk3tools-0.20.tar.gz >wdsetup-0.6a.tar.gz is the smc setup program. > >the following sed script does most of the work to get 'em to compile, >dunno if they run though. I'll try to test the ones I've got hardware >for. > >sed -e 's:ioperm([^)]*):open("/dev/io", O_RDWR):' \ > -e -e 's,asm/io.h,machine/cpufunc.h,' It probably won't work. The args to outb() are reversed (wrong :-) in Linux. Bruce From owner-freebsd-hackers Thu Sep 19 07:40:48 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA06017 for hackers-outgoing; Thu, 19 Sep 1996 07:40:48 -0700 (PDT) Received: from mail.id.net (mail.id.net [199.125.1.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA05949; Thu, 19 Sep 1996 07:40:38 -0700 (PDT) Received: from server.id.net (rls@server.id.net [199.125.1.10]) by mail.id.net (8.7.5/ID-Net) with ESMTP id KAA02961; Thu, 19 Sep 1996 10:43:11 -0400 (EDT) Received: (from rls@localhost) by server.id.net (8.7.5/8.7.3) id KAA09105; Thu, 19 Sep 1996 10:40:39 -0400 (EDT) From: Robert Shady Message-Id: <199609191440.KAA09105@server.id.net> Subject: Re: Very Slow Ethernet Link (FreeBSD v. Linux) In-Reply-To: <199609171635.TAA14831@silver.sms.fi> from Petri Helenius at "Sep 17, 96 07:35:17 pm" To: pete@sms.fi (Petri Helenius) Date: Thu, 19 Sep 1996 10:40:39 -0400 (EDT) Cc: jab@rock.anchorage.net, freebsd-hardware@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 >> Using FreeBSD 2.1.0: >> >> ftp transfer with freebsd 1927427 bytes @ 4.2e+02 seconds 4.4kb/s >> >> Removing FreeBSD and Installed Linux 2.0 >> >> ftp transfer with Linux 1927427 bytes @ 3.05 seconds (6.2e+02 kb/s) Wooo Wooo :) >> >> Using the exact same configuration and computer, the reults are in the >> Linux favor by far. >> Don't know what the problem was. > You did a ftp to the loopback-address? This is a known problem with > the MTU if you did. Set the MTU to 1500 or something more reasonable. I *HOPE* this wasn't to the loopback address, my tests show ftp> get ids local: ids remote: ids 200 PORT command successful. 150 Opening BINARY mode data connection for ids (1152582 bytes). 226 Transfer complete. 1152582 bytes received in 1.41 seconds (797.68 Kbytes/s) 800KB/second to the loopback on a heavily loaded machine.. -- 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 Sep 19 07:45:36 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA07552 for hackers-outgoing; Thu, 19 Sep 1996 07:45:36 -0700 (PDT) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA07523 for ; Thu, 19 Sep 1996 07:45:30 -0700 (PDT) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id JAA17245; Thu, 19 Sep 1996 09:43:17 -0500 Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3) id sma017242; Thu Sep 19 09:43:15 1996 Received: from jake.lodgenet.com (jake.lodgenet.com [204.124.120.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id JAA24586; Thu, 19 Sep 1996 09:44:04 -0500 Received: from localhost (localhost [127.0.0.1]) by jake.lodgenet.com (8.7.5/8.6.12) with SMTP id JAA23164; Thu, 19 Sep 1996 09:43:52 -0500 (CDT) Message-Id: <199609191443.JAA23164@jake.lodgenet.com> X-Authentication-Warning: jake.lodgenet.com: Host localhost [127.0.0.1] didn't use HELO protocol X-Mailer: exmh version 1.6.2 7/18/95 To: Bruce Evans cc: erich@lodgenet.com, hasty@rah.star-gate.com, hackers@freebsd.org Subject: Re: FreeBSD smc program to set smc card? In-reply-to: Your message of "Fri, 20 Sep 1996 00:08:58 +1000." <199609191408.AAA11630@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 19 Sep 1996 09:43:52 -0500 From: "Eric L. Hernes" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Bruce Evans writes: > >It probably won't work. The args to outb() are reversed (wrong :-) in >Linux. Ok, thanks. That's still a pretty minor change ;-) > >Bruce eric. -- erich@lodgenet.com http://rrnet.com/~erich erich@rrnet.com From owner-freebsd-hackers Thu Sep 19 08:11:19 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA17172 for hackers-outgoing; Thu, 19 Sep 1996 08:11:19 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA17145; Thu, 19 Sep 1996 08:11:13 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id KAA08270; Thu, 19 Sep 1996 10:10:15 -0500 (EST) From: "John S. Dyson" Message-Id: <199609191510.KAA08270@dyson.iquest.net> Subject: Re: Very Slow Ethernet Link (FreeBSD v. Linux) To: rls@mail.id.net (Robert Shady) Date: Thu, 19 Sep 1996 10:10:15 -0500 (EST) Cc: pete@sms.fi, jab@rock.anchorage.net, freebsd-hardware@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: <199609191440.KAA09105@server.id.net> from "Robert Shady" at Sep 19, 96 10:40:39 am Reply-To: dyson@FreeBSD.org 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 > >> Using FreeBSD 2.1.0: > >> > >> ftp transfer with freebsd 1927427 bytes @ 4.2e+02 seconds 4.4kb/s > >> > >> Removing FreeBSD and Installed Linux 2.0 > >> > >> ftp transfer with Linux 1927427 bytes @ 3.05 seconds (6.2e+02 kb/s) Wooo Wooo :) > >> > >> Using the exact same configuration and computer, the reults are in the > >> Linux favor by far. > >> Don't know what the problem was. > > > You did a ftp to the loopback-address? This is a known problem with > > the MTU if you did. Set the MTU to 1500 or something more reasonable. > > I *HOPE* this wasn't to the loopback address, my tests show > > ftp> get ids > local: ids remote: ids > 200 PORT command successful. > 150 Opening BINARY mode data connection for ids (1152582 bytes). > 226 Transfer complete. > 1152582 bytes received in 1.41 seconds (797.68 Kbytes/s) > > 800KB/second to the loopback on a heavily loaded machine.. > I think that the loopback buffer size "feature" has been fixed in 2.2 for quite a while??? John From owner-freebsd-hackers Thu Sep 19 08:24:08 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA22257 for hackers-outgoing; Thu, 19 Sep 1996 08:24:08 -0700 (PDT) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA22200 for ; Thu, 19 Sep 1996 08:24:02 -0700 (PDT) Received: from ppp-089.etinc.com (ppp-089.etinc.com [204.141.95.148]) by etinc.com (8.6.12/8.6.9) with SMTP id LAA12464; Thu, 19 Sep 1996 11:31:14 -0400 Date: Thu, 19 Sep 1996 11:31:14 -0400 Message-Id: <199609191531.LAA12464@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: "John T. Farmer" From: dennis@etinc.com (Dennis) Subject: Re: Routers - hardware received wisdom Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>From owner-freebsd-isp@freefall.freebsd.org Wed Sep 18 12:04:46 1996 >>Date: Wed, 18 Sep 1996 11:23:06 -0400 >>X-Sender: dennis@etinc.com >>X-Mailer: Windows Eudora Version 2.0.3 >>Mime-Version: 1.0 >>Content-Type: text/plain; charset="us-ascii" >>To: Nik Clayton >>From: dennis@etinc.com (Dennis) >>Subject: Re: Routers - hardware received wisdom >>Cc: isp@freebsd.org >>Sender: owner-isp@freebsd.org >>X-Loop: FreeBSD.org > > >On 18 Sept 1996 dennis@etinc.com (Dennis) was quoted as saying: >> Nik Clayton asjed: >>>I'm going to be requiring two network routers, and since FreeBSD is more >>>than capable of the task, I figured I'd go for the cheap 486 option. >>> >>>One of these routers will be sat between a 2Mb/s leased line and a 10Mb/s >>>ethernet, and the other will be between 2 10Mb/s ethernets. >>> >>>As far as I can tell, FreeBSD 2.1.5, a PCI based 66MHz 486DX with 16MB RAM >>>and 2 DC201040 PCI network cards should be sufficient. >>> >>>But can I drop it any lower than that? Would the boxes be fine with 8MB >>>RAM? What about 33MHz machines? >> >>Its totally dependent on how much local ethernet traffic you have. If you will >>be switching lots of traffic locally, you might be unhappy with a 33Mhz box. >> >>But at today's prices, what are you going to save? $10.? Its not worth it. >>100Mhz processars are only $32 or so....you're spending more than that >>thinking about it. >> >>Dennis > >I think that Dennis' comment & what Joe said in his note answered a question >that I've had lurking in the back of my mind, "Just what is sufficient to run >a FreeBSD T-1 capable router?" > >Granted that a no-name MB & 133Mhz 486 is running around $120, but I >"happen to have" a 386/33, 8mb, 300mb disk sitting in the corner, with >an ethernet card in it (isa only :^,). And I have a need for a T-1 capable >box soon. Since it would be a fairly un-saturated T-1, I suspect that >I will be able to get away with it for a while... Then the question becomes, >how many 56/64k/128/256k frame relay links could a "little" box like that >handle? (Must be the Scots in me, I hate to throw away anything!) You could easily run 2 T1 on a 386....Joes machine has 2 ethernet cards in it, which adds an extra 10Mbs of bandwidth. Dennis From owner-freebsd-hackers Thu Sep 19 08:46:57 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA02158 for hackers-outgoing; Thu, 19 Sep 1996 08:46:57 -0700 (PDT) Received: from mail1.infinet.com (mail1.infinet.com [206.103.240.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA02123 for ; Thu, 19 Sep 1996 08:46:47 -0700 (PDT) Received: from catty (cmh-p015.infinet.com [206.103.242.15]) by mail1.infinet.com (8.7.3/8.7.3) with SMTP id LAA20964 for ; Thu, 19 Sep 1996 11:46:36 -0400 (EDT) Message-ID: <32416D03.1C03@cylatech.com> Date: Thu, 19 Sep 1996 11:55:47 -0400 From: Wilson MacGyver Reply-To: macgyver@infinet.com Organization: CylaTech Inc. X-Mailer: Mozilla 3.0Gold (WinNT; U) MIME-Version: 1.0 To: hackers@freebsd.org Subject: amusing story Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Something very amusing happened to me this morning. I moved to US from Taiwan ten years ago. And I haven't spoken to my uncle all this time. So I called him this morning. We catch each other up on what's been going on in our lives. Then he asked me, "Have you ever heard of something called FBSD?" "You mean FreeBSD?" I'm completely shocked at this point. "Yea, I had a friend installed it on my machine. It's very powerful, and performs very well. Though I can't seem to find any documentation for it..." "Look in the /usr/share/doc directory..." I suggested. "I will. FreeBSD is wonderful. I'm using the X-windows to try to do some Chinese word processing. Do you think you can get me a latest copy of the CD-ROM. I want to learn more about it, such as how to install it, etc. I also want to find some more documentation." I promised him I will. The entire dialog above occured completely in Chinese. It's amazing how far reached FreeBSD is... -- Wilson MacGyver macgyver@cylatech.com -------------------------------------- Veni, Vidi, Concidi. From owner-freebsd-hackers Thu Sep 19 08:51:20 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA04229 for hackers-outgoing; Thu, 19 Sep 1996 08:51:20 -0700 (PDT) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA04192 for ; Thu, 19 Sep 1996 08:51:15 -0700 (PDT) Received: from ppp-089.etinc.com (ppp-089.etinc.com [204.141.95.148]) by etinc.com (8.6.12/8.6.9) with SMTP id LAA12631; Thu, 19 Sep 1996 11:56:43 -0400 Date: Thu, 19 Sep 1996 11:56:43 -0400 Message-Id: <199609191556.LAA12631@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Joe Greco From: dennis@etinc.com (Dennis) Subject: Re: Routers - hardware received wisdom Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> > I think that Dennis' comment & what Joe said in his note answered a question >> > that I've had lurking in the back of my mind, "Just what is sufficient to run >> > a FreeBSD T-1 capable router?" >> > >> > Granted that a no-name MB & 133Mhz 486 is running around $120, but I >> > "happen to have" a 386/33, 8mb, 300mb disk sitting in the corner, with >> > an ethernet card in it (isa only :^,). And I have a need for a T-1 capable >> > box soon. Since it would be a fairly un-saturated T-1, I suspect that >> > I will be able to get away with it for a while... Then the question becomes, >> > how many 56/64k/128/256k frame relay links could a "little" box like that >> > handle? (Must be the Scots in me, I hate to throw away anything!) >> >> Let's think about this logically people.. We're only talking about a MAX >> of 187 Kilo-Bytes per second for a single T1 line... I've got calculators >> that could max that out! Now.. When you start throwing multiple ethernet >> devices in there, and you want to provide wire-to-wire speed acrossed those, >> that is another story.. We're using a 486DX4-120Mhz w/32MB of RAM here, and >> it is running 3 100Mb Intel Etherexpress cards, and 2 10Mb SMC Elite Ultra >> cards.. It does a decent job, although I don't know that I would expect to >> be able to get full wire speeds on all ethernet cards simultaneously.. But >> luckily, we have enough segments and switches that we don't need to worry >> about that, yet. > >Rob, > >With all due respect it is not that simple. > >I suspect that with MTU-sized packets, I can easily go wire to wire >with 10baseT at peak speeds even on a 386DX/40 with SMC ISA cards. >Actually I was doing that at one point, IIRC, and it worked fine. > >I suspect that with very small packets, the same machine will have >abysmal performance. > >Dennis' T1 sync serial cards are most similar to an Ethernet card, and >I will flat out state that I can saturate your DX4/120 CPU before I hit >T1 saturation if I attempt to saturate that T1 link with miniature packets. >I have saturated a DX5/133 with this test and it is ugly. Joe, with all due respect.... It depends on "why" the packets were dropped. With our product, they can be dropped only if.... 1) The recieve process cannot get a buffer 2) The on-board buffers become overrun. Only 2 is a CPU issue, and there is virtually no way the you can get that situation on a single T1 unless your machine is off doing something else for long periods of time...like processing ethernet packets. With 2 byte packets, yes, but not with IP size packets (44 or more bytes). This is so highly unusual that it shouldnt be considered. Dennis Dennis From owner-freebsd-hackers Thu Sep 19 09:45:55 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA26945 for hackers-outgoing; Thu, 19 Sep 1996 09:45:55 -0700 (PDT) Received: from novell.com (prv-mail20.Provo.Novell.COM [137.65.40.4]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA26921 for ; Thu, 19 Sep 1996 09:45:51 -0700 (PDT) Received: from INET-PRV-Message_Server by novell.com with Novell_GroupWise; Thu, 19 Sep 1996 10:46:04 -0600 Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Thu, 19 Sep 1996 10:54:11 -0600 From: Darren Davis To: hackers@FreeBSD.org Subject: CD-R Drive Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk What write once CD-ROM/CD-R drive do you recommend for FreeBSD. I saw the mail about the HP drive not working, what drive should I get? Thanks, Darren From owner-freebsd-hackers Thu Sep 19 10:06:31 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA03290 for hackers-outgoing; Thu, 19 Sep 1996 10:06:31 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA03258 for ; Thu, 19 Sep 1996 10:06:20 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id KAA14404; Thu, 19 Sep 1996 10:04:44 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) by whistle.com via smap (V1.3) id sma014402; Thu Sep 19 10:04:41 1996 Date: Thu, 19 Sep 1996 10:03:07 -0700 (PDT) From: Julian Elischer To: "Eric L. Hernes" cc: Amancio Hasty , hackers@freebsd.org Subject: Re: FreeBSD smc program to set smc card? In-Reply-To: <199609191317.IAA22700@jake.lodgenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk beware.. LINUX has it's arguments teh other way around in teh outb() instructions :) On Thu, 19 Sep 1996, Eric L. Hernes wrote: > Amancio Hasty writes: > > > > > >Hi, > > > >A little while ago there was a small discussion about the > >possibility of writing such code for FreeBSD. So where is it ? 8) > > > > As I remember, someone mentioned that there's some linux utilities > to configure ethernet cards at: > > ftp://cesdis1.gsfc.nasa.gov/pub/linux/setup/ > ftp://sunsite.unc.edu/system/Network/management/ewrk3tools-0.20.tar.gz > wdsetup-0.6a.tar.gz is the smc setup program. > > the following sed script does most of the work to get 'em to compile, > dunno if they run though. I'll try to test the ones I've got hardware > for. > > sed -e 's:ioperm([^)]*):open("/dev/io", O_RDWR):' \ > -e -e 's,asm/io.h,machine/cpufunc.h,' > > > > > > Tnks, > > Amancio > > > > > > > eric. > -- > erich@lodgenet.com > http://rrnet.com/~erich erich@rrnet.com > > > From owner-freebsd-hackers Thu Sep 19 10:19:02 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA06161 for hackers-outgoing; Thu, 19 Sep 1996 10:19:02 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA06136 for ; Thu, 19 Sep 1996 10:18:56 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id MAA11212; Thu, 19 Sep 1996 12:17:27 -0500 From: Joe Greco Message-Id: <199609191717.MAA11212@brasil.moneng.mei.com> Subject: Re: Routers - hardware received wisdom To: dennis@etinc.com (Dennis) Date: Thu, 19 Sep 1996 12:17:27 -0500 (CDT) Cc: hackers@freebsd.org In-Reply-To: <199609191556.LAA12631@etinc.com> from "Dennis" at Sep 19, 96 11:56:43 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Joe, with all due respect.... > > It depends on "why" the packets were dropped. With our product, they can > be dropped only if.... > > 1) The recieve process cannot get a buffer > 2) The on-board buffers become overrun. > > Only 2 is a CPU issue, and there is virtually no way the you can get that > situation on > a single T1 unless your machine is off doing something else for long periods of > time...like processing ethernet packets. With 2 byte packets, yes, but not with > IP size packets (44 or more bytes). This is so highly unusual that it > shouldnt be > considered. > > Dennis > > Dennis Dennis^2, With all due respect, squared... the case where the machine is acting as a _router_ is precisely what I am talking about... the case where the CPU is maxxed out, inbound Ethernet packets are being silently ignored because the CPU is maxxed out, and the outbound bandwidth on the T1 is less than saturation. Or vice versa: inbound packets on the T1 interface are getting dropped because the CPU is too busy dealing with the previous packets. Or both conditions simultaneously. You _can_ saturate a 486DX5/133 by routing ping sized packets. I believe your average ping packet is about 100 bytes, including IP header, etc. A T1 is 1.544Mbps, at 8 bit bytes that is about 193,000 bytes/sec. That means the router needs to handle 1930 packets per second. When you consider that that means 1930 _in_ via one interface and _out_ via another, that means 3860 packets per second - assuming the remote site does not respond to your pings. My observations during stress testing have been that at 500 packets per second, the CPU is maybe 85-90% idle. Linearly extrapolating to CPU saturation, I conclude that the CPU should be able to handle 3000-5000 packets per second... however my observed performance indicates that it is not linear and performance falls off at about 50% CPU idle... and 3000 pps is a good number to be able to hit. The number we are contemplating (3860) is in excess of that. Now start considering what happens when the replies for those pings come in. :-) Or what happens when somebody starts shooting zillions of small packets at you in a denial of service attack. Think it can't/won't happen? Think of what would happen to you if somebody started pounding on www.etinc.com with a "small packet" attack from a DS3 connected site. What can you do? You _must_ receive the packets, or you _must_ go off line. This may not be such a concern to a small business, but an ISP who has paying customers... such an attack could be deadly. I am not saying it is typical or it is even a major concern, but people need to know what the _worst_ case scenario is in order to make intelligent decisions. I have seen the same router we are discussing saturate a T1 at 96% idle (ok it was fluctuating in the low 90's and that was the peak) with a large number of FTP transfers. There is _NO DOUBT_ in my mind that this is great. For what it's worth, I have seen or heard stories of other folks with "T1" capable hardware that gets swamped with much lower levels of packet traffic than this. I firmly believe that this is one of the best soln's available to anyone building a router. However, _there_ _are_ _limits_ to what you can expect out of the system. That is my point. I am NOT saying your product is flawed. It is not. ... JG From owner-freebsd-hackers Thu Sep 19 10:42:08 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA13091 for hackers-outgoing; Thu, 19 Sep 1996 10:42:08 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA13059 for ; Thu, 19 Sep 1996 10:42:03 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id MAA11243; Thu, 19 Sep 1996 12:39:37 -0500 From: Joe Greco Message-Id: <199609191739.MAA11243@brasil.moneng.mei.com> Subject: Re: Routers - hardware received wisdom To: dennis@etinc.com (Dennis) Date: Thu, 19 Sep 1996 12:39:37 -0500 (CDT) Cc: jfarmer@sabre.goldsword.com, hackers@FreeBSD.ORG In-Reply-To: <199609191531.LAA12464@etinc.com> from "Dennis" at Sep 19, 96 11:31:14 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > You could easily run 2 T1 on a 386....Joes machine has 2 ethernet cards > in it, which adds an extra 10Mbs of bandwidth. :-) Dennis :-) Yeah, but that's a PCI 486DX5/133. :-) See the other thread about this. Your limit is generally how much work the CPU needs to do. At some point, ISA bus bandwidth becomes a consideration, but I doubt it will become a consideration before CPU does on a 386. I highly recommend you consider ET's products... they use DMA transfers and basically work like Ethernet cards from a "system overhead" point of view. Very efficient... much more so than some others I have looked at. The CPU you save by using DMA can then be used for Real Work such as actually routing the packets someplace. My _best_ suggestion is to try it and see how it works. You can always upgrade motherboards if CPU time becomes a problem. % vmstat 1 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr f0 w0 in sy cs us sy id 0 0 0 35124 660 1 0 0 0 0 0 0 0 1111 52 9 2 41 57 0 0 0 35124 660 1 0 0 0 0 0 0 0 861 52 8 1 33 66 0 0 0 35124 660 1 0 0 0 0 0 0 0 1211 62 13 1 56 43 0 0 0 35124 660 1 0 0 0 0 0 0 0 1268 52 9 1 54 45 0 0 0 35124 660 1 0 0 0 0 0 0 0 976 78 13 1 38 61 0 0 0 35124 660 1 0 0 0 0 0 0 0 854 65 11 1 34 65 0 0 0 35124 660 1 0 0 0 0 0 0 0 1116 55 10 1 46 53 0 0 0 35124 660 1 0 0 0 0 0 0 0 763 52 8 1 25 75 0 0 0 35124 660 1 0 0 0 0 0 0 0 634 52 9 0 15 85 0 0 0 35124 660 1 0 0 0 0 0 0 0 661 52 8 2 15 83 0 0 0 30956 660 1 0 0 0 0 0 0 0 718 52 9 0 25 75 0 0 0 35124 660 1 0 0 0 0 0 0 0 488 58 9 1 11 89 0 0 0 35124 660 1 0 0 0 0 0 0 0 659 52 8 1 15 84 0 0 0 30948 660 1 0 0 0 0 0 0 0 763 52 9 0 20 80 0 0 0 30948 660 1 0 0 0 0 0 0 0 640 62 8 1 17 83 0 0 0 30948 660 1 0 0 0 0 0 0 0 639 52 8 2 16 83 % netstat -I ed0 1 input (ed0) output input (Total) output packets errs packets errs colls packets errs packets errs colls 231 0 159 0 0 392 0 392 0 0 108 0 132 0 0 242 0 242 0 2 220 0 172 0 0 398 0 399 0 5 193 0 135 0 0 328 0 327 0 1 292 0 164 0 3 458 0 458 0 7 295 0 174 0 1 478 0 477 0 8 317 0 192 0 0 511 0 510 0 7 221 0 163 0 0 386 0 386 0 4 168 0 138 0 0 307 0 312 0 1 274 0 150 0 0 427 0 427 0 3 134 0 150 0 0 285 0 285 0 1 105 0 97 0 0 204 0 204 0 0 102 0 115 0 0 219 0 219 0 3 107 0 121 0 0 230 0 230 0 0 66 0 64 0 0 135 0 134 0 0 82 0 98 0 1 182 0 182 0 1 129 0 141 0 0 275 0 275 0 2 The snapshots should be within a few seconds of each other... Anyways this is a 386DX/40 with six SMC ISA Ethernet cards in it. You can see that there is a fair amount of traffic flowing through it, and even so it is pretty idle. The traffic is mainly a mix of NNTP and various other traffic, so the packet sizes tend to be smaller than if you were just doing FTP and Web traffic... I personally get nervous when I see idle < 70% or so. You can basically stick as many interfaces in a machine as you want, just as long as the traffic does not swamp the machine. That is a function of several variables: o Number of interfaces o Average traffic on each interface (less = better) o Average packet size (larger = less CPU utilized) o Machine speed and bus speed (most easily adjusted variable) o OS speed (relatively constant) Once you understand the concept that you could support a million 56K lines with the CPU power of an HP-35 as long as nobody tried to send any traffic, you have mastered the concept. I really encourage you to _try_ it.. stress test it.. and draw your own conlusions. That is really the best answer. ... JG From owner-freebsd-hackers Thu Sep 19 10:49:47 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA16480 for hackers-outgoing; Thu, 19 Sep 1996 10:49:47 -0700 (PDT) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA16411 for ; Thu, 19 Sep 1996 10:49:40 -0700 (PDT) Received: from ppp-089.etinc.com (ppp-089.etinc.com [204.141.95.148]) by etinc.com (8.6.12/8.6.9) with SMTP id NAA13350; Thu, 19 Sep 1996 13:55:43 -0400 Date: Thu, 19 Sep 1996 13:55:43 -0400 Message-Id: <199609191755.NAA13350@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Joe Greco From: dennis@etinc.com (Dennis) Subject: Re: Routers - hardware received wisdom Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Joe, with all due respect.... >> >> It depends on "why" the packets were dropped. With our product, they can >> be dropped only if.... >> >> 1) The recieve process cannot get a buffer >> 2) The on-board buffers become overrun. >> >> Only 2 is a CPU issue, and there is virtually no way the you can get that >> situation on >> a single T1 unless your machine is off doing something else for long periods of >> time...like processing ethernet packets. With 2 byte packets, yes, but not with >> IP size packets (44 or more bytes). This is so highly unusual that it >> shouldnt be >> considered. >> >> Dennis >> >> Dennis > >Dennis^2, > >With all due respect, squared... the case where the machine is acting >as a _router_ is precisely what I am talking about... the case where >the CPU is maxxed out, inbound Ethernet packets are being silently >ignored because the CPU is maxxed out, and the outbound bandwidth on >the T1 is less than saturation. Or vice versa: inbound packets on the >T1 interface are getting dropped because the CPU is too busy dealing >with the previous packets. Or both conditions simultaneously. >You _can_ saturate a 486DX5/133 by routing ping sized packets. > >I believe your average ping packet is about 100 bytes, including IP header, >etc. > >A T1 is 1.544Mbps, at 8 bit bytes that is about 193,000 bytes/sec. >That means the router needs to handle 1930 packets per second. When >you consider that that means 1930 _in_ via one interface and _out_ via >another, that means 3860 packets per second - assuming the remote >site does not respond to your pings. Remember that T1 is full-duplex.....so you need to double the potential.... > >My observations during stress testing have been that at 500 packets per >second, the CPU is maybe 85-90% idle. Linearly extrapolating to CPU >saturation, I conclude that the CPU should be able to handle 3000-5000 >packets per second... however my observed performance indicates that it >is not linear and performance falls off at about 50% CPU idle... and >3000 pps is a good number to be able to hit. The number we are >contemplating (3860) is in excess of that. > >Now start considering what happens when the replies for those pings come >in. :-) > >Or what happens when somebody starts shooting zillions of small packets >at you in a denial of service attack. > >Think it can't/won't happen? Think of what would happen to you if >somebody started pounding on www.etinc.com with a "small packet" attack >from a DS3 connected site. What can you do? You _must_ receive the >packets, or you _must_ go off line. This may not be such a concern to >a small business, but an ISP who has paying customers... such an attack >could be deadly. Id doesnt matter what they are connected at.....you cant receive at higher then your bandwidth....you cant kill me on my 56k line, you just CANT do it! > >I am not saying it is typical or it is even a major concern, but people >need to know what the _worst_ case scenario is in order to make >intelligent decisions. > >I have seen the same router we are discussing saturate a T1 at 96% idle >(ok it was fluctuating in the low 90's and that was the peak) with a >large number of FTP transfers. There is _NO DOUBT_ in my mind that this >is great. > >For what it's worth, I have seen or heard stories of other folks with >"T1" capable hardware that gets swamped with much lower levels of packet >traffic than this. I firmly believe that this is one of the best soln's >available to anyone building a router. However, _there_ _are_ _limits_ >to what you can expect out of the system. Please...T1 hardware is not the issue. The board can do 16Mbs single flag separated. The issue is the ability of the host to get the packet off of the board. at 5us per character, you've got 200us to pull off a 40byte packet. Thats your limit on the board. You've got a 32K buffer to protect against cpu contention, which is plenty. Now ethernet is more difficult. The PCI cards are bus masters, so the only hardware reason to drop packets is that you cant get the bus....considering there is no memory on the card, you have to transfer at full bandwidth 100% of the time. I'm not sure that you are correctly diagnosing the reason that packets are getting dropped, and its certainly not easy to do so. Although it is true that most '486 ISA/PCI bridge chipsets are very inefficient....there could be a limitation there as well. The bottom line is that, normally, a '486 is fine for a T1 or even 2. Cisco 2501s are less intelligent and have a 30mhz 68030.....and lots of people use them. Dennis From owner-freebsd-hackers Thu Sep 19 10:57:53 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA20028 for hackers-outgoing; Thu, 19 Sep 1996 10:57:53 -0700 (PDT) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA20010 for ; Thu, 19 Sep 1996 10:57:50 -0700 (PDT) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA11167; Thu, 19 Sep 1996 10:56:32 -0700 Date: Thu, 19 Sep 1996 10:56:32 -0700 (PDT) From: "Brian N. Handy" To: Darren Davis Cc: hackers@freebsd.org Subject: Re: CD-R Drive In-Reply-To: Message-Id: 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 >What write once CD-ROM/CD-R drive do you recommend for FreeBSD. I saw >the mail about the HP drive not working, what drive should I get? Whoa...what's this about the HP CD-R not working? I didn't see this. I've had problems with one, can you/anyone else add some detail to this? (Mine's in the shop right now getting checked out.) Thanks, Brian From owner-freebsd-hackers Thu Sep 19 11:44:59 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA10024 for hackers-outgoing; Thu, 19 Sep 1996 11:44:59 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA10006 for ; Thu, 19 Sep 1996 11:44:56 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id NAA11352; Thu, 19 Sep 1996 13:43:49 -0500 From: Joe Greco Message-Id: <199609191843.NAA11352@brasil.moneng.mei.com> Subject: Re: Routers - hardware received wisdom To: dennis@etinc.com (Dennis) Date: Thu, 19 Sep 1996 13:43:48 -0500 (CDT) Cc: hackers@freebsd.org In-Reply-To: <199609191755.NAA13350@etinc.com> from "Dennis" at Sep 19, 96 01:55:43 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >A T1 is 1.544Mbps, at 8 bit bytes that is about 193,000 bytes/sec. > >That means the router needs to handle 1930 packets per second. When > >you consider that that means 1930 _in_ via one interface and _out_ via > >another, that means 3860 packets per second - assuming the remote > >site does not respond to your pings. > > Remember that T1 is full-duplex.....so you need to double the potential.... I think that last qualification essentially eliminated that, which was intentional for the purposes of this discussion. See later where I added that consideration back in. I simply wanted to draw the simpler case first - but certainly it needs doubling to account for the complete potential. > Id doesnt matter what they are connected at.....you cant receive at higher > then your > bandwidth....you cant kill me on my 56k line, you just CANT do it! Sorry, was not thinking you had a 56k line, but given a slow enough CPU on your side, I could probably kill you. If you had a T1 and anything less than a Pentium, on the other hand... I know I could. Obviously you can not handle more than your bandwidth - that should be elementary. However, if the water coming down your pipe is coming faster than the rate at which you are prepared to drink out of the hose, the excess water usually goes somewhere. > Please...T1 hardware is not the issue. The board can do 16Mbs single flag > separated. The issue is the ability of the host to get the packet off of the > board. I agree!!!!!!!!!!!!!!!!!!!!! And that can be a problem at _ANY_ data rate.... 300 baud, 56k, T1, 10mbps, 100mbps, 655mbps. What I am saying is that at some point, you can probably saturate the host CPU. UNLESS the host CPU is powerful enough to deal with the worst case scenario in the first place... Come on Dennis, you _know_ this as well as I do. > at 5us per character, you've got 200us to pull off a 40byte packet. Thats your > limit on the board. You've got a 32K buffer to protect against cpu > contention, which > is plenty. Bullshit. Pure bullshit. This rate is almost irrelevant to this discussion, as long as it is large enough to support saturation at the desired speed. I can't believe you do not understand this concept, but I will draw it out for you. Let us pretend for the sake of argument that it takes 1ms for the host CPU to route and dispose of a packet. This is known as "overhead". Now for large packets (lets say 1000 bytes), you have 5000us (5ms) to pull off the 1000 byte packet. You also have the 1000us (1ms) packet overhead. HOWEVER - I will grant that in the most ideal circumstances, the two can be overlapped thanks to DMA transfers, and therefore packet reception becomes max(5000us, 1000us) = 5000us. At that rate, I believe that I can receive 200 packets per second. I hope we can agree on that! Because it is derived purely from your 5us figure. Now, given a much smaller packet.. let's use your 40 byte packet. You have 200us to pull off the 40 byte packet. You also have the 1000us (1ms) packet processing overhead. Packet reception time is max(200us, 1000us) = 1000us. At that rate, I believe that I can receive 1000 packets per second. But... let's undo that math. We should be able to receive at 5us per byte, or 200,000cps. E1 speeds. That looks good. We can receive 1000 40 byte packets per second. 1000 packets per second * 40 bytes per packet = 40,000 bytes per second. Uh oh. So - Dennis - it is clear to me that if the CPU takes time to process a packet, that may become a very important consideration when trying to process short packets. What is clearly MOST important - assuming the hardware is fast enough, which I _agree_ it is - is that the CPU be fast enough so that this does not become a serious concern. If you try to drink water out of a fire hose, you will get a wet face and most of the water will not make it into your mouth. > Now ethernet is more difficult. The PCI cards are bus masters, so the only > hardware > reason to drop packets is that you cant get the bus....considering there is > no memory > on the card, you have to transfer at full bandwidth 100% of the time. No, you are still failing to consider that there is overhead in the software. Hardware overhead is generally less of a consideration. > I'm not sure that you are correctly diagnosing the reason that packets are > getting dropped, > and its certainly not easy to do so. Dennis, I have seen the _cursor_ on Trantor blinking irregularly and even _stop_ because the levels of traffic I was pushing through that venerable 386DX/40 were far beyond reasonable. The CPU stops having idle time - or even sufficient time to process the currently pending interrupts.. it is a truly awe inspiring sight to see a console cursor stop blinking entirely. > Although it is true that most '486 ISA/PCI bridge chipsets are very > inefficient....there could > be a limitation there as well. > > The bottom line is that, normally, a '486 is fine for a T1 or even 2. Cisco > 2501s are less intelligent > and have a 30mhz 68030.....and lots of people use them. YES!!! Absolutely! "Normally" a '486 would probably be great for even three or four T1's. As LONG as you realize that a '486 CAN get swamped by lots of small traffic data... and take that into account. Many people won't care. However, those of us who insist on knowing what the risks are, we want to be aware of this. I certainly agree that the CPU on a 486DX5/133 will pound the hell out of a 2501 and still have cycles to spare. I am NOT saying the 2501 doesn't exhibit this problem... it's probably WORSE on a 2501. ... JG From owner-freebsd-hackers Thu Sep 19 11:58:38 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA17253 for hackers-outgoing; Thu, 19 Sep 1996 11:58:38 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA17229 for ; Thu, 19 Sep 1996 11:58:35 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA01219; Thu, 19 Sep 1996 11:56:03 -0700 From: Terry Lambert Message-Id: <199609191856.LAA01219@phaeton.artisoft.com> Subject: Re: thread stacks and protections (was Re: attribute/inode caching) To: michaelh@cet.co.jp (Michael Hancock) Date: Thu, 19 Sep 1996 11:56:03 -0700 (MST) Cc: terry@lambert.org, dg@Root.COM, bde@zeta.org.au, proff@suburbia.net, freebsd-hackers@FreeBSD.org In-Reply-To: from "Michael Hancock" at Sep 19, 96 10:31:23 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 > > Personally, I'd like to use page anonymity based protections to establish > > Chorus-like access priveledge domains for IPC; specifically, for stacks > > capable of being grown by fault for use by threads. I think the POSIX > > model is broken: I should not be required to preallocate stack for a > > thread just because SVR4 and Solaris have bogus architectures (actually, > > the SVR4 VM does *not* impose this limitation: it is a limitation of > > the threading code alone. Steve Baumel, the author of the SVR4 VM, and > > I discussed this at some length when discussing context sharing models > > that would be useful for the NetWare for UNIX product). > > > > How does one implement a u-area concept on top of Chorus? A lot of stuff > that used to be in the u-area has been moved out to the proc and other > structures in 4.4BSD. Maybe moving the kernel stack out of the u-area and > generalizing the proc and u-cred stuff can be a step toward what your > talking about. Maybe I don't understand the question, or maybe you aren't asking in the context of page-anonymity based protections, which are statistical protections using MMU faulting rather than domain crossing protections using instruction faulting. Chorus, the microkernel, is very Mach-like, except that it moves the IPC facilities out of the realm of domain crossing boundries. An external pager, for instance, would exist in the same protection domain as the kernel itself. The difference is that when you mix in page anonymity-based protections (which are probably unsatisfactory for getting *any* orange-book rating), then you get the ability to allow user processes into the same domain as the kernel. The lack of domain crossing means a lack of copying and a lack of remapping and a lack of exception handling in the non-error case. What Chorus buys is a several orders of magnitude improvement in the IPC facilities, but it doesn't itself rely on page anonymity -- that's something I threw into to mix as an "I'd like to use...". The threading stack issue is one of either splitting or domainizing the stack address space. Splitting requires using different mappings from one thread to another. Domainizing is inherently unsatisfactory because it leads to things like "no one will ever need mre than 4K of stack" (a statement Windows95 and Windows NT implicitly make for VXD's). I think John Dyson's response is best: it can be implemented (I wouldn't say it was as trivial to do as John implies, but then John is a VM guy and I am an FS guy), but we need to make sure that it's the right thing being implemented. 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 Sep 19 12:25:21 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA02635 for hackers-outgoing; Thu, 19 Sep 1996 12:25:21 -0700 (PDT) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA01439 for ; Thu, 19 Sep 1996 12:23:24 -0700 (PDT) Received: from ppp-089.etinc.com (ppp-089.etinc.com [204.141.95.148]) by etinc.com (8.6.12/8.6.9) with SMTP id PAA13911; Thu, 19 Sep 1996 15:29:21 -0400 Date: Thu, 19 Sep 1996 15:29:21 -0400 Message-Id: <199609191929.PAA13911@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Joe Greco From: dennis@etinc.com (Dennis) Subject: Re: Routers - hardware received wisdom Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Joe writes.... >What I am saying is that at some point, you can probably saturate the host >CPU. UNLESS the host CPU is powerful enough to deal with the worst case >scenario in the first place... Come on Dennis, you _know_ this as well as >I do. > >> at 5us per character, you've got 200us to pull off a 40byte packet. Thats your >> limit on the board. You've got a 32K buffer to protect against cpu >> contention, which >> is plenty. > >Bullshit. Pure bullshit. This rate is almost irrelevant to this >discussion, as long as it is large enough to support saturation at the >desired speed. I can't believe you do not understand this concept, >but I will draw it out for you. > >Let us pretend for the sake of argument that it takes 1ms for the host >CPU to route and dispose of a packet. This is known as "overhead". > >Now for large packets (lets say 1000 bytes), you have 5000us (5ms) to >pull off the 1000 byte packet. You also have the 1000us (1ms) packet >overhead. HOWEVER - I will grant that in the most ideal circumstances, >the two can be overlapped thanks to DMA transfers, and therefore >packet reception becomes max(5000us, 1000us) = 5000us. At that rate, >I believe that I can receive 200 packets per second. I hope we can >agree on that! Because it is derived purely from your 5us figure. > >Now, given a much smaller packet.. let's use your 40 byte packet. >You have 200us to pull off the 40 byte packet. You also have >the 1000us (1ms) packet processing overhead. Packet reception time >is max(200us, 1000us) = 1000us. At that rate, I believe that I can >receive 1000 packets per second. Well, interfaces just queue packets for the OS, so if you do your queue management properly, you discard packets based on age, and if you have enough memory to hold your bandwidth * hold_time you wont dump anything that shouldnt be dumped. However, what you're talking about is not real data... you can bring a Cisco 4500 to its knees with about 512kbs of data under attack, so the 4000 pps number ain't half bad! Dennis From owner-freebsd-hackers Thu Sep 19 12:26:31 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA03343 for hackers-outgoing; Thu, 19 Sep 1996 12:26:31 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA03323 for ; Thu, 19 Sep 1996 12:26:29 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA01259; Thu, 19 Sep 1996 12:24:31 -0700 From: Terry Lambert Message-Id: <199609191924.MAA01259@phaeton.artisoft.com> Subject: Re: spl models and smp (was Re: Some interesting papers on BSD ...) To: gwr@mc.com (Gordon W. Ross) Date: Thu, 19 Sep 1996 12:24:31 -0700 (MST) Cc: michaelh@cet.co.jp, freebsd-hackers@FreeBSD.org, tech-kern@netbsd.org In-Reply-To: <9609191326.AA03526@bach> from "Gordon W. Ross" at Sep 19, 96 09:26:42 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 [ ... SVR4/MP mutex/spl interaction ... ] > Note that you MUST hold a mutex lock on some object that has both > the mutex and a condition variable, adn the cv_timedwait_sig() > does an atomic "block and release the mutex" while making you > non-runnable, and later does an atomic "resume and take mutex." > Interesting scheme, eh? The one problem with this is that condition variables, as required, must be synchronized across all processors in a shared area mapped into the kernel adress space of all of them. This seems a big hit on concurrency, to me. I prefer a design which would include the ability to transparently localize a mutex/condition-avliable based on the resource locality, to a single CPU. This implies that the mutex allocation is hierarchical, in the same way that all processes are descendents of "init" (a "group leader" is equivalent to a CPU locality for this analogy). This allows the use of mutexes and condition variables which will only invoke bus arbitration *as necessary*. The key is the ability to predict deadlock conditions. You can do this by computing the transitive closure over the hierarchy as if it were a directed acyclic graph. There is code in both "tsort" and "gprof" that gives an example of how this works in actual practice. Because it is a hierarchy, this means you can "inherit to root" hints to allow the computation to be more quickly achieved (or-and-xor-and in the simplest case). The main enabling technology for making hints so inexpensive is the use of lock intention modes, so that once intention is established, a resync of the shared objects is not required to prevent conflicting requests. Clearly, we want to compromise and not propagate inheritance of hints over the boundry to the common system instead of per-CPU objects. This trades propagation bus overhead for run time overhead. In effect, the "expensive" object references become slightly more expensive because the propagation is not interleaved. In trade, we get get vastly increased access concurrency without bus arbitration for "inexpensive" (local to a single CPU context) objects. It is then incumbent upon us to design using as few critical path "expensive" objects as possible. For instance, we should use the Dynix (Sequent) per CPU page pool design for local VM allocations, and only go to a share (bus arbitrating) mutex to refill the local page pool for a CPU from the global page pool, when we hit a high water mark (or conversly, return pages to the global pool only when we hit a low water mark). Unlike file system reentrancy, Sequent did this right: it is intuitively scalable to N processors (it turns out that Unisys has/had the best -- IMO -- FS reentrancy mechanisms). Other issues, such as per FS reentrancy for FS's in a transition kernel, can be handled by allocating an expensive global mutex for the VFS subsystems (and one for each other kernel subsystem, to achieve a per-subsystem granularity). At that point, it's possible to "push down" the interfaces and kernel reentrancy trough the trap, exception, and interrupt code, to gradually increase concurrency. It also allows import of "foreign" file systems, drivers, and other components by causing them to use the global mutex until such time as they can be made "safely kernel reentrant" and "safely kernel context reentrant", for kernel multithreading and SMP reeentrancy, respectively. I *highly* recommend "UNIX For Modern Architectures"; it is basically a handbook on how to build SMP UNIX systems. SMP should be the target, since the context handling necessary for SMP buys you the ability to reenter on a single CPU context (for kernel multithreading) for free. It also buys you the ability to support kernel preemption (because of the multithreading contexts), which is something that is necessary to support true RealTime scheduling algorithms (like deadlining) and related issues (like priority lending or RT event-based preemption). So this discussion probably belongs on the SMP list... 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 Thu Sep 19 12:31:11 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA05052 for hackers-outgoing; Thu, 19 Sep 1996 12:31:11 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA05014 for ; Thu, 19 Sep 1996 12:31:07 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA01280; Thu, 19 Sep 1996 12:29:44 -0700 From: Terry Lambert Message-Id: <199609191929.MAA01280@phaeton.artisoft.com> Subject: Re: Giant Sized Ethernet Packets To: dg@Root.COM Date: Thu, 19 Sep 1996 12:29:44 -0700 (MST) Cc: rohit@cs.UMD.EDU, freebsd-hackers@freebsd.org In-Reply-To: <199609190350.UAA01225@root.com> from "David Greenman" at Sep 18, 96 08:50:52 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 was wondering if it is possible to send giant sized ethernet packets (>1500 > >bytes say 1550) using the current 'de' driver for the SMC 10/100 DEC 21140 > >cards. > > No. > > The answer to this is complicated, but it basically ends up being "no". > I just spent about 15 minutes looking over the DC21140 hardware reference > manual. It appears that the chip can except larger frames, but it signals > an error condition when this occurs, so I don't think you could do this > as a normal mode of operation. I would find this suprising, since it would imply that DEC's cards can't run DECNet (which has a nasty habit of shoving huge frames around). I believe huge frames are technically illegal (according to Xerox), so you should epect that there are hardware limitations which will be biting you somewhere. This doesn't stop DEC from using them, though, so I suspect any card capable of DECNet/LAT/MOP/etc. *should* be physically capable of supporting it. AMD LANCE-based cards should have no problem (except, as you note, potentially in the driver). 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 Sep 19 12:33:22 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA06053 for hackers-outgoing; Thu, 19 Sep 1996 12:33:22 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA06024 for ; Thu, 19 Sep 1996 12:33:19 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA01293; Thu, 19 Sep 1996 12:32:16 -0700 From: Terry Lambert Message-Id: <199609191932.MAA01293@phaeton.artisoft.com> Subject: Re: machine/endian.h: network byte order macros To: bde@zeta.org.au (Bruce Evans) Date: Thu, 19 Sep 1996 12:32:15 -0700 (MST) Cc: brandon@glacier.cold.org, freebsd-hackers@FreeBSD.org In-Reply-To: <199609190256.MAA23999@godzilla.zeta.org.au> from "Bruce Evans" at Sep 19, 96 12:56: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 > >Although trivial, the problem can be fixed by just removing '(' ')' from > >the outside of the macro, leaving '{' '}' there. This likely causes a > > No, this just breaks the statement-expression. `foo = { bar; } is a > syntax error even in gcc. Adding __extension__ before the statement- > expression seems to work right. I am being constantly surprised lately, it seems. I was under the impression that any statement could be used as an rvalue. Where you may be screwed is type conversion of the brace-enclosed statement, so it should be considered bad practice in any case (IMO). 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 Sep 19 12:39:50 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA09170 for hackers-outgoing; Thu, 19 Sep 1996 12:39:50 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA09131 for ; Thu, 19 Sep 1996 12:39:47 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA01311; Thu, 19 Sep 1996 12:37:17 -0700 From: Terry Lambert Message-Id: <199609191937.MAA01311@phaeton.artisoft.com> Subject: Re: the old intel aurora board... To: michaelv@MindBender.serv.net (Michael L. VanLoon -- HeadCandy.com) Date: Thu, 19 Sep 1996 12:37:17 -0700 (MST) Cc: macgyver@infinet.com, hackers@FreeBSD.org In-Reply-To: <199609190801.BAA07949@MindBender.serv.net> from "Michael L. VanLoon -- HeadCandy.com" at Sep 19, 96 01:01:14 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 have a chance to purchase a Aurora board for $800. It has > >a P6-200 CPU, ATX Case. > >I know this board use the old orion chipset, though I also > >heard that some of the later stepings of the chipset is > >"fixed". Is this a good deal, or should I fork out the > >extra and get a Venus Board instead? > > I personally wouldn't buy any Intel board, but that's just MHO... > > See related discussions on the lists recently for alternatives. I would, if it came from their server products group. Unfrotunately, the ones they sell outside the company tend to come from their OEM products group, and generally fall into the category of "technical and minimal standards compliance". That is, they do stupid things like making all PCI cards go to the same interrupt because the PCI standard technically allows this, even though it means that you can't interleave interrupts from multiple PCI cards (for instance, oh, say, reading a disk on a PCI controller and writing NFS packets to a PCI ethernet card at the same time). 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 Sep 19 13:00:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA21025 for hackers-outgoing; Thu, 19 Sep 1996 13:00:34 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA20114 for ; Thu, 19 Sep 1996 12:58:57 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id OAA11449; Thu, 19 Sep 1996 14:57:43 -0500 From: Joe Greco Message-Id: <199609191957.OAA11449@brasil.moneng.mei.com> Subject: Re: Routers - hardware received wisdom To: dennis@etinc.com (Dennis) Date: Thu, 19 Sep 1996 14:57:42 -0500 (CDT) Cc: hackers@freebsd.org In-Reply-To: <199609191929.PAA13911@etinc.com> from "Dennis" at Sep 19, 96 03:29:21 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Well, interfaces just queue packets for the OS, Yes :-) > so if you do your queue > management properly, you discard packets based on age, and if you have > enough memory to hold your bandwidth * hold_time you wont dump anything > that shouldnt be dumped. No. If your CPU is overloaded, you will end up dumping data that is valid and shouldn't be dumped, simply because you never have the chance to deal with it. And queueing only buys you a very little bit, because when it comes right down to it, if I can overload your router for a second, I can probably overload your router continuously - making any queueing you do utterly useless. > However, what you're talking about is not real data... Until it starts coming in at you off the Internet, outside of your control. THAT is the whole point. > you can bring a Cisco 4500 to its knees with about 512kbs of data under > attack, so the 4000 pps number ain't half bad! I definitely agree!! I would think it's actually pretty damn decent. ... JG From owner-freebsd-hackers Thu Sep 19 13:49:40 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA11297 for hackers-outgoing; Thu, 19 Sep 1996 13:49:40 -0700 (PDT) Received: from mail12.digital.com (mail12.digital.com [192.208.46.20]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA11248 for ; Thu, 19 Sep 1996 13:49:33 -0700 (PDT) Received: from muggsy.lkg.dec.com by mail12.digital.com (8.7.5/UNX 1.2/1.0/WV) id QAA18708; Thu, 19 Sep 1996 16:35:31 -0400 (EDT) Received: from whydos.lkg.dec.com by muggsy.lkg.dec.com (5.65/DEC-Ultrix/4.3) with SMTP id AA27107; Thu, 19 Sep 1996 16:35:29 -0400 Received: from localhost.lkg.dec.com (localhost.lkg.dec.com [127.0.0.1]) by whydos.lkg.dec.com (8.6.12/8.6.12) with SMTP id QAA26304; Thu, 19 Sep 1996 16:38:09 GMT Message-Id: <199609191638.QAA26304@whydos.lkg.dec.com> X-Authentication-Warning: whydos.lkg.dec.com: Host localhost.lkg.dec.com didn't use HELO protocol X-Mailer: exmh version 1.6.5 12/11/95 To: Terry Lambert Cc: freebsd-hackers@freebsd.org Subject: Re: Giant Sized Ethernet Packets In-Reply-To: Your message of "Thu, 19 Sep 1996 12:29:44 MST." <199609191929.MAA01280@phaeton.artisoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 19 Sep 1996 16:38:09 +0000 From: Matt Thomas Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In <199609191929.MAA01280@phaeton.artisoft.com>, Terry Lambert wrote: > > The answer to this is complicated, but it basically ends up being "no". > > I just spent about 15 minutes looking over the DC21140 hardware reference > > manual. It appears that the chip can except larger frames, but it signals > > an error condition when this occurs, so I don't think you could do this > > as a normal mode of operation. > > I would find this suprising, since it would imply that DEC's cards can't > run DECNet (which has a nasty habit of shoving huge frames around). That is *complete* and *utter* bullsh*t. DECnet uses standard size Ethernet frames. Always has, always will. > I believe huge frames are technically illegal (according to Xerox), > so you should epect that there are hardware limitations which will > be biting you somewhere. This doesn't stop DEC from using them, though, > so I suspect any card capable of DECNet/LAT/MOP/etc. *should* be > physically capable of supporting it. AMD LANCE-based cards should > have no problem (except, as you note, potentially in the driver). Again, no DEC developed protocol uses over-sized Ethernet frames. Why do I know this? Because for the last several years I (as a Digital employee) have owned (and continure to own) all the DECnet specifications. In fact, I implemented most of them as well. -- Matt Thomas Internet: matt@3am-software.com 3am Software Foundry WWW URL: http://www.3am-software.com/bio/matt.html Westford, MA Disclaimer: I disavow all knowledge of this message From owner-freebsd-hackers Thu Sep 19 14:40:28 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA03981 for hackers-outgoing; Thu, 19 Sep 1996 14:40:28 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA03956 for ; Thu, 19 Sep 1996 14:40:25 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA01485; Thu, 19 Sep 1996 14:38:51 -0700 From: Terry Lambert Message-Id: <199609192138.OAA01485@phaeton.artisoft.com> Subject: Re: Giant Sized Ethernet Packets To: matt@lkg.dec.com (Matt Thomas) Date: Thu, 19 Sep 1996 14:38:51 -0700 (MST) Cc: terry@lambert.org, freebsd-hackers@freebsd.org In-Reply-To: <199609191638.QAA26304@whydos.lkg.dec.com> from "Matt Thomas" at Sep 19, 96 04:38:09 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 would find this suprising, since it would imply that DEC's cards can't > > run DECNet (which has a nasty habit of shoving huge frames around). > > That is *complete* and *utter* bullsh*t. DECnet uses standard size > Ethernet frames. Always has, always will. We had problems with DECNet Phase IV protocols, specificall MOP, specifically MOP-MOM responses generating large frames at Weber State University during the download of DECServer 200's from VMS 4.x systems. This may have been an implementation error or something else; nevertheless, we did have problems, and that is what the DEC field support rep claimed when he suggested we replace some of our non-DEC hardware. > Again, no DEC developed protocol uses over-sized Ethernet frames. What's "oversized"? How many bytes, exactly? 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 Sep 19 15:29:05 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA26311 for hackers-outgoing; Thu, 19 Sep 1996 15:29:05 -0700 (PDT) Received: from hp.com (hp.com [15.255.152.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA26281 for ; Thu, 19 Sep 1996 15:29:01 -0700 (PDT) Received: from srmail.sr.hp.com by hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA186032139; Thu, 19 Sep 1996 15:29:00 -0700 Received: from hpnmhjw.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA274972138; Thu, 19 Sep 1996 15:28:59 -0700 Received: from mina.sr.hp.com by hpnmhjw.sr.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA226642138; Thu, 19 Sep 1996 15:28:58 -0700 Message-Id: <199609192228.AA226642138@hpnmhjw.sr.hp.com> To: hackers@freefall.freebsd.org Cc: handy@sag.space.lockheed.com Subject: Re: CD-R Drive In-Reply-To: Your message of "Thu, 19 Sep 1996 12:26:36 PDT." <199609191926.MAA03395@freefall.freebsd.org> Date: Thu, 19 Sep 1996 15:28:57 -0700 From: Darryl Okahata Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >What write once CD-ROM/CD-R drive do you recommend for FreeBSD. I saw > >the mail about the HP drive not working, what drive should I get? > > Whoa...what's this about the HP CD-R not working? I didn't see this. > I've had problems with one, can you/anyone else add some detail to this? > (Mine's in the shop right now getting checked out.) While the HP CD-R works fine with 2.2-current, it doesn't work with FreeBSD 2.1.5, "out-of-the-box". To get it to work with 2.1.5, you supposedly have to apply a patch to 2.1.5. I'm using an HP 4020i with 2.2-snap-960612, and it works quite well (it's even connected to a recycled boatanchor -- a 25MHz 386). The only time I've had problems is when I tried burning a CDROM across an overloaded LAN (I couldn't transfer data fast enough over the LAN to keep the 4020i constantly fed). Now, I just do the burning from a local disk, and everything works wonderfully. However, I work for HP, so take this posting with a grain of salt. -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. From owner-freebsd-hackers Thu Sep 19 15:50:37 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA04647 for hackers-outgoing; Thu, 19 Sep 1996 15:50:37 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA04600 for ; Thu, 19 Sep 1996 15:50:30 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id IAA07250; Fri, 20 Sep 1996 08:50:19 +1000 (EST) Date: Fri, 20 Sep 1996 08:50:17 +1000 (EST) From: "Daniel O'Callaghan" To: Karl Denninger cc: freebsd-hackers@freebsd.org Subject: Re: TCP extensions breaking TCP. In-Reply-To: <199609191301.IAA24016@Jupiter.Mcs.Net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 19 Sep 1996, Karl Denninger wrote: > > Win95 blows chunks if these are enabled and the connection comes in over an > Ethernet (say, from an ISDN user). ?? I can quite happily talk from W95 to FreeBSD over my LAN, over my PPP link and over ISDN. Danny From owner-freebsd-hackers Thu Sep 19 16:49:40 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA07917 for hackers-outgoing; Thu, 19 Sep 1996 16:49:40 -0700 (PDT) Received: from phantasma.bevc.blacksburg.va.us (kmitch@phantasma.bevc.blacksburg.va.us [198.82.200.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA07882 for ; Thu, 19 Sep 1996 16:49:37 -0700 (PDT) Received: (from kmitch@localhost) by phantasma.bevc.blacksburg.va.us (8.7.5/8.7.3) id TAA20520 for hackers@freebsd.org; Thu, 19 Sep 1996 19:49:20 -0400 (EDT) From: Keith Mitchell Message-Id: <199609192349.TAA20520@phantasma.bevc.blacksburg.va.us> Subject: Pinnacle Micro 5020i CDR To: hackers@freebsd.org Date: Thu, 19 Sep 1996 19:49:20 -0400 (EDT) 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 what th status is on the Pinnacle Micro CDR (5020i) working on FreeBSD? Last time I checked it wasn't supported. Only the HP 5020i was supported. Thanks. From owner-freebsd-hackers Thu Sep 19 16:51:40 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA09262 for hackers-outgoing; Thu, 19 Sep 1996 16:51:40 -0700 (PDT) Received: from scooter.quickweb.com (scooter.quickweb.com [199.212.134.8]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA09035 for ; Thu, 19 Sep 1996 16:51:19 -0700 (PDT) Received: from localhost (mark@localhost) by scooter.quickweb.com (8.6.12/8.6.12) with SMTP id TAA06995; Thu, 19 Sep 1996 19:47:57 -0400 Date: Thu, 19 Sep 1996 19:47:57 -0400 (EDT) From: Mark Mayo To: "Daniel O'Callaghan" cc: Karl Denninger , freebsd-hackers@freebsd.org Subject: Re: TCP extensions breaking TCP. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 20 Sep 1996, Daniel O'Callaghan wrote: > > On Thu, 19 Sep 1996, Karl Denninger wrote: > > > > > Win95 blows chunks if these are enabled and the connection comes in over an > > Ethernet (say, from an ISDN user). > > ?? I can quite happily talk from W95 to FreeBSD over my LAN, over my PPP > link and over ISDN. > Me too -- I have lot's of people who come in from the ethernet via ppp ISDN and I've never had a problem on the win95 or FreeBSD side. I run 2.1.5 plus a few updates from the -STABLE branch. -Mark ------------------------------------------- | Mark Mayo mark@quickweb.com | | C-Soft www.quickweb.com | ------------------------------------------- "To iterate is human, to recurse divine." - L. Peter Deutsch > Danny > From owner-freebsd-hackers Thu Sep 19 17:25:46 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA00608 for hackers-outgoing; Thu, 19 Sep 1996 17:25:46 -0700 (PDT) Received: from w2xo.pgh.pa.us (w2xo.pgh.pa.us [206.210.70.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA00588 for ; Thu, 19 Sep 1996 17:25:43 -0700 (PDT) Received: (from root@localhost) by w2xo.pgh.pa.us (8.6.12/8.6.9) id UAA10452 for hackers@freebsd.org; Thu, 19 Sep 1996 20:25:24 -0400 Date: Thu, 19 Sep 1996 20:25:24 -0400 From: Charlie Root Message-Id: <199609200025.UAA10452@w2xo.pgh.pa.us> To: hackers@freebsd.org Subject: auserver Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is anyone familiar with the au audio server? I'm not able to connect to it on my 2.1.5 box. All the "au" programs just say "Can't connect to audio server". I'm using an old 8 bit soundblaster and I have all the /dev stuff made (MAKEDEV sb). -Jim Durham From owner-freebsd-hackers Thu Sep 19 18:18:05 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA00792 for hackers-outgoing; Thu, 19 Sep 1996 18:18:05 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA00766 for ; Thu, 19 Sep 1996 18:18:01 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id BAA20879; Fri, 20 Sep 1996 01:16:03 GMT Date: Fri, 20 Sep 1996 10:16:03 +0900 (JST) From: Michael Hancock To: Terry Lambert cc: dg@Root.COM, bde@zeta.org.au, proff@suburbia.net, freebsd-hackers@FreeBSD.org Subject: Re: thread stacks and protections (was Re: attribute/inode caching) In-Reply-To: <199609191856.LAA01219@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 19 Sep 1996, Terry Lambert wrote: > The threading stack issue is one of either splitting or domainizing > the stack address space. Splitting requires using different mappings > from one thread to another. Domainizing is inherently unsatisfactory > because it leads to things like "no one will ever need mre than 4K of > stack" (a statement Windows95 and Windows NT implicitly make for VXD's). It is unsatisfactory to see hardlimits forced by the architecture. I understand there are tradeoffs, though I'm not sure what you mean by splitting. > I think John Dyson's response is best: it can be implemented (I wouldn't > say it was as trivial to do as John implies, but then John is a VM > guy and I am an FS guy), but we need to make sure that it's the right > thing being implemented. Yes. Regards, Mike Hancock From owner-freebsd-hackers Thu Sep 19 19:35:35 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA11289 for hackers-outgoing; Thu, 19 Sep 1996 19:35:35 -0700 (PDT) Received: from po2.glue.umd.edu (po2.glue.umd.edu [129.2.128.45]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA11261 for ; Thu, 19 Sep 1996 19:35:29 -0700 (PDT) Received: from skipper.eng.umd.edu (skipper.eng.umd.edu [129.2.103.24]) by po2.glue.umd.edu (8.7.5/8.7.3) with ESMTP id WAA24361; Thu, 19 Sep 1996 22:35:25 -0400 (EDT) Received: from localhost (chuckr@localhost) by skipper.eng.umd.edu (8.7.5/8.7.3) with SMTP id WAA11503; Thu, 19 Sep 1996 22:35:24 -0400 (EDT) X-Authentication-Warning: skipper.eng.umd.edu: chuckr owned process doing -bs Date: Thu, 19 Sep 1996 22:35:24 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@skipper.eng.umd.edu To: "Ron G. Minnich" cc: freebsd-hackers@FreeBSD.org Subject: Re: user-level distributed shared memory available for freebsd In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 16 Sep 1996, Ron G. Minnich wrote: > This system is called ZOUNDS. it's all user mode, no special sysadmin > needed to use it, uses TCP, comes with manual and a sample app. It can > exploit rfork if you have it in your 2.2+ system, provides a simple > shared-file-descriptor rfork loadable module if you have earlier than > 2.2, and for most cases doesn't have to have rfork anyways (There's only > one specific case where it is helpful but not necessary). > > bugs to me, of course. Ron, where is this? I don't know if you have the time to pander to my curiosity on one point, but I'm sure you know the anser to this (if you're not too busy). I know unix in general has never had a really good file locking system. Why doesn't someone write one just for FreeBSD? I've often wondered why I couldn't write something that would look at ufs, and at inodes, say (as a locking point, I think) and make an absolute, enforceable locking call for FreeBSD. I know it would be completely non-portable, but wouldn't it make FreeBSD kinda unique among unixes? I am innocent of the higher level locking strategies (I'm in school for that right now, which is teaching me how dumb I am), but I was wondering if there is some reason it couldn't be done? > > ron > > Ron Minnich |"If you leave out all the killings, D.C. has as > rminnich@sarnoff.com | low a crime rate as many cities" -- > (609)-734-3120 | D.C. Mayor Marion Barry > ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html > > > ----------------------------+----------------------------------------------- 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 n3lxx, both FreeBSD (301) 220-2114 | version 2.2 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Thu Sep 19 20:39:04 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA09665 for hackers-outgoing; Thu, 19 Sep 1996 20:39:04 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA09635 for ; Thu, 19 Sep 1996 20:38:57 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id WAA11828; Thu, 19 Sep 1996 22:38:26 -0500 Date: Thu, 19 Sep 1996 22:38:26 -0500 From: Joe Greco Message-Id: <199609200338.WAA11828@brasil.moneng.mei.com> To: hackers@freebsd.org Subject: Re: Panix, TCP, and RED Newsgroups: comp.security.unix,comp.protocols.tcp-ip In-Reply-To: Organization: Marquette Electronics, Inc. - Milwaukee, WI. Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Are any networking folks looking into doing something like this for FreeBSD? In comp.protocols.tcp-ip article , Robert Morris wrote: :Queues managed by random drop provide reasonably fair service without :knowing the identities of the senders. : :The idea is to drop a randomly selected listen queue entry upon :overflow, rather than the most recently arrived SYN. This penalizes :senders in proportion to the number of SYNs they have queued. If I :send just one SYN, chances are that it will be accepted even if the :queue is full, at somebody else's expense. If the evil hacker has many :SYNs queued, chances are it will be at his expense. Nothing here :depends on the evil hacker using the same IP source address for all :his SYNs. : :Can the evil hacker still win by sending SYNs faster? Suppose that the :listen queue is 100 entries long, that TCP keeps half-open connections :for 75 seconds, and that the server CPU is not overloaded. With the :current TCP implementation, the evil hacker need only send a few SYNs :per second to deny service to the good guys. With random drop, a good :guy's SYN will be placed in the listen queue, and his connection will :be accept()ed if he gets an ACK back before the evil hacker dislodges :him. Imagine that his ACK arrives 100 milliseconds later, so the evil :hacker must dislodge the SYN in just 100ms. If the evil hacker sends :500 SYNs per second, he has less than a 50% chance of dislodging the :good guy's SYN. Perhaps 500/second is fast enough that he'd easily be :caught. : :Consider reading Mankin and Ramakrishnan's RFC 1254, whence these :ideas came. From owner-freebsd-hackers Thu Sep 19 21:37:52 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA03674 for hackers-outgoing; Thu, 19 Sep 1996 21:37:52 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA03618 for ; Thu, 19 Sep 1996 21:37:40 -0700 (PDT) Received: from rover.village.org (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with ESMTP id WAA25562; Thu, 19 Sep 1996 22:36:45 -0600 (MDT) Message-Id: <199609200436.WAA25562@rover.village.org> To: Joe Greco Subject: Re: Panix, TCP, and RED Cc: hackers@freebsd.org In-reply-to: Your message of Thu, 19 Sep 1996 22:38:26 CDT Date: Thu, 19 Sep 1996 22:36:45 -0600 From: Warner Losh Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hmmm. just sent something similar off to -security :-) Great minds... Warner From owner-freebsd-hackers Thu Sep 19 21:53:01 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA08713 for hackers-outgoing; Thu, 19 Sep 1996 21:53:01 -0700 (PDT) Received: from bunyip.cc.uq.oz.au (daemon@bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA08661 for ; Thu, 19 Sep 1996 21:52:52 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.oz.au (8.7.6/8.7.3) id OAA27027; Fri, 20 Sep 1996 14:52:43 +1000 Received: from pandora.devetir.qld.gov.au by ogre.devetir.qld.gov.au (8.7.5/DEVETIR-E0.3a) with ESMTP id OAA01429; Fri, 20 Sep 1996 14:54:29 +1000 (EST) Received: from netfl15a.devetir.qld.gov.au (netfl15a.devetir.qld.gov.au [167.123.24.12]) by pandora.devetir.qld.gov.au (8.6.10/8.6.12) with ESMTP id OAA01724; Fri, 20 Sep 1996 14:54:31 +1000 Received: by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id EAA26597; Fri, 20 Sep 1996 04:55:53 GMT Date: Fri, 20 Sep 1996 04:55:53 GMT Message-Id: <199609200455.EAA26597@netfl15a.devetir.qld.gov.au> MIME-Version: 1.0 X-Mailer: exmh version 1.6.5 12/11/95 X-Newsreader: knews 0.9.7 References: <199609200025.UAA10452@w2xo.pgh.pa.us> In-Reply-To: <199609200025.UAA10452@w2xo.pgh.pa.us> From: sysseh@devetir.qld.gov.au (Stephen Hocking) Subject: Re: auserver X-Original-Newsgroups: local.freebsd.hackers To: root@w2xo.pgh.pa.us, freebsd-hackers@freebsd.org Content-Type: text/plain Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk You need to set the AUDIOSERVER environment variable (this is assumimng you have au running already) to something like localhost:0 or use the -audio option (e.g. "auedit -audio tcp/localhost:8000 foo.wav") Stephen In article <199609200025.UAA10452@w2xo.pgh.pa.us>, Charlie Root writes: > Is anyone familiar with the au audio server? I'm not able to connect > to it on my 2.1.5 box. All the "au" programs just say "Can't connect > to audio server". I'm using an old 8 bit soundblaster and I have > all the /dev stuff made (MAKEDEV sb). > > -Jim Durham -- The views expressed above are not those of the Worker's Compensation Board of Queensland, Australia. From owner-freebsd-hackers Thu Sep 19 22:29:29 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA24392 for hackers-outgoing; Thu, 19 Sep 1996 22:29:29 -0700 (PDT) Received: from nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA24363 for ; Thu, 19 Sep 1996 22:29:24 -0700 (PDT) Received: from localhost (localhost.efn.org [127.0.0.1]) by nike.efn.org (8.7.5/8.7.3) with SMTP id WAA28163; Thu, 19 Sep 1996 22:29:46 -0700 (PDT) Date: Thu, 19 Sep 1996 22:29:45 -0700 (PDT) From: John-Mark Gurney Reply-To: John-Mark Gurney To: Scanner cc: freebsd-hackers@freebsd.org Subject: Re: TCP extensions breaking TCP. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 19 Sep 1996, Scanner wrote: > On Thu, 19 Sep 1996, Joe McGuckin wrote: > > > > > I've seen the enabled TCP extensions hang with SCO. > > More than likely its because the vendor's are not implementing the > extensions right and/or not sticking to the RFC's. Theres a way to prove > this from a FreeBSD box running 2.1+ . I beliece 2.1 is when T/TCP went > in. It can be shown at least in one OS's implementation that it is not > implemented right. The easy way to tell is to finger the machine thats > having problems most of the time if the extensions are not implemented > right or are broke, the finger will freak out and close before any info is > gained. wow... thanks for pointing out about the finger problem... I couldn't figure out why I couldn't finger any of my favorite hosts (i.e. resnet.uoregon.edu 2.1.5-RELEASE, garcia.efn.org SunOS 4.1.3, and dogbert.efn.org 2.1.0-RELEASE)... as soon as I disabled extensions I suddenly am able to finger them... plus I know for a fact that the extensions are turned on for resnet.uoregon.edu... anything I can do to fix the problem besides turning 'em off... I'm on a 2.2-0323-SNAP (soon to be 0801)... and behind slirp which could be my problem but before 0323 snap when I had 2.1.0 or 2.0.5 it worked fine... thanks for the info.. 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 Thu Sep 19 23:53:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA10939 for hackers-outgoing; Thu, 19 Sep 1996 23:53:34 -0700 (PDT) Received: from hp.com (hp.com [15.255.152.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA10921 for ; Thu, 19 Sep 1996 23:53:32 -0700 (PDT) Received: from srmail.sr.hp.com by hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA130742406; Thu, 19 Sep 1996 23:53:26 -0700 Received: from hpnmhjw.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA039052405; Thu, 19 Sep 1996 23:53:25 -0700 Received: from mina.sr.hp.com by hpnmhjw.sr.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA284302404; Thu, 19 Sep 1996 23:53:24 -0700 Message-Id: <199609200653.AA284302404@hpnmhjw.sr.hp.com> To: "Jordan K. Hubbard" Cc: rhh@ct.picker.com, hackers@freebsd.org Subject: Re: fdisk changes, anyone? In-Reply-To: Your message of "Wed, 18 Sep 1996 10:41:26 PDT." <27331.843068486@time.cdrom.com> Date: Thu, 19 Sep 1996 23:53:23 -0700 From: Darryl Okahata Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > To Jordan's point about specifying the partition info using > > command-line options (to avoid having to use a temp file with this method), > > a compromise solution might be to be able to specify a "-" on the command > > line for the config file path to allow the config file to be read from > > stdin. > > Hey, that'd work too! :-) Done. I thought about having an fdisk config database (analogous to /etc/disktab), but I don't think it'll work. I think people tend to use disks in one of two ways: 1. Dedicate the entire disk to FreeBSD. We don't need an fdisk config database for this. 2. Partition the disk up in "unusual" ways. Either an existing DOS partition is present, or the user wants to partition the disk "his way". The former can be handled without an fdisk config database (just use the remainder as a FreeBSD partition), and there are too many different possibilities in the latter. People with Zip or Jaz drives will probably dedicate the entire disk to FreeBSD, and so a special fdisk config database probably isn't necessary for these. -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. From owner-freebsd-hackers Fri Sep 20 01:00:11 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA19476 for hackers-outgoing; Fri, 20 Sep 1996 01:00:11 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA19462 for ; Fri, 20 Sep 1996 01:00:09 -0700 (PDT) Received: from research.gate.nec.co.jp (research.gate.nec.co.jp [202.32.8.49]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id BAA26980 for ; Fri, 20 Sep 1996 01:00:02 -0700 (PDT) Received: from sbl-gw.sbl.cl.nec.co.jp by research.gate.nec.co.jp (8.7.6+2.6Wbeta7/950912) with ESMTP id QAA19463; Fri, 20 Sep 1996 16:58:14 +0900 (JST) Received: from sirius.sbl.cl.nec.co.jp by sbl-gw.sbl.cl.nec.co.jp (8.7.5+2.6Wbeta6/3.3W6) with ESMTP id QAA10378; Fri, 20 Sep 1996 16:57:34 +0900 (JST) X-Authentication-Warning: sbl-gw.sbl.cl.nec.co.jp: Host nao@sirius [133.207.68.90] claimed to be sirius.sbl.cl.nec.co.jp Received: by sirius.sbl.cl.nec.co.jp (8.7.5+2.6Wbeta6/3.3W6) with UUCP id QAA20436; Fri, 20 Sep 1996 16:57:33 +0900 (JST) Date: Fri, 20 Sep 1996 16:57:33 +0900 (JST) From: Naoki Hamada Message-Id: <199609200757.QAA20436@sirius.sbl.cl.nec.co.jp> References: <199609172045.WAA06494@gvr.win.tue.nl> <199609190118.KAA11113@sirius.sbl.cl.nec.co.jp> To: guido@gvr.win.tue.nl CC: dfr@render.com, Guido.vanRooij@nl.cis.philips.com, freebsd-hackers@FreeBSD.org In-reply-to: Naoki Hamada's message of "Thu, 19 Sep 1996 10:18:30 +0900 (JST)" <199609190118.KAA11113@sirius.sbl.cl.nec.co.jp> Subject: Re: new if_vx driver on freefall Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi. A few of my friends tested the new vx driver. The result is mostly positive with/without BROKEN_AVAIL after a ping -f -s 1000. But one of them reported that his system works with the new vx driver (with BROKEN_AVAIL) almost well, but the network stops sometimes, then he had to re-ifconfig the board. -nao From owner-freebsd-hackers Fri Sep 20 01:15:55 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA25814 for hackers-outgoing; Fri, 20 Sep 1996 01:15:55 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA25764 for ; Fri, 20 Sep 1996 01:15:49 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id JAA23058; Fri, 20 Sep 1996 09:49:54 +0200 From: Luigi Rizzo Message-Id: <199609200749.JAA23058@labinfo.iet.unipi.it> Subject: IP queues -- how to limit them ? To: hackers@freebsd.org Date: Fri, 20 Sep 1996 09:49:54 +0200 (MET DST) Cc: luigi@labinfo.iet.unipi.it (Luigi Rizzo) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, (with reference to BSD implementations of TCP, but I'd be curious to know how routers approach this problem): is there any way to limit the amount of packets queued for delivery on a given interface ? I am asking because I notice an annoying problem when using PPP over a 14.4 line (easily reproducible when using a WWW browser). When one or more connections are transferring data, queues tend to pile up segments, up to the maximum window size for each connection (16K default). Since the bandwidth is so low, the queues are not very long (10-12 segments per connection) but take a long time to flush (4..12 sec per 16k, depending on the effectiveness of compression). The connections end up with an RTT constantly growing, up to unacceptable values (10s or more), and the RTT is totally dominated by the queueing delay. All this is totally pointless (as it delays other data, causes reduced control over the line, etc.) but since TCP as it is now does not stop expanding windows until a drop occurs, the only solution would be to avoid that a queue on an interface contains more than X seconds of data (related to its speed). So, any idea on how to set this limitation ? Thanks Luigi ==================================================================== Luigi Rizzo Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it Universita' di Pisa tel: +39-50-568533 via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 http://www.iet.unipi.it/~luigi/ ==================================================================== From owner-freebsd-hackers Fri Sep 20 01:28:32 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA01389 for hackers-outgoing; Fri, 20 Sep 1996 01:28:32 -0700 (PDT) Received: (from hsu@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA01366; Fri, 20 Sep 1996 01:28:29 -0700 (PDT) Date: Fri, 20 Sep 1996 01:28:29 -0700 (PDT) From: Jeffrey Hsu Message-Id: <199609200828.BAA01366@freefall.freebsd.org> To: jb@cimlogic.com.au Subject: libc_r bug Cc: hackers Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following program exhibits a bug in the latest version of libc_r. If the two lines are reversed, then everything's okay. main() { write(1, "hi", 2); printf("hello world\n"); } From owner-freebsd-hackers Fri Sep 20 02:29:15 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA23067 for hackers-outgoing; Fri, 20 Sep 1996 02:29:15 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA23040 for ; Fri, 20 Sep 1996 02:29:10 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id CAA17285 for ; Fri, 20 Sep 1996 02:29:14 -0700 (PDT) Prev-Resent: Fri, 20 Sep 1996 02:29:13 -0700 Prev-Resent: "hackers@freebsd.org " Received: from orade.ora.de (orade.ora.de [194.231.29.130]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id CAA17273 for ; Fri, 20 Sep 1996 02:27:21 -0700 (PDT) Received: (bad@localhost) by orade.ora.de (8.6.12/8.6.4) id LAA06552 for jkh@time.cdrom.com; Fri, 20 Sep 1996 11:27:03 +0200 From: bad@ora.de (Christoph Badura) Message-Id: <199609200927.LAA06552@orade.ora.de> Subject: Re: I can't install FreeBSD on Seagate Medalist 1080sl (ST51080N) :( To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Fri, 20 Sep 1996 11:27:02 +0200 (MET DST) In-Reply-To: <15748.843171383@time.cdrom.com> from "Jordan K. Hubbard" at Sep 19, 96 03:16:23 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Resent-To: hackers@freebsd.org Resent-Date: Fri, 20 Sep 1996 02:29:13 -0700 Resent-Message-ID: <17283.843211753@time.cdrom.com> Resent-From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Robert Nordier has been working for some months on a complete > and total re-write which also handles Win95 long filenames > and other interesting extensions. Since I don't know what the other extensions are this is probably irrelevant. Wolfgang Solfrank committed long filename and NT attribute support in msdosfs last November to the NetBSD source. Recently, he checked in a fsck_msdos. Perhaps you want to point Robert at this if he doesn't already know. -- Christoph Badura O'Reilly/International Thomson Verlag From owner-freebsd-hackers Fri Sep 20 03:03:08 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA09931 for hackers-outgoing; Fri, 20 Sep 1996 03:03:08 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA07491 for ; Fri, 20 Sep 1996 02:58:28 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.6/CET-v2.1) with SMTP id JAA24555; Fri, 20 Sep 1996 09:56:12 GMT Date: Fri, 20 Sep 1996 18:56:12 +0900 (JST) From: Michael Hancock To: "Gordon W. Ross" cc: freebsd-hackers@FreeBSD.ORG, tech-kern@netbsd.org Subject: Re: spl models and smp (was Re: Some interesting papers on BSD ...) In-Reply-To: <9609191326.AA03526@bach> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 19 Sep 1996, Gordon W. Ross wrote: > > Date: Thu, 19 Sep 1996 10:59:37 +0900 (JST) > > From: Michael Hancock > > > [Just going through some old mail] > > > > I was reviewing some spl and locking models for SMP. SVR4/MP combines > > locking primitives with spl and Solaris is completely redesigned to the > > implementation to use kernel threads instead for interrupts so it can use > > the same locking model as the rest of the code. > > Actually, I'm pretty sure that's not quite true. Here is how it works. > The relevant parts of the interface are: You're right. Solaris has Interrupt threads that can use the same *synchonization* primitives as any other thread. It blocks interrupts in some cases when acquiring a mutex lock. The interrupt handler raises the ipl and allocates a thread from the interrupt thread pool and switches to it. I guess ipl's are fairly expensive on Sparcs so not having to block interrupts on sychronization objects makes up for the overhead of setting up the interrupt threads. Sychronization operations are more frequent than interrupts. Bruce Evans said that ipls on Intel are pretty cheap, I think they take about half the clock cycles compared to Sparc. So the wins might be less significant on Intel. Can any confirm this? There's an article on this in the Apr. 95 Unix Review by Kleiman. Regards, Mike Hancock > /* This is a mutex lock. It MIGHT lock out interrupts. */ > kmutex_t driver_mutex; > > /* Somewhere, during initialization (attach) you do this: */ > mutex_init(&driver_mutex, "mcos", MUTEX_DRIVER, (void*)&driver_ibcookie); > > /* Then, a section that needs atomic actions is wrapped with: */ > mutex_enter(&driver_mutex); > /* now have exclusive access to the object locked with this mutex. */ > mutex_exit(&driver_mutex); > /* now others may take the mutex lock. */ > > The way these block interrupts is: if the driver_ibcookie (which > was returned to you when you attached your interrupt handler) is > passed to mutex_init, rather than a null pointer, then anyone who > does a mutex_enter() on that mutex will raise their spl as needed > to block that interrupt, and then spin-wait. The spin-wait will > never have to actually spin unless there is another CPU that holds > the mutex. When we take the mutex from non-interrupt level, the > mutex_enter() will have raised the spl() such that we don't have > to worry about deadlocking against our own interrupt handler. > > Also note that Solaris no longer supports sleep/wakeup in MP drivers. > Instead, you use these new functions: > > /* Here is the equivalent to the old sleep() call: */ > status = cv_timedwait_sig(&sp->condvar, &driver_mutex, abst); > > /* Here is the equivalent to the old wakeup() call: */ > cv_signal(&sp->condvar); > > Note that you MUST hold a mutex lock on some object that has both > the mutex and a condition variable, adn the cv_timedwait_sig() > does an atomic "block and release the mutex" while making you > non-runnable, and later does an atomic "resume and take mutex." > Interesting scheme, eh? > > Gordon > -- michaelh@cet.co.jp http://www.cet.co.jp CET Inc., Daiichi Kasuya BLDG 8F 2-5-12, Higashi Shinbashi, Minato-ku, Tokyo 105 Japan Tel: +81-3-3437-1761 Fax: +81-3-3437-1766 From owner-freebsd-hackers Fri Sep 20 03:06:30 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA11419 for hackers-outgoing; Fri, 20 Sep 1996 03:06:30 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA11349 for ; Fri, 20 Sep 1996 03:06:21 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.6/CET-v2.1) with SMTP id KAA24606 for ; Fri, 20 Sep 1996 10:04:56 GMT Date: Fri, 20 Sep 1996 19:04:56 +0900 (JST) From: Michael Hancock To: FreeBSD Hackers Subject: Intel Deschutes Architecture Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Intel has plans to introduce a new processor card architecture late next year called Deschutes that will allow up to 32 processors and a larger L2 cache. The page coloring stuff should result in bigger wins on that architecture. Regards, Mike Hancock From owner-freebsd-hackers Fri Sep 20 05:31:44 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA20505 for hackers-outgoing; Fri, 20 Sep 1996 05:31:44 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA20390 for ; Fri, 20 Sep 1996 05:31:32 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.6/CET-v2.1) with SMTP id MAA25502; Fri, 20 Sep 1996 12:28:22 GMT Date: Fri, 20 Sep 1996 21:28:22 +0900 (JST) From: Michael Hancock To: Terry Lambert cc: freebsd-hackers@FreeBSD.org Subject: Re: thread stacks and protections (was Re: attribute/inode caching) In-Reply-To: <199609191856.LAA01219@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 19 Sep 1996, Terry Lambert wrote: > > > Personally, I'd like to use page anonymity based protections to establish > > > Chorus-like access priveledge domains for IPC; specifically, for stacks > > > capable of being grown by fault for use by threads. I think the POSIX > > > model is broken: I should not be required to preallocate stack for a > > > thread just because SVR4 and Solaris have bogus architectures (actually, > > > > How does one implement a u-area concept on top of Chorus? A lot of stuff > > that used to be in the u-area has been moved out to the proc and other > > structures in 4.4BSD. Maybe moving the kernel stack out of the u-area and > > generalizing the proc and u-cred stuff can be a step toward what your > > talking about. > > Maybe I don't understand the question, or maybe you aren't asking in > the context of page-anonymity based protections, which are statistical > protections using MMU faulting rather than domain crossing protections > using instruction faulting. Your reference to thread stacks being able to grow is why I brought up the kernel stack being in the u-area. Where would kernel thread stacks go if you wanted them to be able to grow dynamically? > I think John Dyson's response is best: it can be implemented (I wouldn't > say it was as trivial to do as John implies, but then John is a VM > guy and I am an FS guy), but we need to make sure that it's the right > thing being implemented. I think John meant that the kernel stack can easily be moved somewhere else as I was talking about an interim non-smp step. BTW, an interim step doesn't sound necessary after listening to John's description of the flexibility already enabled in the current framework, unless people really wanted more kernel stack then there is now and the tradeoffs were reasonable. Regards, Mike Hancock From owner-freebsd-hackers Fri Sep 20 06:04:14 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA12195 for hackers-outgoing; Fri, 20 Sep 1996 06:04:14 -0700 (PDT) Received: from ccs.sogang.ac.kr (ccs.sogang.ac.kr [163.239.1.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA12099 for ; Fri, 20 Sep 1996 06:04:05 -0700 (PDT) Received: from oslab.sogang.ac.kr by ccs.sogang.ac.kr (8.7.5/Sogang) id VAA16489; Fri, 20 Sep 1996 21:59:48 +0900 (KST) Received: by oslab.sogang.ac.kr (4.1/SMI-4.1) id AA19360; Fri, 20 Sep 96 09:46:15 KST Date: Fri, 20 Sep 96 09:46:15 KST From: dude@oslab.sogang.ac.kr (Hong Seungwook) Message-Id: <9609200046.AA19360@oslab.sogang.ac.kr> Subject: [?] How can I add new field in 'proc' struct Apparently-To: freebsd-hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I am now using freebsd 2.1.0 and I've tried to add a field in 'proc' structure but I couldn't because after compile the kernel and boot again the kernel seems to be downed. So, will you please tell me how can I add a new filed in 'proc' structure. Thank you. from Seungwook, Hong From owner-freebsd-hackers Fri Sep 20 07:57:59 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA11885 for hackers-outgoing; Fri, 20 Sep 1996 07:57:59 -0700 (PDT) Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA11853 for ; Fri, 20 Sep 1996 07:57:54 -0700 (PDT) Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by quackerjack.cc.vt.edu (8.7.1/8.7.1) with SMTP id KAA21331; Fri, 20 Sep 1996 10:57:41 -0400 (EDT) Received: from jandrese.async.vt.edu (jandrese.async.vt.edu [128.173.20.208]) by sable.cc.vt.edu (8.6.12/8.6.12) with SMTP id KAA30830; Fri, 20 Sep 1996 10:57:39 -0400 Date: Fri, 20 Sep 1996 11:01:29 +0000 () From: Nessus X-Sender: jandrese@jandrese.async.vt.edu To: Stephen Hocking cc: root@w2xo.pgh.pa.us, freebsd-hackers@FreeBSD.org Subject: Re: auserver In-Reply-To: <199609200455.EAA26597@netfl15a.devetir.qld.gov.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 20 Sep 1996, Stephen Hocking wrote: > You need to set the AUDIOSERVER environment variable (this is assumimng you > have au running already) to something like localhost:0 or use the -audio > option (e.g. "auedit -audio tcp/localhost:8000 foo.wav") > > Stephen > > In article <199609200025.UAA10452@w2xo.pgh.pa.us>, > Charlie Root writes: > > Is anyone familiar with the au audio server? I'm not able to connect > > to it on my 2.1.5 box. All the "au" programs just say "Can't connect > > to audio server". I'm using an old 8 bit soundblaster and I have > > all the /dev stuff made (MAKEDEV sb). > > > > -Jim Durham > Also, the auserver wouldn't work on my machine unless I specifically set the port when I started the server: eg. au :8000 :::::::::::::::::::::::::::. . . . . ..:::::::::::::::::::::::::::: :: Jason Andresen :. . . . . . . . . : Nessus :: :: jandrese@vt.edu :.:.:.:.:.:.:.:.:.:: nessus@vt.edu :: :.........................: Quote of the day :..........................: I went to a place to eat. It said `BREAKFAST ANYTIME.' So I ordered French toast during the Renaissance. -- Stephen Wright :::::::::::.:.:.:.:.:.:.:.........................:.:.:.:.:.:.:.::::::::::: From owner-freebsd-hackers Fri Sep 20 08:18:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA20642 for hackers-outgoing; Fri, 20 Sep 1996 08:18:34 -0700 (PDT) Received: from relay.philips.nl (ns.philips.nl [130.144.65.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA20605 for ; Fri, 20 Sep 1996 08:18:23 -0700 (PDT) Received: (from smap@localhost) by relay.philips.nl (8.6.9/8.6.9-950414) id RAA29046; Fri, 20 Sep 1996 17:16:35 +0200 Received: from unknown(192.26.173.32) by ns.philips.nl via smap (V1.3+ESMTP) with ESMTP id sma027123; Fri Sep 20 17:04:00 1996 Received: from spooky.lss.cp.philips.com (spooky.lss.cp.philips.com [130.144.199.105]) by smtp.nl.cis.philips.com (8.6.10/8.6.10-0.9z-02May95) with ESMTP id RAA00835; Fri, 20 Sep 1996 17:06:52 +0200 Received: (from guido@localhost) by spooky.lss.cp.philips.com (8.6.10/8.6.10-0.991c-08Nov95) id RAA25073; Fri, 20 Sep 1996 17:03:52 +0200 From: Guido van Rooij Message-Id: <199609201503.RAA25073@spooky.lss.cp.philips.com> Subject: Re: new if_vx driver on freefall To: nao@sbl.cl.nec.co.jp (Naoki Hamada) Date: Fri, 20 Sep 1996 17:03:51 +0200 (MET DST) Cc: guido@gvr.win.tue.nl, dfr@render.com, Guido.vanRooij@nl.cis.philips.com, freebsd-hackers@FreeBSD.org Reply-To: Guido.vanRooij@nl.cis.philips.com In-Reply-To: <199609200757.QAA20436@sirius.sbl.cl.nec.co.jp> from Naoki Hamada at "Sep 20, 96 04:57:33 pm" 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 Naoki Hamada wrote: > Hi. > > A few of my friends tested the new vx driver. The result is mostly > positive with/without BROKEN_AVAIL after a ping -f -s 1000. But one of > them reported that his system works with the new vx driver (with > BROKEN_AVAIL) almost well, but the network stops sometimes, then he > had to re-ifconfig the board. I ordered the specs from 3com and I'm waiting for them. Basically,if your board runs fine without BROKEN_AVAIL, do *not* define it. If it stops for your firends, could you verfiy with ifconfig vx0 that the state is OACTIVE? -Guido From owner-freebsd-hackers Fri Sep 20 09:22:35 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA21813 for hackers-outgoing; Fri, 20 Sep 1996 09:22:35 -0700 (PDT) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA21778 for ; Fri, 20 Sep 1996 09:22:29 -0700 (PDT) Received: from ppp-089.etinc.com (ppp-089.etinc.com [204.141.95.148]) by etinc.com (8.6.12/8.6.9) with SMTP id MAA20916; Fri, 20 Sep 1996 12:28:47 -0400 Date: Fri, 20 Sep 1996 12:28:47 -0400 Message-Id: <199609201628.MAA20916@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Joe Greco From: dennis@etinc.com (Dennis) Subject: Re: Routers - hardware received wisdom Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Well, interfaces just queue packets for the OS, > >Yes :-) > >> so if you do your queue >> management properly, you discard packets based on age, and if you have >> enough memory to hold your bandwidth * hold_time you wont dump anything >> that shouldnt be dumped. > >No. If your CPU is overloaded, you will end up dumping data that >is valid and shouldn't be dumped, simply because you never have the >chance to deal with it. And queueing only buys you a very little bit, >because when it comes right down to it, if I can overload your router >for a second, I can probably overload your router continuously - making >any queueing you do utterly useless. Queue management IS the cpu load. Hardware drivers just queue...all you need is some simple filters to get around abnormal data. A slightly intelligent process... The issue with Ciscos it that their filters have high overhead...so you cant even filter when you come under attack! > >> However, what you're talking about is not real data... > >Until it starts coming in at you off the Internet, outside of your control. >THAT is the whole point. Thats not really what the guy asked....any router can be brought down under certain circumstances. Its like saying the FreeBSD can't handle a 100Mbs ethernet....It can, under normal circumstances... Dennis From owner-freebsd-hackers Fri Sep 20 10:43:31 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA29918 for hackers-outgoing; Fri, 20 Sep 1996 10:43:31 -0700 (PDT) Received: from mail.freegate.net ([205.178.36.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA29892 for ; Fri, 20 Sep 1996 10:43:24 -0700 (PDT) Received: (qmail-queue invoked from smtpd); 20 Sep 1996 17:40:57 -0000 Received: from ws40.freegate.net (192.168.1.40) by freegate.net with SMTP; 20 Sep 1996 17:40:57 -0000 Received: by ws40.freegate.net with Microsoft Mail id <01BBA6E0.7D655A60@ws40.freegate.net>; Fri, 20 Sep 1996 10:42:58 -0700 Message-ID: <01BBA6E0.7D655A60@ws40.freegate.net> From: Janice McLaughlin To: "'hackers@freebsd.org'" Cc: "'janus@freegate.net'" Subject: Plug and Play naivety Date: Fri, 20 Sep 1996 10:42:57 -0700 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 writing a device driver for an ISA card with the Plug and Play chip on it and have a few questions. (I'm not new to device drivers but am definately new to ISA and x86 class machines). I'm runing on 2.2-960801-SNAP. A search of the archives shows me that at least I'm not alone in my problems with PnP. I have also downloaded the latest code from Sujal Patel on freefall.freebsd.org for PnP support. 1. mail from Sujal notes that "if your motherboard supports PnP devices, then you don't need this code". What does this mean? I've been told that the BIOS on the machine I'm using has "Plug and Play" support ... does this mean it's possible that the BIOS has queried the ISA devices on boot and already has all the config info? Can I get at this somehow from the kernel? Or is this only referring to PCI kind of Plug and Play? 2. I notice that the recommendation for other cards (eg: 3c509) is to turn "off" PnP. That's sounds great ... how do I do that? Is it card specific? When you do this to a (for example) 3c509, does it stay off only until the next power up? or is there some NVRAM somewhere that can store this info so you don't have to reconfig it each time you reboot? Thanks alot, Janice From owner-freebsd-hackers Fri Sep 20 11:01:46 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA11176 for hackers-outgoing; Fri, 20 Sep 1996 11:01:46 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA11151 for ; Fri, 20 Sep 1996 11:01:43 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id LAA04635; Fri, 20 Sep 1996 11:01:17 -0700 (PDT) Message-Id: <199609201801.LAA04635@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: Janice McLaughlin cc: "'hackers@freebsd.org'" Subject: Re: Plug and Play naivety In-reply-to: Your message of "Fri, 20 Sep 1996 10:42:57 PDT." <01BBA6E0.7D655A60@ws40.freegate.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Sep 1996 11:01:17 -0700 From: Amancio Hasty Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >From The Desk Of Janice McLaughlin : > > I'm writing a device driver for an ISA card with the Plug and Play > chip on it and have a few questions. (I'm not new to device drivers > but am definately new to ISA and x86 class machines). I'm > runing on 2.2-960801-SNAP. > > A search of the archives shows me that at least I'm not alone > in my problems with PnP. I have also downloaded the latest code > from Sujal Patel on freefall.freebsd.org for PnP support. > > 1. mail from Sujal notes that "if your motherboard supports PnP > devices, then you don't need this code". What does this mean? > I've been told that the BIOS on the machine I'm using has > "Plug and Play" support ... does this mean it's possible that the > BIOS has queried the ISA devices on boot and already has all the > config info? Can I get at this somehow from the kernel? Or is this > only referring to PCI kind of Plug and Play? Some devices may need further initialization and for this you will need driver support. For instance, the GUS PnP after the BIOS or the driver activates the card , the driver then does further initialization specific to the card. The card specific initialization or configuration is usually not due to PnP . Citing again, the GUS cards prior to their PnP implementation one could software program the dma and irq settings for the card. In my case, because it is often difficult for users to modify kernel files, the driver has special hooks so that if the kernel via the kernel configuation passess all the configuration information to the driver , the driver will initialize the card according to the supplied information. The effect is that manually configuring a GUS PnP looks pretty much like any old ISA device in the kernel configuration file. This is useful for cases in which the BIOS PnP implementation is broken , makes a mistake in initializing the card, or the motherboard does not support PnP. > 2. I notice that the recommendation for other cards (eg: 3c509) > is to turn "off" PnP. That's sounds great ... how do I do that? Is > it card specific? When you do this to a (for example) 3c509, does > it stay off only until the next power up? or is there some NVRAM > somewhere that can store this info so you don't have to reconfig > it each time you reboot? Not all ISA PnP devices have a mechanism to disable PnP. Enjoy, Amancio From owner-freebsd-hackers Fri Sep 20 11:02:41 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA11661 for hackers-outgoing; Fri, 20 Sep 1996 11:02:41 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA11639 for ; Fri, 20 Sep 1996 11:02:38 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA02736; Fri, 20 Sep 1996 11:01:58 -0700 From: Terry Lambert Message-Id: <199609201801.LAA02736@phaeton.artisoft.com> Subject: Re: thread stacks and protections (was Re: attribute/inode caching) To: michaelh@cet.co.jp (Michael Hancock) Date: Fri, 20 Sep 1996 11:01:58 -0700 (MST) Cc: terry@lambert.org, freebsd-hackers@FreeBSD.org In-Reply-To: from "Michael Hancock" at Sep 20, 96 09:28:22 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 > > Maybe I don't understand the question, or maybe you aren't asking in > > the context of page-anonymity based protections, which are statistical > > protections using MMU faulting rather than domain crossing protections > > using instruction faulting. > > Your reference to thread stacks being able to grow is why I brought up the > kernel stack being in the u-area. Where would kernel thread stacks go if > you wanted them to be able to grow dynamically? Ah. A kernel thread has a VM disctinct from other threads. Therefore they would go in the same (virtual) place in each thread. John alluded to this in his posting about making the kernel stack dynamic. The only thing that needs to change between kernel-dynamic for single entrancy and thread-dynamic for multiple entrancy is the location of the stack pointer that gets referenced. This assume the kernel can handle a guard page fault at SPL, etc.. It means a preallocation so that the page insertion can take place, and a 4k insertion stack (one page) for handling the fault when it occurs in kernel space. This would require that the processor honor the WP bit if it's an Intel processor; for 386's, you would have to choose a "largest reasonable amount" and just live with it. A much bigger problem is shared heap, unshared stack in a single pmap, which is the case for user space threads, and is why the POSIX threading model specifies you pass the stack to the thread creation as a preallocated entity. You can break this up into "auto-grow" zones using a guard page, but then the mapping can only grow to the point it intersects another zone. Ie: I hit the guard page, I fault, I add a new page, I move the guard page down one page, I continue -- but I've reduced the space to the next area by one page because I've divided up the available space to get my mappings into the same adress space map. The "proper" soloution is *probably* to fragment the map instead, where one thread has a slightly different VM space than another -- the difference being the stack mapping. So mapped text objects (the program and shared library code) and mapped heap objects (the program data and shared library data) remain the same from thread to thread, but the page mapping and guard page mapping for each thread is the only stack mapping for the given process. This implies a heavier-than-expected mapping overhead. Another alternative is a hybrid approach: You zone for some amount, and then after you exceed your zone for a given thread, you engage in pmap changes. This "punishes" threads with "excessive" stack use, while leaving other threads unadulterated. It's probably the correct approach, if the stack can be made arbitrarily large. > > I think John Dyson's response is best: it can be implemented (I wouldn't > > say it was as trivial to do as John implies, but then John is a VM > > guy and I am an FS guy), but we need to make sure that it's the right > > thing being implemented. > > I think John meant that the kernel stack can easily be moved somewhere > else as I was talking about an interim non-smp step. BTW, an interim step > doesn't sound necessary after listening to John's description of the > flexibility already enabled in the current framework, unless people really > wanted more kernel stack then there is now and the tradeoffs were > reasonable. I think the 386 not honoring the WP bit in protected mode (so you can't get a stack-grow fault oon your guard page) is a bigger stumbling block to implementing straight in without an interim step for 386's to fall back to. 8-(. Limits of hardware... 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 Fri Sep 20 11:14:24 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA18929 for hackers-outgoing; Fri, 20 Sep 1996 11:14:24 -0700 (PDT) Received: from mickey.umiacs.umd.edu (12222@mickey.umiacs.umd.edu [128.8.120.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA18903 for ; Fri, 20 Sep 1996 11:14:21 -0700 (PDT) Received: (smpatel@localhost) by mickey.umiacs.umd.edu (8.7.6/UMIACS-0.9/04-05-88) id OAA04117; Fri, 20 Sep 1996 14:14:15 -0400 (EDT) Date: Fri, 20 Sep 1996 14:14:14 -0400 (EDT) From: Sujal Patel To: Janice McLaughlin cc: "'hackers@freebsd.org'" Subject: Re: Plug and Play naivety In-Reply-To: <01BBA6E0.7D655A60@ws40.freegate.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 20 Sep 1996, Janice McLaughlin wrote: > 1. mail from Sujal notes that "if your motherboard supports PnP > devices, then you don't need this code". What does this mean? > I've been told that the BIOS on the machine I'm using has > "Plug and Play" support ... does this mean it's possible that the > BIOS has queried the ISA devices on boot and already has all the > config info? Can I get at this somehow from the kernel? Or is this > only referring to PCI kind of Plug and Play? The PnP-aware BIOS will configure all ISA PnP cards (to the best of it's ability) during the boot up cycle. If the BIOS gets this wrong (which it often does), you'll need to either use the PnP driver or turn if PnP (if the device supports that option). > 2. I notice that the recommendation for other cards (eg: 3c509) > is to turn "off" PnP. That's sounds great ... how do I do that? Is > it card specific? When you do this to a (for example) 3c509, does > it stay off only until the next power up? or is there some NVRAM > somewhere that can store this info so you don't have to reconfig > it each time you reboot? Some cards like the Supra Modem's have no NVRAM, so you must use the PnP driver. The 3c509 has NVRAM which stores the configuration if you turn of PnP, their DOS setup program (on www.3com.com) will be able to do that. Sujal From owner-freebsd-hackers Fri Sep 20 11:20:41 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA22534 for hackers-outgoing; Fri, 20 Sep 1996 11:20:41 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA22508 for ; Fri, 20 Sep 1996 11:20:38 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.6.12/8.6.12) with SMTP id LAA20201 for ; Fri, 20 Sep 1996 11:20:30 -0700 Date: Fri, 20 Sep 1996 11:20:30 -0700 (PDT) From: Jaye Mathisen To: hackers@freebsd.org Subject: Tweaking FreeBSD (2.1) and sendmail for a busy site? Or maybe, Help! , No more sendmail's. Message-ID: 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 P5-120 for a mail/radius server, and it's starting to show a little stress. THe la stays around 0.1 or so, but when I get a lot of incoming mail, then when 14 sendmail's are hanging around, it stops accepting more. Telnet to the smtp port never connect. As soon as one of the 14 drops off, then I can connect. I thought maybe it was the listen parameter, but the default is something like 128. maxusers is set to 128, and there's plenty of RAM and swap. Any good ideas? I looked at cf/README for sendmail, and didn't see an obvious parameter in there that limited the number of sendmail processes, other than la related stuff, which isn't an issue on this box. What else should I check? There are no errors in any log, nothing from the accepting sendmail about unable to fork or any of that stuff. The sendmail is 8.6.12 + patches soon to be upgraded to 8.7.x The box is running a -stable from approx. November. Any ideas appreciated. From owner-freebsd-hackers Fri Sep 20 11:38:55 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA01009 for hackers-outgoing; Fri, 20 Sep 1996 11:38:55 -0700 (PDT) Received: from csla.csl.sri.com (csla.csl.sri.com [192.12.33.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA00935 for ; Fri, 20 Sep 1996 11:38:48 -0700 (PDT) Received: from impulse.csl.sri.com (impulse.csl.sri.com [130.107.15.11]) by csla.csl.sri.com (8.7.3/8.7.3) with ESMTP id LAA07553 for ; Fri, 20 Sep 1996 11:38:14 -0700 (PDT) Received: from impulse.csl.sri.com (localhost [127.0.0.1]) by impulse.csl.sri.com (8.7.3/8.7.3) with ESMTP id LAA01472 for ; Fri, 20 Sep 1996 11:35:45 -0700 (PDT) Message-Id: <199609201835.LAA01472@impulse.csl.sri.com> To: hackers@freebsd.org Subject: rpcgen / fgets Date: Fri, 20 Sep 1996 11:35:45 -0700 From: Fred Gilham Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm having trouble with rpcgen. It seems to happen in both 2.1.5R and 2.2-960801-SNAP. The symptom is that directives (lines in the .x file beginning with %) that have continuation indicators ("\" as the last character of the line) get garbled. Here's what I see: %#define PRINTRECORD(fp,r,t) { \ % fprintf(fp,RECFORMAT, \ % UID_LEN, r->userid, \ % COUNT_LEN, r->count, \ % SEED_LEN, r->seed, \ % VAL_LEN, r->val, \ % TIME_LEN, t); \ %} gets turned into #define PRINTRECORD(fp,r,t) { % fprintf(fp,RECFORMAT, % UID_LEN, r->userid, % COUNT_LEN, r->count, % SEED_LEN, r->seed, % V AL_LEN, r->val, % TIME_LEN, t); %} This obviously won't compile. On the other hand, sunos and solaris rpcgen both handle this correctly. I've run rpcgen through the debugger. The code that writes directives is . . . } else if (directive(curline)) { printdirective(curline); Setting the breakpoint at printdirective(), I see: (gdb) where #0 printdirective ( line=0x13d24 "%#define PRINTRECORD(fp,r,t) { % fprintf(fp,RECFORMAT,", ' ' , "%\t UID_LEN, r->userid, %\t COUNT_LEN, r->count, %\t SEED_LEN, r->seed, %\t VAL_LEN, r->val, % "...) at rpc_scan.c:475 #1 0xb321 in get_token (tokp=0xefbfda18) at rpc_scan.c:192 #2 0x8b88 in get_definition () at rpc_parse.c:76 #3 0x2023 in c_output (infile=0xefbfdb60 "otpdb.x", define=0x15af "-DRPC_XDR", extend=1, outfile=0x15fc "_xdr.c") at rpc_main.c:465 #4 0x17e9 in main (argc=2, argv=0xefbfdaac) at rpc_main.c:206 which means that the line fed to printdirective() is already mangled. It almost looks like fgets() is somehow processing the continuation characters but I don't see anything in the code for fgets() that would do that. Another indication that this problem is caused by the continuation characters is that if I put a space after the continuation characters, the line is handled properly, i.e. %#define PRINTRECORD(fp,r,t) { \ % fprintf(fp,RECFORMAT, \ % UID_LEN, r->userid, \ % COUNT_LEN, r->count, \ % SEED_LEN, r->seed, \ % VAL_LEN, r->val, \ % TIME_LEN, t); \ %} (with spaces after the `\' character) becomes #define PRINTRECORD(fp,r,t) { \ fprintf(fp,RECFORMAT, \ UID_LEN, r->userid, \ COUNT_LEN, r->count, \ SEED_LEN, r->seed, \ VAL_LEN, r->val, \ TIME_LEN, t); \ } (also with spaces after the `\' character---still no good) but in the same file %#define PRINTHEADER(fp) { \ % fprintf(fp,RECFORMAT, \ % UID_LEN, "user", \ % COUNT_LEN, "count", \ % SEED_LEN, "seed", \ % VAL_LEN, "value", \ % TIME_LEN, "timestamp"); \ %} (without spaces after the `\' character) remains #define PRINTHEADER(fp) { % fprintf(fp,RECFORMAT, % UID_LEN, "user", % COUNT_LEN, "count", % SEED_LEN, "seed", % V AL_LEN, "value", % TIME_LEN, "timestamp"); %} Does anyone have any comments about this? Is this a bug or what? Obviously I can work around it, but the behavior seems incorrect. -Fred Gilham gilham@csl.sri.com From owner-freebsd-hackers Fri Sep 20 11:52:29 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA09755 for hackers-outgoing; Fri, 20 Sep 1996 11:52:29 -0700 (PDT) Received: from mickey.umiacs.umd.edu (12222@mickey.umiacs.umd.edu [128.8.120.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA09734 for ; Fri, 20 Sep 1996 11:52:26 -0700 (PDT) Received: (smpatel@localhost) by mickey.umiacs.umd.edu (8.7.6/UMIACS-0.9/04-05-88) id OAA05450; Fri, 20 Sep 1996 14:51:59 -0400 (EDT) Date: Fri, 20 Sep 1996 14:51:58 -0400 (EDT) From: Sujal Patel To: Janice McLaughlin cc: hackers@freebsd.org Subject: RE: Plug and Play naivety In-Reply-To: <01BBA6E8.D79F85C0@ws40.freegate.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 20 Sep 1996, Janice McLaughlin wrote: > It turns out that apparently I can't turn off PnP on my card. Let's > pretend that the BIOS *has* configured the card correctly. How > would I find out what address it has set the IO port and IRQ level to? > How do I find out how to talk to the card without putting mine and all > the other ISA PnP cards in the system through the Isolation Protocol > etc etc all over again? I haven't finished the code for this yet :-) Eventually all FreeBSD PnP (Isa PNP I mean), will just read the settings from the isa_device structure. In the meantime, if you look at the PnP configuration code, after the CSN is set- You can read the registers for IRQ/DRQ/etc (instead of setting them, as I do now). If would like to wait a couple of days, I'll cleanup some of the code I have now and send it to you... Sujal From owner-freebsd-hackers Fri Sep 20 11:54:32 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA11150 for hackers-outgoing; Fri, 20 Sep 1996 11:54:32 -0700 (PDT) Received: from night.primate.wisc.edu (night.primate.wisc.edu [144.92.43.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA11075; Fri, 20 Sep 1996 11:54:25 -0700 (PDT) Received: by night.primate.wisc.edu; id NAA00906; 8.6.10/41.8; Fri, 20 Sep 1996 13:58:20 -0500 From: Paul DuBois Message-Id: <199609201858.NAA00906@night.primate.wisc.edu> Subject: Re: libc_r bug To: hsu@freefall.freebsd.org (Jeffrey Hsu) Date: Fri, 20 Sep 1996 13:58:20 -0500 (CDT) Cc: hackers@freefall.freebsd.org In-Reply-To: <199609200828.BAA01366@freefall.freebsd.org> from "Jeffrey Hsu" at Sep 20, 96 01:28:29 am X-Mailer: ELM [version 2.4 PL25] 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 following program exhibits a bug in the latest version of libc_r. >If the two lines are reversed, then everything's okay. > >main() >{ > write(1, "hi", 2); > printf("hello world\n"); >} What happens, and what do you expect to happen? You're mixing stdio (buffered) and non-stdio (unbuffered) I/O. Unpredictable results will often ensue. From owner-freebsd-hackers Fri Sep 20 12:16:10 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA24140 for hackers-outgoing; Fri, 20 Sep 1996 12:16:10 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA24108 for ; Fri, 20 Sep 1996 12:16:05 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.eu.org [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id VAA11839 for ; Fri, 20 Sep 1996 21:16:00 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id VAA23051 for hackers@freebsd.org; Fri, 20 Sep 1996 21:15:52 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.Beta.4/keltia-uucp-2.9) id VAA21313; Fri, 20 Sep 1996 21:15:39 +0200 (MET DST) Message-Id: <199609201915.VAA21313@keltia.freenix.fr> Date: Fri, 20 Sep 1996 21:15:39 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: hackers@freebsd.org Subject: Re: Tweaking FreeBSD (2.1) and sendmail for a busy site? Or maybe, Help! , No more sendmail's. In-Reply-To: ; from Jaye Mathisen on Sep 20, 1996 11:20:30 -0700 References: X-Mailer: Mutt 0.43g Mime-Version: 1.0 X-Operating-System: FreeBSD 2.2-CURRENT ctm#2443 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Jaye Mathisen: > Telnet to the smtp port never connect. As soon as one of the 14 drops > off, then I can connect. Wild guess: out of pty ? I got burn by a weird problem with ttyp8/ptyp8 on my box. No process can get this particular pty. I had ot rm it to be able to use more pty... -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #21: Sun Sep 8 14:35:00 MET DST 1996 From owner-freebsd-hackers Fri Sep 20 13:12:15 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA28114 for hackers-outgoing; Fri, 20 Sep 1996 13:12:15 -0700 (PDT) Received: from gvr.win.tue.nl (root@gvr.win.tue.nl [131.155.210.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA28078 for ; Fri, 20 Sep 1996 13:12:09 -0700 (PDT) Received: by gvr.win.tue.nl (8.6.13/1.53) id WAA14704; Fri, 20 Sep 1996 22:11:28 +0200 From: guido@gvr.win.tue.nl (Guido van Rooij) Message-Id: <199609202011.WAA14704@gvr.win.tue.nl> Subject: Re: vx device broken in 21.1.5? To: cmcurtin@research.megasoft.com Date: Fri, 20 Sep 1996 22:11:27 +0200 (MET DST) Cc: ache@nagual.ru, dfr@render.com, roberto@keltia.freenix.fr, freebsd-hackers@FreeBSD.org In-Reply-To: <199609172117.RAA00608@goffette.research.megasoft.com> from C Matthew Curtin at "Sep 17, 96 05:17:51 pm" 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 C Matthew Curtin wrote: > >>>>> "Guido" == Guido van Rooij writes: > > > >> It not makes things worse, but not help the problem too. My > >> problem was not performance decrease but complete card hang until > >> reboot. > > Guido> Try ifconfig vx0 down; ifconfig.vx0 up. Then it works again > Guido> ;-() > > The problem is that there are two versions of the 3c590 board. The > FreeBSD driver was written for 3c590, but now all of the 3c590 boards > out there are "3c590b"... some small change made the driver not working. Indeed that's what i found out. I don't know however what is not working. The linux driver does still work... -Guido From owner-freebsd-hackers Fri Sep 20 13:17:02 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA00369 for hackers-outgoing; Fri, 20 Sep 1996 13:17:02 -0700 (PDT) Received: from gvr.win.tue.nl (root@gvr.win.tue.nl [131.155.210.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA00336 for ; Fri, 20 Sep 1996 13:16:56 -0700 (PDT) Received: by gvr.win.tue.nl (8.6.13/1.53) id WAA14725; Fri, 20 Sep 1996 22:14:09 +0200 From: guido@gvr.win.tue.nl (Guido van Rooij) Message-Id: <199609202014.WAA14725@gvr.win.tue.nl> Subject: Re: CD-R Drive To: darrend@novell.com (Darren Davis) Date: Fri, 20 Sep 1996 22:14:08 +0200 (MET DST) Cc: hackers@freebsd.org In-Reply-To: from Darren Davis at "Sep 19, 96 10:54:11 am" 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 Darren Davis wrote: > What write once CD-ROM/CD-R drive do you recommend for FreeBSD. I saw > the mail about the HP drive not working, what drive should I get? > > Thanks, You can use a Philips CDD2000 (use the HP4020i config for that). Basically the two are the same (the HP is an oem-ed version). -Guido From owner-freebsd-hackers Fri Sep 20 13:17:58 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA00799 for hackers-outgoing; Fri, 20 Sep 1996 13:17:58 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA00775 for ; Fri, 20 Sep 1996 13:17:54 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA02942; Fri, 20 Sep 1996 13:15:46 -0700 From: Terry Lambert Message-Id: <199609202015.NAA02942@phaeton.artisoft.com> Subject: Re: Plug and Play naivety To: smpatel@umiacs.umd.edu (Sujal Patel) Date: Fri, 20 Sep 1996 13:15:46 -0700 (MST) Cc: janus@freegate.net, hackers@FreeBSD.org In-Reply-To: from "Sujal Patel" at Sep 20, 96 02:14:14 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 > > 1. mail from Sujal notes that "if your motherboard supports PnP > > devices, then you don't need this code". What does this mean? > > I've been told that the BIOS on the machine I'm using has > > "Plug and Play" support ... does this mean it's possible that the > > BIOS has queried the ISA devices on boot and already has all the > > config info? Can I get at this somehow from the kernel? Or is this > > only referring to PCI kind of Plug and Play? > > The PnP-aware BIOS will configure all ISA PnP cards (to the best of it's > ability) during the boot up cycle. If the BIOS gets this wrong (which it > often does), you'll need to either use the PnP driver or turn if PnP (if > the device supports that option). This exchange implies that the kernel will not use the PnP information in the presence of a PnP BIOS to configure the drivers. Can you confirm or deny this? The benefit of the PnP code is not simply configuration of devices in the absence of a PnP BIOS, but also in the provision of hints to the device drivers. 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 Fri Sep 20 13:31:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA07055 for hackers-outgoing; Fri, 20 Sep 1996 13:31:34 -0700 (PDT) Received: from mickey.umiacs.umd.edu (12222@mickey.umiacs.umd.edu [128.8.120.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA07031 for ; Fri, 20 Sep 1996 13:31:31 -0700 (PDT) Received: (smpatel@localhost) by mickey.umiacs.umd.edu (8.7.6/UMIACS-0.9/04-05-88) id QAA09729; Fri, 20 Sep 1996 16:30:10 -0400 (EDT) Date: Fri, 20 Sep 1996 16:30:09 -0400 (EDT) From: Sujal Patel To: Terry Lambert cc: janus@freegate.net, hackers@FreeBSD.org Subject: Re: Plug and Play naivety In-Reply-To: <199609202015.NAA02942@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 20 Sep 1996, Terry Lambert wrote: > This exchange implies that the kernel will not use the PnP information > in the presence of a PnP BIOS to configure the drivers. Can you confirm > or deny this? > > The benefit of the PnP code is not simply configuration of devices in > the absence of a PnP BIOS, but also in the provision of hints to the > device drivers. The Plug & Play driver will eventually fill in isa_device structures for ISA devices properly. If you chose not to configure your PnP device, it will read the configuration that is already there (i.e. the BIOS setup configuration). You could further extend the model, by allowing the kernel to choose a device driver based on the information presented by the PnP aspect of the card (this is not planned for the first release). Sample code to read a cards configuration (as set by BIOS) is at: http://www.freebsd.org/~smpatel/pnpget.h http://www.freebsd.org/~smpatel/pnpget.cc The code is a bit incomplete, but works fine. Sujal From owner-freebsd-hackers Fri Sep 20 13:37:41 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA09349 for hackers-outgoing; Fri, 20 Sep 1996 13:37:41 -0700 (PDT) Received: from dfw-ix10.ix.netcom.com (dfw-ix10.ix.netcom.com [206.214.98.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA09320 for ; Fri, 20 Sep 1996 13:37:38 -0700 (PDT) Received: from randal (sjx-ca36-18.ix.netcom.com [204.31.236.178]) by dfw-ix10.ix.netcom.com (8.6.13/8.6.12) with ESMTP id NAA06611 for ; Fri, 20 Sep 1996 13:37:03 -0700 Message-Id: <199609202037.NAA06611@dfw-ix10.ix.netcom.com> From: "Randy Thelen" To: Subject: Willing to help Date: Fri, 20 Sep 1996 13:36:46 -0700 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 To whom it may concern -- I'd like to contribute my time and energy to the FreeBSD File System effort. I know a great deal about file systems and have seen a few of the items that need to fixed. Could you explain more about the following: 1) Fix the MSDOS file system. 2) Clean up and document the nullfs filesystem code. I've cc'd the Coordinator: Justin T. Gibbs, for more info. Thank you and I hope that I may be of some help. -- Randy Thelen From owner-freebsd-hackers Fri Sep 20 14:33:31 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA05465 for hackers-outgoing; Fri, 20 Sep 1996 14:33:31 -0700 (PDT) Received: (from hsu@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA05442; Fri, 20 Sep 1996 14:33:28 -0700 (PDT) Date: Fri, 20 Sep 1996 14:33:28 -0700 (PDT) From: Jeffrey Hsu Message-Id: <199609202133.OAA05442@freefall.freebsd.org> To: dubois@primate.wisc.edu Subject: Re: libc_r bug Cc: hackers Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > What happens, and what do you expect to happen? The first write gets lost. This is because the uthreads internal fd table is not set up for fds which are inherited from the parent process. I got around it with the following hack. This workaround is bad because it assumes that fd 0, 1, and 2 are valid upon start-up, which is generally but universally true. Alternatively, one could place a call to _thread_fd_table_init() in uthreads_write.c. Neither solution is very stisfactory. *** uthread_init.c 1996/08/20 08:21:23 1.3 --- uthread_init.c 1996/09/20 18:18:53 *************** *** 176,186 **** */ PANIC("Cannot allocate memory for file descriptor table"); } else { /* * Enter a loop to initialise the file descriptor * table: */ ! for (i = 0; i < _thread_dtablesize; i++) { /* Initialise the file descriptor table: */ _thread_fd_table[i] = NULL; } --- 176,189 ---- */ PANIC("Cannot allocate memory for file descriptor table"); } else { + _thread_fd_table_init(0); + _thread_fd_table_init(1); + _thread_fd_table_init(2); /* * Enter a loop to initialise the file descriptor * table: */ ! for (i = 2; i < _thread_dtablesize; i++) { /* Initialise the file descriptor table: */ _thread_fd_table[i] = NULL; From owner-freebsd-hackers Fri Sep 20 14:37:38 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA07374 for hackers-outgoing; Fri, 20 Sep 1996 14:37:38 -0700 (PDT) Received: from melb.werple.net.au (melb.werple.net.au [203.9.190.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA07349 for ; Fri, 20 Sep 1996 14:37:34 -0700 (PDT) Received: (from uucp@localhost) by melb.werple.net.au (8.7.6/8.7.3/2) with UUCP id GAA23407; Sat, 21 Sep 1996 06:59:19 +1000 (EST) Received: (from jb@localhost) by freebsd3.cimlogic.com.au (8.7.5/8.7.3) id SAA11336; Fri, 20 Sep 1996 18:33:56 +1000 (EST) From: John Birrell Message-Id: <199609200833.SAA11336@freebsd3.cimlogic.com.au> Subject: Re: libc_r and MIT pthreads To: jdrobina@infinet.com (James Drobina) Date: Fri, 20 Sep 1996 18:33:56 +1000 (EST) Cc: freebsd-hackers@FreeBSD.org In-Reply-To: from James Drobina at "Sep 17, 96 07:53:51 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 > > Is ther any chance of updating libc_r to use the lastest version of MIT > pthreads (pthreads-1_60_beta5)? Not much. There are too many functions in MIT pthreads-1_60 which clash with code in FreeBSD's libc. MIT pthreads was based on an early version of NetBSD. Compare the code... it's sufficiently different to make any merge impractical. Regards, -- John Birrell CIMlogic Pty Ltd jb@cimlogic.com.au 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 Fri Sep 20 15:33:09 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA02090 for hackers-outgoing; Fri, 20 Sep 1996 15:33:09 -0700 (PDT) Received: from central.picker.com (central.picker.com [144.54.31.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA02057 for ; Fri, 20 Sep 1996 15:33:04 -0700 (PDT) Received: from ct.picker.com by central.picker.com with smtp (Smail3.1.28.1 #3) id m0v4Drk-0004xOC; Fri, 20 Sep 96 18:16 EDT Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA13212; Fri, 20 Sep 96 18:14:25 EDT Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id SAA27475; Fri, 20 Sep 1996 18:08:14 -0400 From: rhh@ct.picker.com (Randall Hopper) Message-Id: <199609202208.SAA27475@elmer.ct.picker.com> Subject: Re: fdisk changes, anyone? To: darrylo@hpnmhjw.sr.hp.com (Darryl Okahata) Date: Fri, 20 Sep 1996 18:08:14 -0400 (EDT) Cc: hackers@freebsd.org In-Reply-To: <199609200653.AA284302404@hpnmhjw.sr.hp.com> from "Darryl Okahata" at Sep 19, 96 11:53:23 pm Reply-To: rhh@ct.picker.com Organization: Picker International, CT Division X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] 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 thought about having an fdisk config database (analogous to |/etc/disktab), but I don't think it'll work. I think people tend to use |disks in one of two ways: | |1. Dedicate the entire disk to FreeBSD. We don't need an fdisk config | database for this. | |2. Partition the disk up in "unusual" ways. Either an existing DOS | partition is present, or the user wants to partition the disk "his | way". The former can be handled without an fdisk config database | (just use the remainder as a FreeBSD partition), and there are too | many different possibilities in the latter. | |People with Zip or Jaz drives will probably dedicate the entire disk to |FreeBSD, and so a special fdisk config database probably isn't |necessary for these. With your changes, fdisk is going to be a much nicer tool to work with. As far as the fdisktab idea goes, I think your breakdown of usages certainly covers it, and I agree that 1. is probably the only one that could reasonably be covered by a config file. And there might not be enough demand out there right now for fdisking removable media for one large UFS partition to justify implementing it, so waiting to see sounds like a good idea. As for myself, my current make-ufs-zip script, which currently has in it this nasty mess: fdisk -u /dev/${DEVICE} << !EOF! n y 165 1 196576 y 0 1 1 95 63 32 y y 0 0 0 n y y 0 0 0 n y y 0 0 0 n y y 0 y y !EOF! (sed '/ /\n/' of course :-) along with a disklabel and newfs, will become something like: fdisk -u /dev/${DEVICE} -c - << !EOF! 165 1 196576 0 1 1 95 63 32 0 0 0 !EOF (much nicer). Though this isn't rocket science, I can see the benefit of having this in a config file for newbies that just want to be able to store files on a UFS ZIP disk and don't know or even want to know about how to set up what cylinders, heads, and sectors go into their UFS slice. But as they'll still want to build a script to pull the fdisk, disklabel, and newfs into one convenient "just do-it" command, its arguable and not much extra effort for them to just pull this script out of the mailing list archives. Randall Hopper rhh@ct.picker.com From owner-freebsd-hackers Fri Sep 20 16:18:35 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA18805 for hackers-outgoing; Fri, 20 Sep 1996 16:18:35 -0700 (PDT) Received: from w2xo.pgh.pa.us (w2xo.pgh.pa.us [206.210.70.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA18774 for ; Fri, 20 Sep 1996 16:18:31 -0700 (PDT) Received: (from durham@localhost) by w2xo.pgh.pa.us (8.6.12/8.6.9) id TAA13494; Fri, 20 Sep 1996 19:17:38 -0400 Date: Fri, 20 Sep 1996 19:17:37 -0400 (EDT) From: Jim Durham To: Stephen Hocking cc: root@w2xo.pgh.pa.us, freebsd-hackers@freebsd.org Subject: Re: auserver In-Reply-To: <199609200455.EAA26597@netfl15a.devetir.qld.gov.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 20 Sep 1996, Stephen Hocking wrote: > You need to set the AUDIOSERVER environment variable (this is assumimng you > have au running already) to something like localhost:0 or use the -audio > option (e.g. "auedit -audio tcp/localhost:8000 foo.wav") > > Stephen > I should have mentioned that I did set it, but not with the magic invocation you mention. I did get it to run some clients with the -audio option using my entire host/domain name:8000. Thanks, I'll pursue it... -Jim Durham From owner-freebsd-hackers Fri Sep 20 16:37:27 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA01269 for hackers-outgoing; Fri, 20 Sep 1996 16:37:27 -0700 (PDT) Received: from melb.werple.net.au (melb.werple.net.au [203.9.190.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA01231 for ; Fri, 20 Sep 1996 16:37:23 -0700 (PDT) Received: (from uucp@localhost) by melb.werple.net.au (8.7.6/8.7.3/2) with UUCP id IAA25413; Sat, 21 Sep 1996 08:58:23 +1000 (EST) Received: (from jb@localhost) by freebsd3.cimlogic.com.au (8.7.5/8.7.3) id IAA13922; Sat, 21 Sep 1996 08:20:51 +1000 (EST) From: John Birrell Message-Id: <199609202220.IAA13922@freebsd3.cimlogic.com.au> Subject: Re: libc_r bug To: hsu@freefall.freebsd.org (Jeffrey Hsu) Date: Sat, 21 Sep 1996 08:20:51 +1000 (EST) Cc: hackers@FreeBSD.org, jb@cimlogic.com.au In-Reply-To: <199609200828.BAA01366@freefall.freebsd.org> from Jeffrey Hsu at "Sep 20, 96 01:28:29 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 > The following program exhibits a bug in the latest version of libc_r. > If the two lines are reversed, then everything's okay. > > main() > { > write(1, "hi", 2); > printf("hello world\n"); > } > I see. I assume write() is returning errno = EBADF. Try adding... _thread_fd_table_init(0); _thread_fd_table_init(1); _thread_fd_table_init(2); to _thread_init() [in uthread_init.c] after the loop that sets _thread_fd_table[i] to NULL. Regards, -- John Birrell CIMlogic Pty Ltd jb@cimlogic.com.au 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 Fri Sep 20 17:14:59 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA25109 for hackers-outgoing; Fri, 20 Sep 1996 17:14:59 -0700 (PDT) Received: from research.gate.nec.co.jp (research.gate.nec.co.jp [202.32.8.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA25077 for ; Fri, 20 Sep 1996 17:14:55 -0700 (PDT) Received: from sbl-gw.sbl.cl.nec.co.jp by research.gate.nec.co.jp (8.7.6+2.6Wbeta7/950912) with ESMTP id JAA06230; Sat, 21 Sep 1996 09:14:48 +0900 (JST) Received: from sirius.sbl.cl.nec.co.jp by sbl-gw.sbl.cl.nec.co.jp (8.7.5+2.6Wbeta6/3.3W6) with ESMTP id JAA08270; Sat, 21 Sep 1996 09:14:46 +0900 (JST) X-Authentication-Warning: sbl-gw.sbl.cl.nec.co.jp: Host nao@sirius [133.207.68.90] claimed to be sirius.sbl.cl.nec.co.jp Received: by sirius.sbl.cl.nec.co.jp (8.7.5+2.6Wbeta6/3.3W6) with UUCP id JAA24315; Sat, 21 Sep 1996 09:14:46 +0900 (JST) Date: Sat, 21 Sep 1996 09:14:46 +0900 (JST) From: Naoki Hamada Message-Id: <199609210014.JAA24315@sirius.sbl.cl.nec.co.jp> References: <199609201503.RAA25073@spooky.lss.cp.philips.com> To: Guido.vanRooij@nl.cis.philips.com CC: guido@gvr.win.tue.nl, dfr@render.com, freebsd-hackers@FreeBSD.org In-reply-to: Guido van Rooij's message of "Fri, 20 Sep 1996 17:03:51 +0200 (MET DST)" <199609201503.RAA25073@spooky.lss.cp.philips.com> Subject: Re: new if_vx driver on freefall Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Guido wrote: >I ordered the specs from 3com and I'm waiting for them. Basically,if your board >runs fine without BROKEN_AVAIL, do *not* define it. Absolutely. >If it stops for your firends, could you verfiy with ifconfig vx0 that >the state is OACTIVE? Sure. And here is another report from Kumagai-san. -nao ============================================================ Dear Guido-san, Due to Nao-san(Naoki Hamada )'s prompt introducing of your fantastic vx driver: ftp://freefall.freebsd.org/incoming/newif_vx.tgz to Japanese FreeBSD community, I am pleased to report its successful operation on my Gateway machine. In summary: * after some modification of if_vx.c, its compilation turns to success. * my vx0 operates successfully. * after #undef'ed BROKEN_AVAIL and "ping -f -s 1000 ....", it successfully operates 1) Environment Machine:Gateway P5-166 Multimedia Intel 166MHz-Pentium, 32MB EDO DRAM 430HX Chipset AHA 2940, 3c589 OS: FreeBSD 2.1.5-RELEASE Please consult the attached 'dmesg' log if you'd like to examine my machine in detail. 2) Step-by-Step Report 2.1 Extract and Compile * extraction: OK (tar xvfz newif_vx.tgz) * put both (if_vx.c and if_vxreg.h) to /sys/pci. * make depend: OK * make: NG...OOPS! ================================================== cc -c -O -W -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -nostdinc -I. -I../.. -I../../sys -I/usr/include -DLUTE -DI586_CPU -DI486_CPU -DI386_CPU -DATAPI -DSYSVMSG -DSYSVSEM -DSYSVSHM -DUCONSOLE -DBOUNCE_BUFFERS -DSCSI_DELAY=5 -DCOMPAT_43 -DPROCFS -DCD9660 -DMSDOSFS -DNFS -DFFS -DINET -DVX_LOCAL_STATS -DKERNEL -Di386 -DLOAD_ADDRESS=0xF0100000 ../../pci/if_vx.c ../../pci/if_vx.c: In function `vxstart': ../../pci/if_vx.c:432: `s' undeclared (first use this function) ../../pci/if_vx.c:432: (Each undeclared identifier is reported only once ../../pci/if_vx.c:432: for each function it appears in.) *** Error code 1 Stop. ================================================== After some consideration, I decided to change if_vx.c according to the following patch: ============================================================ *** 429,435 **** goto readcheck; } ! if ((s=inw(BASE + VX_W1_FREE_TX)) < len + pad + 4) { outw(BASE + VX_COMMAND, SET_TX_AVAIL_THRESH | (len + pad + 4)); /* not enough room in FIFO */ #ifdef BROKEN_AVAIL --- 429,435 ---- goto readcheck; } ! if ((sh=inw(BASE + VX_W1_FREE_TX)) < len + pad + 4) { outw(BASE + VX_COMMAND, SET_TX_AVAIL_THRESH | (len + pad + 4)); /* not enough room in FIFO */ #ifdef BROKEN_AVAIL ============================================================ This change has caused to compile it successfully. 2.2 Reboot and try ftp * Reboot OK: the kernel recognise vx. vx0 <3Com 3c595 Fast EtherLink III PCI> rev 0 int a irq 9 on pci0:15 utp[*UTP*] address 0:a0:24:bb:a2:21 I specifies 'link2' flag in /etc/sysconfig for vx0. * try ftp: Great! get /kernel /dev/null ... Approx. 800KB/sec put /kernel /dev/null ... Approx. 800KB/sec 2.3 Be #undef'ed BROKEN_AVAIL and try ping. * undef BROKEN_AVAIL * make: OK * reboot: OK * execute: ping -f -s 1000 bell ... OK * terminate with SIGING, and * try ftp: Great! get /kernel /dev/null ... Approx. 800KB/sec put /kernel /dev/null ... Approx. 800KB/sec So my next mission is to get Accelarator-X to construct the X-Empire of Millenium in my Gateway. Many thanks. Norihiro Kumagai (kuma@slab.tnr.sharp.co.jp) ============================================================ (Appendix: my dmesg log) FreeBSD 2.1.5-RELEASE #4: Fri Sep 20 12:40:25 1996 root@lute.slab.tnr.sharp.co.jp:/usr/src/sys/compile/LUTE CPU: 166-MHz Pentium 735\\90 or 815\\100 (Pentium-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 33554432 (32768K bytes) avail memory = 30760960 (30040K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 2 on pci0:7:0 chip2 rev 2 on pci0:7:1 ahc0 rev 0 int a irq 10 on pci0:14 ahc0: aic7870 Single Channel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle vx0 <3Com 3c595 Fast EtherLink III PCI> rev 0 int a irq 9 on pci0:15 utp[*UTP*] address 0:a0:24:bb:a2:21 vga0 rev 1 int a irq 11 on pci0:16 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 not found at 0x2f8 lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0: disabled, not probed. fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff80ff on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (atapi): , removable, intr, dma, iordy wcd0: 1377Kb/sec, 256Kb cache, audio play, 255 volume levels, ejectable tray wcd0: no disc inside, unlocked wdc1 not found at 0x170 ep0 not found at 0x300 npx0 on motherboard npx0: INT 16 interface ============================================================ From owner-freebsd-hackers Fri Sep 20 17:30:48 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA04303 for hackers-outgoing; Fri, 20 Sep 1996 17:30:48 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA04257 for ; Fri, 20 Sep 1996 17:30:41 -0700 (PDT) Received: from schizo.cdsnet.net by mail.crl.com with SMTP id AA25684 (5.65c/IDA-1.5 for ); Fri, 20 Sep 1996 17:31:12 -0700 Received: (from mrcpu@localhost) by schizo.cdsnet.net (8.7.5/8.7.3) id RAA06899; Fri, 20 Sep 1996 17:27:58 -0700 (PDT) Date: Fri, 20 Sep 1996 17:27:58 -0700 (PDT) From: Jaye Mathisen Message-Id: <199609210027.RAA06899@schizo.cdsnet.net> To: hackers@freebsd.org X-Also-Posted-To: comp.lang.perl.misc Subject: Hmmm, command-line vs CGI execution of perl 5.003 app and FreeBSD. Organization: CDS Internet Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk OK, stumper time. Perl 5.003, FreeBSD 2.2-current, Apache 1.1.1 with xssi,php/fi, and Netscape Server 1.0. Under Netscape 1.1 server, I have a perl CGI script that runs fine. I take the same script on the same box and run it under Apache, and I get "Premature end of Script Headers". So I go through the script with use strict, and -w, and no errors. I tried $|=1, and various incarnations of "select" to see if it was an unbuffered output problem, but to no avail. If I run the script from the command line, the generated output looks just peachy, and other than stripping off the initial Content-type: text/html\n\n mumbo-jumbo, when put in a .html file, displays fine. running the script with redirected stdout/stderr shows no output on anything other than stdout. So I muck around in the util-script.c file for apache and throw in some debugging, and add the following after the log message for the error message: fprintf(stderr,"w -> %s, *f -> %s, feof= %d, ferror = %d, fileno = % d\n",w,f,feof(f), ferror(f), fileno(f)); (Ignoring my braindamage for *f, but I didn't feel like re-compiling for the example) And lo and behold: w -> , *f -> , feof= 1, ferror = 0, fileno = 9 So it looks as if somehow the fd's are getting munged? The question, is this a perl/Apache interaction problem? Is there something in Perl I should be doing to make this work properly? This is the same box that had op/exec failing in the perl test, and I notice that perl 5.003_002 won't Configure on it, it fails in Configure with a problem with file descriptor 4. The script has a little database stuff, but none of those modules generate any output. Been doing all the scripting with the Netscape server, and never had this problem other than throwing the $|=1 at the top of every script. I'm starting to think it's a FreeBSD problem, but thought I'd hit the experts first. From owner-freebsd-hackers Fri Sep 20 17:32:50 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA05404 for hackers-outgoing; Fri, 20 Sep 1996 17:32:50 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA05387 for ; Fri, 20 Sep 1996 17:32:48 -0700 (PDT) Received: from schizo.cdsnet.net by mail.crl.com with SMTP id AA25955 (5.65c/IDA-1.5 for ); Fri, 20 Sep 1996 17:33:18 -0700 Received: (from mrcpu@localhost) by schizo.cdsnet.net (8.7.5/8.7.3) id RAA06931; Fri, 20 Sep 1996 17:30:15 -0700 (PDT) Date: Fri, 20 Sep 1996 17:30:15 -0700 (PDT) From: Jaye Mathisen Message-Id: <199609210030.RAA06931@schizo.cdsnet.net> To: hackers@freebsd.org X-Also-Posted-To: comp.lang.perl.misc Subject: Hmmm, command-line vs CGI execution of perl 5.003 app and FreeBSD. Organization: CDS Internet Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk OK, stumper time. Perl 5.003, FreeBSD 2.2-current, Apache 1.1.1 with xssi,php/fi, and Netscape Server 1.0. Under Netscape 1.1 server, I have a perl CGI script that runs fine. I take the same script on the same box and run it under Apache, and I get "Premature end of Script Headers". So I go through the script with use strict, and -w, and no errors. I tried $|=1, and various incarnations of "select" to see if it was an unbuffered output problem, but to no avail. If I run the script from the command line, the generated output looks just peachy, and other than stripping off the initial Content-type: text/html\n\n mumbo-jumbo, when put in a .html file, displays fine. running the script with redirected stdout/stderr shows no output on anything other than stdout. So I muck around in the util-script.c file for apache and throw in some debugging, and add the following after the log message for the error message: fprintf(stderr,"w -> %s, *f -> %s, feof= %d, ferror = %d, fileno = % d\n",w,f,feof(f), ferror(f), fileno(f)); (Ignoring my braindamage for *f, but I didn't feel like re-compiling for the example) And lo and behold: w -> , *f -> , feof= 1, ferror = 0, fileno = 9 So it looks as if somehow the fd's are getting munged? The question, is this a perl/Apache interaction problem? Is there something in Perl I should be doing to make this work properly? This is the same box that had op/exec failing in the perl test, and I notice that perl 5.003_002 won't Configure on it, it fails in Configure with a problem with file descriptor 4. The script has a little database stuff, but none of those modules generate any output. Been doing all the scripting with the Netscape server, and never had this problem other than throwing the $|=1 at the top of every script. I'm starting to think it's a FreeBSD problem, but thought I'd hit the experts first. From owner-freebsd-hackers Fri Sep 20 17:42:38 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA11162 for hackers-outgoing; Fri, 20 Sep 1996 17:42:38 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA11141 for ; Fri, 20 Sep 1996 17:42:36 -0700 (PDT) Received: from schizo.cdsnet.net by mail.crl.com with SMTP id AA28040 (5.65c/IDA-1.5 for ); Fri, 20 Sep 1996 17:42:58 -0700 Received: (from mrcpu@localhost) by schizo.cdsnet.net (8.7.5/8.7.3) id RAA06952; Fri, 20 Sep 1996 17:39:37 -0700 (PDT) Date: Fri, 20 Sep 1996 17:39:37 -0700 (PDT) From: Jaye Mathisen Message-Id: <199609210039.RAA06952@schizo.cdsnet.net> To: hackers@freebsd.org X-Also-Posted-To: comp.lang.perl.misc Subject: Hmmm, command-line vs CGI execution of perl 5.003 app and FreeBSD. Organization: CDS Internet Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk OK, stumper time. Perl 5.003, FreeBSD 2.2-current, Apache 1.1.1 with xssi,php/fi, and Netscape Server 1.0. Under Netscape 1.1 server, I have a perl CGI script that runs fine. I take the same script on the same box and run it under Apache, and I get "Premature end of Script Headers". So I go through the script with use strict, and -w, and no errors. I tried $|=1, and various incarnations of "select" to see if it was an unbuffered output problem, but to no avail. If I run the script from the command line, the generated output looks just peachy, and other than stripping off the initial Content-type: text/html\n\n mumbo-jumbo, when put in a .html file, displays fine. running the script with redirected stdout/stderr shows no output on anything other than stdout. So I muck around in the util-script.c file for apache and throw in some debugging, and add the following after the log message for the error message: fprintf(stderr,"w -> %s, *f -> %s, feof= %d, ferror = %d, fileno = % d\n",w,f,feof(f), ferror(f), fileno(f)); (Ignoring my braindamage for *f, but I didn't feel like re-compiling for the example) And lo and behold: w -> , *f -> , feof= 1, ferror = 0, fileno = 9 So it looks as if somehow the fd's are getting munged? The question, is this a perl/Apache interaction problem? Is there something in Perl I should be doing to make this work properly? This is the same box that had op/exec failing in the perl test, and I notice that perl 5.003_002 won't Configure on it, it fails in Configure with a problem with file descriptor 4. The script has a little database stuff, but none of those modules generate any output. Been doing all the scripting with the Netscape server, and never had this problem other than throwing the $|=1 at the top of every script. I'm starting to think it's a FreeBSD problem, but thought I'd hit the experts first. From owner-freebsd-hackers Fri Sep 20 17:51:04 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA16876 for hackers-outgoing; Fri, 20 Sep 1996 17:51:04 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA16851 for ; Fri, 20 Sep 1996 17:51:02 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id RAA06198; Fri, 20 Sep 1996 17:49:45 -0700 (PDT) Message-Id: <199609210049.RAA06198@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: Terry Lambert cc: smpatel@umiacs.umd.edu (Sujal Patel), janus@freegate.net, hackers@FreeBSD.org Subject: USB + Re: Plug and Play naivety In-reply-to: Your message of "Fri, 20 Sep 1996 13:15:46 PDT." <199609202015.NAA02942@phaeton.artisoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Sep 1996 17:49:45 -0700 From: Amancio Hasty Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >From The Desk Of Terry Lambert : > > > 1. mail from Sujal notes that "if your motherboard supports PnP > > > devices, then you don't need this code". What does this mean? > > > I've been told that the BIOS on the machine I'm using has > > > "Plug and Play" support ... does this mean it's possible that the > > > BIOS has queried the ISA devices on boot and already has all the > > > config info? Can I get at this somehow from the kernel? Or is this > > > only referring to PCI kind of Plug and Play? > > > > The PnP-aware BIOS will configure all ISA PnP cards (to the best of it's > > ability) during the boot up cycle. If the BIOS gets this wrong (which it > > often does), you'll need to either use the PnP driver or turn if PnP (if > > the device supports that option). > > This exchange implies that the kernel will not use the PnP information > in the presence of a PnP BIOS to configure the drivers. Can you confirm > or deny this? Yes, I can confirm that the GUS PnP works with BIOS hints or with hardcoded values in the kernel config file. Additionally, the GUS PnP fills in the isa data structures so the rest of the kernel knows what the card got set to. Since we are discussing PnP and thats good 8) what about support for USB devices?? Enjoy, Amancio From owner-freebsd-hackers Fri Sep 20 17:54:49 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA19038 for hackers-outgoing; Fri, 20 Sep 1996 17:54:49 -0700 (PDT) Received: from mickey.umiacs.umd.edu (12222@mickey.umiacs.umd.edu [128.8.120.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA19021 for ; Fri, 20 Sep 1996 17:54:47 -0700 (PDT) Received: (smpatel@localhost) by mickey.umiacs.umd.edu (8.7.6/UMIACS-0.9/04-05-88) id UAA15582; Fri, 20 Sep 1996 20:54:43 -0400 (EDT) Date: Fri, 20 Sep 1996 20:54:42 -0400 (EDT) From: Sujal Patel To: Amancio Hasty cc: Terry Lambert , janus@freegate.net, hackers@FreeBSD.org Subject: Re: USB + Re: Plug and Play naivety In-Reply-To: <199609210049.RAA06198@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 20 Sep 1996, Amancio Hasty wrote: > Yes, I can confirm that the GUS PnP works with BIOS hints or with hardcoded > values in the kernel config file. Additionally, the GUS PnP fills in the > isa data structures so the rest of the kernel knows what the card > got set to. This is indeed how the PnP driver is evolving (but it's more generic then just one card). The only problem will be that people without any PnP bios support, will have to specify *all* of the parameters that a PnP devices needs (this can become quite ugly for the user, especially if all they have a a config line in the kernel config). It would be nice to have an easy configuration utility wouldn't it? Volunteers? :-) > Since we are discussing PnP and thats good 8) what about support > for USB devices?? That's no my department, I know nothing about USB devices... Terry? :-) ujal From owner-freebsd-hackers Fri Sep 20 18:32:57 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA13873 for hackers-outgoing; Fri, 20 Sep 1996 18:32:57 -0700 (PDT) Received: from hub.empac.com (hub.empac.com [206.25.128.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA13854 for ; Fri, 20 Sep 1996 18:32:54 -0700 (PDT) Received: from salmon.empac.com by hub.empac.com (8.6.12/8.6.10) id SAA05199; Fri, 20 Sep 1996 18:32:24 -0700 Received: from salmon.empac.com (rheaton@localhost.Berkeley.EDU [127.0.0.1]) by salmon.empac.com (8.7.3/8.7.3) with ESMTP id SAA02949 for ; Fri, 20 Sep 1996 18:43:25 -0700 (PDT) Message-Id: <199609210143.SAA02949@salmon.empac.com> X-Mailer: exmh version 1.6.5 12/8/95 To: hackers@freebsd.org From: "Richard Heaton" X-Org: EMPaC International Corp. X-Snail: 47490 Seabridge Dr., Fremont CA. 94538 X-url: http://www.empac.com/ Subject: Job openings: Unix Network Programmers, Internet server Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Sep 1996 18:43:25 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Candidate Profile: Mid to Senior -level Software Engineer Minimum Qualifications: --4+ years in industry. --Design experience with medium to large -scale software projects as an architect or designer. --Team-leadership experience. --Unix programming experience. --Knowledge of Computer Communications Systems, including TCP/IP, PPP, serial-line communications, HTTP --C/C++ programming. --BS in CS or EE. Desired: --Unix/Network Security (Firewalls, IP filtering, Proxies) --Familiarity with WWW, CGI Programming concepts,HTML --Unix system-administration knowledge. --Unix kernel development/configuration. --Familiarity with Perl, shell scripting --Device driver development --MS in EE or CS. Candidate Profile: Junior Entry-level Software Engineer Minimum Qualifications: --0+ experience in industry. --BS in CS or EE. --C/C++ Programming in a Unix environment. --Familiarity with Software Engineering Concepts, such as the software life-cycle and design methodologies, testing principles and techniques. --Familiarity with Software Configuration Management, such as CVS, RCS, make. Desired Qulifications: --Knowledge or Perl, HTML, CGI, shell scripting --Understanding of Unix System-administration --Knowledge of computer communications, such as TCP/IP, PPP, serial communications. --Experience with User-interface design Common Attributes for all candidates: --Team-oriented approach. --Willingness to learn. --Strong "Engineering" attitude: desire to know how/why things work, considers engineering and computers to be hobby as well as career, strongly self-motivated to learn more about own field and computers/engineering in general. =============================================================================== Job Descriptions: Mid to Senior level Software Engineer: This candidate will become an integral part of a team developing a Unix-platform Internet Server system. The job responsibilites for this candidate will include, but not be limited to: --Porting existing product from current BSDI platform to FreeBSD. --Re-design of system for next-generation of product --Unix kernel configuration --Possible device driver development --User Interface design --PPP development --Security system implementation Junior Level Software Engineer: This candidate will have the oportunity to contribute to the design process of the next-generation products and have a major impact on the direction and features of an Internet Server system. Additionally, this candidate will be responsible for helping with the following: -- maintaining and upgrading existing software -- User-interface design of HTML Management system -- software configuration management, including version control, build management -- development and implementation of software testing procedures =============================================================================== Empac International is a small Silicon Valley company that started as a PC manufacturer in the early 1980's. In 1993, Empac entered the internet busisness by developing a fractional T1 router. In early 1995, Empac began developing an Internet/Intranet Server product based on an HTML-managment interface paradigm. That product began selling in late 1995 as an ISP platform. Later in 1995 , a small-office connectivity version was released. The product is now entering its second generation, wherein a refinement of the functionality and features of the earlier versions is taking place. The Internet/Intranet OS product provides the customer with Web Server, Email, FTP, and DNS capability through either dialup (modem or ISDN TA) or router -based connectivity. The customer manages and configures the entire server through the use of an HTML/CGI interface, thereby insulating the user from the underlying UNIX operating system. Empac is looking for qualified candidates to help re-design and re-architecture this product. This presents prospective engineers with a unique opportunity to have a major impact on the design and implementation of a product with a proven market and direction. Ideal candidates will have UNIX Network programming experience, a solid Software Design background and substantial network security knowledge. Desirable qualifications also include experience/familiarity with system-administration and Web/CGI programming and experience with FreeBSD. Candidates should also be prepared to work in a strongly team-oriented atmosphere with a reasonably flat hierarchical structure. Interested candidates should forward their resume to : Human Resources Empac International Corp., 47490 Seabridge Dr., Fremont, CA 94538 Tel: (510)683-8800 or Fax: (510)683-8662 or email: rheaton@empac.com From owner-freebsd-hackers Fri Sep 20 18:37:27 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA16557 for hackers-outgoing; Fri, 20 Sep 1996 18:37:27 -0700 (PDT) Received: from melb.werple.net.au (melb.werple.net.au [203.9.190.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA16528 for ; Fri, 20 Sep 1996 18:37:24 -0700 (PDT) Received: (from uucp@localhost) by melb.werple.net.au (8.7.6/8.7.3/2) with UUCP id KAA28219; Sat, 21 Sep 1996 10:58:29 +1000 (EST) Received: (from jb@localhost) by freebsd3.cimlogic.com.au (8.7.5/8.7.3) id JAA14006; Sat, 21 Sep 1996 09:12:24 +1000 (EST) From: John Birrell Message-Id: <199609202312.JAA14006@freebsd3.cimlogic.com.au> Subject: Re: libc_r bug To: hsu@freefall.freebsd.org (Jeffrey Hsu) Date: Sat, 21 Sep 1996 09:12:23 +1000 (EST) Cc: hackers@FreeBSD.org, jb@cimlogic.com.au In-Reply-To: <199609202133.OAA05442@freefall.freebsd.org> from Jeffrey Hsu at "Sep 20, 96 02:33:28 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 > > What happens, and what do you expect to happen? > > The first write gets lost. This is because the uthreads internal > fd table is not set up for fds which are inherited from the parent > process. I got around it with the following hack. This workaround > is bad because it assumes that fd 0, 1, and 2 are valid upon > start-up, which is generally but universally true. Alternatively, The workaround is "the fix" (provided that the calls to _thread_fd_table_init are _after_ the initialisation loop). _thread_fd_table_init() just sets up the table for a fd. fds 0, 1 and 2 don't have to be valid. > one could place a call to _thread_fd_table_init() in uthreads_write.c. > Neither solution is very stisfactory. > > *** uthread_init.c 1996/08/20 08:21:23 1.3 > --- uthread_init.c 1996/09/20 18:18:53 > *************** > *** 176,186 **** > */ > PANIC("Cannot allocate memory for file descriptor table"); > } else { > /* > * Enter a loop to initialise the file descriptor > * table: > */ > ! for (i = 0; i < _thread_dtablesize; i++) { > /* Initialise the file descriptor table: */ > _thread_fd_table[i] = NULL; > } > --- 176,189 ---- > */ > PANIC("Cannot allocate memory for file descriptor table"); > } else { > + _thread_fd_table_init(0); > + _thread_fd_table_init(1); > + _thread_fd_table_init(2); > /* > * Enter a loop to initialise the file descriptor > * table: > */ > ! for (i = 2; i < _thread_dtablesize; i++) { > /* Initialise the file descriptor table: */ > _thread_fd_table[i] = NULL; > Leave the loop starting at i = 0 so that _thread_fd_table_init(0) etc can check if memory has been allocated, then put the _thread_fd_table_init calls after the loop. Regards, -- John Birrell CIMlogic Pty Ltd jb@cimlogic.com.au 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 Fri Sep 20 18:41:20 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA18952 for hackers-outgoing; Fri, 20 Sep 1996 18:41:20 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA18915 for ; Fri, 20 Sep 1996 18:41:15 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id SAA22768 for ; Fri, 20 Sep 1996 18:40:44 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma022766; Fri Sep 20 18:40:32 1996 Received: (from archie@localhost) by bubba.whistle.com (8.7.5/8.6.12) id SAA00357 for freebsd-hackers@freebsd.org; Fri, 20 Sep 1996 18:40:31 -0700 (PDT) From: Archie Cobbs Message-Id: <199609210140.SAA00357@bubba.whistle.com> Subject: xcdplayer SCSI bus hang To: freebsd-hackers@freebsd.org Date: Fri, 20 Sep 1996 18:40:31 -0700 (PDT) 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 Doing anything non-trivial with "xcdplayer", like pressing the "pause" button, causes what looks like a SCSI bus hang. The SCSI bus LED is lit and the box completely locks up. This bug has been around since before 2.1 was released, on this machine, anyway. Does this happen to anyone else? If not, it's probably because of a bogus CD-ROM drive. Anyone know any more? Thanks, -Archie Equipment: Buslogic 946 SCSI host adapter CHINON CD-ROM CDS-535 Q20 FreeBSD 2.2-960801-SNAP dmesg: FreeBSD 2.2-960801-SNAP #0: Sun Sep 8 14:46:44 PDT 1996 root@bubba.whistle.com:/usr/src/sys/compile/BUBBAB Calibrating clock(s) relative to mc146818A clock... i586 clock: 99467504 Hz, i8254 clock: 1193109 Hz CPU: Pentium (99.46-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x1bf real memory = 16777216 (16384K bytes) avail memory = 14561280 (14220K bytes) DEVFS: ready for devices Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 2 on pci0:7:0 piix0 rev 2 on pci0:7:1 vga0 rev 0 int a irq 10 on pci0:10 bt0 rev 0 int a irq 11 on pci0:12 bt0: Bt946C/ 0-(32bit) bus bt0: reading board settings, busmastering, int=11 bt0: version 4.25J, fast sync, parity, 32 mbxs, 32 ccbs bt0: targ 0 sync rate=10.00MB/s(100ns), offset=08 bt0: Using Strict Round robin scheme (bt0:0:0): "QUANTUM FIREBALL1080S 1Q09" type 0 fixed SCSI 2 sd0(bt0:0:0): Direct-Access 1042MB (2134305 512 byte sectors) (bt0:4:0): "CHINON CD-ROM CDS-535 Q20" type 5 removable SCSI 2 cd0(bt0:4:0): CD-ROM cd present [323232 x 2048 byte records] Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed1 at 0x300-0x31f irq 9 on isa ed1: address 00:00:b4:6f:c3:11, type NE2000 (16 bit) sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2 at 0x3e8-0x3ef irq 5 on isa sio2: type 16550A qcam0 not found at 0x3bc wdc0: disabled, not probed. fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in npx0 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 7 drq 1 on isa sb0: DEVFS: ready to run IP packet filtering initialized, divert enabled, logging limited to 100 packets/entry ___________________________________________________________________________ Archie L. Cobbs, archie@whistle.com * Whistle Communications Corporation From owner-freebsd-hackers Fri Sep 20 19:28:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA14012 for hackers-outgoing; Fri, 20 Sep 1996 19:28:34 -0700 (PDT) Received: (from hsu@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA13995; Fri, 20 Sep 1996 19:28:31 -0700 (PDT) Date: Fri, 20 Sep 1996 19:28:31 -0700 (PDT) From: Jeffrey Hsu Message-Id: <199609210228.TAA13995@freefall.freebsd.org> To: jb@cimlogic.com.au Subject: Re: libc_r bug Cc: hackers Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk That takes care of fd 0, 1, and 2. But how do you tell if the parent process has set up another fd, say, 3, for use by the child? From owner-freebsd-hackers Fri Sep 20 19:29:33 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA14384 for hackers-outgoing; Fri, 20 Sep 1996 19:29:33 -0700 (PDT) Received: from Mail.IDT.NET (mail.idt.net [198.4.75.205]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA14339 for ; Fri, 20 Sep 1996 19:29:27 -0700 (PDT) Received: from sequoia (ppp-12.ts-1.mlb.idt.net [169.132.71.12]) by Mail.IDT.NET (8.7.4/8.7.3) with SMTP id WAA13176; Fri, 20 Sep 1996 22:29:11 -0400 (EDT) Message-ID: <32435339.15C2@mail.idt.net> Date: Fri, 20 Sep 1996 22:30:17 -0400 From: Gary Corcoran Reply-To: garycorc@mail.idt.net X-Mailer: Mozilla 3.0 (WinNT; U) MIME-Version: 1.0 To: Sujal Patel CC: janus@freegate.net, hackers@FreeBSD.org Subject: Re: Plug and Play naivety References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Sujal Patel wrote: > > On Fri, 20 Sep 1996, Terry Lambert wrote: > > > This exchange implies that the kernel will not use the PnP information > > in the presence of a PnP BIOS to configure the drivers. Can you confirm > > or deny this? > > > > The benefit of the PnP code is not simply configuration of devices in > > the absence of a PnP BIOS, but also in the provision of hints to the > > device drivers. > > The Plug & Play driver will eventually fill in isa_device structures for > ISA devices properly. If you chose not to configure your PnP device, it > will read the configuration that is already there (i.e. the BIOS setup > configuration). > > You could further extend the model, by allowing the kernel to choose a > device driver based on the information presented by the PnP aspect of the > card (this is not planned for the first release). > Is the (eventual) plan for the PnP code to allow kernel-config-specified values to override those programmed by a PnP BIOS? This would be desirable to allow for fixing things when the BIOS botches its automatic assignments (and/or I just want to specify, for example, my own priorities for IRQs). Gary From owner-freebsd-hackers Fri Sep 20 19:46:06 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA21262 for hackers-outgoing; Fri, 20 Sep 1996 19:46:06 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA21241 for ; Fri, 20 Sep 1996 19:46:03 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id TAA21087; Fri, 20 Sep 1996 19:46:07 -0700 (PDT) To: hackers@freebsd.org cc: "Richard Heaton" Subject: Re: Job openings: Unix Network Programmers, Internet server In-reply-to: Your message of "Fri, 20 Sep 1996 18:43:25 PDT." <199609210143.SAA02949@salmon.empac.com> Date: Fri, 20 Sep 1996 19:46:07 -0700 Message-ID: <21084.843273967@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ... And lest anyone be tempted to flame Richard for what they deem an "inappropriate posting," I just wanted to say that FreeBSD related job postings definitely constitute reasonable use, especially if they result in someone actually being paid to improve some part of FreeBSD. Jordan From owner-freebsd-hackers Fri Sep 20 20:20:29 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA07049 for hackers-outgoing; Fri, 20 Sep 1996 20:20:29 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA07014 for ; Fri, 20 Sep 1996 20:20:24 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.6/CET-v2.1) with SMTP id DAA29981; Sat, 21 Sep 1996 03:20:15 GMT Date: Sat, 21 Sep 1996 12:20:15 +0900 (JST) From: Michael Hancock To: Randy Thelen cc: FreeBSD-hackers@freefall.freebsd.org Subject: Re: Willing to help In-Reply-To: <199609202037.NAA06611@dfw-ix10.ix.netcom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 20 Sep 1996, Randy Thelen wrote: > To whom it may concern -- > I'd like to contribute my time and energy to the FreeBSD File System > effort. I know a great deal about file systems and have seen a few of the > items that need to fixed. Could you explain more about the following: > > 1) Fix the MSDOS file system. I think Robert Nordier is working on this. > 2) Clean up and document the nullfs filesystem code. I've cc'd the > Coordinator: Justin T. Gibbs, for more info. You probably should wait until lite2 is merged in. > Thank you and I hope that I may be of some help. > > -- Randy Thelen > From owner-freebsd-hackers Fri Sep 20 20:37:59 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA15652 for hackers-outgoing; Fri, 20 Sep 1996 20:37:59 -0700 (PDT) Received: from hp.com (hp.com [15.255.152.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA15625 for ; Fri, 20 Sep 1996 20:37:56 -0700 (PDT) Received: from srmail.sr.hp.com by hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA255387072; Fri, 20 Sep 1996 20:37:52 -0700 Received: from hpnmhjw.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA110087071; Fri, 20 Sep 1996 20:37:52 -0700 Received: from mina.sr.hp.com by hpnmhjw.sr.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA000537071; Fri, 20 Sep 1996 20:37:51 -0700 Message-Id: <199609210337.AA000537071@hpnmhjw.sr.hp.com> To: rhh@ct.picker.com Cc: hackers@freebsd.org Subject: Re: fdisk changes, anyone? In-Reply-To: Your message of "Fri, 20 Sep 1996 18:08:14 EDT." <199609202208.SAA27475@elmer.ct.picker.com> Date: Fri, 20 Sep 1996 20:37:49 -0700 From: Darryl Okahata Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > As for myself, my current make-ufs-zip script, which currently has in > it this nasty mess: > > fdisk -u /dev/${DEVICE} << !EOF! > n y 165 1 196576 y 0 1 1 95 63 32 y y 0 0 0 n y y 0 0 0 n y y 0 0 0 n y > y 0 y y > !EOF! Well, with my fdisk manglings, it now looks something like (this example fully initializes the disk, as opposed to editing existing partitions): fdisk -i -f - /dev/${DEVICE} < Though this isn't rocket science, I can see the benefit of having this > in a config file for newbies that just want to be able to store files on a > UFS ZIP disk and don't know or even want to know about how to set up what > cylinders, heads, and sectors go into their UFS slice. Umm, my changes are aimed at the EXPERT user. With these changes, it's just too easy to accidentally blow away an existing disk. When a config file is used, there is no pretty confirmation query asking the user if he really wants to amputate his toes and other sensitive body parts .... > But as they'll > still want to build a script to pull the fdisk, disklabel, and newfs into > one convenient "just do-it" command, its arguable and not much extra effort > for them to just pull this script out of the mailing list archives. Oh, yes. That's been my goal all along. I want a nice little tool that does everything, and making fdisk non-interactive was step #1. However, what I really want is a nice, screen-oriented, sysinstall-like (;-) tool. I'd also like to be able to use it for disaster-recovery (e.g., on a fixit-like disk). Unfortunately, this means that I'll probably have to write the user-interface in C, which begs the question, "Why don't I drop-kick fdisk and use libdisk instead?" (I discovered libdisk after I had finished most of my fdisk modifications). I don't have an answer for this. Any opinions? [ Instead of writing a C program, I'd love to write a Perl5 script. Unfortunately, not only would this make disaster-recovery impossible (perl is too big), and would force the user to install the optional perl5 package, but it would force the user to install an optional perl5 module to get access to curses. Bleah. ] -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. From owner-freebsd-hackers Fri Sep 20 21:07:39 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA29920 for hackers-outgoing; Fri, 20 Sep 1996 21:07:39 -0700 (PDT) Received: from gromit.pinpt.com (gromit.pinpt.com [205.179.195.7]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA29885; Fri, 20 Sep 1996 21:07:33 -0700 (PDT) Received: from rover3.pinpt.com (gatemaster.pinpt.com [205.179.195.65]) by gromit.pinpt.com (8.7.5/8.6.12) with SMTP id VAA25121; Fri, 20 Sep 1996 21:05:59 -0700 (PDT) Message-Id: <2.2.32.19960921040518.009779bc@wallace.pinpt.com> X-Sender: schluntz@wallace.pinpt.com X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 20 Sep 1996 21:05:18 -0700 To: emulatioin@freebsd.org From: "Sean J. Schluntz" Subject: Help Getting the Linux Emulation to work, please. Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am running 2.1.5R I added the lines: options COMPAT_LINUX options LINUX I already had the options: "COMPAT_43", SYSVSHM When I do a make I get: cc -c -O -W -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -nostdinc -I. -I../.. -I../../sys -I/usr/include -DGROMIT -DI586_CPU -DSYSVMSG -DSYSVSEM -DSYSVSHM -DLINUX -DCOMPAT_LINUX -Dsc0 -DUCONSOLE -DBOUNCE_BUFFERS -DSCSI_DELAY=15 -DCOMPAT_43 -DPROCFS -DCD9660 -DFFS -DINET -DKERNEL -Di386 -DLOAD_ADDRESS=0xF0100000 ../../i386/i386/machdep.c ../../i386/i386/machdep.c: In function `itit386': ../../i386/i386/machdep.c:1360: `Xlinux_syscall' undeclared (first use this function) ../../i386/i386/machdep.c:1360: (Each undeclared identifier is reported only once ../../i386/i386/machdep.c:1360: for each function it appears in.) *** Error code 1 Stop. What should I do? Thanks -Sean --- Sean J. Schluntz eMail schluntz@pinpt.com Manager Support Services Phone (408) 997-6900 x222 PinPoint Software Corporation Fax (408) 323-2300 http://www.pinpt.com/ From owner-freebsd-hackers Fri Sep 20 22:37:32 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA13786 for hackers-outgoing; Fri, 20 Sep 1996 22:37:32 -0700 (PDT) Received: from melb.werple.net.au (melb.werple.net.au [203.9.190.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA13724; Fri, 20 Sep 1996 22:37:27 -0700 (PDT) Received: (from uucp@localhost) by melb.werple.net.au (8.7.6/8.7.3/2) with UUCP id OAA02812; Sat, 21 Sep 1996 14:58:36 +1000 (EST) Received: (from jb@localhost) by freebsd3.cimlogic.com.au (8.7.5/8.7.3) id NAA14305; Sat, 21 Sep 1996 13:24:55 +1000 (EST) From: John Birrell Message-Id: <199609210324.NAA14305@freebsd3.cimlogic.com.au> Subject: Re: libc_r bug To: hsu@freefall.freebsd.org (Jeffrey Hsu) Date: Sat, 21 Sep 1996 13:24:54 +1000 (EST) Cc: jb@cimlogic.com.au, hackers@freefall.freebsd.org In-Reply-To: <199609210228.TAA13995@freefall.freebsd.org> from Jeffrey Hsu at "Sep 20, 96 07:28:31 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 > That takes care of fd 0, 1, and 2. But how do you tell if the parent > process has set up another fd, say, 3, for use by the child? Hmmm. You can't tell. This means that write will have to call _thread_fd_table_init in case the fd hasn't been used yet. There are some traps associated with sharing open file descriptors between processes, particularly between threaded and non-threaded processes because of the need for the threaded process to change the file descriptor to non-blocking. The most common place where this occurs is between the shell and a threaded process. If the shell uses the file descriptor before the child process has _completely_ exited (and set the file descriptors back to blocking) it needs to be able to handle EAGAIN errors. pdksh is much better than sh because it checks for fd = 0 set to non-blocking and restores the blocking state. I think all these issues would go away if kernel threads were used (and to me, this is the best justification for kernel threads). For the time being, though, the handling of blocking/non-blocking file descriptors is a compromize. Regards, -- John Birrell CIMlogic Pty Ltd jb@cimlogic.com.au 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 Sep 21 00:31:50 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA29193 for hackers-outgoing; Sat, 21 Sep 1996 00:31:50 -0700 (PDT) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA29177 for ; Sat, 21 Sep 1996 00:31:48 -0700 (PDT) Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with ESMTP id AAA19479 for ; Sat, 21 Sep 1996 00:31:54 -0700 (PDT) Received: (proff@localhost) by suburbia.net (8.7.4/Proff-950810) id RAA15662 for hackers@freebsd.org; Sat, 21 Sep 1996 17:31:35 +1000 From: Julian Assange Message-Id: <199609210731.RAA15662@suburbia.net> Subject: SVGATextMode under FBSD To: hackers@freebsd.org Date: Sat, 21 Sep 1996 17:31:35 +1000 (EST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a fetish for large text screens (the one I'm writing this email on is 180x60 (8x16 font) 10800 chars on screen at once, that's 5 x as much information before my brain). FreeBSD's inability to do this is the biggest problem I have with it, so I've started porting linux's SVGATextMode package. I'm managed to get vgaset running so far (lets you play with s/vga registers interactively and produces XF86 mode lines from your fiddling), however there are a few kernel issues I'd like advice on, before I start creating my own standards. FreeBSD, SVR4 and linux have: ioctl (open("/dev/console"), KDENABIO|KDDISABIO, 0) which gives access to all ioports. However SVR4 and linux also have: ioctl (open("/dev/console"), KDADDIO|KDDELIO, port) which gives/removes access to ioports in granular manner. Linux also has: int ioperm(unsigned long from, unsigned long num, int turn_on); DESCRIPTION Ioperm sets the port access permission bits for the process for num bytes starting from port address from to the value turn_on. The use of ioperm require root privileges. Only the first 0x3ff I/O ports can be specified in this manner. For more ports, the iopl function must be used. and: int iopl(int level); DESCRIPTION iopl changes the I/O privilege level of the current process, as specified in level. This call is necessary to allow 8514-compatible X servers to run under Linux. Since these X servers require access to all 65536 I/O ports, the ioperm call is not sufficient. Which are really just backends to KDADDIO|KDDISABIO and KDENABIO|KDDELIO respectively. Linux impliments KDADDIO/ioperm as a 128 byte bitmap for each process. This is the way I'd like to see it in FreeBSD, but I do not understand the how inb/outb interacts with the mm system well enough to do this confidently (comments on this?). As a crude hack, I intend to wrap KDADDIO|ioperm in linux_compat to KDENABIO. iopl wraps cleanly. This should be enough to run svgalib programs, which is a big win, IMEO. Linux also has: $ fgrep define /usr/include/linux/vt.h #define _LINUX_VT_H #define VT_OPENQRY 0x5600 /* find available vt */ #define VT_GETMODE 0x5601 /* get mode of active vt */ #define VT_SETMODE 0x5602 /* set mode of active vt */ #define VT_AUTO 0x00 /* auto vt switching */ #define VT_PROCESS 0x01 /* process controls switching */ #define VT_ACKACQ 0x02 /* acknowledge switch */ #define VT_GETSTATE 0x5603 /* get global vt state info */ #define VT_SENDSIG 0x5604 /* signal to send to bitmask of vts */ #define VT_RELDISP 0x5605 /* release display */ #define VT_ACTIVATE 0x5606 /* make vt active */ #define VT_WAITACTIVE 0x5607 /* wait for vt active */ #define VT_DISALLOCATE 0x5608 /* free memory associated to vt */ #define VT_RESIZE 0x5609 /* set kernel's idea of screensize */ #define VT_RESIZEX 0x560A /* set kernel's idea of screensize + more */ #define VT_LOCKSWITCH 0x560B /* disallow vt switching */ #define VT_UNLOCKSWITCH 0x560C /* allow vt switching */ ioctl's used for VT resizing etc, most of which do not have syscon/pcvt counterparts, but all of which should be relatively easy to impliment. In terms of the linux emmulation code, should these be implimented in syscons() using the linux defines/values, or as KD* extensions, with FreeBSD values, and a linux_compat ioctl() wrapper? I'm in favour of VT_* in order to avoid polluting the USL name space. -- "Of all tyrannies a tyranny sincerely exercised for the good of its victims may be the most oppressive. It may be better to live under robber barons than under omnipotent moral busybodies, The robber baron's cruelty may sometimes sleep, his cupidity may at some point be satiated; but those who torment us for own good will torment us without end, for they do so with the approval of their own conscience." - C.S. Lewis, _God in the Dock_ +---------------------+--------------------+----------------------------------+ |Julian Assange RSO | PO Box 2031 BARKER | Secret Analytic Guy Union | |proff@suburbia.net | VIC 3122 AUSTRALIA | finger for PGP key hash ID = | |proff@gnu.ai.mit.edu | FAX +61-3-98199066 | 0619737CCC143F6DEA73E27378933690 | +---------------------+--------------------+----------------------------------+ From owner-freebsd-hackers Sat Sep 21 00:43:32 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA05893 for hackers-outgoing; Sat, 21 Sep 1996 00:43:32 -0700 (PDT) Received: from trinity.radio-do.de (fn@trinity.Radio-do.de [193.101.164.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA05859 for ; Sat, 21 Sep 1996 00:43:28 -0700 (PDT) Received: by trinity.radio-do.de (8.7.5/CLIENT-1.2.7-h) via EUnet id JAA14130; Sat, 21 Sep 1996 09:43:14 +0200 (MET DST) To: Jaye Mathisen Cc: hackers@freebsd.org Subject: Re: Tweaking FreeBSD (2.1) and sendmail for a busy site? Or maybe, Help! , No more sendmail's. References: From: Frank Nobis Date: 21 Sep 1996 09:43:13 +0200 In-Reply-To: Jaye Mathisen's message of Fri, 20 Sep 1996 11:20:30 -0700 (PDT) Message-ID: Lines: 24 X-Mailer: Red Gnus v0.23/XEmacs 19.14 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>>> "Jaye" == Jaye Mathisen writes: Jaye> What else should I check? Sendmail has two parameters at which it starts to auto queue and later to reject incomming messages. >From my sendmail.cf # load avg at which to auto-queue msgs Ox3 # load avg at which to auto-reject connections OX2 Have a look at these parms in your sendmail.cf Regards Frank -- Frank Nobis Email: fn@Radio-do.de PGP AVAILABLE Landgrafenstr. 130 dg3dcn http://www.radio-do.de/~fn/ 44139 Dortmund Powered by FreeBSD Fax: +49 231 7213816 From owner-freebsd-hackers Sat Sep 21 01:38:00 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA03567 for hackers-outgoing; Sat, 21 Sep 1996 01:38:00 -0700 (PDT) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA03508 for ; Sat, 21 Sep 1996 01:37:50 -0700 (PDT) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.6.11/8.6.9) id SAA14845; Sat, 21 Sep 1996 18:37:39 +1000 From: David Dawes Message-Id: <199609210837.SAA14845@rf900.physics.usyd.edu.au> Subject: Re: SVGATextMode under FBSD To: proff@suburbia.net (Julian Assange) Date: Sat, 21 Sep 1996 18:37:39 +1000 (EST) Cc: hackers@FreeBSD.ORG In-Reply-To: <199609210731.RAA15662@suburbia.net> from "Julian Assange" at Sep 21, 96 05:31:35 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I have a fetish for large text screens (the one I'm writing this email on >is 180x60 (8x16 font) 10800 chars on screen at once, that's 5 x as much >information before my brain). FreeBSD's inability to do this is the >biggest problem I have with it, so I've started porting linux's SVGATextMode >package. > >I'm managed to get vgaset running so far (lets you play with s/vga registers >interactively and produces XF86 mode lines from your fiddling), however >there are a few kernel issues I'd like advice on, before I start creating >my own standards. > >FreeBSD, SVR4 and linux have: > > ioctl (open("/dev/console"), KDENABIO|KDDISABIO, 0) > >which gives access to all ioports. On SVR4.0 (at least), this enables/disables the list built up with the KDADDIO|KDDELIO calls. It doesn't turn on access to all ports. >However SVR4 and linux also have: > > ioctl (open("/dev/console"), KDADDIO|KDDELIO, port) > >which gives/removes access to ioports in granular manner. David From owner-freebsd-hackers Sat Sep 21 01:43:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA06034 for hackers-outgoing; Sat, 21 Sep 1996 01:43:34 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA05993 for ; Sat, 21 Sep 1996 01:43:27 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id SAA18103; Sat, 21 Sep 1996 18:12:57 +0930 From: Michael Smith Message-Id: <199609210842.SAA18103@genesis.atrad.adelaide.edu.au> Subject: Re: SVGATextMode under FBSD To: proff@suburbia.net (Julian Assange) Date: Sat, 21 Sep 1996 18:12:57 +0930 (CST) Cc: hackers@FreeBSD.ORG In-Reply-To: <199609210731.RAA15662@suburbia.net> from "Julian Assange" at Sep 21, 96 05:31:35 pm 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 Assange stands accused of saying: > > I have a fetish for large text screens (the one I'm writing this email on > is 180x60 (8x16 font) 10800 chars on screen at once, that's 5 x as much > information before my brain). FreeBSD's inability to do this is the > biggest problem I have with it, so I've started porting linux's SVGATextMode > package. You would be better off writing an LHM wrapper that could load drivers for known video cards and perform a set of basic operations on them, and then provide hooks for the console drivers (both syscons and pcvt) to use them. > Linux also has: > > int ioperm(unsigned long from, unsigned long num, int turn_on); This is not (yet) possible with FreeBSD, as all processes share a common I/O permissions map, and I/O permissions are granted on an all-or-nothing basis. You will need to enlist the help of an Intel guru and at least one kernel hacker to change this. I believe that Sean (sef@freebsd.org) has this on his list; certainly it will become an issue for the vm86 subsystem soon. Bruce has also revealed knowledge of the issue previously. > Which are really just backends to KDADDIO|KDDISABIO and KDENABIO|KDDELIO > respectively. Use of the console driver for controlling I/O permissions is incredibly bogus, and almost certainly stems historically from lazy programming. > Linux impliments KDADDIO/ioperm as a 128 byte bitmap for each process. > This is the way I'd like to see it in FreeBSD, but I do not understand > the how inb/outb interacts with the mm system well enough to do this > confidently (comments on this?). In/out do not interact with the system at all. If you execute an in/out instruction and you don't have the IOPL bit set, you'll trap and be killed. If you do, then the instructions execute as normal. Your suggestions wrt. maintaining linux compatability are worth pursuing IMO. > |Julian Assange RSO | PO Box 2031 BARKER | Secret Analytic Guy Union | Your .sig is too wide. -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sat Sep 21 01:54:22 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA10513 for hackers-outgoing; Sat, 21 Sep 1996 01:54:22 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA10383; Sat, 21 Sep 1996 01:54:03 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id KAA25194; Sat, 21 Sep 1996 10:28:08 +0200 Date: Sat, 21 Sep 1996 10:28:08 +0200 (MET DST) From: Luigi Rizzo To: freebsd-isp@freebsd.org, freebsd-hackers@freebsd.org cc: Luigi Rizzo Subject: Re: IP queue size limitations. (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ---------- Forwarded message ---------- Date: Sat, 21 SEP 1996 10:14:49 +0200 From: Luigi Rizzo Newgroups: comp.protocols.tcp-ip Subject: Re: IP queue size limitations. On 20 Sep 1996, Vernon Schryver wrote: > In article <51ub5h$8ul@noao.edu>, W. Richard Stevens wrote: > >> Now my question(s): > >> > >> + is it possible, in IP implementations (e.g. BSD), to set the > >> size of output queues differently on each interface ? > > > >It's certainly "possible" since each interface has its own ifq_maxlen > >value (in the ifqueue{} in the ifnet{}), but I've never seen an > >implementation that does this. You could always patch this by hand > At least one UNIX vendor's SLIP and PPP implementations bring > control of ifq_maxlen out to the user interface. I also think the (very clear and detailed explaination omitted -- thanks for including that, it is important that people becomes aware of this problem) I have digged through the FreeBSD sources (should not be much different from 4.4Lite2). ifq_maxlen is, for most interfaces, set to the global varialbe ifqmaxlen which in turn is set to IFQ_MAXLEN which defaults to 50. (this kind of chains is very usual in the BSD code). IFQ_MAXLEN can be defined in the configuration file, but it is the same for all interfaces. The exceptions (from memory) are slip and ppp (ifq_maxlen hardwired to explicit constants in the code, 32 and 50 I believe). At first sight, iijppp (user space ppp via the tun device) uses a queue length of 20. The approximate time needed to flush a queue is as follows: Interface MTU b/s qlen T (1 MSS) T (qlen MSS) ==================================================================== Ethernet 1500 10M 50 1.25ms 62.5ms FDDI ~4KB ~100M 50 330us 16.5ms Fast Ethernet 1500(?) 100M 50 125us 6.25ms T1 1500(?) 1.5M 50 8ms 400ms ISDN 1500 64K 50 188ms 9.4s ISDN 576 64K 50 72ms 3.6s PPP 1500 28.8 20 415ms 8.3s PPP 576 28.8 20 160ms 3.2s PPP 576 28.8 20 320ms 6.4s PPP 1500 14.4 20 830ms 16.6s Considering the default timer granularity, I believe that a queue lenght of up to 1s is acceptable for the slowest networks, but not much more than that. On the other hand, a busy router connecting networks of different speeds could benefit from larger sizes on the faster interfaces. For the slowest networks, I think it is fundamental to compute queue lengths in bytes (after compression, if available), not in maximum sized packets. Note that while this is a router issue, if the bottleneck is at the source more efficient solutions are available, such as a modified quench() call which shrinks the congestion window to a small (but larger than 1) segment. > fills and the delays increase. When the queue finially overflows, > it generally does more than than fast-retransmission can recover, > forcing a timeout and a slow-start, which causes the measured > latency on the link to drop to only the transmission delay. of course, all traffic is delayed by such long queues, the loss is detected after a *long* timeout and the process repeats forever. Luigi ==================================================================== Luigi Rizzo Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it Universita' di Pisa tel: +39-50-568533 via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 http://www.iet.unipi.it/~luigi/ ==================================================================== From owner-freebsd-hackers Sat Sep 21 03:12:42 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA18890 for hackers-outgoing; Sat, 21 Sep 1996 03:12:42 -0700 (PDT) Received: from logatome.micronet.fr (root@logatome.micronet.fr [194.51.75.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA18839 for ; Sat, 21 Sep 1996 03:12:36 -0700 (PDT) Received: from colas (pppA216.francenet.fr [193.149.100.70]) by logatome.micronet.fr (8.7.5/8.7.3) with ESMTP id MAA23587 for ; Sat, 21 Sep 1996 12:12:06 +0200 (MET DST) Message-Id: <199609211012.MAA23587@logatome.micronet.fr> From: "Colas" To: Date: Sat, 21 Sep 1996 12:10:16 +0200 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_01BBA7B5.D9C7F4E0" Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ceci est un message avec plusieurs parties au format MIME. ------=_NextPart_000_01BBA7B5.D9C7F4E0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit subscribe ------=_NextPart_000_01BBA7B5.D9C7F4E0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: base64 PGh0bWw+PGhlYWQ+PC9oZWFkPjxCT0RZIGJnY29sb3I9IiNGRkZGRkYiPjxwPjxmb250IHNpemU9 MiBjb2xvcj0iIzAwMDAwMCIgZmFjZT0iQXJpYWwiPnN1YnNjcmliZTwvcD4NCjwvZm9udD48L2Jv ZHk+PC9odG1sPg== ------=_NextPart_000_01BBA7B5.D9C7F4E0-- From owner-freebsd-hackers Sat Sep 21 03:24:32 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA25344 for hackers-outgoing; Sat, 21 Sep 1996 03:24:32 -0700 (PDT) Received: from mail0.iij.ad.jp (mail0.iij.ad.jp [192.244.176.61]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA25314 for ; Sat, 21 Sep 1996 03:24:29 -0700 (PDT) Received: from uucp1.iij.ad.jp (uucp1.iij.ad.jp [192.244.176.73]) by mail0.iij.ad.jp (8.6.12+2.4W/3.3W9-MAIL) with ESMTP id TAA05617 for ; Sat, 21 Sep 1996 19:24:27 +0900 Received: (from uucp@localhost) by uucp1.iij.ad.jp (8.6.12+2.4W/3.3W9-UUCP) with UUCP id TAA12182 for hackers@freebsd.org; Sat, 21 Sep 1996 19:24:27 +0900 Received: from xxx.fct.kgc.co.jp by yyy.kgc.co.jp (8.7.5/3.4W4:96080715) id TAA25691; Sat, 21 Sep 1996 19:07:28 +0900 (JST) Received: from localhost by xxx.fct.kgc.co.jp (8.7.5/3.3W8:95062916) id TAA03677; Sat, 21 Sep 1996 19:06:48 +0900 (JST) Message-Id: <199609211006.TAA03677@xxx.fct.kgc.co.jp> To: hackers@freebsd.org Subject: SIGFPE and signal(3) X-Mailer: Mew version 1.06 on Emacs 19.28.2, Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 21 Sep 1996 19:06:47 +0900 From: Toshihiro Kanda Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello. Next program never ends. Why? And how can I handle SIGFPE? Thank you. -------------------- #include #include void f(int x) { fprintf(stderr, "x = %d\n", x); } int x = 1, y = 0; main() { int z; signal(SIGFPE, f); printf("start\n"); z = x / y; printf("%d\n", z); } ------------------- candy@fct.kgc.co.jp (Toshihiro Kanda) From owner-freebsd-hackers Sat Sep 21 04:48:44 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA26727 for hackers-outgoing; Sat, 21 Sep 1996 04:48:44 -0700 (PDT) Received: from gvr.win.tue.nl (root@gvr.win.tue.nl [131.155.210.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA26688 for ; Sat, 21 Sep 1996 04:48:39 -0700 (PDT) Received: by gvr.win.tue.nl (8.6.13/1.53) id NAA17732; Sat, 21 Sep 1996 13:48:11 +0200 From: guido@gvr.win.tue.nl (Guido van Rooij) Message-Id: <199609211148.NAA17732@gvr.win.tue.nl> Subject: Re: new if_vx driver on freefall To: nao@sbl.cl.nec.co.jp (Naoki Hamada) Date: Sat, 21 Sep 1996 13:48:10 +0200 (MET DST) Cc: Guido.vanRooij@nl.cis.philips.com, dfr@render.com, freebsd-hackers@FreeBSD.org In-Reply-To: <199609210014.JAA24315@sirius.sbl.cl.nec.co.jp> from Naoki Hamada at "Sep 21, 96 09:14:46 am" 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 > * try ftp: Great! > > get /kernel /dev/null ... Approx. 800KB/sec > put /kernel /dev/null ... Approx. 800KB/sec > This is not so great according to me :-( > 2.3 Be #undef'ed BROKEN_AVAIL and try ping. > > * undef BROKEN_AVAIL > * make: OK > * reboot: OK > * execute: ping -f -s 1000 bell ... OK > * terminate with SIGING, and > * try ftp: Great! This means the supplied driver will also work for you...I guess. Perhaps even with more perfomance! -Guido From owner-freebsd-hackers Sat Sep 21 06:29:13 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA29105 for hackers-outgoing; Sat, 21 Sep 1996 06:29:13 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA29038 for ; Sat, 21 Sep 1996 06:29:07 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id XAA18730; Sat, 21 Sep 1996 23:23:30 +1000 Date: Sat, 21 Sep 1996 23:23:30 +1000 From: Bruce Evans Message-Id: <199609211323.XAA18730@godzilla.zeta.org.au> To: candy@fct.kgc.co.jp, hackers@freebsd.org Subject: Re: SIGFPE and signal(3) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Hello. Next program never ends. Why? And how can I handle SIGFPE? On the i386, division instructions that trap are restarted if the signal handler just returns (use gdb to see this). longjmp() in the signal handler is the only simple way to escape from the trap. The main code should be something like: if (setjmp(jb)) fix_up_or_give_up(); else code_that_might_trap(); If there is a large amount of code that might trap, then you won't have much idea where the problem occured, so fixing it is impractical, but giving up might be reasonable. Returning from the SIGFPE handler for a floating point trap is also usually wrong, but may sort of work on the i386 because of the different way that the FPU works and more possibilities for kernel trap handling. FPU instructions that trap are also restarted; however, kernels normally clear the FPU exception bits before calling the signal handler, and FPU instructions that cause an exception don't trap until the next FPU instruction after the one that caused the exception. Thus execution normally proceeds beyond the instruction that caused the original trap. The FPU state is undefined after a SIGFPE, unless the SIGFPE handler calls longjmp(), when (in FreeBSD) it the state is restored to almost the one at the time of the corresponding setjmp(). (The state is actually something like: in -current, all registers are empty, which is usually the wrong state for returning from the signal handler with; in my version, the state is the same as when the trap occured except the exception mask is cleared.) Bruce >-------------------- >#include >#include > >void >f(int x) >{ > fprintf(stderr, "x = %d\n", x); >} > >int x = 1, y = 0; > >main() >{ > int z; > signal(SIGFPE, f); > printf("start\n"); > z = x / y; > printf("%d\n", z); >} >------------------- From owner-freebsd-hackers Sat Sep 21 09:51:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA00499 for hackers-outgoing; Sat, 21 Sep 1996 09:51:25 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA00431 for ; Sat, 21 Sep 1996 09:51:17 -0700 (PDT) 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 SAA01167 for ; Sat, 21 Sep 1996 18:51:20 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id SAA22796 for freebsd-hackers@freefall.cdrom.com; Sat, 21 Sep 1996 18:58:08 +0200 Date: Sat, 21 Sep 1996 18:58:08 +0200 From: Christoph Kukulies Message-Id: <199609211658.SAA22796@gilberto.physik.rwth-aachen.de> To: freebsd-hackers@freefall.FreeBSD.org Subject: /etc/issue Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Is this an issue? Should FreeBSD have such a file? Or is there an equivalent? mgetty+sendfax require such a file when mgetty fakes a login, i.e. it sends the issue file before exec'ing /usr/bin/login. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Sat Sep 21 09:52:09 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA00997 for hackers-outgoing; Sat, 21 Sep 1996 09:52:09 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA00981 for ; Sat, 21 Sep 1996 09:52:07 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id JAA26553; Sat, 21 Sep 1996 09:51:04 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) by whistle.com via smap (V1.3) id sma026551; Sat Sep 21 09:50:43 1996 Date: Sat, 21 Sep 1996 09:49:06 -0700 (PDT) From: Julian Elischer To: "Jordan K. Hubbard" cc: hackers@freebsd.org, Richard Heaton Subject: Re: Job openings: Unix Network Programmers, Internet server In-Reply-To: <21084.843273967@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Of course, as they are in direct competition with Whistle, we hope you'll talk to us too :) (www.whistle.com) julian heh heh On Fri, 20 Sep 1996, Jordan K. Hubbard wrote: > ... And lest anyone be tempted to flame Richard for what they deem an > "inappropriate posting," I just wanted to say that FreeBSD related job > postings definitely constitute reasonable use, especially if they > result in someone actually being paid to improve some part of FreeBSD. > > Jordan > > From owner-freebsd-hackers Sat Sep 21 10:02:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA06337 for hackers-outgoing; Sat, 21 Sep 1996 10:02:34 -0700 (PDT) Received: from casparc.ppp.net (casparc.ppp.net [194.64.12.35]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA06184 for ; Sat, 21 Sep 1996 10:02:18 -0700 (PDT) Received: from ernie by casparc.ppp.net with uucp (Smail3.1.28.1 #1) id m0v4VRV-000I3fC; Sat, 21 Sep 96 19:02 MET DST Received: by ernie.kts.org (Smail3.1.29.1 #5) id m0v4V93-00000bC; Sat, 21 Sep 96 18:43 MET DST Message-Id: From: hm@kts.org (Hellmuth Michaelis) Subject: fullscreen disk partition editor available for testing To: freebsd-hackers@freebsd.org Date: Sat, 21 Sep 1996 18:43:09 +0200 (MET DST) Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, i have just put a curses fullscreen disk partition editor into the FreeBSD/incoming directory on ftp.freebsd.org named dpe-0.2.tar.gz. This package should only be compiled and run by someone who is - able to read source code instead of manuals - knows what he is doing - has a spare drive for testing EVERYONE else should just forget this mail: the code is definitely NOT ready for public usage and may DESTROY all the data on your disk drives !!!!! I will continue to work on this and perhaps add a DOG partition screen and a newfs/mkfs screen to it, but for now it has to settle just a bit. Have fun, hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe (A)bort, (R)etry, (I)nstall BSD ? From owner-freebsd-hackers Sat Sep 21 10:27:20 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA21799 for hackers-outgoing; Sat, 21 Sep 1996 10:27:20 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA21779 for ; Sat, 21 Sep 1996 10:27:18 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id KAA11982; Sat, 21 Sep 1996 10:27:13 -0700 (PDT) To: Julian Elischer cc: Richard Heaton , hackers@freebsd.org Subject: Re: Job openings: Unix Network Programmers, Internet server In-reply-to: Your message of "Sat, 21 Sep 1996 09:49:06 PDT." Date: Sat, 21 Sep 1996 10:27:12 -0700 Message-ID: <11980.843326832@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Of course, as they are in direct competition with Whistle, > we hope you'll talk to us too :) Actually, since you mention it, you guys don't have to view this entirely as "competition" and could actually share some of the development work in areas where there's no "competetive advantage" to give away. Richard and I talked about this yesterday, and Empac feels that things like general PPP improvements or bug fixes to the system should not be viewed as competition points, it being in everyone's best interest to make FreeBSD as robust and reliable a development platform as possible. The competetive advantages lie in what is placed on top, not the foundation, and given that firms like Whistle and Empac are both relatively small (certainly when compared to the Mighty Microsoft), they'd do well to pool their resources if and whenever possible. Richard told me yesterday that Microsoft recently announced a multi-billion (yes, billion) dollar initiative to make NT *the* network operating system in 1997, and that's a whole heck of a lot of money. It's time for small companies involved with UNIX to pool their efforts or Bill is going to eat them all. He might eat them anyway, in the long run, but I'd really hate to look back on this time and reflect that we made it easy for him to do so by squabbling amongst ourselves while Microsoft raced ahead. I think the UNIX community has already done far too much of that already and it's time for a change. Perhaps we could set about identifying areas of common interest and open a discussion on mutual development priorities? Jordan From owner-freebsd-hackers Sat Sep 21 10:59:28 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA11400 for hackers-outgoing; Sat, 21 Sep 1996 10:59:28 -0700 (PDT) Received: from DeepCore.dk (dial54.cybercity.dk [194.16.56.54]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA11356 for ; Sat, 21 Sep 1996 10:59:18 -0700 (PDT) Received: (from sos@localhost) by DeepCore.dk (8.7.6/8.7.3) id QAA00459; Sat, 21 Sep 1996 16:36:57 +0200 (MET DST) Message-Id: <199609211436.QAA00459@DeepCore.dk> Subject: Re: SVGATextMode under FBSD To: proff@suburbia.net (Julian Assange) Date: Sat, 21 Sep 1996 16:36:57 +0200 (MET DST) Cc: hackers@FreeBSD.org In-Reply-To: <199609210731.RAA15662@suburbia.net> from Julian Assange at "Sep 21, 96 05:31:35 pm" From: sos@FreeBSD.org Reply-to: sos@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL15 (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 Julian Assange who wrote: > > I have a fetish for large text screens (the one I'm writing this email on > is 180x60 (8x16 font) 10800 chars on screen at once, that's 5 x as much > information before my brain). FreeBSD's inability to do this is the > biggest problem I have with it, so I've started porting linux's SVGATextMode > package. Oh, someone down that road again :) > Which are really just backends to KDADDIO|KDDISABIO and KDENABIO|KDDELIO > respectively. > > Linux impliments KDADDIO/ioperm as a 128 byte bitmap for each process. > This is the way I'd like to see it in FreeBSD, but I do not understand > the how inb/outb interacts with the mm system well enough to do this > confidently (comments on this?). As a crude hack, I intend to wrap > KDADDIO|ioperm in linux_compat to KDENABIO. iopl wraps cleanly. This > should be enough to run svgalib programs, which is a big win, IMEO. We have no prvision for doing this (yet) it _might_ be done in not so long time.. > ioctl's used for VT resizing etc, most of which do not have syscon/pcvt > counterparts, but all of which should be relatively easy to impliment. > In terms of the linux emmulation code, should these be implimented in > syscons() using the linux defines/values, or as KD* extensions, with > FreeBSD values, and a linux_compat ioctl() wrapper? I'm in favour of > VT_* in order to avoid polluting the USL name space. Syscons uses the winsize structure, and reports back when there is a resolution change :), the extra VT defines is a linux bogosity :) All, in all, the way this should be done, is writing a lkm module that can be loaded and adds the prober ioctl's to the console driver (well at least syscons). The provisions for this is in the next update I have for syscons (most of it is allready there). If you want to do it this way, I'd help where I can, I might know a trick or two in this area :) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- S鷨en Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Sat Sep 21 10:59:52 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA11605 for hackers-outgoing; Sat, 21 Sep 1996 10:59:52 -0700 (PDT) Received: from gluon.mep.ruhr-uni-bochum.de (gluon.mep.ruhr-uni-bochum.de [134.147.160.165]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA11568 for ; Sat, 21 Sep 1996 10:59:48 -0700 (PDT) Received: (from roberte@localhost) by gluon.mep.ruhr-uni-bochum.de (8.6.12/8.6.12) id TAA10968; Sat, 21 Sep 1996 19:59:01 +0200 From: Robert Eckardt Message-Id: <199609211759.TAA10968@gluon.mep.ruhr-uni-bochum.de> Subject: Re: /etc/issue In-Reply-To: <199609211658.SAA22796@gilberto.physik.rwth-aachen.de> from Christoph Kukulies at "21. Sep. 96 18:57:36" To: kuku@gilberto.physik.RWTH-Aachen.DE (Christoph Kukulies) Date: Sat, 21 Sep 1996 19:59:01 +0200 (MET DST) Cc: freebsd-hackers@freefall.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 > Is this an issue? Should FreeBSD have such a file? Or is there an > equivalent? I think /etc/issue is SysVish. On BSD one has /etc/gettytab where you can define such a message for every line separately. E.g.: default:\ :cb:ce:ck:lc:fd#1000:im=\033[1;1H\033[2J\014\r\n\r\n\ Welcome to %h\r\n\r\n\ [...] > mgetty+sendfax require such a file when mgetty fakes a login, i.e. > it sends the issue file before exec'ing /usr/bin/login. > > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de -- Robert Eckardt ( Ruhr-Universitaet Bochum, Inst.f.Theor.Physik, NB6/169 ) Universitaetsstrasse 150, D-44780 Bochum, Germany ----X---8---- Telefon: +49 234 700-3709, Telefax: +49 234 7094-574 8 E-Mail: RobertE@MEP.Ruhr-Uni-Bochum.de --------8---- URL: http://WWW.MEP.Ruhr-Uni-Bochum.de/~roberte >>> To be successful one needs friends, <<< >>> To be very successful one needs enemies. <<< From owner-freebsd-hackers Sat Sep 21 11:27:30 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA28534 for hackers-outgoing; Sat, 21 Sep 1996 11:27:30 -0700 (PDT) Received: from csla.csl.sri.com (csla.csl.sri.com [192.12.33.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA28513 for ; Sat, 21 Sep 1996 11:27:27 -0700 (PDT) Received: from impulse.csl.sri.com (impulse.csl.sri.com [130.107.15.11]) by csla.csl.sri.com (8.7.3/8.7.3) with ESMTP id LAA12021 for ; Sat, 21 Sep 1996 11:26:56 -0700 (PDT) Received: from impulse.csl.sri.com (localhost [127.0.0.1]) by impulse.csl.sri.com (8.7.3/8.7.3) with ESMTP id LAA02569 for ; Sat, 21 Sep 1996 11:24:27 -0700 (PDT) Message-Id: <199609211824.LAA02569@impulse.csl.sri.com> To: freebsd-hackers@freefall.freebsd.org Subject: Problem with rpcgen (resolved, sort of) Date: Sat, 21 Sep 1996 11:24:26 -0700 From: Fred Gilham Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I recently posted a question about a problem I was having with rpcgen, where it would mangle `directive' lines that had line continuation characters as follows: %#define PRINTRECORD(fp,r,t) { \ % fprintf(fp,RECFORMAT, \ % UID_LEN, r->userid, \ % COUNT_LEN, r->count, \ % SEED_LEN, r->seed, \ % VAL_LEN, r->val, \ % TIME_LEN, t); \ %} (The purpose of doing the above was to wind up with macros in the generated files that spanned several lines.) At any rate, after considerable head-scratching I've traced the problem to GNU CPP's habit of removing the backslash/newline pairs in all circumstances. It turns out that rpcgen runs cpp as a front-end, and on FreeBSD, unlike SunOS and Solaris 2, the GNU preprocessor is used. So if anyone had tried to investingate this behavior, there's no need. -Fred P.S. I enjoy using FreeBSD and am pushing it for server use here in the lab I administer. We have 8 machines in various roles with an aggregate of about 60GB of disk space on these 8 machines. Apart from little puzzles (like the above) from time to time, everything works well. From owner-freebsd-hackers Sat Sep 21 11:29:35 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA29882 for hackers-outgoing; Sat, 21 Sep 1996 11:29:35 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA28115 for ; Sat, 21 Sep 1996 11:26:52 -0700 (PDT) Received: from rover.village.org by agora.rdrop.com with smtp (Smail3.1.29.1 #17) id m0v4WlM-0008tzC; Sat, 21 Sep 96 11:26 PDT Received: from rover.village.org (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with ESMTP id MAA12668 for ; Sat, 21 Sep 1996 12:20:11 -0600 (MDT) Message-Id: <199609211820.MAA12668@rover.village.org> To: hackers@freebsd.org Subject: Kernel sizes Date: Sat, 21 Sep 1996 12:20:11 -0600 From: Warner Losh Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Something must be very very wrong. My new kernel is 30k smaller than my old (1month old) kernel. :-) I built a kernel on Aug 24, and got the following: -rwxr-xr-x 1 root wheel 884812 Aug 24 15:23 /kernel Today, I build last night's kernel with exactly the same config file, and I get: -rwxr-xr-x 1 imp wheel 853988 Sep 21 12:10 kernel A 30k reduction in size isn't supposed to happen. Where are the new features? What was in that 30k? Even size(1) tells the same story. A 3.5% reduction on the size of the kernel after a month of fixes. I kinda like that :-) Any ideas why things are this much smaller? I know Bruce did a lot of work on optimizing the size of the boot blocks... This is, btw, with the same compiler. I've not done a make world yet, so it isn't a 2.6.3 vs 2.7.2.1 issue. Congratulations! This is the first time I've seen things move smaller in a long time. Warner From owner-freebsd-hackers Sat Sep 21 11:58:56 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA18056 for hackers-outgoing; Sat, 21 Sep 1996 11:58:56 -0700 (PDT) Received: from glacier.cold.org (glacier.cold.org [206.81.134.54]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA18031 for ; Sat, 21 Sep 1996 11:58:52 -0700 (PDT) Received: (from brandon@localhost) by glacier.cold.org (8.7.5/8.7.3) id NAA13838; Sat, 21 Sep 1996 13:01:19 -0600 (MDT) Date: Sat, 21 Sep 1996 13:01:19 -0600 (MDT) From: Brandon Gillespie To: freebsd-hackers@freebsd.org Subject: splash-page on bootup.. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I realize that I'm getting onto very shaky ground and that my thoughts may possibly be deemed as sacreligeous, but I digress 8) I am involved in an internet company which is composed in majority of Microsoft dead heads--NT is the only solution in their minds. I have been doing my best to work other ideas into their conciousness. Recently when showing one of the guys FreeBSD I was surprised by his reactions. This guy does not actually do much system work--he is an administrator through and through and I love him for it (he can 'network' better than anybody I know :) However, He is used to his padded Microsoft world. When I booted the FreeBSD system for a demo he became quite frantic when he saw all of the system probes. At first I was not sure what the problem was, until I realized he had never seen this type of behaviour before, and assumed it was errors or some other similar problem--and even after a bit of explaning he was still somewhat uncomfortable with it. >From this point, I began to wonder how much work it would be to do something like 95 does, splashing something on the screen during the probes and bootup sequence (and allowing you to get to them with whatever key sequence 95 does, ALT-Tab?). This could be as simple as reading a simple image from the disk or even simpler as a program that just draws single pixel scattered shimmering stars and prints 'Booting FreeBSD 2.1.x-XXXXblah'--or even as complex as an animated GIF showing the FreeBSD daemon searching around with a flashlight ;) (the spash screen would disappear at the end of rc file execution--at which point you could fire up xdm or stick with getty's). What would this accomplish? Quite a bit IMHO. People have horrible pre-conceptions in their mind about Free software, especially if they are from the MSDOS/Windows arena because a LARGE majority of the free software has been (and is still likely)--frankly put--virus infected crap. Coming from this background it takes a lot of effort for somebody to give up their prejudices--no matter how much it will save them or how much 'better' it may be. Having a system which looks and feels professional to them and which gives them the same fuzzy feeling will help them in overcoming their notions and accepting the fact that using something else may be a viable solution. (read: professional == they consider Microsoft a viable solution because they pay $xxxx for it and their friend over at corp X also uses it, therefore it is a professional systems) Is it possible? I don't know, I am not familiar enough with the kernel. Just figured I would let my opinion be known. 8) -Brandon Gillespie From owner-freebsd-hackers Sat Sep 21 12:39:00 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA12865 for hackers-outgoing; Sat, 21 Sep 1996 12:39:00 -0700 (PDT) Received: from ms1.wow.net (wow.net [196.3.138.14]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA12323 for ; Sat, 21 Sep 1996 12:38:10 -0700 (PDT) Received: from berardo.wow.net (196.3.138.73) by ms1.wow.net with SMTP (Apple Internet Mail Server 1.1.1); Sat, 21 Sep 1996 15:37:07 -0400 Message-Id: <1.5.4.32.19960921193656.00671dd8@wow.net> X-Sender: berardo@wow.net (Unverified) X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 21 Sep 1996 15:36:56 -0400 To: hackers@FreeBSD.org From: Tarun Pinto Pereira Subject: supoted platforms Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk is it possible to send me a list of platforms supported be freebsd? Svoboda From owner-freebsd-hackers Sat Sep 21 12:39:28 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA13128 for hackers-outgoing; Sat, 21 Sep 1996 12:39:28 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA13107 for ; Sat, 21 Sep 1996 12:39:25 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA02521; Sat, 21 Sep 1996 12:38:02 -0700 From: Terry Lambert Message-Id: <199609211938.MAA02521@phaeton.artisoft.com> Subject: Re: Plug and Play naivety To: garycorc@mail.idt.net Date: Sat, 21 Sep 1996 12:38:02 -0700 (MST) Cc: smpatel@umiacs.umd.edu, janus@freegate.net, hackers@FreeBSD.org In-Reply-To: <32435339.15C2@mail.idt.net> from "Gary Corcoran" at Sep 20, 96 10:30:17 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 the (eventual) plan for the PnP code to allow kernel-config-specified > values to override those programmed by a PnP BIOS? This would be > desirable to allow for fixing things when the BIOS botches its > automatic assignments (and/or I just want to specify, for example, my > own priorities for IRQs). One would hope the kernel were capable of automatic assignments. The less user involvement, the better. 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 Sat Sep 21 12:39:58 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA13420 for hackers-outgoing; Sat, 21 Sep 1996 12:39:58 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA13404 for ; Sat, 21 Sep 1996 12:39:56 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA02511; Sat, 21 Sep 1996 12:37:15 -0700 From: Terry Lambert Message-Id: <199609211937.MAA02511@phaeton.artisoft.com> Subject: Re: USB + Re: Plug and Play naivety To: smpatel@umiacs.umd.edu (Sujal Patel) Date: Sat, 21 Sep 1996 12:37:15 -0700 (MST) Cc: hasty@rah.star-gate.com, terry@lambert.org, janus@freegate.net, hackers@FreeBSD.org In-Reply-To: from "Sujal Patel" at Sep 20, 96 08:54:42 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 > > Yes, I can confirm that the GUS PnP works with BIOS hints or with hardcoded > > values in the kernel config file. Additionally, the GUS PnP fills in the > > isa data structures so the rest of the kernel knows what the card > > got set to. > > This is indeed how the PnP driver is evolving (but it's more generic then > just one card). The only problem will be that people without any PnP > bios support, will have to specify *all* of the parameters that a PnP > devices needs (this can become quite ugly for the user, especially if all > they have a a config line in the kernel config). It would be nice to > have an easy configuration utility wouldn't it? Volunteers? :-) It would be nicer if the PnP support would do the conflict resoloution itself, actually. There's no reason that the OS can't provide the same services to the OS that a functioning BIOS should provide. This would incidently recover from a BIOS screwup (which people have talked about in this thread, but which I've never seen "in real life"). > > Since we are discussing PnP and thats good 8) what about support > > for USB devices?? > > That's no my department, I know nothing about USB devices... Terry? :-) No USG hardware here, I'm afraid. The Intel doc (in Acrobat format) can be downloaded from the Intel WWW site. 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 Sat Sep 21 12:43:16 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA15414 for hackers-outgoing; Sat, 21 Sep 1996 12:43:16 -0700 (PDT) Received: from gluon.mep.ruhr-uni-bochum.de (gluon.mep.ruhr-uni-bochum.de [134.147.160.165]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA15385 for ; Sat, 21 Sep 1996 12:43:13 -0700 (PDT) Received: (from roberte@localhost) by gluon.mep.ruhr-uni-bochum.de (8.6.12/8.6.12) id VAA11145 for hackers@freebsd.org; Sat, 21 Sep 1996 21:42:50 +0200 From: Robert Eckardt Message-Id: <199609211942.VAA11145@gluon.mep.ruhr-uni-bochum.de> Subject: Swap on vnode pseudo disks ? To: hackers@freebsd.org Date: Sat, 21 Sep 1996 21:42:50 +0200 (MET DST) 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 Hello, can someone please comment on the reliability of vnoded swap areas ? I remember somehow that there were problems and machines liked to crash. However, I have only configured 80 MB of `hard' swap space and need more. I'm running 2.1.5R on a 486DX2/66-ISA with 1 IDE, 2 SCSI drives and 16MB RAM under FreeBSD. Is there a way to avoid that the kernel kills my Xserver ? (It's the most efficient way to start all over again :-) Greetings, Robert -- Robert Eckardt ( Ruhr-Universitaet Bochum, Inst.f.Theor.Physik, NB6/169 ) Universitaetsstrasse 150, D-44780 Bochum, Germany ----X---8---- Telefon: +49 234 700-3709, Telefax: +49 234 7094-574 8 E-Mail: RobertE@MEP.Ruhr-Uni-Bochum.de --------8---- URL: http://WWW.MEP.Ruhr-Uni-Bochum.de/~roberte >>> To be successful one needs friends, <<< >>> To be very successful one needs enemies. <<< From owner-freebsd-hackers Sat Sep 21 12:52:28 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA20369 for hackers-outgoing; Sat, 21 Sep 1996 12:52:28 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA20342 for ; Sat, 21 Sep 1996 12:52:25 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id OAA14040; Sat, 21 Sep 1996 14:50:42 -0500 From: Joe Greco Message-Id: <199609211950.OAA14040@brasil.moneng.mei.com> Subject: Re: /etc/issue To: kuku@gilberto.physik.rwth-aachen.de (Christoph Kukulies) Date: Sat, 21 Sep 1996 14:50:42 -0500 (CDT) Cc: freebsd-hackers@freefall.freebsd.org In-Reply-To: <199609211658.SAA22796@gilberto.physik.rwth-aachen.de> from "Christoph Kukulies" at Sep 21, 96 06:58:08 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Is this an issue? Should FreeBSD have such a file? Or is there an > equivalent? > > mgetty+sendfax require such a file when mgetty fakes a login, i.e. > it sends the issue file before exec'ing /usr/bin/login. You can put a moderately long (but not a page long) message in /etc/gettytab: > telnet smyrno.sol.net. Trying 206.55.64.117 ... Connected to smyrno.sol.net. Escape character is '^]'. sol.net Network Services - Milwaukee, WI This is a restricted access system. Unauthorized access is prohibited. For technical support or problems, please contact . FreeBSD 2.0.5R UNIX (smyrno.sol.net) (ttyp2) login: ^D Connection closed by foreign host. > cat /etc/gettytab [...] default:\ :cb:ce:ck:lc:fd#1000:im=\r\n\r\nsol.net Network Services - Milwaukee, WI\r\n\r\nThis is a restricted access system. Unauthorized access is prohibited.\r\nFor technical support or problems, please contact .\r\n\r\nFreeBSD 2.0.5R UNIX (%h)\r\n\r\n(%t) :sp#1200: [...] I realize that this is somewhat different from /etc/issue, but on the other hand, you can provide different initial messages for each TTY, etc. Been doing it for years... even back in SunOS 4.1 days, where I hacked the support into a few things such as telnetd. Speaking of which: telnetd uses the gettytab "default" entry for its own im=. ... JG From owner-freebsd-hackers Sat Sep 21 13:30:39 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA05169 for hackers-outgoing; Sat, 21 Sep 1996 13:30:39 -0700 (PDT) Received: from phoenix.csie.nctu.edu.tw (root@phoenix.csie.nctu.edu.tw [140.113.17.171]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA05129 for ; Sat, 21 Sep 1996 13:30:31 -0700 (PDT) Received: from FreeBSD.csie.NCTU.edu.tw (freebsd.csie.nctu.edu.tw [140.113.235.250]) by phoenix.csie.nctu.edu.tw (8.7.5/8.7.5) with ESMTP id EAA03991 for ; Sun, 22 Sep 1996 04:28:03 +0800 (CST) Received: (from jdli@localhost) by FreeBSD.csie.NCTU.edu.tw (8.7.6/8.7.3) id EAA27508 for freebsd-hackers@freebsd.org; Sun, 22 Sep 1996 04:29:46 +0800 (CST) Date: Sun, 22 Sep 1996 04:29:46 +0800 (CST) From: Jian-Da Li Message-Id: <199609212029.EAA27508@FreeBSD.csie.NCTU.edu.tw> To: freebsd-hackers@freebsd.org Subject: Re: fullscreen disk partition editor available for testing Newsgroups: mailing.freebsd.hackers Organization: NCTU CSIE FreeBSD Server X-Newsreader: TIN [UNIX 1.3 950824BETA+ANSI+COLOR PL6] Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk : i have just put a curses fullscreen disk partition editor into the : FreeBSD/incoming directory on ftp.freebsd.org named dpe-0.2.tar.gz. Nice tool !! I tested it with my Jaz disk and success... : I will continue to work on this and perhaps add a DOG partition : screen and a newfs/mkfs screen to it, but for now it has to settle : just a bit. suggestions: 1. when allocating partition size, there is no size-range checking, I can allocate larger size than partition-c 2. maybe add fdisk function also ? Thanks. -- 李 建 達 (Jian-Da Li) 交 大 資 工 E-Mail : http://www.csie.nctu.edu.tw/~jdli From owner-freebsd-hackers Sat Sep 21 13:36:24 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA06824 for hackers-outgoing; Sat, 21 Sep 1996 13:36:24 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA06800 for ; Sat, 21 Sep 1996 13:36:17 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id PAA14072; Sat, 21 Sep 1996 15:34:32 -0500 From: Joe Greco Message-Id: <199609212034.PAA14072@brasil.moneng.mei.com> Subject: Re: splash-page on bootup.. To: brandon@glacier.cold.org (Brandon Gillespie) Date: Sat, 21 Sep 1996 15:34:32 -0500 (CDT) Cc: freebsd-hackers@freebsd.org In-Reply-To: from "Brandon Gillespie" at Sep 21, 96 01:01:19 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ohhhh I started to feel sick when I saw this.. :-) > realized he had never seen this type of behaviour before, and assumed it > was errors or some other similar problem--and even after a bit of > explaning he was still somewhat uncomfortable with it. Gee, not like Microsoft products (*cough*.. DOS) didn't do this as a ritual part of the boot process for over a decade... > simple image from the disk or even simpler as a program that just draws > single pixel scattered shimmering stars and prints 'Booting FreeBSD > 2.1.x-XXXXblah'--or even as complex as an animated GIF showing the FreeBSD > daemon searching around with a flashlight ;) (the spash screen would > disappear at the end of rc file execution--at which point you could fire > up xdm or stick with getty's). You're in a difficult situation... even a static GIF image would probably be difficult because you don't know what you have for console until you have probed the video.. animation I would think is out of the question due to the way I understand the kernel works during the probe phase. ( Yes I know this has been discussed as a target for change, Terry :-) ) > What would this accomplish? Quite a bit IMHO. People have horrible > pre-conceptions in their mind about Free software, especially if they are > from the MSDOS/Windows arena because a LARGE majority of the free software > has been (and is still likely)--frankly put--virus infected crap. Coming > from this background it takes a lot of effort for somebody to give up > their prejudices--no matter how much it will save them or how much > 'better' it may be. Having a system which looks and feels professional to > them and which gives them the same fuzzy feeling will help them in > overcoming their notions and accepting the fact that using something else > may be a viable solution. A system that looks and feels professional to me is a system that does not hide every aspect of what the hell it is doing from me. Microsoft Windows 95 is unprofessional. It is slick in many ways... but just try to get it to do what you want, when you really know you want to do what it doesn't want to let you do. Solaris is (reasonably) professional. Although I hate to admit it: DOS is professional. It is simply not a good choice of "OS" (I use the term loosely). Hiding what the hell is going on is fine for the "chump" market... which largely consists of home users on Packard Bells, secretaries, and businessmen lugging their laptops around. > (read: professional == they consider Microsoft a viable solution because > they pay $xxxx for it and their friend over at corp X also uses it, > therefore it is a professional systems) That kind of logic scares me :-( I consider Microsoft to be crap and I usually consider corp X to be crap too when I see them relying on Microsoft for any "major" application. > Is it possible? I don't know, I am not familiar enough with the kernel. > Just figured I would let my opinion be known. 8) Now, the real question is, is it a bad idea? Maybe not. Maybe we just need a fancy (fancier) boot loader. ... JG From owner-freebsd-hackers Sat Sep 21 13:36:41 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA06894 for hackers-outgoing; Sat, 21 Sep 1996 13:36:41 -0700 (PDT) Received: from DeepCore.dk (aalb26.pip.dknet.dk [194.192.0.186]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA06845 for ; Sat, 21 Sep 1996 13:36:29 -0700 (PDT) Received: (from sos@localhost) by DeepCore.dk (8.7.6/8.7.3) id WAA02313; Sat, 21 Sep 1996 22:25:48 +0200 (MET DST) Message-Id: <199609212025.WAA02313@DeepCore.dk> Subject: Re: splash-page on bootup.. To: brandon@glacier.cold.org (Brandon Gillespie) Date: Sat, 21 Sep 1996 22:25:48 +0200 (MET DST) Cc: freebsd-hackers@FreeBSD.org In-Reply-To: from Brandon Gillespie at "Sep 21, 96 01:01:19 pm" From: sos@FreeBSD.org Reply-to: sos@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL15 (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 Brandon Gillespie who wrote: > I realize that I'm getting onto very shaky ground and that my thoughts may > possibly be deemed as sacreligeous, but I digress 8) [snip snap] > >From this point, I began to wonder how much work it would be to do > something like 95 does, splashing something on the screen during the > probes and bootup sequence (and allowing you to get to them with whatever > key sequence 95 does, ALT-Tab?). This could be as simple as reading a > simple image from the disk or even simpler as a program that just draws > single pixel scattered shimmering stars and prints 'Booting FreeBSD > 2.1.x-XXXXblah'--or even as complex as an animated GIF showing the FreeBSD > daemon searching around with a flashlight ;) (the spash screen would > disappear at the end of rc file execution--at which point you could fire > up xdm or stick with getty's). I have done this once a long time ago, but I newer released the code for it, I didn't dare :) > Is it possible? I don't know, I am not familiar enough with the kernel. > Just figured I would let my opinion be known. 8) Sure it is, its a bit complicated if we should support more than just plain VGA, but that could be done pretty easily. Do we have any graphic designers here that could draw a nice FreeBSD "graphics for the dummies" entry pic ?? in say 320x200x256 or 640x480x16, then I'll do the code that makes it appear :) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- S鷨en Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Sat Sep 21 13:39:58 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA07946 for hackers-outgoing; Sat, 21 Sep 1996 13:39:58 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA07830 for ; Sat, 21 Sep 1996 13:39:42 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id PAA14080; Sat, 21 Sep 1996 15:37:56 -0500 From: Joe Greco Message-Id: <199609212037.PAA14080@brasil.moneng.mei.com> Subject: Re: Job openings: Unix Network Programmers, Internet server To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sat, 21 Sep 1996 15:37:56 -0500 (CDT) Cc: julian@current1.whistle.com, Rich.Heaton@empac.com, hackers@FreeBSD.org In-Reply-To: <11980.843326832@time.cdrom.com> from "Jordan K. Hubbard" at Sep 21, 96 10:27:12 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Richard told me yesterday that Microsoft recently announced a > multi-billion (yes, billion) dollar initiative to make NT *the* > network operating system in 1997, and that's a whole heck of a lot of > money. It's time for small companies involved with UNIX to pool their > efforts or Bill is going to eat them all. He might eat them anyway, > in the long run, but I'd really hate to look back on this time and > reflect that we made it easy for him to do so by squabbling amongst > ourselves while Microsoft raced ahead. I think the UNIX community has > already done far too much of that already and it's time for a change. {386,Net,Free,Open}BSD. :-( What you are saying is certainly wise, I have no doubts about that. I am just a little dismayed at how things have developed... we could really use this advice with respect to our multiple working OS development groups. :-( ... JG From owner-freebsd-hackers Sat Sep 21 13:40:56 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA08318 for hackers-outgoing; Sat, 21 Sep 1996 13:40:56 -0700 (PDT) Received: from Mail.IDT.NET (mail.idt.net [198.4.75.205]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA08282 for ; Sat, 21 Sep 1996 13:40:51 -0700 (PDT) Received: from sequoia (ppp-12.ts-1.mlb.idt.net [169.132.71.12]) by Mail.IDT.NET (8.7.4/8.7.3) with SMTP id QAA04250; Sat, 21 Sep 1996 16:39:58 -0400 (EDT) Message-ID: <324452DE.2993@mail.idt.net> Date: Sat, 21 Sep 1996 16:41:02 -0400 From: Gary Corcoran Reply-To: garycorc@mail.idt.net X-Mailer: Mozilla 3.0 (WinNT; U) MIME-Version: 1.0 To: Terry Lambert CC: smpatel@umiacs.umd.edu, janus@freegate.net, hackers@FreeBSD.org Subject: Re: Plug and Play naivety References: <199609211938.MAA02521@phaeton.artisoft.com> 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: > > > Is the (eventual) plan for the PnP code to allow kernel-config-specified > > values to override those programmed by a PnP BIOS? This would be > > desirable to allow for fixing things when the BIOS botches its > > automatic assignments (and/or I just want to specify, for example, my > > own priorities for IRQs). > > One would hope the kernel were capable of automatic assignments. The > less user involvement, the better. > > Terry Lambert > terry@lambert.org > --- Sure, if all assignments _can_ be handled automatically, I'm all for it. But I would like to have the _option_ of overriding automatic assignments in case things go wrong. I've wasted too many hours fighting "all-knowing" PnP BIOSes and Win95, which, had I the option of setting things to what *I* said, would have solved my problems in 2 minutes... Gary From owner-freebsd-hackers Sat Sep 21 15:01:24 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA12330 for hackers-outgoing; Sat, 21 Sep 1996 15:01:24 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA12303 for ; Sat, 21 Sep 1996 15:01:15 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.eu.org [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id AAA12978 for ; Sun, 22 Sep 1996 00:01:06 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id AAA05250 for freebsd-hackers@freefall.freebsd.org; Sun, 22 Sep 1996 00:00:41 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.Beta.4/keltia-uucp-2.9) id XAA02192; Sat, 21 Sep 1996 23:57:16 +0200 (MET DST) Message-Id: <199609212157.XAA02192@keltia.freenix.fr> Date: Sat, 21 Sep 1996 23:57:16 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: freebsd-hackers@freefall.freebsd.org Subject: Re: /etc/issue In-Reply-To: <199609211658.SAA22796@gilberto.physik.rwth-aachen.de>; from Christoph Kukulies on Sep 21, 1996 18:58:08 +0200 References: <199609211658.SAA22796@gilberto.physik.rwth-aachen.de> X-Mailer: Mutt 0.43g Mime-Version: 1.0 X-Operating-System: FreeBSD 2.2-CURRENT ctm#2490 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Christoph Kukulies: > Is this an issue? Should FreeBSD have such a file? Or is there an > equivalent? No. Yes IMO and No. I have patches to implement an "if=/etc/issue" keyword in /etc/gettydefs for getty. They may have to be adjusted to the termios-ified getty we now have. I never committed them because each time I raised this issue (:-)) no one seemed interested... If there are really some people interested, I'll merge my old changes into the new getty. The patches were made in 1993 for 386BSD... -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #0: Sat Sep 21 00:18:27 MET DST 1996 From owner-freebsd-hackers Sat Sep 21 15:04:03 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA13327 for hackers-outgoing; Sat, 21 Sep 1996 15:04:03 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA13271 for ; Sat, 21 Sep 1996 15:03:57 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA02699; Sat, 21 Sep 1996 15:02:21 -0700 From: Terry Lambert Message-Id: <199609212202.PAA02699@phaeton.artisoft.com> Subject: Re: Plug and Play naivety To: garycorc@mail.idt.net Date: Sat, 21 Sep 1996 15:02:21 -0700 (MST) Cc: terry@lambert.org, smpatel@umiacs.umd.edu, janus@freegate.net, hackers@FreeBSD.org In-Reply-To: <324452DE.2993@mail.idt.net> from "Gary Corcoran" at Sep 21, 96 04:41: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 > > One would hope the kernel were capable of automatic assignments. The > > less user involvement, the better. > > Sure, if all assignments _can_ be handled automatically, I'm all for it. > > But I would like to have the _option_ of overriding automatic > assignments in case things go wrong. I've wasted too many hours > fighting > "all-knowing" PnP BIOSes and Win95, which, had I the option of setting > things to what *I* said, would have solved my problems in 2 minutes... The *kernel* would override the BIOS instead of needing a human to do the job by mentally setting jumpers (worse than non-PnP hardware, in that case, if you ask me). 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 Sat Sep 21 15:32:48 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA24150 for hackers-outgoing; Sat, 21 Sep 1996 15:32:48 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA24130 for ; Sat, 21 Sep 1996 15:32:44 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id PAA27363; Sat, 21 Sep 1996 15:32:11 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma027361; Sat Sep 21 15:31:57 1996 Received: (from archie@localhost) by bubba.whistle.com (8.7.5/8.6.12) id PAA04375; Sat, 21 Sep 1996 15:31:57 -0700 (PDT) From: Archie Cobbs Message-Id: <199609212231.PAA04375@bubba.whistle.com> Subject: Re: xcdplayer SCSI bus hang In-Reply-To: <199609210140.SAA00357@bubba.whistle.com> from Archie Cobbs at "Sep 20, 96 06:40:31 pm" To: archie@whistle.com (Archie Cobbs) Date: Sat, 21 Sep 1996 15:31:57 -0700 (PDT) Cc: freebsd-hackers@freebsd.org, julian@whistle.com (Julian Elischer) 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 > Doing anything non-trivial with "xcdplayer", like pressing the > "pause" button, causes what looks like a SCSI bus hang. The > SCSI bus LED is lit and the box completely locks up. > > This bug has been around since before 2.1 was released, on this > machine, anyway. > > Does this happen to anyone else? If not, it's probably because > of a bogus CD-ROM drive. Anyone know any more? > > Thanks, > -Archie > > Equipment: > > Buslogic 946 SCSI host adapter > CHINON CD-ROM CDS-535 Q20 > FreeBSD 2.2-960801-SNAP Update: according to Julian E. this is a combination of a bug in the Buslogic board (which causes it to crash/hang) and a bug in the driver (which fails to reset the board properly). The message on the console just before the hang is "bt0: Try to abort". -Archie ___________________________________________________________________________ Archie L. Cobbs, archie@whistle.com * Whistle Communications Corporation From owner-freebsd-hackers Sat Sep 21 15:51:44 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA01478 for hackers-outgoing; Sat, 21 Sep 1996 15:51:44 -0700 (PDT) Received: from night.primate.wisc.edu (night.primate.wisc.edu [144.92.43.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA01444 for ; Sat, 21 Sep 1996 15:51:35 -0700 (PDT) Received: by night.primate.wisc.edu; id RAA16983; 8.6.10/41.8; Sat, 21 Sep 1996 17:55:21 -0500 Message-Id: <199609212255.RAA16983@night.primate.wisc.edu> Date: Sat, 21 Sep 1996 17:55:20 -0500 From: dubois@primate.wisc.edu (Paul DuBois) To: brandon@glacier.cold.org (Brandon Gillespie) Cc: freebsd-hackers@freebsd.org Subject: Re: splash-page on bootup.. In-Reply-To: ; from Brandon Gillespie on Sep 21, 1996 13:01:19 -0600 References: X-Mailer: Mutt 0.43 Mime-Version: 1.0 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > What would this accomplish? Quite a bit IMHO. People have horrible > pre-conceptions in their mind about Free software, especially if they are > from the MSDOS/Windows arena because a LARGE majority of the free software > has been (and is still likely)--frankly put--virus infected crap. Coming Uh, what? I'm not MS fan, but the majority of free software for the platform is virus-infected? From owner-freebsd-hackers Sat Sep 21 16:06:13 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA07953 for hackers-outgoing; Sat, 21 Sep 1996 16:06:13 -0700 (PDT) Received: from po2.glue.umd.edu (po2.glue.umd.edu [129.2.128.45]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA07920 for ; Sat, 21 Sep 1996 16:06:10 -0700 (PDT) Received: from modem.eng.umd.edu (modem.eng.umd.edu [129.2.98.187]) by po2.glue.umd.edu (8.7.5/8.7.3) with ESMTP id TAA00125 for ; Sat, 21 Sep 1996 19:06:07 -0400 (EDT) Received: from localhost (chuckr@localhost) by modem.eng.umd.edu (8.7.5/8.7.3) with SMTP id TAA07942 for ; Sat, 21 Sep 1996 19:06:07 -0400 (EDT) X-Authentication-Warning: modem.eng.umd.edu: chuckr owned process doing -bs Date: Sat, 21 Sep 1996 19:06:06 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@modem.eng.umd.edu To: FreeBSD-Hackers Subject: Using disklabel Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Help! I need to set up 2 partitions (only 2) on a st42100N seagate scsi disk, size 1812MB. I tried to set up partitions e: and f:, but disklabel kept on telling me (after a frustrating editing session when it kept on getting the default scsi sizes wrong) that my partition names were invalid, and that I had an unused partition d. I only want 2 partitions, this isn't a boot disk. I want them equal in size. Fdisk would not help me by providing good scsi defaults, so I chose 64 heads and 32 sectors/track as scsi default, and for the 1812 MB disk that gave me 1812 cylinders. Would be nice if disklabel could have read that, but how do I get disklabel to take my sector defs? I haven't yet newfs'ed it yet. Here are my entries to disklabel, that failed: a: 0 0 unused 0 0 0 # (Cyl. 0 - 0*) d: 0 0 unused 0 0 0 # (Cyl. 0 - 0*) c: 3711990 0 unused 0 0 # (Cyl. 1 -1811*) e: 1855995 0 4.2BSD 0 0 0 # (Cyl. 1 -906*) f: 1855995 1855995 4.2BSD 0 0 0 # (Cyl. 907 -1811*) /tmp/EdDk.a003023: 26 lines, 753 characters. line 25: bad partition name line 26: bad partition name If I weren't up against a time deadline, I'd experiment more, but disklabel is really unhelpful. This is disk sd2 on an already running system, I wish I could coax the sysinstall into working on sd2. ----------------------------+----------------------------------------------- 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 n3lxx, both FreeBSD (301) 220-2114 | version 2.2 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Sat Sep 21 17:19:10 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA16960 for hackers-outgoing; Sat, 21 Sep 1996 17:19:10 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA16937 for ; Sat, 21 Sep 1996 17:19:07 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id RAA20241; Sat, 21 Sep 1996 17:18:11 -0700 (PDT) To: Joe Greco cc: julian@current1.whistle.com, Rich.Heaton@empac.com, hackers@freebsd.org Subject: Re: Job openings: Unix Network Programmers, Internet server In-reply-to: Your message of "Sat, 21 Sep 1996 15:37:56 CDT." <199609212037.PAA14080@brasil.moneng.mei.com> Date: Sat, 21 Sep 1996 17:18:11 -0700 Message-ID: <20239.843351491@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > {386,Net,Free,Open}BSD. :-( > > What you are saying is certainly wise, I have no doubts about that. > > I am just a little dismayed at how things have developed... we could I think you're looking at the "split" in the wrong light, or at least with what could probably be said to be the "old" view. If we re-examine the situation in today's context, we see: 386BSD: Dead. FreeBSD: Focused on Intel architecture. {Net,Open}BSD: In conflict. Which narrows the problem by quite a bit (and I don't know what to do about the fact that NetBSD and OpenBSD are now trying to occupy the same niche - that truly is a waste). FreeBSD is not in conflict with NetBSD because NetBSD is focused on the different goal of providing a cross platform solution, and it could in fact be said that NetBSD *helped* FreeBSD by giving the ALPHA, Sparc, 68K and other folks a place to go so they didn't pressure the FreeBSD developers into doing a whole bunch of porting work they weren't ready for (or much into the idea of doing). That's not to say there isn't redundancy in the {Net,Free}BSD split which could be eliminated, but I believe that this will slowly improve as various people continue the work they've already started in keeping the two trees in sync. However, it's still not bifurcated *BSD development which worries me. That, despite its occasionally rocky moments, has always been a matter of engineers talking to other engineers, all of whom also pretty much know one another. Getting them to work cooperatively together is child's play compared to the task of getting various commercial entities, many of whom are also hugely paranoid about giving away their "valuable secrets", into overcoming mutual distrust and developer ignorance ("Huh? There are other people doing what I'm doing? How was I supposed to know that when I never leave my office or have time to read the developer's lists?"). Get the vertical market people talking to one another and you've really got something. Jordan From owner-freebsd-hackers Sat Sep 21 17:19:15 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA17015 for hackers-outgoing; Sat, 21 Sep 1996 17:19:15 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA16909 for ; Sat, 21 Sep 1996 17:19:05 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id RAA16883; Sat, 21 Sep 1996 17:19:00 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id RAA01976; Sat, 21 Sep 1996 17:18:15 -0700 (PDT) Message-Id: <199609220018.RAA01976@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Chuck Robey cc: FreeBSD-Hackers Subject: Re: Using disklabel In-reply-to: Your message of Sat, 21 Sep 96 19:06:06 -0400. Date: Sat, 21 Sep 1996 17:18:15 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Help! I need to set up 2 partitions (only 2) on a st42100N seagate scsi >disk, size 1812MB. I tried to set up partitions e: and f:, but disklabel >kept on telling me (after a frustrating editing session when it kept on >getting the default scsi sizes wrong) that my partition names were >invalid, and that I had an unused partition d. [...] >Here are my entries to disklabel, that failed: > a: 0 0 unused 0 0 0 # (Cyl. 0 - 0*) > d: 0 0 unused 0 0 0 # (Cyl. 0 - 0*) > c: 3711990 0 unused 0 0 # (Cyl. 1 -1811*) > e: 1855995 0 4.2BSD 0 0 0 # (Cyl. 1 -906*) > f: 1855995 1855995 4.2BSD 0 0 0 # (Cyl. 907 -1811*) >/tmp/EdDk.a003023: 26 lines, 753 characters. >line 25: bad partition name >line 26: bad partition name You left off the most important part. What does it say for number of partitions immediately before the "a:" line? For partitions through "f", you'll need that to say at least "6 partitions". ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-hackers Sat Sep 21 17:20:39 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA17941 for hackers-outgoing; Sat, 21 Sep 1996 17:20:39 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA17919; Sat, 21 Sep 1996 17:20:36 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id RAA20256; Sat, 21 Sep 1996 17:20:02 -0700 (PDT) To: sos@FreeBSD.org cc: brandon@glacier.cold.org (Brandon Gillespie), freebsd-hackers@FreeBSD.org Subject: Re: splash-page on bootup.. In-reply-to: Your message of "Sat, 21 Sep 1996 22:25:48 +0200." <199609212025.WAA02313@DeepCore.dk> Date: Sat, 21 Sep 1996 17:20:02 -0700 Message-ID: <20253.843351602@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Do we have any graphic designers here that could draw a nice > FreeBSD "graphics for the dummies" entry pic ?? in say > 320x200x256 or 640x480x16, then I'll do the code that makes > it appear :) Just make it optional, that's all I ask. ;-) Jordan From owner-freebsd-hackers Sat Sep 21 17:43:35 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA02841 for hackers-outgoing; Sat, 21 Sep 1996 17:43:35 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA02804 for ; Sat, 21 Sep 1996 17:43:32 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id RAA17210; Sat, 21 Sep 1996 17:42:44 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id RAA02293; Sat, 21 Sep 1996 17:41:58 -0700 (PDT) Message-Id: <199609220041.RAA02293@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Tarun Pinto Pereira cc: hackers@freebsd.org Subject: Re: supoted platforms In-reply-to: Your message of Sat, 21 Sep 96 15:36:56 -0400. <1.5.4.32.19960921193656.00671dd8@wow.net> Date: Sat, 21 Sep 1996 17:41:58 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >is it possible to send me a list of platforms supported be freebsd? No. What platforms are you interested in? Have you checked out http://www.freebsd.org/? ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-hackers Sat Sep 21 17:46:22 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA04487 for hackers-outgoing; Sat, 21 Sep 1996 17:46:22 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA04461 for ; Sat, 21 Sep 1996 17:46:19 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id RAA17253; Sat, 21 Sep 1996 17:46:22 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id RAA02243; Sat, 21 Sep 1996 17:39:53 -0700 (PDT) Message-Id: <199609220039.RAA02243@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Joe Greco cc: jkh@time.cdrom.com (Jordan K. Hubbard), julian@current1.whistle.com, Rich.Heaton@empac.com, hackers@freebsd.org Subject: Re: Job openings: Unix Network Programmers, Internet server In-reply-to: Your message of Sat, 21 Sep 96 15:37:56 -0500. <199609212037.PAA14080@brasil.moneng.mei.com> Date: Sat, 21 Sep 1996 17:39:25 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Richard told me yesterday that Microsoft recently announced a >> multi-billion (yes, billion) dollar initiative to make NT *the* >> network operating system in 1997, and that's a whole heck of a lot of >> money. It's time for small companies involved with UNIX to pool their >> efforts or Bill is going to eat them all. He might eat them anyway, [...] >What you are saying is certainly wise, I have no doubts about that. >I am just a little dismayed at how things have developed... we could >really use this advice with respect to our multiple working OS development >groups. :-( What might be almost as helpful is for people who know what they want, and why they want it, to file bug reports, requests, and such with Microsoft ("telnet sucks, please fix it", "give us a single-rooted filesystem", "give us a Real Shell", etc.). That way, if NT becomes the defacto commercial server OS (which it has a very good chance of doing), at least it will be something that Unix advocates won't mind using so much. It's pretty hard to get some of my bug reports and suggestions taken seriously when they think some of this stuff doesn't matter to the majority of people. For example, two I filed recently on problems with NT telnet and NT ftp. They agreed they were broken, but told me that they were pretty far down the priority list. Microsoft is very sensative to their Net presence, and whatever they deem as threats to it. Microsoft IS also interested in making NT a really great OS. We just have to tell them what we consider "really great" to be. Please no MS flames or on-going MS-bashing threads on the public list. (If that's what you want to do, flame me privately.) I mean this as a serious suggestion. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-hackers Sat Sep 21 17:50:24 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA06872 for hackers-outgoing; Sat, 21 Sep 1996 17:50:24 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA06832 for ; Sat, 21 Sep 1996 17:50:20 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id KAA00135; Sun, 22 Sep 1996 10:46:57 +1000 Date: Sun, 22 Sep 1996 10:46:57 +1000 From: Bruce Evans Message-Id: <199609220046.KAA00135@godzilla.zeta.org.au> To: freebsd-hackers@freefall.freebsd.org, gilham@csl.sri.com Subject: Re: Problem with rpcgen (resolved, sort of) Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >At any rate, after considerable head-scratching I've traced the >problem to GNU CPP's habit of removing the backslash/newline pairs in >all circumstances. It turns out that rpcgen runs cpp as a front-end, >and on FreeBSD, unlike SunOS and Solaris 2, the GNU preprocessor is >used. So if anyone had tried to investingate this behavior, there's >no need. rpcgen runs /usr/libexec/cpp, which is an ANSI standard cpp, so it is required to remove backslash/newline pairs in all circumstances. rpcgen should probably run /usr/bin/cpp or invoke /usr/lib/cpp with the -traditional flag to get a traditional cpp. /usr/bin/cpp invokes /usr/libexec/cpp with several other options: /usr/libexec/cpp -traditional -D__GNUC__=2 -$ -nostdinc -I/usr/include `-D__GNUC__=2' gives the main predefine that cc would give. #ifdefs that depend on other predefines will break. -$ stops `$' from being an ordinary character in identifiers. `-nostdinc -I/usr/' restricts the #include search to /usr/include (which is close to the default anyway, since FreeBSD changes the gnu defaults to just /usr/include:/usr/include/g++). None of these options except possibly -$ is quite right for preprocessing non-C code. Bruce From owner-freebsd-hackers Sat Sep 21 18:02:57 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA12651 for hackers-outgoing; Sat, 21 Sep 1996 18:02:57 -0700 (PDT) Received: from po1.glue.umd.edu (po1.glue.umd.edu [129.2.128.44]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA12625 for ; Sat, 21 Sep 1996 18:02:54 -0700 (PDT) Received: from modem.eng.umd.edu (modem.eng.umd.edu [129.2.98.187]) by po1.glue.umd.edu (8.7.5/8.7.3) with ESMTP id VAA28723; Sat, 21 Sep 1996 21:02:51 -0400 (EDT) Received: from localhost (chuckr@localhost) by modem.eng.umd.edu (8.7.5/8.7.3) with SMTP id VAA08017; Sat, 21 Sep 1996 21:02:51 -0400 (EDT) X-Authentication-Warning: modem.eng.umd.edu: chuckr owned process doing -bs Date: Sat, 21 Sep 1996 21:02:50 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@modem.eng.umd.edu To: "Michael L. VanLoon -- HeadCandy.com" cc: FreeBSD-Hackers Subject: Re: Using disklabel In-Reply-To: <199609220018.RAA01976@MindBender.serv.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 21 Sep 1996, Michael L. VanLoon -- HeadCandy.com wrote: > > >Help! I need to set up 2 partitions (only 2) on a st42100N seagate scsi > >disk, size 1812MB. I tried to set up partitions e: and f:, but disklabel > >kept on telling me (after a frustrating editing session when it kept on > >getting the default scsi sizes wrong) that my partition names were > >invalid, and that I had an unused partition d. > [...] > >Here are my entries to disklabel, that failed: > > a: 0 0 unused 0 0 0 # (Cyl. 0 - 0*) > > d: 0 0 unused 0 0 0 # (Cyl. 0 - 0*) > > c: 3711990 0 unused 0 0 # (Cyl. 1 -1811*) > > e: 1855995 0 4.2BSD 0 0 0 # (Cyl. 1 -906*) > > f: 1855995 1855995 4.2BSD 0 0 0 # (Cyl. 907 -1811*) > >/tmp/EdDk.a003023: 26 lines, 753 characters. > >line 25: bad partition name > >line 26: bad partition name > > You left off the most important part. What does it say for number of > partitions immediately before the "a:" line? For partitions through > "f", you'll need that to say at least "6 partitions". I read the man page 5 times, and didn't see that. Next time you come to the DC area, remember you've a free steak dinner to collect! Thanks! ----------------------------+----------------------------------------------- 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 n3lxx, both FreeBSD (301) 220-2114 | version 2.2 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Sat Sep 21 18:18:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA18045 for hackers-outgoing; Sat, 21 Sep 1996 18:18:34 -0700 (PDT) Received: from alpo.whistle.com (s205m1.whistle.com [207.76.205.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA18021 for ; Sat, 21 Sep 1996 18:18:30 -0700 (PDT) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.7.5/8.7.3) with SMTP id SAA08799; Sat, 21 Sep 1996 18:16:08 -0700 (PDT) Message-ID: <324492F6.2781E494@whistle.com> Date: Sat, 21 Sep 1996 18:14:30 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: "Jordan K. Hubbard" CC: Julian Elischer , Richard Heaton , hackers@freebsd.org Subject: Re: Job openings: Unix Network Programmers, Internet server References: <11980.843326832@time.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard wrote: > > > Of course, as they are in direct competition with Whistle, > > we hope you'll talk to us too :) > > Actually, since you mention it, you guys don't have to view this > entirely as "competition" and could actually share some of the > development work in areas where there's no "competetive advantage" to > give away. we already take that view.. there is no way we are gicving away the interfaces and such. but you'll see our PPP daemon in incoming and work being done for us getting netatalk and samba and such into production quality for FreeBSD will be in those packages. empac or anyone else using FreeBSD is quite welcome to do this.. the more momentum we get as "FreeBSD is the way to go for network nodes" the better. Actually I think that there's enough space here for al of us in this segment.. there was one similar product at interop that was the size ofthe diskdrive (approx) that was running NT.. 1/ I pitty them 2/ they are the cometition 3/ they are from seattle and have a LOT of money ... I wonder if it's a coincidence? > > Richard and I talked about this yesterday, and Empac feels that things > like general PPP improvements or bug fixes to the system should not be > viewed as competition points, it being in everyone's best interest to > make FreeBSD as robust and reliable a development platform as > possible. The competetive advantages lie in what is placed on top, > not the foundation, and given that firms like Whistle and Empac are > both relatively small (certainly when compared to the Mighty > Microsoft), they'd do well to pool their resources if and whenever > possible. > > Richard told me yesterday that Microsoft recently announced a > multi-billion (yes, billion) dollar initiative to make NT *the* > network operating system in 1997, and that's a whole heck of a lot of > money. It's time for small companies involved with UNIX to pool their > efforts or Bill is going to eat them all. He might eat them anyway, > in the long run, but I'd really hate to look back on this time and > reflect that we made it easy for him to do so by squabbling amongst > ourselves while Microsoft raced ahead. I think the UNIX community has > already done far too much of that already and it's time for a change. > > Perhaps we could set about identifying areas of common interest and > open a discussion on mutual development priorities? I think that htere are enough ares to keep us busy.. I'm about to revamp the networking lower end for ATM/Frame/ISDN I'll work with anyone who's intersetd.. I'll be taking the FreeBSD ATM crew the BISDN crew and the NetBSD/OPENBSD ATM crew's stuff, and our own work here and hopefully drawing a common thread through it all. I have already got a good commmunication with them and hope to expand it.. > > Jordan From owner-freebsd-hackers Sat Sep 21 18:30:26 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA24230 for hackers-outgoing; Sat, 21 Sep 1996 18:30:26 -0700 (PDT) Received: from alpo.whistle.com (s205m1.whistle.com [207.76.205.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA24200 for ; Sat, 21 Sep 1996 18:30:22 -0700 (PDT) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.7.5/8.7.3) with SMTP id SAA08890; Sat, 21 Sep 1996 18:28:50 -0700 (PDT) Message-ID: <324495EC.446B9B3D@whistle.com> Date: Sat, 21 Sep 1996 18:27:08 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Brandon Gillespie CC: freebsd-hackers@freebsd.org Subject: Re: splash-page on bootup.. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Brandon Gillespie wrote: > the system probes. At first I was not sure what the problem was, until I > realized he had never seen this type of behaviour before, and assumed it > was errors or some other similar problem--and even after a bit of > explaning he was still somewhat uncomfortable with it. > On the interjet we have a 128x64 bit LCD as the 'console' we have a module that we link in with a SYSINIT entry soitidoesn't need any patches anwhere else.. it just throws up a bitmap of our logo. it wouldn't be hard to do similar for a screen it just needs to be an appropriatly compressed file.. and an 'expander'.. of course I wouldn't want that bloat in MY system, but yes.. From owner-freebsd-hackers Sat Sep 21 20:48:15 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA02521 for hackers-outgoing; Sat, 21 Sep 1996 20:48:15 -0700 (PDT) Received: from w2xo.pgh.pa.us (w2xo.pgh.pa.us [206.210.70.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id UAA02487; Sat, 21 Sep 1996 20:48:10 -0700 (PDT) Received: (from durham@localhost) by w2xo.pgh.pa.us (8.6.12/8.6.9) id XAA01703; Sat, 21 Sep 1996 23:45:39 -0400 Date: Sat, 21 Sep 1996 23:45:39 -0400 Message-ID: X-Mailer: XFMail 0.3-beta [p0] on FreeBSD In-Reply-To: <20253.843351602@time.cdrom.com> Reply-To: durham@w2xo.pgh.pa.us Organization: Very little From: Jim Durham To: "Jordan K. Hubbard" Subject: Re: splash-page on bootup.. Cc: , Brandon Gillespie , Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat Sep 21 21:20:02 1996 Jordan K. Hubbard wrote: >>> Do we have any graphic designers here that could draw a nice >> FreeBSD "graphics for the dummies" entry pic ?? in say >> 320x200x256 or 640x480x16, then I'll do the code that makes >> it appear :) > >Just make it optional, that's all I ask. ;-) > > Jordan From owner-freebsd-hackers Sat Sep 21 20:49:38 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA03088 for hackers-outgoing; Sat, 21 Sep 1996 20:49:38 -0700 (PDT) Received: from w2xo.pgh.pa.us (w2xo.pgh.pa.us [206.210.70.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id UAA03052; Sat, 21 Sep 1996 20:49:33 -0700 (PDT) Received: (from durham@localhost) by w2xo.pgh.pa.us (8.6.12/8.6.9) id XAA01717; Sat, 21 Sep 1996 23:47:21 -0400 Date: Sat, 21 Sep 1996 23:47:21 -0400 Message-ID: X-Mailer: XFMail 0.3-beta [p0] on FreeBSD In-Reply-To: <20253.843351602@time.cdrom.com> Reply-To: durham@w2xo.pgh.pa.us Organization: Very little From: Jim Durham To: "Jordan K. Hubbard" Subject: Re: splash-page on bootup.. Cc: , Brandon Gillespie , Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat Sep 21 21:20:02 1996 Jordan K. Hubbard wrote: >>> Do we have any graphic designers here that could draw a nice >> FreeBSD "graphics for the dummies" entry pic ?? in say >> 320x200x256 or 640x480x16, then I'll do the code that makes >> it appear :) > >Just make it optional, that's all I ask. ;-) > > Jordan Amen... can you imagine what would happen if the system didn't boot? No boot...no reading var/log/messages to see what happened.. IMHO setting up the root window in X to some neat FreeBSD graphic would be just fine to impress the masses. Is it really a viable objection that probe messages are construed as flakey operation? I always thought the probe messages were the sign of "gee..this is a real operating system". regards, From owner-freebsd-hackers Sat Sep 21 21:37:14 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA23846 for hackers-outgoing; Sat, 21 Sep 1996 21:37:14 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA23805 for ; Sat, 21 Sep 1996 21:37:10 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.6.12/8.6.12) with SMTP id VAA22643; Sat, 21 Sep 1996 21:37:04 -0700 Date: Sat, 21 Sep 1996 21:37:02 -0700 (PDT) From: Jaye Mathisen To: Frank Nobis cc: hackers@freebsd.org Subject: Re: Tweaking FreeBSD (2.1) and sendmail for a busy site? Or maybe, Help! , No more sendmail's. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk If you'll note in the original message, la is not the issue. The load rarely climbs over 1.0. This is something to do with # of processes. I point out to that it appears that if la was the issue, there would be Connection Refused, rather than no connection at all. On 21 Sep 1996, Frank Nobis wrote: > Date: 21 Sep 1996 09:43:13 +0200 > From: Frank Nobis > To: Jaye Mathisen > Cc: hackers@freebsd.org > Subject: Re: Tweaking FreeBSD (2.1) and sendmail for a busy site? Or maybe, Help! , No more sendmail's. > > >>>>> "Jaye" == Jaye Mathisen writes: > > > Jaye> What else should I check? > > Sendmail has two parameters at which it starts to auto queue and later > to reject incomming messages. > > >From my sendmail.cf > > # load avg at which to auto-queue msgs > Ox3 > > # load avg at which to auto-reject connections > OX2 > > Have a look at these parms in your sendmail.cf > > Regards > Frank > -- > Frank Nobis Email: fn@Radio-do.de PGP AVAILABLE > Landgrafenstr. 130 dg3dcn http://www.radio-do.de/~fn/ > 44139 Dortmund Powered by FreeBSD Fax: +49 231 7213816 > From owner-freebsd-hackers Sat Sep 21 21:41:22 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA26738 for hackers-outgoing; Sat, 21 Sep 1996 21:41:22 -0700 (PDT) Received: from sasami.jurai.net (root@sasami.jurai.net [206.151.208.162]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA26714 for ; Sat, 21 Sep 1996 21:41:20 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.7.5/8.7.3) with SMTP id XAA12259; Sat, 21 Sep 1996 23:42:47 -0500 (CDT) Date: Sat, 21 Sep 1996 23:42:47 -0500 (CDT) From: "Matthew N. Dodd" To: Ollivier Robert cc: freebsd-hackers@freefall.freebsd.org Subject: Re: /etc/issue In-Reply-To: <199609212157.XAA02192@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 21 Sep 1996, Ollivier Robert wrote: > I never committed them because each time I raised this issue (:-)) no one > seemed interested... > > If there are really some people interested, I'll merge my old changes into > the new getty. The patches were made in 1993 for 386BSD... Um... "me too!" :) | Matthew N. Dodd | winter@jurai.net | http://www.jurai.net/~winter | | Technical Manager | mdodd@intersurf.net | http://www.intersurf.net | | InterSurf Online | "Welcome to the net Sir, would you like a handbasket?"| From owner-freebsd-hackers Sat Sep 21 23:01:39 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA21451 for hackers-outgoing; Sat, 21 Sep 1996 23:01:39 -0700 (PDT) Received: from glacier.cold.org (glacier.cold.org [206.81.134.54]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA21425 for ; Sat, 21 Sep 1996 23:01:37 -0700 (PDT) Received: (from brandon@localhost) by glacier.cold.org (8.7.5/8.7.3) id AAA14676; Sun, 22 Sep 1996 00:04:13 -0600 (MDT) Date: Sun, 22 Sep 1996 00:04:13 -0600 (MDT) From: Brandon Gillespie To: freebsd-hackers@freebsd.org Subject: Re: splash-page on bootup.. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 21 Sep 1996, Jim Durham wrote: > Amen... can you imagine what would happen if the system didn't > boot? No boot...no reading var/log/messages to see what happened.. Uhrm, it was nestled at the end of a paragraph, but I figured it would work like 95 where a simply hitting 'tab' or something similar would toggle the two windows. > IMHO setting up the root window in X to some neat FreeBSD graphic > would be just fine to impress the masses. > > Is it really a viable objection that probe messages are construed as > flakey operation? I always thought the probe messages were the sign > of "gee..this is a real operating system". As is my opinion, unfortunately many of the people who may agree are not in a position to decide which OS goes on a server. Joe Greco : > A system that looks and feels professional to me is a system that does > not hide every aspect of what the hell it is doing from me. *nod* and I agree; but often those making decisions have no idea about the true nature of the OS, just how many warm fuzzies it gives them. > Microsoft Windows 95 is unprofessional. It is slick in many ways... but > just try to get it to do what you want, when you really know you want to > do what it doesn't want to let you do. Its rather irrelevant, if the owner feels better about 95 (or more appropriately NT) because it feels safer--he will use NT and thats the end of discussion. My point is to try and make it easier for non-FreeBSD (read: Microsoft Junkies) to accept it as an alternative, great! What I think would work best for this is a simple kernel option: options SPLASH_PAGE ## make the microsoft junkies feel good Which would be in kernel.GENERIC but which is easilly removed by anybody who cares with a simple recompile. *shrug* Its just a thought afterall ;) Paul DuBois : > Uh, what? I'm not MS fan, but the majority of free software for the > platform is virus-infected? No, that is simply a common opinion in that crowd--I work with people who use NT and 95 daily (and whos primary involvement with 'unix' is through some aromatic SCO product), its a nightmare trying to convince them that Free does not mean 'virus-infected and shitty'. Enjoy; -Brandon Gillespie From owner-freebsd-hackers Sat Sep 21 23:13:08 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA28792 for hackers-outgoing; Sat, 21 Sep 1996 23:13:08 -0700 (PDT) Received: (from hsu@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA28775; Sat, 21 Sep 1996 23:13:07 -0700 (PDT) Date: Sat, 21 Sep 1996 23:13:07 -0700 (PDT) From: Jeffrey Hsu Message-Id: <199609220613.XAA28775@freefall.freebsd.org> To: jb@cimlogic.com.au Subject: Re: libc_r bug Cc: hackers@FreeBSD.org Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > _thread_fd_table_init() just sets up > the table for a fd. fds 0, 1 and 2 don't have to be valid. Since we can't tell whether a given fd might need a call to _thread_fd_table_init() or not, the correctness before all else principle would argue for either pre-allocating all the fd entries or doing it on demand by placing a call to _thread_fd_table_init() in write() and all the other places where it might be needed. Of these two, I prefer the second. What about you? From owner-freebsd-hackers Sat Sep 21 23:35:22 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA13687 for hackers-outgoing; Sat, 21 Sep 1996 23:35:22 -0700 (PDT) Received: from alpo.whistle.com (s205m1.whistle.com [207.76.205.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA13645 for ; Sat, 21 Sep 1996 23:35:17 -0700 (PDT) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.7.5/8.7.3) with SMTP id XAA10999; Sat, 21 Sep 1996 23:34:06 -0700 (PDT) Message-ID: <3244DD7A.FF6D5DF@whistle.com> Date: Sat, 21 Sep 1996 23:32:26 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Brandon Gillespie CC: freebsd-hackers@freebsd.org Subject: Re: splash-page on bootup.. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Brandon Gillespie wrote: > > No, that is simply a common opinion in that crowd--I work with people who > use NT and 95 daily (and whos primary involvement with 'unix' is through > some aromatic SCO product), its a nightmare trying to convince them that > Free does not mean 'virus-infected and shitty'. I agree that FreeBSD suffers from a naming problem.. I'd like to see us make a version called SERVIX-PRO or something. :) (yeah I just noticed that ... I surprised myself when I pronounced it) but you get the Idea.. > > Enjoy; > > -Brandon Gillespie From owner-freebsd-hackers Sat Sep 21 23:48:54 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA22317 for hackers-outgoing; Sat, 21 Sep 1996 23:48:54 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA22283 for ; Sat, 21 Sep 1996 23:48:51 -0700 (PDT) Received: from rover.village.org (localhost [127.0.0.1]) by rover.village.org (8.7.6/8.6.6) with ESMTP id AAA00373; Sun, 22 Sep 1996 00:47:59 -0600 (MDT) Message-Id: <199609220647.AAA00373@rover.village.org> To: Julian Elischer Subject: Re: splash-page on bootup.. Cc: Brandon Gillespie , freebsd-hackers@freebsd.org In-reply-to: Your message of "Sat, 21 Sep 1996 23:32:26 PDT." <3244DD7A.FF6D5DF@whistle.com> References: <3244DD7A.FF6D5DF@whistle.com> Date: Sun, 22 Sep 1996 00:47:58 -0600 From: Warner Losh Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <3244DD7A.FF6D5DF@whistle.com> Julian Elischer writes: : I'd like to see us make a version called SERVIX-PRO or something. I'd hate to see what *THAT* os would splash up on the screen at boot time :-) Warner