From owner-freebsd-bugs Sun Feb 25 01:07:40 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA20520 for bugs-outgoing; Sun, 25 Feb 1996 01:07:40 -0800 (PST) Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id BAA20513 Sun, 25 Feb 1996 01:07:14 -0800 (PST) Received: from katiska.clinet.fi (root@katiska.clinet.fi [194.100.0.4]) by hauki.clinet.fi (8.7.3/8.6.4) with ESMTP id KAA29172; Sun, 25 Feb 1996 10:57:37 +0200 (EET) Received: (hsu@localhost) by katiska.clinet.fi (8.7.3/8.6.4) id KAA01206; Sun, 25 Feb 1996 10:57:36 +0200 (EET) Date: Sun, 25 Feb 1996 10:57:36 +0200 (EET) Message-Id: <199602250857.KAA01206@katiska.clinet.fi> From: Heikki Suonsivu To: Peter Wemm Cc: hsu@clinet.fi, freebsd-bugs@freefall.freebsd.org Subject: Re: bin/1033 In-Reply-To: <199602191045.CAA18934@freefall.freebsd.org> References: <199602191045.CAA18934@freefall.freebsd.org> Organization: Clinet Ltd, Espoo, Finland Sender: owner-bugs@FreeBSD.ORG Precedence: bulk Peter Wemm writes: > Synopsis: xinstall install rule broken? > > State-Changed-From-To: open-feedback > State-Changed-By: peter > State-Changed-When: Mon Feb 19 02:42:33 PST 1996 > State-Changed-Why: > I committed a fix for this shortly before this bug was filed. > (rev 1.76 of Makefile) > Can you please check to see if it is working now after your next sup/ctm? Yes, it seems to work now, I upgraded couple of machines with reinstall and it went through without problems (these aren't 2.1R, though, but I think there were old enough to justify this statement). -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@clinet.fi mobile +358-40-5519679 work +358-0-4375360 fax -4555276 home -8031121 From owner-freebsd-bugs Sun Feb 25 05:29:03 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA29969 for bugs-outgoing; Sun, 25 Feb 1996 05:29:03 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA29947 for ; Sun, 25 Feb 1996 05:28:46 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id OAA17144; Sun, 25 Feb 1996 14:28:36 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id OAA04949; Sun, 25 Feb 1996 14:28:22 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id NAA15454; Sun, 25 Feb 1996 13:58:54 +0100 (MET) From: J Wunsch Message-Id: <199602251258.NAA15454@uriah.heep.sax.de> Subject: Re: installation problem 2.1.0 To: erix@axis.fr (Eric Molinie) Date: Sun, 25 Feb 1996 13:58:54 +0100 (MET) Cc: bugs@freebsd.org, erix@rome.axis.fr Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <9602241855.aa22869@rome.axis.fr> from "Eric Molinie" at Feb 24, 96 06:55:55 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-bugs@freebsd.org Precedence: bulk As Eric Molinie wrote: > fatal trap12: page fault while in kernel mode > fault virtual address = 0x7200744 > fault code = supervisor read, page not present > instruction pointer = 0x8 : 0xf01a0ebb > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL0, pres 1, def32 1, gran 1 > What do you think about that ? That it wasn't from /kernel.GENERIC on stock 2.1R. The instructions around address 0xf01a0ebb in this kernel are: 0xf01a0eb2: cmpl $0x0,0x8c(%eax) 0xf01a0eb9: jne 0xa0ed6 0xf01a0ebb: addl $0x58,%eax <<- 0xf01a0ebe: pushl %eax ...and adding a value to a register ain't supposed to cause a page fault. Can you either send us the exact panic message for the GENERIC 2.1R kernel (prefered, since i've got this kernel on my CD-ROM for reference), or do: nm /kernel | sort | more and send us the lines around address 0xf01a0ebb. -- 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-bugs Sun Feb 25 05:54:49 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA00562 for bugs-outgoing; Sun, 25 Feb 1996 05:54:49 -0800 (PST) Received: from plum.cyber.com.au (plum.cyber.com.au [203.7.155.24]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA00556 for ; Sun, 25 Feb 1996 05:54:42 -0800 (PST) Received: (from darrenr@localhost) by plum.cyber.com.au (8.6.12/8.6.6) id AAA01557; Mon, 26 Feb 1996 00:51:46 +1100 From: Darren Reed Message-Id: <199602251351.AAA01557@plum.cyber.com.au> Subject: Incompatible slices. To: freebsd-bugs@freebsd.org, port-i386@netbsd.org Date: Mon, 26 Feb 1996 00:51:46 +1100 (EST) Reply-To: darrenr@cyber.com.au X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-bugs@freebsd.org Precedence: bulk I'd like to report that partition slices in FreeBSD 2.1.0 and NetBSD 1.1 aren't 100% compatible. wd2s4: raw partition size != slice size wd2s4: start 2459520, end 3173183, size 713664 wd2s4c: start 2459520, end 3169151, size 709632 wd2s4: rejecting partition in BSD label: it isn't entirely within the slice wd2s4: start 2459520, end 3173183, size 713664 wd2s4d: start 0, end 3169151, size 3169152 wd2s4: raw partition size != slice size wd2s4: start 2459520, end 3173183, size 713664 wd2s4c: start 2459520, end 3169151, size 709632 wd2s4: rejecting partition in BSD label: it isn't entirely within the slice wd2s4: start 2459520, end 3173183, size 713664 wd2s4d: start 0, end 3169151, size 3169152 wd2s4: raw partition size != slice size wd2s4: start 2459520, end 3173183, size 713664 wd2s4c: start 2459520, end 3169151, size 709632 wd2s4: rejecting partition in BSD label: it isn't entirely within the slice wd2s4: start 2459520, end 3173183, size 713664 wd2s4d: start 0, end 3169151, size 3169152 - slices created using NetBSD, when FreeBSD tries to fsck them. I regard it as a bug of both OSs that this doesn't work 100% :) Of course, for either to change, it means being incompatible with the past.. a solution of sorts would be nice... (No, I can't tell you what NetBSD says yet, I don't have a kernel that looks for any drives on the 2nd isa bus or mounts root from wd1a). enjoy! p.s. yes, I know I cross posted, please be sensible when replying. From owner-freebsd-bugs Sun Feb 25 08:48:46 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA06026 for bugs-outgoing; Sun, 25 Feb 1996 08:48:46 -0800 (PST) Received: from plato.algonet.se (mail.algonet.se [193.12.207.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA06021 for ; Sun, 25 Feb 1996 08:48:40 -0800 (PST) Received: from sophocles.algonet.se (mal@sophocles.algonet.se [193.12.207.10]) by plato.algonet.se (8.6.12/hdw.1.0) with ESMTP id RAA10118 for ; Sun, 25 Feb 1996 17:48:22 +0100 Received: (from mal@localhost) by sophocles.algonet.se (8.6.12/hdw.1.0) id RAA03898; Sun, 25 Feb 1996 17:48:14 +0100 Date: Sun, 25 Feb 1996 17:48:14 +0100 Message-Id: <199602251648.RAA03898@sophocles.algonet.se> From: Mats Lofkvist To: freebsd-bugs@freebsd.org Subject: 2.1-stable building problems Sender: owner-bugs@freebsd.org Precedence: bulk I had the following problems rebuilding 2.1-stable (sup'ed around 10am gmt saturday 24): - The makefiles in gnu/lib/libgmp and lib/libutil use install with the -C flag which my 'old' 2.1-stable-a-few-months-ago install does not support. - The ipfw lkm doesn't build (error messages below). - The termcap.db built by cap_mkdb is empty (od output below). The text version seems ok (ln -s /usr/share/misc/termcap ~/.termcap made xterm, vi and friends wake up). I reran cap_mkdb with the same result. _ Mats Lofkvist mal@algonet.se bash# cd /usr/src/lkm/ipfw/ bash# make cc -O -DIPFIREWALL -DIPACCT -DKERNEL -I/usr/src/lkm/ipfw/../../sys -W -Wcomment -Wredundant-decls -c /usr/src/lkm/ipfw/ipfw_lkm.c In file included from /usr/src/lkm/ipfw/ipfw_lkm.c:39: /usr/src/lkm/ipfw/../../sys/netinet/ip_fw.h:55: parse error before `LIST_ENTRY' /usr/src/lkm/ipfw/../../sys/netinet/ip_fw.h:55: warning: no semicolon at end of struct or union /usr/src/lkm/ipfw/../../sys/netinet/ip_fw.h:57: parse error before `}' /usr/src/lkm/ipfw/ipfw_lkm.c: In function `ipfw_load': /usr/src/lkm/ipfw/ipfw_lkm.c:53: `ip_acct_cnt_ptr' undeclared (first use this function) /usr/src/lkm/ipfw/ipfw_lkm.c:53: (Each undeclared identifier is reported only once /usr/src/lkm/ipfw/ipfw_lkm.c:53: for each function it appears in.) /usr/src/lkm/ipfw/ipfw_lkm.c:53: `ip_acct_ctl_ptr' undeclared (first use this function) /usr/src/lkm/ipfw/ipfw_lkm.c:59: `ip_fw_chk' undeclared (first use this function) /usr/src/lkm/ipfw/ipfw_lkm.c:60: `ip_fw_ctl' undeclared (first use this function) /usr/src/lkm/ipfw/ipfw_lkm.c:63: `ip_acct_cnt' undeclared (first use this function) /usr/src/lkm/ipfw/ipfw_lkm.c:64: `ip_acct_ctl' undeclared (first use this function) /usr/src/lkm/ipfw/ipfw_lkm.c: In function `ipfw_unload': /usr/src/lkm/ipfw/ipfw_lkm.c:79: `ip_acct_ctl_ptr' undeclared (first use this function) /usr/src/lkm/ipfw/ipfw_lkm.c:80: `ip_acct_cnt_ptr' undeclared (first use this function) *** Error code 1 Stop. bash# od -c /usr/share/misc/termcap.db 0000000 \0 006 025 a \0 \0 \0 002 \0 \0 004 322 \0 \0 \0 0000020 \0 \0 \0 \r \0 \0 001 \0 \0 \0 001 \0 \0 \0 \0 \b 0000040 \0 \0 \0 001 \0 \0 \0 002 \0 \0 \0 001 \0 \0 \0 003 0000060 \0 \0 \0 001 \0 001 \0 \0 \0 \0 \0 \0 \0 \0 \0 001 0000100 225 n } 343 \0 \0 \0 \0 \0 \0 \0 002 \0 \0 \0 002 0000120 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000300 \0 \0 \0 \0 \b 001 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0000320 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0060000 375 377 377 377 377 377 377 377 377 377 377 377 377 377 377 377 0060020 377 377 377 377 377 377 377 377 377 377 377 377 377 377 377 377 * 0100000 bash# From owner-freebsd-bugs Sun Feb 25 09:31:54 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA07645 for bugs-outgoing; Sun, 25 Feb 1996 09:31:54 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA07637 for ; Sun, 25 Feb 1996 09:31:52 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.4/8.6.9) with SMTP id JAA02304; Sun, 25 Feb 1996 09:31:07 -0800 (PST) To: darrenr@cyber.com.au cc: freebsd-bugs@freebsd.org, port-i386@NetBSD.ORG Subject: Re: Incompatible slices. In-reply-to: Your message of "Mon, 26 Feb 1996 00:51:46 +1100." <199602251351.AAA01557@plum.cyber.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2301.825269466.1@time.cdrom.com> Date: Sun, 25 Feb 1996 09:31:06 -0800 Message-ID: <2302.825269466@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-bugs@freebsd.org Precedence: bulk > I'd like to report that partition slices in FreeBSD 2.1.0 and NetBSD 1.1 > aren't 100% compatible. Thanks. Now where's the fix you were supposed to have attached? :-) I'm actually semi-serious with the above, if only because you've now declared yourself to be one of those rare folks who have even *tried* this, much less had the motivation to see it work. Myself, I'd just put NetBSD on a spare box and stop thinking about it, as I suspect would most people in the FreeBSD core team. I'm not say that there isn't a problem with FreeBSD here - there probably is, assuming that interoperability is some kind of goal (and I believe it is, though not a highest-priority one). What I'm saying is that the *only* way problems like this get fixed is when someone with both: a) the skill and b) the motivation gets involved enough to come up with a fix acceptable to both parties. Actually, (a) is often optional when (b) is high enough, since skill can be acquired. As far as I can see, you're it! :-) Jordan From owner-freebsd-bugs Sun Feb 25 11:13:02 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA12671 for bugs-outgoing; Sun, 25 Feb 1996 11:13:02 -0800 (PST) Received: from ozzy (tc2_39.teclink.net [205.229.32.209]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA12660 for ; Sun, 25 Feb 1996 11:12:59 -0800 (PST) Received: from ozzy (etheisen@localhost [127.0.0.1]) by ozzy (8.6.12/8.6.12) with ESMTP id NAA04650; Sun, 25 Feb 1996 13:13:01 -0600 Message-Id: <199602251913.NAA04650@ozzy> To: darrenr@cyber.com.au cc: freebsd-bugs@freebsd.org, port-i386@netbsd.org Subject: Re: Incompatible slices. In-reply-to: Your message of "Mon, 26 Feb 1996 00:51:46 +1100." <199602251351.AAA01557@plum.cyber.com.au> Date: Sun, 25 Feb 1996 13:12:58 -0600 From: "Erik M. Theisen" Sender: owner-bugs@freebsd.org Precedence: bulk The difference's are because of BIOS geometery. FreeBSD correctly uses the BIOS geo for partition layout. NetBSD does it own thing based upon a default partioning scheme layed out in the 1st stage loader. Or it uses it idea of the drives native geo. We need to work on getting this resolved. It has caused newcomers serious grief. Plus it's partioning scheme is not PC OS compatible. 1) Partion geo should always be layed out in the MBR in exact same geo that DOG would use. 2) The actual size should be used, not 24MB. 3) Same goes for beginning/end addresses. 3) The first track as defined by DOG should be skipped. erik From owner-freebsd-bugs Sun Feb 25 11:13:03 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA12684 for bugs-outgoing; Sun, 25 Feb 1996 11:13:03 -0800 (PST) Received: from ozzy (tc2_39.teclink.net [205.229.32.209]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA12664 for ; Sun, 25 Feb 1996 11:13:00 -0800 (PST) Received: from ozzy (etheisen@localhost [127.0.0.1]) by ozzy (8.6.12/8.6.12) with ESMTP id NAA04640; Sun, 25 Feb 1996 13:12:54 -0600 Message-Id: <199602251912.NAA04640@ozzy> To: darrenr@cyber.com.au cc: freebsd-bugs@freebsd.org, port-i386@netbsd.org, etheisen@ozzy Subject: Re: Incompatible slices. In-reply-to: Your message of "Mon, 26 Feb 1996 00:51:46 +1100." <199602251351.AAA01557@plum.cyber.com.au> Date: Sun, 25 Feb 1996 13:12:43 -0600 From: "Erik M. Theisen" Sender: owner-bugs@freebsd.org Precedence: bulk The difference's are because of BIOS geometery. FreeBSD correctly uses the BIOS geo for partition layout. NetBSD does it own thing based upon a default partioning scheme layed out in the 1st stage loader. Or it uses it idea of the drives native geo. We need to work on getting this resolved. It has caused newcomers serious grief. Plus it's partioning scheme is not PC OS compatible. 1) Partion geo should always be layed out in the MBR in exact same geo that DOG would use. 2) The actual size should be used, not 24MB. 3) Same goes for beginning/end addresses. 3) The first track as defined by DOG should be skipped. erik From owner-freebsd-bugs Sun Feb 25 11:34:54 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA13509 for bugs-outgoing; Sun, 25 Feb 1996 11:34:54 -0800 (PST) Received: (from peter@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA13490 Sun, 25 Feb 1996 11:34:53 -0800 (PST) Date: Sun, 25 Feb 1996 11:34:53 -0800 (PST) From: Peter Wemm Message-Id: <199602251934.LAA13490@freefall.freebsd.org> To: hsu@clinet.fi, peter, freebsd-bugs Subject: Re: bin/1033 Sender: owner-bugs@FreeBSD.ORG Precedence: bulk Synopsis: xinstall install rule broken? State-Changed-From-To: feedback-closed State-Changed-By: peter State-Changed-When: Sun Feb 25 11:33:40 PST 1996 State-Changed-Why: Confirmed fixed. From owner-freebsd-bugs Sun Feb 25 11:36:56 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA13593 for bugs-outgoing; Sun, 25 Feb 1996 11:36:56 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA13586 for ; Sun, 25 Feb 1996 11:36:48 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id GAA31993; Mon, 26 Feb 1996 06:34:05 +1100 Date: Mon, 26 Feb 1996 06:34:05 +1100 From: Bruce Evans Message-Id: <199602251934.GAA31993@godzilla.zeta.org.au> To: darrenr@cyber.com.au, freebsd-bugs@FreeBSD.org, port-i386@netbsd.org Subject: Re: Incompatible slices. Sender: owner-bugs@FreeBSD.org Precedence: bulk >I'd like to report that partition slices in FreeBSD 2.1.0 and NetBSD 1.1 >aren't 100% compatible. >wd2s4: raw partition size != slice size >wd2s4: start 2459520, end 3173183, size 713664 >wd2s4c: start 2459520, end 3169151, size 709632 >wd2s4: rejecting partition in BSD label: it isn't entirely within the slice >wd2s4: start 2459520, end 3173183, size 713664 >wd2s4d: start 0, end 3169151, size 3169152 FreeBSD doesn't allow partitions outside the slice that contains the label. It deletes such partitions from the in-core label but doesn't write anything to the disk unless you write the label. The 'd' and 'c' partitions are handled automatically to match the DOS partition table and/or the drive if there is no DOS partition table. The messages could be punctuated better: wd2s4: warning: raw partition size != slice size: wd2s4: start 2459520, end 3173183, size 713664, wd2s4c: start 2459520, end 3169151, size 709632 The first line is a warning and the last 2 lines describe the inconsistent objects. You seem to be wasting 713664 - 709632 = 4032 sectors. wd2s4: error: rejecting partition in BSD label: it isn't entirely within the slice: wd2s4: start 2459520, end 3173183, size 713664 wd2s4d: start 0, end 3169151, size 3169152 The first line is an error and the last 2 lines describe the inconsistent objects. Old 'd' partitions often cause this error. >wd2s4: raw partition size != slice size >wd2s4: start 2459520, end 3173183, size 713664 >wd2s4c: start 2459520, end 3169151, size 709632 >wd2s4: rejecting partition in BSD label: it isn't entirely within the slice >wd2s4: start 2459520, end 3173183, size 713664 >wd2s4d: start 0, end 3169151, size 3169152 >wd2s4: raw partition size != slice size >wd2s4: start 2459520, end 3173183, size 713664 >wd2s4c: start 2459520, end 3169151, size 709632 >wd2s4: rejecting partition in BSD label: it isn't entirely within the slice >wd2s4: start 2459520, end 3173183, size 713664 >wd2s4d: start 0, end 3169151, size 3169152 >- slices created using NetBSD, when FreeBSD tries to fsck them. The messages are repeated because fsck opens and closes the devices several times and rebuilding the tables on first opens is a simple way of getting them right for removable media. Bruce From owner-freebsd-bugs Sun Feb 25 17:48:13 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA10494 for bugs-outgoing; Sun, 25 Feb 1996 17:48:13 -0800 (PST) Received: (from gibbs@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA10475 Sun, 25 Feb 1996 17:48:11 -0800 (PST) Date: Sun, 25 Feb 1996 17:48:11 -0800 (PST) From: "Justin T. Gibbs" Message-Id: <199602260148.RAA10475@freefall.freebsd.org> To: asami@cs.berkeley.edu, gibbs, freebsd-bugs Subject: Re: kern/385 Sender: owner-bugs@FreeBSD.ORG Precedence: bulk Synopsis: ep0 finds card on irq 10 when it's actually on 11 State-Changed-From-To: open-closed State-Changed-By: gibbs State-Changed-When: Sun Feb 25 17:45:59 PST 1996 State-Changed-Why: This is "by design". The driver will set the card to the irq configured in the kernel config file or will use the irq set on the adapter if "irq ?" is specified. The solution to this users problem is to modify their config file. From owner-freebsd-bugs Sun Feb 25 17:50:53 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA10672 for bugs-outgoing; Sun, 25 Feb 1996 17:50:53 -0800 (PST) Received: (from gibbs@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA10653 Sun, 25 Feb 1996 17:50:50 -0800 (PST) Date: Sun, 25 Feb 1996 17:50:50 -0800 (PST) From: "Justin T. Gibbs" Message-Id: <199602260150.RAA10653@freefall.freebsd.org> To: root@amelie.frmug.fr.net, gibbs, freebsd-bugs Subject: Re: kern/532 Sender: owner-bugs@FreeBSD.ORG Precedence: bulk Synopsis: buslogic bt 445S hangups wit FreeBSD 2.0.5 State-Changed-From-To: open-closed State-Changed-By: gibbs State-Changed-When: Sun Feb 25 17:49:28 PST 1996 State-Changed-Why: This was a generic SCSI problem that has been fixed. From owner-freebsd-bugs Sun Feb 25 17:57:48 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA10991 for bugs-outgoing; Sun, 25 Feb 1996 17:57:48 -0800 (PST) Received: (from gibbs@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA10972 Sun, 25 Feb 1996 17:57:47 -0800 (PST) Date: Sun, 25 Feb 1996 17:57:47 -0800 (PST) From: "Justin T. Gibbs" Message-Id: <199602260157.RAA10972@freefall.freebsd.org> To: gibbs, freebsd-bugs, gibbs Subject: Re: kern/793 Sender: owner-bugs@FreeBSD.ORG Precedence: bulk Synopsis: ep0 cannot be configured and more. Responsible-Changed-From-To: freebsd-bugs->gibbs Responsible-Changed-By: gibbs Responsible-Changed-When: Sun Feb 25 17:56:28 PST 1996 Responsible-Changed-Why: I guess I'll owe up to fixing *some* of the ep driver's problems From owner-freebsd-bugs Sun Feb 25 17:58:36 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA11093 for bugs-outgoing; Sun, 25 Feb 1996 17:58:36 -0800 (PST) Received: (from gibbs@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA11073 Sun, 25 Feb 1996 17:58:34 -0800 (PST) Date: Sun, 25 Feb 1996 17:58:34 -0800 (PST) From: "Justin T. Gibbs" Message-Id: <199602260158.RAA11073@freefall.freebsd.org> To: gibbs, freebsd-bugs, gibbs Subject: Re: kern/730 Sender: owner-bugs@FreeBSD.ORG Precedence: bulk Synopsis: 3Com 3C5x9 probe problem Responsible-Changed-From-To: freebsd-bugs->gibbs Responsible-Changed-By: gibbs Responsible-Changed-When: Sun Feb 25 17:57:56 PST 1996 Responsible-Changed-Why: From owner-freebsd-bugs Sun Feb 25 18:02:26 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA11448 for bugs-outgoing; Sun, 25 Feb 1996 18:02:26 -0800 (PST) Received: (from gibbs@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA11437 Sun, 25 Feb 1996 18:02:24 -0800 (PST) Date: Sun, 25 Feb 1996 18:02:24 -0800 (PST) From: "Justin T. Gibbs" Message-Id: <199602260202.SAA11437@freefall.freebsd.org> To: widmer@cisco.com, gibbs, freebsd-bugs, gibbs Subject: Re: i386/394 Sender: owner-bugs@FreeBSD.ORG Precedence: bulk Synopsis: IP multicast not supported by ep driver State-Changed-From-To: open-closed State-Changed-By: gibbs State-Changed-When: Sun Feb 25 18:01:06 PST 1996 State-Changed-Why: This was fixed some time ago in -current. The changes will be going into -stable shortly. Responsible-Changed-From-To: freebsd-bugs->gibbs Responsible-Changed-By: gibbs Responsible-Changed-When: Sun Feb 25 18:01:06 PST 1996 Responsible-Changed-Why: I own these now, I guess. From owner-freebsd-bugs Sun Feb 25 18:50:04 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA13771 for bugs-outgoing; Sun, 25 Feb 1996 18:50:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA13765 Sun, 25 Feb 1996 18:50:03 -0800 (PST) Resent-Date: Sun, 25 Feb 1996 18:50:03 -0800 (PST) Resent-Message-Id: <199602260250.SAA13765@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, uhclem Received: from fw.ast.com (fw.ast.com [165.164.6.25]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA13538 for ; Sun, 25 Feb 1996 18:40:54 -0800 (PST) Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #2) id m0tqsoT-00084iC; Sun, 25 Feb 96 20:37 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #20) id m0tqslH-000CKVC; Sun, 25 Feb 96 20:34 WET Message-Id: Date: Sun, 25 Feb 96 20:34 WET From: uhclem@nemesis.lonestar.org Reply-To: uhclem To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: i386/1042: Warning from sio driver reports wrong device FDIV045 Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 1042 >Category: i386 >Synopsis: Warning from sio driver reports wrong device FDIV045 >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Feb 25 18:50:01 PST 1996 >Last-Modified: >Originator: Frank Durda IV >Organization: None >Release: FreeBSD 2.1-STABLE i386 >Environment: FreeBSD 2.1 system running a 486DX-33MHz 128K L2 Cache, 12Meg RAM, four 16550A serial ports (one NS16552 (dual port 16550A), two Startech 16550A), 1540B SCSI controller, WD8013 Ethernet (inactive). Ports sio0, sio2, sio3 connected to modems, sio1 not connected to anything for this test. Two of the ports connected to Telebit WorldBlazers configured at fixed DTE 57600. Also a Cardinal V.34 modem at DTE 57600 All modems have hardware flow control enabled. >Description: When the DTE speed of the WorldBlazers is increased from 38400 to 57600, the above system experiences "tty-level buffer overflows". As a symptom of the problem, UUCP sessions end up receiving corrupted files (this should not happen but it does), and the kernel reports messages like: Feb 25 19:48:00 nemesis /kernel: sio1: 247 more tty-level buffer overflows (total 3100) Note that the system reports the problem on sio1, when there is nothing connected to that port. That actual overrun probably occurred on sio0 or sio3. Another interesting thing is that the Cardinal modem is V.34 and receives compressed news at rates up to 3100CPS, but never appears to cause these overruns. The Telebits (Turbo PEP or PEP) only manage between 1600 and 2100 CPS and they do experience these overruns when the DTE is set to 57600. There are no overruns when the Worldblazers are fixed at 38400. Hardware flow control is set on all devices and uucico is patched to force RTSCTS flow control on incoming and outgoing UUCP sessions, and this can be verified by stty -a < /dev/tty[Dd]3. Modifying the sio.c driver to trigger at 8 instead of 14 reduces but does not eliminate the above error messages. Only reducing the DTE on the WorldBlazers back to 38400 eliminates the problem. I have also swapped ports in case the NS16552 and Startech parts were performing differently. The problem follows the ports used by the WorldBlazers. So the problems appear to be: 1. Faulty reporting of the guilty device in the kernel warning message. It seems to always blame sio1 regardless of what lines are active. 2. There doesn't appear to be any documentation on what the kernel error message is trying to report. Reducing the FIFO interrupt trigger did not help, implying a different type of overrun in the kernel instead of a hardware FIFO overrun. Because PEP tends to return data in bursts of 64 bytes, perhaps some software-based buffer is being overrun. Since there appears to be code in sio.c that would detect overruns in the hardware FIFO, report this and lower the trigger value automatically, either this code isn't working or this isn't the type of overrun the kernel is trying to report. Again, no documentation. 3. When the kernel message is displayed, it usually is displayed three times in a row, all with the same timestamp. It only appears once in /var/log/messages. >How-To-Repeat: Here, simply establish a protocol g or i UUCP session using Telebit WorldBlazers and receive data from a remote system with the DTE fixed at 57600. If the connection is at 22000bps or faster, failure is likely. Failures only appear during PEP/Turbo PEP sessions. >Fix: Workarounds: By reducing the hardware interrupt trigger to 8 (from 14), the error count was reduced, but not eliminated. The only sure-fire workaround is to lower the DTE speeds to 38400. *END* >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sun Feb 25 21:33:18 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA23869 for bugs-outgoing; Sun, 25 Feb 1996 21:33:18 -0800 (PST) Received: from seanet.com (kesha.seanet.com [199.181.164.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA23858 for ; Sun, 25 Feb 1996 21:33:16 -0800 (PST) Received: from MindBender.HeadCandy.com by seanet.com with ESMTP (8.6.12/25-eef) id VAA24860; Sun, 25 Feb 1996 21:33:10 -0800 Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.4/8.6.9) with SMTP id VAA10264; Sun, 25 Feb 1996 21:33:08 -0800 (PST) Message-Id: <199602260533.VAA10264@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: darrenr@cyber.com.au cc: freebsd-bugs@freebsd.org, port-i386@netbsd.org Subject: Re: Incompatible slices. In-reply-to: Your message of Mon, 26 Feb 96 00:51:46 +1100. <199602251351.AAA01557@plum.cyber.com.au> Date: Sun, 25 Feb 1996 21:32:00 -0800 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-bugs@freebsd.org Precedence: bulk >I'd like to report that partition slices in FreeBSD 2.1.0 and NetBSD 1.1 >aren't 100% compatible. I wasn't aware NetBSD even *had* "slices". ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, HP300, Sun3, Sun4, DEC PMAX (MIPS), DEC Alpha, PC532 NetBSD ports in progress: VAX, Atari 68k, others... ----------------------------------------------------------------------------- From owner-freebsd-bugs Sun Feb 25 23:34:04 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA00555 for bugs-outgoing; Sun, 25 Feb 1996 23:34:04 -0800 (PST) Received: from plum.cyber.com.au (plum.cyber.com.au [203.7.155.24]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA00543 for ; Sun, 25 Feb 1996 23:33:56 -0800 (PST) Received: (from darrenr@localhost) by plum.cyber.com.au (8.6.12/8.6.6) id SAA03149; Mon, 26 Feb 1996 18:27:25 +1100 From: Darren Reed Message-Id: <199602260727.SAA03149@plum.cyber.com.au> Subject: Re: Incompatible slices. To: michaelv@HeadCandy.com (Michael L. VanLoon -- HeadCandy.com) Date: Mon, 26 Feb 1996 18:27:24 +1100 (EST) Cc: darrenr@cyber.com.au, freebsd-bugs@freebsd.org, port-i386@netbsd.org In-Reply-To: <199602260533.VAA10264@MindBender.HeadCandy.com> from "Michael L. VanLoon -- HeadCandy.com" at Feb 25, 96 09:32:00 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-bugs@freebsd.org Precedence: bulk In some mail I received from Michael L. VanLoon -- HeadCandy.com, sie wrote > > > >I'd like to report that partition slices in FreeBSD 2.1.0 and NetBSD 1.1 > >aren't 100% compatible. > > I wasn't aware NetBSD even *had* "slices". It depends on what you want to call it, I guess, but is a good a name as any for describing partitioning within a partition. FreeBSD distinguishes them as "wd0s[1-4][a-h]". So what would have been wd0g is now wd0s1g, for example. Linux doesn't support this (1.2.13) at all, from what I can tell. Solaris 2.x x86 does (haven't tried to mount one of those partitions yet, but will try tonight or later this week). Yes, I'm trying to make all 4 co-exist on one box...Interestingly, the Solaris 2 partition shows up as "Linux Swap" under various fdisks...and otherwise forgetting about Linux as much as possible. In my case, I've got 7 partitions across 2 disks, with 2 for DOS, 1 for Solaris, 1 for Linux, 3 for BSD. To make booting work, the boot partition for each of FreeBSD and NetBSD needs to be on a separate disk (unless I want to play with what is active and not all the time). The third BSD partition is being used to provide "private" extra trees for each whilst also (hopefully) provide a common partition (for stuff like netscape, etc). DOS's 4 partition rule is a pain. btw, I'm coming to the realisation that I'm insane attempting this >%-) From owner-freebsd-bugs Sun Feb 25 23:50:03 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA01527 for bugs-outgoing; Sun, 25 Feb 1996 23:50:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA01521 Sun, 25 Feb 1996 23:50:02 -0800 (PST) Date: Sun, 25 Feb 1996 23:50:02 -0800 (PST) Message-Id: <199602260750.XAA01521@freefall.freebsd.org> To: freebsd-bugs Cc: From: Bruce Evans Subject: Re: i386/1042: Warning from sio driver reports wrong device FDIV045 Reply-To: Bruce Evans Sender: owner-bugs@FreeBSD.ORG Precedence: bulk The following reply was made to PR i386/1042; it has been noted by GNATS. From: Bruce Evans To: FreeBSD-gnats-submit@FreeBSD.ORG, uhclem@freefall.freebsd.org Cc: Subject: Re: i386/1042: Warning from sio driver reports wrong device FDIV045 Date: Mon, 26 Feb 1996 18:33:51 +1100 >... >Ports sio0, sio2, sio3 connected to modems, sio1 not connected to anything ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >... >Feb 25 19:48:00 nemesis /kernel: sio1: 247 more tty-level buffer overflows (total 3100) >Note that the system reports the problem on sio1, when there is nothing >connected to that port. That actual overrun probably occurred on sio0 >or sio3. This may be caused by sio1 picking up radiation from the other ports. It shouldn't occur if sio1 isn't open, however (then the UART may be kept busy by the radiation but the driver ignores it). The radiation problem can usually be fixed by connecting the port to something (even something inactive). The verbose error reporting can take long enough to interfere with the reception of futher data :-(. Errors were once reported every clock tick (the rc driver still does this) and slow machines take more than one clock tick to report an error so the first error triggered an endless cascade of errors. >Another interesting thing is that the Cardinal modem is V.34 and receives >compressed news at rates up to 3100CPS, but never appears to cause >these overruns. The Telebits (Turbo PEP or PEP) only manage between >1600 and 2100 CPS and they do experience these overruns when the DTE >is set to 57600. There are no overruns when the Worldblazers are fixed >at 38400. Do the Telebits honour flow control? >So the problems appear to be: >1. Faulty reporting of the guilty device in the kernel warning message. > It seems to always blame sio1 regardless of what lines are active. Probably not. >2. There doesn't appear to be any documentation on what the kernel > error message is trying to report. See the sio man page. > Reducing the FIFO interrupt trigger did not help, implying a > different type of overrun in the kernel instead of a hardware FIFO > overrun. Because PEP tends to return data in bursts of 64 bytes, > perhaps some software-based buffer is being overrun. The raw queue has a size of only 1024 at all baud rates so it is quite easy to overrun at high baud rates. At 115200 bps, 1024 bytes may arrive in less than one process scheduling quantum (100 msec) so there the buffer is too small if there are 2 hog processes. Flow control had better work. > Since there appears to be code in sio.c that would detect overruns > in the hardware FIFO, report this and lower the trigger value > automatically, either this code isn't working or this isn't the > type of overrun the kernel is trying to report. Again, no > documentation. That code has almost always been disabled and doesn't exist in -current. It tended to drop the trigger level to 1 for transient errors. >3. When the kernel message is displayed, it usually is displayed three > times in a row, all with the same timestamp. It only appears once > in /var/log/messages. Messages are normally repeated for each root login. Bruce From owner-freebsd-bugs Mon Feb 26 00:26:37 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA04268 for bugs-outgoing; Mon, 26 Feb 1996 00:26:37 -0800 (PST) Received: from frig.mt.cs.keio.ac.jp (frig.mt.cs.keio.ac.jp [131.113.32.7]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA04262 for ; Mon, 26 Feb 1996 00:26:31 -0800 (PST) Received: (from hosokawa@localhost) by frig.mt.cs.keio.ac.jp (8.6.12+2.4W/3.4Wbeta3) id RAA10660; Mon, 26 Feb 1996 17:20:53 +0900 Date: Mon, 26 Feb 1996 17:20:53 +0900 Message-Id: <199602260820.RAA10660@frig.mt.cs.keio.ac.jp> To: bugs@freebsd.org Cc: hosokawa@mt.cs.keio.ac.jp Subject: sysinstall bug From: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.18PL3] 1994-08/01(Mon) Sender: owner-bugs@freebsd.org Precedence: bulk sysinstall can't find any network device that is probed after tun0. hosokawa --- devices.c.orig Wed Nov 15 15:57:02 1995 +++ devices.c Sat Feb 17 18:53:59 1996 @@ -319,8 +319,9 @@ continue; /* Eliminate network devices that don't make sense */ if (!strncmp(ifptr->ifr_name, "tun", 3) + || !strncmp(ifptr->ifr_name, "sl", 2) || !strncmp(ifptr->ifr_name, "lo0", 3)) - continue; + goto loopend; deviceRegister(ifptr->ifr_name, ifptr->ifr_name, ifptr->ifr_name, DEVICE_TYPE_NETWORK, TRUE, mediaInitNetwork, NULL, NULL, mediaShutdownNetwork, NULL); msgDebug("Found a device of type network named: %s\n", ifptr->ifr_name); @@ -330,6 +331,7 @@ msgConfirm("ifconfig: socket"); continue; } +loopend: if (ifptr->ifr_addr.sa_len) /* I'm not sure why this is here - it's inherited */ ifptr = (struct ifreq *)((caddr_t)ifptr + ifptr->ifr_addr.sa_len - sizeof(struct sockaddr)); } From owner-freebsd-bugs Mon Feb 26 00:38:48 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA04828 for bugs-outgoing; Mon, 26 Feb 1996 00:38:48 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA04821 for ; Mon, 26 Feb 1996 00:38:32 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id TAA29001; Mon, 26 Feb 1996 19:32:31 +1100 Date: Mon, 26 Feb 1996 19:32:31 +1100 From: Bruce Evans Message-Id: <199602260832.TAA29001@godzilla.zeta.org.au> To: darrenr@cyber.com.au, etheisen@teclink.net Subject: Re: Incompatible slices. Cc: etheisen@ozzy, freebsd-bugs@freebsd.org, port-i386@NetBSD.ORG Sender: owner-bugs@freebsd.org Precedence: bulk >The difference's are because of BIOS geometery. No, the messages are because the FreeBSD drivers hide the DOS partitions from the BSD parts of the system. They are to give enough information to recover a 386BSD/NetBSD label (with DOS cruft inside the label) after the drivers have rewritten the label to hide the DOS partitions. >FreeBSD correctly >uses the BIOS geo for partition layout. No, only the FreeBSD sysinstall, fdisk and boot programs use the BIOS geometry. The drivers don't use it, but they attempt to determine it (so that they can reporte it to sysinstall and fdisk) by looking at the contents of the DOS partition table. Of course, this can only work if the partition table is nonempty, and it often gives the wrong results unless the partition table follows defacto standard conventions. FreeBSD doesn't determine the BIOS geometry in the "correct" way because this is very difficult to do automatically. It would involve the following steps: for each drive supported by the BIOS # The following self-referential step is required # because many modern SCSI BIOSes attempt to determine # the geometry by looking at the partition table. Run utilities to write the final partition table. # If the drive has Boot Manager on it, then its # geometry will probably be different if you boot # from a floppy unless you load the BM drivers # from the floppy. Ensure a standard boot environment. Ask the BIOS for the geometry. Record this geometry and don't allow it to magically change when someone forgets to set up the standard boot environment... Map this drive to a BSD drive and don't allow the mapping to change. # The mapping should probably be indexed by the BIOS # drive number. This is hard because the BIOS decides # how to assign drive numbers and doesn't tell you. # Consider multiple SCSI chains with multiple removable # drives (some removed) on each. Some BIOSes will only # see the attached drives... end for for each drive NOT supported by the BIOS Choose a working geometry and don't allow it to magically change. Don't allow this drive to mutate to a BIOS drive when someone changes the cables... Map this drive to a BSD drive and don't allow the mapping to change. end for Pass enough info about all drives from the boot stage(s) to the kernel. >NetBSD does it own thing >based upon a default partioning scheme layed out in the 1st stage >loader. Or it uses it idea of the drives native geo. We need to >work on getting this resolved. It has caused newcomers serious >grief. Plus it's partioning scheme is not PC OS compatible. I think NetBSD allows almost any partitioning scheme to be specified in fdisk and disklabel. It's up to the installation programs and installation people whether it works. > 1) Partion geo should always be layed out in the MBR in > exact same geo that DOG would use. See above about the self-referential nature of partitioning. The DOG geometry is sometimes determined by the BSD geometry if BSD is installed first. > 2) The actual size should be used, not 24MB. Certainly. > 3) Same goes for beginning/end addresses. This is impossible if the geometry isn't know. Using the wrong geometry is worse than useless. There seems to be be a convention that 1023/255/63 means "don't know". > 3) The first track as defined by DOG should be skipped. ^ 4 This is too restrictive since it isn't compatible with using the whole disk for BSD. (1)-(3) are probably sufficient for stopping foreign installation programs from deciding that the partition table is garbage and reinitializing it. Bruce From owner-freebsd-bugs Mon Feb 26 01:20:08 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA06558 for bugs-outgoing; Mon, 26 Feb 1996 01:20:08 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA06525 Mon, 26 Feb 1996 01:20:05 -0800 (PST) Resent-Date: Mon, 26 Feb 1996 01:20:05 -0800 (PST) Resent-Message-Id: <199602260920.BAA06525@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, ian@smartmedia.co.uk Received: from opti.smartmedia.co.uk (opti.smartmedia.co.uk [194.159.153.4]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA05899 for ; Mon, 26 Feb 1996 01:09:58 -0800 (PST) Received: (from ian@localhost) by opti.smartmedia.co.uk (8.6.11/8.960220) id JAA16050; Mon, 26 Feb 1996 09:09:59 GMT Message-Id: <199602260909.JAA16050@opti.smartmedia.co.uk> Date: Mon, 26 Feb 1996 09:09:59 GMT From: ian@smartmedia.co.uk Reply-To: ian@smartmedia.co.uk To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: misc/1043: vm_bounce_alloc during install of 2.1 Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 1043 >Category: misc >Synopsis: vm_bounce_alloc error on 2.1 install with 4G drive >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Feb 26 01:20:03 PST 1996 >Last-Modified: >Originator: Ian williams >Organization: Smart Media >Release: FreeBSD 2.1 >Environment: 90MHz Intel Plato, 32M RAM PCI Buslogic 946 (out of box config = DOS translation on) 1G+4G (ST15150N) disks >Description: Get vm_bounce_alloc during install (or W command in Partition table edit) When creating a BSD partition start 4194304 size 4192256 (2047 Meg) (In custom install) (/ file system is on 1G disk) >How-To-Repeat: Try to create partition again. >Fix: Work around, install BSD partition: start 32 size 4194272 (2047 Meg) Move other data on disk to partition start 4194304 size 4192256 >Audit-Trail: >Unformatted: From owner-freebsd-bugs Mon Feb 26 07:12:05 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA23592 for bugs-outgoing; Mon, 26 Feb 1996 07:12:05 -0800 (PST) Received: from fw.ast.com (fw.ast.com [165.164.6.25]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA23525 for ; Mon, 26 Feb 1996 07:12:01 -0800 (PST) Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #2) id m0tr4Y6-00084cC; Mon, 26 Feb 96 09:09 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #20) id m0tr4Bj-000DDbC; Mon, 26 Feb 96 08:46 WET Message-Id: Date: Mon, 26 Feb 96 08:46 WET To: freebsd-bugs@freefall.freebsd.org From: uhclem@nemesis.lonestar.org (Frank Durda IV) Sent: Mon Feb 26 1996, 08:46:06 CST Subject: Re: i386/1042: Warning from sio driver reports wrong device FDIV045 Sender: owner-bugs@FreeBSD.ORG Precedence: bulk [1]From: Bruce Evans [1]The following reply was made to PR i386/1042; it has been noted by GNATS. Well I guess this additional input won't be in there... :-) [0]Ports sio0, sio2, sio3 connected to modems, sio1 not connected to anything [0] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [0]Feb 25 19:48:00 nemesis /kernel: sio1: 247 more tty-level buffer overflows (total 3100) [0]Note that the system reports the problem on sio1, when there is nothing [0]connected to that port. That actual overrun probably occurred on sio0 [0]or sio3. [1]This may be caused by sio1 picking up radiation from the other ports. [1]It shouldn't occur if sio1 isn't open, however (then the UART may be [1]kept busy by the radiation but the driver ignores it). The radiation [1]problem can usually be fixed by connecting the port to something (even [1]something inactive). This is not the case. One of the WorldBlazers was connected to sio1 but was not taking calls when the problem was noticed. To simplify the error report, the modems were moved off the ports to see if the problem moved. The error message did not follow the modems. No matter what modem or modems were busy, the error message always said sio1. [1]The verbose error reporting can take long enough to interfere with the [1]reception of futher data :-(. Errors were once reported every clock [1]tick (the rc driver still does this) and slow machines take more than [1]one clock tick to report an error so the first error triggered an [1]endless cascade of errors. They usually appear at the end of a call (including successful calls), so that also seems unlikely. [0]Another interesting thing is that the Cardinal modem is V.34 and receives [0]compressed news at rates up to 3100CPS, but never appears to cause [0]these overruns. The Telebits (Turbo PEP or PEP) only manage between [0]1600 and 2100 CPS and they do experience these overruns when the DTE [0]is set to 57600. There are no overruns when the Worldblazers are fixed [0]at 38400. [1]Do the Telebits honour flow control? Yes. Several types. I currently have WorldBlazer - SA - Version LA7.05C- Active Configuration B1 E0 L1 M0 Q2 T V1 X2 Y0 &C1 &D3 &G0 &J0 &L0 &Q1 &R3 &S1 &T4 &X0 S000:1 S001=0 S002:128 S003=13 S004=10 S005=8 S006=2 S007=60 S008=2 S009=6 S010=14 S011=70 S012=50 S018=0 S025=5 S026=1 S038=0 S041:10 S045=0 S046=0 S047=4 S048:1 S050:255 S051:6 S056=17 S057=19 S058:2 S059:15 S060=0 S061:0 S062=15 S063=0 S064:1 S068=255 S069=0 S090=0 S092:1 S093=8 S094=1 S100=0 S104=0 S105=1 S111:0 S112=1 S113=126 S114=0 S115=0 S116=0 S119=0 S151=4 S155=0 S180=2 S181=1 S183=25 S190=1 S191=7 S253=10 S254=255 S255=255 OK S68 == 255 which says look at setting in S58 S58 == 2 which says Use full-duplex RTS/CTS flow control. When RTS is off, the modem does not send data to the local DTE. When RTS is on, the modem sends data to the local DTE. When CTS is ON, the modem can accept data; when CTS is off, the modem cannot accept data. [0]So the problems appear to be: [0]1. Faulty reporting of the guilty device in the kernel warning message. [0] It seems to always blame sio1 regardless of what lines are active. [1]Probably not. See above. This is happening when a device is present but inactive. No line noise. [0]2. There doesn't appear to be any documentation on what the kernel [0] error message is trying to report. [1]See the sio man page. Ok, how do I "fix the application?" (uucico) as the man page cryptically suggests when the application runs fine on other ports running at 57600 with faster DCE data rates (28.8 vs 24)? If we have the equivalent of a TTYHOG or CLIST limits, where are they controlled? (I have already looked at the LINT kernel.) [0] Reducing the FIFO interrupt trigger did not help, implying a [0] different type of overrun in the kernel instead of a hardware FIFO [0] overrun. Because PEP tends to return data in bursts of 64 bytes, [0] perhaps some software-based buffer is being overrun. [1]The raw queue has a size of only 1024 at all baud rates so it is quite [1]easy to overrun at high baud rates. At 115200 bps, 1024 bytes may arrive [1]in less than one process scheduling quantum (100 msec) so there the buffer [1]is too small if there are 2 hog processes. Flow control had better work. Problem was repeatedly demonstrated with only one modem active. No other serial activity seen. [0] Since there appears to be code in sio.c that would detect overruns [0] in the hardware FIFO, report this and lower the trigger value [0] automatically, either this code isn't working or this isn't the [0] type of overrun the kernel is trying to report. Again, no [0] documentation. [1]That code has almost always been disabled and doesn't exist in -current. [1]It tended to drop the trigger level to 1 for transient errors. Great. :-( It was one of the few parts of the driver that wasn't goofy. The figure-out-what-type-of-UART-you-have is a bad idea and can freak on many internal modems. "Reserved" and "0" for apparently-unused bits mean different things to different silicon vendors. [0]3. When the kernel message is displayed, it usually is displayed three [0] times in a row, all with the same timestamp. It only appears once [0] in /var/log/messages. [1]Messages are normally repeated for each root login. Ok, all that said, flow control is working (although it may not respond as fast as our take-it-to-the-edge scheme can stand), but it still sounds like the serial buffer resources are too limited. Geez, I was running four modems like this on a 8MHz 68000 system years ago and not having this problem. Frank Durda IV |"The Knights who say "LETNi" or uhclem%nemesis@rwsystr.nkn.net | demand... A SEGMENT REGISTER!!!" |"A what?" or ...letni!rwsys!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983 From owner-freebsd-bugs Mon Feb 26 08:51:25 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA00469 for bugs-outgoing; Mon, 26 Feb 1996 08:51:25 -0800 (PST) Received: from glacier.MIT.EDU (GLACIER.MIT.EDU [18.248.0.54]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA00464 for ; Mon, 26 Feb 1996 08:51:23 -0800 (PST) Received: (from ghudson@localhost) by glacier.MIT.EDU (8.6.12/8.6.11) id LAA05895; Mon, 26 Feb 1996 11:51:10 -0500 Message-Id: <199602261651.LAA05895@glacier.MIT.EDU> To: Bruce Evans cc: darrenr@cyber.com.au, etheisen@teclink.net, etheisen@ozzy.MIT.EDU, freebsd-bugs@freebsd.org, port-i386@NetBSD.ORG Subject: Re: Incompatible slices. In-reply-to: Your message of "Mon, 26 Feb 1996 19:32:31 +1100." <199602260832.TAA29001@godzilla.zeta.org.au> Date: Mon, 26 Feb 1996 11:51:09 EST From: Greg Hudson Sender: owner-bugs@freebsd.org Precedence: bulk > No, only the FreeBSD sysinstall, fdisk and boot programs use the > BIOS geometry. The drivers don't use it, but they attempt to > determine it (so that they can reporte it to sysinstall and fdisk) > by looking at the contents of the DOS partition table. I think you're confused, or perhaps only talking about SCSI disks. >From sys/i386/boot/biosboot: /* Pick up the story from the Bios on geometry of disks */ for(ret = 0; ret < N_BIOS_GEOM; ret ++) bootinfo.bi_bios_geom[ret] = get_diskinfo(ret + 0x80); and then from sys/i386/isa/wd.c, in wdgetctlr(): if (du->dk_unit == bootinfo.bi_n_bios_used) { du->dk_dd.d_secsize = DEV_BSIZE; du->dk_dd.d_nsectors = bootinfo.bi_bios_geom[du->dk_unit] & 0xff; [etc.] bootinfo.bi_n_bios_used ++; return 0; } I haven't examined the SCSI code get. > Of course, this can only work if the partition table is nonempty, > and it often gives the wrong results unless the partition table > follows defacto standard conventions. I added code to the NetBSD fdisk to do this kind of heuristic calculation, and it does not rely on any de facto partition table conventions. It treats each partition table entry as an equation, and attempts to find non-degenerate equations in the partition table which will yield the number of sectors per track and the number of heads. Arguably, the code should have gone into the disk drivers (so that disklabel can work properly), but I'd rather see the drivers use the BIOS geometry. > # The following self-referential step is required > # because many modern SCSI BIOSes attempt to determine > # the geometry by looking at the partition table. So what do they do if there's no partition table? They have to return something; as long as it's a valid geometry for the disk, you should be able to use it and the next time the BIOS is queried for the disk geometry, it should return the same thing. From owner-freebsd-bugs Mon Feb 26 11:04:07 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA08461 for bugs-outgoing; Mon, 26 Feb 1996 11:04:07 -0800 (PST) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA08328 for ; Mon, 26 Feb 1996 11:03:46 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.7.3/8.6.12) with SMTP id KAA01560; Mon, 26 Feb 1996 10:59:13 -0800 (PST) Message-Id: <199602261859.KAA01560@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: Host localhost [127.0.0.1] didn't use HELO protocol To: "Michael L. VanLoon -- HeadCandy.com" Cc: darrenr@cyber.com.au, freebsd-bugs@freebsd.org, port-i386@netbsd.org Subject: Re: Incompatible slices. Reply-To: Jason Thorpe From: Jason Thorpe Date: Mon, 26 Feb 1996 10:59:11 -0800 Sender: owner-bugs@freebsd.org Precedence: bulk On Sun, 25 Feb 1996 21:32:00 -0800 "Michael L. VanLoon -- HeadCandy.com" wrote: > >I'd like to report that partition slices in FreeBSD 2.1.0 and NetBSD 1.1 > >aren't 100% compatible. > > I wasn't aware NetBSD even *had* "slices". AFAIK, we *don't*. I think the FreeBSD notion of "slices" is what's created by the DOS partition table. FreeBSD get's a "slice" of the disk (we call this the "NetBSD portion of the disk") and partitions it up. This is based on quick scans of the FreeBSD code ... I could be totally wrong. -------------------------------------------------------------------------- Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: 408.866.1912 NAS: M/S 258-6 Work: 415.604.0935 Moffett Field, CA 94035 Pager: 415.428.6939 From owner-freebsd-bugs Mon Feb 26 13:21:45 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA17583 for bugs-outgoing; Mon, 26 Feb 1996 13:21:45 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA17569 for ; Mon, 26 Feb 1996 13:21:40 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA11946; Mon, 26 Feb 1996 22:20:47 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id WAA21456; Mon, 26 Feb 1996 22:20:25 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id WAA01165; Mon, 26 Feb 1996 22:16:22 +0100 (MET) From: J Wunsch Message-Id: <199602262116.WAA01165@uriah.heep.sax.de> Subject: Re: Incompatible slices. To: bde@zeta.org.au (Bruce Evans) Date: Mon, 26 Feb 1996 22:16:22 +0100 (MET) Cc: darrenr@cyber.com.au, etheisen@teclink.net, etheisen@ozzy, freebsd-bugs@FreeBSD.ORG, port-i386@NetBSD.ORG Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199602260832.TAA29001@godzilla.zeta.org.au> from "Bruce Evans" at Feb 26, 96 07:32:31 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-bugs@FreeBSD.ORG Precedence: bulk As Bruce Evans wrote: > > 3) The first track as defined by DOG should be skipped. > ^ 4 > > This is too restrictive since it isn't compatible with using the whole > disk for BSD. (1)-(3) are probably sufficient for stopping foreign > installation programs from deciding that the partition table is garbage > and reinitializing it. Apparently. Except that somebody who wants to recycle a BSD disk has to care to use ``fdisk /mbr'' in DOG, or to dd /dev/zero over the first hundred or so sectors from within BSD.. Otherwise, DOG does re-use the first sector of the BSD bootstrap, and only updates the fdisk entries. :-) (At least some reason why we call it ``Dangerously dedicated.'') -- 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-bugs Mon Feb 26 14:02:17 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA21064 for bugs-outgoing; Mon, 26 Feb 1996 14:02:17 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA21047 for ; Mon, 26 Feb 1996 14:01:41 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id IAA24553; Tue, 27 Feb 1996 08:43:12 +1100 Date: Tue, 27 Feb 1996 08:43:12 +1100 From: Bruce Evans Message-Id: <199602262143.IAA24553@godzilla.zeta.org.au> To: bde@zeta.org.au, ghudson@mit.edu Subject: Re: Incompatible slices. Cc: darrenr@cyber.com.au, etheisen@ozzy.MIT.EDU, etheisen@teclink.net, freebsd-bugs@FreeBSD.org, port-i386@NetBSD.ORG Sender: owner-bugs@FreeBSD.org Precedence: bulk >> No, only the FreeBSD sysinstall, fdisk and boot programs use the >> BIOS geometry. The drivers don't use it, but they attempt to >> determine it (so that they can reporte it to sysinstall and fdisk) >> by looking at the contents of the DOS partition table. >I think you're confused, or perhaps only talking about SCSI disks. No, I know too much about this problem. >From sys/i386/boot/biosboot: > /* Pick up the story from the Bios on geometry of disks */ > for(ret = 0; ret < N_BIOS_GEOM; ret ++) > bootinfo.bi_bios_geom[ret] = get_diskinfo(ret + 0x80); This gives you the BIOS geometries indexed by the BIOS drive numbers. It can only be used if the mapping from the BIOS drive numbers to BSD device names or numbers are known. The mapping isn't known. >and then from sys/i386/isa/wd.c, in wdgetctlr(): > if (du->dk_unit == bootinfo.bi_n_bios_used) { > du->dk_dd.d_secsize = DEV_BSIZE; > du->dk_dd.d_nsectors = > bootinfo.bi_bios_geom[du->dk_unit] & 0xff; > [etc.] > bootinfo.bi_n_bios_used ++; > return 0; > } This code only works in the usual case of one controller with one (master) drive or 2 drives attached to it. It probably fails for 2 controllers with one (master) drive on each and some mixture of cdroms on the slave channels, because the BIOS numbers the drives 0 and 1 while BSD numbers them 0 and 2. Fortunately, this code is only used for drives that don't report their default geometry (probably never for modern drives). There's another bug there if the first drive reports its geometry and the others don't - bi_n_bios_used isn't incremented for the first drive. >> Of course, this can only work if the partition table is nonempty, >I added code to the NetBSD fdisk to do this kind of heuristic >calculation, and it does not rely on any de facto partition table >conventions. It treats each partition table entry as an equation, and >attempts to find non-degenerate equations in the partition table which >will yield the number of sectors per track and the number of heads. I had forgotten about this method. I think it works well iff there is more than one partition. >> # The following self-referential step is required >> # because many modern SCSI BIOSes attempt to determine >> # the geometry by looking at the partition table. >So what do they do if there's no partition table? They have to return >something; as long as it's a valid geometry for the disk, you should >be able to use it and the next time the BIOS is queried for the disk >geometry, it should return the same thing. I'm most familiar with the BT445C controller. I think it chooses a 64 head, 32 sector geometry for empty disks even when its '> 1GB' option is enabled, even though that is poor geometry for drives larger than 1GB. It returned 255H 63S as soon as I repartitioned a drive from 64H 32S to 255H 63S (without changing the partition offsets or the OS's) and the changed geometry continued to work when I moved the drive to an SC200 controller on another system. This makes sense: the geometry is a property of the drive and the controller should handle geometries that were defaulted to on other controllers. Bruce From owner-freebsd-bugs Mon Feb 26 16:30:06 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA01604 for bugs-outgoing; Mon, 26 Feb 1996 16:30:06 -0800 (PST) Received: (from wosch@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA01577 Mon, 26 Feb 1996 16:30:03 -0800 (PST) Date: Mon, 26 Feb 1996 16:30:03 -0800 (PST) From: Wolfram Schneider Message-Id: <199602270030.QAA01577@freefall.freebsd.org> To: obrien@cs.ucdavis.edu, wosch, freebsd-bugs Subject: Re: docs/1039 Sender: owner-bugs@FreeBSD.ORG Precedence: bulk Synopsis: two different spellings of "timezone" State-Changed-From-To: open-closed State-Changed-By: wosch State-Changed-When: Mon Feb 26 16:28:08 PST 1996 State-Changed-Why: submitted fix applied From owner-freebsd-bugs Mon Feb 26 18:38:01 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA11540 for bugs-outgoing; Mon, 26 Feb 1996 18:38:01 -0800 (PST) Received: (from asami@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA11521 Mon, 26 Feb 1996 18:38:00 -0800 (PST) Date: Mon, 26 Feb 1996 18:38:00 -0800 (PST) From: Satoshi Asami Message-Id: <199602270238.SAA11521@freefall.freebsd.org> To: asami, freebsd-bugs Subject: Re: ports/1041 Sender: owner-bugs@FreeBSD.ORG Precedence: bulk Synopsis: ports submissions Responsible-Changed-From-To: freebsd-bugs->freebsd-ports Responsible-Changed-By: asami Responsible-Changed-When: Mon Feb 26 18:37:15 PST 1996 Responsible-Changed-Why: Obvious. :) From owner-freebsd-bugs Mon Feb 26 22:51:31 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA04352 for bugs-outgoing; Mon, 26 Feb 1996 22:51:31 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA04343 for ; Mon, 26 Feb 1996 22:51:26 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id HAA23317; Tue, 27 Feb 1996 07:50:32 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id HAA25888; Tue, 27 Feb 1996 07:50:20 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id HAA02281; Tue, 27 Feb 1996 07:37:42 +0100 (MET) From: J Wunsch Message-Id: <199602270637.HAA02281@uriah.heep.sax.de> Subject: Re: Incompatible slices. To: thorpej@nas.nasa.gov Date: Tue, 27 Feb 1996 07:37:42 +0100 (MET) Cc: michaelv@headcandy.com, darrenr@cyber.com.au, freebsd-bugs@FreeBSD.ORG, port-i386@netbsd.org In-Reply-To: <199602261859.KAA01560@lestat.nas.nasa.gov> from "Jason Thorpe" at Feb 26, 96 10:59:11 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-bugs@FreeBSD.ORG Precedence: bulk As Jason Thorpe wrote: > I think the FreeBSD notion of "slices" is what's > created by the DOS partition table. FreeBSD get's a "slice" of the disk > (we call this the "NetBSD portion of the disk") and partitions it up. > > This is based on quick scans of the FreeBSD code ... I could be totally > wrong. You're absolutely right. There used to be a ``README.slices'' someday explaining this... -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Mon Feb 26 23:40:05 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA09665 for bugs-outgoing; Mon, 26 Feb 1996 23:40:05 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA09644 Mon, 26 Feb 1996 23:40:03 -0800 (PST) Resent-Date: Mon, 26 Feb 1996 23:40:03 -0800 (PST) Resent-Message-Id: <199602270740.XAA09644@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, muir@idiom.com Received: from idiom.com (idiom.com [140.174.82.4]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA08854 for ; Mon, 26 Feb 1996 23:34:21 -0800 (PST) Received: (from muir@localhost) by idiom.com (8.6.12/8.6.12) id XAA09032; Mon, 26 Feb 1996 23:34:18 -0800 Message-Id: <199602270734.XAA09032@idiom.com> Date: Mon, 26 Feb 1996 23:34:18 -0800 From: David Muir Sharnoff Reply-To: muir@idiom.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: docs/1044: clri(8) man page references man pages that don't exist Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 1044 >Category: docs >Synopsis: clri(8) man page references man pages that don't exist >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Mon Feb 26 23:40:01 PST 1996 >Last-Modified: >Originator: David Muir Sharnoff >Organization: Idiom Consulting >Release: FreeBSD 2.1-STABLE i386 >Environment: >Description: Does anyone use clri any more? Anyone? I've only been using unix for twelve years and I've never had to use clri. In any case, the clri documentation references: fsdb(8) icheck(8) ncheck(8) none of which exist. >How-To-Repeat: >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue Feb 27 06:00:04 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA19398 for bugs-outgoing; Tue, 27 Feb 1996 06:00:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA19357 Tue, 27 Feb 1996 06:00:02 -0800 (PST) Date: Tue, 27 Feb 1996 06:00:02 -0800 (PST) Message-Id: <199602271400.GAA19357@freefall.freebsd.org> To: freebsd-bugs Cc: From: J Wunsch Subject: Re: docs/1044: clri(8) man page references man pages that don't exist Reply-To: J Wunsch Sender: owner-bugs@FreeBSD.ORG Precedence: bulk The following reply was made to PR docs/1044; it has been noted by GNATS. From: J Wunsch To: muir@idiom.com Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: docs/1044: clri(8) man page references man pages that don't exist Date: Tue, 27 Feb 1996 14:28:36 +0100 (MET) As David Muir Sharnoff wrote: > In any case, the clri documentation references: > > fsdb(8) icheck(8) ncheck(8) > > none of which exist. fsdb(8) exists now. icheck(8) used to exist, but has apparently vanished at the transition to 4.4BSD-Lite. -- 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-bugs Tue Feb 27 08:27:13 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA01078 for bugs-outgoing; Tue, 27 Feb 1996 08:27:13 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA01035 for ; Tue, 27 Feb 1996 08:26:40 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id DAA06241; Wed, 28 Feb 1996 03:25:22 +1100 Date: Wed, 28 Feb 1996 03:25:22 +1100 From: Bruce Evans Message-Id: <199602271625.DAA06241@godzilla.zeta.org.au> To: freebsd-bugs@freefall.freebsd.org, uhclem@nemesis.lonestar.org Subject: Re: i386/1042: Warning from sio driver reports wrong device FDIV045 Sender: owner-bugs@FreeBSD.ORG Precedence: bulk >[1]The following reply was made to PR i386/1042; it has been noted by GNATS. >Well I guess this additional input won't be in there... :-) It's a bit too easy to have replies noted by GNATS. >[0]Note that the system reports the problem on sio1, when there is nothing >[0]connected to that port. That actual overrun probably occurred on sio0 >[0]or sio3. > >[1]This may be caused by sio1 picking up radiation from the other ports. >This is not the case. One of the WorldBlazers was connected to >sio1 but was not taking calls when the problem was noticed. To simplify >the error report, the modems were moved off the ports to see if the >problem moved. The error message did not follow the modems. >No matter what modem or modems were busy, the error message always >said sio1. There isn't much that can go wrong in counting and reporting the errors. Please report the output from `pstat -t' run while errors are arriving. I usually get error messages for sio0, e.g.: Feb 24 00:07:51 alphplex /kernel: sio0: 2168190 more interrupt-level buffer overflows (total 3476872) I bet you don't get that many errors, especially in one second :-). I was debugging an UMC hardware bug. >[0]2. There doesn't appear to be any documentation on what the kernel >[0] error message is trying to report. > >[1]See the sio man page. >Ok, how do I "fix the application?" (uucico) as the man page cryptically >suggests when the application runs fine on other ports running at 57600 >with faster DCE data rates (28.8 vs 24)? If we have the equivalent of >a TTYHOG or CLIST limits, where are they controlled? (I have already >looked at the LINT kernel.) The man page should say something like "problem in the application mix". An application can't be blamed for not getting enough cpu cycles if it has to compete with too many other applications. TTYHOG can only be controlled by redefining it and recompiling. The clist limits are mostly controlled by TTYHOG. >[0] Since there appears to be code in sio.c that would detect overruns >[0] in the hardware FIFO, report this and lower the trigger value >[0] automatically, either this code isn't working or this isn't the >[0] type of overrun the kernel is trying to report. Again, no >[0] documentation. > >[1]That code has almost always been disabled and doesn't exist in -current. >[1]It tended to drop the trigger level to 1 for transient errors. >Great. :-( It was one of the few parts of the driver that wasn't >goofy. The figure-out-what-type-of-UART-you-have is a bad idea and can >freak on many internal modems. "Reserved" and "0" for apparently-unused >bits mean different things to different silicon vendors. The UART detection hasn't caused any problems that I know of. Checking that the IRQ works is what causes problems. How do you want the UART type to be configured? Bruce From owner-freebsd-bugs Tue Feb 27 11:20:04 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA14423 for bugs-outgoing; Tue, 27 Feb 1996 11:20:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA14399 Tue, 27 Feb 1996 11:20:02 -0800 (PST) Resent-Date: Tue, 27 Feb 1996 11:20:02 -0800 (PST) Resent-Message-Id: <199602271920.LAA14399@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, hsu@clinet.fi Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA14058 for ; Tue, 27 Feb 1996 11:16:04 -0800 (PST) Received: from katiska.clinet.fi (root@katiska.clinet.fi [194.100.0.4]) by hauki.clinet.fi (8.7.3/8.6.4) with ESMTP id VAA26762 for ; Tue, 27 Feb 1996 21:15:18 +0200 (EET) Received: (root@localhost) by katiska.clinet.fi (8.7.3/8.6.4) id VAA18465; Tue, 27 Feb 1996 21:15:18 +0200 (EET) Message-Id: <199602271915.VAA18465@katiska.clinet.fi> Date: Tue, 27 Feb 1996 21:15:18 +0200 (EET) From: Heikki Suonsivu Reply-To: hsu@clinet.fi To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/1045: Lockup: b_to_q to a clist with no reserved cblocks Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 1045 >Category: kern >Synopsis: Lockup: b_to_q to a clist with no reserved cblocks >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Feb 27 11:20:01 PST 1996 >Last-Modified: >Originator: Heikki Suonsivu >Organization: Clinet, Espoo, Finland >Release: FreeBSD 2.2-CURRENT i386 >Environment: 486-100 used as a terminal server, -current. Never seen this on older sups, it seems to be new problem. Cyclades 32 port board. >Description: The machine stops responding to any requests and prints this message to console as fast as it can: b_to_q to a clist with no reserved cblocks >How-To-Repeat: I don't know, but I guess a large number of active serial ports could have something to do with this. >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue Feb 27 12:00:06 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA19198 for bugs-outgoing; Tue, 27 Feb 1996 12:00:06 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA19170 Tue, 27 Feb 1996 12:00:03 -0800 (PST) Resent-Date: Tue, 27 Feb 1996 12:00:03 -0800 (PST) Resent-Message-Id: <199602272000.MAA19170@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, hsu@clinet.fi Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA18992 for ; Tue, 27 Feb 1996 11:58:14 -0800 (PST) Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id LAA14223 for ; Tue, 27 Feb 1996 11:58:02 -0800 Received: from plentium.clinet.fi (root@plentium.clinet.fi [194.100.0.7]) by hauki.clinet.fi (8.7.3/8.6.4) with ESMTP id VAA28191 for ; Tue, 27 Feb 1996 21:52:34 +0200 (EET) Received: (hsu@localhost) by plentium.clinet.fi (8.7.3/8.6.4) id VAA11867; Tue, 27 Feb 1996 21:52:34 +0200 (EET) Message-Id: <199602271952.VAA11867@plentium.clinet.fi> Date: Tue, 27 Feb 1996 21:52:34 +0200 (EET) From: Heikki Suonsivu Reply-To: hsu@clinet.fi To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: misc/1046: X dies with sig11 Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 1046 >Category: misc >Synopsis: X dies with sig11 with -current >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Feb 27 12:00:02 PST 1996 >Last-Modified: >Originator: Heikki Suonsivu >Organization: Clinet, Espoo, Finland >Release: FreeBSD 2.2-CURRENT i386 >Environment: P90, S3Trio64. Runs an irc server and X, tkined and tkgnats. >Description: X server suddenly dies with Sig11. I never saw this before with previous kernels, now it has happened three or four times within four days (the kernel sources were supped at about that time). >How-To-Repeat: Run X, start a lot of windows, start doing something very important and do not save your editor buffers for a long time ;-) Once it happened when I tried to start netscape, other times I do not think I had anythign special going on, other than normal editing. >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue Feb 27 12:10:04 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA20354 for bugs-outgoing; Tue, 27 Feb 1996 12:10:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA20327 Tue, 27 Feb 1996 12:10:01 -0800 (PST) Resent-Date: Tue, 27 Feb 1996 12:10:01 -0800 (PST) Resent-Message-Id: <199602272010.MAA20327@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, hsu@clinet.fi Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA19356 for ; Tue, 27 Feb 1996 12:01:38 -0800 (PST) Received: from plentium.clinet.fi (root@plentium.clinet.fi [194.100.0.7]) by hauki.clinet.fi (8.7.3/8.6.4) with ESMTP id WAA28556 for ; Tue, 27 Feb 1996 22:01:27 +0200 (EET) Received: (hsu@localhost) by plentium.clinet.fi (8.7.3/8.6.4) id WAA12047; Tue, 27 Feb 1996 22:01:27 +0200 (EET) Message-Id: <199602272001.WAA12047@plentium.clinet.fi> Date: Tue, 27 Feb 1996 22:01:27 +0200 (EET) From: Heikki Suonsivu Reply-To: hsu@clinet.fi To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: gnu/1047: send-pr: Aborting... Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 1047 >Category: gnu >Synopsis: send-pr: Aborting... >Confidential: no >Severity: non-critical >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Feb 27 12:10:01 PST 1996 >Last-Modified: >Originator: Heikki Suonsivu >Organization: Clinet, Espoo, Finland >Release: FreeBSD 2.2-CURRENT i386 >Environment: -current from 4 days back >Description: send-pr sometimes after you have written your bug report and exit the editor, will say send-pr: Aborting... and deletes your bug report without sending it. Enormously irritating! This actually was happening often long time ago, but it went away for at least several months. Now its back, or is happening less often. It first ate my previous PR, then I rewrote it and it worked, and tried to PR this problem, and again send-pr ate the report (but learning from experience, I had written the buffer to a safe place before exiting the editor!). >How-To-Repeat: Author lots of bug reports. It may or may not help to use emacs to edit the pr's. >Fix: As a workaround I would suggest: < # Catch some signals. ($xs kludge needed by Sun /bin/sh) < xs=0 < trap 'rm -f $REF $TEMP; exit $xs' 0 < trap 'echo "$COMMAND: Aborting ..."; rm -f $REF $TEMP; xs=1; exit' 1 2 3 13 15 -- > # Catch some signals. ($xs kludge needed by Sun /bin/sh) > xs=0 > trap 'rm -f $REF $TEMP; exit $xs' 0 > trap 'echo "$COMMAND: Aborting ..."; echo $REF $TEMP 'left around, clean up manually'; xs=1; exit' 1 2 3 13 15 This does not fix the actual problem, why does it get a signal? A bug in sh? -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@clinet.fi mobile +358-40-5519679 work +358-0-4375360 fax -4555276 home -8031121 >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue Feb 27 12:43:37 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA01345 for bugs-outgoing; Tue, 27 Feb 1996 12:43:37 -0800 (PST) Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA01308 for ; Tue, 27 Feb 1996 12:43:07 -0800 (PST) Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by quackerjack.cc.vt.edu (8.7.1/8.7.1) with SMTP id PAA03731 for ; Tue, 27 Feb 1996 15:41:37 -0500 (EST) Received: from tquach.vt.edu (as2511-32.sl015.cns.vt.edu [128.173.36.244]) by sable.cc.vt.edu (8.6.12/8.6.12) with SMTP id PAA17495 for ; Tue, 27 Feb 1996 15:41:35 -0500 Message-Id: <2.2.32.19960227204132.0068a884@mail.vt.edu> X-Sender: tquach@mail.vt.edu X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 27 Feb 1996 15:41:32 -0500 To: bugs@freebsd.org From: Thanh Quach Subject: microsoft serial mouse in freebsd Sender: owner-bugs@freebsd.org Precedence: bulk I'm trying to install xwindows and having trouble configuring the mouse. I have a microsoft mouse that is connected to a serial port. Can you please tell me what kind of configuration I should use? Thank You. ****************************************************************** *Message From: Thanh Quach * *e-mail: tquach@vt.edu * * * * IIIII IIIIII II II IIIIII II II IIIIII IIIIII IIIIII * * II II II II II II II II II II II II * * II II II II IIIIII II II III II IIIIII IIIIII * * II II II II II II II II II II II II II * * IIIII IIIIII II II IIIIII II II IIIIII IIIIII IIIIII * * * ****************************************************************** From owner-freebsd-bugs Tue Feb 27 22:48:47 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA16044 for bugs-outgoing; Tue, 27 Feb 1996 22:48:47 -0800 (PST) Received: from fw.ast.com (fw.ast.com [165.164.6.25]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA16033 for ; Tue, 27 Feb 1996 22:48:45 -0800 (PST) Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #2) id m0treEN-00084fC; Tue, 27 Feb 96 23:15 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #20) id m0trdvl-000DI3C; Tue, 27 Feb 96 22:56 WET Message-Id: Date: Tue, 27 Feb 96 22:56 WET To: bugs@freebsd.org From: uhclem@nemesis.lonestar.org (Frank Durda IV) Sent: Tue Feb 27 1996, 22:56:01 CST Subject: gnu/1047: send-pr: Aborting... Sender: owner-bugs@freebsd.org Precedence: bulk [0]send-pr sometimes after you have written your bug report and exit the [0]editor, will say [0] [0]send-pr: Aborting... [0] [0]and deletes your bug report without sending it. Enormously irritating! I agree! You can cause this if you hit at any point while in VI writing the problem report. When you exit after carefully constructing the problem reports, send-pr immediately aborts and the tmp file is erased. It used to be the case that you could press or *prior* to vi completely exiting and cause it to abort, although this is much harder to do. I suggest the code be modified to at least keep the prepared bug file around somewhere like it does if you do select "A" for Abort. It certainly should disregard signals sent to children like . Frank Durda IV |"The Knights who say "LETNi" or uhclem%nemesis@rwsystr.nkn.net | demand... A SEGMENT REGISTER!!!" |"A what?" or ...letni!rwsys!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983 From owner-freebsd-bugs Wed Feb 28 06:30:05 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA11271 for bugs-outgoing; Wed, 28 Feb 1996 06:30:05 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA11238 Wed, 28 Feb 1996 06:30:02 -0800 (PST) Resent-Date: Wed, 28 Feb 1996 06:30:02 -0800 (PST) Resent-Message-Id: <199602281430.GAA11238@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, nik@blueberry.co.uk Received: from elbereth.blueberry.co.uk (surfs-up.demon.co.uk [158.152.128.94]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA11100 for ; Wed, 28 Feb 1996 06:27:51 -0800 (PST) Received: (from nik@localhost) by elbereth.blueberry.co.uk (8.6.12/8.6.12) id MAA00400; Wed, 28 Feb 1996 12:25:57 GMT Message-Id: <199602281225.MAA00400@elbereth.blueberry.co.uk> Date: Wed, 28 Feb 1996 12:25:57 GMT From: Nik Clayton Reply-To: nik@blueberry.co.uk To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: i386/1048: ep driver not detecting card with specific values Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 1048 >Category: i386 >Synopsis: ep driver fails to detect card when told specific values >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Feb 28 06:30:01 PST 1996 >Last-Modified: >Originator: Nik Clayton >Organization: Blueberry Design Ltd. >Release: FreeBSD 2.1-STABLE i386 >Environment: avail memory = 15044608 (14692K bytes) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x380-0x39f irq 15 maddr 0xd8000 msize 16384 on isa ed0: address 00:00:c0:dc:5b:ab, type SMC8216/SMC8216C (16 bit) lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x63 irq 12 on motherboard sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1: disabled, not probed. pca0 on motherboard pca0: PC speaker audio driver fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in 1 3C5x9 board(s) on ISA found at 0x300 ep0 at 0x300-0x30f irq 3 on isa ep0: aui/bnc/utp[*UTP*] address 00:20:af:5b:9a:03 irq 3 npx0 on motherboard npx0: INT 16 interface gus0 at 0x220 irq 11 drq 1 flags 0x3 on isa gus0: gus0: Probing for devices on the PCI bus: chip0 rev 2 on pci0:0 chip1 rev 2 on pci0:7 vga0 rev 0 int a irq 9 on pci0:10 ncr0 rev 2 int a irq 10 on pci0:12 ncr0 waiting for scsi devices to settle (ncr0:0:0): "FUJITSU M1606S-512 6234" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 1041MB (2131992 512 byte sectors) sd0(ncr0:0:0): with 3457 cyls, 6 heads, and an average 102 sectors/track (ncr0:1:0): "NEC CD-ROM DRIVE:502 2.0r" type 5 removable SCSI 2 cd0(ncr0:1:0): CD-ROM cd0(ncr0:1:0): FAST SCSI-2 125ns (8 Mb/sec) offset 8. cd present.[308654 x 2048 byte records] (ncr0:2:0): "MICROP 2210-09MQ1001901 HQ30" type 0 fixed SCSI 2 sd1(ncr0:2:0): Direct-Access sd1(ncr0:2:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 1007MB (2062820 512 byte sectors) sd1(ncr0:2:0): with 2372 cyls, 9 heads, and an average 96 sectors/track >Description: My machine has two network cards in. One SMC Elite 16C (using the ed driver) and one 3COM 3C509 (using the ep driver). The kernel config lines for these two devices are device ed0 at isa? port 0x380 net irq 15 iomem 0xd8000 vector edintr device ep0 at isa? port 0x300 net irq 3 vector epintr Those are the correct irq and port values for the cards, as set using their respective DOS setup programs. Where applicable, plug and play is turned off. With this configuration, at boot time ed0 is successfully recognised. ed0 at 0x380-0x39f irq 15 maddr 0xd8000 msize 16384 on isa ed0: address 00:00:c0:dc:5b:ab, type SMC8216/SMC8216C (16 bit) However, ep0 is not, ep0 not found at 0x300 If I boot with -c, and tell the ep driver to pick up the port address from the card, with port ep0 -1 then it is successfully found. At 0x300! 1 3C5x9 board(s) on ISA found at 0x300 ep0 at 0x300-0x30f irq 3 on isa ep0: aui/bnc/utp[*UTP*] address 00:20:af:5b:9a:03 irq 3 This is somewhat confusing. This problem persists if ep0 is the only network card in the machine. I have not been able to confirm whether this occurs when the card is on other port addresses, but it does happen on other IRQ settings. >How-To-Repeat: Boot a 3C509 network card at port 300 with that port referenced in the kernel configuration. >Fix: Tell the driver to pick up the base address from the card. It may also be possible to use '-1' in the kernel config file, although I have not tested this. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed Feb 28 08:40:08 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA20558 for bugs-outgoing; Wed, 28 Feb 1996 08:40:08 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA20527 Wed, 28 Feb 1996 08:40:04 -0800 (PST) Resent-Date: Wed, 28 Feb 1996 08:40:04 -0800 (PST) Resent-Message-Id: <199602281640.IAA20527@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, hsu@clinet.fi Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA20320 for ; Wed, 28 Feb 1996 08:37:01 -0800 (PST) Received: from katiska.clinet.fi (root@katiska.clinet.fi [194.100.0.4]) by hauki.clinet.fi (8.7.3/8.6.4) with ESMTP id SAA01155 for ; Wed, 28 Feb 1996 18:36:14 +0200 (EET) Received: (root@localhost) by katiska.clinet.fi (8.7.3/8.6.4) id SAA15192; Wed, 28 Feb 1996 18:36:14 +0200 (EET) Message-Id: <199602281636.SAA15192@katiska.clinet.fi> Date: Wed, 28 Feb 1996 18:36:14 +0200 (EET) From: Heikki Suonsivu Reply-To: hsu@clinet.fi To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/1049: /kernel: arpresolve: can't allocate llinfo for 194.100.0.30 Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 1049 >Category: kern >Synopsis: /kernel: arpresolve: can't allocate llinfo for 194.100.0.30 >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Feb 28 08:40:01 PST 1996 >Last-Modified: >Originator: Heikki Suonsivu >Organization: Clinet, Espoo, Finland >Release: FreeBSD 2.2-CURRENT i386 >Environment: A terminal server built on top of FreeBSD. I tried to install -current into it, and in addition to becoming more unstable it also looses entries in its arp tables. >Description: Feb 28 18:03:55 osku /kernel: arpresolve: can't allocate llinfo for 194.100.0.30 Feb 28 18:04:30 osku last message repeated 3 times If I try manually enter the hardware address of the 194.100.0.30, I get set: can only proxy for 194.100.0.30 The problem disappears when I shut down gated, but after starting gated again the arp entry for 194.100.0.30 disappears with 30 seconds. >How-To-Repeat: I don't know exact pattern which causes this. >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed Feb 28 09:42:29 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA25847 for bugs-outgoing; Wed, 28 Feb 1996 09:42:29 -0800 (PST) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA25842 for ; Wed, 28 Feb 1996 09:42:27 -0800 (PST) Received: by agora.rdrop.com (Smail3.1.29.1 #17) id m0trptJ-000AoBC; Wed, 28 Feb 96 09:42 PST Message-Id: From: batie@agora.rdrop.com (Alan Batie) Subject: vi core dump To: freebsd-bugs@freebsd.org Date: Wed, 28 Feb 1996 09:42:17 -0800 (PST) X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-bugs@freebsd.org Precedence: bulk The following sequence will cause vi to core dump: vi 0 5 * * * ~ba (yes, I forgot to go in to insert mode before pasting a crontab entry; this is the subset of the line that causes the core dump) -- Alan Batie ______ Freedom for me to be and do batie@agora.rdrop.com \ / only what *you* approve of +1 503 452-0960 \ / is no freedom at all. DE 3C 29 17 C0 49 7A 27 \/ 40 A5 3C 37 4A DA 52 B9 It is my policy to avoid purchase of any products from companies which use unrequested email advertisements or telephone solicitation. From owner-freebsd-bugs Wed Feb 28 10:44:18 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA00826 for bugs-outgoing; Wed, 28 Feb 1996 10:44:18 -0800 (PST) Received: (from fenner@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA00807 Wed, 28 Feb 1996 10:44:16 -0800 (PST) Date: Wed, 28 Feb 1996 10:44:16 -0800 (PST) From: Bill Fenner Message-Id: <199602281844.KAA00807@freefall.freebsd.org> To: fenner, freebsd-bugs, fenner Subject: Re: kern/1049 Sender: owner-bugs@FreeBSD.ORG Precedence: bulk Synopsis: /kernel: arpresolve: can't allocate llinfo for 194.100.0.30 Responsible-Changed-From-To: freebsd-bugs->fenner Responsible-Changed-By: fenner Responsible-Changed-When: Wed Feb 28 10:43:30 PST 1996 Responsible-Changed-Why: fenner has been mucking with arp/routing stuff From owner-freebsd-bugs Wed Feb 28 11:56:28 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA06813 for bugs-outgoing; Wed, 28 Feb 1996 11:56:28 -0800 (PST) Received: from narq.avian.org ([199.103.168.126]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA06808 for ; Wed, 28 Feb 1996 11:56:21 -0800 (PST) Received: (from hobbit@localhost) by narq.avian.org (8.6.12/_H*) id OAA14421; Wed, 28 Feb 1996 14:56:41 -0500 Date: Wed, 28 Feb 1996 14:56:41 -0500 From: *Hobbit* Message-Id: <199602281956.OAA14421@narq.avian.org> To: eichin@cygnus.com, freebsd-bugs@freefall.freebsd.org, problems@bsdi.com Subject: Kerberos 4 rsh/rcp fixes Cc: sra@epilogue.com Sender: owner-bugs@FreeBSD.ORG Precedence: bulk As long as maintainers are in there fixing the Kerberos 4 random_key stuff, it seems appropriate that other release tree fixes could be made at the same time before new "official" releases go out. I've [finally!] completed some work on the encrypting modes of "rsh" and "rcp", and have released the patches for review. These apply to Cygnus CNS, and the built-in applications that come with BSDI 2.0 and FreeBSD 2.x. Please anonymous-FTP to ftp.epilogue.com, and do cd /pub/hobbit/crypto/f9601 get krbfix-out.tar This single tar file contains a detailed description of the problems/fixes, and patch kits for various releases. Sorry for the sort of scatter-shot mailing; please forward to the right places if I blew it.. _H* From owner-freebsd-bugs Wed Feb 28 12:10:05 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA07847 for bugs-outgoing; Wed, 28 Feb 1996 12:10:05 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA07825 Wed, 28 Feb 1996 12:10:03 -0800 (PST) Resent-Date: Wed, 28 Feb 1996 12:10:03 -0800 (PST) Resent-Message-Id: <199602282010.MAA07825@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, mi@ALDAN.algebra.com Received: from aldan (PPP-86-9.BU.EDU [128.197.8.189]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA07174 for ; Wed, 28 Feb 1996 12:02:03 -0800 (PST) Received: (from root@localhost) by aldan (8.6.12/8.6.12) id PAA00354; Wed, 28 Feb 1996 15:02:43 -0500 Message-Id: <199602282002.PAA00354@aldan> Date: Wed, 28 Feb 1996 15:02:43 -0500 From: mi@ALDAN.algebra.com Reply-To: mi@ALDAN.algebra.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/1050: Process (zip) hangs (unkillable) after floppy error Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 1050 >Category: bin >Synopsis: Process (zip) hangs (unkillable) after floppy error >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Feb 28 12:10:01 PST 1996 >Last-Modified: >Originator: Mikhail Teterin >Organization: >Release: FreeBSD 2.1-STABLE i386 >Environment: 3" Floppy drive is attached to Adaptec-1542. >Description: Floppy disk is mounted (-t msdos) zip starts creating an archive on it. At some point a bunch of fsbn errors (possibly a hardware fault) appear (hard error writing, cmd 4 failed, etc.) After this, zip waits forever: 0 222 150 0 -6 0 512 564 getblk D+ v2 0:00.06 zip -9 -r /diska/tcl75b2.zip tcl7.5b2 Note. Tar hangs in the same manner on tape-drive failure. It can not be killed -- even shutdown does not kill it (hangs in system call?) >How-To-Repeat: See description >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed Feb 28 13:18:52 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA13490 for bugs-outgoing; Wed, 28 Feb 1996 13:18:52 -0800 (PST) Received: from bacata.usc.unal.edu.co ([200.21.26.80]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA13465 for ; Wed, 28 Feb 1996 13:18:12 -0800 (PST) Received: by bacata.usc.unal.edu.co (AIX 4.1/UCB 5.64/4.03) id AA32950; Wed, 28 Feb 1996 16:14:16 -0600 Date: Wed, 28 Feb 1996 16:14:16 -0600 (CST) From: Pedro Giffuni To: freebsd-bugs@freebsd.org Subject: Installation bugs ! Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-bugs@freebsd.org Precedence: bulk Hi, I noticed one bug: The installation doesnt properly define Colombia`s hour! It also looks for Botoga or something, I guess it was meant to be Bogota (the capital). A feature that doesn`t work either is adding packages through nfs, it reads the list of packages but doesn`t access it. The terminal also have some strange overlappings, otherwise the system is pretty cool ! thanx, Pedro. From owner-freebsd-bugs Wed Feb 28 13:33:41 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA14880 for bugs-outgoing; Wed, 28 Feb 1996 13:33:41 -0800 (PST) Received: from iaehv.IAEhv.nl (root@iaehv.IAEhv.nl [192.87.208.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA14874 for ; Wed, 28 Feb 1996 13:33:38 -0800 (PST) Received: by iaehv.IAEhv.nl (8.6.13/1.63) id WAA03839; Wed, 28 Feb 1996 22:33:32 +0100 Date: Wed, 28 Feb 1996 22:33:32 +0100 From: wjw@IAEhv.nl (Willem Jan Withagen) Message-Id: <199602282133.WAA03839@iaehv.IAEhv.nl> X-Disclaimer: iaehv.nl is a public access UNIX system and cannot be held responsible for the opinions of its individual users. To: bugs@freebsd.org Subject: Re: slattach problems Newsgroups: list.freebsd.questions In-Reply-To: <199602212107.WAA06944@digi.digiware.nl> Organization: Internet Access Eindhoven, the Netherlands Sender: owner-bugs@freebsd.org Precedence: bulk I tried the question below on questions@freebsd.org without much effect. Perhaps someone on the bugs list can give me a pointer? Thanx, WjW In article <199602212107.WAA06944@digi.digiware.nl> you write: >Hi, > >I'm running 2.1.0 on a 486/100 with all RELEASE stuff. > >My Internet connection is a leased line with 2 Zyxels, and this has >funtioned flawless under 2.0.5. > >But under 2.1.0 there occurs a problem once the leased line has gone down >and comes up again: > - slattach informes about the missing carrier > - and in due time the status the routing entry for the link is > adjusted > - then the lines comes up, but slattach only tells the system that the > carrier has returned. > The IP routing entry is not updated. > NOTE: This is a fixed connection, so I have a permanent SLIP > without login at the portmaster at the other side. It > just always speaks SLIP to me. > - If I kill the current slattach, and start a fresh one, then the > routing entry IS updated. > >Now what can the problems be, and how do I detect them? > >Thanx, > Willem Jan Withagen From owner-freebsd-bugs Wed Feb 28 14:24:04 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA20717 for bugs-outgoing; Wed, 28 Feb 1996 14:24:04 -0800 (PST) Received: from scuba.cygnus.com ([192.80.44.19]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA20615 for ; Wed, 28 Feb 1996 14:24:00 -0800 (PST) Message-Id: <199602282224.OAA20615@freefall.freebsd.org> Received: by scuba.cygnus.com (1.39.111.2/16.2) id AA034836170; Wed, 28 Feb 1996 17:22:50 -0500 Date: Wed, 28 Feb 1996 17:22:50 -0500 To: hobbit@avian.org Cc: freebsd-bugs@freefall.freebsd.org, problems@bsdi.com In-Reply-To: <199602281956.OAA14421@narq.avian.org> (message from *Hobbit* on Wed, 28 Feb 1996 14:56:41 -0500) Subject: Re: Kerberos 4 rsh/rcp fixes From: eichin@cygnus.com Mime-Version: 1.0 Sender: owner-bugs@FreeBSD.ORG Precedence: bulk > it seems appropriate that other release tree fixes could be made at the same > time before new "official" releases go out. You're about a week and a half late for that... we prefer our customers learn about problems from us *before* the read about them in the Wall Street Journal :-) >README >is a later release of October 1995 or so. Despite my signed affidavit of U.S. >citizenship existing in their records as they require, repeated efforts to >obtain the updated release from Cygnus have failed. I don't (and never have) deal with the faxed signatures directly, but this is still odd, since many people have succeeded in getting new releases. We *have* recently changed policy to permit people to send us a copy of the original email we sent listing the hidden path to some previous release in order to get the newest one, which should make it easier if you have the old mail. >indications as to what the latter port should *be*. While initially trying to >get things working, Rob Austein off the cuff assigned it to TCP 2106, or one I thought there was some convention about not using even-numbered ports, though I can't recall what the logic was; it may only apply to low-numbered ports, and may be a BSD convention anyhow. >Which brings us to the major "rcp" problem. Cygnus decided to invent their own >protocol for "rcp" rather than fix encrypted "rsh" and make "rcp" able to talk You're confused. Cygnus simply made our code implement *exactly* what the MIT code did. Really, it would have been ludicrous to invent an rcp encryption system that *only* differed from rlogin by the padding order... it's just that they were written by different undergrads who didn't communicate :-) It wasn't until we tried to unify the code through the kstream library that we found that problem... >> CNS release is still portable across more >> operating systems than the KrbIV/BSD code, but the way they get there is messy >> and clearly ill-maintained. You don't defend that at all, though most of the rest of your analysis is fairly solid... there is a reason we're using autoconf for krb5, of course :-) However: >> I also had to deal with their rather cavalier way >> of inventing standards. is patently untrue. We've always maintained the the MIT release was standard, and preserved compatibility with it, at some cost... see the rcp complexity above, or the fact that rsh still uses a stderr back channel, or the *really* gross error-checking hack for encrypted rlogin, which causes you to actually see server side errors (instead of "rcmd failed") *without* changing the protocol. Again, much of your analysis about the existing V4 code base is quite accurate; the exceptions, however, are glaring... _Mark_ Cygnus Support Cygnus Network Security http://www.cygnus.com/data/cns/ From owner-freebsd-bugs Wed Feb 28 15:56:37 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA28111 for bugs-outgoing; Wed, 28 Feb 1996 15:56:37 -0800 (PST) Received: from overlord.dmv.com (root@overlord.dmv.com [206.30.64.6]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA28106 for ; Wed, 28 Feb 1996 15:56:34 -0800 (PST) Received: from overlord.dmv.com by overlord.dmv.com via SMTP (950215.SGI.8.6.10/940406.SGI.AUTO) for id SAA12168; Wed, 28 Feb 1996 18:56:23 -0500 Date: Wed, 28 Feb 1996 18:56:23 -0500 (EDT) From: Patrick Ferguson To: bugs@freebsd.org Subject: ProAudio 16 SCSI parity errors In-Reply-To: <199602282133.WAA03839@iaehv.IAEhv.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-bugs@freebsd.org Precedence: bulk How do I turn off parity checking in the nca driver? I looked through the source file and saw that it the flags are defined, but I still get parity errors from the CD. Thanks. ------------------------------------------------------------------------------ Patrick Ferguson - Systems Administrator patrick@dmv.com DelMarVa OnLine! - Salisbury, MD From owner-freebsd-bugs Wed Feb 28 17:49:12 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA06347 for bugs-outgoing; Wed, 28 Feb 1996 17:49:12 -0800 (PST) Received: (from asami@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA06334 Wed, 28 Feb 1996 17:49:09 -0800 (PST) Date: Wed, 28 Feb 1996 17:49:09 -0800 (PST) From: Satoshi Asami Message-Id: <199602290149.RAA06334@freefall.freebsd.org> To: obrien@cs.ucdavis.edu, asami, freebsd-bugs Subject: Re: ports/1041 Sender: owner-bugs@FreeBSD.ORG Precedence: bulk Synopsis: ports submissions State-Changed-From-To: open-feedback State-Changed-By: asami State-Changed-When: Wed Feb 28 17:48:23 PST 1996 State-Changed-Why: Some problems encountered, sent message to submitter. From owner-freebsd-bugs Wed Feb 28 17:50:02 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA06415 for bugs-outgoing; Wed, 28 Feb 1996 17:50:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA06397 Wed, 28 Feb 1996 17:50:01 -0800 (PST) Date: Wed, 28 Feb 1996 17:50:01 -0800 (PST) Message-Id: <199602290150.RAA06397@freefall.freebsd.org> To: freebsd-bugs Cc: From: asami@cs.berkeley.edu (Satoshi Asami) Subject: Re: ports/1041: ports submissions Reply-To: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-bugs@FreeBSD.ORG Precedence: bulk The following reply was made to PR ports/1041; it has been noted by GNATS. From: asami@cs.berkeley.edu (Satoshi Asami) To: FreeBSD-gnats-submit@freefall.freebsd.org, obrien@cs.ucdavis.edu Cc: Subject: Re: ports/1041: ports submissions Date: Wed, 28 Feb 1996 17:51:43 -0800 * I would like to submit: * xcpustate-portball.tgz * minicom-portball-1.74.README * minicom-portball-1.74.tgz * minicom-1.74.tar.gz By the way, no need to upload the source tarball, we always get it from the master site. * For inclusion in the FreeBSD ports-current collection. * They are in ftp.cdrom.com:/pub/FreeBSD/incoming. Thanks, xcpustate worked fine, I'm going to commit it soon. Please take a look at what changed. I didn't have much luck with minicom. The tarball I got from sunsite had a checksum mismatch. I forced it to use it and the patch failed in patchlevel.h. Further investigating showed that your patch seems to expect version 1.73 of the source. Maybe something is amiss here. I already made some changes, and put the modified version as minicom-updated.tar.gz, so please start from there (I haven't changed any patches). Satoshi P.S. One more thing -- it will be nice if you put only one port in one message, so I can "close" the PR independently.... From owner-freebsd-bugs Wed Feb 28 19:44:30 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA17889 for bugs-outgoing; Wed, 28 Feb 1996 19:44:30 -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.3/8.7.3) with ESMTP id TAA17884 for ; Wed, 28 Feb 1996 19:44:26 -0800 (PST) Received: from caramba.cs.tu-berlin.de (wosch@caramba.cs.tu-berlin.de [130.149.17.12]) by mail.cs.tu-berlin.de (8.6.12/8.6.12) with ESMTP id EAA02468; Thu, 29 Feb 1996 04:39:06 +0100 Received: (from wosch@localhost) by campa.panke.de (8.6.9/8.6.9) id EAA01570; Thu, 29 Feb 1996 04:35:14 +0100 Date: Thu, 29 Feb 1996 04:35:14 +0100 From: Wolfram Schneider Message-Id: <199602290335.EAA01570@campa.panke.de> To: batie@agora.rdrop.com (Alan Batie) CC: bugs@freebsd.org In-reply-to: batie@agora.rdrop.com's message of Wed, 28 Feb 1996 09:42:17 -0800 (PST) Subject: Re: vi core dump Reply-to: Wolfram Schneider MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit References: Sender: owner-bugs@freebsd.org Precedence: bulk In article batie@agora.rdrop.com (Alan Batie) writes: >The following sequence will cause vi to core dump: > > vi > 0 5 * * * ~ba or '~a', '~i' Fix: --- 1.1 1996/02/29 03:10:46 +++ vi/v_ulcase.c 1996/02/29 03:27:57 @@ -84,6 +84,7 @@ u_long cnt; char *p; + len = 0; lno = vp->m_start.lno; cno = vp->m_start.cno; Wolfram (happy Emacs user) From owner-freebsd-bugs Thu Feb 29 12:50:04 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA06827 for bugs-outgoing; Thu, 29 Feb 1996 12:50:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA06815 Thu, 29 Feb 1996 12:50:02 -0800 (PST) Resent-Date: Thu, 29 Feb 1996 12:50:02 -0800 (PST) Resent-Message-Id: <199602292050.MAA06815@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, mi@ALDAN.algebra.com Received: from aldan ([128.197.8.141]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA06737 for ; Thu, 29 Feb 1996 12:49:43 -0800 (PST) Received: (from root@localhost) by aldan (8.6.12/8.6.12) id PAA01365; Thu, 29 Feb 1996 15:50:33 -0500 Message-Id: <199602292050.PAA01365@aldan> Date: Thu, 29 Feb 1996 15:50:33 -0500 From: mi@ALDAN.algebra.com Reply-To: mi@ALDAN.algebra.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: ports/1051: zip fails on dos partition Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 1051 >Category: ports >Synopsis: zip fails on dos partition >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Feb 29 12:50:01 PST 1996 >Last-Modified: >Originator: Mikhail Teterin >Organization: >Release: FreeBSD 2.1-STABLE i386 >Environment: Floppy disk with FAT-filesystem is mounted on /diska zip's version -- 201 >Description: zip /diska/filename.zip ... files ... Creates the temporary zip file, but after compression fails moving/renaming it to filename.zip >How-To-Repeat: zip -9 -r /diska/zip.zip zip201 >Fix: Manually move the "residual" file (named like _z*) on the floppy to the filename.zip. Or, specify another location for temporary file with -b option to zip. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu Feb 29 14:45:25 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.FreeBSD.org (8.7.3/8.7.3) id OAA15712 for bugs-outgoing; Thu, 29 Feb 1996 14:45:25 -0800 (PST) Received: (from gnats@localhost) by freefall.FreeBSD.org (8.7.3/8.7.3) id OAA15559 Thu, 29 Feb 1996 14:42:44 -0800 (PST) Resent-Date: Thu, 29 Feb 1996 14:42:44 -0800 (PST) Resent-Message-Id: <199602292242.OAA15559@freefall.FreeBSD.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, tege@noisy.matematik.su.se Received: from noisy.matematik.su.se ([130.237.198.146]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA14876 for ; Thu, 29 Feb 1996 14:30:03 -0800 (PST) Received: (from tege@localhost) by noisy.matematik.su.se (8.6.12/8.6.12) id XAA05612; Thu, 29 Feb 1996 23:27:57 +0100 Message-Id: <199602292227.XAA05612@noisy.matematik.su.se> Date: Thu, 29 Feb 1996 23:27:57 +0100 From: tege@matematik.su.se Reply-To: tege@noisy.matematik.su.se To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/1052: /bin/sh problem with new GCC (snapshot for 2.8) Sender: owner-bugs@FreeBSD.ORG Precedence: bulk >Number: 1052 >Category: bin >Synopsis: /bin/sh problem with new GCC (snapshot for 2.8) >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Feb 29 14:40:03 PST 1996 >Last-Modified: >Originator: Torbjorn Granlund >Organization: TMG Datakonsult >Release: FreeBSD 2.1-STABLE i386 >Environment: Hardly relevant. >Description: The /bin/sh of FreeBSD doesn't work as on other systems, or like bash. The problem seems to be with the builtin `eval'. >How-To-Repeat: bash$ foo=tomte; var=foo; echo `eval echo \\$$var` tomte sh$ foo=tomte; var=foo; echo `eval echo \\$$var` 5578var >Fix: I don't know of any fix that is compatible with a non-flawed sh. A fix would be desirable if you want your users that install GCC 2.8 to avoid problems. Just imagine the flood of bug reports that you will get... If you provide me with a (reasonable) fix, I will put it in to the gcc repository in time for 2.8. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu Feb 29 15:30:10 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA19220 for bugs-outgoing; Thu, 29 Feb 1996 15:30:10 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA19210 Thu, 29 Feb 1996 15:30:05 -0800 (PST) Resent-Date: Thu, 29 Feb 1996 15:30:05 -0800 (PST) Resent-Message-Id: <199602292330.PAA19210@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, tege@noisy.matematik.su.se Received: from noisy.matematik.su.se ([130.237.198.146]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA14876 for ; Thu, 29 Feb 1996 14:30:03 -0800 (PST) Received: (from tege@localhost) by noisy.matematik.su.se (8.6.12/8.6.12) id XAA05612; Thu, 29 Feb 1996 23:27:57 +0100 Message-Id: <199602292227.XAA05612@noisy.matematik.su.se> Date: Thu, 29 Feb 1996 23:27:57 +0100 From: tege@matematik.su.se Reply-To: tege@noisy.matematik.su.se To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/1053: /bin/sh problem with new GCC (snapshot for 2.8) Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 1053 >Category: bin >Synopsis: /bin/sh problem with new GCC (snapshot for 2.8) >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Feb 29 15:30:02 PST 1996 >Last-Modified: >Originator: Torbjorn Granlund >Organization: TMG Datakonsult >Release: FreeBSD 2.1-STABLE i386 >Environment: Hardly relevant. >Description: The /bin/sh of FreeBSD doesn't work as on other systems, or like bash. The problem seems to be with the builtin `eval'. >How-To-Repeat: bash$ foo=tomte; var=foo; echo `eval echo \\$$var` tomte sh$ foo=tomte; var=foo; echo `eval echo \\$$var` 5578var >Fix: I don't know of any fix that is compatible with a non-flawed sh. A fix would be desirable if you want your users that install GCC 2.8 to avoid problems. Just imagine the flood of bug reports that you will get... If you provide me with a (reasonable) fix, I will put it in to the gcc repository in time for 2.8. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu Feb 29 16:10:05 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA22603 for bugs-outgoing; Thu, 29 Feb 1996 16:10:05 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA22597 Thu, 29 Feb 1996 16:10:02 -0800 (PST) Resent-Date: Thu, 29 Feb 1996 16:10:02 -0800 (PST) Resent-Message-Id: <199603010010.QAA22597@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, tege@noisy.matematik.su.se Received: from noisy.matematik.su.se ([130.237.198.146]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA14876 for ; Thu, 29 Feb 1996 14:30:03 -0800 (PST) Received: (from tege@localhost) by noisy.matematik.su.se (8.6.12/8.6.12) id XAA05612; Thu, 29 Feb 1996 23:27:57 +0100 Message-Id: <199602292227.XAA05612@noisy.matematik.su.se> Date: Thu, 29 Feb 1996 23:27:57 +0100 From: tege@matematik.su.se Reply-To: tege@noisy.matematik.su.se To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/1054: /bin/sh problem with new GCC (snapshot for 2.8) Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 1054 >Category: bin >Synopsis: /bin/sh problem with new GCC (snapshot for 2.8) >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Feb 29 16:10:01 PST 1996 >Last-Modified: >Originator: Torbjorn Granlund >Organization: TMG Datakonsult >Release: FreeBSD 2.1-STABLE i386 >Environment: Hardly relevant. >Description: The /bin/sh of FreeBSD doesn't work as on other systems, or like bash. The problem seems to be with the builtin `eval'. >How-To-Repeat: bash$ foo=tomte; var=foo; echo `eval echo \\$$var` tomte sh$ foo=tomte; var=foo; echo `eval echo \\$$var` 5578var >Fix: I don't know of any fix that is compatible with a non-flawed sh. A fix would be desirable if you want your users that install GCC 2.8 to avoid problems. Just imagine the flood of bug reports that you will get... If you provide me with a (reasonable) fix, I will put it in to the gcc repository in time for 2.8. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu Feb 29 22:50:03 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA20996 for bugs-outgoing; Thu, 29 Feb 1996 22:50:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA20974 Thu, 29 Feb 1996 22:50:01 -0800 (PST) Date: Thu, 29 Feb 1996 22:50:01 -0800 (PST) Message-Id: <199603010650.WAA20974@freefall.freebsd.org> To: freebsd-bugs Cc: From: Mark Murray Subject: Re: bin/1053: /bin/sh problem with new GCC (snapshot for 2.8) Reply-To: Mark Murray Sender: owner-bugs@FreeBSD.ORG Precedence: bulk The following reply was made to PR bin/1053; it has been noted by GNATS. From: Mark Murray To: tege@noisy.matematik.su.se Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: bin/1053: /bin/sh problem with new GCC (snapshot for 2.8) Date: Fri, 01 Mar 1996 08:42:08 +0200 > >Description: > > The /bin/sh of FreeBSD doesn't work as on other systems, or like bash. > The problem seems to be with the builtin `eval'. > > >How-To-Repeat: > > bash$ foo=tomte; var=foo; echo `eval echo \\$$var` > tomte > sh$ foo=tomte; var=foo; echo `eval echo \\$$var` > 5578var This is a duplicate (different technique) of my bin/1030. M From owner-freebsd-bugs Fri Mar 1 00:59:06 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA26902 for bugs-outgoing; Fri, 1 Mar 1996 00:59:06 -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.3/8.7.3) with ESMTP id AAA26822 for ; Fri, 1 Mar 1996 00:56:44 -0800 (PST) Received: from ole.cs.tu-berlin.de (wosch@ole.cs.tu-berlin.de [130.149.22.3]) by mail.cs.tu-berlin.de (8.6.12/8.6.12) with ESMTP id JAA28376; Fri, 1 Mar 1996 09:55:23 +0100 From: Wolfram Schneider Received: (wosch@localhost) by ole.cs.tu-berlin.de (8.6.12/8.6.6) id JAA25172; Fri, 1 Mar 1996 09:55:22 +0100 Date: Fri, 1 Mar 1996 09:55:22 +0100 Message-Id: <199603010855.JAA25172@ole.cs.tu-berlin.de> To: batie@agora.rdrop.com (Alan Batie), bugs@FreeBSD.ORG Subject: Re: vi core dump In-Reply-To: <199602290335.EAA01570@campa.panke.de> References: <199602290335.EAA01570@campa.panke.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Conversion: prohibited Sender: owner-bugs@FreeBSD.ORG Precedence: bulk Wolfram Schneider writes: >In article batie@agora.rdrop.com (Alan Batie) writes: > >>The following sequence will cause vi to core dump: >> >> vi >> 0 5 * * * ~ba > >or '~a', '~i' > >Fix: Argh! You need also fix the line number. --- vi/v_ulcase.c 1996/03/01 09:33:31 1.1 +++ vi/v_ulcase.c 1996/03/01 09:39:21 @@ -84,6 +84,7 @@ u_long cnt; char *p; + len = 0; lno = vp->m_start.lno; cno = vp->m_start.cno; @@ -120,7 +121,10 @@ /* Check to see if we tried to move past EOF. */ if (file_gline(sp, ep, vp->m_final.lno, &len) == NULL) { - (void)file_gline(sp, ep, --vp->m_final.lno, &len); + /* line number start with 1, lno zero is illegal */ + if (vp->m_final.lno > 1) + --vp->m_final.lno; + (void)file_gline(sp, ep, vp->m_final.lno, &len); vp->m_final.cno = len == 0 ? 0 : len - 1; } return (0); From owner-freebsd-bugs Fri Mar 1 02:40:04 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA03217 for bugs-outgoing; Fri, 1 Mar 1996 02:40:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA03191 Fri, 1 Mar 1996 02:40:02 -0800 (PST) Date: Fri, 1 Mar 1996 02:40:02 -0800 (PST) Message-Id: <199603011040.CAA03191@freefall.freebsd.org> To: freebsd-bugs Cc: From: Bruce Evans Subject: Re: bin/1052: /bin/sh problem with new GCC (snapshot for 2.8) Reply-To: Bruce Evans Sender: owner-bugs@FreeBSD.ORG Precedence: bulk The following reply was made to PR bin/1052; it has been noted by GNATS. From: Bruce Evans To: FreeBSD-gnats-submit@FreeBSD.ORG, tege@matematik.su.se Cc: Subject: Re: bin/1052: /bin/sh problem with new GCC (snapshot for 2.8) Date: Fri, 1 Mar 1996 21:29:09 +1100 >The /bin/sh of FreeBSD doesn't work as on other systems, or like bash. >The problem seems to be with the builtin `eval'. >>How-To-Repeat: >bash$ foo=tomte; var=foo; echo `eval echo \\$$var` >tomte >sh$ foo=tomte; var=foo; echo `eval echo \\$$var` >5578var This is fixed in the following versions of ash: the one in FreeBSD-1.1.5 the original one + assorted fixes from various places the one in BSD-4.4lite2 Bruce From owner-freebsd-bugs Fri Mar 1 02:50:57 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA03790 for bugs-outgoing; Fri, 1 Mar 1996 02:50:57 -0800 (PST) Received: from Sysiphos (Sysiphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA03760 for ; Fri, 1 Mar 1996 02:50:11 -0800 (PST) Received: by Sysiphos id AA19051 (5.67b/IDA-1.5 for bugs@freebsd.org); Fri, 1 Mar 1996 11:46:07 +0100 Message-Id: <199603011046.AA19051@Sysiphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Fri, 1 Mar 1996 11:46:06 +0100 In-Reply-To: tege@matematik.su.se "bin/1052: /bin/sh problem with new GCC (snapshot for 2.8)" (Feb 29, 23:27) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: tege@noisy.matematik.su.se Subject: Re: bin/1052: /bin/sh problem with new GCC (snapshot for 2.8) Cc: bugs@freebsd.org Sender: owner-bugs@freebsd.org Precedence: bulk On Feb 29, 23:27, tege@matematik.su.se wrote: } Subject: bin/1052: /bin/sh problem with new GCC (snapshot for 2.8) } } >Number: 1052 } >Category: bin } >Synopsis: /bin/sh problem with new GCC (snapshot for 2.8) } >Confidential: no } >Severity: serious } >Priority: low } >Responsible: freebsd-bugs } >State: open } >Class: sw-bug } >Submitter-Id: current-users } >Arrival-Date: Thu Feb 29 14:40:03 PST 1996 } >Last-Modified: } >Originator: Torbjorn Granlund } >Organization: } TMG Datakonsult } >Release: FreeBSD 2.1-STABLE i386 } >Environment: } Hardly relevant. } } >Description: } } The /bin/sh of FreeBSD doesn't work as on other systems, or like bash. } The problem seems to be with the builtin `eval'. } } >How-To-Repeat: } } bash$ foo=tomte; var=foo; echo `eval echo \\$$var` } tomte } sh$ foo=tomte; var=foo; echo `eval echo \\$$var` } 5578var } } >Fix: } } I don't know of any fix that is compatible with a non-flawed sh. A fix } would be desirable if you want your users that install GCC 2.8 to avoid } problems. Just imagine the flood of bug reports that you will get... } } If you provide me with a (reasonable) fix, I will put it in to the gcc } repository in time for 2.8. How about: sh$ foo=tomte; var=foo; echo `eval echo \$"$var"` (Tested under BASH, too ...) Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se From owner-freebsd-bugs Fri Mar 1 09:01:28 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA24652 for bugs-outgoing; Fri, 1 Mar 1996 09:01:28 -0800 (PST) Received: from omega.physik.fu-berlin.de (omega.physik.fu-berlin.de [130.133.3.51]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA24616 for ; Fri, 1 Mar 1996 09:01:18 -0800 (PST) Received: from prospero.physik.fu-berlin.de (graichen.dialup.fu-berlin.de [160.45.217.183]) by omega.physik.fu-berlin.de (8.7.1/8.7.1) with ESMTP id SAA30993 for ; Fri, 1 Mar 1996 18:01:11 +0100 (MET) Received: (from news@localhost) by prospero (8.6.12/8.6.12) id IAA04629; Fri, 1 Mar 1996 08:31:24 +0100 To: bugs@FreeBSD.org Path: graichen From: graichen@omega.physik.fu-berlin.de (Thomas Graichen) Newsgroups: local.freebsd-bugs Subject: Re: bin/1052: /bin/sh problem with new GCC (snapshot for 2.8) Date: 1 Mar 1996 07:31:23 GMT Organization: his FreeBSD box :-) Lines: 26 Distribution: local Message-ID: <4h694b$4eq@prospero.physik.fu-berlin.de> References: <199602292227.XAA05612@noisy.matematik.su.se> NNTP-Posting-Host: localhost.physik.fu-berlin.de X-Newsreader: TIN [version 1.2 PL2] Sender: owner-bugs@FreeBSD.org Precedence: bulk tege@matematik.su.se wrote: : >Synopsis: /bin/sh problem with new GCC (snapshot for 2.8) ... : >Release: FreeBSD 2.1-STABLE i386 maybe it's solved in -current ? : >Description: : The /bin/sh of FreeBSD doesn't work as on other systems, or like bash. : The problem seems to be with the builtin `eval'. : >How-To-Repeat: : bash$ foo=tomte; var=foo; echo `eval echo \\$$var` : tomte : sh$ foo=tomte; var=foo; echo `eval echo \\$$var` : 5578var looks like it's interpreting the $$ as the pid of the process and thus ignoring the \\ 's t -- thomas graichen graichen@mail.physik.fu-berlin.de graichen@FreeBSD.org perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away antoine de saint-exupery From owner-freebsd-bugs Fri Mar 1 12:17:35 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA06230 for bugs-outgoing; Fri, 1 Mar 1996 12:17:35 -0800 (PST) Received: (from fenner@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA06211 Fri, 1 Mar 1996 12:17:33 -0800 (PST) Date: Fri, 1 Mar 1996 12:17:33 -0800 (PST) From: Bill Fenner Message-Id: <199603012017.MAA06211@freefall.freebsd.org> To: mi@ALDAN.algebra.com, fenner, freebsd-bugs Subject: Re: bin/1038 Sender: owner-bugs@FreeBSD.ORG Precedence: bulk Synopsis: telnet gives ANSI80X30; rlogin gives (correct) cons30 State-Changed-From-To: open-closed State-Changed-By: fenner State-Changed-When: Fri Mar 1 12:08:06 PST 1996 State-Changed-Why: The option negotiation SENT WILL TERMINAL TYPE RCVD DO TERMINAL TYPE RCVD IAC SB TERMINAL-TYPE SEND SENT IAC SB TERMINAL-TYPE IS "CONS25" RCVD IAC SB TERMINAL-TYPE SEND SENT IAC SB TERMINAL-TYPE IS "ANSIS" RCVD IAC SB TERMINAL-TYPE SEND SENT IAC SB TERMINAL-TYPE IS "ANSI80X25" RCVD IAC SB TERMINAL-TYPE SEND SENT IAC SB TERMINAL-TYPE IS "ANSI80X25" is correct RFC-1091 behavior on the part of the telnet client. The telnet server is apparently either not RFC-1091 compliant or chooses not to pick the first-reported terminal type. The easiest way to work around this is to remove all aliases in your /usr/share/misc/termcap file; change it from cons25|ansis|ansi80x25:\ to cons25:\ and if you still want to have the ansis and ansi80x25 aliases, add entries like ansis:tc=cons25: ansi80x25:tc=cons25: From owner-freebsd-bugs Sat Mar 2 04:30:15 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA10271 for bugs-outgoing; Sat, 2 Mar 1996 04:30:15 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA10258 for freebsd-bugs; Sat, 2 Mar 1996 04:30:13 -0800 (PST) Date: Sat, 2 Mar 1996 04:30:13 -0800 (PST) From: GNU GNATS Message-Id: <199603021230.EAA10258@freefall.freebsd.org> To: freebsd-bugs Subject: Summary of Problem Reports Sender: owner-bugs@FreeBSD.ORG Precedence: bulk Number of currently open reports: 276 Number of curently analyzed reports: 15 From owner-freebsd-bugs Sat Mar 2 04:30:16 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA10280 for bugs-outgoing; Sat, 2 Mar 1996 04:30:16 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA10255 for freebsd-bugs; Sat, 2 Mar 1996 04:30:13 -0800 (PST) Date: Sat, 2 Mar 1996 04:30:13 -0800 (PST) From: GNU GNATS Message-Id: <199603021230.EAA10255@freefall.freebsd.org> To: freebsd-bugs Subject: List of open Problem Reports Sender: owner-bugs@FreeBSD.ORG Precedence: bulk This is the list of currently open problem reports [1994/11/14] bin/17 "mount -t foo /dev/wd1h /mnt" gives incorrect error [1994/11/18] conf/22 Cannot use links to share kernel objects [1994/11/30] kern/34 nullfs and union mounts can result in wild pointer r [1995/01/10] bin/104 pax -rwl may corrupt filesystem [1995/01/14] bin/115 systat iostat display doesn't scale high enough [1995/01/14] bin/116 disk transfer rates reported by systat :iostat are t [1995/01/14] bin/124 traceroute doesn't support -g flag. [1995/01/14] bin/129 fsck cannot take a mount point as an argument [1995/01/14] bin/133 mail program doesn't have editheaders option [1995/01/15] bin/146 version of compress is kinda old and slow [1995/01/20] bin/153 mount -u improvement for diskless systems [1995/01/21] misc/166 /usr/include/machine/asmacros.h includes uninstalled [1995/01/21] bin/172 cp -f does not work [1995/01/21] bin/173 rc trys to mount modload fs before ld is available. [1995/01/21] bin/174 Poor error message from stty [1995/01/22] kern/176 EIDRM not defined in errno.h [1995/01/24] gnu/183 can't resolve "operator <<" overload [1995/01/24] bin/184 send-pr says "Aborting ..." and happily removes the [1995/01/30] gnu/196 size of bss in *.o's reported wrong by size [1995/01/30] bin/198 1.1.5.1 pine binary loops; top shows fancy values [1995/02/01] bin/199 quiz(6) reading database bug, pattern matching bug [1995/02/14] kern/216 /kernel: panic: ffs_alloccg: map corrupted [1995/02/14] docs/218 dbm references from hash(3) [1995/02/16] kern/219 Performance on local net drops too much when SNDBUF [1995/02/16] i386/222 boot prompt doesn't always work [1995/03/02] misc/229 acos() core dump [1995/03/17] kern/247 Berkeley Packet Filter fix [1995/03/28] kern/275 qic-02 streamer won't work [1995/03/28] kern/281 Messages printed when checking CD ROM device too ver [1995/03/28] kern/282 buslogic adapter information WAY too verbose [1995/04/01] kern/291 PCI devices still probe/attach after being disabled [1995/04/09] bin/323 Creating lost+found causes fsck to stop fsck -y FDIV [1995/04/09] bin/326 Weekly cron generates some usage and error messages [1995/04/09] bin/329 FTP transfers above 99K shown in scientific notation [1995/04/15] kern/345 panic "biodone: page busy < 0" [1995/04/17] kern/349 Panic with bad dir [1995/04/20] kern/353 xcdplayer crashes machine (with NCR810 SCSI) [1995/04/20] misc/355 policy on /usr/local permission in base release [1995/04/20] bin/357 pkg_delete aborts when subcommand fails [1995/05/01] gnu/373 In response to admittedly bogus code, gcc emits an o [1995/05/01] kern/374 panic: bad dir [1995/05/08] bin/389 Simultaneous creation/deletion of dirs corrupts file [1995/05/12] bin/398 VI doesnt do the correct thing [1995/05/13] bin/401 Add REMOTE_* variables [1995/05/13] bin/402 w -n shows non-numeric addresses [1995/05/13] misc/403 FreeBSD 1-compiled tcsh, bash and zsh binaries dump [1995/05/14] kern/405 The gpio driver does not work with the AT-GPIB, only [1995/05/14] kern/416 page fault in syscons.c:scopen() [1995/05/14] bin/419 pkg_delete refuses to delete an incompletely added p [1995/05/15] misc/423 Sound devices are too insecure [1995/05/16] kern/425 arp entries not getting removed when interface chang [1995/05/16] kern/427 eg doesn't work with more than one card [1995/05/16] kern/428 configure is not foolproof [1995/05/22] kern/434 umapfs panics when mounting ufs over itself [1995/05/23] i386/440 want vidcontrol option to apply settings to all sysc [1995/05/25] kern/443 65 sendmails crashes system [1995/05/26] i386/444 GUS sound driver does not seem to work. [1995/05/26] kern/446 unable to diskless-boot a PC when the server mounts [1995/05/27] gnu/450 tar --exclude -c doesn't work [1995/05/28] gnu/451 cvsinit/cvs doesn't work as expected with perl [1995/05/29] bin/457 We may have an obscure csh bug [1995/05/30] docs/458 px doc does not find include figure [1995/05/31] bin/464 dialog_gauge goes one char too far for 100% value [1995/05/31] kern/466 Unexpected disk errors with sector-mapping controlle [1995/06/01] misc/469 ctm leaves temp files after errors [1995/06/05] kern/492 sysinstall shows "success" after "no space" failure. [1995/06/14] bin/514 Crash recovery impossible without static mt/chflags. [1995/06/15] bin/517 Bad group change with 'install' [1995/06/15] bin/519 execution of quotacheck from /etc/rc fails [1995/06/17] kern/528 slow 386 reports excessive interrupt-level buffer ov [1995/06/18] misc/530 Failed install from SCSI tape [1995/06/20] docs/536 No copyrights in usr/src/lib/libc/stdtime [1995/06/20] bin/537 FSCK Fails [1995/06/26] kern/565 slip freezes machine [1995/07/02] kern/579 sio: RS_IBUFSIZE at 256 bytes serial lines loose dat [1995/07/04] kern/587 if_le hangs on OACTIVE with 2k buffer [1995/07/04] kern/588 Configuration of DEC ethernet cards not possible [1995/07/05] bin/591 SPAP request REJexted in stead of NAKed [1995/07/06] i386/596 and conflict with _POSIX_SOURCE [1995/07/07] bin/599 pkg_add does not stop if dependencies are missing [1995/07/09] misc/605 NIS: get*bynis routine problems [1995/07/13] kern/611 WIDE-dhcp doesn't work with FreeBSD-2.0 bpf [1995/07/21] i386/631 if_ix does not support bpf, nor does it appear to su [1995/07/24] docs/633 no manpage for ndbm [1995/07/29] kern/638 Transmitted packets not passed to bpf in if_le.c [1995/08/01] docs/646 vmstat man page out of date [1995/08/01] bin/648 printf format conversion incorrect (duplicate) [1995/08/02] gnu/650 Current flex is outdated [1995/08/03] kern/652 Multiple addresses on one interface interacts badly [1995/08/05] gnu/655 ld -r of shared objects worked in 1.1.5, not in 2.0. [1995/08/07] bin/658 ifconfig alias has to be separately given [1995/08/07] bin/661 Hercules is not capable of having a ISO-Latin1 Scree [1995/08/11] gnu/672 Nor all ph headers get created [1995/08/11] ports/673 /bin/sh + inn1.4 innwatch going belly up [1995/08/11] bin/675 make does unnecessary rebuilds [1995/08/12] kern/677 X gets a bus error when calling mmap() [1995/08/13] bin/680 2.0.5's tip using termios doesn't act the way it did [1995/08/14] bin/683 cron(8) [1995/08/14] kern/688 Page fault: supervisor write, page not present [1995/08/15] i386/692 My modem is not found if my external cache is disabl [1995/08/16] bin/693 `pkg_add' is umask-sensitive [1995/08/16] kern/695 cat B > C ; cmp B C can fail! [1995/08/17] misc/697 "make -DCLOBBER" is broken [1995/08/18] kern/700 The comments in /sys/net/in.h are confusing [1995/08/21] kern/703 ppp not always deleting route properly when a ppp li [1995/08/22] bin/706 increased root DNS traffic and long latencies for r- [1995/08/29] bin/715 ls gives weird tabular form [1995/08/31] bin/716 W returns wrong results at login [1995/09/01] misc/717 ft.c attach fail on my Mountain tape drive [1995/09/02] bin/718 pkg_add incorrectly prints an error message [1995/09/15] bin/722 Off-by-one error in wbkgd() in ncurses [1995/09/19] bin/728 /bin/sh messes up quoting when going through eval [1995/09/21] docs/731 socketpair(2) and man page inconsistent about return [1995/09/23] docs/735 missing description for mount options in fstab(5) ma [1995/09/25] gnu/737 FreeBSD-current/src/gnu/usr.bin/gzip/Makefile [1995/09/26] bin/739 Some problems when an output filter reads all input [1995/09/26] docs/741 netstat -rn not showing all routes in Kernel - not i [1995/09/26] kern/742 syslog errors accessing Mac hard disks [patch] [1995/09/27] bin/743 vi cannot edit a file where the name starts with + [1995/09/27] bin/747 date(1) gives weird time zones and interprets GMT[+- [1995/09/27] kern/750 cd9660 confused by not-ready or I/O errors FDIV030 [1995/09/28] bin/751 crontab(1): `crontab -e' exits on SIGINT [1995/09/28] kern/752 setting multiple addresses for a single interfaces l [1995/09/28] kern/753 my archive scsi tape drive does not work [1995/09/28] docs/754 there is no man page for the psm(4) mouse driver [1995/10/01] kern/757 Removal of mounted CD-ROM causes reboot & single use [1995/10/01] bin/759 nfsd without arg's doesn't work [1995/10/03] kern/765 umount -f can`t umount a NFS filesystem in use [1995/10/05] misc/767 Configure-time does time-warp on non-UTC CMOS - FDIV [1995/10/06] kern/770 Floppy kernel won't boot with T485 or IDT L2 cache F [1995/10/08] kern/772 page fault while in kernel mode (two cases) [1995/10/09] kern/774 dump fails with "slave couldn't reopen disk: Device [1995/10/11] bin/777 patch doesn't realize stdin is closed and asks quest [1995/10/12] bin/778 tar complains "EOF not on block boundary" on a good [1995/10/12] bin/779 #include gets undefined 'rune_t' type. [1995/10/14] kern/781 OPEN_MAX in kernel config and FD_SETSIZE in /usr/inc [1995/10/18] bin/786 Problem with NIS and large group maps [1995/10/23] bin/789 pkg_add doesn't work [1995/10/25] kern/792 cd9660 very slow. [1995/10/25] kern/793 ep0 cannot be configured and more. [1995/10/26] kern/794 swap partition at offset 0 still broken [1995/10/27] misc/796 Network install doesn't update /etc/hosts FDIV036 [1995/10/27] bin/797 X probeonly during install gets Not Found error FDIV [1995/10/29] kern/798 PPP panics, touches 0xdeadc0de pointers [1995/10/29] misc/799 sysinstall segfaults if part of distribution missing [1995/10/29] docs/801 rlogind k, v, and x options are not documented [1995/10/30] misc/802 default fstab mounts disks in bad order [1995/10/31] bin/803 bsd m4 chokes and dies while FSF m4 works... [1995/10/31] kern/806 kernel default parameters need tuning [1995/11/01] bin/809 `.' gives the minimum number of (DIGITS+SIGN) [1995/11/09] ports/814 unable to compile the port of "pine3.91" [1995/11/11] bin/815 mountd reports unknown hosts with non-informative me [1995/11/12] kern/820 scsi tape problems [1995/11/13] kern/821 Config doesn't properly trap signals [1995/11/16] bin/826 tcpmux listener in inetd does not work [1995/11/20] kern/830 installing hang [1995/11/20] kern/831 one minor complaint about the kernel visual config c [1995/11/21] i386/832 Tape drive busy errors - dump aborts [1995/11/21] i386/833 SCSI hard disks time out during tape rewind - FDIV03 [1995/11/22] kern/834 pcvt: console keyboard locks up randonly [1995/11/22] kern/835 ed panics with SMC ultra with iomem, if no iomem in [1995/11/24] misc/838 /usr/src/lib Makefile assumes you want to install... [1995/11/25] bin/839 by default, use of "at" is overly restricted [1995/11/27] bin/841 stale nfs mounts cannot be umounted [1995/11/27] kern/844 mbuf panic, dump available [1995/11/27] kern/845 Automatic reboot says you can abort but boots anyway [1995/11/27] conf/846 2.1R install disk tries to use sd0 even if not reque [1995/11/28] misc/848 Inst gripes about geometry but won't accept true val [1995/11/28] misc/849 Install skimps on inodes and newfs default is wrong [1995/11/28] bin/850 dump treats write-protect as an EOT & spoils set FDI [1995/11/29] bin/852 Sendmail is loosing mail (apparently)! [1995/11/30] bin/854 swapinfo shows incorrect information for vnconfig'd [1995/11/30] misc/856 Install 2.0.5 Upgrade option does too much damage FD [1995/11/30] ports/857 Need ANSI_C define to not declare some functions [1995/12/01] bin/859 /bin/sh -c does not ignore SIGINT [1995/12/02] kern/860 visual mode in kernel -c is too restrictive [1995/12/03] kern/861 sb16 support in 2.1 is erratic and has cosmetic defe [1995/12/03] kern/863 panic on kernel page fault, NULL curproc [1995/12/04] kern/866 pcvt causes system console to lock up [1995/12/04] i386/867 Notebook with APM and 3C589C in PCMCIA freezes after [1995/12/06] ports/869 xcdplayer installs itself is /usr/X11R6, not /usr/lo [1995/12/06] ports/871 port.subdir.mk DEBUG_FLAGS is not used for CFLAGS [1995/12/08] misc/875 Cleaned code using -Wall to remove warnings [1995/12/08] kern/876 NFS allows bogus accesses to cached data [1995/12/09] misc/882 Makefile is not smart enough to bypass libraries... [1995/12/09] ports/883 tclX-port does not build properly [1995/12/09] kern/884 arnet driver does not assert DTR, which is necessary [1995/12/14] misc/893 terminfo.h not installed??? [1995/12/17] kern/900 ext2fs triggers divide by zero trap in vnode_pager_h [1995/12/18] kern/902 system becomes very sluggish, odd messages, odd vmst [1995/12/20] i386/906 /sys/i386/boot/netboot/nb8390.com cannot recognize N [1995/12/21] kern/907 scsi-dat tape station has stopped working [1995/12/21] bin/908 sed bug with trailing backslashes [1995/12/24] kern/912 unmount: dangling vnode [1995/12/24] conf/913 2.1.0-RELEASE, problem with cpio verbosity in instal [1995/12/25] bin/914 hayes dialer for tip fails 1st attempt to dial [1995/12/29] kern/919 weird output of vmstat, iostat, top [1995/12/29] kern/920 sio output looses chars in fifo on close() [1995/12/29] kern/921 getrusage() returns 0 after system up for a long tim [1995/12/31] kern/924 EISA devices have disappeared from vmstat/systat int [1996/01/01] bin/926 Mounting nfs disks before starting mountd: Chicken o [1996/01/02] kern/927 VGA mode not restored [1996/01/03] kern/930 sio/getty problem? [1996/01/06] kern/932 de0 occasionally enables 100baseTX when plugged into [1996/01/06] misc/934 ppp dies with Bus Error when processing long LOGIN s [1996/01/07] kern/938 after heavy disk I/O, processes sleep on "newbuf" in [1996/01/09] kern/940 panic: free vnode isn't [1996/01/12] misc/942 X11 mono server dumps core on supported video hardwa [1996/01/13] ports/944 Security fixes for Fvwm 1.24r [1996/01/15] kern/946 divide-by-zero in kernel on bad disk info [1996/01/16] kern/949 panic, undebugable dump? [1996/01/16] kern/950 Two PCI bridge chips fail (multiple multiport ethern [1996/01/17] kern/951 -current kernel crashes with devfs error on bootup [1996/01/19] ports/955 make CFLAGS=whatever for a port will not be honored [1996/01/19] kern/956 Kernel page fault, null callp [1996/01/19] bin/958 ttys file does not include all ptys [1996/01/20] i386/960 gameport enabling on ProAudio Spectrum isn't documen [1996/01/21] bin/961 'more $file', incorrect CRLF compacting. [1996/01/22] kern/962 panic on shutdown -- have crash dump [1996/01/23] ports/968 Netscape & cern_httpd ports out of date/dead links [1996/01/25] kern/971 Default limits for number of processes per user ridi [1996/01/25] conf/972 inetd.conf should comment out k-services if no Kerbe [1996/01/27] kern/974 ktrace causes panic: freeing busy page [1996/01/28] kern/975 getrusage returns negative deltas [1996/01/28] kern/976 NCR SCSI driver gives assertion errors and disk beco [1996/01/29] kern/977 system panic on sowakeup() [1996/01/29] kern/978 Three deadlocks in row [1996/01/29] kern/979 Linux programs using pipes crash system [1996/01/30] bin/981 clnt_broadcast() is not aware of aliases [1996/02/01] bin/986 problems make-ing with cd in the rule [1996/02/03] kern/989 devfs error messages on boot [1996/02/03] kern/991 pcvt keyboard doesn't accept input at crash reboot [1996/02/03] bin/993 g++ complains about /usr/include/machine/cpufunc.h [1996/02/04] kern/994 syscons bug in ESC[nX handling (w/fix) [1996/02/05] misc/995 /var/run/gated.pid is deleted [1996/02/06] kern/998 badness in file system silently crashes machine [1996/02/07] bin/999 /usr/share/mk/sys.mk missing common $(RM) macro [1996/02/07] docs/1000 miscellaneous man page bugs [1996/02/07] kern/1001 M_NAMEI malloc leak in the kernel [1996/02/08] ports/1005 netscape port is obsolete, mv netscape2 netscape [1996/02/08] kern/1008 Daily crash while writing network backups to local t [1996/02/09] docs/1010 no man page for qcamcontrol(8) [1996/02/09] kern/1012 vnode_pager_putpages: attempt to write meta-data!!! [1996/02/10] kern/1016 panic: vm_page_free: freeing free page, sddump: no s [1996/02/10] kern/1017 ssh stopped working between 15th Jan and 9th Feb [1996/02/12] kern/1018 panic: unwire: page not in pmap [1996/02/12] bin/1019 getty cannot detect ppp logins [1996/02/12] kern/1020 Boca 16-port board still hangs [1996/02/12] bin/1021 pppd doesn't handle PAP-only authentication well [1996/02/12] bin/1022 daily security report has too much junk in it [1996/02/12] docs/1023 using touch to create swap file for NFS doesn't work [1996/02/13] misc/1024 installation may delete partitions on existing boot [1996/02/14] kern/1026 deadlocks if parent vfork and child has cntrl termin [1996/02/14] kern/1027 panic on vm_map_insert [1996/02/14] bin/1028 shutdown -r does not seem to always complete [1996/02/15] bin/1029 cd behaves erraticly if cwd is a mount-point, which [1996/02/17] bin/1030 /bin/sh does not pass environment variables on prope [1996/02/18] kern/1034 Instant panic in -current [1996/02/19] bin/1035 ls to terminal always uses ? for non-printable chars [1996/02/19] docs/1036 List of dead xrefs in man pages [1996/02/19] bin/1037 2.x telnetd handles CTRL-M differently than other tt [1996/02/23] bin/1040 with certain flags, route can reboot your machine. [1996/02/25] i386/1042 Warning from sio driver reports wrong device FDIV045 [1996/02/26] misc/1043 vm_bounce_alloc error on 2.1 install with 4G drive [1996/02/26] docs/1044 clri(8) man page references man pages that don't exi [1996/02/27] kern/1045 Lockup: b_to_q to a clist with no reserved cblocks [1996/02/27] misc/1046 X dies with sig11 with -current [1996/02/27] gnu/1047 send-pr: Aborting... [1996/02/28] i386/1048 ep driver fails to detect card when told specific va [1996/02/28] kern/1049 /kernel: arpresolve: can't allocate llinfo for 194.1 [1996/02/28] bin/1050 Process (zip) hangs (unkillable) after floppy error [1996/02/29] ports/1051 zip fails on dos partition [1996/02/29] bin/1052 /bin/sh problem with new GCC (snapshot for 2.8) [1996/02/29] bin/1053 /bin/sh problem with new GCC (snapshot for 2.8) [1996/02/29] bin/1054 /bin/sh problem with new GCC (snapshot for 2.8) [1996/03/02] pending/1055 request for a customer id This is the list of problem reports already analyzed: [1994/12/01] kern/35 mount -t union -o -b : lower layer not seen by shell [1995/01/11] i386/105 Distributed libm (msun) has non-standard error handl [1995/01/22] docs/177 man pages missing for SYSV IPC funtions [1995/03/20] kern/260 msync and munmap don't bother to update mod times [1995/03/20] docs/264 There are no manual pages for the forms library. [1995/03/22] kern/267 NFS code gives error messages, systems jams for a fe [1995/05/09] bin/392 Simultaneous cp and ls of files on dos f/s hangs pro [1995/06/17] kern/527 dump causes assertion in ncr.c [1995/06/21] docs/538 MAP_FILE not mentioned in mmap man page. [1995/10/07] bin/771 telnet character mode not set and broken when set - [1995/10/15] kern/782 chmod does a null pointer dereference [1995/12/29] misc/922 From line handling incorrect in mail.local [1996/01/09] bin/941 pkg_create removes current directory if interupted [1996/01/22] kern/965 2.0.5: system crashes daily because of "multiple fre [1996/02/08] bin/1006 Kerberized su has poor password interface /* EOF -- this list has not been truncated */ From owner-freebsd-bugs Sat Mar 2 06:40:03 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA16786 for bugs-outgoing; Sat, 2 Mar 1996 06:40:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA16755 Sat, 2 Mar 1996 06:40:01 -0800 (PST) Resent-Date: Sat, 2 Mar 1996 06:40:01 -0800 (PST) Resent-Message-Id: <199603021440.GAA16755@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, enami@ba2.so-net.or.jp Received: from mail.ba2.so-net.or.jp (mail.ba2.so-net.or.jp [202.238.95.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA16226 for ; Sat, 2 Mar 1996 06:32:19 -0800 (PST) Received: from euphoria.enami.ba2.so-net.or.jp (ppp580e.ykhm.ap.so-net.or.jp [202.238.88.14]) by mail.ba2.so-net.or.jp (8.7.3/3.4W396011914) with ESMTP id XAA15496 for ; Sat, 2 Mar 1996 23:32:11 +0900 Received: (from enami@localhost) by euphoria.enami.ba2.so-net.or.jp (8.7.4/3.4W4-euphoria) id XAA00902; Sat, 2 Mar 1996 23:36:27 +0900 (JST) Message-Id: <199603021436.XAA00902@euphoria.enami.ba2.so-net.or.jp> Date: Sat, 2 Mar 1996 23:36:27 +0900 (JST) From: enami@ba2.so-net.or.jp Reply-To: enami@ba2.so-net.or.jp To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/1056: pppd failes if -detach Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 1056 >Category: bin >Synopsis: pppd fails if -detach >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Mar 2 06:40:01 PST 1996 >Last-Modified: >Originator: enami tsugutomo >Organization: a hacker in japan >Release: FreeBSD 2.2-CURRENT i386 >Environment: FreeBSD 2.2, 486DX2, 12M mem, ... >Description: pppd failes to set control terminal if -detach option is given. >How-To-Repeat: Run pppd with -detach option. >Fix: I think there is no need to set control terminal if pppd doesn't detached. *** main.c 1996/03/02 13:36:46 1.1 --- main.c 1996/03/02 13:37:20 *************** *** 329,335 **** hungup = 0; kill_link = 0; ! if (!default_device) setsid(); /* run connection script */ --- 329,335 ---- hungup = 0; kill_link = 0; ! if (!default_device && !nodetach) setsid(); /* run connection script */ *************** *** 360,366 **** set_up_tty(fd, 0); /* attach to the controlling tty for signals */ ! if (!default_device && ioctl(fd, TIOCSCTTY) < 0) { syslog(LOG_ERR, "ioctl(TIOCSCTTY) : %m"); die(1); } --- 360,366 ---- set_up_tty(fd, 0); /* attach to the controlling tty for signals */ ! if (!default_device && !nodetach && ioctl(fd, TIOCSCTTY) < 0) { syslog(LOG_ERR, "ioctl(TIOCSCTTY) : %m"); die(1); } >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sat Mar 2 16:03:27 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA26413 for bugs-outgoing; Sat, 2 Mar 1996 16:03:27 -0800 (PST) Received: from birk04.studby.uio.no (birk04.studby.uio.no [129.240.214.13]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA26408 for ; Sat, 2 Mar 1996 16:03:24 -0800 (PST) Received: (from aagero@localhost) by birk04.studby.uio.no (8.6.12/8.6.12) id BAA00291; Sun, 3 Mar 1996 01:03:23 +0100 Date: Sun, 3 Mar 1996 01:03:23 +0100 Message-Id: <199603030003.BAA00291@birk04.studby.uio.no> From: Aage Roebekk To: freebsd-bugs@freebsd.org Subject: unsigned 32 bit uid breaks ar(1) MIME-Version: 1.0 Sender: owner-bugs@freebsd.org Precedence: bulk If someone e.g. on NFS as root, which maps to uid -2, creates a archive with ar(1), the uid field overflows the 6 character array declared in the structure defined in /usr/include/ar.h. This can be a problem when e.g. doing a "make world" on a NFS mounted filesystem. Perhaps an option to use 16 bit unsigned uids would be appropriate? Editing the ar structure is of course not an option, which would break all implementations expecting char[6] uid and char[6] gid. -aage