From owner-freebsd-current Sun Nov 10 00:18:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA23203 for current-outgoing; Sun, 10 Nov 1996 00:18:00 -0800 (PST) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA23195; Sun, 10 Nov 1996 00:17:57 -0800 (PST) Message-Id: <199611100817.AAA23195@freefall.freebsd.org> To: Jaye Mathisen cc: current@FreeBSD.org Subject: Re: Some fundamental datatype change? Excessive unsigned vs signed compare warnings on kernel builds. In-reply-to: Your message of "Sat, 09 Nov 1996 23:59:06 PST." Date: Sun, 10 Nov 1996 00:17:57 -0800 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk This is due to our change in compilers from 2.6.3 to 2.7.2.1. 2.7 is more vocal and/or better at finding, these kinds of errors. >I haven't actually watched a full kernel build in a while, just copying >the result to /. However, I've been messing with Justin's new AHC code, >and just happened to watch a compile of a -current downloaded around 11/7, >and there's lots of warnings about compares of unsigned vs. signed. > >Normally these don't worry me, but there were numerous ones in the FS >stuff, a few in the vm section, and oodles in the NFS stuff. Just seems >unhealthy. > -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Sun Nov 10 00:26:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA23680 for current-outgoing; Sun, 10 Nov 1996 00:26:54 -0800 (PST) Received: from dyson.iquest.net ([198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA23674 for ; Sun, 10 Nov 1996 00:26:50 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id DAA11968; Sun, 10 Nov 1996 03:26:40 -0500 (EST) From: "John S. Dyson" Message-Id: <199611100826.DAA11968@dyson.iquest.net> Subject: Re: Some fundamental datatype change? Excessive unsigned vs signed compare warnings on kernel builds. To: mrcpu@cdsnet.net (Jaye Mathisen) Date: Sun, 10 Nov 1996 03:26:39 -0500 (EST) Cc: current@FreeBSD.org In-Reply-To: from "Jaye Mathisen" at Nov 9, 96 11:59:06 pm X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > > I haven't actually watched a full kernel build in a while, just copying > the result to /. However, I've been messing with Justin's new AHC code, > and just happened to watch a compile of a -current downloaded around 11/7, > and there's lots of warnings about compares of unsigned vs. signed. > > Normally these don't worry me, but there were numerous ones in the FS > stuff, a few in the vm section, and oodles in the NFS stuff. Just seems > unhealthy. > Yep, I kind-of agree with you. I certainly will be cleaning up the VM stuff (and perhaps some of the VFS stuff) soon. Probably will not make it into 2.2-RELEASE though. The messages are indicating potential problems that have been generally checked out. The problem is that it requires careful consideration/coordination to clean-em up. John From owner-freebsd-current Sun Nov 10 00:40:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA24193 for current-outgoing; Sun, 10 Nov 1996 00:40:54 -0800 (PST) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA24107; Sun, 10 Nov 1996 00:38:31 -0800 (PST) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id AAA16753; Sun, 10 Nov 1996 00:38:38 -0800 (PST) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id AAA18952; Sun, 10 Nov 1996 00:38:16 -0800 (PST) Message-Id: <199611100838.AAA18952@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: "Justin T. Gibbs" cc: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A.) Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Chernov) , current@freebsd.org, scsi@freebsd.org Subject: Re: SCSI system becomes broken in -current? In-reply-to: Your message of Sat, 09 Nov 96 19:04:22 -0800. <199611100304.TAA07061@freefall.freebsd.org> Date: Sun, 10 Nov 1996 00:38:16 -0800 From: "Michael L. VanLoon -- HeadCandy.com" >>Needless to say that it works OK under Win95. >They probably have a quirk entry for it. Either that, or there is a new >bug in the driver. The changes I made shouldn't have effected tagged >queueing, so the bug should be reproducible with tagged queueing disabled. I *seriously* doubt Win95 does tagged-queuing. In fact, I wouldn't be surprised if it did everything via PIO. If you said it worked OK under WinNT, that might be different (although I would expect them to have a pretty comprehensive quirk database, or some such). ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-current Sun Nov 10 01:51:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA26968 for current-outgoing; Sun, 10 Nov 1996 01:51:48 -0800 (PST) Received: from MVS.OAC.UCLA.EDU (mvs.oac.ucla.edu [164.67.200.200]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA26958 for ; Sun, 10 Nov 1996 01:51:46 -0800 (PST) Message-Id: <199611100951.BAA26958@freefall.freebsd.org> Received: from UCLAMVS.BITNET by MVS.OAC.UCLA.EDU (IBM MVS SMTP V2R2.1) with BSMTP id 5183; Sun, 10 Nov 96 01:51:50 PST Date: Sun, 10 Nov 96 01:51 PST To: current@FREEBSD.ORG From: Denis DeLaRoca (310) 825-4580 Subject: bpf-1.1, libpcap-0.2.1 and tcpdump-3.2.1 Sender: owner-current@FREEBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Will these new versions make into the 2.2 release? -- Denis From owner-freebsd-current Sun Nov 10 01:52:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA27029 for current-outgoing; Sun, 10 Nov 1996 01:52:18 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA27018 for ; Sun, 10 Nov 1996 01:52:13 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA10009; Sun, 10 Nov 1996 10:51:27 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA25159; Sun, 10 Nov 1996 10:51:26 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id KAA09119; Sun, 10 Nov 1996 10:47:36 +0100 (MET) From: J Wunsch Message-Id: <199611100947.KAA09119@uriah.heep.sax.de> Subject: Re: Where does the zic source live? To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 10 Nov 1996 10:47:36 +0100 (MET) Cc: reilly@zeta.org.au (Andrew Reilly) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199611090838.TAA12184@budgie.zeta.org.au> from Andrew Reilly at "Nov 9, 96 07:38:54 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Andrew Reilly wrote: > I havn't been able to hunt any more information > down in the man pages or the FAQ or the handbook, so does > anyone know? Well, if you rephrase your question from ``where does'' to ``where is'', you're already done. :-) j@uriah 214% whereis zic zic: /usr/sbin/zic /usr/share/man/man8/zic.8.gz /usr/src/usr.sbin/zic -- 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-current Sun Nov 10 02:08:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA27753 for current-outgoing; Sun, 10 Nov 1996 02:08:30 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA27747 for ; Sun, 10 Nov 1996 02:08:22 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id UAA03369; Sun, 10 Nov 1996 20:58:07 +1100 Date: Sun, 10 Nov 1996 20:58:07 +1100 From: Bruce Evans Message-Id: <199611100958.UAA03369@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, reilly@zeta.org.au Subject: Re: Where does the zic source live? Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Hi, Daylight savings time has just started in Sydney, and >my system didn't respond too well. I thought that part of >the problem might be that the clock chip was running >wall-clock time (from a Windows config.) So I changed that It works OK running wall-clock time here. >down in the man pages or the FAQ or the handbook, so does >anyone know? I don't believe that the compiled time info >files are all that we have. When I worked in Brisbane on a Sources are in /usr/src: /usr/src/share/zoneinfo. Other parts of the Olsen timezone package are /usr/src/usr.sbin/zic and /usr/src/lib/libc/stdtime. Bruce From owner-freebsd-current Sun Nov 10 02:17:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA28176 for current-outgoing; Sun, 10 Nov 1996 02:17:40 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA28168 for ; Sun, 10 Nov 1996 02:17:31 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id VAA03875 for current@freebsd.org; Sun, 10 Nov 1996 21:14:27 +1100 Date: Sun, 10 Nov 1996 21:14:27 +1100 From: Bruce Evans Message-Id: <199611101014.VAA03875@godzilla.zeta.org.au> To: current@freebsd.org Subject: gdb anomalies Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk gdb sometimes tells me that the executable file has changed, although it shouldn't have. It seems to be correct though - executing the file apparently clobbers at least its ctime and mtime: Stat of object file built just before the executable: file=obj/dkcksum.o type=regular mode= ---rw-r--r-- size=4132 links=1 blksize=8192 blocks=10 user=15 group=0 unit=4/7 inode=114042 atime=Sun Nov 10 21:03:00 1996 ctime=Sun Nov 10 21:03:00 1996 mtime=Sun Nov 10 21:03:00 1996 Stat of executable: file=obj/disklabel type=regular mode= ---rwxr-xr-x size=54058 links=1 blksize=8192 blocks=106 user=15 group=0 unit=4/7 inode=114043 atime=Sun Nov 10 21:03:49 1996 <- changed OK when the file was execed ctime=Sun Nov 10 21:04:14 1996 <- changed !OK after file was execed mtime=Sun Nov 10 21:04:14 1996 <- changed !OK Bruce From owner-freebsd-current Sun Nov 10 02:21:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA28426 for current-outgoing; Sun, 10 Nov 1996 02:21:56 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA28376 for ; Sun, 10 Nov 1996 02:21:29 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id VAA04056 for current@freebsd.org; Sun, 10 Nov 1996 21:19:53 +1100 Date: Sun, 10 Nov 1996 21:19:53 +1100 From: Bruce Evans Message-Id: <199611101019.VAA04056@godzilla.zeta.org.au> To: current@FreeBSD.ORG Subject: more gdb anamolies Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Yow, now it's touching libc.so.3.0. Also, removing one breakpoint sometimes seems to stop other breakpoints from working. Bruce From owner-freebsd-current Sun Nov 10 02:52:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA29808 for current-outgoing; Sun, 10 Nov 1996 02:52:22 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA29800 for ; Sun, 10 Nov 1996 02:52:10 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id LAA11111 for ; Sun, 10 Nov 1996 11:52:05 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id LAA26104 for freebsd-current@FreeBSD.org; Sun, 10 Nov 1996 11:52:05 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id LAA09750 for freebsd-current@FreeBSD.org; Sun, 10 Nov 1996 11:50:23 +0100 (MET) From: J Wunsch Message-Id: <199611101050.LAA09750@uriah.heep.sax.de> Subject: wt driver broken! To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 10 Nov 1996 11:50:23 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I can't get my couple of `wt' drives recognized anymore in -current. (One is an Archive, one is a Wangtek.) Do other people experience the same, or is it just my hardware? I wouldn't love it to ship 2.2R with a broken driver... -- 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-current Sun Nov 10 06:02:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA10225 for current-outgoing; Sun, 10 Nov 1996 06:02:52 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA10200; Sun, 10 Nov 1996 06:02:41 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id OAA01274; Sun, 10 Nov 1996 14:46:18 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.8.2/8.8.2) with ESMTP id NAA00866; Sun, 10 Nov 1996 13:14:14 +0100 (MET) Date: Sun, 10 Nov 1996 13:14:14 +0100 (MET) From: Andreas Klemm To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= cc: FreeBSD-current , scsi@freebsd.org Subject: Re: SCSI system becomes broken in -current? In-Reply-To: <199611100133.EAA00401@nagual.ru> Message-ID: X-try-apsfilter: ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz X-Fax: +49 2137 2018 X-Phone: +49 2137 2020 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 10 Nov 1996, [KOI8-R] áÎÄÒÅÊ þÅÒÎÏ× wrote: > It work for me without any error for very long time, but after > todays rebuild I often got: > > sd0(ahc0:0:0): timed out in dataout phase, SCSISIGI == 0x0 > Ordered Tag queued > Ordered Tag sent Which syslog settings do you use, so that you can get the messages out of a logfile ?! BTW, I have sinilar problems when doing backups on tape only if tagged queuing is enabled. -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-current Sun Nov 10 06:19:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA11060 for current-outgoing; Sun, 10 Nov 1996 06:19:46 -0800 (PST) Received: from watt.cae.uwm.edu (hench@watt.cae.uwm.edu [129.89.52.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA11052 for ; Sun, 10 Nov 1996 06:19:40 -0800 (PST) Received: (from hench@localhost) by watt.cae.uwm.edu (8.6.12/8.6.12) id IAA08071; Sun, 10 Nov 1996 08:19:34 -0600 From: Mike Hench Message-Id: <199611101419.IAA08071@watt.cae.uwm.edu> Subject: scsi lockups (Was Stop me b4 i kill again) To: gibbs@freefall.freebsd.org (Justin T. Gibbs) Date: Sun, 10 Nov 1996 08:19:34 -0600 (CST) Cc: hench@cae.uwm.edu, freebsd-current@freebsd.org In-Reply-To: <199611100217.SAA04688@freefall.freebsd.org> from "Justin T. Gibbs" at Nov 9, 96 06:17:06 pm X-Mailer: ELM [version 2.4 PL21] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Is this a pci card? If so, can you try options "AHC_FORCE_PIO"? > yes pci, AHC_FORCE_PIO *works*. so what does it mean ? thanks again mike hench hench@cae.uwm.edu From owner-freebsd-current Sun Nov 10 07:04:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA14908 for current-outgoing; Sun, 10 Nov 1996 07:04:15 -0800 (PST) Received: from sanewo.ba2.so-net.or.jp (pppba48.pppp.ap.so-net.or.jp [210.132.186.72]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA14896 for ; Sun, 10 Nov 1996 07:04:04 -0800 (PST) Received: (from sanewo@localhost) by sanewo.ba2.so-net.or.jp (8.8.2/8.7.3) id AAA26943; Mon, 11 Nov 1996 00:03:54 +0900 (JST) To: freebsd-current@freebsd.org Subject: Re: Strange PS2 Mouse Behavior References: <199611052202.PAA26779@rocky.mt.sri.com> From: Takanori Saneto In-Reply-To: Nate Williams's message of Tue, 5 Nov 1996 15:02:22 -0700 (MST) Mime-Version: 1.0 (generated by tm-edit 7.93) Content-Type: text/plain; charset=US-ASCII Date: 11 Nov 1996 00:03:53 +0900 Message-ID: <873eyiat5y.fsf@sanewo.ba2.so-net.or.jp> Lines: 24 X-Mailer: Red Gnus v0.57/Emacs 19.34/Mule 2.3 (SUETSUMUHANA) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199611052202.PAA26779@rocky.mt.sri.com>, Nate Williams writes: >Ron Bolin writes: >> After updating from around a 10-26-96 current to todays 11-5-96 >> I am having problems with my PS2 mouse. A times it reacts strange >> when I move my cursor to another window too fast. It will charge to >> the far right of the screen when I am moving it to the left. It was >> working I experienced strang PS2 mouse behavior, too. My kernel built on Nov 2 was OK but the one built on Nov 9 was showed this problem. In addition to spourious motion of mouse pointer, I experienced something wrong about buttons and keys. (window manager menus pop up, random characters appear on my xterm, etc.) >This problem showed up in the last 2 weeks, but I had other >modifications on my system that I blamed it on. I've since removed all >of them and the problem persists. When I use sys/i386/isa/syscons.c 1.182 instead of 1.183 (current), problems above seem to disappear. -- Takanori Saneto From owner-freebsd-current Sun Nov 10 08:25:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA17714 for current-outgoing; Sun, 10 Nov 1996 08:25:38 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA17702; Sun, 10 Nov 1996 08:25:33 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA16541; Sun, 10 Nov 1996 09:25:26 -0700 (MST) Date: Sun, 10 Nov 1996 09:25:26 -0700 (MST) Message-Id: <199611101625.JAA16541@rocky.mt.sri.com> From: Nate Williams To: current@freebsd.org CC: sos@freebsd.org Subject: New PS/2 mouse driver stalled Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have read the comments on the new syscons|ps/2 mouse driver bugs, but looking at Bruce's comments regarding the new syscons 'polling' behavior it looks like it wouldn't matter since it really requires a new 'combo' driver that differentiates between keyboard interrupts and mouse interrupts, which has been the 'goal' for a long time with no resolution. I believe the new driver is 'better' than the old driver, but I don't believe it will work any better with the syscons changes that folks are complaining about. The author of the new driver would like to work on it more, and has even provided a man-page but none of this matters until we get the syscons/mouse interaction resolved. I agree that syscons is within it's rights to poll the keyboard, but it means that the PS/2 driver will not work if I read Bruce's notes correctly. Nate ps. S'ren, is it possible to have the XT_KEYBOARD code turned into a flag for 2.2/2.1.6? This would allow ThinkPad owners to use the GENERIC boot floppy and not require any special boot floppy? I could provide the (simple) patch if necessary. From owner-freebsd-current Sun Nov 10 08:39:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA18315 for current-outgoing; Sun, 10 Nov 1996 08:39:03 -0800 (PST) Received: from janai.thuvia.org (linus.demon.co.uk [158.152.10.220]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA18308 for ; Sun, 10 Nov 1996 08:38:55 -0800 (PST) Received: (from mark@localhost) by janai.thuvia.org (8.8.2/8.8.2) id QAA10987; Sun, 10 Nov 1996 16:38:46 GMT Message-Id: <199611101638.QAA10987@janai.thuvia.org> From: mark@linus.demon.co.uk (Mark Valentine) Date: Sun, 10 Nov 1996 16:38:45 +0000 In-Reply-To: Takanori Saneto's message of Nov 11, 12:03am X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Takanori Saneto , freebsd-current@freebsd.org Subject: Re: Strange PS2 Mouse Behavior Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > From: Takanori Saneto > Date: Mon 11 Nov, 1996 > Subject: Re: Strange PS2 Mouse Behavior > In article <199611052202.PAA26779@rocky.mt.sri.com>, > Nate Williams writes: > >Ron Bolin writes: > >> After updating from around a 10-26-96 current to todays 11-5-96 > >> I am having problems with my PS2 mouse. A times it reacts strange > >> when I move my cursor to another window too fast. It will charge to > >> the far right of the screen when I am moving it to the left. It was > >> working > > I experienced strang PS2 mouse behavior, too. My kernel built on Nov 2 > was OK but the one built on Nov 9 was showed this problem. > > In addition to spourious motion of mouse pointer, I experienced > something wrong about buttons and keys. (window manager menus pop up, > random characters appear on my xterm, etc.) Me too, though this is the first time I've been up to date with -current in a few months. I usually just get my olvwm menu popping up in the top right corner, but sometimes I get a random cut and paste into an xterm on the way. :-( > >This problem showed up in the last 2 weeks, but I had other > >modifications on my system that I blamed it on. I've since removed all > >of them and the problem persists. I also made another change when I brought myself up to date: adding the pt0 device; I took that out and the problem is less frequent, but still there - probably a coincidence? I may just have had more system activity yesterday (ppp0 internal modem connection running at 33k6 solid for 12 hours and a make World for XFree86). I upgraded from XFree86 3.1.2G (binary release) to 3.2 (from source) subsequently - no change. Sometimes my system gets into a state where the ALT key seems to be locked on. Usually it's better if I switch to a text vt and back, but I've also seen the text vt get confused. dmesg output available if it might be useful. ASUS T2P4, Pentium/133, 64MB, AHA2940UW (narrow Hawk attached), NCR810 (scanner, 2xCD, QIC, all mainly idle), EIDE drive (DOS, idle), SMC 9332 (mostly idle), sound card (active, but just pass-through from my walkman...); external serial ports disabled in BIOS. Mark. -- Mark Valentine at Home From owner-freebsd-current Sun Nov 10 08:52:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA19049 for current-outgoing; Sun, 10 Nov 1996 08:52:40 -0800 (PST) Received: from janai.thuvia.org (linus.demon.co.uk [158.152.10.220]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA19042 for ; Sun, 10 Nov 1996 08:52:35 -0800 (PST) Received: (from mark@localhost) by janai.thuvia.org (8.8.2/8.8.2) id QAA11893 for freebsd-current@freebsd.org; Sun, 10 Nov 1996 16:52:51 GMT Message-Id: <199611101652.QAA11893@janai.thuvia.org> From: mark@linus.demon.co.uk (Mark Valentine) Date: Sun, 10 Nov 1996 16:52:51 +0000 X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: freebsd-current@freebsd.org Subject: anyone have cvs-cur.2482.gz? Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm missing this CTM update. If anyone has it lying around, it would save me a *lot* of modem time catching up from a newer 'A' delta! Cheers, Mark. -- Mark Valentine at Home From owner-freebsd-current Sun Nov 10 09:14:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA19909 for current-outgoing; Sun, 10 Nov 1996 09:14:15 -0800 (PST) Received: from grackle.grondar.za (root@grackle.grondar.za [196.7.18.131]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA19898 for ; Sun, 10 Nov 1996 09:14:05 -0800 (PST) Received: from grackle.grondar.za (mark@localhost.grondar.za [127.0.0.1]) by grackle.grondar.za (8.8.2/8.7.3) with ESMTP id TAA01423; Sun, 10 Nov 1996 19:13:57 +0200 (SAT) Message-Id: <199611101713.TAA01423@grackle.grondar.za> To: mark@linus.demon.co.uk (Mark Valentine) cc: freebsd-current@freebsd.org Subject: Re: anyone have cvs-cur.2482.gz? Date: Sun, 10 Nov 1996 19:13:52 +0200 From: Mark R V Murray Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk wrote: > I'm missing this CTM update. If anyone has it lying around, it would > save me a *lot* of modem time catching up from a newer 'A' delta! You can find it at ftp://ftp.za.freebsd.org/pub/FreeBSD/CTM/cvs-cur/cvs-cur.2482.gz M -- Mark Murray PGP key fingerprint = 80 36 6E 40 83 D6 8A 36 This .sig is umop ap!sdn. BC 06 EA 0E 7A F2 CE CE From owner-freebsd-current Sun Nov 10 09:57:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA21610 for current-outgoing; Sun, 10 Nov 1996 09:57:55 -0800 (PST) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA21583; Sun, 10 Nov 1996 09:57:43 -0800 (PST) Received: by sovcom.kiae.su id AA09890 (5.65.kiae-1 ); Sun, 10 Nov 1996 20:47:23 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Sun, 10 Nov 96 20:47:23 +0300 Received: (from ache@localhost) by nagual.ru (8.8.2/8.8.2) id UAA00409; Sun, 10 Nov 1996 20:36:19 +0300 (MSK) Message-Id: <199611101736.UAA00409@nagual.ru> Subject: Re: SCSI system becomes broken in -current? In-Reply-To: <96Nov9.230310pst.177557@crevenia.parc.xerox.com> from "Bill Fenner" at "Nov 9, 96 11:03:01 pm" To: fenner@parc.xerox.com (Bill Fenner) Date: Sun, 10 Nov 1996 20:36:18 +0300 (MSK) Cc: gibbs@freefall.freebsd.org, current@freebsd.org, scsi@freebsd.org From: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) Organization: self X-Class: Fast X-Mailer: ELM [version 2.4ME+ PL28 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > In message <199611100215.SAA04532@freefall.freebsd.org> you write: > >I tried www.conner.com, but Seagate has that now... > > Seagate bought Conner earlier this year. They have all the conner-related > stuff mixed in on their web and ftp site. (e.g. look through the drive > model numbers and you will find the CFP1080S, etc.) I already do it, their WWW/FTP have only CFP1060S jumper settings... BTW, I already have an upgrade (thanx to Serge) and it fix tagged queueing bug really. -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Sun Nov 10 10:13:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA22552 for current-outgoing; Sun, 10 Nov 1996 10:13:52 -0800 (PST) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA22544; Sun, 10 Nov 1996 10:13:47 -0800 (PST) Message-Id: <199611101813.KAA22544@freefall.freebsd.org> To: Mike Hench cc: freebsd-current@freebsd.org Subject: Re: scsi lockups (Was Stop me b4 i kill again) In-reply-to: Your message of "Sun, 10 Nov 1996 08:19:34 CST." <199611101419.IAA08071@watt.cae.uwm.edu> Date: Sun, 10 Nov 1996 10:13:47 -0800 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Is this a pci card? If so, can you try options "AHC_FORCE_PIO"? >> >yes pci, >AHC_FORCE_PIO *works*. >so what does it mean ? It means that your motherboard doesn't support memory mapped I/O. This setting forces the driver to ignore the memory mapped address space the BIOS configured for the chip and use programmed I/O instead. >thanks again >mike hench >hench@cae.uwm.edu > -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Sun Nov 10 11:26:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA27148 for current-outgoing; Sun, 10 Nov 1996 11:26:11 -0800 (PST) Received: from dyson.iquest.net ([198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA27140 for ; Sun, 10 Nov 1996 11:26:07 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id OAA06336 for current@freebsd.org; Sun, 10 Nov 1996 14:26:06 -0500 (EST) From: "John S. Dyson" Message-Id: <199611101926.OAA06336@dyson.iquest.net> Subject: Bad news: kind-of about page coloring To: current@freebsd.org Date: Sun, 10 Nov 1996 14:26:05 -0500 (EST) Reply-To: dyson@freebsd.org X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As some of you know, I just got a PP motherboard (mostly to be able to work on SMP in the near future.) For now, I just have one processor, and have been studying it (in relation to FreeBSD.) As I kind-of expected due to the 4 way 2nd level cache on the PP, the page coloring code appears to be more of a hinderance than an advantage. I did find a significant improvement on the Pentium though. Just to let you know, I am going to make the coloring code work by setting itself up at runtime as opposed to compile time. The coloring code does have a liability of messing up our page caching stats (a little bit), but since the the PP cache is 4 way associative, we don't need the coloring nearly as much. So, IMO, coloring appears to be generally bad on the PPro. John From owner-freebsd-current Sun Nov 10 11:58:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA29742 for current-outgoing; Sun, 10 Nov 1996 11:58:42 -0800 (PST) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA29735 for ; Sun, 10 Nov 1996 11:58:39 -0800 (PST) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <15759(6)>; Sun, 10 Nov 1996 11:58:06 PST Received: from localhost by crevenia.parc.xerox.com with SMTP id <177557>; Sun, 10 Nov 1996 11:57:53 -0800 To: Denis DeLaRoca 825-4580 (310) cc: current@freebsd.org Subject: Re: bpf-1.1, libpcap-0.2.1 and tcpdump-3.2.1 In-reply-to: Your message of "Sun, 10 Nov 96 01:51:00 PST." <199611100951.BAA26958@freefall.freebsd.org> Date: Sun, 10 Nov 1996 11:57:47 PST From: Bill Fenner Message-Id: <96Nov10.115753pst.177557@crevenia.parc.xerox.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199611100951.BAA26958@freefall.freebsd.org> you write: >Will these new versions make into the 2.2 release? libpcap-0.2.1 and tcpdump-3.2.1 are in contrib. There are several diff's between bpf-1.1 and the bpf that's in the FreeBSD tree. Some of them seem to be the same thing done in different ways, some of them might be different functionality. Is there anything specific that bpf-1.1 does that FreeBSD's doesn't that you need? Bill From owner-freebsd-current Sun Nov 10 13:44:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA06791 for current-outgoing; Sun, 10 Nov 1996 13:44:33 -0800 (PST) Received: from inga.augusta.de (root@inga.augusta.de [193.175.23.65]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA06772 for ; Sun, 10 Nov 1996 13:44:26 -0800 (PST) Received: from rabbit by inga.augusta.de with uucp (Smail3.1.29.1 #1) id m0vMhaN-004cqwC; Sun, 10 Nov 96 22:38 MET Received: by rabbit.augusta.de (Smail3.1.29.1 #1) id m0vMZah-000A1XC; Sun, 10 Nov 96 14:06 MET Message-Id: Date: Sun, 10 Nov 96 14:06 MET X-Newsreader: knews 0.9.6 Organization: Privat Site running FreeBSD References: <5001.847289114@critter.tfs.com> From: shanee@rabbit.augusta.de (Andreas Kohout) Subject: Re: please test -currents kernel X-Original-Newsgroups: muc.lists.freebsd.current In-Reply-To: <5001.847289114@critter.tfs.com> To: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <5001.847289114@critter.tfs.com>, phk@critter.tfs.com (Poul-Henning Kamp) writes: > Please test the kernel in -current as much as you can. I use thr kernel at Nov 05th 96 with SCSI (Disk, Tape, CD) and there are no problems! Five day´s uptime ... -- Greeting, Andy running FreeBSD-current --------------------------------------------------------------------------- From owner-freebsd-current Sun Nov 10 15:41:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA00547 for current-outgoing; Sun, 10 Nov 1996 15:41:29 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA00537; Sun, 10 Nov 1996 15:41:27 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id OAA26827 ; Sun, 10 Nov 1996 14:50:07 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA17065; Sun, 10 Nov 1996 15:40:42 -0700 From: Terry Lambert Message-Id: <199611102240.PAA17065@phaeton.artisoft.com> Subject: Re: Bad news: kind-of about page coloring To: dyson@freebsd.org Date: Sun, 10 Nov 1996 15:40:42 -0700 (MST) Cc: current@freebsd.org In-Reply-To: <199611101926.OAA06336@dyson.iquest.net> from "John S. Dyson" at Nov 10, 96 02:26:05 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > As some of you know, I just got a PP motherboard (mostly to be able > to work on SMP in the near future.) For now, I just have one processor, > and have been studying it (in relation to FreeBSD.) As I kind-of expected > due to the 4 way 2nd level cache on the PP, the page coloring code appears > to be more of a hinderance than an advantage. I did find a significant > improvement on the Pentium though. Just to let you know, I am going to > make the coloring code work by setting itself up at runtime as opposed > to compile time. The coloring code does have a liability of messing up > our page caching stats (a little bit), but since the the PP cache is > 4 way associative, we don't need the coloring nearly as much. So, IMO, > coloring appears to be generally bad on the PPro. I'm a bit curious: how would you gage the associativity of a two processor system? Ie: is it possible that an N processor (N>1) PP system would still benefit from coloring if it was layered on top of the coherency model? I assume the code is on top of the coherency model, in any case... 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-current Sun Nov 10 15:49:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA00996 for current-outgoing; Sun, 10 Nov 1996 15:49:15 -0800 (PST) Received: from cicerone.uunet.ca (root@cicerone.uunet.ca [142.77.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA00990 for ; Sun, 10 Nov 1996 15:49:11 -0800 (PST) Received: from why.whine.com ([205.150.249.1]) by mail.uunet.ca with ESMTP id <115212-19838>; Sun, 10 Nov 1996 14:49:02 -0500 Received: from why (andrew@why [205.150.249.1]) by why.whine.com (8.7.6/8.6.12) with SMTP id SAA00256 for ; Sun, 10 Nov 1996 18:48:41 -0500 (EST) Date: Sun, 10 Nov 1996 18:48:40 -0500 From: Andrew Herdman X-Sender: andrew@why To: current@freebsd.org Subject: Crash doing make world. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I get the following crash doing a make world on current (sup'd last night). I haven't been able to build a make world in over two weeks due to these crashes. It was building libg++ when the following occured: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x24 fault code = supervisor read, page not present instruction pointer = 0x8:0xf017dce0 stack pointer = 0x10:0xefbffeb0 frame pointer = 0x10:0xefbffebc code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 13794 (cc1plus) interrupt mask = net bio panic: page fault ---------------------Kernel Configuration File------------------------- machine "i386" cpu "I586_CPU" ident WHY maxusers 10 options "MAXMEM=(96*1024)" options "CLK_USE_I586_CALIBRATION" options "CLK_USE_I8254_CALIBRATION" options "I586_FAST_BCOPY" options "SHOW_BUSYBUFS" options "SYSVSHM" options "SYSVSEM" options "SYSVMSG" options "SHMMAX=16777216" options "SHMALL=16384" options "INET" options "MROUTING" options "FFS" options "MSDOSFS" options "CD9660" options "PROCFS" options "KERNFS" options "COMPAT_43" options "UCONSOLE" options "FAT_CURSOR" options "SCSI_DELAY=3" options "NCONS=5" options "NSWAPDEV=5" options "DUMMY_NOPS" options "KTRACE" options "NMBCLUSTERS=128" options "COMPAT_LINUX" options "LINUX" options "CHILD_MAX=128" options "OPEN_MAX=128" options "USER_LDT" options "AUTO_EOI_1" options "ATAPI" options "ATAPI_STATIC" options "FAILSAFE" config kernel root on sd0 swap on sd0 controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr controller bt0 controller ncr0 controller scbus0 at bt0 controller scbus1 at ncr0 controller snd0 controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk fd0 at fdc0 drive 0 device wcd0 device sd0 at scbus0 target 0 device sd1 at scbus0 target 1 device sd2 at scbus0 target 2 device sd3 at scbus0 target 3 device sd4 at scbus0 target 4 device sd10 at scbus1 target 0 device st0 device cd0 device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr 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 lpt0 at isa? port? tty irq 7 vector lptintr device joy0 at isa? port "IO_GAME" device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr device sbxvi0 at isa? drq 6 device sbmidi0 at isa? port 0x330 device opl0 at isa? port 0x388 conflicts device ed1 at isa? port 0x300 net irq 10 iomem 0xd0000 vector edintr device dgb0 at isa? port 0x100 iomem 0xfc0000 iosiz ? tty pseudo-device loop pseudo-device ether pseudo-device log pseudo-device speaker pseudo-device vn pseudo-device ccd 4 pseudo-device tun 4 pseudo-device pty 32 pseudo-device bpfilter 4 pseudo-device disc -----------------End of Kernel Configuration File------------------------- The make world environment is a chroot'd onto sd10a on the ncr controller. I've also noticed that sometimes sup'ping to this disk also cause panics. The bt0 bus has not caused any problems at all. I'm wondering if the problem lies with the NCR driver, perhaps it was sick when I last made world (i think it was around the time 1014-SNAP was released). I'd like to provide the dumps (vmcore.0 and kernel.0) but with 96mb of ram they are huge... and i've only got 28.8k. I waiting to see how gzip does on it. But if you need the info perhaps giving me the commands to get the info required would be the easiest. I appreciate any help into this problem and will do what I can to help from my end. Thanks Andrew From owner-freebsd-current Sun Nov 10 15:49:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA01024 for current-outgoing; Sun, 10 Nov 1996 15:49:52 -0800 (PST) Received: from dyson.iquest.net ([198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA01017; Sun, 10 Nov 1996 15:49:46 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id SAA00301; Sun, 10 Nov 1996 18:48:46 -0500 (EST) From: "John S. Dyson" Message-Id: <199611102348.SAA00301@dyson.iquest.net> Subject: Re: Bad news: kind-of about page coloring To: terry@lambert.org (Terry Lambert) Date: Sun, 10 Nov 1996 18:48:46 -0500 (EST) Cc: dyson@freebsd.org, current@freebsd.org In-Reply-To: <199611102240.PAA17065@phaeton.artisoft.com> from "Terry Lambert" at Nov 10, 96 03:40:42 pm Reply-To: dyson@freebsd.org X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I'm a bit curious: how would you gage the associativity of a two > processor system? > I have an SMP capable MB now, and will soon be working with the SMP guys a little bit. Hopefully, I'll be able to check this out. I would guess that it won't help an SMP P6 much at all, but it will still help the P5 (usually direct-mapped.) We'll certainly find out!!! John From owner-freebsd-current Sun Nov 10 18:34:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA06441 for current-outgoing; Sun, 10 Nov 1996 18:34:09 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA06433 for ; Sun, 10 Nov 1996 18:34:04 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id NAA04685; Mon, 11 Nov 1996 13:02:45 +1030 (CST) From: Michael Smith Message-Id: <199611110232.NAA04685@genesis.atrad.adelaide.edu.au> Subject: Re: syscons and mono VGA screens? In-Reply-To: <199611091055.LAA10906@uriah.heep.sax.de> from J Wunsch at "Nov 9, 96 11:55:26 am" To: joerg_wunsch@uriah.heep.sax.de Date: Mon, 11 Nov 1996 13:02:44 +1030 (CST) Cc: freebsd-current@FreeBSD.org, msmith@atrad.adelaide.edu.au 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-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch stands accused of saying: > > > (There's also an annoying delay when adding the default route, despite my > > adding '-n' to the 'route add' line in netstart. The machine has two > > ethernets, and resolves via a local nameserver, so I can only guess that > > -n is not having the desired effect.) > > -n does only have an effect on reverse lookups to translate addresses > into names when printing. You gotta explicit use numerical addresses > in your case -- how else should the names translate into addresses > otherwise? route -n add -interface 129.127.96.120 which takes no time at all once the system is up, causes a resolver-timeout-like delay when specified via defaultrouter="-interface 129.127.96.120" in /etc/sysconfig. > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Sun Nov 10 18:35:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA06552 for current-outgoing; Sun, 10 Nov 1996 18:35:43 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA06543; Sun, 10 Nov 1996 18:35:33 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id NAA04705; Mon, 11 Nov 1996 13:04:31 +1030 (CST) From: Michael Smith Message-Id: <199611110234.NAA04705@genesis.atrad.adelaide.edu.au> Subject: Re: syscons and mono VGA screens? In-Reply-To: <199611091604.RAA03165@ravenock.cybercity.dk> from "sos@FreeBSD.org" at "Nov 9, 96 05:04:18 pm" To: sos@FreeBSD.org Date: Mon, 11 Nov 1996 13:04:31 +1030 (CST) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.org, msmith@atrad.adelaide.edu.au X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk sos@FreeBSD.org stands accused of saying: > > I'll look at it as soon as I get a few minutes... > Has anybody tried uncommenting the lines around 2369 and see if that > helps ? Sorry, the machine is remote and rather vital. If you think that this will help, I can possibly arrange to try it in about a week 8( 8( > Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Sun Nov 10 19:27:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA08253 for current-outgoing; Sun, 10 Nov 1996 19:27:26 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA08247 for ; Sun, 10 Nov 1996 19:27:21 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id NAA05096 for current@freebsd.org; Mon, 11 Nov 1996 13:57:11 +1030 (CST) From: Michael Smith Message-Id: <199611110327.NAA05096@genesis.atrad.adelaide.edu.au> Subject: Updates for UserConfig To: current@freebsd.org Date: Mon, 11 Nov 1996 13:57:10 +1030 (CST) 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I can't get to freefall at the moment (I presume it's still down for PM). The following attempt to address the drivers missing from UserConfig's database, and improves the handling of unknown or changed PCI devices. This should _properly_ fix Joerg's problem. Poul, _please_ consider at least the code portion of this for 2.2; as it stands, UserConfig can be fatally confused by unknown devices. --- userconfig.c.old Mon Nov 11 13:35:03 1996 +++ userconfig.c Mon Nov 11 13:47:13 1996 @@ -259,6 +259,11 @@ {"cx", "Cronyx/Sigma multiport sync/async adapter",0, CLS_COMMS}, {"rc", "RISCom/8 multiport async adapter", 0, CLS_COMMS}, {"cy", "Cyclades multiport async adapter", 0, CLS_COMMS}, +{"cyy", "Cyclades Ye/PCI multiport async adapter",FLG_INVISBLE, CLS_COMMS}, +{"dgb", "Digiboard PC/Xe, PC/Xi async adapter", 0, CLS_COMMS}, +{"si", "Specialix SI/XIO async adapter", 0, CLS_COMMS}, +{"stl", "Stallion EasyIO/Easy Connection 8/32 async adapter",0, CLS_COMMS}, +{"stli", "Stallion intelligent async adapter" ,0, CLS_COMMS}, {"lpt", "Parallel printer port", 0, CLS_COMMS}, {"gp", "National Instruments AT-GPIB/TNT driver", 0, CLS_COMMS}, @@ -282,7 +287,9 @@ {"pca", "PC speaker PCM audio driver", FLG_FIXED, CLS_MMEDIA}, {"ctx", "Coretex-I frame grabber", 0, CLS_MMEDIA}, {"spigot", "Creative Labs Video Spigot video capture", 0, CLS_MMEDIA}, +{"scc", "IBM Smart Capture Card", 0, CLS_MMEDIA}, {"gsc", "Genius GS-4500 hand scanner", 0, CLS_MMEDIA}, +{"asc", "AmiScan scanner", 0, CLS_MMEDIA}, {"qcam", "QuickCam parallel port camera", 0, CLS_MMEDIA}, {"apm", "Advanced Power Management", FLG_FIXED, CLS_MISC}, @@ -673,11 +680,10 @@ while (list) { - if ((list->comment == DEV_DEVICE) && list->changed) - { - if ((list->iobase == -2) || /* is a PCI device; can't save */ - (list->device == NULL)) /* no isa_device associated at all?! */ - continue; + if ((list->comment == DEV_DEVICE) && /* is a device */ + (list->changed) && /* has been changed */ + (list->iobase != -2) && /* is not a PCI device */ + (list->device != NULL)) { /* has an isa_device structure */ setdev(list,active); /* set the device itself */ -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Sun Nov 10 19:50:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA09590 for current-outgoing; Sun, 10 Nov 1996 19:50:49 -0800 (PST) Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA09584 for ; Sun, 10 Nov 1996 19:50:45 -0800 (PST) Received: from katiska.clinet.fi (root@katiska.clinet.fi [194.100.0.4]) by hauki.clinet.fi (8.7.6/8.6.4) with ESMTP id FAA06567; Mon, 11 Nov 1996 05:50:42 +0200 (EET) Received: (hsu@localhost) by katiska.clinet.fi (8.8.2/8.6.4) id FAA14681; Mon, 11 Nov 1996 05:50:42 +0200 (EET) Date: Mon, 11 Nov 1996 05:50:42 +0200 (EET) Message-Id: <199611110350.FAA14681@katiska.clinet.fi> From: Heikki Suonsivu To: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) Cc: freebsd-current@freebsd.org Subject: Re: SCSI system becomes broken in -current? In-Reply-To: <199611101749.UAA00486@nagual.ru> References: <199611100815.KAA27253@cantina.clinet.fi> <199611101749.UAA00486@nagual.ru> Organization: Clinet Ltd, Espoo, Finland Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk KOI8-R writes: > > From: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) > > BTW, SCB Paging still not work for two devices and cause > > serious inode damages as before. It work for any of device alone. > > > > What kind of inode damage ? We are not using SCB paging, but anything > > later than Aug 19 kernel corrupts filesystems, the more damage the more io > > (on news servers kernels are ununsable, crash within 24 hours, usually > > within couple of hours). > > I got junk written to inode area immediately after boot. It is stable > effect with SCB paging enabled with two devices. This may be different. We see crashes after which randomly around the disk, usually files which were in use/written at the time of crash. It always results in fsck reporting sequences of DUP/BAD inodes (one blockfull of them, I assume). > -- > Andrey A. Chernov > > http://www.nagual.ru/~ache/ -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@clinet.fi mobile +358-40-5519679 work +358-9-43542270 fax -4555276 From owner-freebsd-current Sun Nov 10 22:26:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA19585 for current-outgoing; Sun, 10 Nov 1996 22:26:56 -0800 (PST) Received: from MVS.OAC.UCLA.EDU (mvs.oac.ucla.edu [164.67.200.200]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA19564 for ; Sun, 10 Nov 1996 22:26:50 -0800 (PST) Message-Id: <199611110626.WAA19564@freefall.freebsd.org> Received: from UCLAMVS.BITNET by MVS.OAC.UCLA.EDU (IBM MVS SMTP V2R2.1) with BSMTP id 1528; Sun, 10 Nov 96 22:26:53 PST Date: Sun, 10 Nov 96 22:26 PST To: Bill Fenner From: Denis DeLaRoca (310) 825-4580 Subject: Re: Re: bpf-1.1, libpcap-0.2.1 and tcpdump-3.2.1 CC: current@FREEBSD.ORG Sender: owner-current@FREEBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 10 Nov 1996 11:57:47 PST, Bill Fenner said: > In message <199611100951.BAA26958@freefall.freebsd.org> you write: > > There are several diff's between bpf-1.1 and the bpf that's in the FreeBSD > tree. Some of them seem to be the same thing done in different ways, > some of them might be different functionality. Is there anything specific > that bpf-1.1 does that FreeBSD's doesn't that you need? Humm? The bpf-1.1 change log shows fixes for various ioctl bugs, fixes for promiscuous mode handling, a fix with the handling of BIOCSRTIMEOUT whihc may or may not be relevant to the FreeBSD version... but perhaps the bpf filter (minor) fixes are more relevant? My only concern was to have the bpf code as of up to date and bug-free as possible. -- Denis From owner-freebsd-current Sun Nov 10 22:46:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA21302 for current-outgoing; Sun, 10 Nov 1996 22:46:44 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA21293 for ; Sun, 10 Nov 1996 22:46:41 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id RAA06552 for current@freebsd.org; Mon, 11 Nov 1996 17:16:32 +1030 (CST) From: Michael Smith Message-Id: <199611110646.RAA06552@genesis.atrad.adelaide.edu.au> Subject: vi unusable? To: current@freebsd.org Date: Mon, 11 Nov 1996 17:16:31 +1030 (CST) 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Now I hate vi as much as anyone else, but there are times when it's handy to use. Those of us that don't have hjkl wired into our fingers tend to go for the cursor keys to move around though, and I've noticed on a couple of -current systems I just set up that hitting a cursor key in move mode wins you a beep and you drop into insert mode. Extremely annoying. I've experienced this on the console, under X, and telnetted in both fast (local ether) and slow (SLIP link), on several machines. Anyone else? -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Sun Nov 10 23:05:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA22606 for current-outgoing; Sun, 10 Nov 1996 23:05:45 -0800 (PST) Received: from grackle.grondar.za (root@grackle.grondar.za [196.7.18.131]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA22558 for ; Sun, 10 Nov 1996 23:05:29 -0800 (PST) Received: from grackle.grondar.za (mark@localhost.grondar.za [127.0.0.1]) by grackle.grondar.za (8.8.2/8.7.3) with ESMTP id JAA14789; Mon, 11 Nov 1996 09:04:50 +0200 (SAT) Message-Id: <199611110704.JAA14789@grackle.grondar.za> To: Michael Smith cc: current@freebsd.org Subject: Re: vi unusable? Date: Mon, 11 Nov 1996 09:04:49 +0200 From: Mark R V Murray Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Michael Smith wrote: > > Now I hate vi as much as anyone else, but there are times when it's > handy to use. Those of us that don't have hjkl wired into our fingers > tend to go for the cursor keys to move around though, and I've noticed > on a couple of -current systems I just set up that hitting a cursor > key in move mode wins you a beep and you drop into insert mode. > Extremely annoying. > > I've experienced this on the console, under X, and telnetted in both fast > (local ether) and slow (SLIP link), on several machines. > > Anyone else? Yup, Me. It mostly happens in XTerms, and happens when i am hittin lots of cursor keys. Sooner or later, one of them turns into an input and I get D D D D Or the like and I start practising my swearword vocabulary. This mostly happens over ethernet to a SUN, but also happens FreeBSD<->FreeBSD. M -- Mark Murray PGP key fingerprint = 80 36 6E 40 83 D6 8A 36 This .sig is umop ap!sdn. BC 06 EA 0E 7A F2 CE CE From owner-freebsd-current Sun Nov 10 23:18:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA23549 for current-outgoing; Sun, 10 Nov 1996 23:18:23 -0800 (PST) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA23544 for ; Sun, 10 Nov 1996 23:18:20 -0800 (PST) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <14478(7)>; Sun, 10 Nov 1996 23:17:45 PST Received: by crevenia.parc.xerox.com id <177557>; Sun, 10 Nov 1996 23:17:34 -0800 From: Bill Fenner To: current@freebsd.org, msmith@atrad.adelaide.edu.au Subject: Re: vi unusable? Message-Id: <96Nov10.231734pst.177557@crevenia.parc.xerox.com> Date: Sun, 10 Nov 1996 23:17:26 PST Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Try "set escapetime=10". That should make vi wait a full second for the rest of the characters. The default is 1 (= 1/10 second), which should be good enough for the console, so perhaps its timing is broken. Bill From owner-freebsd-current Sun Nov 10 23:33:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA24417 for current-outgoing; Sun, 10 Nov 1996 23:33:11 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA24401 for ; Sun, 10 Nov 1996 23:33:04 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id SAA06910; Mon, 11 Nov 1996 18:02:58 +1030 (CST) From: Michael Smith Message-Id: <199611110732.SAA06910@genesis.atrad.adelaide.edu.au> Subject: Re: vi unusable? In-Reply-To: <96Nov10.231734pst.177557@crevenia.parc.xerox.com> from Bill Fenner at "Nov 10, 96 11:17:26 pm" To: fenner@parc.xerox.com (Bill Fenner) Date: Mon, 11 Nov 1996 18:02:57 +1030 (CST) Cc: current@freebsd.org, msmith@atrad.adelaide.edu.au 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Bill Fenner stands accused of saying: > Try "set escapetime=10". That should make vi wait a full second for the > rest of the characters. The default is 1 (= 1/10 second), which should > be good enough for the console, so perhaps its timing is broken. escapetime=3 is adequate for a 14k SLIP link. escapetime=2 is necessary for local xterm operation. This is with : Version 1.79 (10/23/96) The CSRG, University of California, Berkeley. The older version on my system at home is usable as-is with its defaults over several laggy 14k links : Version 1.34, Thu Aug 18 04:07:48 1994 The CSRG, University of California, Berkeley. > Bill -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Sun Nov 10 23:44:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA25429 for current-outgoing; Sun, 10 Nov 1996 23:44:27 -0800 (PST) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA25424 for ; Sun, 10 Nov 1996 23:44:23 -0800 (PST) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id IAA16415; Mon, 11 Nov 1996 08:44:02 +0100 Message-Id: <199611110744.IAA16415@ra.dkuug.dk> Subject: Re: wt driver broken! To: joerg_wunsch@uriah.heep.sax.de Date: Mon, 11 Nov 1996 08:44:01 +0100 (MET) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199611101050.LAA09750@uriah.heep.sax.de> from "J Wunsch" at Nov 10, 96 11:50:23 am From: sos@FreeBSD.org Reply-to: sos@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In reply to J Wunsch who wrote: > > I can't get my couple of `wt' drives recognized anymore in -current. > (One is an Archive, one is a Wangtek.) > > Do other people experience the same, or is it just my hardware? > > I wouldn't love it to ship 2.2R with a broken driver... I have one too, I'll try to find it in the attic tonight at try it... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-current Sun Nov 10 23:49:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA25928 for current-outgoing; Sun, 10 Nov 1996 23:49:45 -0800 (PST) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA25921; Sun, 10 Nov 1996 23:49:42 -0800 (PST) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id IAA16459; Mon, 11 Nov 1996 08:49:24 +0100 Message-Id: <199611110749.IAA16459@ra.dkuug.dk> Subject: Re: New PS/2 mouse driver stalled To: nate@mt.sri.com (Nate Williams) Date: Mon, 11 Nov 1996 08:49:24 +0100 (MET) Cc: current@FreeBSD.org, sos@FreeBSD.org In-Reply-To: <199611101625.JAA16541@rocky.mt.sri.com> from "Nate Williams" at Nov 10, 96 09:25:26 am From: sos@FreeBSD.org Reply-to: sos@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In reply to Nate Williams who wrote: > > I have read the comments on the new syscons|ps/2 mouse driver bugs, but > looking at Bruce's comments regarding the new syscons 'polling' behavior > it looks like it wouldn't matter since it really requires a new 'combo' > driver that differentiates between keyboard interrupts and mouse > interrupts, which has been the 'goal' for a long time with no > resolution. Sigh, I've wanted to do a merge for a long time. I'm currently struggeling with taring syscons apart into smaller more generic pieces, some of wich can be optional. It should have been in 2.2 but now its a candidate for 3.0 :(. My plans for this does include the ps/2 mouse interface, so I havn't forgotten.... > I believe the new driver is 'better' than the old driver, but I don't > believe it will work any better with the syscons changes that folks are > complaining about. > > The author of the new driver would like to work on it more, and has even > provided a man-page but none of this matters until we get the > syscons/mouse interaction resolved. I agree that syscons is within it's > rights to poll the keyboard, but it means that the PS/2 driver will not > work if I read Bruce's notes correctly. After trying out a patch to clock.c that a Japanese guy sent us in a pr to fix the hanging keyboard, we _might_ have an alternative to a polling syscons (I don't like polling at any rate), I just fail to understand how the fix should cure the problem, bruce ?? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-current Mon Nov 11 00:59:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA01423 for current-outgoing; Mon, 11 Nov 1996 00:59:58 -0800 (PST) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA01415 for ; Mon, 11 Nov 1996 00:59:53 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id KAA21435 for ; Mon, 11 Nov 1996 10:01:02 +0100 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id KAA18400 for freebsd-current@freefall.cdrom.com; Mon, 11 Nov 1996 10:10:21 +0100 Date: Mon, 11 Nov 1996 10:10:21 +0100 From: Christoph Kukulies Message-Id: <199611110910.KAA18400@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.FreeBSD.org Subject: CVSup Q: some files missing Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I changed sup.de.freebsd.org to use CVSup. I used supconv to convert my supfile and it looks like CVSup is fetching the repository fine, also checks out but my /usr/src tree doesn't yet look like it used to be. COPYRIGHT Makefile TODO are missing. As I'm also a sup server, I assume it is correct that I run update-all after a CVSsup, right? --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Mon Nov 11 02:42:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA07175 for current-outgoing; Mon, 11 Nov 1996 02:42:31 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA07169 for ; Mon, 11 Nov 1996 02:42:28 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.2/8.6.9) with ESMTP id CAA01933; Mon, 11 Nov 1996 02:42:05 -0800 (PST) To: Christoph Kukulies cc: freebsd-current@freefall.freebsd.org Subject: Re: CVSup Q: some files missing In-reply-to: Your message of "Mon, 11 Nov 1996 10:10:21 +0100." <199611110910.KAA18400@gilberto.physik.rwth-aachen.de> Date: Mon, 11 Nov 1996 02:42:05 -0800 Message-ID: <1931.847708925@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > checks out but my /usr/src tree doesn't yet look like it used to be. > > COPYRIGHT Makefile TODO are missing. And you have src-base in your supfile? > As I'm also a sup server, I assume it is correct that I run update-all > after a CVSsup, right? That's correct. *shudder* - death to sup! long live cvsup! :-) Jordan From owner-freebsd-current Mon Nov 11 03:03:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA07807 for current-outgoing; Mon, 11 Nov 1996 03:03:34 -0800 (PST) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA07800 for ; Mon, 11 Nov 1996 03:03:28 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id MAA23736; Mon, 11 Nov 1996 12:04:36 +0100 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id MAA20009; Mon, 11 Nov 1996 12:13:56 +0100 Message-Id: <199611111113.MAA20009@gilberto.physik.rwth-aachen.de> Date: Mon, 11 Nov 1996 12:13:56 +0100 From: kuku@gilberto.physik.rwth-aachen.de (Christoph Kukulies) To: jkh@time.cdrom.com (Jordan K. Hubbard) Cc: kuku@gilberto.physik.rwth-aachen.de (Christoph Kukulies), freebsd-current@freefall.freebsd.org Subject: Re: CVSup Q: some files missing References: <199611110910.KAA18400@gilberto.physik.rwth-aachen.de> <1931.847708925@time.cdrom.com> X-Mailer: Mutt 0.48.1 Mime-Version: 1.0 In-Reply-To: <1931.847708925@time.cdrom.com>; from "Jordan K. Hubbard" on Nov 11, 1996 02:42:05 -0800 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard writes: > > checks out but my /usr/src tree doesn't yet look like it used to be. > > > > COPYRIGHT Makefile TODO are missing. > > And you have src-base in your supfile? Yes, I have. But it seems I found it. I was using the wrong cvsupfile in my sup script. Up to another try. > > > As I'm also a sup server, I assume it is correct that I run update-all > > after a CVSsup, right? > > That's correct. *shudder* - death to sup! long live cvsup! :-) > > Jordan -- --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Mon Nov 11 04:15:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA10438 for current-outgoing; Mon, 11 Nov 1996 04:15:24 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA10417; Mon, 11 Nov 1996 04:15:14 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id XAA11539; Mon, 11 Nov 1996 23:06:20 +1100 Date: Mon, 11 Nov 1996 23:06:20 +1100 From: Bruce Evans Message-Id: <199611111206.XAA11539@godzilla.zeta.org.au> To: 100120.3121@CompuServe.COM, Tor.Egge@idt.ntnu.no Subject: Re: Follow on Atlantis board Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >When using gdb on /usr/obj/usr/src/sys/i386/boot/biosboot/boot in >FreeBSD 3.0-current and disassembling the boot function, you'll >see that early in the function, the boot device is placed in %edi. >The compiler correctly (according to the calling conventions) assumes >that %edi is not modified by any routine called. Both memsize() and >get_diskinfo() are called before the content of %edi is saved in the >dosdev variable. They have a good chance of stomping upon the contents >of %edi on some bioses. Good work. The problem is almost certainly in get_diskinfo(). It is documented to clobber ES:DI in some manuals: Phoenix "System BIOS ...": ES:DI = Address of Fixed Disk Parameters table Van Gilluwe "The Undocumented PC": This function does _not_ return a pointer to the drive type table as is commonly indicated in many other technical references. Ralf Brown's Interrupt List version 45: (PC,XT286,CONV,PS,ESDI,SCSI): ES:DI -> drive parameter table (floppies only) [Long bug list: sometimes bogusly returns success for drives after the last; sometimes returns wrong number of drives.] This problem apparently became serious when I optimised some things. I think dosdev used to be kept in memory, and apparently nothing important was kept in %edi. >This means that it's OK to clobber most registers except %ebx, %esi, >%edi and %ebp. (%eax is a special case, it may contain a return >value). I think the other registers are preserved as insurance against the function call protocol changing. This isn't worthwhile, since the function call protocol is more likely to change in other ways, but but I'll keep preserving all(?) registers for now. Bruce From owner-freebsd-current Mon Nov 11 05:02:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA12494 for current-outgoing; Mon, 11 Nov 1996 05:02:05 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA12488; Mon, 11 Nov 1996 05:01:59 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id XAA12713; Mon, 11 Nov 1996 23:56:32 +1100 Date: Mon, 11 Nov 1996 23:56:32 +1100 From: Bruce Evans Message-Id: <199611111256.XAA12713@godzilla.zeta.org.au> To: current@freebsd.org Subject: panic in kvtop for bad maddr Cc: dyson@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I tried putting `bootdev' (0xa0500004 = some slice on sd0a) in npx0's id_maddr. This failed because kvtop() is called on id_maddr just to print its physical address (after id_maddr has been converted from a physical address to a virtual address). The bug seems to be that kvtop() only works for valid addresses and id_maddr is invalid if it wasn't originally between 0xa0000 and 0xfffff. Config and userconfig don't restrict the address. Bruce From owner-freebsd-current Mon Nov 11 05:08:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA12708 for current-outgoing; Mon, 11 Nov 1996 05:08:21 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA12687; Mon, 11 Nov 1996 05:08:10 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id AAA13000; Tue, 12 Nov 1996 00:04:59 +1100 Date: Tue, 12 Nov 1996 00:04:59 +1100 From: Bruce Evans Message-Id: <199611111304.AAA13000@godzilla.zeta.org.au> To: 100120.3121@CompuServe.COM, bde@zeta.org.au, Tor.Egge@idt.ntnu.no Subject: Re: Follow on Atlantis board Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I wrote: >Good work. The problem is almost certainly in get_diskinfo(). It >is documented to clobber ES:DI in some manuals: > >Phoenix "System BIOS ...": > ES:DI = Address of Fixed Disk Parameters table >Van Gilluwe "The Undocumented PC": > This function does _not_ return a pointer to the drive type > table as is commonly indicated in many other technical > references. >Ralf Brown's Interrupt List version 45: > (PC,XT286,CONV,PS,ESDI,SCSI): > ES:DI -> drive parameter table (floppies only) The first 2 references have a separate section for floppies. They agree with the 3rd reference for floppies. So the floppy case is always broken, and the hard disk case is broken if BIOS implements what the 1st reference says. Bruce From owner-freebsd-current Mon Nov 11 05:41:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA13977 for current-outgoing; Mon, 11 Nov 1996 05:41:57 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA13956; Mon, 11 Nov 1996 05:41:51 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id AAA13786; Tue, 12 Nov 1996 00:37:07 +1100 Date: Tue, 12 Nov 1996 00:37:07 +1100 From: Bruce Evans Message-Id: <199611111337.AAA13786@godzilla.zeta.org.au> To: 100120.3121@CompuServe.COM, bde@zeta.org.au, Tor.Egge@idt.ntnu.no Subject: Re: Follow on Atlantis board Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I wrote: >The first 2 references have a separate section for floppies. They >agree with the 3rd reference for floppies. So the floppy case is >always broken, and the hard disk case is broken if BIOS implements >what the 1st reference says. Actually, although the bootstrap calls get_diskinfo() for floppies (if the boot drive is a floppy, in disk.c), %edi happens to usually be unused at that point, so there is usually only a problem for BIOSes that change %edi for hard disks. Bruce From owner-freebsd-current Mon Nov 11 06:36:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA17114 for current-outgoing; Mon, 11 Nov 1996 06:36:22 -0800 (PST) Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA17079 for ; Mon, 11 Nov 1996 06:36:02 -0800 (PST) Received: (from bsdcur@localhost) by shadows.aeon.net (8.7.5/8.6.9) id QAA23398 for freebsd-current@freebsd.org; Mon, 11 Nov 1996 16:35:53 +0200 (EET) From: mika ruohotie Message-Id: <199611111435.QAA23398@shadows.aeon.net> Subject: ufs is too slow? To: freebsd-current@freebsd.org Date: Mon, 11 Nov 1996 16:35:53 +0200 (EET) 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk well... i posted this to usenet too... i was wondering if there's any truth here... my friend told me that the ufs filesystem is too slow for a high end nntp server usage... the average 7 articles per second is supposed to be too much, and that using some log type filesystem, like xfs (in sgi) would be better... he was saying that ufs cant create those 7 files in the second. is that so? mickey -- mika@aeon.net mika ruohotie From owner-freebsd-current Mon Nov 11 07:04:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA18378 for current-outgoing; Mon, 11 Nov 1996 07:04:45 -0800 (PST) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA18373 for ; Mon, 11 Nov 1996 07:04:43 -0800 (PST) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id JAA19277; Mon, 11 Nov 1996 09:03:09 -0600 From: Joe Greco Message-Id: <199611111503.JAA19277@brasil.moneng.mei.com> Subject: Re: ufs is too slow? To: bsdcur@shadows.aeon.net (mika ruohotie) Date: Mon, 11 Nov 1996 09:03:09 -0600 (CST) Cc: freebsd-current@freebsd.org In-Reply-To: <199611111435.QAA23398@shadows.aeon.net> from "mika ruohotie" at Nov 11, 96 04:35:53 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > well... > > i posted this to usenet too... > > i was wondering if there's any truth here... > > my friend told me that the ufs filesystem is too slow for a high end > nntp server usage... > > the average 7 articles per second is supposed to be too much, and that > using some log type filesystem, like xfs (in sgi) would be better... > > he was saying that ufs cant create those 7 files in the second. > > is that so? I have seen peaks of Average articles per second was 15.842105263157895578 over a 300 article sample. That was, however, on a machine heavily optimized towards the task. We were flyyyyyying.... FFS is in general a great FS... but it is optimized for the general case. It is particularly poor at handling large directories or lots of writes, and news is excellent at pounding on these qualities. (see my other note this morning, or I can cc: you a copy). ... JG From owner-freebsd-current Mon Nov 11 09:06:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA26014 for current-outgoing; Mon, 11 Nov 1996 09:06:17 -0800 (PST) Received: from smily.3skel.com (3skel.com [206.138.212.40]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA26004 for ; Mon, 11 Nov 1996 09:06:11 -0800 (PST) Received: from fnur.3skel.com (root@fnur.3skel.com [192.168.0.8]) by smily.3skel.com (8.8.2/8.8.2) with ESMTP id MAA06305; Mon, 11 Nov 1996 12:04:40 -0500 (EST) Received: (from danj@localhost) by fnur.3skel.com (8.8.2/8.8.2) id MAA12463; Mon, 11 Nov 1996 12:04:35 -0500 (EST) Date: Mon, 11 Nov 1996 12:04:35 -0500 (EST) From: Dan Janowski Message-Id: <199611111704.MAA12463@fnur.3skel.com> To: bsdcur@shadows.aeon.net, jgreco@brasil.moneng.mei.com Subject: Re: ufs is too slow? Cc: freebsd-current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > my friend told me that the ufs filesystem is too slow for a high end > > nntp server usage... > > > > the average 7 articles per second is supposed to be too much, and that > > using some log type filesystem, like xfs (in sgi) would be better... > > > > he was saying that ufs cant create those 7 files in the second. > > > > is that so? > > That was, however, on a machine heavily optimized towards the task. > We were flyyyyyying.... > > FFS is in general a great FS... but it is optimized for the general case. > > It is particularly poor at handling large directories or lots of writes, > and news is excellent at pounding on these qualities. > > (see my other note this morning, or I can cc: you a copy). me, please. > ... JG At one point I had inquired about lfs (log file system), in part because of my experience with xfs (SGI's). Although lfs is not xfs, they are both better performers than ufs/ffs (which are both REALLY old, I think ufs dates from the 50's and ffs from the 70's). I have seen that OpenBSD is doing something with lfs, but I am not sure what. It would be worth while to get lfs running for sure; if you ever wondered, a lot of that disk bandwith goes to filesystem overhead. I once exchanged some e-mail with someone at BSDI and with Margo Seltzer, who was a principle for lfs. The apparent primary reason why lfs does not run here is that lfs does some wierd stuff with the ATT buffer code that is missing in 4.4-lite. I was not able to get a synopsis of what or how to get around it, but it didn't sound like lfs was broken, it's just missing some wheels. Maybe we can all talk about it a little and figure out how hard it would be to get going. If we were running a kick-ass big/fast file system, FreeBSD would capture some more of the Int(er|tra)+Net market. In addition to which, the infamous 'make world' time would surely benefit. Dan -- danj@3skel.com Triskelion Systems, Inc. New York From owner-freebsd-current Mon Nov 11 09:12:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA26427 for current-outgoing; Mon, 11 Nov 1996 09:12:27 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA26421 for ; Mon, 11 Nov 1996 09:12:24 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA20142; Mon, 11 Nov 1996 10:12:21 -0700 (MST) Date: Mon, 11 Nov 1996 10:12:21 -0700 (MST) Message-Id: <199611111712.KAA20142@rocky.mt.sri.com> From: Nate Williams To: current@freebsd.org Subject: missing email Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've been missing some email lately that I now is being sent to the list, as I'm seeing the followups but I'm not seeing the original email. I also know I'm losing email since I made two commits yesterday, and I only received the commit email for the one made to the 2.1.6 branch, but not the email for the -current commit. Does this have to do with the bad spots on the disk on freefall, or is there something else bad going on? Nate From owner-freebsd-current Mon Nov 11 09:28:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA27527 for current-outgoing; Mon, 11 Nov 1996 09:28:00 -0800 (PST) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA27514 for ; Mon, 11 Nov 1996 09:27:57 -0800 (PST) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id LAA19552; Mon, 11 Nov 1996 11:24:39 -0600 From: Joe Greco Message-Id: <199611111724.LAA19552@brasil.moneng.mei.com> Subject: Re: ufs is too slow? To: danj@3skel.com (Dan Janowski) Date: Mon, 11 Nov 1996 11:24:38 -0600 (CST) Cc: bsdcur@shadows.aeon.net, jgreco@brasil.moneng.mei.com, freebsd-current@freebsd.org In-Reply-To: <199611111704.MAA12463@fnur.3skel.com> from "Dan Janowski" at Nov 11, 96 12:04:35 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I have seen that OpenBSD is doing something with lfs, but I > am not sure what. It would be worth while to get lfs running > for sure; if you ever wondered, a lot of that disk bandwith > goes to filesystem overhead. In the specific case of "lots of small articles being accessed all over the place", yes... in general I would have to disagree :-) With the "-noatime" hack, you gain some of that bandwidth back by not having to support all the crummy metadata updates that you probably didn't care too much about anyways. > I once exchanged some e-mail with someone at BSDI and with > Margo Seltzer, who was a principle for lfs. The apparent > primary reason why lfs does not run here is that lfs does some > wierd stuff with the ATT buffer code that is missing in > 4.4-lite. I was not able to get a synopsis of what or how to > get around it, but it didn't sound like lfs was broken, it's > just missing some wheels. > > Maybe we can all talk about it a little and figure out > how hard it would be to get going. If we were running > a kick-ass big/fast file system, FreeBSD would capture > some more of the Int(er|tra)+Net market. In addition > to which, the infamous 'make world' time would surely > benefit. While I agree with this analysis, I unfortunately lack the skills and internals knowledge to even contemplate doing something like this... otherwise I would be off writing "newsfs" in a corner somewhere. ... JG From owner-freebsd-current Mon Nov 11 09:38:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA28165 for current-outgoing; Mon, 11 Nov 1996 09:38:00 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA28159 for ; Mon, 11 Nov 1996 09:37:57 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA18328; Mon, 11 Nov 1996 10:27:28 -0700 From: Terry Lambert Message-Id: <199611111727.KAA18328@phaeton.artisoft.com> Subject: Re: ufs is too slow? To: bsdcur@shadows.aeon.net (mika ruohotie) Date: Mon, 11 Nov 1996 10:27:28 -0700 (MST) Cc: freebsd-current@freebsd.org In-Reply-To: <199611111435.QAA23398@shadows.aeon.net> from "mika ruohotie" at Nov 11, 96 04:35:53 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > i posted this to usenet too... > > i was wondering if there's any truth here... > > my friend told me that the ufs filesystem is too slow for a high end > nntp server usage... > > the average 7 articles per second is supposed to be too much, and that > using some log type filesystem, like xfs (in sgi) would be better... > > he was saying that ufs cant create those 7 files in the second. > > is that so? VXFS is a log structured FS. UFS (the FFS implementation in SVR4) is within 5% of the speed of VXFS, as long as you use a comparable block size. For SVR4 defaults, this block size should be 8k for UFS (FFS). Most of the directory handling code in VXFS was ripped directly from the SVR4 UFS code. A better soloution is to go to a general soft updates mechanism as the bottom end buffer cache interface for FS's. Many (not all) of the benefits of log structuring have been highly exagerated... file create time is one of them. 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-current Mon Nov 11 09:52:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA29084 for current-outgoing; Mon, 11 Nov 1996 09:52:27 -0800 (PST) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA29079 for ; Mon, 11 Nov 1996 09:52:25 -0800 (PST) Received: from localhost (mark@localhost) by vinyl.quickweb.com (8.7.5/8.6.12) with SMTP id MAA14159; Mon, 11 Nov 1996 12:51:13 -0500 (EST) Date: Mon, 11 Nov 1996 12:51:13 -0500 (EST) From: Mark Mayo To: Nate Williams cc: current@FreeBSD.ORG Subject: Re: missing email In-Reply-To: <199611111712.KAA20142@rocky.mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 11 Nov 1996, Nate Williams wrote: > I've been missing some email lately that I now is being sent to the > list, as I'm seeing the followups but I'm not seeing the original > email. I too am noticing the same problem. I zsee follow ups, but not the original porst (or in some cases I'll see two or three posts quoted, but I didn't get those original posts..) argghh, slow link.. I'll leeave those typos. . . -Mark I also know I'm losing email since I made two commits yesterday, > and I only received the commit email for the one made to the 2.1.6 > branch, but not the email for the -current commit. > > Does this have to do with the bad spots on the disk on freefall, or is > there something else bad going on? > > > > Nate > From owner-freebsd-current Mon Nov 11 10:08:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA29955 for current-outgoing; Mon, 11 Nov 1996 10:08:49 -0800 (PST) Received: from friley216.res.iastate.edu (friley216.res.iastate.edu [129.186.78.216]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA29950 for ; Mon, 11 Nov 1996 10:08:46 -0800 (PST) Received: from friley216.res.iastate.edu (loopback [127.0.0.1]) by friley216.res.iastate.edu (8.7.6/8.7.3) with ESMTP id MAA02300; Mon, 11 Nov 1996 12:06:31 -0600 (CST) Message-Id: <199611111806.MAA02300@friley216.res.iastate.edu> X-Mailer: exmh version 1.6.9 8/22/96 To: Dan Janowski cc: bsdcur@shadows.aeon.net, jgreco@brasil.moneng.mei.com, freebsd-current@FreeBSD.ORG Subject: Re: ufs is too slow? In-reply-to: Your message of Mon, 11 Nov 1996 12:04:35 -0500. <199611111704.MAA12463@fnur.3skel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Nov 1996 12:06:31 -0600 From: Chris Csanady Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Speaking of LFS, I believe John Dyson mentioned that he was fixing/rewriting(some of) it. Also, getting the other various file systems (union, null, etc) to work for 2.2. Are you still working on any of this? Or did I confuse something? :-) Later, chris csanady >At one point I had inquired about lfs (log file system), in >part because of my experience with xfs (SGI's). Although lfs >is not xfs, they are both better performers than ufs/ffs (which >are both REALLY old, I think ufs dates from the 50's and ffs >from the 70's). >I have seen that OpenBSD is doing something with lfs, but I >am not sure what. It would be worth while to get lfs running >for sure; if you ever wondered, a lot of that disk bandwith >goes to filesystem overhead. > >I once exchanged some e-mail with someone at BSDI and with >Margo Seltzer, who was a principle for lfs. The apparent >primary reason why lfs does not run here is that lfs does some >wierd stuff with the ATT buffer code that is missing in >4.4-lite. I was not able to get a synopsis of what or how to >get around it, but it didn't sound like lfs was broken, it's >just missing some wheels. > >Maybe we can all talk about it a little and figure out >how hard it would be to get going. If we were running >a kick-ass big/fast file system, FreeBSD would capture >some more of the Int(er|tra)+Net market. In addition >to which, the infamous 'make world' time would surely >benefit. > >Dan > >-- >danj@3skel.com >Triskelion Systems, Inc. >New York > From owner-freebsd-current Mon Nov 11 10:33:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA01483 for current-outgoing; Mon, 11 Nov 1996 10:33:44 -0800 (PST) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA01478; Mon, 11 Nov 1996 10:33:35 -0800 (PST) Received: by sovcom.kiae.su id AA16704 (5.65.kiae-1 ); Mon, 11 Nov 1996 21:18:06 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Mon, 11 Nov 96 21:18:06 +0300 Received: (from ache@localhost) by nagual.ru (8.8.2/8.8.2) id VAA03132; Mon, 11 Nov 1996 21:17:18 +0300 (MSK) Message-Id: <199611111817.VAA03132@nagual.ru> Subject: locore.s is broken To: current@freebsd.org (FreeBSD-current) Date: Mon, 11 Nov 1996 21:17:07 +0300 (MSK) Cc: dyson@freebsd.org From: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) Organization: self X-Class: Fast X-Mailer: ELM [version 2.4ME+ PL28 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk cc -c -x assembler-with-cpp -DLOCORE -nostdinc -I- -I. -I../.. -I../../../include -DDUMMY_NOPS -DCOMPAT_43 -DFFS -DINET -DKERNEL ../../i386/i386/locore.s ../../i386/i386/locore.s: Assembler messages: ../../i386/i386/locore.s:705: Error: bad register name ('%cr4') ../../i386/i386/locore.s:707: Error: bad register name ('%cr4') *** Error code 1 Stop. -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Mon Nov 11 10:43:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA02116 for current-outgoing; Mon, 11 Nov 1996 10:43:17 -0800 (PST) Received: from cenotaph.snafu.de (root@gw-deadnet.snafu.de [194.121.229.33]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA02106 for ; Mon, 11 Nov 1996 10:43:02 -0800 (PST) Received: by cenotaph.snafu.de from deadline.snafu.de using smtp id m0vN1Jd-000Zn5C; Mon, 11 Nov 1996 19:42:37 +0100 (MET) (Smail-3.2 1996-Jul-4 #1) Received: by deadline.snafu.de id m0vN1Ja-00080FC; Mon, 11 Nov 1996 19:42:34 +0100 (MET) (Smail-3.2 1996-Jul-4 #1) Message-Id: From: root@deadline.snafu.de (Andreas S. Wetzel) Subject: FreeBSD-current & Creatix ISDN card? To: current@freebsd.org Date: Mon, 11 Nov 1996 19:42:34 +0100 (MET) Organization: A world stranger than you have ever imagined. X-Mailer: ELM [version 2.4ME+ PL13] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi! --- Is there any process ongoing regarding to the ISDN drivers for Creatix S0 or other SIEMENS semiconductor based cards? Where can I get in touch with the people who are working on the bisdn stuff? Which cards will run with the older nic drivers? Thankful for any advice Mickey -- (__) (@@) Andreas S. Wetzel E-mail: mickey@deadline.snafu.de /-------\/ Utrechter Strasse 41 Web: http://deadline.snafu.de/ / | || 13347 Berlin Fon: <+4930> 456 066 90 * ||----|| Germany Fax: <+4930> 456 066 91/92 ~~ ~~ From owner-freebsd-current Mon Nov 11 11:01:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA02999 for current-outgoing; Mon, 11 Nov 1996 11:01:54 -0800 (PST) Received: from dyson.iquest.net ([198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA02956; Mon, 11 Nov 1996 11:01:44 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id OAA02943; Mon, 11 Nov 1996 14:00:34 -0500 (EST) From: John Dyson Message-Id: <199611111900.OAA02943@dyson.iquest.net> Subject: Re: locore.s is broken To: ache@nagual.ru (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=) Date: Mon, 11 Nov 1996 14:00:34 -0500 (EST) Cc: current@FreeBSD.org, dyson@FreeBSD.org In-Reply-To: <199611111817.VAA03132@nagual.ru> from "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" at Nov 11, 96 09:17:07 pm Reply-To: dyson@FreeBSD.org X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > cc -c -x assembler-with-cpp -DLOCORE -nostdinc -I- -I. -I../.. -I../../../include -DDUMMY_NOPS -DCOMPAT_43 -DFFS -DINET -DKERNEL ../../i386/i386/locore.s > ../../i386/i386/locore.s: Assembler messages: > ../../i386/i386/locore.s:705: Error: bad register name ('%cr4') > ../../i386/i386/locore.s:707: Error: bad register name ('%cr4') > *** Error code 1 > AIEEE!!! I forgot to commit the change to the assembler. I'll fix it ASAP!!! Sorry... Note that you will need to rebuild the assembler. John From owner-freebsd-current Mon Nov 11 11:34:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA04999 for current-outgoing; Mon, 11 Nov 1996 11:34:05 -0800 (PST) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA04976 for ; Mon, 11 Nov 1996 11:34:00 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id UAA00518; Mon, 11 Nov 1996 20:34:49 +0100 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id UAA22929; Mon, 11 Nov 1996 20:44:19 +0100 From: Christoph Kukulies Message-Id: <199611111944.UAA22929@gilberto.physik.rwth-aachen.de> Subject: Re: FreeBSD-current & Creatix ISDN card? In-Reply-To: from "Andreas S. Wetzel" at "Nov 11, 96 07:42:34 pm" To: root@deadline.snafu.de (Andreas S. Wetzel) Date: Mon, 11 Nov 1996 20:44:18 +0100 (MET) Cc: current@FreeBSD.org Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Hi! > --- > > Is there any process ongoing regarding to the ISDN drivers for Creatix S0 > or other SIEMENS semiconductor based cards? Where can I get in touch with > the people who are working on the bisdn stuff? Which cards will run with > the older nic drivers? Join in into isdn@muc.ditec.de (It's a majordomo server I think) Creatix S0 , Teles S0, Teles 16.3 and some other brands are supported. > > Thankful for any advice > > Mickey > > -- > (__) > (@@) Andreas S. Wetzel E-mail: mickey@deadline.snafu.de > /-------\/ Utrechter Strasse 41 Web: http://deadline.snafu.de/ > / | || 13347 Berlin Fon: <+4930> 456 066 90 > * ||----|| Germany Fax: <+4930> 456 066 91/92 > ~~ ~~ > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Mon Nov 11 12:25:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA07527 for current-outgoing; Mon, 11 Nov 1996 12:25:03 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA07516 for ; Mon, 11 Nov 1996 12:24:59 -0800 (PST) Received: from critter.tfs.com ([140.145.230.177]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id MAA28623 for ; Mon, 11 Nov 1996 12:24:54 -0800 (PST) Received: from critter.tfs.com (localhost [127.0.0.1]) by critter.tfs.com (8.8.2/8.8.2) with ESMTP id NAA12676; Mon, 11 Nov 1996 13:30:24 +0100 (MET) To: Nate Williams cc: current@FreeBSD.org Subject: Re: missing email In-reply-to: Your message of "Mon, 11 Nov 1996 10:12:21 MST." <199611111712.KAA20142@rocky.mt.sri.com> Date: Mon, 11 Nov 1996 13:30:22 +0100 Message-ID: <12674.847715422@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In message <199611111712.KAA20142@rocky.mt.sri.com>, Nate Williams writes: >I've been missing some email lately that I now is being sent to the > >Does this have to do with the bad spots on the disk on freefall, or is >there something else bad going on? Probably, it didn't go quite according to the book, and some email could have been lost. Sorry. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Mon Nov 11 12:51:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA08772 for current-outgoing; Mon, 11 Nov 1996 12:51:45 -0800 (PST) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA08749 for ; Mon, 11 Nov 1996 12:51:35 -0800 (PST) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id VAA00797 for ; Mon, 11 Nov 1996 21:50:44 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id VAA05740 for freebsd-current@freebsd.org; Mon, 11 Nov 1996 21:49:56 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.2/keltia-uucp-2.9) id TAA24352; Mon, 11 Nov 1996 19:26:16 +0100 (MET) Message-ID: Date: Mon, 11 Nov 1996 19:26:15 +0100 From: roberto@keltia.freenix.fr (Ollivier Robert) To: freebsd-current@freebsd.org Subject: Re: ufs is too slow? References: <199611111704.MAA12463@fnur.3skel.com> X-Mailer: Mutt 0.50.04 Mime-Version: 1.0 X-Operating-System: FreeBSD 3.0-CURRENT ctm#2686 In-Reply-To: <199611111704.MAA12463@fnur.3skel.com>; from Dan Janowski on Nov 11, 1996 12:04:35 -0500 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Dan Janowski: > At one point I had inquired about lfs (log file system), in > part because of my experience with xfs (SGI's). Although lfs > is not xfs, they are both better performers than ufs/ffs (which Xfs is pretty fragile from what I've heard. > are both REALLY old, I think ufs dates from the 50's and ffs > from the 70's). They appeared in 1983 in a paper that you'll find in /usr/src/share/doc/papers/smm/05.fastfs. > Margo Seltzer, who was a principle for lfs. The apparent > primary reason why lfs does not run here is that lfs does some > wierd stuff with the ATT buffer code that is missing in > 4.4-lite. I was not able to get a synopsis of what or how to > get around it, but it didn't sound like lfs was broken, it's > just missing some wheels. Not exactly. It is broken in FreeBSD since the VM/Buffer cache merge and it lacks some features like fsck. John Dyson said he was working on it and hoped to have it fixed for 2.2. Now maybe 3.0. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #28: Sun Nov 10 13:37:41 MET 1996 From owner-freebsd-current Mon Nov 11 13:06:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA09837 for current-outgoing; Mon, 11 Nov 1996 13:06:13 -0800 (PST) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA09798 for ; Mon, 11 Nov 1996 13:05:46 -0800 (PST) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id WAA00885 for ; Mon, 11 Nov 1996 22:05:33 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id WAA05878 for freebsd-current@FreeBSD.org; Mon, 11 Nov 1996 22:04:49 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.2/keltia-uucp-2.9) id VAA24745; Mon, 11 Nov 1996 21:59:38 +0100 (MET) Message-ID: Date: Mon, 11 Nov 1996 21:59:37 +0100 From: roberto@keltia.freenix.fr (Ollivier Robert) To: freebsd-current@FreeBSD.org Subject: Re: ufs is too slow? References: <199611111704.MAA12463@fnur.3skel.com> <199611111724.LAA19552@brasil.moneng.mei.com> X-Mailer: Mutt 0.50.04 Mime-Version: 1.0 X-Operating-System: FreeBSD 3.0-CURRENT ctm#2686 In-Reply-To: <199611111724.LAA19552@brasil.moneng.mei.com>; from Joe Greco on Nov 11, 1996 11:24:38 -0600 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk According to Joe Greco: > internals knowledge to even contemplate doing something like this... > otherwise I would be off writing "newsfs" in a corner somewhere. Just to keep people tuned, James Brister (from ISC, author of INN 1.5 & Innfeed) is considering/working on such a file system. There is some discussion at this moment in the inn-workers list... -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #28: Sun Nov 10 13:37:41 MET 1996 From owner-freebsd-current Mon Nov 11 15:36:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA20725 for current-outgoing; Mon, 11 Nov 1996 15:36:25 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA20720 for ; Mon, 11 Nov 1996 15:36:21 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA18888; Mon, 11 Nov 1996 16:25:00 -0700 From: Terry Lambert Message-Id: <199611112325.QAA18888@phaeton.artisoft.com> Subject: Re: ufs is too slow? To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Mon, 11 Nov 1996 16:25:00 -0700 (MST) Cc: freebsd-current@freebsd.org In-Reply-To: from "Ollivier Robert" at Nov 11, 96 09:59:37 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > internals knowledge to even contemplate doing something like this... > > otherwise I would be off writing "newsfs" in a corner somewhere. > > Just to keep people tuned, James Brister (from ISC, author of INN 1.5 & > Innfeed) is considering/working on such a file system. There is some > discussion at this moment in the inn-workers list... >From what I have heard of these discussions, they are planning on internal multi indexing. This does not seem wise, since returning a file to a consistent state following a crash would be a 1:n fanout and therefore ambiguous. Much better to fix the problems another way... Article directory lookup too slow? ...Use a btree directory structure. Etc. They are probably also not considering record orientation, a must for MIME attachments or encapsulation of article header items not in 822 (which, from memory, only had a "newsgroups" and an "in-reply-to" line...). There is very little difference from a good "MIMEFS" and a good "NEWSFS". 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-current Mon Nov 11 16:11:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA23465 for current-outgoing; Mon, 11 Nov 1996 16:11:37 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA23448 for ; Mon, 11 Nov 1996 16:11:26 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id KAA12318; Tue, 12 Nov 1996 10:37:35 +1030 (CST) From: Michael Smith Message-Id: <199611120007.KAA12318@genesis.atrad.adelaide.edu.au> Subject: Re: ufs is too slow? In-Reply-To: <199611111704.MAA12463@fnur.3skel.com> from Dan Janowski at "Nov 11, 96 12:04:35 pm" To: danj@3skel.com (Dan Janowski) Date: Tue, 12 Nov 1996 10:37:34 +1030 (CST) Cc: bsdcur@shadows.aeon.net, jgreco@brasil.moneng.mei.com, freebsd-current@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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Dan Janowski stands accused of saying: > > At one point I had inquired about lfs (log file system), in > part because of my experience with xfs (SGI's). Although lfs > is not xfs, they are both better performers than ufs/ffs (which > are both REALLY old, I think ufs dates from the 50's and ffs > from the 70's). I don't know where you get this idea from. FFS, especially with some of the performance tweaks available in FreeBSD, is pretty snappy. As has been observed, SGI's xfs is rather fragile, and Terry's comments about log-structured filsystems are worth bearing in mind. > I have seen that OpenBSD is doing something with lfs, but I > am not sure what. It would be worth while to get lfs running > for sure; if you ever wondered, a lot of that disk bandwith > goes to filesystem overhead. Theo's words on lfs were essentially "I've never heard of it working outside Margo's lab", in a context which I read as "lfs is bogus". > Maybe we can all talk about it a little and figure out > how hard it would be to get going. If we were running > a kick-ass big/fast file system, FreeBSD would capture > some more of the Int(er|tra)+Net market. In addition > to which, the infamous 'make world' time would surely > benefit. I doubt that a working lfs would actually offer much, if any, in the way of performance in anything other than the applications that it handles well. As a consequence of the data acquisition stuff that we do, we often end up with directories with literally thousands of fairly large files in them; a BSD ffs filesystem mounted async,noatime is _significantly_ faster at moving/copying/deleting this sort of stuff than any of the other (Solaris, OSF, NTFS, HPFS, FAT) filesystems that we've ever put data on. One of the most notable performance improvements can actually be had by using SCSI disks and controllers that support tagged queueing; don't ever make the mistake of benchmarking an IDE based disk subsystem against anything else. > Dan -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Mon Nov 11 16:34:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA00432 for current-outgoing; Mon, 11 Nov 1996 16:34:44 -0800 (PST) Received: from smily.3skel.com (3skel.com [206.138.212.40]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA00340 for ; Mon, 11 Nov 1996 16:34:35 -0800 (PST) Received: from fnur.3skel.com (root@fnur.3skel.com [192.168.0.8]) by smily.3skel.com (8.8.2/8.8.2) with ESMTP id TAA06966; Mon, 11 Nov 1996 19:34:14 -0500 (EST) Received: (from danj@localhost) by fnur.3skel.com (8.8.2/8.8.2) id TAA15191; Mon, 11 Nov 1996 19:34:13 -0500 (EST) Date: Mon, 11 Nov 1996 19:34:13 -0500 (EST) From: Dan Janowski Message-Id: <199611120034.TAA15191@fnur.3skel.com> To: freebsd-current@FreeBSD.ORG, roberto@keltia.freenix.fr Subject: Re: ufs is too slow? Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk From: roberto@keltia.freenix.fr (Ollivier Robert) > According to Dan Janowski: > > is not xfs, they are both better performers than ufs/ffs (which > > Xfs is pretty fragile from what I've heard. SGI's XFS is actually pretty robust. We run 16 and 32GB file systems with it, and the performance is good. It can handle an FS of some-number Terabytes. It is really a journal filesystem, not a log filesystem. More like the way that relational databases work, commmiting of changes are done completely or not at all. There is no fsck (ever see an fsck run on multiple 32GB filesystems? It is really ugly), but some kind of consistancy check is done, but only doing it on the journal is necessary. > > are both REALLY old, I think ufs dates from the 50's and ffs > > from the 70's). > > They appeared in 1983 in a paper that you'll find in > /usr/src/share/doc/papers/smm/05.fastfs. Although the Berkeley FFS is a significant step up from that which preceded it, the FFS is largely of the same basis. Log or journal filesystems don't have the same kind of meta-data or data access. LFS was compared to more of a garbage-collection mechanism, and XFS as above. Dan From owner-freebsd-current Mon Nov 11 16:51:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA02240 for current-outgoing; Mon, 11 Nov 1996 16:51:56 -0800 (PST) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA02217 for ; Mon, 11 Nov 1996 16:51:47 -0800 (PST) Received: from localhost (mark@localhost) by vinyl.quickweb.com (8.7.5/8.6.12) with SMTP id TAA15322; Mon, 11 Nov 1996 19:49:06 -0500 (EST) Date: Mon, 11 Nov 1996 19:49:06 -0500 (EST) From: Mark Mayo To: Terry Lambert cc: Ollivier Robert , freebsd-current@FreeBSD.org Subject: Re: ufs is too slow? In-Reply-To: <199611112325.QAA18888@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 11 Nov 1996, Terry Lambert wrote: > > > internals knowledge to even contemplate doing something like this... > > > otherwise I would be off writing "newsfs" in a corner somewhere. > > > > Just to keep people tuned, James Brister (from ISC, author of INN 1.5 & > > Innfeed) is considering/working on such a file system. There is some > > discussion at this moment in the inn-workers list... > > Article directory lookup too slow? ...Use a btree directory structure. Just curious, how would a NTFS perform in this scenario? As far as I remember, NTFS allows btree directory structures. Also NTFS allows per file compression, and "live" partition extension (making a logical drive spread across multiple disks, or extending the size of a logical partition on the current disk). It seems to me that NTFS has quite a bit of functionality, but how does it perform compared to UFS - under the 'general' and extreme cases (such as news). I personally would love to see support for NTFS in FreeBSD, and although I'm not saying I have the technical ability to implement it, I think I might start working on this as a little project in my spare time. File systems are cool, but I have no experience implementing one. Where should I start? I'm assuming there must be a few good references out there (I have a Tanenbaum book on OS's, which covers UFS and Filesystems a little), and I get the MSDN Enterprise Subscription stuff, so I'm assuming NTFS must be documented in there somewhere... Thanks, -Mark --------------------------------------------------- | Mark Mayo mark@quickweb.com | | RingZero Comp. vinyl.quickweb.com/mark | --------------------------------------------------- "To iterate is human, to recurse divine." - L. Peter Deutsch > Etc. > > They are probably also not considering record orientation, a must for MIME > attachments or encapsulation of article header items not in 822 (which, > from memory, only had a "newsgroups" and an "in-reply-to" line...). > > There is very little difference from a good "MIMEFS" and a good "NEWSFS". > > > 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-current Mon Nov 11 17:15:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA03637 for current-outgoing; Mon, 11 Nov 1996 17:15:48 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA03632 for ; Mon, 11 Nov 1996 17:15:45 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id SAA19076; Mon, 11 Nov 1996 18:05:01 -0700 From: Terry Lambert Message-Id: <199611120105.SAA19076@phaeton.artisoft.com> Subject: Re: ufs is too slow? To: mark@quickweb.com (Mark Mayo) Date: Mon, 11 Nov 1996 18:05:00 -0700 (MST) Cc: terry@lambert.org, roberto@keltia.freenix.fr, freebsd-current@FreeBSD.org In-Reply-To: from "Mark Mayo" at Nov 11, 96 07:49:06 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > > Just to keep people tuned, James Brister (from ISC, author of INN 1.5 & > > > Innfeed) is considering/working on such a file system. There is some > > > discussion at this moment in the inn-workers list... > > > > Article directory lookup too slow? ...Use a btree directory structure. > > Just curious, how would a NTFS perform in this scenario? As far as I > remember, NTFS allows btree directory structures. Also NTFS allows per > file compression, and "live" partition extension (making a logical drive > spread across multiple disks, or extending the size of a logical partition > on the current disk). It seems to me that NTFS has quite a bit of > functionality, but how does it perform compared to UFS - under the > 'general' and extreme cases (such as news). Volume spanning is "trivial" (ie: BSD already has it). NTFS itself is slow; not because it has to be, but because of implementation. In point of fact, Microsoft itself has been quoted as recommending that people who need more speed go to VFAT instead of NTFS. The directory lookup speed is probably the sole win; on the other hand, as I argue every time the LMBench stuff comes up, directory operations are the least frequent use of an FS. The mode frequent is file data content reads, which account for ~76% of FS usage, writes, which account for 18% more, leaving 6% for all other operations, including delete, create, and lookup. These figures are from a Novell study. > I personally would love to see support for NTFS in FreeBSD, and although > I'm not saying I have the technical ability to implement it, I think I > might start working on this as a little project in my spare time. File > systems are cool, but I have no experience implementing one. Where should > I start? I'm assuming there must be a few good references out there (I > have a Tanenbaum book on OS's, which covers UFS and Filesystems a little), > and I get the MSDN Enterprise Subscription stuff, so I'm assuming NTFS > must be documented in there somewhere... Start with the BSD sources, the read-only NTFS for Linux, and the book: Inside the Windows NT File System Helen Custer Microsoft Press ISBN 1-55615-660-X US$9.95 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-current Mon Nov 11 17:24:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA03983 for current-outgoing; Mon, 11 Nov 1996 17:24:50 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA03971; Mon, 11 Nov 1996 17:24:43 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.2/8.8.2) with SMTP id RAA12078; Mon, 11 Nov 1996 17:12:19 -0800 (PST) Message-ID: <3287CEDB.1CFBAE39@whistle.com> Date: Mon, 11 Nov 1996 17:11:55 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Tor Egge CC: 100120.3121@compuserve.com, freebsd-stable@freebsd.org, freebsd-current@freebsd.org Subject: Re: Follow on Atlantis board References: <961109200834_100120.3121_EHQ22-1@CompuServe.COM> <199611092319.AAA04767@pat.idt.unit.no> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Tor Egge wrote: > @@ -221,7 +221,6 @@ > push %es > push %esi > push %edi > - push %ecx [...etc...] what about using pushad/popad? From owner-freebsd-current Mon Nov 11 17:31:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA04261 for current-outgoing; Mon, 11 Nov 1996 17:31:25 -0800 (PST) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA04255; Mon, 11 Nov 1996 17:31:23 -0800 (PST) Message-Id: <199611120131.RAA04255@freefall.freebsd.org> To: Mark Mayo cc: Terry Lambert , Ollivier Robert , freebsd-current@FreeBSD.org Subject: Re: ufs is too slow? In-reply-to: Your message of "Mon, 11 Nov 1996 19:49:06 EST." Date: Mon, 11 Nov 1996 17:31:22 -0800 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Just FYI, NTFS will not be the "server" filesystem for NT 5.0. It will be replaced with the Veritas File System and the Veritas volume manager. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Mon Nov 11 17:36:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA04701 for current-outgoing; Mon, 11 Nov 1996 17:36:06 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA04611 for ; Mon, 11 Nov 1996 17:35:24 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id SAA19129; Mon, 11 Nov 1996 18:20:50 -0700 From: Terry Lambert Message-Id: <199611120120.SAA19129@phaeton.artisoft.com> Subject: Re: ufs is too slow? To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Mon, 11 Nov 1996 18:20:50 -0700 (MST) Cc: danj@3skel.com, bsdcur@shadows.aeon.net, jgreco@brasil.moneng.mei.com, freebsd-current@FreeBSD.org In-Reply-To: <199611120007.KAA12318@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Nov 12, 96 10:37:34 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > I have seen that OpenBSD is doing something with lfs, but I > > am not sure what. It would be worth while to get lfs running > > for sure; if you ever wondered, a lot of that disk bandwith > > goes to filesystem overhead. > > Theo's words on lfs were essentially "I've never heard of it working > outside Margo's lab", in a context which I read as "lfs is bogus". I believe it works; Margo knows what the hell she's doing, unlike many people who try to pass themselves off as FS experts. There's really comparatively very little real FS research going on in the world, and I'd stack Margo up there with John Heidemann and the other Names in a heartbeat. I would also not be so quick to dismiss log structured FS's entirely; they beat journalled FS's in terms of support for implied state across multiple files. Journalled FS's can only roll those kinds of transactions back (not forward) following a failure. Further, they can't support even that without the ability to enable transaction tracking journal events, exposing them all the way to user space so the program can explicitly tell the FS about implied state. That kind of blows the reason for the implication in the first place. Journalling and log structured FS's have their places in databasing; but NetNews isn't the place. NetNews is predominantly create/read, with no intervening write accesses, followed by delite (expire). Not very impressive in terms of requirements. Given functioning soft updates, there is little reason for journalling at all... it only introduces unnecessary complexity. Depending on the boundry definitions, however, log structuring is still very useful for fast crash recovery, atomicity of multifile implied state, and record oriented manipulation of files (depending on the records, however, an LFS may be subject to high fragmentation -- for instance, variable length records, ala VMS, would be difficult to implement without needing a real defragger). The VIVA work on idempotence is especially relevant. Again, news articles are created, written only once, and not updated; there's really no reason to get more complex on a "newsfs" than doing what you can to speed up indexing, etc.. And that can be just as easily laid on *top* of *any* FS -- after all, the indices won't change significantly either, if they have correct organizing principles, since the data they refer to is invariant until expiration or creation. 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-current Mon Nov 11 19:59:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA12676 for current-outgoing; Mon, 11 Nov 1996 19:59:17 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA12671 for ; Mon, 11 Nov 1996 19:59:13 -0800 (PST) Received: from dyson.iquest.net ([198.70.144.127]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id TAA29324 for ; Mon, 11 Nov 1996 19:59:11 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id WAA03769; Mon, 11 Nov 1996 22:53:50 -0500 (EST) From: "John S. Dyson" Message-Id: <199611120353.WAA03769@dyson.iquest.net> Subject: Re: ufs is too slow? To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Mon, 11 Nov 1996 22:53:50 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: from "Ollivier Robert" at Nov 11, 96 07:26:15 pm Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Not exactly. It is broken in FreeBSD since the VM/Buffer cache merge and it > lacks some features like fsck. John Dyson said he was working on it and > hoped to have it fixed for 2.2. Now maybe 3.0. > The LFS that we have had in our tree never really worked correctly, and wasn't very robust. However, it doesn't excuse me missing my target for getting it fixed. I did ask Margo for help with her latest sources, but got no response, other than an initial ack. Given that, I intend to fully integrate it with our merged VM/Buffer cache, hopefully making progress like getting rid of locked buffers, etc... John From owner-freebsd-current Mon Nov 11 20:07:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA13138 for current-outgoing; Mon, 11 Nov 1996 20:07:10 -0800 (PST) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA13128; Mon, 11 Nov 1996 20:07:07 -0800 (PST) Message-Id: <199611120407.UAA13128@freefall.freebsd.org> To: dyson@FreeBSD.org cc: roberto@keltia.freenix.fr (Ollivier Robert), freebsd-current@FreeBSD.org Subject: Re: ufs is too slow? In-reply-to: Your message of "Mon, 11 Nov 1996 22:53:50 EST." <199611120353.WAA03769@dyson.iquest.net> Date: Mon, 11 Nov 1996 20:07:07 -0800 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >The LFS that we have had in our tree never really worked correctly, >and wasn't very robust. However, it doesn't excuse me missing my target >for getting it fixed. I did ask Margo for help with her latest sources, >but got no response, other than an initial ack. Given that, I intend to >fully integrate it with our merged VM/Buffer cache, hopefully making progress >like getting rid of locked buffers, etc... > >John Yes, please get rid of the locked buffer stuff. That code is EVIL. BTW,do you have any plans for removing the 64k I/O limitation? It sorta sucks when you want to write a 1meg segment to have to cut it up into such small pieces. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Mon Nov 11 20:22:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA13678 for current-outgoing; Mon, 11 Nov 1996 20:22:46 -0800 (PST) Received: from dyson.iquest.net ([198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA13672; Mon, 11 Nov 1996 20:22:38 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id XAA03836; Mon, 11 Nov 1996 23:22:29 -0500 (EST) From: "John S. Dyson" Message-Id: <199611120422.XAA03836@dyson.iquest.net> Subject: Re: ufs is too slow? To: gibbs@freefall.freebsd.org (Justin T. Gibbs) Date: Mon, 11 Nov 1996 23:22:28 -0500 (EST) Cc: dyson@FreeBSD.org, roberto@keltia.freenix.fr, freebsd-current@FreeBSD.org In-Reply-To: <199611120407.UAA13128@freefall.freebsd.org> from "Justin T. Gibbs" at Nov 11, 96 08:07:07 pm Reply-To: dyson@FreeBSD.org X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > Yes, please get rid of the locked buffer stuff. That code is EVIL. > > BTW,do you have any plans for removing the 64k I/O limitation? It sorta > sucks when you want to write a 1meg segment to have to cut it up into such > small pieces. > You have always hated that!!! I plan to do something to create alternate mappings: segments. Segments will probably use a yet to be enhanced VM/Buffer cache pbuf mechanism (not to be confused with VJ's networking pbufs.) There will be no 64K limitation as such. I am still listening to "bright ideas" though :-). John From owner-freebsd-current Mon Nov 11 21:16:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA22300 for current-outgoing; Mon, 11 Nov 1996 21:16:10 -0800 (PST) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA22292; Mon, 11 Nov 1996 21:16:06 -0800 (PST) Received: from localhost (scrappy@localhost) by quagmire.ki.net (8.8.2/8.7.5) with SMTP id AAA07321; Tue, 12 Nov 1996 00:16:04 -0500 (EST) Date: Tue, 12 Nov 1996 00:16:02 -0500 (EST) From: "Marc G. Fournier" To: smp@freebsd.org cc: current@freebsd.org Subject: GigaByte GA-586DX-512 Motherboard Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... I asked my supplier for a quote on the GigaByte GA-586DX-512 Motherboard, and got the following response: ---- I am still searching for the GigaByte GA-586DX-512 Motherboard. Apparantly they have had a great deal of problems with this board and are not carrying it anymore. I still might find one but would you consider getting something more reliable. eg. Asus. Let me know what you need ie: PCI/ISA/EISA and tomarrow I can find prices for you. ---- Can anyone comment on this? I've always had good dealing with the ASUS brand of motherboards, but is there an equivalent ASUS motherboard that ppl would recommend? I'm wondering if their "great deal of problems" might have been with earlier models, and they just said to hell with carrying it altogether? Thanks... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Mon Nov 11 22:46:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA26610 for current-outgoing; Mon, 11 Nov 1996 22:46:11 -0800 (PST) Received: from lsd.relcom.eu.net (ache@lsd.relcom.eu.net [193.124.23.23]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA26585; Mon, 11 Nov 1996 22:46:04 -0800 (PST) Received: (from ache@localhost) by lsd.relcom.eu.net (8.8.2/8.8.2) id JAA02474; Tue, 12 Nov 1996 09:45:58 +0300 (MSK) Message-Id: <199611120645.JAA02474@lsd.relcom.eu.net> Subject: SCB paging is most dangerous option now! To: current@freebsd.org, scsi@freebsd.org Date: Tue, 12 Nov 1996 09:45:57 +0300 (MSK) From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (Andrey A. Chernov) Organization: self X-Class: Fast X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well, situation becomes even worse after latest SCB paging changes: for all previous damages I was able to restore my disk, but now all inodes are completely clean! -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Mon Nov 11 23:00:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA27390 for current-outgoing; Mon, 11 Nov 1996 23:00:54 -0800 (PST) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA27383 for ; Mon, 11 Nov 1996 23:00:51 -0800 (PST) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.2/CET-v2.1) with SMTP id GAA04113; Tue, 12 Nov 1996 06:58:01 GMT Date: Tue, 12 Nov 1996 15:58:01 +0900 (JST) From: Michael Hancock To: Joe Greco cc: mika ruohotie , freebsd-current@FreeBSD.ORG Subject: Re: ufs is too slow? In-Reply-To: <199611111503.JAA19277@brasil.moneng.mei.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 11 Nov 1996, Joe Greco wrote: > FFS is in general a great FS... but it is optimized for the general case. > > It is particularly poor at handling large directories or lots of writes, > and news is excellent at pounding on these qualities. NTFS uses btrees for large directories and a simple linear method for small directories. I've seen some tuning tips for SQLServer where they recommended NTFS for the db and FAT for the logs because NTFS had faster read performance but FAT had faster write performance. I agree that btree scheme would improve the large directory read performance, while a soft update scheme would improve write performance in ufs. Regards, Mike Hancock From owner-freebsd-current Mon Nov 11 23:04:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA27660 for current-outgoing; Mon, 11 Nov 1996 23:04:00 -0800 (PST) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA27655; Mon, 11 Nov 1996 23:03:56 -0800 (PST) Message-Id: <199611120703.XAA27655@freefall.freebsd.org> To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (Andrey A. Chernov) cc: current@freebsd.org, scsi@freebsd.org Subject: Re: SCB paging is most dangerous option now! In-reply-to: Your message of "Tue, 12 Nov 1996 09:45:57 +0300." <199611120645.JAA02474@lsd.relcom.eu.net> Date: Mon, 11 Nov 1996 23:03:56 -0800 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk What were the error messages? >Well, situation becomes even worse after latest SCB paging changes: >for all previous damages I was able to restore my disk, but >now all inodes are completely clean! >-- >Andrey A. Chernov > >http://www.nagual.ru/~ache/ -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Mon Nov 11 23:21:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA28532 for current-outgoing; Mon, 11 Nov 1996 23:21:13 -0800 (PST) Received: from clem.systemsix.com (clem.systemsix.com [198.99.86.131]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA28527; Mon, 11 Nov 1996 23:21:10 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by clem.systemsix.com (8.6.12/8.6.12) with SMTP id AAA26401; Tue, 12 Nov 1996 00:20:55 -0700 Message-Id: <199611120720.AAA26401@clem.systemsix.com> X-Authentication-Warning: clem.systemsix.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6.5 12/11/95 From: Steve Passe To: "Marc G. Fournier" cc: smp@freebsd.org, current@freebsd.org Subject: Re: GigaByte GA-586DX-512 Motherboard In-reply-to: Your message of "Tue, 12 Nov 1996 00:16:02 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 12 Nov 1996 00:20:55 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, > I asked my supplier for a quote on the GigaByte GA-586DX-512 > Motherboard, and got the following response: > > ---- > I am still searching for the GigaByte GA-586DX-512 Motherboard. > Apparantly they have had a great deal of problems with this board and are not > carrying it anymore. I still might find one but would you consider getting > something more reliable. eg. Asus. Let me know what you need ie: PCI/ISA/EISA > and tomarrow I can find prices for you. > ---- > > Can anyone comment on this? I've always had good dealing with > the ASUS brand of motherboards, but is there an equivalent ASUS motherboard > that ppl would recommend? > > I'm wondering if their "great deal of problems" might have been > with earlier models, and they just said to hell with carrying it altogether? or they just want to sell you what they have experience with (or can make more money on). This is the board that I pound on many hours a day, and have never had a lick of trouble with it. It supports the MP spec properly (and there's a LOT of room in that spec to do stupid things). Never seen a sigfault that "smells" of the flaky memory sub-system variety. I do see occasional faults, but we know the current SMP kernel is not "doing the good thing" in all respects yet. From my limited experience of one board I would not hesitate to recommend it. Try www.atipa.com, they could probably have one to you by end of the week. -- Steve Passe | powered by smp@csn.net | FreeBSD From owner-freebsd-current Mon Nov 11 23:22:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA28607 for current-outgoing; Mon, 11 Nov 1996 23:22:57 -0800 (PST) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA28602 for ; Mon, 11 Nov 1996 23:22:54 -0800 (PST) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id XAA09056; Mon, 11 Nov 1996 23:23:01 -0800 (PST) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id XAA01655; Mon, 11 Nov 1996 23:22:46 -0800 (PST) Message-Id: <199611120722.XAA01655@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: "Justin T. Gibbs" cc: Mark Mayo , Terry Lambert , Ollivier Robert , freebsd-current@freebsd.org Subject: Re: ufs is too slow? In-reply-to: Your message of Mon, 11 Nov 96 17:31:22 -0800. <199611120131.RAA04255@freefall.freebsd.org> Date: Mon, 11 Nov 1996 23:22:44 -0800 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Just FYI, NTFS will not be the "server" filesystem for NT 5.0. It will be >replaced with the Veritas File System and the Veritas volume manager. Where did you hear this? It's certainly the first I've heard of it... They are working on an object-based filesystem for NT 5.0. But I haven't heard of anyone replacing the underlying technology. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-current Mon Nov 11 23:43:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA29654 for current-outgoing; Mon, 11 Nov 1996 23:43:50 -0800 (PST) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA29643; Mon, 11 Nov 1996 23:43:47 -0800 (PST) Message-Id: <199611120743.XAA29643@freefall.freebsd.org> To: "Michael L. VanLoon -- HeadCandy.com" cc: Mark Mayo , Terry Lambert , Ollivier Robert , freebsd-current@freebsd.org Subject: Re: ufs is too slow? In-reply-to: Your message of "Mon, 11 Nov 1996 23:22:44 PST." <199611120722.XAA01655@MindBender.serv.net> Date: Mon, 11 Nov 1996 23:43:47 -0800 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >>Just FYI, NTFS will not be the "server" filesystem for NT 5.0. It will be >>replaced with the Veritas File System and the Veritas volume manager. > >Where did you hear this? It's certainly the first I've heard of it... http://www.veritas.com/News/microsoft_partnership.html >----------------------------------------------------------------------------- > Michael L. VanLoon michaelv@MindBender.serv.net > --< Free your mind and your machine -- NetBSD free un*x >-- > NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, > Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... > NetBSD ports in progress: PICA, others... >----------------------------------------------------------------------------- -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Tue Nov 12 00:09:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA00973 for current-outgoing; Tue, 12 Nov 1996 00:09:03 -0800 (PST) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA00968; Tue, 12 Nov 1996 00:09:00 -0800 (PST) Received: from localhost (scrappy@localhost) by quagmire.ki.net (8.8.2/8.7.5) with SMTP id DAA10379; Tue, 12 Nov 1996 03:08:56 -0500 (EST) Date: Tue, 12 Nov 1996 03:08:55 -0500 (EST) From: "Marc G. Fournier" To: Steve Passe cc: smp@freebsd.org, current@freebsd.org Subject: Re: GigaByte GA-586DX-512 Motherboard In-Reply-To: <199611120720.AAA26401@clem.systemsix.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 12 Nov 1996, Steve Passe wrote: > Hi, > > > I asked my supplier for a quote on the GigaByte GA-586DX-512 > > Motherboard, and got the following response: > > > > ---- > > I am still searching for the GigaByte GA-586DX-512 Motherboard. > > Apparantly they have had a great deal of problems with this board and are not > > carrying it anymore. I still might find one but would you consider getting > > something more reliable. eg. Asus. Let me know what you need ie: PCI/ISA/EISA > > and tomarrow I can find prices for you. > > ---- > > > > Can anyone comment on this? I've always had good dealing with > > the ASUS brand of motherboards, but is there an equivalent ASUS motherboard > > that ppl would recommend? > > > > I'm wondering if their "great deal of problems" might have been > > with earlier models, and they just said to hell with carrying it altogether? > > or they just want to sell you what they have experience with (or can make > more money on). > > This is the board that I pound on many hours a day, and have never had a lick > of trouble with it. It supports the MP spec properly (and there's a LOT >of room in that spec to do stupid things). Never seen a sigfault that "smells" > of the flaky memory sub-system variety. I do see occasional faults, but we > know the current SMP kernel is not "doing the good thing" in all respects >yet. From my limited experience of one board I would not hesitate to recommend >it. Try www.atipa.com, they could probably have one to you by end of the week. > Okay...sound arguments :) How does this sound: GigaByte GA-586DX-512 Intel Pentium 133 (is 133 that much better then 120 to warrant extra cost?) 64Meg of RAM (EDO?) How about Hard Drive? atipa doesn't list Seagates, that I can find, and recent experiencees with Quantum are steering me clear of them. Essentially, I'm looking at setting up a server that I can play with SMP on, but if I get a crash/core, I can confidently send in a bug report on without being worried its a hardware problem :) Thanks... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Tue Nov 12 00:19:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA01282 for current-outgoing; Tue, 12 Nov 1996 00:19:14 -0800 (PST) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA01276 for ; Tue, 12 Nov 1996 00:19:09 -0800 (PST) Received: from critter.tfs.com (localhost.phk.dk [127.0.0.1]) by critter.tfs.com (8.8.2/8.8.2) with ESMTP id CAA13979; Tue, 12 Nov 1996 02:44:31 +0100 (MET) To: Terry Lambert cc: msmith@atrad.adelaide.edu.au (Michael Smith), danj@3skel.com, bsdcur@shadows.aeon.net, jgreco@brasil.moneng.mei.com, freebsd-current@FreeBSD.org Subject: Re: ufs is too slow? In-reply-to: Your message of "Mon, 11 Nov 1996 18:20:50 MST." <199611120120.SAA19129@phaeton.artisoft.com> Date: Tue, 12 Nov 1996 02:44:31 +0100 Message-ID: <13977.847763071@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In message <199611120120.SAA19129@phaeton.artisoft.com>, Terry Lambert writes: >> > I have seen that OpenBSD is doing something with lfs, but I >> > am not sure what. It would be worth while to get lfs running >> > for sure; if you ever wondered, a lot of that disk bandwith >> > goes to filesystem overhead. >> >> Theo's words on lfs were essentially "I've never heard of it working >> outside Margo's lab", in a context which I read as "lfs is bogus". > >I believe it works; Margo knows what the hell she's doing, unlike many >people who try to pass themselves off as FS experts. There's really >comparatively very little real FS research going on in the world, and >I'd stack Margo up there with John Heidemann and the other Names in a >heartbeat. She just doesn't seem to want to answer Kirks comments... -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Tue Nov 12 00:22:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA01652 for current-outgoing; Tue, 12 Nov 1996 00:22:04 -0800 (PST) Received: from clem.systemsix.com (clem.systemsix.com [198.99.86.131]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA01641; Tue, 12 Nov 1996 00:21:59 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by clem.systemsix.com (8.6.12/8.6.12) with SMTP id BAA26733; Tue, 12 Nov 1996 01:21:46 -0700 Message-Id: <199611120821.BAA26733@clem.systemsix.com> X-Authentication-Warning: clem.systemsix.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6.5 12/11/95 From: Steve Passe To: "Marc G. Fournier" cc: smp@freebsd.org, current@freebsd.org Subject: Re: GigaByte GA-586DX-512 Motherboard In-reply-to: Your message of "Tue, 12 Nov 1996 03:08:55 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 12 Nov 1996 01:21:46 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, > How does this sound: > > GigaByte GA-586DX-512 > Intel Pentium 133 (is 133 that much better then 120 to warrant extra > cost?) yes, not only faster, but 133s use a 66mHz bus, while 120s use a 60mHz bus. > 64Meg of RAM (EDO?) I recommend 64meg of parity. Don't really have direct knowledge of EDO vs not. > How about Hard Drive? atipa doesn't list Seagates, that I can find, >and recent experiencees with Quantum are steering me clear of them. atipa carries a rather limited selection in general, just how they do business. I would suggest getting the drive from someplace that carries what you want. -- Steve Passe | powered by smp@csn.net | FreeBSD -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQCNAzHe7tEAAAEEAM274wAEEdP+grIrV6UtBt54FB5ufifFRA5ujzflrvlF8aoE 04it5BsUPFi3jJLfvOQeydbegexspPXL6kUejYt2OeptHuroIVW5+y2M2naTwqtX WVGeBP6s2q/fPPAS+g+sNZCpVBTbuinKa/C4Q6HJ++M9AyzIq5EuvO0a8Rr9AAUR tBlTdGV2ZSBQYXNzZSA8c21wQGNzbi5uZXQ+ =ds99 -----END PGP PUBLIC KEY BLOCK----- From owner-freebsd-current Tue Nov 12 00:33:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA02233 for current-outgoing; Tue, 12 Nov 1996 00:33:27 -0800 (PST) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA02228 for ; Tue, 12 Nov 1996 00:33:22 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id JAA06542 for ; Tue, 12 Nov 1996 09:34:34 +0100 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id JAA25385 for freebsd-current@freefall.cdrom.com; Tue, 12 Nov 1996 09:44:11 +0100 Date: Tue, 12 Nov 1996 09:44:11 +0100 From: Christoph Kukulies Message-Id: <199611120844.JAA25385@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.FreeBSD.org Subject: world build Makefile (mk) Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk What am I missing resp. what has changed that I cannot build world any longer in a hierarchy that looks like this: cd /u/BLUES/src blues# make mk cd /u/BLUES/src/share/mk && make install cd /u/BLUES/src/share/mk && install -c -o bin -g bin -m 444 bsd.README bsd.dep.mk bsd.doc.mk bsd.info.mk bsd.kern.mk bsd.kmod.mk bsd.lib.mk bsd.libnames.mk bsd.man.mk bsd.obj.mk bsd.own.mk bsd.port.mk bsd.port.subdir.mk bsd.prog.mk bsd.sgml.mk bsd.subdir.mk sys.mk /mk usage: install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-g group] [-m mode] [-o owner] directory ... *** Error code 64 Stop. *** Error code 1 Stop. While doing that in /usr/src works fine. (This all used to work one or two weeks ago without setting any special environmental variable). blues# cd /usr/src blues# make mk cd /usr/src/share/mk && make install cd /home/src/share/mk && install -c -o bin -g bin -m 444 bsd.README bsd.dep.mk bsd.doc.mk bsd.info.mk bsd.kern.mk bsd.kmod.mk bsd.lib.mk bsd.libnames.mk bsd.man.mk bsd.obj.mk bsd.own.mk bsd.port.mk bsd.port.subdir.mk bsd.prog.mk bsd.sgml.mk bsd.subdir.mk sys.mk /usr/share/mk blues# --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Tue Nov 12 00:44:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA02884 for current-outgoing; Tue, 12 Nov 1996 00:44:53 -0800 (PST) Received: from whale.gu.kiev.ua ([194.93.190.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA02878 for ; Tue, 12 Nov 1996 00:44:43 -0800 (PST) Received: from creator.gu.kiev.ua (stesin@creator.gu.kiev.ua [194.93.190.3]) by whale.gu.kiev.ua (8.7.5/8.7.3) with SMTP id KAA93618; Tue, 12 Nov 1996 10:42:56 +0200 Date: Tue, 12 Nov 1996 10:42:54 +0200 (EET) From: Andrew Stesin X-Sender: stesin@creator.gu.kiev.ua To: Michael Smith cc: jgreco@brasil.moneng.mei.com, freebsd-current@freebsd.org Subject: Re: ufs is too slow? In-Reply-To: <199611120007.KAA12318@genesis.atrad.adelaide.edu.au> Message-ID: X-NCC-RegID: ua.gu MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello people, just some (presumably bogus ;) comments of mine... > > Maybe we can all talk about it a little and figure out > > how hard it would be to get going. If we were running > > a kick-ass big/fast file system, FreeBSD would capture > > some more of the Int(er|tra)+Net market. In addition > > to which, the infamous 'make world' time would surely > > benefit. > > I doubt that a working lfs would actually offer much, if any, in the > way of performance in anything other than the applications that it > handles well. As a consequence of the data acquisition stuff that we > do, we often end up with directories with literally thousands of > fairly large files in them; a BSD ffs filesystem mounted async,noatime > is _significantly_ faster at moving/copying/deleting this sort of > stuff than any of the other (Solaris, OSF, NTFS, HPFS, FAT) > filesystems that we've ever put data on. If only some filesystem and kernel Guru considered writing FFS-B -- FFS with B-tree used for directory structures, no other modifications; _that_ would probably be the best bet for FS with a BIG (3000+ files per dir) directories? Or another (plain bogus ;) approach for NewsFS: take a raw partition, and create a BerkeleyDB, "One Big B-tree" over it... put everything there, including article bodies, and all indices nessesary, set a size of memory-pool buffer inside innd as appropriate -- and what will happen? Just a plain big multi-table database, should be pretty simple and fast. > One of the most notable performance improvements can actually be had > by using SCSI disks and controllers that support tagged queueing; > don't ever make the mistake of benchmarking an IDE based disk > subsystem against anything else. Anyway, good algorithms will give you some win even on cheap and crappy HW. As for me, I won't be able to afford anything but cheap IDE for my home PC for a long time yet. :) This doesn't mean of course that I will never want to run some small, 1Gb or even smaller, news spool on it. ;) -- Best, Andrew Stesin nic-hdl: ST73-RIPE From owner-freebsd-current Tue Nov 12 00:46:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA02972 for current-outgoing; Tue, 12 Nov 1996 00:46:09 -0800 (PST) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA02965; Tue, 12 Nov 1996 00:46:06 -0800 (PST) Received: from localhost (scrappy@localhost) by quagmire.ki.net (8.8.2/8.7.5) with SMTP id DAA10792; Tue, 12 Nov 1996 03:46:11 -0500 (EST) Date: Tue, 12 Nov 1996 03:46:11 -0500 (EST) From: "Marc G. Fournier" To: Steve Passe cc: smp@freebsd.org, current@freebsd.org Subject: Re: GigaByte GA-586DX-512 Motherboard In-Reply-To: <199611120821.BAA26733@clem.systemsix.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 12 Nov 1996, Steve Passe wrote: > > 64Meg of RAM (EDO?) > >I recommend 64meg of parity. Don't really have direct knowledge of EDO vs not. > Hrmmm...I had thought that EDO RAM was better because it had 'on chip' cache or something like that ... > > How about Hard Drive? atipa doesn't list Seagates, that I can find, > >and recent experiencees with Quantum are steering me clear of them. > >atipa carries a rather limited selection in general, just how they do business. > I would suggest getting the drive from someplace that carries what you want. > Does anyone have any recommendations on drives? Or, any drives in particular I should stick away from? I heard that SeaGate went downhill for awhile there...anyone have a current opinion of them? Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Tue Nov 12 01:06:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA04290 for current-outgoing; Tue, 12 Nov 1996 01:06:35 -0800 (PST) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA04281 for ; Tue, 12 Nov 1996 01:06:29 -0800 (PST) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id JAA13517 for ; Tue, 12 Nov 1996 09:07:56 GMT Date: Tue, 12 Nov 1996 09:07:56 +0000 (GMT) From: Developer To: freebsd-current@freebsd.org Subject: Help with NIS Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Ive installed NIS on a group of 3 machines, but I'm having a problem that when a nis password is changed the machine still things the old password is being used until I kill -HUP ypserv. The strange thing is nis knows it's changed because if I try to change it again I need to supply the new password, but the system thinks it's still at the old one (When I telnet I have to use the old password till the kill -HUP is done). Any ideas? Please could people reply by email direct to me. Thanks very much in advance. Regards, Trefor S. From owner-freebsd-current Tue Nov 12 01:21:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA05531 for current-outgoing; Tue, 12 Nov 1996 01:21:06 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA05526 for ; Tue, 12 Nov 1996 01:21:01 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.2/8.6.9) with ESMTP id BAA07360; Tue, 12 Nov 1996 01:20:35 -0800 (PST) To: Dan Janowski cc: freebsd-current@FreeBSD.ORG, roberto@keltia.freenix.fr Subject: Re: ufs is too slow? In-reply-to: Your message of "Mon, 11 Nov 1996 19:34:13 EST." <199611120034.TAA15191@fnur.3skel.com> Date: Tue, 12 Nov 1996 01:20:35 -0800 Message-ID: <7358.847790435@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Xfs is pretty fragile from what I've heard. > > SGI's XFS is actually pretty robust. We run 16 and 32GB file > systems with it, and the performance is good. It can handle > an FS of some-number Terabytes. It is really a journal filesystem, Actually, Matt Dillon over at BEST Internet talked about their experiences with XFS in a recent presentation, and his opinion of XFS was far from flattering. In their experience, using XFS was a good way of crashing IRIX far too frequently for comfort. Jordan From owner-freebsd-current Tue Nov 12 03:12:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA10319 for current-outgoing; Tue, 12 Nov 1996 03:12:50 -0800 (PST) Received: from smily.3skel.com (3skel.com [206.138.212.40]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA10293; Tue, 12 Nov 1996 03:12:37 -0800 (PST) Received: from fnur.3skel.com (root@fnur.3skel.com [192.168.0.8]) by smily.3skel.com (8.8.2/8.8.2) with ESMTP id GAA07879; Tue, 12 Nov 1996 06:12:16 -0500 (EST) Received: (from danj@localhost) by fnur.3skel.com (8.8.2/8.8.2) id GAA24880; Tue, 12 Nov 1996 06:12:15 -0500 (EST) Date: Tue, 12 Nov 1996 06:12:15 -0500 (EST) Message-Id: <199611121112.GAA24880@fnur.3skel.com> From: Dan Janowski To: "Marc G. Fournier" Cc: Steve Passe , smp@freebsd.org, current@freebsd.org Subject: Re: GigaByte GA-586DX-512 Motherboard In-Reply-To: References: <199611120821.BAA26733@clem.systemsix.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Marc G. Fournier writes: > > Does anyone have any recommendations on drives? Or, any drives > in particular I should stick away from? I heard that SeaGate went downhill > for awhile there...anyone have a current opinion of them? The Conner stuff that Seagate bought is less than desirable. I have two IDEs that I am swapping out. If you are doing SCSI, the Baracudas are really good. I have an ST32550N, two of them. I would recommend the Baracuda or the IBM starfire, both high spindle speed, fast drives. Quantum, hold on to your .... No Atlas 1s, Atlas 2s I have not tried. Dan From owner-freebsd-current Tue Nov 12 03:25:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA11989 for current-outgoing; Tue, 12 Nov 1996 03:25:19 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA11889; Tue, 12 Nov 1996 03:24:37 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id WAA23318; Tue, 12 Nov 1996 22:14:14 +1100 Date: Tue, 12 Nov 1996 22:14:14 +1100 From: Bruce Evans Message-Id: <199611121114.WAA23318@godzilla.zeta.org.au> To: julian@whistle.com, Tor.Egge@idt.ntnu.no Subject: Re: Follow on Atlantis board Cc: 100120.3121@CompuServe.COM, freebsd-current@freebsd.org, freebsd-stable@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> @@ -221,7 +221,6 @@ >> push %es >> push %esi >> push %edi >> - push %ecx > >[...etc...] > >what about using pushad/popad? It preserves %eax, which you usually want to change to return a value in. The value could be stored on the stack, but would lose 3 of the bytes saved by using pushal/popal. It would also require too many changes to the arg offsets for a quick fix. Bruce From owner-freebsd-current Tue Nov 12 04:29:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA20327 for current-outgoing; Tue, 12 Nov 1996 04:29:31 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA20318 for ; Tue, 12 Nov 1996 04:29:20 -0800 (PST) Received: from btp1da.phy.uni-bayreuth.de (btp1da.phy.uni-bayreuth.de [132.180.20.32]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id EAA00188 for ; Tue, 12 Nov 1996 04:29:18 -0800 (PST) Received: (from root@localhost) by btp1da.phy.uni-bayreuth.de (8.8.2/8.7.3) id NAA02086 for freebsd-current@freebsd.org; Tue, 12 Nov 1996 13:27:07 GMT From: Werner Griessl Message-Id: <199611121327.NAA02086@btp1da.phy.uni-bayreuth.de> Subject: kernel compile To: freebsd-current@freebsd.org Date: Tue, 12 Nov 1996 13:27:06 +0000 () 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Cannot compile current kernel because: ../../i386/i386/identcpu.c:42: opt_temporary.h: No such file or directory *** Error code 1 Werner From owner-freebsd-current Tue Nov 12 04:35:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA20610 for current-outgoing; Tue, 12 Nov 1996 04:35:11 -0800 (PST) Received: from wgrobez1.remote.louisville.edu (wgrobez1.remote.louisville.edu [136.165.243.183]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA20589 for ; Tue, 12 Nov 1996 04:34:57 -0800 (PST) Received: from localhost (wangel@localhost) by wgrobez1.remote.louisville.edu (8.7.6/8.6.12) with SMTP id HAA18826 for ; Tue, 12 Nov 1996 07:35:37 -0500 (EST) Date: Tue, 12 Nov 1996 07:35:37 -0500 (EST) From: Gary Roberts To: freebsd-current@freebsd.org Subject: Sup Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hey all. I've been trying for 2 days now to sup my tree. However, I keep getting Connection Refused when trying to run sup. Is the server down? Am I missing something? I got a new supfile, and I still have my old one, they both don't work. Thanks! Gary Roberts From owner-freebsd-current Tue Nov 12 04:42:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA21006 for current-outgoing; Tue, 12 Nov 1996 04:42:47 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA20987; Tue, 12 Nov 1996 04:42:34 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id NAA10429; Tue, 12 Nov 1996 13:30:32 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.8.2/8.8.2) with SMTP id MAA02670; Tue, 12 Nov 1996 12:28:36 +0100 (MET) Date: Tue, 12 Nov 1996 12:28:35 +0100 (MET) From: Andreas Klemm To: "Marc G. Fournier" cc: Steve Passe , smp@FreeBSD.org, current@FreeBSD.org Subject: Re: GigaByte GA-586DX-512 Motherboard In-Reply-To: Message-ID: X-try-apsfilter: ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz X-Fax: +49 2137 2018 X-Phone: +49 2137 2020 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 12 Nov 1996, Marc G. Fournier wrote: > Does anyone have any recommendations on drives? Or, any drives > in particular I should stick away from? I heard that SeaGate went downhill > for awhile there...anyone have a current opinion of them? Quantum Atlas 2GB, the 4GB modell is too loud for a home environment. Both drives have 1 MB cache ! Another fast, but loud and expensive drive, is the IBM DHFS .... sorry forgot the model number. The Quantum drives are also available as wide scsi disks. Andreas /// -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-current Tue Nov 12 04:43:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA21039 for current-outgoing; Tue, 12 Nov 1996 04:43:03 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA21021; Tue, 12 Nov 1996 04:42:52 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id NAA10417; Tue, 12 Nov 1996 13:30:25 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.8.2/8.8.2) with SMTP id MAA02577; Tue, 12 Nov 1996 12:26:01 +0100 (MET) Date: Tue, 12 Nov 1996 12:26:01 +0100 (MET) From: Andreas Klemm To: "Marc G. Fournier" cc: Steve Passe , smp@FreeBSD.org, current@FreeBSD.org Subject: Re: GigaByte GA-586DX-512 Motherboard In-Reply-To: Message-ID: X-try-apsfilter: ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz X-Fax: +49 2137 2018 X-Phone: +49 2137 2020 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 12 Nov 1996, Marc G. Fournier wrote: > Okay...sound arguments :) > How does this sound: > > GigaByte GA-586DX-512 > Intel Pentium 133 (is 133 that much better then 120 to warrant extra > cost?) > 64Meg of RAM (EDO?) > How about Hard Drive? atipa doesn't list Seagates, that I can find, > and recent experiencees with Quantum are steering me clear of them. > > Essentially, I'm looking at setting up a server that I can play with > SMP on, but if I get a crash/core, I can confidently send in a bug report on > without being worried its a hardware problem :) The performance difference between PS/2 and EDO Ram's isn't so large, that it's worth the higher price. This was the case with single processor boards, and I think it's also true with mp boards. I'd buy PS/2 RAMS with 60ns and Parity (since most mp boards support parity checking - or am I wrong -) and would choose a 133 MHZ CPU, because then memory and bus bandwidth are higher ! 66MHz instead of 60 MHz. Many people say, that it's better to choose a - 200 MHz CPU instead of a 180 MHz CPU - 166 MHz CPU instead of a 150 MHz CPU - 133 MHz CPU instead of a 150 MHz CPU - 100 MHz CPU instead of a 120 MHz CPU because bus and memory speed have a more impact on overall performance on a multiuser/multitasking system, than the 20MHz clock frequency... Andreas /// -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-current Tue Nov 12 04:48:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA21346 for current-outgoing; Tue, 12 Nov 1996 04:48:01 -0800 (PST) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA21336; Tue, 12 Nov 1996 04:47:27 -0800 (PST) Received: from critter.tfs.com (localhost.phk.dk [127.0.0.1]) by critter.tfs.com (8.8.2/8.8.2) with ESMTP id HAA14812; Tue, 12 Nov 1996 07:18:42 +0100 (MET) To: Gary Roberts cc: freebsd-current@FreeBSD.org Subject: Re: Sup In-reply-to: Your message of "Tue, 12 Nov 1996 07:35:37 EST." Date: Tue, 12 Nov 1996 07:18:41 +0100 Message-ID: <14810.847779521@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In message , Gary Roberts writes: >Hey all. > >I've been trying for 2 days now to sup my tree. However, I keep getting >Connection Refused when trying to run sup. Is the server down? Am I >missing something? I got a new supfile, and I still have my old one, they >both don't work. switch to another sup server or to cvsup. sup is no longer supported on freebsd.org, since it loads the line of our host too much. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Tue Nov 12 05:52:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA25309 for current-outgoing; Tue, 12 Nov 1996 05:52:39 -0800 (PST) Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA25297 for ; Tue, 12 Nov 1996 05:52:26 -0800 (PST) Received: (from imb@localhost) by asstdc.scgt.oz.au (8.7.6/BSD4.4) id AAA25254 Wed, 13 Nov 1996 00:51:54 +1100 (EST) From: michael butler Message-Id: <199611121351.AAA25254@asstdc.scgt.oz.au> Subject: Re: Sup In-Reply-To: <14810.847779521@critter.tfs.com> from Poul-Henning Kamp at "Nov 12, 96 07:18:41 am" To: phk@critter.tfs.com (Poul-Henning Kamp) Date: Wed, 13 Nov 1996 00:51:53 +1100 (EST) Cc: current@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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Poul-Henning Kamp writes: > switch to another sup server or to cvsup. sup is no longer supported > on freebsd.org, since it loads the line of our host too much. There are few alternatives .. sup2 points at "bilbo.gdw.com" and for which there is no 'A' record in the DNS and sup3 (aka "burka.rdy.com", the only other US-based server I can find that's still functioning) still has the 2.1/TODO files which were removed yonks ago, michael From owner-freebsd-current Tue Nov 12 05:57:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA25494 for current-outgoing; Tue, 12 Nov 1996 05:57:00 -0800 (PST) Received: from charlotte.spiders.com (charlotte.spiders.com [199.224.7.188]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA25489; Tue, 12 Nov 1996 05:56:56 -0800 (PST) Received: (from gwh@localhost) by charlotte.spiders.com (8.6.12/8.6.12) id IAA12311; Tue, 12 Nov 1996 08:59:49 -0500 Message-Id: <199611121359.IAA12311@charlotte.spiders.com> From: gwh@spiders.com (Gene W Homicki) Date: Tue, 12 Nov 1996 08:59:49 -0500 In-Reply-To: Steve Passe's message as of Nov 12, 0:20 X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Steve Passe , "Marc G. Fournier" Subject: Re: GigaByte GA-586DX-512 Motherboard Cc: smp@freebsd.org, current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk +--- | This is the board that I pound on many hours a day, and have never had a lick | of trouble with it. It supports the MP spec properly (and there's a LOT +--- I'll second this. I'm still using the board as a uniprocessor, but I've had no trouble with it. Running a current SNAP (non-smp) I've had this box up for over 3 weeks (and I pound on it pretty hard). Now to get a second P166. B-) --Gene -- Gene W. Homicki gwh@spiders.com Objective Consulting, Inc. http://www.spiders.com/ Internet Presence Design voice: +1 914.353.3511 From owner-freebsd-current Tue Nov 12 06:05:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA26012 for current-outgoing; Tue, 12 Nov 1996 06:05:49 -0800 (PST) Received: from charlotte.spiders.com (charlotte.spiders.com [199.224.7.188]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA26000; Tue, 12 Nov 1996 06:05:41 -0800 (PST) Received: (from gwh@localhost) by charlotte.spiders.com (8.6.12/8.6.12) id JAA12381; Tue, 12 Nov 1996 09:08:38 -0500 Message-Id: <199611121408.JAA12381@charlotte.spiders.com> From: gwh@spiders.com (Gene W Homicki) Date: Tue, 12 Nov 1996 09:08:38 -0500 In-Reply-To: Andreas Klemm's message as of Nov 12, 12:26 X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Andreas Klemm , "Marc G. Fournier" Subject: Re: GigaByte GA-586DX-512 Motherboard Cc: Steve Passe , smp@FreeBSD.org, current@FreeBSD.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk +--- | The performance difference between PS/2 and EDO Ram's isn't so | large, that it's worth the higher price. This was the case with | single processor boards, and I think it's also true with mp boards. +--- Actually, FPM RAM is slightly MORE expensive than EDO at the moment. Parity RAM is defintely more expensive than both. Seems like comapnies are producing a lot more EDO these days so prices have come down. One good source for RAM is ChipMerchant: http://www.thechipmerchant.com/ (Careful, the CPU prices are "cash only", bu the listed RAM prices are Credit Card prices). +--- | I'd buy PS/2 RAMS with 60ns and Parity (since most mp boards support | parity checking - or am I wrong -) and would choose a 133 MHZ CPU, | because then memory and bus bandwidth are higher ! 66MHz instead of | 60 MHz. +--- All the 430HX (Triton II) boards support parity (and ECC). Most current (Pentium) baords are Triton-II, inclduing the Gigabyte 586DX-512. --Gene -- Gene W. Homicki gwh@spiders.com Objective Consulting, Inc. http://www.spiders.com/ Internet Presence Design voice: +1 914.353.3511 From owner-freebsd-current Tue Nov 12 06:23:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA26787 for current-outgoing; Tue, 12 Nov 1996 06:23:27 -0800 (PST) Received: from wgrobez1.remote.louisville.edu (wgrobez1.remote.louisville.edu [136.165.243.183]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA26782 for ; Tue, 12 Nov 1996 06:23:21 -0800 (PST) Received: from localhost (wangel@localhost) by wgrobez1.remote.louisville.edu (8.7.6/8.6.12) with SMTP id JAA19955 for ; Tue, 12 Nov 1996 09:24:07 -0500 (EST) Date: Tue, 12 Nov 1996 09:24:06 -0500 (EST) From: Gary Roberts To: freebsd-current@freebsd.org Subject: Sup Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ah, then that explains why I can't connect. Only thing is, the only alternate sup servers listed in the README file are oversea sup servers, there aren't any more US based sup servers besides cdrom.com? Thanks! Gary Roberts From owner-freebsd-current Tue Nov 12 07:04:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA29079 for current-outgoing; Tue, 12 Nov 1996 07:04:50 -0800 (PST) Received: from lirmm.lirmm.fr (lirmm.lirmm.fr [193.49.104.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA29065 for ; Tue, 12 Nov 1996 07:04:27 -0800 (PST) Received: from lirmm.fr (baobab.lirmm.fr [193.49.106.14]) by lirmm.lirmm.fr (8.7.6/8.6.4) with ESMTP id QAA28462 for ; Tue, 12 Nov 1996 16:04:00 +0100 (MET) Message-Id: <199611121504.QAA28462@lirmm.lirmm.fr> To: current@FreeBSD.org Subject: reference to format(8) Date: Tue, 12 Nov 1996 16:03:56 +0100 From: "Philippe Charnier" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi, badsect and bad144 manual pages contain a reference to format(8) that does not exist. -------- -------- Philippe Charnier charnier@lirmm.fr LIRMM, 161 rue Ada, 34392 Montpellier cedex 5 -- France ------------------------------------------------------------------------ From owner-freebsd-current Tue Nov 12 07:08:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA29229 for current-outgoing; Tue, 12 Nov 1996 07:08:30 -0800 (PST) Received: from cs.utah.edu (cs.utah.edu [128.110.4.21]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA29205; Tue, 12 Nov 1996 07:08:20 -0800 (PST) Received: from fast.cs.utah.edu by cs.utah.edu (8.6.12/utah-2.21-cs) id IAA24250; Tue, 12 Nov 1996 08:08:16 -0700 Received: by fast.cs.utah.edu (8.6.10/utah-2.15-leaf) id IAA02827; Tue, 12 Nov 1996 08:08:15 -0700 Date: Tue, 12 Nov 1996 08:08:15 -0700 From: vanmaren@fast.cs.utah.edu (Kevin Van Maren) Message-Id: <199611121508.IAA02827@fast.cs.utah.edu> To: current@FreeBSD.org, smp@FreeBSD.org, smp@csn.net Subject: Re: GigaByte GA-586DX-512 Motherboard Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk +--- | The performance difference between PS/2 and EDO Ram's isn't so | large, that it's worth the higher price. This was the case with | single processor boards, and I think it's also true with mp boards. +--- Actually, FPM RAM is slightly MORE expensive than EDO at the moment. Parity RAM is defintely more expensive than both. Seems like comapnies are producing a lot more EDO these days so prices have come down. One good source for RAM is ChipMerchant: http://www.thechipmerchant.com/ (Careful, the CPU prices are "cash only", bu the listed RAM prices are Credit Card prices). +--- | I'd buy PS/2 RAMS with 60ns and Parity (since most mp boards support | parity checking - or am I wrong -) and would choose a 133 MHZ CPU, | because then memory and bus bandwidth are higher ! 66MHz instead of | 60 MHz. +--- All the 430HX (Triton II) boards support parity (and ECC). Most current (Pentium) baords are Triton-II, inclduing the Gigabyte 586DX-512. --Gene Actually, there are a couple of places that *say* they have Parity EDO...for $12/MB. If you want reliable hardware, go Parity; if it crashes, you'll at least know you have a memory problem. EDO will give a read B/W improvement, but hopefully most things are in the cache anyway. Burst EDO (I haven't found anyplace that wants to sell it to me) improves Write B/W as well. When Parity Burst EDO (or SDRAM is also supported) is available, I'll probably make the plunge; until then I'll stick with 60ns FPM w/parity. From owner-freebsd-current Tue Nov 12 07:32:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA00330 for current-outgoing; Tue, 12 Nov 1996 07:32:59 -0800 (PST) Received: from gargoyle.bazzle.com (gargoyle.bazzle.com [206.103.246.190]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA00320; Tue, 12 Nov 1996 07:32:34 -0800 (PST) Received: from gargoyle.bazzle.com (localhost [127.0.0.1]) by gargoyle.bazzle.com (8.8.2/8.6.12) with SMTP id KAA04441; Tue, 12 Nov 1996 10:30:45 -0500 (EST) Date: Tue, 12 Nov 1996 10:30:45 -0500 (EST) From: "Eric J. Chet" To: Andreas Klemm cc: "Marc G. Fournier" , Steve Passe , smp@FreeBSD.org, current@FreeBSD.org Subject: Re: GigaByte GA-586DX-512 Motherboard In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 12 Nov 1996, Andreas Klemm wrote: > On Tue, 12 Nov 1996, Marc G. Fournier wrote: > > > Does anyone have any recommendations on drives? Or, any drives > > in particular I should stick away from? I heard that SeaGate went downhill > > for awhile there...anyone have a current opinion of them? > > Quantum Atlas 2GB, the 4GB modell is too loud for a home environment. > Both drives have 1 MB cache ! > > Another fast, but loud and expensive drive, is the IBM DHFS .... sorry > forgot the model number. Hello Check out http://www.basoncomputer.com 2.0GB IBM DFHS SCSI 8mS, 3.5"LP, 7200RPM $429 Not a bad deal, Eric J. Chet - ejc@bazzle.com From owner-freebsd-current Tue Nov 12 07:39:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA00679 for current-outgoing; Tue, 12 Nov 1996 07:39:37 -0800 (PST) Received: from neworder.cc.uky.edu (neworder.cc.uky.edu [128.163.18.198]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA00670; Tue, 12 Nov 1996 07:39:21 -0800 (PST) Received: (from soward@localhost) by neworder.cc.uky.edu (8.7/Soward0.1) id KAA04858; Tue, 12 Nov 1996 10:39:18 -0500 (EST) Message-Id: <199611121539.KAA04858@neworder.cc.uky.edu> MIME-Version: 1.0 (NeXT Mail 4.0 v141) Content-Type: text/plain Received: by NeXT.Mailer (1.141) From: John Soward Date: Tue, 12 Nov 96 10:39:17 -0500 To: smp@freebsd.org, current@freebsd.org Subject: Re: GigaByte GA-586DX-512 Motherboard cc: "Marc G. Fournier" Reply-To: soward@service1.uky.edu References: <199611120720.AAA26401@clem.systemsix.com> Organization: University of Kentucky Technical Services X-URL: "http://neworder.cc.uky.edu/" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I too have had excellent luck with this motherboard (and I too bought mine from Atipa, though I had somewhat less luck there ;-). I am not using the smp code (yet), but I've had NT4, FreeBSD2.1.5, current, DOS, Win95, and NEXTSTEP on it. The only things that have irked me were the need to get an ATX case, and the lack of an external SCSI connector...It's been on pretty much 24 hours a day since early august... --- John Soward JpS Systems Programmer 'The Midnight sun will burn you up.' University of Kentucky (NeXT and MIME mail OK) -R. Smith From owner-freebsd-current Tue Nov 12 08:00:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA01377 for current-outgoing; Tue, 12 Nov 1996 08:00:54 -0800 (PST) Received: from charlotte.spiders.com (charlotte.spiders.com [199.224.7.188]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA01372; Tue, 12 Nov 1996 08:00:45 -0800 (PST) Received: (from gwh@localhost) by charlotte.spiders.com (8.6.12/8.6.12) id LAA13027; Tue, 12 Nov 1996 11:03:38 -0500 Message-Id: <199611121603.LAA13027@charlotte.spiders.com> From: gwh@spiders.com (Gene W Homicki) Date: Tue, 12 Nov 1996 11:03:38 -0500 In-Reply-To: John Soward's message as of Nov 12, 10:39 X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: soward@service1.uky.edu, smp@FreeBSD.org, current@FreeBSD.org Subject: Re: GigaByte GA-586DX-512 Motherboard Cc: "Marc G. Fournier" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk +--- | I too have had excellent luck with this motherboard (and I too bought mine | from Atipa, though I had somewhat less luck there ;-). I am not using the smp +--- Me too, to getting it there and slight irks. +--- | on it. The only things that have irked me were the need to get an ATX case, and | the lack of an external SCSI connector...It's been on pretty much 24 hours a | day since early august... +--- Mine came with an external connector (got it a couple of months ago from Atipa). The thing that REALLY irked me was that it requires an ATX form factor case, but a standard power supply connector. So its some wort of AT/ATX hybrid (or low-bred B-). If you order from Atipa (or anywhere else), make sure they send you the right case, the first time. --Gene -- Gene W. Homicki gwh@spiders.com Objective Consulting, Inc. http://www.spiders.com/ Internet Presence Design voice: +1 914.353.3511 From owner-freebsd-current Tue Nov 12 08:10:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA01876 for current-outgoing; Tue, 12 Nov 1996 08:10:59 -0800 (PST) Received: from plains.nodak.edu (tinguely@plains.NoDak.edu [134.129.111.64]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA01827; Tue, 12 Nov 1996 08:10:34 -0800 (PST) Received: (from tinguely@localhost) by plains.nodak.edu (8.8.2/8.8.2) id KAA13353; Tue, 12 Nov 1996 10:10:20 -0600 (CST) Date: Tue, 12 Nov 1996 10:10:20 -0600 (CST) From: Mark Tinguely Message-Id: <199611121610.KAA13353@plains.nodak.edu> To: freebsd-hackers@freebsd.org Subject: -current mbuf reference function Cc: freebsd-current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I don't think the external reference (m_ext.ext_ref) function in the -current sys/mbuf.h is complete. First, the function m_copypacket in kern/uipc_mbuf.c only uses the old style reference incrememnt of: mclrefcnt[mtocl(m->m_ext.ext_buf)]++ and even worse the MCLFREE macros in sys/mbuf.h only uses: --mclrefcnt[mtocl(p)] == 0 to decrement the reference count and check to see if it time to release. I think either a increment/decrement flag is needed to m_ext.ext_ref, or an additional decrement function is needed, and this function is needed in the MCLFREE macro. --mark. From owner-freebsd-current Tue Nov 12 08:12:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA02094 for current-outgoing; Tue, 12 Nov 1996 08:12:41 -0800 (PST) Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA02067 for ; Tue, 12 Nov 1996 08:12:23 -0800 (PST) Received: from gmarco.eclipse.org.eclipse.org (ts1port12d.masternet.it [194.184.65.34]) by scotty.masternet.it (8.7.5/8.7.3) with SMTP id RAA00849 for ; Tue, 12 Nov 1996 17:12:37 +0100 (MET) Message-Id: <3.0b35.32.19961112170719.0068667c@scotty.masternet.it> X-Sender: gmarco@scotty.masternet.it X-Mailer: Windows Eudora Pro Version 3.0b35 (32) Date: Tue, 12 Nov 1996 17:07:59 +0100 To: current@freebsd.org From: Gianmarco Giovannelli Subject: cc: Internal compiler error (again) Mime-Version: 1.0 Content-Type: text/enriched; charset="us-ascii" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am sorry if this is the right list, but with all the changes to the branches I am a little bit confusing. I posted some days ago a message concerning an error while trying to rebuild the world with the 3.0-current (#ctm 2403). I thought it was my fault so I decide to try the 2.2-stable instead. I remove the entire sources tree (rm -r src), I make the dir again and then I patched till ctm #29 I make world and what happens ? :-) --- cut 2.2 error--- building profiled objc library ranlib libobjc_p.a ===> gnu/lib/libregex cc -O -I/usr/src/gnu/lib/libregex -DHAVE_STRING_H=1 -DSTDC_HEADERS=1 -c /usr/src/gnu/lib/libregex/regex.c -o regex.o building standard gnuregex library ranlib libgnuregex.a cc -p -O -I/usr/src/gnu/lib/libregex -DHAVE_STRING_H=1 -DSTDC_HEADERS=1 -c /usr/src/gnu/lib/libregex/regex.c -o regex.po cc: Internal compiler error: program cc1 got fatal signal 6 *** Error code 1 --- cut 3.0 error--- ranlib libobjc_p.a ===> gnu/lib/libregex cc -O -I/usr/src/gnu/lib/libregex -DHAVE_STRING_H=1 -DSTDC_HEADERS=1 -c /usr/src/gnu/lib/libregex/regex.c -o regex.o building standard gnuregex library ranlib libgnuregex.a cc -p -O -I/usr/src/gnu/lib/libregex -DHAVE_STRING_H=1 -DSTDC_HEADERS=1 -c /usr/src/gnu/lib/libregex/regex.c -o regex.po cc: Internal compiler error: program cc1 got fatal signal 6 *** Error code 1 --- cut --- The same error in the same file of the 3.0-current !!!! Now I begin to think is something related the hardware , is it possible ? I run with a cyrix cpu 6x86 166+, 32mb edo ram 60ns, A2940UW , 2hd 2mb Quantum vp32170 wide scsi, some others devices on scsi bus. Is possible is something concerning the cyrix cpu ? As someone suggested me (Frank Terhaar-Yonkers <) I tried to lower the bus clock to 100mhz instead of 133+, to change the ram (with another bank of 32mb ram edo) but everything continue to not work. I'll try to make world on my laptop (p133, 24mbram) to see if it woks... This is my kernel config : --- cut --- # # # $Id: GMARCO,v0.2 # machine "i386" cpu "I486_CPU" ident GMARCO maxusers 4 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 options SCSI_REPORT_GEOMETRY options SCSI_DELAY=1 options BOUNCE_BUFFERS options UCONSOLE options FAILSAFE options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options SYSVSHM options SYSVSEM options SYSVMSG config kernel root on sd0 controller isa0 controller pci0 controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr disk wd2 at wdc1 drive 0 options ATAPI #Enable ATAPI support for IDE bus device wcd0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 controller scbus0 controller ahc0 device sd0 #Hd scsi device st0 #Tape scsi device cd0 #Cd rom Scsi controller snd0 #Generic support for ALL Sound Card device sb0 at isa? port 0x220 irq 5 conflicts drq 1 vector sbintr device opl0 at isa? port 0x388 conflicts device sbmidi0 at isa? port 0x330 device sbxvi0 at isa? drq 5 #Sb16 in 16 BIT DMA 5 device joy0 at isa? port "IO_GAME" device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr device ed0 at isa? port 0x300 net irq 10 iomem 0xd8000 vector edintr 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 lpt0 at isa? port? tty irq 7 vector lptintr device qcam0 at isa? port "IO_LPT1" conflicts flags 1 pseudo-device loop pseudo-device ether pseudo-device log pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip --- cut --- Please let me know anything. Regards... +-------------------------------------+--------------------+ | Internet: gmarco@masternet.it | ,,, | | Internet: gmarco@nettuno.it | (o o) | | BIX : ggiovannelli@bix.com | ---oo0-(_)-0oo--- | | http://www2.masternet.it/ | Gianmarco | +-------------------------------------+--------------------+ From owner-freebsd-current Tue Nov 12 08:22:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA02861 for current-outgoing; Tue, 12 Nov 1996 08:22:43 -0800 (PST) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA02585; Tue, 12 Nov 1996 08:19:56 -0800 (PST) Received: by sovcom.kiae.su id AA18466 (5.65.kiae-1 ); Tue, 12 Nov 1996 19:06:49 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Tue, 12 Nov 96 19:06:49 +0300 Received: (from ache@localhost) by nagual.ru (8.8.2/8.8.2) id SAA00746; Tue, 12 Nov 1996 18:41:17 +0300 (MSK) Message-Id: <199611121541.SAA00746@nagual.ru> Subject: Re: SCB paging is most dangerous option now! In-Reply-To: <199611120703.XAA27655@freefall.freebsd.org> from "Justin T. Gibbs" at "Nov 11, 96 11:03:56 pm" To: gibbs@freefall.freebsd.org (Justin T. Gibbs) Date: Tue, 12 Nov 1996 18:41:16 +0300 (MSK) Cc: current@freebsd.org, scsi@freebsd.org From: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) Organization: self X-Class: Fast X-Mailer: ELM [version 2.4ME+ PL28 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > What were the error messages? > They not stored anywhere now because it seems ANY disk write cause immediately destruction of inode table including syslog writes. As I remember there was something like: data overrun of XXXX bytes detected followed by various retraining/resetting failure attempts. As I remember no one successfull write's happens. my configuration: ahc0: at 0x1c00-0x1cff irq 11 on eisa0 slot 1 ahc0: aic7770 >= Rev E, Single Channel, SCSI Id=7, 4 SCBs when SCB paging is enabled, this line looks like ahc0: aic7770 >= Rev E, Single Channel, SCSI Id=7, 4/255 SCBs ahc0: target 0 Tagged Queuing Device (ahc0:0:0): "CONNER CFP1060S 1.05GB 213C" type 0 fixed SCSI 2 ^^^^ upgraded sd0(ahc0:0:0): Direct-Access 1013MB (2074880 512 byte sectors) ahc0: target 1 Tagged Queuing Device (ahc0:1:0): "IBM DORS-32160 S84A" type 0 fixed SCSI 2 sd1(ahc0:1:0): Direct-Access 2063MB (4226725 512 byte sectors) As I already say, SCB paging works with any _one_ device alone. -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Tue Nov 12 08:29:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA03417 for current-outgoing; Tue, 12 Nov 1996 08:29:48 -0800 (PST) Received: from clem.systemsix.com (clem.systemsix.com [198.99.86.131]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA03406; Tue, 12 Nov 1996 08:29:37 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by clem.systemsix.com (8.6.12/8.6.12) with SMTP id JAA29256; Tue, 12 Nov 1996 09:29:05 -0700 Message-Id: <199611121629.JAA29256@clem.systemsix.com> X-Authentication-Warning: clem.systemsix.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6.5 12/11/95 From: Steve Passe To: gwh@spiders.com (Gene W Homicki) cc: soward@service1.uky.edu, smp@FreeBSD.org, current@FreeBSD.org, "Marc G. Fournier" Subject: Re: GigaByte GA-586DX-512 Motherboard In-reply-to: Your message of "Tue, 12 Nov 1996 11:03:38 EST." <199611121603.LAA13027@charlotte.spiders.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 12 Nov 1996 09:29:05 -0700 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi, > Mine came with an external connector (got it a couple of > months ago from Atipa). The thing that REALLY irked me was that it > requires an ATX form factor case, but a standard power supply > connector. So its some wort of AT/ATX hybrid (or low-bred B-). indeed a bad design point. I guess they were thinking that there were limited sources of ATX supplies at the time... never mind that the case is still different. > If you order from Atipa (or anywhere else), make sure they send you > the right case, the first time. I have to admit I was less than happy with the case. My big gripe is that the case has 6 backplane slot cutouts, but the board supports 7 cards (4 ISA, 4 PCI, one slot shared). So one PCI slot doesn't have a cutout! In general I really like the ATX formfactor. In this case all the MB mounts (except one) are steel posts instead of those flimsy nylon standoffs. Don't know if this is part of the ATX standard, but it fits great, no flexing of the MB when inserting cards! And ALL the card slots are full length, the CPUs and stuff being to the side of the slots. If anyone knows of a good source of ATX cases please speak up. -- Steve Passe | powered by smp@csn.net | FreeBSD From owner-freebsd-current Tue Nov 12 08:30:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA03536 for current-outgoing; Tue, 12 Nov 1996 08:30:55 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA03499; Tue, 12 Nov 1996 08:30:31 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.7.5/8.7.3) id IAA15688; Tue, 12 Nov 1996 08:29:54 -0800 (PST) From: "Rodney W. Grimes" Message-Id: <199611121629.IAA15688@GndRsh.aac.dev.com> Subject: Re: GigaByte GA-586DX-512 Motherboard In-Reply-To: from Andreas Klemm at "Nov 12, 96 12:28:35 pm" To: andreas@klemm.gtn.com (Andreas Klemm) Date: Tue, 12 Nov 1996 08:29:53 -0800 (PST) Cc: scrappy@ki.net, smp@csn.net, smp@FreeBSD.org, current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > On Tue, 12 Nov 1996, Marc G. Fournier wrote: > > > Does anyone have any recommendations on drives? Or, any drives > > in particular I should stick away from? I heard that SeaGate went downhill > > for awhile there...anyone have a current opinion of them? > > Quantum Atlas 2GB, the 4GB modell is too loud for a home environment. > Both drives have 1 MB cache ! I'll correct that, the 4GB model has a 2MB cache on it... -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-current Tue Nov 12 08:41:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA04439 for current-outgoing; Tue, 12 Nov 1996 08:41:13 -0800 (PST) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA04421; Tue, 12 Nov 1996 08:41:01 -0800 (PST) Received: from localhost (scrappy@localhost) by quagmire.ki.net (8.8.2/8.7.5) with SMTP id LAA16408; Tue, 12 Nov 1996 11:40:50 -0500 (EST) Date: Tue, 12 Nov 1996 11:40:50 -0500 (EST) From: "Marc G. Fournier" To: soward@service1.uky.edu cc: smp@freebsd.org, current@freebsd.org Subject: Re: GigaByte GA-586DX-512 Motherboard In-Reply-To: <199611121539.KAA04858@neworder.cc.uky.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 12 Nov 1996, John Soward wrote: > > I too have had excellent luck with this motherboard (and I too bought mine > from Atipa, though I had somewhat less luck there ;-). I am not using the smp > code (yet), but I've had NT4, FreeBSD2.1.5, current, DOS, Win95, and NEXTSTEP > on it. The only things that have irked me were the need to get an ATX case, and ATX case? Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Tue Nov 12 08:47:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA04944 for current-outgoing; Tue, 12 Nov 1996 08:47:30 -0800 (PST) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA04926 for ; Tue, 12 Nov 1996 08:47:15 -0800 (PST) Received: by halloran-eldar.lcs.mit.edu; (5.65v3.2/1.1.8.2/19Aug95-0530PM) id AA09956; Tue, 12 Nov 1996 11:47:03 -0500 Date: Tue, 12 Nov 1996 11:47:03 -0500 From: Garrett Wollman Message-Id: <9611121647.AA09956@halloran-eldar.lcs.mit.edu> To: Mark Tinguely Cc: freebsd-current@FreeBSD.org Subject: -current mbuf reference function In-Reply-To: <199611121610.KAA13353@plains.nodak.edu> References: <199611121610.KAA13353@plains.nodak.edu> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk < said: > and even worse the MCLFREE macros in sys/mbuf.h only uses: > --mclrefcnt[mtocl(p)] == 0 > to decrement the reference count and check to see if it time to release. This is correct. It is an error to call MCLFREE if there is a free function (m_ext.ext_free) set. The calling convention could be a lot better (I'd like to have it take a pointer to the mbuf rather than the buffer pointer and size parameters).... > I think either a increment/decrement flag is needed to m_ext.ext_ref, or an > additional decrement function is needed Nope, that function is m_ext.ext_free. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Tue Nov 12 08:58:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA05545 for current-outgoing; Tue, 12 Nov 1996 08:58:29 -0800 (PST) Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA05533 for ; Tue, 12 Nov 1996 08:58:17 -0800 (PST) Received: from campa.panke.de (anonymous214.ppp.cs.tu-berlin.de [130.149.17.214]) by mail.cs.tu-berlin.de (8.6.13/8.6.12) with ESMTP id RAA04752 for ; Tue, 12 Nov 1996 17:46:11 +0100 Received: (from wosch@localhost) by campa.panke.de (8.6.12/8.6.12) id QAA00777; Tue, 12 Nov 1996 16:53:26 +0100 Date: Tue, 12 Nov 1996 16:53:26 +0100 From: Wolfram Schneider Message-Id: <199611121553.QAA00777@campa.panke.de> To: current@freebsd.org Subject: (add|rm)(user|group) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I did not got a reply for the removeuser, addgroup, and rmgroup scripts. So I guess they works well ;-) If nobody objects I will change the -current Makefile and install the scripts in /usr/sbin/ Wolfram From owner-freebsd-current Tue Nov 12 09:00:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA05697 for current-outgoing; Tue, 12 Nov 1996 09:00:05 -0800 (PST) Received: from romberg.imf.unit.no (romberg.imf.unit.no [129.241.15.150]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA05642 for ; Tue, 12 Nov 1996 08:59:45 -0800 (PST) Received: (from arnej@localhost) by romberg.imf.unit.no (8.7.5/8.7.3) id RAA24471 for freebsd-current@freebsd.org; Tue, 12 Nov 1996 17:59:39 +0100 (MET) Date: Tue, 12 Nov 1996 17:59:39 +0100 (MET) From: Arne Henrik Juul Message-Id: <199611121659.RAA24471@romberg.imf.unit.no> To: freebsd-current@freebsd.org Subject: dirs missing from mtree files? Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Trying to do 'make world' in a -current tree builds OK, but on install stops on these errors: install: mkstemp: /usr/share/examples/syscons/fonts for /usr/share/examples/sysc ons/fonts/INDEX.fonts: No such file or directory install: mkstemp: /usr/share/examples/syscons/keymaps for /usr/share/examples/sy scons/keymaps/INDEX.keymaps: No such file or directory install: mkstemp: /usr/share/examples/syscons/scrnmaps for /usr/share/examples/s yscons/scrnmaps/Makefile: No such file or directory Something missing from the mtree files, or what? - Arne H. J. From owner-freebsd-current Tue Nov 12 09:14:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA06535 for current-outgoing; Tue, 12 Nov 1996 09:14:36 -0800 (PST) Received: from brimstone.gage.com (brimstone.gage.com [205.217.2.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA06272; Tue, 12 Nov 1996 09:08:22 -0800 (PST) Received: (from mail@localhost) by brimstone.gage.com (8.8.2/8.7.3) id LAA04391; Tue, 12 Nov 1996 11:07:16 -0600 (CST) Received: from octopus.gage.com(158.60.57.50) by brimstone.gage.com via smap (V2.0beta) id xma004389; Tue, 12 Nov 96 11:06:58 -0600 Received: from squid.gage.com (squid [158.60.57.101]) by octopus.gage.com (8.7.5/8.7.3) with SMTP id KAA05438; Tue, 12 Nov 1996 10:57:40 -0600 (CST) Received: from schemer by squid.gage.com (NX5.67e/NX3.0S) id AA14777; Tue, 12 Nov 96 10:57:38 -0600 Message-Id: <9611121657.AA14777@squid.gage.com> Received: by schemer.gage.com (NX5.67g/NX3.0X) id AA03568; Tue, 12 Nov 96 11:08:54 -0600 Content-Type: text/plain Mime-Version: 1.0 (NeXT Mail 4.0 v146.2) In-Reply-To: <199611121629.JAA29256@clem.systemsix.com> X-Nextstep-Mailer: Mail 3.3 (Enhance 1.3) Received: by NeXT.Mailer (1.146.2) From: Ben Black Date: Tue, 12 Nov 96 11:08:53 -0600 To: Steve Passe Subject: Re: GigaByte GA-586DX-512 Motherboard Cc: gwh@spiders.com (Gene W Homicki), soward@service1.uky.edu, smp@freebsd.org, current@freebsd.org, "Marc G. Fournier" References: <199611121629.JAA29256@clem.systemsix.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >If anyone knows of a good source of ATX cases please speak up. > i have an In-Win Q500A full tower case. it is fantastic, but it costs an arm and a leg. the motherboard and cards are mounted on a tray that slide out the back of the case, it's all steel, and has lots of space for fans (i have tons of high flow panaflwo fans around). b3n From owner-freebsd-current Tue Nov 12 09:27:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA07109 for current-outgoing; Tue, 12 Nov 1996 09:27:30 -0800 (PST) Received: from clem.systemsix.com (clem.systemsix.com [198.99.86.131]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA07099; Tue, 12 Nov 1996 09:27:18 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by clem.systemsix.com (8.6.12/8.6.12) with SMTP id KAA29604; Tue, 12 Nov 1996 10:21:13 -0700 Message-Id: <199611121721.KAA29604@clem.systemsix.com> X-Authentication-Warning: clem.systemsix.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6.5 12/11/95 From: Steve Passe To: "Marc G. Fournier" cc: soward@service1.uky.edu, smp@freebsd.org, current@freebsd.org Subject: Re: GigaByte GA-586DX-512 Motherboard In-reply-to: Your message of "Tue, 12 Nov 1996 11:40:50 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 12 Nov 1996 10:21:13 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, > On Tue, 12 Nov 1996, John Soward wrote: > ... > > on it. The only things that have irked me were the need to get an ATX case, and > > ATX case? yes, this is an ATX formfactor board, which is either what they all will be in the not too distant future, OR the "beta" of motherboards. see this for details on ATX: http://www.intel.com/pc-supp/motherbd/atx.htm heres a couple links to the GA586DX: http://www.giga-byte.com/GA586DX.html http://www.surfusa.com/mbs/ga/586dx.html -- Steve Passe | powered by smp@csn.net | FreeBSD From owner-freebsd-current Tue Nov 12 09:32:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA07495 for current-outgoing; Tue, 12 Nov 1996 09:32:09 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA07464; Tue, 12 Nov 1996 09:32:00 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.2/8.8.2) with SMTP id JAA00583; Tue, 12 Nov 1996 09:29:44 -0800 (PST) Message-ID: <3288B3F1.41C67EA6@whistle.com> Date: Tue, 12 Nov 1996 09:29:21 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Mark Tinguely CC: freebsd-hackers@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: -current mbuf reference function References: <199611121610.KAA13353@plains.nodak.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Mark Tinguely wrote: > > I don't think the external reference (m_ext.ext_ref) function in the -current > sys/mbuf.h is complete. First, the function m_copypacket in kern/uipc_mbuf.c > only uses the old style reference incrememnt of: > > mclrefcnt[mtocl(m->m_ext.ext_buf)]++ > > and even worse the MCLFREE macros in sys/mbuf.h only uses: > > --mclrefcnt[mtocl(p)] == 0 > > to decrement the reference count and check to see if it time to release. > > I think either a increment/decrement flag is needed to m_ext.ext_ref, or an > additional decrement function is needed, and this function is needed in the > MCLFREE macro. > > --mark. This code was originally in BSD4.3. We use it in our 4.3 , OSF1 and FreeBSD based systems to pass around externally defined objects the idea is that if the M_EXT flag is set but there is no ext_free function defined, then is is a default Mbuf cluster and the default functions are called. If there is a special ext_free function defined then use it instead. A cleaner method would be to Impliment the default functions in the same was as teh exception functions, in other words always have ext_free and ext_ref pointers defined, but in the default case they point to the default functions. I think it wasn't done that way simply to reduce the impact of the change, as the Mbuf cluster code was pre-existing. the function ext_ref is to increment the number of references to the object (e.g. if you were to duplicate the mbuf, but not duplicate the buffer,) and the ext_free routine is to decrement the references, (and presumably free the item in an item-specific manner if the reference count reaches 0 ). The MCLFREE macro is not included in the MFREE macro only because that would duplicate the MBUFLOCK code. The MCLFREE code should only be called if the ext_free entry is NULL (as it is set to NULL in MCLGET). It could be argued that the MCLFREE macro should be able to handle the case inn which the free function exists, and call that instead.. I don't know how many active cases of MCLFREE there are in the code.. I can probably put up a good case that there shouldn't be many if any. usually MFREE could surfice as usually the whole mbuf is being freed. there is a further enhancement from the OSF code that is rather stunningly brilliant, that Matt Thomas wants to bring in.. I once had a version that incoporated it as well.. (for some ATM code he wants to import I believe) I may still do it.. julian From owner-freebsd-current Tue Nov 12 09:33:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA07661 for current-outgoing; Tue, 12 Nov 1996 09:33:46 -0800 (PST) Received: from troll.uunet.ca (troll.uunet.ca [142.77.1.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA07645; Tue, 12 Nov 1996 09:33:25 -0800 (PST) Received: from localhost by troll.uunet.ca with SMTP id <21007-14637>; Tue, 12 Nov 1996 12:33:04 -0500 Date: Tue, 12 Nov 1996 12:32:59 -0500 From: Cat Okita To: "Marc G. Fournier" cc: soward@service1.uky.edu, smp@FreeBSD.org, current@FreeBSD.org Subject: Re: GigaByte GA-586DX-512 Motherboard In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 12 Nov 1996, Marc G. Fournier wrote: > ATX case? What is ATX? ATX is a baseboard mechanical specification that addresses shortcomings in the Baby AT design. Think of ATX as a Baby AT board rotated 90 degrees so that the long side is to the rear of the chassis. This allows designers to add more on-board I/O, if they want. In addition, CPU and SIMM sockets are relocated to improve accessibility and eliminate interference with expansion slots. What are the main advantages? The ATX form-factor provides big advantages for manufacturers, integrators, and users of personal computers. For PC manufacturers, ATX brings the following benefits: 7 ATX allows use of higher integration and better design to reduce total system cost More on board I/O connectors reduce internal cabling and improve manufacturability 7 Relocated CPU and SIMM sockets allow easy access and dont interfere with add-in cards 7 All expansion slots support full length add-in cards 7 Improved layout allows a single fan to cool the entire baseboard, reducing cost and improving system acoustics 7 Double height flexible I/O supports multimedia requirements and highly integrated designs 7 Higher integration and less cabling means fewer emissions problems and easier CE mark certification with ATX based products 7 I/O supports future requirements like USB, video in/out, TV in/out, cable and ISDN 7 Single power connector located near the processor simplifies manufacturing and improves power trace routing 7 Floppy and IDE connectors are located close to peripheral bays to allow shorter cables 7 Mounting holes are defined to ease transition from Baby AT, allowing chassis to be designed that can accept ATX or Baby AT boards with minimal modification Advantages for Integrators and VARs For systems integrators and Value Added Resellers (VARs), ATX greatly eases the integration effort. With higher integration systems, there is less cable clutter and there are more empty expansion slots left for add-in card configuration; also, since the CPU and memory are relocated, these slots are all full length. Advantages for End Users For end users, ATX means better designed systems that are quieter, more reliable, easier to upgrade and easier to service. The improved layout gives the end user easy access to key components like memory and CPU sites, making upgrades much easier. Since all expansion slots in ATX systems are full length, end users need have no worries on fitting the latest full length multimedia upgrade boards in their systems. From owner-freebsd-current Tue Nov 12 09:34:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA07750 for current-outgoing; Tue, 12 Nov 1996 09:34:49 -0800 (PST) Received: from troll.uunet.ca (troll.uunet.ca [142.77.1.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA07718; Tue, 12 Nov 1996 09:34:22 -0800 (PST) Received: from localhost by troll.uunet.ca with SMTP id <21007-14637>; Tue, 12 Nov 1996 12:34:05 -0500 Date: Tue, 12 Nov 1996 12:33:58 -0500 From: Cat Okita To: Steve Passe cc: Gene W Homicki , soward@service1.uky.edu, smp@FreeBSD.org, current@FreeBSD.org, "Marc G. Fournier" Subject: Re: GigaByte GA-586DX-512 Motherboard In-Reply-To: <199611121629.JAA29256@clem.systemsix.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 12 Nov 1996, Steve Passe wrote: > In general I really like the ATX formfactor. In this case all the MB > mounts (except one) are steel posts instead of those flimsy nylon > standoffs. Don't know if this is part of the ATX standard, but it > fits great, no flexing of the MB when inserting cards! And ALL the card > slots are full length, the CPUs and stuff being to the side of the slots. > > If anyone knows of a good source of ATX cases please speak up. I've just gotten a case from 'Procase' - I'll forward more once I've got the thing out of its box *grin* Cat From owner-freebsd-current Tue Nov 12 09:43:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA08360 for current-outgoing; Tue, 12 Nov 1996 09:43:41 -0800 (PST) Received: from spinner.DIALix.COM (root@spinner.DIALix.COM [192.203.228.67]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA08335; Tue, 12 Nov 1996 09:43:01 -0800 (PST) Received: from spinner.DIALix.COM (peter@localhost.DIALix.oz.au [127.0.0.1]) by spinner.DIALix.COM (8.8.2/8.8.2) with ESMTP id BAA12031; Wed, 13 Nov 1996 01:41:53 +0800 (WST) Message-Id: <199611121741.BAA12031@spinner.DIALix.COM> X-Mailer: exmh version 1.6.9 8/22/96 To: "Marc G. Fournier" cc: soward@service1.uky.edu, smp@freebsd.org, current@freebsd.org Subject: Re: GigaByte GA-586DX-512 Motherboard In-reply-to: Your message of "Tue, 12 Nov 1996 11:40:50 EST." Date: Wed, 13 Nov 1996 01:41:52 +0800 From: Peter Wemm Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "Marc G. Fournier" wrote: > On Tue, 12 Nov 1996, John Soward wrote: > > > > > I too have had excellent luck with this motherboard (and I too bought mine > > from Atipa, though I had somewhat less luck there ;-). I am not using the s mp > > code (yet), but I've had NT4, FreeBSD2.1.5, current, DOS, Win95, and NEXTST EP > > on it. The only things that have irked me were the need to get an ATX case, and > > ATX case? yeah, a long overdue idea. Basically, it's a standard form factor defining the shape, size etc of motherboards and has the connectors on the rear edge (serial, parallel, mouse, kbd etc) rather than floating on ribbon cables. The cpu is moved to a standard location to the right of the slots, directly in the airflow through the power supply. This means there are no obstructions in front of the slots, which are generally all full length.. Typically, this means that you take a standard baby-AT motherboard, rotate it 90 degrees anti-clockwise, and rotate the slot connectors back so they are in the same position as before. For a sample of what they look like, a (large) ATX motherboard can be seen on: http://www.tyan.com/s1668.htm and http://www.tyan.com/s1668i.jpg (no comment on the motherboard, this was just the first ATX picture I could find in my bookmarks :-) > Marc G. Fournier scrappy@ki.net > Systems Administrator @ ki.net scrappy@freebsd.org > Cheers, -Peter From owner-freebsd-current Tue Nov 12 09:43:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA08393 for current-outgoing; Tue, 12 Nov 1996 09:43:56 -0800 (PST) Received: from wgrobez1.remote.louisville.edu (wgrobez1.remote.louisville.edu [136.165.243.183]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA08362 for ; Tue, 12 Nov 1996 09:43:40 -0800 (PST) Received: from localhost (wangel@localhost) by wgrobez1.remote.louisville.edu (8.7.6/8.6.12) with SMTP id MAA07960 for ; Tue, 12 Nov 1996 12:44:05 -0500 (EST) Date: Tue, 12 Nov 1996 12:43:17 -0500 (EST) From: Gary Roberts To: freebsd-current@freebsd.org Subject: Problem w/ make world Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Finally got supped(thanks!) but now make world pukes: ===> libgmp mkdir /usr/obj/usr/src/gnu/lib/libgmp/mpz mkdir /usr/obj/usr/src/gnu/lib/libgmp/mpf mkdir /usr/obj/usr/src/gnu/lib/libgmp/mpq make: don't know how to make /usr/src/gnu/lib/libgmp/../../../contrib/libgmp/mpn /bsd.h. Stop *** Error code 2 Stop. *** Error code 1 Stop. *** Error code 1 That's the errors ... Thanks again!! Gary Roberts System Admin. -- Altered Reality. http://136.165.243.183 -- Main User Pages From owner-freebsd-current Tue Nov 12 09:43:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA08366 for current-outgoing; Tue, 12 Nov 1996 09:43:44 -0800 (PST) Received: from r33h77.res.gatech.edu (r33h77.res.gatech.edu [128.61.33.77]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA08347 for ; Tue, 12 Nov 1996 09:43:22 -0800 (PST) Received: (from jason@localhost) by r33h77.res.gatech.edu (8.8.2/8.7.3) id MAA04691 for freebsd-current@freebsd.org; Tue, 12 Nov 1996 12:43:23 -0500 (EST) From: Jason Bennett Message-Id: <199611121743.MAA04691@r33h77.res.gatech.edu> Subject: Fvwm2 To: freebsd-current@freebsd.org Date: Tue, 12 Nov 1996 12:43:23 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm running 3.0-Current, but when I try to compile the Fvwm2 port, it claims a patch step failed. I just upgraded, did a make world, then rebuilt the kernal. Did I forget something? jason -- Jason Bennett, jbennett@cc.gatech.edu | Member, Team OS/2! CS Major, Georgia Institute of Technology | Senior TA, CS 1501! Believer in Jesus Christ as Savior and Lord | VP-Comm, BSU! http://bsu.gt.ed.net/jason/ | finger for PGP key! From owner-freebsd-current Tue Nov 12 09:51:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA08905 for current-outgoing; Tue, 12 Nov 1996 09:51:15 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA08791 for ; Tue, 12 Nov 1996 09:50:07 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.2/8.8.2) with SMTP id JAA01022; Tue, 12 Nov 1996 09:45:39 -0800 (PST) Message-ID: <3288B7AB.167EB0E7@whistle.com> Date: Tue, 12 Nov 1996 09:45:15 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Garrett Wollman CC: Mark Tinguely , freebsd-current@freebsd.org Subject: Re: -current mbuf reference function References: <199611121610.KAA13353@plains.nodak.edu> <9611121647.AA09956@halloran-eldar.lcs.mit.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Garrett Wollman wrote: > > < said: > > > and even worse the MCLFREE macros in sys/mbuf.h only uses: > > > --mclrefcnt[mtocl(p)] == 0 > > > to decrement the reference count and check to see if it time to release. > > This is correct. It is an error to call MCLFREE if there is a free > function (m_ext.ext_free) set. The calling convention could be a lot > better (I'd like to have it take a pointer to the mbuf rather than the > buffer pointer and size parameters).... In the places we use it, the free routine wouldn't know an mbuf if one came up and kicked it in the shins.. I really wanted to copy the syntax of the earlier code, but was afraid that people would yell about bloat.. in that version, the external information was: ext_start address of start of external buffer. ext_size size of external buffer ext_free() function to decrement references/free ext_ref() function to increment references ext_handle opaque ID by which the ext_free and ext_ref functions Identified the object ext_arg2 opaque second argument to ref and free. This avoided overloading the start/size as arguments to the free and allows object to be freed by 'name' or other more abstract schemes, rather than just a pointer.. (or in the scheme we originally used, the extra arg pointed to an associateed structure that was allocated with, but not within the bounds of, the buffer). In that version all external frees used the ext_free() pointer which was usually a pointer to m_clfree() this meant there was an aditional function call when a MACRO might sometimes have been sufficient. (I think it's cleaner though) > > > I think either a increment/decrement flag is needed to m_ext.ext_ref, or an > > additional decrement function is needed > > Nope, that function is m_ext.ext_free. exactly.. it's more a 'remove reference and free if 0' > From owner-freebsd-current Tue Nov 12 09:54:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA09182 for current-outgoing; Tue, 12 Nov 1996 09:54:56 -0800 (PST) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA08580; Tue, 12 Nov 1996 09:47:16 -0800 (PST) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id JAA18456; Tue, 12 Nov 1996 09:46:49 -0800 (PST) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id JAA06447; Tue, 12 Nov 1996 09:46:43 -0800 (PST) Message-Id: <199611121746.JAA06447@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Andreas Klemm cc: "Marc G. Fournier" , Steve Passe , smp@freebsd.org, current@freebsd.org Subject: Re: GigaByte GA-586DX-512 Motherboard In-reply-to: Your message of Tue, 12 Nov 96 12:26:01 +0100. Date: Tue, 12 Nov 1996 09:46:42 -0800 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Many people say, that it's better to choose a > - 200 MHz CPU instead of a 180 MHz CPU > - 166 MHz CPU instead of a 150 MHz CPU > - 133 MHz CPU instead of a 150 MHz CPU These are OK, although I'd put "166 MHz CPU instead of a 180"... > - 100 MHz CPU instead of a 120 MHz CPU No, in my experience, a 120 is actually faster than a 100 for everything I've benchmarked. The 120 is 20% faster than a 100, but the advantage is much smaller than that. The difference is small enough that I can say that a 133 will probably be faster than a 150 in most cases, and a 166 will definitely be faster than a 180, in almost every case. Note also that these are specifically Pentiums. Pentium Pros and/or Cyrix 6x86s might have totally different characteristics (but I would expect them to roughly follow the same trend). ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-current Tue Nov 12 10:01:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA09658 for current-outgoing; Tue, 12 Nov 1996 10:01:19 -0800 (PST) Received: from clem.systemsix.com (clem.systemsix.com [198.99.86.131]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA09538; Tue, 12 Nov 1996 10:00:29 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by clem.systemsix.com (8.6.12/8.6.12) with SMTP id KAA29886; Tue, 12 Nov 1996 10:59:11 -0700 Message-Id: <199611121759.KAA29886@clem.systemsix.com> X-Authentication-Warning: clem.systemsix.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6.5 12/11/95 From: Steve Passe To: Cat Okita cc: "Marc G. Fournier" , soward@service1.uky.edu, smp@FreeBSD.org, current@FreeBSD.org, freebsd-hardware@FreeBSD.org Subject: Re: GigaByte GA-586DX-512 Motherboard In-reply-to: Your message of "Tue, 12 Nov 1996 12:32:59 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 12 Nov 1996 10:59:10 -0700 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi, Last message to -current Lets move this from -current to hardware where it belongs (keep smp, please) -- Steve Passe | powered by smp@csn.net | FreeBSD From owner-freebsd-current Tue Nov 12 10:02:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA09791 for current-outgoing; Tue, 12 Nov 1996 10:02:58 -0800 (PST) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA09266; Tue, 12 Nov 1996 09:56:22 -0800 (PST) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id JAA18697; Tue, 12 Nov 1996 09:56:15 -0800 (PST) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id JAA06618; Tue, 12 Nov 1996 09:56:09 -0800 (PST) Message-Id: <199611121756.JAA06618@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: "Marc G. Fournier" cc: Steve Passe , smp@freebsd.org, current@freebsd.org Subject: Re: GigaByte GA-586DX-512 Motherboard In-reply-to: Your message of Tue, 12 Nov 96 03:46:11 -0500. Date: Tue, 12 Nov 1996 09:56:09 -0800 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>I recommend 64meg of parity. Don't really have direct knowledge of EDO vs not. > Hrmmm...I had thought that EDO RAM was better because it had >'on chip' cache or something like that ... Uh, no. EDO RAM simply takes less clock cycles per access than standard (or FPM) RAM. And EDO isn't more expensive. It hasn't been for many months. Parity RAM will be more expensive (not that I'm saying you shouldn't buy it). >> > How about Hard Drive? atipa doesn't list Seagates, that I can find, >> >and recent experiencees with Quantum are steering me clear of them. >>atipa carries a rather limited selection in general, just how they do business. >> I would suggest getting the drive from someplace that carries what you want. A place I have been generall happy with: http://www.basoncomputer.com/. > Does anyone have any recommendations on drives? Or, any drives >in particular I should stick away from? I heard that SeaGate went downhill >for awhile there...anyone have a current opinion of them? The IBM drives appear to be particularly good values at the moment. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-current Tue Nov 12 10:06:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA10061 for current-outgoing; Tue, 12 Nov 1996 10:06:49 -0800 (PST) Received: from rosie.scsn.net (scsn.net [206.25.246.12]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA10047 for ; Tue, 12 Nov 1996 10:06:33 -0800 (PST) Received: from rhiannon.scsn.net (cola33.scsn.net [206.25.247.33]) by rosie.scsn.net (post.office MTA v2.0 0813 ID# 0-13529) with SMTP id AAA154; Tue, 12 Nov 1996 13:05:26 -0500 Message-ID: <3288BCB4.1119@scsn.net> Date: Tue, 12 Nov 1996 13:06:44 -0500 From: dmaddox@scsn.net (Donald J. Maddox) Reply-To: dmaddox@scsn.net X-Mailer: Mozilla 3.0Gold (Win95; I) MIME-Version: 1.0 To: Poul-Henning Kamp CC: freebsd-current@FreeBSD.org Subject: Re: Sup References: <14810.847779521@critter.tfs.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Poul-Henning Kamp wrote: > > In message .edu>, Gary Roberts writes: > >Hey all. > > > >I've been trying for 2 days now to sup my tree. However, I keep getting > >Connection Refused when trying to run sup. Is the server down? Am I > >missing something? I got a new supfile, and I still have my old one, they > >both don't work. > > switch to another sup server or to cvsup. sup is no longer supported > on freebsd.org, since it loads the line of our host too much. Hmmm... I'm using CVSup, and still seeing something like 'Rejected by server: Too many simultaneous connections' every time I try to update. From owner-freebsd-current Tue Nov 12 10:06:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA10067 for current-outgoing; Tue, 12 Nov 1996 10:06:53 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA10058 for ; Tue, 12 Nov 1996 10:06:43 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA20485; Tue, 12 Nov 1996 10:55:36 -0700 From: Terry Lambert Message-Id: <199611121755.KAA20485@phaeton.artisoft.com> Subject: Re: ufs is too slow? To: gibbs@freefall.freebsd.org (Justin T. Gibbs) Date: Tue, 12 Nov 1996 10:55:36 -0700 (MST) Cc: mark@quickweb.com, terry@lambert.org, roberto@keltia.freenix.fr, freebsd-current@FreeBSD.org In-Reply-To: <199611120131.RAA04255@freefall.freebsd.org> from "Justin T. Gibbs" at Nov 11, 96 05:31:22 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Just FYI, NTFS will not be the "server" filesystem for NT 5.0. It will be > replaced with the Veritas File System and the Veritas volume manager. Heh. I knew that. I'm interested to know what they plan to do about upgrade, though... I know 4.0 dropped HPFS, and *no* upgrade path was given... 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-current Tue Nov 12 10:16:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA10728 for current-outgoing; Tue, 12 Nov 1996 10:16:51 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA10700 for ; Tue, 12 Nov 1996 10:16:37 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA20519; Tue, 12 Nov 1996 11:01:41 -0700 From: Terry Lambert Message-Id: <199611121801.LAA20519@phaeton.artisoft.com> Subject: Re: ufs is too slow? To: phk@critter.tfs.com (Poul-Henning Kamp) Date: Tue, 12 Nov 1996 11:01:41 -0700 (MST) Cc: terry@lambert.org, msmith@atrad.adelaide.edu.au, danj@3skel.com, bsdcur@shadows.aeon.net, jgreco@brasil.moneng.mei.com, freebsd-current@freebsd.org In-Reply-To: <13977.847763071@critter.tfs.com> from "Poul-Henning Kamp" at Nov 12, 96 02:44:31 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >I believe it works; Margo knows what the hell she's doing, unlike many > >people who try to pass themselves off as FS experts. There's really > >comparatively very little real FS research going on in the world, and > >I'd stack Margo up there with John Heidemann and the other Names in a > >heartbeat. > > She just doesn't seem to want to answer Kirks comments... I haven't heard about a conflict between Margo and Kirk. I have heard that Kirk was bludgeoning in soft updates according to the Ganger/Patt paper, and that they would only apply to FFS... which sort of craps on Margo's work, since she shares code (UFS) with the code he's changing. I don't know if Kirk was responsible for the Heidemann code integration, but CSRG screwed that up a bit as well (and it was not fixed in Lite2). Hell, FreeBSD, NetBSD, and OpenBSD have all perpetuated the screwup... tell me that the linkage table in vfs_init() is no longer sized off of the static UFS descriptor table (for instance). I still disagree with the implementation of the Ganger/Patt changes as FS delta instead of graph reduction (considering each FS as an event node graph, with commutative nd associative node relationships). It seems strange to me to make the soft update work apply to one (and only one) FS... 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-current Tue Nov 12 10:18:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA10871 for current-outgoing; Tue, 12 Nov 1996 10:18:06 -0800 (PST) Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA10791; Tue, 12 Nov 1996 10:17:16 -0800 (PST) Received: (from bsdcur@localhost) by shadows.aeon.net (8.7.5/8.6.9) id UAA02970; Tue, 12 Nov 1996 20:16:39 +0200 (EET) From: mika ruohotie Message-Id: <199611121816.UAA02970@shadows.aeon.net> Subject: Re: GigaByte GA-586DX-512 Motherboard To: scrappy@ki.net (Marc G. Fournier) Date: Tue, 12 Nov 1996 20:16:39 +0200 (EET) Cc: smp@freebsd.org, current@freebsd.org In-Reply-To: from "Marc G. Fournier" at "Nov 12, 96 00:16:02 am" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Apparantly they have had a great deal of problems with this board and are not > > Can anyone comment on this? I've always had good dealing with > the ASUS brand of motherboards, but is there an equivalent ASUS motherboard > that ppl would recommend? well. i've used the DX board for a while, but not with dual cpu's... didnt have any reasonable way to get smp part at the time... too bad. and i had no problems whatsoever with it running freebsd... > I'm wondering if their "great deal of problems" might have been > with earlier models, and they just said to hell with carrying it altogether? i have no idea. unless. the board is _very_ picky about what kinds ram you throw into it. if it's edo/true parity ram, expect probs unless it's high quolity ram. example. with poor ram i got easy crashes when the parity check was on, finally it messed up the inodes from sd0a. then i turned that off, and got signal 11's and strange errors with cc... and _all_ that went away right after i changed the ram, now the servers are very happy... and for the record the asus boards are not bug free either. and what makes the said DX interesting is the onboard aic7880, since the board is _cheaper_ than a HX and 2940UW PCI card. atleast here. anyway, i prefer the said board over asus any day coz of the six simm slots and the _easy_ dip switch (only 4) speed configuring... ofcourse, since the latest asus supports these incredible bus speeds, it gets pretty tempting, but. (notice that i havent got my hands on tyans so far) and i _do_ run the servers at work now using the HX version. which is very close to the DX in any ways. while i'm posting, anyone got any information from the TX chipset? since _that_ is something i am interested in testing. gigabyte will have a board out with that chipset very soon after it's out i've been told. > Marc G. Fournier scrappy@ki.net > Systems Administrator @ ki.net scrappy@freebsd.org mickey -- mika ruohotie mika@aeon.net From owner-freebsd-current Tue Nov 12 10:19:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA11032 for current-outgoing; Tue, 12 Nov 1996 10:19:30 -0800 (PST) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA10994 for ; Tue, 12 Nov 1996 10:19:13 -0800 (PST) Received: from critter.tfs.com (localhost.phk.dk [127.0.0.1]) by critter.tfs.com (8.8.2/8.8.2) with ESMTP id MAA15662; Tue, 12 Nov 1996 12:49:34 +0100 (MET) To: dmaddox@scsn.net cc: freebsd-current@FreeBSD.org Subject: Re: Sup In-reply-to: Your message of "Tue, 12 Nov 1996 13:06:44 EST." <3288BCB4.1119@scsn.net> Date: Tue, 12 Nov 1996 12:49:33 +0100 Message-ID: <15660.847799373@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In message <3288BCB4.1119@scsn.net>, Donald J. Maddox writes: >Hmmm... I'm using CVSup, and still seeing something like 'Rejected by >server: Too >many simultaneous connections' every time I try to update. Right now we're actually discussing ways to improve this in -core. I belive that we will soon have a "cvsup server kit" available for people who want to run mirrors for this protocol. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Tue Nov 12 10:21:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA11360 for current-outgoing; Tue, 12 Nov 1996 10:21:09 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA11321; Tue, 12 Nov 1996 10:20:49 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA20558; Tue, 12 Nov 1996 11:09:20 -0700 From: Terry Lambert Message-Id: <199611121809.LAA20558@phaeton.artisoft.com> Subject: Re: GigaByte GA-586DX-512 Motherboard To: cat@uunet.ca (Cat Okita) Date: Tue, 12 Nov 1996 11:09:20 -0700 (MST) Cc: scrappy@ki.net, soward@service1.uky.edu, smp@FreeBSD.org, current@FreeBSD.org In-Reply-To: from "Cat Okita" at Nov 12, 96 12:32:59 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > For end users, ATX means better designed systems > that are quieter, more reliable, easier to upgrade > and easier to service. The improved layout gives the > end user easy access to key components like memory > and CPU sites, making upgrades much easier. Since all > expansion slots in ATX systems are full length, end > users need have no worries on fitting the latest full > length multimedia upgrade boards in their systems. Unless their systems have standard cases... (sorry, couldn't resist). 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-current Tue Nov 12 10:25:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA11656 for current-outgoing; Tue, 12 Nov 1996 10:25:57 -0800 (PST) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA11627 for ; Tue, 12 Nov 1996 10:25:24 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id TAA18359 for ; Tue, 12 Nov 1996 19:26:10 +0100 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id TAA27912 for freebsd-current@freefall.cdrom.com; Tue, 12 Nov 1996 19:35:56 +0100 Date: Tue, 12 Nov 1996 19:35:56 +0100 From: Christoph Kukulies Message-Id: <199611121835.TAA27912@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.FreeBSD.org Subject: ncr phase change messages with newer kernel Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk With a one week old -current kernel I'm getting the following messages (reproducible) sio1: type 16550A qcam0 at 0x378 on isa qcam0: unidirectional parallel port lpt1 at 0x378-0x37f irq 7 on isa lpt1 not probed due to I/O address conflict with qcam0 at 0x378 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in wdc0 not found at 0x1f0 tel0 at 0xd80 irq 15 on isa tel0: card type Teles S0/16.3 (isac version=0 / hscx version=5) npx0 on motherboard npx0: INT 16 interface gus0 at 0x220 irq 12 drq 1 flags 0x3 on isa gus0: changing root device to sd0a sd0(ncr0:0:0): phase change 2-3 10@03d9f6d8 resid=10. disdn0: TEI = 0xa1 = 80 sd0(ncr0:0:0): phase change 2-7 10@03d9f6d8 resid=9. The first phase change message occurs pratically after each reboot. The second sometime later (unpredictably). Admittedly, my binaries (on that machine) aren't quite synchronous with that kernel and I'm trying to get this fixed soon. Anyway I thought I'd better report it.. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Tue Nov 12 11:03:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA13755 for current-outgoing; Tue, 12 Nov 1996 11:03:34 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA13734 for ; Tue, 12 Nov 1996 11:03:23 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA20717; Tue, 12 Nov 1996 11:50:47 -0700 From: Terry Lambert Message-Id: <199611121850.LAA20717@phaeton.artisoft.com> Subject: Re: ufs is too slow? To: michaelh@cet.co.jp (Michael Hancock) Date: Tue, 12 Nov 1996 11:50:47 -0700 (MST) Cc: jgreco@brasil.moneng.mei.com, bsdcur@shadows.aeon.net, freebsd-current@FreeBSD.ORG In-Reply-To: from "Michael Hancock" at Nov 12, 96 03:58:01 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > FFS is in general a great FS... but it is optimized for the general case. > > > > It is particularly poor at handling large directories or lots of writes, > > and news is excellent at pounding on these qualities. > > NTFS uses btrees for large directories and a simple linear method for > small directories. I've seen some tuning tips for SQLServer where they > recommended NTFS for the db and FAT for the logs because NTFS had faster > read performance but FAT had faster write performance. For small files. FAT chains must be linearly traversed, so their performance decreases expotentially (after you normalize for base access rates which are not related to element structure). > I agree that btree scheme would improve the large directory read > performance, while a soft update scheme would improve write performance in > ufs. Yes. Actually, I've been wanting to divorce the VOP's for directory entry manipulation in the same way the FFS/UFS divorce was handled for about three years now (I wanted to do it to UnixWare UFS at Novell). This would allow you to replace the directory entry management with a btree (or whatever you wanted -- skiplists, etc. would probably be a better idea for flexname support) without touching the data store. The problem is that the directory entry I/O is done with block I/O instead of VOP_{READ|WRITE}. Bogus. 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-current Tue Nov 12 11:05:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA13918 for current-outgoing; Tue, 12 Nov 1996 11:05:52 -0800 (PST) Received: from grackle.grondar.za (root@grackle.grondar.za [196.7.18.131]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA13908 for ; Tue, 12 Nov 1996 11:05:37 -0800 (PST) Received: from grackle.grondar.za (mark@localhost.grondar.za [127.0.0.1]) by grackle.grondar.za (8.8.2/8.7.3) with ESMTP id VAA11718; Tue, 12 Nov 1996 21:05:02 +0200 (SAT) Message-Id: <199611121905.VAA11718@grackle.grondar.za> To: Gary Roberts cc: freebsd-current@freebsd.org Subject: Re: Problem w/ make world Date: Tue, 12 Nov 1996 21:05:01 +0200 From: Mark R V Murray Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Are you sure you have the complete src/contrib dir - with libgmp? M Gary Roberts wrote: > Finally got supped(thanks!) but now make world pukes: > > ===> libgmp > mkdir /usr/obj/usr/src/gnu/lib/libgmp/mpz > mkdir /usr/obj/usr/src/gnu/lib/libgmp/mpf > mkdir /usr/obj/usr/src/gnu/lib/libgmp/mpq > make: don't know how to make > /usr/src/gnu/lib/libgmp/../../../contrib/libgmp/mpn > /bsd.h. Stop > *** Error code 2 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > That's the errors ... > > Thanks again!! > > > Gary Roberts > System Admin. -- Altered Reality. > http://136.165.243.183 -- Main User Pages > -- Mark Murray PGP key fingerprint = 80 36 6E 40 83 D6 8A 36 This .sig is umop ap!sdn. BC 06 EA 0E 7A F2 CE CE From owner-freebsd-current Tue Nov 12 11:17:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA14475 for current-outgoing; Tue, 12 Nov 1996 11:17:18 -0800 (PST) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA14449 for ; Tue, 12 Nov 1996 11:16:49 -0800 (PST) Received: from localhost (mark@localhost) by vinyl.quickweb.com (8.7.5/8.6.12) with SMTP id OAA17393; Tue, 12 Nov 1996 14:12:35 -0500 (EST) Date: Tue, 12 Nov 1996 14:12:35 -0500 (EST) From: Mark Mayo To: Terry Lambert cc: "Justin T. Gibbs" , roberto@keltia.freenix.fr, freebsd-current@FreeBSD.org Subject: Re: ufs is too slow? In-Reply-To: <199611121755.KAA20485@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 12 Nov 1996, Terry Lambert wrote: > > Just FYI, NTFS will not be the "server" filesystem for NT 5.0. It will be > > replaced with the Veritas File System and the Veritas volume manager. > > Heh. I knew that. > > I'm interested to know what they plan to do about upgrade, though... I I just checked, and all they mention in the press_release is that they will be using the Veritas Volume Manger - I don't kow if this _necessarily_ implies use of the Veritas File sSystem. And when you look at it, all the veritas file system does above and beyond a NTFS is the ability to 'Live" manage volumes. Please correct me if I'm wrong. They even talk about the performance increases through the use of 'extents" - the same terminology is used to decribe NTFS. To me, they really don't seem that different, and they mention an upgrade procut to be released in mid 1997 for existing NT 4.0 servers -- all this leads me to believe that they might be implementing the volume manager on exisiting NTFS filesystems. All that said, do you think it's worth my time to try and implement NTFS support under FreBSD? I was thinking of trying to get the existing Linux code ruuing, and adding the ability for it to read the 8.3 short file names, but under writeds only write out the long Unicode file name to increase performance. I agree with Terry that NTFS could be significantly faster on a non backwords compatible non-microsoft implementation. Thoughts? -Mark --------------------------------------------------- | Mark Mayo mark@quickweb.com | | RingZero Comp. vinyl.quickweb.com/mark | --------------------------------------------------- "To iterate is human, to recurse divine." - L. Peter Deutsch > know 4.0 dropped HPFS, and *no* upgrade path was given... > > > 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-current Tue Nov 12 11:20:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA14766 for current-outgoing; Tue, 12 Nov 1996 11:20:27 -0800 (PST) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA14691 for ; Tue, 12 Nov 1996 11:19:47 -0800 (PST) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id UAA02718 for ; Tue, 12 Nov 1996 20:19:26 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id UAA21135 for freebsd-current@FreeBSD.ORG; Tue, 12 Nov 1996 20:19:07 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.2/keltia-uucp-2.9) id TAA28644; Tue, 12 Nov 1996 19:53:51 +0100 (MET) Message-ID: Date: Tue, 12 Nov 1996 19:53:50 +0100 From: roberto@keltia.freenix.fr (Ollivier Robert) To: freebsd-current@FreeBSD.ORG (FreeBSD Current Users' list) Subject: Nvi 1.79 in current X-Mailer: Mutt 0.50.05 Mime-Version: 1.0 X-Operating-System: FreeBSD 3.0-CURRENT ctm#2686 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I've sent a patch to Keith to change the accents in the french message catalog (nvi/catalog/french.base) because it was using PC-437 (!) accents. Keith said it would be in the next version. Do we wait for 1.80 or do we add the change now to get it in 2.2-CURRENT ? -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #28: Sun Nov 10 13:37:41 MET 1996 From owner-freebsd-current Tue Nov 12 11:26:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA15598 for current-outgoing; Tue, 12 Nov 1996 11:26:07 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA15537; Tue, 12 Nov 1996 11:25:41 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id UAA27223; Tue, 12 Nov 1996 20:15:46 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.8.2/8.8.2) with SMTP id SAA13298; Tue, 12 Nov 1996 18:56:42 +0100 (MET) Date: Tue, 12 Nov 1996 18:56:42 +0100 (MET) From: Andreas Klemm To: "Rodney W. Grimes" cc: scrappy@ki.net, smp@csn.net, smp@FreeBSD.org, current@FreeBSD.org Subject: Re: GigaByte GA-586DX-512 Motherboard In-Reply-To: <199611121629.IAA15688@GndRsh.aac.dev.com> Message-ID: X-try-apsfilter: ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz X-Fax: +49 2137 2018 X-Phone: +49 2137 2020 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 12 Nov 1996, Rodney W. Grimes wrote: > > Quantum Atlas 2GB, the 4GB modell is too loud for a home environment. > > Both drives have 1 MB cache ! > > I'll correct that, the 4GB model has a 2MB cache on it... Oh wow ! Thanks for correcting me. BTW, the German PC magazine C't made a harddisk test, they also gave information about the noise, the several disks produce (in DB and a sone factor). Be careful if you want to get a 4GB harddisk with 7200 U/min for home environment. I successfully sold a Grand Prix 4GB and bought 2 2GB IBM DORS 32160. ;) -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-current Tue Nov 12 11:29:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA16170 for current-outgoing; Tue, 12 Nov 1996 11:29:46 -0800 (PST) Received: from wgrobez1.remote.louisville.edu (wgrobez1.remote.louisville.edu [136.165.243.183]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA16090 for ; Tue, 12 Nov 1996 11:29:09 -0800 (PST) Received: from localhost (wangel@localhost) by wgrobez1.remote.louisville.edu (8.7.6/8.6.12) with SMTP id OAA08999; Tue, 12 Nov 1996 14:28:04 -0500 (EST) Date: Tue, 12 Nov 1996 14:27:54 -0500 (EST) From: Gary Roberts To: Mark R V Murray cc: freebsd-current@freebsd.org Subject: Re: Problem w/ make world In-Reply-To: <199611121905.VAA11718@grackle.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 12 Nov 1996, Mark R V Murray wrote: > Are you sure you have the complete src/contrib dir - with libgmp? > > M > > make: don't know how to make > > /usr/src/gnu/lib/libgmp/../../../contrib/libgmp/mpn > > /bsd.h. Stop > > *** Error code 2 Yah, I got everything?? I'll try to sup again. Thanks Gary Roberts System Admin. -- Altered Reality. http://136.165.243.183 -- Main User Pages From owner-freebsd-current Tue Nov 12 12:25:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA25047 for current-outgoing; Tue, 12 Nov 1996 12:25:11 -0800 (PST) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA25041; Tue, 12 Nov 1996 12:25:09 -0800 (PST) Message-Id: <199611122025.MAA25041@freefall.freebsd.org> To: Mark Mayo cc: Terry Lambert , roberto@keltia.freenix.fr, freebsd-current@FreeBSD.org Subject: Re: ufs is too slow? In-reply-to: Your message of "Tue, 12 Nov 1996 14:12:35 EST." Date: Tue, 12 Nov 1996 12:25:08 -0800 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >I just checked, and all they mention in the press_release is that they >will be using the Veritas Volume Manger - I don't kow if this >_necessarily_ implies use of the Veritas File sSystem. The volume manager can work on other FS types too, but according to my friend that works at Veritas, VxFS will be ported to NT. I'd have to check again with him to see if they've struck a deal with MS similar to what they have with other vendors (Sun and HP) where you pay X dollars extra and you get VxFS in the box. >And when you look >at it, all the veritas file system does above and beyond a NTFS is the >ability to 'Live" manage volumes. Please correct me if I'm wrong. They >even talk about the performance increases through the use of 'extents" - >the same terminology is used to decribe NTFS. To me, they really don't >seem that different, and they mention an upgrade procut to be released in >mid 1997 for existing NT 4.0 servers -- all this leads me to believe that >they might be implementing the volume manager on exisiting NTFS >filesystems. The main reason MS is looking to Veritas is that NTFS just doesn't perform when striped or mirrored. The NOW project at Cal did I/O comparison studies on x86 platforms using Solaris, FreeBSD, Linux and NT and found that while FreeBSD and Solaris could achieve upwards of 30MB/s through a striped file system, NT topped out at around 9MB/s. This was NT3.51 - they may have improved things for 4.0. VxFS is quite a bit different then NTFS even though they use similar, extent based, algorithms. VxFS is actually very closely related to XFS if you replace VxFS's "binary buddy maps" with the B+Trees of XFS. (XFS was written by a former Veritas employee that jumped ship to SGI). >All that said, do you think it's worth my time to try and implement NTFS >support under FreBSD? It is most certainly valuable. Any FS type we can support that extends the ability of FreeBSD to interoperate in mixed environments is a big win. You want to write an HPFS filesystem too? 8-) >-Mark > >--------------------------------------------------- >| Mark Mayo mark@quickweb.com | >| RingZero Comp. vinyl.quickweb.com/mark | >--------------------------------------------------- >"To iterate is human, to recurse divine." > - L. Peter Deutsch > > >> know 4.0 dropped HPFS, and *no* upgrade path was given... >> >> >> Terry Lambert >> terry@lambert.org >> --- >> Any opinions in this posting are my own and not those of my present >> or previous employers. >> > -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Tue Nov 12 12:41:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA25806 for current-outgoing; Tue, 12 Nov 1996 12:41:42 -0800 (PST) Received: from night.primate.wisc.edu (night.primate.wisc.edu [144.92.43.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA25798 for ; Tue, 12 Nov 1996 12:41:39 -0800 (PST) Received: (from dubois@localhost) by night.primate.wisc.edu (8.8.2/8.8.2) id OAA12836; Tue, 12 Nov 1996 14:43:12 -0600 (CST) Message-Id: <199611122043.OAA12836@night.primate.wisc.edu> Date: Tue, 12 Nov 1996 14:43:11 -0600 From: dubois@primate.wisc.edu (Paul DuBois) To: current@freebsd.org Subject: Re: GigaByte GA-586DX-512 Motherboard In-Reply-To: ; from Andreas Klemm on Nov 12, 1996 18:56:42 +0100 References: <199611121629.IAA15688@GndRsh.aac.dev.com> X-Mailer: Mutt 0.47 Mime-Version: 1.0 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Andreas Klemm writes: > Oh wow ! Thanks for correcting me. BTW, the German PC magazine C't made > a harddisk test, they also gave information about the noise, the several > disks produce (in DB and a sone factor). Be careful if you want to get > a 4GB harddisk with 7200 U/min for home environment. Doesn't have to be 4GB. I had a Digital 1GB 7200RPM drive that finally drove me nuts and that I replaced last week with a 4500RPM Quantum. -- Paul DuBois dubois@primate.wisc.edu Home page: http://www.primate.wisc.edu/people/dubois Software: http://www.primate.wisc.edu/software From owner-freebsd-current Tue Nov 12 12:47:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA26161 for current-outgoing; Tue, 12 Nov 1996 12:47:11 -0800 (PST) Received: from plains.nodak.edu (tinguely@plains.NoDak.edu [134.129.111.64]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA26156 for ; Tue, 12 Nov 1996 12:47:06 -0800 (PST) Received: (from tinguely@localhost) by plains.nodak.edu (8.8.2/8.8.2) id OAA21010; Tue, 12 Nov 1996 14:46:59 -0600 (CST) Date: Tue, 12 Nov 1996 14:46:59 -0600 (CST) From: Mark Tinguely Message-Id: <199611122046.OAA21010@plains.nodak.edu> To: julian@whistle.com, wollman@lcs.mit.edu Subject: Re: -current mbuf reference function Cc: freebsd-current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk insert red face on CLFREE. Things are bad when I can't even read a macro if statement. thanks, I knew this was for the reference count to the data object. I know I need to keep track of my reference count differently because my data is not allocated close to the mbuf data, and the mclrefcnt array won't help me. I am still planning on adding a complete PERM mbuf extension where the mbuf and data are kept together. The free routine will accept a pointer to the mbuf as well as pointers to the data that could get referenced and linked to other mbufs when pages are copied. I would feel better if the m_copypacket function in kern/uipc_mbuf.c would also use the external reference function. --mark. From owner-freebsd-current Tue Nov 12 13:03:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA27005 for current-outgoing; Tue, 12 Nov 1996 13:03:11 -0800 (PST) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA26998 for ; Tue, 12 Nov 1996 13:03:02 -0800 (PST) Received: by halloran-eldar.lcs.mit.edu; (5.65v3.2/1.1.8.2/19Aug95-0530PM) id AA12536; Tue, 12 Nov 1996 16:02:33 -0500 Date: Tue, 12 Nov 1996 16:02:33 -0500 From: Garrett Wollman Message-Id: <9611122102.AA12536@halloran-eldar.lcs.mit.edu> To: Mark Tinguely Cc: julian@whistle.com, wollman@lcs.mit.edu, freebsd-current@freebsd.org Subject: Re: -current mbuf reference function In-Reply-To: <199611122046.OAA21010@plains.nodak.edu> References: <199611122046.OAA21010@plains.nodak.edu> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk < said: > I would feel better if the m_copypacket function in kern/uipc_mbuf.c > would also use the external reference function. It should, but I don't know that m_copypacket is actually used anywhere. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Tue Nov 12 13:13:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA27501 for current-outgoing; Tue, 12 Nov 1996 13:13:31 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA27490 for ; Tue, 12 Nov 1996 13:13:17 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA20928; Tue, 12 Nov 1996 14:02:02 -0700 From: Terry Lambert Message-Id: <199611122102.OAA20928@phaeton.artisoft.com> Subject: Re: ufs is too slow? To: mark@quickweb.com (Mark Mayo) Date: Tue, 12 Nov 1996 14:02:02 -0700 (MST) Cc: terry@lambert.org, gibbs@freefall.freebsd.org, roberto@keltia.freenix.fr, freebsd-current@FreeBSD.org In-Reply-To: from "Mark Mayo" at Nov 12, 96 02:12:35 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > I just checked, and all they mention in the press_release is that they > will be using the Veritas Volume Manger - I don't kow if this > _necessarily_ implies use of the Veritas File sSystem. And when you look > at it, all the veritas file system does above and beyond a NTFS is the > ability to 'Live" manage volumes. Please correct me if I'm wrong. They > even talk about the performance increases through the use of 'extents" - > the same terminology is used to decribe NTFS. To me, they really don't > seem that different, and they mention an upgrade procut to be released in > mid 1997 for existing NT 4.0 servers -- all this leads me to believe that > they might be implementing the volume manager on exisiting NTFS > filesystems. The file manager will supposedly work with FS's other than VXFS, though they were unable to make it work in NetWare, last I heard. I had heard specifically that VXFS would be ported. The "volume manager" product is generally nothing more than "value add" for their VXFS, so I suspect that's still what they are talking about. The Veritas press release made it look like VXFS will be the native FS for NT in the first paragraph... however, they go on to hem, haw, and hedge about their technology being "value add" and about retrofitting their stuff into NT 4.x. From this I suspect the real story is that they are simply value add, and what they got from their deal is the documentation that Microsoft has been promising everyone else for about a year and a half now (ever since they released the sample CDFS code to the developers back when NT 3.5 was beta...). > All that said, do you think it's worth my time to try and implement NTFS > support under FreBSD? Probably. It's at least as valuable as MSDOS, VFAT, HPFS, or EXT2FS support. Any alient FS is a good bet when you are trying to position yourself as an interoperability bridge (FreeBSD's prime strength right now). > I was thinking of trying to get the existing Linux > code ruuing, and adding the ability for it to read the 8.3 short file > names, but under writeds only write out the long Unicode file name to > increase performance. I agree with Terry that NTFS could be significantly > faster on a non backwords compatible non-microsoft implementation. > > Thoughts? The Linux code does not support writing, mostly because their VFS layer is badly abstracted for orthogonal access necessary to support log rollback. FreeBSD actually has similar layering problems, but they are closer to being fixable (less code required than the Linux VFS code). Neither OS supports the idea of multiple name spaces very well. The default NTFS name space is Unicode. The short name support is handled by attributing the files. I believe NTFS was not supported in Win95 because of the old "search continue" having to have a cookie that is valid for an indefinite future time. There was code in the Win95 IFS in the Beta that was taken out in the release that handled the backward compatability interfaces automatically by mapping an LRU cookie list (similar to the *crap* FreeBSD supports for NFS dirent formatting) in there. They removed it because they apparently had an insertion bug and couldn't find it. They hacked the code back in at the VFAT layer, and changed the IFS consumer requirements so that they no longer matched the IFS documentation shipped with the Win95 SDK. I know this because I spent several weeks in WinICE on both versions of the IFSMGR.VXD. I believe that FreeBSD would suffer some serious problems handling short name generation because of this, and this would, in turn, cause problems for programs running in DOS windows on NT when operating against NTFS file names generated by FreeBSD. Specifically, there would be crashes which were simply not recoverable. I have to note at this point that, since names must be handled twice in a conforming-to-MS-expectations-about-name-space implementation, any gains for going to a btree directory layout are probably lost *immediately* on the second inode access for the short name attribute. The soloution is to support multiple name space collision resoloution at the namei layer for a CREATE nameiop. This requires two full directory traversals, the first one locked, for the short name creation. I did this code once already when I ported the long/short name support into FFS for Artisofts FFS port to Win95. This happens to be *exactly* how Win95 deals with name resoloution (using the IFS functions CreateBasis/MatchBasisName/AppendBasisTail) for the same effect, and for the same reasons. The only way to safely correct this is to make the component name handling opaque to the underlying FS. This was the substance of my changes to the namei/VOP_LOOKUP layering when I created the nameifree() and supplied all those patches everyone hated. By moving the buffer free to the layer in which the buffer allocate originated, the interface was made orthogonal, and it was possible to slip in a second iteration of the directory for the short name collision check (which has to be done at this level to assure that multiple client creates do not cause a creation race which results in a duplicate short name). I think that to get past "ready-only" for an NTFS, you will have to readdress these issues. Unfortunately, current keeps changing slightly, and the Lite2 integration has not happened, so my patches are out of date unless you are running my full source base (which is out of date for VM and a couple of other serious subsystems). 8-(. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Nov 12 13:26:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA28051 for current-outgoing; Tue, 12 Nov 1996 13:26:40 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA28039; Tue, 12 Nov 1996 13:26:29 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.7.5/8.7.3) id NAA17321; Tue, 12 Nov 1996 13:24:27 -0800 (PST) From: "Rodney W. Grimes" Message-Id: <199611122124.NAA17321@GndRsh.aac.dev.com> Subject: Re: GigaByte GA-586DX-512 Motherboard In-Reply-To: <199611121756.JAA06618@MindBender.serv.net> from "Michael L. VanLoon -- HeadCandy.com" at "Nov 12, 96 09:56:09 am" To: michaelv@MindBender.serv.net (Michael L. VanLoon -- HeadCandy.com) Date: Tue, 12 Nov 1996 13:24:27 -0800 (PST) Cc: scrappy@ki.net, smp@csn.net, smp@freebsd.org, current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > >>I recommend 64meg of parity. Don't really have direct knowledge of EDO vs not. > > > Hrmmm...I had thought that EDO RAM was better because it had > >'on chip' cache or something like that ... > > Uh, no. EDO RAM simply takes less clock cycles per access than > standard (or FPM) RAM. You should go read some technical specifications before you make such statements. The actual access time changes very very little between EDO (``Extended Data Out'') and FPM (``Fast Page Mode''). The only real effective difference is that EDO memory holds it's data outputs valid after CAS goes back high, allowing a wider and slopper data latching. This _can_ lead to elimination of wait states in poor designs, but does zilch in good designs, since good designs don't need the added 15nS of valid data out as they latch the data in the 5 to 6nS window you get when running FPM at minimum timings. Note that the cycle time for EDO vs FPM is IDENTICAL for every manufactures data sheet I have looked at. Real memory bandwidth is a direct function of cycle time, and has nothing to do with access times. Access times are for wimps, real memory designers work with cycle times :-) :-). You can not transfer 1MB of data out of EDO memory any faster than you can transfer 1MB of data out of FPM. Period. Look over the data sheets, study memory design, _know_ before you speak. Also note that the ``access'' time difference is usually less than 5nS and due to other timing constraints you can rarely if ever take advantage of this. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-current Tue Nov 12 15:06:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA02816 for current-outgoing; Tue, 12 Nov 1996 15:06:01 -0800 (PST) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA02805; Tue, 12 Nov 1996 15:05:51 -0800 (PST) Message-Id: <199611122305.PAA02805@freefall.freebsd.org> To: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) cc: current@freebsd.org, scsi@freebsd.org Subject: Re: SCB paging is most dangerous option now! In-reply-to: Your message of "Tue, 12 Nov 1996 18:41:16 +0300." <199611121541.SAA00746@nagual.ru> Date: Tue, 12 Nov 1996 15:05:48 -0800 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> What were the error messages? >> > >They not stored anywhere now because it seems ANY disk write cause >immediately destruction of inode table including syslog writes. >As I remember there was something like: > >data overrun of XXXX bytes detected > >followed by various retraining/resetting failure attempts. >As I remember no one successfull write's happens. This sounds like a cache coherency bug with your motherboard. What kind is it? The reason I belive this to be the case is that: 1) SCB paging causes the same piece of memory to be DMA'ed in and out in rapid succession - much more often then in the non paging case. The amount of DMA will see a dramatic increase when you switch from 1 to two active targets. 2) After I saw your bug report last night, I again attempted to reproduce the error. I made my 2940 look as much like a 2842 as I could by making the driver believe that it only has 4 SCBs. After about 30 minutes of poinding my two disks with as many as 30 outstanding transactions at a time, I gave up. I will try again tonight with my aic7850 card (3 SCBs) as soon as I can rip the machine apart and rearange my disks. Now I don't have access to a Rev E board anywhere, and the driver does take advantage of undocumented features of that revision of the aic7770. I can send you a little snippet of code that can verify that the 1 important feature, being able to store full 8 bit values in the QIN and QOUTFIFO does work on your card without you having to turn on SCB paging. I don't believe this to be the case since 1 drive would not work at all either. If someone has either a 2742A(T) or 2842A that they'd like to send me, I may be able to debug this further. If it is DMA related, it should be easy to see that by playing with your cache settings and trying to reproduce the problem. If you are going to do this, attempt to repro it *only in single user mode*, with your filesystems mounted read only, by starting multiple processes acessing the disks. I have yet to lose any disk data with this kind of testing, and this will usually fail easily if the problem you are reporting still exists. If the system starts to go south, note what the error messages are and hit the reset button. Multiple dds (at least 8 to each drive) from the raw partitions of your disks to /dev/null will work nicely. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Tue Nov 12 15:20:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA03667 for current-outgoing; Tue, 12 Nov 1996 15:20:51 -0800 (PST) Received: from smily.3skel.com (3skel.com [206.138.212.40]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA03654 for ; Tue, 12 Nov 1996 15:20:33 -0800 (PST) Received: from fnur.3skel.com (root@fnur.3skel.com [192.168.0.8]) by smily.3skel.com (8.8.2/8.8.2) with ESMTP id SAA08947; Tue, 12 Nov 1996 18:20:16 -0500 (EST) Received: (from danj@localhost) by fnur.3skel.com (8.8.2/8.8.2) id SAA25982; Tue, 12 Nov 1996 18:20:09 -0500 (EST) Date: Tue, 12 Nov 1996 18:20:09 -0500 (EST) Message-Id: <199611122320.SAA25982@fnur.3skel.com> From: Dan Janowski To: "Justin T. Gibbs" Cc: freebsd-current@FreeBSD.org Subject: Re: ufs is too slow? In-Reply-To: <199611122025.MAA25041@freefall.freebsd.org> References: <199611122025.MAA25041@freefall.freebsd.org> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Justin T. Gibbs writes: > > The main reason MS is looking to Veritas is that NTFS just doesn't perform > when striped or mirrored. The NOW project at Cal did I/O comparison studies > on x86 platforms using Solaris, FreeBSD, Linux and NT and found that while > FreeBSD and Solaris could achieve upwards of 30MB/s through a striped file > system, NT topped out at around 9MB/s. This was NT3.51 - they may have > improved things for 4.0. where did the Linux ext2fs fall? Dan -- danj@3skel.com Dan Janowski Triskelion Systems, Inc. Bronx, NY From owner-freebsd-current Tue Nov 12 15:28:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA03964 for current-outgoing; Tue, 12 Nov 1996 15:28:57 -0800 (PST) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA03953; Tue, 12 Nov 1996 15:28:51 -0800 (PST) Message-Id: <199611122328.PAA03953@freefall.freebsd.org> To: Dan Janowski cc: freebsd-current@FreeBSD.org Subject: Re: ufs is too slow? In-reply-to: Your message of "Tue, 12 Nov 1996 18:20:09 EST." <199611122320.SAA25982@fnur.3skel.com> Date: Tue, 12 Nov 1996 15:28:48 -0800 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >Justin T. Gibbs writes: > > > > The main reason MS is looking to Veritas is that NTFS just doesn't perform > > when striped or mirrored. The NOW project at Cal did I/O comparison studie >s > > on x86 platforms using Solaris, FreeBSD, Linux and NT and found that while > > FreeBSD and Solaris could achieve upwards of 30MB/s through a striped file > > system, NT topped out at around 9MB/s. This was NT3.51 - they may have > > improved things for 4.0. > >where did the Linux ext2fs fall? Satoshi Asami would be the one to ask. >Dan > >-- >danj@3skel.com >Dan Janowski >Triskelion Systems, Inc. >Bronx, NY -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Tue Nov 12 15:37:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA04507 for current-outgoing; Tue, 12 Nov 1996 15:37:16 -0800 (PST) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA04497 for ; Tue, 12 Nov 1996 15:36:48 -0800 (PST) Received: (from asami@localhost) by vader.cs.berkeley.edu (8.8.2/8.7.3) id PAA14170; Tue, 12 Nov 1996 15:36:39 -0800 (PST) Date: Tue, 12 Nov 1996 15:36:39 -0800 (PST) Message-Id: <199611122336.PAA14170@vader.cs.berkeley.edu> To: danj@3skel.com CC: gibbs@freefall.freebsd.org, freebsd-current@FreeBSD.org In-reply-to: <199611122320.SAA25982@fnur.3skel.com> (message from Dan Janowski on Tue, 12 Nov 1996 18:20:09 -0500 (EST)) Subject: Re: ufs is too slow? From: asami@FreeBSD.org (Satoshi Asami) Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk * Justin T. Gibbs writes: * > * > The main reason MS is looking to Veritas is that NTFS just doesn't perform * > when striped or mirrored. The NOW project at Cal did I/O comparison studies * > on x86 platforms using Solaris, FreeBSD, Linux and NT and found that while * > FreeBSD and Solaris could achieve upwards of 30MB/s through a striped file * > system, NT topped out at around 9MB/s. This was NT3.51 - they may have * > improved things for 4.0. Uh, are you talking about us? ;) Yes, we did, but Solaris didn't perform nearly that well. It was more like 13MB/s. You are right about FreeBSD and Windows NT. * where did the Linux ext2fs fall? It didn't install on our PC with 2940UW. :( (We spent 2 weeks trying to install that crap, ugh.) Satoshi From owner-freebsd-current Tue Nov 12 16:10:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA05863 for current-outgoing; Tue, 12 Nov 1996 16:10:03 -0800 (PST) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA05844; Tue, 12 Nov 1996 16:09:21 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr3-18.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA10750 (5.67b/IDA-1.5); Wed, 13 Nov 1996 01:08:24 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.2/8.6.9) id AAA02103; Wed, 13 Nov 1996 00:54:17 +0100 (MET) Message-Id: <199611122354.AAA02103@x14.mi.uni-koeln.de> Date: Wed, 13 Nov 1996 00:52:57 +0100 From: se@zpr.uni-koeln.de (Stefan Esser) To: asami@FreeBSD.org (Satoshi Asami) Cc: danj@3skel.com, gibbs@freefall.freebsd.org, freebsd-current@FreeBSD.org Subject: Re: ufs is too slow? In-Reply-To: <199611122336.PAA14170@vader.cs.berkeley.edu>; from Satoshi Asami on Nov 12, 1996 15:36:39 -0800 References: <199611122336.PAA14170@vader.cs.berkeley.edu> X-Mailer: Mutt 0.45 Mime-Version: 1.0 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Satoshi Asami writes: > * where did the Linux ext2fs fall? > > It didn't install on our PC with 2940UW. :( (We spent 2 weeks trying > to install that crap, ugh.) Sorry, I already deleted the original message, so I'm replying to this one instead :) I've asked several owners of Linux systems to send Bonnie results, and found that EXT2FS was very much slower than FFS. This lead to the clustering code in Linux being changed, by Gerard Roudier, who had ported the FreeBSD NCR driver to Linux before, and was very disappointed by the lack of file system performance. He acchieved more than a factor of two of improvement on some metrics. The improved clustering plus 4KB allocation blocks (which waste an additional 10% beyond what is reserved to avoid fragmentation) made Linux perform about as good as FreeBSD UFS on all tests except the seek test. The seek values suffered, because of the unconditional read-ahead, if I understand the situation correctly. EXT2FS with 1KB allocation units performs significantly worse than FFS with 4K/512byte. But this is in part due to Bonnie doing 8KB reads, which are very 8K/1K FFS friendly, and still work better given 4KB blocks than 1KB blocks ... (There often was a factor of up to 3 in the rewrite results between Linux and FreeBSD on comparable disk drives, for example. If I remember correctly, the seek rate is now by nearly a factor of 2 lower than before the cluster code changes, and is by about that factor lower than under FreeBSD. But beware of buffer cache effects in that test: Linux tends to use a far higher percentage of memory as a buffer cache!) Linux was unique under Unix operating systems on current hardware in that it was not CPU limited in the "per char" tests (which I use as an estimate of CPU performance on large memory applications :) This was corrected with the new clustering code. I could dig out some numbers from my mail archive, but those are not obtained on recent Linux kernels, and thus are of not too much value anymore (IMHO). Regards, STefan From owner-freebsd-current Tue Nov 12 17:31:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA16678 for current-outgoing; Tue, 12 Nov 1996 17:31:20 -0800 (PST) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA16673; Tue, 12 Nov 1996 17:31:18 -0800 (PST) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.6/8.7.3) with ESMTP id RAA27724; Tue, 12 Nov 1996 17:31:16 -0800 (PST) Message-Id: <199611130131.RAA27724@austin.polstra.com> To: current@freebsd.org Subject: Re: Sup Newsgroups: polstra.freebsd.current In-Reply-To: <15660.847799373@critter.tfs.com> References: <15660.847799373@critter.tfs.com> Organization: Polstra & Co., Seattle, WA Cc: phk@freebsd.org Date: Tue, 12 Nov 1996 17:31:16 -0800 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I belive that we will soon have a "cvsup server kit" available for > people who want to run mirrors for this protocol. Yes, I'm getting fairly close to having this ready. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Tue Nov 12 19:33:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA21844 for current-outgoing; Tue, 12 Nov 1996 19:33:35 -0800 (PST) Received: from wgrobez1.remote.louisville.edu (wgrobez1.remote.louisville.edu [136.165.243.183]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA21838 for ; Tue, 12 Nov 1996 19:33:28 -0800 (PST) Received: from localhost (wangel@localhost) by wgrobez1.remote.louisville.edu (8.7.6/8.6.12) with SMTP id WAA02201 for ; Tue, 12 Nov 1996 22:33:24 -0500 (EST) Date: Tue, 12 Nov 1996 22:33:24 -0500 (EST) From: Gary Roberts To: freebsd-current@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I gotta bring this up :D Has anyone been looking into why the Keyboard spastically locks up? We know there is the 'band-aid'(echo "set ipending=2"|gdb -k -w /kernel /dev/mem)by telnetting into the 'locked' machine by another machine. Not a problem, and it works, but what if people don't have another machine? Just wondering if anyone has concerned fixing this in 3.0 or what a status was? Thanks! Gary Roberts System Admin. -- Altered Reality. http://136.165.243.183 -- Main User Pages From owner-freebsd-current Tue Nov 12 22:50:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA28570 for current-outgoing; Tue, 12 Nov 1996 22:50:52 -0800 (PST) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA28469; Tue, 12 Nov 1996 22:47:11 -0800 (PST) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id WAA11475; Tue, 12 Nov 1996 22:47:17 -0800 (PST) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id WAA08610; Tue, 12 Nov 1996 22:47:02 -0800 (PST) Message-Id: <199611130647.WAA08610@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: "Rodney W. Grimes" cc: scrappy@ki.net, smp@csn.net, smp@freebsd.org, current@freebsd.org Subject: Re: GigaByte GA-586DX-512 Motherboard In-reply-to: Your message of Tue, 12 Nov 96 13:24:27 -0800. <199611122124.NAA17321@GndRsh.aac.dev.com> Date: Tue, 12 Nov 1996 22:47:01 -0800 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> >>I recommend 64meg of parity. Don't really have direct knowledge of EDO vs not. >> > Hrmmm...I had thought that EDO RAM was better because it had >> >'on chip' cache or something like that ... >> Uh, no. EDO RAM simply takes less clock cycles per access than >> standard (or FPM) RAM. >You should go read some technical specifications before you make such >statements. The actual access time changes very very little between >EDO (``Extended Data Out'') and FPM (``Fast Page Mode''). The only >real effective difference is that EDO memory holds it's data outputs [...] No thank you. I have enough to keep me very busy already. I am not a hardware engineer. I understand the _effect_ of running EDO RAM, and that is that cycle times can generally be shorter, in typical modern motherboards. You can argue about the electical intricacies if you want, but I have better things to do. I'm sure you know what you're talking about, and I may get around to looking at this info some time in the future (I am always curious about the intricacies of the hardware, and generally understand it fairly well). But right now, I don't have the time. How am I wrong in stating that "the effect of running EDO RAM in a typical modern motherboard is that you can run with shorter cycle times"? ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-current Tue Nov 12 22:53:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA28634 for current-outgoing; Tue, 12 Nov 1996 22:53:08 -0800 (PST) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA28625 for ; Tue, 12 Nov 1996 22:53:04 -0800 (PST) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id WAA11677; Tue, 12 Nov 1996 22:53:09 -0800 (PST) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id WAA08685; Tue, 12 Nov 1996 22:52:53 -0800 (PST) Message-Id: <199611130652.WAA08685@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: "Justin T. Gibbs" cc: Mark Mayo , Terry Lambert , roberto@keltia.freenix.fr, freebsd-current@freebsd.org Subject: Re: ufs is too slow? In-reply-to: Your message of Tue, 12 Nov 96 12:25:08 -0800. <199611122025.MAA25041@freefall.freebsd.org> Date: Tue, 12 Nov 1996 22:52:44 -0800 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>I just checked, and all they mention in the press_release is that they >>will be using the Veritas Volume Manger - I don't kow if this >>_necessarily_ implies use of the Veritas File sSystem. >The volume manager can work on other FS types too, but according to my friend >that works at Veritas, VxFS will be ported to NT. I'd have to check again >with him to see if they've struck a deal with MS similar to what they have >with other vendors (Sun and HP) where you pay X dollars extra and you get >VxFS in the box. I talked to an engineer in the NT development area (not filesystems, but he's well connected). His comment was basically that NTFS will still be the de-facto FS. If VxFS comes with NT, it will be a supplementary type of deal, and not a replacement for NTFS. Obviously, this is not a statement in any way, shape, or form, that should be taken as "official" from Microsoft. >The main reason MS is looking to Veritas is that NTFS just doesn't perform >when striped or mirrored. The NOW project at Cal did I/O comparison studies >on x86 platforms using Solaris, FreeBSD, Linux and NT and found that while >FreeBSD and Solaris could achieve upwards of 30MB/s through a striped file >system, NT topped out at around 9MB/s. This was NT3.51 - they may have >improved things for 4.0. Several areas of the kernel have improved, performance-wise, in 4.0 (the obvious being the graphics stuff, but also some of the more important areas in multi-processor contention, as well). I don't know if this affects NTFS performance in any substantial way. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-current Tue Nov 12 22:53:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA28700 for current-outgoing; Tue, 12 Nov 1996 22:53:47 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA28686 for ; Tue, 12 Nov 1996 22:53:33 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id HAA15828; Wed, 13 Nov 1996 07:45:44 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.8.2/8.8.2) with SMTP id DAA27570; Wed, 13 Nov 1996 03:44:33 +0100 (MET) Date: Wed, 13 Nov 1996 03:44:33 +0100 (MET) From: Andreas Klemm To: Gary Roberts cc: Mark R V Murray , freebsd-current@freebsd.org Subject: Re: Problem w/ make world In-Reply-To: Message-ID: X-try-apsfilter: ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz X-Fax: +49 2137 2018 X-Phone: +49 2137 2020 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 12 Nov 1996, Gary Roberts wrote: > On Tue, 12 Nov 1996, Mark R V Murray wrote: > > Are you sure you have the complete src/contrib dir - with libgmp? > > M > > > make: don't know how to make > > > /usr/src/gnu/lib/libgmp/../../../contrib/libgmp/mpn > > > /bsd.h. Stop > > > *** Error code 2 > Yah, I got everything?? I'll try to sup again. Especially double check, that your sup-file is up to date and sup's /usr/src/contrib as well ! -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-current Wed Nov 13 00:20:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA02206 for current-outgoing; Wed, 13 Nov 1996 00:20:27 -0800 (PST) Received: from trapdoor.aracnet.com (trapdoor.aracnet.com [204.188.47.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA02198; Wed, 13 Nov 1996 00:20:25 -0800 (PST) Received: from cbrowni2-home (ppp-u20.aracnet.com [204.188.47.149]) by trapdoor.aracnet.com (8.7.4/8.6.9) with SMTP id AAA05424; Wed, 13 Nov 1996 00:13:46 -0800 Message-ID: <3289833E.571F@aracnet.com> Date: Wed, 13 Nov 1996 00:13:50 -0800 From: Chris Browning Reply-To: cbrown@aracnet.com X-Mailer: Mozilla 3.01 (WinNT; U) MIME-Version: 1.0 To: "Michael L. VanLoon -- HeadCandy.com" CC: "Rodney W. Grimes" , scrappy@ki.net, smp@csn.net, smp@freebsd.org, current@freebsd.org Subject: Re: GigaByte GA-586DX-512 Motherboard References: <199611130647.WAA08610@MindBender.serv.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Michael L. VanLoon -- HeadCandy.com wrote: > > >> >>I recommend 64meg of parity. Don't really have direct knowledge of EDO vs not. > > >> > Hrmmm...I had thought that EDO RAM was better because it had > >> >'on chip' cache or something like that ... > > >> Uh, no. EDO RAM simply takes less clock cycles per access than > >> standard (or FPM) RAM. > > >You should go read some technical specifications before you make such > >statements. The actual access time changes very very little between > >EDO (``Extended Data Out'') and FPM (``Fast Page Mode''). The only > >real effective difference is that EDO memory holds it's data outputs > [...] > > No thank you. I have enough to keep me very busy already. > > I am not a hardware engineer. I understand the _effect_ of running > EDO RAM, and that is that cycle times can generally be shorter, in > typical modern motherboards. > > You can argue about the electical intricacies if you want, but I have > better things to do. I'm sure you know what you're talking about, and > I may get around to looking at this info some time in the future (I am > always curious about the intricacies of the hardware, and generally > understand it fairly well). But right now, I don't have the time. > > How am I wrong in stating that "the effect of running EDO RAM in a > typical modern motherboard is that you can run with shorter cycle > times"? Ok, I will try to answer this. I recommend that we take any future replies off the list. What the previous gentleman was telling you is correct. Both of your statements are incorrect. The cycle time and # of clock cycles to access EDO and FP RAM is approximately the same. Maybe there is confusion here because you are using some very specific terms used to spec memory but I don't think that is what you are intending to say. The cycle time of memory is how fast you can access the same cell of memory sequentially. This is pretty much the same for EDO & FP. The number of clocks that it takes to access memory will be about the same for EDO & FP. Both of these items are determined by the technology used to implement the chips on the S(D)IMMS, which will be the same for both EDO & FP. Both of these really don't talk about the differences between EDO and FP. What makes EDO RAM attractive is the fact that once you have paid the penality to get to memory, you can get a whole row without much additional overhead. This is a kind of "bursting", if you will. This way, if you are getting a lot of sequential bytes, then you pay one large delay to get to memory and a small subsequent delay to get to the adjacent bytes. With FP, on the other hand, you would incur the same large delay to get all the bytes (assuming no interleaving). Unfortunately, some of the advantage of EDO is hidden by the cache. If you have to go to memory, the processor will get the byte (word, etc) that it wanted and the EDO fill will all go to the cache. This makes for faster cache fills, but the processor didn't really see any of the advantage. Well, I hope this help. Again, lets take this off the list. Thanks, Chris From owner-freebsd-current Wed Nov 13 02:16:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA06480 for current-outgoing; Wed, 13 Nov 1996 02:16:08 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA06467 for ; Wed, 13 Nov 1996 02:16:02 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.2/8.6.9) with ESMTP id CAA16291; Wed, 13 Nov 1996 02:14:51 -0800 (PST) To: Gary Roberts cc: freebsd-current@FreeBSD.org In-reply-to: Your message of "Tue, 12 Nov 1996 22:33:24 EST." Date: Wed, 13 Nov 1996 02:14:51 -0800 Message-ID: <16289.847880091@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Has anyone been looking into why the Keyboard spastically locks up? We > know there is the 'band-aid'(echo "set ipending=2"|gdb -k -w /kernel > /dev/mem)by telnetting into the 'locked' machine by another machine. Not > a problem, and it works, but what if people don't have another machine? That's been fixed in -current with Soren's latest syscons changes. Jordan From owner-freebsd-current Wed Nov 13 04:19:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA12481 for current-outgoing; Wed, 13 Nov 1996 04:19:33 -0800 (PST) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA12476 for ; Wed, 13 Nov 1996 04:19:12 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id NAA29538 for ; Wed, 13 Nov 1996 13:19:51 +0100 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id NAA02642 for freebsd-current@freefall.cdrom.com; Wed, 13 Nov 1996 13:29:59 +0100 Date: Wed, 13 Nov 1996 13:29:59 +0100 From: Christoph Kukulies Message-Id: <199611131229.NAA02642@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.FreeBSD.org Subject: aic0/ed0 problem Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I still have a strange interaction between a ed0 (WD8013EPC/16bit) and a board which calls AVA 1505 Total CD Kit (Adaptec Altra (tm) Line) The board is recognized a an aic0 and it recognizes the HP DAT drive I've attached to it even fine. But it somehow interacts badly with ed0 (I have ed0 and ed1 in that machine both being a WD8013EPC). This is my config: # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # $Id: GENERIC,v 1.46.2.6 1995/10/25 17:29:51 jkh Exp $ # machine "i386" cpu "I486_CPU" ident CGATE maxusers 64 options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 options "SCSI_DELAY=0" #Be pessimistic about Joe SCSI device options BOUNCE_BUFFERS #include support for DMA bounce buffers options UCONSOLE #Allow users to grab the console options MROUTING #Allow MCAST options USERCONFIG options SYSVSHM options SYSVSEM options SYSVMSG config kernel root on wd0 controller isa0 controller aic0 at isa? port 0x140 bio irq 11 vector aicintr controller scbus0 at aic0 disk sd0 device st0 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 controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device lpt0 at isa? port? tty irq 7 vector lptintr # 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. #ed0 at 0x300-0x31f irq 10 maddr 0xcc000 msize 16384 on isa #ed0: address 00:00:c0:50:8f:67, type WD8013EPC (16 bit) #ed1 at 0x280-0x29f irq 3 maddr 0xd8000 msize 16384 on isa #ed1: address 00:00:c0:12:3b:2e, type WD8013EPC (16 bit) device ed0 at isa? port 0x300 net irq 10 iomem 0xcc000 vector edintr device ed1 at isa? port 0x280 net irq 3 iomem 0xd8000 vector edintr pseudo-device loop pseudo-device ether pseudo-device log # ijppp uses tun instead of ppp device #pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 32 pseudo-device gzip # Exec gzipped a.out's MB is a ISA/VL board with only ISA devices attached. The Adaptec SCSI board doesn't have a BIOS ROM on it though there are PC board locations for this but the decoding logic isn't populated either so I don't think the cc000 range is decoded. The effect is that ed0 always sends 'ed0 timeout' messages while ed1 is still functioning. I cannot ping into the network, ed0 is attached to while the network on ed1 works fine. The Adaptec board is definitely strapped to IRQ 11. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Wed Nov 13 04:30:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA12987 for current-outgoing; Wed, 13 Nov 1996 04:30:29 -0800 (PST) Received: from answerman.mindspring.com (answerman.mindspring.com [204.180.128.8]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA12980 for ; Wed, 13 Nov 1996 04:30:25 -0800 (PST) Received: from rlb.users.mindspring.com (user-168-121-25-139.dialup.mindspring.com [168.121.25.139]) by answerman.mindspring.com (8.7.5/8.7.3) with SMTP id HAA19919 for ; Wed, 13 Nov 1996 07:42:34 -0500 (EST) Message-ID: <3289BF79.167EB0E7@mindspring.com> Date: Wed, 13 Nov 1996 07:30:49 -0500 From: Ron Bolin X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Kernel Build Failes on locore.s Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is there a fix for this? I just cvsup'd today and can't build the kernel now. e -DAPM_BROKEN_STATCLOCK -DFAILSAFE -DCOMPAT_43 -DCD9660 -DMSDOSFS -DNFS -DFFS - DINET -DI586_OPTIMIZED_BZERO -DI586_OPTIMIZED_BCOPY -DI586_FAST_BCOPY -DKERNEL . ./../i386/i386/locore.s ../../i386/i386/locore.s: Assembler messages: ../../i386/i386/locore.s:705: Error: bad register name ('%cr4') ../../i386/i386/locore.s:707: Error: bad register name ('%cr4') *** Error code 1 -- **************************************************************************** Ron Bolin rlb@mindspring.com, http://www.mindspring.com/~rlb/ GSU: gs01rlb@panther.gsu.edu matrlbx@indigo4.cs.gsu.edu Home: 770-992-8877 **************************************************************************** From owner-freebsd-current Wed Nov 13 04:51:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA14470 for current-outgoing; Wed, 13 Nov 1996 04:51:37 -0800 (PST) Received: from dyson.iquest.net ([198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA14458 for ; Wed, 13 Nov 1996 04:51:35 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id HAA00673; Wed, 13 Nov 1996 07:51:29 -0500 (EST) From: "John S. Dyson" Message-Id: <199611131251.HAA00673@dyson.iquest.net> Subject: Re: Kernel Build Failes on locore.s To: rlb@mindspring.com (Ron Bolin) Date: Wed, 13 Nov 1996 07:51:28 -0500 (EST) Cc: freebsd-current@freebsd.org In-Reply-To: <3289BF79.167EB0E7@mindspring.com> from "Ron Bolin" at Nov 13, 96 07:30:49 am Reply-To: dyson@freebsd.org X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Is there a fix for this? I just cvsup'd today and can't build the kernel > now. > > e -DAPM_BROKEN_STATCLOCK -DFAILSAFE -DCOMPAT_43 -DCD9660 -DMSDOSFS -DNFS > -DFFS - > DINET -DI586_OPTIMIZED_BZERO -DI586_OPTIMIZED_BCOPY -DI586_FAST_BCOPY > -DKERNEL . > ./../i386/i386/locore.s > ../../i386/i386/locore.s: Assembler messages: > ../../i386/i386/locore.s:705: Error: bad register name ('%cr4') > ../../i386/i386/locore.s:707: Error: bad register name ('%cr4') > *** Error code 1 > cvsup and build the assembler. From owner-freebsd-current Wed Nov 13 05:04:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA15284 for current-outgoing; Wed, 13 Nov 1996 05:04:27 -0800 (PST) Received: from friley216.res.iastate.edu (friley216.res.iastate.edu [129.186.78.216]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA15276 for ; Wed, 13 Nov 1996 05:04:23 -0800 (PST) Received: from friley216.res.iastate.edu (loopback [127.0.0.1]) by friley216.res.iastate.edu (8.7.6/8.7.3) with ESMTP id HAA03822; Wed, 13 Nov 1996 07:04:19 -0600 (CST) Message-Id: <199611131304.HAA03822@friley216.res.iastate.edu> X-Mailer: exmh version 1.6.9 8/22/96 To: Ron Bolin cc: freebsd-current@freebsd.org Subject: Re: Kernel Build Failes on locore.s In-reply-to: Your message of Wed, 13 Nov 1996 07:30:49 -0500. <3289BF79.167EB0E7@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Nov 1996 07:04:19 -0600 From: Chris Csanady Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Is there a fix for this? I just cvsup'd today and can't build the kernel >now. I believe it was mentioned recently that some changes were made gas. Recompile gas, and it should work... --Chris Csanady >e -DAPM_BROKEN_STATCLOCK -DFAILSAFE -DCOMPAT_43 -DCD9660 -DMSDOSFS -DNFS >-DFFS - >DINET -DI586_OPTIMIZED_BZERO -DI586_OPTIMIZED_BCOPY -DI586_FAST_BCOPY >-DKERNEL . >./../i386/i386/locore.s >../../i386/i386/locore.s: Assembler messages: >../../i386/i386/locore.s:705: Error: bad register name ('%cr4') >../../i386/i386/locore.s:707: Error: bad register name ('%cr4') >*** Error code 1 > >-- >**************************************************************************** >Ron Bolin rlb@mindspring.com, http://www.mindspring.com/~rlb/ >GSU: gs01rlb@panther.gsu.edu matrlbx@indigo4.cs.gsu.edu Home: >770-992-8877 >**************************************************************************** From owner-freebsd-current Wed Nov 13 05:15:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA15589 for current-outgoing; Wed, 13 Nov 1996 05:15:23 -0800 (PST) Received: from friley216.res.iastate.edu (friley216.res.iastate.edu [129.186.78.216]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA15582; Wed, 13 Nov 1996 05:15:21 -0800 (PST) Received: from friley216.res.iastate.edu (loopback [127.0.0.1]) by friley216.res.iastate.edu (8.7.6/8.7.3) with ESMTP id HAA03860; Wed, 13 Nov 1996 07:15:19 -0600 (CST) Message-Id: <199611131315.HAA03860@friley216.res.iastate.edu> X-Mailer: exmh version 1.6.9 8/22/96 To: dyson@FreeBSD.org cc: gibbs@freefall.freebsd.org (Justin T. Gibbs), roberto@keltia.freenix.fr, freebsd-current@FreeBSD.org Subject: pbufs (was: Re: ufs is too slow?) In-reply-to: Your message of Mon, 11 Nov 1996 23:22:28 -0500. <199611120422.XAA03836@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Nov 1996 07:15:18 -0600 From: Chris Csanady Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> >> Yes, please get rid of the locked buffer stuff. That code is EVIL. >> >> BTW,do you have any plans for removing the 64k I/O limitation? It sorta >> sucks when you want to write a 1meg segment to have to cut it up into such >> small pieces. >> >You have always hated that!!! I plan to do something to create alternate >mappings: segments. Segments will probably use a yet to be enhanced >VM/Buffer cache pbuf mechanism (not to be confused with VJ's networking VJ's pbufs? ive not heard of these before, what are they? i remember hearing something about him rewriting the tcp/ip stack to work well on gigabit networks... this wouldnt have anything to do with it, would it? probably not i suppose, but if anyone could point me to papers on anything related, id apreciate it. :) Chris Csanady >pbufs.) There will be no 64K limitation as such. I am still listening >to "bright ideas" though :-). > >John > From owner-freebsd-current Wed Nov 13 05:56:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA17718 for current-outgoing; Wed, 13 Nov 1996 05:56:03 -0800 (PST) Received: from wgrobez1.remote.louisville.edu (wgrobez1.remote.louisville.edu [136.165.243.183]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA17697 for ; Wed, 13 Nov 1996 05:55:59 -0800 (PST) Received: from localhost (wangel@localhost) by wgrobez1.remote.louisville.edu (8.7.6/8.6.12) with SMTP id IAA17027; Wed, 13 Nov 1996 08:55:46 -0500 (EST) Date: Wed, 13 Nov 1996 08:55:46 -0500 (EST) From: Gary Roberts To: "Jordan K. Hubbard" cc: freebsd-current@FreeBSD.org Subject: Re: your mail In-Reply-To: <16289.847880091@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 13 Nov 1996, Jordan K. Hubbard wrote: > > Has anyone been looking into why the Keyboard spastically locks up? We > > know there is the 'band-aid'(echo "set ipending=2"|gdb -k -w /kernel > > /dev/mem)by telnetting into the 'locked' machine by another machine. Not > > a problem, and it works, but what if people don't have another machine? > > That's been fixed in -current with Soren's latest syscons changes. > > Jordan > Wow ... Show's how much I've been paying attention :D Gary Roberts System Admin. -- Altered Reality. http://136.165.243.183 -- Main User Pages From owner-freebsd-current Wed Nov 13 06:11:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA18526 for current-outgoing; Wed, 13 Nov 1996 06:11:20 -0800 (PST) Received: from bbs.mpcs.com (hgoldste@bbs.mpcs.com [204.215.226.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA18517 for ; Wed, 13 Nov 1996 06:11:14 -0800 (PST) Received: (from hgoldste@localhost) by bbs.mpcs.com (8.8.2/8.8.2/MPCS) id JAA30752; Wed, 13 Nov 1996 09:10:59 -0500 Date: Wed, 13 Nov 1996 09:10:59 -0500 From: Howard Goldstein Message-Id: <199611131410.JAA30752@bbs.mpcs.com> To: freebsd-current@freebsd.org Cc: terry@lambert.org Subject: Re: ufs is too slow? In-Reply-To: <199611120120.SAA19129@phaeton.artisoft.com> Reply-To: hgoldste@bbs.mpcs.com Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199611120120.SAA19129@phaeton.artisoft.com>, Terry Lambert wrote: : Again, news articles are created, written only once, and not updated; : there's really no reason to get more complex on a "newsfs" than doing : what you can to speed up indexing, etc.. And that can be just as easily : laid on *top* of *any* FS -- after all, the indices won't change : significantly either, if they have correct organizing principles, since : the data they refer to is invariant until expiration or creation. The only catch is with regard to overview files, one per newsgroup, to which per-article header data are appended. Whether or not it's a large catch in the discussion about what I call an "expfs", an expendable filesystem with a care-less (careless) attitude towards integrity, I do not know. -- Howard Goldstein From owner-freebsd-current Wed Nov 13 06:31:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA19266 for current-outgoing; Wed, 13 Nov 1996 06:31:59 -0800 (PST) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA19261 for ; Wed, 13 Nov 1996 06:31:50 -0800 (PST) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id IAA23176; Wed, 13 Nov 1996 08:31:16 -0600 From: Joe Greco Message-Id: <199611131431.IAA23176@brasil.moneng.mei.com> Subject: Re: ufs is too slow? To: hgoldste@bbs.mpcs.com Date: Wed, 13 Nov 1996 08:31:16 -0600 (CST) Cc: freebsd-current@freebsd.org, terry@lambert.org In-Reply-To: <199611131410.JAA30752@bbs.mpcs.com> from "Howard Goldstein" at Nov 13, 96 09:10:59 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > In article <199611120120.SAA19129@phaeton.artisoft.com>, Terry Lambert wrote: > : Again, news articles are created, written only once, and not updated; > : there's really no reason to get more complex on a "newsfs" than doing > : what you can to speed up indexing, etc.. And that can be just as easily > : laid on *top* of *any* FS -- after all, the indices won't change > : significantly either, if they have correct organizing principles, since > : the data they refer to is invariant until expiration or creation. > > The only catch is with regard to overview files, one per newsgroup, to > which per-article header data are appended. Whether or not it's a > large catch in the discussion about what I call an "expfs", an > expendable filesystem with a care-less (careless) attitude towards > integrity, I do not know. Who is saying that you need to use the same type of filesystem to store the overview files? I see no reason to switch from FFS for those, or for /usr/local, /var, etc. ... JG From owner-freebsd-current Wed Nov 13 07:10:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA21698 for current-outgoing; Wed, 13 Nov 1996 07:10:08 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA21691 for ; Wed, 13 Nov 1996 07:10:03 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id IAA00027; Wed, 13 Nov 1996 08:09:53 -0700 (MST) Date: Wed, 13 Nov 1996 08:09:53 -0700 (MST) Message-Id: <199611131509.IAA00027@rocky.mt.sri.com> From: Nate Williams To: "Jordan K. Hubbard" Cc: Gary Roberts , freebsd-current@freebsd.org In-Reply-To: <16289.847880091@time.cdrom.com> References: <16289.847880091@time.cdrom.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Has anyone been looking into why the Keyboard spastically locks up? We > > know there is the 'band-aid'(echo "set ipending=2"|gdb -k -w /kernel > > /dev/mem)by telnetting into the 'locked' machine by another machine. Not > > a problem, and it works, but what if people don't have another machine? > > That's been fixed in -current with Soren's latest syscons changes. The fix also broke PS/2 mouse support. :( :( Nate From owner-freebsd-current Wed Nov 13 07:43:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA24596 for current-outgoing; Wed, 13 Nov 1996 07:43:26 -0800 (PST) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA24563; Wed, 13 Nov 1996 07:42:38 -0800 (PST) Received: by sovcom.kiae.su id AA15233 (5.65.kiae-1 ); Wed, 13 Nov 1996 18:35:54 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Wed, 13 Nov 96 18:35:54 +0300 Received: (from ache@localhost) by nagual.ru (8.8.2/8.8.2) id SAA00239; Wed, 13 Nov 1996 18:34:26 +0300 (MSK) Message-Id: <199611131534.SAA00239@nagual.ru> Subject: Re: SCB paging is most dangerous option now! In-Reply-To: <199611122305.PAA02805@freefall.freebsd.org> from "Justin T. Gibbs" at "Nov 12, 96 03:05:48 pm" To: gibbs@freefall.freebsd.org (Justin T. Gibbs) Date: Wed, 13 Nov 1996 18:34:25 +0300 (MSK) Cc: current@freebsd.org, scsi@freebsd.org From: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) Organization: self X-Class: Fast X-Mailer: ELM [version 2.4ME+ PL28 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > This sounds like a cache coherency bug with your motherboard. What kind > is it? OPTI895 VL/ISA-PB486P3 > 2) After I saw your bug report last night, I again attempted to reproduce > the error. I made my 2940 look as much like a 2842 as I could by making > the driver believe that it only has 4 SCBs. After about 30 minutes of > poinding my two disks with as many as 30 outstanding transactions at a > time, I gave up. I will try again tonight with my aic7850 card (3 SCBs) > as soon as I can rip the machine apart and rearange my disks. I don't even wait a minutes, I got inodes wipe on very _first_ write immediately. > If it is DMA related, it should be easy to see that by playing with your > cache settings and trying to reproduce the problem. If you are going to do > this, attempt to repro it *only in single user mode*, with your filesystems > mounted read only, by starting multiple processes acessing the disks. I > have yet to lose any disk data with this kind of testing, and this will > usually fail easily if the problem you are reporting still exists. If the > system starts to go south, note what the error messages are and hit the > reset button. Multiple dds (at least 8 to each drive) from the raw > partitions of your disks to /dev/null will work nicely. I read only mode I got the almost same result with SCB paging as without it. This bug affects _writing_only_, not reading. And I can't start 8 dds for each drive in both modes, 3 dds per drive is enough to cause "Queue Full" in both modes, but it is harmless due to read only. If I increase dds count, I got "timed out in dataout phase" for SCB mode or "timed out in message out phase" for non-SCB mode. -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Wed Nov 13 08:06:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA25512 for current-outgoing; Wed, 13 Nov 1996 08:06:17 -0800 (PST) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA25507; Wed, 13 Nov 1996 08:06:12 -0800 (PST) Message-Id: <199611131606.IAA25507@freefall.freebsd.org> To: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) cc: current@freebsd.org, scsi@freebsd.org Subject: Re: SCB paging is most dangerous option now! In-reply-to: Your message of "Wed, 13 Nov 1996 18:34:25 +0300." <199611131534.SAA00239@nagual.ru> Date: Wed, 13 Nov 1996 08:06:10 -0800 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I read only mode I got the almost same result with SCB paging as without it. >This bug affects _writing_only_, not reading. >And I can't start 8 dds for each drive in both modes, >3 dds per drive is enough to cause "Queue Full" in both modes, but >it is harmless due to read only. This is probably what is causing your corruption in the SCB Paging case. Which drive can only do 3 transactions at a time? I'm sure that your IBM can do more. It may very well be that one of your drives doesn't like the fact that the code with SCB paging turned on will basically continually pound on that drive, causing queue full conditions, until there aren't enough transactions queued to make this happen any more. The patch I posted for Andreas' problem may help in this regard. As for your problem happening on the "first write", are you sure this isn't the "first sync" after boot?? >If I increase dds count, I got "timed out in dataout phase" for SCB mode or >"timed out in message out phase" for non-SCB mode. That dataout phase one could actually be "while idle". I just found a bug in the diagnostic code that reports that. Hmmm. >-- >Andrey A. Chernov > >http://www.nagual.ru/~ache/ -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Wed Nov 13 08:22:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA26456 for current-outgoing; Wed, 13 Nov 1996 08:22:57 -0800 (PST) Received: from premise.CS.Berkeley.EDU (root@premise.CS.Berkeley.EDU [128.32.33.172]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA26440; Wed, 13 Nov 1996 08:22:39 -0800 (PST) Received: from premise.CS.Berkeley.EDU (bmah@localhost.Berkeley.EDU [127.0.0.1]) by premise.CS.Berkeley.EDU (8.8.2/8.8.2) with ESMTP id IAA03524; Wed, 13 Nov 1996 08:22:30 -0800 (PST) Message-Id: <199611131622.IAA03524@premise.CS.Berkeley.EDU> X-Mailer: exmh version 1.6.9 8/22/96 To: Chris Csanady cc: dyson@freebsd.org, gibbs@freefall.freebsd.org (Justin T. Gibbs), roberto@keltia.freenix.fr, freebsd-current@freebsd.org Subject: Re: pbufs (was: Re: ufs is too slow?) In-reply-to: Your message of "Wed, 13 Nov 1996 07:15:18 CST." <199611131315.HAA03860@friley216.res.iastate.edu> From: bmah@cs.berkeley.edu (Bruce A. Mah) Reply-to: bmah@cs.berkeley.edu X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Nov 1996 08:22:26 -0800 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Chris Csanady writes: > VJ's pbufs? ive not heard of these before, what are they? i remember hearin > g > something about him rewriting the tcp/ip stack to work well on gigabit > networks... this wouldnt have anything to do with it, would it? probably > not i suppose, but if anyone could point me to papers on anything related, id > apreciate it. :) I don't think Van has written any papers, but he's given a few talks on it. Going largely from memory: One of the losses of the current BSD TCP/IP implementation is that the unit of memory allocation (mbufs) doesn't really match the unit of network transmission. You'd like to allocate memory in packet- (or frame-) sized chunks, e.g. ~1500 bytes for Ethernet, rather than small mbufs (~112 bytes) or page mbufs (4K) which require a lot of copying and munging around of data. So the idea behind pbufs is that the lower protocol layers expose enough details to higher layers (e.g. the socket layer and TCP) to make this feasible. This also dovetails rather nicely with some assertions he's made about putting memory on network interfaces and mapping them into kernel memory (e.g. using the card's memory as socket/protocol buffers). One example of this is the Medusa/Afterburner series of high-speed network interfaces from HP/HP Labs. (Editorial note: Packet traces have shown that many packets, at least on LANs, tend to be small. So it's not clear to me what effect this would have for "typical" network traffic, though the wins for large bulk transfers have shown to be substantial.) Some of the other modifications also streamlined the protocol processing by combining layers (in the implementation, not protocol design). By doing several layers at once you can save overhead. Layering is great when designing a protocol stack, but many times not so great when you go to build something. Somewhere in the mess I call a desk I think I have hardcopies from a talk he gave on this stuff at a Gigabit TCP workshop a few years ago, but a cursory search has not revealed it. Bruce. From owner-freebsd-current Wed Nov 13 08:58:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA28086 for current-outgoing; Wed, 13 Nov 1996 08:58:17 -0800 (PST) Received: from ravenock.cybercity.dk (disn34.cybercity.dk [194.16.57.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA28070 for ; Wed, 13 Nov 1996 08:58:05 -0800 (PST) Received: (from sos@localhost) by ravenock.cybercity.dk (8.8.2/8.7.3) id RAA16645; Wed, 13 Nov 1996 17:55:51 +0100 (MET) Message-Id: <199611131655.RAA16645@ravenock.cybercity.dk> Subject: Re: your mail To: nate@mt.sri.com (Nate Williams) Date: Wed, 13 Nov 1996 17:55:40 +0100 (MET) From: "Soren Schmidt" Cc: jkh@time.cdrom.com, wangel@wgrobez1.remote.louisville.edu, freebsd-current@FreeBSD.org In-Reply-To: <199611131509.IAA00027@rocky.mt.sri.com> from "Nate Williams" at Nov 13, 96 08:09:53 am From: sos@FreeBSD.org Reply-to: sos@FreeBSD.org X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In reply to Nate Williams who wrote: > > > > > Has anyone been looking into why the Keyboard spastically locks up? We > > > know there is the 'band-aid'(echo "set ipending=2"|gdb -k -w /kernel > > > /dev/mem)by telnetting into the 'locked' machine by another machine. Not > > > a problem, and it works, but what if people don't have another machine? > > > > That's been fixed in -current with Soren's latest syscons changes. > > The fix also broke PS/2 mouse support. :( :( I know :(, but so long as we occasionally looses an interrupt, there is not much else to do. Or merge syscons and the ps/2 mousedriver. (which I have on my TODO list) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-current Wed Nov 13 09:13:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA28982 for current-outgoing; Wed, 13 Nov 1996 09:13:41 -0800 (PST) Received: from verdi.nethelp.no (verdi.nethelp.no [193.91.212.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA28968 for ; Wed, 13 Nov 1996 09:13:34 -0800 (PST) From: sthaug@nethelp.no Received: (qmail 22585 invoked by uid 1001); 13 Nov 1996 17:13:18 +0000 (GMT) To: bmah@cs.berkeley.edu Cc: ccsanady@friley216.res.iastate.edu, dyson@FreeBSD.org, gibbs@freefall.freebsd.org, roberto@keltia.freenix.fr, freebsd-current@FreeBSD.org Subject: Re: pbufs (was: Re: ufs is too slow?) In-Reply-To: Your message of "Wed, 13 Nov 1996 08:22:26 -0800" References: <199611131622.IAA03524@premise.CS.Berkeley.EDU> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Date: Wed, 13 Nov 1996 18:13:18 +0100 Message-ID: <22583.847905198@verdi.nethelp.no> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > (Editorial note: Packet traces have shown that many packets, at least on > LANs, tend to be small. So it's not clear to me what effect this would have > for "typical" network traffic, though the wins for large bulk transfers have > shown to be substantial.) It's also likely to help *latency* for smaller packets quite a bit. > Somewhere in the mess I call a desk I think I have hardcopies from a talk he > gave on this stuff at a Gigabit TCP workshop a few years ago, but a cursory > search has not revealed it. See http://ee.lbl.gov/nrg-talks.html In particular, the 1992 talk "Design Changes to the Kernel Network Architecture for 4.4BSD", and the 1993 talk "Some Design Issues for High-speed Networks". Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-current Wed Nov 13 09:31:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA29754 for current-outgoing; Wed, 13 Nov 1996 09:31:08 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA29746; Wed, 13 Nov 1996 09:31:01 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA00439; Wed, 13 Nov 1996 10:30:43 -0700 (MST) Date: Wed, 13 Nov 1996 10:30:43 -0700 (MST) Message-Id: <199611131730.KAA00439@rocky.mt.sri.com> From: Nate Williams To: sos@freebsd.org Cc: nate@mt.sri.com (Nate Williams), jkh@time.cdrom.com, wangel@wgrobez1.remote.louisville.edu, freebsd-current@freebsd.org Subject: Re: your mail In-Reply-To: <199611131655.RAA16645@ravenock.cybercity.dk> References: <199611131509.IAA00027@rocky.mt.sri.com> <199611131655.RAA16645@ravenock.cybercity.dk> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > > Has anyone been looking into why the Keyboard spastically locks up? We > > > > know there is the 'band-aid'(echo "set ipending=2"|gdb -k -w /kernel > > > > /dev/mem)by telnetting into the 'locked' machine by another machine. Not > > > > a problem, and it works, but what if people don't have another machine? > > > > > > That's been fixed in -current with Soren's latest syscons changes. > > > > The fix also broke PS/2 mouse support. :( :( > > I know :(, but so long as we occasionally looses an interrupt, there > is not much else to do. Or merge syscons and the ps/2 mousedriver. > (which I have on my TODO list) Are we losing interrupts, or is there something else going on? Also, I just spoke with someone (the recent psm.c author) who is willing to do the work to integrate the two, so hopefully you two can resolve this. Nate From owner-freebsd-current Wed Nov 13 09:42:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA00699 for current-outgoing; Wed, 13 Nov 1996 09:42:19 -0800 (PST) Received: from white.dogwood.com (dave@white.dogwood.com [140.174.96.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA00694 for ; Wed, 13 Nov 1996 09:42:13 -0800 (PST) Received: (from dave@localhost) by white.dogwood.com (8.8.2/8.8.2) id JAA19573 for freebsd-current@freebsd.org; Wed, 13 Nov 1996 09:42:03 -0800 (PST) From: Dave Cornejo Message-Id: <199611131742.JAA19573@white.dogwood.com> Subject: make world on read only filesystem To: freebsd-current@freebsd.org Date: Wed, 13 Nov 1996 09:42:03 -0800 (PST) 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have noticed a problem in 'make world' on a read-only /usr/src: 'make bootstrap' rebuilds lex with the command: make -DNOMAN -DNOPROFILE -DNOLIB all install cleandir obj the problem is that cleandir removes /usr/obj/usr/src/usr.bin/lex/lib, (via an rm -rf) ignoring the -DNOLIB while the obj heeds it and doesn't actually remake .../lex/lib. This sets up the problem later in make lib-tools where there is no obj directory for the lex library - so it tries to build it in place. The read-only status keeps this from working very well... I can see two ways of fixing this: do a make obj in the lex/lib dir before you try to rebuild lex in make lib-tools, or possibly just change the rm -rf in make cleandir to just rm -f Should/can it be possible to do what I am trying to do here? If so, what is the correct or most correct way to get past this? -- Dave Cornejo - Dogwood Media, Fremont, California From owner-freebsd-current Wed Nov 13 10:04:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA02382 for current-outgoing; Wed, 13 Nov 1996 10:04:21 -0800 (PST) Received: from premise.CS.Berkeley.EDU (root@premise.CS.Berkeley.EDU [128.32.33.172]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA02371; Wed, 13 Nov 1996 10:04:14 -0800 (PST) Received: from premise.CS.Berkeley.EDU (bmah@localhost.Berkeley.EDU [127.0.0.1]) by premise.CS.Berkeley.EDU (8.8.2/8.8.2) with ESMTP id KAA04201; Wed, 13 Nov 1996 10:03:52 -0800 (PST) Message-Id: <199611131803.KAA04201@premise.CS.Berkeley.EDU> X-Mailer: exmh version 1.6.9 8/22/96 To: sthaug@nethelp.no cc: bmah@cs.berkeley.edu, ccsanady@friley216.res.iastate.edu, dyson@freebsd.org, gibbs@freefall.freebsd.org, roberto@keltia.freenix.fr, freebsd-current@freebsd.org Subject: Re: pbufs (was: Re: ufs is too slow?) In-reply-to: Your message of "Wed, 13 Nov 1996 18:13:18 +0100." <22583.847905198@verdi.nethelp.no> From: bmah@cs.berkeley.edu (Bruce A. Mah) Reply-to: bmah@cs.berkeley.edu X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Nov 1996 10:03:44 -0800 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk sthaug@nethelp.no writes: > > (Editorial note: Packet traces have shown that many packets, at least on > > LANs, tend to be small. So it's not clear to me what effect this would hav > e > > for "typical" network traffic, though the wins for large bulk transfers hav > e > > shown to be substantial.) > > It's also likely to help *latency* for smaller packets quite a bit. I agree that Van's proposed changes to packet processing will improve latency, but it is not at all obvious how the changes to *buffer allocation* would affect latency. Sorry if I was unclear on what "this" meant in my note. > See http://ee.lbl.gov/nrg-talks.html > > In particular, the 1992 talk "Design Changes to the Kernel Network > Architecture for 4.4BSD", and the 1993 talk "Some Design Issues for > High-speed Networks". Thanks for the pointer. Cheers, Bruce. From owner-freebsd-current Wed Nov 13 10:06:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA02591 for current-outgoing; Wed, 13 Nov 1996 10:06:26 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA02584 for ; Wed, 13 Nov 1996 10:06:22 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id FAA11738; Thu, 14 Nov 1996 05:04:36 +1100 Date: Thu, 14 Nov 1996 05:04:36 +1100 From: Bruce Evans Message-Id: <199611131804.FAA11738@godzilla.zeta.org.au> To: nate@mt.sri.com, sos@ravenock.cybercity.dk Subject: Re: your mail Cc: freebsd-current@FreeBSD.org, jkh@time.cdrom.com, wangel@wgrobez1.remote.louisville.edu Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> The fix also broke PS/2 mouse support. :( :( > >I know :(, but so long as we occasionally looses an interrupt, there >is not much else to do. Or merge syscons and the ps/2 mousedriver. Lots can be done: - back out fix OR - poll less often (fixed period) OR - poll less often (after keyboard has been inactice for a while) OR - make fix a compile time option OR - make fix a run time option OR - check for psm interrupt and don't poll keyboard if one is pending OR ... Bruce From owner-freebsd-current Wed Nov 13 10:17:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA03546 for current-outgoing; Wed, 13 Nov 1996 10:17:07 -0800 (PST) Received: from ravenock.cybercity.dk (disn48.cybercity.dk [194.16.57.48]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA03541; Wed, 13 Nov 1996 10:17:00 -0800 (PST) Received: (from sos@localhost) by ravenock.cybercity.dk (8.8.2/8.7.3) id TAA16764; Wed, 13 Nov 1996 19:18:13 +0100 (MET) Message-Id: <199611131818.TAA16764@ravenock.cybercity.dk> Subject: Re: your mail To: nate@mt.sri.com (Nate Williams) Date: Wed, 13 Nov 1996 19:18:00 +0100 (MET) From: "Soren Schmidt" Cc: sos@FreeBSD.org, nate@mt.sri.com, jkh@time.cdrom.com, wangel@wgrobez1.remote.louisville.edu, freebsd-current@FreeBSD.org In-Reply-To: <199611131730.KAA00439@rocky.mt.sri.com> from "Nate Williams" at Nov 13, 96 10:30:43 am From: sos@FreeBSD.org Reply-to: sos@FreeBSD.org X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In reply to Nate Williams who wrote: > > > > > > > Has anyone been looking into why the Keyboard spastically locks up? We > > > > > know there is the 'band-aid'(echo "set ipending=2"|gdb -k -w /kernel > > > > > /dev/mem)by telnetting into the 'locked' machine by another machine. Not > > > > > a problem, and it works, but what if people don't have another machine? > > > > > > > > That's been fixed in -current with Soren's latest syscons changes. > > > > > > The fix also broke PS/2 mouse support. :( :( > > > > I know :(, but so long as we occasionally looses an interrupt, there > > is not much else to do. Or merge syscons and the ps/2 mousedriver. > > (which I have on my TODO list) > > Are we losing interrupts, or is there something else going on? Yes we are loosing interrupts, mostly on very fast machines :( I don't know how & why, but I guess its a symptom for the same failure that made me put in the timeout code in wd.c years ago :( :( > Also, I just spoke with someone (the recent psm.c author) who is willing > to do the work to integrate the two, so hopefully you two can resolve > this. Great!, I have a pretty good idea on how the it should be done... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-current Wed Nov 13 10:45:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA05324 for current-outgoing; Wed, 13 Nov 1996 10:45:30 -0800 (PST) Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA05302; Wed, 13 Nov 1996 10:45:16 -0800 (PST) Received: (from bsdcur@localhost) by shadows.aeon.net (8.7.5/8.6.9) id UAA12163; Wed, 13 Nov 1996 20:40:32 +0200 (EET) From: mika ruohotie Message-Id: <199611131840.UAA12163@shadows.aeon.net> Subject: Re: GigaByte GA-586DX-512 Motherboard To: cat@uunet.ca (Cat Okita) Date: Wed, 13 Nov 1996 20:40:31 +0200 (EET) Cc: smp@csn.net, gwh@spiders.com, soward@service1.uky.edu, smp@FreeBSD.org, current@FreeBSD.org, scrappy@ki.net In-Reply-To: from Cat Okita at "Nov 12, 96 12:33:58 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > If anyone knows of a good source of ATX cases please speak up. > I've just gotten a case from 'Procase' - I'll forward more once I've got > the thing out of its box *grin* we use macase, the ztx box took a while to come out but looks really good... unlike the _all_ others i've seen, it has space for disks, still is not huge, and most of all the power switch allows either the "atx power" type or "baby-at power" type of powers... anyone know what i mean? well, ok... so i thought... but anyway. > Cat mickey From owner-freebsd-current Wed Nov 13 10:52:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA05892 for current-outgoing; Wed, 13 Nov 1996 10:52:10 -0800 (PST) Received: from ravenock.cybercity.dk (disn41.cybercity.dk [194.16.57.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA05843 for ; Wed, 13 Nov 1996 10:52:04 -0800 (PST) Received: (from sos@localhost) by ravenock.cybercity.dk (8.8.2/8.7.3) id TAA21608; Wed, 13 Nov 1996 19:52:45 +0100 (MET) Message-Id: <199611131852.TAA21608@ravenock.cybercity.dk> Subject: Re: your mail To: bde@zeta.org.au (Bruce Evans) Date: Wed, 13 Nov 1996 19:52:32 +0100 (MET) From: "Soren Schmidt" Cc: nate@mt.sri.com, freebsd-current@FreeBSD.org, jkh@time.cdrom.com, wangel@wgrobez1.remote.louisville.edu In-Reply-To: <199611131804.FAA11738@godzilla.zeta.org.au> from "Bruce Evans" at Nov 14, 96 05:04:36 am From: sos@FreeBSD.org Reply-to: sos@FreeBSD.org X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In reply to Bruce Evans who wrote: > > > >> The fix also broke PS/2 mouse support. :( :( > > > >I know :(, but so long as we occasionally looses an interrupt, there > >is not much else to do. Or merge syscons and the ps/2 mousedriver. > > Lots can be done: > - back out fix OR Bad idea keyboards will hang all over the globe... > - poll less often (fixed period) OR > - poll less often (after keyboard has been inactice for a while) OR Will still break the psm device, just more seldom... > - make fix a compile time option OR > - make fix a run time option OR Hmm, run time optime could be an idea... > - check for psm interrupt and don't poll keyboard if one is pending OR which bits to poll for that ??, and its difficult to know if a keyboard int has been lost already, so who's data is it we're reading... What I'd like to see was that we found out WHY/WHERE we are loosing the interrupt, it seems we have this problem from time to time, and I can't help it, but I still think our interrupt system is the prime suspect... The problem is that there aren't many people that understand it (hint hint)... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-current Wed Nov 13 10:56:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA06234 for current-outgoing; Wed, 13 Nov 1996 10:56:14 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA06181; Wed, 13 Nov 1996 10:55:59 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id LAA00978; Wed, 13 Nov 1996 11:55:50 -0700 (MST) Date: Wed, 13 Nov 1996 11:55:50 -0700 (MST) Message-Id: <199611131855.LAA00978@rocky.mt.sri.com> From: Nate Williams To: sos@freebsd.org Cc: bde@zeta.org.au (Bruce Evans), nate@mt.sri.com, freebsd-current@freebsd.org, jkh@time.cdrom.com, wangel@wgrobez1.remote.louisville.edu Subject: Re: your mail In-Reply-To: <199611131852.TAA21608@ravenock.cybercity.dk> References: <199611131804.FAA11738@godzilla.zeta.org.au> <199611131852.TAA21608@ravenock.cybercity.dk> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > >> The fix also broke PS/2 mouse support. :( :( > > > > > >I know :(, but so long as we occasionally looses an interrupt, there > > >is not much else to do. Or merge syscons and the ps/2 mousedriver. > > > > Lots can be done: > > - back out fix OR > > Bad idea keyboards will hang all over the globe... Is the bug that the 'set ipending=2' bug that many of us are seeing? > > - poll less often (fixed period) OR > > - poll less often (after keyboard has been inactice for a while) OR > > Will still break the psm device, just more seldom... Or less often even. ;) > > - make fix a compile time option OR > > - make fix a run time option OR > > Hmm, run time optime could be an idea... > > > - check for psm interrupt and don't poll keyboard if one is pending OR > > which bits to poll for that ??, and its difficult to know if a keyboard > int has been lost already, so who's data is it we're reading... The suggestion I made to the psm author is to have *one* read routine, which somehow can distinguish between keyboard and mouse reads. (Easier said than done). If a read is for the other device, it is queued up for that device to read earlier or their interrupt routine is called. It's not a *really* hard problem, but it's not necessarily an easy problem to work either. Nate From owner-freebsd-current Wed Nov 13 11:41:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA09311 for current-outgoing; Wed, 13 Nov 1996 11:41:27 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA09306 for ; Wed, 13 Nov 1996 11:41:22 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id GAA13980; Thu, 14 Nov 1996 06:35:35 +1100 Date: Thu, 14 Nov 1996 06:35:35 +1100 From: Bruce Evans Message-Id: <199611131935.GAA13980@godzilla.zeta.org.au> To: bde@zeta.org.au, sos@ravenock.cybercity.dk Subject: Re: your mail Cc: freebsd-current@freebsd.org, jkh@time.cdrom.com, nate@mt.sri.com, wangel@wgrobez1.remote.louisville.edu Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> - check for psm interrupt and don't poll keyboard if one is pending OR > >which bits to poll for that ??, and its difficult to know if a keyboard >int has been lost already, so who's data is it we're reading... The psm bit in ipending. We already check the KB_BUF_FULL bit, so there should be no races: an IRQ should have occured since there is some data, but we haven't processed it because of the spltty(). I hope that IRQs are serialized so that ones for the keyboard and the psm don't happen concurrently. Then ipending gives lots of information: ipending & kbd_IRQ && !(ipending & psm_IRQ) => scancode for keyboard !(ipending & kbd_IRQ) && ipending & psm_IRQ => scancode for psm ipending & kbd_IRQ && ipending & psm_IRQ => can't happen, we hope !(ipending & kbd_IRQ) && !(ipending & psm_IRQ) => oops, lost kbd IRQ Bruce From owner-freebsd-current Wed Nov 13 13:02:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA15946 for current-outgoing; Wed, 13 Nov 1996 13:02:58 -0800 (PST) Received: from ravenock.cybercity.dk (disn60.cybercity.dk [194.16.57.60]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA15937 for ; Wed, 13 Nov 1996 13:02:43 -0800 (PST) Received: (from sos@localhost) by ravenock.cybercity.dk (8.8.2/8.7.3) id WAA09059; Wed, 13 Nov 1996 22:03:10 +0100 (MET) Message-Id: <199611132103.WAA09059@ravenock.cybercity.dk> Subject: Re: your mail To: bde@zeta.org.au (Bruce Evans) Date: Wed, 13 Nov 1996 22:03:09 +0100 (MET) From: "Soren Schmidt" Cc: bde@zeta.org.au, freebsd-current@freebsd.org, jkh@time.cdrom.com, nate@mt.sri.com, wangel@wgrobez1.remote.louisville.edu In-Reply-To: <199611131935.GAA13980@godzilla.zeta.org.au> from "Bruce Evans" at Nov 14, 96 06:35:35 am From: sos@freebsd.org Reply-to: sos@freebsd.org X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply to Bruce Evans who wrote: > > > >> - check for psm interrupt and don't poll keyboard if one is pending OR > > > >which bits to poll for that ??, and its difficult to know if a keyboard > >int has been lost already, so who's data is it we're reading... > > The psm bit in ipending. We already check the KB_BUF_FULL bit, so there > should be no races: an IRQ should have occured since there is some data, > but we haven't processed it because of the spltty(). I hope that IRQs > are serialized so that ones for the keyboard and the psm don't happen > concurrently. Then ipending gives lots of information: > > ipending & kbd_IRQ && !(ipending & psm_IRQ) => scancode for keyboard > !(ipending & kbd_IRQ) && ipending & psm_IRQ => scancode for psm > ipending & kbd_IRQ && ipending & psm_IRQ => can't happen, we hope > !(ipending & kbd_IRQ) && !(ipending & psm_IRQ) => oops, lost kbd IRQ Or lost psm IRQ :( OK, I'll put code in for this and check the results, that might bring some elight over what happens... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-current Wed Nov 13 13:23:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA17225 for current-outgoing; Wed, 13 Nov 1996 13:23:52 -0800 (PST) Received: from troll.uunet.ca (troll.uunet.ca [142.77.1.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA17215; Wed, 13 Nov 1996 13:23:40 -0800 (PST) Received: from localhost by troll.uunet.ca with SMTP id <21006-23369>; Wed, 13 Nov 1996 16:23:20 -0500 Date: Wed, 13 Nov 1996 16:23:19 -0500 From: Cat Okita To: mika ruohotie cc: smp@csn.net, gwh@spiders.com, soward@service1.uky.edu, smp@FreeBSD.org, current@FreeBSD.org, scrappy@ki.net Subject: Re: GigaByte GA-586DX-512 Motherboard In-Reply-To: <199611131840.UAA12163@shadows.aeon.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 13 Nov 1996, mika ruohotie wrote: > > I've just gotten a case from 'Procase' - I'll forward more once I've got > > the thing out of its box *grin* > we use macase, the ztx box took a while to come out but looks really > good... unlike the _all_ others i've seen, it has space for disks, > still is not huge, and most of all the power switch allows either > the "atx power" type or "baby-at power" type of powers... The Procase box isn't bad: 3 5.25 bays 4 3.5 bays ATX power reasonable ammount of power plugs (had to add one splitter) 230W power supply Medium tower case The only thing that I don't like about this case is not having the removable side - mounting the MB was simple (and would have been simpler if I'd read the stuff on the face plate :<), and the clip ins were nice. The 3.5" 'bays' can be removed, for ease of installation, and they ship faceplates and 'tailplates' for all of the bays. There's plenty of room to work in, and room for an extra fan, if you want one :> Cat From owner-freebsd-current Wed Nov 13 14:19:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA21076 for current-outgoing; Wed, 13 Nov 1996 14:19:47 -0800 (PST) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA21057; Wed, 13 Nov 1996 14:19:28 -0800 (PST) Received: by sovcom.kiae.su id AA27514 (5.65.kiae-1 ); Thu, 14 Nov 1996 01:14:47 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Thu, 14 Nov 96 01:14:46 +0300 Received: (from ache@localhost) by nagual.ru (8.8.2/8.8.2) id BAA00212; Thu, 14 Nov 1996 01:13:25 +0300 (MSK) Message-Id: <199611132213.BAA00212@nagual.ru> Subject: Re: SCB paging is most dangerous option now! In-Reply-To: <199611131606.IAA25507@freefall.freebsd.org> from "Justin T. Gibbs" at "Nov 13, 96 08:06:10 am" To: gibbs@freefall.freebsd.org (Justin T. Gibbs) Date: Thu, 14 Nov 1996 01:13:25 +0300 (MSK) Cc: current@FreeBSD.org, scsi@FreeBSD.org From: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) Organization: self X-Class: Fast X-Mailer: ELM [version 2.4ME+ PL28 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > >I read only mode I got the almost same result with SCB paging as without it. > >This bug affects _writing_only_, not reading. > >And I can't start 8 dds for each drive in both modes, > >3 dds per drive is enough to cause "Queue Full" in both modes, but > >it is harmless due to read only. > > This is probably what is causing your corruption in the SCB Paging case. > Which drive can only do 3 transactions at a time? I'm sure that your IBM > can do more. It may very well be that one of your drives doesn't like the > fact that the code with SCB paging turned on will basically continually > pound on that drive, causing queue full conditions, until there aren't > enough transactions queued to make this happen any more. The patch I > posted for Andreas' problem may help in this regard. No, _any_ of two drives says "Queue full" after 2-3 dds and goes to "timed out" state after more dds which ends up with "panic: Timed-out command times out again" It happens equally in both SCB paging and not SCB paging modes. BTW, I see it only for dds, I can start f.e. about 20 "ls -lR" safely. Does it means that Tagged Queueing not work well with 2842? > As for your problem happening on the "first write", are you sure this isn't > the "first sync" after boot?? I mean first physical write, of course. It happens just after fsck puts info lines about each drive at boot phase. -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Wed Nov 13 15:03:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA23454 for current-outgoing; Wed, 13 Nov 1996 15:03:20 -0800 (PST) Received: from sequent.kiae.su (sequent.kiae.su [193.125.152.6]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA23435; Wed, 13 Nov 1996 15:03:07 -0800 (PST) Received: by sequent.kiae.su id AA29634 (5.65.kiae-2 ); Thu, 14 Nov 1996 01:48:04 +0300 Received: by sequent.KIAE.su (UUMAIL/2.0); Thu, 14 Nov 96 01:48:03 +0300 Received: (from ache@localhost) by nagual.ru (8.8.2/8.8.2) id BAA00285; Thu, 14 Nov 1996 01:47:18 +0300 (MSK) Message-Id: <199611132247.BAA00285@nagual.ru> Subject: Re: SCB paging is ... (Interesting result) In-Reply-To: <199611132213.BAA00212@nagual.ru> from "áÎÄÒÅÊ þÅÒÎÏ×" at "Nov 14, 96 01:13:25 am" X-Elm-Osv: (Our standard violations) hdr-charset=US-ASCII To: ache@nagual.ru (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=) Date: Thu, 14 Nov 1996 01:47:18 +0300 (MSK) Cc: gibbs@freefall.freebsd.org, current@FreeBSD.org, scsi@FreeBSD.org From: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) Organization: self X-Class: Fast X-Mailer: ELM [version 2.4ME+ PL28 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Does it means that Tagged Queueing not work well with 2842? I just try turn Tagged Queueing OFF and SCB paging ON and it works even for writes! Some test results: 1) TAG=OFF SCB=OFF I can easily start up to 8 dds on each drive without any errors. 2) TAG=OFF SCB=ON I can start up to 6 dds on each drive, more dds cause "timed out in message out phase" error -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Wed Nov 13 15:07:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA23631 for current-outgoing; Wed, 13 Nov 1996 15:07:05 -0800 (PST) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA23618; Wed, 13 Nov 1996 15:06:56 -0800 (PST) Message-Id: <199611132306.PAA23618@freefall.freebsd.org> To: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) cc: current@FreeBSD.org, scsi@FreeBSD.org Subject: Re: SCB paging is ... (Interesting result) In-reply-to: Your message of "Thu, 14 Nov 1996 01:47:18 +0300." <199611132247.BAA00285@nagual.ru> Date: Wed, 13 Nov 1996 15:06:55 -0800 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> Does it means that Tagged Queueing not work well with 2842? > >I just try turn Tagged Queueing OFF and SCB paging ON and it works >even for writes! You will only be using a maximum of 4 SCBs if you don't use tagged queueing (assuming only 2 devices active) since you can only have two SCBs active per non-tagged target. In otherwords, you will not be getting the heavy DMA load from moving SCBs in and out of the card's hadware SCB ram in this scenario. >Some test results: >1) TAG=OFF SCB=OFF >I can easily start up to 8 dds on each drive without any errors. >2) TAG=OFF SCB=ON >I can start up to 6 dds on each drive, more dds cause >"timed out in message out phase" error Hmm. Does the patch I just posted have any effect on your timeouts? >-- >Andrey A. Chernov > >http://www.nagual.ru/~ache/ -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Wed Nov 13 18:08:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA04554 for current-outgoing; Wed, 13 Nov 1996 18:08:16 -0800 (PST) Received: from friley216.res.iastate.edu (friley216.res.iastate.edu [129.186.78.216]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA04431; Wed, 13 Nov 1996 18:08:01 -0800 (PST) Received: from friley216.res.iastate.edu (loopback [127.0.0.1]) by friley216.res.iastate.edu (8.7.6/8.7.3) with ESMTP id UAA06226; Wed, 13 Nov 1996 20:07:39 -0600 (CST) Message-Id: <199611140207.UAA06226@friley216.res.iastate.edu> X-Mailer: exmh version 1.6.9 8/22/96 To: sthaug@nethelp.no cc: bmah@cs.berkeley.edu, dyson@FreeBSD.org, gibbs@freefall.freebsd.org, roberto@keltia.freenix.fr, freebsd-current@FreeBSD.org Subject: Re: pbufs (was: Re: ufs is too slow?) In-reply-to: Your message of Wed, 13 Nov 1996 18:13:18 +0100. <22583.847905198@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Nov 1996 20:07:38 -0600 From: Chris Csanady Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >See http://ee.lbl.gov/nrg-talks.html Thanks for the pointer. >In particular, the 1992 talk "Design Changes to the Kernel Network >Architecture for 4.4BSD", and the 1993 talk "Some Design Issues for >High-speed Networks". I like it. So who is going to do the implementation then? :) I saw it mentioned that the new tcp/ip code was intended for inclusion in 4.4, but the lawsuit made that impossible. It's really too bad.. Chris >Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-current Wed Nov 13 18:10:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA04839 for current-outgoing; Wed, 13 Nov 1996 18:10:52 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA04796 for ; Wed, 13 Nov 1996 18:10:48 -0800 (PST) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id RAA02572 for ; Wed, 13 Nov 1996 17:17:34 -0800 (PST) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.2/CET-v2.1) with SMTP id BAA17749; Thu, 14 Nov 1996 01:17:05 GMT Date: Thu, 14 Nov 1996 10:17:05 +0900 (JST) From: Michael Hancock To: "Justin T. Gibbs" cc: Mark Mayo , Terry Lambert , roberto@keltia.freenix.fr, freebsd-current@freebsd.org Subject: Re: ufs is too slow? In-Reply-To: <199611122025.MAA25041@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I talked to a WinNT products manager at Veritas and this was his reply: ----- The Volume Manager will sit (optionally) under NTFS or FAT or whatever file systems someone is using on NT. It is optional in the sense that people will still use hard disk partitions for data that they may need to access from Win95 should they want/need to boot that OS. VxFS (which you mention in the subject line and later) is not part of the agreement with Microsoft, and is not yet being ported to NT. ----- Regards, Mike Hancock From owner-freebsd-current Wed Nov 13 19:04:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA07414 for current-outgoing; Wed, 13 Nov 1996 19:04:38 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA07333; Wed, 13 Nov 1996 19:03:57 -0800 (PST) Received: from gargoyle.bazzle.com (gargoyle.bazzle.com [206.103.246.190]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id TAA02850 ; Wed, 13 Nov 1996 19:03:47 -0800 (PST) Received: from gargoyle.bazzle.com (localhost [127.0.0.1]) by gargoyle.bazzle.com (8.8.2/8.6.12) with SMTP id WAA27995; Wed, 13 Nov 1996 22:01:23 -0500 (EST) Date: Wed, 13 Nov 1996 22:01:23 -0500 (EST) From: "Eric J. Chet" To: Ernie Elu cc: ports@freebsd.org, current@freebsd.org, dob@nasvr1.cb.lucent.com Subject: Re: guavac, libstdc++ In-Reply-To: <199611132232.IAA02557@spooky.eis.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 14 Nov 1996, Ernie Elu wrote: > Has anyone managed to get the guavac java compiler from > http://http.cs.berkeley.edu/~engberg/guavac to compile under FreeBSD > current? > > Everytime I try it gets a link error from the g++ file tree.h saying that > the varialbe rb_NIL is unknown. I can't find that variable in any of the g++ > libraries so it might be a bug that it's missing. > > - Ernie. > Hello There are three *.cc files in /usr/src/contrib/libg++/libstdc++/stl random.cc tree.cc tempbuf.cc That are not being built under FreeBSD. Should these three files be added to the build process for libstdc++? They really need to be included into a library. Thanks, Eric J. Chet - ejc@bazzle.com From owner-freebsd-current Wed Nov 13 19:09:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA07674 for current-outgoing; Wed, 13 Nov 1996 19:09:15 -0800 (PST) Received: from gargoyle.bazzle.com (gargoyle.bazzle.com [206.103.246.190]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA07540 for ; Wed, 13 Nov 1996 19:07:37 -0800 (PST) Received: from gargoyle.bazzle.com (localhost [127.0.0.1]) by gargoyle.bazzle.com (8.8.2/8.6.12) with SMTP id WAA00909; Wed, 13 Nov 1996 22:07:18 -0500 (EST) Date: Wed, 13 Nov 1996 22:07:18 -0500 (EST) From: "Eric J. Chet" To: current@freebsd.org cc: dob@nasvr1.cb.lucent.com Subject: diff.deque.h (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello We have a bug in deque.h, I think this should be patched. Eric J. Chet - ejc@bazzle.com ---------- Forwarded message ---------- Date: Fri, 8 Nov 1996 15:45:43 -0500 From: "Dan O'Brien, 614.860.3292" To: ejc@naserver1.cb.lucent.com, ejc@gargoyle.bazzle.com Subject: diff.deque.h Eric, I found the bug in FreeBSD GNU STL version of deque.h. Looks like a source file maintenance error. Here is the patch. *** deque.h.ORG Fri Nov 8 15:36:38 1996 --- deque.h Fri Nov 8 15:36:46 1996 *************** void deque::allocate_at_begin() { *** 437,444 **** finish = iterator(finish.current, map + map_size / 4 + i + 1); } else { #ifdef __GNUG__ ! map_size = map_allocator_type::init_page_size(); ! map = map_allocator_type::allocate(map_size); #else *--start.node = p; start = iterator(p + __dq_buffer_size, start.node); --- 437,446 ---- finish = iterator(finish.current, map + map_size / 4 + i + 1); } else { #ifdef __GNUG__ ! // map_size = map_allocator_type::init_page_size(); ! // map = map_allocator_type::allocate(map_size); ! *--start.node = p; ! start = iterator(p + __dq_buffer_size, start.node); #else *--start.node = p; start = iterator(p + __dq_buffer_size, start.node); I'm not sure who to submit this to. Please forward it to whomever should receive this bug report. Here is a test program. It core dumps without the patch. #include #include int main() { deque a; for ( int i = 0 ; i < 8000 ; i++ ) { a.push_front( i ); } return 1; } Thanks for handling this report, Dan O'Brien From owner-freebsd-current Wed Nov 13 19:40:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA09407 for current-outgoing; Wed, 13 Nov 1996 19:40:36 -0800 (PST) Received: from itchy.mindspring.com (itchy.mindspring.com [204.180.128.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA09251 for ; Wed, 13 Nov 1996 19:38:21 -0800 (PST) Received: from rlb.users.mindspring.com (user-168-121-25-139.dialup.mindspring.com [168.121.25.139]) by itchy.mindspring.com (8.7.5/8.7.3) with SMTP id WAA05326 for ; Wed, 13 Nov 1996 22:37:28 -0500 (EST) Message-ID: <328A9413.794BDF32@mindspring.com> Date: Wed, 13 Nov 1996 22:37:55 -0500 From: Ron Bolin X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: New Syscons.c still gives PS/2 Mouse problems. Suggestions? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I did a cvsup and got the 1.86 version of syscons.c, and am still experiencing the wierd PS/2 mouse behavior. Any thoughts? Ron -- **************************************************************************** Ron Bolin rlb@mindspring.com, http://www.mindspring.com/~rlb/ GSU: gs01rlb@panther.gsu.edu matrlbx@indigo4.cs.gsu.edu Home: 770-992-8877 **************************************************************************** From owner-freebsd-current Wed Nov 13 19:44:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA09582 for current-outgoing; Wed, 13 Nov 1996 19:44:53 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id TAA09577 for ; Wed, 13 Nov 1996 19:44:40 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id UAA23387; Wed, 13 Nov 1996 20:32:33 -0700 From: Terry Lambert Message-Id: <199611140332.UAA23387@phaeton.artisoft.com> Subject: Re: ufs is too slow? To: michaelh@cet.co.jp (Michael Hancock) Date: Wed, 13 Nov 1996 20:32:32 -0700 (MST) Cc: gibbs@freefall.freebsd.org, mark@quickweb.com, terry@lambert.org, roberto@keltia.freenix.fr, freebsd-current@FreeBSD.ORG In-Reply-To: from "Michael Hancock" at Nov 14, 96 10:17:05 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > VxFS (which you mention in the subject line and later) is not part of the > agreement with Microsoft, and is not yet being ported to NT. Thanks for the more concrete info... 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-current Wed Nov 13 22:29:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA17694 for current-outgoing; Wed, 13 Nov 1996 22:29:24 -0800 (PST) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA17689; Wed, 13 Nov 1996 22:29:22 -0800 (PST) Message-Id: <199611140629.WAA17689@freefall.freebsd.org> To: Michael Hancock cc: Mark Mayo , Terry Lambert , roberto@keltia.freenix.fr, freebsd-current@freebsd.org Subject: Re: ufs is too slow? In-reply-to: Your message of "Thu, 14 Nov 1996 10:17:05 +0900." Date: Wed, 13 Nov 1996 22:29:22 -0800 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >VxFS (which you mention in the subject line and later) is not part of the >agreement with Microsoft, and is not yet being ported to NT. I don't believe that the Volume manager has been ported yet either. Do you mean that it will not be ported??? >----- > >Regards, > > >Mike Hancock > -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Wed Nov 13 23:46:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA21348 for current-outgoing; Wed, 13 Nov 1996 23:46:54 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA21343 for ; Wed, 13 Nov 1996 23:46:52 -0800 (PST) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id XAA03237 for ; Wed, 13 Nov 1996 23:46:45 -0800 (PST) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.2/CET-v2.1) with SMTP id HAA20035; Thu, 14 Nov 1996 07:45:04 GMT Date: Thu, 14 Nov 1996 16:45:03 +0900 (JST) From: Michael Hancock Reply-To: Michael Hancock To: "Justin T. Gibbs" cc: freebsd-current@freebsd.org Subject: Re: ufs is too slow? In-Reply-To: <199611140629.WAA17689@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 13 Nov 1996, Justin T. Gibbs wrote: > >VxFS (which you mention in the subject line and later) is not part of the > >agreement with Microsoft, and is not yet being ported to NT. > > I don't believe that the Volume manager has been ported yet either. Do > you mean that it will not be ported??? The deal with MS is about the Volume Manager Only. I talked to a VxFS engineer there and a Veritas WinNT product manager and speaking for themselves they are both keen on porting VxFS to WinNT. I didn't get a reply that sounded like a concrete decision to do VxFS though. Regards, Mike Hancock From owner-freebsd-current Thu Nov 14 00:41:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA24094 for current-outgoing; Thu, 14 Nov 1996 00:41:49 -0800 (PST) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA24087 for ; Thu, 14 Nov 1996 00:41:38 -0800 (PST) Received: (from karpen@localhost) by ocean.campus.luth.se (8.7.5/8.7.3) id JAA03583; Thu, 14 Nov 1996 09:46:12 +0100 (MET) From: Mikael Karpberg Message-Id: <199611140846.JAA03583@ocean.campus.luth.se> Subject: Re: (add|rm)(user|group) To: wosch@cs.tu-berlin.de (Wolfram Schneider) Date: Thu, 14 Nov 1996 09:46:12 +0100 (MET) Cc: current@freebsd.org In-Reply-To: <199611121553.QAA00777@campa.panke.de> from Wolfram Schneider at "Nov 12, 96 04:53:26 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Wolfram Schneider: > > I did not got a reply for the removeuser, addgroup, and > rmgroup scripts. So I guess they works well ;-) > If nobody objects I will change the -current Makefile > and install the scripts in /usr/sbin/ I haven't looked at them at all, but I thought I'd just comment on their names as you listed them above. addgroup / adduser - seems logical rmgroup / removeuser - not so logical Why not rmuser or removegroup ? I think it would be nice with consistant naming, maybe? /Mikael From owner-freebsd-current Thu Nov 14 00:50:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA24676 for current-outgoing; Thu, 14 Nov 1996 00:50:37 -0800 (PST) Received: from fox.uni-trier.de (blank@fox.uni-trier.de [136.199.8.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA24668 for ; Thu, 14 Nov 1996 00:50:25 -0800 (PST) Received: (from blank@localhost) by fox.uni-trier.de (8.7.5/8.7.3) id JAA18620 for current@freefall.freebsd.org; Thu, 14 Nov 1996 09:51:06 +0100 From: Sascha Blank Message-Id: <199611140851.JAA18620@fox.uni-trier.de> Subject: Shipping of CTM deltas for ports-cur has stopped To: current@freefall.freebsd.org Date: Thu, 14 Nov 1996 09:51:05 +0100 (MET) Reply-To: blank@fox.uni-trier.de (Sascha Blank) 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-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi there, I have noticed that I haven't received one single CTM delta of ports-cur since November 10th. The last delta I received was number 1454. I have looked at the archive on freefall.freebsd.org as well but they don't have a more recent delta either. This looks suspicious to me as I am used to receive at least one delta a day and still receive the usual amount of CVS commit messages concerning the ports collection. -- Sascha Blank - mailto:blank@fox.uni-trier.de Student and System Administrator at the University of Trier, Germany Finger my account to receive my Public PGP key All opinions expressed herein reflect only my personal point of view From owner-freebsd-current Thu Nov 14 01:19:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA25597 for current-outgoing; Thu, 14 Nov 1996 01:19:51 -0800 (PST) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA25590; Thu, 14 Nov 1996 01:19:40 -0800 (PST) Received: from critter.tfs.com (localhost.dk.tfs.com [127.0.0.1]) by critter.tfs.com (8.8.2/8.8.2) with ESMTP id KAA02944; Thu, 14 Nov 1996 10:19:25 +0100 (MET) To: blank@fox.uni-trier.de (Sascha Blank) cc: current@freefall.freebsd.org Subject: Re: Shipping of CTM deltas for ports-cur has stopped In-reply-to: Your message of "Thu, 14 Nov 1996 09:51:05 +0100." <199611140851.JAA18620@fox.uni-trier.de> Date: Thu, 14 Nov 1996 10:19:24 +0100 Message-ID: <2942.847963164@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199611140851.JAA18620@fox.uni-trier.de>, Sascha Blank writes: >Hi there, > >I have noticed that I haven't received one single CTM delta of ports-cur I've kicked it. Be carefull about the next one comming. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Thu Nov 14 01:27:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA26106 for current-outgoing; Thu, 14 Nov 1996 01:27:26 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA26094; Thu, 14 Nov 1996 01:27:15 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id KAA22316; Thu, 14 Nov 1996 10:15:20 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.8.2/8.8.2) with SMTP id JAA00989; Thu, 14 Nov 1996 09:39:05 +0100 (MET) Date: Thu, 14 Nov 1996 09:39:04 +0100 (MET) From: Andreas Klemm To: jkh@freebsd.org cc: current@freebsd.org Subject: an error during make release Message-ID: X-try-apsfilter: ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz X-Fax: +49 2137 2018 X-Phone: +49 2137 2020 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Jordan ! During make release I noticed the following error. I hope it helps you to find the problem. I did a 'make release' for the HEAD branch ... very very current as of 2 days ago. sfd/stand 23 blocks echo "nameserver 42/tcp name" > /R/stage/mfsfd/stand/etc/services echo "ftp 21/tcp" >> /R/stage/mfsfd/stand/etc/services echo "domain 53/tcp nameserver" >> /R/stage/mfsfd/stand/etc/services echo "domain 53/udp nameserver" >> /R/stage/mfsfd/stand/etc/services echo "cmd 514/tcp shell" >> /R/stage/mfsfd/stand/etc/services gzip -c /usr/src/release/../COPYRIGHT > /R/stage/mfsfd/stand/help/COPYRIGHT.hlp.gz test -f /usr/src/release/install.cfg && cp /usr/src/release/install.cfg /R/stage/mfsfd *** Error code 1 (ignored) # make the small bootfd Making the small 4MB boot floppy. sh -e /usr/src/release/doFS.sh /R/stage /mnt 1400 /R/stage/mfsfd 42000 minimum open: Device not configured *** Error code 1 Stop. *** Error code 1 Stop. -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-current Thu Nov 14 02:02:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA27721 for current-outgoing; Thu, 14 Nov 1996 02:02:46 -0800 (PST) Received: from ravenock.cybercity.dk (disn62.cybercity.dk [194.16.57.62]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA27714; Thu, 14 Nov 1996 02:02:38 -0800 (PST) Received: (from sos@localhost) by ravenock.cybercity.dk (8.8.2/8.7.3) id LAA01069; Thu, 14 Nov 1996 11:02:48 +0100 (MET) Message-Id: <199611141002.LAA01069@ravenock.cybercity.dk> Subject: Re: an error during make release To: andreas@klemm.gtn.com (Andreas Klemm) Date: Thu, 14 Nov 1996 11:02:48 +0100 (MET) From: "Soren Schmidt" Cc: jkh@FreeBSD.org, current@FreeBSD.org In-Reply-To: from "Andreas Klemm" at Nov 14, 96 09:39:04 am From: sos@FreeBSD.org Reply-to: sos@FreeBSD.org X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In reply to Andreas Klemm who wrote: > > Hi Jordan ! > > During make release I noticed the following error. I hope it helps you > to find the problem. I did a 'make release' for the HEAD branch ... > very very current as of 2 days ago. > Do you have a vn device in your kernel ?? > sfd/stand > 23 blocks > echo "nameserver 42/tcp name" > /R/stage/mfsfd/stand/etc/services > echo "ftp 21/tcp" >> /R/stage/mfsfd/stand/etc/services > echo "domain 53/tcp nameserver" >> /R/stage/mfsfd/stand/etc/services > echo "domain 53/udp nameserver" >> /R/stage/mfsfd/stand/etc/services > echo "cmd 514/tcp shell" >> /R/stage/mfsfd/stand/etc/services > gzip -c /usr/src/release/../COPYRIGHT > /R/stage/mfsfd/stand/help/COPYRIGHT.hlp.gz > test -f /usr/src/release/install.cfg && cp /usr/src/release/install.cfg /R/stage/mfsfd > *** Error code 1 (ignored) > # make the small bootfd > Making the small 4MB boot floppy. > sh -e /usr/src/release/doFS.sh /R/stage /mnt 1400 /R/stage/mfsfd 42000 minimum > open: Device not configured > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-current Thu Nov 14 03:37:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA02263 for current-outgoing; Thu, 14 Nov 1996 03:37:56 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA02217; Thu, 14 Nov 1996 03:37:51 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id MAA12875; Thu, 14 Nov 1996 12:16:17 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.8.2/8.8.2) with SMTP id MAA00690; Thu, 14 Nov 1996 12:02:46 +0100 (MET) Date: Thu, 14 Nov 1996 12:02:45 +0100 (MET) From: Andreas Klemm To: sos@freebsd.org cc: jkh@freebsd.org, current@freebsd.org Subject: Re: an error during make release In-Reply-To: <199611141002.LAA01069@ravenock.cybercity.dk> Message-ID: X-try-apsfilter: ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz X-Fax: +49 2137 2018 X-Phone: +49 2137 2020 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 14 Nov 1996, Soren Schmidt wrote: > > During make release I noticed the following error. I hope it helps you > > to find the problem. I did a 'make release' for the HEAD branch ... > > very very current as of 2 days ago. > > > > Do you have a vn device in your kernel ?? No I hadn't, thanks. I'll drop a hint about that in release/Makefile. -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-current Thu Nov 14 03:39:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA02358 for current-outgoing; Thu, 14 Nov 1996 03:39:03 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA02339; Thu, 14 Nov 1996 03:38:57 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id MAA12880; Thu, 14 Nov 1996 12:16:26 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.8.2/8.8.2) with SMTP id MAA00704; Thu, 14 Nov 1996 12:05:13 +0100 (MET) Date: Thu, 14 Nov 1996 12:05:13 +0100 (MET) From: Andreas Klemm To: "Justin T. Gibbs" cc: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= , current@freebsd.org, scsi@freebsd.org Subject: Re: SCB paging is ... (Interesting result) In-Reply-To: <199611132306.PAA23618@freefall.freebsd.org> Message-ID: X-try-apsfilter: ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz X-Fax: +49 2137 2018 X-Phone: +49 2137 2020 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 13 Nov 1996, Justin T. Gibbs wrote: > Hmm. Does the patch I just posted have any effect on your timeouts? BTW, sorry, I didn't test your patch, yet. What do you think / expect: That with your patch tagged queuing will work ? Or should I enable both: tagged queuing _and_ SCB paging ? -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-current Thu Nov 14 04:32:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA05662 for current-outgoing; Thu, 14 Nov 1996 04:32:51 -0800 (PST) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA05640 for ; Thu, 14 Nov 1996 04:32:44 -0800 (PST) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.2/8.7.3) id XAA01269 for current@freebsd.org; Thu, 14 Nov 1996 23:32:40 +1100 (EST) From: David Dawes Message-Id: <199611141232.XAA01269@rf900.physics.usyd.edu.au> Subject: Problem with kernel version number on the RELENG_2_2 branch To: current@freebsd.org Date: Thu, 14 Nov 1996 23:32:40 +1100 (EST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I noticed that a kernel I built from a cvsup with 'tag=RELENG_2_2' reports itself as 3.0-CURRENT. sys/conf/newvers.sh has: # $Id: newvers.sh,v 1.26.2.2 1996/11/12 09:07:05 phk Exp $ TYPE="FreeBSD" REVISION="3.0" BRANCH="CURRENT" David From owner-freebsd-current Thu Nov 14 04:54:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA07085 for current-outgoing; Thu, 14 Nov 1996 04:54:12 -0800 (PST) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA07073; Thu, 14 Nov 1996 04:54:08 -0800 (PST) Received: from critter.tfs.com (localhost.dk.tfs.com [127.0.0.1]) by critter.tfs.com (8.8.2/8.8.2) with ESMTP id NAA03258; Thu, 14 Nov 1996 13:53:58 +0100 (MET) To: David Dawes cc: current@freebsd.org Subject: Re: Problem with kernel version number on the RELENG_2_2 branch In-reply-to: Your message of "Thu, 14 Nov 1996 23:32:40 +1100." <199611141232.XAA01269@rf900.physics.usyd.edu.au> Date: Thu, 14 Nov 1996 13:53:57 +0100 Message-ID: <3256.847976037@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199611141232.XAA01269@rf900.physics.usyd.edu.au>, David Dawes write s: >I noticed that a kernel I built from a cvsup with 'tag=RELENG_2_2' >reports itself as 3.0-CURRENT. sys/conf/newvers.sh has: > ># $Id: newvers.sh,v 1.26.2.2 1996/11/12 09:07:05 phk Exp $ > >TYPE="FreeBSD" >REVISION="3.0" >BRANCH="CURRENT" Thanks Dave! -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Thu Nov 14 05:31:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA08907 for current-outgoing; Thu, 14 Nov 1996 05:31:49 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA08901; Thu, 14 Nov 1996 05:31:47 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.2/8.6.9) with ESMTP id FAA05028; Thu, 14 Nov 1996 05:31:47 -0800 (PST) To: Andreas Klemm cc: jkh@freebsd.org, current@freebsd.org Subject: Re: an error during make release In-reply-to: Your message of "Thu, 14 Nov 1996 09:39:04 +0100." Date: Thu, 14 Nov 1996 05:31:47 -0800 Message-ID: <5026.847978307@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > sh -e /usr/src/release/doFS.sh /R/stage /mnt 1400 /R/stage/mfsfd 42000 minim um > open: Device not configured Sorry, no. This one's pilot error, I'm afraid. :-) You simply don't have the vn device in your kernel. Jordan From owner-freebsd-current Thu Nov 14 05:52:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA09838 for current-outgoing; Thu, 14 Nov 1996 05:52:09 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA09829 for ; Thu, 14 Nov 1996 05:52:06 -0800 (PST) Received: from ki1.chemie.fu-berlin.de (ki1.Chemie.FU-Berlin.DE [160.45.24.21]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id FAA03672 for ; Thu, 14 Nov 1996 05:52:04 -0800 (PST) Received: by ki1.chemie.fu-berlin.de (Smail3.1.28.1) from mail.hanse.de (193.174.9.9) with smtp id ; Thu, 14 Nov 96 14:51 MET Received: from wavehh.UUCP by mail.hanse.de with UUCP for freebsd-current@freebsd.org id ; Thu, 14 Nov 96 14:51 MET Received: by wavehh.hanse.de (4.1/SMI-4.1) id AA13611; Thu, 14 Nov 96 14:51:03 +0100 From: cracauer@wavehh.hanse.de (Martin Cracauer) Message-Id: <9611141351.AA13611@wavehh.hanse.de> Subject: EDO vs. other (Re: GigaByte GA-586DX-512 Motherboard) To: freebsd-current@freebsd.org Date: Thu, 14 Nov 1996 14:51:03 +0100 (MET) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just ran that famous RAM benchmark that came down -hackers some time ago: normal parity RAM (8x 32 MB installed) 49005fb0 0.160 uS/op 6.24e+06 op/S 23.805 Mb/S 8938c0df 0.369 uS/op 2.71e+06 op/S 10.338 Mb/S 49005fb0 0.160 uS/op 6.24e+06 op/S 23.806 Mb/S 8938c0df 0.369 uS/op 2.71e+06 op/S 10.337 Mb/S EDO w/o Parity (2x 16 MB installed) 49005fb0 0.159 uS/op 6.29e+06 op/S 23.999 Mb/S 8938c0df 0.366 uS/op 2.73e+06 op/S 10.421 Mb/S 49005fb0 0.159 uS/op 6.29e+06 op/S 23.999 Mb/S 8938c0df 0.366 uS/op 2.73e+06 op/S 10.422 Mb/S I don't beleive one can speed up any real application using EDO. The machine is a newer ATX double-P6 board, only one P6 installed, 512 KB cache, FreeBSD-2.1.5. Nice box, BTW... Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://cracauer.cons.org From owner-freebsd-current Thu Nov 14 05:53:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA09900 for current-outgoing; Thu, 14 Nov 1996 05:53:02 -0800 (PST) Received: from wgrobez1.remote.louisville.edu (wgrobez1.remote.louisville.edu [136.165.243.183]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA09876 for ; Thu, 14 Nov 1996 05:52:37 -0800 (PST) Received: from localhost (wangel@localhost) by wgrobez1.remote.louisville.edu (8.7.6/8.6.12) with SMTP id IAA01217 for ; Thu, 14 Nov 1996 08:53:06 -0500 (EST) Date: Thu, 14 Nov 1996 08:53:06 -0500 (EST) From: Gary Roberts To: freebsd-current@freebsd.org Subject: cvsup Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Call me stupid. I just upgraded to cvsup, ran it, worked great. However, it put everything in /archive/pub/FreeBSD/FreeBSD-Current/src. I thought it was supposed to go in /usr/src, w/ everything being in their directories. Can I rm -rf the dirs from /usr/src, and run make world from the /archive dir? Or do I need to move everything from /archive -> /usr/src? Thanks Gary From owner-freebsd-current Thu Nov 14 06:07:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA10788 for current-outgoing; Thu, 14 Nov 1996 06:07:28 -0800 (PST) Received: from whale.gu.kiev.ua ([194.93.190.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA10743; Thu, 14 Nov 1996 06:07:17 -0800 (PST) Received: from creator.gu.kiev.ua (stesin@creator.gu.kiev.ua [194.93.190.3]) by whale.gu.kiev.ua (8.7.5/8.7.3) with SMTP id QAA30558; Thu, 14 Nov 1996 16:07:10 +0200 Date: Thu, 14 Nov 1996 16:07:09 +0200 (EET) From: Andrew Stesin X-Sender: stesin@creator.gu.kiev.ua To: current@freebsd.org, stable@freebsd.org Subject: First impressions on 2.2-ALPHA installer Message-ID: X-NCC-RegID: ua.gu MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Seems to be Ok, though the installation now just runs over a 57600 async null-modem. Probably tomorrow I'll see what will be the real result. :) This is SLIP; sorry, I didn't read the supplied doco, maybe it already has the fact mentioned, -- but anyway, if you want to use SLIP, then in "additional ifconfig args" you should also enter: 1. (from the beginning of the box!) your SLIP peer address, 2. (if needed) mtu XXX (whatever you do use) Additional comments are to be sent later. Thanks, guys, that's really cool: one just go and install UNIX from distribution which sits somewhere at the other side of the globe! 8-) -- Best, Andrew Stesin nic-hdl: ST73-RIPE From owner-freebsd-current Thu Nov 14 06:37:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA12324 for current-outgoing; Thu, 14 Nov 1996 06:37:23 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA12313 for ; Thu, 14 Nov 1996 06:37:09 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id PAA16682 for current@freebsd.org; Thu, 14 Nov 1996 15:30:31 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.8.2/8.8.2) with SMTP id PAA00774 for ; Thu, 14 Nov 1996 15:19:15 +0100 (MET) Date: Thu, 14 Nov 1996 15:19:14 +0100 (MET) From: Andreas Klemm To: current@freebsd.org Subject: fixit floppy trouble on -current 3.0 Message-ID: X-try-apsfilter: ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz X-Fax: +49 2137 2018 X-Phone: +49 2137 2020 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi ! Finally I got 'make release' running after linking the vn driver into the kernel. Why a 'make release' ? Well, I needed a fresh /stand directory and wanted to get a new fixit floppy, just to see, if I would be able to get my system recovered in case of trouble. As it looks to me, I wouldn't be able to get my system recovered. First of all some experiences using MAKEDEV in /mnt2/dev of the fixit floppy: ./MAKEDEV doesn't run, since #!/bin/sh isn't in the search path. so I have to use it typing sh MAKEDEV 'sh MAKEDEV somedevice' fails, because expr can't be found. expr is located somewhere in /mnt2/stand or such, if I remember right. This path is set in the shell envireoment, no trouble here. The problem comes from inside the MAKEDEV script, where the PATH environment is set fixed to a PATH, not suitable for a fixit floppy environment. So I'd set the PATH environment of MAKEDEV to something like: PATH=/sbin:/bin/:/usr/bin:/usr/sbin:$PATH ^^^^^ Workaround is, to edit MAKEDEV on the fixit floppy ... But then ... Then I wanted to try to backup some of my partitions: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/sd0a 31775 13274 15959 45% / /dev/sd0s3e 63567 37149 21333 64% /www /dev/sd0s3f 127151 87752 29227 75% /var /dev/sd0s3g 765058 500994 202860 71% /usr /dev/sd1s1e 193855 104777 73570 59% /news /dev/sd1s1f 1790627 1568730 78647 95% /local So the 1st task was to try to create the devices rsd0s3e and so on. MAKEDEV complained about no space left .... Well, a df -i shows this numbers: Filesystem 1K-blocks Used Avail Capacity iused ifree %iused M. on root_device 1319 1137 182 86% 101 281 26% / /dev/fd0 1095 1051 44 96% 381 193 66% /mnt2 I removed some special devices, and the output of df shows some space, but I was unable to create any sd0s3x device. I typed: sh MAKEDEV sd0s3e sh MAKEDEV sd0s3f and so on but the commands didn't have any result, because of 'no space left'. Could perhaps someone have a look at this, because I think it's important to have a working fixit floppy, or does somebody have another idea of how to recover 'fast && reliable' ? Andreas /// On the other hand: the new installation menu looks smart, Jordan. I mean the part, where you can jump through an index of functions. Can't remember, if the other boot floppies had that, too, but looks cool ;-) -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-current Thu Nov 14 07:25:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA14947 for current-outgoing; Thu, 14 Nov 1996 07:25:07 -0800 (PST) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA14880; Thu, 14 Nov 1996 07:24:39 -0800 (PST) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id PAA28432; Thu, 14 Nov 1996 15:25:55 GMT Date: Thu, 14 Nov 1996 15:25:54 +0000 (GMT) From: Developer To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org, freebsd-chat@freebsd.org Subject: PLEASE HELP - PROBLEM WITH NIS Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Does anyone know how I can get NIS to work correctly? I have to manually kill -HUP ypserv every time an NIS password is changed or the system still thinks it is the old one -- ypcat returns the old password??? I am using FreeBSD 2.2 -- the yp stuff is compiled from -current. Any help would be very helpful. Regards, Trefor S. From owner-freebsd-current Thu Nov 14 07:28:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA15133 for current-outgoing; Thu, 14 Nov 1996 07:28:50 -0800 (PST) Received: from gateway.skipstone.com (root@GATEWAY.SKIPSTONE.COM [198.214.10.129]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA15128 for ; Thu, 14 Nov 1996 07:28:45 -0800 (PST) Received: from bugs.skipstone.com (bugs.skipstone.com [204.69.236.2]) by gateway.skipstone.com (8.7.4/8.6.9) with ESMTP id JAA13533; Thu, 14 Nov 1996 09:28:32 -0600 Received: from [204.69.236.50] (hotapplepie.skipstone.com [204.69.236.50]) by bugs.skipstone.com (8.7.5/8.7.3) with ESMTP id JAA14462; Thu, 14 Nov 1996 09:28:31 -0600 X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 14 Nov 1996 09:28:30 -0600 To: Gary Roberts From: Richard Wackerbarth Subject: Re: cvsup Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Call me stupid. I just upgraded to cvsup, ran it, worked great. However, >it put everything in /archive/pub/FreeBSD/FreeBSD-Current/src. I thought >it was supposed to go in /usr/src, w/ everything being in their >directories. Can I rm -rf the dirs from /usr/src, and run make world from >the /archive dir? Or do I need to move everything from /archive -> >/usr/src? You will need the source in /usr/src when you compile it:-( However, I would leave it elsewhere and simply "ln -s ....../FreeBSD-Current/src /usr". That way you can also easily switch to FreeBSD-2.2/src, etc. if you want to try another system (like the releases in progress). If you do not like " /archive/pub/FreeBSD", edit the supfile to include you own prefix. BTW, John, since we have to (CV)sup a large number of distributions from the same place, it would be nice if the input would allow us to specify the common elements only once rather thanon each entry. From owner-freebsd-current Thu Nov 14 07:59:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA28534 for current-outgoing; Thu, 14 Nov 1996 07:59:21 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA28377 for ; Thu, 14 Nov 1996 07:59:08 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id QAA29502; Thu, 14 Nov 1996 16:45:44 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.8.2/8.8.2) with SMTP id QAA01908; Thu, 14 Nov 1996 16:01:34 +0100 (MET) Date: Thu, 14 Nov 1996 16:01:34 +0100 (MET) From: Andreas Klemm To: Mark Mayo cc: Terry Lambert , Ollivier Robert , freebsd-current@FreeBSD.org Subject: Re: ufs is too slow? In-Reply-To: Message-ID: X-try-apsfilter: ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz X-Fax: +49 2137 2018 X-Phone: +49 2137 2020 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 11 Nov 1996, Mark Mayo wrote: > Just curious, how would a NTFS perform in this scenario? As far as I > remember, NTFS allows btree directory structures. Also NTFS allows per > file compression, and "live" partition extension (making a logical drive > spread across multiple disks, or extending the size of a logical partition > on the current disk). One exception, the logical drive must not be a system partition (boot partition or a swapfile on it). You are only allowed to extend upto 32 _pure data_ volumes. > It seems to me that NTFS has quite a bit of > functionality, but how does it perform compared to UFS - under the > 'general' and extreme cases (such as news). BTW: one undocumented feature of NTFS is, that it fragments ! Our developers got a tool from a ftp site, that reported severe fragmentation. ewwwwww! That explained the loss of filesystem performance over some weeks... BTW, who would love to write additionally an fsck for it ?! When trying to implement NTFS, don't forget this ;) If I had to choose between ufs and NTFS, I'd choose UFS ;) I would use NTFS only for playing ;) -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-current Thu Nov 14 08:20:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA04755 for current-outgoing; Thu, 14 Nov 1996 08:20:05 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA04705 for ; Thu, 14 Nov 1996 08:19:57 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA05621; Thu, 14 Nov 1996 09:19:43 -0700 (MST) Date: Thu, 14 Nov 1996 09:19:43 -0700 (MST) Message-Id: <199611141619.JAA05621@rocky.mt.sri.com> From: Nate Williams To: Ron Bolin Cc: freebsd-current@freebsd.org Subject: Re: New Syscons.c still gives PS/2 Mouse problems. Suggestions? In-Reply-To: <328A9413.794BDF32@mindspring.com> References: <328A9413.794BDF32@mindspring.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ron Bolin writes: > I did a cvsup and got the 1.86 version of syscons.c, and am still > experiencing the wierd PS/2 mouse behavior. > > Any thoughts? S'ren hasn't yet applied the fixes that Bruce suggested. In the meantime, you can back out the following 'fix' which seems to be causing the problem. Nate --------------- Index: syscons.c =================================================================== RCS file: /home/CVS/src/sys/i386/isa/syscons.c,v retrieving revision 1.182 retrieving revision 1.183 diff -c -r1.182 -r1.183 *** syscons.c 1996/10/26 20:16:58 1.182 --- syscons.c 1996/11/04 21:01:08 1.183 *************** *** 25,31 **** * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. * ! * $Id: syscons.c,v 1.182 1996/10/26 20:16:58 sos Exp $ */ #include "sc.h" --- 25,31 ---- * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. * ! * $Id: syscons.c,v 1.183 1996/11/04 21:01:08 sos Exp $ */ #include "sc.h" *************** *** 572,606 **** mark_all(cur_console); } ! c = scgetc(SCGETC_NONBLOCK); ! cur_tty = VIRTUAL_TTY(get_scr_num()); ! if (!(cur_tty->t_state & TS_ISOPEN)) ! if (!((cur_tty = CONSOLE_TTY)->t_state & TS_ISOPEN)) ! return; ! switch (c & 0xff00) { ! case 0x0000: /* normal key */ ! (*linesw[cur_tty->t_line].l_rint)(c & 0xFF, cur_tty); break; ! case NOKEY: /* nothing there */ ! return; ! case FKEY: /* function key, return string */ ! if (cp = get_fstr((u_int)c, (u_int *)&len)) { ! while (len-- > 0) ! (*linesw[cur_tty->t_line].l_rint)(*cp++ & 0xFF, cur_tty); } - break; - case MKEY: /* meta is active, prepend ESC */ - (*linesw[cur_tty->t_line].l_rint)(0x1b, cur_tty); - (*linesw[cur_tty->t_line].l_rint)(c & 0xFF, cur_tty); - break; - case BKEY: /* backtab fixed sequence (esc [ Z) */ - (*linesw[cur_tty->t_line].l_rint)(0x1b, cur_tty); - (*linesw[cur_tty->t_line].l_rint)('[', cur_tty); - (*linesw[cur_tty->t_line].l_rint)('Z', cur_tty); - break; } if (cur_console->status & MOUSE_ENABLED) { cur_console->status &= ~MOUSE_VISIBLE; remove_mouse_image(cur_console); --- 572,611 ---- mark_all(cur_console); } ! /* ! * Loop while there is still input to get from the keyboard. ! * I don't think this is nessesary, and it doesn't fix ! * the Xaccel-2.1 keyboard hang, but it can't hurt. XXX ! */ ! while ((c = scgetc(SCGETC_NONBLOCK)) != NOKEY) { ! cur_tty = VIRTUAL_TTY(get_scr_num()); ! if (!(cur_tty->t_state & TS_ISOPEN)) ! if (!((cur_tty = CONSOLE_TTY)->t_state & TS_ISOPEN)) ! return; ! switch (c & 0xff00) { ! case 0x0000: /* normal key */ ! (*linesw[cur_tty->t_line].l_rint)(c & 0xFF, cur_tty); ! break; ! case FKEY: /* function key, return string */ ! if (cp = get_fstr((u_int)c, (u_int *)&len)) { ! while (len-- > 0) ! (*linesw[cur_tty->t_line].l_rint)(*cp++ & 0xFF, cur_tty); ! } break; ! case MKEY: /* meta is active, prepend ESC */ ! (*linesw[cur_tty->t_line].l_rint)(0x1b, cur_tty); ! (*linesw[cur_tty->t_line].l_rint)(c & 0xFF, cur_tty); ! break; ! case BKEY: /* backtab fixed sequence (esc [ Z) */ ! (*linesw[cur_tty->t_line].l_rint)(0x1b, cur_tty); ! (*linesw[cur_tty->t_line].l_rint)('[', cur_tty); ! (*linesw[cur_tty->t_line].l_rint)('Z', cur_tty); ! break; } } + if (cur_console->status & MOUSE_ENABLED) { cur_console->status &= ~MOUSE_VISIBLE; remove_mouse_image(cur_console); *************** *** 1442,1447 **** --- 1447,1462 ---- scr_stat *scp = cur_console; int s = spltty(); + /* + * With release 2.1 of the Xaccel server, the keyboard is left + * hanging pretty often. Apparently the interrupt from the + * keyboard is lost, and I don't know why (yet). + * This Ugly hack calls scintr if input is ready and + * conveniently hides the problem. XXX + */ + if (inb(KB_STAT) & KB_BUF_FULL) + scintr(0); + /* should we just return ? */ if ((scp->status&UNKNOWN_MODE) || blink_in_progress || switch_in_progress) { timeout((timeout_func_t)scrn_timer, 0, hz/10); *************** *** 2462,2471 **** static u_int chr = 0; next_code: ! kbd_wait(); ! /* first see if there is something in the keyboard port */ ! if (inb(KB_STAT) & KB_BUF_FULL) scancode = inb(KB_DATA); else if (flags & SCGETC_NONBLOCK) return(NOKEY); else --- 2477,2487 ---- static u_int chr = 0; next_code: ! /* check if there is anything in the keyboard buffer */ ! if (inb(KB_STAT) & KB_BUF_FULL) { ! DELAY(25); scancode = inb(KB_DATA); + } else if (flags & SCGETC_NONBLOCK) return(NOKEY); else *************** *** 2830,2836 **** console[0]->smode.mode == VT_AUTO) switch_scr(cur_console, 0); Debugger("manual escape to debugger"); - return(NOKEY); #else printf("No debugger in kernel\n"); #endif --- 2846,2851 ---- From owner-freebsd-current Thu Nov 14 10:11:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA22491 for current-outgoing; Thu, 14 Nov 1996 10:11:22 -0800 (PST) Received: from belgrath.widomaker.com (belgrath.widomaker.com [204.17.220.88]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA22461; Thu, 14 Nov 1996 10:10:55 -0800 (PST) Received: (from branson@localhost) by belgrath.widomaker.com (8.7.5/8.7.3) id NAA16148; Thu, 14 Nov 1996 13:10:29 -0500 (EST) Date: Thu, 14 Nov 1996 13:10:29 -0500 (EST) From: Branson Matheson To: Developer cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org, freebsd-chat@freebsd.org Subject: Re: PLEASE HELP - PROBLEM WITH NIS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 14 Nov 1996, Developer wrote: > > Does anyone know how I can get NIS to work correctly? I have to manually > kill -HUP ypserv every time an NIS password is changed or the system still > thinks it is the old one -- ypcat returns the old password??? > > I am using FreeBSD 2.2 -- the yp stuff is compiled from -current. > > Any help would be very helpful. > > Regards, > > Trefor S. Uhhh.. I have to ask .. are you running yppasswdd? if not then the passwords will not be updated. - branson From owner-freebsd-current Thu Nov 14 10:12:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA22699 for current-outgoing; Thu, 14 Nov 1996 10:12:52 -0800 (PST) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA22649; Thu, 14 Nov 1996 10:12:26 -0800 (PST) Message-Id: <199611141812.KAA22649@freefall.freebsd.org> To: Andreas Klemm cc: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= , current@freebsd.org, scsi@freebsd.org Subject: Re: SCB paging is ... (Interesting result) In-reply-to: Your message of "Thu, 14 Nov 1996 12:05:13 +0100." Date: Thu, 14 Nov 1996 10:12:22 -0800 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >On Wed, 13 Nov 1996, Justin T. Gibbs wrote: > >> Hmm. Does the patch I just posted have any effect on your timeouts? > >BTW, sorry, I didn't test your patch, yet. What do you think / expect: > >That with your patch tagged queuing will work ? Or should I enable >both: tagged queuing _and_ SCB paging ? Just try tagged queueing for the moment. After many different attempts with strange I/O loads, I was able to get SCB paging to die on me although I basically got timeouts and not inode death, so I'm not sure if it is the same problem as Andrey's. >-- >andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik Gmb >H > Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.d >e >pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by << >< >ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD << >< > -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Thu Nov 14 11:41:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA29417 for current-outgoing; Thu, 14 Nov 1996 11:41:43 -0800 (PST) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA29406; Thu, 14 Nov 1996 11:41:36 -0800 (PST) Received: from localhost (mark@localhost) by vinyl.quickweb.com (8.7.5/8.6.12) with SMTP id OAA22823; Thu, 14 Nov 1996 14:36:56 -0500 (EST) Date: Thu, 14 Nov 1996 14:36:55 -0500 (EST) From: Mark Mayo To: hackers@freebsd.org cc: current@freebsd.org Subject: userland PPP giving weird load numbers Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've had this problem since 2.1x, and it appaears to still happen occasionally in 2.2-ALPHA: mark:{105}/home/mark % w 8:14AM up 46 mins, 3 users, load averages: 0.99, 0.97, 0.88 USER TTY FROM LOGIN@ IDLE WHAT mark p1 :0.0 7:28AM 45 -tcsh (tcsh) mark p2 :0.0 7:28AM - w mark p3 :0.0 7:32AM 37 ppp the ppp process causes the high load (which isn't real, BTW). Top shows it as not doing a thing. As soon as I kill ppp off, the load drops right back down. A friend of mine gets the exact same thing regularily in 2.1.5, and although it rarely happens to me these days, it happens enough to make me curious about what's going on here :-) -mark --------------------------------------------------- | Mark Mayo mark@quickweb.com | | RingZero Comp. vinyl.quickweb.com/mark | --------------------------------------------------- "To iterate is human, to recurse divine." - L. Peter Deutsch From owner-freebsd-current Thu Nov 14 12:18:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA02356 for current-outgoing; Thu, 14 Nov 1996 12:18:51 -0800 (PST) Received: from ki1.chemie.fu-berlin.de (ki1.Chemie.FU-Berlin.DE [160.45.24.21]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA02346 for ; Thu, 14 Nov 1996 12:18:47 -0800 (PST) Received: by ki1.chemie.fu-berlin.de (Smail3.1.28.1) from mail.hanse.de (193.174.9.9) with smtp id ; Thu, 14 Nov 96 21:18 MET Received: from wavehh.UUCP by mail.hanse.de with UUCP for freebsd-current@freebsd.org id ; Thu, 14 Nov 96 21:18 MET Received: by wavehh.hanse.de (4.1/SMI-4.1) id AA16477; Thu, 14 Nov 96 21:14:51 +0100 From: cracauer@wavehh.hanse.de (Martin Cracauer) Message-Id: <9611142014.AA16477@wavehh.hanse.de> Subject: Re: EDO vs. other (Re: GigaByte GA-586DX-512 Motherboard) To: hsu@freefall.freebsd.org Date: Thu, 14 Nov 1996 21:14:50 +0100 (MET) Cc: wscott@ichips.intel.com, freebsd-current@freebsd.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Regarding my P6 Board, some people asked: it is named P6FX2-A, the vendor is called elitegroup at least here in Germany. I put the benchmark on http://www-intern.bik-gmbh.de/bench-ram.c Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://cracauer.cons.org Fax +49 40 522 85 36 From owner-freebsd-current Thu Nov 14 12:47:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA04234 for current-outgoing; Thu, 14 Nov 1996 12:47:56 -0800 (PST) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA04203 for ; Thu, 14 Nov 1996 12:47:49 -0800 (PST) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id PAA27723; Thu, 14 Nov 1996 15:46:39 -0500 From: Bill Paul Message-Id: <199611142046.PAA27723@skynet.ctr.columbia.edu> Subject: Re: PLEASE HELP - PROBLEM WITH NIS To: dev@fgate.flevel.co.uk (Developer) Date: Thu, 14 Nov 1996 15:46:38 -0500 (EST) Cc: freebsd-current@FreeBSD.org In-Reply-To: from "Developer" at Nov 14, 96 03:25:54 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Of all the gin joints in all the towns in all the world, Developer had to walk into mine and say: > > Does anyone know how I can get NIS to work correctly? I have to manually > kill -HUP ypserv every time an NIS password is changed or the system still > thinks it is the old one -- ypcat returns the old password??? > > I am using FreeBSD 2.2 -- the yp stuff is compiled from -current. > > Any help would be very helpful. > > Regards, > > Trefor S. Please don't crosspost stuff like this to three different mailing lists when only one applies. (You say you're running -current, yet you also posted to the freebsd-stable and freebsd-chat groups.) You need to tell me a little more about how you have NIS configured. The rpc.yppasswdd server in 2.2 can do updates in one of two ways: the usual 'modify the master.passwd file and run a make to update the maps' way or the in-place update way. It defaults to the 'normal way' unless you start rpc.yppasswdd with the -i flag, in which case it switches to in-place updates. In either case, rpc.yppasswdd is supposed to spawn a child and call the /usr/libexec/yppwupdate script, which in turn runs a make using /var/yp/Makefile. If you are using the 'normal' update method, the script will run a normal 'make' which will generate a new set of master.passwd and passwd maps from the /var/yp/master.passwd file. This is done using the yp_mkdb command. Once the new map is ready, yp_mkdb is invoked again with the -c flag, which sends a YPPROC_CLEAR request to ypserv. This is equivalent to kill -HUP for the FreeBSD ypserv (I rigged it up this way on purpose -- other ypserv inplementations don't honor SIGHUP like this). The YPPROC_CLEAR message tells ypserv to flush out its DB handle cache and reopen all the map databases again; since ypserv caches open DB handles, it has to be told to flush its cache otherwise it will continue to serve stale data. When you use in-place updates, the /usr/libexec/yppwupdate script calls a special taeget in /var/yp/Makefile called 'pushpw'. This target skips the map regeneration step since it's not necessary in this case: when doing in-place updates, rpc.yppasswdd modifies the master.passwd and passwd maps directly. (This is much faster for sites with very large user databases.) However the pushpw target is still supposed to call yp_mkdb -c in order to tell ypserv to flush its cache. Note also that /usr/libexec/ypxfr will send a YPPROC_CLEAR message to the local ypserv itself as the result of a map transfer. This is so that NIS slave servers will also know when to flush their caches after a new map has been transfered from the master. What seems to be happening is that ypserv is not getting the YPPROC_CLEAR message. The thing now is to figure out why. There are a couple of possible reasons: - Somehow, yp_mkdb is broken. You can test this by running yp_mkdb -c manually. Start ypserv with the -d flag to see debug messages, then run yp_mkdb -c from another session; ypserv should tell you when the YPPROC_CLEAR message is received. - rpc.yppasswdd is not calling /usr/libexec/yppwupdate, or /usr/libexec/yppwupdate is barfing somehow. I have a theory. I could _swear_ that DBLOAD in /var/yp/Makefile is specified with an absolute path. But I may be wrong. In that case, edit /usr/libexec/yppwupdate and fix the PATH defined there so that it includes /usr/sbin, which is where yp_mkdb lives. Other things to try: Run ypserv in debug mode with -d and rpc.yppasswdd in verbose mode with -v and pay attention to the output you see (rpc.yppasswdd syslogs messages to /var/log/messages). Try to do a password change and see what happens. Look at /var/yp/ypupdate.log for incriminating error messages. If you find a reproducable problem or error message, let me know. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "If you're ever in trouble, go to the CTR. Ask for Bill. He will help you." ============================================================================= From owner-freebsd-current Thu Nov 14 15:53:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA21838 for current-outgoing; Thu, 14 Nov 1996 15:53:34 -0800 (PST) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA21824 for ; Thu, 14 Nov 1996 15:53:23 -0800 (PST) Received: from Mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by Kitten.mcs.com (8.8.2/8.8.2) with ESMTP id RAA03473 for ; Thu, 14 Nov 1996 17:50:53 -0600 (CST) Received: from Jupiter.Mcs.Net (karl@Jupiter.mcs.net [192.160.127.88]) by Mailbox.mcs.com (8.8.2/8.8.2) with ESMTP id RAA19049 for ; Thu, 14 Nov 1996 17:50:52 -0600 (CST) Received: (from karl@localhost) by Jupiter.Mcs.Net (8.8.2/8.8.2) id RAA08015 for current@freebsd.org; Thu, 14 Nov 1996 17:50:51 -0600 (CST) From: Karl Denninger Message-Id: <199611142350.RAA08015@Jupiter.Mcs.Net> Subject: SERIOUS TCP problem in 3.0 and the new compiler To: current@freebsd.org Date: Thu, 14 Nov 1996 17:50:51 -0600 (CST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi folks, I have uncovered a very serious problem in the new compiler and/or libraries (at least, I think it is) in the -CURRENT branch. Unfortunately, I haven't been able to run it down as of yet. This is what happens: 1) Open a socket to a server, which forks off a copy of itself after accepting the socket connection. 2) Send LOTS (thousands) of transactions (a "transaction" is defined as transmission of one packet of data with a known size and prefix, the server end reads it, does something, and responds in some way with data). At some point a few thousand transactions into the process, you "lose" one of the responses. That is, the process which is doing the serving THINKS it wrote a response, but the CLIENT never gets it! Since this is a lock-step protocol, and we're relying on TCP to do the reliability part of data delivery, and no more than one request can ever be outstanding in this protocol, you're screwed. The process locks up hard. If we recompile under gcc 2.6.3, even running with a 3.0 (-current) kernel, the problem DOES NOT happen. If you compile under the current release (as of 11/11 at least) it *DOES* -- reliably. In both cases we're linked -static so that the binaries are portable, so the shared libraries should not be involved in this at all. The problem appears to be that somewhere along the line one packet in the TCP stream gets "lost" and never is delivered to the other end. Now, I've seen this in rlogin before -- a rlogin'd connection will just "hang" for no apparent reason, and sending something the other direction (ie: "~" -- not "~.", which would disconnect me, gets it going again). In this case the socket in question is full-duplex; we both read and write from it. Unfortuately, since the protocol is lock-step, I *can't* prime the channel at that point with a message in the opposite direction. This is a pretty serious problem folks. I've never seen anything like it before, but its definitely real and definitely a problem in the current source base. Again, this is NOT a library mismatch issue -- I linked the software in question static on our codebase machine and was able to reliably reproduce the problem. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1's from $600 monthly to FULL DS-3 Service | 32 Analog Prefixes, 13 ISDN, Web servers $75/mo Voice: [+1 312 803-MCS1 x219]| Email to "info@mcs.net" WWW: http://www.mcs.net/ Fax: [+1 312 248-9865] | 2 FULL DS-3 Internet links; 400Mbps B/W Internal From owner-freebsd-current Thu Nov 14 17:40:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA01003 for current-outgoing; Thu, 14 Nov 1996 17:40:02 -0800 (PST) Received: from bunyip.cc.uq.oz.au (daemon@bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA00970 for ; Thu, 14 Nov 1996 17:39:56 -0800 (PST) Received: (from daemon@localhost) by bunyip.cc.uq.oz.au (8.7.6/8.7.3) id LAA26401 for current@freebsd.org; Fri, 15 Nov 1996 11:39:51 +1000 Received: from pandora.devetir.qld.gov.au by ogre.devetir.qld.gov.au (8.7.5/DEVETIR-E0.3a) with ESMTP id LAA10447 for ; Fri, 15 Nov 1996 11:44:08 +1000 (EST) Received: from netfl15a.devetir.qld.gov.au (netfl15a.devetir.qld.gov.au [167.123.24.12]) by pandora.devetir.qld.gov.au (8.6.10/8.6.12) with ESMTP id LAA04350 for ; Fri, 15 Nov 1996 11:42:07 +1000 Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id BAA01827 for ; Fri, 15 Nov 1996 01:40:43 GMT Message-Id: <199611150140.BAA01827@netfl15a.devetir.qld.gov.au> X-Mailer: exmh version 1.6.5 12/11/95 To: current@freebsd.org Subject: Asse,mbler error messages for locore.s X-Face: 3}heU+2?b->-GSF-G4T4>jEB9~FR(V9lo&o>kAy=Pj&;oVOc<|pr%I/VSG"ZD32J>5gGC0N 7gj]^GI@M:LlqNd]|(2OxOxy@$6@/!,";-!OlucF^=jq8s57$%qXd/ieC8DhWmIy@J1AcnvSGV\|*! >Bvu7+0h4zCY^]{AxXKsDTlgA2m]fX$W@'8ev-Qi+-;%L'CcZ'NBL!@n?}q!M&Em3*eW7,093nOeV8 M)(u+6D;%B7j\XA/9j4!Gj~&jYzflG[#)E9sI&Xe9~y~Gn%fA7>F:YKr"Wx4cZU*6{^2ocZ!YyR Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 15 Nov 1996 11:40:43 +1000 From: Stephen Hocking Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk cc -c -x assembler-with-cpp -DLOCORE -nostdinc -I- -I. -I../.. -I../../../includ e -DNCONS=4 -DMFS -DNFS -DFFS -DTCP_COMPAT_42 -DINET -DPQ_MEDIUMCACHE -DCOMPAT_4 3 -DKERNEL ../../i386/i386/locore.s ../../i386/i386/locore.s: Assembler messages: ../../i386/i386/locore.s:528: Error: operands given don't match any known 386 in struction *** Error code 1 Stop. and the offending code is */ olddiskboot: movl 8(%ebp),%eax movl %eax,R(_boothowto) movl 12(%ebp),%eax movl %eax,R(_bootdev) #if defined(USERCONFIG_BOOT) && defined(USERCONFIG) movl $0x10200, %esi lea $R(_userconfig_from_boot),%edi <------- movl $512,%ecx cld rep movsb #endif /* USERCONFIG_BOOT */ ret Stephen -- The views expressed above are not those of the Worker's Compensation Board of Queensland, Australia. From owner-freebsd-current Thu Nov 14 17:45:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA01393 for current-outgoing; Thu, 14 Nov 1996 17:45:11 -0800 (PST) Received: from wgrobez1.remote.louisville.edu (wgrobez1.remote.louisville.edu [136.165.243.183]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA01387 for ; Thu, 14 Nov 1996 17:45:08 -0800 (PST) Received: from localhost (wangel@localhost) by wgrobez1.remote.louisville.edu (8.7.6/8.6.12) with SMTP id UAA17126 for ; Thu, 14 Nov 1996 20:45:20 -0500 (EST) Date: Thu, 14 Nov 1996 20:45:17 -0500 (EST) From: Gary Roberts To: freebsd-current@freebsd.org Subject: Argh .. Make world Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk DOH!@#!@!!@ 6 hours and 24 minutes into MAKE WORLD and it crashes :( Error follows: cc -O -c /usr/src/usr.sbin/pkg_install/lib/file.c: In function `fileGetURL': /usr/src/usr/sbin/pkg_install/lib/file.c:250: too many arguments to function `ftpGetURL' Uhm, is there anyway I can start where it left off ... 6 hours is a long time :D Thanks Gary Roberts System Admin. -- Altered Reality. http://136.165.243.183 -- Main User Pages From owner-freebsd-current Thu Nov 14 19:18:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA07194 for current-outgoing; Thu, 14 Nov 1996 19:18:51 -0800 (PST) Received: from rosemary.fsl.noaa.gov (rosemary.fsl.noaa.gov [137.75.8.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA07175; Thu, 14 Nov 1996 19:18:27 -0800 (PST) Received: from sage.fsl.noaa.gov (sage.fsl.noaa.gov [137.75.253.42]) by rosemary.fsl.noaa.gov (8.7.5/8.6.12) with SMTP id UAA25318; Thu, 14 Nov 1996 20:17:25 -0700 (MST) Message-ID: <328BE0C4.41C67EA6@fsl.noaa.gov> Date: Thu, 14 Nov 1996 20:17:24 -0700 From: Sean Kelly Organization: NOAA Forecast Systems Laboratory X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.1.5-RELEASE i386) MIME-Version: 1.0 To: Mark Mayo CC: hackers@FreeBSD.org, current@FreeBSD.org Subject: Re: userland PPP giving weird load numbers References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Mark Mayo wrote: > the ppp process causes the high load (which isn't real, BTW). Top shows it > as not doing a thing. As soon as I kill ppp off, the load drops right back > down. I see this too all the time, from 2.0.5 all the way to 2.1.5. While /usr/sbin/ppp is running, the load average hangs around 1.0. Sometimes, it'll drop. It's odd ... it's usually when ppp is idle that it hangs around 1.0. -- Sean Kelly NOAA Forecast Systems Laboratory Boulder Colorado USA From owner-freebsd-current Thu Nov 14 20:25:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA10639 for current-outgoing; Thu, 14 Nov 1996 20:25:03 -0800 (PST) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA10627 for ; Thu, 14 Nov 1996 20:24:23 -0800 (PST) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id UAA01844; Thu, 14 Nov 1996 20:23:43 -0800 (PST) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma001842; Thu Nov 14 20:23:32 1996 Received: (from archie@localhost) by bubba.whistle.com (8.7.5/8.6.12) id UAA19805; Thu, 14 Nov 1996 20:23:32 -0800 (PST) From: Archie Cobbs Message-Id: <199611150423.UAA19805@bubba.whistle.com> Subject: Re: SERIOUS TCP problem in 3.0 and the new compiler In-Reply-To: <199611142350.RAA08015@Jupiter.Mcs.Net> from Karl Denninger at "Nov 14, 96 05:50:51 pm" To: karl@Mcs.Net (Karl Denninger) Date: Thu, 14 Nov 1996 20:23:32 -0800 (PST) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I have uncovered a very serious problem in the new compiler and/or libraries > (at least, I think it is) in the -CURRENT branch. > > Unfortunately, I haven't been able to run it down as of yet. > > This is what happens: > > 1) Open a socket to a server, which forks off a copy of itself after > accepting the socket connection. > 2) Send LOTS (thousands) of transactions (a "transaction" is defined > as transmission of one packet of data with a known size and prefix, > the server end reads it, does something, and responds in some way > with data). > > At some point a few thousand transactions into the process, you "lose" one > of the responses. That is, the process which is doing the serving THINKS it > wrote a response, but the CLIENT never gets it! > > Since this is a lock-step protocol, and we're relying on TCP to do the > reliability part of data delivery, and no more than one request can ever be > outstanding in this protocol, you're screwed. The process locks up hard. > > If we recompile under gcc 2.6.3, even running with a 3.0 (-current) kernel, > the problem DOES NOT happen. If you compile under the current release (as > of 11/11 at least) it *DOES* -- reliably. Can you provide some sample code, ie., the smallest piece(s) of code that reproduce the problem? -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com From owner-freebsd-current Thu Nov 14 20:44:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA11609 for current-outgoing; Thu, 14 Nov 1996 20:44:50 -0800 (PST) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA11547 for ; Thu, 14 Nov 1996 20:44:15 -0800 (PST) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id UAA01939 for ; Thu, 14 Nov 1996 20:43:44 -0800 (PST) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma001937; Thu Nov 14 20:43:39 1996 Received: (from archie@localhost) by bubba.whistle.com (8.7.5/8.6.12) id UAA19871 for freebsd-current@freebsd.org; Thu, 14 Nov 1996 20:43:39 -0800 (PST) From: Archie Cobbs Message-Id: <199611150443.UAA19871@bubba.whistle.com> Subject: vi complaints To: freebsd-current@freebsd.org Date: Thu, 14 Nov 1996 20:43:39 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk People are sensitive about their text editors. I'm no exception... :-) The new "vi" has two new flaws IMHO... o The ESC timeout is too short. My definition of too short is that when you're telneted to another machine on the same Ethernet segment, and up arrow sometimes gets misinterpreted as ESC, A, causing it to open a new line, insert an A, etc. etc. o Sometimes when I exit out (maybe via control-z) it displays some message in reverse video at the bottom, but forgets to reverse it back, so now everything on the command line is in reverse video. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com From owner-freebsd-current Thu Nov 14 20:56:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA12532 for current-outgoing; Thu, 14 Nov 1996 20:56:42 -0800 (PST) Received: from waru.life.nthu.edu.tw (waru.life.nthu.edu.tw [140.114.98.107]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA12510 for ; Thu, 14 Nov 1996 20:56:25 -0800 (PST) Received: from waru.life.nthu.edu.tw (waru.life.nthu.edu.tw [140.114.98.107]) by waru.life.nthu.edu.tw (8.7.6/8.7.3) with SMTP id MAA07641 for ; Fri, 15 Nov 1996 12:57:49 +0800 (CST) Date: Fri, 15 Nov 1996 12:57:49 +0800 (CST) From: Frank Chen-Hsiung Chan To: freebsd-current@freebsd.org Subject: fast libm? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Our lab is planning to buy some PPro for scientific calculation. We have previously test the performance of a PPro 200 running FreeBSD and another running Linux. The performance in the Linux box is 2 times faster than the FreeBSD box. Through some investigation, we have found that the problem is due to the math library. The Linux libm is optimized for i386 machine, and written in assembly. Whereas FreeBSD libm is written entirely in C. Personally I favor the FreeBSD, but calculation speed is the major concern. I wonder whether there's anyone trying to optimize libm in FreeBSD? I believe this will extend the use of FreeBSD in scientific realms. BTW, if the FPU option in /etc/make.conf is not turned on, the FreeBSD performance will be 9 times slower than Linux (in Math calculations). -- Frank Chen Hsiung Chan | ------------------------------+--------------------------------- Department of Life Science | frankch@waru.life.nthu.edu.tw National Tsing Hua University | http://waru.life.nthu.edu.tw/ Taiwan | From owner-freebsd-current Thu Nov 14 23:02:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA20622 for current-outgoing; Thu, 14 Nov 1996 23:02:43 -0800 (PST) Received: from casparc.ppp.net (casparc.ppp.net [194.64.12.35]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA20576; Thu, 14 Nov 1996 23:02:24 -0800 (PST) Received: from ernie by casparc.ppp.net with uucp (Smail3.1.28.1 #1) id m0vOIHq-000I9dC; Fri, 15 Nov 96 08:02 MET Received: by ernie.kts.org (Smail3.1.29.1 #5) id m0vOHoc-00001bC; Fri, 15 Nov 96 07:31 MET Message-Id: From: hm@kts.org (Hellmuth Michaelis) Subject: Re: userland PPP giving weird load numbers To: kelly@fsl.noaa.gov (Sean Kelly) Date: Fri, 15 Nov 1996 07:31:50 +0100 (MET) Cc: mark@quickweb.com, hackers@FreeBSD.org, current@FreeBSD.org In-Reply-To: <328BE0C4.41C67EA6@fsl.noaa.gov> from "Sean Kelly" at Nov 14, 96 08:17:24 pm Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Sean Kelly wrote: > > Mark Mayo wrote: > > > the ppp process causes the high load (which isn't real, BTW). Top shows it > > as not doing a thing. As soon as I kill ppp off, the load drops right back > > down. > > I see this too all the time, from 2.0.5 all the way to 2.1.5. While > /usr/sbin/ppp is running, the load average hangs around 1.0. Sometimes, > it'll drop. It's odd ... it's usually when ppp is idle that it hangs > around 1.0. I had this phenomenon too - but NOT with ppp. An isdn userland daemon i am working on showed this exact behaviour; when it was running, the system load was constantly 1.0 or very nearby. This all is under 2.1.5 (and 2.1 too). The process wasn't doing anything (or very little). My impression is that there is something wrong in the kernel, not in the applications. hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe (A)bort, (R)etry, (I)nstall BSD ? -------------------------------------------------------------------------------- kts.org will move and will be not available from November 20th for 10 days -------------------------------------------------------------------------------- From owner-freebsd-current Thu Nov 14 23:56:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA23966 for current-outgoing; Thu, 14 Nov 1996 23:56:25 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA23951; Thu, 14 Nov 1996 23:56:20 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id SAA06861; Fri, 15 Nov 1996 18:26:02 +1030 (CST) From: Michael Smith Message-Id: <199611150756.SAA06861@genesis.atrad.adelaide.edu.au> Subject: Re: userland PPP giving weird load numbers In-Reply-To: from Hellmuth Michaelis at "Nov 15, 96 07:31:50 am" To: hm@kts.org Date: Fri, 15 Nov 1996 18:26:01 +1030 (CST) Cc: kelly@fsl.noaa.gov, mark@quickweb.com, hackers@FreeBSD.org, current@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-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hellmuth Michaelis stands accused of saying: > > > > I see this too all the time, from 2.0.5 all the way to 2.1.5. While > > /usr/sbin/ppp is running, the load average hangs around 1.0. Sometimes, > > it'll drop. It's odd ... it's usually when ppp is idle that it hangs > > around 1.0. > > I had this phenomenon too - but NOT with ppp. An isdn userland daemon i am > working on showed this exact behaviour; when it was running, the system load > was constantly 1.0 or very nearby. This all is under 2.1.5 (and 2.1 too). > The process wasn't doing anything (or very little). But what _was_ it supposed to be doing? > My impression is that there is something wrong in the kernel, not in the > applications. I'd be inclined to say that there's something wrong in the applications, not in the kernel, actually. There's a chance that you have a driver problem (perhaps a broken select() handler), but the major causes of this sort of thing are applications failing to realise that a 0 return from a read() indicates EOF. Another possible is not checking all the bits enabled for a select(). Why not be a bit intelligent; attach a debugger to the offending process and wait for it to go gaga, then look at it to see what it's doing? > Hellmuth Michaelis -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Fri Nov 15 06:02:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA14643 for current-outgoing; Fri, 15 Nov 1996 06:02:32 -0800 (PST) Received: from casparc.ppp.net (casparc.ppp.net [194.64.12.35]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA14633; Fri, 15 Nov 1996 06:02:25 -0800 (PST) Received: from ernie by casparc.ppp.net with uucp (Smail3.1.28.1 #1) id m0vOOqI-000I9vC; Fri, 15 Nov 96 15:02 MET Received: by ernie.kts.org (Smail3.1.29.1 #5) id m0vOMhn-00001bC; Fri, 15 Nov 96 12:45 MET Message-Id: From: hm@kts.org (Hellmuth Michaelis) Subject: Re: userland PPP giving weird load numbers To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Fri, 15 Nov 1996 12:45:06 +0100 (MET) Cc: hm@kts.org, kelly@fsl.noaa.gov, mark@quickweb.com, hackers@FreeBSD.org, current@FreeBSD.org In-Reply-To: <199611150756.SAA06861@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Nov 15, 96 06:26:01 pm Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > > I see this too all the time, from 2.0.5 all the way to 2.1.5. While > > > /usr/sbin/ppp is running, the load average hangs around 1.0. Sometimes, > > > it'll drop. It's odd ... it's usually when ppp is idle that it hangs > > > around 1.0. > > > > I had this phenomenon too - but NOT with ppp. An isdn userland daemon i am > > working on showed this exact behaviour; when it was running, the system load > > was constantly 1.0 or very nearby. This all is under 2.1.5 (and 2.1 too). > > The process wasn't doing anything (or very little). > > But what _was_ it supposed to be doing? Ok, when this happened, the daemon was in a tight read() loop, where the read() timed out every second in the driver. Basically after implementing select() in the driver and using that with a one second timeout made the problem go away. In the whole application several one second timeouts exists at several drivers in the kernel - i'm quite shure there is a problem with something like several timeouts timing out simultaneously causing something. I just ran out of ideas where to search for and what to search for so i stopped looking for the real problem. But i'm able to reproduce it. hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe (A)bort, (R)etry, (I)nstall BSD ? -------------------------------------------------------------------------------- kts.org will move and will be not available from November 20th for 10 days -------------------------------------------------------------------------------- From owner-freebsd-current Fri Nov 15 07:04:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA18717 for current-outgoing; Fri, 15 Nov 1996 07:04:12 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA18671 for ; Fri, 15 Nov 1996 07:04:04 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id CAA16104; Sat, 16 Nov 1996 02:01:46 +1100 Date: Sat, 16 Nov 1996 02:01:46 +1100 From: Bruce Evans Message-Id: <199611151501.CAA16104@godzilla.zeta.org.au> To: frankch@waru.life.nthu.edu.tw, freebsd-current@FreeBSD.org Subject: Re: fast libm? Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Our lab is planning to buy some PPro for scientific calculation. > We have previously test the performance of a PPro 200 running > FreeBSD and another running Linux. > > The performance in the Linux box is 2 times faster than the > FreeBSD box. Through some investigation, we have found that the > problem is due to the math library. The Linux libm is optimized > for i386 machine, and written in assembly. Whereas FreeBSD libm > is written entirely in C. Are you benchmarking it with your applications? It is possible to make the FreeBSD library look very bad by using a benchmark biased towards the slowest functions in it, but I think the slowest functions are rarely used. FPU-intensive code tends to be limited by memory bandwidth anyway. I hope the Linux libm isn't optimized for i386's - i386's don't even have FPU's, and PPro's are quite different. The FreeBSD libm is not entirely written in C - most of the functions directly supported by the FPU are written in assembler and the assembler versions are used if HAVE_FPU is defined in /etc/make.conf. > I wonder whether there's anyone trying to optimize libm in > FreeBSD? I believe this will extend the use of FreeBSD in > scientific realms. Someone who uses it a lot will have to do it. Bruce From owner-freebsd-current Fri Nov 15 07:28:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA20440 for current-outgoing; Fri, 15 Nov 1996 07:28:27 -0800 (PST) Received: from nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA20430 for ; Fri, 15 Nov 1996 07:28:16 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by nike.efn.org (8.7.5/8.7.3) with SMTP id HAA12425; Fri, 15 Nov 1996 07:27:48 -0800 (PST) Date: Fri, 15 Nov 1996 07:27:46 -0800 (PST) From: John-Mark Gurney X-Sender: jmg@nike Reply-To: John-Mark Gurney To: Bill Paul cc: Developer , freebsd-current@FreeBSD.org Subject: Re: PLEASE HELP - PROBLEM WITH NIS In-Reply-To: <199611142046.PAA27723@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 14 Nov 1996, Bill Paul wrote: > - Somehow, yp_mkdb is broken. You can test this by running yp_mkdb -c > manually. Start ypserv with the -d flag to see debug messages, then > run yp_mkdb -c from another session; ypserv should tell you when the > YPPROC_CLEAR message is received. thank you for this hit... I decided to take a look at /var/yp/Makefile (as I was having this same problem)... and found that yp_mkdb was not being run with the -c flag... I simply added that and now it all works as it should... just for your information I'm running 960801-SNAP... thanks for your words of advise... ttyl... John-Mark gurney_j@efn.org http://resnet.uoregon.edu/~gurney_j/ Modem/FAX: (541) 683-6954 (FreeBSD Box) Live in Peace, destroy Micro$oft, support free software, run FreeBSD (unix) From owner-freebsd-current Fri Nov 15 07:55:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA22757 for current-outgoing; Fri, 15 Nov 1996 07:55:01 -0800 (PST) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA22725 for ; Fri, 15 Nov 1996 07:54:46 -0800 (PST) Received: by halloran-eldar.lcs.mit.edu; (5.65v3.2/1.1.8.2/19Aug95-0530PM) id AA08798; Fri, 15 Nov 1996 10:54:27 -0500 Date: Fri, 15 Nov 1996 10:54:27 -0500 From: Garrett Wollman Message-Id: <9611151554.AA08798@halloran-eldar.lcs.mit.edu> To: current@freebsd.org Subject: [Martha M. Gray: Availability of NIST-PCTS:151-2] Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Like it says.... ------- start of forwarded message (RFC 934 encapsulation) ------- Message-Id: <9611151534.AA16863@sst.ncsl.nist.gov> From: gray@sst.ncsl.nist.gov (Martha M. Gray) To: ron@caldera.com, kurt.fuchs@aut.alcatel.at, tudor@cs.unh.edu, rh@unifix.de, bruce@pixar.com, csapuntz@mit.edu, tytso@mit.edu, jmb@frb.gov, chet@po.cwru.edu, sprice@hiwaay.net, terry@lambert.org, meyering@asic.sc.ti.com, ralf@julia.de, jtc@cygnus.com, alex@freebsd.org, dyson@freebsd.org, wollman@lcs.mit.edu, stephe@softway.com, nicole@craftwork.com, tholo@tetherless.com, adam@yggdrasil.com, gray@sst.ncsl.nist.gov Subject: Availability of NIST-PCTS:151-2 Date: Fri, 15 Nov 96 10:34:49 EST Date: November 15, 1996 >From: Marty Gray Conformance Testing Group Subject: Availability of NIST-PCTS:151-2 The final version of the NIST POSIX Conformance Test Suite for FIPS 151-2 (Version 1.8, October 1, 1995) is now available on the WWW. Availability in no longer encumbered by fees. Support for this POSIX Conformance Test Suite (PCTS) is only provided to the Accredited POSIX Testing Laboratories (APTLs). Only APTLs may submit Test Reports for the purpose of obtaining a Certificate of Validation. This PCTS and its associated documents are available for download via the URL: http://www.itl.nist.gov/div897/ctg/posix_form.htm - ---------------------------------------------------------------- Mrs. Martha M. Gray National Institute of Standards and Technology Bldg. 820 Rm. 517 Gaithersburg, MD 20899 Phone: 301-975-3276 email: martha.gray@nist.gov FAX: 301-926-3696 - ----------------------------------------------------------------  ------- end ------- From owner-freebsd-current Fri Nov 15 08:01:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA23326 for current-outgoing; Fri, 15 Nov 1996 08:01:53 -0800 (PST) Received: from jack.colorado.edu (jack.Colorado.EDU [128.138.149.29]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA23321 for ; Fri, 15 Nov 1996 08:01:43 -0800 (PST) Received: from jack (localhost [127.0.0.1]) by jack.colorado.edu (8.7.6/8.7.3/CNS-4.0p) with SMTP id JAA04880; Fri, 15 Nov 1996 09:00:44 -0700 (MST) Message-ID: <328C93AC.4C5E@Colorado.EDU> Date: Fri, 15 Nov 1996 09:00:44 -0700 From: "Mark O'Lear" Organization: University of Colorado X-Mailer: Mozilla 3.0Gold (X11; I; SunOS 5.4 sun4m) MIME-Version: 1.0 To: Archie Cobbs CC: freebsd-current@FreeBSD.ORG Subject: Re: vi complaints References: <199611150443.UAA19871@bubba.whistle.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Archie Cobbs wrote: > > People are sensitive about their text editors. > > I'm no exception... :-) > > The new "vi" has two new flaws IMHO... > > o The ESC timeout is too short. My definition of too short is > that when you're telneted to another machine on the same > Ethernet segment, and up arrow sometimes gets misinterpreted > as ESC, A, causing it to open a new line, insert an A, etc. etc. > > o Sometimes when I exit out (maybe via control-z) it displays some > message in reverse video at the bottom, but forgets to reverse > it back, so now everything on the command line is in reverse video. > > -Archie > > ___________________________________________________________________________ > Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com >From the vi man page: keytime [6] The 10th's of a second ex/vi waits for a subsequent key to complete a key mapping. What is your 'keytime' set for? (do a ':set keytime' from vi). This may be too low, you can always set it higher in your .exrc file (put a line 'set keytime=10' or some appropriate value for your configuration). -- Mark O'Lear \ e-mail: Mark.Olear@Colorado.EDU University of Colorado \ phone: (303) 492-3798 Telecomm. Svcs. (CB 313) \ fax: (303) 492-5105 Boulder, CO 80309 \ From owner-freebsd-current Fri Nov 15 08:10:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA24433 for current-outgoing; Fri, 15 Nov 1996 08:10:53 -0800 (PST) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA24403 for ; Fri, 15 Nov 1996 08:10:46 -0800 (PST) Received: from Mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by Kitten.mcs.com (8.8.2/8.8.2) with ESMTP id KAA01107; Fri, 15 Nov 1996 10:10:43 -0600 (CST) Received: from Mercury.mcs.net (karl@Mercury.mcs.com [192.160.127.80]) by Mailbox.mcs.com (8.8.2/8.8.2) with ESMTP id KAA26703; Fri, 15 Nov 1996 10:10:40 -0600 (CST) Received: (from karl@localhost) by Mercury.mcs.net (8.8.2/8.8.2) id KAA21074; Fri, 15 Nov 1996 10:10:39 -0600 (CST) From: Karl Denninger Message-Id: <199611151610.KAA21074@Mercury.mcs.net> Subject: Re: SERIOUS TCP problem in 3.0 and the new compiler To: archie@whistle.com (Archie Cobbs) Date: Fri, 15 Nov 1996 10:10:39 -0600 (CST) Cc: karl@Mcs.Net, current@freebsd.org In-Reply-To: <199611150423.UAA19805@bubba.whistle.com> from "Archie Cobbs" at Nov 14, 96 08:23:32 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Unfortunately, I haven't been able to run it down as of yet. > > > > This is what happens: > > > > 1) Open a socket to a server, which forks off a copy of itself after > > accepting the socket connection. > > 2) Send LOTS (thousands) of transactions (a "transaction" is defined > > as transmission of one packet of data with a known size and prefix, > > the server end reads it, does something, and responds in some way > > with data). > > > > At some point a few thousand transactions into the process, you "lose" one > > of the responses. That is, the process which is doing the serving THINKS it > > wrote a response, but the CLIENT never gets it! > > > > Since this is a lock-step protocol, and we're relying on TCP to do the > > reliability part of data delivery, and no more than one request can ever be > > outstanding in this protocol, you're screwed. The process locks up hard. > > > > If we recompile under gcc 2.6.3, even running with a 3.0 (-current) kernel, > > the problem DOES NOT happen. If you compile under the current release (as > > of 11/11 at least) it *DOES* -- reliably. > > Can you provide some sample code, ie., the smallest piece(s) of code > that reproduce the problem? > > -Archie Working on it. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1's from $600 monthly to FULL DS-3 Service | 33 Analog Prefixes, 13 ISDN, Web servers $75/mo Voice: [+1 312 803-MCS1 x219]| Email to "info@mcs.net" WWW: http://www.mcs.net/ Fax: [+1 312 248-9865] | 2 FULL DS-3 Internet links; 400Mbps B/W Internal From owner-freebsd-current Fri Nov 15 08:37:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA27331 for current-outgoing; Fri, 15 Nov 1996 08:37:04 -0800 (PST) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA27303 for ; Fri, 15 Nov 1996 08:36:54 -0800 (PST) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id QAA03257 for ; Fri, 15 Nov 1996 16:38:24 GMT Date: Fri, 15 Nov 1996 16:38:24 +0000 (GMT) From: Developer To: freebsd-current@freebsd.org Subject: HELP with dialup Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm trying to setup a modem on a freebsd-current system for use with dialup. The problem is that whenever we connect to the USR robotics 28K modem from a non-USR modem it just gives junk!! What is the correct way for doing this -- we have a getty entry for tty01 as std.38400. Regards, Trefor S. From owner-freebsd-current Fri Nov 15 09:03:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA29793 for current-outgoing; Fri, 15 Nov 1996 09:03:26 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA29767 for ; Fri, 15 Nov 1996 09:03:15 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id DAA19190; Sat, 16 Nov 1996 03:55:55 +1100 Date: Sat, 16 Nov 1996 03:55:55 +1100 From: Bruce Evans Message-Id: <199611151655.DAA19190@godzilla.zeta.org.au> To: cracauer@wavehh.hanse.de, freebsd-current@FreeBSD.org Subject: Re: EDO vs. other (Re: GigaByte GA-586DX-512 Motherboard) Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >I just ran that famous RAM benchmark that came down -hackers some time >ago: Infamous? :-) >normal parity RAM (8x 32 MB installed) >49005fb0 0.160 uS/op 6.24e+06 op/S 23.805 Mb/S >8938c0df 0.369 uS/op 2.71e+06 op/S 10.338 Mb/S >49005fb0 0.160 uS/op 6.24e+06 op/S 23.806 Mb/S >8938c0df 0.369 uS/op 2.71e+06 op/S 10.337 Mb/S > >EDO w/o Parity (2x 16 MB installed) >49005fb0 0.159 uS/op 6.29e+06 op/S 23.999 Mb/S >8938c0df 0.366 uS/op 2.73e+06 op/S 10.421 Mb/S >49005fb0 0.159 uS/op 6.29e+06 op/S 23.999 Mb/S >8938c0df 0.366 uS/op 2.73e+06 op/S 10.422 Mb/S I forget exactly what this does. I guess it does a lot of random accesses. Random access is not the strongest point of RAM :-). >I don't beleive one can speed up any real application using EDO. It speeds up copying of large amounts of data in the kernel by 5-10% (from 75MB/sec to > 80MB/sec for uncached memory on ASUS Triton 1 P133 systems). This might show up in real applications that read a lot of data from fast disks. Bruce From owner-freebsd-current Fri Nov 15 09:19:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA00773 for current-outgoing; Fri, 15 Nov 1996 09:19:03 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA00768 for ; Fri, 15 Nov 1996 09:18:49 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0vORuL-0005Dp-00; Fri, 15 Nov 1996 10:18:25 -0700 To: Developer Subject: Re: HELP with dialup Cc: freebsd-current@freebsd.org In-reply-to: Your message of "Fri, 15 Nov 1996 16:38:24 GMT." References: Date: Fri, 15 Nov 1996 10:18:25 -0700 From: Warner Losh Message-Id: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message Developer writes: : I'm trying to setup a modem on a freebsd-current system for use with : dialup. The problem is that whenever we connect to the USR robotics 28K : modem from a non-USR modem it just gives junk!! Which type of USR modem? The sportster or the courier? The sportster works great to dial out, but we've had intermittent problems with it answering the phones. We've had problems with getting bogus 33.6 modems from USR that had to be returned they were so broken. :-(. : What is the correct way for doing this -- we have a getty entry for tty01 : as std.38400. I think you'll be happier with std.115200. Warner From owner-freebsd-current Fri Nov 15 09:36:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA01818 for current-outgoing; Fri, 15 Nov 1996 09:36:15 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA01773 for ; Fri, 15 Nov 1996 09:36:05 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA12169; Fri, 15 Nov 1996 10:36:02 -0700 (MST) Date: Fri, 15 Nov 1996 10:36:02 -0700 (MST) Message-Id: <199611151736.KAA12169@rocky.mt.sri.com> From: Nate Williams To: current@freebsd.org Subject: UserConfig is broken + PS/2 support success Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk UserConfig is now broken in current. It may have to do withe the recent syscons changes, but in any case nothing happens at the "config>" prompt when I type anymore. The sources are from early this morning, so it's probably a fairly recent change. On a positive note, the new PS/2 + syscons + shared KBD code seems to work fine on my PS/2 systems. The mouse is (correctly) found, and the keyboard works fine if I skip UserConfig and boot straight into the normal boot process. (Once I get into UserConfig I'm hosed since I can't even tell it to continue). Nate From owner-freebsd-current Fri Nov 15 10:10:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA04529 for current-outgoing; Fri, 15 Nov 1996 10:10:15 -0800 (PST) Received: from ec.camitel.com (ec.camitel.com [206.231.123.130]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA04473 for ; Fri, 15 Nov 1996 10:09:54 -0800 (PST) Received: (from cfortin@localhost) by ec.camitel.com (8.7.5/8.7.3) id NAA01638; Fri, 15 Nov 1996 13:07:47 -0500 (EST) From: Christian Fortin Message-ID: X-Mailer: XFMail 0.4 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 15 Nov 1996 12:34:24 -0500 (EST) Organization: =?us-ascii?Q?=C9lectro-Concepti= To: undisclosed-recipients:; Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk on?= From: Christian Fortin To: Warner Losh Subject: Re: HELP with dialup Cc: Developer , freebsd-current@freebsd.org I have the same problem with USR,... Many incompatibility problem between USR !!! Dial out , no problem, Dial-in many problem happen... - Must dial 2 time for connect ( First time the modem hangup ) - Transmission stop for no reason, it restart after few second... - I have upgrade my USR Bios, whitout succes... Try ZyXel modem, it definitively work better I have change all my pool of modem for this modem, it work fine... Usualy with Sportster I download the /kernel at 3K/s With ZyXel I reach 4.1K/s When a dial-in connection is done, a USR dial-in modem say = CONNECT 33600 but ZyXel say CONNECT 24600 But ZyXel is definitively more faster... With his auto-speed adjust... On 15-Nov-96 Warner Losh wrote: >>In message > Developer >writes: >: I'm trying to setup a modem on a freebsd-current system for use with >: dialup. The problem is that whenever we connect to the USR robotics 28K >: modem from a non-USR modem it just gives junk!! > >Which type of USR modem? The sportster or the courier? The sportster >works great to dial out, but we've had intermittent problems with >it answering the phones. We've had problems with getting bogus 33.6 >modems from USR that had to be returned they were so broken. :-(. > >: What is the correct way for doing this -- we have a getty entry for tty01 >: as std.38400. > >I think you'll be happier with std.115200. > >Warner ---------------------------------- E-Mail: Christian Fortin Date: 11/15/96 Heure: 12:34:24 ##################################################--------+ Electro-Conception tel:(418) 872-6641 | 3665 Croisset fax:(418) 872-9198 | Quebec,P.Q. www.ec.camitel.com/ec | Canada ftp.ec.camitel.com | G1P-1L4 | /----|<|----WM--|(--J --------------------------L---WM-----< \----1 --- - From owner-freebsd-current Fri Nov 15 10:29:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA06360 for current-outgoing; Fri, 15 Nov 1996 10:29:21 -0800 (PST) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA06338 for ; Fri, 15 Nov 1996 10:29:06 -0800 (PST) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id KAA05311; Fri, 15 Nov 1996 10:28:32 -0800 (PST) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma005305; Fri Nov 15 10:28:03 1996 Received: (from archie@localhost) by bubba.whistle.com (8.7.5/8.6.12) id KAA21383; Fri, 15 Nov 1996 10:28:03 -0800 (PST) From: Archie Cobbs Message-Id: <199611151828.KAA21383@bubba.whistle.com> Subject: Re: vi complaints In-Reply-To: <328C93AC.4C5E@Colorado.EDU> from Mark O'Lear at "Nov 15, 96 09:00:44 am" To: Mark.Olear@Colorado.EDU (Mark O'Lear) Date: Fri, 15 Nov 1996 10:28:03 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > keytime [6] > The 10th's of a second ex/vi waits for a subsequent key to > complete > a key mapping. > > What is your 'keytime' set for? (do a ':set keytime' from > vi). This may be too low, you can always set it higher > in your .exrc file (put a line 'set keytime=10' or some > appropriate value for your configuration). It doesn't seem to have any effect. I did "set keytime=30" and still it turns up arrow into open line, insert 'A' ... and it's happening almost immediately. ?? -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com From owner-freebsd-current Fri Nov 15 10:52:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA07856 for current-outgoing; Fri, 15 Nov 1996 10:52:15 -0800 (PST) Received: from sumatra.americantv.com (sumatra.americantv.com [199.184.181.250]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA07816 for ; Fri, 15 Nov 1996 10:51:58 -0800 (PST) Received: from right.PCS (right.pcs. [148.105.10.31]) by sumatra.americantv.com (8.7.6/8.7.3) with ESMTP id MAA11572; Fri, 15 Nov 1996 12:11:52 -0600 (CST) Received: (jlemon@localhost) by right.PCS (8.6.13/8.6.4) id SAA14380; Fri, 15 Nov 1996 18:50:01 GMT Message-Id: <199611151850.SAA14380@right.PCS> Date: Fri, 15 Nov 1996 12:50:01 -0600 From: jlemon@americantv.com (Jonathan Lemon) To: archie@whistle.com (Archie Cobbs) Cc: Mark.Olear@Colorado.EDU (Mark O'Lear), freebsd-current@FreeBSD.org Subject: Re: vi complaints References: <328C93AC.4C5E@Colorado.EDU> <199611151828.KAA21383@bubba.whistle.com> X-Mailer: Mutt 0.48.1 Mime-Version: 1.0 In-Reply-To: <199611151828.KAA21383@bubba.whistle.com>; from Archie Cobbs on Nov 15, 1996 10:28:03 -0800 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Archie Cobbs writes: > > It doesn't seem to have any effect. I did "set keytime=30" and > still it turns up arrow into open line, insert 'A' ... and it's > happening almost immediately. Use "set escapetime=30", in your .exrc file. -- Jonathan From owner-freebsd-current Fri Nov 15 10:58:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA08303 for current-outgoing; Fri, 15 Nov 1996 10:58:41 -0800 (PST) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA08296 for ; Fri, 15 Nov 1996 10:58:34 -0800 (PST) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id KAA05546; Fri, 15 Nov 1996 10:58:02 -0800 (PST) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma005544; Fri Nov 15 10:57:47 1996 Received: (from archie@localhost) by bubba.whistle.com (8.7.5/8.6.12) id KAA24145; Fri, 15 Nov 1996 10:57:47 -0800 (PST) From: Archie Cobbs Message-Id: <199611151857.KAA24145@bubba.whistle.com> Subject: Re: vi complaints In-Reply-To: <199611151850.SAA14380@right.PCS> from Jonathan Lemon at "Nov 15, 96 12:50:01 pm" To: jlemon@americantv.com (Jonathan Lemon) Date: Fri, 15 Nov 1996 10:57:46 -0800 (PST) Cc: archie@whistle.com, Mark.Olear@Colorado.EDU, freebsd-current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > It doesn't seem to have any effect. I did "set keytime=30" and > > still it turns up arrow into open line, insert 'A' ... and it's > > happening almost immediately. > > Use "set escapetime=30", in your .exrc file. set escapetime does the trick.. thanks! -archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com From owner-freebsd-current Fri Nov 15 11:06:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA08675 for current-outgoing; Fri, 15 Nov 1996 11:06:09 -0800 (PST) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA08666 for ; Fri, 15 Nov 1996 11:06:01 -0800 (PST) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id NAA28512; Fri, 15 Nov 1996 13:04:46 -0600 From: Joe Greco Message-Id: <199611151904.NAA28512@brasil.moneng.mei.com> Subject: Re: HELP with dialup To: imp@village.org (Warner Losh) Date: Fri, 15 Nov 1996 13:04:45 -0600 (CST) Cc: dev@fgate.flevel.co.uk, freebsd-current@freebsd.org In-Reply-To: from "Warner Losh" at Nov 15, 96 10:18:25 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > In message > Developer > writes: > : I'm trying to setup a modem on a freebsd-current system for use with > : dialup. The problem is that whenever we connect to the USR robotics 28K > : modem from a non-USR modem it just gives junk!! > > Which type of USR modem? The sportster or the courier? The sportster > works great to dial out, but we've had intermittent problems with > it answering the phones. We've had problems with getting bogus 33.6 > modems from USR that had to be returned they were so broken. :-(. > > : What is the correct way for doing this -- we have a getty entry for tty01 > : as std.38400. > > I think you'll be happier with std.115200. That might actually be the problem... In any case. Is the modem set up correctly? (Taking it out of the box and setting the DIP switches does not count). I posted a bunch of initialization strings here the other day... ... JG From owner-freebsd-current Fri Nov 15 13:18:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA16855 for current-outgoing; Fri, 15 Nov 1996 13:18:01 -0800 (PST) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA16850 for ; Fri, 15 Nov 1996 13:17:57 -0800 (PST) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.6/8.7.3) with ESMTP id NAA21083; Fri, 15 Nov 1996 13:16:08 -0800 (PST) Message-Id: <199611152116.NAA21083@austin.polstra.com> To: rkw@dataplex.net Subject: Re: cvsup Newsgroups: polstra.freebsd.current In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Date: Fri, 15 Nov 1996 13:16:08 -0800 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > BTW, John, since we have to (CV)sup a large number of distributions from > the same place, it would be nice if the input would allow us to specify the > common elements only once rather thanon each entry. Yes, this is on my to-do list. John From owner-freebsd-current Fri Nov 15 14:25:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA21802 for current-outgoing; Fri, 15 Nov 1996 14:25:25 -0800 (PST) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA21779 for ; Fri, 15 Nov 1996 14:25:07 -0800 (PST) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id OAA06971; Fri, 15 Nov 1996 14:24:36 -0800 (PST) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma006965; Fri Nov 15 14:24:09 1996 Received: (from archie@localhost) by bubba.whistle.com (8.7.5/8.6.12) id OAA00340; Fri, 15 Nov 1996 14:24:09 -0800 (PST) From: Archie Cobbs Message-Id: <199611152224.OAA00340@bubba.whistle.com> Subject: Re: vi complaints In-Reply-To: <199611151857.KAA24145@bubba.whistle.com> from Archie Cobbs at "Nov 15, 96 10:57:46 am" To: archie@whistle.com (Archie Cobbs) Date: Fri, 15 Nov 1996 14:24:09 -0800 (PST) Cc: jlemon@americantv.com, archie@whistle.com, Mark.Olear@Colorado.EDU, freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > It doesn't seem to have any effect. I did "set keytime=30" and > > > still it turns up arrow into open line, insert 'A' ... and it's > > > happening almost immediately. > > > > Use "set escapetime=30", in your .exrc file. > > set escapetime does the trick.. thanks! > -archie ...but i still think the default should be 2 instead of 1 (which in fact seems to be long enough for telnet over ethernet)... -archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com From owner-freebsd-current Fri Nov 15 15:29:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA26541 for current-outgoing; Fri, 15 Nov 1996 15:29:53 -0800 (PST) Received: from ican.net (ican.net [198.133.36.9]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA26536 for ; Fri, 15 Nov 1996 15:29:51 -0800 (PST) Received: from gate.ican.net(really [198.133.36.2]) by ican.net via sendmail with esmtp id for ; Fri, 15 Nov 1996 18:29:41 -0500 (EST) (Smail-3.2 1996-Jul-4 #1 built 1996-Jul-10) Received: (from smap@localhost) by gate.ican.net (8.7.5/8.7.3) id SAA18125 for ; Fri, 15 Nov 1996 18:28:32 -0500 (EST) Received: from cabal.io.org(10.1.6.2) by gate.ican.net via smap (V1.3) id sma018121; Fri Nov 15 18:28:11 1996 Received: from localhost (taob@localhost) by cabal.io.org (8.7.6/8.7.3) with SMTP id SAA16632 for ; Fri, 15 Nov 1996 18:28:16 GMT X-Authentication-Warning: cabal.io.org: taob owned process doing -bs Date: Fri, 15 Nov 1996 18:28:16 +0000 () From: Brian Tao To: FREEBSD-CURRENT-L Subject: "panic: nfs: sillyrename dir" Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is a new and amusing one. ;-) I have two shell servers, one running 2.2-961014-SNAP and the other running 2.2-960501-SNAP. Both have identical hardware and both mount the same nine filesystems from three NFS servers (one is NetBSD 1.1, one is FreeBSD 2.2-961014-SNAP, and one is BSD/OS 2.01). Neither act as an NFS server. A couple of days ago, both of them crashed with the same kernel panic within 97 seconds of each other, "panic: nfs: sillyrename dir". I don't know if this is significant, but it takes about that length of time for one of those shell servers to reboot. In /usr/src/sys/nfs/nfs_vnops.c, there is the following comment block before the nfs_sillyrename() function: /* * Silly rename. To make the NFS filesystem that is stateless look a little * more like the "ufs" a remove of an active vnode is translated to a rename * to a funny looking filename that is removed by nfs_inactive on the * nfsnode. There is the potential for another process on a different client * to create the same funny name between the nfs_lookitup() fails and the * nfs_rename() completes, but... */ But... what?!?! :) Was this double panic just a coincidence? -- Brian Tao (BT300, taob@io.org, taob@ican.net) Senior Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't" From owner-freebsd-current Fri Nov 15 16:37:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA29890 for current-outgoing; Fri, 15 Nov 1996 16:37:13 -0800 (PST) Received: from nexgen.n4hhe.ampr.org (max2-163.HiWAAY.net [206.104.22.163]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA29885 for ; Fri, 15 Nov 1996 16:37:09 -0800 (PST) Received: (from dkelly@localhost) by nexgen.n4hhe.ampr.org (8.7.5/8.7.3) id SAA07235 for freebsd-current@freebsd.org; Fri, 15 Nov 1996 18:37:02 -0600 (CST) Message-ID: X-Mailer: XFMail 0.5-alpha [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Resent-Date: Fri, 15 Nov 1996 16:55:36 -0600 Resent-Message-Id: Resent-From: David Kelly Resent-To: dkelly@hiwaay.net Date: Fri, 15 Nov 1996 18:16:11 -0600 (CST) Organization: Amateur Radio N4HHE, Madison, AL. From: David Kelly To: freebsd-current@freebsd.org Subject: /usr/bin/mail in current is giving me fits. Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This example of /usr/bin/mail's behaviour in 3.0-current bugs me. Its not like this on 2.1.5R, or any other system with the BSD Mail. If I wanted it to "dt" I'd have typed "dt" and not "d 2". What is causing this? Went so far as to lift the binary of mail from 2.1.5R and libc.so.2.2 and place it on the new machine and *still* got the same results. The terminal used doesn't matter. Now I beg for help... PeeCee: {1006} mail Mail version 8.1 6/6/93. Type ? for help. "/var/mail/dkelly": 3 messages 3 new >N 1 dkelly Fri Nov 15 16:52 12/385 "test1" N 2 dkelly Fri Nov 15 16:52 12/385 "test2" N 3 dkelly Fri Nov 15 16:52 12/385 "test3" & d 2 Message 3: >From dkelly Fri Nov 15 16:52:57 1996 Date: Fri, 15 Nov 1996 16:52:57 -0600 (CST) From: David Kelly To: dkelly Subject: test3 3 & x PeeCee: {1007} uname -a FreeBSD PeeCee.tbe.com 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Wed Nov 6 18:22:58 CST 1996 dkelly@PeeCee.tbe.com:/usr/src/sys/compile/PEECEE i386 PeeCee: {1008} Kernel was compiled with sources current on Nov 6, "make world" was Nov 2. -- David Kelly N4HHE, dkelly@tomcat1.tbe.com (wk), dkelly@hiwaay.net (hm) ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. From owner-freebsd-current Fri Nov 15 17:09:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA01479 for current-outgoing; Fri, 15 Nov 1996 17:09:51 -0800 (PST) Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA01473 for ; Fri, 15 Nov 1996 17:09:47 -0800 (PST) Received: from campa.panke.de (anonymous215.ppp.cs.tu-berlin.de [130.149.17.215]) by mail.cs.tu-berlin.de (8.6.13/8.6.12) with ESMTP id CAA06391; Sat, 16 Nov 1996 02:06:56 +0100 Received: (from wosch@localhost) by campa.panke.de (8.6.12/8.6.12) id BAA01725; Sat, 16 Nov 1996 01:00:38 +0100 Date: Sat, 16 Nov 1996 01:00:38 +0100 From: Wolfram Schneider Message-Id: <199611160000.BAA01725@campa.panke.de> To: Mikael Karpberg Cc: current@freebsd.org Subject: Re: (add|rm)(user|group) In-Reply-To: <199611140846.JAA03583@ocean.campus.luth.se> References: <199611121553.QAA00777@campa.panke.de> <199611140846.JAA03583@ocean.campus.luth.se> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Mikael Karpberg writes: >I haven't looked at them at all, but I thought I'd just comment on their >names as you listed them above. > >addgroup / adduser - seems logical >rmgroup / removeuser - not so logical > >Why not rmuser or removegroup ? I think it would be nice with consistant >naming, maybe? I will rename 'removeuser' to 'rmuser', to be compatible with BSD/OS Wolfram From owner-freebsd-current Fri Nov 15 17:58:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA03461 for current-outgoing; Fri, 15 Nov 1996 17:58:13 -0800 (PST) Received: from itchy.mindspring.com (itchy.mindspring.com [204.180.128.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA03455 for ; Fri, 15 Nov 1996 17:58:04 -0800 (PST) Received: from rlb.users.mindspring.com (user-168-121-25-139.dialup.mindspring.com [168.121.25.139]) by itchy.mindspring.com (8.7.5/8.7.3) with SMTP id UAA06444 for ; Fri, 15 Nov 1996 20:58:00 -0500 (EST) Message-ID: <328D1FC4.41C67EA6@mindspring.com> Date: Fri, 15 Nov 1996 20:58:28 -0500 From: Ron Bolin X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Build of libc_r broken Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In building current today 11-15 9PM EDT this error was reported. -O -DLIBC_RCS -DSYSLIBC_RCS -DPTHREAD_KERNEL -D_THREAD_SAFE -I/usr/src/lib/li bc_r/uthread -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc_r/../li bc/locale -DYP -c /usr/src/lib/libc_r/../libc/gen/isatty.c -o isatty.o In file included from /usr/src/lib/libc_r/../libc/gen/isatty.c:42: /usr/src/lib/libc_r/uthread/pthread_private.h:84: field `m_type' has incomplete type /usr/src/lib/libc_r/uthread/pthread_private.h:106: field `m_type' has incomplete type /usr/src/lib/libc_r/uthread/pthread_private.h:509: parse error before `0' *** Error code 1 Ron -- **************************************************************************** Ron Bolin rlb@mindspring.com, http://www.mindspring.com/~rlb/ GSU: gs01rlb@panther.gsu.edu matrlbx@indigo4.cs.gsu.edu Home: 770-992-8877 **************************************************************************** From owner-freebsd-current Fri Nov 15 18:32:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA04840 for current-outgoing; Fri, 15 Nov 1996 18:32:25 -0800 (PST) Received: (from hsu@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA04834; Fri, 15 Nov 1996 18:32:24 -0800 (PST) Date: Fri, 15 Nov 1996 18:32:24 -0800 (PST) From: Jeffrey Hsu Message-Id: <199611160232.SAA04834@freefall.freebsd.org> To: rlb@mindspring.com Subject: Re: Build of libc_r broken Cc: current Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Do a make install in /usr/src/include. From owner-freebsd-current Fri Nov 15 20:59:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA11608 for current-outgoing; Fri, 15 Nov 1996 20:59:16 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA11603 for ; Fri, 15 Nov 1996 20:59:09 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id PAA10727; Sat, 16 Nov 1996 15:28:58 +1030 (CST) From: Michael Smith Message-Id: <199611160458.PAA10727@genesis.atrad.adelaide.edu.au> Subject: Re: vi complaints In-Reply-To: <328C93AC.4C5E@Colorado.EDU> from Mark O'Lear at "Nov 15, 96 09:00:44 am" To: Mark.Olear@Colorado.EDU (Mark O'Lear) Date: Sat, 16 Nov 1996 15:28:57 +1030 (CST) Cc: archie@whistle.com, freebsd-current@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-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Mark O'Lear stands accused of saying: > > > > The new "vi" has two new flaws IMHO... ... > What is your 'keytime' set for? (do a ':set keytime' from > vi). This may be too low, you can always set it higher > in your .exrc file (put a line 'set keytime=10' or some > appropriate value for your configuration). The problem is not that people have this value wrong, the problem is that the _DEFAULT_ value is wrong. I have already complained about this. > Mark O'Lear \ e-mail: Mark.Olear@Colorado.EDU -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Sat Nov 16 02:52:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA20694 for current-outgoing; Sat, 16 Nov 1996 02:52:21 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA20688 for ; Sat, 16 Nov 1996 02:52:12 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id LAA10217; Sat, 16 Nov 1996 11:51:53 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id LAA01374; Sat, 16 Nov 1996 11:51:53 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id LAA05963; Sat, 16 Nov 1996 11:50:14 +0100 (MET) From: J Wunsch Message-Id: <199611161050.LAA05963@uriah.heep.sax.de> Subject: Re: /usr/bin/mail in current is giving me fits. To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 16 Nov 1996 11:50:14 +0100 (MET) Cc: dkelly@hiwaay.net (David Kelly) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from David Kelly at "Nov 15, 96 06:16:11 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As David Kelly wrote: > PeeCee: {1006} mail > Mail version 8.1 6/6/93. Type ? for help. > "/var/mail/dkelly": 3 messages 3 new > >N 1 dkelly Fri Nov 15 16:52 12/385 "test1" > N 2 dkelly Fri Nov 15 16:52 12/385 "test2" > N 3 dkelly Fri Nov 15 16:52 12/385 "test3" > & d 2 > Message 3: > >From dkelly Fri Nov 15 16:52:57 1996 > Date: Fri, 15 Nov 1996 16:52:57 -0600 (CST) > From: David Kelly ...strange. I cannot reproduce it, it works as expected for me. -- 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-current Sat Nov 16 05:52:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA29915 for current-outgoing; Sat, 16 Nov 1996 05:52:44 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA29910 for ; Sat, 16 Nov 1996 05:52:40 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id OAA15201; Sat, 16 Nov 1996 14:51:38 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id OAA05282; Sat, 16 Nov 1996 14:51:33 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id OAA19764; Sat, 16 Nov 1996 14:35:41 +0100 (MET) From: J Wunsch Message-Id: <199611161335.OAA19764@uriah.heep.sax.de> Subject: Re: fixit floppy trouble on -current 3.0 To: andreas@klemm.gtn.com (Andreas Klemm) Date: Sat, 16 Nov 1996 14:35:40 +0100 (MET) Cc: current@FreeBSD.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Andreas Klemm at "Nov 14, 96 03:19:14 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Andreas Klemm wrote: > As it looks to me, I wouldn't be able to get my system recovered. Well, you would -- but not out of the box. ;-) I think you're experienced enough to work around the problems... > First of all some experiences using MAKEDEV in /mnt2/dev of the fixit > floppy: > ./MAKEDEV doesn't run, since #!/bin/sh isn't in the search path. > so I have to use it typing > sh MAKEDEV I used to type `sh MAKEDEV' all the time since the script wasn't executable at all in previous versions. But you're right, there should be a symlink for /bin/sh anyway. > 'sh MAKEDEV somedevice' fails, because expr can't be found. > expr is located somewhere in /mnt2/stand or such, if I remember right. Ähem... well, all this rather looks like another cry for a working DEVFS. ;-) To hack around the problem, we should perhaps simply comment out the PATH line in MAKEDEV on the fixit floppy. This can be done as part of the build process using some sed magic. > So the 1st task was to try to create the devices rsd0s3e and so on. > MAKEDEV complained about no space left .... > > Well, a df -i shows this numbers: > Filesystem 1K-blocks Used Avail Capacity iused ifree %iused M. on > root_device 1319 1137 182 86% 101 281 26% / > /dev/fd0 1095 1051 44 96% 381 193 66% /mnt2 That's surprising. There should be enough i-nodes left. Well, yet another cry for DEVFS. ;) There's no ``works for everybody'' solution, so you should probably edit the fixit floppy before to include the device nodes you need (and remove stuff you don't need). The only bad thing is that the device nodes appear as /mnt2/dev/node then unless you chroot to the fixit floppy (which is IMHO a bad idea since you need some of the stuff from the root MFS). -- 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-current Sat Nov 16 06:03:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA00351 for current-outgoing; Sat, 16 Nov 1996 06:03:50 -0800 (PST) Received: from key.sms.fi (count@key.sms.fi [194.197.125.241]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA00346 for ; Sat, 16 Nov 1996 06:03:43 -0800 (PST) Received: (from count@localhost) by key.sms.fi (8.8.2/8.7.3) id QAA00252 for current@freebsd.org; Sat, 16 Nov 1996 16:03:36 +0200 (EET) From: "Bror 'Count' Heinola" Message-Id: <199611161403.QAA00252@key.sms.fi> Subject: Signal 11's while doing make world To: current@freebsd.org Date: Sat, 16 Nov 1996 16:03:36 +0200 (EET) 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just bought a new ATX motherboard (Intel Tucson) and I'm having problems with make world dying on signal 11's while compiling. I think that it isn't the memory (all 64M of it) because I'm running with ECC enabled, so I'm suspecting the cache, which is unfortunately soldered on the motherboard. Is there any reliable way to test the cache in place? The board is only two days old so there's no fear of warranty running out :) Just for information, I'm including the dmesg output and current kernel config file. System and kernel is as of today's -current. Copyright (c) 1992-1996 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #1: Sat Nov 16 15:52:25 EET 1996 count@key.sms.fi:/usr/src/sys/compile/KEY Calibrating clock(s) relative to mc146818A clock ... i586 clock: 132949839 Hz, i8254 clock: 1193141 Hz CPU: Pentium (132.95-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x526 Stepping=6 Features=0x1bf real memory = 67108864 (65536K bytes) avail memory = 64188416 (62684K bytes) Probing for devices on PCI bus 0: chip0 rev 1 on pci0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 vga0 rev 1 int a irq ?? on pci0:13 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface 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 flags 0x80ff80ff on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 3067MB (6281856 sectors), 6232 cyls, 16 heads, 63 S/T, 512 B/S wdc1 not found at 0x170 1 3C5x9 board(s) on ISA found at 0x300 ep0 at 0x300-0x30f irq 10 on isa ep0: aui/utp/bnc[*UTP*] address 00:20:af:c1:6b:11 npx0 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 5 drq 1 on isa sb0: sbxvi0 not found sbmidi0 not found at 0x330 mpu0 at 0x330 irq 5 drq 0 on isa mpu0: machine "i386" cpu "I586_CPU" ident KEY maxusers 10 options INET #InterNETworking options FFS #Berkeley Fast 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 USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options SYSVSHM options SYSVSEM options SYSVMSG options "AUTO_EOI_1" options "AUTO_EOI_2" config kernel root on wd0 controller isa0 controller pci0 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 flags 0x80ff80ff vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr 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 lpt0 at isa? port? tty irq 7 vector lptintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 device mpu0 at isa? port 0x330 conflicts irq 5 drq 0 device ep0 at isa? port 0x300 net irq 10 vector epintr pseudo-device loop pseudo-device ether pseudo-device log pseudo-device pty 64 pseudo-device gzip # Exec gzipped a.out's pseudo-device bpfilter 4 -- Bror 'Count' Heinola % count@key.hole.fi % http://pobox.com/~count/ Isokaari 27 A 2 % IRC: Count NIC: BH271 % FI-00200 HELSINKI % Work: bror@sms.fi % Roads? Where we're going, Cell: +358-40-5533-554 % Santa Monica Software % we don't need roads. From owner-freebsd-current Sat Nov 16 06:22:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA00785 for current-outgoing; Sat, 16 Nov 1996 06:22:09 -0800 (PST) Received: from answerman.mindspring.com (answerman.mindspring.com [204.180.128.8]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA00780 for ; Sat, 16 Nov 1996 06:22:06 -0800 (PST) Received: from rlb.users.mindspring.com (user-168-121-25-139.dialup.mindspring.com [168.121.25.139]) by answerman.mindspring.com (8.7.5/8.7.3) with SMTP id JAA20534 for ; Sat, 16 Nov 1996 09:35:32 -0500 (EST) Message-ID: <328DCDF8.167EB0E7@mindspring.com> Date: Sat, 16 Nov 1996 09:21:44 -0500 From: Ron Bolin X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Thread library libc_r and Makefile error egrep -o Content-Type: multipart/mixed; boundary="------------794BDF32446B9B3D2781E494" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is a multi-part message in MIME format. --------------794BDF32446B9B3D2781E494 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit In building the thread library I noticed the following error(s) (see attached). Duplicate identifiers and and error in the option to egrep in the Makefile. I tried to replace the Makefile '-o' option with '-e', but that did not work. The library builds, but the duplicate names and the installation script erros make me wonder if there may be some problem down the road if one uses threads on FBSD. Any thoughts on this would be welcome. Ron -- **************************************************************************** Ron Bolin rlb@mindspring.com, http://www.mindspring.com/~rlb/ GSU: gs01rlb@panther.gsu.edu matrlbx@indigo4.cs.gsu.edu Home: 770-992-8877 **************************************************************************** --------------794BDF32446B9B3D2781E494 Content-Type: text/plain; charset=us-ascii; name="BUG" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="BUG" Duplicate entry in file /usr/src/lib/libc_r/../libc/db/btree/bt_debug.c, line 116: X Second entry ignored Duplicate entry in file /usr/src/lib/libc_r/../libc/db/btree/bt_debug.c, line 169: X Second entry ignored Duplicate entry in files /usr/src/lib/libc_r/../libc/db/hash/hsearch.c and /usr/src/lib/libc_r/../libc/db/hash/hash.c: hdestroy (Warning only) Duplicate entry in files /usr/src/lib/libc_r/../libc/gen/getcwd.c and /usr/src/lib/libc_r/../libc/gen/fts.c: ISDOT (Warning only) Duplicate entry in files /usr/src/lib/libc_r/../libc/gen/times.c and /usr/src/lib/libc_r/../libc/gen/clock.c: CONVTCK (Warning only) Duplicate entry in file /usr/src/lib/libc_r/../libc/gen/ttyname.c, line 164: ttyname Second entry ignored Duplicate entry in files /usr/src/lib/libc_r/../libc/gen/usleep.c and /usr/src/lib/libc_r/../libc/gen/sleep.c: setvec (Warning only) Duplicate entry in files /usr/src/lib/libc_r/../libc/gen/usleep.c and /usr/src/lib/libc_r/../libc/gen/sleep.c: sleephandler (Warning only) Duplicate entry in files /usr/src/lib/libc_r/../libc/gen/vis.c and /usr/src/lib/libc_r/../libc/gen/unvis.c: isoctal (Warning only) Duplicate entry in file /usr/src/lib/libc_r/../libc/locale/collate.c, line 157: __collate_err Second entry ignored Duplicate entry in files /usr/src/lib/libc_r/../libc/net/getnetnamadr.c and /usr/src/lib/libc_r/../libc/net/gethostnamadr.c: get_service_name (Warning only) Duplicate entry in files /usr/src/lib/libc_r/../libc/net/getnetnamadr.c and /usr/src/lib/libc_r/../libc/net/gethostnamadr.c: init_services (Warning only) Duplicate entry in files /usr/src/lib/libc_r/../libc/net/inet_ntop.c and /usr/src/lib/libc_r/../libc/net/gethostbydns.c: SPRINTF (Warning only) Duplicate entry in files /usr/src/lib/libc_r/../libc/regex/regexec.c and /usr/src/lib/libc_r/../libc/gen/fts.c: ISSET (Warning only) Duplicate entry in file /usr/src/lib/libc_r/../libc/regex/regexec.c, line 114: CLEAR Second entry ignored Duplicate entry in file /usr/src/lib/libc_r/../libc/regex/regexec.c, line 115: SET0 Second entry ignored Duplicate entry in file /usr/src/lib/libc_r/../libc/regex/regexec.c, line 116: SET1 Second entry ignored Duplicate entry in file /usr/src/lib/libc_r/../libc/regex/regexec.c, line 118: ASSIGN Second entry ignored Duplicate entry in file /usr/src/lib/libc_r/../libc/regex/regexec.c, line 119: EQ Second entry ignored Duplicate entry in file /usr/src/lib/libc_r/../libc/regex/regexec.c, line 121: STATESETUP Second entry ignored Duplicate entry in file /usr/src/lib/libc_r/../libc/regex/regexec.c, line 124: STATETEARDOWN Second entry ignored Duplicate entry in file /usr/src/lib/libc_r/../libc/regex/regexec.c, line 125: SETUP Second entry ignored Duplicate entry in file /usr/src/lib/libc_r/../libc/regex/regexec.c, line 127: INIT Second entry ignored Duplicate entry in file /usr/src/lib/libc_r/../libc/regex/regexec.c, line 128: INC Second entry ignored Duplicate entry in file /usr/src/lib/libc_r/../libc/regex/regexec.c, line 129: ISSTATEIN Second entry ignored Duplicate entry in file /usr/src/lib/libc_r/../libc/regex/regexec.c, line 132: FWD Second entry ignored Duplicate entry in file /usr/src/lib/libc_r/../libc/regex/regexec.c, line 133: BACK Second entry ignored Duplicate entry in file /usr/src/lib/libc_r/../libc/regex/regexec.c, line 134: ISSETBACK Second entry ignored Duplicate entry in files /usr/src/lib/libc_r/../libc/stdio/vasprintf.c and /usr/src/lib/libc_r/../libc/gen/syslog.c: writehook (Warning only) Duplicate entry in files /usr/src/lib/libc_r/../libc/stdio/vsscanf.c and /usr/src/lib/libc_r/../libc/stdio/sscanf.c: eofread (Warning only) Duplicate entry in files /usr/src/lib/libc_r/../libc/stdlib/heapsort.c and /usr/src/lib/libc_r/../libc/stdio/fvwrite.c: COPY (Warning only) Duplicate entry in file /usr/src/lib/libc_r/../libc/stdlib/malloc.c, line 201: UTRACE Second entry ignored Duplicate entry in file /usr/src/lib/libc_r/../libc/stdlib/malloc.c, line 1090: THREAD_LOCK Second entry ignored Duplicate entry in file /usr/src/lib/libc_r/../libc/stdlib/malloc.c, line 1091: THREAD_UNLOCK Second entry ignored Duplicate entry in files /usr/src/lib/libc_r/../libc/stdlib/qsort.c and /usr/src/lib/libc_r/../libc/stdlib/strhash.c: min (Warning only) Duplicate entry in files /usr/src/lib/libc_r/../libc/stdlib/qsort.c and /usr/src/lib/libc_r/../libc/stdlib/merge.c: swap (Warning only) Duplicate entry in file /usr/src/lib/libc_r/../libc/stdlib/strtod.c, line 210: Sign_Extend Second entry ignored Duplicate entry in file /usr/src/lib/libc_r/../libc/stdlib/strtod.c, line 221: word0 Second entry ignored Duplicate entry in file /usr/src/lib/libc_r/../libc/stdlib/strtod.c, line 222: word1 Second entry ignored Duplicate entry in file /usr/src/lib/libc_r/../libc/stdlib/strtod.c, line 233: Storeinc Second entry ignored Duplicate entry in file /usr/src/lib/libc_r/../libc/stdlib/strtod.c, line 337: rounded_product Second entry ignored Duplicate entry in file /usr/src/lib/libc_r/../libc/stdlib/strtod.c, line 338: rounded_quotient Second entry ignored Duplicate entry in file /usr/src/lib/libc_r/../libc/stdtime/localtime.c, line 960: P Second entry ignored Duplicate entry in file /usr/src/lib/libc_r/../libc/stdtime/localtime.c, line 1016: P Second entry ignored Duplicate entry in files /usr/src/lib/libc_r/../libc/rpc/pmap_rmt.c and /usr/src/lib/libc_r/../libc/net/rcmd.c: max (Warning only) Duplicate entry in files /usr/src/lib/libc_r/../libc/rpc/svc_tcp.c and /usr/src/lib/libc_r/../libc/rpc/clnt_tcp.c: readtcp (Warning only) Duplicate entry in files /usr/src/lib/libc_r/../libc/rpc/svc_tcp.c and /usr/src/lib/libc_r/../libc/rpc/clnt_tcp.c: writetcp (Warning only) Duplicate entry in file /usr/src/lib/libc_r/uthread/uthread_init.c, line 212: _thread_init Second entry ignored egrep -o "^ENTRY(.*)|^FUNC(.*)|^SYSCALL(.*)" | sed "s;\([^:]*\):\([^(]*\)(\([^, )]*\)\(.*\);\3 \1 /^\2(\3\4$/;" >> tags; sort -o tags tags egrep: illegal option -- o usage: egrep [-[AB] ] [-HRPS] [-CEFGLVabchilnqsvwx] [-e ] [-f file] [files ...] install -c -o bin -g bin -m 444 tags /var/db/libc_r.tags install -c -o bin -g bin -m 444 libc_r.a /usr/lib install -c -o bin -g bin -m 444 libc_r_p.a /usr/lib install -c -o bin -g bin -m 444 -fschg libc_r.so.3.0 /usr/lib install -c -o bin -g bin -m 444 pthread_create.3.gz pthread_detach.3.gz pthread_equal.3.gz pthread_exit.3.gz pthread_getspecific.3.gz pthread_join.3.gz pthread_key_create.3.gz pthread_key_delete.3.gz pthread_once.3.gz pthread_self.3.gz pthread_setspecific.3.gz /usr/share/man/man3 --------------794BDF32446B9B3D2781E494-- From owner-freebsd-current Sat Nov 16 07:37:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA02926 for current-outgoing; Sat, 16 Nov 1996 07:37:37 -0800 (PST) Received: from friley216.res.iastate.edu (friley216.res.iastate.edu [129.186.78.216]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA02918; Sat, 16 Nov 1996 07:37:33 -0800 (PST) Received: from friley216.res.iastate.edu (loopback [127.0.0.1]) by friley216.res.iastate.edu (8.7.6/8.7.3) with ESMTP id JAA00513; Sat, 16 Nov 1996 09:37:32 -0600 (CST) Message-Id: <199611161537.JAA00513@friley216.res.iastate.edu> X-Mailer: exmh version 1.6.9 8/22/96 cc: questions@freebsd.org, freebsd-current@freebsd.org Subject: PAS16 broken? (Was: Re: Logitech Soundman 16 support?) In-reply-to: Your message of Fri, 15 Nov 1996 22:25:19 -0600. <199611160425.WAA13349@friley216.res.iastate.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 16 Nov 1996 09:37:32 -0600 From: Chris Csanady Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I happen to have one of these now, however can not get FreeBSD to decect it. >Does anyone have this working? From the sound.doc there are a couple >references to it, so I assume it is supposed to work. I have the card in >sound blaster compatibility mode, ive tried various irq's/etc.. Ok.. I didnt realize that it is actually a PAS16, I thought I just needed the soundblaster driver, and it would be compatible. I included the pas driver, and it sortof works. It is at least detected. :) The problem now, it things dont play back correctly. When I cat an au file to /dev/audio, its almost as if chunks of the file are missing and then played after a pause at the end. Chunks played out of order essentialy. :\ This is on a kernel built from todays sources. Anyone know what might cause this? Its sortof annoying.. Chris Csanady >This is in 3.0-CURRENT > >Any insight would be appreciated. > >--Chris Csanady > > > From owner-freebsd-current Sat Nov 16 07:49:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA03406 for current-outgoing; Sat, 16 Nov 1996 07:49:53 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA03398 for ; Sat, 16 Nov 1996 07:49:48 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id QAA23748 for current@freebsd.org; Sat, 16 Nov 1996 16:45:19 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.8.2/8.8.2) with SMTP id QAA21463 for ; Sat, 16 Nov 1996 16:41:04 +0100 (MET) Date: Sat, 16 Nov 1996 16:41:03 +0100 (MET) From: Andreas Klemm To: current@freebsd.org Subject: mysterious super scsi device.... Message-ID: X-try-apsfilter: ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz X-Fax: +49 2137 2018 X-Phone: +49 2137 2020 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I think MAKEDEV isn't prepared yet, to use the super scsi device. The scsi man page says, The -p option can be used against the "super scsi" device /dev/scsi/super to probe all devices with a given SCSI lun on a given SCSI bus. The bus can be selected with the -b option and the default is 0. The lun can be selected with the -l option and the default is 0. See scsi(4) for a de- scription of the "super scsi" device. So it should be possible for me, to re-probe for a tape device after reboot, if I forgot to power on the tape. But what devices are all needed for this super scsi feature. Only /dev/scsi/super ? Which major minor numbers ? Thanks for any advice. BTW, this should definitively go into 2.2, if MAKEDEV would be fixed ... Andreas /// andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev..html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-current Sat Nov 16 07:55:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA03780 for current-outgoing; Sat, 16 Nov 1996 07:55:44 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA03771 for ; Sat, 16 Nov 1996 07:55:37 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id QAA19874; Sat, 16 Nov 1996 16:54:11 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id QAA07084; Sat, 16 Nov 1996 16:54:10 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id QAA17104; Sat, 16 Nov 1996 16:47:41 +0100 (MET) From: J Wunsch Message-Id: <199611161547.QAA17104@uriah.heep.sax.de> Subject: Re: kernel compile To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 16 Nov 1996 16:47:40 +0100 (MET) Cc: croot@btp1da.phy.uni-bayreuth.de (Werner Griessl) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199611121327.NAA02086@btp1da.phy.uni-bayreuth.de> from Werner Griessl at "Nov 12, 96 01:27:06 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Werner Griessl wrote: > > Cannot compile current kernel because: > > ../../i386/i386/identcpu.c:42: opt_temporary.h: No such file or directory > *** Error code 1 ``Don't forget to make depend.'' :-) (For those who don't understand the joke, the above reminder used to be spit out by `config' previously.) -- 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-current Sat Nov 16 08:22:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA05243 for current-outgoing; Sat, 16 Nov 1996 08:22:08 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA05229 for ; Sat, 16 Nov 1996 08:22:02 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id RAA20496 for ; Sat, 16 Nov 1996 17:21:30 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id RAA07509 for freebsd-current@FreeBSD.org; Sat, 16 Nov 1996 17:21:29 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id RAA24620 for freebsd-current@FreeBSD.org; Sat, 16 Nov 1996 17:06:23 +0100 (MET) From: J Wunsch Message-Id: <199611161606.RAA24620@uriah.heep.sax.de> Subject: Re: missing email To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 16 Nov 1996 17:06:23 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <12674.847715422@critter.tfs.com> from Poul-Henning Kamp at "Nov 11, 96 01:30:22 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Poul-Henning Kamp wrote: > >I've been missing some email lately that I now is being sent to the > > > >Does this have to do with the bad spots on the disk on freefall, or is > >there something else bad going on? > > Probably, it didn't go quite according to the book, and some email > could have been lost. I've been missing part 4 of the recent CTM `compat' megadelta. Can i assume it fell into the same hole? (I had to recreate it on freefall which is not a simple task since ctm_smail insists on calling sendmail directly.) -- 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-current Sat Nov 16 08:23:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA05309 for current-outgoing; Sat, 16 Nov 1996 08:23:01 -0800 (PST) Received: from nexgen.n4hhe.ampr.org (max12-70.HiWAAY.net [206.104.16.70]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA05292 for ; Sat, 16 Nov 1996 08:22:51 -0800 (PST) Received: (from dkelly@localhost) by nexgen.n4hhe.ampr.org (8.7.5/8.7.3) id KAA10005; Sat, 16 Nov 1996 10:22:07 -0600 (CST) Message-ID: X-Mailer: XFMail 0.5-alpha [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <199611161050.LAA05963@uriah.heep.sax.de> Date: Sat, 16 Nov 1996 10:12:18 -0600 (CST) Organization: Amateur Radio N4HHE, Madison, AL. From: David Kelly To: J Wunsch Subject: Re: /usr/bin/mail in current is giving me fits. Cc: (FreeBSD-current users) Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On 17:50:14 J Wunsch wrote: >>As David Kelly wrote: > >> PeeCee: {1006} mail >> Mail version 8.1 6/6/93. Type ? for help. >> "/var/mail/dkelly": 3 messages 3 new >> >N 1 dkelly Fri Nov 15 16:52 12/385 "test1" >> N 2 dkelly Fri Nov 15 16:52 12/385 "test2" >> N 3 dkelly Fri Nov 15 16:52 12/385 "test3" >> & d 2 >> Message 3: >> >From dkelly Fri Nov 15 16:52:57 1996 >> Date: Fri, 15 Nov 1996 16:52:57 -0600 (CST) >> From: David Kelly > >...strange. I cannot reproduce it, it works as expected for me. Well, it looks like I'm going to have to contribute something to FreeBSD and hunt it down myself. Another user emailed me saying the same problem was happening to him since 2.1.0R. And I almost stated I had the same problem with 2.1.5R but I double checked just before posting and could not reproduce the problem. The question is, "did I have the problem with 2.1.5R and now don't?" Guess we'll know if I ever figure it out. Surely this problem wouldn't be hardware related? Same time I put 2.2-current on it, it got a new motherboard. My 2.1.0R and 2.1.5R systems are all on totally different hardware. 2.1.0R is 486DX33 ISA, 2.1.5R is NexGen PCI, and 2.2/3.0-current is [45]86/133 PCI. -- David Kelly N4HHE, dkelly@tomcat1.tbe.com (wk), dkelly@hiwaay.net (hm) ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. From owner-freebsd-current Sat Nov 16 08:43:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA06550 for current-outgoing; Sat, 16 Nov 1996 08:43:28 -0800 (PST) Received: from zeus.gel.usherb.ca (zeus.gel.usherb.ca [132.210.70.7]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA06542; Sat, 16 Nov 1996 08:43:24 -0800 (PST) Received: from castor.gel.usherb.ca by zeus.gel.usherb.ca (4.1/SMI-4.1) id AA01145; Sat, 16 Nov 96 11:43:20 EST Received: by castor.gel.usherb.ca (SMI-8.6/SMI-SVR4) id LAA29031; Sat, 16 Nov 1996 11:43:19 -0500 Date: Sat, 16 Nov 1996 11:43:19 -0500 (EST) From: "Alex.Boisvert" To: Mark Mayo Cc: hackers@freebsd.org, current@freebsd.org Subject: Re: userland PPP giving weird load numbers In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I've had this problem since 2.1x, and it appaears to still happen > occasionally in 2.2-ALPHA: > > mark:{105}/home/mark % w > 8:14AM up 46 mins, 3 users, load averages: 0.99, 0.97, 0.88 > USER TTY FROM LOGIN@ IDLE WHAT > mark p1 :0.0 7:28AM 45 -tcsh (tcsh) > mark p2 :0.0 7:28AM - w > mark p3 :0.0 7:32AM 37 ppp > > the ppp process causes the high load (which isn't real, BTW). Top shows it > as not doing a thing. As soon as I kill ppp off, the load drops right back > down. > I've noticed the same thing in 2.2-ALPHA since my installation. The load goes between .80 to 1.1 when doing (moderate) FTP transmissions with userland PPP. I don't know if the load is real or not because I have not verified that impact on performance it made. Alex Boisvert From owner-freebsd-current Sat Nov 16 08:53:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA07431 for current-outgoing; Sat, 16 Nov 1996 08:53:01 -0800 (PST) Received: from po2.glue.umd.edu (po2.glue.umd.edu [129.2.128.45]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA07426 for ; Sat, 16 Nov 1996 08:52:59 -0800 (PST) Received: from baud.eng.umd.edu (baud.eng.umd.edu [129.2.98.183]) by po2.glue.umd.edu (8.8.2/8.7.3) with ESMTP id LAA12783; Sat, 16 Nov 1996 11:52:56 -0500 (EST) Received: from localhost (chuckr@localhost) by baud.eng.umd.edu (8.7.5/8.7.3) with SMTP id LAA18888; Sat, 16 Nov 1996 11:52:55 -0500 (EST) X-Authentication-Warning: baud.eng.umd.edu: chuckr owned process doing -bs Date: Sat, 16 Nov 1996 11:52:54 -0500 (EST) From: Chuck Robey X-Sender: chuckr@baud.eng.umd.edu To: Joerg Wunsch cc: FreeBSD-current users Subject: Re: missing email In-Reply-To: <199611161606.RAA24620@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 16 Nov 1996, J Wunsch wrote: > As Poul-Henning Kamp wrote: > > > >I've been missing some email lately that I now is being sent to the > > > > > >Does this have to do with the bad spots on the disk on freefall, or is > > >there something else bad going on? > > > > Probably, it didn't go quite according to the book, and some email > > could have been lost. > > I've been missing part 4 of the recent CTM `compat' megadelta. Can i > assume it fell into the same hole? (I had to recreate it on freefall > which is not a simple task since ctm_smail insists on calling sendmail > directly.) My mail system here has a sense of humor. It always delays delivery of the last ctm update in a batch until one or two of the intervening updates past the batch come through, making me wonder if I've lost a delta. I haven't, yet, but that performance is reliable. Scary sort of thing, and I'd be much more worried if I didn't have access to ftp. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Sat Nov 16 09:31:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA09188 for current-outgoing; Sat, 16 Nov 1996 09:31:54 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA09183 for ; Sat, 16 Nov 1996 09:31:50 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id SAA05386; Sat, 16 Nov 1996 18:30:18 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.8.2/8.8.2) with SMTP id RAA22219; Sat, 16 Nov 1996 17:17:48 +0100 (MET) Date: Sat, 16 Nov 1996 17:17:46 +0100 (MET) From: Andreas Klemm To: Gary Roberts cc: freebsd-current@FreeBSD.org Subject: Re: Argh .. Make world In-Reply-To: Message-ID: X-try-apsfilter: ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz X-Fax: +49 2137 2018 X-Phone: +49 2137 2020 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 14 Nov 1996, Gary Roberts wrote: > DOH!@#!@!!@ > > 6 hours and 24 minutes into MAKE WORLD and it crashes :( > > Error follows: > cc -O -c /usr/src/usr.sbin/pkg_install/lib/file.c: In function > `fileGetURL': > /usr/src/usr/sbin/pkg_install/lib/file.c:250: too many arguments to > function `ftpGetURL' > > Uhm, is there anyway I can start where it left off ... 6 hours is a long > time :D cd /usr/src make all install -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-current Sat Nov 16 10:18:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA10899 for current-outgoing; Sat, 16 Nov 1996 10:18:51 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA10894 for ; Sat, 16 Nov 1996 10:18:48 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id FAA24323; Sun, 17 Nov 1996 05:03:49 +1100 Date: Sun, 17 Nov 1996 05:03:49 +1100 From: Bruce Evans Message-Id: <199611161803.FAA24323@godzilla.zeta.org.au> To: freebsd-current@freebsd.org, j@uriah.heep.sax.de Subject: Re: kernel compile Cc: croot@btp1da.phy.uni-bayreuth.de Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >As Werner Griessl wrote: >> >> Cannot compile current kernel because: >> >> ../../i386/i386/identcpu.c:42: opt_temporary.h: No such file or directory >> *** Error code 1 > >``Don't forget to make depend.'' > >:-) > >(For those who don't understand the joke, the above reminder used to >be spit out by `config' previously.) I had a lot of trouble understanding the joke :-). I think you meant to write: ``Don't forget to run the clobbering version of config when changing options, since the non-clobbering version won't remove old options files so the kernel build environment won't be standard enough for testing in.'' Bruce From owner-freebsd-current Sat Nov 16 10:52:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA13203 for current-outgoing; Sat, 16 Nov 1996 10:52:35 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA13191 for ; Sat, 16 Nov 1996 10:52:30 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id TAA23680; Sat, 16 Nov 1996 19:50:55 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id TAA12275; Sat, 16 Nov 1996 19:50:55 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id TAA22322; Sat, 16 Nov 1996 19:27:13 +0100 (MET) From: J Wunsch Message-Id: <199611161827.TAA22322@uriah.heep.sax.de> Subject: Re: kernel compile To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 16 Nov 1996 19:27:12 +0100 (MET) Cc: croot@btp1da.phy.uni-bayreuth.de Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199611161803.FAA24323@godzilla.zeta.org.au> from Bruce Evans at "Nov 17, 96 05:03:49 am" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Bruce Evans wrote: > >``Don't forget to make depend.'' > > > >:-) > I had a lot of trouble understanding the joke :-). I think you meant > to write: > > ``Don't forget to run the clobbering version of config when changing > options,... No. I think the problem originated from an old .depend file that still mentioned opt_temporary.h while this was no longer actually used. It's just a wild guess, of course. -- 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-current Sat Nov 16 11:37:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA14784 for current-outgoing; Sat, 16 Nov 1996 11:37:51 -0800 (PST) Received: from dworshak.cs.uidaho.edu (dworshak.cs.uidaho.edu [129.101.100.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA14779 for ; Sat, 16 Nov 1996 11:37:44 -0800 (PST) Received: from waldrog.cs.uidaho.edu (waldrog.cs.uidaho.edu [129.101.100.23]) by dworshak.cs.uidaho.edu (8.7.5/1.1) with ESMTP id LAA00802 for ; Sat, 16 Nov 1996 11:37:37 -0800 (PST) Received: (nawaz921@localhost) by waldrog.cs.uidaho.edu (8.7.5/1.0) id LAA08928; Sat, 16 Nov 1996 11:37:37 -0800 (PST) Date: Sat, 16 Nov 1996 11:37:37 -0800 (PST) Message-Id: <199611161937.LAA08928@waldrog.cs.uidaho.edu> From: Faried Nawaz To: freebsd-current@freebsd.org Subject: Re: /usr/bin/mail in current is giving me fits. Organization: People's Front Against WWW X-Real-Name: Faried Nawaz X-Address: Box 3582, Moscow, ID 83843-1914 X-Phone: +1 208 882 8896 X-Notice: Do not redistribute in any form without prior explicit consent of the author. Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk David Kelly -- > Well, it looks like I'm going to have to contribute something to > FreeBSD and hunt it down myself. Another user emailed me saying > the same problem was happening to him since 2.1.0R. And I almost > stated I had the same problem with 2.1.5R but I double checked > just before posting and could not reproduce the problem. The > question is, "did I have the problem with 2.1.5R and now don't?" > Guess we'll know if I ever figure it out. In your ~/.mailrc and in /usr/share/skel/dot.mailrc, 'autoprint' is set. This is causing the behavior you see. From owner-freebsd-current Sat Nov 16 11:45:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA15073 for current-outgoing; Sat, 16 Nov 1996 11:45:20 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA15061 for ; Sat, 16 Nov 1996 11:45:12 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.7.6/8.7.3) with SMTP id LAA21064 for ; Sat, 16 Nov 1996 11:45:10 -0800 (PST) Date: Sat, 16 Nov 1996 11:45:10 -0800 (PST) From: Jaye Mathisen To: current@freebsd.org Subject: -current build dies in fetch Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Wrong number of arguments. I just cvsup'd (Great tool, BTW), on 11/15. From owner-freebsd-current Sat Nov 16 12:01:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA15766 for current-outgoing; Sat, 16 Nov 1996 12:01:41 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA15759 for ; Sat, 16 Nov 1996 12:01:36 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id GAA26181; Sun, 17 Nov 1996 06:50:39 +1100 Date: Sun, 17 Nov 1996 06:50:39 +1100 From: Bruce Evans Message-Id: <199611161950.GAA26181@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.org, j@uriah.heep.sax.de Subject: Re: kernel compile Cc: croot@btp1da.phy.uni-bayreuth.de Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> >``Don't forget to make depend.'' >> > >> >:-) > >> I had a lot of trouble understanding the joke :-). I think you meant >> to write: >> >> ``Don't forget to run the clobbering version of config when changing >> options,... > >No. I think the problem originated from an old .depend file that >still mentioned opt_temporary.h while this was no longer actually >used. It's just a wild guess, of course. I'm not guessing. The error message for an old .depend file would be completely different. I introduced this bug and fixed it when Werner pointed it out 4 or 5 days ago. Maybe you got the mail late. Bruce From owner-freebsd-current Sat Nov 16 12:31:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA16837 for current-outgoing; Sat, 16 Nov 1996 12:31:02 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA16832; Sat, 16 Nov 1996 12:31:00 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.7.6/8.7.3) with SMTP id MAA25863; Sat, 16 Nov 1996 12:30:59 -0800 (PST) Date: Sat, 16 Nov 1996 12:30:58 -0800 (PST) From: Jaye Mathisen To: hackers@freebsd.org cc: current@freebsd.org Subject: I think our fsck is still funky. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 2.2-current, supped this morning. P120, 2940, Conner 4GB disk. Copy lots of small files to the disk in lots of directories (like news). Begin an rm while copying. Simulate failure by pulling plug. Unsimulate failure by re-inerting power cord. Reboot, fsck disk. Mount, and try again. I get crashes in dup_inode, and some ffs_alloc stuff. newfs the disk and it's fine. Me thinks that fsck is still missing some sanity checks. From owner-freebsd-current Sat Nov 16 12:37:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA17269 for current-outgoing; Sat, 16 Nov 1996 12:37:13 -0800 (PST) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA17263 for ; Sat, 16 Nov 1996 12:37:11 -0800 (PST) Received: by sovcom.kiae.su id AA14808 (5.65.kiae-1 ); Sat, 16 Nov 1996 23:26:26 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Sat, 16 Nov 96 23:26:26 +0300 Received: (from ache@localhost) by nagual.ru (8.8.2/8.8.2) id XAA00326; Sat, 16 Nov 1996 23:23:27 +0300 (MSK) Message-Id: <199611162023.XAA00326@nagual.ru> Subject: Re: -current build dies in fetch In-Reply-To: from "Jaye Mathisen" at "Nov 16, 96 11:45:10 am" To: mrcpu@cdsnet.net (Jaye Mathisen) Date: Sat, 16 Nov 1996 23:23:27 +0300 (MSK) Cc: current@freebsd.org From: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) Organization: self X-Class: Fast X-Mailer: ELM [version 2.4ME+ PL28 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > Wrong number of arguments. I just cvsup'd (Great tool, BTW), on 11/15. > Use 'make world' -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Sat Nov 16 12:39:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA17404 for current-outgoing; Sat, 16 Nov 1996 12:39:55 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA17398 for ; Sat, 16 Nov 1996 12:39:53 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.7.6/8.7.3) with ESMTP id MAA26668; Sat, 16 Nov 1996 12:39:48 -0800 (PST) Date: Sat, 16 Nov 1996 12:39:47 -0800 (PST) From: Jaye Mathisen To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= cc: current@freebsd.org Subject: Re: -current build dies in fetch In-Reply-To: <199611162023.XAA00326@nagual.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8BIT Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I always do. On Sat, 16 Nov 1996, [KOI8-R] áÎÄÒÅÊ þÅÒÎÏ× wrote: > Date: Sat, 16 Nov 1996 23:23:27 +0300 (MSK) > From: "[KOI8-R] áÎÄÒÅÊ þÅÒÎÏ×" > To: Jaye Mathisen > Cc: current@freebsd.org > Subject: Re: -current build dies in fetch > > > > > > > Wrong number of arguments. I just cvsup'd (Great tool, BTW), on 11/15. > > > > Use 'make world' > > -- > Andrey A. Chernov > > http://www.nagual.ru/~ache/ > From owner-freebsd-current Sat Nov 16 13:05:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA18625 for current-outgoing; Sat, 16 Nov 1996 13:05:06 -0800 (PST) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA18609 for ; Sat, 16 Nov 1996 13:04:54 -0800 (PST) Received: by sovcom.kiae.su id AA21004 (5.65.kiae-1 ); Sat, 16 Nov 1996 23:51:25 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Sat, 16 Nov 96 23:51:25 +0300 Received: (from ache@localhost) by nagual.ru (8.8.2/8.8.2) id XAA00495; Sat, 16 Nov 1996 23:48:32 +0300 (MSK) Message-Id: <199611162048.XAA00495@nagual.ru> Subject: Re: -current build dies in fetch In-Reply-To: from "Jaye Mathisen" at "Nov 16, 96 12:39:47 pm" To: mrcpu@cdsnet.net (Jaye Mathisen) Date: Sat, 16 Nov 1996 23:48:32 +0300 (MSK) Cc: current@freebsd.org From: "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) Organization: self X-Class: Fast X-Mailer: ELM [version 2.4ME+ PL28 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I always do. > > > > > Use 'make world' world: ... make includes (install new ftpio.h) ... make libraries (install new libftpio.a) ... make all (build fetch) It seems your sourses are out of sync -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Sat Nov 16 13:15:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA19562 for current-outgoing; Sat, 16 Nov 1996 13:15:29 -0800 (PST) Received: from murrow.prognet.com (prognet.com [205.219.198.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA19557; Sat, 16 Nov 1996 13:15:16 -0800 (PST) Received: from peterh.dev.prognet.com (two89.dev.prognet.com) by murrow.prognet.com with SMTP id AA26299 (5.67b/IDA-1.5); Sat, 16 Nov 1996 13:14:44 -0800 Message-Id: <3.0b36.32.19961116131427.010daf60@prognet.com> X-Sender: peterh@prognet.com X-Mailer: Windows Eudora Pro Version 3.0b36 (32) Date: Sat, 16 Nov 1996 13:14:29 -0800 To: "Eric J. Chet" , Ernie Elu From: Peter Haight Subject: Re: guavac, libstdc++ Cc: ports@FreeBSD.org, current@FreeBSD.org, dob@nasvr1.cb.lucent.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk At 10:01 PM 11/13/96 -0500, Eric J. Chet wrote: >On Thu, 14 Nov 1996, Ernie Elu wrote: > >> Has anyone managed to get the guavac java compiler from >> http://http.cs.berkeley.edu/~engberg/guavac to compile under FreeBSD >> current? >> >> Everytime I try it gets a link error from the g++ file tree.h saying that >> the varialbe rb_NIL is unknown. I can't find that variable in any of the g++ >> libraries so it might be a bug that it's missing. >> >> - Ernie. >> > >Hello > There are three *.cc files in >/usr/src/contrib/libg++/libstdc++/stl > >random.cc >tree.cc >tempbuf.cc > >That are not being built under FreeBSD. Should these three files >be added to the build process for libstdc++? They really need >to be included into a library. I encountered this problem too. It is not that those files are not being compiled at all, but that they are not compiled into the shared library. I moved 'libstdc++.so.2.0' out of my /usr/lib and any STL stuff that uses red black trees now works. This only happened after I upgraded to the 2.2-961014-SNAP. I don't know whether this is still a problem. From owner-freebsd-current Sat Nov 16 14:00:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA22956 for current-outgoing; Sat, 16 Nov 1996 14:00:58 -0800 (PST) Received: from friley216.res.iastate.edu (friley216.res.iastate.edu [129.186.78.216]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA22950 for ; Sat, 16 Nov 1996 14:00:54 -0800 (PST) Received: from friley216.res.iastate.edu (loopback [127.0.0.1]) by friley216.res.iastate.edu (8.7.6/8.7.3) with ESMTP id QAA03736 for ; Sat, 16 Nov 1996 16:00:53 -0600 (CST) Message-Id: <199611162200.QAA03736@friley216.res.iastate.edu> X-Mailer: exmh version 1.6.9 8/22/96 To: freebsd-current@freebsd.org Subject: NFS dies in current Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 16 Nov 1996 16:00:52 -0600 From: Chris Csanady Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I recently updated to a Nov 15 kernel, and NFS is virtually unuseable. I keep getting "nfs server not responding" messages, and am unable to see the server anymore. As of a kernel built on the 9th, things were much better. I would occasionally have this problem, but a lot less. What has changed? In early october, I am pretty sure it all worked perfectly.. (or i didnt notice) --Chris Csanady From owner-freebsd-current Sat Nov 16 14:07:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA23389 for current-outgoing; Sat, 16 Nov 1996 14:07:04 -0800 (PST) Received: from r33h77.res.gatech.edu (r33h77.res.gatech.edu [128.61.33.77]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA23365 for ; Sat, 16 Nov 1996 14:06:53 -0800 (PST) Received: (from jason@localhost) by r33h77.res.gatech.edu (8.8.2/8.7.3) id RAA03715 for current@freebsd.org; Sat, 16 Nov 1996 17:07:06 -0500 (EST) From: Jason Bennett Message-Id: <199611162207.RAA03715@r33h77.res.gatech.edu> Subject: Audio CD To: current@freebsd.org Date: Sat, 16 Nov 1996 17:07:06 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Before upgraded from 2.1.5, my CD player was working fine with cdplay. Since the upgrade to 3.0-current, though, it cannot see the cd in the drive. I've rebuilt the kernel and and done a make world. Is there a step I left out? jason -- Jason Bennett, jbennett@cc.gatech.edu | Member, Team OS/2! CS Major, Georgia Institute of Technology | Senior TA, CS 1501! Believer in Jesus Christ as Savior and Lord | VP-Comm, BSU! http://bsu.gt.ed.net/jason/ | finger for PGP key! From owner-freebsd-current Sat Nov 16 14:51:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA25604 for current-outgoing; Sat, 16 Nov 1996 14:51:58 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA25599 for ; Sat, 16 Nov 1996 14:51:51 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id XAA28361; Sat, 16 Nov 1996 23:51:45 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA16148; Sat, 16 Nov 1996 23:51:45 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id XAA03942; Sat, 16 Nov 1996 23:31:52 +0100 (MET) From: J Wunsch Message-Id: <199611162231.XAA03942@uriah.heep.sax.de> Subject: Re: fixit floppy trouble on -current 3.0 To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 16 Nov 1996 23:31:50 +0100 (MET) Cc: andreas@klemm.gtn.com (Andreas Klemm) In-Reply-To: from Andreas Klemm at "Nov 14, 96 03:19:14 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Andreas Klemm wrote: > Well, a df -i shows this numbers: > Filesystem 1K-blocks Used Avail Capacity iused ifree %iused M. on > root_device 1319 1137 182 86% 101 281 26% / > /dev/fd0 1095 1051 44 96% 381 193 66% /mnt2 > > I removed some special devices, and the output of df shows some space, > but I was unable to create any sd0s3x device. I typed: > sh MAKEDEV sd0s3e > sh MAKEDEV sd0s3f > and so on > but the commands didn't have any result, because of 'no space left'. Well, your observation was incomplete. You should have noticed that `expr' actually segfaulted... _this_ was what caused the `no space left on device'. There was no space for a 600 KB coredump on the floppy -- obviously. :) The actual problem was hard to find. The Posix regexp stuff has been defined twice, once in libc and once in libgnuregexp. The latter is required for the fixit floppy since grep(1) uses it. However, expr(1) uses the header file for the Posix regexp stuff in libc, which is (of course) incompatible with the GNU stuff. By now, i simply don't know a better solution than leaving out the Posix regexp stuff from libgnuregexp. -- 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-current Sat Nov 16 14:53:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA25764 for current-outgoing; Sat, 16 Nov 1996 14:53:06 -0800 (PST) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA25755 for ; Sat, 16 Nov 1996 14:53:00 -0800 (PST) Received: (from uucp@localhost) by frmug.org (8.8.2/8.8.2/frmug-1.2) with UUCP id XAA02284 for current@FreeBSD.org; Sat, 16 Nov 1996 23:52:58 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by xp11.frmug.org (8.8.2/8.7.3/xp11-uucp-1.1) with ESMTP id OAA00521 for ; Sat, 16 Nov 1996 14:41:32 +0100 (MET) Message-Id: <199611161341.OAA00521@xp11.frmug.org> To: current@FreeBSD.org Subject: can not change to correct boot device Date: Sat, 16 Nov 1996 14:41:32 +0100 From: "Philippe Charnier" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi, My config is: wd0 : MSDOS (40 MB) + FreeBSD-stable (/ /var /usr) + booteasy wd1 : FreeBSD-current (/ /var /usr) + booteasy sd0 : FreeBSD-current (/ /var /usr data) + booteasy sd1 : FreeBSD (data) My wd1 is dying, so I'm switching to sd0 as my bootable -current drive. I disabled wd1 in the bios to be able to boot from sd0, and changed my kernel to config kernel root on sd0 swap on wd0 and sd0 #dumps on wd0 ^^^was wd1 here controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 #controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr #disk wd1 at wdc1 drive 0 ^^^^removed wdc1 and wd1 If I let him boot, it tries 1:sd(1,a)/kernel and fails at `change root to sd1a'. Entering 1:sd(0,a)/kernel is ok. How can I do this in the kernel config file? ------ ------ Philippe Charnier charnier@lirmm.fr (smtp) charnier@xp11.frmug.org (uucp) ``a PC not running FreeBSD is like a venusian with no tentacles'' ------------------------------------------------------------------------ From owner-freebsd-current Sat Nov 16 14:53:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA25794 for current-outgoing; Sat, 16 Nov 1996 14:53:22 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA25784 for ; Sat, 16 Nov 1996 14:53:13 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id XAA28366; Sat, 16 Nov 1996 23:51:47 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA16150; Sat, 16 Nov 1996 23:51:46 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id XAA03968; Sat, 16 Nov 1996 23:34:24 +0100 (MET) From: J Wunsch Message-Id: <199611162234.XAA03968@uriah.heep.sax.de> Subject: Re: kernel compile To: freebsd-current@FreeBSD.org Date: Sat, 16 Nov 1996 23:34:23 +0100 (MET) Cc: croot@btp1da.phy.uni-bayreuth.de Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199611161950.GAA26181@godzilla.zeta.org.au> from Bruce Evans at "Nov 17, 96 06:50:39 am" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Bruce Evans wrote: > I'm not guessing. The error message for an old .depend file would be > completely different. I introduced this bug and fixed it when Werner > pointed it out 4 or 5 days ago. Maybe you got the mail late. Nope, but i've been away for a week, and had to catch up with 1500 emails. So i haven't kept your change fully in mind (though i remember that i've seen a message to this avail). -- 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-current Sat Nov 16 15:14:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA26714 for current-outgoing; Sat, 16 Nov 1996 15:14:41 -0800 (PST) Received: from ravenock.cybercity.dk (disn49.cybercity.dk [194.16.57.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA26706 for ; Sat, 16 Nov 1996 15:14:32 -0800 (PST) Received: (from sos@localhost) by ravenock.cybercity.dk (8.8.2/8.7.3) id AAA01173 for current@freebsd.org; Sun, 17 Nov 1996 00:15:30 +0100 (MET) Message-Id: <199611162315.AAA01173@ravenock.cybercity.dk> Subject: Problem with syscons mouse pointer... To: current@freebsd.org (FreeBSD current) Date: Sun, 17 Nov 1996 00:15:19 +0100 (MET) From: "Soren Schmidt" From: sos@freebsd.org Reply-to: sos@freebsd.org X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Guys... I've just come across a problem with the mousepointer in syscons. If I use it on my p5 machine in will lock the machine tight in a few seconds. This happens both in 2.2-ALPHA and -current, so it has nothing to do with the latest psm&syscons changes (why do I always feel at risk when stating such things :) ) I can also run X which uses the mouse pseudo-device through syscons so it must have something to do with the mousepointer update rutine, but I havn't found out why yet (need some sleep). The strange thing is it doesn't happen on a 486 machine running the exact same code... Anybody else seeing this ?? Or am I halucinating due to lack of sleep lately.... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-current Sat Nov 16 15:52:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA28405 for current-outgoing; Sat, 16 Nov 1996 15:52:00 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA28388 for ; Sat, 16 Nov 1996 15:51:54 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id AAA29843; Sun, 17 Nov 1996 00:51:36 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA17438; Sun, 17 Nov 1996 00:51:35 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id AAA04631; Sun, 17 Nov 1996 00:36:15 +0100 (MET) From: J Wunsch Message-Id: <199611162336.AAA04631@uriah.heep.sax.de> Subject: Re: can not change to correct boot device To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 17 Nov 1996 00:36:14 +0100 (MET) Cc: charnier@xp11.frmug.org (Philippe Charnier) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199611161341.OAA00521@xp11.frmug.org> from Philippe Charnier at "Nov 16, 96 02:41:32 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Philippe Charnier wrote: > If I let him boot, it tries 1:sd(1,a)/kernel and fails at > `change root to sd1a'. Entering 1:sd(0,a)/kernel is ok. > > How can I do this in the kernel config file? You can't. You must do it in the bootblocks. I think there's something from Julian around that would let you store such a change automatically in the bootblock, but offhand i don't remember any pointers to documentation for it. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat Nov 16 16:31:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA00199 for current-outgoing; Sat, 16 Nov 1996 16:31:27 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA00194 for ; Sat, 16 Nov 1996 16:31:14 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id LAA00201; Sun, 17 Nov 1996 11:27:16 +1100 Date: Sun, 17 Nov 1996 11:27:16 +1100 From: Bruce Evans Message-Id: <199611170027.LAA00201@godzilla.zeta.org.au> To: current@FreeBSD.org, nate@mt.sri.com Subject: Re: UserConfig is broken + PS/2 support success Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >UserConfig is now broken in current. It may have to do withe the recent >syscons changes, but in any case nothing happens at the "config>" prompt >when I type anymore. The sources are from early this morning, so it's >probably a fairly recent change. This is (at least) because sc_port is not initialized until scprobe() is called much later. There is no keyboard at port 0. I don't like the new keyboard driver much. It's has too many features, and too many spinloops. Some of the flags and flags testing seem to be wrong: 1. KBD_DISABLE_AUX_PORT 0x20 According to Van Gilluwe, on ISA/EISA keyboards setting this gives: "Ignore parity from keyboard, no scan code conversion" [not the default]. This is now used. It seems to be harmless. It was also used in pccons. It is still defined in /sys/i386/isa/ic/i8042.h (which is where all the i8042-specific defines should always have been) as KC8_OLDPC 0x20 /* old 9bit codes instead of new 11bit */ 2. KC8_IGNSEC 0x08 /* ignore security lock */ [in i8042.h] This silently went away. Now syscons honors the security lock switch like most drivers. The PROBE_KEYBOARD_LOCK feature in the bootstrap works better with old buggy behaviour. 3. KBDS_CONTROLLER_BUSY 0x0002 aka KBS_IBF 0x02 According to Van Gilluwe and all other docs and drivers that I've seen, this bit is for "The motherboard controller's input buffer is full ... no writes should occur to ports 60h or 64h or the data/command will be lost". It has nothing to do with the controller's output buffer (i.e., scancodes for the driver to read). This bit is spun on for up to 100 msec in wait_while_controller_busy() which is (incorrectly) called from read_kbd_data_no_wait(). Not good for a no-wait routine in an interrupt handler. Calling it a "busy" bit encourages this error. --- The wait_until_controller_is_really_idle() function seems to be unusable. E.g., when it use used for a LED update,, interrupts are disabled, so it is guaranteed to spin if a scancode arrives. The LED update will succeed after a delay of a couple of hundred msec because it ignores the return code. The empty_*_buffer*() functions are broken. They miss scancodes that arrive a microsecond after the test and are almost certain to miss all but the first of a bunch of scancodes - the controller is unlikely to be able to deliver another scancode on the 0-20 usec delay time, especially if the keyboard is a few msec away from sending it! See pcvt_kbd.c for a working version (which is unsuitable for general use because of the lengthy spinloop). write_kbd_command() ignores the return code from wait_until_controller_is_really_idle(). Apart from the buggy interface (see above), this is critical for issueing the reset command - it is possible for the keyboard to hang and resetting it fixes it. I think the return code should not be ignored for other commands - the keyboard should be reset and reinitialized in this case. The 7us delays that are said to be necessary for MCA keyboards aren't there. Bruce From owner-freebsd-current Sat Nov 16 16:32:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA00249 for current-outgoing; Sat, 16 Nov 1996 16:32:19 -0800 (PST) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA00242; Sat, 16 Nov 1996 16:32:08 -0800 (PST) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.7.6/8.7.3) with SMTP id TAA26733; Sat, 16 Nov 1996 19:31:23 -0500 (EST) Date: Sat, 16 Nov 1996 19:31:22 -0500 (EST) From: John Fieber To: Peter Haight cc: "Eric J. Chet" , Ernie Elu , ports@FreeBSD.org, current@FreeBSD.org, dob@nasvr1.cb.lucent.com Subject: Re: guavac, libstdc++ In-Reply-To: <3.0b36.32.19961116131427.010daf60@prognet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 16 Nov 1996, Peter Haight wrote: > This only happened after I upgraded to the 2.2-961014-SNAP. I don't know > whether this is still a problem. Check in current now. It was supposedly fixed yesterday, but you might want to verify it before 2.2 gets set in stone. -john == jfieber@indiana.edu =========================================== == http://fallout.campusview.indiana.edu/~jfieber ================ From owner-freebsd-current Sat Nov 16 16:59:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA01513 for current-outgoing; Sat, 16 Nov 1996 16:59:28 -0800 (PST) Received: from itchy.mindspring.com (itchy.mindspring.com [204.180.128.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA01504 for ; Sat, 16 Nov 1996 16:59:26 -0800 (PST) Received: from rlb.users.mindspring.com (user-168-121-25-139.dialup.mindspring.com [168.121.25.139]) by itchy.mindspring.com (8.7.5/8.7.3) with SMTP id TAA02925 for ; Sat, 16 Nov 1996 19:59:18 -0500 (EST) Message-ID: <328E6381.41C67EA6@mindspring.com> Date: Sat, 16 Nov 1996 19:59:45 -0500 From: Ron Bolin X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: UserConfig is broken + PS/2 support success Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ditto, I like the way the PS2 mouse now works under X. Great, even the cut and paste works better. However, I had to save an earlier version of my kernel because the UserConfig option (AKA -c) is broken now. I can't configure this kernel on the fly with the current fix. Great job on the mouse interface. Maybe this mouse and console interface needs to be separated someday. Ron -- **************************************************************************** Ron Bolin rlb@mindspring.com, http://www.mindspring.com/~rlb/ GSU: gs01rlb@panther.gsu.edu matrlbx@indigo4.cs.gsu.edu Home: 770-992-8877 **************************************************************************** From owner-freebsd-current Sat Nov 16 17:34:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA03869 for current-outgoing; Sat, 16 Nov 1996 17:34:20 -0800 (PST) Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA03864 for ; Sat, 16 Nov 1996 17:34:14 -0800 (PST) Received: from cantina.clinet.fi (root@cantina.clinet.fi [194.100.0.15]) by hauki.clinet.fi (8.7.6/8.6.4) with ESMTP id DAA27687; Sun, 17 Nov 1996 03:33:58 +0200 (EET) Received: (hsu@localhost) by cantina.clinet.fi (8.7.5/8.6.4) id DAA16989; Sun, 17 Nov 1996 03:33:57 +0200 (EET) Date: Sun, 17 Nov 1996 03:33:57 +0200 (EET) Message-Id: <199611170133.DAA16989@cantina.clinet.fi> From: Heikki Suonsivu To: Jaye Mathisen Cc: freebsd-current@freebsd.org In-reply-to: Jaye Mathisen's message of 16 Nov 1996 22:46:33 +0200 Subject: Re: I think our fsck is still funky. Organization: Clinet Ltd, Espoo, Finland References: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article Jaye Mathisen writes: 2.2-current, supped this morning. P120, 2940, Conner 4GB disk. Copy lots of small files to the disk in lots of directories (like news). Begin an rm while copying. Simulate failure by pulling plug. Unsimulate failure by re-inerting power cord. Reboot, fsck disk. Mount, and try again. I get crashes in dup_inode, and some ffs_alloc stuff. newfs the disk and it's fine. Me thinks that fsck is still missing some sanity checks. Since end of August (I have kernel compiled 19th) freebsd has been corrupting disks repeatably with -current. For us symptom is always the same, crash, and fsck fails on number of DUP/BAD inodes (random sequences of 8 corrupted inodes around the disk). It seems that couple of blockfulls of inodes get written over, usually files which were used at the time. On news server we get crash too quickly that any later kernel would be usable, I'm still using the old one. At least two people have had same problem, but it happens on IDE disks (quantum bigfoots) and 2.1.5 (!), the hardware is - cyrix p150+, 2*2.5G bigfoot, 64M, stealth 64, adaptek 2940, 5G hawk, DAT, other machine P133, 32M, 1G IDE, Stealth 64, no SCSI. The first machine is server, the latter one X terminal. Originally the latter machine was running 2.1R reliably (for 7 months) with P133, 128M, 1G IDE, Adaptek 2940, 1G SCSI, 4G hawk, DAT. This does not quite fit the picture, if it is scsi problem, as corrupted disks are IDE. For more info ask ylo@ssh.fi We only have seen corruption on SCSI disks but that may be because we generally use SCSI for anything involving any real work, only routers and X-terminals have IDE disks. -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@clinet.fi mobile +358-40-5519679 work +358-9-43542270 fax -4555276 From owner-freebsd-current Sat Nov 16 17:35:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA04016 for current-outgoing; Sat, 16 Nov 1996 17:35:18 -0800 (PST) Received: from fools.ecpnet.com (ppp-67-227.dialup.winternet.com [204.246.67.227]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA04011 for ; Sat, 16 Nov 1996 17:35:15 -0800 (PST) Received: (from moke@localhost) by fools.ecpnet.com (8.8.2/8.8.2) id TAA00465; Sat, 16 Nov 1996 19:28:22 -0600 (CST) Date: Sat, 16 Nov 1996 19:28:21 -0600 (CST) From: Jimbo Bahooli To: freebsd-current@freebsd.org Subject: identd broken? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have been following -current for awhile now with few problems that I could not fix. Then this strange bug comes along, pidentd 2.7.2 comiled out of ports-current simpy does not work. This is the error message it generates. Nov 16 19:17:31 fools identd[437]: getbuf: bad address (00000000 not in f0100000 -0xFFC00000) - ofile I'm guessing its because its looking for something in the kernel thats changed positions in -current, if any would could help I would appreciate it.