From owner-freebsd-hackers Sun Sep 28 00:05:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA13537 for hackers-outgoing; Sun, 28 Sep 1997 00:05:26 -0700 (PDT) Received: from cedb.dpcsys.com (cedb.dpcsys.com [206.16.184.4]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA13520 for ; Sun, 28 Sep 1997 00:05:17 -0700 (PDT) Received: from localhost (dan@localhost) by cedb.dpcsys.com (8.8.5/8.8.2) with SMTP id HAA00716 for ; Sun, 28 Sep 1997 07:05:15 GMT Date: Sun, 28 Sep 1997 00:05:15 -0700 (PDT) From: Dan Busarow To: hackers@freebsd.org Subject: Problems with diskless Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm having problems building a 2.2.2 diskless client, here are the symptoms and config files I thing are relevant. It finds the bootp and tftp servers, loads the kernel and starts the boot. Right after apm0: disabled, not probed. NFS SWAP: 206.16.184.1.4:/u/export/rootfs/reg01 NFS ROOT: 206.16.184.4:/u/export/swapfs I get exec /sbin/init: error 13 followed by tries on /sbin/oinit ... and an eventual panic I have looked at all the diskless stuff I could find plus 2 years worth of list archives on the subject. I think I have every thing correct but obviously I don't. Where did I f up? The /etc/fstab in /u/export/rootfs/reg01 is cedb:/u/export/rootfs/reg01/etc $ cat fstab # Device Mountpoint FStype Options Dump Pass# 206.16.184.4:/u/export/swapfs none nfs rw 0 0 206.16.184.4:/u/export/rootfs/reg01 / nfs rw 0 0 proc /proc procfs rw 0 0 206.16.184.4:/u/export/X11R6 /usr/X11R6 nfs rw 0 0 cedb:/u/export/rootfs/reg01/etc $ The X11R6 fs is exported on its own since this started as an IDE ZIP system where only X needed to be NFS mounted. (see other ZIP thread) In /tftpboot/freebsd.206.16.184.101 I have cedb:/tftpboot $ cat freebsd.206.16.184.101 kernel /kernel # this seemed to be needed though I don't see why rootfs 206.16.184.4:/u/export/rootfs/reg01 rootopts rsize=1024,wsize=1024 swapfs 206.16.184.4:/u/export/swapfs swapopts rsize=1024,wsize=1024 swapsize 10000 hostname reg01.dpcsys.com cedb:/tftpboot $ Without the kernel /kernel directive it tries to use /usr/boot//u/export/rootfs/reg01/kernel but I dont see where it picks the /usr/boot/ up from ?!? The exported dirs cedb:/u/export $ ls -l total 0 drwxr-xr-x 7 root root 96 Sep 2 19:23 X11R6 drwxr-xr-x 3 root root 96 Sep 27 17:02 rootfs drwxr-xr-x 2 root root 96 Sep 27 16:46 swapfs cedb:/u/export $ Swap is cedb:/u/export $ ls -l swapfs total 20000 -rw-r--r-- 1 root root 10240000 Sep 27 16:46 swap.206.16.184.101 cedb:/u/export $ On to NFS. The server is an SVR4 box (Unixware 2.1). Sorry, I can't change this :) >From share cedb:/var/adm/log $ share x11r6 /u/export/X11R6 rw "X11R6" root /u/export/rootfs rw,root=reg01 "root" swap /u/export/swapfs rw,root=reg01 "swap" cedb:/var/adm/log $ When the diskless client tries to connect (from /var/adm/log/osmlog) Sep 27 23:17:37 inetd[275]: got SC_ENABLE message NFS request from an unprivileged port nfs_server: weak authentication NFS request from an unprivileged port nfs_server: weak authentication NFS request from an unprivileged port nfs_server: weak authentication NFS request from an unprivileged port nfs_server: weak authentication Sound: DMA (output) timed out - IRQ/DRQ config error? No times but that was the diskless client. But the mounts succeeded. From dfsmounts cedb:/var/adm/log $ dfmounts RESOURCE SERVER PATHNAME CLIENTS - cedb /u/export/rootfs/reg01 reg01.dpcsys.com - cedb /u/export/swapfs reg01.dpcsys.com cedb:/var/adm/log $ Does anyone have any ideas here? Many, many thanks in advance for help on this. Dan -- Dan Busarow 714 443 4172 DPC Systems / Beach.Net dan@dpcsys.com Dana Point, California 83 09 EF 59 E0 11 89 B4 8D 09 DB FD E1 DD 0C 82 From owner-freebsd-hackers Sun Sep 28 00:16:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA14381 for hackers-outgoing; Sun, 28 Sep 1997 00:16:30 -0700 (PDT) Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id AAA14360 for ; Sun, 28 Sep 1997 00:16:26 -0700 (PDT) Received: from ant.us.dell.com (ant.us.dell.com [198.64.66.34]) by bugs.us.dell.com (8.6.12/8.6.12) with SMTP id CAA28005; Sun, 28 Sep 1997 02:15:23 -0500 Message-Id: <3.0.2.32.19970927055543.006bd29c@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.2 (32) Date: Sat, 27 Sep 1997 05:55:43 -0500 To: Terry Lambert From: Tony Overfield Subject: Re: INB question Cc: hackers@FreeBSD.ORG In-Reply-To: <199709191444.HAA06050@usr07.primenet.com> References: <199709190659.QAA01136@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 02:44 PM 9/19/97 +0000, Terry Lambert wrote: >> > Yeah; that's why I picked the extended MCA DMA ports for the detect; >> > that, and I can do the probe non-destructively, with the expectation of >> > a 0 bit in my data and no hardware configuratio changes resulting. >> >> Where is the port exactly? ie. is it likely to be sat on or masked >> over by an ISA device? > >Port 0x18 is the control, and port 0x1A is the data. Port 0x18, on many systems, is an alias of port 0x08, which is the read-only DMA status register and the write-only DMA command register. Likewise, port 0x1A is often an alias of the write-only port 0x0A DMA mask register. From owner-freebsd-hackers Sun Sep 28 00:16:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA14389 for hackers-outgoing; Sun, 28 Sep 1997 00:16:32 -0700 (PDT) Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id AAA14372 for ; Sun, 28 Sep 1997 00:16:27 -0700 (PDT) Received: from ant.us.dell.com (ant.us.dell.com [198.64.66.34]) by bugs.us.dell.com (8.6.12/8.6.12) with SMTP id CAA28008; Sun, 28 Sep 1997 02:15:24 -0500 Message-Id: <3.0.2.32.19970928015842.006ce080@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.2 (32) Date: Sun, 28 Sep 1997 01:58:42 -0500 To: Terry Lambert From: Tony Overfield Subject: Re: INB question Cc: hackers@FreeBSD.ORG In-Reply-To: <199709191519.IAA07324@usr07.primenet.com> References: <19970919084937.PR22228@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 03:19 PM 9/19/97 +0000, Terry Lambert wrote: >> >> With a true plain ISA card? The boot code still uses an inb(0x84) for >> a timing loop, and it seems to get the timing well enough with it. > >This is actually bogus as hell. First, because it's an input, not >an output. I don't see anything wrong with using an input for this. >Second, port 0x84 is the Compaq POST output port, Port 0x84 is an unused DMA page register, just like 0x80, 0x85, 0x86 and others. Each of these unused registers is read/write and should have no effect, except to cause an 8-bit ISA I/O cycle. I can't speak for their BIOS, but using these registers in POST for progress codes or temporary scratch space is common for a BIOS. By the time the system begins to boot, however, they're fair game. >or >it is the EISA "Synchronize Bus Cycle Register" -- reading it only >causes an extended I/O ready cycle to occur on EISA systems, and >is more useful for flushing EISA bus master or DMA. It's not even >support on all EISA systems (ie: HiNT chipsets, which are broken in >other ways). It doesn't matter whether the port exists, the only benefit of the access is that it causes a slow ISA bus cycle, which will happen even if the port doesn't exist. >I think the "correct" timing mechanism is to output a byte to port >0x80. This is the POST code port, and it's what Linux uses. That will work too, but it seems the same to me. From owner-freebsd-hackers Sun Sep 28 00:16:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA14490 for hackers-outgoing; Sun, 28 Sep 1997 00:16:47 -0700 (PDT) Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id AAA14465 for ; Sun, 28 Sep 1997 00:16:44 -0700 (PDT) Received: from ant.us.dell.com (ant.us.dell.com [198.64.66.34]) by bugs.us.dell.com (8.6.12/8.6.12) with SMTP id CAA28011; Sun, 28 Sep 1997 02:15:25 -0500 Message-Id: <3.0.2.32.19970928020001.006ce080@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.2 (32) Date: Sun, 28 Sep 1997 02:00:01 -0500 To: Mike Smith From: Tony Overfield Subject: Re: INB question Cc: hackers@FreeBSD.ORG In-Reply-To: <199709190838.SAA02899@word.smith.net.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 06:08 PM 9/19/97 +0930, Mike Smith wrote: >> OTOH, 800000 transfers per second seem to support your figure. If the >> transfers are 16 bits wide, this would be ~ 80 % of the theoretical >> maximum. > >Read it again. 1.3MegaWords. Specifically, implying that it's making >1.3 million 16-bit I/O transactions per second, or 2.6MB/sec. > >Yes, this is substantially faster than I was expecting. 8) 16-bit ISA I/O cycles are not only wider but also faster than 8-bit ISA I/O cycles. Back when IDE drives were still attached to the ISA bus, a fast drive could transfer about 3.5MB/sec, but 2.5MB/sec or 2MB/sec was more typical. The speed depends on the chipset and the way that the BIOS programs the ISA timing options. From owner-freebsd-hackers Sun Sep 28 00:20:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA14876 for hackers-outgoing; Sun, 28 Sep 1997 00:20:41 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id AAA14856 for ; Sun, 28 Sep 1997 00:20:34 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA00267; Sun, 28 Sep 1997 09:20:33 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id JAA00677; Sun, 28 Sep 1997 09:03:16 +0200 (MET DST) Message-ID: <19970928090315.YW58243@uriah.heep.sax.de> Date: Sun, 28 Sep 1997 09:03:15 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: roberte@MEP.Ruhr-Uni-Bochum.de (Robert Eckardt) Subject: Re: ? malloc Dump ? References: <199709280112.DAA02142@ghost.mep.ruhr-uni-bochum.de> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199709280112.DAA02142@ghost.mep.ruhr-uni-bochum.de>; from Robert Eckardt on Sep 28, 1997 03:12:33 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Robert Eckardt wrote: > I'm trying to get malloc (2.2.2) to dump statistics in `malloc.out'. (Btw., this option disappeared in -current, it has been dropped in rev 1.26.) > However, I don't get the statistics. > -rw-rw-r-- 1 roberte work 0 23 Sep 23:36 malloc.out > > > What am I doing wrong ? Did you recompile malloc(3) with MALLOC_STATS? It's being explicitly #undef'ed by default. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sun Sep 28 00:39:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA15665 for hackers-outgoing; Sun, 28 Sep 1997 00:39:28 -0700 (PDT) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA15660 for ; Sun, 28 Sep 1997 00:39:23 -0700 (PDT) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.8.7/8.8.7) id JAA21944; Sun, 28 Sep 1997 09:28:37 +0200 (SAT) From: John Hay Message-Id: <199709280728.JAA21944@zibbi.mikom.csir.co.za> Subject: Re: Tulip IPX support in -current unimplemented, why ? In-Reply-To: from "Vasily V. Grechishnikov" at "Sep 27, 97 12:57:41 pm" To: bazilio@ied-vorstu.ac.ru (Vasily V. Grechishnikov) Date: Sun, 28 Sep 1997 09:28:36 +0200 (SAT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I have the following problem: > My FreeBSD box runs FreeBSD-current and it provides > IP/IPX routing between the four newtwork interfaces ( 3 NE2000 + 1 Tulip). > Sometime ago since the CVSup'ing of -current my tulip card couldn't assign > IPX address to interface by the ifconfig. I seen at /pci/if_de.c and can't > find implementation of IPX portion of code for ioctl requests > ( SIOCSIFADDR). FreeBSD actually have a common handler for some (SIOCSIFADDR, SIOCGIFADDR and SIOCSIFMTU) ethernet ioctls called ether_ioctl() which should be used by the ethernet device drivers. That way they don't need to do anything special to support IPX. The problem is drivers like the deX device that actually comes from a third party and other drivers like the epX driver which has never been updated to use the common ether_ioctl(). > After patching I can work with IPX on tulip but, the next > misteriuos thing is happen : > IPX packets to one of my networks, connected to tulip card > can't successfully forwards from the remote network : > > NET 0 NET 1 > > Broken IPX net. Good IPX net. > *--------------- Tulip ( ) NE2000 ------------* > ( FreeBSD box ) Good IPX net > +--------( )NE2000--1'st if(*)2'nd if--+ > | NetWare 3.12 | > | NET 2 | > | | > | NetWare 4.1 > | NET 3 > | > 1'st if > ( FreeBSD box) > 2'nd if NET 4 > | > +-------------NetWare 4.1 ( unreachable from tulip). > > But Netware 4.1 from unreachable network can see from a NET 1-3 :-( You don't give much information about your patch, so I can't comment on this. It might be that you just got it to not generate an error when you ifconfig it, without actually working. Then IPXrouted might pick up the IPX net and broadcast it on the other nets. That way they might learn about the broken net, without actually being able to use it. But to try and figure out what is wrong, I'll have to see the patch that you have made and also the part of your rc.conf files that have to do with IPX. John -- John Hay -- John.Hay@mikom.csir.co.za From owner-freebsd-hackers Sun Sep 28 01:34:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA18265 for hackers-outgoing; Sun, 28 Sep 1997 01:34:41 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id BAA18248 for ; Sun, 28 Sep 1997 01:34:36 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id IAA03488; Sun, 28 Sep 1997 08:17:56 +0100 From: Luigi Rizzo Message-Id: <199709280717.IAA03488@labinfo.iet.unipi.it> Subject: Re: Problems with diskless To: dan@dpcsys.com (Dan Busarow) Date: Sun, 28 Sep 1997 08:17:56 +0100 (MET) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Dan Busarow" at Sep 28, 97 00:04:56 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > It finds the bootp and tftp servers, loads the kernel and starts > the boot. Right after ... > I get > > exec /sbin/init: error 13 change the protections on /sbin/init. For some silly reasons it is -r-x------ 1 bin bin 180224 Mar 25 1997 /sbin/init and the client cannot read it unless the server exports with root privs. I have been suggesting a change of permissions in /sbin/init for years for this exact reason, but never got heard... Cheers Luigi From owner-freebsd-hackers Sun Sep 28 02:21:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA21357 for hackers-outgoing; Sun, 28 Sep 1997 02:21:02 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA21343 for ; Sun, 28 Sep 1997 02:20:48 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id SAA05469; Sun, 28 Sep 1997 18:47:57 +0930 (CST) Message-Id: <199709280917.SAA05469@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: hackers@FreeBSD.ORG Subject: Re: Timeout for sh(1) 'read' ?? In-reply-to: Your message of "Sun, 28 Sep 1997 08:36:19 +0200." <19970928083619.EN11505@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_17929333040" Date: Sun, 28 Sep 1997 18:47:53 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk This is a multipart MIME message. --==_Exmh_17929333040 Content-Type: text/plain; charset=us-ascii > As Mike Smith wrote: > > > > $foo=${foo:-default} > > > > Hmm. Actually, you would get the desired behaviour with > > > > val=${default} > > Well, sure. I didn't see this. :) You need to assign a value in the > first place anyway. I think you are misreading me; I was agreeing that the "default value" option was the wrong way to go, and that an equivalent behaviour could be achieved by setting the variable before calling read. > j@uriah 66% ksh93 > $ read -t 5 foo # and just wait > $ echo $? > 1 > $ read -t 5 foo > babble > $ echo $? > 0 > $ exit This is identical to the enclosed patch, which is good. Comments anyone? mike --==_Exmh_17929333040 Content-Type: text/plain ; name="sh.diff"; charset=us-ascii Content-Description: sh.diff Content-Disposition: attachment; filename="sh.diff" *** /usr/src/bin/sh/miscbltin.c Mon Aug 4 18:54:31 1997 --- miscbltin.c Sun Sep 28 18:44:03 1997 *************** *** 52,57 **** --- 52,58 ---- #include #include #include + #include #include "shell.h" #include "options.h" *************** *** 88,101 **** int startword; int status; int i; eflag = 0; prompt = NULL; ! while ((i = nextopt("ep:")) != '\0') { ! if (i == 'p') prompt = optarg; ! else eflag = 1; } if (prompt && isatty(0)) { out2str(prompt); --- 89,131 ---- int startword; int status; int i; + struct timeval tv; + char *tvptr; + fd_set ifds; + struct termios told, tnew; + int tsaved; eflag = 0; prompt = NULL; ! tv.tv_sec = -1; ! tv.tv_usec = 0; ! while ((i = nextopt("d:ep:t:")) != '\0') { ! switch(i) { ! case 'p': prompt = optarg; ! break; ! case 'e': eflag = 1; + break; + case 't': + tv.tv_sec = strtol(optarg, &tvptr, 0); + if (tvptr == optarg) + error("timeout value"); + switch(*tvptr) { + case 0: + case 's': + break; + case 'h': + tv.tv_sec *= 60; + /* FALLTHROUGH */ + case 'm': + tv.tv_sec *= 60; + break; + default: + error("timeout unit"); + } + break; + } } if (prompt && isatty(0)) { out2str(prompt); *************** *** 105,110 **** --- 135,169 ---- error("arg count"); if ((ifs = bltinlookup("IFS", 1)) == NULL) ifs = nullstr; + + if (tv.tv_sec >= 0) { + /* + * See if we can disable input processing; this will + * not give the desired result if we are in a pipeline + * and someone upstream is still in line-by-line mode. + */ + tsaved = 0; + if (tcgetattr(0, &told) == 0) { + memcpy(&tnew, &told, sizeof(told)); + cfmakeraw(&tnew); + tcsetattr(0, TCSANOW, &tnew); + tsaved = 1; + } + /* + * Wait for something to become available. + */ + FD_ZERO(&ifds); + FD_SET(0, &ifds); + status = select(1, &ifds, NULL, NULL, &tv); + if (tsaved) + tcsetattr(0, TCSANOW, &told); + /* + * If there's nothing ready, return an error. + */ + if (status <= 0) + return(1); + } + status = 0; startword = 1; backslash = 0; *** /usr/src/bin/sh/sh.1 Mon Sep 15 01:01:24 1997 --- sh.1 Sun Sep 28 15:40:37 1997 *************** *** 1123,1129 **** it faster. However, if the current directory is renamed, the builtin version of pwd will continue to print the old name for the directory. ! .It read [ -p prompt ] [ -e ] variable ... The prompt is printed if the -p option is specified and the standard input is a terminal. Then a line is read from the standard input. The trailing newline --- 1123,1129 ---- it faster. However, if the current directory is renamed, the builtin version of pwd will continue to print the old name for the directory. ! .It read [ -p prompt ] [-t timeout ] [ -e ] variable ... The prompt is printed if the -p option is specified and the standard input is a terminal. Then a line is read from the standard input. The trailing newline *************** *** 1135,1140 **** --- 1135,1143 ---- separated them) are assigned to the last variable. If there are more variables than pieces, the remaining variables are assigned the null string. + If the -t option is specified and timeout seconds elapse + before any input is supplied, the read command will + return without assigning any values. .Pp The -e option causes any backslashes in the input to be treated specially. If a backslash is followed by --==_Exmh_17929333040-- From owner-freebsd-hackers Sun Sep 28 02:22:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA21451 for hackers-outgoing; Sun, 28 Sep 1997 02:22:49 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA21420 for ; Sun, 28 Sep 1997 02:22:33 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id SAA05487; Sun, 28 Sep 1997 18:49:00 +0930 (CST) Message-Id: <199709280919.SAA05487@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Tony Overfield cc: Terry Lambert , hackers@freebsd.org Subject: Re: INB question In-reply-to: Your message of "Sat, 27 Sep 1997 05:55:43 EST." <3.0.2.32.19970927055543.006bd29c@bugs.us.dell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Sep 1997 18:48:57 +0930 From: Mike Smith Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > At 02:44 PM 9/19/97 +0000, Terry Lambert wrote: > >> > Yeah; that's why I picked the extended MCA DMA ports for the detect; > >> > that, and I can do the probe non-destructively, with the expectation of > >> > a 0 bit in my data and no hardware configuratio changes resulting. > >> > >> Where is the port exactly? ie. is it likely to be sat on or masked > >> over by an ISA device? > > > >Port 0x18 is the control, and port 0x1A is the data. > > Port 0x18, on many systems, is an alias of port 0x08, which is > the read-only DMA status register and the write-only DMA command > register. Likewise, port 0x1A is often an alias of the write-only > port 0x0A DMA mask register. Eep. That's not so good then. Now you're back; do *you* know how to identify an MCA machine uniquely? mike From owner-freebsd-hackers Sun Sep 28 02:23:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA21496 for hackers-outgoing; Sun, 28 Sep 1997 02:23:25 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA21487 for ; Sun, 28 Sep 1997 02:23:17 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id SAA05505; Sun, 28 Sep 1997 18:50:04 +0930 (CST) Message-Id: <199709280920.SAA05505@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Tony Overfield cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: INB question In-reply-to: Your message of "Sun, 28 Sep 1997 02:00:01 EST." <3.0.2.32.19970928020001.006ce080@bugs.us.dell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Sep 1997 18:50:03 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >Read it again. 1.3MegaWords. Specifically, implying that it's making > >1.3 million 16-bit I/O transactions per second, or 2.6MB/sec. > > > >Yes, this is substantially faster than I was expecting. 8) > > 16-bit ISA I/O cycles are not only wider but also faster than 8-bit ISA > I/O cycles. Back when IDE drives were still attached to the ISA bus, a > fast drive could transfer about 3.5MB/sec, but 2.5MB/sec or 2MB/sec was > more typical. The speed depends on the chipset and the way that the > BIOS programs the ISA timing options. Gotcha. Hmm, does this mean that you can read an 8-bit peripheral faster by using 16-bit cycles, or will the sizing signals trip you up? mike From owner-freebsd-hackers Sun Sep 28 02:26:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA21807 for hackers-outgoing; Sun, 28 Sep 1997 02:26:24 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id CAA21791 for ; Sun, 28 Sep 1997 02:26:18 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 22416 invoked by uid 1001); 28 Sep 1997 09:26:13 +0000 (GMT) To: tlambert@primenet.com Cc: freebsd-hackers@freefall.FreeBSD.org Subject: Re: r-cmds and DNS and /etc/host.conf In-Reply-To: Your message of "Sat, 27 Sep 1997 21:29:41 +0000 (GMT)" References: <199709272129.OAA11592@usr08.primenet.com> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 28 Sep 1997 11:26:12 +0200 Message-ID: <22414.875438772@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Technically 127.1 and 127.0.0.1 are synonymous; one would think the > code should know this... Technically, 127.0.0.1 for the loopback address is a Berkeley-ism, but it is now cast in stone, since RFC1700 defines (g) {127, } Internal host loopback address. Should never appear outside a host. As far as I can see, this change occurred in two steps: - RFC 820 (January 1983 "Assigned Numbers") doesn't mention 127.*.*.*. - RFC 870 (October 1983 "Assigned Numbers") has 127.*.*.* as "reserved". - RFC 990 (November 1986 "Assigned Numbers") has 127.*.*.* explicitly as loopback. 127.1 as an alternative way of writing 127.0.0.1 is also a Berkeley-ism, as far as I know. The name server (BIND) knows nothing about it, and the inet_pton() routine (part of POSIX 1003.1g work in progress) does not recognize this format, even if inet_addr() and inet_ntoa() does. It is *not* a particularly good idea to depend on 127.1 being interpreted as 127.0.0.1. Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-hackers Sun Sep 28 02:32:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA22239 for hackers-outgoing; Sun, 28 Sep 1997 02:32:54 -0700 (PDT) Received: from casparc.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id CAA22234 for ; Sun, 28 Sep 1997 02:32:42 -0700 (PDT) Received: from ernie by casparc.ppp.net with uucp (Smail3.1.28.1 #1) id m0xFFhq-000oJZC; Sun, 28 Sep 97 10:32 MET Received: from bert.kts.org(really [194.55.156.2]) by ernie.kts.org via sendmail with smtp id for ; Sun, 28 Sep 1997 11:24:21 +0200 (MET DST) (Smail-3.2.0.91 1997-Jan-14 #2 built 1997-Feb-8) Received: by bert.kts.org via sendmail with stdio id for hackers@FreeBSD.ORG; Sun, 28 Sep 1997 11:16:14 +0200 (CEST) (Smail-3.2.0.94 1997-Apr-22 #7 built 1997-Jul-4) Message-Id: From: hm@kts.org (Hellmuth Michaelis) Subject: Re: INB question In-Reply-To: <3.0.2.32.19970928015842.006ce080@bugs.us.dell.com> from Tony Overfield at "Sep 28, 97 01:58:42 am" To: tony@dell.com (Tony Overfield) Date: Sun, 28 Sep 1997 11:16:14 +0200 (CEST) Cc: tlambert@primenet.com, hackers@FreeBSD.ORG Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Tony Overfield wrote: > Port 0x84 is an unused DMA page register, just like 0x80, 0x85, 0x86 > and others. Each of these unused registers is read/write and should > have no effect, except to cause an 8-bit ISA I/O cycle. This might be on some (or even the majority) motherboards, but not on all: some existing chipsets seem to detect accesses to "unused" register addresses and prevent the i/o cycle to happen. I had exactly this problem in pcvt, and for the majority of cases the i/o read to 0x84 ran without problems but on some platforms you'll get strange behaviours (see /usr/src/sys/i386/isa/pcvt/pcvt_hdr.h, around line 1364, "#if PCVT_PORTIO_DELAY"). hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe "Those who can, do. Those who can't, talk. And those who can't talk, talk about talking." (B. Shaw) From owner-freebsd-hackers Sun Sep 28 05:31:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA29039 for hackers-outgoing; Sun, 28 Sep 1997 05:31:24 -0700 (PDT) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA29029 for ; Sun, 28 Sep 1997 05:31:08 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id FAA00308; Sun, 28 Sep 1997 05:28:55 -0700 (PDT) Message-ID: <19970928052854.58152@hydrogen.nike.efn.org> Date: Sun, 28 Sep 1997 05:28:54 -0700 From: John-Mark Gurney To: FreeBSD Hackers Subject: preliminary design of new bus/device system for FreeBSD Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk well... I've been looking at improving the bus/device design in freebsd to handle better conflicts in resources and making the design more expandable... right now I've put what I've writen down so far at http://resnet.uoregon.edu:6971/~jmg/FreeBSD/busdevice.html... I'm looking at using extent for resource management.. but also extending it so that we can include a tag so we know which device is the conflicting device... at the same time, I plan on improving extent so that it will coalesce objects into a sublist so that inserting a new extent will be faster, but still keep all extents seperate... Right now this bus design depends upon the creation of a processor bus that will initally create the resources and start probing... do we have anybody that is knowledgable about EISA/vlb design that can inform me (in private mail) on the specifics on how they hang off the processor bus along with the ISA bus? comments? suggestions? improvements? (the struct/memeber names are open to sugestion, just needed something now :) ) right now the only thing I'm questioning is possibly adding a busid feild to struct gendevice to make sure we don't call a probe/attach/etc on the wrong device... but I'm not sure that really should be neccessary... -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-hackers Sun Sep 28 11:05:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA15625 for hackers-outgoing; Sun, 28 Sep 1997 11:05:32 -0700 (PDT) Received: from zippy.dyn.ml.org (garbanzo@haiti-100.ppp.hooked.net [206.169.228.100]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA15618 for ; Sun, 28 Sep 1997 11:05:28 -0700 (PDT) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.7/8.8.7) with SMTP id LAA00622; Sun, 28 Sep 1997 11:04:57 -0700 (PDT) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Sun, 28 Sep 1997 11:04:56 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Mike Smith cc: Tony Overfield , Terry Lambert , hackers@FreeBSD.ORG Subject: Re: INB question In-Reply-To: <199709280919.SAA05487@word.smith.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 28 Sep 1997, Mike Smith wrote: > > At 02:44 PM 9/19/97 +0000, Terry Lambert wrote: > > >> > Yeah; that's why I picked the extended MCA DMA ports for the detect; > > >> > that, and I can do the probe non-destructively, with the expectation of > > >> > a 0 bit in my data and no hardware configuratio changes resulting. > > >> > > >> Where is the port exactly? ie. is it likely to be sat on or masked > > >> over by an ISA device? > > > > > >Port 0x18 is the control, and port 0x1A is the data. > > > > Port 0x18, on many systems, is an alias of port 0x08, which is > > the read-only DMA status register and the write-only DMA command > > register. Likewise, port 0x1A is often an alias of the write-only > > port 0x0A DMA mask register. > > Eep. That's not so good then. Now you're back; do *you* know how to > identify an MCA machine uniquely? >From the NetBSD/MCA page: "MCA bus detection is by checking certain bits of MCA adapter setup register at port 0x96: not sure if this is the best way to do it." - alex From owner-freebsd-hackers Sun Sep 28 11:40:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA17099 for hackers-outgoing; Sun, 28 Sep 1997 11:40:05 -0700 (PDT) Received: from cedb.dpcsys.com (cedb.dpcsys.com [206.16.184.4]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA17085 for ; Sun, 28 Sep 1997 11:40:02 -0700 (PDT) Received: from localhost (dan@localhost) by cedb.dpcsys.com (8.8.5/8.8.2) with SMTP id SAA01062; Sun, 28 Sep 1997 18:39:53 GMT Date: Sun, 28 Sep 1997 11:39:53 -0700 (PDT) From: Dan Busarow To: Luigi Rizzo cc: hackers@FreeBSD.ORG Subject: Re: Problems with diskless In-Reply-To: <199709280717.IAA03488@labinfo.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 28 Sep 1997, Luigi Rizzo wrote: > change the protections on /sbin/init. For some silly reasons it is > > -r-x------ 1 bin bin 180224 Mar 25 1997 /sbin/init I already tried that. Even with 0777 permissions I get the same error. rootfs is exported with root access allowed also. Dan -- Dan Busarow 714 443 4172 DPC Systems / Beach.Net dan@dpcsys.com Dana Point, California 83 09 EF 59 E0 11 89 B4 8D 09 DB FD E1 DD 0C 82 From owner-freebsd-hackers Sun Sep 28 15:45:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA27901 for hackers-outgoing; Sun, 28 Sep 1997 15:45:16 -0700 (PDT) Received: from usr07.primenet.com (tlambert@usr07.primenet.com [206.165.6.207]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA27867 for ; Sun, 28 Sep 1997 15:44:50 -0700 (PDT) Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id PAA17978; Sun, 28 Sep 1997 15:44:28 -0700 (MST) From: Terry Lambert Message-Id: <199709282244.PAA17978@usr07.primenet.com> Subject: Re: ee taking up weird cpu amount. To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sun, 28 Sep 1997 22:44:27 +0000 (GMT) Cc: tlambert@primenet.com, joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.ORG In-Reply-To: <27013.875412811@time.cdrom.com> from "Jordan K. Hubbard" at Sep 27, 97 07:13:31 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >Dealing with the error case is only a requirement of FreeBSD and > >several other "broken" systems. The only other one that springs to > > Dealing with I/O errors on reading from the tty is the responsibilty > of any reasonably well written program. Is that a genuine Stetson I > see you talking out of there? Nice hat! ;-) Read my other posting. The only possible errors in this particular read case are related to inpout redirection from a file (EIO). If the read returns a zero, it only does so because SIGHUP processing has not killed the process as it should have in the trampoline code on the way out of the read system call before the call was alloed to return. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sun Sep 28 15:57:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA28459 for hackers-outgoing; Sun, 28 Sep 1997 15:57:58 -0700 (PDT) Received: from usr07.primenet.com (tlambert@usr07.primenet.com [206.165.6.207]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA28437 for ; Sun, 28 Sep 1997 15:57:26 -0700 (PDT) Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id PAA18439; Sun, 28 Sep 1997 15:56:49 -0700 (MST) From: Terry Lambert Message-Id: <199709282256.PAA18439@usr07.primenet.com> Subject: Re: INB question To: tony@dell.com (Tony Overfield) Date: Sun, 28 Sep 1997 22:56:48 +0000 (GMT) Cc: tlambert@primenet.com, hackers@FreeBSD.ORG In-Reply-To: <3.0.2.32.19970927055543.006bd29c@bugs.us.dell.com> from "Tony Overfield" at Sep 27, 97 05:55:43 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Port 0x18, on many systems, is an alias of port 0x08, which is > the read-only DMA status register and the write-only DMA command > register. Likewise, port 0x1A is often an alias of the write-only > port 0x0A DMA mask register. Peachy. I suppose this was done "for no good reason", as usual in PC hardware design. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sun Sep 28 15:59:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA28580 for hackers-outgoing; Sun, 28 Sep 1997 15:59:46 -0700 (PDT) Received: from usr07.primenet.com (tlambert@usr07.primenet.com [206.165.6.207]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA28572 for ; Sun, 28 Sep 1997 15:59:39 -0700 (PDT) Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id PAA18491; Sun, 28 Sep 1997 15:59:35 -0700 (MST) From: Terry Lambert Message-Id: <199709282259.PAA18491@usr07.primenet.com> Subject: Re: ee taking up weird cpu amount. To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 28 Sep 1997 22:59:35 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <19970928002450.TG36648@uriah.heep.sax.de> from "J Wunsch" at Sep 28, 97 00:24:50 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > The foreground process group gets properly signalled. I've been using > > > a FreeBSD-based ISP for long enough to know that it works. > > > > Then under what circumstances is it ever possible to get a process > > buzzing in a "read returns 0 bytes" loop? > > The process was in the background, thus in a different process group. Why isn't it "stopped on tty input" instead? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sun Sep 28 16:04:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA29028 for hackers-outgoing; Sun, 28 Sep 1997 16:04:21 -0700 (PDT) Received: from usr07.primenet.com (tlambert@usr07.primenet.com [206.165.6.207]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA29015 for ; Sun, 28 Sep 1997 16:04:10 -0700 (PDT) Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id QAA18628; Sun, 28 Sep 1997 16:03:39 -0700 (MST) From: Terry Lambert Message-Id: <199709282303.QAA18628@usr07.primenet.com> Subject: Re: How do I check out a snapshot? To: nate@mt.sri.com (Nate Williams) Date: Sun, 28 Sep 1997 23:03:38 +0000 (GMT) Cc: chuckr@glue.umd.edu, nate@mt.sri.com, rkw@dataplex.net, jkh@time.cdrom.com, hackers@FreeBSD.ORG In-Reply-To: <199709272247.QAA28003@rocky.mt.sri.com> from "Nate Williams" at Sep 27, 97 04:47:59 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > The whole FreeBSD process is a multi-threaded/SMP kind of thing, so you > gotta think about race conditions and all those other OS kinds of > things. :) I'm sure you didn't mean this analogy... the fix in the SMP case is locking. 8-) 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sun Sep 28 16:12:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA29499 for hackers-outgoing; Sun, 28 Sep 1997 16:12:50 -0700 (PDT) Received: from usr07.primenet.com (tlambert@usr07.primenet.com [206.165.6.207]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA29476 for ; Sun, 28 Sep 1997 16:12:26 -0700 (PDT) Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id QAA18807; Sun, 28 Sep 1997 16:11:49 -0700 (MST) From: Terry Lambert Message-Id: <199709282311.QAA18807@usr07.primenet.com> Subject: Re: INB question To: tony@dell.com (Tony Overfield) Date: Sun, 28 Sep 1997 23:11:48 +0000 (GMT) Cc: tlambert@primenet.com, hackers@FreeBSD.ORG In-Reply-To: <3.0.2.32.19970928015842.006ce080@bugs.us.dell.com> from "Tony Overfield" at Sep 28, 97 01:58:42 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >This is actually bogus as hell. First, because it's an input, not > >an output. > > I don't see anything wrong with using an input for this. An input doesn't guarantee a synchronization cycle, but an output does. The point of the delay is to get a synchronization cycle. It would be better to force it than to hope that it got done in the time window of the inb. > It doesn't matter whether the port exists, the only benefit of the > access is that it causes a slow ISA bus cycle, which will happen > even if the port doesn't exist. I think -- according to Van Gilluwe, anyway -- an input does not necessarily cause a cycle, but an output will, for sure. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sun Sep 28 16:20:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA29874 for hackers-outgoing; Sun, 28 Sep 1997 16:20:18 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA29864 for ; Sun, 28 Sep 1997 16:20:07 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA14527 for ; Sun, 28 Sep 1997 16:17:15 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd014524; Sun Sep 28 23:17:06 1997 Message-ID: <342EE53C.59E2B600@whistle.com> Date: Sun, 28 Sep 1997 16:16:12 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: Do you have Ontrack Disk manager? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk can anyone who has this isntalled, send me copies of the block 0 of their disk, and a description of the disk's geometry as seen by the BIOS and by BSD..? Does anyone know the answers to the folowing questions? (BDE?) 1/ does ontrack just use '63' as the start of it's section or does it use the start of the 2nd cylinder? 2/ does it write teh start location of it's bit in it's MBR entry? does it set the END entries correctly? maybe with enough examples I can andswer these questions definatively. I'm most of the way through writing a disk subsystem to replace the diskslice wd/sd fdisk/disklabel mess we have at the moment.. (though it's a great improvement over what we had originally) thanks From owner-freebsd-hackers Sun Sep 28 17:00:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA01846 for hackers-outgoing; Sun, 28 Sep 1997 17:00:10 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA01840 for ; Sun, 28 Sep 1997 17:00:07 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA15094 for ; Sun, 28 Sep 1997 16:52:38 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd015091; Sun Sep 28 23:52:28 1997 Message-ID: <342EED86.1CFBAE39@whistle.com> Date: Sun, 28 Sep 1997 16:51:34 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Re: Do you have Ontrack Disk manager? References: <342EE53C.59E2B600@whistle.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Julian Elischer wrote: > > can anyone who has this isntalled, send me copies of the block 0 > of their disk, and a description of the disk's geometry > as seen by the BIOS and by BSD..? just the output of 'fdisk' will do. OR > > Does anyone know the answers to the folowing questions? (BDE?) > 1/ does ontrack just use '63' as the start of it's section or does > it use the start of the 2nd cylinder? errr. I mean 2nd track > 2/ does it write teh start location of it's bit in it's MBR entry? > > does it set the END entries correctly? > > maybe with enough examples I can answer these questions definatively. > > I'm most of the way through writing a disk subsystem to replace > the diskslice wd/sd fdisk/disklabel mess we have at the moment.. > (though it's a great improvement over what we had originally) > > thanks From owner-freebsd-hackers Sun Sep 28 17:33:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA03771 for hackers-outgoing; Sun, 28 Sep 1997 17:33:25 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA03748 for ; Sun, 28 Sep 1997 17:33:16 -0700 (PDT) Received: (qmail 16299 invoked by uid 1000); 29 Sep 1997 00:33:37 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092597 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199709282256.PAA18439@usr07.primenet.com> Date: Sun, 28 Sep 1997 17:33:37 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Terry Lambert Subject: Re: INB question Cc: hackers@FreeBSD.ORG, (Tony Overfield) Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Terry Lambert; On 28-Sep-97 you wrote: > > Port 0x18, on many systems, is an alias of port 0x08, which is > > the read-only DMA status register and the write-only DMA command > > register. Likewise, port 0x1A is often an alias of the write-only > > port 0x0A DMA mask register. > > Peachy. I suppose this was done "for no good reason", as usual in > PC hardware design. 8-(. At the time, it probably saved a nickel by saving some address latch. A nickel, times some millions is lots of money. What percentage of the profit it represents? Who cares. Greed is greed. > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-hackers Sun Sep 28 20:58:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA13597 for hackers-outgoing; Sun, 28 Sep 1997 20:58:47 -0700 (PDT) Received: from public1.guangzhou.gd.cn (public1.guangzhou.gd.cn [202.96.128.111]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA13591 for ; Sun, 28 Sep 1997 20:58:31 -0700 (PDT) Received: from public.public.guangzhou.gd.cn (max3-242.guangzhou.gd.cn [202.96.185.242]) by public1.guangzhou.gd.cn (8.8.5/8.8.5) with SMTP id LAA16904 for ; Mon, 29 Sep 1997 11:56:33 +0900 (CDT) Message-Id: <199709290256.LAA16904@public1.guangzhou.gd.cn> From: "Yuan Jianshan" To: Date: Mon, 29 Sep 1997 11:59:17 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1008.3 X-MimeOle: Produced By Microsoft MimeOLE Engine V4.71.1008.3 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk unsubscribe gzyuanjs@public1.guangzhou.gd.cn From owner-freebsd-hackers Sun Sep 28 21:20:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA14655 for hackers-outgoing; Sun, 28 Sep 1997 21:20:09 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA14621 for ; Sun, 28 Sep 1997 21:20:02 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id OAA04922; Mon, 29 Sep 1997 14:19:34 +1000 (EST) Date: Mon, 29 Sep 1997 14:19:32 +1000 (EST) From: "Daniel O'Callaghan" To: Yuan Jianshan cc: hackers@FreeBSD.ORG Subject: Re: your mail In-Reply-To: <199709290256.LAA16904@public1.guangzhou.gd.cn> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 29 Sep 1997, Yuan Jianshan wrote: > unsubscribe gzyuanjs@public1.guangzhou.gd.cn you need to send mail to majordomo@freebsd.org From owner-freebsd-hackers Sun Sep 28 21:27:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA15021 for hackers-outgoing; Sun, 28 Sep 1997 21:27:20 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA15016 for ; Sun, 28 Sep 1997 21:27:17 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.7/8.8.5) with ESMTP id VAA22383; Sun, 28 Sep 1997 21:27:12 -0700 (PDT) Message-Id: <199709290427.VAA22383@austin.polstra.com> To: ccsanady@bob.scl.ameslab.gov Subject: Re: CVS permissions after checkout In-Reply-To: <199709260008.TAA10113@bob.scl.ameslab.gov> References: <199709260008.TAA10113@bob.scl.ameslab.gov> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Date: Sun, 28 Sep 1997 21:27:12 -0700 From: John Polstra Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199709260008.TAA10113@bob.scl.ameslab.gov>, Chris Csanady wrote: > I have recently cvsuped a cvs tree, but am experiencing some interesting > problems. I am not sure why, but after I cvsup, my entire repository is > marked as executable. This happened because the execute permissions in the repository were all screwed up on the mirror site from which you did your update. I just found out about it myself, and it's fixed now. The new version 15.2 of CVSup (by coincidence released today) corrects any bad permissions on each update. Until version 15.2, the permissions were set correctly on the first creation of a file, but ignored after that. This was a design decision which I subsequently decided was wrong. Bottom line: Upgrade your CVSup client, and then do an update from a server which is also running the latest version. All of them should be upgraded soon. I know for a fact that cvsup.freebsd.org and cvsup2.freebsd.org are already upgraded. (Freefall is too.) John -- 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 Sun Sep 28 22:31:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA17956 for hackers-outgoing; Sun, 28 Sep 1997 22:31:45 -0700 (PDT) Received: from usr08.primenet.com (tlambert@usr08.primenet.com [206.165.6.208]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA17933; Sun, 28 Sep 1997 22:31:39 -0700 (PDT) Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id WAA16168; Sun, 28 Sep 1997 22:31:28 -0700 (MST) From: Terry Lambert Message-Id: <199709290531.WAA16168@usr08.primenet.com> Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) To: rgrimes@GndRsh.aac.dev.com (Rodney W. Grimes) Date: Mon, 29 Sep 1997 05:31:28 +0000 (GMT) Cc: tlambert@primenet.com, sthaug@nethelp.no, hackers@FreeBSD.ORG, stable@FreeBSD.ORG In-Reply-To: <199709280656.XAA20941@GndRsh.aac.dev.com> from "Rodney W. Grimes" at Sep 27, 97 11:56:53 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Ah, Terry, do you realize who you quoted above? Please reread > what I wrote, I don't think you can find a NIC that meets my > spec without getting a ``good one''. Yes; I'll note the subtle distinction between "prevent" and "not fail as a result of". If you are spending money, since hubs cost more than cards, unless you already have a significant amount of bad cards to hubs, and the price of replacing the cards is higher than the marginal cost of upgrading the card to a switch, you might as well go for "not fail as a result of" instead, and save the money. The problem is specific to the fxp cards; don't buy fxp cards, and you don't have the problem. Upgrade your hubs to switches, and you don't have the problem. Is it really cheaper to buy switched than new cards? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sun Sep 28 23:37:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA21545 for hackers-outgoing; Sun, 28 Sep 1997 23:37:18 -0700 (PDT) Received: from ns1.ied-vorstu.ac.ru (ns1.IED-VorSTU.ac.ru [193.233.113.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA21466 for ; Sun, 28 Sep 1997 23:35:12 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by ns1.ied-vorstu.ac.ru (8.8.7/8.8.7) with SMTP id KAA05105; Mon, 29 Sep 1997 10:25:18 +0400 (MSD) Date: Mon, 29 Sep 1997 10:25:18 +0400 (MSD) From: "Vasily V. Grechishnikov" X-Sender: bazilio@ns1 To: John Hay cc: freebsd-hackers@freebsd.org Subject: Re: Tulip IPX support in -current unimplemented, why ? In-Reply-To: <199709280728.JAA21944@zibbi.mikom.csir.co.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 28 Sep 1997, John Hay wrote: > > > > I have the following problem: > > My FreeBSD box runs FreeBSD-current and it provides > > IP/IPX routing between the four newtwork interfaces ( 3 NE2000 + 1 Tulip). > > Sometime ago since the CVSup'ing of -current my tulip card couldn't assign > > IPX address to interface by the ifconfig. I seen at /pci/if_de.c and can't > > find implementation of IPX portion of code for ioctl requests > > ( SIOCSIFADDR). > > FreeBSD actually have a common handler for some (SIOCSIFADDR, SIOCGIFADDR > and SIOCSIFMTU) ethernet ioctls called ether_ioctl() which should be > used by the ethernet device drivers. That way they don't need to do > anything special to support IPX. The problem is drivers like the deX > device that actually comes from a third party and other drivers like the > epX driver which has never been updated to use the common ether_ioctl(). I knew it . The deX driver has it's own ioctl handler: tulip_ioctl(). > > After patching I can work with IPX on tulip but, the next > > misteriuos thing is happen : > > IPX packets to one of my networks, connected to tulip card > > can't successfully forwards from the remote network : > > > > NET 0 NET 1 > > > > Broken IPX net. Good IPX net. > > *--------------- Tulip ( ) NE2000 ------------* > > ( FreeBSD box ) Good IPX net > > +--------( )NE2000--1'st if(*)2'nd if--+ > > | NetWare 3.12 | > > | NET 2 | > > | | > > | NetWare 4.1 > > | NET 3 > > | > > 1'st if > > ( FreeBSD box) > > 2'nd if NET 4 > > | > > +-------------NetWare 4.1 ( unreachable from tulip). > > > > But Netware 4.1 from unreachable network can see from a NET 1-3 :-( > > You don't give much information about your patch, so I can't comment on > this. It might be that you just got it to not generate an error when > you ifconfig it, without actually working. Then IPXrouted might pick > up the IPX net and broadcast it on the other nets. That way they might > learn about the broken net, without actually being able to use it. Here is my patch to pci/if_de.c : ************************************************ --- if_de.c.3.0 Wed Aug 13 11:52:33 1997 +++ if_de.c Wed Aug 13 12:07:04 1997 @@ -83,6 +83,11 @@ #include #endif +#ifdef IPX +#include +#include +#endif + #ifdef NS #include #include @@ -4238,6 +4243,21 @@ break; } #endif /* INET */ + +#ifdef IPX + case AF_IPX: { + struct ipx_addr *ina = &(IA_SIPX(ifa)->sipx_addr); + if(ipx_nullhost(*ina)) { + ina->x_host = + *(union ipx_host*)sc->tulip_enaddr; + } else { + ifp->if_flags &= ~ IFF_RUNNING; + bcopy((caddr_t)->ina.x_host.c_host, + (caddr_t)sc->tulip_enaddr, + sizeof(sc->tulip_enaddr)); + } + } +#endif /* IPX */ #ifdef NS /* **************************************************** It is very simple, trivial and dumby. > But to try and figure out what is wrong, I'll have to see the patch > that you have made and also the part of your rc.conf files that have > to do with IPX. With my patch tulip driver can correctly assign right IPX address from the ifconfig. And from broken IPX net I can reach any Netware server in my LAN, except the 4.1 in NET4. First I think that FreeBSD 2.2BETA at the secondary router had broken IPX support, but NET4 is reachable from the NET1-3.And from the NET0 I can see Netware server 4.1 connected to 2'nd if of Netware 3.12 in NET2. Here is the chunk of /etc/rc.conf : [ ... ] network_interfaces="de0 ed0 ed1 ed2 lo0" # List of network interfaces (lo0 is loopback) ifconfig_de0="inet 193.233.113.225 netmask 255.255.255.240" ifconfig_de0_ipx="ipx 0x7" ifconfig_ed0="inet 193.233.113.18 netmask 255.255.255.248" ifconfig_ed0_alias0="inet 193.233.113.20 broadcast 193.233.113.23" ifconfig_ed0_ipx="ipx 0xd" ifconfig_ed1="inet 193.233.113.129 netmask 255.255.255.240" ifconfig_ed1_ipx="ipx 0x330" ifconfig_ed2="inet 193.233.113.249 netmask 255.255.255.248" ifconfig_ed2_ipx="ipx 0x329" ifconfig_lo0="inet 127.0.0.1" # default loopback device configuration. [ ... ] ipxgateway_enable="YES" # Set to YES to enable IPX routing. ipxrouted_enable="YES" # Set to YES to run the IPX routing daemon. ipxrouted_flags="-s" # Flags for IPX routing daemon. [ ... ] Thanks , Vasily . ***************[ FreeBSD it is coolest UNIX for PCs ! ]*************** * System admin/programmer, ftp/web/post master. * IM & PE of VorSTU * * Home Page: http://www.ied-vorstu.ac.ru/~bazilio * ********************************************************************** From owner-freebsd-hackers Sun Sep 28 23:46:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA22126 for hackers-outgoing; Sun, 28 Sep 1997 23:46:42 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA22104 for ; Sun, 28 Sep 1997 23:46:37 -0700 (PDT) Received: from x14.mi.uni-koeln.de ([134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA03871 (5.67b/IDA-1.5 for ); Mon, 29 Sep 1997 08:46:34 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.7/8.6.9) id IAA00580; Mon, 29 Sep 1997 08:45:24 +0200 (CEST) X-Face: " Date: Mon, 29 Sep 1997 08:45:23 +0200 From: Stefan Esser To: will@iki.fi Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Conflicting I/O address spaces -- caused by...? References: <199709281110.OAA04780@dol-guldur.hut.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199709281110.OAA04780@dol-guldur.hut.fi>; from Ville-Pertti Keinonen on Sun, Sep 28, 1997 at 02:10:25PM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sep 28, Ville-Pertti Keinonen wrote: > I posted a question regarding this issue on freebsd-hackers several > weeks ago and haven't received any kind of response, so I'm posting Sorry, I had seen your message, but did not have time to respond (had quit reading mail for more than one week because of paid work demanding all my energy ...) [ This is now CCed to the mail list where you originally posted your question ... ] > this to you directly hoping that you're the right person to answer my > question... The problem doesn't seem to be caused by FreeBSD, but > could possibly be fixed in the PCI code. OK. We'll see ... > For some reason, my Diamond Stealth64 Video 3200 and Adaptec AHA-3985W > are getting overlapping I/O address spaces. More specifically, the > topmost S3 register (the registers appear to have fixed I/O addresses > between 0x2e8 and 0xe2ea, mostly 0x??e8, where 0xe2e8 is the problem) > is located in the middle of I/O register space used by one of the > channels on the SCSI adapter. Hmmm, yes, the S3 chips are known to decode those addresses, and often conflict with a fourth UART (sio3) at 0x2e8, IIRC ... > This was causing the system to lock up when the X server (XFree86 3.3 > and XFree86 3.3.1, S3 server) was started whenever the SCSI adapter > driver was configured in the kernel (it appeared to depend on whether > it had its interrupt handlers registered correctly...) with several > FreeBSD versions (2.2.2, some 3.0 snapshot and -current) with and > without SMP. > > The problem was occurring even when the X server was supposed to be > using memory mapped I/O -- for some reason, the one problematic > register was being accessed using outw even though a memory mapped > equivalent was available... I changed it and now the X server works > in newmmio mode. However, this is obviously only a workaround, the > real problem still remains... You better ask this on a xfree86 list, but I seem to remember, that the X server *has to* use that port. > Here's the relevant portion of boot -v info (a somewhat current > SMP kernel, kludged to get the right IRQs for the AHA-3985W): > chip2: rev 0x02 on pci0.14.0 Just BTW: That bridge chip is not PCI 2.1 compliant, and may cause system hangs in various (unlikely but not impossible) situations. > found-> vendor=0x5333, dev=0x88f0, revid=0x00 > class=03-00-00, hdrtype=0x00, mfdev=0 > intpin=a, irq=19 > map[0]: type 1, range 32, base e0000000, size 25 > vga0: rev 0x00 int a irq 19 on pci0.17.0 The VGA does really only claim one memory range. There once was a bug in the S3 968 chip, which made it request only half the memory range it actually decodes, but this should have been fixed in more recent chips ... > Probing for devices on PCI bus 1: You are *behind* the PCI to PCI bridge now! > Freeing (NOT implemented) redirected PCI irq 11. > found-> vendor=0x9004, dev=0x7378, revid=0x03 > class=01-00-00, hdrtype=0x00, mfdev=0 > intpin=a, irq=16 > map[0]: type 4, range 32, base 0000e000, size 8 > map[1]: type 1, range 32, base d0000000, size 12 > ahc0: rev 0x03 int a irq 16 on pci1.4.0 > found-> vendor=0x9004, dev=0x1078, revid=0x00 > class=05-80-00, hdrtype=0x00, mfdev=0 > intpin=a, irq=17 > map[0]: type 4, range 32, base 0000e100, size 8 > map[1]: type 1, range 32, base d0001000, size 12 > map[2]: type 3, range 32, base df000000, size 21 > ahc1: rev 0x00 int a irq 17 on pci1.5.0 > found-> vendor=0x9004, dev=0x7378, revid=0x03 > class=01-00-00, hdrtype=0x00, mfdev=0 > intpin=a, irq=16 > map[0]: type 4, range 32, base 0000e200, size 8 > map[1]: type 1, range 32, base d0002000, size 12 > ahc2: rev 0x03 int a irq 16 on pci1.8.0 As you observed, that Adaptec chip decodes 0xe200 up to 0xe2ff and thus overlaps with the addresses claimed by the S3 card. > found-> vendor=0x9004, dev=0x7378, revid=0x03 > class=01-00-00, hdrtype=0x00, mfdev=0 > intpin=a, irq=16 > map[0]: type 4, range 32, base 0000e300, size 8 > ahc3: rev 0x03 int a irq 16 on pci1.12.0 > As you can see, the S3 card isn't indicating any use of I/O address > space and 0xe2e8 is in the I/O space of channel B (which also happens > to be the only channel with anything currently connected, but that > doesn't affect the lockup behavior, it occurs without any devices > connected). Yes. Absolutely correct. > These are the only PCI cards I have installed, I also tried moving the > graphics card around earlier when I thought interrupts were the > problem (it was sharing the interrupt used by the aic7810). The > motherboard is a Soyo 5TH5 (430HX, Award BIOS). > > The question is, where is the real problem and what is the correct > solution? My guess is that it would be the S3 card not indicating I/O > address usage (which can't really be solved), but it could also be the > BIOS or even the SCSI adapter (maybe it has fixed addresses, although > I strongly doubt it). However, I don't know how the PCI configuration > is done so I really can only guess... Well, the problem really appears to be the port addresses decoded by the S3, which have been choosen from within the ISA legacy port range, and thus should not be expected to be available to PCI devices. This caused problems with ISA UART cards before, but your conflict with a PCI card is new ;-) I think your PCI BIOS is at fault. When the PC was designed, the port range 0x0000 to 0x00ff was assigned to motherboard devices, and the range 0x0100 to 0x03ff to expansion cards, which often only decoded 10 bits of the port address, and thus were visible on each multiple of 1024 again. The PCI standard had to take this bogosity into consideration, and they defined the ISA MODE bit in the bridge control register, which will have the effect of blocking accesses to the secondary side for port addresses that don't have the 8th and 9th equal to 0. This makes the I/O space behind the bridge appear as non-contigous ranges of 256 port addresses, which caused the requirement, that no device should claim a port range of more than 256 bytes. Anyway, the PCI BIOS should have known about this and should have assigned port addresses 0xe000 to 0xe0ff, 0xe400 to 0x4ff, and so on to the Adaptec cards. In failing to do so, it assigned addresses that are known to cause problems as you observe. If the ISA MODE bit had been set, the PCI BIOS had been forced to only use addresses with bit 8 and 9 off, but the PCI BIOS does not seem to have set the 21050 chip into that mode. (You may want to check bit 18 of the result of pciconf -r pci0:14:0 0x3c which will read the bridge control and interrupt pin and line registers. If that bit is a 1, then ISA MODE is enabled, but I doubt it, you Adaptec card would not get accesses to 0xe100 to 0xe3ff forwarded to the SCSI chips through the bridge, then ...) Changing the port ranges from the values assigned by the BIOS to non-conflicting ones is not that easy, in general, since all PCI to PCI bridges upstream may have to be reprogrammed, and there may be conflicts with neighbour bridges, then. Using memory accesses to the Adaptec cards is a valid fix, though! Port addresses in PCI are only present for legacy device emulations, and for DOS which has no easy way to access memory mapped registers above 1MB. Justin Gibbs gave a good reason why he still uses port accesses (got to do with broken 21050 chips :) and the PCI BIOS deactivating memory accesses through them ...) So, your primary problem is the assignment of port addresses to the Adaptec chips, which fall into ranges that are known to cause conflicts with ISA cards. And while re-assigning those addresses is at least technically possible in the PCI code, I do not want to add such code. You seem to be the first one to report that problem, because it only happens, if there are 4 chips with port maps behind the bridge, and this appears not to be a common thing ... Complain to your motherboard vendor, explain the situation, and see whether they are able to provide a fix. Using memory mapped accesses through that PCI bridge may cause system hangs, but only if one of several possible scenarios exists on your system. They cause dead-lock, or even delivery of wrong data, with a very low probability. Regards, STefan From owner-freebsd-hackers Sun Sep 28 23:50:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA22445 for hackers-outgoing; Sun, 28 Sep 1997 23:50:36 -0700 (PDT) Received: from lab321.ru (anonymous1.omsk.net.ru [194.226.32.34]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA21815 for ; Sun, 28 Sep 1997 23:40:45 -0700 (PDT) Received: from lab321.ru (kev.l321.omsk.net.ru [194.226.33.68]) by lab321.ru (8.8.5-MVC-230497/8.8.5) with ESMTP id OAA08205 for ; Mon, 29 Sep 1997 14:45:20 +0600 (OSK) Message-ID: <342F4D28.417B2D09@lab321.ru> Date: Mon, 29 Sep 1997 13:39:36 +0700 From: Eugeny Kuzakov Organization: Powered by FreeBSD. X-Mailer: Mozilla 4.03b8 [en] (X11; I; FreeBSD 3.0-970807-SNAP i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: Recursive fork() and different fbsd's Content-Type: multipart/mixed; boundary="------------601EF9CC89B220D54F72F227" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is a multi-part message in MIME format. --------------601EF9CC89B220D54F72F227 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Hi, All ! I run this program on: 1. 3.0-970807-SNAP - no hangs, fork always rerurns 0. But process count does not grow.. 2. 2.1.7.1-RELEASE - more swap, more processes, not hangs really, but ....Works only router...Any applications stoped... On linux, when will process count more than same constant, fork returns -1. Any comments ? -- Best wishes, Eugeny Kuzakov Laboratory 321 ( Omsk, Russia ) http://www.lab321.ru/~kev kev@lab321.ru --------------601EF9CC89B220D54F72F227 Content-Type: application/octet-stream; name="crash.c" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="crash.c" I2luY2x1ZGUgPHN0ZGlvLmg+CiNpbmNsdWRlIDxzdGRsaWIuaD4Kdm9pZCBtYWluKCl7CiAg ICB3aGlsZSgxKXsKCWlmKGZvcmsoKSl7cHJpbnRmKCIuIik7fTsKICAgIH0KfQo= --------------601EF9CC89B220D54F72F227-- From owner-freebsd-hackers Mon Sep 29 00:25:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA24233 for hackers-outgoing; Mon, 29 Sep 1997 00:25:07 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id AAA24220 for ; Mon, 29 Sep 1997 00:25:01 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA13436 for hackers@FreeBSD.ORG; Mon, 29 Sep 1997 09:25:00 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id JAA03728; Mon, 29 Sep 1997 09:16:41 +0200 (MET DST) Message-ID: <19970929091641.ZL20420@uriah.heep.sax.de> Date: Mon, 29 Sep 1997 09:16:41 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: CVS permissions after checkout References: <199709260008.TAA10113@bob.scl.ameslab.gov> <199709290427.VAA22383@austin.polstra.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199709290427.VAA22383@austin.polstra.com>; from John Polstra on Sep 28, 1997 21:27:12 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As John Polstra wrote: > The new version 15.2 of CVSup (by coincidence released today) > corrects any bad permissions on each update. Oh, no longer the missing group write permissions iff the file creation missed them? That is great! -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Mon Sep 29 01:52:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA28387 for hackers-outgoing; Mon, 29 Sep 1997 01:52:02 -0700 (PDT) Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id BAA28348 for ; Mon, 29 Sep 1997 01:51:55 -0700 (PDT) Received: from ant.us.dell.com (ant.us.dell.com [198.64.66.34]) by bugs.us.dell.com (8.6.12/8.6.12) with SMTP id DAA01030; Mon, 29 Sep 1997 03:50:48 -0500 Message-Id: <3.0.2.32.19970929034452.006ff1c0@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.2 (32) Date: Mon, 29 Sep 1997 03:44:52 -0500 To: Mike Smith From: Tony Overfield Subject: Re: INB question Cc: hackers@FreeBSD.ORG In-Reply-To: <199709280920.SAA05505@word.smith.net.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 06:50 PM 9/28/97 +0930, Mike Smith wrote: >> 16-bit ISA I/O cycles are not only wider but also faster than 8-bit ISA >> I/O cycles. Back when IDE drives were still attached to the ISA bus, a >> fast drive could transfer about 3.5MB/sec, but 2.5MB/sec or 2MB/sec was >> more typical. The speed depends on the chipset and the way that the >> BIOS programs the ISA timing options. > >Gotcha. Hmm, does this mean that you can read an 8-bit peripheral >faster by using 16-bit cycles, No. >or will the sizing signals trip you up? Yes. Unless IOCS16# is asserted, the ISA controller will split the cycle into two slower 8-bit cycles. If IOCS16# is asserted, the cycle will be 16-bits wide and will complete faster. From owner-freebsd-hackers Mon Sep 29 01:53:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA28475 for hackers-outgoing; Mon, 29 Sep 1997 01:53:02 -0700 (PDT) Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id BAA28467 for ; Mon, 29 Sep 1997 01:52:56 -0700 (PDT) Received: from ant.us.dell.com (ant.us.dell.com [198.64.66.34]) by bugs.us.dell.com (8.6.12/8.6.12) with SMTP id DAA01021; Mon, 29 Sep 1997 03:50:46 -0500 Message-Id: <3.0.2.32.19970929030500.006ff1c0@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.2 (32) Date: Mon, 29 Sep 1997 03:05:00 -0500 To: Simon Shapiro , Terry Lambert From: Tony Overfield Subject: Re: INB question Cc: hackers@FreeBSD.ORG In-Reply-To: References: <199709282256.PAA18439@usr07.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 05:33 PM 9/28/97 -0700, Simon Shapiro wrote: > >Hi Terry Lambert; On 28-Sep-97 you wrote: >> > Port 0x18, on many systems, is an alias of port 0x08, which is >> > the read-only DMA status register and the write-only DMA command >> > register. Likewise, port 0x1A is often an alias of the write-only >> > port 0x0A DMA mask register. >> >> Peachy. I suppose this was done "for no good reason", as usual in >> PC hardware design. 8-(. > >At the time, it probably saved a nickel by saving some address latch. >A nickel, times some millions is lots of money. > >What percentage of the profit it represents? Who cares. Greed is greed. Actually, I think "no good reason" is the best answer here. I don't think there's a villain to be found here. This was first hooked up this way back in 1981 when the first IBM PC came out. This has been working the same way for over 15 years. They had no way to know that it would suddenly become a problem for Terry in late 1997. *opinion on* It was not greed that drove them to make it this way. They weren't looking for an ideal circuit so that they could take a nickel back out of it. They came up with a simple circuit that solved all known needs at that time. They probably didn't even realize that the circuit lacked "vision," since they had no idea they were laying the foundations of such a colossal legacy. *opinion off* *casual, semi-technical circuit observations follow* The address decoder circuit used in the first IBM PC (and the AT, and many derivative designs) consists of an LS138 3->8 decoder. This chip has three encoded inputs, three "G" chip select inputs, and 8 decoded outputs. They hooked up address lines A5, A6, and A7 to the three inputs of the decoder and A8 and A9 to the two active-low "G" inputs. The last "G" input is hooked up to AEN (or it's moral equivalent). This results in a decoder that decodes 10-bit I/O addresses in 8 blocks of 32 bytes ranging from 0x000 to 0x0E0. They then assigned most of those 32 byte chunks to the various devices we're all now so familiar with. The address decode aliasing on the various devices is a direct consequence of this circuit. For example, the DMA controller (8237) decodes only 4 address lines, thus those 16 decoded bytes will appear twice within the 32-byte block created by the LS138. - From owner-freebsd-hackers Mon Sep 29 02:26:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA00207 for hackers-outgoing; Mon, 29 Sep 1997 02:26:33 -0700 (PDT) Received: from gatekeeper.tsc.tdk.com (root@gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA00200 for ; Mon, 29 Sep 1997 02:26:31 -0700 (PDT) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.4/8.8.4) with ESMTP id CAA04244 for ; Mon, 29 Sep 1997 02:26:29 -0700 (PDT) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id CAA21274 for ; Mon, 29 Sep 1997 02:26:29 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id CAA03516 for freebsd-hackers@FreeBSD.ORG; Mon, 29 Sep 1997 02:26:27 -0700 (PDT) From: Don Lewis Message-Id: <199709290926.CAA03516@salsa.gv.tsc.tdk.com> Date: Mon, 29 Sep 1997 02:26:25 -0700 In-Reply-To: Don Lewis "F_SETOWN implementation redesign" (Sep 27, 1:01am) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: freebsd-hackers@FreeBSD.ORG Subject: Re: F_SETOWN implementation redesign Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk While the patch I sent out previously built a nicely functional kernel, some of the changes in broke "make world". I've rearranged things so that the changes to the include files are much less intrusive. At the same time I changed the implementation to dynamically allocate the sigio structure to decrease the overall amount of memory consumed, since most ttys, sockets, etc. aren't the target of F_SETOWN. I don't want to stuff everyone's mailboxes with another copy of the patch, so drop me a note if you're interested in obtaining a copy. --- Truck From owner-freebsd-hackers Mon Sep 29 04:53:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA06500 for hackers-outgoing; Mon, 29 Sep 1997 04:53:11 -0700 (PDT) Received: from isgate.is (isgate.is [193.4.58.51]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA06483 for ; Mon, 29 Sep 1997 04:53:00 -0700 (PDT) Received: from eh.est.is (eh.est.is [194.144.208.34]) by isgate.is (8.7.5-M/) with ESMTP id LAA03664 for ; Mon, 29 Sep 1997 11:52:45 GMT Received: from didda.est.is (totii@ppp-24.est.is [194.144.208.124]) by eh.est.is (8.8.5/8.8.5) with SMTP id LAA03595 for ; Mon, 29 Sep 1997 11:52:01 GMT Message-ID: <342F9686.41C67EA6@est.is> Date: Mon, 29 Sep 1997 11:52:38 +0000 From: =?iso-8859-1?Q?=DEor=F0ur?= Ivarsson X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2.2-RELEASE i386) MIME-Version: 1.0 To: FreeBSD-hackers@FreeBSD.ORG Subject: Is something broken in PPPD? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I am administrator for ISP service in Iceland and have some problem. Most of our modem lines are taken trough Xyplex Access server and authenticated with Radius, But four lines are connected to our FreeBSD server and are using PPPD started through ttys(5). When looking at last(1) output I see lot of connections that are "still logged in" even thoug they are dead. The modems works normally and the users are using FreeBSD ,WIN-NT, and WIN 95 to get in. I only would like to see those information correct. Thordur Ivarsson thivars@est.is From owner-freebsd-hackers Mon Sep 29 05:13:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA07329 for hackers-outgoing; Mon, 29 Sep 1997 05:13:15 -0700 (PDT) Received: from a42.deep-thought.org (A42.deep-thought.org [203.4.184.227]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA07322 for ; Mon, 29 Sep 1997 05:13:09 -0700 (PDT) Received: from a42.deep-thought.org ([127.0.0.1]) by a42.deep-thought.org with esmtp id m0xFekM-0024xQC (Debian Smail-3.2 1996-Jul-4 #2); Mon, 29 Sep 1997 22:16:18 +1000 (EST) Message-Id: X-Mailer: exmh version 1.6.9 8/22/96 To: freebsd-hackers@freebsd.org Subject: TCP connection initiation problem? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 29 Sep 1997 22:16:17 +1000 From: Richard Jones Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Could someone explain what lies behind the packet exchange shown below. 204.216.27.18 is FreeBSD's smtp port and port 8000 is a non-existent port on aaa.bbb.ccc.ddd (i.e. the initial packet from aaa.bbb.ccc.ddd to freebsd.org is forged). 20:42:56.116714 aaa.bbb.ccc.ddd.8000 > 204.216.27.18.25: S 667:667(0) win 4096 (ttl 200, id 666) 20:42:56.686714 204.216.27.18.25 > aaa.bbb.ccc.ddd.8000: S 856239105:856239105(0) ack 668 win 16384 (DF) (ttl 53, id 16513) 20:42:56.686714 aaa.bbb.ccc.ddd.8000 > 204.216.27.18.25: R 668:668(0) win 0 (ttl 255, id 5507) Now at this point SunOS, Linux and NetBSD all take no for an answer, but FreeBSD just won't quit. It takes FreeBSD another 1min15secs to decide its SYN's are not wanted (i.e the connection establishment timers kicks in). It should be noted that the initial packet can have its source faked and the packet exchange will occur between the FreeBSD host and the unsuspecting other. 20:43:02.266714 204.216.27.18.25 > aaa.bbb.ccc.ddd.8000: S 856239105:856239105(0) ack 668 win 16384 (DF) (ttl 53, id 16672) 20:43:02.266714 aaa.bbb.ccc.ddd.8000 > 204.216.27.18.25: R 668:668(0) win 0 (ttl 255, id 5508) 20:43:26.236714 204.216.27.18.25 > aaa.bbb.ccc.ddd.8000: S 856239105:856239105(0) ack 668 win 16384 (DF) (ttl 53, id 17083) 20:43:26.236714 aaa.bbb.ccc.ddd.8000 > 204.216.27.18.25: R 668:668(0) win 0 (ttl 255, id 5509) Ok, so in the next packet FreeBSD finally decides to give up: 20:44:11.236714 204.216.27.18.25 > aaa.bbb.ccc.ddd.8000: R 1:1(0) ack 1 win 16384 (DF) (ttl 53, id 18235) Note the RST's from aaa.bbb.ccc.ddd are not getting lost on the network, I've verified on another host that these packets get through (the timings really tell that story anyways). Is this broken SYN-Flood protection? Does it allow Evil others to cause a large exchange of data between a FreeBSD host and any other at just the cost of a single packet to Mrs/Mr Evil? Or am I completely missing the point? Does this exchange have a use which is beyond my ken? Richard Jones From owner-freebsd-hackers Mon Sep 29 06:45:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA11143 for hackers-outgoing; Mon, 29 Sep 1997 06:45:57 -0700 (PDT) Received: from xioa.cosmic.org (jwb@xioa.cosmic.org [206.151.181.200]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA11119 for ; Mon, 29 Sep 1997 06:45:32 -0700 (PDT) Received: (from jwb@localhost) by xioa.cosmic.org (8.8.7/8.8.5) id JAA02311 for hackers@freebsd.org; Mon, 29 Sep 1997 09:44:43 -0400 (EDT) From: Joe Beiter Message-Id: <199709291344.JAA02311@xioa.cosmic.org> Subject: Plug and Play naivety To: hackers@freebsd.org Date: Mon, 29 Sep 1997 09:44:41 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk My BIOs also claims to support plug and play. In Freebsd (2.2.2-R) I have set the sound card (soundblaster 16) to the same settings Windoze 95 picked up but the Kernel still can't find the card. I was going to seek out this beta driver until I saw Janice's posting. What is my recourse? Do without the sound card or find another OS? I'm already "doing without" PPP due to an obscure problem between pppd and a particular release of Bay code. I'm using Award BIOs with PCI/PnP support.. Soundblaster 16 PnP card. Micky- soft works great with the card. FreeBSD can't even see it. There doesn't even seem to be a way to turn off the PnP on the sound card. Janice McLaughlin wrote: ]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? :---==@==---==@==---==@==---: Joseph Beiter Hacking's just another word for nothing jwb@cosmic.org left to kludge. From owner-freebsd-hackers Mon Sep 29 07:46:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA14586 for hackers-outgoing; Mon, 29 Sep 1997 07:46:08 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA14581 for ; Mon, 29 Sep 1997 07:46:02 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id AAA00386; Tue, 30 Sep 1997 00:12:54 +0930 (CST) Message-Id: <199709291442.AAA00386@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Joe Beiter cc: hackers@FreeBSD.ORG Subject: Re: Plug and Play naivety In-reply-to: Your message of "Mon, 29 Sep 1997 09:44:41 -0400." <199709291344.JAA02311@xioa.cosmic.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 30 Sep 1997 00:12:52 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > My BIOs also claims to support plug and play. In Freebsd (2.2.2-R) I have > set the sound card (soundblaster 16) to the same settings Windoze 95 picked > up but the Kernel still can't find the card. Your BIOS is leaving the card disabled because it is not a device required for booting. This is correct behaviour according to the PnP standard document. Windows '95 will be performing resource allocation and activating the card. There is no code in FreeBSD 2.2.* to do this. > I was going to seek out this beta driver until I saw Janice's posting. What > is my recourse? Do without the sound card or find another OS? That depends on your requirements. I wouldn't be exactly inclined to chose an operating system based on whether or not it supported my soundcard, but your criteria may vary. > I'm already "doing without" PPP due to an obscure problem between pppd and > a particular release of Bay code. ... you could always try the usermode 'ppp', which is slightly more actively maintained, or attempt to work through your problem with Paul Mackerras. (The developer/maintainer of the 'pppd' program.) > ]1. mail from Sujal notes that "if your motherboard supports PnP > ]devices, then you don't need this code". What does this mean? It's not entirely correct, in that it implies that the PnP BIOS will leave all devices enabled. Some older systems did this; it is not universal. mike From owner-freebsd-hackers Mon Sep 29 07:55:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA15031 for hackers-outgoing; Mon, 29 Sep 1997 07:55:35 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA15014 for ; Mon, 29 Sep 1997 07:55:32 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.7/8.8.5) with ESMTP id HAA25802 for ; Mon, 29 Sep 1997 07:55:31 -0700 (PDT) Message-Id: <199709291455.HAA25802@austin.polstra.com> To: hackers@freebsd.org Subject: Re: CVS permissions after checkout In-Reply-To: <19970929091641.ZL20420@uriah.heep.sax.de> References: <199709260008.TAA10113@bob.scl.ameslab.gov> <199709290427.VAA22383@austin.polstra.com> <19970929091641.ZL20420@uriah.heep.sax.de> Organization: Polstra & Co., Seattle, WA Date: Mon, 29 Sep 1997 07:55:30 -0700 From: John Polstra Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <19970929091641.ZL20420@uriah.heep.sax.de>, J Wunsch wrote: > > Oh, no longer the missing group write permissions iff the file > creation missed them? That is great! That's right -- as long as you have a umask of 002 or something like that (00x) when you do your CVSup updates. Also, the server you are updating from has to have at least version 15.2 for this feature to work. It should have been that way all along. But I started out with the strange idea that if a user changed the permissions of some of his files, then CVSup should honor that and not change them back. Several people complained (nicely) about that, and I became convinced that they were right. Starting with the version 15.2, CVSup maintains this condition for each file: (client's modes & ~umask) == (server's modes & ~umask) where "umask" is that of the client. -- 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 Mon Sep 29 09:07:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA19251 for hackers-outgoing; Mon, 29 Sep 1997 09:07:06 -0700 (PDT) Received: from ceres.pha.jhu.edu (ceres.pha.jhu.edu [128.220.226.25]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA19213 for ; Mon, 29 Sep 1997 09:06:47 -0700 (PDT) Received: from localhost (josephm@localhost) by ceres.pha.jhu.edu (8.8.6/8.8.6) with SMTP id MAA02205 for ; Mon, 29 Sep 1997 12:06:09 -0400 (EDT) X-Authentication-Warning: ceres.pha.jhu.edu: josephm owned process doing -bs Date: Mon, 29 Sep 1997 12:06:09 -0400 (EDT) From: Joseph Moran X-Sender: josephm@ceres To: freebsd-hackers@freebsd.org Subject: termcap munged Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi all, I've munged my termcap file on a 386 system, a system with no floppy drive, cdrom or tape drive. The only way to get files on or off is through the network, and so far I can't find a replacement file on the net. Could someone throw me a copy of /etc/termcap? I'm running 2.1.6 but I doubt the format's changed. Thanks everyone, Joe Moran JHU ACM From owner-freebsd-hackers Mon Sep 29 09:20:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA20080 for hackers-outgoing; Mon, 29 Sep 1997 09:20:30 -0700 (PDT) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA20071 for ; Mon, 29 Sep 1997 09:20:23 -0700 (PDT) Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id SAA20041; Mon, 29 Sep 1997 18:19:54 +0200 (MET DST) Message-ID: <19970929181954.63240@bitbox.follo.net> Date: Mon, 29 Sep 1997 18:19:54 +0200 From: Eivind Eklund To: Andreas Klemm Cc: hackers@freebsd.org Subject: Bisdn port - would a change to 'config' be a good idea? References: <19970928160328.07959@klemm.gtn.com> <19970928165202.53879@bitbox.follo.net> <19970928172622.64875@klemm.gtn.com> <19970928182508.02645@bitbox.follo.net> <19970928191645.13276@klemm.gtn.com> <19970928202235.56072@bitbox.follo.net> <19970928210138.37935@klemm.gtn.com> <19970929015151.24733@bitbox.follo.net> <19970929084930.02876@klemm.gtn.com> <19970929162418.29237@bitbox.follo.net> <19970929173855.63705@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.69e In-Reply-To: <19970929173855.63705@klemm.gtn.com>; from Andreas Klemm on Mon, Sep 29, 1997 at 05:38:55PM +0200 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, Sep 29, 1997 at 05:38:55PM +0200, Andreas Klemm wrote: > On Mon, Sep 29, 1997 at 04:24:18PM +0200, Eivind Eklund wrote: > > On Mon, Sep 29, 1997 at 08:49:30AM +0200, Andreas Klemm wrote: > > > On Mon, Sep 29, 1997 at 01:51:51AM +0200, Eivind Eklund wrote: > > > > > > This is right. We should synchronize that with JЖrg ... > > > Optimal would be, that only the questionable modules can > > > be replaced easily. > > > > This would AFAIR only require changes to the wayfutile > > sys/${machine}/conf/files.${machine} and sys/conf/files is handled, > > allowing a way of looking for files other places, and scanning an > > extra file for them. Do you see anything more that actually require > > patching? > > Well, here a list of files and necessary changes (for -current): > [ the +indicates simply one line more ] > > 1. sys/conf/files: > > +bisdn/b_disdn.c optional disdn device-driver > +bisdn/b_isdn.c optional isdn device-driver > +bisdn/b_isdnipi.c optional ipi device-driver > +bisdn/b_isdnlap.c optional disdn device-driver > +bisdn/b_isdntel.c optional ispy device-driver > +bisdn/b_isdntel.c optional itel device-driver > +bisdn/b_isdntty.c optional ity device-driver > +net/slcompress.c optional ipi This should preferably go into a separate file, to allow cvsup to update the . To do this, we would need some way to tell config that there are extra files it should look at - possibly by an extra option in the config file. This would allow building of bisdn and similar kernel additions without modifying the normal kernel files at all. > 2. sys/i386/conf/files.i386: [actual changes deleted as irrelevant to the discussion] > 3. sys/i386/conf/options.i386: [actual changes deleted as irrelevant to the discussion] Same for the changes to these files. > 4. update LINT [actual changes deleted as irrelevant to the discussion] These are not positively required, just a convenience. They are required for the actual kernel config used to build a kernel with ISDN support, of course. > 5. make the necessary changes in MKDEV script, so that the following > devices are created: Could be done by the port directly. Not as clean for integration into the system, but nice to avoid mixup between contributions and the base system. Eivind. From owner-freebsd-hackers Mon Sep 29 09:40:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA21347 for hackers-outgoing; Mon, 29 Sep 1997 09:40:39 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [206.246.122.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA21339 for ; Mon, 29 Sep 1997 09:40:31 -0700 (PDT) Received: from Journey2.mat.net (journey2.mat.net [206.246.122.116]) by earth.mat.net (8.8.7/8.6.12) with SMTP id MAA20006; Mon, 29 Sep 1997 12:40:05 -0400 (EDT) Date: Mon, 29 Sep 1997 12:40:03 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Joseph Moran cc: freebsd-hackers@FreeBSD.ORG Subject: Re: termcap munged In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 29 Sep 1997, Joseph Moran wrote: > > Hi all, > > I've munged my termcap file on a 386 system, a system with no > floppy drive, cdrom or tape drive. The only way to get files on or off is > through the network, and so far I can't find a replacement file on the > net. Could someone throw me a copy of /etc/termcap? I'm running 2.1.6 > but I doubt the format's changed. Thanks everyone, Any possibility you mean /usr/share/misc/termcap ? > > Joe Moran > JHU ACM > > > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Mon Sep 29 09:46:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA21658 for hackers-outgoing; Mon, 29 Sep 1997 09:46:16 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA21644 for ; Mon, 29 Sep 1997 09:46:13 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.7/8.8.5) with ESMTP id JAA04828; Mon, 29 Sep 1997 09:35:46 -0700 (PDT) Message-Id: <199709291635.JAA04828@rah.star-gate.com> to: Joe Beiter cc: hackers@FreeBSD.ORG Subject: Re: Plug and Play naivety In-reply-to: Your message of "Tue, 30 Sep 1997 00:12:52 +0930." <199709291442.AAA00386@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 29 Sep 1997 09:35:46 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Joe, Questions related to sound cards to the multimedia mailing list. Luigi has a sound driver which works with Sujal Patel's PnP package. Cheers, Amancio >From The Desk Of Mike Smith : > > > > My BIOs also claims to support plug and play. In Freebsd (2.2.2-R) I have > > set the sound card (soundblaster 16) to the same settings Windoze 95 picked > > up but the Kernel still can't find the card. > > Your BIOS is leaving the card disabled because it is not a device > required for booting. This is correct behaviour according to the PnP > standard document. > > Windows '95 will be performing resource allocation and activating the > card. There is no code in FreeBSD 2.2.* to do this. > > > I was going to seek out this beta driver until I saw Janice's posting. What > > is my recourse? Do without the sound card or find another OS? > > That depends on your requirements. I wouldn't be exactly inclined to > chose an operating system based on whether or not it supported my > soundcard, but your criteria may vary. > > > I'm already "doing without" PPP due to an obscure problem between pppd and > > a particular release of Bay code. > > ... you could always try the usermode 'ppp', which is slightly more > actively maintained, or attempt to work through your problem with Paul > Mackerras. (The developer/maintainer of the 'pppd' program.) > > > ]1. mail from Sujal notes that "if your motherboard supports PnP > > ]devices, then you don't need this code". What does this mean? > > It's not entirely correct, in that it implies that the PnP BIOS will > leave all devices enabled. Some older systems did this; it is not > universal. > > mike > > > From owner-freebsd-hackers Mon Sep 29 11:03:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA26524 for hackers-outgoing; Mon, 29 Sep 1997 11:03:55 -0700 (PDT) Received: from ceres.pha.jhu.edu (ceres.pha.jhu.edu [128.220.226.25]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA26514 for ; Mon, 29 Sep 1997 11:03:50 -0700 (PDT) Received: from localhost (josephm@localhost) by ceres.pha.jhu.edu (8.8.6/8.8.6) with SMTP id OAA02737; Mon, 29 Sep 1997 14:03:09 -0400 (EDT) X-Authentication-Warning: ceres.pha.jhu.edu: josephm owned process doing -bs Date: Mon, 29 Sep 1997 14:03:08 -0400 (EDT) From: Joseph Moran X-Sender: josephm@ceres To: Gary Kendall cc: freebsd-hackers@freebsd.org Subject: Re: termcap munged In-Reply-To: <199709291651.MAA08341@ccomp.inode.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thanks Gary, the replacement worked just fine. Thanks to everyone else who got back to me (within an hour, no less), I had really run out of ideas (the only machines I had access to were Suns). Incidentally I caused this mess by wiping out /usr/share/misc to save space, but I didn't check symlinks beforehand. Live and learn... jm From owner-freebsd-hackers Mon Sep 29 11:06:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA26813 for hackers-outgoing; Mon, 29 Sep 1997 11:06:51 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA26808 for ; Mon, 29 Sep 1997 11:06:47 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id RAA06229; Mon, 29 Sep 1997 17:49:20 +0100 From: Luigi Rizzo Message-Id: <199709291649.RAA06229@labinfo.iet.unipi.it> Subject: Re: Plug and Play naivety To: jwb@xioa.cosmic.org (Joe Beiter) Date: Mon, 29 Sep 1997 17:49:19 +0100 (MET) Cc: hackers@FreeBSD.ORG In-Reply-To: <199709291344.JAA02311@xioa.cosmic.org> from "Joe Beiter" at Sep 29, 97 09:44:22 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Check out the sound and pnp code on my page (also in -current) http://www.iet.unipi.it/~luigi/FreeBSD.html this is known to work in 2.2.X and 3.0 Cheers 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 Mon Sep 29 11:24:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA28298 for hackers-outgoing; Mon, 29 Sep 1997 11:24:51 -0700 (PDT) Received: from unix.tfs.net (root@unix.tfs.net [199.79.146.60]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA28293 for ; Mon, 29 Sep 1997 11:24:48 -0700 (PDT) Received: from argus.tfs.net (pm3-p38.tfs.net [206.154.183.230]) by unix.tfs.net (8.8.5/8.8.5) with ESMTP id MAA07439; Mon, 29 Sep 1997 12:23:05 -0500 Received: (from jbryant@localhost) by argus.tfs.net (8.8.7/8.8.5) id NAA00235; Mon, 29 Sep 1997 13:24:41 -0500 (CDT) From: Jim Bryant Message-Id: <199709291824.NAA00235@argus.tfs.net> Subject: Re: termcap munged In-Reply-To: from Joseph Moran at "Sep 29, 97 12:06:09 pm" To: josephm@saturn.pha.jhu.edu (Joseph Moran) Date: Mon, 29 Sep 1997 13:24:41 -0500 (CDT) Cc: freebsd-hackers@freebsd.org Reply-to: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-Operating-System: FreeBSD 2.2.2-RELEASE #0: Wed Jul 9 01:01:24 CDT 1997 X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply: > Hi all, > > I've munged my termcap file on a 386 system, a system with no > floppy drive, cdrom or tape drive. The only way to get files on or off is > through the network, and so far I can't find a replacement file on the > net. Could someone throw me a copy of /etc/termcap? I'm running 2.1.6 > but I doubt the format's changed. Thanks everyone, > > Joe Moran > JHU ACM ftp://ftp.cdrom.com/pub/FreeBSD/FreeBSD-current/src/share/termcap/* jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28PW voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ From owner-freebsd-hackers Mon Sep 29 11:59:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA00355 for hackers-outgoing; Mon, 29 Sep 1997 11:59:38 -0700 (PDT) Received: from ns.systemresc.com (dave@[207.198.60.196]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA00349 for ; Mon, 29 Sep 1997 11:59:34 -0700 (PDT) From: dave@ns.systemresc.com Received: from localhost (dave@localhost) by ns.systemresc.com (8.8.5/8.8.5) with SMTP id OAA12254 for ; Mon, 29 Sep 1997 14:58:59 -0400 (EDT) Date: Mon, 29 Sep 1997 14:58:58 -0400 (EDT) To: hackers@FreeBSD.org Subject: tape drives and floppy Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I need some help.... I have a Mountain tape backup...connected to me floppy...and would like to use it in my 2.2.2 FreeBSD box...problem..on bootup it is not reconized...I will check the connnection but believe they are right...one thing that I have not been able to do before installing the tape drive is to use the floppy...it is not listed in fstab and when I try to mount it I get a block device not found error... I have looked in the html pages for some help with the tape drive I would like to list it in the fstab file so that it is available without mounting it...all the time...same for the floppy... all suggestion are welcome... dave From owner-freebsd-hackers Mon Sep 29 12:14:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA01228 for hackers-outgoing; Mon, 29 Sep 1997 12:14:50 -0700 (PDT) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA01223 for ; Mon, 29 Sep 1997 12:14:45 -0700 (PDT) Received: from ponds.dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.5/8.8.4) with ESMTP id PAA28745; Mon, 29 Sep 1997 15:14:20 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.8.5) with ESMTP id NAA00882; Mon, 29 Sep 1997 13:32:00 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id NAA09262; Mon, 29 Sep 1997 13:20:03 -0400 (EDT) Date: Mon, 29 Sep 1997 13:20:03 -0400 (EDT) From: Thomas David Rivers Message-Id: <199709291720.NAA09262@lakes.dignus.com> To: freebsd-hackers@freefall.FreeBSD.org, joerg_wunsch@uriah.heep.sax.de, rivers@lakes.dignus.com Subject: Re: r-cmds and DNS and /etc/host.conf Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk J"org writes: > As Thomas David Rivers wrote: > > > I originally reported this problem in version 2.1.5 of FreeBSD, on > > Aug. 16th, 1996. The subject of that message was > > > > "Nameserver and 'rlogin' in 2.1.5." > > > > it should be in the freebsd-hackers mail archives. But, at that time > > I thought it was a totally different problem and let it languish. > > Since it didn't get resolved; particularly when my network situation > > changed, I brought it back up... > > I still blame your setup. As well as Sean, i can't reproduce the > problem in a way where i could not resolve it using /etc/hosts. One > particular thing i've just noticed (by tracing the nameserver's > requests, as mentioned in the other mail) was... but first the setup, > so you can match it your situation: > > > uncle.heep.sax.de uriah.heep.sax.de > | | | > +--------------------+ +--- . . . dialup link to > Ethernet 192.168.0 Internet > > > rlogin from uriah to uncle worked well, and generated no DNS queries. > rlogin back from uncle to uriah caused one query from uriah for > `localhost.heep.sax.de', which was not resolved by placing this name > in /etc/hosts on uriah. I then found that i had to replace the line > > 127.1 localhost localhost.heep.sax.de > > by > > 127.0.0.1 localhost localhost.heep.sax.de > > and *bingo* it worked. Now, we've been discussing this before... > > (Ok, now fix the broken setup again to use DNS for everything. Heck, > why should i rely on outdated /etc/hosts files? :-) > > -- Oh yes, if you recall, I moaned about this some months ago... (which prompted many pieces of mail say "127.1" isn't valid; but historical, etc...) Anyway - at one time, that was my fix... but now it's not. My host file has: 127.0.0.1 localhost.dignus.com. localhost.dignus.com localhost 10.0.0.1 ponds ponds.dignus.com ponds.dignus.com. 10.0.0.3 lakes lakes.dignus.com lakes.dignus.com. - Dave Rivers - From owner-freebsd-hackers Mon Sep 29 12:16:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA01402 for hackers-outgoing; Mon, 29 Sep 1997 12:16:49 -0700 (PDT) Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA01397 for ; Mon, 29 Sep 1997 12:16:43 -0700 (PDT) Received: from panke.panke.de (anonymous213.ppp.cs.tu-berlin.de [130.149.17.213]) by mail.cs.tu-berlin.de (8.8.6/8.8.7) with ESMTP id VAA17358 for ; Mon, 29 Sep 1997 21:10:21 +0200 (MET DST) Received: (from wosch@localhost) by panke.panke.de (8.8.5/8.6.12) id UAA16748; Mon, 29 Sep 1997 20:43:57 +0200 (MET DST) Date: Mon, 29 Sep 1997 20:43:57 +0200 (MET DST) Message-Id: <199709291843.UAA16748@panke.panke.de> From: Wolfram Schneider To: hackers@freebsd.org Subject: no documentation for mk_cmds(1) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk What does the mk_cmds(1) command do? -- Wolfram Schneider http://www.apfel.de/~wosch/ From owner-freebsd-hackers Mon Sep 29 12:33:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA02604 for hackers-outgoing; Mon, 29 Sep 1997 12:33:32 -0700 (PDT) Received: from unix.tfs.net (root@unix.tfs.net [199.79.146.60]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA02599 for ; Mon, 29 Sep 1997 12:33:29 -0700 (PDT) Received: from argus.tfs.net (pm3-p38.tfs.net [206.154.183.230]) by unix.tfs.net (8.8.5/8.8.5) with ESMTP id NAA19342; Mon, 29 Sep 1997 13:31:46 -0500 Received: (from jbryant@localhost) by argus.tfs.net (8.8.7/8.8.5) id OAA00425; Mon, 29 Sep 1997 14:33:22 -0500 (CDT) From: Jim Bryant Message-Id: <199709291933.OAA00425@argus.tfs.net> Subject: Re: tape drives and floppy In-Reply-To: from "dave@ns.systemresc.com" at "Sep 29, 97 02:58:58 pm" To: dave@ns.systemresc.com Date: Mon, 29 Sep 1997 14:33:22 -0500 (CDT) Cc: freebsd-hackers@freebsd.org Reply-to: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-Operating-System: FreeBSD 2.2.2-RELEASE #0: Wed Jul 9 01:01:24 CDT 1997 X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply: > I need some help.... > > I have a Mountain tape backup...connected to me floppy...and would like to > use it in my 2.2.2 FreeBSD box...problem..on bootup it is not > reconized...I will check the connnection but believe they are right...one controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 tape ft0 at fdc0 drive 2 ## Enable Floppy-tape support jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28PW voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ From owner-freebsd-hackers Mon Sep 29 12:36:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA02864 for hackers-outgoing; Mon, 29 Sep 1997 12:36:29 -0700 (PDT) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA02857 for ; Mon, 29 Sep 1997 12:36:25 -0700 (PDT) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id PAA07420; Mon, 29 Sep 1997 15:28:30 -0400 Date: Mon, 29 Sep 1997 15:28:29 -0400 (EDT) From: "Ron G. Minnich" X-Sender: rminnich@terra To: hackers@freebsd.org Subject: PCI device loadable module Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk maybe this is all clear on 3.0, but i am on 2.2.1. Here's the question: I have a loadable module for a device. How do I arrange for the probe() to be called? As i understand it on fbsd this happens at pci_configure time, which is done at boot time. But my driver is not in at that point, obviously: so what's the right thing to do? pci_configure says it can be called more than once. So, should my load entry point call pci_configure()? what's the right way here? There are no examples in the lkm's that I can find that point the way. thanks ron Ron Minnich |Java: an operating-system-independent, rminnich@sarnoff.com |architecture-independent programming language (609)-734-3120 |for Windows/95 and Windows/NT on the Pentium ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html From owner-freebsd-hackers Mon Sep 29 12:49:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA03719 for hackers-outgoing; Mon, 29 Sep 1997 12:49:41 -0700 (PDT) Received: from frodo.epigram.com ([199.2.31.210]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA03709 for ; Mon, 29 Sep 1997 12:49:33 -0700 (PDT) Received: from mail.epigram.com (DALAT.epigram.com [10.100.100.211]) by frodo.epigram.com (8.7.5/8.7.3) with ESMTP id MAA19290 for ; Mon, 29 Sep 1997 12:49:30 -0700 (PDT) Message-ID: <3430063E.5B8B5E43@mail.epigram.com> Date: Mon, 29 Sep 1997 12:49:18 -0700 From: Brandon Huey Reply-To: brandon@epigram.com Organization: Epigram, Inc. X-Mailer: Mozilla 4.03 [en] (WinNT; I) MIME-Version: 1.0 To: hackers@freebsd.org Subject: amd: nfs_ops.c undeclared instance of MOUNTVERS3 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk i'm trying to build an amd under 2.2.2 that will only use NFSv2. However, make says: nfs_ops.c: In function `got_nfs_fh': nfs_ops.c:172: `MOUNTVERS3' undeclared (first use this function) nfs_ops.c:172: (Each undeclared identifier is reported only once nfs_ops.c:172: for each function it appears in.) nfs_ops.c:173: `xdr_mountres3' undeclared (first use this function) nfs_ops.c: In function `discard_fh': nfs_ops.c:226: `MOUNTVERS3' undeclared (first use this function) nfs_ops.c:227: `xdr_mountres3' undeclared (first use this function) nfs_ops.c: In function `prime_nfs_fhandle_cache': nfs_ops.c:259: `MNT3ERR_NOTSUPP' undeclared (first use this function) nfs_ops.c:259: `MNT3ERR_SERVERFAULT' undeclared (first use this function) nfs_ops.c:347: `MOUNTVERS3' undeclared (first use this function) *** Error code 1 we checked all the header files we could to see where it might have been defined and turned up nothing. this all relates back to my desire to force amd to use only nfs v2... i'd like to correspond out of this group if possible via email. thank you. -- Brandon Huey brandon@epigram.com Epigram, Inc. +1 415 843 4487 From owner-freebsd-hackers Mon Sep 29 13:50:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA08684 for hackers-outgoing; Mon, 29 Sep 1997 13:50:36 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA08675 for ; Mon, 29 Sep 1997 13:50:31 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA23228 for freebsd-hackers@freefall.FreeBSD.org; Mon, 29 Sep 1997 22:50:23 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id WAA05492; Mon, 29 Sep 1997 22:25:08 +0200 (MET DST) Message-ID: <19970929222507.QI17620@uriah.heep.sax.de> Date: Mon, 29 Sep 1997 22:25:07 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freefall.FreeBSD.org Subject: Re: r-cmds and DNS and /etc/host.conf References: <199709291720.NAA09262@lakes.dignus.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199709291720.NAA09262@lakes.dignus.com>; from Thomas David Rivers on Sep 29, 1997 13:20:03 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Thomas David Rivers wrote: > Anyway - at one time, that was my fix... but now it's not. > My host file has: > > > 127.0.0.1 localhost.dignus.com. localhost.dignus.com localhost > 10.0.0.1 ponds ponds.dignus.com ponds.dignus.com. > 10.0.0.3 lakes lakes.dignus.com lakes.dignus.com. Didn't you say there's another domain involved (by resolv.conf, IIRC)? David, why don't you simply start a caching-only nameserver, redirect your resolv.conf(s) to it, and look at its debug output? This will lead you *way quicker* to the solution about what names are being looked up than any of our guesswork here in the mailinglist. A caching-only nameserver is a matter of one minute: cd /etc/namedb sh make-localhost named -d 2 -b /etc/namedb/named.boot FreeBSD ships with a reasonable default named.boot for a caching-only server (which also has a bunch of comments for what to do to add a secondary). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Mon Sep 29 14:01:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA09528 for hackers-outgoing; Mon, 29 Sep 1997 14:01:39 -0700 (PDT) Received: from toth.ferginc.com (toth.ferginc.com [205.139.23.69]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA09515 for ; Mon, 29 Sep 1997 14:01:36 -0700 (PDT) Received: by toth.ferginc.com (You/Wish) id QAA15612; Mon, 29 Sep 1997 16:59:33 -0400 (EDT) Posted-Date: Mon, 29 Sep 1997 16:59:33 -0400 (EDT) Message-ID: <19970929165933.10373@toth.hq.ferg.com> Date: Mon, 29 Sep 1997 16:59:33 -0400 From: Branson Matheson To: Bill Paul Cc: hackers@FreeBSD.ORG Subject: can you do me a fav. Reply-To: Branson.Matheson@ferginc.com References: <199709271825.OAA13926@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <199709271825.OAA13926@skynet.ctr.columbia.edu>; from Bill Paul on Sat, Sep 27, 1997 at 02:25:26PM -0400 Organization: Ferguson Enterprises, Inc. X-Operating-System: FreeBSD 2.2.2-RELEASE Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I am still chasing the amd problem... got the latest patches that they recomended and that did not solve the problem... can you do for me a swlist -l product | grep PH | mail branson@ferginc.com I'd greatly appreciate it! -branson From owner-freebsd-hackers Mon Sep 29 14:39:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA11822 for hackers-outgoing; Mon, 29 Sep 1997 14:39:08 -0700 (PDT) Received: from toth.ferginc.com (toth.ferginc.com [205.139.23.69]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA11815 for ; Mon, 29 Sep 1997 14:39:05 -0700 (PDT) Received: by toth.ferginc.com (You/Wish) id RAA16429; Mon, 29 Sep 1997 17:38:33 -0400 (EDT) Posted-Date: Mon, 29 Sep 1997 17:38:33 -0400 (EDT) Message-ID: <19970929173833.32809@toth.hq.ferg.com> Date: Mon, 29 Sep 1997 17:38:33 -0400 From: Branson Matheson To: freebsd-hackers@freebsd.org Subject: OOps... I am a retard Reply-To: Branson.Matheson@ferginc.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e Organization: Ferguson Enterprises, Inc. X-Operating-System: FreeBSD 2.2.2-RELEASE Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ok .. so a reply to Bill Paul somehow got the CC line in it as well to hackers... I am a dweeb and I humbly beg this lists understanding of a long day and fumble fingers ( I have an appt with the local digit dr to get them replaced. ) -branson From owner-freebsd-hackers Mon Sep 29 14:50:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA12818 for hackers-outgoing; Mon, 29 Sep 1997 14:50:14 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA12811 for ; Mon, 29 Sep 1997 14:50:11 -0700 (PDT) Received: from x14.mi.uni-koeln.de ([134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA07171 (5.67b/IDA-1.5 for ); Mon, 29 Sep 1997 23:50:07 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.7/8.6.9) id XAA00488; Mon, 29 Sep 1997 23:50:03 +0200 (CEST) X-Face: " Date: Mon, 29 Sep 1997 23:50:03 +0200 From: Stefan Esser To: "Ron G. Minnich" Cc: hackers@FreeBSD.ORG Subject: Re: PCI device loadable module References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: ; from Ron G. Minnich on Mon, Sep 29, 1997 at 03:28:29PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sep 29, "Ron G. Minnich" wrote: > maybe this is all clear on 3.0, but i am on 2.2.1. Hmm, I added PCI LKM support to the then 2.2-current in January 1997, but it has been temporarily disabled there, when I replaced the PCI code by a total rewrite ... Since I expected some data structures to change again, I did not move these changes into the -stable tree, yet. You want revision 1.64 of /sys/pci/pci.c and revision 1.8 of /sys/pci/pcibus.h, which should just fit into a 2.2.1 source tree. Let me know, if you have any trouble with them! > Here's the question: I have a loadable module for a device. How do I > arrange for the probe() to be called? As i understand it on fbsd this > happens at pci_configure time, which is done at boot time. But my driver > is not in at that point, obviously: so what's the right thing to do? You call pci_register_lkm(&xxx_device). The parameter is the address of the struct pci_device that is put into the DATA_SET in case of a compiled in driver ... > pci_configure says it can be called more than once. So, should my load > entry point call pci_configure()? what's the right way here? There are no > examples in the lkm's that I can find that point the way. The following is from a message I sent to the -current list on January 22, 1997: % From se@freebsd.org Wed Jan 22 05:18:09 1997 % Subject: PCI LKM support added to -current % % On Jan 21, se@freefall.freebsd.org (Stefan Esser) wrote: % > se 97/01/21 15:41:44 % > % > Modified: sys/pci pcibus.h % > Log: % > Add PCI LKM support: % > The new function pci_register_lkm (struct pci_device *dvp) appends the % > driver to the list of known PCI drivers, and initiates a PCI bus rescan. % % This completes my changes to add PCI LKM support to FreeBSD-current. % % Some code has to be called from /etc/rc, if PCI LKMs are to be modloaded % automatically as part of going multi-user. % % I'm suggesting something as follows (to be called from rc.d): % % *** /dev/null Tue Dec 31 15:02:04 1996 % --- load-pci-lkm.sh Tue Dec 31 14:25:31 1996 % *************** % *** 0 **** % --- 1,12 ---- % + #!/bin/sh % + for dev in `pciconf -l |cut -f1` % + do % + if pciconf -a $dev | grep -q "not attached" % + then % + DevVendorID=`pciconf -r $dev 0` % + LKM=`grep $DevVendorID /etc/pcidevices | cut -f 2` % + LKMfile=/lkm/pci/$LKM.o % + echo "$dev Loading $LKMfile for DevVendorID $DevVendorID" % + modload $LKMfile % + fi % + done % % The file /etc/pcidevices will contain lines with the PCI vendor and device % ID, and an associated driver object file: % % 0x802910ec if_ed % % % In order to attach a PCI LKM, just call pci_register_lkm with the address % of a struct pci_device (which is a parameter to the DATA_SET macro in the % non-LKM case). On return from pci_register_lkm(), all devices that have % no driver attached, will have been offered to the new device's probe() % function, and will have been attached, if the probe succeeded. Regards, STefan From owner-freebsd-hackers Mon Sep 29 16:01:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA16734 for hackers-outgoing; Mon, 29 Sep 1997 16:01:11 -0700 (PDT) Received: from usr09.primenet.com (tlambert@usr09.primenet.com [206.165.6.209]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA16727 for ; Mon, 29 Sep 1997 16:01:07 -0700 (PDT) Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id QAA18099; Mon, 29 Sep 1997 16:00:26 -0700 (MST) From: Terry Lambert Message-Id: <199709292300.QAA18099@usr09.primenet.com> Subject: Re: INB question To: tony@dell.com (Tony Overfield) Date: Mon, 29 Sep 1997 23:00:24 +0000 (GMT) Cc: Shimon@i-Connect.Net, tlambert@primenet.com, hackers@FreeBSD.ORG In-Reply-To: <3.0.2.32.19970929030500.006ff1c0@bugs.us.dell.com> from "Tony Overfield" at Sep 29, 97 03:05:00 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > This was first hooked up this way back in 1981 when the first IBM PC > came out. This has been working the same way for over 15 years. > They had no way to know that it would suddenly become a problem for > Terry in late 1997. Or anyone else programming an MCA DMA register. > They probably didn't even realize that the circuit > lacked "vision," since they had no idea they were laying the > foundations of such a colossal legacy. Heh. Because they lacked "vision"... 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 29 16:02:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA16792 for hackers-outgoing; Mon, 29 Sep 1997 16:02:02 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA16787 for ; Mon, 29 Sep 1997 16:01:58 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id JAA09404; Tue, 30 Sep 1997 09:01:39 +1000 (EST) Date: Tue, 30 Sep 1997 09:01:39 +1000 (EST) From: "Daniel O'Callaghan" To: =?iso-8859-1?Q?=DEor=F0ur?= Ivarsson cc: FreeBSD-hackers@FreeBSD.ORG Subject: Re: Is something broken in PPPD? In-Reply-To: <342F9686.41C67EA6@est.is> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 29 Sep 1997, =?iso-8859-1?Q?=DEor=F0ur?= Ivarsson wrote: > I am administrator for ISP service in Iceland and have some problem. > > four lines are connected to our FreeBSD server and are using > PPPD started through ttys(5). > When looking at last(1) output I see lot of connections that are "still > logged in" > even thoug they are dead. What version of FreeBSD are you using? Grab my pppkit from ftp://ftp.hilink.com.au/pub/FreeBSD/pppkit.tgz for a version of pppd which I made sure would work. Danny From owner-freebsd-hackers Mon Sep 29 21:46:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA01861 for hackers-outgoing; Mon, 29 Sep 1997 21:46:02 -0700 (PDT) Received: from gras-varg.worldgate.com (skafte@gras-varg.worldgate.com [198.161.84.12]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA01855; Mon, 29 Sep 1997 21:45:55 -0700 (PDT) Received: (from skafte@localhost) by gras-varg.worldgate.com (8.8.7/8.6.12) id WAA06419; Mon, 29 Sep 1997 22:45:54 -0600 (MDT) Message-ID: <19970929224553.56867@worldgate.com> Date: Mon, 29 Sep 1997 22:45:53 -0600 From: Greg Skafte To: freebsd-stable@freebsd.org Cc: Freebsd-hackers@freebsd.org Subject: libncurses ..... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 Organization: WorldGate Inc. X-PGP-Fingerprint: 42 9C 2C A8 4D 2B C9 C4 7D B6 00 B0 50 47 20 97 X-URL: http://gras-varg.worldgate.com/~skafte Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Outta curiosity for libncurses why are we using 1.8.6 instead of the current 4.1 in 2.2-stable ..... -- Email: skafte@worldgate.com Voice: +403 413 1910 Fax: +403 421 4929 #575 Sun Life Place * 10123 99 Street * Edmonton, AB * Canada * T5J 3H1 -- -- When things can't get any worse, they simplify themselves by getting a whole lot worse then complicated. A complete and utter disaster is the simplest thing in the world; it's preventing one that's complex. (Janet Morris) From owner-freebsd-hackers Mon Sep 29 21:54:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA02263 for hackers-outgoing; Mon, 29 Sep 1997 21:54:05 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA02257 for ; Mon, 29 Sep 1997 21:53:59 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id VAA00680 for ; Mon, 29 Sep 1997 21:53:50 -0700 (PDT) Date: Mon, 29 Sep 1997 21:53:50 -0700 (PDT) From: "Jamil J. Weatherbee" To: freebsd-hackers@freebsd.org Subject: Good Lord, Commercial Linux Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I was taking a look at Calderas web page noticing that their OpenLinux Standard is $399, and wondering who would be willing to pay such a price for a commercial Linux --- Of course if FreeBSD Inc. would put together a commercial FreeBSD with similar features I'd be willing to spend $300-$400 on it, as long as you could continue to keep up with the base installation through cvsup/make world. Staroffice port to freebsd? Please. From owner-freebsd-hackers Mon Sep 29 21:59:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA02625 for hackers-outgoing; Mon, 29 Sep 1997 21:59:41 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA02619 for ; Mon, 29 Sep 1997 21:59:35 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id VAA00692 for ; Mon, 29 Sep 1997 21:59:26 -0700 (PDT) Date: Mon, 29 Sep 1997 21:59:26 -0700 (PDT) From: "Jamil J. Weatherbee" To: freebsd-hackers@freebsd.org Subject: Packet Routing.. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am not sure about the mechanism, but If I have a freebsd machine acting as a firewall between a 10bT Ethernet and fractional to full T1. How does the gatewaying/firewalling ability degrade as a function of the load of unrelated processes on that machine. In other words I am running some huge backup/ big simulation on my firewall (lets say a PPro 200) does it measurably effect the Throughput of the firewall? Does anyone have some numbers on this. Basically saying what the networking capabilities of freebsd are on variously configured machines. Like would it be a bad Idea to use a freebsd machine as a router between 4 100 baseT networks and a T1? From owner-freebsd-hackers Mon Sep 29 23:34:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA06439 for hackers-outgoing; Mon, 29 Sep 1997 23:34:13 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA06420 for ; Mon, 29 Sep 1997 23:34:03 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.71 #1) id 0xFvs7-0001Px-00; Mon, 29 Sep 1997 23:33:27 -0700 Date: Mon, 29 Sep 1997 23:33:22 -0700 (PDT) From: Tom To: "Jamil J. Weatherbee" cc: freebsd-hackers@freebsd.org Subject: Re: Packet Routing.. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 29 Sep 1997, Jamil J. Weatherbee wrote: > I am not sure about the mechanism, but If I have a freebsd machine acting > as a firewall between a 10bT Ethernet and fractional to full T1. How does > the gatewaying/firewalling ability degrade as a function of the load of > unrelated processes on that machine. In other words I am running some huge > backup/ big simulation on my firewall (lets say a PPro 200) does it > measurably effect the Throughput of the firewall? Does anyone have some > numbers on this. Basically saying what the networking capabilities of > freebsd are on variously configured machines. Like would it be a bad Idea > to use a freebsd machine as a router between 4 100 baseT networks and a > T1? You are going to have to measure it. You need to look at the number of packets per second your hardware can handle. You shouldn't have a throughput problems unless you hit your motherboard's memory bandwith limit. So you need to figure out the packet per second rate your router box must be able to handle. Other processes running on your router box shouldn't degrade performance severely unless the CPU is at 100%, although you may see more latency. Some things to measure: latency - how long it takes to process (route) a packet pps - how many packets per second it can process throughput - how many bytes per second it can process Tom From owner-freebsd-hackers Tue Sep 30 00:32:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA09551 for hackers-outgoing; Tue, 30 Sep 1997 00:32:38 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id AAA09542 for ; Tue, 30 Sep 1997 00:32:32 -0700 (PDT) Received: (qmail 28454 invoked by uid 1000); 30 Sep 1997 07:32:57 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092597 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 30 Sep 1997 00:32:57 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: "Jamil J. Weatherbee" Subject: RE: Good Lord, Commercial Linux Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi "Jamil J. Weatherbee"; On 30-Sep-97 you wrote: > > I was taking a look at Calderas web page noticing that their OpenLinux > Standard is $399, and wondering who would be willing to pay such a price > for a commercial Linux ... Actually, if you raise the price to $700, it will sell even better. If you reduce the number of releases to 1 per year, you can charge even more. I doubt FreeBSd will ever be able to do that, on that scale. Justification: a. If it is free it is useless. You get what you pay for. Why would anyone give away anything which is of any value? b. The fewer releases, the more ``stable'' your product. If you doubt this statement, search for some high-level sales aids for NiceTry. Or Slowlaris, for that matter. c. BSD came from Berkeley, it is a hack. Linux is systemV like. It has a heritage of Large Company. Caldera was founded by Mr. Noorda, he is the radical rebel of Corporate America. Made billions with Novell. Calder Linux must therfore be a good thing. Now, BEFORE you jump down my throat, please evaluate the technology I employ in my professional work :-) BTW, join the Debian developers list. You will see a volunteer project gone mad with commercialism... --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-hackers Tue Sep 30 01:20:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA12523 for hackers-outgoing; Tue, 30 Sep 1997 01:20:27 -0700 (PDT) Received: from styx.aic.net (Styx.AIC.NET [195.250.64.68]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA12514 for ; Tue, 30 Sep 1997 01:20:15 -0700 (PDT) Received: (from ran@localhost) by styx.aic.net (8.8.5/8.8.5) id MAA24711; Tue, 30 Sep 1997 12:18:42 +0400 (AMT) Message-Id: <199709300818.MAA24711@styx.aic.net> Subject: Re: Plug and Play naivety In-Reply-To: <199709291344.JAA02311@xioa.cosmic.org> from Joe Beiter at "Sep 29, 97 09:44:41 am" To: jwb@xioa.cosmic.org (Joe Beiter) Date: Tue, 30 Sep 1997 12:18:42 +0400 (AMT) Cc: hackers@FreeBSD.ORG From: ran@ran.am Reply-To: ran@ran.am X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Hi, some time ago i had same problem, - ISA PnP motherboard, PnP sound card, but it didn't work under FreeBSD. after check out all of possible, I found some interesting info - Intel 430HX chipset doesn't configure ISA PnP devices IRQ and DMA channels, it only assigns io addresses. In this case, you need to use Sujal Patels PnP code to configure PnP sound card. > My BIOs also claims to support plug and play. In Freebsd (2.2.2-R) I have > set the sound card (soundblaster 16) to the same settings Windoze 95 picked > up but the Kernel still can't find the card. > > I was going to seek out this beta driver until I saw Janice's posting. What > is my recourse? Do without the sound card or find another OS? > > I'm already "doing without" PPP due to an obscure problem between pppd and > a particular release of Bay code. > > I'm using Award BIOs with PCI/PnP support.. Soundblaster 16 PnP card. Micky- > soft works great with the card. FreeBSD can't even see it. There doesn't > even seem to be a way to turn off the PnP on the sound card. > > Janice McLaughlin wrote: > ]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? > > > :---==@==---==@==---==@==---: > Joseph Beiter Hacking's just another word for nothing > jwb@cosmic.org left to kludge. -- Ran d'Adi ran@ran.am ran@styx.aic.net From owner-freebsd-hackers Tue Sep 30 02:02:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA14563 for hackers-outgoing; Tue, 30 Sep 1997 02:02:48 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id CAA14523 for ; Tue, 30 Sep 1997 02:02:29 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id IAA07579; Tue, 30 Sep 1997 08:35:40 +0100 From: Luigi Rizzo Message-Id: <199709300735.IAA07579@labinfo.iet.unipi.it> Subject: Re: Plug and Play naivety To: ran@ran.am Date: Tue, 30 Sep 1997 08:35:40 +0100 (MET) Cc: jwb@xioa.cosmic.org, hackers@FreeBSD.ORG In-Reply-To: <199709300818.MAA24711@styx.aic.net> from "ran@ran.am" at Sep 30, 97 12:18:23 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Hi, > some time ago i had same problem, - ISA PnP motherboard, > PnP sound card, but it didn't work under FreeBSD. > after check out all of possible, I found some interesting info - > Intel 430HX chipset doesn't configure ISA PnP devices IRQ and DMA > channels, it only assigns io addresses. it is not something the chipset does, it is the BIOS or the OS. > In this case, you need to use Sujal Patels PnP code to configure > PnP sound card. I strongly suggest to pick up my version of the PnP code, which is largely based over Sujal code but much easier to configure via userconfig. You can find it in -current or at http://www.iet.unipi.it/~luigi/FreeBSD.html Cheers Luigi From owner-freebsd-hackers Tue Sep 30 07:51:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA29366 for hackers-outgoing; Tue, 30 Sep 1997 07:51:32 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA29353 for ; Tue, 30 Sep 1997 07:51:24 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id AAA00810 for ; Wed, 1 Oct 1997 00:19:00 +0930 (CST) Message-Id: <199709301449.AAA00810@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: hackers@freebsd.org Subject: Interface configuration : call for ideas. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 01 Oct 1997 00:18:58 +0930 From: Mike Smith Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In the light of various issues I've been considering the way that network interface configuration is handled from user-space. Currently, interface configuration is handled by /etc/rc.network at startup for static network interfaces, by /etc/ppcard.ether for PCCARDs and by assorted internal configuration magic for PPP and SLIP links. In many cases this diversity is undesirable. It doesn't handle adding such extra interface attributes such as static routes in a consistent fashion, and it is difficult to configure. To address some of these concerns, a model along the following lines is proposed. Please note that there are undoubtably problems with this model, and the author would appreciate vigorous criticism of any percieved weaknesses. If this is swallowed reasonably well, a proposed '/etc/rc.interface' and accompanying details will be put forward. Comments? = = = = = = = = = The arrival of an unconfigured interface is viewed as an event. The set of consequences of this event should include: - Startup script(s) for the interface and address families being run. - The interface being given address details, possibly for more than one address family. In order to achieve this, the following information may need to be available or inferrable: o An association between an interface name or type and an address. This may be effected by allowing interface address details to be attached to an interface name or type. On interface arrival, if no address details are attached to the name of the interface, details should be retrieved from the first association to the interface type. One means of achieving this would be to evolve from the current rc.conf parameters. For example, consider : ifconfig_ed0="inet 10.2.3.4" ifconfig_lan="inet 10.5.6.7" The arrival of the interface "ed0" would result in it having the address 10.2.3.4 configured. If the interface "fxp0" were to arrive, there would be no address directly associated with it. In this case, as "fxp0" is of type "lan", the generic "lan" address 10.5.6.7 would be assigned to it. Notes: It might be seen as desirable to have more than one of these generic type-associated addresses available, however it is not clear how it could safely be determined which interface should obtain which address. "Address" should be considered to include "address solicitation technique" (eg. BOOTP, DHCP). o An association between the specific arrival event, interface name and address details. Such information may be attached to the arrival event, as it is likely to have been derived as part of the arrival process (eg. PPP negotiation, SLIP login, etc.). o Locations to be searched for startup scripts. The departure of an interface is viewed as an event. The set of consequences of this event should include: - Shutdown script(s) for the interface and address families being run. - Address details being taken from the interface, if it still exists. In most cases, the removal of an interface automatically cleans up behind itself. Shutdown would only be relevant if there were daemons associated with the interface which needed to be cleaned up. The arrival of new address information on an interface is viewed as an event, with the following possible consequences: - Routing alterations being made to accomodate the new interface. A specific set of routing directives should be associated with an given interface address, or possibly indirectly via the interface name or type. This might be achieved by adding a directory etc/routes containing files named after interfaces, interface types or interface addresses, or possibly definitions in rc.conf. There are a number of possiblities for feature-creep here (eg. matching to a range of addresses). The departure of address information is viewed as an event, with the following consequences: - Routing information for the interface being removed, if it still exists. This should normally be taken care of by the removal of the interface iteself. From owner-freebsd-hackers Tue Sep 30 07:57:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA29600 for hackers-outgoing; Tue, 30 Sep 1997 07:57:20 -0700 (PDT) Received: from onyx.atipa.com (user9259@ns.atipa.com [208.128.22.10]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id HAA29595 for ; Tue, 30 Sep 1997 07:57:17 -0700 (PDT) Received: (qmail-queue invoked by uid 1018); 30 Sep 1997 15:01:37 -0000 Date: Tue, 30 Sep 1997 09:01:36 -0600 (MDT) From: Atipa X-Sender: freebsd@dot.ishiboo.com To: Simon Shapiro cc: "Jamil J. Weatherbee" , freebsd-hackers@FreeBSD.ORG Subject: RE: Good Lord, Commercial Linux In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 30 Sep 1997, Simon Shapiro wrote: > > Hi "Jamil J. Weatherbee"; On 30-Sep-97 you wrote: > > > > I was taking a look at Calderas web page noticing that their OpenLinux > > Standard is $399, and wondering who would be willing to pay such a price > > for a commercial Linux > > ... > > Actually, if you raise the price to $700, it will sell even better. > If you reduce the number of releases to 1 per year, you can charge even > more. I agree! It is a huge marketing faux pas to assume people are smart. That is why some very smart people are bad businessmen; they think other people are just as rational... haha The average consumer falls back on a herd mentality. Nice points, Simon! "A" and "B" are good; "C" I don't agree with as much. The whole fact that FreeBSD is an OS and not a _kernel_ makes it entirely more consistent. As SystemVish as it wants to be, each Linux release will have its own nuances, which seem much more of a kludge/hack to me. If you want to be truly "mainstream", all you need to do is have a GUI administration suite, then people won't know the difference. Yuck, I can't believe I just said that. That sounds gross even for a Devil's Advocate! Kevin > Justification: > > a. If it is free it is useless. You get what you pay for. Why would > anyone give away anything which is of any value? > > b. The fewer releases, the more ``stable'' your product. If you doubt > this statement, search for some high-level sales aids for NiceTry. > Or Slowlaris, for that matter. > > c. BSD came from Berkeley, it is a hack. Linux is systemV like. It has a > heritage of Large Company. Caldera was founded by Mr. Noorda, he is > the radical rebel of Corporate America. Made billions with Novell. > Calder Linux must therfore be a good thing. > > Now, BEFORE you jump down my throat, please evaluate the technology I > employ in my professional work :-) > > > BTW, join the Debian developers list. You will see a volunteer project > gone mad with commercialism... > > --- > > > Sincerely Yours, > > Simon Shapiro Atlas Telecom > Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 > Shimon@i-Connect.Net Voice: 503.799.2313 > From owner-freebsd-hackers Tue Sep 30 07:58:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA29709 for hackers-outgoing; Tue, 30 Sep 1997 07:58:49 -0700 (PDT) Received: from tor-adm1.nbc.netcom.ca (taob@tor-adm1.nbc.netcom.ca [207.181.89.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA29689; Tue, 30 Sep 1997 07:58:44 -0700 (PDT) Received: (from taob@localhost) by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) id KAA15636; Tue, 30 Sep 1997 10:58:35 -0400 (EDT) Date: Tue, 30 Sep 1997 10:58:35 -0400 (EDT) From: Brian Tao To: FREEBSD-HACKERS cc: FREEBSD-ISP Subject: Cyclades Cyclom-Y PCI multiport serial as console server? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Before I start more troubleshooting, has anyone used the Cyclom-Y 16-port PCI serial controllers as null modem ports? We have several dozen pieces of equipment here that all have serial console ports (Sparcs, Ciscos, Netapps, etc.) Rather than running around with a long cable attached to a VT-420, I wanted to build a FreeBSD box with 64 serial ports and just use cu to get console access. I note that the cy(4) man page from a May 1997 3.0 snapshot states: > BUGS > BREAK is not yet implemented. > > Serial consoles are not implemented. Is there a newer version that does allow me to send breaks to the remote side (very important if you're dealing with Sparcs)? What exactly does "serial consoles" mean in this context? If it works with a modem, I don't see why I can't slap a null modem changer on the cable, and use it as a serial console. I've already modifed /etc/rc.serial to set the ttyc* and cuac* devices to "terminal" rather than the default of "modem". Anything else I need to do? -- Brian Tao (BT300, taob@netcom.ca) "Though this be madness, yet there is method in't" From owner-freebsd-hackers Tue Sep 30 08:24:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA01255 for hackers-outgoing; Tue, 30 Sep 1997 08:24:36 -0700 (PDT) Received: from mailhost.Ipsilon.COM (mailhost.ipsilon.com [205.226.5.12]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id IAA01241 for ; Tue, 30 Sep 1997 08:24:34 -0700 (PDT) Received: from quito.ipsilon.com (quito.Ipsilon.COM [205.226.1.246]) by mailhost.Ipsilon.COM (8.6.11/8.6.10) with ESMTP id IAA29906 for ; Tue, 30 Sep 1997 08:23:58 -0700 Message-Id: <199709301523.IAA29906@mailhost.Ipsilon.COM> X-Mailer: exmh version 2.0gamma 1/27/96 To: freebsd-hackers@freebsd.org Subject: src to netboot for PCI cards Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 30 Sep 1997 08:24:15 -0700 From: Adrian Caceres Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I need to implement an option rom for a network pci card. I am looking for src to a netboot that I can use as a model/base. The src in 2.2.2 or 3.0 uses an isa model and I need pci. Trying not to reinvent the wheel so any pointers/suggestions are appreciated. email to ali@ipsilon.com thanks adrian From owner-freebsd-hackers Tue Sep 30 08:48:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA02697 for hackers-outgoing; Tue, 30 Sep 1997 08:48:31 -0700 (PDT) Received: from mail.virginia.edu (mail.Virginia.EDU [128.143.2.9]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id IAA02685 for ; Tue, 30 Sep 1997 08:48:22 -0700 (PDT) Received: from ares.cs.virginia.edu by mail.virginia.edu id aa00745; 30 Sep 97 11:47 EDT Received: from stretch.cs.virginia.edu (atf3r@stretch-fo.cs.Virginia.EDU [128.143.136.14]) by ares.cs.Virginia.EDU (8.8.5/8.8.5) with ESMTP id LAA01637; Tue, 30 Sep 1997 11:47:49 -0400 (EDT) Received: (from atf3r@localhost) by stretch.cs.virginia.edu (8.8.5/8.8.5) id LAA02903; Tue, 30 Sep 1997 11:47:47 -0400 (EDT) Date: Tue, 30 Sep 1997 11:47:47 -0400 (EDT) From: "Adrian T. Filipi-Martin" Reply-To: adrian@virginia.edu To: Simon Shapiro cc: "Jamil J. Weatherbee" , freebsd-hackers@freebsd.org Subject: RE: Good Lord, Commercial Linux In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 30 Sep 1997, Simon Shapiro wrote: > c. BSD came from Berkeley, it is a hack. Linux is systemV like. It has a > heritage of Large Company. Caldera was founded by Mr. Noorda, he is Ahem! Linux has no such "heritage". That's why it too is free. The linux crowd just whent the SYSV like API. Designing a car that looks like a volkswagen bug, invokes the image of volkswagen the company and alows you to buy third party parts, but nothing of the orignal is inate to the the copy, quality, stability, history, etc. As to BSD being a 'hack', I think you do it disservice. Berkeley has produced a lot of top notch software. How much of what we call the internet is just Berkely derived software: tcp/ip, sockets, sendmail, etc. Adrian -- adrian@virginia.edu ---->>>>| If I were stranded on a desert island, and System Administrator --->>>| I could only have one OS for my computer, Neurosurgical Visualzation Lab -->>| it would be FreeBSD. Think about it..... http://www.nvl.virginia.edu/ ->| http://www.freebsd.org/ From owner-freebsd-hackers Tue Sep 30 09:03:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA03681 for hackers-outgoing; Tue, 30 Sep 1997 09:03:49 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA03657; Tue, 30 Sep 1997 09:03:38 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id BAA01118; Wed, 1 Oct 1997 01:31:05 +0930 (CST) Message-Id: <199709301601.BAA01118@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Brian Tao cc: FREEBSD-HACKERS , FREEBSD-ISP Subject: Re: Cyclades Cyclom-Y PCI multiport serial as console server? In-reply-to: Your message of "Tue, 30 Sep 1997 10:58:35 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 01 Oct 1997 01:31:02 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Before I start more troubleshooting, has anyone used the Cyclom-Y > 16-port PCI serial controllers as null modem ports? Should be nothing special about this. > I note that the cy(4) man page from a May 1997 3.0 snapshot states: > > > BUGS > > BREAK is not yet implemented. > > > > Serial consoles are not implemented. > > > Is there a newer version that does allow me to send breaks to the > remote side (very important if you're dealing with Sparcs)? Can't help here, sorry. The 'cy' driver is a fairly nasty cross of the 'sio' driver (for understandable reasons), but the BREAK code is specifically commented out. It's possible that BREAK is not well handled by the cd1400 UARTs. > What > exactly does "serial consoles" mean in this context? If it works with > a modem, I don't see why I can't slap a null modem changer on the > cable, and use it as a serial console. It almost certainly means that you can't have the BSD box use one of the cy ports as a console. There's nothing magic about using a port as a console on a remote system. > I've already modifed /etc/rc.serial to set the ttyc* and cuac* > devices to "terminal" rather than the default of "modem". Anything > else I need to do? Do you really want the hardware flowcontrol? You will want to do the traditional 2/3, 4/5, 6+8/20 crosses in your cables. From owner-freebsd-hackers Tue Sep 30 10:16:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA08100 for hackers-outgoing; Tue, 30 Sep 1997 10:16:23 -0700 (PDT) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA08092 for ; Tue, 30 Sep 1997 10:16:19 -0700 (PDT) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.5/8.8.5) id TAA03502 for hackers@FreeBSD.ORG; Tue, 30 Sep 1997 19:22:10 +0200 (CEST) From: Mikael Karpberg Message-Id: <199709301722.TAA03502@ocean.campus.luth.se> Subject: TIP: cvs commit readers To: hackers@FreeBSD.ORG Date: Tue, 30 Sep 1997 19:22:10 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi! For all you guys out there that read the cvs commit lists, I have a little practical javascript code. Some of you have probably (like me) read the messages, and when wanting to see the diff for a file, used something like the page posted quite some time ago: http://www-intern.bik-gmbh.de/test/cvsmsg.html This works by a CGI script bouncing you to the right page, which is slow. Specially if that server is down or unreachable. :-) So I set out (with the help of a javascipt programmer I know) to correct this problem. The final result is a little javascript function which can be used very easilly with a HTML form to do the same thing, but without CGI programming, and it's therefor a lot easier to add to your own homepage, or so. Having it locally, and not using a CGI scipt makes the thing so much faster. So... For those who are interested, here is the javascript code, embeded into a small page with just a form on it. Feel free to copy and use. Maybe ever add to some page like http://www.freebsd.org/support.html, or let the cgi-script for the cvs pages add it to the CVS root page, or something. -------8<--------
Enter change-lines below:
-------8<-------- Enjoy! Please comment on the script if you feel like it. /Mikael From owner-freebsd-hackers Tue Sep 30 11:37:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA12367 for hackers-outgoing; Tue, 30 Sep 1997 11:37:42 -0700 (PDT) Received: from bmccane.uit.net (bmccane.uit.net [209.83.205.48]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA12362; Tue, 30 Sep 1997 11:37:38 -0700 (PDT) Received: from bmccane.uit.net (localhost.mccane.com [127.0.0.1]) by bmccane.uit.net (8.8.7/8.8.5) with ESMTP id NAA07381; Tue, 30 Sep 1997 13:37:23 -0500 (CDT) Message-Id: <199709301837.NAA07381@bmccane.uit.net> X-Mailer: exmh version 2.0gamma 1/27/96 To: current@freebsd.org cc: hackers@freebsd.org Subject: PPP problems Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 30 Sep 1997 13:37:21 -0500 From: Wm Brian McCane Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings, Sorry for the crosspost, but I thought I might not get hold of the right person without it. I did a make world, and kernel rebuild on Sep 20 using current, and everything worked just spiffy. On Sep 26, I replaced my old slow internal modem with a new fast PNP modem. This motherboard does not have PNP in the BIOS so I rebuilt the kernel with pnp installed. After rebooting, everything seemed to work ok, but my ps and other `kvm' related programs didn't work. So, not wanting to look foolish, I did the right thing, I did a `make world', and another kernel build and rebooted. Once again everything worked, until I went to eat dinner.... Okay, here's what I am seeing: I use kernel PPP for a full time connection to the InterNet My connection gets dropped every 5 hours by my ISP (shouldn't unlimited mean UNLIMITED!) Occasionally pppd does not recognize that the connection has dropped, and hangs there. If I kill -9 pppd, it becomes a Zombie (state in `ps' is SEs) I tried to change to iij-ppp, and it will not reconnect after it is disconnected (It doesn't recognize the disconnect). If I kill iij-ppp and restart it by hand, it is screwed up and still will not talk. If I run iij-ppp first, then kill it when the connection dies, I can connect with pppd (once). The only way to reconnect after that is to reboot. I tried my old modem, it has the same behaviour so it is not an incompatibility issue as I see it. When the PPP is screwed up, there is a noticable slow down of the system. But systat shows 90-95% idle. Logging in from another PC feels like I am doing telnet over a 9600 baud dialin line (I've done this, it sucks). My console is dead. It goes through the "Local package initialization", and then no more output goes to the screen. If I login blind, it succeeds, I verified this from a rlogin. help!!! brian BTW> I have already written a script to check out all the code as it was on 09/20/97, and will probably do this unless someone has some helpful suggestions. From owner-freebsd-hackers Tue Sep 30 11:41:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA12674 for hackers-outgoing; Tue, 30 Sep 1997 11:41:44 -0700 (PDT) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA12662; Tue, 30 Sep 1997 11:41:40 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id LAA06242; Tue, 30 Sep 1997 11:41:18 -0700 (PDT) Message-ID: <19970930114118.44619@hydrogen.nike.efn.org> Date: Tue, 30 Sep 1997 11:41:18 -0700 From: John-Mark Gurney To: Brian Tao Cc: FREEBSD-HACKERS , FREEBSD-ISP Subject: Re: Cyclades Cyclom-Y PCI multiport serial as console server? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Brian Tao on Tue, Sep 30, 1997 at 10:58:35AM -0400 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Brian Tao scribbled this message on Sep 30: > Before I start more troubleshooting, has anyone used the Cyclom-Y > 16-port PCI serial controllers as null modem ports? We have several > dozen pieces of equipment here that all have serial console ports > (Sparcs, Ciscos, Netapps, etc.) Rather than running around with a > long cable attached to a VT-420, I wanted to build a FreeBSD box with > 64 serial ports and just use cu to get console access. > > I note that the cy(4) man page from a May 1997 3.0 snapshot states: > > > BUGS > > BREAK is not yet implemented. you might be able to fake this... just set the line speed to a really slow rate and send some nulls... that's how many programs send a break... > > Serial consoles are not implemented. this just means that you can't use a cy as a serial console for the machine.. not that you can't hook it up to a remove serial console.. > Is there a newer version that does allow me to send breaks to the > remote side (very important if you're dealing with Sparcs)? What > exactly does "serial consoles" mean in this context? If it works with > a modem, I don't see why I can't slap a null modem changer on the > cable, and use it as a serial console. > > I've already modifed /etc/rc.serial to set the ttyc* and cuac* > devices to "terminal" rather than the default of "modem". Anything > else I need to do? not that I know of.. you might want to look at conserver that Poul asked for someone to port... not sure if I have the patches around anymore.. but it wasn't that hard to port.. just needed to convert the termios stuff from SYSV to BSD style... APUE is VERY useful in this situation.. :) -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-hackers Tue Sep 30 12:54:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA17596 for hackers-outgoing; Tue, 30 Sep 1997 12:54:02 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [206.246.122.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA17585 for ; Tue, 30 Sep 1997 12:53:56 -0700 (PDT) Received: from Journey2.mat.net (journey2.mat.net [206.246.122.116]) by earth.mat.net (8.8.7/8.6.12) with SMTP id PAA10868; Tue, 30 Sep 1997 15:52:07 -0400 (EDT) Date: Tue, 30 Sep 1997 15:52:06 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: adrian@virginia.edu cc: Simon Shapiro , "Jamil J. Weatherbee" , freebsd-hackers@FreeBSD.ORG Subject: RE: Good Lord, Commercial Linux In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 30 Sep 1997, Adrian T. Filipi-Martin wrote: > On Tue, 30 Sep 1997, Simon Shapiro wrote: > > > c. BSD came from Berkeley, it is a hack. Linux is systemV like. It has a > > heritage of Large Company. Caldera was founded by Mr. Noorda, he is > > Ahem! Linux has no such "heritage". That's why it too is free. > The linux crowd just whent the SYSV like API. Designing a car that looks > like a volkswagen bug, invokes the image of volkswagen the company and > alows you to buy third party parts, but nothing of the orignal is inate to > the the copy, quality, stability, history, etc. > > As to BSD being a 'hack', I think you do it disservice. Berkeley > has produced a lot of top notch software. How much of what we call the > internet is just Berkely derived software: tcp/ip, sockets, sendmail, etc. I think he was trying to illustrate what many managers (who have little understanding past buzzwords-fluency) might be relied upon to say. > > Adrian > -- > adrian@virginia.edu ---->>>>| If I were stranded on a desert island, and > System Administrator --->>>| I could only have one OS for my computer, > Neurosurgical Visualzation Lab -->>| it would be FreeBSD. Think about it..... > http://www.nvl.virginia.edu/ ->| http://www.freebsd.org/ > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Tue Sep 30 13:17:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA19147 for hackers-outgoing; Tue, 30 Sep 1997 13:17:34 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA19125 for ; Tue, 30 Sep 1997 13:17:24 -0700 (PDT) Received: (qmail 11576 invoked by uid 1000); 30 Sep 1997 20:17:37 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092597 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199709301837.NAA07381@bmccane.uit.net> Date: Tue, 30 Sep 1997 13:17:37 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Wm Brian McCane Subject: RE: PPP problems Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Wm Brian McCane; On 30-Sep-97 you wrote: ... > and another kernel build and rebooted. Once again everything worked, > until I > went to eat dinner.... You see! Had you stayed at the keyboard... :-) > Okay, here's what I am seeing: > > I use kernel PPP for a full time connection to the InterNet > My connection gets dropped every 5 hours by my ISP > (shouldn't unlimited mean UNLIMITED!) Yup! Here too... To this i might add: Sep 29 10:52:30 sendero /kernel.sendero: ppp0: no compressor for [15 3 29], 3 Sep 29 10:52:30 sendero /kernel.sendero: ppp0: no compressor for [18 4 8], 4 Sep 30 01:21:27 sendero /kernel.sendero: ppp0: no compressor for [15 3 29], 3 Sep 30 01:21:27 sendero /kernel.sendero: ppp0: no compressor for [18 4 8], 4 Sep 30 01:24:47 sendero /kernel.sendero: ppp0: no compressor for [15 3 29], 3 Sep 30 01:24:47 sendero /kernel.sendero: ppp0: no compressor for [18 4 8], 4 Sep 30 12:16:56 sendero /kernel.sendero: ppp0: no compressor for [15 3 29], 3 Sep 30 12:16:56 sendero /kernel.sendero: ppp0: no compressor for [18 4 8], 4 and ... Sep 30 12:24:09 sendero /kernel.sendero: ppp0: line error 4000000 Sep 30 12:24:09 sendero last message repeated 2 times Sep 30 12:24:10 sendero /kernel.sendero: sio2: 3 more silo overflows (total 3) Sep 30 12:38:23 sendero /kernel.sendero: ppp0: line error 4000000 Sep 30 12:38:24 sendero /kernel.sendero: sio2: 1 more silo overflow (total 4) Current as of last night. Also ppp in sysinstall needs -ldes again to compile... --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-hackers Tue Sep 30 13:17:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA19167 for hackers-outgoing; Tue, 30 Sep 1997 13:17:36 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA19131 for ; Tue, 30 Sep 1997 13:17:29 -0700 (PDT) Received: (qmail 11584 invoked by uid 1000); 30 Sep 1997 20:17:37 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092597 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 30 Sep 1997 13:17:37 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: adrian@virginia.edu Subject: RE: Good Lord, Commercial Linux Cc: freebsd-hackers@freebsd.org, "Jamil J. Weatherbee" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi "Adrian T. Filipi-Martin"; On 30-Sep-97 you wrote: > On Tue, 30 Sep 1997, Simon Shapiro wrote: > > > c. BSD came from Berkeley, it is a hack. Linux is systemV like. It > > has a > > heritage of Large Company. Caldera was founded by Mr. Noorda, he > > is > > Ahem! Linux has no such "heritage". That's why it too is free. > The linux crowd just whent the SYSV like API. Designing a car that > looks > like a volkswagen bug, invokes the image of volkswagen the company and > alows you to buy third party parts, but nothing of the orignal is inate > to > the the copy, quality, stability, history, etc. > > As to BSD being a 'hack', I think you do it disservice. Berkeley > has produced a lot of top notch software. How much of what we call the > internet is just Berkely derived software: tcp/ip, sockets, sendmail, > etc. You obviously missed part of my message. I put a (what I thought was) a clear disclaimer at the bottom. This is not how I think and feel. This is how things, in corporate circles are precived many times. Were I to think this way, I would not have chosen FreeBSD as a platform for a critical and HUGE project. Besides, were it not for the BSD project, SystemV will still be swapping, rather than paging, using uucp and ISO instead of TCP/IP, etc. It is healthy, at times, to see how the other side is thinking. BTW, I would not necessarily put sendmail as one of the jewels in Berkeley crowns :-) and you forgot the Ingres-Postgres project. One of the more impressive, and ORIGINAL developments at Berkeley. Also, you ommited vi :-) --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-hackers Tue Sep 30 15:14:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA25571 for hackers-outgoing; Tue, 30 Sep 1997 15:14:07 -0700 (PDT) Received: from bmccane.uit.net (bmccane.uit.net [209.83.205.48]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA25520; Tue, 30 Sep 1997 15:13:33 -0700 (PDT) Received: (from root@localhost) by bmccane.uit.net (8.8.7/8.8.5) id RAA20779; Tue, 30 Sep 1997 17:11:06 -0500 (CDT) Date: Tue, 30 Sep 1997 17:11:06 -0500 (CDT) From: Wm Brian McCane To: Simon Shapiro cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: RE: PPP problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 30 Sep 1997, Simon Shapiro wrote: > > Hi Wm Brian McCane; On 30-Sep-97 you wrote: > > ... > > > and another kernel build and rebooted. Once again everything worked, > > until I > > went to eat dinner.... > > You see! Had you stayed at the keyboard... :-) I tried to use this argument with my wife too. I have the still healing bite marks to prove it 8(. > > Okay, here's what I am seeing: > > > > I use kernel PPP for a full time connection to the InterNet > > My connection gets dropped every 5 hours by my ISP > > (shouldn't unlimited mean UNLIMITED!) > > Yup! Here too... > > To this i might add: I haven't seen these errors, what level of debugging do you have to have turned on for them? > Sep 29 10:52:30 sendero /kernel.sendero: ppp0: no compressor for [15 3 29], > 3 > Sep 29 10:52:30 sendero /kernel.sendero: ppp0: no compressor for [18 4 8], 4 > Sep 30 01:21:27 sendero /kernel.sendero: ppp0: no compressor for [15 3 29], ... > and ... > > Sep 30 12:24:09 sendero /kernel.sendero: ppp0: line error 4000000 > Sep 30 12:24:09 sendero last message repeated 2 times > Sep 30 12:24:10 sendero /kernel.sendero: sio2: 3 more silo overflows (total > 3) > Sep 30 12:38:23 sendero /kernel.sendero: ppp0: line error 4000000 > Sep 30 12:38:24 sendero /kernel.sendero: sio2: 1 more silo overflow (total > 4) ... I have pppd run automatically from cron. It checks to see if the port is already locked, and if not it starts processing. So what I see in messages file is: Sep 29 08:00:01 bmccane pppd[13936]: Device cuaa1 is locked by pid 75 Sep 29 08:00:01 bmccane last message repeated 13 times Sep 29 08:00:01 bmccane pppd[12853]: Device cuaa1 is locked by pid 75 Sep 29 08:00:01 bmccane last message repeated 9 times Sep 29 08:00:01 bmccane pppd[13936]: Device cuaa1 is locked by pid 75 Sep 29 08:00:01 bmccane last message repeated 25 times Sep 29 08:00:03 bmccane pppd[12853]: Device cuaa1 is locked by pid 75 Nice to know that even without a valid `pid' file in /var/run, the port is still locked. This also happens after I try to kill the #*$(&% program. brian From owner-freebsd-hackers Tue Sep 30 15:49:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA28126 for hackers-outgoing; Tue, 30 Sep 1997 15:49:48 -0700 (PDT) Received: from unix.tfs.net (root@unix.tfs.net [199.79.146.60]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA28120 for ; Tue, 30 Sep 1997 15:49:42 -0700 (PDT) Received: from argus.tfs.net (pm3-p2.tfs.net [206.154.183.194]) by unix.tfs.net (8.8.5/8.8.5) with ESMTP id QAA32099; Tue, 30 Sep 1997 16:47:49 -0500 Received: (from jbryant@localhost) by argus.tfs.net (8.8.7/8.8.5) id RAA02920; Tue, 30 Sep 1997 17:49:29 -0500 (CDT) From: Jim Bryant Message-Id: <199709302249.RAA02920@argus.tfs.net> Subject: Re: Good Lord, Commercial Linux In-Reply-To: from Simon Shapiro at "Sep 30, 97 01:17:37 pm" To: Shimon@i-Connect.Net (Simon Shapiro) Date: Tue, 30 Sep 1997 17:49:28 -0500 (CDT) Cc: freebsd-hackers@freebsd.org Reply-to: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-Operating-System: FreeBSD 2.2.2-RELEASE #0: Wed Jul 9 01:01:24 CDT 1997 X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply: > Also, you ommited vi :-) simon, this is where i draw the line... vi is pure unadulterated evil. EMACS is the only true editor :^] Emacs makes the sun shine. Emacs makes the birds sing. Emacs makes the grass grow green. [just stating fact, not trying to start a holy war] jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28PW voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ From owner-freebsd-hackers Tue Sep 30 16:06:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA29084 for hackers-outgoing; Tue, 30 Sep 1997 16:06:31 -0700 (PDT) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA29079 for ; Tue, 30 Sep 1997 16:06:27 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.6/8.6.12) with SMTP id QAA00755; Tue, 30 Sep 1997 16:01:42 -0700 (PDT) Message-Id: <199709302301.QAA00755@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol To: jbryant@tfs.net Cc: Shimon@i-connect.net (Simon Shapiro), freebsd-hackers@freebsd.org Subject: Re: Good Lord, Commercial Linux Reply-To: Jason Thorpe From: Jason Thorpe Date: Tue, 30 Sep 1997 16:01:41 -0700 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 30 Sep 1997 17:49:28 -0500 (CDT) Jim Bryant wrote: > Emacs makes the sun shine. > Emacs makes the birds sing. > Emacs makes the grass grow green. And, thankfully, vi(1) concentrates on editing :-) -- Jason "I use vi to edit files, and emacs to run lisp programs." Thorpe From owner-freebsd-hackers Tue Sep 30 17:53:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA04971 for hackers-outgoing; Tue, 30 Sep 1997 17:53:20 -0700 (PDT) Received: from a42.deep-thought.org (A42.deep-thought.org [203.4.184.227]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA04966 for ; Tue, 30 Sep 1997 17:53:14 -0700 (PDT) Received: from a42.deep-thought.org ([127.0.0.1]) by a42.deep-thought.org with esmtp id m0xGD5O-0024w4C (Debian Smail-3.2 1996-Jul-4 #2); Wed, 1 Oct 1997 10:56:18 +1000 (EST) Message-Id: X-Mailer: exmh version 1.6.9 8/22/96 To: hackers@freebsd.org Subject: FreeBSD TCP stack SUX big juicy ones. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 01 Oct 1997 10:56:17 +1000 From: Richard Jones Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well it seems the original subject for this email: "TCP connection initiation problem?" was not technical enough for the hackers@freebsd.org list and got lost amongst techno-gems such as "Our *NIX is better than their *NIX" and "The number of the beast is vi vi vi". Now as important as these issues are I was hoping I could get some feedback on the following situation: Could someone explain what lies behind the packet exchange shown below. 204.216.27.18 is FreeBSD's smtp port and port 8000 is a non-existent port on aaa.bbb.ccc.ddd (i.e. the initial packet from aaa.bbb.ccc.ddd to freebsd.org is forged). 20:42:56.116714 aaa.bbb.ccc.ddd.8000 > 204.216.27.18.25: S 667:667(0) win 4096 (ttl 200, id 666) 20:42:56.686714 204.216.27.18.25 > aaa.bbb.ccc.ddd.8000: S 856239105:856239105(0) ack 668 win 16384 (DF) (ttl 53, id 16513) 20:42:56.686714 aaa.bbb.ccc.ddd.8000 > 204.216.27.18.25: R 668:668(0) win 0 (ttl 255, id 5507) Now at this point SunOS, Linux and NetBSD all take no for an answer, but FreeBSD just won't quit. It takes FreeBSD another 1min15secs to decide its SYN's are not wanted (i.e the connection establishment timers kicks in). It should be noted that the initial packet can have its source faked and the packet exchange will occur between the FreeBSD host and the unsuspecting other. 20:43:02.266714 204.216.27.18.25 > aaa.bbb.ccc.ddd.8000: S 856239105:856239105(0) ack 668 win 16384 (DF) (ttl 53, id 16672) 20:43:02.266714 aaa.bbb.ccc.ddd.8000 > 204.216.27.18.25: R 668:668(0) win 0 (ttl 255, id 5508) 20:43:26.236714 204.216.27.18.25 > aaa.bbb.ccc.ddd.8000: S 856239105:856239105(0) ack 668 win 16384 (DF) (ttl 53, id 17083) 20:43:26.236714 aaa.bbb.ccc.ddd.8000 > 204.216.27.18.25: R 668:668(0) win 0 (ttl 255, id 5509) Ok, so in the next packet FreeBSD finally decides to give up: 20:44:11.236714 204.216.27.18.25 > aaa.bbb.ccc.ddd.8000: R 1:1(0) ack 1 win 16384 (DF) (ttl 53, id 18235) Note the RST's from aaa.bbb.ccc.ddd are not getting lost on the network, I've verified on another host that these packets get through (the timings really tell that story anyways). Is this broken SYN-Flood protection? Does it allow Evil others to cause a large exchange of data between a FreeBSD host and any other at just the cost of a single packet to Mrs/Mr Evil? Or am I completely missing the point? Does this exchange have a use which is beyond my ken? Richard Jones From owner-freebsd-hackers Tue Sep 30 19:07:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA08976 for hackers-outgoing; Tue, 30 Sep 1997 19:07:27 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA08969 for ; Tue, 30 Sep 1997 19:07:22 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id TAA00275; Tue, 30 Sep 1997 19:07:01 -0700 (PDT) Date: Tue, 30 Sep 1997 19:07:01 -0700 (PDT) From: "Jamil J. Weatherbee" To: Atipa cc: Simon Shapiro , freebsd-hackers@FreeBSD.ORG Subject: RE: Good Lord, Commercial Linux In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk That's not what I was really saying. I would be willing to pay a few hundred dollars for freebsd on the alpha with some of the productivity tools (notably staroffice) that caldera linux has, I wonder also if caldera has hacker the 2.0.29 kernel to make i a bit more stable? What about that UNIX compliance tests like the now defunct LinuxFT product which I think was a really good product, of very high quality from what I saw. > > > > a. If it is free it is useless. You get what you pay for. Why would > > anyone give away anything which is of any value? > > > > b. The fewer releases, the more ``stable'' your product. If you doubt > > this statement, search for some high-level sales aids for NiceTry. > > Or Slowlaris, for that matter. > > > > c. BSD came from Berkeley, it is a hack. Linux is systemV like. It has a > > heritage of Large Company. Caldera was founded by Mr. Noorda, he is > > the radical rebel of Corporate America. Made billions with Novell. > > Calder Linux must therfore be a good thing. > > From owner-freebsd-hackers Tue Sep 30 19:09:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA09098 for hackers-outgoing; Tue, 30 Sep 1997 19:09:00 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA09093 for ; Tue, 30 Sep 1997 19:08:56 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id TAA00279; Tue, 30 Sep 1997 19:08:37 -0700 (PDT) Date: Tue, 30 Sep 1997 19:08:37 -0700 (PDT) From: "Jamil J. Weatherbee" To: adrian@virginia.edu cc: Simon Shapiro , freebsd-hackers@freebsd.org Subject: RE: Good Lord, Commercial Linux In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Yes, I must agree, Cal rocks! > As to BSD being a 'hack', I think you do it disservice. Berkeley > has produced a lot of top notch software. How much of what we call the > internet is just Berkely derived software: tcp/ip, sockets, sendmail, etc. From owner-freebsd-hackers Tue Sep 30 20:49:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA12988 for hackers-outgoing; Tue, 30 Sep 1997 20:49:47 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id UAA12935 for ; Tue, 30 Sep 1997 20:49:39 -0700 (PDT) Received: (qmail 15332 invoked by uid 1000); 1 Oct 1997 03:50:02 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092597 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 30 Sep 1997 20:50:02 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: "Jamil J. Weatherbee" Subject: RE: Good Lord, Commercial Linux Cc: freebsd-hackers@FreeBSD.ORG, Atipa Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi "Jamil J. Weatherbee"; On 01-Oct-97 you wrote: > > That's not what I was really saying. I would be willing to pay a few > hundred dollars for freebsd on the alpha with some of the productivity > tools (notably staroffice) that caldera linux has, I wonder also if > caldera has hacker the 2.0.29 kernel to make i a bit more stable? > What about that UNIX compliance tests like the now defunct LinuxFT > product > which I think was a really good product, of very high quality from what > I > saw. i apologize for mixing sarcasm, humor (Nah, wasn't all that funny), and seriousness. As a packaged, commercial O/S, these packages are good. I still like FreeBSD installation better. The rest is pretty much the same to me. Kernel-wise, I think i trust FreeBSD kernel better than Linux, although performance is, well, six of this, half a dozen of the other; Both are tuned very well. The Alpha bit; I am, professionally, very interested in this. Contact me privately if you want to help. --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-hackers Tue Sep 30 20:49:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA13001 for hackers-outgoing; Tue, 30 Sep 1997 20:49:48 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id UAA12931 for ; Tue, 30 Sep 1997 20:49:38 -0700 (PDT) Received: (qmail 15300 invoked by uid 1000); 1 Oct 1997 03:50:01 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092597 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 30 Sep 1997 20:50:01 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Wm Brian McCane Subject: RE: PPP problems Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Wm Brian McCane; On 30-Sep-97 you wrote: ... > > To this i might add: > I haven't seen these errors, what level of debugging do you have to have > turned on for them? Just ``debug'' in /etc/ppp/options --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-hackers Tue Sep 30 20:49:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA13036 for hackers-outgoing; Tue, 30 Sep 1997 20:49:57 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id UAA13016 for ; Tue, 30 Sep 1997 20:49:53 -0700 (PDT) Received: (qmail 15320 invoked by uid 1000); 1 Oct 1997 03:50:02 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092597 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <199709302249.RAA02920@argus.tfs.net> Date: Tue, 30 Sep 1997 20:50:01 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: jbryant@tfs.net Subject: Re: Good Lord, Commercial Linux Cc: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Jim Bryant; On 30-Sep-97 you wrote: ... > simon, this is where i draw the line... vi is pure unadulterated > evil. EMACS is the only true editor :^] > > Emacs makes the sun shine. > Emacs makes the birds sing. > Emacs makes the grass grow green. > > [just stating fact, not trying to start a holy war] I resisted vi until the late 80's. Used ed, and something tcalled ``the Rand E editor''. Then used vi, then SAM from Plan9 for the longest time. Could not stomach the idea that a text editor consumes 600 times the disk space my first home computer did (Heathkit H8). Trying to adjust to KNF made me, reluctuntly switch to xemacs. Justin gave me some .emacs scripts that (hopefully) make the code presentable. If you know of another (better) whatchamagig to help me, please let me know (Justin claims to be a vi man). --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-hackers Tue Sep 30 21:11:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA14066 for hackers-outgoing; Tue, 30 Sep 1997 21:11:11 -0700 (PDT) Received: from bmccane.uit.net (bmccane.uit.net [209.83.205.48]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA14057 for ; Tue, 30 Sep 1997 21:11:04 -0700 (PDT) Received: from bmccane.uit.net (localhost.mccane.com [127.0.0.1]) by bmccane.uit.net (8.8.7/8.8.5) with ESMTP id XAA00466; Tue, 30 Sep 1997 23:10:54 -0500 (CDT) Message-Id: <199710010410.XAA00466@bmccane.uit.net> X-Mailer: exmh version 2.0gamma 1/27/96 To: jbryant@tfs.net cc: Shimon@i-Connect.Net (Simon Shapiro), freebsd-hackers@FreeBSD.ORG Subject: Re: Good Lord, Commercial Linux In-reply-to: Your message of "Tue, 30 Sep 1997 17:49:28 CDT." <199709302249.RAA02920@argus.tfs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 30 Sep 1997 23:10:19 -0500 From: Wm Brian McCane Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > In reply: > > Also, you ommited vi :-) > > simon, this is where i draw the line... vi is pure unadulterated > evil. EMACS is the only true editor :^] > > Emacs makes the sun shine. > Emacs makes the birds sing. > Emacs makes the grass grow green. Did you ever notice that the grass also grows greener on the septic tank?? brian From owner-freebsd-hackers Tue Sep 30 21:50:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA16134 for hackers-outgoing; Tue, 30 Sep 1997 21:50:59 -0700 (PDT) Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA16117; Tue, 30 Sep 1997 21:50:52 -0700 (PDT) Received: from guppy.cs.columbia.edu (guppy.cs.columbia.edu [128.59.16.155]) by cs.columbia.edu (8.8.5/8.6.6) with ESMTP id AAA07941; Wed, 1 Oct 1997 00:50:44 -0400 (EDT) Received: from guppy.cs.columbia.edu (sauce@localhost) by guppy.cs.columbia.edu (8.8.5/8.6.6) with ESMTP id AAA12529; Wed, 1 Oct 1997 00:50:44 -0400 (EDT) Message-Id: <199710010450.AAA12529@guppy.cs.columbia.edu> X-Mailer: exmh version 1.6.7 5/3/96 To: fs@freebsd.org cc: hackers@freebsd.org Subject: kernel modules Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 01 Oct 1997 00:50:44 -0400 From: Alex Shender Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I was wondering if any of you have written any filesytems as kernel modules. If so can you send me a pointer to the code. I am currently developing a filesystem for linux and Solaris and would like to port it to FreeBSD and would really appreciate it, if I could do it as a module. Thanks, Alex Shender From owner-freebsd-hackers Tue Sep 30 23:04:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA19805 for hackers-outgoing; Tue, 30 Sep 1997 23:04:56 -0700 (PDT) Received: from bob.scl.ameslab.gov (bob.scl.ameslab.gov [147.155.137.254]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA19799 for ; Tue, 30 Sep 1997 23:04:51 -0700 (PDT) Received: from bob.scl.ameslab.gov (localhost [127.0.0.1]) by bob.scl.ameslab.gov (8.8.7/8.8.5) with ESMTP id BAA02252 for ; Wed, 1 Oct 1997 01:04:51 -0500 (CDT) Message-Id: <199710010604.BAA02252@bob.scl.ameslab.gov> To: freebsd-hackers@freebsd.org Subject: CVS and branches.. Date: Wed, 01 Oct 1997 01:04:51 -0500 From: Chris Csanady Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a very basic understanding of CVS, but I'm not exactly sure how branches fit into the whole thing. Basically, I want to create a branch of my own that I can work, while remaining current as well. How do I go about this? I was thinking that I would need a cvsup'd copy of the current repository, as well as a local one, and then keep them in sync. Then I would create a branch in my local repository, and periodically merge the current one in with it. In the end, I would like to produce diffs against current that would be suitable for inclusion. If this is fairly close to reality, could someone briefly explain how you actually accomplish this? (Perhaps even usesable cvs command syntax) Thanks, Chris Csanady From owner-freebsd-hackers Tue Sep 30 23:35:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA22066 for hackers-outgoing; Tue, 30 Sep 1997 23:35:09 -0700 (PDT) Received: from oskar.nanoteq.co.za (oskar.nanoteq.co.za [163.195.220.170]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA22048 for ; Tue, 30 Sep 1997 23:35:03 -0700 (PDT) Received: (from rbezuide@localhost) by oskar.nanoteq.co.za (8.8.7/8.8.5) id IAA00705; Wed, 1 Oct 1997 08:33:36 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <199710010633.IAA00705@oskar.nanoteq.co.za> Subject: Re: FreeBSD TCP stack SUX big juicy ones. In-Reply-To: from Richard Jones at "Oct 1, 97 10:56:17 am" To: richard@a42.deep-thought.org (Richard Jones) Date: Wed, 1 Oct 1997 08:33:36 +0200 (SAT) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Greetings good and humble user ... > was not technical enough for the hackers@freebsd.org list and got lost > amongst techno-gems such as "Our *NIX is better than their *NIX" and > "The number of the beast is vi vi vi". Now as important as these issues are I It would not amaze me if you didn't get any answer with this e-mail ... So .. sorry .. I don't have a technical answer for you, explaining what happens, but maybe it's the attitude of you TCP/IP stack that's the problem :) But like I know the guys at FreeBSD ... they probably won't get offended by this and reply anyway :) Bye Reinier From owner-freebsd-hackers Tue Sep 30 23:57:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA23525 for hackers-outgoing; Tue, 30 Sep 1997 23:57:42 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA23517 for ; Tue, 30 Sep 1997 23:57:18 -0700 (PDT) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id QAA18210; Wed, 1 Oct 1997 16:26:46 +0930 (CST) Message-ID: <19971001162645.28059@lemis.com> Date: Wed, 1 Oct 1997 16:26:45 +0930 From: Greg Lehey To: Chris Csanady Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: CVS and branches.. References: <199710010604.BAA02252@bob.scl.ameslab.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <199710010604.BAA02252@bob.scl.ameslab.gov>; from Chris Csanady on Wed, Oct 01, 1997 at 01:04:51AM -0500 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, Oct 01, 1997 at 01:04:51AM -0500, Chris Csanady wrote: > I have a very basic understanding of CVS, but I'm not exactly sure how > branches fit into the whole thing. Basically, I want to create a branch > of my own that I can work, while remaining current as well. How do I > go about this? > > I was thinking that I would need a cvsup'd copy of the current repository, > as well as a local one, and then keep them in sync. Then I would create a > branch in my local repository, and periodically merge the current one in > with it. In the end, I would like to produce diffs against current that > would be suitable for inclusion. > > If this is fairly close to reality, could someone briefly explain how > you actually accomplish this? (Perhaps even usesable cvs command syntax) I have a document on this subject, part of the upcoming second edition of "The Complete FreeBSD". If you're interested in reviewing this (which means sending me back detailled comments on the text), please contact me and I'll arrange to get it to you. Greg From owner-freebsd-hackers Wed Oct 1 00:26:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA24990 for hackers-outgoing; Wed, 1 Oct 1997 00:26:49 -0700 (PDT) Received: from a42.deep-thought.org (A42.deep-thought.org [203.4.184.227]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA24974 for ; Wed, 1 Oct 1997 00:26:11 -0700 (PDT) Received: from a42.deep-thought.org ([127.0.0.1]) by a42.deep-thought.org with esmtp id m0xGJDX-0024w4C (Debian Smail-3.2 1996-Jul-4 #2); Wed, 1 Oct 1997 17:29:07 +1000 (EST) Message-Id: X-Mailer: exmh version 1.6.9 8/22/96 To: Reinier Bezuidenhout Cc: hackers@freebsd.org Subject: Re: FreeBSD TCP stack SUX big juicy ones. In-reply-to: Your message of "Sat, 01 Oct 1997 08:33:36 +0200." <199710010633.IAA00705@oskar.nanoteq.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 01 Oct 1997 17:29:06 +1000 From: Richard Jones Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Reinier Bezuidenhout writes: > Greetings good and humble user ... > > > was not technical enough for the hackers@freebsd.org list and got lost > > amongst techno-gems such as "Our *NIX is better than their *NIX" and > > "The number of the beast is vi vi vi". Now as important as these issues are I > It would not amaze me if you didn't get any answer with this e-mail ... > well be amazed. Your reply is one more than I received with a serious subject header. Do people here hit for all messages that don't contain the words "linux" or "plug and play" coz my short 72 hours on the list seem to indicate this to be so? > So .. sorry .. I don't have a technical answer for you, > explaining what happens, but maybe it's the attitude of you > TCP/IP stack that's the problem :) > You are probably right, my TCP/IP stack has been more than a little ornery of late. Me and the rest of the kernel have been talking to it regarding the shocking attitude problem exhibited recently. The damn thing just has no respect for authority. Anyways someone should give it a good talking to before it starts leading to faceless DoS attacks. > But like I know the guys at FreeBSD ... they probably won't > get offended by this and reply anyway :) Or maybe the guys at FreeBSD who can answer the question don't even read this list coz of the low SNR. oh well. From owner-freebsd-hackers Wed Oct 1 01:15:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA27666 for hackers-outgoing; Wed, 1 Oct 1997 01:15:17 -0700 (PDT) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA27659 for ; Wed, 1 Oct 1997 01:15:13 -0700 (PDT) Received: from word.smith.net.au (localhost.gsoft.com.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id RAA01232; Wed, 1 Oct 1997 17:41:47 +0930 (CST) Message-Id: <199710010811.RAA01232@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Richard Jones cc: Reinier Bezuidenhout , hackers@FreeBSD.ORG Subject: Re: FreeBSD TCP stack SUX big juicy ones. In-reply-to: Your message of "Wed, 01 Oct 1997 17:29:06 +1000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 01 Oct 1997 17:41:47 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Or maybe the guys at FreeBSD who can answer the question don't even read > this list coz of the low SNR. I'd guess that it's probably sitting in half a dozen inboxes with mental notes saying "this is weird, worry about it just after I get time to breathe". However your _second_ post is likely to have people deleting both it and the first; if your only response to a day or so delay is "complain louder" then people are going to ignore you. If you've got to the point where you can see what's going on, you probably have the skill to trace it further. So go for it! mike From owner-freebsd-hackers Wed Oct 1 01:31:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA28424 for hackers-outgoing; Wed, 1 Oct 1997 01:31:01 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA28416 for ; Wed, 1 Oct 1997 01:30:59 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id BAA08234; Wed, 1 Oct 1997 01:33:34 -0700 (PDT) Message-Id: <199710010833.BAA08234@implode.root.com> To: Richard Jones cc: hackers@FreeBSD.ORG Subject: Re: FreeBSD TCP stack SUX big juicy ones. In-reply-to: Your message of "Wed, 01 Oct 1997 17:29:06 +1000." From: David Greenman Reply-To: dg@root.com Date: Wed, 01 Oct 1997 01:33:34 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Reinier Bezuidenhout writes: >> Greetings good and humble user ... >> >> > was not technical enough for the hackers@freebsd.org list and got lost >> > amongst techno-gems such as "Our *NIX is better than their *NIX" and >> > "The number of the beast is vi vi vi". Now as important as these issues are I >> It would not amaze me if you didn't get any answer with this e-mail ... >> > >well be amazed. Your reply is one more than I received with a serious >subject header. Do people here hit for all messages that don't contain >the words "linux" or "plug and play" coz my short 72 hours on the list seem >to indicate this to be so? You're being very presumptious about too many things. While we try to respond in a timely manner, your original message was posted only 24 hours ago and more importantly, right before a code freeze for our next release. I've personally been busy trying to make sure that important fixes have been merged before the deadline and haven't had time to look into the problem you've reported. Your report lacks many important details, not the least of which is the versions of FreeBSD you've tested this with. "freefall" is running old code from about 4 months ago, and might very well not have some important fixes. We're generally a pretty friendly croud, but your attitude is certainly making this much more difficult than it needs to be. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Wed Oct 1 02:28:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA01738 for hackers-outgoing; Wed, 1 Oct 1997 02:28:01 -0700 (PDT) Received: from unix.tfs.net (root@unix.tfs.net [199.79.146.60]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA01717 for ; Wed, 1 Oct 1997 02:27:57 -0700 (PDT) Received: from argus.tfs.net (pm3-p3.tfs.net [206.154.183.195]) by unix.tfs.net (8.8.5/8.8.5) with ESMTP id DAA31060; Wed, 1 Oct 1997 03:26:08 -0500 Received: (from jbryant@localhost) by argus.tfs.net (8.8.7/8.8.5) id EAA03973; Wed, 1 Oct 1997 04:27:50 -0500 (CDT) From: Jim Bryant Message-Id: <199710010927.EAA03973@argus.tfs.net> Subject: Re: FreeBSD TCP stack SUX big juicy ones. In-Reply-To: from Richard Jones at "Oct 1, 97 05:29:06 pm" To: richard@a42.deep-thought.org (Richard Jones) Date: Wed, 1 Oct 1997 04:27:45 -0500 (CDT) Cc: freebsd-hackers@freebsd.org Reply-to: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-Operating-System: FreeBSD 2.2.2-RELEASE #0: Wed Jul 9 01:01:24 CDT 1997 X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk sorry for the "S/N ratio", occasionally we use humor to break the monotony. a commercial linux is funny. as funny as bsdi. i sent the vi -vs- emacs message to make a point, and that point was: "let's not start another holy war". sarcasm in order to make a valid point is sometimes needed in order to drive a point home. in this mailing list are probably some of the brightest minds in the world, and there will soon be an answer to the previous gentleman's questions concerning tcp/ip oddities. if we are going to be as involved with computers as we are, we must have both a finely developed sense of dark humor, as well as that of sarcasm. words to live by. "You RRRRaaaaaaaannnnnggg?" "Cocktails Lurch! Use the good hemlock!" - Gomez Addams, [my childhood hero] In reply: > Reinier Bezuidenhout writes: > > Greetings good and humble user ... > > > > > was not technical enough for the hackers@freebsd.org list and got lost > > > amongst techno-gems such as "Our *NIX is better than their *NIX" and > > > "The number of the beast is vi vi vi". Now as important as these issues are I > > It would not amaze me if you didn't get any answer with this e-mail ... > > > > well be amazed. Your reply is one more than I received with a serious > subject header. Do people here hit for all messages that don't contain > the words "linux" or "plug and play" coz my short 72 hours on the list seem > to indicate this to be so? > > > So .. sorry .. I don't have a technical answer for you, > > explaining what happens, but maybe it's the attitude of you > > TCP/IP stack that's the problem :) > > > > You are probably right, my TCP/IP stack has been more than a little ornery > of late. Me and the rest of the kernel have been talking to it regarding the > shocking attitude problem exhibited recently. The damn thing just has no > respect for authority. Anyways someone should give it a good talking to > before it starts leading to faceless DoS attacks. > > > But like I know the guys at FreeBSD ... they probably won't > > get offended by this and reply anyway :) > > Or maybe the guys at FreeBSD who can answer the question don't even read > this list coz of the low SNR. > > oh well. jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28PW voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ From owner-freebsd-hackers Wed Oct 1 02:29:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA01818 for hackers-outgoing; Wed, 1 Oct 1997 02:29:32 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA01811 for ; Wed, 1 Oct 1997 02:29:28 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id CAA08397; Wed, 1 Oct 1997 02:32:05 -0700 (PDT) Message-Id: <199710010932.CAA08397@implode.root.com> To: Richard Jones cc: hackers@FreeBSD.ORG Subject: Re: FreeBSD TCP stack SUX big juicy ones. From: David Greenman Reply-To: dg@root.com Date: Wed, 01 Oct 1997 02:32:05 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I said: >problem you've reported. Your report lacks many important details, not >the least of which is the versions of FreeBSD you've tested this with. >"freefall" is running old code from about 4 months ago, and might very well >not have some important fixes. Oh, and it's even worse than that - 204.216.27.18 in your example is hub.freebsd.org, not freefall, and hub is running FreeBSD 2.1.7 which is a code base that is several years old. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Wed Oct 1 02:38:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA02218 for hackers-outgoing; Wed, 1 Oct 1997 02:38:15 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA02208 for ; Wed, 1 Oct 1997 02:38:11 -0700 (PDT) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id TAA21978; Wed, 1 Oct 1997 19:07:58 +0930 (CST) Message-ID: <19971001190757.43209@lemis.com> Date: Wed, 1 Oct 1997 19:07:57 +0930 From: Greg Lehey To: Richard Jones Cc: Reinier Bezuidenhout , hackers@FreeBSD.ORG Subject: Re: FreeBSD TCP stack SUX big juicy ones. References: <199710010633.IAA00705@oskar.nanoteq.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: ; from Richard Jones on Wed, Oct 01, 1997 at 05:29:06PM +1000 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, Oct 01, 1997 at 05:29:06PM +1000, Richard Jones wrote: > > Reinier Bezuidenhout writes: >> Greetings good and humble user ... >> >>> was not technical enough for the hackers@freebsd.org list and got lost >>> amongst techno-gems such as "Our *NIX is better than their *NIX" and >>> "The number of the beast is vi vi vi". Now as important as these issues are I >> It would not amaze me if you didn't get any answer with this e-mail ... >> > > well be amazed. Your reply is one more than I received with a serious > subject header. Do people here hit for all messages that don't contain > the words "linux" or "plug and play" coz my short 72 hours on the list seem > to indicate this to be so? Well, I'm not as pissed off as the others appear to be, but you *will* note that, while you now have more answers, they still don't answer your question. Greg From owner-freebsd-hackers Wed Oct 1 02:46:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA02695 for hackers-outgoing; Wed, 1 Oct 1997 02:46:27 -0700 (PDT) Received: from a42.deep-thought.org (A42.deep-thought.org [203.4.184.227]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA02674 for ; Wed, 1 Oct 1997 02:45:57 -0700 (PDT) Received: from a42.deep-thought.org ([127.0.0.1]) by a42.deep-thought.org with esmtp id m0xGLOU-0024w4C (Debian Smail-3.2 1996-Jul-4 #2); Wed, 1 Oct 1997 19:48:34 +1000 (EST) Message-Id: X-Mailer: exmh version 1.6.9 8/22/96 To: dg@root.com cc: hackers@freebsd.org Subject: Re: FreeBSD TCP stack and RST processing [subj changed] In-reply-to: Your message of "Wed, 01 Oct 1997 01:33:34 MST." <199710010833.BAA08234@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 01 Oct 1997 19:48:34 +1000 From: Richard Jones Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [childish stuff from myself deleted] then David Greenman wrote: > > You're being very presumptious about too many things. While we try to > respond in a timely manner, your original message was posted only 24 hours > ago and more importantly, right before a code freeze for our next release. It was closer to 48 hours than 24 and I assumed the original email had been skipped. I Apologise for my childish response and impatience. > I've personally been busy trying to make sure that important fixes have > been merged before the deadline and haven't had time to look into the > problem you've reported. Once again I aplogise, I was unawre the FreeBSD project was in a close-to-deadline situation. > Your report lacks many important details, not > the least of which is the versions of FreeBSD you've tested this with. > "freefall" is running old code from about 4 months ago, and might very well > not have some important fixes. Ok the other system tested was 2-2 Stable. implode.root.com exhibits the same behaviour as does 204.216.27.21 (the real freefall as pointed out by you in a later mail). The main reason I didn't provide version info was that I thought it was an easy enough situation to replicate if it was indeed replicatable. Unfortunately I know of no systems that are running CURRENT to test upon. > We're generally a pretty friendly croud, but your attitude is certainly > making this much more difficult than it needs to be. Yes, I did not mean to be as obnoxious as I came across [yeah , all the obnoxious bastards say that right] , things were mostly mean tongue in cheek, perhaps more smilies and/or manners would have helped. I doubt this is any more info I can provide. At a guess if a problem exists and this is not just a harmless FreeBSD eccentricity then its in the RST processing (Duh), possibly brought about by recent SYN flood protection code, although if hub is an unpatched code base of several years old this may not be it. TCP extensions? I Dunno, anyways I figured this would be best solved by the people that maintain the code, hence posting here. Richard Jones. From owner-freebsd-hackers Wed Oct 1 03:12:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA04034 for hackers-outgoing; Wed, 1 Oct 1997 03:12:27 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA04029 for ; Wed, 1 Oct 1997 03:12:23 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id DAA08484; Wed, 1 Oct 1997 03:14:55 -0700 (PDT) Message-Id: <199710011014.DAA08484@implode.root.com> To: Richard Jones cc: hackers@freebsd.org Subject: Re: FreeBSD TCP stack and RST processing [subj changed] In-reply-to: Your message of "Wed, 01 Oct 1997 19:48:34 +1000." From: David Greenman Reply-To: dg@root.com Date: Wed, 01 Oct 1997 03:14:55 -0700 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Your report lacks many important details, not >> the least of which is the versions of FreeBSD you've tested this with. >> "freefall" is running old code from about 4 months ago, and might very well >> not have some important fixes. > >Ok the other system tested was 2-2 Stable. implode.root.com exhibits the >same behaviour as does 204.216.27.21 (the real freefall as pointed out by >you in a later mail). implode.root.com is also running 2.1.7. One of these days I'll upgrade it, but it has some special hardware/device drivers that will need to be updated first. > The main reason I didn't provide version info >was that I thought it was an easy enough situation to replicate if it was >indeed replicatable. Unfortunately I know of no systems that are running >CURRENT to test upon. Thanks for the bug report. In the future, it's better to either file a PR via GNATS or send email to freebsd-bugs; you're more likely to get to the right people this way. I forwarded your original message to some people yesterday who might have some input on this. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Wed Oct 1 03:19:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA04455 for hackers-outgoing; Wed, 1 Oct 1997 03:19:44 -0700 (PDT) Received: from thorin.hway.ru (root@thorin.hway.ru [194.87.58.130]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA04432 for ; Wed, 1 Oct 1997 03:19:01 -0700 (PDT) Received: from flash.intech.hway.ru (flash.intech.hway.ru [192.168.1.16]) by thorin.hway.ru (8.8.6/8.8.6) with ESMTP id OAA25674 for ; Wed, 1 Oct 1997 14:16:41 +0400 (MSD) Message-Id: <199710011016.OAA25674@thorin.hway.ru> From: "Alexander V. Tischenko" To: Subject: Re: Recursive fork() and different fbsd's Date: Wed, 1 Oct 1997 14:16:10 +0400 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1161 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_01BCCE74.9100ACC0" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_01BCCE74.9100ACC0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 8bit I tried a bit modified sample and got right into resource limit. Don't know how you can count proc's with your source. Alexander V. Tischenko ---------- > From: Eugeny Kuzakov > To: hackers@FreeBSD.ORG > Subject: Recursive fork() and different fbsd's > Date: 29 сентября 1997 г. 10:39 > > Hi, All ! > > > I run this program on: > > 1. 3.0-970807-SNAP - no hangs, fork always rerurns 0. But process count > does not grow.. > 2. 2.1.7.1-RELEASE - more swap, more processes, not hangs really, but > ....Works only > router...Any applications stoped... > > On linux, when will process count more than same constant, fork returns > -1. > > Any comments ? > > -- > Best wishes, Eugeny Kuzakov > Laboratory 321 ( Omsk, Russia ) > http://www.lab321.ru/~kev > kev@lab321.ru ------=_NextPart_000_01BCCE74.9100ACC0 Content-Type: application/octet-stream; name="ncrash.c" Content-Transfer-Encoding: 7bit Content-Description: ncrash.c (C ) Content-Disposition: attachment; filename="ncrash.c" #include #include #include #include #include #include int main () { pid_t pid; register int count = 0; while (1) { if ((pid = fork()) == (pid_t)-1) { printf("\nCollected: %d boys, return is %d\n", count, errno); fflush(stdout); signal(SIGINT, SIG_IGN); killpg(0, SIGINT); exit(0); } if (pid == 0) { /* Do nothing loop! */ while (1) pause(); } else { printf("."); count++; } } } ------=_NextPart_000_01BCCE74.9100ACC0-- From owner-freebsd-hackers Wed Oct 1 04:09:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA06418 for hackers-outgoing; Wed, 1 Oct 1997 04:09:47 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA06412 for ; Wed, 1 Oct 1997 04:09:40 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id EAA11661; Wed, 1 Oct 1997 04:09:23 -0700 (PDT) To: Mike Smith cc: hackers@FreeBSD.ORG Subject: Re: Interface configuration : call for ideas. In-reply-to: Your message of "Wed, 01 Oct 1997 00:18:58 +0930." <199709301449.AAA00810@word.smith.net.au> Date: Wed, 01 Oct 1997 04:09:22 -0700 Message-ID: <11625.875704162@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > ifconfig_ed0="inet 10.2.3.4" > ifconfig_lan="inet 10.5.6.7" 1. I think that having to know the name and class of any given ethernet driver so that one can properly understand the "fall through" behavior is probably asking a bit much of the administrator. Right now it's not *totally* obvious when the value of, say, "ifconfig_ed0" is going to be used, but at least there's a one-to-one correspondence. If you're going to try and implement your behavior along these lines, I might suggest that something closer in ideology to "wildcarding" be adopted, e.g. "ifconfig_@" would be equivalent to "ifconfig_lan" in your example (I'd like to use * instead of @ there but that'd probably lead to globbing problems :). I think that'd be easier to understand as a general rule than having to know more about the attributes of an interface. 2. If you're going to go the full route of having "arrival events" being paired up with associated actions, why go with the kludge above at all? It seems to me that creating lots of ifconfig_foo and route_static_bar variables which essentially do no more than add conditionals to a fixed scripting sequence (e.g. rc.network) is counterproductive in what you're trying to do here. Why not something closer to a variable naming syntax like: ${eventClass}_${eventName}[_${objName}] Meaning that for arrival event foo of class bar for object fnord, you execute the contents of ${bar_foo_fnord} if found, falling back to ${bar_foo} if that doesn't exist and, finally, doing no action if the 2nd lookup fails. Some practical (though highly contrived) examples: Events "up" and "down" are in class ethercard, these being your new variable entries: ethercard_up="ifconfig \${objName} inet 10.5.6.7" ethercard_up_ed0="ifconfig ed0 inet 10.2.3.4" ethercard_down="ifconfig \${objName} down" Note that you also get to use the implicit wildcarding feature for ethercard_down since you don't need an interface specific line for it. Needless to say, certain variables like ${objName}, ${eventName}, etc would also be set before doing a final expansion of the variable and passing it off to execution, allowing you reasonable access to important parameters. Optional scripts could be looked for and executed using similar logic. Or is that too radical? :-) Jordan From owner-freebsd-hackers Wed Oct 1 04:19:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA06965 for hackers-outgoing; Wed, 1 Oct 1997 04:19:44 -0700 (PDT) Received: from gatekeeper.tsc.tdk.com (root@gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA06938; Wed, 1 Oct 1997 04:19:29 -0700 (PDT) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.4/8.8.4) with ESMTP id EAA27657; Wed, 1 Oct 1997 04:19:05 -0700 (PDT) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id EAA08918; Wed, 1 Oct 1997 04:19:04 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id EAA14305; Wed, 1 Oct 1997 04:19:03 -0700 (PDT) From: Don Lewis Message-Id: <199710011119.EAA14305@salsa.gv.tsc.tdk.com> Date: Wed, 1 Oct 1997 04:19:03 -0700 In-Reply-To: Richard Jones "Re: FreeBSD TCP stack and RST processing [subj changed]" (Oct 1, 7:48pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Richard Jones , dg@root.com Subject: Re: FreeBSD TCP stack and RST processing [subj changed] Cc: hackers@FreeBSD.ORG, bugs@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Oct 1, 7:48pm, Richard Jones wrote: } Subject: Re: FreeBSD TCP stack and RST processing [subj changed] } } Ok the other system tested was 2-2 Stable. implode.root.com exhibits the } same behaviour as does 204.216.27.21 (the real freefall as pointed out by } you in a later mail). The main reason I didn't provide version info } was that I thought it was an easy enough situation to replicate if it was } indeed replicatable. Unfortunately I know of no systems that are running } CURRENT to test upon. I think this bug exists in all versions including -current ... Fortunately, I have my copy of TCP/IP Illustrated Volume 2 here in the office :-) The initial faked SYN will put is in the SYN_RECEIVED state. This is the code from tcp_input() in -current that is supposed handle this situation, and it appears to be the same in 2.1 and 2.2: /* * If the RST bit is set examine the state: * SYN_RECEIVED STATE: * If passive open, return to LISTEN state. * If active open, inform user that connection was refused. * ESTABLISHED, FIN_WAIT_1, FIN_WAIT2, CLOSE_WAIT STATES: * Inform user that connection was reset, and close tcb. * CLOSING, LAST_ACK, TIME_WAIT STATES * Close the tcb. */ if (tiflags&TH_RST) switch (tp->t_state) { case TCPS_SYN_RECEIVED: so->so_error = ECONNREFUSED; goto close; This code appears to be correct, and agrees with what's in the book. However ... there is some code *earlier* in tcp_input() that looks like it botches this situation: /* * If the state is SYN_RECEIVED: * do just the ack and RST checks from SYN_SENT state. * If the state is SYN_SENT: * if seg contains an ACK, but not for our SYN, drop the input. * if seg contains a RST, then drop the connection. * if seg does not contain SYN, then drop it. * Otherwise this is an acceptable SYN segment * initialize tp->rcv_nxt and tp->irs * if seg contains ack then advance tp->snd_una * if SYN has been acked change to ESTABLISHED else SYN_RCVD state * arrange for segment to be acked (eventually) * continue processing rest of data/controls, beginning with URG */ case TCPS_SYN_RECEIVED: case TCPS_SYN_SENT: if ((taop = tcp_gettaocache(inp)) == NULL) { taop = &tao_noncached; bzero(taop, sizeof(*taop)); } if ((tiflags & TH_ACK) && (SEQ_LEQ(ti->ti_ack, tp->iss) || SEQ_GT(ti->ti_ack, tp->snd_max))) { /* * If we have a cached CCsent for the remote host, * hence we haven't just crashed and restarted, * do not send a RST. This may be a retransmission * from the other side after our earlier ACK was lost. * Our new SYN, when it arrives, will serve as the * needed ACK. */ if (taop->tao_ccsent != 0) goto drop; else goto dropwithreset; } if (tiflags & TH_RST) { if (tiflags & TH_ACK) tp = tcp_drop(tp, ECONNREFUSED); goto drop; } if (tp->t_state == TCPS_SYN_RECEIVED) break; It looks like we just drop the packet containing the RST! The example code in the book does not execute this code in the SYN_RECEIVED state. I don't know the history of this code, so I don't know why it was changed. copied to freebsd-bugs --- Truck From owner-freebsd-hackers Wed Oct 1 04:49:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA08212 for hackers-outgoing; Wed, 1 Oct 1997 04:49:17 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA08192; Wed, 1 Oct 1997 04:49:05 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id EAA08698; Wed, 1 Oct 1997 04:51:35 -0700 (PDT) Message-Id: <199710011151.EAA08698@implode.root.com> To: Don Lewis cc: Richard Jones , pst@freebsd.org, hackers@freebsd.org, bugs@freebsd.org Subject: Re: FreeBSD TCP stack and RST processing [subj changed] In-reply-to: Your message of "Wed, 01 Oct 1997 04:19:03 PDT." <199710011119.EAA14305@salsa.gv.tsc.tdk.com> From: David Greenman Reply-To: dg@root.com Date: Wed, 01 Oct 1997 04:51:35 -0700 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >This code appears to be correct, and agrees with what's in the book. > >However ... there is some code *earlier* in tcp_input() that looks like it >botches this situation: ... >It looks like we just drop the packet containing the RST! The example code >in the book does not execute this code in the SYN_RECEIVED state. I don't >know the history of this code, so I don't know why it was changed. > >copied to freebsd-bugs This appears to have been broken in rev 1.52: ---------------------------- revision 1.52 date: 1996/10/07 04:32:39; author: pst; state: Exp; lines: +23 -13 Increase robustness of FreeBSD against high-rate connection attempt denial of service attacks. Reviewed by: bde,wollman,olah Inspired by: vjs@sgi.com ---------------------------- ... *************** *** 753,758 **** --- 758,765 ---- } /* + * If the state is SYN_RECEIVED: + * do just the ack and RST checks from SYN_SENT state. * If the state is SYN_SENT: * if seg contains an ACK, but not for our SYN, drop the input. * if seg contains a RST, then drop the connection. *************** *** 764,769 **** --- 771,777 ---- * arrange for segment to be acked (eventually) * continue processing rest of data/controls, beginning with URG */ + case TCPS_SYN_RECEIVED: case TCPS_SYN_SENT: if ((taop = tcp_gettaocache(inp)) == NULL) { taop = &tao_noncached; *************** *** 791,796 **** --- 799,806 ---- tp = tcp_drop(tp, ECONNREFUSED); goto drop; } + if (tp->t_state == TCPS_SYN_RECEIVED) + break; if ((tiflags & TH_SYN) == 0) goto drop; tp->snd_wnd = ti->ti_win; /* initial send window */ -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Wed Oct 1 04:58:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA08654 for hackers-outgoing; Wed, 1 Oct 1997 04:58:08 -0700 (PDT) Received: from m7.boston.juno.com (m7.boston.juno.com [205.231.100.196]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA08647 for ; Wed, 1 Oct 1997 04:58:03 -0700 (PDT) Received: (from cfdupuis@juno.com) by m7.boston.juno.com (queuemail) id HWH24479; Wed, 01 Oct 1997 07:56:58 EDT To: freebsd-hackers@FreeBSD.org Date: Wed, 1 Oct 1997 06:51:40 -0500 Subject: 1.4 Can I run DOS binaries under FreeBSD? Message-ID: <19971001.065141.3822.0.cfdupuis@juno.com> X-Mailer: Juno 1.38 X-Juno-Line-Breaks: 7-10 From: cfdupuis@juno.com (Charles F. Dupuis) Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Your note states that you are looking for someone to write the DOS support for FreeBSD. I am an assembly language programmer, and I was wondering if you could tell me if there is a book of code on your system? I have several books of free dos kernels that could be modified to work with your system. I will also need to how I could compile and link my assembly code with your code. I also have several books on Windows and could attempt to write an interface for Windows 3.1 programs to run in FreeBSD. C. F. Dupuis cfdupuis@juno.com From owner-freebsd-hackers Wed Oct 1 04:59:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA08765 for hackers-outgoing; Wed, 1 Oct 1997 04:59:58 -0700 (PDT) Received: from gatekeeper.tsc.tdk.com (root@gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA08729; Wed, 1 Oct 1997 04:59:15 -0700 (PDT) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.4/8.8.4) with ESMTP id EAA27860; Wed, 1 Oct 1997 04:58:57 -0700 (PDT) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id EAA09539; Wed, 1 Oct 1997 04:58:56 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id EAA14360; Wed, 1 Oct 1997 04:58:55 -0700 (PDT) From: Don Lewis Message-Id: <199710011158.EAA14360@salsa.gv.tsc.tdk.com> Date: Wed, 1 Oct 1997 04:58:55 -0700 In-Reply-To: David Greenman "Re: FreeBSD TCP stack and RST processing [subj changed]" (Oct 1, 4:51am) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: dg@root.com, Don Lewis Subject: Re: FreeBSD TCP stack and RST processing [subj changed] Cc: Richard Jones , pst@freebsd.org, hackers@freebsd.org, bugs@freebsd.org Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Oct 1, 4:51am, David Greenman wrote: } Subject: Re: FreeBSD TCP stack and RST processing [subj changed] } ---------------------------- } revision 1.52 } date: 1996/10/07 04:32:39; author: pst; state: Exp; lines: +23 -13 } Increase robustness of FreeBSD against high-rate connection attempt } denial of service attacks. It sure looks to me like it does the opposite :-( I'd either back this patch out entirely, or only do the ack check. A third possibility would be to always call tcp_drop() if TH_RST is set in the TCPS_SYN_RECEIVED state, no matter if TH_ACK is set or not. I looked at {Open,Net}BSD and neither of them picked up this change. --- Truck From owner-freebsd-hackers Wed Oct 1 07:30:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA16531 for hackers-outgoing; Wed, 1 Oct 1997 07:30:22 -0700 (PDT) Received: from isgate.is (isgate.is [193.4.58.51]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA16521 for ; Wed, 1 Oct 1997 07:30:03 -0700 (PDT) Received: from eh.est.is (eh.est.is [194.144.208.34]) by isgate.is (8.7.5-M/) with ESMTP id OAA23939; Wed, 1 Oct 1997 14:29:18 GMT Received: from didda.est.is (totii@ppp-24.est.is [194.144.208.124]) by eh.est.is (8.8.5/8.8.5) with SMTP id OAA21662; Wed, 1 Oct 1997 14:28:11 GMT Message-ID: <34325E24.41C67EA6@est.is> Date: Wed, 01 Oct 1997 14:28:52 +0000 From: =?iso-8859-1?Q?=DEor=F0ur?= Ivarsson X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2.2-RELEASE i386) MIME-Version: 1.0 To: "Daniel O'Callaghan" CC: FreeBSD-hackers@FreeBSD.ORG Subject: Re: Is something broken in PPPD? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Daniel O'Callaghan wrote: > > On Mon, 29 Sep 1997, =?iso-8859-1?Q?=DEor=F0ur?= Ivarsson wrote: > > > I am administrator for ISP service in Iceland and have some problem. > > > > four lines are connected to our FreeBSD server and are using > > PPPD started through ttys(5). > > When looking at last(1) output I see lot of connections that are "still > > logged in" > > even thoug they are dead. > > What version of FreeBSD are you using? Grab my pppkit from > ftp://ftp.hilink.com.au/pub/FreeBSD/pppkit.tgz for a version of pppd > which I made sure would work. > > Danny I am running 2.2.2-RELEASE Thordur Ivarsson thivars@est.is From owner-freebsd-hackers Wed Oct 1 07:59:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA18184 for hackers-outgoing; Wed, 1 Oct 1997 07:59:41 -0700 (PDT) Received: from mail.virginia.edu (mail.Virginia.EDU [128.143.2.9]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id HAA18154; Wed, 1 Oct 1997 07:59:27 -0700 (PDT) Received: from ares.cs.virginia.edu by mail.virginia.edu id aa08300; 1 Oct 97 10:58 EDT Received: from stretch.cs.virginia.edu (atf3r@stretch-fo.cs.Virginia.EDU [128.143.136.14]) by ares.cs.Virginia.EDU (8.8.5/8.8.5) with ESMTP id KAA00741; Wed, 1 Oct 1997 10:58:41 -0400 (EDT) Received: (from atf3r@localhost) by stretch.cs.virginia.edu (8.8.5/8.8.5) id KAA11458; Wed, 1 Oct 1997 10:58:39 -0400 (EDT) Date: Wed, 1 Oct 1997 10:58:39 -0400 (EDT) From: "Adrian T. Filipi-Martin" Reply-To: adrian@virginia.edu To: jbryant@tfs.net cc: Simon Shapiro , freebsd-hackers@freebsd.org, freebsd-chat@freebsd.org Subject: Re: Good Lord, Commercial Linux [redirected to chat] In-Reply-To: <199709302249.RAA02920@argus.tfs.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 30 Sep 1997, Jim Bryant wrote: > In reply: > > Also, you ommited vi :-) > > simon, this is where i draw the line... vi is pure unadulterated > evil. EMACS is the only true editor :^] > > Emacs makes the sun shine. > Emacs makes the birds sing. > Emacs makes the grass grow green. > > [just stating fact, not trying to start a holy war] Of course not. (grin) Being an old hand at and daily user of both, I feel comfortable to argue you _need_ to know both. Both set of key binding are integrated into oh so many applications. X (both athena and now CDE/motif toolkits) use emacs style bindings, and su much else uses vi. My editing motto: If you need to shoot form the hip, reach for vi. Especially for those small critters that live in hard to reach places. If you need to plan an extended textual campaign of hack and burn, emacs is the optimal weapon of destruction. Adrian -- adrian@virginia.edu ---->>>>| If I were stranded on a desert island, and System Administrator --->>>| I could only have one OS for my computer, Neurosurgical Visualzation Lab -->>| it would be FreeBSD. Think about it..... http://www.nvl.virginia.edu/ ->| http://www.freebsd.org/ From owner-freebsd-hackers Wed Oct 1 08:14:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA18925 for hackers-outgoing; Wed, 1 Oct 1997 08:14:43 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA18916 for ; Wed, 1 Oct 1997 08:14:36 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id AAA00666; Thu, 2 Oct 1997 00:41:51 +0930 (CST) Message-Id: <199710011511.AAA00666@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jordan K. Hubbard" cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: Interface configuration : call for ideas. In-reply-to: Your message of "Wed, 01 Oct 1997 04:09:22 MST." <11625.875704162@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Oct 1997 00:41:48 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Ah, some input! I thought you were busy? If this is the quality of feedback I get from busy people, we must be alone here... 8( > > ifconfig_ed0="inet 10.2.3.4" > > ifconfig_lan="inet 10.5.6.7" > > 1. I think that having to know the name and class of any given ethernet > driver so that one can properly understand the "fall through" behavior > is probably asking a bit much of the administrator. Right now it's > not *totally* obvious when the value of, say, "ifconfig_ed0" is going > to be used, but at least there's a one-to-one correspondence. Fair enough. The ultimate goal was actually to have the majority of systems with a single 'ifconfig_lan' directive and nothing anywhere naming a specific driver. The only ones that would require this would be those with more than one interface, a relatively rare thing. > If you're going to try and implement your behavior along these lines, > I might suggest that something closer in ideology to "wildcarding" > be adopted, e.g. "ifconfig_@" would be equivalent to "ifconfig_lan" > in your example (I'd like to use * instead of @ there but that'd > probably lead to globbing problems :). I think that'd be easier > to understand as a general rule than having to know more about the > attributes of an interface. This isn't actually very helpful; it just means @ = "lan", and that's only going to confuse people. I was originally going to say "ether" rather than "lan", but decided that there were "lan" interfaces that weren't "ether". Still, it's a hack rather than a good solution, I agree. > 2. If you're going to go the full route of having "arrival events" > being paired up with associated actions, why go with the kludge > above at all? Because the actual set of event-response sequences are very small, with just a few opt-in/opt out items? > It seems to me that creating lots of ifconfig_foo > and route_static_bar variables which essentially do no more > than add conditionals to a fixed scripting sequence > (e.g. rc.network) is counterproductive in what you're trying to do > here. It's certainly an insult to generality, agreed. > Why not something closer to a variable naming syntax like: > > ${eventClass}_${eventName}[_${objName}] > > Meaning that for arrival event foo of class bar for object fnord, you > execute the contents of ${bar_foo_fnord} if found, falling back > to ${bar_foo} if that doesn't exist and, finally, doing no action if > the 2nd lookup fails. Not unreasonable. > Some practical (though highly contrived) examples: > > Events "up" and "down" are in class ethercard, these being your > new variable entries: > > ethercard_up="ifconfig \${objName} inet 10.5.6.7" > ethercard_up_ed0="ifconfig ed0 inet 10.2.3.4" > ethercard_down="ifconfig \${objName} down" Fair enough. This sort of shell syntax would get pretty cramped pretty fast unfortunately, but the idea works. > Note that you also get to use the implicit wildcarding feature > for ethercard_down since you don't need an interface specific > line for it. Needless to say, certain variables like ${objName}, > ${eventName}, etc would also be set before doing a final > expansion of the variable and passing it off to execution, > allowing you reasonable access to important parameters. > > Optional scripts could be looked for and executed using > similar logic. > > Or is that too radical? :-) OK here. I'm not sure how others will buy it. Perhaps a POC implementation is called for? How do people feel about a potentially new directory in /etc for files associated with this sort of thing? Is there any way in sh of determining the existence of a function? mike From owner-freebsd-hackers Wed Oct 1 08:22:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA19456 for hackers-outgoing; Wed, 1 Oct 1997 08:22:24 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id IAA19440 for ; Wed, 1 Oct 1997 08:22:08 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id RAA17893; Wed, 1 Oct 1997 17:21:48 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id RAA12855; Wed, 1 Oct 1997 17:16:11 +0200 (MET DST) Message-ID: <19971001171611.EQ10851@uriah.heep.sax.de> Date: Wed, 1 Oct 1997 17:16:11 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Cc: cfdupuis@juno.com (Charles F. Dupuis) Subject: Re: 1.4 Can I run DOS binaries under FreeBSD? References: <19971001.065141.3822.0.cfdupuis@juno.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19971001.065141.3822.0.cfdupuis@juno.com>; from Charles F. Dupuis on Oct 1, 1997 06:51:40 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Charles F. Dupuis wrote: > Your note states that you are looking for someone to write the DOS > support for FreeBSD. I am an assembly language programmer, and I was > wondering if you could tell me if there is a book of code on your system? Well, ``the times, they are a-changing'', as Bob Dylan once sang. The DOS emulator is already reality now. I think if you subscribe to the emulation@freebsd.org mailing list, you'll find more people to work with in this field. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Wed Oct 1 09:07:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA22111 for hackers-outgoing; Wed, 1 Oct 1997 09:07:41 -0700 (PDT) Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [206.14.52.27]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA22105 for ; Wed, 1 Oct 1997 09:07:37 -0700 (PDT) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id JAA21714; Wed, 1 Oct 1997 09:08:39 -0700 (PDT) Date: Wed, 1 Oct 1997 09:08:39 -0700 (PDT) From: Jim Shankland Message-Id: <199710011608.JAA21714@biggusdiskus.flyingfox.com> To: richard@a42.deep-thought.org Subject: Re: FreeBSD TCP stack and RST processing [subj changed] Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I took a look at the code in 2.2.2-RELEASE, and it sure looks as though it should not exhibit the behavior you described: if a RST packet arrives on a connection in the SYN_RECEIVED state, the tcb is closed -- there should be no retries. So either this problem is not present in 2.2.2-RELEASE; or your problem lies elsewhre (packet filters?); or my read of the code is wrong (very possible). I realize this isn't much, but perhaps it's better than nothing. Jim Shankland Flying Fox Computer Systems, Inc. From owner-freebsd-hackers Wed Oct 1 11:45:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA00297 for hackers-outgoing; Wed, 1 Oct 1997 11:45:43 -0700 (PDT) Received: from pluto.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA00287 for ; Wed, 1 Oct 1997 11:45:37 -0700 (PDT) Received: from shane.plutotech.com (shane.plutotech.com [206.168.67.149]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id MAA19255 for ; Wed, 1 Oct 1997 12:45:28 -0600 (MDT) Message-Id: <199710011845.MAA19255@pluto.plutotech.com> From: "Mike Durian" To: hackers@freebsd.org Subject: strange interaction with Pentium and fxp Date: Wed, 01 Oct 1997 12:45:27 -0600 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've been chatting with David Greenman about this problem I'm seeing, but since we've determined it's not really a fxp driver bug, I'd like to get some input from a wider audience. When I boot single user and ifconfig fxp0 I get a PCI bus failure with a new -current kernel, but don't with an old kernel. The nature of the PCI bus failure is that the 430fx chipset never asserts TRDY# for the read mem multiple command issued by the EtherExpress as part of its very first DMA. Eventually the command times out, the PCI cards (including the EtherExpress) get confused by the invalid PCI command and start throwing interrupts that aren't normally checked for in the interrupt handler, thus locking up the system. So I need to figure out why TRDY# isn't getting asserted with the new kernel. I've got traces of both a working instance of this first mem read multiple from an old kernel and one that fails with the new kernel. The only difference I can detect is that the old kernel stores the mbuf at a physical address like 0x2bxx54 and the new one has the mbuf at 0x3f54 - a much lower memory address. I should also mention that this problem does not occur on a Pentium Pro system. I have not stuck my PCI bus analyzer on the P6 machine, so I'm not positive it uses the same addresses, but I'm assuming it would. This could very well be a 430FX chipset bug, but I still need a work around. I have not yet verified that this problem exists on a different Pentium system, so it is possible that it is specific to the motherboard. Does anyone have any ideas? mike From owner-freebsd-hackers Wed Oct 1 12:15:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA01828 for hackers-outgoing; Wed, 1 Oct 1997 12:15:56 -0700 (PDT) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA01814 for ; Wed, 1 Oct 1997 12:15:47 -0700 (PDT) Received: from ponds.dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.5/8.8.4) with ESMTP id PAA27503; Wed, 1 Oct 1997 15:15:28 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.8.5) with ESMTP id NAA22261; Wed, 1 Oct 1997 13:02:44 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id MAA12565; Wed, 1 Oct 1997 12:53:18 -0400 (EDT) Date: Wed, 1 Oct 1997 12:53:18 -0400 (EDT) From: Thomas David Rivers Message-Id: <199710011653.MAA12565@lakes.dignus.com> To: freebsd-hackers@freefall.FreeBSD.org, joerg_wunsch@uriah.heep.sax.de Subject: Re: r-cmds and DNS and /etc/host.conf Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk J"org wrote: > > As Terry Lambert wrote: > > > Of course, you should feel free to suggest to us any soloution which > > does not require us to run named to implement. And not feel free to > > suggest running named. > > It doesn't require named to run. I have reconstructed your setup, and > proven that my named doesn't get any request if the setup is done > correctly. As i've mentioned, the only pitfall was specifying > localhost without adding the local domain, and with 127.1 instead of > 127.0.0.1 in /etc/hosts. Umm... I have 127.0.0.1 in /etc/hosts and continue to experience the problem... - Dave R. - From owner-freebsd-hackers Wed Oct 1 12:16:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA01908 for hackers-outgoing; Wed, 1 Oct 1997 12:16:05 -0700 (PDT) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA01815 for ; Wed, 1 Oct 1997 12:15:49 -0700 (PDT) Received: from ponds.dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.5/8.8.4) with ESMTP id PAA27524; Wed, 1 Oct 1997 15:15:37 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.8.5) with ESMTP id NAA22291; Wed, 1 Oct 1997 13:18:56 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id NAA12633; Wed, 1 Oct 1997 13:09:29 -0400 (EDT) Date: Wed, 1 Oct 1997 13:09:29 -0400 (EDT) From: Thomas David Rivers Message-Id: <199710011709.NAA12633@lakes.dignus.com> To: freebsd-hackers@freefall.FreeBSD.org, joerg_wunsch@uriah.heep.sax.de Subject: Re: r-cmds and DNS and /etc/host.conf Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > As Thomas David Rivers wrote: > > > Anyway - at one time, that was my fix... but now it's not. > > My host file has: > > > > > > 127.0.0.1 localhost.dignus.com. localhost.dignus.com localhost > > 10.0.0.1 ponds ponds.dignus.com ponds.dignus.com. > > 10.0.0.3 lakes lakes.dignus.com lakes.dignus.com. > > Didn't you say there's another domain involved (by resolv.conf, IIRC)? Yes, my /etc/resolv.conf claims the machine is in a different domain (vnet.net). Could that be the problem? [I would assert that /etc/resolv.conf should not be consolted, as /etc/host.conf indicates you should look in /etc/hosts first, which should resolve everything...] > > David, why don't you simply start a caching-only nameserver, redirect > your resolv.conf(s) to it, and look at its debug output? This will > lead you *way quicker* to the solution about what names are being > looked up than any of our guesswork here in the mailinglist. > > A caching-only nameserver is a matter of one minute: > > cd /etc/namedb > sh make-localhost > named -d 2 -b /etc/namedb/named.boot > > FreeBSD ships with a reasonable default named.boot for a caching-only > server (which also has a bunch of comments for what to do to add a > secondary). Ok - we'll do... - Dave Rivers - From owner-freebsd-hackers Wed Oct 1 12:16:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA01961 for hackers-outgoing; Wed, 1 Oct 1997 12:16:35 -0700 (PDT) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA01956 for ; Wed, 1 Oct 1997 12:16:28 -0700 (PDT) Received: from ponds.dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.5/8.8.4) with ESMTP id PAA27548; Wed, 1 Oct 1997 15:15:47 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.8.5) with ESMTP id NAA22275; Wed, 1 Oct 1997 13:13:39 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id NAA12603; Wed, 1 Oct 1997 13:04:12 -0400 (EDT) Date: Wed, 1 Oct 1997 13:04:12 -0400 (EDT) From: Thomas David Rivers Message-Id: <199710011704.NAA12603@lakes.dignus.com> To: joerg_wunsch@uriah.heep.sax.de, tlambert@primenet.com Subject: Re: r-cmds and DNS and /etc/host.conf Cc: freebsd-hackers@freefall.FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Terry Lambert wrote: > > > > Of course, you should feel free to suggest to us any soloution which > > > does not require us to run named to implement. And not feel free to > > > suggest running named. > > > > It doesn't require named to run. I have reconstructed your setup, and > > proven that my named doesn't get any request if the setup is done > > correctly. As i've mentioned, the only pitfall was specifying > > localhost without adding the local domain, and with 127.1 instead of > > 127.0.0.1 in /etc/hosts. > > I didn't see this. Perhaps this was the interval during which primenet > had munged my MX record. I will give it a try. > > Technically 127.1 and 127.0.0.1 are synonymous; one would think the > code should know this... Earlier discussions in the -hackers group (where I made a similar point) came to the conclusion that support 127.1 was purposely removed from the relavent library. It was deamed to be a dropped BSD-ism. - Dave Rivers - From owner-freebsd-hackers Wed Oct 1 13:01:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA04168 for hackers-outgoing; Wed, 1 Oct 1997 13:01:05 -0700 (PDT) Received: from server.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA04158 for ; Wed, 1 Oct 1997 13:00:56 -0700 (PDT) Received: from localhost (perlsta@localhost) by server.local.sunyit.edu (8.8.7/8.8.5) with SMTP id QAA00315 for ; Wed, 1 Oct 1997 16:06:05 -0500 (EST) X-Authentication-Warning: server.local.sunyit.edu: perlsta owned process doing -bs Date: Wed, 1 Oct 1997 16:06:05 -0500 (EST) From: Alfred Perlstein X-Sender: perlsta@server.local.sunyit.edu To: hackers@FreeBSD.org Subject: distributing binaries only? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk i have a machine with very little disk space that i'm using for a gateway/firewall, the problem is that i would like to update the machine to 2.2.2-stable, however i only have like 60megs to work with (base distribution only, no source). i do have another machine where i just made world as well as a new kernel for the machine, is there a way to copy over the binaries from the usual places: /bin /sbin /stand /usr/sbin /usr/bin onto the machine with very little space left? i'd rather not have to mount the source dir and recompile as the machine is a 586/133 and i don't want to wait 2-3 days for it to finish, so if anyone has a suggestion on how to mirror the binaries i'd really appreciate it. i'm temped just to tar things over, but i'm afraid that might not be the way to do it. thank you, .________________________________________________________________________ __ _ |Alfred Perlstein - Programming & SysAdmin --"Have you seen my FreeBSD tatoo?" |perlsta@sunyit.edu --"who was that masked admin?" |http://www.cs.sunyit.edu/~perlsta : ' From owner-freebsd-hackers Wed Oct 1 13:30:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA05855 for hackers-outgoing; Wed, 1 Oct 1997 13:30:58 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA05850 for ; Wed, 1 Oct 1997 13:30:54 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id NAA17783; Wed, 1 Oct 1997 13:30:45 -0700 (PDT) To: Mike Smith cc: hackers@FreeBSD.ORG Subject: Re: Interface configuration : call for ideas. In-reply-to: Your message of "Thu, 02 Oct 1997 00:41:48 +0930." <199710011511.AAA00666@word.smith.net.au> Date: Wed, 01 Oct 1997 13:30:45 -0700 Message-ID: <17758.875737845@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Ah, some input! I thought you were busy? If this is the quality of > feedback I get from busy people, we must be alone here... 8( I am busy, but I hated to see this get the usual silent treatment. :-) > This isn't actually very helpful; it just means @ = "lan", and that's > only going to confuse people. I was originally going to say "ether" Actually, I meant "@ = wildcard" - this would be a general convention and wouldn't just expand to "lan" in all cases, it would expand to fit whatever was necessary to allow the fall-through case to work, be it for an ethernet card or something else (how about specific vs generic route entries, for example?). But I still like option #2 better, so it's also probably not worth debating overmuch. :) > Because the actual set of event-response sequences are very small, with > just a few opt-in/opt out items? Creeping featurism will expand this set of event-response sequences, I'm sure. :-) Also, if you think about it, the system's initial boot is also sort of an "event" of sorts - I'm sure you could generalize this to the point of absurdity, and it might not even be that bad of an idea. > OK here. I'm not sure how others will buy it. Perhaps a POC > implementation is called for? How do people feel about a potentially > new directory in /etc for files associated with this sort of thing? POC? > Is there any way in sh of determining the existence of a function? I thought you'd just expand the target variable and check it for NULL-ness (""). If it expands, you pass it to eval. If it doesn't, you move on. Jordan From owner-freebsd-hackers Wed Oct 1 14:12:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA08504 for hackers-outgoing; Wed, 1 Oct 1997 14:12:17 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA08494 for ; Wed, 1 Oct 1997 14:12:09 -0700 (PDT) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0xGW3R-0007Py-00; Wed, 1 Oct 1997 15:11:33 -0600 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.7/8.8.3) with ESMTP id PAA26166; Wed, 1 Oct 1997 15:12:23 -0600 (MDT) Message-Id: <199710012112.PAA26166@harmony.village.org> To: Alfred Perlstein Subject: Re: distributing binaries only? Cc: hackers@freebsd.org In-reply-to: Your message of "Wed, 01 Oct 1997 16:06:05 CDT." References: Date: Wed, 01 Oct 1997 15:12:23 -0600 From: Warner Losh Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message Alfred Perlstein writes: : i'd rather not have to mount the source dir and recompile as the machine : is a 586/133 and i don't want to wait 2-3 days for it to finish, so if : anyone has a suggestion on how to mirror the binaries i'd really : appreciate it. make buildworld on a fast machine. Then NFS mount the /usr/src and /usr/obj trees and do a make installworld on the 133 box. Also my 486 Dx2-66 did make world in about 12 hours, and I likely could have dropped that down into the 8 hour range with the addition of more disks, better mount point options, etc. I suspect that 2-3 days is a little pessimistic, unless the machine has little memory. Warner From owner-freebsd-hackers Wed Oct 1 14:36:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA10533 for hackers-outgoing; Wed, 1 Oct 1997 14:36:36 -0700 (PDT) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA10502 for ; Wed, 1 Oct 1997 14:36:17 -0700 (PDT) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id WAA19353; Wed, 1 Oct 1997 22:11:06 +0100 (BST) Received: from [194.32.164.2] by seagoon.gid.co.uk; Wed, 1 Oct 1997 22:06:13 +0100 X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 1 Oct 1997 21:59:23 +0100 To: Alfred Perlstein , hackers@FreeBSD.ORG From: Bob Bishop Subject: Re: distributing binaries only? Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, At 10:06 pm +0100 1/10/97, Alfred Perlstein wrote: >i have a machine with very little disk space that i'm using for a >gateway/firewall, the problem is that i would like to update the machine >to 2.2.2-stable, however i only have like 60megs to work with (base >distribution only, no source). I just had to get a router going in a hurry and I only had a 40Mb disk. What I did was to unpack the bin distribution in spare space on another machine, cut out large chunks of it, and tar/gzip what remained into a single piece (bin.aa). You also need bin.mtree and bin.inf: hack the latter up to say Pieces = 1 and junk the cksum lines. Then do an NFS install. Not elegant but it worked. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK From owner-freebsd-hackers Wed Oct 1 15:31:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA13490 for hackers-outgoing; Wed, 1 Oct 1997 15:31:07 -0700 (PDT) Received: from red.juniper.net (red.juniper.net [208.197.169.254]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA13478; Wed, 1 Oct 1997 15:31:03 -0700 (PDT) Received: from base.juniper.net (base.juniper.net [208.197.169.208]) by red.juniper.net (8.8.5/8.8.5) with ESMTP id PAA12785; Wed, 1 Oct 1997 15:30:28 -0700 (PDT) Received: from base.juniper.net (localhost.juniper.net [127.0.0.1]) by base.juniper.net (8.8.7/8.7.3) with ESMTP id PAA03697; Wed, 1 Oct 1997 15:30:15 -0700 (PDT) Message-Id: <199710012230.PAA03697@base.juniper.net> To: dg@root.com cc: Don Lewis , Richard Jones , hackers@freebsd.org, bugs@freebsd.org Subject: Re: FreeBSD TCP stack and RST processing [subj changed] In-reply-to: Your message of "Wed, 01 Oct 1997 04:51:35 PDT." <199710011151.EAA08698@implode.root.com> Date: Wed, 01 Oct 1997 15:30:15 -0700 From: Paul Traina Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It's been so long since I touched this that I won't offer an opinion. The original idea was ripped from Stevens by vjs and then from me, if memory serves me. From: David Greenman Subject: Re: FreeBSD TCP stack and RST processing [subj changed] >This code appears to be correct, and agrees with what's in the book. > >However ... there is some code *earlier* in tcp_input() that looks like it >botches this situation: ... >It looks like we just drop the packet containing the RST! The example code >in the book does not execute this code in the SYN_RECEIVED state. I don't >know the history of this code, so I don't know why it was changed. > >copied to freebsd-bugs This appears to have been broken in rev 1.52: ---------------------------- revision 1.52 date: 1996/10/07 04:32:39; author: pst; state: Exp; lines: +23 -13 Increase robustness of FreeBSD against high-rate connection attempt denial of service attacks. Reviewed by: bde,wollman,olah Inspired by: vjs@sgi.com ---------------------------- ... *************** *** 753,758 **** --- 758,765 ---- } /* + * If the state is SYN_RECEIVED: + * do just the ack and RST checks from SYN_SENT state. * If the state is SYN_SENT: * if seg contains an ACK, but not for our SYN, drop the input. * if seg contains a RST, then drop the connection. *************** *** 764,769 **** --- 771,777 ---- * arrange for segment to be acked (eventually) * continue processing rest of data/controls, beginning with URG */ + case TCPS_SYN_RECEIVED: case TCPS_SYN_SENT: if ((taop = tcp_gettaocache(inp)) == NULL) { taop = &tao_noncached; *************** *** 791,796 **** --- 799,806 ---- tp = tcp_drop(tp, ECONNREFUSED); goto drop; } + if (tp->t_state == TCPS_SYN_RECEIVED) + break; if ((tiflags & TH_SYN) == 0) goto drop; tp->snd_wnd = ti->ti_win; /* initial send window */ -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Wed Oct 1 15:39:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA14048 for hackers-outgoing; Wed, 1 Oct 1997 15:39:58 -0700 (PDT) Received: from gatekeeper.tsc.tdk.com (root@gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA14042 for ; Wed, 1 Oct 1997 15:39:55 -0700 (PDT) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.4/8.8.4) with ESMTP id PAA05607; Wed, 1 Oct 1997 15:39:26 -0700 (PDT) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id PAA20624; Wed, 1 Oct 1997 15:39:26 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id PAA16119; Wed, 1 Oct 1997 15:39:24 -0700 (PDT) From: Don Lewis Message-Id: <199710012239.PAA16119@salsa.gv.tsc.tdk.com> Date: Wed, 1 Oct 1997 15:39:24 -0700 In-Reply-To: Jim Shankland "Re: FreeBSD TCP stack and RST processing [subj changed]" (Oct 1, 9:08am) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Jim Shankland , richard@a42.deep-thought.org Subject: Re: FreeBSD TCP stack and RST processing [subj changed] Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Oct 1, 9:08am, Jim Shankland wrote: } Subject: Re: FreeBSD TCP stack and RST processing [subj changed] } I took a look at the code in 2.2.2-RELEASE, and it sure looks as though } it should not exhibit the behavior you described: if a RST packet } arrives on a connection in the SYN_RECEIVED state, the tcb is closed -- } there should be no retries. Nope, it looks broken too. case TCPS_SYN_RECEIVED: case TCPS_SYN_SENT: [ deleted ] if (tiflags & TH_RST) { if (tiflags & TH_ACK) tp = tcp_drop(tp, ECONNREFUSED); goto drop; } If a RST arrives without TH_ACK set, the packet is just dropped. --- Truck From owner-freebsd-hackers Wed Oct 1 16:06:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA15212 for hackers-outgoing; Wed, 1 Oct 1997 16:06:21 -0700 (PDT) Received: from pluto.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA15188; Wed, 1 Oct 1997 16:06:07 -0700 (PDT) Received: from shane.plutotech.com (shane.plutotech.com [206.168.67.149]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id RAA25757; Wed, 1 Oct 1997 17:06:06 -0600 (MDT) Message-Id: <199710012306.RAA25757@pluto.plutotech.com> From: "Mike Durian" To: hackers@FreeBSD.ORG cc: dg@root.com, dyson@FreeBSD.ORG Subject: Re: strange interaction with Pentium and fxp In-reply-to: Your message of "Wed, 01 Oct 1997 12:45:27 MDT." Date: Wed, 01 Oct 1997 17:06:05 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 01 Oct 1997 12:45:27 MDT, "Mike Durian" wrote: >The only difference >I can detect is that the old kernel stores the mbuf at >a physical address like 0x2bxx54 and the new one has the >mbuf at 0x3f54 - a much lower memory address. > I should also mention that this problem does not occur >on a Pentium Pro system. I have not stuck my PCI bus >analyzer on the P6 machine, so I'm not positive it uses >the same addresses, but I'm assuming it would. This could >very well be a 430FX chipset bug, but I still need a work >around. I'm got a better grasp on the problem now. I tried running the new kernel on another P6 system and when I experienced the same problem, I knew it wasn't a chipset bug. The only difference between the two P6's was the amount of memory. The one that worked had 64MB and the one that failed on 32MB. When I put 64MB in the one that failed, it started working. Then I put 64MB in the Pentium machine and it too started working. Here's what I know: Machine Mem kernel mbuf Phys Addr. result P6 64MB new NA OK P6 32MB new NA fail P5 32MB new 0x00003f54 fail P5 32MB old 0x002b9f54 OK P5 64MB new 0x0009bf54 OK Apparently, there is a problem with the EtherExpress card DMAing data out of host memory at physical address 0x3f54 using the memory read multiple PCI transaction. Does anyone know why 0x3f54 would be an unacceptable address, and does anyone have a fix? mike From owner-freebsd-hackers Wed Oct 1 16:49:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA17001 for hackers-outgoing; Wed, 1 Oct 1997 16:49:55 -0700 (PDT) Received: from usr04.primenet.com (tlambert@usr04.primenet.com [206.165.6.204]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA16993; Wed, 1 Oct 1997 16:49:48 -0700 (PDT) Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id QAA22980; Wed, 1 Oct 1997 16:49:44 -0700 (MST) From: Terry Lambert Message-Id: <199710012349.QAA22980@usr04.primenet.com> Subject: Re: kernel modules To: sauce@cs.columbia.edu (Alex Shender) Date: Wed, 1 Oct 1997 23:49:44 +0000 (GMT) Cc: fs@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <199710010450.AAA12529@guppy.cs.columbia.edu> from "Alex Shender" at Oct 1, 97 00:50:44 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I was wondering if any of you have written any filesytems as kernel > modules. If so can you send me a pointer to the code. I am currently > developing a filesystem for linux and Solaris and would like to port it to > FreeBSD and would really appreciate it, if I could do it as a module. Look in the source tree. NFS and several other FS's can be loaded as modules. When I wrote the initial module code, I converted procfs as my example. The initialization code in the FS is a bit bogus: if you need to add new VOP_* calls, you will need to recompile the kernel anyway. This is because of the fact that the number of VOP entries is counted from the UFS_VNOPS table instead of the actual number of VOPS_* calls defined in vnode_if.c, and the vnode_if.c (a generated file) is not padded at all to allow growth. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Oct 1 16:55:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA17358 for hackers-outgoing; Wed, 1 Oct 1997 16:55:15 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA17339; Wed, 1 Oct 1997 16:55:11 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id QAA18570; Wed, 1 Oct 1997 16:54:42 -0700 (PDT) To: Paul Traina cc: dg@root.com, Don Lewis , Richard Jones , hackers@FreeBSD.ORG, bugs@FreeBSD.ORG Subject: Re: FreeBSD TCP stack and RST processing [subj changed] In-reply-to: Your message of "Wed, 01 Oct 1997 15:30:15 PDT." <199710012230.PAA03697@base.juniper.net> Date: Wed, 01 Oct 1997 16:54:42 -0700 Message-ID: <18567.875750082@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > It's been so long since I touched this that I won't offer an opinion. > The original idea was ripped from Stevens by vjs and then from me, if > memory serves me. Well, since it certainly seems to cause deviation from expected behavior and none of the other *BSDs have picked it up, shall we simply rip it out? Jordan From owner-freebsd-hackers Wed Oct 1 17:36:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA19433 for hackers-outgoing; Wed, 1 Oct 1997 17:36:56 -0700 (PDT) Received: from usr04.primenet.com (tlambert@usr04.primenet.com [206.165.6.204]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA19428 for ; Wed, 1 Oct 1997 17:36:54 -0700 (PDT) Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id RAA28729; Wed, 1 Oct 1997 17:36:45 -0700 (MST) From: Terry Lambert Message-Id: <199710020036.RAA28729@usr04.primenet.com> Subject: Re: Good Lord, Commercial Linux To: Shimon@i-Connect.Net (Simon Shapiro) Date: Thu, 2 Oct 1997 00:36:45 +0000 (GMT) Cc: jamil@counterintelligence.ml.org, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Simon Shapiro" at Sep 30, 97 00:32:57 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > c. BSD came from Berkeley, it is a hack. Linux is systemV like. It has a > heritage of Large Company. Caldera was founded by Mr. Noorda, he is > the radical rebel of Corporate America. Made billions with Novell. > Calder Linux must therfore be a good thing. > > Now, BEFORE you jump down my throat, please evaluate the technology I > employ in my professional work :-) Caldera was founded by Brian Sparks. Noorda was an early investor, but not the initial investor. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Oct 1 17:55:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA20130 for hackers-outgoing; Wed, 1 Oct 1997 17:55:10 -0700 (PDT) Received: from red.juniper.net (red.juniper.net [208.197.169.254]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA20125; Wed, 1 Oct 1997 17:55:08 -0700 (PDT) Received: from base.juniper.net (base.juniper.net [208.197.169.208]) by red.juniper.net (8.8.5/8.8.5) with ESMTP id RAA15433; Wed, 1 Oct 1997 17:54:37 -0700 (PDT) Received: from base.juniper.net (localhost.juniper.net [127.0.0.1]) by base.juniper.net (8.8.7/8.7.3) with ESMTP id RAA04241; Wed, 1 Oct 1997 17:54:24 -0700 (PDT) Message-Id: <199710020054.RAA04241@base.juniper.net> To: "Jordan K. Hubbard" cc: dg@root.com, Don Lewis , Richard Jones , hackers@FreeBSD.ORG, bugs@FreeBSD.ORG Subject: Re: FreeBSD TCP stack and RST processing [subj changed] In-reply-to: Your message of "Wed, 01 Oct 1997 16:54:42 PDT." <18567.875750082@time.cdrom.com> Date: Wed, 01 Oct 1997 17:54:24 -0700 From: Paul Traina Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I put it in there for a reason, Steven's III showed a case where you could pummel the box with a barage of, I believe, syn ack's and basicly melt things. Sorry my memory is so foggy on the issue now. I'll go back and try to remember. From: "Jordan K. Hubbard" Subject: Re: FreeBSD TCP stack and RST processing [subj changed] > It's been so long since I touched this that I won't offer an opinion. > The original idea was ripped from Stevens by vjs and then from me, if > memory serves me. Well, since it certainly seems to cause deviation from expected behavior and none of the other *BSDs have picked it up, shall we simply rip it out? Jordan From owner-freebsd-hackers Wed Oct 1 18:06:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA20642 for hackers-outgoing; Wed, 1 Oct 1997 18:06:59 -0700 (PDT) Received: from a42.deep-thought.org (A42.deep-thought.org [203.4.184.227]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA20635; Wed, 1 Oct 1997 18:06:45 -0700 (PDT) Received: from a42.deep-thought.org ([127.0.0.1]) by a42.deep-thought.org with esmtp id m0xGZlz-0024w4C (Debian Smail-3.2 1996-Jul-4 #2); Thu, 2 Oct 1997 11:09:47 +1000 (EST) Message-Id: X-Mailer: exmh version 1.6.9 8/22/96 To: Paul Traina cc: "Jordan K. Hubbard" , dg@root.com, Don Lewis , hackers@FreeBSD.ORG, bugs@FreeBSD.ORG Subject: Re: FreeBSD TCP stack and RST processing [subj changed] In-reply-to: Your message of "Wed, 01 Oct 1997 17:54:24 MST." <199710020054.RAA04241@base.juniper.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Oct 1997 11:09:47 +1000 From: Richard Jones Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Paul Traina wrote: > I put it in there for a reason, Steven's III showed a case where you could > pummel the box with a barage of, I believe, syn ack's and basicly melt things. > Sorry my memory is so foggy on the issue now. I'll go back and try to > remember. Hmm..but if you barrage the system with SYN ACK's when the system is in a listen state, you shouldn't jump into SYN_RECEIVED should you? The code which does the if (TH_RST) stuff is prolly ok...its the addition of the case SYN_RECEIVED up the top that does the trick. Its ok to look for an ACK when in SYN_SENT on RST's coz thats what is expected, and if you get other than expected and drop then its no big deal unless you can force a remote freebsd system to send out (pure) SYN's to non-connected ports, unlikely. I only have the snippets posted to the list available, but based on them I'd say remove the case SYN_RECEIVED that was added. You might get away with getting rid of the ACK flag check without losing anything, but any side effects should be thought through. Anyways I'm running late for appointment which is why this may sound a little incoherent, gotta run. Richard Jones. From owner-freebsd-hackers Wed Oct 1 18:10:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA20846 for hackers-outgoing; Wed, 1 Oct 1997 18:10:19 -0700 (PDT) Received: from usr04.primenet.com (tlambert@usr04.primenet.com [206.165.6.204]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA20840 for ; Wed, 1 Oct 1997 18:10:15 -0700 (PDT) Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id SAA01345; Wed, 1 Oct 1997 18:10:03 -0700 (MST) From: Terry Lambert Message-Id: <199710020110.SAA01345@usr04.primenet.com> Subject: Re: FreeBSD TCP stack SUX big juicy ones. To: richard@a42.deep-thought.org (Richard Jones) Date: Thu, 2 Oct 1997 01:10:03 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Richard Jones" at Oct 1, 97 10:56:17 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > "TCP connection initiation problem?" > > was not technical enough for the hackers@freebsd.org list and got lost > amongst techno-gems such as "Our *NIX is better than their *NIX" and > "The number of the beast is vi vi vi". No; actually it's in muy inbox taking up otherwise useful space with the tag "get to this when you have time". Mostly, after 55 lines in an xterm, you had still not come to the point. I resolved to dig it out when I has more time to parse the damn thing. This more recent posting is much more to the point, so I will answer it now, despite the unproductive bashing you've engaged in. > Could someone explain what lies behind the packet exchange shown below. > 204.216.27.18 is FreeBSD's smtp port and port 8000 is a non-existent port > on aaa.bbb.ccc.ddd (i.e. the initial packet from aaa.bbb.ccc.ddd to > freebsd.org is forged). > > 20:42:56.116714 aaa.bbb.ccc.ddd.8000 > 204.216.27.18.25: S 667:667(0) win 4096 > (ttl 200, id 666) A valid request. Many places have moved their starting user port much higher afte X started in at 6000. If you look at /etc/services, user ports should probably start above 47557 now. > 20:42:56.686714 204.216.27.18.25 > aaa.bbb.ccc.ddd.8000: S > 856239105:856239105(0) ack 668 win 16384 (DF) (ttl 53, id 16513) "Hello", says the FreeBSD box, "I can take a window thiiiiiiiiis big". > 20:42:56.686714 aaa.bbb.ccc.ddd.8000 > 204.216.27.18.25: R 668:668(0) win 0 > (ttl 255, id 5507) "Well", says the caller on line 8000, "I can take a window of 0". > Now at this point SunOS, Linux and NetBSD all take no for an answer, This is not "no for an answer", this is "gee, I don't know how to write a TCP stack; hit me again!". > but FreeBSD just won't quit. It takes FreeBSD another 1min15secs to decide > its SYN's are not wanted (i.e the connection establishment timers kicks in). "Not wanted"? You can't "not want a SYN". If you "not want a SYN" then you "not want a connection". If you are truly honest about "not want a connection", why'd you ask for the thing in the first place? > It should be noted that the initial packet can have its source > faked and the packet exchange will occur between the FreeBSD host and > the unsuspecting other. Only is someone stupid has enabled source routing. I really don't know how you can set a window of 0 and then complain about getting SYN's. Garrett would be a better person to ask, but you might have made his kill file already. 8-|. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Oct 1 18:13:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA21012 for hackers-outgoing; Wed, 1 Oct 1997 18:13:32 -0700 (PDT) Received: from usr04.primenet.com (tlambert@usr04.primenet.com [206.165.6.204]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA21006 for ; Wed, 1 Oct 1997 18:13:28 -0700 (PDT) Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id SAA01588; Wed, 1 Oct 1997 18:12:55 -0700 (MST) From: Terry Lambert Message-Id: <199710020112.SAA01588@usr04.primenet.com> Subject: Re: FreeBSD TCP stack and RST processing [subj changed] To: dg@root.com Date: Thu, 2 Oct 1997 01:12:55 +0000 (GMT) Cc: richard@a42.deep-thought.org, hackers@FreeBSD.ORG In-Reply-To: <199710011014.DAA08484@implode.root.com> from "David Greenman" at Oct 1, 97 03:14:55 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > The main reason I didn't provide version info > >was that I thought it was an easy enough situation to replicate if it was > >indeed replicatable. Unfortunately I know of no systems that are running > >CURRENT to test upon. > > Thanks for the bug report. In the future, it's better to either file a PR > via GNATS or send email to freebsd-bugs; you're more likely to get to the > right people this way. I forwarded your original message to some people > yesterday who might have some input on this. I don't get why this is considered a bug. You do something bizarre, and you get an undefined result. The only thing it could "deny service" on is if you let someone subscribe to a list, and then they ambushed you: a trojan subscription, so to speak. This would be come pretty obvious when the mail failed, and subsequent subscriotions would be blocked. It's only when you stab the guy calling you in the back that you can make him have a long timeout, right? He has to be willing to call you in the first place... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Oct 1 18:16:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA21194 for hackers-outgoing; Wed, 1 Oct 1997 18:16:42 -0700 (PDT) Received: from usr04.primenet.com (tlambert@usr04.primenet.com [206.165.6.204]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA21177; Wed, 1 Oct 1997 18:16:26 -0700 (PDT) Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id SAA01906; Wed, 1 Oct 1997 18:15:57 -0700 (MST) From: Terry Lambert Message-Id: <199710020115.SAA01906@usr04.primenet.com> Subject: Re: FreeBSD TCP stack and RST processing [subj changed] To: dg@root.com Date: Thu, 2 Oct 1997 01:15:57 +0000 (GMT) Cc: Don.Lewis@tsc.tdk.com, richard@a42.deep-thought.org, pst@FreeBSD.ORG, hackers@FreeBSD.ORG, bugs@FreeBSD.ORG In-Reply-To: <199710011151.EAA08698@implode.root.com> from "David Greenman" at Oct 1, 97 04:51:35 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > This appears to have been broken in rev 1.52: [ ... diff ... ] Forget my other posting -- I see the problem now. I still think it requires a trojan connect to trigger it: the attacking system has to get you to connect to it. For normal traffic, sendmail is the only push-model interface, where the sever connects, I think. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Oct 1 18:20:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA21457 for hackers-outgoing; Wed, 1 Oct 1997 18:20:22 -0700 (PDT) Received: from usr04.primenet.com (tlambert@usr04.primenet.com [206.165.6.204]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA21435; Wed, 1 Oct 1997 18:20:14 -0700 (PDT) Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id SAA02029; Wed, 1 Oct 1997 18:19:37 -0700 (MST) From: Terry Lambert Message-Id: <199710020119.SAA02029@usr04.primenet.com> Subject: Re: FreeBSD TCP stack and RST processing [subj changed] To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Thu, 2 Oct 1997 01:19:37 +0000 (GMT) Cc: pst@juniper.net, dg@root.com, Don.Lewis@tsc.tdk.com, richard@a42.deep-thought.org, hackers@FreeBSD.ORG, bugs@FreeBSD.ORG In-Reply-To: <18567.875750082@time.cdrom.com> from "Jordan K. Hubbard" at Oct 1, 97 04:54:42 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > It's been so long since I touched this that I won't offer an opinion. > > The original idea was ripped from Stevens by vjs and then from me, if > > memory serves me. > > Well, since it certainly seems to cause deviation from expected > behavior and none of the other *BSDs have picked it up, shall we > simply rip it out? I think the "ignore H_ACK for the compare" suggestion is best. If we ripped out everything that the other BSD's didn't agree was BSD, then you'd lose things like, oh, the new VM code. And so on. Not a strong justifiable argument, 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 Wed Oct 1 18:38:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA22230 for hackers-outgoing; Wed, 1 Oct 1997 18:38:20 -0700 (PDT) Received: from gatekeeper.tsc.tdk.com (root@gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA22212; Wed, 1 Oct 1997 18:38:15 -0700 (PDT) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.4/8.8.4) with ESMTP id SAA08144; Wed, 1 Oct 1997 18:37:39 -0700 (PDT) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id SAA24062; Wed, 1 Oct 1997 18:37:37 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id SAA16461; Wed, 1 Oct 1997 18:37:36 -0700 (PDT) From: Don Lewis Message-Id: <199710020137.SAA16461@salsa.gv.tsc.tdk.com> Date: Wed, 1 Oct 1997 18:37:36 -0700 In-Reply-To: Richard Jones "Re: FreeBSD TCP stack and RST processing [subj changed]" (Oct 2, 11:09am) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Richard Jones , Paul Traina Subject: Re: FreeBSD TCP stack and RST processing [subj changed] Cc: "Jordan K. Hubbard" , dg@root.com, Don Lewis , hackers@FreeBSD.ORG, bugs@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Oct 2, 11:09am, Richard Jones wrote: } Subject: Re: FreeBSD TCP stack and RST processing [subj changed] } Paul Traina wrote: } > I put it in there for a reason, Steven's III showed a case where you could } > pummel the box with a barage of, I believe, syn ack's and basicly melt things. } > Sorry my memory is so foggy on the issue now. I'll go back and try to } > remember. Steven's III? I don't have that one, since I figured that I already knew how NNTP worked. } Hmm..but if you barrage the system with SYN ACK's when the system is in a } listen state, you shouldn't jump into SYN_RECEIVED should you? Nope. This case is handled earlier: case TCPS_LISTEN: { struct mbuf *am; register struct sockaddr_in *sin; if (tiflags & TH_RST) goto drop; if (tiflags & TH_ACK) goto dropwithreset; if ((tiflags & TH_SYN) == 0) goto drop; } The code } which does the if (TH_RST) stuff is prolly ok...its the addition of the } case SYN_RECEIVED up the top that does the trick. As in goobers it up. } Its ok to look for } an ACK when in SYN_SENT on RST's coz thats what is expected, and if you } get other than expected and drop then its no big deal unless you can force } a remote freebsd system to send out (pure) SYN's to non-connected } ports, unlikely. I only have the snippets posted to the list available, but } based on them I'd say remove the case SYN_RECEIVED that was added. That's what I did in my local source tree. } You might } get away with getting rid of the ACK flag check without losing anything, but } any side effects should be thought through. Yeah, the case of what to do if you receive an ACK in the SYN_RECEIVED case bothers me as well. --- Truck From owner-freebsd-hackers Wed Oct 1 18:40:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA22296 for hackers-outgoing; Wed, 1 Oct 1997 18:40:00 -0700 (PDT) Received: from server.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA22288 for ; Wed, 1 Oct 1997 18:39:57 -0700 (PDT) Received: from localhost (perlsta@localhost) by server.local.sunyit.edu (8.8.7/8.8.5) with SMTP id VAA00247; Wed, 1 Oct 1997 21:43:49 -0500 (EST) X-Authentication-Warning: server.local.sunyit.edu: perlsta owned process doing -bs Date: Wed, 1 Oct 1997 21:43:48 -0500 (EST) From: Alfred Perlstein X-Sender: perlsta@server.local.sunyit.edu To: Warner Losh cc: hackers@FreeBSD.ORG Subject: Re: distributing binaries only? In-Reply-To: <199710012112.PAA26166@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk i appreciate the help, thank you, you saved me a lot of fustration and time. i was kinda over emphisizing the time for a make world, but then i again i never did it on the machine. thanks again, -Alfred > make buildworld on a fast machine. Then NFS mount the /usr/src and > /usr/obj trees and do a make installworld on the 133 box. > > Also my 486 Dx2-66 did make world in about 12 hours, and I likely > could have dropped that down into the 8 hour range with the addition > of more disks, better mount point options, etc. I suspect that 2-3 > days is a little pessimistic, unless the machine has little memory. > > Warner > From owner-freebsd-hackers Wed Oct 1 19:01:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA23353 for hackers-outgoing; Wed, 1 Oct 1997 19:01:33 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id TAA23344 for ; Wed, 1 Oct 1997 19:01:29 -0700 (PDT) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0xGaZt-0007XC-00; Wed, 1 Oct 1997 20:01:21 -0600 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.7/8.8.3) with ESMTP id UAA27747; Wed, 1 Oct 1997 20:02:13 -0600 (MDT) Message-Id: <199710020202.UAA27747@harmony.village.org> To: Alfred Perlstein Subject: Re: distributing binaries only? Cc: hackers@freebsd.org In-reply-to: Your message of "Wed, 01 Oct 1997 21:43:48 CDT." References: Date: Wed, 01 Oct 1997 20:02:13 -0600 From: Warner Losh Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message Alfred Perlstein writes: : i appreciate the help, thank you, you saved me a lot of fustration and : time. Glad I could be of service. The new buildworld/installworld stuff is really neat. Warner From owner-freebsd-hackers Wed Oct 1 19:11:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA23985 for hackers-outgoing; Wed, 1 Oct 1997 19:11:11 -0700 (PDT) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id TAA23964; Wed, 1 Oct 1997 19:11:02 -0700 (PDT) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <52020(2)>; Wed, 1 Oct 1997 19:10:21 PDT Received: by crevenia.parc.xerox.com id <177486>; Wed, 1 Oct 1997 19:10:14 -0700 From: Bill Fenner To: jkh@time.cdrom.com, tlambert@primenet.com Subject: Re: FreeBSD TCP stack and RST processing [subj changed] Cc: Don.Lewis@tsc.tdk.com, bugs@freebsd.org, dg@root.com, hackers@freebsd.org, pst@juniper.net, richard@a42.deep-thought.org Message-Id: <97Oct1.191014pdt.177486@crevenia.parc.xerox.com> Date: Wed, 1 Oct 1997 19:10:10 PDT Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I think the "ignore H_ACK for the compare" suggestion is best. No. Validating the ACK is a required part of RST processing in SYN_SENT state (but not in SYN_RECEIVED). Bill From owner-freebsd-hackers Wed Oct 1 19:17:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA24506 for hackers-outgoing; Wed, 1 Oct 1997 19:17:55 -0700 (PDT) Received: from ingenieria ([168.176.15.11]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id TAA24501 for ; Wed, 1 Oct 1997 19:17:51 -0700 (PDT) Received: from unalmodem.usc.unal.edu.co by ingenieria (SMI-8.6/SMI-SVR4) id WAA16225; Wed, 1 Oct 1997 22:03:42 -0400 Message-ID: <34331F3E.3CD4@asme.org> Date: Wed, 01 Oct 1997 21:12:46 -0700 From: "Pedro Giffuni S," Reply-To: pgiffuni@fps.biblos.unal.edu.co Organization: Universidad Nacional de Colombia X-Mailer: Mozilla 3.01Gold [it] (Win16; I) MIME-Version: 1.0 To: Terry Lambert CC: Simon Shapiro , jamil@counterintelligence.ml.org, freebsd-hackers@FreeBSD.ORG Subject: Re: Good Lord, Commercial Linux References: <199710020036.RAA28729@usr04.primenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk And Noorda didn't leave Novell in a good position either...they seem to be getting better without him. BTW, it seems like the Groupwise client is a Java application :-) Pedro. Terry Lambert wrote: > > > c. BSD came from Berkeley, it is a hack. Linux is systemV like. It has a > > heritage of Large Company. Caldera was founded by Mr. Noorda, he is > > the radical rebel of Corporate America. Made billions with Novell. > > Calder Linux must therfore be a good thing. > > > > Now, BEFORE you jump down my throat, please evaluate the technology I > > employ in my professional work :-) > > Caldera was founded by Brian Sparks. Noorda was an early investor, > but not the initial investor. > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. From owner-freebsd-hackers Wed Oct 1 19:41:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA25631 for hackers-outgoing; Wed, 1 Oct 1997 19:41:08 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id TAA25621 for ; Wed, 1 Oct 1997 19:41:05 -0700 (PDT) Received: (qmail 7621 invoked by uid 1000); 2 Oct 1997 02:41:29 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092597 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Date: Wed, 01 Oct 1997 19:41:29 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: freebsd-hackers@freebsd.org Subject: DLM News Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Y'all. Sorry for the delay. We started a new mailing list, freebsd-dlm@primer.i-connect.net. The list is geared towards discussion of Distributed Lock Manager issues. Those of you who expressed interest in this subject, were automatically subscribed to the list. Those of you who are interested in this subject are very welcome to join the list. To Join: Send an empty e-mail message to: freebsd-dlm-subscribe@primer.i-connect.net To unsubscribe, sen an empty message to: freebsd-dlm-unsubscribe@primer.i-connect.net If there is interest on this list, or others, to post a digest, just let me know. Thanx! --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-hackers Wed Oct 1 19:51:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA26136 for hackers-outgoing; Wed, 1 Oct 1997 19:51:18 -0700 (PDT) Received: from lab321.ru (anonymous1.omsk.net.ru [194.226.32.34]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA26126 for ; Wed, 1 Oct 1997 19:50:57 -0700 (PDT) Received: from lab321.ru (kev.l321.omsk.net.ru [194.226.33.68]) by lab321.ru (8.8.5-MVC-230497/8.8.5) with ESMTP id KAA06753; Thu, 2 Oct 1997 10:55:45 +0600 (OSK) Message-ID: <34330BBA.BE0B0BDD@lab321.ru> Date: Thu, 02 Oct 1997 09:49:30 +0700 From: Eugeny Kuzakov Organization: Powered by FreeBSD. X-Mailer: Mozilla 4.03b8 [en] (X11; I; FreeBSD 3.0-970807-SNAP i386) MIME-Version: 1.0 To: "Alexander V. Tischenko" CC: hackers@FreeBSD.ORG Subject: Re: Recursive fork() and different fbsd's References: <199710011016.OAA25674@thorin.hway.ru> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Alexander V. Tischenko wrote: > > I tried a bit modified sample and got right into resource limit. > Don't know how you can count proc's with your source. > Why you try to modify source ? It's bug(???)/problem in freebsd kernel. My crash.c program hangs freebsd, but not hangs linux and any SysV. ....If I understand you correctly. -- Best wishes, Eugeny Kuzakov Laboratory 321 ( Omsk, Russia ) http://www.lab321.ru/~kev kev@lab321.ru From owner-freebsd-hackers Wed Oct 1 20:56:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA29297 for hackers-outgoing; Wed, 1 Oct 1997 20:56:20 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA29287 for ; Wed, 1 Oct 1997 20:56:16 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id UAA01365 for ; Wed, 1 Oct 1997 20:56:00 -0700 (PDT) Date: Wed, 1 Oct 1997 20:56:00 -0700 (PDT) From: "Jamil J. Weatherbee" To: hackers@freebsd.org Subject: Device drivers Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've taken a look at the source code to a few device drivers and run the example scripts for Isa stuff, I have a general feeling of what needs to be in one and how it operates however I simply don't feel I have enough information (or a well enough documented example) to feel confident writing one myself, does anyone have a document/FAQ no matter how small describng the required functions/tables/probing /irq setup etc. so I would know what exactly I am doing. A line by line walk through of even a cheeseball driver would be greatly appreciated or perhaps even a pointer to a well documented driver (My standard is to have a comment on every line of code, that's what I mean by "well documented"), but preferably not to lengthy where I am goin to mostly be looking at the nitty gritty of a device I don't know about or understand. Someone passed me a driver for a stepper motor, the idea of what it is doing with the physical hardware is easy for me since I deal with that stuff all the time, unfortunately there are hardly no comments. From owner-freebsd-hackers Wed Oct 1 21:00:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA29542 for hackers-outgoing; Wed, 1 Oct 1997 21:00:04 -0700 (PDT) Received: from shell.monmouth.com (root@shell.monmouth.com [205.164.220.9]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA29448; Wed, 1 Oct 1997 20:59:46 -0700 (PDT) Received: from i4got.lakewood.com (ppp80.monmouth.com [205.164.220.112]) by shell.monmouth.com (8.8.5/8.7.3) with ESMTP id XAA04292; Wed, 1 Oct 1997 23:56:00 -0400 (EDT) Received: (from pechter@localhost) by i4got.lakewood.com id XAA00539 (8.8.5/IDA-1.6); Wed, 1 Oct 1997 23:59:37 -0400 (EDT) From: Bill Pechter Message-ID: <199710020359.XAA00539@i4got.lakewood.com> Subject: Sysctl variables To: hackers@freebsd.org Date: Wed, 1 Oct 1997 23:59:37 -0400 (EDT) Cc: chat@freebsd.org Reply-to: pechter@lakewood.com X-Phone-Number: 908-389-3592 X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm copying this to -chat because I'm wondering if there's any user interest in this except just me... I'm back working on the SysV init again. I know it's been a long layoff since a number of you sent code to me to work on. I've now got a dedicated test box and will be working hard on finishing the work that was started by a number of folks. Any chance of getting two varibles in the "official" FreeBSD sysctl MIB base... I was thinking of kern.run_level and kern.last_run_level. I'd like to avoid homebrew kernel patches to do this (I don't think I want to have to continually update the init code after each cvsup upgrade.) If they were standard in the kernel and blank, I think it would allow the SYSV init to be added as a package. This would make utmp changes unnecessary and be kind of slick. We'd be able to make both the BSD and SysV users happy. (I'm going to look at the userland command differences after this... including the ps, ls differences. I still haven't given up on the idea of supporting dual universes and getting tools up to support Unixware and SCO commercial packages.) This is kind of like the Pyramid OS/x System -- they shipped with both the SysV and BSD init programs and a script that will enable either one and save the old rc scripts and init files in the event of a reinstall of the other init. Bill ------------------------------------------------------------------------------ Bill Pechter | 17 Meredith Drive Tinton Falls, NJ 07724 | 908-389-3592 pechter@lakewood.com | Save computing history, give an old geek old hardware. This msg brought to you by the letters PDP and the number 11. From owner-freebsd-hackers Wed Oct 1 22:37:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA04638 for hackers-outgoing; Wed, 1 Oct 1997 22:37:21 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA04621; Wed, 1 Oct 1997 22:37:18 -0700 (PDT) Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id WAA04596; Wed, 1 Oct 1997 22:36:20 -0700 (PDT) To: Terry Lambert cc: pst@juniper.net, dg@root.com, Don.Lewis@tsc.tdk.com, richard@a42.deep-thought.org, hackers@FreeBSD.ORG, bugs@FreeBSD.ORG Subject: Re: FreeBSD TCP stack and RST processing [subj changed] In-reply-to: Your message of "Thu, 02 Oct 1997 01:19:37 -0000." <199710020119.SAA02029@usr04.primenet.com> Date: Wed, 01 Oct 1997 22:36:19 -0700 Message-ID: <4592.875770579@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Well, since it certainly seems to cause deviation from expected > > behavior and none of the other *BSDs have picked it up, shall we > > simply rip it out? > > I think the "ignore H_ACK for the compare" suggestion is best. If we > ripped out everything that the other BSD's didn't agree was BSD, then > you'd lose things like, oh, the new VM code. And so on. Not a strong > justifiable argument, IMO. No, but it's also not my argument. I merely cited it as a data point, any comparison between the VM system and a relatively syn-flood fix being definite apples-and-oranges material anyway. The other *BSDs generally do track one another's DoS and general security fixes unless there's a clear reason to avoid something. The VM system is not in this category, it's merely too hard to track in a multi-architecture environment (not for want of trying on the part of various folks in NetBSD, at least). Jordan From owner-freebsd-hackers Wed Oct 1 23:20:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA06825 for hackers-outgoing; Wed, 1 Oct 1997 23:20:59 -0700 (PDT) Received: from bunyip.cc.uq.edu.au (daemon@bunyip.cc.uq.edu.au [130.102.2.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA06819 for ; Wed, 1 Oct 1997 23:20:53 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.edu.au (8.8.7/8.8.7) id QAA00235; Thu, 2 Oct 1997 16:20:11 +1000 Received: from localhost.dtir.qld.gov.au (localhost.dtir.qld.gov.au [127.0.0.1]) by ogre.dtir.qld.gov.au (8.8.7/8.8.7) with SMTP id QAA20756; Thu, 2 Oct 1997 16:20:56 +1000 (EST) Message-Id: <199710020620.QAA20756@ogre.dtir.qld.gov.au> X-Authentication-Warning: ogre.dtir.qld.gov.au: localhost.dtir.qld.gov.au [127.0.0.1] didn't use HELO protocol To: Bill Pechter cc: freebsd-hackers@freebsd.org, syssgm@dtir.qld.gov.au Subject: Re: Sysctl variables References: <199710020359.XAA00539@i4got.lakewood.com> In-Reply-To: <199710020359.XAA00539@i4got.lakewood.com> from Bill Pechter at "Thu, 02 Oct 1997 03:59:37 +0000" Date: Thu, 02 Oct 1997 16:20:56 +1000 From: Stephen McKay Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thursday, 2nd October 1997, Bill Pechter wrote: >I'm copying this to -chat because I'm wondering if there's any user interest >in this except just me... > >I'm back working on the SysV init again. I know it's been a long layoff since >a number of you sent code to me to work on. I've now got a dedicated test >box and will be working hard on finishing the work that was started by >a number of folks. > >Any chance of getting two varibles in the "official" FreeBSD sysctl MIB base.. > >I was thinking of kern.run_level and kern.last_run_level. >I'd like to avoid homebrew kernel patches to do this (I don't think I want >to have to continually update the init code after each cvsup upgrade.) > >If they were standard in the kernel and blank, I think it would allow the >SYSV init to be added as a package. This would make utmp changes >unnecessary and be kind of slick. We'd be able to make both the BSD and >SysV users happy. (I'm going to look at the userland command differences >after this... including the ps, ls differences. I still haven't given up >on the idea of supporting dual universes and getting tools up to support >Unixware and SCO commercial packages.) > >This is kind of like the Pyramid OS/x System -- they shipped with both >the SysV and BSD init programs and a script that will enable either one >and save the old rc scripts and init files in the event of a reinstall of >the other init. My first reaction to this is "OH MY GOD, NO!!!". Look in the mail archives for the run_level/run_state wars. I think it's the only time I've beaten Terry into submission. ;-) To be clear: I am very glad we have no SysV style run levels. I think they are a technically inferior solution. On the other hand, there's no reason why the occasional superior item can't be imported. Digital Unix has a ps command that supports both syntax styles. I can use "ps -ef" or "ps axl" any time I like. This stuff I'll help with. Similarly, both BSD and SysV printing subsystems suck. If you have a better one, tell us all about it. But OS/x?! I only talk about that to emphasise Great Failures! The Pyramid dual universe stuff was a pain in the arse. No, a Right Royal Pain in the Arse. All those variant symlinks and stuff just made things pretty much impossible to get right. You couldn't stay in one universe and do it all; you had to pop from one to the other to get a useful set of features working. We had our Pyramids crushed a couple weeks ago. Woo Hoo! So, please, no dual universes. Stephen. From owner-freebsd-hackers Wed Oct 1 23:52:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA08154 for hackers-outgoing; Wed, 1 Oct 1997 23:52:08 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA08146 for ; Wed, 1 Oct 1997 23:52:03 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA27044 for freebsd-hackers@freefall.FreeBSD.org; Thu, 2 Oct 1997 08:52:02 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id IAA15601; Thu, 2 Oct 1997 08:29:13 +0200 (MET DST) Message-ID: <19971002082913.AL43712@uriah.heep.sax.de> Date: Thu, 2 Oct 1997 08:29:13 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freefall.FreeBSD.org Subject: Re: r-cmds and DNS and /etc/host.conf References: <199710011709.NAA12633@lakes.dignus.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199710011709.NAA12633@lakes.dignus.com>; from Thomas David Rivers on Oct 1, 1997 13:09:29 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Thomas David Rivers wrote: > > > 127.0.0.1 localhost.dignus.com. localhost.dignus.com localhost > > > 10.0.0.1 ponds ponds.dignus.com ponds.dignus.com. > > > 10.0.0.3 lakes lakes.dignus.com lakes.dignus.com. > > > > Didn't you say there's another domain involved (by resolv.conf, IIRC)? > > Yes, my /etc/resolv.conf claims the machine is in a different > domain (vnet.net). > > Could that be the problem? Yes. I wouldn't be surprised if one of the clients were asking for localhost.vnet.net. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Thu Oct 2 00:01:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA08671 for hackers-outgoing; Thu, 2 Oct 1997 00:01:39 -0700 (PDT) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA08665 for ; Thu, 2 Oct 1997 00:01:32 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id QAA00788; Thu, 2 Oct 1997 16:28:47 +0930 (CST) Message-Id: <199710020658.QAA00788@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Dan Busarow cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: More ATAPI Zip news (will he ever shut up?) In-reply-to: Your message of "Sat, 27 Sep 1997 09:24:49 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Oct 1997 16:28:46 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I believe so; I don't have access to any of the older IDE units at the > > moment, but if you have a part number on the IDE version I can compare > > it with that on the ATAPI-only one later today. > > P/N 320056-01, Model Z100IDE ZIP Took a bit longer than a day. 8( No part number, Model Z100ATAPI Zip. > What about the LS120 drives, anyone using (and booting) those? The glossy says "Functions as standard Drive A, can act as boot drive". However it also says "Supported by all major BIOS manufacturers", so I suspect that it's in the same category. We need an ATAPI disk driver 8) mike From owner-freebsd-hackers Thu Oct 2 00:02:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA08724 for hackers-outgoing; Thu, 2 Oct 1997 00:02:40 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA08718 for ; Thu, 2 Oct 1997 00:02:34 -0700 (PDT) Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id AAA22281; Thu, 2 Oct 1997 00:01:29 -0700 (PDT) To: Stephen McKay cc: Bill Pechter , freebsd-hackers@FreeBSD.ORG Subject: Re: Sysctl variables In-reply-to: Your message of "Thu, 02 Oct 1997 16:20:56 +1000." <199710020620.QAA20756@ogre.dtir.qld.gov.au> Date: Thu, 02 Oct 1997 00:01:27 -0700 Message-ID: <22273.875775687@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > So, please, no dual universes. OK, how about Domain/OS variant symlinks? :-) Jordan From owner-freebsd-hackers Thu Oct 2 01:20:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA12253 for hackers-outgoing; Thu, 2 Oct 1997 01:20:27 -0700 (PDT) Received: from usr08.primenet.com (tlambert@usr08.primenet.com [206.165.6.208]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA12248 for ; Thu, 2 Oct 1997 01:20:24 -0700 (PDT) Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id BAA24323; Thu, 2 Oct 1997 01:20:05 -0700 (MST) From: Terry Lambert Message-Id: <199710020820.BAA24323@usr08.primenet.com> Subject: Re: Good Lord, Commercial Linux To: pgiffuni@fps.biblos.unal.edu.co Date: Thu, 2 Oct 1997 08:20:05 +0000 (GMT) Cc: tlambert@primenet.com, Shimon@i-Connect.Net, jamil@counterintelligence.ml.org, freebsd-hackers@FreeBSD.ORG In-Reply-To: <34331F3E.3CD4@asme.org> from "Pedro Giffuni S," at Oct 1, 97 09:12:46 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > And Noorda didn't leave Novell in a good position either...they seem to > be getting better without him. > BTW, it seems like the Groupwise client is a Java application :-) Noorda was forced out by Mar Burnside and the other members of "The Office Of The President", a triumvarite of which Burnside was the strongest member. Burnside was a bean-counter (accountant) who decided that the best way to optimize short term profit was to milk the existing product line to death without investment in new technology. That strategy has a 5 year cap. Novell is doing better because of the retirement of the HP vice president, Frankenburg, who never got over the V.P. "Yes man" stage and thus let people like Mike DeFazio ride roughshod over him. 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 Oct 2 01:26:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA12473 for hackers-outgoing; Thu, 2 Oct 1997 01:26:00 -0700 (PDT) Received: from usr08.primenet.com (tlambert@usr08.primenet.com [206.165.6.208]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA12468; Thu, 2 Oct 1997 01:25:58 -0700 (PDT) Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id BAA24472; Thu, 2 Oct 1997 01:25:51 -0700 (MST) From: Terry Lambert Message-Id: <199710020825.BAA24472@usr08.primenet.com> Subject: Re: FreeBSD TCP stack and RST processing [subj changed] To: fenner@parc.xerox.com (Bill Fenner) Date: Thu, 2 Oct 1997 08:25:50 +0000 (GMT) Cc: jkh@time.cdrom.com, tlambert@primenet.com, Don.Lewis@tsc.tdk.com, bugs@freebsd.org, dg@root.com, hackers@freebsd.org, pst@juniper.net, richard@a42.deep-thought.org In-Reply-To: <97Oct1.191014pdt.177486@crevenia.parc.xerox.com> from "Bill Fenner" at Oct 1, 97 07:10:10 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >I think the "ignore H_ACK for the compare" suggestion is best. > > No. Validating the ACK is a required part of RST processing in SYN_SENT > state (but not in SYN_RECEIVED). The fallthrough case does this. We are talking about the conditions under which a fallthreough can occur. 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 Oct 2 01:28:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA12628 for hackers-outgoing; Thu, 2 Oct 1997 01:28:10 -0700 (PDT) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA12622 for ; Thu, 2 Oct 1997 01:28:07 -0700 (PDT) Received: (from sos@localhost) by sos.freebsd.dk (8.8.7/8.7.3) id KAA02053; Thu, 2 Oct 1997 10:27:28 +0200 (MEST) From: SЬren Schmidt Message-Id: <199710020827.KAA02053@sos.freebsd.dk> Subject: Re: Sysctl variables In-Reply-To: <22273.875775687@time.cdrom.com> from "Jordan K. Hubbard" at "Oct 2, 97 00:01:27 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Thu, 2 Oct 1997 10:27:28 +0200 (MEST) Cc: syssgm@dtir.qld.gov.au, pechter@lakewood.com, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Jordan K. Hubbard who wrote: > > So, please, no dual universes. > > OK, how about Domain/OS variant symlinks? :-) Yes! oh yes yes yes... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- SЬren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Thu Oct 2 01:37:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA13184 for hackers-outgoing; Thu, 2 Oct 1997 01:37:57 -0700 (PDT) Received: from usr08.primenet.com (tlambert@usr08.primenet.com [206.165.6.208]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA13179 for ; Thu, 2 Oct 1997 01:37:55 -0700 (PDT) Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id BAA24945; Thu, 2 Oct 1997 01:37:35 -0700 (MST) From: Terry Lambert Message-Id: <199710020837.BAA24945@usr08.primenet.com> Subject: Re: Sysctl variables To: syssgm@dtir.qld.gov.au (Stephen McKay) Date: Thu, 2 Oct 1997 08:37:35 +0000 (GMT) Cc: pechter@lakewood.com, freebsd-hackers@FreeBSD.ORG, syssgm@dtir.qld.gov.au In-Reply-To: <199710020620.QAA20756@ogre.dtir.qld.gov.au> from "Stephen McKay" at Oct 2, 97 04:20:56 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > My first reaction to this is "OH MY GOD, NO!!!". Look in the mail archives > for the run_level/run_state wars. I think it's the only time I've beaten > Terry into submission. ;-) To be clear: I am very glad we have no SysV > style run levels. I think they are a technically inferior solution. More of a mutual acknowledgement of irreconcilability than sumbission; I really don't buy the BSD model. An idea can be good, even if it originated with USL (not everyone at USL is the moron that the BSD camps would seem to have us believe). Meanwhile, I want run states, not levels, so that transitions do not have to be monotonically increasing or decreasing. ;-). > On the other hand, there's no reason why the occasional superior item can't > be imported. Digital Unix has a ps command that supports both syntax styles. > I can use "ps -ef" or "ps axl" any time I like. This stuff I'll help with. I use "-gax". If the "no '-' convention is used to distinguish them, there will be a lot of losers... > Similarly, both BSD and SysV printing subsystems suck. If you have a > better one, tell us all about it. Palladioum, from Project Athena at MIT. The only real problem with it is that it soes not specify a general queue management subsystem upon which it is layered. Garrett Wollman and I happen to agree on printing models (from conversations of 3 or more years ago). > The Pyramid dual universe stuff was a pain in the arse. Mostly because of how the user environment is still linked off of a global envp in the user data space instead of as a logical name table off the proc struct. POSIX is the pain in this regard, because of the execve(2) requirements it makes, syntactically. This is a flaw in POSIX (one of many). > All those variant symlinks and stuff just made things pretty much > impossible to get right. You couldn't stay in one universe and do it all; > you had to pop from one to the other to get a useful set of features working. Implementation details. Really. Consider a "Linux ABI Universe" on a FreeBSD system, and the freedom to mix binary types without inheritance of "/compat/" in the system call table per ABI... The lack of (effectively) "logical name tables" is what is screwing you. 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 Oct 2 01:40:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA13384 for hackers-outgoing; Thu, 2 Oct 1997 01:40:16 -0700 (PDT) Received: from usr08.primenet.com (tlambert@usr08.primenet.com [206.165.6.208]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA13374 for ; Thu, 2 Oct 1997 01:40:14 -0700 (PDT) Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id BAA24994; Thu, 2 Oct 1997 01:40:05 -0700 (MST) From: Terry Lambert Message-Id: <199710020840.BAA24994@usr08.primenet.com> Subject: Re: r-cmds and DNS and /etc/host.conf To: joerg_wunsch@uriah.heep.sax.de Date: Thu, 2 Oct 1997 08:40:04 +0000 (GMT) Cc: freebsd-hackers@freefall.FreeBSD.org In-Reply-To: <19971002082913.AL43712@uriah.heep.sax.de> from "J Wunsch" at Oct 2, 97 08:29:13 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Could that be the problem? > > Yes. I wouldn't be surprised if one of the clients were asking for > localhost.vnet.net. In my case, it's the fully qualified host name. As I said before, how the hell does it know to qualify the host name when it reads /etc/host.conf and doesn't read /etc/resolv.conf to determine the domain name until the /etc/hosts reverse lookup fails? The /etc/hosts lookup should not be qualified, nor should it fail... 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 Oct 2 01:43:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA13493 for hackers-outgoing; Thu, 2 Oct 1997 01:43:03 -0700 (PDT) Received: from usr08.primenet.com (tlambert@usr08.primenet.com [206.165.6.208]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA13488 for ; Thu, 2 Oct 1997 01:43:01 -0700 (PDT) Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id BAA25099; Thu, 2 Oct 1997 01:42:33 -0700 (MST) From: Terry Lambert Message-Id: <199710020842.BAA25099@usr08.primenet.com> Subject: Re: Good Lord, Commercial Linux To: tlambert@primenet.com (Terry Lambert) Date: Thu, 2 Oct 1997 08:42:33 +0000 (GMT) Cc: pgiffuni@fps.biblos.unal.edu.co, tlambert@primenet.com, Shimon@i-Connect.Net, jamil@counterintelligence.ml.org, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199710020820.BAA24323@usr08.primenet.com> from "Terry Lambert" at Oct 2, 97 08:20:05 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Noorda was forced out by Mar Burnside and the other members of "The Mary > Burnside was a bean-counter (accountant) who decided that the best way > to optimize short term profit was to milk the existing product line to > death without investment in new technology. That strategy has a 5 year > cap. And this sould not have made it to this list, since socioecnomic modelling is not this list's strong point... Sorry. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Thu Oct 2 02:49:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA16766 for hackers-outgoing; Thu, 2 Oct 1997 02:49:21 -0700 (PDT) Received: from bunyip.cc.uq.edu.au (daemon@bunyip.cc.uq.edu.au [130.102.2.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA16757 for ; Thu, 2 Oct 1997 02:49:11 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.edu.au (8.8.7/8.8.7) id TAA21247; Thu, 2 Oct 1997 19:49:05 +1000 Received: from troll.dtir.qld.gov.au (troll.dtir.qld.gov.au [167.123.8.1]) by ogre.dtir.qld.gov.au (8.8.7/8.8.7) with ESMTP id TAA06619; Thu, 2 Oct 1997 19:49:51 +1000 (EST) Received: from localhost (syssgm@localhost) by troll.dtir.qld.gov.au (8.8.5/8.8.5) with SMTP id TAA08205; Thu, 2 Oct 1997 19:49:48 +1000 (EST) Message-Id: <199710020949.TAA08205@troll.dtir.qld.gov.au> X-Authentication-Warning: troll.dtir.qld.gov.au: syssgm@localhost didn't use HELO protocol To: Terry Lambert cc: freebsd-hackers@FreeBSD.ORG, syssgm@dtir.qld.gov.au Subject: Re: Sysctl variables References: <199710020837.BAA24945@usr08.primenet.com> In-Reply-To: <199710020837.BAA24945@usr08.primenet.com> from Terry Lambert at "Thu, 02 Oct 1997 08:37:35 +0000" Date: Thu, 02 Oct 1997 19:49:47 +1000 From: Stephen McKay Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thursday, 2nd October 1997, Terry Lambert wrote: >An idea can be good, even if it >originated with USL (not everyone at USL is the moron that the BSD >camps would seem to have us believe). Come on! It's fun to toss rocks at USL for being a bunch of duffers. Just look at the SysV IPC stuff for a crock that was whacked in in a hurry, and never removed for a proper burial. Look how long they held on to 14 char file names and slow file systems. Remember that awful shell layers stuff that was supposed to be better than BSD job control! And who can forget the original ulimit? USL's halfwit answer to BSD quotas. But honestly, I don't bag run levels (or even run states) because USL got there first. I bag them because I think they deserve it. >> On the other hand, there's no reason why the occasional superior item can't >> be imported. Digital Unix has a ps command that supports both syntax styles. >> I can use "ps -ef" or "ps axl" any time I like. This stuff I'll help with. > >I use "-gax". If the "no '-' convention is used to distinguish them, >there will be a lot of losers... *giggle* Puzzled by the 'g' in your command I checked the source. case 'g': break; /* no-op */ Did you add that one? :-) OK, it's a bummer if you already use the '-' prefix with BSD. That makes the hybrid less attractive, and I suppose "ps" would check to see if it is running as "s5ps" before using the SysV command syntax. I would still be happy to see the DEC variant imported anyway. Us oldies still use ps and tar without '-', and newbies probably try 'ps -ef' anyway. >Palladioum, from Project Athena at MIT. The only real problem with it >is that it soes not specify a general queue management subsystem upon >which it is layered. Garrett Wollman and I happen to agree on printing >models (from conversations of 3 or more years ago). It's not a port yet. Is the source easy to get? Web searching got me hits on chemical engineering processes, rock music, and role playing games. :-( Yes, I even tried it spelt "palladioum" and got a Greek hotel, and something that sounded catchy but was actually very dull called "Gretchen goes to the Internet". I suppose the Internet is still the future, not the present... >> All those variant symlinks and stuff just made things pretty much >> impossible to get right. You couldn't stay in one universe and do it all; >> you had to pop from one to the other to get a useful set of features working. > >Implementation details. Really. Consider a "Linux ABI Universe" on a >FreeBSD system, and the freedom to mix binary types without inheritance >of "/compat/" in the system call table per ABI... The idea of a Linux ABI Universe that has some programs I want to use while not having other programs I want to use is 1) a likely event, and 2) a pain. If you are proposing the sort of either/or dual universe that Pyramid had, then I am completely opposed. The current linux emulator does a good job for me with minimal file system aberration. >The lack of (effectively) "logical name tables" is what is screwing you. Are you suggesting something with a Plan 9 flavour where each process sees a different file system name space? Interesting idea, but too radical to wedge into FreeBSD and still call it FreeBSD. Stephen. From owner-freebsd-hackers Thu Oct 2 04:12:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA19346 for hackers-outgoing; Thu, 2 Oct 1997 04:12:56 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA19341 for ; Thu, 2 Oct 1997 04:12:52 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id EAA19164; Thu, 2 Oct 1997 04:15:29 -0700 (PDT) Message-Id: <199710021115.EAA19164@implode.root.com> To: "Mike Durian" cc: hackers@FreeBSD.ORG Subject: Re: strange interaction with Pentium and fxp In-reply-to: Your message of "Wed, 01 Oct 1997 17:06:05 MDT." <199710012306.RAA25757@pluto.plutotech.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 02 Oct 1997 04:15:29 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I'm got a better grasp on the problem now. I tried running >the new kernel on another P6 system and when I experienced the >same problem, I knew it wasn't a chipset bug. The only difference >between the two P6's was the amount of memory. The one that >worked had 64MB and the one that failed on 32MB. When I put >64MB in the one that failed, it started working. Then I put >64MB in the Pentium machine and it too started working. Here's >what I know: > >Machine Mem kernel mbuf Phys Addr. result >P6 64MB new NA OK >P6 32MB new NA fail >P5 32MB new 0x00003f54 fail >P5 32MB old 0x002b9f54 OK >P5 64MB new 0x0009bf54 OK > >Apparently, there is a problem with the EtherExpress card >DMAing data out of host memory at physical address 0x3f54 >using the memory read multiple PCI transaction. > Does anyone know why 0x3f54 would be an unacceptable >address, and does anyone have a fix? I'm not able to reproduce the problem here. I added a bunch of code to FreeBSD to set aside the lower few pages specifically for mbufs, carefully tuned so that the page at 0x3000 was the first page to be used in DMA with the fxp card. The DMAs started at the following addresses at startup: 0x3f56 0x3f56 0x3eb6 0x4056 0x409e 0x419e 0x411e 0x429e 0x3e1e 0x439e (...) This was tested on both a 430VX (P5) chipset MB and a 440FX (P6/Natoma), with both 32MB of RAM and 64MB of RAM, and both -stable and -current. There were no hangs or any other problems. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Thu Oct 2 05:49:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA23466 for hackers-outgoing; Thu, 2 Oct 1997 05:49:55 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA23455 for ; Thu, 2 Oct 1997 05:49:46 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id WAA00408; Thu, 2 Oct 1997 22:13:53 +0930 (CST) Message-Id: <199710021243.WAA00408@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jamil J. Weatherbee" cc: hackers@freebsd.org Subject: Re: Device drivers In-reply-to: Your message of "Wed, 01 Oct 1997 20:56:00 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Oct 1997 22:13:52 +0930 From: Mike Smith Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hey Jamil, I'll say it again: Format Your Messages. I'm pretty prolific when it comes to replying to stuff, and I was this || close to throwing this one out. You are really seriously handicapping yourself here. > I've taken a look at the source code to a few device drivers and run the > example scripts for Isa stuff, I have a general feeling of what needs to > be in one and how it operates however I simply don't feel I have enough > information (or a well enough documented example) to feel confident > writing one myself. The skeletons are a good start; just accumulate bits relevant to your hardware's functions as you go. What it actually sounds like is that you can't work out how to map the activities of your hardware onto the device model. In the case of the hardware you've been talking about before it's likely that you're expecting to do more in the driver than is actually necessary. > does anyone have a document/FAQ no matter how small > describng the required functions/tables/probing /irq setup etc. Not really; the existing driver set is actually pretty good for this. Look at another driver that does something similar to yours and work off that. If you have specific questions, by all means post them. OTOH, posting a "will someone else do all my work for me" message won't get you much. (Hint: this is a learning process. It's not _meant_ to be easy, or you wouldn't take anything useful away from it.) > A line by line walk through of even a > cheeseball driver would be greatly appreciated or perhaps even a pointer > to a well documented driver Again, the skeletons are pretty good here. If you want to take this off the list, I'd be happy to talk you through the process. One proviso; learn first about "paragraphs". 8) mike From owner-freebsd-hackers Thu Oct 2 06:56:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA26709 for hackers-outgoing; Thu, 2 Oct 1997 06:56:04 -0700 (PDT) Received: from inetfw.sonycsl.co.jp (inetfw.sonycsl.co.jp [203.137.129.4]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA26674 for ; Thu, 2 Oct 1997 06:55:58 -0700 (PDT) Received: from hotaka.csl.sony.co.jp (hotaka.csl.sony.co.jp [43.27.98.57]) by inetfw.sonycsl.co.jp (8.8.5/3.5W) with ESMTP id WAA08474 for ; Thu, 2 Oct 1997 22:55:55 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by hotaka.csl.sony.co.jp (8.8.4/3.3W3) with ESMTP id WAA16171 for ; Thu, 2 Oct 1997 22:55:40 +0900 (JST) Message-Id: <199710021355.WAA16171@hotaka.csl.sony.co.jp> To: hackers@FreeBSD.ORG Subject: icmp sourcequench Date: Thu, 02 Oct 1997 22:55:39 +0900 From: Kenjiro Cho Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I noticed that FreeBSD routers (and most other BSD based routers) send an ICMP_SOURCEQUENCH packet everytime a forwarding packet gets dropped, in other words, ip_forward receives ENOBUFS from ip_output. Isn't it better to comment out this part of the code? RFC1812 (Requirements for IP Version 4 Routers) says: 4.3.3.3 Source Quench A router SHOULD NOT originate ICMP Source Quench messages. As specified in Section [4.3.2], a router that does originate Source Quench messages MUST be able to limit the rate at which they are generated. DISCUSSION Research seems to suggest that Source Quench consumes network bandwidth but is an ineffective (and unfair) antidote to congestion. See, for example, [INTERNET:9] and [INTERNET:10]. Section [5.3.6] discusses the current thinking on how routers ought to deal with overload and network congestion. --kj --- Kenjiro Cho Sony Computer Science Laboratory Inc. From owner-freebsd-hackers Thu Oct 2 07:53:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA29822 for hackers-outgoing; Thu, 2 Oct 1997 07:53:09 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA29809 for ; Thu, 2 Oct 1997 07:52:42 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id AAA00412; Fri, 3 Oct 1997 00:19:31 +0930 (CST) Message-Id: <199710021449.AAA00412@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jordan K. Hubbard" cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: Interface configuration : call for ideas. In-reply-to: Your message of "Wed, 01 Oct 1997 13:30:45 MST." <17758.875737845@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Oct 1997 00:19:30 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Ah, some input! I thought you were busy? If this is the quality of > > feedback I get from busy people, we must be alone here... 8( > > I am busy, but I hated to see this get the usual silent treatment. :-) Yah. I've had a couple of OOB responses, mostly cautious-approving. > Also, if you think about it, the system's initial boot is also sort of > an "event" of sorts - I'm sure you could generalize this to the point > of absurdity, and it might not even be that bad of an idea. Whilst it would be nice to take the current sequential bootstrap approach and remodel it in a dependancy-based fashion, I could see this confusing people a great deal. The current approach has the substantial virtue of simplicity, not to mention historical precedent. > > OK here. I'm not sure how others will buy it. Perhaps a POC > > implementation is called for? How do people feel about a potentially > > new directory in /etc for files associated with this sort of thing? > > POC? Proof Of Concept. > > Is there any way in sh of determining the existence of a function? > > I thought you'd just expand the target variable and check it > for NULL-ness (""). If it expands, you pass it to eval. If it > doesn't, you move on. I don't want to use variables, as it's unpleasant to stack more than one command into a variable. I was thinking either shell functions or discrete files in a subdirectory; the most-default file would implement fallback behaviour suited to the ifconfig_xx* variables currently in use for compatability's sake. mike From owner-freebsd-hackers Thu Oct 2 08:36:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA02738 for hackers-outgoing; Thu, 2 Oct 1997 08:36:28 -0700 (PDT) Received: from usr05.primenet.com (tlambert@usr05.primenet.com [206.165.6.205]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA02732 for ; Thu, 2 Oct 1997 08:36:19 -0700 (PDT) Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id IAA13987; Thu, 2 Oct 1997 08:35:50 -0700 (MST) From: Terry Lambert Message-Id: <199710021535.IAA13987@usr05.primenet.com> Subject: Re: Sysctl variables To: syssgm@dtir.qld.gov.au (Stephen McKay) Date: Thu, 2 Oct 1997 15:35:50 +0000 (GMT) Cc: tlambert@primenet.com, freebsd-hackers@FreeBSD.ORG, syssgm@dtir.qld.gov.au In-Reply-To: <199710020949.TAA08205@troll.dtir.qld.gov.au> from "Stephen McKay" at Oct 2, 97 07:49:47 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >> I can use "ps -ef" or "ps axl" any time I like. This stuff I'll help with. > > > >I use "-gax". If the "no '-' convention is used to distinguish them, > >there will be a lot of losers... > > *giggle* Puzzled by the 'g' in your command I checked the source. > > case 'g': > break; /* no-op */ > > Did you add that one? :-) No. Berkeley did. -g Display all processes. Without this option, ps prints only "interesting" processes. Processes are deemed to be uninteresting if they are process group leaders. This normally eliminates top-level command interpreters and processes waiting for users to login on free termi- nals. > OK, it's a bummer if you already use the '-' prefix with BSD. That makes > the hybrid less attractive, and I suppose "ps" would check to see if it is > running as "s5ps" before using the SysV command syntax. I would still be > happy to see the DEC variant imported anyway. Us oldies still use ps and > tar without '-', and newbies probably try 'ps -ef' anyway. > >Palladioum, from Project Athena at MIT. The only real problem with it > >is that it soes not specify a general queue management subsystem upon > >which it is layered. Garrett Wollman and I happen to agree on printing > >models (from conversations of 3 or more years ago). > > It's not a port yet. Is the source easy to get? Web searching got me hits > on chemical engineering processes, rock music, and role playing games. :-( > Yes, I even tried it spelt "palladioum" and got a Greek hotel, and something > that sounded catchy but was actually very dull called "Gretchen goes to the > Internet". I suppose the Internet is still the future, not the present... Well, the 'o' was a typo. I "don't know" how easy the code from Project Athena is to get... let's see... can you tel me where to get X Windows? That's out of Athena, too. 8-) 8-). > The idea of a Linux ABI Universe that has some programs I want to use while > not having other programs I want to use is 1) a likely event, and 2) a pain. > If you are proposing the sort of either/or dual universe that Pyramid had, > then I am completely opposed. The current linux emulator does a good job > for me with minimal file system aberration. The FS aberration for Linux emulation currently impacts all system calls which take file name arguments: open, creat, link, unlink, chdir, mknod, chmod, chown, mount, unmount, access, chflags, stat, lstat, acct, revoke, symlink, readlink, chroot, truncate, ftruncate, mkfifo, mkdir, rmdir, utimes, quotactl, statfs pathconf, undelete, and lchown. This means that, even if the call is functionally identical to the FreeBSD call, a stub must exist for each of these calls supported by the emulated ABI, times the number of ABI's. A variant symlink approach that set the process local name that was used to process the non-relative path roots would mean a single change to namei(), instead of all these stubs. > >The lack of (effectively) "logical name tables" is what is screwing you. > > Are you suggesting something with a Plan 9 flavour where each process sees > a different file system name space? Interesting idea, but too radical to > wedge into FreeBSD and still call it FreeBSD. No, I'm suggesting that we do away with external access to envp, and hang the environment off the proc struct instead. Then the process group leader's environment is the group logical name table, and the init process' environmnet is the system logical name table. Hopefully, you replace the initial process exec at login with a session manager, but it's not mandatory (only very, very useful) to have one. It solves the "how do I set global environment variables" proble, the "how do I change my paren't environment" problem, the "how do I access environment variables from the kernel when envp may have changed" problem, the "where do I stick session management information, like 'SMBFS' and 'NetWare' credentials" problem, the "how do I share an environment between siblings with the same parent" problem, and a host of others. The only thing you loses is the ability to manipulate the environment directly by hacking on envp instead of using the environment manipulation functions like you were supposed to be doing in the first place. You can build an environment by iterating (not shown here) the current processes table, and building an envp. Ideally, you would use a vfork instead, and do the manipulation prior to the exec on an inherited copy of the parent's environment, but you can't fight City Hall (in this case, POSIX's definition of execve(2)). Plus, it's pretty trivial to implement, assuming a call to get at these tables exists, and these tables are maintained in the same form as they are maintained currently in libc; the replacement libc code looks like: -------------------------------------------------------------------------- /* * getenv -- * Returns ptr to value associated with name, if any, else NULL. */ char * getenv(name) const char *name; { static char ret[ LNM_GET_MAX]; struct lnm_get_arg get; /* * search all tables on lookup; cariables set in LNM_TYPE_PROCESS * overrides LNM_TYPE_GROUP overrides LNM_TYPE_SYSTEM */ get.name = name; /* name to get*/ get.buf = ret; /* store it here*/ get.bufsize = LNM_MAX_GET; /* max of this many*/ get.flags = LNM_FLAG_INHERIT; /* inherit values*/ get.table = LNM_TYPE_ANY; /* name table to use*/ if( syslnm( LNM_CMD_GET, (caddr_t)&get)) return( NULL); else return( ret); } int putenv(str) const char *str; { struct lnm_set_arg set; char *p, *equal; int rval; if ((p = strdup(str)) == NULL) return (-1); if ((equal = index(p, '=')) == NULL) { (void)free(p); return (-1); } *equal = '\0'; /* * set only in LNM_TYPE_PROCESS; use syslnm() instead of * putenv() to access other spaces; credentials are enforced */ set.name = name; /* name to set*/ set.buf = equal + 1; /* value to assign*/ set.flags = LNM_FLAG_REPLACE; /* replae if exists*/ set.table = LNM_TYPE_PROCESS; /* process name table*/ rval = syslnm( LNM_CMD_SET, (caddr_t)&set); (void)free(p); return (rval); } /* * setenv -- * Set the value of the environmental variable "name" to be * "value". If rewrite is set, replace any current value. */ setenv(name, value, rewrite) register const char *name; register const char *value; int rewrite; { struct lnm_set_arg set; /* * set only in LNM_TYPE_PROCESS; use syslnm() instead of * setenv() to access other spaces; credentials are enforced */ set.name = name; /* name to set*/ set.buf = value; /* value to assign*/ set.flags = ( rewrite ? LNM_FLAG_REPLACE : 0); /* conditionally replace*/ set.table = LNM_TYPE_PROCESS; /* process name table*/ return( syslnm( LNM_CMD_SET, (caddr_t)&set)); } /* * unsetenv(name) -- * Delete environmental variable "name". */ void unsetenv(name) const char *name; { struct lnm_del_arg del; /* * remove only in LNM_TYPE_PROCESS; use syslnm() instead of * unsetenv() to access other spaces; credentials are enforced */ del.name = name; /* name to delete*/ del.flags = 0; /* no flags*/ del.table = LNM_TYPE_PROCESS; /* delete from process*/ (void)syslnm( LNM_CMD_UNSET, (caddr_t)&del); } -------------------------------------------------------------------------- Other types of access, and ideally, any new code's access, is via the syslnm() call. 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 Oct 2 08:40:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA03012 for hackers-outgoing; Thu, 2 Oct 1997 08:40:31 -0700 (PDT) Received: from server.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA03005 for ; Thu, 2 Oct 1997 08:40:24 -0700 (PDT) Received: from localhost (perlsta@localhost) by server.local.sunyit.edu (8.8.7/8.8.5) with SMTP id LAA02731 for ; Thu, 2 Oct 1997 11:45:28 -0500 (EST) X-Authentication-Warning: server.local.sunyit.edu: perlsta owned process doing -bs Date: Thu, 2 Oct 1997 11:45:28 -0500 (EST) From: Alfred Perlstein X-Sender: perlsta@server.local.sunyit.edu To: hackers@FreeBSD.org Subject: help with tutorial = printscreen during boot Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk i was wondering it it would be a major undertaking to get the printscreen key to work while in the visual boot editor? and maybe also the non-visual editor? the reason i ask is that i would like to be able to take snapshots of what i am doing and scan them into a turtorial i am making for my school. i figure enableing printscreen wouldn't be as difficult as having it dump the screen to a file in the root directory... .________________________________________________________________________ __ _ |Alfred Perlstein - Programming & SysAdmin --"Have you seen my FreeBSD tatoo?" |perlsta@sunyit.edu --"who was that masked admin?" |http://www.cs.sunyit.edu/~perlsta : ' From owner-freebsd-hackers Thu Oct 2 09:20:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA06050 for hackers-outgoing; Thu, 2 Oct 1997 09:20:12 -0700 (PDT) Received: from isgate.is (isgate.is [193.4.58.51]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA06031 for ; Thu, 2 Oct 1997 09:20:02 -0700 (PDT) Received: from eh.est.is (eh.est.is [194.144.208.34]) by isgate.is (8.7.5-M/) with ESMTP id QAA05625; Thu, 2 Oct 1997 16:19:54 GMT Received: from didda.est.is (totii@ppp-24.est.is [194.144.208.124]) by eh.est.is (8.8.5/8.8.5) with SMTP id QAA22539; Thu, 2 Oct 1997 16:18:59 GMT Message-ID: <3433C896.41C67EA6@est.is> Date: Thu, 02 Oct 1997 16:19:40 +0000 From: =?iso-8859-1?Q?=DEor=F0ur?= Ivarsson X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2.2-RELEASE i386) MIME-Version: 1.0 To: Wilko Bulte CC: Chuck Robey , FreeBSD-Hackers@FreeBSD.ORG Subject: Re: thickwisre<->thinwire References: <199709261752.TAA01396@yedi.iaf.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Wilko Bulte wrote: > > As Chuck Robey wrote... > > I'm doing a bit of computer re-arrangement (keeps my life interesting) and > > I find I have to connect another computer to my existing home ethernet. > > Trouble is, the ethernet is thinwire, and the new computer (a DECStation > > 5000/120, which will be running NetBSD) is thickwire. I'm going to be > > connecting it to my two existing FreeBSD boxes. > > It probably has an AUI 15 pin D connector. Just find a thinwire tranceiver, > they are quite abundant. Or if you have an AUI-10base5 tranceiver, rewire > it to use a BNC connector. The electronics are the same for 10base2 and > 10base5 (at least they are not distinguishable in normal use) > The specs changes only little and does not care for short cables. The main difference is the velocity factor of Thick Wire is lot higer than Thin Wire cable. The electronic is the same. Thordur Ivarsson Electronic technician thivars@est.is From owner-freebsd-hackers Thu Oct 2 09:54:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA08113 for hackers-outgoing; Thu, 2 Oct 1997 09:54:01 -0700 (PDT) Received: from red.juniper.net (red.juniper.net [208.197.169.254]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA08107; Thu, 2 Oct 1997 09:53:57 -0700 (PDT) Received: from base.juniper.net (base.juniper.net [208.197.169.208]) by red.juniper.net (8.8.5/8.8.5) with ESMTP id JAA24951; Thu, 2 Oct 1997 09:53:26 -0700 (PDT) Received: from base.juniper.net (localhost.juniper.net [127.0.0.1]) by base.juniper.net (8.8.7/8.7.3) with ESMTP id JAA05848; Thu, 2 Oct 1997 09:53:13 -0700 (PDT) Message-Id: <199710021653.JAA05848@base.juniper.net> To: Don Lewis cc: Richard Jones , "Jordan K. Hubbard" , dg@root.com, hackers@FreeBSD.ORG, bugs@FreeBSD.ORG Subject: Re: FreeBSD TCP stack and RST processing [subj changed] In-reply-to: Your message of "Wed, 01 Oct 1997 18:37:36 PDT." <199710020137.SAA16461@salsa.gv.tsc.tdk.com> Date: Thu, 02 Oct 1997 09:53:13 -0700 From: Paul Traina Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk From: Don Lewis Subject: Re: FreeBSD TCP stack and RST processing [subj changed] On Oct 2, 11:09am, Richard Jones wrote: } Subject: Re: FreeBSD TCP stack and RST processing [subj changed] } Paul Traina wrote: } > I put it in there for a reason, Steven's III showed a case where you coul >>d } > pummel the box with a barage of, I believe, syn ack's and basicly melt th >>ings. } > Sorry my memory is so foggy on the issue now. I'll go back and try to } > remember. Steven's III? I don't have that one, since I figured that I already knew how NNTP worked. No, it's actually the most interesting, because it goes into a lot of performance. } Hmm..but if you barrage the system with SYN ACK's when the system is in a } listen state, you shouldn't jump into SYN_RECEIVED should you? Nope. This case is handled earlier: case TCPS_LISTEN: { struct mbuf *am; register struct sockaddr_in *sin; if (tiflags & TH_RST) goto drop; if (tiflags & TH_ACK) goto dropwithreset; if ((tiflags & TH_SYN) == 0) goto drop; Yep, and the bug is that the two got spammed together after I gutted one. From owner-freebsd-hackers Thu Oct 2 11:49:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA14908 for hackers-outgoing; Thu, 2 Oct 1997 11:49:03 -0700 (PDT) Received: from vipunen.hut.fi (root@vipunen.hut.fi [130.233.224.20]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA14903; Thu, 2 Oct 1997 11:48:55 -0700 (PDT) Received: from dol-guldur.hut.fi (will@dol-guldur.hut.fi [130.233.224.39]) by vipunen.hut.fi (8.8.7/8.8.7) with ESMTP id VAA139470; Thu, 2 Oct 1997 21:48:48 +0300 Received: (will@localhost) by dol-guldur.hut.fi (8.8.3/8.6.7) id VAA31187; Thu, 2 Oct 1997 21:48:47 +0300 (EET DST) Date: Thu, 2 Oct 1997 21:48:47 +0300 (EET DST) Message-Id: <199710021848.VAA31187@dol-guldur.hut.fi> From: Ville-Pertti Keinonen To: Stefan Esser Cc: freebsd-hackers@freebsd.org Subject: Re: Conflicting I/O address spaces -- caused by...? In-Reply-To: <19970929084523.37780@mi.uni-koeln.de> References: <199709281110.OAA04780@dol-guldur.hut.fi> <19970929084523.37780@mi.uni-koeln.de> Reply-To: will@iki.fi Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Stefan Esser writes: > You better ask this on a xfree86 list, but I seem to > remember, that the X server *has to* use that port. That's basically the answer I got from there, as well. The question "why?" is still unanswered. > I think your PCI BIOS is at fault. When the PC Thanks. That was the problem, upgrading the BIOS helped. As a bonus, it also provided a new option, MPS version, which could be changed to 1.4, fixing the problem with the IOAPIC interrupt assignments for devices behind the PCI-PCI bridge. Strangely, it didn't change the revision in the floating pointer structure, but provides much more sensible information in the actual table. > (You may want to check bit 18 of the result of > > pciconf -r pci0:14:0 0x3c > > which will read the bridge control and interrupt > pin and line registers. If that bit is a 1, then > ISA MODE is enabled, but I doubt it, you Adaptec It wasn't, as you suspected, but it is now. > Using memory accesses to the Adaptec cards is a > valid fix, though! Wouldn't they still see the I/O ports, as well? > Port addresses in PCI are only present for legacy > device emulations, and for DOS which has no easy > way to access memory mapped registers above 1MB. That doesn't mean they shouldn't be assigned sane, non-conflicting values. ;--) > a fix. Using memory mapped accesses through that > PCI bridge may cause system hangs, but only if one > of several possible scenarios exists on your system. > They cause dead-lock, or even delivery of wrong data, > with a very low probability. It seemed to always hang within less than a minute while accessing a SCSI disk when I had it enabled... Maybe I'll try it again now that everything else seems to be working nicely. From owner-freebsd-hackers Thu Oct 2 12:29:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA17254 for hackers-outgoing; Thu, 2 Oct 1997 12:29:49 -0700 (PDT) Received: from coal.nis.newscorp.com (mxa.newscorp.com [206.15.105.135]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA17126 for ; Thu, 2 Oct 1997 12:28:15 -0700 (PDT) Received: from multivac.narcissus.net (ts2port39.port.net [207.38.248.167]) by coal.nis.newscorp.com (News Corp SMTP GW 1.1) with SMTP id PAA25640 for ; Thu, 2 Oct 1997 15:29:14 -0400 (EDT) Received: from localhost by multivac.narcissus.net (NX5.67e/NX3.0S) id AA00242; Thu, 2 Oct 97 15:23:16 -0400 Date: Thu, 2 Oct 1997 15:23:15 -0400 (GMT-0400) From: Snob Art Genre Reply-To: benedict@echonyc.com To: hackers@freebsd.org Subject: snob art genre seeks instruction, work, coffee Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm interested in working for cheap or free for someone who can give me hands-on experience with networking, system administration, and/or C unix programming. I've administered a FreeBSD box for the convenience and fun of myself and my friends; some of you have used it in various ways when it was up as narcissus.ml.org. Soonish it will be up again as narcissus.net. I've been reading Stevens on Unix programming and networks, McKusick et al on 4.4BSD, Plauger on the standard C library, Cheswick and Bellovin on network security. I'm looking for what I can't get from books. I'm in lower Manhattan. I can telecommute if necessary, but I'd much rather work locally. Ben "You have your mind on computers, it seems." From owner-freebsd-hackers Thu Oct 2 12:58:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA18801 for hackers-outgoing; Thu, 2 Oct 1997 12:58:25 -0700 (PDT) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA18787 for ; Thu, 2 Oct 1997 12:58:17 -0700 (PDT) Received: by iafnl.es.iaf.nl with UUCP id AA17622 (5.67b/IDA-1.5 for FreeBSD-Hackers@FreeBSD.ORG); Thu, 2 Oct 1997 21:58:01 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.5/8.6.12) id TAA00977; Thu, 2 Oct 1997 19:54:02 +0100 (MET) From: Wilko Bulte Message-Id: <199710021854.TAA00977@yedi.iaf.nl> Subject: Re: thickwisre<->thinwire To: totii@est.is (=?iso-8859-1?Q?=DEor=F0ur?= Ivarsson) Date: Thu, 2 Oct 1997 19:54:02 +0100 (MET) Cc: chuckr@Glue.umd.edu, FreeBSD-Hackers@FreeBSD.ORG In-Reply-To: <3433C896.41C67EA6@est.is> from "=?iso-8859-1?Q?=DEor=F0ur?= Ivarsson" at Oct 2, 97 04:19:40 pm X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' 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-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As =?iso-8859-1?Q?=DEor=F0ur?= Ivarsson wrote... > Wilko Bulte wrote: > > > > As Chuck Robey wrote... > > > I'm doing a bit of computer re-arrangement (keeps my life interesting) and > > > I find I have to connect another computer to my existing home ethernet. > > > Trouble is, the ethernet is thinwire, and the new computer (a DECStation > > > 5000/120, which will be running NetBSD) is thickwire. I'm going to be > > > connecting it to my two existing FreeBSD boxes. > > > > It probably has an AUI 15 pin D connector. Just find a thinwire tranceiver, > > they are quite abundant. Or if you have an AUI-10base5 tranceiver, rewire > > it to use a BNC connector. The electronics are the same for 10base2 and > > 10base5 (at least they are not distinguishable in normal use) > > > The specs changes only little and does not care for short cables. > The main difference is the velocity factor of Thick Wire is lot higer > than > Thin Wire cable. The electronic is the same. Not completely. The collision detect uses a diode connection to the central conductor on the thinwire tranceiver, and is directly connected for thickwire (or the other way around, I forgot that detail). This is at least the difference in the NS8392 based implementation I used when I built a couple of tranceivers myself (years ago, when they were rare and $ were few ;-) Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl http://www.tcja.nl/~wilko |/|/ / / /( (_) Arnhem, The Netherlands - Do, or do not. There is no 'try' ----------------------------------------------------------------------Yoda From owner-freebsd-hackers Thu Oct 2 12:58:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA18848 for hackers-outgoing; Thu, 2 Oct 1997 12:58:48 -0700 (PDT) Received: from pandora.hh.kew.com (ahd@kendra.ne.mediaone.net [24.128.53.73]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA18842 for ; Thu, 2 Oct 1997 12:58:44 -0700 (PDT) Received: (from ahd@localhost) by pandora.hh.kew.com (8.8.5/8.8.5) id PAA09937; Thu, 2 Oct 1997 15:58:42 -0400 (EDT) Date: Thu, 2 Oct 1997 15:58:42 -0400 (EDT) From: Drew Derbyshire Message-Id: <199710021958.PAA09937@pandora.hh.kew.com> To: hackers@FreeBSD.ORG, perlsta@cs.sunyit.edu Subject: Re: help with tutorial = printscreen during boot Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > i was wondering it it would be a major undertaking to get the printscreen > key to work while in the visual boot editor? and maybe also the non-visual > editor? > > the reason i ask is that i would like to be able to take snapshots of what > i am doing and scan them into a turtorial i am making for my school. > > i figure enableing printscreen wouldn't be as difficult as having it dump > the screen to a file in the root directory... I would boot in serial console mode with the console actually a terminal emulator such as kermit that supports session and/or screen capture. No programming required ... -- Drew Derbyshire Internet: ahd@kew.com Kendra Electronic Wonderworks Telephone: 781-279-9812 "I speak Spanish to God, Italian to women, French to men, and German to my horse." - Charles V of France From owner-freebsd-hackers Thu Oct 2 13:15:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA20068 for hackers-outgoing; Thu, 2 Oct 1997 13:15:04 -0700 (PDT) Received: from lab321.ru (anonymous1.omsk.net.ru [194.226.32.34]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA20035 for ; Thu, 2 Oct 1997 13:14:34 -0700 (PDT) Received: from lab321.ru (kev.l321.omsk.net.ru [194.226.33.68]) by lab321.ru (8.8.5-MVC-230497/8.8.5) with ESMTP id EAA19399 for ; Fri, 3 Oct 1997 04:21:08 +0600 (OSK) Message-ID: <343400C0.43B8D453@lab321.ru> Date: Fri, 03 Oct 1997 03:14:57 +0700 From: Eugeny Kuzakov Organization: Powered by FreeBSD. X-Mailer: Mozilla 4.03b8 [en] (X11; I; FreeBSD 3.0-970807-SNAP i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: Java ICQ under FreeBSD Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi ! Has anyone siccessfully run java version of ICQ ? -- Best wishes, Eugeny Kuzakov Laboratory 321 ( Omsk, Russia ) http://www.lab321.ru/~kev kev@lab321.ru From owner-freebsd-hackers Thu Oct 2 13:37:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA21257 for hackers-outgoing; Thu, 2 Oct 1997 13:37:59 -0700 (PDT) Received: from bigpuppy.newell.arlington.va.us (bigpuppy.newell.arlington.va.us [209.31.147.242]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA21252 for ; Thu, 2 Oct 1997 13:37:54 -0700 (PDT) Received: from localhost (mnewell@localhost) by bigpuppy.newell.arlington.va.us (8.8.5/8.8.5) with SMTP id QAA04746; Thu, 2 Oct 1997 16:36:31 -0400 (EDT) Date: Thu, 2 Oct 1997 16:36:31 -0400 (EDT) From: Mike Newell To: Wilko Bulte cc: =?iso-8859-1?Q?=DEor=F0ur?= Ivarsson , chuckr@Glue.umd.edu, FreeBSD-Hackers@FreeBSD.ORG Subject: Re: thickwisre<->thinwire In-Reply-To: <199710021854.TAA00977@yedi.iaf.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 2 Oct 1997, Wilko Bulte wrote: wilko> Not completely. The collision detect uses a diode connection to the central wilko> conductor on the thinwire tranceiver, and is directly connected for wilko> thickwire (or the other way around, I forgot that detail). This is at least wilko> the difference in the NS8392 based implementation I used when I built wilko> a couple of tranceivers myself (years ago, when they were rare and $ were wilko> few ;-) For short distances we had good success using an "N" to BNC adaptor (a few bucks in most "real" electronics stores). Just pull the terminator off one end of the thick, screw the adaptor on, twist on the thin, and put the standard BNC type terminator at the end of the thin. Wouldn't recommend it for cables near their max length, but for short ones... Much obliged, Mike +--------------------------------------+------------------------------------+ | Mike Newell | The opinions expressed herein | | Affiliation: | are mine. You can take them or | | Address: | leave them. Flames to /dev/null. | +--------------------------------------+------------------------------------+ | Mike@Newell.arlington.va.us | http://www.newell.arlington.va.us | +--------------------------------------+------------------------------------+ | "Peace. It's wonderful!" Father Divine. | +---------------------------------------------------------------------------+ From owner-freebsd-hackers Thu Oct 2 13:41:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA21487 for hackers-outgoing; Thu, 2 Oct 1997 13:41:25 -0700 (PDT) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA21480 for ; Thu, 2 Oct 1997 13:41:16 -0700 (PDT) Received: from ponds.dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.5/8.8.4) with ESMTP id QAA10402; Thu, 2 Oct 1997 16:41:08 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.8.5) with ESMTP id QAA00483; Thu, 2 Oct 1997 16:43:00 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id QAA14834; Thu, 2 Oct 1997 16:34:20 -0400 (EDT) Date: Thu, 2 Oct 1997 16:34:20 -0400 (EDT) From: Thomas David Rivers Message-Id: <199710022034.QAA14834@lakes.dignus.com> To: freebsd-hackers@freefall.FreeBSD.org, joerg_wunsch@uriah.heep.sax.de, rivers@dignus.com Subject: Re: r-cmds and DNS and /etc/host.conf Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk J"org wrote: > > David, why don't you simply start a caching-only nameserver, redirect > your resolv.conf(s) to it, and look at its debug output? This will > lead you *way quicker* to the solution about what names are being > looked up than any of our guesswork here in the mailinglist. > > A caching-only nameserver is a matter of one minute: > > cd /etc/namedb > sh make-localhost > named -d 2 -b /etc/namedb/named.boot > > FreeBSD ships with a reasonable default named.boot for a caching-only > server (which also has a bunch of comments for what to do to add a > secondary). Ok - Here's what I have in /etc/resolv.conf: domain vnet.net nameserver 127.0.0.1 And, to ensure things are consistent; I rebooted... Then, after the reboot, I did my rlogin - it worked immediately (notice; no nameserver is running on the machine where rlogind is running...) Then, I started named as suggested above; with the command: named -d 2 -b /etc/namedb/named.boot (I had already run the make-localhost script.) Now, my rlogins hang again... Unfortunately, named doesn't report *anything* at all.. Not a single byte... So, I added "options query-log" to the end of named-boot and redid all of this... named still doesn't report anything. Then, I added -q on the named command line (which shouldn't be needed, since options query-log is in named.boot). named still doesn't report anything. So, I changed the debug level from 2 to 10. named still doesn't report anything. As soon as I kill my local named; my rlogin succeeds... (This is the 2.2.1-RELEASE named; perhaps it's been compiled without the flags to report queries???) I also went through the entire exercise with "domain dignus.com" in /etc/resolv.conf - no change. Anyway - here's some of the text from /var/log/messages... it indicates that named was started (several times) and also that something is trying to go out the gateway interface to my ISP (which is down) via natd. My default route is to the external world... Oct 2 15:52:09 ponds named[497]: starting. named 4.9.4-P1 Tue Mar 25 12:43:20 GMT 1997 jkh@time.cdrom.com:/usr/obj/usr/src/usr.sbin/named Oct 2 15:52:09 ponds named[497]: Ready to answer queries. Oct 2 15:52:09 ponds natd: Failed to write packet back. (Network is down) Oct 2 15:52:17 ponds last message repeated 5 times Oct 2 15:52:18 ponds named[497]: dumping nameserver data Oct 2 15:52:18 ponds named[497]: finished dumping nameserver data Oct 2 15:52:19 ponds natd: Failed to write packet back. (Network is down) Oct 2 15:52:26 ponds last message repeated 6 times Any idea why my named isn't producing any debug info? - Dave Rivers - From owner-freebsd-hackers Thu Oct 2 14:07:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA23290 for hackers-outgoing; Thu, 2 Oct 1997 14:07:57 -0700 (PDT) Received: from horst.bfd.com (horst.bfd.com [204.160.242.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA23284 for ; Thu, 2 Oct 1997 14:07:55 -0700 (PDT) Received: from harlie.bfd.com (bastion.bfd.com [204.160.242.14]) by horst.bfd.com (8.8.5/8.7.3) with SMTP id OAA26901; Thu, 2 Oct 1997 14:07:18 -0700 (PDT) Date: Thu, 2 Oct 1997 14:07:18 -0700 (PDT) From: "Eric J. Schwertfeger" To: Eugeny Kuzakov cc: hackers@FreeBSD.ORG Subject: Re: Java ICQ under FreeBSD In-Reply-To: <343400C0.43B8D453@lab321.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 3 Oct 1997, Eugeny Kuzakov wrote: > Has anyone siccessfully run java version > of ICQ ? I wasn't aware that it had been released yet, though I am on their email notification list. From owner-freebsd-hackers Thu Oct 2 14:21:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA24012 for hackers-outgoing; Thu, 2 Oct 1997 14:21:33 -0700 (PDT) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA23995 for ; Thu, 2 Oct 1997 14:21:21 -0700 (PDT) Received: from ponds.dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.5/8.8.4) with ESMTP id RAA16152; Thu, 2 Oct 1997 17:21:00 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.8.5) with ESMTP id RAA00258; Thu, 2 Oct 1997 17:24:50 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id RAA15045; Thu, 2 Oct 1997 17:16:12 -0400 (EDT) Date: Thu, 2 Oct 1997 17:16:12 -0400 (EDT) From: Thomas David Rivers Message-Id: <199710022116.RAA15045@lakes.dignus.com> To: freebsd-hackers@freefall.FreeBSD.org, joerg_wunsch@uriah.heep.sax.de, rivers@dignus.com, tlambert@primenet.com Subject: Re: r-cmds and DNS and /etc/host.conf - *resolved* Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Ok - I just wrote and sent the following... without reading enough of the man page... but - the problem, for me at least, is resolved: See below... ] ] J"org wrote: ] > ] > David, why don't you simply start a caching-only nameserver, redirect ] > your resolv.conf(s) to it, and look at its debug output? This will ] > lead you *way quicker* to the solution about what names are being ] > looked up than any of our guesswork here in the mailinglist. ] > ] > A caching-only nameserver is a matter of one minute: ] > ] > cd /etc/namedb ] > sh make-localhost ] > named -d 2 -b /etc/namedb/named.boot ] > ] > FreeBSD ships with a reasonable default named.boot for a caching-only ] > server (which also has a bunch of comments for what to do to add a ] > secondary). ] ] Ok - ] ] Here's what I have in /etc/resolv.conf: ] ] domain vnet.net ] nameserver 127.0.0.1 ] ] And, to ensure things are consistent; I rebooted... ] ] Then, after the reboot, I did my rlogin - it worked ] immediately (notice; no nameserver is running on the machine ] where rlogind is running...) ] ] Then, I started named as suggested above; with the command: ] ] named -d 2 -b /etc/namedb/named.boot ] ] (I had already run the make-localhost script.) ] ] Now, my rlogins hang again... ] ] Unfortunately, named doesn't report *anything* at all.. Not ] a single byte... ] ] So, I added "options query-log" to the end of named-boot and ] redid all of this... ] ] named still doesn't report anything. ] ] ] Then, I added -q on the named command line (which shouldn't ] be needed, since options query-log is in named.boot). ] ] ] named still doesn't report anything. ] ] ] So, I changed the debug level from 2 to 10. ] ] ] named still doesn't report anything. ] ] ] As soon as I kill my local named; my rlogin succeeds... ] ] (This is the 2.2.1-RELEASE named; perhaps it's been compiled ] without the flags to report queries???) ] ] I also went through the entire exercise with "domain dignus.com" ] in /etc/resolv.conf - no change. ] ] Anyway - here's some of the text from /var/log/messages... it ] indicates that named was started (several times) and also that something ] is trying to go out the gateway interface to my ISP (which is down) via ] natd. My default route is to the external world... ] ] Oct 2 15:52:09 ponds named[497]: starting. named 4.9.4-P1 Tue Mar 25 12:43:20 ] GMT 1997 jkh@time.cdrom.com:/usr/obj/usr/src/usr.sbin/named ] Oct 2 15:52:09 ponds named[497]: Ready to answer queries. ] Oct 2 15:52:09 ponds natd: Failed to write packet back. (Network is down) ] Oct 2 15:52:17 ponds last message repeated 5 times ] Oct 2 15:52:18 ponds named[497]: dumping nameserver data ] Oct 2 15:52:18 ponds named[497]: finished dumping nameserver data ] Oct 2 15:52:19 ponds natd: Failed to write packet back. (Network is down) ] Oct 2 15:52:26 ponds last message repeated 6 times ] ] ] Any idea why my named isn't producing any debug info? ] ] - Dave Rivers - ] Well - reading the man page; I read to the bottom of the named man page to find /var/tmp/named.run. Here's what I see: datagram from [127.0.0.1].1066, fd 7, len 36; now Thu Oct 2 16:59:35 1997 named[349]: XX /127.0.0.1/puddles.dignus.com/A req: nlookup(puddles.dignus.com) id 17714 type=1 class=1 req: missed 'puddles.dignus.com' as '' (cname=0) forw: forw -> [198.41.0.11].53 ds=8 nsid=31064 id=17714 0ms retry 4sec resend(addr=1 n=0) -> [128.9.0.107].53 ds=8 nsid=31063 id=0 0ms resend(addr=1 n=0) -> [128.9.0.107].53 ds=8 nsid=31064 id=17714 0ms Followed by attempts to go higher toward the root to resolve this... So - the question is "what is puddles.dignus.com".... Here's the info: the rlogin machine: lakes.dignus.com 10.0.0.3 # ifconfig ed0 ed0: flags=8843 mtu 1500 inet 10.0.0.3 netmask 0xffffff00 broadcast 10.0.0.255 ether 00:40:33:22:a2:6b the rlogind/gateway machine (where named is running): ponds.dignus.com 10.0.0.1 # ifconfig ed0 ed0: flags=8843 mtu 1500 inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255 ether 66:66:77:00:0b:31 puddles.dignus.com does *not* appear in /etc/hosts on the gateway machine (which explains the search.) *But* - just where is "puddles.dignus.com" coming from? A quick grep in /etc on both of the machines indicates that puddles.dignus.com doesn't exist on "lakes.dignus.com" - but it is found in /etc/hosts.equiv on 'ponds.dignus.com'. Here's /etc/hosts.equiv on the gateway machine (ponds.dignus.com): #localhost #my_very_good_friend.domain localhost ponds ponds.dignus.com puddles puddles.dignus.com rivulet rivulet.dignus.com So - I think, somehow, /etc/hosts.equiv is being examined..., and since ponds.dignus.com isn't in /etc/hosts; the loolup for it is going to the resolver... Would someone care to explain why the hosts in /etc/hosts.equiv are being referenced for an rlogin? Now - fixing that particular problem lead me to another one (perhaps this is what's causing Terry's problem?) My .rhosts file contained many host names that weren't in my /etc/hosts; causing a "punt" to the nameserver. When I fixed up my .rhosts - *poof* - all of my problems disappeared. Thanks for the wonderful suggestion J"org! So, when unwanted resolver references (and timeouts) are occurring, here's my advice: 1) Use J"org's local cacheing nameserver trick to determine what hosts are trying to be looked up. 2) Look around for where that host might be referenced, some likely locations: /etc/hosts.equiv .rhosts .netrc - Dave Rivers - From owner-freebsd-hackers Thu Oct 2 17:00:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA02792 for hackers-outgoing; Thu, 2 Oct 1997 17:00:58 -0700 (PDT) Received: from unix.tfs.net (root@unix.tfs.net [199.79.146.60]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA02785 for ; Thu, 2 Oct 1997 17:00:51 -0700 (PDT) Received: from argus.tfs.net (pm3-p26.tfs.net [206.154.183.218]) by unix.tfs.net (8.8.5/8.8.5) with ESMTP id RAA07783; Thu, 2 Oct 1997 17:58:56 -0500 Received: (from jbryant@localhost) by argus.tfs.net (8.8.7/8.8.5) id TAA03036; Thu, 2 Oct 1997 19:00:41 -0500 (CDT) From: Jim Bryant Message-Id: <199710030000.TAA03036@argus.tfs.net> Subject: Re: thickwire<->thinwire In-Reply-To: from Mike Newell at "Oct 2, 97 04:36:31 pm" To: mnewell@newell.arlington.va.us (Mike Newell) Date: Thu, 2 Oct 1997 19:00:40 -0500 (CDT) Cc: freebsd-hackers@freebsd.org Reply-to: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-Operating-System: FreeBSD 2.2.2-RELEASE #0: Wed Jul 9 01:01:24 CDT 1997 X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply: > On Thu, 2 Oct 1997, Wilko Bulte wrote: > > wilko> Not completely. The collision detect uses a diode connection to the central > wilko> conductor on the thinwire tranceiver, and is directly connected for > wilko> thickwire (or the other way around, I forgot that detail). This is at least > wilko> the difference in the NS8392 based implementation I used when I built > wilko> a couple of tranceivers myself (years ago, when they were rare and $ were > wilko> few ;-) > > For short distances we had good success using an "N" to BNC adaptor (a few > bucks in most "real" electronics stores). Just pull the terminator off > one end of the thick, screw the adaptor on, twist on the thin, and put the > standard BNC type terminator at the end of the thin. Wouldn't recommend > it for cables near their max length, but for short ones... my memory fails me... the wire frequency is 20MHz, correct? the max length is limited by distributed capacitance [assuming a long, random, non-resonant length of transmission line], correct? applying conventional transmission line theory, could you not use longer lengths that are multiples of one wavelength of the base frequency in use? this should apply maximum in-phase signal to the downstream connection. or am i completely misunderstanding ethernet here? i would think that the only problems that would occur through the N<->BNC adaptor would be a small insertion loss [avg for a good connector around 1.05-1.1 dB], and slight increase in SWR. jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ From owner-freebsd-hackers Thu Oct 2 17:41:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA05000 for hackers-outgoing; Thu, 2 Oct 1997 17:41:06 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA04992 for ; Thu, 2 Oct 1997 17:41:04 -0700 (PDT) Received: (qmail 14183 invoked by uid 1000); 3 Oct 1997 00:41:25 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092597 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Date: Thu, 02 Oct 1997 17:41:25 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: freebsd-hackers@freebsd.org Subject: DPT release Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Y'all, I just released the DPT driver, version 1.2.5. It is on ftp://ftp.i-connect.net/crash. The patch is rolled into the very early dlm code and these two really should be separated. Thanx! --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-hackers Thu Oct 2 17:41:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA05055 for hackers-outgoing; Thu, 2 Oct 1997 17:41:15 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA05007 for ; Thu, 2 Oct 1997 17:41:08 -0700 (PDT) Received: (qmail 14176 invoked by uid 1000); 3 Oct 1997 00:41:25 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092597 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 02 Oct 1997 17:41:25 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: "Jamil J. Weatherbee" Subject: RE: Device drivers Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi "Jamil J. Weatherbee"; On 02-Oct-97 you wrote: > > > I've taken a look at the source code to a few device drivers and run the > example scripts for Isa stuff, I have a general feeling of what needs to > be in one and how it operates however I simply don't feel I have enough > information (or a well enough documented example) to feel confident > writing one myself, does anyone have a document/FAQ no matter how small > describng the required functions/tables/probing /irq setup etc. so I > would > know what exactly I am doing. A line by line walk through of even a > cheeseball driver would be greatly appreciated or perhaps even a pointer > to a well documented driver (My standard is to have a comment on every > line of code, that's what I mean by "well documented"), but preferably > not > to lengthy where I am goin to mostly be looking at the nitty gritty of a > device I don't know about or understand. Someone passed me a driver for > a > stepper motor, the idea of what it is doing with the physical hardware > is > easy for me since I deal with that stuff all the time, unfortunately > there > are hardly no comments. Being new to FreeBSD drivers, I can appreciate your desire. Grab the dlm patch from ftp://ftp.i-connect.net/crash. It contains both the DLM (very, very alpha) and the DPT driver. There is also a paid of matching design papers. They are not great but do contain a description of the flow. The DPT driver is actualy two drivers. One is a SCSI Host Bus Adapter, and one is a character decive driver. They are both documented and hopefully readable. For SCSI only, try Justin's ahc driver. --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-hackers Thu Oct 2 17:41:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA05153 for hackers-outgoing; Thu, 2 Oct 1997 17:41:41 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA05042 for ; Thu, 2 Oct 1997 17:41:14 -0700 (PDT) Received: (qmail 14210 invoked by uid 1000); 3 Oct 1997 00:41:26 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092597 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 02 Oct 1997 17:41:26 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Arizona Coyote , freebsd-hackers@freebsd.org Subject: How to be rude, miss the point and feel good about it Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Formal Apology From Simonh Shapiro to The whole iInternet, FreeBSD in particular and one unnamed dessert four legged creature. In an attempt to contribute back to this fine community and project some of the great benefits I personally gained, and my employer has gained, we decided to put the technology of Distributed Lock Manager up for public review, with an eye, once it has stabilized, towards contributing it to the project. I have announced some key features, avialability plans, etc. on the Freebsd-hackers mailing list. I have kept all the replies which had an indication of interest in them. Few days ago, I finally fot the code and documentation to a somewhat presentable manner and decided in my eternal stupidity and ignorance of good manners to create a little mailing list and subscribe to it those who replied with interest. A single mail message went out to those interested parties, announcing what is available. A short message afterwards announced a patch release. Apparently, this is an abhorable abomination and I was severely admonished for my transgression. The range of admonitions was wide. Some simply asked to be removed from the list. Some demanded to know how I got their name and some decided to teach me a lesson and raid the ftp/mail server with junk mail. The message below I like the best. It is polite, to the point and an excellent way to teach someone he/she made an etiquette mistake. If I thought for a moment that this is representative of our little community, I would have thought long and hard about being part of it. BTW, If one of my 6.5 children ever talked to me in that language... So, if any of you is interested in distributed computing rather than vandalism, or in distributed resource allocation than foul language, please drop me a line. If I offended any of you by following up on something YOU expressed written interest in, or if I mistook your interests and intent, I formally and publicly apologize. Simon ======================================================================= Hi Arizona Coyote; On 02-Oct-97 you wrote: > On Wed, 1 Oct 1997, Simon Shapiro wrote: > > > Hi Y'all. > > > > You are on this mailing list because you expressed (even a fleeting) > > interest in this subject. > > Yes, I use FreeBSD. Why does that give you the right to subscribe me to > your fucking SPAM list? > > > To unsubscribe, send an empty e-mail message to: > > > > freebsd-dlm-unsubscribe@primer.i-connect.net > > Why should I have to unsubscribe to a list that i never willingly > subscribed to? > > > This list is dedicated to the review and discussion of Distributed Lock > > Managers. Since our initial implementation is on FreeBSD, it is the > > platform of choice for this discussion, at this time. > > This is starting to sound like fucking SPAM to me. > > > Some ground rules: > > No more fucking SPAM asshole! Get it? Now, --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-hackers Thu Oct 2 21:45:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA16391 for hackers-outgoing; Thu, 2 Oct 1997 21:45:46 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA16386 for ; Thu, 2 Oct 1997 21:45:40 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.5/CET-v2.1) with SMTP id EAA04324 for ; Fri, 3 Oct 1997 04:45:14 GMT Date: Fri, 3 Oct 1997 13:45:14 +0900 (JST) From: Michael Hancock To: FreeBSD Hackers Subject: BIND 8.1 is pretty cool Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I recently installed BIND 8.1 on a machine that only does DNS and it looks pretty good. The /etc/named.conf has a whole bunch of knobs, but you can start off with a simple config and tweak to your hearts delight. It comes with a perl script to convert old named.boot files. Thankfully, the zone files still use the same format. Incorporating the new resolve stuff into apps will take a little investigating. The library source code is particularly impressive, take a look at the eventlib stuff. The abstraction of the IO channels in C is excellent. This can be reused in a variety of network server applications. See http://www.isc.org to get a distribution. On 2.2 just do... make make install Edit /etc/named.conf (See the simple example at www.isc.org) Take a look at ./bin/named.conf for detailed examples. Edit /etc/rc.conf to startup named Regards, Mike From owner-freebsd-hackers Thu Oct 2 22:34:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA18793 for hackers-outgoing; Thu, 2 Oct 1997 22:34:42 -0700 (PDT) Received: from adam.adonai.net (adam.adonai.net [207.8.83.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA18785 for ; Thu, 2 Oct 1997 22:34:39 -0700 (PDT) Received: from localhost (leec@localhost) by adam.adonai.net (8.8.5/8.7.3) with SMTP id AAA28858; Fri, 3 Oct 1997 00:34:29 -0500 (CDT) Date: Fri, 3 Oct 1997 00:34:29 -0500 (CDT) From: "Lee Crites (AEI)" To: Simon Shapiro cc: freebsd-hackers@FreeBSD.ORG Subject: Re: How to be rude, miss the point and feel good about it In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 2 Oct 1997, Simon Shapiro wrote: =>Few days ago, I finally fot the code and documentation to a somewhat =>presentable manner and decided in my eternal stupidity and ignorance of =>good manners to create a little mailing list and subscribe to it those who =>replied with interest. Thanks for the warning. I had thought of doing something sort of similar. There are a few individuals who I have discussed some things with at length, and thought of just tossing a quick majordomo list together with the several of us to make it easier. =>If I thought for a moment that this is representative of our little =>community, I would have thought long and hard about being part of it. I have noticed that while a great majority of the individuals on the FreeBSD lists are *very* nice and helpful, there are a few who can be counted on to regurgitate the kind of malignant sludge you received. =>If I offended any of you by following up on something YOU expressed written =>interest in, or if I mistook your interests and intent, I formally and =>publicly apologize. It would be interesting to forward the original message back to it (the sender) so it could see why you thought it was interested in the first place. Perhaps *it* might learn a lesson in netiquite, which just might save *lots* of people from that kind of grief. I have noticed that small minds have small vocabularies. Which, I think, is why we see that particular *F* word used in so many ways -- when you don't have a large vocabulary, you are stuck using the few words you do know, sometimes in ways which have no real meaning. Lee From owner-freebsd-hackers Thu Oct 2 22:46:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA19651 for hackers-outgoing; Thu, 2 Oct 1997 22:46:59 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id WAA19646 for ; Thu, 2 Oct 1997 22:46:55 -0700 (PDT) Received: (qmail 17944 invoked by uid 1000); 3 Oct 1997 05:47:20 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092597 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 02 Oct 1997 22:47:20 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: "Lee Crites \(AEI\)" Subject: Re: How to be rude, miss the point and feel good about it Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi "Lee Crites (AEI)"; On 03-Oct-97 you wrote: ... Thank you for your kind words. > It would be interesting to forward the original message back to > it (the sender) so it could see why you thought it was interested > in the first place. Perhaps *it* might learn a lesson in > netiquite, which just might save *lots* of people from that kind > of grief. I investigated this (hopefully this is the last we hear about this issue) and found out that it is really my mistake: When collecting names of people who expressed interest in the DLM, I put into that folder, by mistake, a digest of freebsd-questions. Not noticing this mistake, I processed the folder mechanically and ended up with a much larger (by 4 so far :-) list than I intended. I do recognize, however late, the great sensitivity which people have to unsolicited listing. I was strongly repremended, each word deserving. ``The road to hell is paved with good intentions'' - Who am I quoting here? --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-hackers Thu Oct 2 23:04:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA21051 for hackers-outgoing; Thu, 2 Oct 1997 23:04:22 -0700 (PDT) Received: from dog.farm.org (gw-serial2.farm.org [207.111.140.45]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA21046 for ; Thu, 2 Oct 1997 23:04:15 -0700 (PDT) Received: (from dk@localhost) by dog.farm.org (8.7.5/dk#3) id XAA04517; Thu, 2 Oct 1997 23:04:04 -0700 (PDT) Date: Thu, 2 Oct 1997 23:04:04 -0700 (PDT) From: Dmitry Kohmanyuk Message-Id: <199710030604.XAA04517@dog.farm.org> To: jdn@qiv.com (Jay D. Nelson) Cc: freebsd-hackers@freebsd.org Subject: Re: 2nd Notice: 4 days to code freeze in RELENG_2_2 branch. Newsgroups: cs-monolit.gated.lists.freebsd.stable Organization: FARM Computing Association Reply-To: dk+@ua.net X-Newsreader: TIN [version 1.2 PL2] Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article you wrote: > Would it be possible to uncomment the HDB capabilities in UUCP for the > next release? Even though UUCP died years ago, I'm converting more UUCP WHAT?? How else are you supposed to do mail backups with other ISP, but with UUCP over TCP to your primary line? The network I set up in university 2 years ago still works this way, and mail goes in and out even if leased line and/or router died. What about hundreds of customers in xUSSR with non-nailed lines (which are more expensive than dedicated ISDN in the U.S.?) etc. As for UUCP in FreeBSD tree, well, there were some problems reported before, but I beleive they were all fixed. -- "AT&T -- anything better is illegal." -- Keith Lofstrom, comp.unix.bsd, "AT&T sues BSDI" thread From owner-freebsd-hackers Thu Oct 2 23:05:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA21154 for hackers-outgoing; Thu, 2 Oct 1997 23:05:45 -0700 (PDT) Received: from y.dyson.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA21138 for ; Thu, 2 Oct 1997 23:05:20 -0700 (PDT) Received: (from root@localhost) by y.dyson.net (8.8.7/8.8.5) id BAA06750; Fri, 3 Oct 1997 01:00:41 -0500 (EST) From: "John S. Dyson" Message-Id: <199710030600.BAA06750@y.dyson.net> Subject: Re: Sysctl variables In-Reply-To: <199710020620.QAA20756@ogre.dtir.qld.gov.au> from Stephen McKay at "Oct 2, 97 04:20:56 pm" To: syssgm@dtir.qld.gov.au (Stephen McKay) Date: Fri, 3 Oct 1997 01:00:40 -0500 (EST) Cc: pechter@lakewood.com, freebsd-hackers@FreeBSD.ORG, syssgm@dtir.qld.gov.au X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Thursday, 2nd October 1997, Bill Pechter wrote: > > >I'm copying this to -chat because I'm wondering if there's any user interest > >in this except just me... > > > >I'm back working on the SysV init again. I know it's been a long layoff since > >a number of you sent code to me to work on. I've now got a dedicated test > >box and will be working hard on finishing the work that was started by > >a number of folks. > > > >Any chance of getting two varibles in the "official" FreeBSD sysctl MIB base.. > > > >I was thinking of kern.run_level and kern.last_run_level. > >I'd like to avoid homebrew kernel patches to do this (I don't think I want > >to have to continually update the init code after each cvsup upgrade.) > > > I'll sponsor those two variables. I know that there are those who HATE SYSV type init, but there are those who also NEED it. As long as they don't do anything, other than support a consistant interface for those who need the SYSV init, then I don't see why there is a problem. I don't think that we can get into the habit of adding special variables into the kernel sysctl database. Things like SYSV init are special, and as long as I don't get shouted down, I would like to allow and *support* optional use of SYSV init. John From owner-freebsd-hackers Thu Oct 2 23:16:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA21854 for hackers-outgoing; Thu, 2 Oct 1997 23:16:00 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA21842 for ; Thu, 2 Oct 1997 23:15:57 -0700 (PDT) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by Campino.Informatik.RWTH-Aachen.DE (8.8.7/RBI-Z13) with ESMTP id IAA14582; Fri, 3 Oct 1997 08:16:06 +0200 (MET DST) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.8.5/8.6.9) id IAA04570; Fri, 3 Oct 1997 08:23:46 +0200 (MEST) Message-ID: <19971003082346.17295@gil.physik.rwth-aachen.de> Date: Fri, 3 Oct 1997 08:23:46 +0200 From: Christoph Kukulies To: Luigi Rizzo Cc: freebsd-hackers@freebsd.org Subject: Re: netboot.com References: <199710021515.RAA01742@gil.physik.rwth-aachen.de> <199710021711.SAA12765@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199710021711.SAA12765@labinfo.iet.unipi.it>; from Luigi Rizzo on Thu, Oct 02, 1997 at 06:11:00PM +0100 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, Oct 02, 1997 at 06:11:00PM +0100, Luigi Rizzo wrote: > > Anyone using netboot.com recently? > > > > I compiled a version for WD (-DINCLUDE_WD) and want to use it > > with a WD8013. > > I am using it everyday although my code is pretty old (april perhaps ?) > Am having no problems. Do you want a copy of my sources (mostly the > same as -current) Yes. please. But only if you are using a WD80xx card and not a PCI card nor a NE2000 or 3COM. Does the load address play a role? 0x90000 ? > > Cheers > Luigi -- --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Fri Oct 3 00:00:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA25023 for hackers-outgoing; Fri, 3 Oct 1997 00:00:04 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA24967 for ; Thu, 2 Oct 1997 23:59:57 -0700 (PDT) Received: (qmail 18461 invoked by uid 1000); 3 Oct 1997 07:00:22 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092597 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Date: Fri, 03 Oct 1997 00:00:22 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: freebsd-hackers@freebsd.org, freebsd-dlm@primer.i-connect.net Subject: Advice Seeked - Non-Invasive Metrics Techniques Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Y'all, I hope the subject line is accurate. I need to carefully tune and analyze timing and perfromance statistics. Mainly to identify why some rotines in the DLM take so much time. I am looking for ideas on how to measure the behavior of code, take time measurements, count events, etc. without consuming so much time. For example, when measuring time, I have the following strategy: In the dlm_lock_t structure, I have typedef struct dlm_lock } ... struct timeval start_time, stop_time; } dlm_lock_t Then, I have the function: static INLINE void dlm_debug_times(dlm_lock_t *lock, int line) { microtime(&lock->stop_time); printf("So far (%d) %d\n", line, time_delta(lock->start_time, lock->stop_time)); } ... Then, when I want to time sone code I do static int some_function(dlm_lock_t *lock, ...) { ... microtime(&lock->start_time); ... /* Before a certain block of code */ dlm_debug_times(lock, __LINE__); ... /* Some code to be timed */ ... dlm_debug_times(lock, __LINE__); ... } Is there a better way to do that? In this context, better means a way to impact the performance of the system to a lesser degree. I have a sneaking suspicion that the above mechnism takes a lot of time, thus upsetting the code being timed. Any suggestion will be appreciated. Thanx! --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-hackers Fri Oct 3 00:17:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA26289 for hackers-outgoing; Fri, 3 Oct 1997 00:17:25 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA26283 for ; Fri, 3 Oct 1997 00:17:20 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id JAA11808 for ; Fri, 3 Oct 1997 09:17:17 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with UUCP id JAA02890 for freebsd-hackers@FreeBSD.ORG; Fri, 3 Oct 1997 09:17:06 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.7/keltia-2.10/nospam) id JAA06617; Fri, 3 Oct 1997 09:03:21 +0200 (CEST) Message-ID: <19971003090321.13308@keltia.freenix.fr> Date: Fri, 3 Oct 1997 09:03:21 +0200 From: Ollivier Robert To: freebsd-hackers@FreeBSD.ORG Subject: Re: How to be rude, miss the point and feel good about it References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: ; from Lee Crites (AEI) on Fri, Oct 03, 1997 at 12:34:29AM -0500 X-Operating-System: FreeBSD 3.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Lee Crites (AEI): > Thanks for the warning. I had thought of doing something sort of > similar. There are a few individuals who I have discussed some > things with at length, and thought of just tossing a quick > majordomo list together with the several of us to make it easier. The main problem Simon faced is that people are _sick_ of spam (especially UCE). Some received so much of it that the thought they were on a new list did turn them on. I do not condone their attitude and their language but as a Usenet spam canceller and receiver of mail spam, I understand them very well... Just ask before and everything will be well. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #35: Sun Sep 21 19:28:07 CEST 1997 From owner-freebsd-hackers Fri Oct 3 00:28:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA27047 for hackers-outgoing; Fri, 3 Oct 1997 00:28:07 -0700 (PDT) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA27021 for ; Fri, 3 Oct 1997 00:28:03 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.6/8.6.12) with SMTP id AAA04419; Fri, 3 Oct 1997 00:24:10 -0700 (PDT) Message-Id: <199710030724.AAA04419@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol To: Simon Shapiro Cc: freebsd-hackers@freebsd.org, freebsd-dlm@primer.i-connect.net Subject: Re: Advice Seeked - Non-Invasive Metrics Techniques Reply-To: Jason Thorpe From: Jason Thorpe Date: Fri, 03 Oct 1997 00:24:10 -0700 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 03 Oct 1997 00:00:22 -0700 (PDT) Simon Shapiro wrote: > I need to carefully tune and analyze timing and perfromance statistics. > Mainly to identify why some rotines in the DLM take so much time. I guess generic kernel profiling isn't enough, here? Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: +1 408 866 1912 NAS: M/S 258-6 Work: +1 415 604 0935 Moffett Field, CA 94035 Pager: +1 415 428 6939 From owner-freebsd-hackers Fri Oct 3 00:36:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA27673 for hackers-outgoing; Fri, 3 Oct 1997 00:36:22 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA27662 for ; Fri, 3 Oct 1997 00:36:19 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.7/8.8.5) with ESMTP id AAA00425; Fri, 3 Oct 1997 00:36:12 -0700 (PDT) Message-Id: <199710030736.AAA00425@rah.star-gate.com> To: Simon Shapiro cc: "Lee Crites \(AEI\)" , freebsd-hackers@FreeBSD.ORG Subject: Re: How to be rude, miss the point and feel good about it In-reply-to: Your message of "Thu, 02 Oct 1997 22:47:20 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Oct 1997 00:36:12 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Look it was an honest mistake;additionaly, you are trying to contribute to FreeBSD . The crude and rude responses that you received are not characteristic of FreeBSD etiguette. So please don't take to heart and move on with God Speed ! Regards, Amancio >From The Desk Of Simon Shapiro : > > Hi "Lee Crites (AEI)"; On 03-Oct-97 you wrote: > > ... > > Thank you for your kind words. > > > It would be interesting to forward the original message back to > > it (the sender) so it could see why you thought it was interested > > in the first place. Perhaps *it* might learn a lesson in > > netiquite, which just might save *lots* of people from that kind > > of grief. > > I investigated this (hopefully this is the last we hear about this issue) > and found out that it is really my mistake: > > When collecting names of people who expressed interest in the DLM, I put > into that folder, by mistake, a digest of freebsd-questions. Not noticing > this mistake, I processed the folder mechanically and ended up with a much > larger (by 4 so far :-) list than I intended. > > I do recognize, however late, the great sensitivity which people have to > unsolicited listing. I was strongly repremended, each word deserving. > ``The road to hell is paved with good intentions'' - Who am I quoting here? > > --- > > > Sincerely Yours, > > Simon Shapiro Atlas Telecom > Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 > Shimon@i-Connect.Net Voice: 503.799.2313 > From owner-freebsd-hackers Fri Oct 3 00:42:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA28062 for hackers-outgoing; Fri, 3 Oct 1997 00:42:27 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA28056 for ; Fri, 3 Oct 1997 00:42:22 -0700 (PDT) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id RAA00423; Fri, 3 Oct 1997 17:08:02 +0930 (CST) Message-ID: <19971003170802.12051@lemis.com> Date: Fri, 3 Oct 1997 17:08:02 +0930 From: Greg Lehey To: dk+@ua.net Cc: "Jay D. Nelson" , freebsd-hackers@FreeBSD.ORG Subject: Re: 2nd Notice: 4 days to code freeze in RELENG_2_2 branch. References: <199710030604.XAA04517@dog.farm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <199710030604.XAA04517@dog.farm.org>; from Dmitry Kohmanyuk on Thu, Oct 02, 1997 at 11:04:04PM -0700 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, Oct 02, 1997 at 11:04:04PM -0700, Dmitry Kohmanyuk wrote: > In article you wrote: >> Would it be possible to uncomment the HDB capabilities in UUCP for the >> next release? Even though UUCP died years ago, I'm converting more > > UUCP WHAT?? How else are you supposed to do mail backups with > other ISP, but with UUCP over TCP to your primary line? > The network I set up in university 2 years ago still works this way, > and mail goes in and out even if leased line and/or router died. > > What about hundreds of customers in xUSSR with non-nailed lines (which > are more expensive than dedicated ISDN in the U.S.?) etc. > > As for UUCP in FreeBSD tree, well, there were some problems reported > before, but I beleive they were all fixed. I certainly believe that reports of UUCP's death are greatly exaggerated. I'm documenting it in the second edition of "The Complete FreeBSD". That doesn't mean, of course, that I think HDB is the way to go. The Taylor semantics are much easier to handle. Greg From owner-freebsd-hackers Fri Oct 3 00:55:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA28575 for hackers-outgoing; Fri, 3 Oct 1997 00:55:07 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA28562; Fri, 3 Oct 1997 00:54:53 -0700 (PDT) Received: (from jkh@localhost) by time.cdrom.com (8.8.7/8.6.9) id AAA27900; Fri, 3 Oct 1997 00:54:25 -0700 (PDT) Date: Fri, 3 Oct 1997 00:54:25 -0700 (PDT) From: "Jordan K. Hubbard" Message-Id: <199710030754.AAA27900@time.cdrom.com> To: bde@freebsd.org Subject: Ever looked at this page? Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk http://wauug.erols.com/~balsa/linux/cyrix/ Looks like it might be interesting for Cyrix users. Jordan From owner-freebsd-hackers Fri Oct 3 01:55:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA01629 for hackers-outgoing; Fri, 3 Oct 1997 01:55:42 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca14-03.ix.netcom.com [204.32.168.67]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA01571; Fri, 3 Oct 1997 01:54:18 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id BAA13885; Fri, 3 Oct 1997 01:54:11 -0700 (PDT) Date: Fri, 3 Oct 1997 01:54:11 -0700 (PDT) Message-Id: <199710030854.BAA13885@silvia.HIP.Berkeley.EDU> To: jkh@time.cdrom.com CC: bde@FreeBSD.ORG, hackers@FreeBSD.ORG, kato@FreeBSD.ORG In-reply-to: <199710030754.AAA27900@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: Ever looked at this page? From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * http://wauug.erols.com/~balsa/linux/cyrix/ * * Looks like it might be interesting for Cyrix users. Didn't Kato-san already do this stuff a while ago? Satoshi From owner-freebsd-hackers Fri Oct 3 02:41:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA03756 for hackers-outgoing; Fri, 3 Oct 1997 02:41:37 -0700 (PDT) Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.219]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA03739 for ; Fri, 3 Oct 1997 02:41:34 -0700 (PDT) Received: from postbox.india.hp.com (postbox.india.hp.com [15.10.45.1]) by palrel3.hp.com (8.8.5/8.8.5tis) with ESMTP id CAA28596; Fri, 3 Oct 1997 02:40:56 -0700 (PDT) Message-Id: <199710030940.CAA28596@palrel3.hp.com> Received: from localhost by postbox.india.hp.com with ESMTP (1.39.111.2/16.2) id AA021391382; Fri, 3 Oct 1997 15:06:22 +0530 To: Simon Shapiro Cc: freebsd-hackers@freebsd.org, freebsd-dlm@primer.i-connect.net Subject: Re: Advice Seeked - Non-Invasive Metrics Techniques In-Reply-To: Your message of "Fri, 03 Oct 1997 00:00:22 MST." Date: Fri, 03 Oct 1997 15:06:22 +0530 From: A Joseph Koshy Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>> "Simon Shapiro" writes > I need to carefully tune and analyze timing and perfromance statistics. > Mainly to identify why some rotines in the DLM take so much time. One suggestion would be to write `event logs' like this to a memory buffer with periodic flushing to disk file. A userland tool would later reconstruct the sequence of events that occurred in the kernel from the log. Such a tool could also bring out to light "interesting interactions". The process of writing an event log can be made reasonably cheap: writing out some 4 words of memory and a pointer increment. There would be some overhead from the periodic flushing of the log to permanent storage, but for large log size, this overhead could be amortized over many log entries. Take a look at: Sharon E. Perl and Richard L. Sites, "Studies of Windows NT Performance using Dynamic Execution Traces" ftp://ftp.digital.com/pub/DEC/SRC/research-reports/SRC-146.ps.gz for this approach taken to the extreme. Standard kernel profiling gives you statistical information on objects like functions (-p) or basic blocks (-a), but cannot capture timing and latency interactions. Event logs can capture timing/latency issues very well. Koshy From owner-freebsd-hackers Fri Oct 3 03:45:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA06337 for hackers-outgoing; Fri, 3 Oct 1997 03:45:09 -0700 (PDT) Received: from gneiss.eps.nagoya-u.ac.jp (gneiss.eps.nagoya-u.ac.jp [133.6.57.99]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA06303; Fri, 3 Oct 1997 03:44:05 -0700 (PDT) Received: from marble.eps.nagoya-u.ac.jp (localhost [127.0.0.1]) by gneiss.eps.nagoya-u.ac.jp (8.8.7/3.4W4) with ESMTP id TAA05088; Fri, 3 Oct 1997 19:43:45 +0900 (JST) Message-Id: <199710031043.TAA05088@gneiss.eps.nagoya-u.ac.jp> To: asami@cs.berkeley.edu Cc: jkh@time.cdrom.com, bde@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Ever looked at this page? From: KATO Takenori In-Reply-To: Your message of "Fri, 3 Oct 1997 01:54:11 -0700 (PDT)" References: <199710030854.BAA13885@silvia.HIP.Berkeley.EDU> X-Mailer: Mew version 1.70 on Emacs 19.28.1 / Mule 2.3 X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 03 Oct 1997 19:43:45 +0900 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I don't subscribe hackers@freebsd.org, so please CC'ed to me if you consider I should read your follow-ups. > * http://wauug.erols.com/~balsa/linux/cyrix/ > * > * Looks like it might be interesting for Cyrix users. > > Didn't Kato-san already do this stuff a while ago? Yes, I did. But, I would like to know whether FreeBSD can recognize Cyrix 6x86MX cpu. If there is any problem, I will try to fix. Kernel configuration options of FreeBSD (c.f. LINT) and Linux-patch are as follows: FreeBSD Linux ------------------------------------------------------------------ (5x86 options) CPU_BTB_EN (1) N.A. (5) CPU_DISABLE_5X86_LSSER N.A. (5) CPU_FASTER_5X86_FPU N.A. (5) CPU_RSTK_EN (1) N.A. (5) (6x86 option) CPU_CACHE_REASLLY_WORKS N.A. N.A. (2) CONFIG_CYRIX_6X86_NOLOCK N.A. (2) CONFIG_CYRIX_6X86_WTALLOC N.A. (2) CONFIG_CYRIX_6X86_BTB N.A. (2) CONFIG_CYRIX_6X86_BTB_RISKEY N.A. (3) CONFIG_CYRIX_6X86_VSPM N.A. (3) CONFIG_CYRIX_6X86_VSPM_NOTRADPAGE (both 5x86 and 6x86 options) CPU_SUSP_HLT CONFIG_CYRIX_SUSP_HLT CPU_IORT (4) CYRIX_FAST_IO (6) ------------------------------------------------------------------ N.A.: not available. Note: (1) Should not be used because of CPU bug. (2) I consider they should be controled by BIOS. (3) I don't know how to implement these options without problem. (4) Should not used on Cyrix 5x86 box. Default is fasttest (no clock delay). Because of cpu bug, IORT of Cyrix 5x86 should be 0. (5) Linux-patch does not have any problem about these options. (6) Linux-patch modifies IORT only when this option is set. Unsafe! IORT should be 0 if CPU is Cyrix 5x86. If IORT is not 0, system automagically becomes unstable. PS: Linux-patch might recognize IBM BlueLightning CPU as Cyrix 486. (I'm not tested.) Of course, FreeBSD can recoginize it correctly. PPS: There are many CPU related initialization routines in /sys/i386/i386/initcpu.c. If we should add new feature, it is not so difficult. ---- KATO Takenori Dept. Earth Planet. Sci., Nagoya Univ., Nagoya, 464-01, Japan PGP public key: finger kato@eclogite.eps.nagoya-u.ac.jp ------------------- Powered by FreeBSD(98) ------------------- From owner-freebsd-hackers Fri Oct 3 05:14:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA09650 for hackers-outgoing; Fri, 3 Oct 1997 05:14:58 -0700 (PDT) Received: from papagaio.voga.com.br (papagaio.voga.com.br [200.239.39.2]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id FAA09645 for ; Fri, 3 Oct 1997 05:14:52 -0700 (PDT) Received: by papagaio.voga.com.br(Lotus SMTP MTA v1.06 (346.7 3-18-1997)) id 03256525.00433689 ; Fri, 3 Oct 1997 09:14:08 -0300 X-Lotus-FromDomain: VOGA From: "Daniel Sobral" To: freebsd-hackers@freebsd.org Message-ID: <03256525.0042CA69.00@papagaio.voga.com.br> Date: Fri, 3 Oct 1997 09:14:05 -0300 Subject: TCP stack implementation Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is strictly off-topic, as it does not relate in any way to FreeBSD. Anyway, I need help debugging an apparently broken TCP implementation, as I couldn't find the information I need on TCP Illustrated (probably because I really don't know where to look for). If anyone is willing to help me, please contact me at daniel_sobral@voga.com.br. Please, do _not_ send any replies to this message to the list (except to say how I shouldn't have sent this message here, but, hey, I'm desperate). From owner-freebsd-hackers Fri Oct 3 05:40:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA10878 for hackers-outgoing; Fri, 3 Oct 1997 05:40:58 -0700 (PDT) Received: from mail.sat.t.u-tokyo.ac.jp (dryad.sat.t.u-tokyo.ac.jp [133.11.156.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA10862; Fri, 3 Oct 1997 05:40:38 -0700 (PDT) Received: by mail.sat.t.u-tokyo.ac.jp (8.8.6/3.4Wbeta6-SAT1.0) with ESMTP id VAA25488; Fri, 3 Oct 1997 21:39:03 +0900 (JST) To: kato@migmatite.eps.nagoya-u.ac.jp Cc: asami@cs.berkeley.edu, jkh@time.cdrom.com, bde@FreeBSD.ORG, hackers@FreeBSD.ORG Newsgroups: freebsd.hackers Subject: Re: Ever looked at this page? In-Reply-To: Your message of "03 Oct 1997 19:43:45 +0900" <199710031043.TAA05088@gneiss.eps.nagoya-u.ac.jp> References: <199710031043.TAA05088@gneiss.eps.nagoya-u.ac.jp> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19971003213903V.hideyuki@sat.t.u-tokyo.ac.jp> Date: 03 Oct 1997 21:39:03 +0900 From: Hideyuki Suzuki X-Dispatcher: imput version 970918 Lines: 22 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk KATO Takenori writes: > > * http://wauug.erols.com/~balsa/linux/cyrix/ > > * > > * Looks like it might be interesting for Cyrix users. > > > > Didn't Kato-san already do this stuff a while ago? > > Yes, I did. But, I would like to know whether FreeBSD can recognize > Cyrix 6x86MX cpu. If there is any problem, I will try to fix. My 6x86MX box has been working with no problem so far, though without any related config option. If you have to test something, please tell me. (And of course Japanese is welcome.:) The result of dmesg is as follows: FreeBSD 2.2-STABLE #3: Sat Sep 27 12:49:48 JST 1997 hideyuki@raspberry.sat.t.u-tokyo.ac.jp:/usr/src/sys/compile/RASPBERRY CPU: Cyrix 6x86MX (150.34-MHz 686-class CPU) Origin = "CyrixInstead" Id = 0x600 Device ID = 0x0 Stepping=0 Revision=0 -- Hideyuki Suzuki Department of Mathematical Engineering, University of Tokyo From owner-freebsd-hackers Fri Oct 3 05:53:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA11394 for hackers-outgoing; Fri, 3 Oct 1997 05:53:20 -0700 (PDT) Received: from gneiss.eps.nagoya-u.ac.jp (gneiss.eps.nagoya-u.ac.jp [133.6.57.99]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA11388 for ; Fri, 3 Oct 1997 05:53:17 -0700 (PDT) Received: from marble.eps.nagoya-u.ac.jp (localhost [127.0.0.1]) by gneiss.eps.nagoya-u.ac.jp (8.8.7/3.4W4) with ESMTP id VAA05369; Fri, 3 Oct 1997 21:53:06 +0900 (JST) Message-Id: <199710031253.VAA05369@gneiss.eps.nagoya-u.ac.jp> To: hideyuki@sat.t.u-tokyo.ac.jp Cc: hackers@FreeBSD.ORG, kato@migmatite.eps.nagoya-u.ac.jp Newsgroups: freebsd.hackers Subject: Re: Ever looked at this page? From: KATO Takenori In-Reply-To: Your message of "03 Oct 1997 21:39:03 +0900" References: <19971003213903V.hideyuki@sat.t.u-tokyo.ac.jp> X-Mailer: Mew version 1.70 on Emacs 19.28.1 / Mule 2.3 X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 03 Oct 1997 21:53:05 +0900 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >CPU: Cyrix 6x86MX (150.34-MHz 686-class CPU) > Origin = "CyrixInstead" Id = 0x600 Device ID = 0x0 Stepping=0 Revision=0 Thanks!!!!!!! This is just what I want to know. I now find a problem; device ID is wrong :-(. ---- KATO Takenori Dept. Earth Planet. Sci., Nagoya Univ., Nagoya, 464-01, Japan PGP public key: finger kato@eclogite.eps.nagoya-u.ac.jp ------------------- Powered by FreeBSD(98) ------------------- From owner-freebsd-hackers Fri Oct 3 06:31:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA13404 for hackers-outgoing; Fri, 3 Oct 1997 06:31:09 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id GAA13398 for ; Fri, 3 Oct 1997 06:31:06 -0700 (PDT) Received: from x14.mi.uni-koeln.de ([134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA28424 (5.67b/IDA-1.5 for ); Fri, 3 Oct 1997 15:31:02 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.7/8.6.9) id KAA01014; Fri, 3 Oct 1997 10:49:48 +0200 (CEST) X-Face: " Date: Fri, 3 Oct 1997 10:49:48 +0200 From: Stefan Esser To: will@iki.fi Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Conflicting I/O address spaces -- caused by...? References: <199709281110.OAA04780@dol-guldur.hut.fi> <19970929084523.37780@mi.uni-koeln.de> <199710021848.VAA31187@dol-guldur.hut.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199710021848.VAA31187@dol-guldur.hut.fi>; from Ville-Pertti Keinonen on Thu, Oct 02, 1997 at 09:48:47PM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 1997-10-02 21:48 +0300, Ville-Pertti Keinonen wrote: > > I think your PCI BIOS is at fault. When the PC > > Thanks. That was the problem, upgrading the BIOS helped. As a bonus, Good! > > Using memory accesses to the Adaptec cards is a > > valid fix, though! > > Wouldn't they still see the I/O ports, as well? You can clear the LSB of the command register (the config space register at offset 0x04) to prevent the decoding of port accesses by some device ... > > Port addresses in PCI are only present for legacy > > device emulations, and for DOS which has no easy > > way to access memory mapped registers above 1MB. > > That doesn't mean they shouldn't be assigned sane, > non-conflicting values. ;--) Sure! > > a fix. Using memory mapped accesses through that > > PCI bridge may cause system hangs, but only if one > > of several possible scenarios exists on your system. > > They cause dead-lock, or even delivery of wrong data, > > with a very low probability. > > It seemed to always hang within less than a minute while accessing a > SCSI disk when I had it enabled... This was with the old PCI BIOS ? Since accesses to the S3 card will no longer be seen by the Adaptec, now that it got reasonable port addresses, it should work a lot better now :) Regards, STefan From owner-freebsd-hackers Fri Oct 3 06:40:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA13955 for hackers-outgoing; Fri, 3 Oct 1997 06:40:12 -0700 (PDT) Received: from isgate.is (isgate.is [193.4.58.51]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA13927 for ; Fri, 3 Oct 1997 06:40:01 -0700 (PDT) Received: from eh.est.is (eh.est.is [194.144.208.34]) by isgate.is (8.7.5-M/) with ESMTP id NAA06671; Fri, 3 Oct 1997 13:28:26 GMT Received: from didda.est.is (totii@ppp-24.est.is [194.144.208.124]) by eh.est.is (8.8.5/8.8.5) with SMTP id NAA15984; Fri, 3 Oct 1997 13:27:33 GMT Message-ID: <3434F2EF.41C67EA6@est.is> Date: Fri, 03 Oct 1997 13:28:15 +0000 From: =?iso-8859-1?Q?=DEor=F0ur?= Ivarsson X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2.2-RELEASE i386) MIME-Version: 1.0 To: jbryant@tfs.net CC: Mike Newell , freebsd-hackers@FreeBSD.ORG Subject: Re: thickwire<->thinwire References: <199710030000.TAA03036@argus.tfs.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jim Bryant wrote: > > In reply: > > On Thu, 2 Oct 1997, Wilko Bulte wrote: > > > > wilko> Not completely. The collision detect uses a diode connection to the central > > wilko> conductor on the thinwire tranceiver, and is directly connected for > > wilko> thickwire (or the other way around, I forgot that detail). This is at least > > wilko> the difference in the NS8392 based implementation I used when I built > > wilko> a couple of tranceivers myself (years ago, when they were rare and $ were > > wilko> few ;-) > > > > For short distances we had good success using an "N" to BNC adaptor (a few > > bucks in most "real" electronics stores). Just pull the terminator off > > one end of the thick, screw the adaptor on, twist on the thin, and put the > > standard BNC type terminator at the end of the thin. Wouldn't recommend > > it for cables near their max length, but for short ones... > > my memory fails me... the wire frequency is 20MHz, correct? > > the max length is limited by distributed capacitance [assuming a long, > random, non-resonant length of transmission line], correct? > > applying conventional transmission line theory, could you not use > longer lengths that are multiples of one wavelength of the base > frequency in use? this should apply maximum in-phase signal to the > downstream connection. > > or am i completely misunderstanding ethernet here? > > i would think that the only problems that would occur through the > N<->BNC adaptor would be a small insertion loss [avg for a good > connector around 1.05-1.1 dB], and slight increase in SWR. > I was told by network specialist and engineer at Novell that the time factor is the ruling factor of the length of cable. Rules was as following 1. Velocity factor (Size and dielectric of cable) 2. Number of clients (changes the SWR) 3. SWR of cable (damages cables, connectors, terminators) 4. External interference (Improper earthed computer) You might have seen cards from "Western Digital" that support extra long thin wire cables, just move jumper. Company here in Iceland had very long thin ethernet cable and lot of those cards but when we rushed in and put up our new computer with NE2000 from Novell nothing seemd to work. Thordur Ivarsson thivars@est.is From owner-freebsd-hackers Fri Oct 3 06:56:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA14800 for hackers-outgoing; Fri, 3 Oct 1997 06:56:03 -0700 (PDT) Received: from shell.monmouth.com (root@shell.monmouth.com [205.164.220.9]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA14750 for ; Fri, 3 Oct 1997 06:56:00 -0700 (PDT) Received: from i4got.lakewood.com (fh-ppp38.monmouth.com [205.164.221.70]) by shell.monmouth.com (8.8.5/8.7.3) with ESMTP id JAA05736; Fri, 3 Oct 1997 09:51:26 -0400 (EDT) Received: (from pechter@localhost) by i4got.lakewood.com id JAA04901 (8.8.5/IDA-1.6); Fri, 3 Oct 1997 09:54:59 -0400 (EDT) From: Bill Pechter Message-ID: <199710031354.JAA04901@i4got.lakewood.com> Subject: UUCP In-Reply-To: <199710030604.XAA04517@dog.farm.org> from Dmitry Kohmanyuk at "Oct 2, 97 11:04:04 pm" To: dk+@ua.net Date: Fri, 3 Oct 1997 09:54:59 -0400 (EDT) Cc: freebsd-hackers@freebsd.org Reply-to: pechter@lakewood.com X-Phone-Number: 908-389-3592 X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > In article you wrote: > > Would it be possible to uncomment the HDB capabilities in UUCP for the > > next release? Even though UUCP died years ago, I'm converting more > > UUCP WHAT?? How else are you supposed to do mail backups with > other ISP, but with UUCP over TCP to your primary line? > The network I set up in university 2 years ago still works this way, > and mail goes in and out even if leased line and/or router died. > > What about hundreds of customers in xUSSR with non-nailed lines (which > are more expensive than dedicated ISDN in the U.S.?) etc. > > As for UUCP in FreeBSD tree, well, there were some problems reported > before, but I beleive they were all fixed. > I still think that FreeBSD should adopt the position of supporting HDB V2 uucp configuration files in the system. (I have to rebuild uucp after all the make worlds with my own patches to do so...) If it's a "lets not do any SysVish stuff" we should be using the 4.3BSD logging and directory structure with the V2 config files 8-) Bill ------------------------------------------------------------------------------ Bill Pechter | 17 Meredith Drive Tinton Falls, NJ 07724 | 908-389-3592 pechter@lakewood.com | Save computing history, give an old geek old hardware. This msg brought to you by the letters PDP and the number 11. From owner-freebsd-hackers Fri Oct 3 07:39:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA17983 for hackers-outgoing; Fri, 3 Oct 1997 07:39:33 -0700 (PDT) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA17968 for ; Fri, 3 Oct 1997 07:39:28 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id AAA00858; Sat, 4 Oct 1997 00:00:45 +0930 (CST) Message-Id: <199710031430.AAA00858@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: pechter@lakewood.com cc: dk+@ua.net, freebsd-hackers@FreeBSD.ORG Subject: Re: UUCP (important clarification) In-reply-to: Your message of "Fri, 03 Oct 1997 09:54:59 -0400." <199710031354.JAA04901@i4got.lakewood.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 04 Oct 1997 00:00:44 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I still think that FreeBSD should adopt the position of supporting HDB > V2 uucp configuration files in the system. (I have to rebuild uucp > after all the make worlds with my own patches to do so...) You are not helping yourself by not being clear. You do not mean "the Taylor configuration format should be abandoned in favour of the HDB and V2 formats", you mean "the UUCP suite should be built with support for the Taylor, HDB and V2 configuration formats". ie. HAVE_HDB_CONFIG and HAVE_V2_CONFIG should be set to 1 in /usr/src/ gnu/libexec/uucp/common_source/policy.h. This wouldn't cost anything functionality-wise, and would make Bill happy. Can we achieve enough consensus on this to make it into 2.2.5? mike From owner-freebsd-hackers Fri Oct 3 08:14:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA20108 for hackers-outgoing; Fri, 3 Oct 1997 08:14:34 -0700 (PDT) Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA20103 for ; Fri, 3 Oct 1997 08:14:31 -0700 (PDT) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id KAA04234; Fri, 3 Oct 1997 10:13:50 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id KAA21947; Fri, 3 Oct 1997 10:13:19 -0500 Message-ID: <19971003101318.32875@right.PCS> Date: Fri, 3 Oct 1997 10:13:18 -0500 From: Jonathan Lemon To: Simon Shapiro Cc: "Lee Crites (AEI)" , freebsd-hackers@FreeBSD.ORG Subject: Re: How to be rude, miss the point and feel good about it References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: ; from Simon Shapiro on Oct 10, 1997 at 10:47:20PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Oct 10, 1997 at 10:47:20PM -0700, Simon Shapiro wrote: > ``The road to hell is paved with good intentions'' - Who am I quoting here? Karl Marx, I believe. -- Jonathan From owner-freebsd-hackers Fri Oct 3 08:33:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA21413 for hackers-outgoing; Fri, 3 Oct 1997 08:33:08 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA21406 for ; Fri, 3 Oct 1997 08:33:03 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id IAA15852 for ; Fri, 3 Oct 1997 08:32:55 -0700 (PDT) Date: Fri, 3 Oct 1997 08:32:54 -0700 (PDT) From: Jaye Mathisen To: hackers@freebsd.org Subject: Qmail vs Sendmail? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Anybody care to share their comments? I need a simple high volume mail server, supporting POP and smtp, and delivery to procmail for final delivery. I'm familiar with sendmail, and it works just fine, but I wasn't real thrilled with throughput, even on relatively high-end PC hardware. I have no experience with qmail, but the docs make it look interesting. If anybody's willing to share their views, I'd appreciate it. From owner-freebsd-hackers Fri Oct 3 10:28:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA29211 for hackers-outgoing; Fri, 3 Oct 1997 10:28:24 -0700 (PDT) Received: from konig.elte.hu (konig.elte.hu [157.181.6.22]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA29165 for ; Fri, 3 Oct 1997 10:28:00 -0700 (PDT) Received: from neumann.cs.elte.hu (neumann [157.181.6.200]) by konig.elte.hu (8.8.3/8.7.3/7s) with ESMTP id TAA08521 for ; Fri, 3 Oct 1997 19:11:23 +0200 Received: from localhost (sebesty@localhost) by neumann.cs.elte.hu (8.8.3/8.7.3/4c) with SMTP id TAA06052 for ; Fri, 3 Oct 1997 19:11:38 +0200 X-Authentication-Warning: neumann.cs.elte.hu: sebesty owned process doing -bs Date: Fri, 3 Oct 1997 19:11:38 +0200 (MET DST) From: Zoltan Sebestyen To: FreeBSD hackers mailinglist Subject: cpu/memory monitoring Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I'd like to know if there's any other any other program than top, which monitors the REAL cpu and memory load, but have more simple source code. ------------------------------------------------------------------------------- Sebestyen Zoltan It all seems so stupid, it makes me want to give up. szoli@caesar.elte.hu But why should I give up, when it all seems so stupid? From owner-freebsd-hackers Fri Oct 3 10:42:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA00221 for hackers-outgoing; Fri, 3 Oct 1997 10:42:23 -0700 (PDT) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA00212 for ; Fri, 3 Oct 1997 10:42:12 -0700 (PDT) Received: from ponds.dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.5/8.8.4) with ESMTP id NAA15043; Fri, 3 Oct 1997 13:42:02 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.8.5) with ESMTP id NAA11319; Fri, 3 Oct 1997 13:57:04 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id NAA16721; Fri, 3 Oct 1997 13:47:58 -0400 (EDT) Date: Fri, 3 Oct 1997 13:47:58 -0400 (EDT) From: Thomas David Rivers Message-Id: <199710031747.NAA16721@lakes.dignus.com> To: freebsd-hackers@freefall.FreeBSD.org, pechter@lakewood.com Subject: Re: UUCP Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bill Pechter wrote: > > In article you wrote: > > > Would it be possible to uncomment the HDB capabilities in UUCP for the > > > next release? Even though UUCP died years ago, I'm converting more > > > > UUCP WHAT?? How else are you supposed to do mail backups with > > other ISP, but with UUCP over TCP to your primary line? > > The network I set up in university 2 years ago still works this way, > > and mail goes in and out even if leased line and/or router died. > > > > What about hundreds of customers in xUSSR with non-nailed lines (which > > are more expensive than dedicated ISDN in the U.S.?) etc. > > > > As for UUCP in FreeBSD tree, well, there were some problems reported > > before, but I beleive they were all fixed. > > > > I still think that FreeBSD should adopt the position of supporting HDB > V2 uucp configuration files in the system. (I have to rebuild uucp > after all the make worlds with my own patches to do so...) > > If it's a "lets not do any SysVish stuff" we should be using the 4.3BSD > logging and directory structure with the V2 config files 8-) > > Bill > Back in the "days of yore" - I made exactly the same suggestion. As you noted; after every upgrade I rebuild UUCP to accept my HDB setup... The reasons for using HDB back then were: 1) Reasonably documented in the O'Reilly book. 2) The "uutraf" program understood the HDB log files. 3) I had always done so, since I suffered the pain of converting to HDB.. But, at that time; I was the only person to make the suggestion, so it was decided to leave things alone (the Taylor configs do have some nice options, so there is a good argument to convert.) Since then, there's a new release of the O'Reilly UUCP book that covers Taylor UUCP, there's also a new version of "uutraf" that reads Taylor log files... so reasons #1, and #2 have gone by the wayside. But; being comfortable, I would like to give reason #3 an unduly amount of weight and suggest it again. The config file can by taylored (no pun intended) to accept all three styles; but I would be happy with just HDB and Taylor styles... The problem is the logging style, I believe you can only have one of those. [I prefer the HDB logging style because of reason #3 :-) ] - Dave Rivers - From owner-freebsd-hackers Fri Oct 3 11:03:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA01875 for hackers-outgoing; Fri, 3 Oct 1997 11:03:40 -0700 (PDT) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA01869 for ; Fri, 3 Oct 1997 11:03:30 -0700 (PDT) Received: from ponds.dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.5/8.8.4) with ESMTP id OAA18176; Fri, 3 Oct 1997 14:02:16 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.8.5) with ESMTP id OAA11356; Fri, 3 Oct 1997 14:17:19 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id OAA16774; Fri, 3 Oct 1997 14:08:12 -0400 (EDT) Date: Fri, 3 Oct 1997 14:08:12 -0400 (EDT) From: Thomas David Rivers Message-Id: <199710031808.OAA16774@lakes.dignus.com> To: nate@mt.sri.com, phk@critter.freebsd.dk Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) Cc: gram@cdsec.com, hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > In message <199709181912.NAA13699@rocky.mt.sri.com>, Nate Williams writes: > > >[ 'hangs' in malloc due to memory over-write causing circular lists ] > > > >> >> This is about the only way you could get it to loop I think. That means > >> >> that somebody wrote to memory malloc hadn't passed them (ie: your code). > >> > > >> >Yikes, this would be 'Hard to Do', even by design (ie; self-modifying > >> >code). But, stranger things have happened, especially with dealing with > >> >malloc/free. > >> > >> No, all you have to do is to make each allocation have it's own set of > >> pages, munmap them when free is called and never use those pages again. > >> > >> You run out of address space really fast, and it is slow, but it works. > > > >It's slow, but how would it cause malloc to hang? > > It wouldn't, it would detect accesses to free'ed memory. > Sorry to reply so late for this - I'm just now getting to it... Anyway; such a package already exists, and runs on FreeBSD. It's called Electric Fence. I'd be happy to send anyone the information & source... - Dave Rivers - From owner-freebsd-hackers Fri Oct 3 11:12:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA02395 for hackers-outgoing; Fri, 3 Oct 1997 11:12:09 -0700 (PDT) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA02341; Fri, 3 Oct 1997 11:11:38 -0700 (PDT) Received: from ponds.dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.5/8.8.4) with ESMTP id OAA19557; Fri, 3 Oct 1997 14:11:21 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.8.5) with ESMTP id OAA11377; Fri, 3 Oct 1997 14:26:24 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id OAA16814; Fri, 3 Oct 1997 14:17:17 -0400 (EDT) Date: Fri, 3 Oct 1997 14:17:17 -0400 (EDT) From: Thomas David Rivers Message-Id: <199710031817.OAA16814@lakes.dignus.com> To: jkh@time.cdrom.com, phk@critter.freebsd.dk Subject: Electric Fence info (was Re: Bug in malloc/free (was: Memory leak in getservbyXXX?)) Cc: freebsd-bugs@FreeBSD.ORG, gram@cdsec.com, hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > This would indicate a bug of the class where memory is written to after > > being free()'ed, a kind of bug which phkmalloc makes no attempt to catch. > > Man, I sure wish there was a copy of purify available for FreeBSD. > It's great at catching stuff like this! :( > > Maybe you could hack free() to do an mprotect(addr, len, PROT_NONE) on > free'd pages, unprotecting them again as necessary when the malloc > routines themselves need to frob that memory. Or, since we're just > testing, do it from an internally registered SIGBUS handler which > figures out the right thing to do. :-) > > BTW, how *do* you get the faulting memory location from a SIGBUS > handler? I was just playing around with this a bit and noted that it > wasn't immediately obvious how you'd get that info from the signal > handler. > > Jordan Ok - there seems to be enough interest... Here's the man page for electric fence (which does the mprotect() trick Jordan mentions): I can make the source available to anyone who wants it. - Dave Rivers - efence(3) efence(3) NAME efence - Electric Fence Malloc Debugger SYNOPSIS #include void * malloc (size_t size); void free (void *ptr); void * realloc (void *ptr, size_t size); void * calloc (size_t nelem, size_t elsize); void * memalign (size_t alignment, size_t size); void * valloc (size_t size); extern int EF_ALIGNMENT; extern int EF_PROTECT_BELOW; extern int EF_PROTECT_FREE; DESCRIPTION Electric Fence helps you detect two common programming bugs: software that overruns the boundaries of a malloc() memory allocation, and software that touches a memory allocation that has been released by free(). Unlike other malloc() debuggers, Electric Fence will detect read accesses as well as writes, and it will pinpoint the exact instruction that causes an error. It has been in use at Pixar since 1987, and at many other sites for years. Electric Fence uses the virtual memory hardware of your computer to place an inaccessible memory page immediately after (or before, at the user's option) each memory allo- cation. When software reads or writes this inaccessible page, the hardware issues a segmentation fault, stopping the program at the offending instruction. It is then triv- ial to find the erroneous statement using your favorite debugger. In a similar manner, memory that has been released by free() is made inaccessible, and any code that touches it will get a segmentation fault. Simply linking your application with libefence.a will allow you to detect most, but not all, malloc buffer over- runs and accesses of free memory. If you want to be rea- sonably sure that you've found all bugs of this type, you'll have to read and understand the rest of this man page. USAGE Link your program with the library libefence.a . Make 27-April-1993 1 efence(3) efence(3) sure you are not linking with -lmalloc, -lmallocdebug, or with other malloc-debugger or malloc-enhancer libraries. You can only use one at a time. If your system adminis- trator has installed Electric Fence for public use, you'll be able to use the -lefence argument to the linker, other- wise you'll have to put the path-name for libefence.a in the linker's command line. Some systems will require spe- cial arguments to the linker to assure that you are using the Electric Fence malloc() and not the one from your C library. On AIX systems, you may have to use the flags -bnso -bnodelcsect -bI:/lib/syscalls.exp On Sun systems running SunOS 4.X, you'll probably have to use -Bstatic. Run your program using a debugger. It's easier to work this way than to create a core file and post-mortem debug it. Electric Fence can create huge core files, and some operating systems will thus take minutes simply to dump core! Some operating systems will not create usable core files from programs that are linked with Electric Fence. If your program has one of the errors detected by Electric Fence, it will get a segmentation fault (SIGSEGV) at the offending instruction. Use the debugger to locate the erroneous statement, and repair it. GLOBAL AND ENVIRONMENT VARIABLES Electric Fence has four configuration switches that can be enabled via the shell environment, or by setting the value of global integer variables using a debugger. These switches change what bugs Electric Fence will detect, so it's important that you know how to use them. EF_ALIGNMENT This is an integer that specifies the alignment for any memory allocations that will be returned by malloc(), calloc(), and realloc(). The value is specified in bytes, thus a value of 4 will cause memory to be aligned to 32-bit boundaries unless your system doesn't have a 8-bit characters. EF_ALIGNMENT is set to sizeof(int) by default, since that is generally the word-size of your CPU. If your program requires that allocations be aligned to 64-bit boundaries and you have a 32-bit int you'll have to set this value to 8. This is the case when compiling with the -mips2 flag on MIPS- based systems such as those from SGI. The memory allocation that is returned by Electric Fence mal- loc() is aligned using the value in EF_ALIGNMENT, and its size the multiple of that value that is greater than or equal to the requested size. For this reason, you will sometimes want to set EF_ALIGNMENT to 0 (no alignment), so that you can detect overruns of less than your CPU's word size. Be sure to read the section WORD-ALIGNMENT AND 27-April-1993 2 efence(3) efence(3) OVERRUN DETECTION in this manual page before you try this. To change this value, set EF_ALIGNMENT in the shell environment to an integer value, or assign to the global integer variable EF_ALIGNMENT using a debugger. EF_PROTECT_BELOW Electric Fence usually places an inaccessible page immediately after each memory allocation, so that software that runs past the end of the allocation will be detected. Setting EF_PROTECT_BELOW to 1 causes Electric Fence to place the inaccessible page before the allocation in the address space, so that under-runs will be detected instead of over- runs. When EF_PROTECT_BELOW is set, the EF_ALIGN- MENT parameter is ignored. All allocations will be aligned to virtual-memory-page boundaries, and their size will be the exact size that was requested. To change this value, set EF_PRO- TECT_BELOW in the shell environment to an integer value, or assign to the global integer variable EF_PROTECT_BELOW using a debugger. EF_PROTECT_FREE Electric Fence usually returns free memory to a pool from which it may be re-allocated. If you sus- pect that a program may be touching free memory, set EF_PROTECT_FREE to 1. This will cause Electric Fence to never re-allocate memory once it has been freed, so that any access to free memory will be detected. Some programs will use tremendous amounts of memory when this parameter is set. To change this value, set EF_PROTECT_FREE in the shell envi- ronment to an integer value, or assign to the global integer variable EF_PROTECT_FREE using a debugger. EF_ALLOW_MALLOC_0 By default, Electric Fence traps calls to malloc() with a size of zero, because they are often the result of a software bug. If EF_ALLOW_MALLOC_0 is non-zero, the software will not trap calls to mal- loc() with a size of zero. To change this value, set EF_ALLOC_MALLOC_0 in the shell environment to an integer value, or assign to the global integer variable EF_ALLOC_MALLOC_0 using a debugger. WORD-ALIGNMENT AND OVERRUN DETECTION There is a conflict between the alignment restrictions that malloc() operates under and the debugging strategy used by Electric Fence. When detecting overruns, Electric Fence malloc() allocates two or more virtual memory pages for each allocation. The last page is made inaccessible in such a way that any read, write, or execute access will 27-April-1993 3 efence(3) efence(3) cause a segmentation fault. Then, Electric Fence malloc() will return an address such that the first byte after the end of the allocation is on the inaccessible page. Thus, any overrun of the allocation will cause a segmentation fault. It follows that the address returned by malloc() is the address of the inaccessible page minus the size of the memory allocation. Unfortunately, malloc() is required to return word-aligned allocations, since many CPUs can only access a word when its address is aligned. The conflict happens when software makes a memory allocation using a size that is not a multiple of the word size, and expects to do word accesses to that allocation. The location of the inaccessible page is fixed by hardware at a word- aligned address. If Electric Fence malloc() is to return an aligned address, it must increase the size of the allo- cation to a multiple of the word size. In addition, the functions memalign() and valloc() must honor explicit specifications on the alignment of the memory allocation, and this, as well can only be implemented by increasing the size of the allocation. Thus, there will be situa- tions in which the end of a memory allocation contains some padding space, and accesses of that padding space will not be detected, even if they are overruns. Electric Fence provides the variable EF_ALIGNMENT so that the user can control the default alignment used by mal- loc(), calloc(), and realloc(). To debug overruns as small as a single byte, you can set EF_ALIGNMENT to zero. This will result in Electric Fence malloc() returning unaligned addresses for allocations with sizes that are not a multiple of the word size. This is not a problem in most cases, because compilers must pad the size of objects so that alignment restrictions are honored when storing those objects in arrays. The problem surfaces when soft- ware allocates odd-sized buffers for objects that must be word-aligned. One case of this is software that allocates a buffer to contain a structure and a string, and the string has an odd size (this example was in a popular TIFF library). If word references are made to un-aligned buffers, you will see a bus error (SIGBUS) instead of a segmentation fault. The only way to fix this is to re- write the offending code to make byte references or not make odd-sized allocations, or to set EF_ALIGNMENT to the word size. Another example of software incompatible with EF_ALIGNMENT < word-size is the strcmp() function and other string functions on SunOS (and probably Solaris), which make word-sized accesses to character strings, and may attempt to access up to three bytes beyond the end of a string. These result in a segmentation fault (SIGSEGV). The only way around this is to use versions of the string functions 27-April-1993 4 efence(3) efence(3) that perform byte references instead of word references. INSTRUCTIONS FOR DEBUGGING YOUR PROGRAM 1. Link with libefence.a as explained above. 2. Run your program in a debugger and fix any overruns or accesses to free memory. 3. Quit the debugger. 4. Set EF_PROTECT_BELOW = 1 in the shell environment. 5. Repeat step 2, this time repairing underruns if they occur. 6. Quit the debugger. 7. Read the restrictions in the section on WORD-ALIGN- MENT AND OVERRUN DETECTION. See if you can set EF_ALIGNMENT to 0 and repeat step 2. Sometimes this will be too much work, or there will be problems with library routines for which you don't have the source, that will prevent you from doing this. MEMORY USAGE AND EXECUTION SPEED Since Electric Fence uses at least two virtual memory pages for each of its allocations, it's a terrible memory hog. I've sometimes found it necessary to add a swap file using swapon(8) so that the system would have enough vir- tual memory to debug my program. Also, the way we manipu- late memory results in various cache and translation buffer entries being flushed with each call to malloc or free. The end result is that your program will be much slower and use more resources while you are debugging it with Electric Fence. Don't leave libefence.a linked into production software! Use it only for debugging. PORTING Electric Fence is written for ANSI C. You should be able to port it with simple changes to the Makefile and to page.c, which contains the memory management primitives . Many POSIX platforms will require only a re-compile. The operating system facilities required to port Electric Fence are: A way to allocate memory pages A way to make selected pages inaccessible. A way to make the pages accessible again. A way to detect when a program touches an inacces- sible page. A way to print messages. 27-April-1993 5 efence(3) efence(3) Please e-mail me a copy of any changes you have to make, so that I can merge them into the distribution. AUTHOR Bruce Perens WARNINGS I have tried to do as good a job as I can on this soft- ware, but I doubt that it is even theoretically possible to make it bug-free. This software has no warranty. It will not detect some bugs that you might expect it to detect, and will indicate that some non-bugs are bugs. Bruce Perens and/or Pixar will not be liable to any claims resulting from the use of this software or the ideas within it. The entire responsibility for its use must be assumed by the user. If you use it and it results in loss of life and/or property, tough. If it leads you on a wild goose chase and you waste two weeks debugging something, too bad. If you can't deal with the above, please don't use the software! I've written this in an attempt to help other people, not to get myself sued or prosecuted. LICENSE Copyright 1987,1988,1989,1990,1991,1992,1993 Bruce Perens. All Rights Reserved except for those granted in this notice. Permission is granted for you to use this software to debug other programs. You may re-distribute it the origi- nal form in which I released it to you. If you make modi- fications to it, please send them to me for distribution - you may not re-distribute modified versions. You may not sell this software. You may not sell support for this software. If you use ideas from this software in your own product, please pay me for them. CONTACTING THE AUTHOR Bruce Perens c/o Pixar 1001 West Cutting Blvd., Suite 200 Richmond, CA 94804 Telephone: 510-215-3502 Fax: 510-236-0388 Internet: Bruce@Pixar.com FILES /dev/zero: Source of memory pages (via mmap(2)). SEE ALSO malloc(3), mmap(2), mprotect(2), swapon(8) DIAGNOSTICS Segmentation Fault: Examine the offending statement for violation of the boundaries of a memory allocation. 27-April-1993 6 efence(3) efence(3) Bus Error: See the section on WORD-ALIGNMENT AND OVERRUN DETECTION. in this manual page. BUGS My explanation of the alignment issue could be improved. Some Sun systems running SunOS 4.1 are reported to signal an access to a protected page with SIGBUS rather than SIGSEGV, I suspect this is an undocumented feature of a particular Sun hardware version, not just the operating system. On these systems, eftest will fail with a bus error until you modify the Makefile to define PAGE_PROTEC- TION_VIOLATED_SIGNAL as SIGBUS. There are, without doubt, other bugs and porting issues. Please contact me via e-mail if you have any bug reports, ideas, etc. WHAT'S BETTER PURIFY, from Purify Systems, does a much better job than Electric Fence, and does much more. It's available at this writing on SPARC systems only, soon on HP. I'm not affili- ated with Purify, I just think it's a wonderful product and you should check it out. 27-April-1993 7 From owner-freebsd-hackers Fri Oct 3 12:20:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA06904 for hackers-outgoing; Fri, 3 Oct 1997 12:20:09 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA06804 for ; Fri, 3 Oct 1997 12:19:53 -0700 (PDT) Received: (qmail 956 invoked by uid 1000); 3 Oct 1997 19:20:11 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092597 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 03 Oct 1997 12:20:11 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Jaye Mathisen Subject: RE: Qmail vs Sendmail? Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Jaye Mathisen; On 03-Oct-97 you wrote: > > > Anybody care to share their comments? I need a simple high volume mail > server, supporting POP and smtp, and delivery to procmail for final > delivery. > > I'm familiar with sendmail, and it works just fine, but I wasn't real > thrilled with throughput, even on relatively high-end PC hardware. > > I have no experience with qmail, but the docs make it look interesting. > > If anybody's willing to share their views, I'd appreciate it. I use qmail for almost two years now. Yet have to find a reason to complain. Setup is simple, once you read and accept the fact that it is not sendmail. Some complain that it ``makes too many assumptions'' - I heard this expression several times. I have an ISP service deliver over 200,000 messages a day from a 486 DX-50 without complaint. Virtual domains are trivial to setup. Mailing lists are easy and self managed and it is inherently safe. I like it. --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-hackers Fri Oct 3 12:20:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA06967 for hackers-outgoing; Fri, 3 Oct 1997 12:20:20 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA06885 for ; Fri, 3 Oct 1997 12:20:04 -0700 (PDT) Received: (qmail 958 invoked by uid 1000); 3 Oct 1997 19:20:11 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092597 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199710030724.AAA04419@lestat.nas.nasa.gov> Date: Fri, 03 Oct 1997 12:20:11 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Jason Thorpe Subject: Re: Advice Seeked - Non-Invasive Metrics Techniques Cc: freebsd-dlm@primer.i-connect.net, freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Jason Thorpe; On 03-Oct-97 you wrote: > On Fri, 03 Oct 1997 00:00:22 -0700 (PDT) > Simon Shapiro wrote: > > > I need to carefully tune and analyze timing and perfromance > statistics. > > Mainly to identify why some rotines in the DLM take so much time. > > I guess generic kernel profiling isn't enough, here? It is not an issue of ``not enough'' but rather of ``too much''. I need a light-weight mechanism that can stay there. Also, for my own edification, I was curuious about the efficiency of my code. --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-hackers Fri Oct 3 12:28:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA07473 for hackers-outgoing; Fri, 3 Oct 1997 12:28:35 -0700 (PDT) Received: from mail.id.net (mail.id.net [199.125.1.6]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA07467 for ; Fri, 3 Oct 1997 12:28:32 -0700 (PDT) Received: from server.id.net (server.id.net [199.125.2.20]) by mail.id.net (8.8.6/8.8.6) with ESMTP id PAA04581 for ; Fri, 3 Oct 1997 15:38:02 -0400 (EDT) From: Robert Shady Received: (from rls@localhost) by server.id.net (8.8.5/8.7.3) id PAA10104 for freebsd-hackers@freebsd.org; Fri, 3 Oct 1997 15:28:46 -0400 (EDT) Message-Id: <199710031928.PAA10104@server.id.net> Subject: Video-Capture To: freebsd-hackers@freebsd.org Date: Fri, 3 Oct 1997 15:28:46 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Out of the video capture cards that are supported under FreeBSD, which one would be considered the best? Meaning... 1. It is still readily available.. 2. It can capture at least 640x480 @ 15 frames/sec. in 16bit or better color. 3. Has decent developers support available.. 4. Has support for video-in (either RCA or S-Video) Would be nice to have video-out as well, but not necessary at this point. I'm looking at buying a ton of these, so I need some good info and most of the boxes I could find, or websites I went to were very misleading... Ie: Some say 320x240 @ 60fps (were fps = fields per second, wutz dat? it ain't a frame cause further down it said 320x240 @ 10 frames per second) Suggestions, comments, ec. BTW, in case you don't know, "supported" video captures devices are (according to RELNOTES.TXT in 3.0) Connectix QuickCam Matrox Meteor Video frame grabber Creative Labs Video Spigot frame grabber Cortex1 frame grabber Hauppauge Wincast/TV boards (PCI) STB TV PCI From owner-freebsd-hackers Fri Oct 3 13:52:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA12159 for hackers-outgoing; Fri, 3 Oct 1997 13:52:53 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA12154 for ; Fri, 3 Oct 1997 13:52:49 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id NAA16929 for ; Fri, 3 Oct 1997 13:52:11 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma016924; Fri Oct 3 13:51:41 1997 Received: (from archie@localhost) by bubba.whistle.com (8.8.5/8.6.12) id NAA23325 for freebsd-hackers@freebsd.org; Fri, 3 Oct 1997 13:51:40 -0700 (PDT) From: Archie Cobbs Message-Id: <199710032051.NAA23325@bubba.whistle.com> Subject: bpfattach() bug To: freebsd-hackers@freebsd.org Date: Fri, 3 Oct 1997 13:51:40 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk FYI- The bpfattach() routine makes an assumption that it will only ever be called at boot time (specifically, before any /dev/bpf* devices are opened). This assumption is false, for example, in any case where an interface can be created dynamically (such as ours). The following patch fixes this in both -stable and -current. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com *** /usr/src/sys/net/bpf.c Wed Apr 9 00:31:05 1997 --- bpf.c Fri Oct 3 13:11:44 1997 *************** *** 115,120 **** --- 115,121 ---- */ static struct bpf_if *bpf_iflist; static struct bpf_d bpf_dtab[NBPFILTER]; + static int bpf_dtab_init; static int bpf_allocbufs __P((struct bpf_d *)); static void bpf_attachd __P((struct bpf_d *d, struct bpf_if *bp)); *************** *** 1293,1301 **** /* * Mark all the descriptors free if this hasn't been done. */ ! if (!D_ISFREE(&bpf_dtab[0])) for (i = 0; i < NBPFILTER; ++i) D_MARKFREE(&bpf_dtab[i]); if (bootverbose) printf("bpf: %s%d attached\n", ifp->if_name, ifp->if_unit); --- 1294,1304 ---- /* * Mark all the descriptors free if this hasn't been done. */ ! if (!bpf_dtab_init) { for (i = 0; i < NBPFILTER; ++i) D_MARKFREE(&bpf_dtab[i]); + bpf_dtab_init = 1; + } if (bootverbose) printf("bpf: %s%d attached\n", ifp->if_name, ifp->if_unit); From owner-freebsd-hackers Fri Oct 3 14:49:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA14825 for hackers-outgoing; Fri, 3 Oct 1997 14:49:46 -0700 (PDT) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA14820 for ; Fri, 3 Oct 1997 14:49:42 -0700 (PDT) Received: by iafnl.es.iaf.nl with UUCP id AA16952 (5.67b/IDA-1.5 for freebsd-hackers@FreeBSD.ORG); Fri, 3 Oct 1997 23:49:05 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.5/8.6.12) id TAA01259; Fri, 3 Oct 1997 19:03:22 +0100 (MET) From: Wilko Bulte Message-Id: <199710031803.TAA01259@yedi.iaf.nl> Subject: Re: UUCP To: pechter@lakewood.com Date: Fri, 3 Oct 1997 19:03:22 +0100 (MET) Cc: dk+@ua.net, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199710031354.JAA04901@i4got.lakewood.com> from "Bill Pechter" at Oct 3, 97 09:54:59 am X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' 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-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Bill Pechter wrote... > > In article you wrote: > > > Would it be possible to uncomment the HDB capabilities in UUCP for the > > > next release? Even though UUCP died years ago, I'm converting more > > > > UUCP WHAT?? How else are you supposed to do mail backups with > > other ISP, but with UUCP over TCP to your primary line? > > The network I set up in university 2 years ago still works this way, > > and mail goes in and out even if leased line and/or router died. > > > > What about hundreds of customers in xUSSR with non-nailed lines (which > > are more expensive than dedicated ISDN in the U.S.?) etc. > > > > As for UUCP in FreeBSD tree, well, there were some problems reported > > before, but I beleive they were all fixed. > > > > I still think that FreeBSD should adopt the position of supporting HDB > V2 uucp configuration files in the system. (I have to rebuild uucp > after all the make worlds with my own patches to do so...) No thanks. HDB config files are a pain IMHO. _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl http://www.tcja.nl/~wilko |/|/ / / /( (_) Arnhem, The Netherlands - Do, or do not. There is no 'try' ----------------------------------------------------------------------Yoda From owner-freebsd-hackers Fri Oct 3 15:34:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA17347 for hackers-outgoing; Fri, 3 Oct 1997 15:34:57 -0700 (PDT) Received: from proxy3.ba.best.com (root@proxy3.ba.best.com [206.184.139.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA17323 for ; Fri, 3 Oct 1997 15:34:50 -0700 (PDT) Received: from shellx.best.com (shellx.best.com [206.86.0.11]) by proxy3.ba.best.com (8.8.7/8.8.BEST) with ESMTP id PAA01207 for ; Fri, 3 Oct 1997 15:33:57 -0700 (PDT) Received: from localhost (mdean@localhost) by shellx.best.com (8.8.6/8.8.3) with SMTP id PAA20884 for ; Fri, 3 Oct 1997 15:33:56 -0700 (PDT) Date: Fri, 3 Oct 1997 15:33:56 -0700 (PDT) From: mdean To: freebsd-hackers@freebsd.org Subject: devfs / cdevsw Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk When should I use cdevsw, and when should I use devfs, will new systems have the /devs mountpoint or something? And if your device is named dummy then how are you supposed to use NDUMMY, and where does it get defined? From owner-freebsd-hackers Fri Oct 3 16:13:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA19236 for hackers-outgoing; Fri, 3 Oct 1997 16:13:37 -0700 (PDT) Received: from seagull.rtd.com (dgy@seagull.rtd.com [198.102.68.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA19231 for ; Fri, 3 Oct 1997 16:13:33 -0700 (PDT) Received: (from dgy@localhost) by seagull.rtd.com (8.8.5/8.8.5) id QAA02873; Fri, 3 Oct 1997 16:12:10 -0700 (MST) From: Don Yuniskis Message-Id: <199710032312.QAA02873@seagull.rtd.com> Subject: Re: UUCP In-Reply-To: <199710031803.TAA01259@yedi.iaf.nl> from Wilko Bulte at "Oct 3, 97 07:03:22 pm" To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Fri, 3 Oct 1997 16:12:10 -0700 (MST) Cc: pechter@lakewood.com, dk+@ua.net, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In the words of the world-renowned author, Wilko Bulte: > As Bill Pechter wrote... > > > > In article you wrote: > > > > Would it be possible to uncomment the HDB capabilities in UUCP for the > > > > next release? Even though UUCP died years ago, I'm converting more > > > > > > UUCP WHAT?? How else are you supposed to do mail backups with > > > other ISP, but with UUCP over TCP to your primary line? > > > The network I set up in university 2 years ago still works this way, > > > and mail goes in and out even if leased line and/or router died. > > > > > > What about hundreds of customers in xUSSR with non-nailed lines (which > > > are more expensive than dedicated ISDN in the U.S.?) etc. > > > > > > As for UUCP in FreeBSD tree, well, there were some problems reported > > > before, but I beleive they were all fixed. > > > > I still think that FreeBSD should adopt the position of supporting HDB > > V2 uucp configuration files in the system. (I have to rebuild uucp > > after all the make worlds with my own patches to do so...) > > No thanks. HDB config files are a pain IMHO. You can quite easily support V2, HDB and Taylor *config* files at the same time. My /etc/uucp contains HBB, V2, Taylor and shared subdirs. Each contains the files appropriate for that particular flavor of UUCP. (shared contains things like dialcodes). They are all symlinked, as needed, up into /etc/uucp. I think the issue of *log* file format was the concern (of a previous poster)... --don From owner-freebsd-hackers Fri Oct 3 17:00:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA21231 for hackers-outgoing; Fri, 3 Oct 1997 17:00:19 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA21226 for ; Fri, 3 Oct 1997 17:00:18 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA16923; Fri, 3 Oct 1997 16:52:28 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd016921; Fri Oct 3 23:52:21 1997 Message-ID: <343584F8.5656AEC7@whistle.com> Date: Fri, 03 Oct 1997 16:51:20 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: mdean CC: freebsd-hackers@FreeBSD.ORG Subject: Re: devfs / cdevsw References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk mdean wrote: > > When should I use cdevsw, and when should I use devfs, will new systems > have the /devs mountpoint or something? And if your device is named dummy > then how are you supposed to use NDUMMY, and where does it get defined? wow, actually I'm actually doing active development of devfs again after two year's break. NDUMMY is used should you want to statically allocate some resources. New drivers should not do this, but use 'malloc' as a general rule. The use of NDUMMY teneds to make code that is unsuitable for conversion to an LKM and the eventual aim is to have nearly all drivers LKM'able. I run /devs here, but have some problems with disks the answer is a rather large change to the way that disks are handled on FreeBSD, so I've detoured into that for a while before I resume working on DEVFS itself. till then, the example drivers should show you how to do devfs entries. julian From owner-freebsd-hackers Fri Oct 3 17:49:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA23812 for hackers-outgoing; Fri, 3 Oct 1997 17:49:23 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA23807 for ; Fri, 3 Oct 1997 17:49:14 -0700 (PDT) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id KAA05461; Sat, 4 Oct 1997 10:18:46 +0930 (CST) Message-ID: <19971004101846.12337@lemis.com> Date: Sat, 4 Oct 1997 10:18:46 +0930 From: Greg Lehey To: Mike Smith Cc: pechter@lakewood.com, dk+@ua.net, freebsd-hackers@FreeBSD.ORG Subject: Re: UUCP (important clarification) References: <199710031354.JAA04901@i4got.lakewood.com> <199710031430.AAA00858@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <199710031430.AAA00858@word.smith.net.au>; from Mike Smith on Sat, Oct 04, 1997 at 12:00:44AM +0930 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, Oct 04, 1997 at 12:00:44AM +0930, Mike Smith wrote: >> I still think that FreeBSD should adopt the position of supporting HDB >> V2 uucp configuration files in the system. (I have to rebuild uucp >> after all the make worlds with my own patches to do so...) > > You are not helping yourself by not being clear. > > You do not mean "the Taylor configuration format should be abandoned in > favour of the HDB and V2 formats", you mean "the UUCP suite should be > built with support for the Taylor, HDB and V2 configuration formats". > > ie. HAVE_HDB_CONFIG and HAVE_V2_CONFIG should be set to 1 in /usr/src/ > gnu/libexec/uucp/common_source/policy.h. > > This wouldn't cost anything functionality-wise, and would make Bill > happy. Can we achieve enough consensus on this to make it into 2.2.5? It's a good thing that you said this. I misunderstood Bill, and I'm sure a lot of other people do. I agree with this suggestion, and not what I understood Bill to have said. I can't really see this getting changed for 2.2.5, though. Greg From owner-freebsd-hackers Fri Oct 3 17:51:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA23932 for hackers-outgoing; Fri, 3 Oct 1997 17:51:17 -0700 (PDT) Received: from tok.qiv.com (uucp@[204.214.141.211]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA23926 for ; Fri, 3 Oct 1997 17:51:13 -0700 (PDT) Received: (from uucp@localhost) by tok.qiv.com (8.8.6/8.8.5) with UUCP id TAA16249; Fri, 3 Oct 1997 19:50:21 -0500 (CDT) Received: from localhost (jdn@localhost) by acp.qiv.com (8.8.6/8.8.5) with SMTP id TAA00551; Fri, 3 Oct 1997 19:41:57 -0500 (CDT) X-Authentication-Warning: acp.qiv.com: jdn owned process doing -bs Date: Fri, 3 Oct 1997 19:41:57 -0500 (CDT) From: "Jay D. Nelson" To: Greg Lehey cc: dk+@ua.net, freebsd-hackers@FreeBSD.ORG Subject: Re: 2nd Notice: 4 days to code freeze in RELENG_2_2 branch. In-Reply-To: <19971003170802.12051@lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 3 Oct 1997, Greg Lehey wrote: > On Thu, Oct 02, 1997 at 11:04:04PM -0700, Dmitry Kohmanyuk wrote: > > In article you wrote: > >> Would it be possible to uncomment the HDB capabilities in UUCP for the > >> next release? Even though UUCP died years ago, I'm converting more > > > > UUCP WHAT?? How else are you supposed to do mail backups with > > other ISP, but with UUCP over TCP to your primary line? > > The network I set up in university 2 years ago still works this way, > > and mail goes in and out even if leased line and/or router died. > > > > What about hundreds of customers in xUSSR with non-nailed lines (which > > are more expensive than dedicated ISDN in the U.S.?) etc. > > > > As for UUCP in FreeBSD tree, well, there were some problems reported > > before, but I beleive they were all fixed. > > I certainly believe that reports of UUCP's death are greatly > exaggerated. I'm documenting it in the second edition of "The > Complete FreeBSD". > > That doesn't mean, of course, that I think HDB is the way to go. The > Taylor semantics are much easier to handle. Yes, Taylor is better in some respects. I'm not suggesting changing sample files or anything _except_ uncommenting the HDB capability in the build. When you are migrating from an older HDB system to FreeBSD, _and there is no compeling reason_ to use Taylor features, it is simpler, quicker and more reliable to simply move the config files to the FreeBSD system and go. The down side is code size. It will grow a bit. The up side is that those of us who use it won't have to convert files and can convert older systems more quickly (and at less cost to a paying client.) Newbies won't see the change because they won't be using it. Old farts like me will be happier because we can deal with the same files we have been using for years. What can it hurt? > Greg > -- Jay From owner-freebsd-hackers Fri Oct 3 18:39:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA25668 for hackers-outgoing; Fri, 3 Oct 1997 18:39:23 -0700 (PDT) Received: from proxy4.ba.best.com (root@proxy4.ba.best.com [206.184.139.15]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA25663 for ; Fri, 3 Oct 1997 18:39:21 -0700 (PDT) Received: from shellx.best.com (shellx.best.com [206.86.0.11]) by proxy4.ba.best.com (8.8.7/8.8.BEST) with ESMTP id SAA20417; Fri, 3 Oct 1997 18:38:50 -0700 (PDT) Received: from localhost (mdean@localhost) by shellx.best.com (8.8.6/8.8.3) with SMTP id SAA18044; Fri, 3 Oct 1997 18:38:49 -0700 (PDT) Date: Fri, 3 Oct 1997 18:38:49 -0700 (PDT) From: mdean To: Julian Elischer cc: freebsd-hackers@FreeBSD.ORG Subject: Re: devfs / cdevsw In-Reply-To: <343584F8.5656AEC7@whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > till then, the example drivers should show you how to do devfs entries. > ?? HUNH ?? Should I actually use devfs, or would most people avoid it for character drivers? Also is cdevsw[] deprecated, because I can't find conf.c? I remember reading this story about this guy who wrote a completely brilliant piece of software, when he went back 2 years later to modify it he was unable to figure out his own program. There were no comments! From owner-freebsd-hackers Fri Oct 3 19:07:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA26792 for hackers-outgoing; Fri, 3 Oct 1997 19:07:01 -0700 (PDT) Received: from proxy3.ba.best.com (root@proxy3.ba.best.com [206.184.139.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA26787 for ; Fri, 3 Oct 1997 19:06:58 -0700 (PDT) Received: from shellx.best.com (shellx.best.com [206.86.0.11]) by proxy3.ba.best.com (8.8.7/8.8.BEST) with ESMTP id TAA23860 for ; Fri, 3 Oct 1997 19:05:57 -0700 (PDT) Received: from localhost (mdean@localhost) by shellx.best.com (8.8.6/8.8.3) with SMTP id TAA28428 for ; Fri, 3 Oct 1997 19:05:57 -0700 (PDT) Date: Fri, 3 Oct 1997 19:05:57 -0700 (PDT) From: mdean Reply-To: mdean To: freebsd-hackers@freebsd.org Subject: lkms versus hard linked drivers Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk My question is very simple: What can't be a lkm? For instance if I have some intel 8255As that I am going to use to produce a 500hz pulse train for stepper motor control. These chips aren't stateless and need to be intialized and mostly need to be kernel code to access change of state interrupts and the high frequency clock (obviously). Can I do all this from an lkm? Will everything except the boot device driver and microkernel eventually be an lkm? Is it undesirable or something, because the only module that I am using on my system is for the screensaver? What about this: I am pretty sure I cannot do this inside the kernel. What if I want my device driver for the stepper motor to socket(2) since it is really not going to have any ioctls. This way controlling motor position can be done from any machine on the network. Can I use any system call in a) device driver in the kernel tree b) lkm? From owner-freebsd-hackers Fri Oct 3 19:19:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA27167 for hackers-outgoing; Fri, 3 Oct 1997 19:19:01 -0700 (PDT) Received: from proxy3.ba.best.com (root@proxy3.ba.best.com [206.184.139.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA27162 for ; Fri, 3 Oct 1997 19:18:57 -0700 (PDT) Received: from shellx.best.com (shellx.best.com [206.86.0.11]) by proxy3.ba.best.com (8.8.7/8.8.BEST) with ESMTP id TAA10781; Fri, 3 Oct 1997 19:17:47 -0700 (PDT) Received: from localhost (mdean@localhost) by shellx.best.com (8.8.6/8.8.3) with SMTP id TAA02765; Fri, 3 Oct 1997 19:17:46 -0700 (PDT) Date: Fri, 3 Oct 1997 19:17:46 -0700 (PDT) From: mdean To: Julian Elischer cc: freebsd-hackers@freebsd.org Subject: Re: devfs / cdevsw In-Reply-To: <3435A37E.4A7B7C1D@whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > These are shell script that will write a driver for you and put > it in the sources in /usr/src and compile a kernel with your > new driver.. the driver is a skelaton driver that does nothing, > but then you can fill out the function. I have these, it talks about conf.c in there. What does __P() do to a function declaration? I see it in the lkm examples. And also in .h files for c library calls apparently (pointing?) to the kernel syscalls. From owner-freebsd-hackers Fri Oct 3 19:20:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA27291 for hackers-outgoing; Fri, 3 Oct 1997 19:20:31 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA27281 for ; Fri, 3 Oct 1997 19:20:26 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.7/8.8.5) with ESMTP id TAA06529; Fri, 3 Oct 1997 19:19:46 -0700 (PDT) Message-Id: <199710040219.TAA06529@rah.star-gate.com> To: Robert Shady cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Video-Capture In-reply-to: Your message of "Fri, 03 Oct 1997 15:28:46 EDT." <199710031928.PAA10104@server.id.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Oct 1997 19:19:46 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Questions related to video and/or audio to the multimedia mailing list: multimedia@freebsd.org We can capture 640x480 32bits at 30fps with Bt848 based cards such as the WinCast TV PCI for further info visit the Bt848 project web page: http://www.freebsd.org/~hasty/Bt848.html Amancio >From The Desk Of Robert Shady : > Out of the video capture cards that are supported under FreeBSD, which one > would be considered the best? Meaning... > > > 1. It is still readily available.. > 2. It can capture at least > 640x480 @ 15 frames/sec. in 16bit or better color. > 3. Has decent developers support available.. > 4. Has support for video-in (either RCA or S-Video) > > Would be nice to have video-out as well, but not necessary at this point. > I'm looking at buying a ton of these, so I need some good info and most of > the boxes I could find, or websites I went to were very misleading... > Ie: Some say 320x240 @ 60fps (were fps = fields per second, wutz dat? it > ain't a frame cause further down it said 320x240 @ 10 frames per second) > > Suggestions, comments, ec. > > BTW, in case you don't know, "supported" video captures devices are > (according to RELNOTES.TXT in 3.0) > > Connectix QuickCam > Matrox Meteor Video frame grabber > Creative Labs Video Spigot frame grabber > Cortex1 frame grabber > Hauppauge Wincast/TV boards (PCI) > STB TV PCI > > > From owner-freebsd-hackers Fri Oct 3 19:24:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA27476 for hackers-outgoing; Fri, 3 Oct 1997 19:24:47 -0700 (PDT) Received: from earth.sunlink.net (mml@earth.sunlink.net [204.170.191.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA27450 for ; Fri, 3 Oct 1997 19:24:04 -0700 (PDT) Received: from localhost (mml@localhost) by earth.sunlink.net (1.9.14/9.9.9) with SMTP id WAA11018 for ; Fri, 3 Oct 1997 22:23:25 -0400 (EDT) Date: Fri, 3 Oct 1997 22:23:25 -0400 (EDT) From: "Marc M. LaFerrera" To: hackers@freebsd.org Subject: HELP!??!?! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I am having alot of problems. Hopefully you will be able to help me. First, I can't mount my linux partition from FreeBSD. Everytime I do: mount -t ext2fs /dev/wd0s1 /mnt I get, : mount: ext2fs filesystem unsupported or something along those lines. I have the book "The complete FreeBSD" distributed by walnut creek cdrom. But it says nothing what so ever bout this. How do I add ext2fs support into my kernel? And, I know I shouldn't ask you this next question, but, you never know. I have the same problem with linux. I can't mount my BSD partition from linux. what would the fs type be? And how can I add support for the fs type? And, problem number 2. I have a Iomega Zip drive (Paralelle SCSI). It is very simple to get it working in Linux. But I haven't the slightest idea how to even get FreeBSD to know it exists. How can I make FreeBSD notice it? Problem number 3. I am on a regular analog line. 56k motorola modem surfr. Once again, getting ppp to work in linux is very simple. I can get FreeBSD to dial out using pppd and connect. It will assign me a dynamic IP and everything. Except, the only problem is, whenever I try to connect to a remote host or do anything other then connect to localhost, I get "unknown host". I've tried everything I know of. I have edited /etc/resolv.conf to the correct NS's and a few other things. But everything I seem to do doesn't work. Any ideas of what can be wrong? I know these may seem like lame questions. But I am very new to FreeBSD. I have been with linux for quiet a while and kinda got used to it. Here is some information about my system if it helps you any: OS: FreeBSD 2.2.2 RAM: 24mb HD: 1 maxtor 2.0GB (IDE) 1 Samsung 2.1GB (IDE) CDROM: ATAPI IDE 6x Thanx for all your help in advance. ------------------------------------------------------------ "Depression is just ther obvious solution for putting things aside" mml@sunlink.net http://www.sunlink.net/~mml -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNCQHVf2osiC/e/e1AQHR3QP/SX+JicHOYTfiVVTJWUGspTCFNV5/d/yV u6gcdOZXFymjUVJEI7zTJXTSdHD0rTZ8HUXLxS5b22BDk+8D7OB18nx1lBryDqhU 3tfR7DJns5SPQczi0pBfvXdIiEjVL3yj3zb40s64y8WwTq0rGxyY3/8oQcyhdqdc oI3hLyn0uMs= =piM2 -----END PGP SIGNATURE----- From owner-freebsd-hackers Fri Oct 3 23:35:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA00872 for hackers-outgoing; Fri, 3 Oct 1997 23:35:05 -0700 (PDT) Received: from nemesis.idirect.com (root@nemesis.idirect.com [207.136.80.40]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA29447 for ; Fri, 3 Oct 1997 20:16:12 -0700 (PDT) Received: from thor.idirect.com (jlixfeld@thor.idirect.com [207.136.80.105]) by nemesis.idirect.com (8.8.5/8.8.4) with SMTP id XAA05517 for ; Fri, 3 Oct 1997 23:16:04 -0400 (EDT) Received: from localhost (jlixfeld@localhost) by thor.idirect.com (8.6.12/8.6.12) with SMTP id XAA14027 for ; Fri, 3 Oct 1997 23:15:58 -0400 X-Authentication-Warning: thor.idirect.com: jlixfeld owned process doing -bs Date: Fri, 3 Oct 1997 23:15:58 -0400 (EDT) From: Jason Lixfeld To: freebsd-hackers@freebsd.org Subject: FreeBSD & BSD/OS crypt compatibility Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk How do I do this?! How can I get a BSD/OS Password to authenticate under FreeBSD, and make FreeBSD passwords backwards compatible with BSD/OS?! TiA! From owner-freebsd-hackers Fri Oct 3 23:35:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA00970 for hackers-outgoing; Fri, 3 Oct 1997 23:35:31 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA00553 for ; Fri, 3 Oct 1997 20:40:13 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id UAA21124; Fri, 3 Oct 1997 20:31:51 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd021120; Sat Oct 4 03:31:41 1997 Message-ID: <3435B860.19A13460@whistle.com> Date: Fri, 03 Oct 1997 20:30:40 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: mdean CC: freebsd-hackers@freebsd.org Subject: Re: lkms versus hard linked drivers References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk mdean wrote: > > My question is very simple: What can't be a lkm? > For instance if I have some intel 8255As that I am going to use to produce > a 500hz pulse train for stepper motor control. These chips aren't stateless > and need to be intialized and mostly need to be kernel code to access > change of state interrupts and the high frequency clock (obviously). Can I > do all this from an lkm? yes sure. the only function that MUST be done at bootup is allocation of LARGE physically contiguous buffers of ram. because after running a few seconds ram get's fragmented.. large VIRTUALLY contiguous buffers are ok. I'm not sure about interrupts in the present code.. > > Will everything except the boot device driver and microkernel eventually be > an lkm? yes > Is it undesirable or something, because the only module that I am > using on my system is for the screensaver? no there are a few pieces of the puzzle still not quite ready. check the LKM examples in /usr/share/exaples/lkm as well. > > What about this: I am pretty sure I cannot do this inside the kernel. What > if I want my device driver for the stepper motor to socket(2) since it is > really not going to have any ioctls. This way controlling motor position > can be done from any machine on the network. of course it can be done.. but it may be better to have a daemon do that part.. > > Can I use any system call in a) device driver in the kernel tree b) lkm? no, and no. From owner-freebsd-hackers Sat Oct 4 00:07:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA02574 for hackers-outgoing; Sat, 4 Oct 1997 00:07:24 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA02569; Sat, 4 Oct 1997 00:07:19 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id GAA14906; Sat, 4 Oct 1997 06:31:48 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with UUCP id GAA09876; Sat, 4 Oct 1997 06:31:25 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.7/keltia-2.10/nospam) id DAA17652; Sat, 4 Oct 1997 03:58:59 +0200 (CEST) Message-ID: <19971004035858.34857@keltia.freenix.fr> Date: Sat, 4 Oct 1997 03:58:58 +0200 From: Ollivier Robert To: freebsd-bugs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Electric Fence info (was Re: Bug in malloc/free (was: Memory leak in getservbyXXX?)) References: <199710031817.OAA16814@lakes.dignus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199710031817.OAA16814@lakes.dignus.com>; from Thomas David Rivers on Fri, Oct 03, 1997 at 02:17:17PM -0400 X-Operating-System: FreeBSD 3.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Thomas David Rivers: > Ok - there seems to be enough interest... Here's the man page > for electric fence (which does the mprotect() trick Jordan mentions): The main problem of EFence is the amount of swap it takes... I tried to run Mutt through it a few months ago and ran out of swap _before_ displaying anything. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #35: Sun Sep 21 19:28:07 CEST 1997 From owner-freebsd-hackers Sat Oct 4 01:04:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA05253 for hackers-outgoing; Sat, 4 Oct 1997 01:04:26 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA05246 for ; Sat, 4 Oct 1997 01:04:21 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id RAA00530; Sat, 4 Oct 1997 17:31:20 +0930 (CST) Message-Id: <199710040801.RAA00530@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: mdean cc: Julian Elischer , freebsd-hackers@freebsd.org Subject: Re: devfs / cdevsw In-reply-to: Your message of "Fri, 03 Oct 1997 19:17:46 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 04 Oct 1997 17:31:19 +0930 From: Mike Smith Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > These are shell script that will write a driver for you and put > > it in the sources in /usr/src and compile a kernel with your > > new driver.. the driver is a skelaton driver that does nothing, > > but then you can fill out the function. > > I have these, it talks about conf.c in there. > > What does __P() do to a function declaration? I see it in the lkm examples. > And also in .h files for c library calls apparently (pointing?) to the > kernel syscalls. It's archaic junk left over from the days of pre-ANSI compilers. Use it if you are adding to an existing source file (ie. maintain consistency), but do not use it in new code. mike From owner-freebsd-hackers Sat Oct 4 01:09:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA05462 for hackers-outgoing; Sat, 4 Oct 1997 01:09:51 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id BAA05455 for ; Sat, 4 Oct 1997 01:09:46 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.71 #1) id 0xHPGf-0003wT-00; Sat, 4 Oct 1997 01:08:53 -0700 Date: Sat, 4 Oct 1997 01:08:51 -0700 (PDT) From: Tom To: Jason Lixfeld cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD & BSD/OS crypt compatibility In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 3 Oct 1997, Jason Lixfeld wrote: > How do I do this?! How can I get a BSD/OS Password to authenticate under > FreeBSD, and make FreeBSD passwords backwards compatible with BSD/OS?! Just install the DES stuff on FreeBSD. BTW, this belongs on freebsd-questions, not hackers. > TiA! > > > Tom From owner-freebsd-hackers Sat Oct 4 01:10:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA05560 for hackers-outgoing; Sat, 4 Oct 1997 01:10:20 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA05549 for ; Sat, 4 Oct 1997 01:10:15 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id DAA04089; Sat, 4 Oct 1997 03:52:07 +0930 (CST) Message-Id: <199710031822.DAA04089@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Zoltan Sebestyen cc: FreeBSD hackers mailinglist Subject: Re: cpu/memory monitoring In-reply-to: Your message of "Fri, 03 Oct 1997 19:11:38 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 04 Oct 1997 03:52:06 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I'd like to know if there's any other any other program than top, which > monitors the REAL cpu and memory load, but have more simple source code. What is "REAL cpu and memory load"? The problem here is, I think, that you have seen what Microsoft (and some other vendors) pass off as a "simple" CPU/memory monitor and think that there is some simple value that is "CPU load" or "memory load". In reality, things aren't so simple. What do you consider "memory load"? Do you mean all pages that have been recently referenced? All pages that are accounted for (ie. not "free")? Do you classify pages into degrees of "freeness"? And how do you propose to accumulate this figure? Traversing all of the memory information isn't cheap. If you want to get a feel for memory usage, and to give you some idea of the complexity involved, try looking at the output of 'vmstat -m'. And that's just the _kernel_. As for CPU load, again: what is "CPU load"? The amount of CPU time "not idle"? How about otherwise-idle time that is consumed in speculative makework? Is that "free but better-used"? How about interrupt time? The only way to present this sort of information is either to dumb it down Microsoft-style, or present it all and be generous enough to assume the user isn't completely stupid. mike From owner-freebsd-hackers Sat Oct 4 01:24:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA06078 for hackers-outgoing; Sat, 4 Oct 1997 01:24:38 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA06072 for ; Sat, 4 Oct 1997 01:24:33 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id RAA00605; Sat, 4 Oct 1997 17:51:54 +0930 (CST) Message-Id: <199710040821.RAA00605@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: mdean cc: freebsd-hackers@freebsd.org Subject: Re: lkms versus hard linked drivers In-reply-to: Your message of "Fri, 03 Oct 1997 19:05:57 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 04 Oct 1997 17:51:50 +0930 From: Mike Smith Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > My question is very simple: What can't be a lkm? Literally speaking; anything that's required by the load path for LKMs. > For instance if I have some intel 8255As that I am going to use to produce > a 500hz pulse train for stepper motor control. These chips aren't stateless > and need to be intialized and mostly need to be kernel code to access > change of state interrupts and the high frequency clock (obviously). Can I > do all this from an lkm? You don't want to do this sort of very hard realtime work inside the FreeBSD kernel. Use a real stepper controller card and save yourself a world of grief. Yes, you could do this from an LKM, but you would find that your 500Hz output was not anything like as regular as you might want. Delayed stages in your pattern sequence will give you stepper a really ugly sound, and may cause you serious problems depending on what you're trying to do with it. > What about this: I am pretty sure I cannot do this inside the kernel. What > if I want my device driver for the stepper motor to socket(2) since it is > really not going to have any ioctls. This way controlling motor position > can be done from any machine on the network. You appear to have some strange ideas about how the kernel actually works internally. 8) If you want to make the motor position network-controllable, write a device driver for the stepper controller card (if necessasry, you might well find that user-space I/O is adequate for your needs) and have *that* open the server socket. > Can I use any system call in a) device driver in the kernel tree b) lkm? Not in the fashion that you are thinking of above, no. mike From owner-freebsd-hackers Sat Oct 4 03:00:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA09417 for hackers-outgoing; Sat, 4 Oct 1997 03:00:40 -0700 (PDT) Received: from soleil.uvsq.fr (soleil.uvsq.fr [193.51.24.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA09406 for ; Sat, 4 Oct 1997 03:00:33 -0700 (PDT) Received: from cezanne.prism.uvsq.fr (rtc105.reseau.uvsq.fr [193.51.24.21]) by soleil.uvsq.fr (8.8.6/jtpda-5.2) with ESMTP id LAA23362 ; Sat, 4 Oct 1997 11:45:24 +0200 (METDST) Received: (from son@localhost) by cezanne.prism.uvsq.fr (8.8.5/8.8.5) id LAA00275; Sat, 4 Oct 1997 11:03:41 GMT Message-ID: <19971004110341.63138@coreff.prism.uvsq.fr> Date: Sat, 4 Oct 1997 11:03:41 +0000 From: Nicolas Souchu To: "Marc M. LaFerrera" Cc: hackers@FreeBSD.ORG Subject: Re: HELP!??!?! References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: ; from Marc M. LaFerrera on Fri, Oct 03, 1997 at 10:23:25PM -0400 X-Operating-System: FreeBSD coreff 2.2.1-RELEASE FreeBSD 2.2.1-RELEASE Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, Oct 03, 1997 at 10:23:25PM -0400, Marc M. LaFerrera wrote: > >And, problem number 2. I have a Iomega Zip drive (Paralelle SCSI). It is ^^^^^^^^^^^^^^ ZIP+ drive with SCSI _and_ parallel support? Then, I would be really happy to know how it works for you ;) >very simple to get it working in Linux. But I haven't the slightest idea >how to even get FreeBSD to know it exists. How can I make FreeBSD notice >it? If your ZIP is plugged to your parallel interface, see http://www.prism.uvsq.fr/~son/ppa3.html -- Nicolas.Souchu@prism.uvsq.fr FreeBSD - Turning PC's into workstations - http://www.FreeBSD.org From owner-freebsd-hackers Sat Oct 4 03:41:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA12362 for hackers-outgoing; Sat, 4 Oct 1997 03:41:12 -0700 (PDT) Received: from ghost.mep.ruhr-uni-bochum.de (ghost.mep.ruhr-uni-bochum.de [134.147.6.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA12357 for ; Sat, 4 Oct 1997 03:41:06 -0700 (PDT) Received: (from roberte@localhost) by ghost.mep.ruhr-uni-bochum.de (8.8.5/8.8.4) id MAA01096; Sat, 4 Oct 1997 12:40:53 +0200 (MESZ) From: Robert Eckardt Message-Id: <199710041040.MAA01096@ghost.mep.ruhr-uni-bochum.de> Subject: Re: HELP!??!?! In-Reply-To: from "Marc M. LaFerrera" at "Oct 3, 97 10:23:25 pm" To: mml@sunlink.net (Marc M. LaFerrera) Date: Sat, 4 Oct 1997 12:40:53 +0200 (MESZ) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk It was Marc M. LaFerrera who wrote: > Hello, I am having alot of problems. Hopefully you will be able to help > me. First, I can't mount my linux partition from FreeBSD. Everytime I do: > mount -t ext2fs /dev/wd0s1 /mnt > I get, : > mount: ext2fs filesystem unsupported > or something along those lines. I have the book "The complete FreeBSD" > distributed by walnut creek cdrom. But it says nothing what so ever bout > this. How do I add ext2fs support into my kernel? And, I know I shouldn't add to your file systems in your kernel config file: options "EXT2FS" Don't forget to umount the linux FS *before* reboot or halt. Otherwise, it will not umount / correctly and BSD will have to check / on next reboot and Linux will need to check your linux FS. > ask you this next question, but, you never know. I have the same problem > with linux. I can't mount my BSD partition from linux. what would the fs > type be? And how can I add support for the fs type? I don't know too. The docs say it is supported, but linux doesn't recognize the BSD partitions (the subdivisions in the primary BSD slice). > OS: FreeBSD 2.2.2 > RAM: 24mb > HD: 1 maxtor 2.0GB (IDE) > 1 Samsung 2.1GB (IDE) > CDROM: ATAPI IDE 6x Robert > mml@sunlink.net -- Robert Eckardt \\ FreeBSD -- solutions for a large universe.(tm) RobertE@MEP.Ruhr-Uni-Bochum.de \\ What do you want to boot tomorrow ?(tm) http://WWW.MEP.Ruhr-Uni-Bochum.de/~roberte For PGP-key finger roberte@gluon.MEP.Ruhr-Uni-Bochum.de From owner-freebsd-hackers Sat Oct 4 06:16:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA15745 for hackers-outgoing; Sat, 4 Oct 1997 06:16:42 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA15740 for ; Sat, 4 Oct 1997 06:16:36 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id OAA12951 for hackers@FreeBSD.ORG; Sat, 4 Oct 1997 14:00:10 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.7/8.8.7) id OAA07496; Sat, 4 Oct 1997 14:45:24 +0200 (CEST) Message-ID: <19971004144524.34098@klemm.gtn.com> Date: Sat, 4 Oct 1997 14:45:24 +0200 From: Andreas Klemm To: hackers@FreeBSD.ORG Subject: application/x-tcl: netscape plugin for Linux not running Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi ! Wanted to browse the demos on: http://www.tcltk.com/tclets/ Then a Netscape popup box leads me to: http://www.sun.com/960710/cover/dlplugin.html I registered and downloaded the binary version for Linux which comes closest to FreeBSD as binary format. I tried both, the system wide installation and the user installation. Netscape even doesn't seem to find the plugin ... When trying to insert this into the applications manually Preferences->Applications->New In "Handeled By" the "Plug In:" field is still not active.. Is it possibly to let a Linux binary run as plugin ? Or is there something in sight, that there will be a FreeBSD version ?! Andreas /// -- Andreas Klemm powered by ,,symmetric multiprocessor FreeBSD'' andreas@klemm.gtn.com - http://www.freebsd.org/~fsmp/SMP/SMP.html andreas@FreeBSD.ORG - http://www.freebsd.org/~fsmp/SMP/benches.html From owner-freebsd-hackers Sat Oct 4 07:08:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA17051 for hackers-outgoing; Sat, 4 Oct 1997 07:08:29 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA17046 for ; Sat, 4 Oct 1997 07:08:25 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id XAA01406; Sat, 4 Oct 1997 23:33:49 +0930 (CST) Message-Id: <199710041403.XAA01406@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Andreas Klemm cc: hackers@FreeBSD.ORG Subject: Re: application/x-tcl: netscape plugin for Linux not running In-reply-to: Your message of "Sat, 04 Oct 1997 14:45:24 +0200." <19971004144524.34098@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 04 Oct 1997 23:33:47 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I registered and downloaded the binary version for Linux > which comes closest to FreeBSD as binary format. > > I tried both, the system wide installation and the user > installation. Netscape even doesn't seem to find the > plugin ... You cannot generally mix and match ABIs in a single binary, ie. expect a Linux shared library to work linked against a FreeBSD executable. > Is it possibly to let a Linux binary run as plugin ? You would have to run the Linux Netscape for this. > Or is there something in sight, that there will be a FreeBSD > version ?! There is some expectation that there will be a FreeBSD version of the Tcl plugin, yes. mike From owner-freebsd-hackers Sat Oct 4 07:10:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA17162 for hackers-outgoing; Sat, 4 Oct 1997 07:10:37 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA17153 for ; Sat, 4 Oct 1997 07:10:34 -0700 (PDT) Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id GAA20076; Sat, 4 Oct 1997 06:54:59 -0700 (PDT) To: Andreas Klemm cc: hackers@FreeBSD.ORG Subject: Re: application/x-tcl: netscape plugin for Linux not running In-reply-to: Your message of "Sat, 04 Oct 1997 14:45:24 +0200." <19971004144524.34098@klemm.gtn.com> Date: Sat, 04 Oct 1997 06:54:59 -0700 Message-ID: <20072.875973299@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Or is there something in sight, that there will be a FreeBSD > version ?! Yeah, I had one working here for awhile that the Sun folks gave me, but we encountered some fairly major difficulties with it and, last I heard, they'd gone back to look at it some more (and I'm also not sure that Netscape 4.0's plugin support for FreeBSD is exactly 100% there yet either). Jordan From owner-freebsd-hackers Sat Oct 4 07:15:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA17374 for hackers-outgoing; Sat, 4 Oct 1997 07:15:55 -0700 (PDT) Received: from hq.icb.chel.su (hq.icb.chel.su [193.125.10.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA17363 for ; Sat, 4 Oct 1997 07:15:37 -0700 (PDT) Received: (babkin@localhost) by hq.icb.chel.su (8.8.3/8.6.5) id UAA09967 for hackers@freebsd.org; Sat, 4 Oct 1997 20:05:25 +0600 (ESD) From: "Serge A. Babkin" Message-Id: <199710041405.UAA09967@hq.icb.chel.su> Subject: PCI slowness ? To: hackers@freebsd.org Date: Sat, 4 Oct 1997 20:05:25 +0600 (ESD) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi! I've made a simple driver to test the SCSI throughput. It takes 2 NCR53c810A SCSI cards and starts to transfer data between them at (theoretically) 10MBps synchronous rate. But in fact I get at most 8.5MBps ! I was able to rase it from 7.5MBps to 8.5MBps by changing the memory access options in NCRs from simplest to maximal optimization so probably the PCI or memory bus limits the throughput. Can anyone suggest me what's the problem ? The chipset is Intel Triton on some chineese motherboard with 75MHz Pentium, memory is 60ns EDO. Theoretical PCI throughput is 33M of 4-byte transfers per second (the card claims to work in burst mode). Theoretical memory throughput is at least 10M of 4-byte transfers per second if we suppose that the memory cycle with all overhead is 100ns and the card reads by 4 bytes at a time. But the experiment shows throughput of only 17MBps or 4.25M of 4 byte transfers. Does the processor eats all the remaining throughput (although I think it must load most of the code it runs at idling into the cache) ? And another thing. I know that expensive machines like DEC Prioris have possibilities to change some PCI timing parameters for PCI cards. My cheap box does not have anything like. May be that's the problem ? Thanks for any clue! -SB From owner-freebsd-hackers Sat Oct 4 07:56:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA18638 for hackers-outgoing; Sat, 4 Oct 1997 07:56:48 -0700 (PDT) Received: from dcarmich.pr.mcs.net (dcarmich.pr.mcs.net [204.95.63.202]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA18627; Sat, 4 Oct 1997 07:56:43 -0700 (PDT) Received: (from dcarmich@localhost) by dcarmich.pr.mcs.net (8.8.5/8.8.5) id JAA00302; Sat, 4 Oct 1997 09:46:56 -0500 (CDT) From: Douglas Carmichael Message-Id: <199710041446.JAA00302@dcarmich.pr.mcs.net> Subject: FreeBSD 2.2.2-RELEASE kernel compiled with pgcc failed to boot To: phk@freebsd.org Date: Sat, 4 Oct 1997 09:46:56 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk When I tried compiling a kernel with -O -mpentium as the options in Makefile.i386, the compile went smoothly (i.e. didn't die) after removing NFS from the kernel config file, but when I tried to boot the new kernel, it showed the normal messages for a while, but then my screen got all scrambled and then my machine rebooted. Here's the config file: # My new kernel configuration (10/3/97) machine "i386" cpu "I586_CPU" ident NECVERSA-PGCC maxusers 60 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options MFS #Memory Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options SYSVSHM options SYSVSEM options SYSVMSG # laptop-specific configuration options LAPTOP # If your laptop have not had Windoze95-Ready BIOS, please update it. # Such old BIOS'es sometimes have critical bugs at 32-bit protected # mode APM BIOS interface (which have not used by Windoze 3.1). # PC-card suspend/resume support (experimental) options APM_PCCARD_RESUME options PCIC_RESUME_RESET # Keep power for serial cards when the system suspends # (If your machine hangs up when you try to suspend the system with # FAX/Modem PCMCIA card, uncomment this option). #options SIO_SUSP_KEEP_PWR # Detach SCSI devices when the SCSI card is removed options SCSI_DETACH # Don't suspend the system immediately before the system is resumed # from suspended mode (Default 3 seconds) options "APM_NOSUSPEND_IMMEDIATE=3" config kernel root on wd0 controller isa0 controller pci0 controller crd0 device pcic0 at crd? device pcic1 at crd? controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device wcd0 #IDE CD-ROM device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr # # Laptop support (see LINT for more options) # device apm0 at isa? # Advanced Power Management options APM_BROKEN_STATCLOCK # Workaround some buggy APM BIOS device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device sio2 at isa? port "IO_COM3" tty irq 9 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr # Sound devices controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr options SBC_IRQ=5 device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 device opl0 at isa? port 0x388 # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. pseudo-device loop pseudo-device speaker pseudo-device ppp 2 pseudo-device tun 2 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's pseudo-device vn #Vnode driver (turns a file into a device) Here's the version of Pentium-GCC: Reading specs from /usr/local/lib/gcc-lib/pentium-freebsd/2.7.2p/specs gcc version 2.7.2p snapshot 970721 What gives? From owner-freebsd-hackers Sat Oct 4 08:05:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA18967 for hackers-outgoing; Sat, 4 Oct 1997 08:05:49 -0700 (PDT) Received: from dcarmich.pr.mcs.net (dcarmich.pr.mcs.net [204.95.63.202]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA18961; Sat, 4 Oct 1997 08:05:42 -0700 (PDT) Received: (from dcarmich@localhost) by dcarmich.pr.mcs.net (8.8.5/8.8.5) id KAA00373; Sat, 4 Oct 1997 10:08:59 -0500 (CDT) From: Douglas Carmichael Message-Id: <199710041508.KAA00373@dcarmich.pr.mcs.net> Subject: More developments in the kernel compile with Pentium-GCC To: phk@freebsd.org, freebsd-hackers@freebsd.org Date: Sat, 4 Oct 1997 10:08:59 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk When I boot it with no options, it panics with the message "Fatal double fault" and then does: Syncing disks...... and then reboots. However, when I boot with the -v option, it boots and runs fine (as I can see) and runs as fast as a bat out of h*** compared to the normal FreeBSD kernel. My machine is an NEC Versa 6050MH laptop with a Pentium/150 MMX processor. Here's my dmesg when booting with -v: Copyright (c) 1992-1997 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.2-RELEASE #0: Sat Oct 4 09:31:15 CDT 1997 dcarmich@dcarmich.pr.mcs.net:/usr/src/sys/compile/NECVERSA-PGCC Calibrating clock(s) ... i586 clock: 150869998 Hz, i8254 clock: 1193325 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency CLK_USE_I586_CALIBRATION not specified - using old calibration method CPU: Pentium (150.85-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x544 Stepping=4 Features=0x8001bf real memory = 50331648 (49152K bytes) avail memory = 47575040 (46460K bytes) Initializing PC-card drivers: sio wdc pcibus_setup(1): mode 1 addr port (0x0cf8) is 0x00000000 pcibus_setup(1a): mode1res=0x80000000 (0x80000000) pcibus_check: device 0 is there (id=12358086) Probing for devices on PCI bus 0: configuration mode 1 allows 32 devices. chip0 rev 2 on pci0:0 chip1 rev 3 on pci0:1 vga0 rev 69 on pci0:2 mapreg[10] type=0 addr=3e000000 size=1000000. pcic0 rev 4 int a irq ?? on pci0:3:0 mapreg[14] type=0 addr=02000000 size=fe000000. CardBus: Legacy PC-card 16bit I/O address [0x3e0] PCI Config space: 00: ac12104c 02000047 06070004 00820000 10: 00000000 02000000 00000000 00000000 20: 00000000 00000000 00000000 00000000 30: 00000000 00000000 00000000 00c001ff 40: 00000000 000003e1 00000000 00000000 50: 00000000 00000000 00000000 00000000 60: 00000000 00000000 00000000 00000000 70: 00000000 00000000 00000000 00000000 80: 00041020 00000000 00000000 00000000 90: 00720200 00000000 00000000 00000000 Cardbus Socket registers: 00: f00047e0: f00047e0: f000e2c3: f00047e0: 10: f00047e0: f000ff54: f000ea79: f000ea21: ExCa registers: 00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 pcic1 rev 4 int b irq ?? on pci0:3:1 mapreg[14] type=0 addr=02000000 size=fe000000. CardBus: Legacy PC-card 16bit I/O address [0x3e0] PCI Config space: 00: ac12104c 02000047 06070004 00820000 10: 00000000 02000000 00000000 00000000 20: 00000000 00000000 00000000 00000000 30: 00000000 00000000 00000000 00c002ff 40: 00000000 000003e1 00000000 00000000 50: 00000000 00000000 00000000 00000000 60: 00000000 00000000 00000000 00000000 70: 00000000 00000000 00000000 00000000 80: 00041020 00000000 00000000 00000000 90: 00720200 00000000 00000000 00000000 Cardbus Socket registers: 00: f00047e0: f00047e0: f000e2c3: f00047e0: 10: f00047e0: f000ff54: f000ea79: f000ea21: ExCa registers: 00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 pci0: uses -50331648 bytes of memory from 2000000 upto ffffffff. Probing for devices on the ISA bus: sc0: the current keyboard controller command byte 0047 kbdio: RESET_KBD return code:00fa kbdio: RESET_KBD status:00aa sc0 at 0x60-0x6f irq 1 on motherboard sc0: BIOS video mode:3 sc0: VGA registers upon power-up 50 18 10 00 10 01 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 ff ff 9c 0e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 00 00 00 00 00 00 10 0e 00 ff sc0: video mode:24 sc0: VGA color <16 virtual consoles, flags=0x0> 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 9 on isa sio2: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0: current command byte:0047 kbdio: TEST_AUX_PORT status:0000 kbdio: RESET_AUX return code:00fa kbdio: RESET_AUX status:00aa kbdio: RESET_AUX ID:0000 psm0: status after reset 00 02 64 psm: status 00 00 64 (get_mouse_buttons) psm0: status 00 02 64 psm0 at 0x60-0x64 irq 12 on motherboard psm0: device ID 0, 2 buttons fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 1376MB (2818368 sectors), 2796 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (atapi): , removable, accel, dma, iordy wcd0: 1722Kb/sec, 128Kb cache, audio play, 255 volume levels, ejectable tray wcd0: no disc inside, unlocked npx0 on motherboard npx0: INT 16 interface apm0 on isa apm: found APM BIOS version 1.1 sb0 at 0x220 irq 5 drq 1 on isa sb0: sbxvi0 at 0x0 drq 5 on isa sbxvi0: sbmidi0 at 0x330 on isa opl0 at 0x388 on isa opl0: imasks: bio c0004040, tty c003129a, net c0020000 PC-Card TI PCI-1130 [i82365 compatible mode] (5 mem & 2 I/O windows) pcic: controller irq 10 BIOS Geometries: 0:02b93f3f 0..697=698 cylinders, 0..63=64 heads, 1..63=63 sectors 0 accounted for Device configuration finished. Considering FFS root f/s. configure() finished. new masks: bio c0004040, tty c003129a, net c003129a wd0s1: type 0xa5, start 63, end = 2818367, size 2818305 : OK From owner-freebsd-hackers Sat Oct 4 08:45:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA20460 for hackers-outgoing; Sat, 4 Oct 1997 08:45:21 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA20453 for ; Sat, 4 Oct 1997 08:45:08 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id QAA27691; Sat, 4 Oct 1997 16:15:12 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.7/8.8.7) id QAA12251; Sat, 4 Oct 1997 16:53:59 +0200 (CEST) Message-ID: <19971004165359.35574@klemm.gtn.com> Date: Sat, 4 Oct 1997 16:53:59 +0200 From: Andreas Klemm To: Mike Smith Cc: hackers@FreeBSD.ORG Subject: Re: application/x-tcl: netscape plugin for Linux not running References: <19971004144524.34098@klemm.gtn.com> <199710041403.XAA01406@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199710041403.XAA01406@word.smith.net.au>; from Mike Smith on Sat, Oct 04, 1997 at 11:33:47PM +0930 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, Oct 04, 1997 at 11:33:47PM +0930, Mike Smith wrote: > You cannot generally mix and match ABIs in a single binary, ie. expect > a Linux shared library to work linked against a FreeBSD executable. Had already that feeling ... > You would have to run the Linux Netscape for this. Doesn't run very stable here on -current. Often hangs. But will check it's ability to run this tcl stuff. Thanks. -- Andreas Klemm powered by ,,symmetric multiprocessor FreeBSD'' andreas@klemm.gtn.com - http://www.freebsd.org/~fsmp/SMP/SMP.html andreas@FreeBSD.ORG - http://www.freebsd.org/~fsmp/SMP/benches.html From owner-freebsd-hackers Sat Oct 4 09:07:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA21247 for hackers-outgoing; Sat, 4 Oct 1997 09:07:50 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA21237; Sat, 4 Oct 1997 09:07:13 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id BAA01775; Sun, 5 Oct 1997 01:34:30 +0930 (CST) Message-Id: <199710041604.BAA01775@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Douglas Carmichael cc: phk@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: More developments in the kernel compile with Pentium-GCC In-reply-to: Your message of "Sat, 04 Oct 1997 10:08:59 EST." <199710041508.KAA00373@dcarmich.pr.mcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 05 Oct 1997 01:34:29 +0930 From: Mike Smith Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > When I boot it with no options, it panics with the message "Fatal double fault" and then does: ... > However, when I boot with the -v option, it boots and runs fine (as I can see) and runs as fast as a bat out of h*** compared to the normal FreeBSD kernel. "pgcc produces fast but wrong code" - we have known this for some time. What would be more helpful would be for you to help the pgcc people fix their code generation so that it produced fast and correct code. 8) mike From owner-freebsd-hackers Sat Oct 4 09:47:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA22987 for hackers-outgoing; Sat, 4 Oct 1997 09:47:03 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA22982 for ; Sat, 4 Oct 1997 09:46:57 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id RAA04659 for hackers@FreeBSD.ORG; Sat, 4 Oct 1997 17:30:15 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.7/8.8.7) id SAA03396; Sat, 4 Oct 1997 18:28:55 +0200 (CEST) (envelope-from andreas) Message-ID: <19971004182854.38375@klemm.gtn.com> Date: Sat, 4 Oct 1997 18:28:54 +0200 From: Andreas Klemm To: hackers@FreeBSD.ORG Subject: SpecTcl needs java, which port to use for this ? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As the subject says ... -- Andreas Klemm powered by ,,symmetric multiprocessor FreeBSD'' andreas@klemm.gtn.com - http://www.freebsd.org/~fsmp/SMP/SMP.html andreas@FreeBSD.ORG - http://www.freebsd.org/~fsmp/SMP/benches.html From owner-freebsd-hackers Sat Oct 4 09:56:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA23500 for hackers-outgoing; Sat, 4 Oct 1997 09:56:55 -0700 (PDT) Received: from thelab.hub.org (ppp-146.halifax-01.ican.net [206.231.248.146]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA23483 for ; Sat, 4 Oct 1997 09:56:39 -0700 (PDT) Received: from thelab.hub.org (localhost [127.0.0.1]) by thelab.hub.org (8.8.7/8.8.2) with SMTP id NAA23023 for ; Sat, 4 Oct 1997 13:56:28 -0300 (ADT) Date: Sat, 4 Oct 1997 13:56:28 -0300 (ADT) From: The Hermit Hacker To: hackers@freebsd.org Subject: Netscape 4.03b8 and Encryption: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ============================= Insufficient encryption This document requires a larger secret key size for encryption than your browser is capable of supporting. ============================= Has anyone seen this before? I'm trying to access my bank account, through the web, using Netscape 4.03b8 under FreeBSD 3.0-CURRENT. I can do it using 4.03 under Win95 *ick* but it fails through FreeBSD :( Any ideas? Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org From owner-freebsd-hackers Sat Oct 4 10:09:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA24362 for hackers-outgoing; Sat, 4 Oct 1997 10:09:35 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA24356 for ; Sat, 4 Oct 1997 10:09:30 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.7/8.8.5) with ESMTP id KAA06983; Sat, 4 Oct 1997 10:09:17 -0700 (PDT) Message-Id: <199710041709.KAA06983@rah.star-gate.com> To: Andreas Klemm cc: hackers@FreeBSD.ORG Subject: Re: application/x-tcl: netscape plugin for Linux not running In-reply-to: Your message of "Sat, 04 Oct 1997 14:45:24 +0200." <19971004144524.34098@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 04 Oct 1997 10:09:17 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Well, I think that you can download the tcl plugin sources and compile it for FreeBSD 8) Cheers, Amancio >From The Desk Of Andreas Klemm : > Hi ! > > Wanted to browse the demos on: > > http://www.tcltk.com/tclets/ > > Then a Netscape popup box leads me to: > > http://www.sun.com/960710/cover/dlplugin.html > > I registered and downloaded the binary version for Linux > which comes closest to FreeBSD as binary format. > > I tried both, the system wide installation and the user > installation. Netscape even doesn't seem to find the > plugin ... > > When trying to insert this into the applications manually > > Preferences->Applications->New > In "Handeled By" the "Plug In:" field > is still not active.. > > Is it possibly to let a Linux binary run as plugin ? > > Or is there something in sight, that there will be a FreeBSD > version ?! > > Andreas /// > > -- > Andreas Klemm powered by ,,symmetric multiprocessor FreeBS D'' > andreas@klemm.gtn.com - http://www.freebsd.org/~fsmp/SMP/SMP.html > andreas@FreeBSD.ORG - http://www.freebsd.org/~fsmp/SMP/benches.h tml > From owner-freebsd-hackers Sat Oct 4 10:12:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA24703 for hackers-outgoing; Sat, 4 Oct 1997 10:12:58 -0700 (PDT) Received: from server.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA24693 for ; Sat, 4 Oct 1997 10:12:52 -0700 (PDT) Received: from localhost (perlsta@localhost) by server.local.sunyit.edu (8.8.7/8.8.5) with SMTP id NAA00208 for ; Sat, 4 Oct 1997 13:18:01 -0500 (EST) X-Authentication-Warning: server.local.sunyit.edu: perlsta owned process doing -bs Date: Sat, 4 Oct 1997 13:18:01 -0500 (EST) From: Alfred Perlstein X-Sender: perlsta@server.local.sunyit.edu To: hackers@FreeBSD.org Subject: booting via serial device? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I'm having a little trouble getting FreeBSD to boot to a serial port, i have my second serial port null modem'd to a win95 PC, when i: echo whatever > /dev/ttyd1 it comes across, however when i try the combination of -D and -h flags at the "boot:" prompt i get nothing. am i using the wrong boot flags? how do i tell it to use the second serial port? if FreeBSD expecting the connection to be on the first serial port? and what kind of terminal emulation should i use on the terminal, i think ANSI is correct? right? any help with this would be great, thank you, .________________________________________________________________________ __ _ |Alfred Perlstein - Programming & SysAdmin --"Have you seen my FreeBSD tatoo?" |perlsta@sunyit.edu --"who was that masked admin?" |http://www.cs.sunyit.edu/~perlsta : ' From owner-freebsd-hackers Sat Oct 4 10:29:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA25814 for hackers-outgoing; Sat, 4 Oct 1997 10:29:51 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA25801 for ; Sat, 4 Oct 1997 10:29:43 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id SAA08726 for hackers@FreeBSD.ORG; Sat, 4 Oct 1997 18:15:04 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.7/8.8.7) id TAA06435; Sat, 4 Oct 1997 19:09:29 +0200 (CEST) (envelope-from andreas) Message-ID: <19971004190929.38979@klemm.gtn.com> Date: Sat, 4 Oct 1997 19:09:29 +0200 From: Andreas Klemm To: hackers@FreeBSD.ORG Subject: Re: application/x-tcl: netscape plugin for Linux not running References: <19971004144524.34098@klemm.gtn.com> <199710041403.XAA01406@word.smith.net.au> <19971004165359.35574@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <19971004165359.35574@klemm.gtn.com>; from Andreas Klemm on Sat, Oct 04, 1997 at 04:53:59PM +0200 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, Oct 04, 1997 at 04:53:59PM +0200, Andreas Klemm wrote: > On Sat, Oct 04, 1997 at 11:33:47PM +0930, Mike Smith wrote: > > > You cannot generally mix and match ABIs in a single binary, ie. expect > > a Linux shared library to work linked against a FreeBSD executable. > > Had already that feeling ... > > > You would have to run the Linux Netscape for this. > > Doesn't run very stable here on -current. Often hangs. > But will check it's ability to run this tcl stuff. Thanks. linux-netscape4 doesn't find the linux tclplugin either. Tried both, site wide and easy-install. Even setting these env variables didn't help... # # TCL plugin # setenv NPX_PLUGIN_PATH /home/andreas/.netscape/plugins setenv TCL_PLUGIN_DIR /home/andreas/.tclplug -- Andreas Klemm powered by ,,symmetric multiprocessor FreeBSD'' andreas@klemm.gtn.com - http://www.freebsd.org/~fsmp/SMP/SMP.html andreas@FreeBSD.ORG - http://www.freebsd.org/~fsmp/SMP/benches.html From owner-freebsd-hackers Sat Oct 4 10:30:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA25952 for hackers-outgoing; Sat, 4 Oct 1997 10:30:45 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA25935 for ; Sat, 4 Oct 1997 10:30:42 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.7/8.8.5) with ESMTP id KAA07158; Sat, 4 Oct 1997 10:30:19 -0700 (PDT) Message-Id: <199710041730.KAA07158@rah.star-gate.com> to: Robert Shady cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Video-Capture In-reply-to: Your message of "Fri, 03 Oct 1997 19:19:46 PDT." <199710040219.TAA06529@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 04 Oct 1997 10:30:19 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >From The Desk Of Amancio Hasty : > Questions related to video and/or audio to the multimedia mailing list: > multimedia@freebsd.org > > We can capture 640x480 32bits at 30fps with Bt848 based cards such > as the WinCast TV PCI for further info visit the Bt848 project web page: > > http://www.freebsd.org/~hasty/Bt848.html Oops, the http pointer is: http://www.freebsd.org/~ahasty/Bt848.html Under the Applications section there is a pointer to an mpeg movie generated with fxtv 8) Amancio From owner-freebsd-hackers Sat Oct 4 10:40:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA26520 for hackers-outgoing; Sat, 4 Oct 1997 10:40:41 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA26512 for ; Sat, 4 Oct 1997 10:40:38 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.7/8.8.5) with ESMTP id KAA07288; Sat, 4 Oct 1997 10:40:01 -0700 (PDT) Message-Id: <199710041740.KAA07288@rah.star-gate.com> To: Andreas Klemm cc: hackers@FreeBSD.ORG Subject: Re: SpecTcl needs java, which port to use for this ? In-reply-to: Your message of "Sat, 04 Oct 1997 18:28:54 +0200." <19971004182854.38375@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 04 Oct 1997 10:40:01 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I don't think so . Spectcl is written in TCL and can generate target code for tcl or java . Amancio >From The Desk Of Andreas Klemm : > As the subject says ... > > -- > Andreas Klemm powered by ,,symmetric multiprocessor FreeBS D'' > andreas@klemm.gtn.com - http://www.freebsd.org/~fsmp/SMP/SMP.html > andreas@FreeBSD.ORG - http://www.freebsd.org/~fsmp/SMP/benches.h tml > From owner-freebsd-hackers Sat Oct 4 10:54:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA27295 for hackers-outgoing; Sat, 4 Oct 1997 10:54:35 -0700 (PDT) Received: from ptway.com (apollo.ptway.com [199.176.148.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA27288 for ; Sat, 4 Oct 1997 10:54:30 -0700 (PDT) Received: from brianjr.haskin.org (219R1.ptway.com [199.176.148.86]) by ptway.com (8.7.1/3.4W4-PTWAY-sco-ODT3.0) with ESMTP id NAA09776; Sat, 4 Oct 1997 13:46:56 -0400 (EDT) Message-ID: <3436829A.BA613792@ptway.com> Date: Sat, 04 Oct 1997 13:53:30 -0400 From: Brian Haskin X-Mailer: Mozilla 4.01 [en] (Win95; I) MIME-Version: 1.0 To: The Hermit Hacker CC: FreeBSD-Hackers Subject: Re: Netscape 4.03b8 and Encryption: X-Priority: 3 (Normal) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The Hermit Hacker wrote: > > ============================= > Insufficient encryption > > This document requires a larger secret key size for encryption than > your > browser is capable of supporting. > ============================= > > Has anyone seen this before? I'm trying to access my bank account, > through > the web, using Netscape 4.03b8 under FreeBSD 3.0-CURRENT. I can do it > using > 4.03 under Win95 *ick* but it fails through FreeBSD :( > > Any ideas? > > Marc G. Fournier > Systems Administrator @ hub.org > primary: scrappy@hub.org secondary: > scrappy@{freebsd|postgresql}.org Unfortunately the beta put out by netscape only has the weaker international 40 bit encryption (last I heard anyway). Which is fairly easy to break and is the reason your bank doesn't want you useing this to connect with them. Brian Haskin From owner-freebsd-hackers Sat Oct 4 11:12:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA28576 for hackers-outgoing; Sat, 4 Oct 1997 11:12:59 -0700 (PDT) Received: from ns2.harborcom.net (root@ns2.harborcom.net [206.158.4.4]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA28569 for ; Sat, 4 Oct 1997 11:12:56 -0700 (PDT) Received: from localhost (bradley@localhost) by ns2.harborcom.net (8.8.7/8.8.5) with SMTP id OAA29325; Sat, 4 Oct 1997 14:12:42 -0400 (EDT) Date: Sat, 4 Oct 1997 14:12:42 -0400 (EDT) From: Bradley Dunn X-Sender: bradley@ns2.harborcom.net To: The Hermit Hacker cc: hackers@FreeBSD.ORG Subject: Re: Netscape 4.03b8 and Encryption: In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 4 Oct 1997, The Hermit Hacker wrote: > ============================= > Insufficient encryption > > This document requires a larger secret key size for encryption than your > browser is capable of supporting. > ============================= Mail Netscape and ask them when/if they will have a US/Canada version with support for 128-bit encryption keys for FreeBSD. pbd -- "Seems she thought of me as some mystic, fatalistic, mystical guru Me, I haven't got a clue." -- Tears for Fears, "Cold" From owner-freebsd-hackers Sat Oct 4 11:37:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA00153 for hackers-outgoing; Sat, 4 Oct 1997 11:37:31 -0700 (PDT) Received: from pcpsj.pfcs.com (LoJJ+nUvDWK3bA4dfCWZVddbEDwKqp/4@harlan.fred.net [205.252.219.31]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA00135; Sat, 4 Oct 1997 11:37:11 -0700 (PDT) Received: from mumps.pfcs.com (mumps.pfcs.com [192.52.69.11]) by pcpsj.pfcs.com (8.8.6/8.6.9) with SMTP id OAA21892; Sat, 4 Oct 1997 14:36:50 -0400 (EDT) Received: from localhost by mumps.pfcs.com with SMTP id AA04598 (5.67b/IDA-1.5); Sat, 4 Oct 1997 14:36:49 -0400 To: Mike Smith Cc: Douglas Carmichael , phk@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: More developments in the kernel compile with Pentium-GCC In-Reply-To: Your message of "Sun, 05 Oct 1997 01:34:29 +0930." <199710041604.BAA01775@word.smith.net.au> Date: Sat, 04 Oct 1997 14:36:47 -0300 Message-Id: <4596.875990207@mumps.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Has anybody used a current release of egcs instead of pgcc? The ports collection versions of pgcc in 2.2-stable look for patch files that just aren't there anymore. If I get the time, I might try compiling a kernel with egcs this weekend (I just got the latest version compiled on a -stable box last night). H From owner-freebsd-hackers Sat Oct 4 11:43:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA00442 for hackers-outgoing; Sat, 4 Oct 1997 11:43:22 -0700 (PDT) Received: from srv.net (snake.srv.net [199.104.81.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA00427; Sat, 4 Oct 1997 11:42:19 -0700 (PDT) Received: from darkstar.home (dialin1.anlw.anl.gov [141.221.254.101]) by srv.net (8.8.5/8.8.5) with SMTP id MAA26286; Sat, 4 Oct 1997 12:42:05 -0600 (MDT) Date: Sat, 4 Oct 1997 11:41:26 -0700 (MST) From: Charles Mott X-Sender: cmott@darkstar.home To: freebsd-hackers@freebsd.org cc: ari@suutari.iki.fi, brian@freebsd.org Subject: link tables and scope Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a question regarding linker tables created for libraries. In the packet aliasing library (libalias) used by ppp and natd, there are two header files in the source, alias.h and alias_local.h. The first contains "public" interfaces and the second is basically a set of function prototypes used between different modules within the library source, but not intended for public access. What I observe is that the link symbol table (I don't know a better word for it), contains function names both in alias.h and alias_local.h. Is there any way to somehow restrict the scope of some globals in a library so that they cannot be linked by modules outside the library. The only way I know to do this is put the entire library in a single file and make as much as possible static. Charles Mott From owner-freebsd-hackers Sat Oct 4 11:59:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA01243 for hackers-outgoing; Sat, 4 Oct 1997 11:59:48 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA01229 for ; Sat, 4 Oct 1997 11:59:23 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id TAA17522; Sat, 4 Oct 1997 19:45:11 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.7/8.8.7) id UAA14115; Sat, 4 Oct 1997 20:34:43 +0200 (CEST) (envelope-from andreas) Message-ID: <19971004203442.65007@klemm.gtn.com> Date: Sat, 4 Oct 1997 20:34:42 +0200 From: Andreas Klemm To: Amancio Hasty Cc: hackers@FreeBSD.ORG Subject: Re: SpecTcl needs java, which port to use for this ? References: <19971004182854.38375@klemm.gtn.com> <199710041740.KAA07288@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199710041740.KAA07288@rah.star-gate.com>; from Amancio Hasty on Sat, Oct 04, 1997 at 10:40:01AM -0700 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, Oct 04, 1997 at 10:40:01AM -0700, Amancio Hasty wrote: > I don't think so . Spectcl is written in TCL and can generate target code > for tcl or java . There is a separate specJava script to start wish -java or such ... Then a popup comes and says: Can't find java in your path, Java testing and help will be disabled. It seems to be the case, that without java you are missing some of the ports functionality. -- Andreas Klemm powered by ,,symmetric multiprocessor FreeBSD'' andreas@klemm.gtn.com - http://www.freebsd.org/~fsmp/SMP/SMP.html andreas@FreeBSD.ORG - http://www.freebsd.org/~fsmp/SMP/benches.html From owner-freebsd-hackers Sat Oct 4 12:14:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA02037 for hackers-outgoing; Sat, 4 Oct 1997 12:14:24 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA02027 for ; Sat, 4 Oct 1997 12:14:19 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.7/8.8.5) with ESMTP id MAA07756; Sat, 4 Oct 1997 12:13:58 -0700 (PDT) Message-Id: <199710041913.MAA07756@rah.star-gate.com> To: Andreas Klemm cc: hackers@FreeBSD.ORG Subject: Re: SpecTcl needs java, which port to use for this ? In-reply-to: Your message of "Sat, 04 Oct 1997 20:34:42 +0200." <19971004203442.65007@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 04 Oct 1997 12:13:58 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk If you try to use the Java components of course it is going to look or ask for Java however if you start up specTcl and use tk8.0 at the very least SpecTcl should start up and you can play with it. ./specTcl Starting SpecTcl 1.1 more specTcl #!/bin/sh SpecTcl # Copyright (c) 1994-1997 Sun Microsystems, Inc. # # See the file "license.txt" for information on usage and redistribution # of this file, and for a DISCLAIMER OF ALL WARRANTIES. # # SCCS: @(#) specTcl 1.9 97/06/26 10:06:06 # Change DIR to the directory that contains the SpecTcl source files DIR=../SpecTcl # Change WISH to the pathname of your tk4.1a2 (or >) wish binary WISH=`which wish8.0` env SPECTCL_DIR=$DIR $WISH $DIR/main.tk $@ & echo "Starting SpecTcl 1.1" exit 0 Amancio >From The Desk Of Andreas Klemm : > On Sat, Oct 04, 1997 at 10:40:01AM -0700, Amancio Hasty wrote: > > I don't think so . Spectcl is written in TCL and can generate target code > > for tcl or java . > > There is a separate specJava script to start wish -java or such ... > Then a popup comes and says: > > Can't find java in your path, Java testing and help will be disabled. > > It seems to be the case, that without java you are missing some of > the ports functionality. > > -- > Andreas Klemm powered by ,,symmetric multiprocessor FreeBS D'' > andreas@klemm.gtn.com - http://www.freebsd.org/~fsmp/SMP/SMP.html > andreas@FreeBSD.ORG - http://www.freebsd.org/~fsmp/SMP/benches.h tml From owner-freebsd-hackers Sat Oct 4 12:30:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA02681 for hackers-outgoing; Sat, 4 Oct 1997 12:30:20 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA02673 for ; Sat, 4 Oct 1997 12:30:13 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id UAA19630; Sat, 4 Oct 1997 20:15:06 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.7/8.8.7) id VAA15086; Sat, 4 Oct 1997 21:02:11 +0200 (CEST) (envelope-from andreas) Message-ID: <19971004210211.32240@klemm.gtn.com> Date: Sat, 4 Oct 1997 21:02:11 +0200 From: Andreas Klemm To: Simon Shapiro Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Good Lord, Commercial Linux References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: ; from Simon Shapiro on Tue, Sep 30, 1997 at 08:50:02PM -0700 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi ! On Tue, Sep 30, 1997 at 08:50:02PM -0700, Simon Shapiro wrote: > I still like FreeBSD installation better. The rest is pretty much > the same to me. Can't understand this. Could you please explain it a bit more ? Based on my own experience I can't follow here... > Kernel-wise, I think i trust FreeBSD kernel better than Linux, > although performance is, well, six of this, half a dozen of the > other; Both are tuned very well. Could you please explain this a little more verbose as well. So you are saying that FreeBSD has about half the performance as Linux ? You're kidding ;-) Or did you compare things like the speed of rm -rf on a large directory tree without recognizing, that FreeBSD doesn't do asynchronous I/O to a file system as default ?! Please facts here. -- Andreas Klemm powered by ,,symmetric multiprocessor FreeBSD'' andreas@klemm.gtn.com - http://www.freebsd.org/~fsmp/SMP/SMP.html andreas@FreeBSD.ORG - http://www.freebsd.org/~fsmp/SMP/benches.html From owner-freebsd-hackers Sat Oct 4 12:55:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA03599 for hackers-outgoing; Sat, 4 Oct 1997 12:55:40 -0700 (PDT) Received: from proxy4.ba.best.com (root@proxy4.ba.best.com [206.184.139.15]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA03593 for ; Sat, 4 Oct 1997 12:55:39 -0700 (PDT) Received: from shellx.best.com (shellx.best.com [206.86.0.11]) by proxy4.ba.best.com (8.8.7/8.8.BEST) with ESMTP id MAA07348; Sat, 4 Oct 1997 12:53:45 -0700 (PDT) Received: from localhost (mdean@localhost) by shellx.best.com (8.8.6/8.8.3) with SMTP id MAA23411; Sat, 4 Oct 1997 12:53:44 -0700 (PDT) Date: Sat, 4 Oct 1997 12:53:44 -0700 (PDT) From: mdean To: The Hermit Hacker cc: hackers@FreeBSD.ORG Subject: Re: Netscape 4.03b8 and Encryption: In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Yes --- I do the same thing, you are trying to do bill pay right? There is no netscape 4.0 for freebsd supporting 128 bit encryption (US), you need to get netscape 3.1 for BSD-OS with US (128 bit) encryption. The file should be called netscape-v301gold-us.x86-unknown-bsd.tar.gz and you'll have to fill out a form with your address and p/n to get it from netscape. Use the netscape3 port to install the regualr netscape then, take the encrypted file untar it and copy netscape over netscape.bin that was installed by the port. On Sat, 4 Oct 1997, The Hermit Hacker wrote: > > ============================= > Insufficient encryption > > This document requires a larger secret key size for encryption than your > browser is capable of supporting. > ============================= > > Has anyone seen this before? I'm trying to access my bank account, through > the web, using Netscape 4.03b8 under FreeBSD 3.0-CURRENT. I can do it using > 4.03 under Win95 *ick* but it fails through FreeBSD :( > > Any ideas? > > Marc G. Fournier > Systems Administrator @ hub.org > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org > > From owner-freebsd-hackers Sat Oct 4 13:04:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA04037 for hackers-outgoing; Sat, 4 Oct 1997 13:04:12 -0700 (PDT) Received: from heathers2.stdio.com (kyle@heathers2.stdio.com [204.152.114.165]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA04032 for ; Sat, 4 Oct 1997 13:04:08 -0700 (PDT) Received: (from kyle@localhost) by heathers2.stdio.com (8.6.12/8.6.13) id QAA19384; Sat, 4 Oct 1997 16:02:48 -0400 Date: Sat, 4 Oct 1997 16:02:48 -0400 (EDT) From: Kyle McPeek To: hackers@freebsd.org Subject: Replacing a drive in a ccd array... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a configured ccd array of 8 9GB drives, however one of them is going bad. I have a replacement drive already in the machine. What is the easiest way to replace the drive? I have thought about using dd to copy the data from the old drive to the new one, will this work ok? If so, which device(s) should I copy from/to? Any other suggestions? TIA, kyle. From owner-freebsd-hackers Sat Oct 4 13:12:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA04415 for hackers-outgoing; Sat, 4 Oct 1997 13:12:50 -0700 (PDT) Received: from dog.farm.org (gw-serial2.farm.org [207.111.140.45]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA04405 for ; Sat, 4 Oct 1997 13:12:32 -0700 (PDT) Received: (from dk@localhost) by dog.farm.org (8.7.5/dk#3) id NAA28354; Sat, 4 Oct 1997 13:16:00 -0700 (PDT) Message-ID: <19971004131600.29971@dog.farm.org> Date: Sat, 4 Oct 1997 13:16:00 -0700 From: Dmitry Kohmanyuk =?KOI8-R?B?5M3J1NLJyiDrz8jNwc7Ayw==?= To: "Jay D. Nelson" Cc: Greg Lehey , dk+@ua.net, freebsd-hackers@FreeBSD.ORG Subject: Re: 2nd Notice: 4 days to code freeze in RELENG_2_2 branch. Reply-To: dk+@ua.net References: <19971003170802.12051@lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: ; from "Jay D. Nelson" on Fri, Oct 03, 1997 at 07:41:57PM -0500 X-Class: Fast X-OS-Used: FreeBSD 2.2-960501-SNAP X-NIC-Handle: DK379 X-Pager-Email: dk@interpage.net Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, Oct 03, 1997 at 07:41:57PM -0500, Jay D. Nelson wrote: > Yes, Taylor is better in some respects. I'm not suggesting changing > sample files or anything _except_ uncommenting the HDB capability in > the build. When you are migrating from an older HDB system to FreeBSD, > _and there is no compeling reason_ to use Taylor features, it is > simpler, quicker and more reliable to simply move the config files to > the FreeBSD system and go. Well, since we are now in beta period for 2.2, major changes in core system are not allowed; but this change cannot hurt, and it would be really nice to enable all kinds of config files for folks converting from old uucp installations. Here is the patch (tested); I did diff -U15 so precedent comment is visible. As you can see, enabling all three features is backward-compatible: first, tailor configs are looked up, then V2, then HDB. Patch: --- policy.h.ok Sat Oct 4 12:52:10 1997 +++ policy.h Sat Oct 4 12:52:26 1997 @@ -453,32 +453,32 @@ /* To compile in use of the new style of configuration files described in the documentation, set HAVE_TAYLOR_CONFIG to 1. */ #define HAVE_TAYLOR_CONFIG 1 /* To compile in use of V2 style configuration files (L.sys, L-devices and so on), set HAVE_V2_CONFIG to 1. To compile in use of HDB style configuration files (Systems, Devices and so on) set HAVE_HDB_CONFIG to 1. The files will be looked up in the oldconfigdir directory as defined in the Makefile. You may set any or all of HAVE_TAYLOR_CONFIG, HAVE_V2_CONFIG and HAVE_HDB_CONFIG to 1 (you must set at least one of the macros). When looking something up (a system, a port, etc.) the new style configuration files will be read first, followed by the V2 configuration files, followed by the HDB configuration files. */ -#define HAVE_V2_CONFIG 0 -#define HAVE_HDB_CONFIG 0 +#define HAVE_V2_CONFIG 1 +#define HAVE_HDB_CONFIG 1 /* Exactly one of the following macros must be set to 1. The exact format of the spool directories is explained in unix/spool.c. SPOOLDIR_V2 -- Use a Version 2 (original UUCP) style spool directory SPOOLDIR_BSD42 -- Use a BSD 4.2 style spool directory SPOOLDIR_BSD43 -- Use a BSD 4.3 style spool directory SPOOLDIR_HDB -- Use a HDB (BNU) style spool directory SPOOLDIR_ULTRIX -- Use an Ultrix style spool directory SPOOLDIR_SVR4 -- Use a System V Release 4 spool directory SPOOLDIR_TAYLOR -- Use a new style spool directory If you are not worried about compatibility with a currently running UUCP, use SPOOLDIR_TAYLOR. */ #define SPOOLDIR_V2 0 It is a 2-line change. > > The down side is code size. It will grow a bit. The up side is that > those of us who use it won't have to convert files and can convert > older systems more quickly (and at less cost to a paying client.) > Newbies won't see the change because they won't be using it. Old farts > like me will be happier because we can deal with the same files we > have been using for years. What can it hurt? Code size change is negligible: # size /usr/obj/usr/src/gnu/libexec/uucp/uuxqt/uuxqt /usr/libexec/uucp/uuxqt text data bss dec hex 98304 4096 692 103092 192b4 /usr/obj/usr/src/gnu/libexec/uucp/uuxqt/uuxqt 86016 4096 692 90804 162b4 /usr/libexec/uucp/uuxqt # size /usr/obj/usr/src/gnu/libexec/uucp/uucico/uucico /usr/libexec/uucp/uucico text data bss dec hex 208896 4096 20788 233780 39134 /usr/obj/usr/src/gnu/libexec/uucp/uucico/uucico 192512 4096 20788 217396 35134 /usr/libexec/uucp/uucico # So, how about changing 2 lines and making uucp configs compatible with all of the outside world? From owner-freebsd-hackers Sat Oct 4 13:47:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA06018 for hackers-outgoing; Sat, 4 Oct 1997 13:47:05 -0700 (PDT) Received: from tok.qiv.com (uucp@[204.214.141.211]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA06013 for ; Sat, 4 Oct 1997 13:47:00 -0700 (PDT) Received: (from uucp@localhost) by tok.qiv.com (8.8.6/8.8.5) with UUCP id PAA20466; Sat, 4 Oct 1997 15:45:23 -0500 (CDT) Received: from localhost (jdn@localhost) by acp.qiv.com (8.8.6/8.8.5) with ESMTP id PAA13843; Sat, 4 Oct 1997 15:40:53 -0500 (CDT) X-Authentication-Warning: acp.qiv.com: jdn owned process doing -bs Date: Sat, 4 Oct 1997 15:40:52 -0500 (CDT) From: "Jay D. Nelson" To: dk+@ua.net cc: Greg Lehey , freebsd-hackers@FreeBSD.ORG Subject: Re: 2nd Notice: 4 days to code freeze in RELENG_2_2 branch. In-Reply-To: <19971004131600.29971@dog.farm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Thanks, Dmitry, your argument is much better stated than mine. What we are asking is _not_ a code change but a _comment_ change ;) If not now, how about after 2.2.5 is out the door? -- Jay On Sat, 4 Oct 1997, Dmitry Kohmanyuk [KOI8-R] Дмитрий Кохманюк wrote: > On Fri, Oct 03, 1997 at 07:41:57PM -0500, Jay D. Nelson wrote: > > Yes, Taylor is better in some respects. I'm not suggesting changing > > sample files or anything _except_ uncommenting the HDB capability in > > the build. When you are migrating from an older HDB system to FreeBSD, > > _and there is no compeling reason_ to use Taylor features, it is > > simpler, quicker and more reliable to simply move the config files to > > the FreeBSD system and go. > > Well, since we are now in beta period for 2.2, major changes in core > system are not allowed; but this change cannot hurt, and it would be > really nice to enable all kinds of config files for folks converting > from old uucp installations. > > Here is the patch (tested); I did diff -U15 so precedent comment is > visible. > As you can see, enabling all three features is backward-compatible: > first, tailor configs are looked up, then V2, then HDB. > > Patch: > > --- policy.h.ok Sat Oct 4 12:52:10 1997 > +++ policy.h Sat Oct 4 12:52:26 1997 > @@ -453,32 +453,32 @@ > /* To compile in use of the new style of configuration files described > in the documentation, set HAVE_TAYLOR_CONFIG to 1. */ > #define HAVE_TAYLOR_CONFIG 1 > > /* To compile in use of V2 style configuration files (L.sys, L-devices > and so on), set HAVE_V2_CONFIG to 1. To compile in use of HDB > style configuration files (Systems, Devices and so on) set > HAVE_HDB_CONFIG to 1. The files will be looked up in the > oldconfigdir directory as defined in the Makefile. > > You may set any or all of HAVE_TAYLOR_CONFIG, HAVE_V2_CONFIG and > HAVE_HDB_CONFIG to 1 (you must set at least one of the macros). > When looking something up (a system, a port, etc.) the new style > configuration files will be read first, followed by the V2 > configuration files, followed by the HDB configuration files. */ > -#define HAVE_V2_CONFIG 0 > -#define HAVE_HDB_CONFIG 0 > +#define HAVE_V2_CONFIG 1 > +#define HAVE_HDB_CONFIG 1 > > /* Exactly one of the following macros must be set to 1. The exact > format of the spool directories is explained in unix/spool.c. > > SPOOLDIR_V2 -- Use a Version 2 (original UUCP) style spool directory > SPOOLDIR_BSD42 -- Use a BSD 4.2 style spool directory > SPOOLDIR_BSD43 -- Use a BSD 4.3 style spool directory > SPOOLDIR_HDB -- Use a HDB (BNU) style spool directory > SPOOLDIR_ULTRIX -- Use an Ultrix style spool directory > SPOOLDIR_SVR4 -- Use a System V Release 4 spool directory > SPOOLDIR_TAYLOR -- Use a new style spool directory > > If you are not worried about compatibility with a currently running > UUCP, use SPOOLDIR_TAYLOR. */ > #define SPOOLDIR_V2 0 > > It is a 2-line change. > > > > > The down side is code size. It will grow a bit. The up side is that > > those of us who use it won't have to convert files and can convert > > older systems more quickly (and at less cost to a paying client.) > > Newbies won't see the change because they won't be using it. Old farts > > like me will be happier because we can deal with the same files we > > have been using for years. What can it hurt? > > Code size change is negligible: > > # size /usr/obj/usr/src/gnu/libexec/uucp/uuxqt/uuxqt /usr/libexec/uucp/uuxqt > text data bss dec hex > 98304 4096 692 103092 192b4 /usr/obj/usr/src/gnu/libexec/uucp/uuxqt/uuxqt > 86016 4096 692 90804 162b4 /usr/libexec/uucp/uuxqt > # size /usr/obj/usr/src/gnu/libexec/uucp/uucico/uucico /usr/libexec/uucp/uucico > text data bss dec hex > 208896 4096 20788 233780 39134 /usr/obj/usr/src/gnu/libexec/uucp/uucico/uucico > 192512 4096 20788 217396 35134 /usr/libexec/uucp/uucico > # > > So, how about changing 2 lines and making uucp configs compatible with all > of the outside world? > From owner-freebsd-hackers Sat Oct 4 14:14:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA06973 for hackers-outgoing; Sat, 4 Oct 1997 14:14:43 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA06968 for ; Sat, 4 Oct 1997 14:14:41 -0700 (PDT) Received: from x14.mi.uni-koeln.de ([134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA23107 (5.67b/IDA-1.5 for ); Sat, 4 Oct 1997 23:14:37 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.7/8.6.9) id WAA17607; Sat, 4 Oct 1997 22:12:07 +0200 (CEST) X-Face: " Date: Sat, 4 Oct 1997 22:12:05 +0200 From: Stefan Esser To: "Serge A. Babkin" Cc: hackers@FreeBSD.ORG Subject: Re: PCI slowness ? References: <199710041405.UAA09967@hq.icb.chel.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199710041405.UAA09967@hq.icb.chel.su>; from Serge A. Babkin on Sat, Oct 04, 1997 at 08:05:25PM +0600 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 1997-10-04 20:05 +0600, "Serge A. Babkin" wrote: > Hi! > > I've made a simple driver to test the SCSI throughput. It takes > 2 NCR53c810A SCSI cards and starts to transfer data between them > at (theoretically) 10MBps synchronous rate. But in fact I get at most > 8.5MBps ! I was able to rase it from 7.5MBps to 8.5MBps > by changing the memory access options in NCRs from simplest > to maximal optimization so probably the PCI or memory > bus limits the throughput. Can anyone suggest me what's > the problem ? You don't tell about your actual setup: 1) transfer length ? 2) did disconnects occur ? 3) does the time measurement include the time to prepare the transfer (which may be hidden in most cases) ? Did you take into account, that FAST SCSI uses a 100ns cycle length, which allows for 10mio B/s, or 9.5MB/s ? If you transfer 64KB blocks (which takes 6.7ms at 10MHz) and the SCSI overhead is 1ms, then you'll see an actual transfer rate of 8.3MB/s. > The chipset is Intel Triton on some chineese motherboard > with 75MHz Pentium, memory is 60ns EDO. > Theoretical PCI throughput is 33M > of 4-byte transfers per second (the card claims to work > in burst mode). Theoretical memory throughput is at least > 10M of 4-byte transfers per second if we suppose that > the memory cycle with all overhead is 100ns and the > card reads by 4 bytes at a time. But the experiment > shows throughput of only 17MBps or 4.25M of 4 byte > transfers. Does the processor eats all the remaining > throughput (although I think it must load most of the > code it runs at idling into the cache) ? The PCI accesses don't limit throughput in your case. But you should allow for large bursts and should make sure, that read-multiple and write-and-invalidate PCI commands are used. What's the setting of the master latency-timer and the NCR latency timers ? Is the cache line size register set correctly ? What's the burst length limit chosen in DMODE ? > And another thing. I know that expensive machines like > DEC Prioris have possibilities to change some PCI > timing parameters for PCI cards. My cheap box does > not have anything like. May be that's the problem ? Which PCI timing parameters ??? You can modify PCI chip set parameters, but most should already be set to best values (i.e. all optimisations should be enabled by default). Increasing the value of the latency timer may improve PCI bus throughput, but its effect is often over-estimated. You should make sure, that the NCR cards are configured correctly, and you should take the into account, that the SCSI standard uses powers of 10, while throughput is measured in MB/s which are based on powers of 2 ... You want to overlap the preparation of the next transfer with the execution of the previous one, and you want to use transfer lengths long enough to hide the SCSI command overhead (which may be as low as 50us, but it takes some effort to get it that low ...). Regards, STefan From owner-freebsd-hackers Sat Oct 4 14:30:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA07509 for hackers-outgoing; Sat, 4 Oct 1997 14:30:02 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA07477 for ; Sat, 4 Oct 1997 14:29:59 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id WAA01704; Sat, 4 Oct 1997 22:15:15 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.7/8.8.7) id WAA17334; Sat, 4 Oct 1997 22:11:34 +0200 (CEST) (envelope-from andreas) Message-ID: <19971004221134.13249@klemm.gtn.com> Date: Sat, 4 Oct 1997 22:11:34 +0200 From: Andreas Klemm To: Amancio Hasty Cc: hackers@FreeBSD.ORG Subject: Re: SpecTcl needs java, which port to use for this ? References: <19971004203442.65007@klemm.gtn.com> <199710041913.MAA07756@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199710041913.MAA07756@rah.star-gate.com>; from Amancio Hasty on Sat, Oct 04, 1997 at 12:13:58PM -0700 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, Oct 04, 1997 at 12:13:58PM -0700, Amancio Hasty wrote: > If you try to use the Java components of course it is going to look or > ask for Java however if you start up specTcl and use tk8.0 at the very > least SpecTcl should start up and you can play with it. Yes that works fine ... I only asked for the Jave thing .. -- Andreas Klemm powered by ,,symmetric multiprocessor FreeBSD'' andreas@klemm.gtn.com - http://www.freebsd.org/~fsmp/SMP/SMP.html andreas@FreeBSD.ORG - http://www.freebsd.org/~fsmp/SMP/benches.html From owner-freebsd-hackers Sat Oct 4 14:36:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA08048 for hackers-outgoing; Sat, 4 Oct 1997 14:36:02 -0700 (PDT) Received: from dcarmich.pr.mcs.net (dcarmich.pr.mcs.net [204.95.63.202]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA07706; Sat, 4 Oct 1997 14:33:30 -0700 (PDT) Received: (from dcarmich@localhost) by dcarmich.pr.mcs.net (8.8.5/8.8.5) id QAA00718; Sat, 4 Oct 1997 16:36:46 -0500 (CDT) From: Douglas Carmichael Message-Id: <199710042136.QAA00718@dcarmich.pr.mcs.net> Subject: Update on accessibility w/FreeBSD To: sos@freebsd.org Date: Sat, 4 Oct 1997 16:36:45 -0500 (CDT) Cc: freebsd-hackers@freebsd.org Reply-To: dcarmich@mcs.com X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk One manufacturer of augmentative/alternative communication and assistive devices (Prentke Romich Company (or PRC), http://www.prentrom.com) makes a box that translates the infrared output or RS-232 output of the communication device into standard PS/2 keyboard/mouse signals. However, when I contacted PRC, the only mention of UNIX support was for Sun systems (with their HeadMaster alternate mouse): >From fetchpop Tue Sep 30 17:10:23 1997 Received: from dilbert.prentrom.com (root@dilbert.prentrom.com [208.4.213.198]) by Mailbox.mcs.net (8.8.7/8.8.2) with SMTP id SAA26819 for ; Mon, 29 Sep 1997 18:35:58 -0500 (CDT) Received: from [208.4.213.54] (macluser51.prentrom.com [208.4.213.54]) by dilbert.prentrom.com (8.6.12/8.6.12) with SMTP id QAA13600 for ; Mon, 29 Sep 1997 16:28:12 -0400 X-Sender: mlb@dilbert.prentrom.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 29 Sep 1997 16:07:04 -0500 To: dcarmich@mcs.com From: mlb@prentrom.com (Mary Bing) Subject: Unix on-screen keyboard X-UIDL: 245cdbedc564f8ac7bc65d7fa1ef27a9 Status: RO Dear Doug, I am responding to your inquiry about an on-screen keyboard for a Unix system. The HeadMaster is compatible with the Sun workstation. It also emulates a 2 button Microsoft mouse or a 3 button mouse systems mouse. Earl Johnson at Sun was previewing an on-screen keyboard he was working on at a conference 2 years ago. You can reach him by e-mail at earljohnson@eng.sun.com I don't know of anyone else woring on a unix on-screen keyboard. Sincerely, Mary Bing +--------------------------------------+--------------------------------+ | mlb@prentrom.com (Mary Bing) | | | | | +--------------------------------------+--------------------------------+ | Prentke Romich Company | | Augmentative and Alternative Communications devices for | | individuals with disabilities. | | (800) 262-1984 (330) 262-1984 | | | |Please note our new Web address http://www.prentrom.com | +-----------------------------------------------------------------------+ Ideas: 1) Make an on-screen keyboard that fits into the XKB framework and injects keystrokes into the X server. 2) Hack the console driver to only require one key (which could be defined on the device's keyboard) to switch to a certain VT (and distribute FreeBSD with all eleven VTs (leaving 1 free for X) enabled) 3) Hack the X server to also display the current window in focus out on the serial line back to the device's LCD screen (any more?) From owner-freebsd-hackers Sat Oct 4 15:10:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA09676 for hackers-outgoing; Sat, 4 Oct 1997 15:10:04 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA09646 for ; Sat, 4 Oct 1997 15:09:59 -0700 (PDT) Received: (qmail 16687 invoked by uid 1000); 4 Oct 1997 22:10:24 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092997 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19971004210211.32240@klemm.gtn.com> Date: Sat, 04 Oct 1997 15:10:24 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Andreas Klemm Subject: Re: Good Lord, Commercial Linux Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Andreas Klemm; On 04-Oct-97 you wrote: > Hi ! > > On Tue, Sep 30, 1997 at 08:50:02PM -0700, Simon Shapiro wrote: > > I still like FreeBSD installation better. The rest is pretty much > > the same to me. > > Can't understand this. Could you please explain it a bit more ? > Based on my own experience I can't follow here... On second reading, it does require a clarification; Aside from ``minor'' issues like quality, integrity, stability, etc., once you install either a Linux or a FreeBSD, provides they both work, what you get is a very current, complete and usable... Unix. Some people care a great deal about the SysV vs. BSD differences. I do not. I see the differences as noise. Having said that, we can go to the ``minor'' issues listed above and analyze them. Here FreeBSD is (in my opinion) a clear winner. This is why I am investing in and using FreeBSD and not Linux (as I did in the past). > > Kernel-wise, I think i trust FreeBSD kernel better than Linux, > > although performance is, well, six of this, half a dozen of the > > other; Both are tuned very well. > > Could you please explain this a little more verbose as well. Sure, The Linux kernel appears to me as a sandbox; A great place to build interesting structures and tear them down just as fast, while maintaining a strong toy orintation. Watch children in a sandbox. They are NOT playing. They are seriously building. Some of what they do will, one day, be built professionally, etc. Although much of my professional life was within the SystemV camp, I actually like the BSD kernel better than Linux. It is much more traditional, building on well known principles and expreinces. The Linux kernel seems to me like a hack. A hodge-podge of ideas (some of them excellent!). >From performance, on a PC platform, performance ends up being similar. Under heavy load, I'll choose FreeBSD over Linux, as FreeBSD runs and Linux dies. By heavy load I mean hundreds of processes running continious disk I/O and networking code, and RDBMS code. LA of 250 for months on end. >From stability point of view, FreeBSD is a winner. One can only take the weekly kernel for only so long. > So you are saying that FreeBSD has about half the performance > as Linux ? You're kidding ;-) No, I said that 6 Linuxes are about equal to half dozen FreeBSDs. I said 6 == 12 / 2, which is still true, last I checked :-)) > Or did you compare things like the speed of rm -rf on a large > directory tree without recognizing, that FreeBSD doesn't do > asynchronous I/O to a file system as default ?! While anomalies are important, they are not representative of the entities they are excepting. In my daily work, I do not have much use for large rm -rf. I have use for other things, but there they are similar. I would have copared a ``make world'' session on both O/S's but that concenpt does not exist on Linux, that I know of. For my professional work, that (lack of a coherent source tree) was a major reason to NOT use Linux. If I cannot reliably build a coherent, synchornized release, then I cannot say with certinty that my system is reproducable and thus true regression testing is impossible, thus I cannot use Linux for mission critical without faith. I have a lot of faith, but not in engineering products being correct by default :-) --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-hackers Sat Oct 4 15:26:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA10456 for hackers-outgoing; Sat, 4 Oct 1997 15:26:26 -0700 (PDT) Received: from rvc1.informatik.ba-stuttgart.de (rvc1.informatik.ba-stuttgart.de [141.31.112.22]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA10435 for ; Sat, 4 Oct 1997 15:26:09 -0700 (PDT) Received: (from helbig@localhost) by rvc1.informatik.ba-stuttgart.de (8.8.7/8.8.5) id AAA15231; Sun, 5 Oct 1997 00:25:15 +0200 (MET DST) From: Wolfgang Helbig Message-Id: <199710042225.AAA15231@rvc1.informatik.ba-stuttgart.de> Subject: Re: Good Lord, Commercial Linux In-Reply-To: <19971004210211.32240@klemm.gtn.com> from Andreas Klemm at "Oct 4, 97 09:02:11 pm" To: andreas@klemm.gtn.com (Andreas Klemm) Date: Sun, 5 Oct 1997 00:25:14 +0200 (MET DST) Cc: Shimon@i-Connect.Net, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Hi ! > > On Tue, Sep 30, 1997 at 08:50:02PM -0700, Simon Shapiro wrote: > > I still like FreeBSD installation better. The rest is pretty much > > the same to me. > > Can't understand this. Could you please explain it a bit more ? > Based on my own experience I can't follow here... > > > Kernel-wise, I think i trust FreeBSD kernel better than Linux, > > although performance is, well, six of this, half a dozen of the ^^^ ^^^^^^^^^^^^ > > other; Both are tuned very well. > > Could you please explain this a little more verbose as well. > > So you are saying that FreeBSD has about half the performance > as Linux ? You're kidding ;-) Well, `six' is about the same as `half a dozen', so Simon is saying that FreeBSD has about the same performance as Linux. > Or did you compare things like the speed of rm -rf on a large > directory tree without recognizing, that FreeBSD doesn't do > asynchronous I/O to a file system as default ?! > > Please facts here. > > -- > Andreas Klemm powered by ,,symmetric multiprocessor FreeBSD'' > andreas@klemm.gtn.com - http://www.freebsd.org/~fsmp/SMP/SMP.html > andreas@FreeBSD.ORG - http://www.freebsd.org/~fsmp/SMP/benches.html > From owner-freebsd-hackers Sat Oct 4 16:05:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA12019 for hackers-outgoing; Sat, 4 Oct 1997 16:05:45 -0700 (PDT) Received: from server.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA11996 for ; Sat, 4 Oct 1997 16:05:31 -0700 (PDT) Received: from localhost (perlsta@localhost) by server.local.sunyit.edu (8.8.7/8.8.5) with SMTP id TAA00830 for ; Sat, 4 Oct 1997 19:10:44 -0500 (EST) X-Authentication-Warning: server.local.sunyit.edu: perlsta owned process doing -bs Date: Sat, 4 Oct 1997 19:10:44 -0500 (EST) From: Alfred Perlstein X-Sender: perlsta@server.local.sunyit.edu To: hackers@FreeBSD.org Subject: help with serial boot? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk could someone give me a bit of help with getting the FreeBSD boot to work with my serial line? i have a nullmodem cable set up between two computers, one if a FreeBSD box (2.2-Stable), the other a winbloze 95 PC. i have the serial cable attached to the second serial port on the freebsd box. sending data over via "cat somefile > /dev/ttyd1" works as well as in the opposite direction, but i was unable to decypher the commands to the "boot:" prompt enough for me to get the boot to come across the serial line... can anyone help me with this? .________________________________________________________________________ __ _ |Alfred Perlstein - Programming & SysAdmin --"Have you seen my FreeBSD tatoo?" |perlsta@sunyit.edu --"who was that masked admin?" |http://www.cs.sunyit.edu/~perlsta : ' From owner-freebsd-hackers Sat Oct 4 16:06:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA12054 for hackers-outgoing; Sat, 4 Oct 1997 16:06:04 -0700 (PDT) Received: from dcarmich.pr.mcs.net (dcarmich.pr.mcs.net [204.95.63.202]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA11630; Sat, 4 Oct 1997 15:55:40 -0700 (PDT) Received: (from dcarmich@localhost) by dcarmich.pr.mcs.net (8.8.5/8.8.5) id RAA00924; Sat, 4 Oct 1997 17:58:56 -0500 (CDT) From: Douglas Carmichael Message-Id: <199710042258.RAA00924@dcarmich.pr.mcs.net> Subject: Building parallel "Beowulf-style" supercomputers with FreeBSD To: freebsd-hackers@freebsd.org Date: Sat, 4 Oct 1997 17:58:56 -0500 (CDT) Cc: freebsd-smp@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is there any way one can build large "Beowulf-like" clusters with FreeBSD and its SMP functionality? Anyone built such a beast? From owner-freebsd-hackers Sat Oct 4 16:57:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA14186 for hackers-outgoing; Sat, 4 Oct 1997 16:57:17 -0700 (PDT) Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.2.8]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA14170 for ; Sat, 4 Oct 1997 16:57:14 -0700 (PDT) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.3/8.8.3a) id QAA03731 for freebsd-hackers@freebsd.org; Sat, 4 Oct 1997 16:56:39 -0700 (MST) From: "Chad R. Larson" Message-Id: <199710042356.QAA03731@freebie.dcfinc.com> Subject: new floppy driver To: freebsd-hackers@freebsd.org Date: Sat, 4 Oct 1997 16:56:37 -0700 (MST) Reply-to: chad@dcfinc.com 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-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is anyone working on changes to the floppy driver to support the new Imation LS-120? This is the drive that can use both the existing 1.44meg 3.5" floppies, and (using optical positioning) a new standard 120meg format. That sure sounds like it would beat floppy tape for a backup medium, and for things like archiving/transporting image files. -crl -- Chad R. Larson (CRL22) Brother, can you paradigm? 602-953-1392 chad@dcfinc.com chad@anasazi.com crl22@aol.com DCF, Inc. - 14523 North 49th Place, Scottsdale, Arizona 85254 From owner-freebsd-hackers Sat Oct 4 17:55:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA16842 for hackers-outgoing; Sat, 4 Oct 1997 17:55:29 -0700 (PDT) Received: from news.quick.net (donegan@news.quick.net [207.212.170.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA16837; Sat, 4 Oct 1997 17:55:26 -0700 (PDT) Received: (from donegan@localhost) by news.quick.net (8.8.5/8.6.9) id RAA09114; Sat, 4 Oct 1997 17:55:19 -0700 (PDT) Date: Sat, 4 Oct 1997 17:55:18 -0700 (PDT) From: "Steven P. Donegan" To: Douglas Carmichael cc: freebsd-hackers@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: Building parallel "Beowulf-style" supercomputers with FreeBSD In-Reply-To: <199710042258.RAA00924@dcarmich.pr.mcs.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 4 Oct 1997, Douglas Carmichael wrote: > Is there any way one can build large "Beowulf-like" clusters with FreeBSD and its SMP functionality? > Anyone built such a beast? > > I too am very interested in SMP NOW toy's From owner-freebsd-hackers Sat Oct 4 18:16:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA17521 for hackers-outgoing; Sat, 4 Oct 1997 18:16:19 -0700 (PDT) Received: from consys.com (consys.com [209.60.202.194]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA17515; Sat, 4 Oct 1997 18:16:14 -0700 (PDT) Received: from cssunix.conceptual.com (cssunix.conceptual.com [10.0.2.5]) by consys.com (8.8.6/8.8.6) with ESMTP id SAA00917; Sat, 4 Oct 1997 18:16:13 -0700 (MST) Received: (from rcarter@localhost) by cssunix.conceptual.com (8.8.5/8.8.6) id SAA29007; Sat, 4 Oct 1997 18:16:13 -0700 (MST) Date: Sat, 4 Oct 1997 18:16:13 -0700 (MST) From: "Russell L. Carter" Message-Id: <199710050116.SAA29007@cssunix.conceptual.com> To: dcarmich@mcs.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Building parallel "Beowulf-style" supercomputers with FreeBSD Cc: freebsd-smp@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Yes. Now it is a curious thing that NFS server perf. is not considered, but such is life. In fact, there are lots of interesting questions to be asked, but, who am I to ask them? :-) Cheers, Russell From owner-freebsd-hackers Sat Oct 4 18:33:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA18135 for hackers-outgoing; Sat, 4 Oct 1997 18:33:27 -0700 (PDT) Received: from proxy4.ba.best.com (root@proxy4.ba.best.com [206.184.139.15]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA18129 for ; Sat, 4 Oct 1997 18:33:26 -0700 (PDT) Received: from shellx.best.com (shellx.best.com [206.86.0.11]) by proxy4.ba.best.com (8.8.7/8.8.BEST) with ESMTP id SAA29567 for ; Sat, 4 Oct 1997 18:33:04 -0700 (PDT) Received: from localhost (mdean@localhost) by shellx.best.com (8.8.6/8.8.3) with SMTP id SAA24886 for ; Sat, 4 Oct 1997 18:33:03 -0700 (PDT) Date: Sat, 4 Oct 1997 18:33:03 -0700 (PDT) From: mdean To: freebsd-hackers@freebsd.org Subject: Interrupt Handling Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk How do you handle devices with tristate interrupts. I guess this means that they can share a single IRQ line with other devices, I think this is also called wired-OR. From owner-freebsd-hackers Sat Oct 4 18:41:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA18407 for hackers-outgoing; Sat, 4 Oct 1997 18:41:38 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA18399 for ; Sat, 4 Oct 1997 18:41:33 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id LAA02371; Sun, 5 Oct 1997 11:08:32 +0930 (CST) Message-Id: <199710050138.LAA02371@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: chad@dcfinc.com cc: freebsd-hackers@freebsd.org Subject: Re: new floppy driver In-reply-to: Your message of "Sat, 04 Oct 1997 16:56:37 MST." <199710042356.QAA03731@freebie.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 05 Oct 1997 11:08:28 +0930 From: Mike Smith Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Is anyone working on changes to the floppy driver to support the > new Imation LS-120? No. But that's because the *Mitsubishi* LS-120 is an ATAPI device, and like the ATAPI Zip drive requires a new ATAPI device type. > That sure sounds like it would beat floppy tape for a backup medium, and > for things like archiving/transporting image files. There's not much that _doesn't_ beat a floppy tape. mike From owner-freebsd-hackers Sat Oct 4 19:05:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA19408 for hackers-outgoing; Sat, 4 Oct 1997 19:05:00 -0700 (PDT) Received: from pcpsj.pfcs.com (Vsr4HCrpC0Ramv/9hmjm1BpT9x8kWjNw@harlan.fred.net [205.252.219.31]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA19399 for ; Sat, 4 Oct 1997 19:04:54 -0700 (PDT) Received: from mumps.pfcs.com (mumps.pfcs.com [192.52.69.11]) by pcpsj.pfcs.com (8.8.6/8.6.9) with SMTP id WAA23238; Sat, 4 Oct 1997 22:04:48 -0400 (EDT) Received: from localhost by mumps.pfcs.com with SMTP id AA05658 (5.67b/IDA-1.5); Sat, 4 Oct 1997 22:04:46 -0400 To: chad@dcfinc.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: new floppy driver In-Reply-To: Your message of "Sat, 04 Oct 1997 16:56:37 PDT." <199710042356.QAA03731@freebie.dcfinc.com> Date: Sat, 04 Oct 1997 22:04:45 -0300 Message-Id: <5656.876017085@mumps.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk We got the "intro pricing" blurb on these, and I'm still not sure if we can order several or just one of each model at the "intro pricing". I *did* notice that no mention was made of the price of the diskettes... H From owner-freebsd-hackers Sat Oct 4 19:20:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA19959 for hackers-outgoing; Sat, 4 Oct 1997 19:20:34 -0700 (PDT) Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.2.8]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA19954 for ; Sat, 4 Oct 1997 19:20:31 -0700 (PDT) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.3/8.8.3a) id TAA03881; Sat, 4 Oct 1997 19:19:37 -0700 (MST) From: "Chad R. Larson" Message-Id: <199710050219.TAA03881@freebie.dcfinc.com> Subject: Re: new floppy driver To: Harlan.Stenn@pfcs.com (Harlan Stenn) Date: Sat, 4 Oct 1997 19:19:36 -0700 (MST) Cc: chad@dcfinc.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: <5656.876017085@mumps.pfcs.com> from Harlan Stenn at "Oct 4, 97 10:04:45 pm" Reply-to: chad@dcfinc.com 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-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > We got the "intro pricing" blurb on these, and I'm still not sure if we > can order several or just one of each model at the "intro pricing". > > I *did* notice that no mention was made of the price of the diskettes... They're in several catalogs at around $15 each. Insight Direct will sell you drives and media. Fry's Electronics had the drive (list price $399) for about $200, but that was an external parallel-port version. I've heard Dell and Compaq are going to start shipping the internal version as the only floppy on their systems. -crl -- Chad R. Larson (CRL22) Brother, can you paradigm? 602-953-1392 chad@dcfinc.com chad@anasazi.com crl22@aol.com DCF, Inc. - 14523 North 49th Place, Scottsdale, Arizona 85254 From owner-freebsd-hackers Sat Oct 4 19:30:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA20304 for hackers-outgoing; Sat, 4 Oct 1997 19:30:21 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id TAA20299 for ; Sat, 4 Oct 1997 19:30:18 -0700 (PDT) Received: (qmail 8891 invoked by uid 1000); 5 Oct 1997 02:30:44 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092997 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Date: Sat, 04 Oct 1997 19:30:44 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: freebsd-hackers@freebsd.org Subject: Minor error (?) in regex.h Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Y'all, Struggling along with the GIMP (I am a masochist :-), it seems as if /usr/include/regex.h really needs #include to compile. Should it be included? --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-hackers Sat Oct 4 20:16:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA21654 for hackers-outgoing; Sat, 4 Oct 1997 20:16:22 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id UAA21648 for ; Sat, 4 Oct 1997 20:16:19 -0700 (PDT) Received: (qmail 5490 invoked by uid 1000); 5 Oct 1997 03:16:44 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-092997 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Date: Sat, 04 Oct 1997 20:16:44 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: freebsd-hackers@freebsd.org, freebsd-dlm@primer.i-connect.net Subject: Solicitation for Review Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Y'all, Will some kind soul volunteer to review the kernel component of the Distributed Lock Manager? It is a character device driver with an excercise/test program included. It is short, simple and easy to work with. Although the remote component is still work-in-progress, I feel that the local component is stable enough to be tested an included. The remote lock daemon will be finished in the next few weeks. A kernel-kernel communications over SCSI will be added maybe sooner. These components create the framework for running a database, or anything else that wants to share resources from two instances of FreeBSD. If you are willing to review the code, please let me know and I will provide you with a complete kit; patch, documentation and instructions. Thanx a million. --- Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313 From owner-freebsd-hackers Sat Oct 4 22:41:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA26883 for hackers-outgoing; Sat, 4 Oct 1997 22:41:51 -0700 (PDT) Received: from hq.icb.chel.su (hq.icb.chel.su [193.125.10.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA26723; Sat, 4 Oct 1997 22:38:38 -0700 (PDT) Received: (babkin@localhost) by hq.icb.chel.su (8.8.3/8.6.5) id LAA09048; Sun, 5 Oct 1997 11:39:56 +0600 (ESD) From: "Serge A. Babkin" Message-Id: <199710050539.LAA09048@hq.icb.chel.su> Subject: Re: PCI slowness ? To: se@freebsd.org (Stefan Esser) Date: Sun, 5 Oct 1997 11:39:56 +0600 (ESD) Cc: hackers@freebsd.org In-Reply-To: <19971004221205.63474@mi.uni-koeln.de> from "Stefan Esser" at Oct 4, 97 10:12:05 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > On 1997-10-04 20:05 +0600, "Serge A. Babkin" wrote: > > Hi! > > > > I've made a simple driver to test the SCSI throughput. It takes > > 2 NCR53c810A SCSI cards and starts to transfer data between them > > at (theoretically) 10MBps synchronous rate. But in fact I get at most > > 8.5MBps ! I was able to rase it from 7.5MBps to 8.5MBps > > by changing the memory access options in NCRs from simplest > > to maximal optimization so probably the PCI or memory > > bus limits the throughput. Can anyone suggest me what's > > the problem ? > > You don't tell about your actual setup: > > 1) transfer length ? 1024 bytes > 2) did disconnects occur ? No, the phase never changes, the cards just send and receive those 1K blocks in SCRIPTS loop. The exact loop is: loop: SCR_NOP, 0, SCR_MOVE_INIT_ABS(1024) ^ SCR_DATA_OUT, /* or MOVE_TARG_ABS */ &initbf, /* or targbf */ SCR_COPY(4), &initcnt, /* or targcnt */ RADDR(scr0), SCR_CALL, PADDR(increase), SCR_COPY(4), RADDR(scr0), &initcnt, SCR_JUMP, PADDR(loop), The `increase' subroutine increases scr0..3 as 4-byte register by 1. > 3) does the time measurement include the time to prepare > the transfer (which may be hidden in most cases) ? It just interrupts on timer each 3 seconds, prints out 'initcnt' and 'targcnt' and prints the computed transfer rate (difference between current and previous `*cnt' divided by 3). > > Did you take into account, that FAST SCSI uses a 100ns > cycle length, which allows for 10mio B/s, or 9.5MB/s ? Sorry, I was wrong. In fact it was 7500 to 8250 1Kbyte transfers. I was catched in this trap. This must be 7.68 to 8.45 mio B/s. > > If you transfer 64KB blocks (which takes 6.7ms at 10MHz) > and the SCSI overhead is 1ms, then you'll see an actual > transfer rate of 8.3MB/s. There must be no SCSI overhead because I do not reestablish the connections and do not change phases. But I never throught that SCRIPTS overhead can be so high. > > > The chipset is Intel Triton on some chineese motherboard > > with 75MHz Pentium, memory is 60ns EDO. > > Theoretical PCI throughput is 33M > > of 4-byte transfers per second (the card claims to work > > in burst mode). Theoretical memory throughput is at least > > 10M of 4-byte transfers per second if we suppose that > > the memory cycle with all overhead is 100ns and the > > card reads by 4 bytes at a time. But the experiment > > shows throughput of only 17MBps or 4.25M of 4 byte > > transfers. Does the processor eats all the remaining > > throughput (although I think it must load most of the > > code it runs at idling into the cache) ? > > The PCI accesses don't limit throughput in your case. > But you should allow for large bursts and should make > sure, that read-multiple and write-and-invalidate PCI > commands are used. How can I do that ? Should I look on the PCI bus driver ? > > What's the setting of the master latency-timer and > the NCR latency timers ? scntl3=0x13 sxfer=0x04 Do you mean them ? > Is the cache line size register set correctly ? > What's the burst length limit chosen in DMODE ? dmode=0xce; dcntl=0x20|NOCOM; I can describe the history: Initial speed: 7.5 mio Using EXT flag in SCNTL2: no difference Enabled ERL, ERMP, BOF in DMODE. Got speed around 8.1 mio Enabled CLSE, PFEN in DCNTL. Got speed around 8.25 mio Removed CLSE in DCNTL : no difference It seems strange because it must reduce the granularity of memory accesses from 16 to 4 bytes. May be EDO memory is the reason why it didn't influenced at all. Reduced SCSI offset in SXFER from 8 to 4: no difference This must show that SCSI is not limiting the speed. > > > And another thing. I know that expensive machines like > > DEC Prioris have possibilities to change some PCI > > timing parameters for PCI cards. My cheap box does > > not have anything like. May be that's the problem ? > > Which PCI timing parameters ??? Per-card latency timers. If I remember correctly. Increasing them led to lower throughput of Adaptec under SCO. We had problems because 2 of 4 machines had only one interrupt used for Adaptec instead of two. And before we discovered this reason we tried to increase latencies. This led to slower work but it paniced less frequently. > > You can modify PCI chip set parameters, but most should > already be set to best values (i.e. all optimisations > should be enabled by default). > > Increasing the value of the latency timer may improve PCI > bus throughput, but its effect is often over-estimated. Hm. May be I decreased them on Prioris, not increased as I wrote earlier. I can't remember now. > > You should make sure, that the NCR cards are configured > correctly, and you should take the into account, that > the SCSI standard uses powers of 10, while throughput > is measured in MB/s which are based on powers of 2 ... I've checked the Symbios examples and it seems to me that I do everything like them. > > You want to overlap the preparation of the next transfer > with the execution of the previous one, and you want to > use transfer lengths long enough to hide the SCSI command > overhead (which may be as low as 50us, but it takes some > effort to get it that low ...). I tried to absolutely get rid of them. The only possible slowdown reason is SCRIPTS overhead. Thanks! -SB From owner-freebsd-hackers Sat Oct 4 23:27:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA01537 for hackers-outgoing; Sat, 4 Oct 1997 23:27:10 -0700 (PDT) Received: from proxy3.ba.best.com (root@proxy3.ba.best.com [206.184.139.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA01531 for ; Sat, 4 Oct 1997 23:27:08 -0700 (PDT) Received: from shellx.best.com (shellx.best.com [206.86.0.11]) by proxy3.ba.best.com (8.8.7/8.8.BEST) with ESMTP id XAA01588 for ; Sat, 4 Oct 1997 23:25:45 -0700 (PDT) Received: from localhost (mdean@localhost) by shellx.best.com (8.8.6/8.8.3) with SMTP id XAA13212 for ; Sat, 4 Oct 1997 23:25:44 -0700 (PDT) Date: Sat, 4 Oct 1997 23:25:44 -0700 (PDT) From: mdean To: freebsd-hackers@freebsd.org Subject: A world of unexplored pain. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Please stop me if I am about to waste my time doing something that just isn't possible. I have received a lot of conflicting arguments on wheter or not the following is possible (more importantly will it function as designed). What I need is one or more 0-500Hz Square Waves generated at the output pins of and 8255 PPi. These are to be used to run the inputs to a single axis stepper motor controller. I have the device drivers for dos, however my application is such that it would be truly a waste to not have a networked application (also considering that the controlling app run under X). The do device driver function quite nicely, however when called they consume 100% cpu time and **CANNOT** have the commands cancelled once called. One reason to use a comuputer to do this instead of a custom controller is co$t the other is complexity. To properly control the motors the pulse train must be scaled from 0 to 500Hz and back down as it slows. This is not a standard feature on the 68hc11 even though it has nearly everything but the kitchen sink built in. With a freebsd machine I am likely to be able to accomplish this and also set it up as a system where the target position can be changed in realtime, thus making it possible to cancel a command. I just cannot do this with the embedded equipment I have available (mc68hc11) because a) rti on the 68hc11 don't run faster than 500hz (you need 1000hz for a 500hz square wave) and b) if the routine was dedicated then the rs232/485 interrupt would possibly cause a lot of jitter taking the commands while scaling the output. I think that this can be done from what I've seen you can acquire_timer0() from clock.c up to 20000hz to your interrupt routine. This should make possible driving equipment of this type or any small scale polling stuff like AtoD boards without there own interrupts (there are quite a few of these available). I guess Ideally I should combine AtoD drivers and digital output drivers into one so that they may share the same interrupt routine, the real question for me is: If I use acquire_timer0(1000, myintr) what kind of jitter should I expect in delivery of those interrupts, i.e how far off center will myintr() get called from the every 1/1000 of a second mark? From owner-freebsd-hackers Sat Oct 4 23:47:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA02319 for hackers-outgoing; Sat, 4 Oct 1997 23:47:29 -0700 (PDT) Received: from proxy4.ba.best.com (root@proxy4.ba.best.com [206.184.139.15]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA02314 for ; Sat, 4 Oct 1997 23:47:26 -0700 (PDT) Received: from shellx.best.com (shellx.best.com [206.86.0.11]) by proxy4.ba.best.com (8.8.7/8.8.BEST) with ESMTP id XAA13178 for ; Sat, 4 Oct 1997 23:45:28 -0700 (PDT) Received: from localhost (mdean@localhost) by shellx.best.com (8.8.6/8.8.3) with SMTP id XAA17787 for ; Sat, 4 Oct 1997 23:45:27 -0700 (PDT) Date: Sat, 4 Oct 1997 23:45:27 -0700 (PDT) From: mdean To: freebsd-hackers@freebsd.org Subject: Kernel function index. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is there an easy way to index all of the functions and structs in the kernel source tree? So that if I for instance want to know where the bubba() function is defined or struct foo I can do somethnig to the extent of a locate on the kernel sourcetext?