From owner-freebsd-bugs  Sun Oct 18 06:00:09 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA15031
          for freebsd-bugs-outgoing; Sun, 18 Oct 1998 06:00:09 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA14976
          for <freebsd-bugs@FreeBSD.org>; Sun, 18 Oct 1998 06:00:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id GAA23693;
	Sun, 18 Oct 1998 06:00:01 -0700 (PDT)
Received: from camel14.mindspring.com (camel14.mindspring.com [207.69.200.64])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA14350
          for <FreeBSD-gnats-submit@freebsd.org>; Sun, 18 Oct 1998 05:51:25 -0700 (PDT)
          (envelope-from brdean@mindspring.com)
Received: from vger.foo.com (user-38ld9e3.dialup.mindspring.com [209.86.165.195])
	by camel14.mindspring.com (8.8.5/8.8.5) with ESMTP id IAA04399
	for <FreeBSD-gnats-submit@freebsd.org>; Sun, 18 Oct 1998 08:51:01 -0400 (EDT)
Received: (from bsd@localhost)
	by vger.foo.com (8.9.1/8.9.1) id IAA17735;
	Sun, 18 Oct 1998 08:51:03 -0400 (EDT)
	(envelope-from bsd)
Message-Id: <199810181251.IAA17735@vger.foo.com>
Date: Sun, 18 Oct 1998 08:51:03 -0400 (EDT)
From: Brian Dean <brdean@mindspring.com>
Reply-To: brdean@mindspring.com
To: FreeBSD-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: 3.2
Subject: i386/8368: 3.0-RELEASE: boot failure after install, possible problem with BootEasy
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8368
>Category:       i386
>Synopsis:       3.0-RELEASE: boot failure after install, possible problem with BootEasy
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Oct 18 06:00:01 PDT 1998
>Last-Modified:
>Originator:     Brian Dean
>Organization:
>Release:        FreeBSD 3.0-RELEASE i386
>Environment:

FreeBSD vger.foo.com 3.0-RELEASE FreeBSD 3.0-RELEASE #0: Sat Oct 17 21:41:25 GMT 1998     root@vger.foo.com:/usr/src/sys/compile/VGER  i386

Motherboard:	QDI Brilliant (440BX) w/Pentium II 300MHz CPU
Disk:		/kernel: wdc0 at 0x1f0-0x1f7 irq 14 on isa
		/kernel: wdc0: unit 0 (wd0): <ST38641A>
		/kernel: wd0: 8207MB (16809660 sectors), 16676 cyls, 16 heads, 63 S/T, 512 B/S

>Description:

The system would not boot after 3.0-RELEASE was installed.  The
problem appears to be related to having a DOS partition defined.  When
presented with the BootEasy screen, i.e., Press 'F1 for DOS, F2 for
FreeBSD', pressing any function key results only in a beep.  FreeBSD
will not boot.

>How-To-Repeat:

Boot with the 3.0-RELEASE boot floppy.  Start with a clean disk (no
partitions).  At the disk partitioning screen, first create a DOS
partition, partition type = 6 (I used a 1024MB partition size).  Then
create a FreeBSD partition, type = 165, using all of the remaining
space.  Choose the "BootEasy" boot block.  Continue to define slices
in the FreeBSD parition, and install FreeBSD.  Reboot.  The system
should reset, and won't be able to get past choosing which partition
to boot from.

>Fix:

Installation using a dedicated disk, i.e., no 'fdisk' paritions, works
fine.
>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Sun Oct 18 13:01:28 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA01885
          for freebsd-bugs-outgoing; Sun, 18 Oct 1998 13:01:28 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01870;
          Sun, 18 Oct 1998 13:01:22 -0700 (PDT)
          (envelope-from rnordier@FreeBSD.org)
From: Robert Nordier <rnordier@FreeBSD.ORG>
Received: (from rnordier@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id NAA08819;
	Sun, 18 Oct 1998 13:01:20 -0700 (PDT)
Date: Sun, 18 Oct 1998 13:01:20 -0700 (PDT)
Message-Id: <199810182001.NAA08819@freefall.freebsd.org>
To: brdean@mindspring.com, rnordier@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG,
        rnordier@FreeBSD.ORG
Subject: Re: i386/8368
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: 3.0-RELEASE: boot failure after install, possible problem with BootEasy

State-Changed-From-To: open-feedback
State-Changed-By: rnordier
State-Changed-When: Sun Oct 18 12:57:36 PDT 1998
State-Changed-Why: 
Requesting further details from submitter.


Responsible-Changed-From-To: freebsd-bugs->rnordier
Responsible-Changed-By: rnordier
Responsible-Changed-When: Sun Oct 18 12:57:36 PDT 1998
Responsible-Changed-Why: 
I'll handle this.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Mon Oct 19 00:20:08 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id AAA28599
          for freebsd-bugs-outgoing; Mon, 19 Oct 1998 00:20:08 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA28589
          for <freebsd-bugs@FreeBSD.org>; Mon, 19 Oct 1998 00:20:05 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id AAA26294;
	Mon, 19 Oct 1998 00:20:01 -0700 (PDT)
Received: from beebite.ugh.net.au ([203.17.118.148])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA28129
          for <FreeBSD-gnats-submit@freebsd.org>; Mon, 19 Oct 1998 00:13:23 -0700 (PDT)
          (envelope-from andrew@ugh.net.au)
Received: (from andrew@localhost)
	by beebite.ugh.net.au (8.8.8/8.8.8) id HAA00919;
	Mon, 19 Oct 1998 07:12:16 GMT
	(envelope-from andrew)
Message-Id: <199810190712.HAA00919@beebite.ugh.net.au>
Date: Mon, 19 Oct 1998 07:12:16 GMT
From: andrew@ugh.net.au
Reply-To: andrew@ugh.net.au
To: FreeBSD-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: 3.2
Subject: bin/8369: netstat seems to miss a connection
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8369
>Category:       bin
>Synopsis:       netstat seems to miss a connection
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Oct 19 00:20:01 PDT 1998
>Last-Modified:
>Originator:     Andrew
>Organization:
UgH!
>Release:        FreeBSD 2.2.7-STABLE i386
>Environment:

	FreeBSD stable as of yesterday. Rebuilt kernel. Running ppp -alias.

>Description:

I'm making a port and it is ftping a file from ftp.freebsd.org but the
connection is marked as FIN_WAIT_2 in netstat. The file is arriving according
to fetch and the modem receive light is full on but netstat says:

Active Internet connections
Proto Recv-Q Send-Q  Local Address          Foreign Address        (state)
tcp        0      0  ts1m48.the-gc.ne.1037  foxy.ion.com.au.8080   FIN_WAIT_2
tcp        0      0  ts1m13.the-gc.ne.1031  foxy.ion.com.au.8080   FIN_WAIT_2
tcp        0      0  ts1m13.the-gc.ne.1030  irc01.powerup.co.6667  ESTABLISHED
tcp        0      0  beebite.telnet         seabite.2052           ESTABLISHED
tcp        0    423  beebite.telnet         seabite.2051           ESTABLISHED
tcp        0      0  beebite.telnet         seabite.2050           ESTABLISHED
tcp        0      0  beebite.telnet         seabite.2049           ESTABLISHED
udp        0      0  localhost.domain       *.*
udp        0      0  ts1m48.the-gc.ne.domai *.*
udp        0      0  beebite.domain         *.*

foxy.ion.com.au is set as my proxy. ts1m48.the-gc.net is my address on the tun
interface.

>How-To-Repeat:

It does it quite regularly...not just when making ports either.

>Fix:
	
	

>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Mon Oct 19 01:00:06 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id BAA01861
          for freebsd-bugs-outgoing; Mon, 19 Oct 1998 01:00:06 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA01856
          for <freebsd-bugs@FreeBSD.org>; Mon, 19 Oct 1998 01:00:03 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id BAA27548;
	Mon, 19 Oct 1998 01:00:01 -0700 (PDT)
Date: Mon, 19 Oct 1998 01:00:01 -0700 (PDT)
Message-Id: <199810190800.BAA27548@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.ORG
From: Marc Slemko <marcs@znep.com>
Subject: Re: bin/8369: netstat seems to miss a connection
Reply-To: Marc Slemko <marcs@znep.com>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR bin/8369; it has been noted by GNATS.

From: Marc Slemko <marcs@znep.com>
To: andrew@ugh.net.au
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: bin/8369: netstat seems to miss a connection
Date: Mon, 19 Oct 1998 00:56:32 -0700 (PDT)

 On Mon, 19 Oct 1998 andrew@ugh.net.au wrote:
 
 > >Description:
 > 
 > I'm making a port and it is ftping a file from ftp.freebsd.org but the
 > connection is marked as FIN_WAIT_2 in netstat. The file is arriving according
 > to fetch and the modem receive light is full on but netstat says:
 > 
 > Active Internet connections
 > Proto Recv-Q Send-Q  Local Address          Foreign Address        (state)
 > tcp        0      0  ts1m48.the-gc.ne.1037  foxy.ion.com.au.8080   FIN_WAIT_2
 > tcp        0      0  ts1m13.the-gc.ne.1031  foxy.ion.com.au.8080   FIN_WAIT_2
 
 Perfectly legitimate.
 
 FIN_WAIT_2 is a valid state when the connection has been half closed.  No
 more data can be sent, but it can (and is) still accepting data.
 
 Using the -b option to fetch will avoid this, but it isn't a problem so
 there is no reason to avoid it.
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Mon Oct 19 02:50:09 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id CAA14082
          for freebsd-bugs-outgoing; Mon, 19 Oct 1998 02:50:09 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA14043
          for <freebsd-bugs@FreeBSD.org>; Mon, 19 Oct 1998 02:50:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id CAA01243;
	Mon, 19 Oct 1998 02:50:01 -0700 (PDT)
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id CAA13736;
          Mon, 19 Oct 1998 02:46:48 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199810190946.CAA13736@hub.freebsd.org>
Date: Mon, 19 Oct 1998 02:46:48 -0700 (PDT)
From: tomas@ftp.sk
To: freebsd-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: www-1.0
Subject: i386/8370: unable to install 3.0-RELEASE from dos partition
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8370
>Category:       i386
>Synopsis:       unable to install 3.0-RELEASE from dos partition
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Oct 19 02:50:00 PDT 1998
>Last-Modified:
>Originator:     tomas hodan
>Organization:
ftp
>Release:        3.0-RELEASE
>Environment:
>Description:
unable to install 3.0-RELEASE from dos partition
>How-To-Repeat:

>Fix:

>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Mon Oct 19 06:01:09 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA02508
          for freebsd-bugs-outgoing; Mon, 19 Oct 1998 06:01:09 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA02500
          for <freebsd-bugs@FreeBSD.ORG>; Mon, 19 Oct 1998 06:01:04 -0700 (PDT)
          (envelope-from matt@zigg.com)
Received: from localhost (matt@localhost)
	by megaweapon.zigg.com (8.8.8/8.8.8) with SMTP id JAA09682
	for <freebsd-bugs@FreeBSD.ORG>; Mon, 19 Oct 1998 09:07:29 -0400 (EDT)
	(envelope-from matt@zigg.com)
Date: Mon, 19 Oct 1998 09:07:28 -0400 (EDT)
From: Matt Behrens <matt@zigg.com>
To: freebsd-bugs@FreeBSD.ORG
Subject: Re: bin/8352: 3.0-RELEASE sysinstall bombs on newfs
In-Reply-To: <199810170240.TAA26324@freefall.freebsd.org>
Message-ID: <Pine.BSF.4.02A.9810190907040.9669-100000@megaweapon.zigg.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

This bug has been fixed.  Thanks.

On Fri, 16 Oct 1998 FreeBSD-gnats-submit@FreeBSD.ORG wrote:

> Thank you very much for your problem report.
> It has the internal identification `bin/8352'.
> The individual assigned to look at your
> report is: freebsd-bugs. 
> 
> >Category:       bin
> >Responsible:    freebsd-bugs
> >Synopsis:       3.0-RELEASE sysinstall bombs on newfs
> >Arrival-Date:   Fri Oct 16 19:40:01 PDT 1998
> 

Matt Behrens <matt@zigg.com>   | If only I could learn Japanese and get my
Servant of Karen Behrens       | hands on all 200 Sailor Moon episodes and
Engineer, Nameless IRC Network | all the movies, I think my life would
I eat Penguins for breakfast.  | finally be complete. . . . . . . . . . .


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Mon Oct 19 08:50:06 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA17435
          for freebsd-bugs-outgoing; Mon, 19 Oct 1998 08:50:06 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17430
          for <freebsd-bugs@FreeBSD.org>; Mon, 19 Oct 1998 08:50:03 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id IAA21654;
	Mon, 19 Oct 1998 08:50:01 -0700 (PDT)
Date: Mon, 19 Oct 1998 08:50:01 -0700 (PDT)
Message-Id: <199810191550.IAA21654@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.ORG
From: Jason Liao <jasonl@quanxing.org>
Subject: Re: i386/8131: Support for PCI NE2000 compatible Ethernet card in the `netboot' code
Reply-To: Jason Liao <jasonl@quanxing.org>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR i386/8131; it has been noted by GNATS.

From: Jason Liao <jasonl@quanxing.org>
To: freebsd-gnats-submit@freebsd.org
Cc:  Subject: Re: i386/8131: Support for PCI NE2000 compatible Ethernet card in the `netboot' code
Date: Mon, 19 Oct 1998 08:44:05 -0700

 I just finished the netboot support for Intel i82557/82558-based Fast
 Ethernet NICs (including Intel EtherExpress Pro/100B).  The boot code is
 based on the if_fxp driver by David Greenman.  The PCI portion is
 written in assembly language using PCI BIOS calls.  The source is
 available at http://www.quanxing.org/netboot/ .
 
 Just before I submit this follow-up, I found that another contributor
 had done the netboot support for Intel i82557/82558-based NICs.  See
 problem report i386/8171 for details.
 
 --
 ---------------------
      Jason Liao
 <jasonl@quanxing.org>
 ---------------------
 
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Mon Oct 19 09:50:07 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA22939
          for freebsd-bugs-outgoing; Mon, 19 Oct 1998 09:50:07 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22927
          for <freebsd-bugs@FreeBSD.org>; Mon, 19 Oct 1998 09:50:03 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id JAA24417;
	Mon, 19 Oct 1998 09:50:00 -0700 (PDT)
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA22581;
          Mon, 19 Oct 1998 09:45:58 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199810191645.JAA22581@hub.freebsd.org>
Date: Mon, 19 Oct 1998 09:45:58 -0700 (PDT)
From: aef@shu.smolensk.su
To: freebsd-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: www-1.0
Subject: i386/8373: make buildworld on 3.0-RELEASE don't  work
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8373
>Category:       i386
>Synopsis:       make buildworld on 3.0-RELEASE don't  work
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Oct 19 09:50:00 PDT 1998
>Last-Modified:
>Originator:     Andrew Filonov
>Organization:
SHU
>Release:        3.0-RELEASE
>Environment:
FreeBSD shu.smolensk.su 3.0-980426-SNAP FreeBSD 3.0-980426-SNAP #7: Wed Sep  2 2 0:12:51 MSD 1998     root@shu.smolensk.su:/usr/src/sys/compile/LOCAL  i386

>Description:
I try to "make buildworld".
On run make in lib/csu/i386-elf i have a error:
========
cc -O2 -pipe -elf -Wall -Wno-unused -c crt1.c -o crt1.o
{standard input}: Assembler messages:
{standard input}:5: Error: Unknown pseudo-op:  `.section'
*** Error code 1
========
>How-To-Repeat:
On 3.0-RELEASE sources
cd lib/csu/i386-elf 
make

>Fix:

>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Mon Oct 19 10:30:07 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA26684
          for freebsd-bugs-outgoing; Mon, 19 Oct 1998 10:30:07 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26674
          for <freebsd-bugs@FreeBSD.org>; Mon, 19 Oct 1998 10:30:03 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id KAA26413;
	Mon, 19 Oct 1998 10:30:00 -0700 (PDT)
Received: from sinope.frii.com (sinope.frii.com [208.146.240.11])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26569
          for <FreeBSD-gnats-submit@freebsd.org>; Mon, 19 Oct 1998 10:29:02 -0700 (PDT)
          (envelope-from gnat@sinope.frii.com)
Received: (from gnat@localhost)
	by sinope.frii.com (8.9.1/8.9.1) id LAA23879;
	Mon, 19 Oct 1998 11:27:33 GMT
	(envelope-from gnat)
Message-Id: <199810191127.LAA23879@sinope.frii.com>
Date: Mon, 19 Oct 1998 11:27:33 GMT
From: gnat@frii.com
Reply-To: gnat@frii.com
To: FreeBSD-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: 3.2
Subject: misc/8374: 3.0-RELEASE src/install.sh refers to missing package smailcf
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8374
>Category:       misc
>Synopsis:       3.0-RELEASE/src/install.sh refers to missing package
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Oct 19 10:30:00 PDT 1998
>Last-Modified:
>Originator:     Nathan Torkington
>Organization:
Interchangeable Antipodeans, Inc.
>Release:        FreeBSD 3.0-RELEASE i386
>Environment:

3.0-RELEASE

>Description:

src/install.sh lists 'smailcf' as one of the source packages to install,
but there is no smailcf in the 3.0-RELEASE/src distribution.

>How-To-Repeat:

Look for yourself :-)

>Fix:
	
Either add the smailcf packages or take it out of install.sh

I don't know if this will cause a src installation to fail, because I
haven't yet tried to do one with 3.0-RELEASE.

>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Mon Oct 19 11:40:10 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA05064
          for freebsd-bugs-outgoing; Mon, 19 Oct 1998 11:40:10 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05048
          for <freebsd-bugs@FreeBSD.org>; Mon, 19 Oct 1998 11:40:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id LAA29325;
	Mon, 19 Oct 1998 11:40:01 -0700 (PDT)
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA03985;
          Mon, 19 Oct 1998 11:30:17 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199810191830.LAA03985@hub.freebsd.org>
Date: Mon, 19 Oct 1998 11:30:17 -0700 (PDT)
From: info@highwind.com
To: freebsd-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: www-1.0
Subject: kern/8375: pthread_cond_wait() spins the CPU
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8375
>Category:       kern
>Synopsis:       pthread_cond_wait() spins the CPU
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Oct 19 11:40:00 PDT 1998
>Last-Modified:
>Originator:     Robert Fleischman
>Organization:
HighWind Software, Inc.
>Release:        3.0 with LATEST libc_r
>Environment:
% uname -a
FreeBSD zonda.highwind.com 3.0-19980831-SNAP FreeBSD 3.0-19980831-SNAP #0: Mon Aug 31 14:03:19 GMT 1998     root@make.ican.net:/usr/src/sys/compile/GENERIC  i386

>Description:
If a number of threads are waiting for a condition, the application spins
the CPU at 100% and eventually hangs the application. I've included
a test program below which illustrates the problem.
>How-To-Repeat:
/* Illustration of FreeBSD pthread_cond_wait() bug
   
   This program sets up a conditional wait and fires off a dozen threads
   that simply wait for the condition. Once the threads are started, 
   the main thread loops signalling the condition once a second.

   Normally, this should result in "Signalling" and "Got Condition"
   being printed once a second. However, because of some bugs in
   FreeBSD, the pthread_cond_wait() spins the CPU and no progress is
   made.

   g++ -o condWaitBug -D_REENTRANT -D_THREAD_SAFE -g -Wall condWaitBug.C -pthread

*/

#include <assert.h>
#include <pthread.h>
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>

pthread_mutex_t lock;
pthread_cond_t condition;

static void *condThread(void *)
{
    // Wait until we are signalled, then print.
    while (true) {
	assert(!::pthread_cond_wait(&condition, &lock));
	::printf("Got Condition!\n");
    }
}

int main(int, char **)
{
    // Initialize Lock
    pthread_mutexattr_t lock_attr;
    assert(!::pthread_mutexattr_init(&lock_attr));
    assert(!::pthread_mutex_init(&lock, &lock_attr));
    assert(!::pthread_mutexattr_destroy(&lock_attr));

    // Initialize Condition
    pthread_condattr_t cond_attr;
    assert(!::pthread_condattr_init(&cond_attr));
    assert(!::pthread_cond_init(&condition, &cond_attr));
    assert(!::pthread_condattr_destroy(&cond_attr));

    // Lock the lock
    assert(!::pthread_mutex_lock(&lock));

    // Spawn off a dozen threads to get signalled
    for (int j = 0; j < 12; ++j) {
	pthread_t tid;
	pthread_attr_t attr;
	assert(!::pthread_attr_init(&attr));
	assert(!::pthread_create(&tid, &attr, condThread, 0));
	assert(!::pthread_attr_destroy(&attr));
    }

    // Sleep for 3 seconds to make sure the threads started up.
    timeval timeout;
    timeout.tv_sec = 3;
    timeout.tv_usec = 0;
    ::select(0, 0, 0, 0, &timeout);

    for (int k = 0; k < 60; ++k) {
	::printf("Signalling\n");
	::pthread_cond_signal(&condition);

	// Sleep for a second
	timeout.tv_sec = 1;
	timeout.tv_usec = 0;
	::select(0, 0, 0, 0, &timeout);
    }

    return EXIT_SUCCESS;
}

>Fix:

>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Mon Oct 19 12:55:16 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA12828
          for freebsd-bugs-outgoing; Mon, 19 Oct 1998 12:55:16 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from george.lbl.gov (george.lbl.gov [131.243.2.12])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12820
          for <bugs@freebsd.org>; Mon, 19 Oct 1998 12:55:14 -0700 (PDT)
          (envelope-from jin@george.lbl.gov)
Received: (from jin@localhost)
	by george.lbl.gov (8.8.8/8.8.8) id MAA07044;
	Mon, 19 Oct 1998 12:54:49 -0700 (PDT)
Date: Mon, 19 Oct 1998 12:54:49 -0700 (PDT)
From: Jin Guojun (FTG staff) <jin@george.lbl.gov>
Message-Id: <199810191954.MAA07044@george.lbl.gov>
To: se@mi.uni-koeln.de
Subject: pciconf does not report unloaded devices under 3.x-RELEASE, as well as the kernel, which causes modload failure
Cc: bugs@FreeBSD.ORG
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

STefan,

Under 3.0 RELEASE, the pciconf does not report these devices if there is
no driver is loaded into the kernel for them. This causes the modload fails:

# modload -v -ezatm_mod /lkm/znatmdrv.o
modload: error initializing module: Device not configured


The 2.2.7 and 3.0 dmesg and pciconf output are appened at the end of this mail.
The unused ISA devices are reported by dmesg on both systems, but not unused
PCI devices are not reported under 3.0. 
I do not know if this is kernel issue or PCI probe issue.

	-Jin

Appendix:	dmesg and pciconf output

FBSD2.2.7 # dmesg
...
Probing for devices on PCI bus 0:
chip0 <Intel 82440FX (Natoma) PCI and memory controller> rev 2 on pci0:0:0
chip1 <Intel 82371SB PCI-ISA bridge> rev 1 on pci0:1:0
chip2 <Intel 82371SB IDE interface> rev 0 on pci0:1:1
ncr0 <ncr 53c825a fast10 wide scsi> rev 19 int a irq 12 on pci0:10:0
ncr0 waiting for scsi devices to settle
(ncr0:1:0): "CDC 94181-15 5466" type 0 fixed SCSI 1
sd0(ncr0:1:0): Direct-Access 573MB (1173930 512 byte sectors)
fxp0 <Intel EtherExpress Pro 10/100B Ethernet> rev 2 int a irq 10 on pci0:11:0
fxp0: Ethernet address 00:a0:c9:9b:88:18
vga0 <VGA-compatible display device> rev 1 int a irq 11 on pci0:12:0
pci0:13:    vendor=0x1193, device=0x0001, class=network (unknown subclass 0x30) int a irq 9 [no driver assigned]
Probing for devices on the ISA bus:
sc0 at 0x60-0x6f irq 1 on motherboard
sc0: VGA color <16 virtual consoles, flags=0x0>
fe0 not found at 0x300
...
wd0: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S
wdc0: unit 1 (atapi): <FX120T/b03>, removable, intr, dma, iordis
1 3C5x9 board(s) on ISA found at 0x300
ep0 at 0x300-0x30f irq 15 on isa
ep0: aui/utp[*UTP*] address 00:20:af:ec:32:3c
ex0 not found at 0xffffffff
...

FBSD2.2.7 # pciconf -l
pci0:0:0:       class=0x060000 card=0x00000000 chip=0x12378086 rev=0x02 hdr=0x00
pci0:1:0:       class=0x060100 card=0x00000000 chip=0x70008086 rev=0x01 hdr=0x80
pci0:1:1:       class=0x010180 card=0x00000000 chip=0x70108086 rev=0x00 hdr=0x00
pci0:10:0:      class=0x010000 card=0x00000000 chip=0x00031000 rev=0x13 hdr=0x00
pci0:11:0:      class=0x020000 card=0x00018086 chip=0x12298086 rev=0x02 hdr=0x00
pci0:12:0:      class=0x030000 card=0x8a015333 chip=0x8a015333 rev=0x01 hdr=0x00
pci0:13:0:      class=0x023000 card=0x00000000 chip=0x00011193 rev=0x0a hdr=0x00

------------

FBSD3.x # dmesg
...
Probing for devices on PCI bus 0:
chip0: <Intel 82440FX System Controller (Natoma)> rev 0x02 on pci0.0.0
chip1: <Intel 82371SB PCI to ISA bridge> rev 0x01 on pci0.1.0
ide_pci0: <Intel PIIX4 Bus-master IDE controller> rev 0x01 on pci0.1.1
fxp0: <Intel EtherExpress Pro 10/100B Ethernet> rev 0x02 int a irq 10 on pci0.11.0
fxp0: Ethernet address 00:a0:c9:9b:88:18
ncr0: <ncr 53c825a fast10 wide scsi> rev 0x13 int a irq 12 on pci0.10.0
Probing for devices on the ISA bus:
sc0 at 0x60-0x6f irq 1 on motherboard
sc0: VGA color <16 virtual consoles, flags=0x0>
fe0 not found at 0x300
...
wdc0 not found at 0x1f0
1 3C5x9 board(s) on ISA found at 0x300
ep0 at 0x300-0x30f irq 15 on isa
ep0: aui/utp[*UTP*] address 00:20:af:ec:32:3c
ex0 not found at 0xffffffff
...

FBSD3.x # pciconf -l

chip0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x12378086 rev=0x02 hdr=0x00
chip1@pci0:1:0: class=0x060100 card=0x00000000 chip=0x70008086 rev=0x01 hdr=0x00
ide_pci0@pci0:1:1:      class=0x010180 card=0x00000000 chip=0x70008086 rev=0x01 hdr=0x00
chip2@pci0:1:2: class=0x0c0300 card=0x00000000 chip=0x70108086 rev=0x00 hdr=0x00
ncr0@pci0:10:0: class=0x010000 card=0x00000000 chip=0x00031000 rev=0x03 hdr=0x00
fxp0@pci0:11:0: class=0x020000 card=0x00018086 chip=0x12298086 rev=0x02 hdr=0x00

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Mon Oct 19 13:28:34 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA15657
          for freebsd-bugs-outgoing; Mon, 19 Oct 1998 13:28:34 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA15650
          for <bugs@FreeBSD.ORG>; Mon, 19 Oct 1998 13:28:33 -0700 (PDT)
          (envelope-from ken@panzer.plutotech.com)
Received: (from ken@localhost)
          by panzer.plutotech.com (8.9.1/8.8.5) id OAA24944;
          Mon, 19 Oct 1998 14:27:43 -0600 (MDT)
From: "Kenneth D. Merry" <ken@plutotech.com>
Message-Id: <199810192027.OAA24944@panzer.plutotech.com>
Subject: Re: pciconf does not report unloaded devices under 3.x-RELEASE, as well as the kernel, which causes modload failure
In-Reply-To: <199810191954.MAA07044@george.lbl.gov> from Jin Guojun at "Oct 19, 98 12:54:49 pm"
To: jin@george.lbl.gov (Jin Guojun)
Date: Mon, 19 Oct 1998 14:27:43 -0600 (MDT)
Cc: se@mi.uni-koeln.de, bugs@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL28s (25)]
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary=ELM908828863-24887-0_
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


--ELM908828863-24887-0_
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Jin Guojun wrote...
> STefan,
> 
> Under 3.0 RELEASE, the pciconf does not report these devices if there is
> no driver is loaded into the kernel for them. This causes the modload fails:
> 
> # modload -v -ezatm_mod /lkm/znatmdrv.o
> modload: error initializing module: Device not configured
> 
> 
> The 2.2.7 and 3.0 dmesg and pciconf output are appened at the end of this mail.
> The unused ISA devices are reported by dmesg on both systems, but not unused
> PCI devices are not reported under 3.0. 

I think unused PCI devices are reported if you boot with -v.

> I do not know if this is kernel issue or PCI probe issue.

[ ... ]

> FBSD3.x # pciconf -l
> 
> chip0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x12378086 rev=0x02 hdr=0x00
> chip1@pci0:1:0: class=0x060100 card=0x00000000 chip=0x70008086 rev=0x01 hdr=0x00
> ide_pci0@pci0:1:1:      class=0x010180 card=0x00000000 chip=0x70008086 rev=0x01 hdr=0x00
> chip2@pci0:1:2: class=0x0c0300 card=0x00000000 chip=0x70108086 rev=0x00 hdr=0x00
> ncr0@pci0:10:0: class=0x010000 card=0x00000000 chip=0x00031000 rev=0x03 hdr=0x00
> fxp0@pci0:11:0: class=0x020000 card=0x00018086 chip=0x12298086 rev=0x02 hdr=0x00
> 

Try the attached patch to src/usr.sbin/pciconf/pciconf.c and see if it
causes all of the devices to be printed out.

The PCI code in 3.0 is substantially different than the PCI code in the 2.x
tree.  The pciconf device listing code didn't work until I re-wrote it.

Anyway, let me know what the patched version of pciconf prints out.

Ken
-- 
Kenneth Merry
ken@plutotech.com

--ELM908828863-24887-0_
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: attachment; filename=pciconf.c.diffs
Content-Description: pciconf.c.diffs
Content-Transfer-Encoding: 7bit

==== //depot/cam/usr.sbin/pciconf/pciconf.c#12 - /usr/home/ken/perforce/cam/usr.sbin/pciconf/pciconf.c ====
*** /tmp/tmp.27776.0	Mon Oct 19 14:26:34 1998
--- /usr/home/ken/perforce/cam/usr.sbin/pciconf/pciconf.c	Mon Oct 19 14:25:28 1998
***************
*** 167,178 ****
  			return;
  		}
  		for (p = conf; p < &conf[pc.num_matches]; p++) {
- 			if ((p->pd_name == NULL) || (*p->pd_name == '\0'))
- 				continue;
  
  			printf("%s%d@pci%d:%d:%d:\tclass=0x%06x card=0x%08lx "
  			       "chip=0x%08lx rev=0x%02x hdr=0x%02x\n", 
! 			       p->pd_name, p->pd_unit, 
  			       p->pc_sel.pc_bus, p->pc_sel.pc_dev, 
  			       p->pc_sel.pc_func, (p->pc_class << 16) |
  			       (p->pc_subclass << 8) | p->pc_progif,
--- 167,177 ----
  			return;
  		}
  		for (p = conf; p < &conf[pc.num_matches]; p++) {
  
  			printf("%s%d@pci%d:%d:%d:\tclass=0x%06x card=0x%08lx "
  			       "chip=0x%08lx rev=0x%02x hdr=0x%02x\n", 
! 			       (p->pd_name && *p->pd_name) ? p->pd_name :
! 			       "none", p->pd_unit, 
  			       p->pc_sel.pc_bus, p->pc_sel.pc_dev, 
  			       p->pc_sel.pc_func, (p->pc_class << 16) |
  			       (p->pc_subclass << 8) | p->pc_progif,

--ELM908828863-24887-0_--

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Mon Oct 19 13:41:40 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA16771
          for freebsd-bugs-outgoing; Mon, 19 Oct 1998 13:41:40 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from george.lbl.gov (george.lbl.gov [131.243.2.12])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16762
          for <bugs@FreeBSD.ORG>; Mon, 19 Oct 1998 13:41:36 -0700 (PDT)
          (envelope-from jin@george.lbl.gov)
Received: (from jin@localhost)
	by george.lbl.gov (8.8.8/8.8.8) id NAA07912;
	Mon, 19 Oct 1998 13:41:12 -0700 (PDT)
Date: Mon, 19 Oct 1998 13:41:12 -0700 (PDT)
From: Jin Guojun (FTG staff) <jin@george.lbl.gov>
Message-Id: <199810192041.NAA07912@george.lbl.gov>
To: ken@plutotech.com
Subject: Re: pciconf does not report unloaded devices under 3.x-RELEASE, as well as the kernel, which causes modload failure
Cc: bugs@FreeBSD.ORG, se@mi.uni-koeln.de
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Ken,

The patch does fix pciconf problem, but modload still fails, any idea?

Thanks,

	-Jin

# pciconf -l
chip0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x12378086 rev=0x02 hdr=0x00
chip1@pci0:1:0: class=0x060100 card=0x00000000 chip=0x70008086 rev=0x01 hdr=0x00
ide_pci0@pci0:1:1:      class=0x010180 card=0x00000000 chip=0x70008086 rev=0x01 hdr=0x00
none0@pci0:9:0:         class=0x020300 card=0x00000000 chip=0x03001127 rev=0x00 hdr=0x00
ncr0@pci0:10:0: class=0x010000 card=0x00000000 chip=0x000f1000 rev=0x03 hdr=0x00
fxp0@pci0:11:0: class=0x020000 card=0x00018086 chip=0x12298086 rev=0x02 hdr=0x00
none0@pci0:12:0:        class=0x023000 card=0x00000000 chip=0x00011193 rev=0x0a hdr=0x00

# modload -v -ezatm_mod /lkm/znatmdrv.o
modload: error initializing module: Device not configured

> > FBSD3.x # pciconf -l
> > 
> > chip0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x12378086 rev=0x02 hdr=0x
> 00
> > chip1@pci0:1:0: class=0x060100 card=0x00000000 chip=0x70008086 rev=0x01 hdr=0x
> 00
> > ide_pci0@pci0:1:1:      class=0x010180 card=0x00000000 chip=0x70008086 rev=0x0
> 1 hdr=0x00
> > chip2@pci0:1:2: class=0x0c0300 card=0x00000000 chip=0x70108086 rev=0x00 hdr=0x
> 00
> > ncr0@pci0:10:0: class=0x010000 card=0x00000000 chip=0x00031000 rev=0x03 hdr=0x
> 00
> > fxp0@pci0:11:0: class=0x020000 card=0x00018086 chip=0x12298086 rev=0x02 hdr=0x
> 00
> > 
> 
> Try the attached patch to src/usr.sbin/pciconf/pciconf.c and see if it
> causes all of the devices to be printed out.
> 
> The PCI code in 3.0 is substantially different than the PCI code in the 2.x
> tree.  The pciconf device listing code didn't work until I re-wrote it.
> 
> Anyway, let me know what the patched version of pciconf prints out.
> 
> Ken

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Mon Oct 19 13:49:12 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA17635
          for freebsd-bugs-outgoing; Mon, 19 Oct 1998 13:49:12 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17627
          for <bugs@FreeBSD.ORG>; Mon, 19 Oct 1998 13:49:09 -0700 (PDT)
          (envelope-from ken@panzer.plutotech.com)
Received: (from ken@localhost)
          by panzer.plutotech.com (8.9.1/8.8.5) id OAA25198;
          Mon, 19 Oct 1998 14:48:37 -0600 (MDT)
From: "Kenneth D. Merry" <ken@plutotech.com>
Message-Id: <199810192048.OAA25198@panzer.plutotech.com>
Subject: Re: pciconf does not report unloaded devices under 3.x-RELEASE, as well as the kernel, which causes modload failure
In-Reply-To: <199810192041.NAA07912@george.lbl.gov> from Jin Guojun at "Oct 19, 98 01:41:12 pm"
To: jin@george.lbl.gov (Jin Guojun)
Date: Mon, 19 Oct 1998 14:48:37 -0600 (MDT)
Cc: bugs@FreeBSD.ORG, se@mi.uni-koeln.de
X-Mailer: ELM [version 2.4ME+ PL28s (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Jin Guojun wrote...
> Ken,
> 
> The patch does fix pciconf problem, but modload still fails, any idea?

[ ... ]

> # modload -v -ezatm_mod /lkm/znatmdrv.o
> modload: error initializing module: Device not configured

Sorry, dunno why it doesn't work.  Someone more familiar with modload will
have to tackle that one...

Ken
-- 
Kenneth Merry
ken@plutotech.com

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Mon Oct 19 14:50:09 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA23617
          for freebsd-bugs-outgoing; Mon, 19 Oct 1998 14:50:09 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23602
          for <freebsd-bugs@FreeBSD.org>; Mon, 19 Oct 1998 14:50:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id OAA07305;
	Mon, 19 Oct 1998 14:50:01 -0700 (PDT)
Received: from sleipnir.watson.org (SLEIPNIR.RES.CMU.EDU [128.2.91.229])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23447
          for <FreeBSD-gnats-submit@freebsd.org>; Mon, 19 Oct 1998 14:48:20 -0700 (PDT)
          (envelope-from robert@sleipnir.watson.org)
Received: (from robert@localhost)
	by sleipnir.watson.org (8.9.1/8.8.8) id OAA20173;
	Mon, 19 Oct 1998 14:29:52 -0400 (EDT)
	(envelope-from robert)
Message-Id: <199810191829.OAA20173@sleipnir.watson.org>
Date: Mon, 19 Oct 1998 14:29:52 -0400 (EDT)
From: robert@fledge.watson.org
Reply-To: robert+freebsd@cyrus.watson.org
To: FreeBSD-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: 3.2
Subject: kern/8376: clock_gettime and CLOCK_VIRTUAL -- not implemented
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8376
>Category:       kern
>Synopsis:       CLOCK_VIRTUAL not implemented
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Oct 19 14:50:00 PDT 1998
>Last-Modified:
>Originator:     Robert Watson
>Organization:
>Release:        FreeBSD 3.0-BETA i386
>Environment:

3.0-BETA

>Description:

This is either a documentation bug or a software bug.  Currently, clock_gettime
syscall does not implement CLOCK_VIRTUAL as described in clock_gettime(2).
EINVAL is returned.  Either a BUGS section should be added to clock_gettime(2)
to indicate that a described feature is not present, or the implementation
should be fixed.

>How-To-Repeat:
	struct timespec ts;
	if (clock_gettime(CLOCK_VIRTUAL, &ts) != 0) {
		perror("clock_gettime");
		exit(-1);
	}
>Fix:
	
Described in description.  I have not written up patches.  Presumably a fix
would require maintaining state in the proc structure -- this would be
inefficient in many ways as most processes don't use realtime clock data
about themselves.  Maintaining the accuracy of a lot of clocks is presumably
far less easy than maintaining it for a few.

>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Mon Oct 19 15:30:05 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA27215
          for freebsd-bugs-outgoing; Mon, 19 Oct 1998 15:30:05 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27208
          for <freebsd-bugs@FreeBSD.org>; Mon, 19 Oct 1998 15:30:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id PAA08384;
	Mon, 19 Oct 1998 15:30:01 -0700 (PDT)
Received: from orion.tamu.edu (orion.tamu.edu [128.194.177.3])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27090
          for <FreeBSD-gnats-submit@freebsd.org>; Mon, 19 Oct 1998 15:29:27 -0700 (PDT)
          (envelope-from daved@orion.tamu.edu)
Received: (from daved@localhost)
	by orion.tamu.edu (8.8.8/8.8.8) id RAA21591;
	Mon, 19 Oct 1998 17:30:32 -0500 (CDT)
	(envelope-from daved)
Message-Id: <199810192230.RAA21591@orion.tamu.edu>
Date: Mon, 19 Oct 1998 17:30:32 -0500 (CDT)
From: daved@tamu.edu
Reply-To: daved@tamu.edu
To: FreeBSD-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: 3.2
Subject: kern/8377: boot.config not being used.
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8377
>Category:       kern
>Synopsis:       boot.config not being used.
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Oct 19 15:30:00 PDT 1998
>Last-Modified:
>Originator:     Dave Duchscher
>Organization:
Texas A&M University
>Release:        FreeBSD 2.2.7-RELEASE i386
>Environment:



>Description:

boot.config file is read but the settings are not used.  I have made
the following changes to get things to work but someone should really
sanity check this patch.  My problem was that the -P switch would not
work with out this change.

>How-To-Repeat:

	

>Fix:
	
diff -Nur sys-dist/i386/boot/biosboot/boot.c sys/i386/boot/biosboot/boot.c
--- sys-dist/i386/boot/biosboot/boot.c	Fri Feb 27 16:56:14 1998
+++ sys/i386/boot/biosboot/boot.c	Sun Aug  9 08:51:14 1998
@@ -140,13 +140,18 @@
 	} else
 #endif	/*NAMEBLOCK*/
 		name = "kernel";
+loadstart:
+	/*
+	 * Ignore flags from previous attempted boot, if any.
+	 */
+	loadflags &= (RB_DUAL | RB_SERIAL);
+
 	if (boot_config[0] != '\0') {
 		printf("boot.config: %s", boot_config);
 		getbootdev(boot_config, &loadflags);
 		if (openrd() != 0)
 			name = "kernel";
 	}
-loadstart:
 	/* print this all each time.. (saves space to do so) */
 	/* If we have looped, use the previous entries as defaults */
 	printf("\r \n>> FreeBSD BOOT @ 0x%x: %d/%d k of memory, %s%s console\n"
@@ -159,13 +164,6 @@
 	       dosdev & 0x7f, devs[maj], unit, 'a' + part,
 	       name ? name : "*specify_a_kernel_name*",
 	       boot_help);
-
-	/*
-	 * Ignore flags from previous attempted boot, if any.
-	 * XXX this is now too strict.  Settings given in boot.config should
-	 * not be changed.
-	 */
-	loadflags &= (RB_DUAL | RB_SERIAL);
 
 	/*
 	 * Be paranoid and make doubly sure that the input buffer is empty.
>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Mon Oct 19 18:24:16 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA16792
          for freebsd-bugs-outgoing; Mon, 19 Oct 1998 18:24:16 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA16769;
          Mon, 19 Oct 1998 18:24:01 -0700 (PDT)
          (envelope-from steve@FreeBSD.org)
From: Steve Price <steve@FreeBSD.ORG>
Received: (from steve@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id SAA14419;
	Mon, 19 Oct 1998 18:23:58 -0700 (PDT)
Date: Mon, 19 Oct 1998 18:23:58 -0700 (PDT)
Message-Id: <199810200123.SAA14419@freefall.freebsd.org>
To: matt@zigg.com, steve@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG
Subject: Re: bin/8352
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: 3.0-RELEASE sysinstall bombs on newfs

State-Changed-From-To: open-closed
State-Changed-By: steve
State-Changed-When: Mon Oct 19 18:23:42 PDT 1998
State-Changed-Why: 
Closed at originator's request.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Mon Oct 19 18:26:42 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA17337
          for freebsd-bugs-outgoing; Mon, 19 Oct 1998 18:26:42 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from fledge.watson.org (COPLAND.CODA.CS.CMU.EDU [128.2.222.48])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA17326;
          Mon, 19 Oct 1998 18:26:39 -0700 (PDT)
          (envelope-from robert@cyrus.watson.org)
Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3])
	by fledge.watson.org (8.8.8/8.8.8) with SMTP id VAA16924;
	Mon, 19 Oct 1998 21:26:13 -0400 (EDT)
Date: Mon, 19 Oct 1998 21:26:13 -0400 (EDT)
From: Robert Watson <robert@cyrus.watson.org>
X-Sender: robert@fledge.watson.org
Reply-To: robert+freebsd@cyrus.watson.org
To: FreeBSD-gnats-submit@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG
Subject: Re: kern/8376: clock_gettime and CLOCK_VIRTUAL -- not implemented
In-Reply-To: <199810192150.OAA07300@freefall.freebsd.org>
Message-ID: <Pine.BSF.3.96.981019212331.16887A-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


Additionally, POSIX.1b-1993 indicates that the clock_* functions and
CLOCK_* constants should be defined in time.h, not in sys/time.h. 

(Bad luck for non-POSIX today, I have a copy of the spec in front of me
for a change -- that and I am trying to write portable code that uses
accurate timing on multiple platforms :).

On Mon, 19 Oct 1998 FreeBSD-gnats-submit@FreeBSD.ORG wrote:

> Thank you very much for your problem report.
> It has the internal identification `kern/8376'.
> The individual assigned to look at your
> report is: freebsd-bugs. 
> 
> >Category:       kern
> >Responsible:    freebsd-bugs
> >Synopsis:       CLOCK_VIRTUAL not implemented
> >Arrival-Date:   Mon Oct 19 14:50:00 PDT 1998
> 


  Robert N Watson 

Carnegie Mellon University            http://www.cmu.edu/
TIS Labs at Network Associates, Inc.  http://www.tis.com/
SafePort Network Services             http://www.safeport.com/
robert@fledge.watson.org              http://www.watson.org/~robert/


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Mon Oct 19 18:30:08 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA17847
          for freebsd-bugs-outgoing; Mon, 19 Oct 1998 18:30:08 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA17833
          for <freebsd-bugs@FreeBSD.org>; Mon, 19 Oct 1998 18:30:03 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id SAA14984;
	Mon, 19 Oct 1998 18:30:00 -0700 (PDT)
Date: Mon, 19 Oct 1998 18:30:00 -0700 (PDT)
Message-Id: <199810200130.SAA14984@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.ORG
From: Robert Watson <robert@cyrus.watson.org>
Subject: Re: kern/8376: clock_gettime and CLOCK_VIRTUAL -- not implemented
Reply-To: Robert Watson <robert@cyrus.watson.org>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR kern/8376; it has been noted by GNATS.

From: Robert Watson <robert@cyrus.watson.org>
To: FreeBSD-gnats-submit@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG
Cc:  Subject: Re: kern/8376: clock_gettime and CLOCK_VIRTUAL -- not implemented
Date: Mon, 19 Oct 1998 21:26:13 -0400 (EDT)

 Additionally, POSIX.1b-1993 indicates that the clock_* functions and
 CLOCK_* constants should be defined in time.h, not in sys/time.h. 
 
 (Bad luck for non-POSIX today, I have a copy of the spec in front of me
 for a change -- that and I am trying to write portable code that uses
 accurate timing on multiple platforms :).
 
 On Mon, 19 Oct 1998 FreeBSD-gnats-submit@FreeBSD.ORG wrote:
 
 > Thank you very much for your problem report.
 > It has the internal identification `kern/8376'.
 > The individual assigned to look at your
 > report is: freebsd-bugs. 
 > 
 > >Category:       kern
 > >Responsible:    freebsd-bugs
 > >Synopsis:       CLOCK_VIRTUAL not implemented
 > >Arrival-Date:   Mon Oct 19 14:50:00 PDT 1998
 > 
 
 
   Robert N Watson 
 
 Carnegie Mellon University            http://www.cmu.edu/
 TIS Labs at Network Associates, Inc.  http://www.tis.com/
 SafePort Network Services             http://www.safeport.com/
 robert@fledge.watson.org              http://www.watson.org/~robert/
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Mon Oct 19 20:58:25 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA01678
          for freebsd-bugs-outgoing; Mon, 19 Oct 1998 20:58:25 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from daleth.grace.edu (daleth.grace.edu [199.8.50.1])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA01671
          for <bugs@freebsd.org>; Mon, 19 Oct 1998 20:58:22 -0700 (PDT)
          (envelope-from linvilmd@daleth.grace.edu)
Received: from linvilmd.grace.edu ([199.8.49.87]) by daleth.grace.edu (8.8.0/8.8.0) with SMTP id XAA17688 for <bugs@freebsd.org>; Mon, 19 Oct 1998 23:52:08 -0500
Message-Id: <199810200452.XAA17688@daleth.grace.edu>
Comments: Authenticated sender is <linvilmd@[199.8.50.1]>
From: "MISTY D LINVILLE" <linvilmd@daleth.grace.edu>
To: bugs@FreeBSD.ORG
Date: Mon, 19 Oct 1998 22:58:01 +0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: 3.0 install from DOS
X-mailer: Pegasus Mail for Windows (v2.54)
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Hi, 

Even though I have all of the install directories in the right place 
(under c:\freebsd), the 3.0 install floppy refuses torecognize any of 
the distributions at install time.  I think this must be a bug.  
Thanks..

~Misty

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Mon Oct 19 22:10:07 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA06574
          for freebsd-bugs-outgoing; Mon, 19 Oct 1998 22:10:07 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA06564
          for <freebsd-bugs@FreeBSD.org>; Mon, 19 Oct 1998 22:10:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id WAA24213;
	Mon, 19 Oct 1998 22:10:01 -0700 (PDT)
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA06246;
          Mon, 19 Oct 1998 22:03:25 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199810200503.WAA06246@hub.freebsd.org>
Date: Mon, 19 Oct 1998 22:03:25 -0700 (PDT)
From: shirai@nintendo.co.jp
To: freebsd-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: www-1.0
Subject: misc/8378: Is termcap not maintained enough ?
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8378
>Category:       misc
>Synopsis:       Is termcap not maintained enough ?
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Mon Oct 19 22:10:00 PDT 1998
>Last-Modified:
>Originator:     Takashi SHIRAI
>Organization:
Nintendo, Co., Ltd.
>Release:        No concerned
>Environment:
No concerned
>Description:
/etc/termcap looks like not to be maintained enough, I think.
For example, entry 'kterm' refers to 'xterm' not to 'xterm-color', though it can treat ANSI color.
Some entries answer a wrong key-code, some entries don't know x? flags right.
It's an old status or an obsolute information, because of no maintenance of termcap, isn't it?
Of cource, it is not due to FreeBSD core team, then it's the probrem for all UNIX societies, I know.
But, for one probrem of FreeBSD, I want to treat this, to establish the project team,
Anyway, investigate /etc/termcap, please.
>How-To-Repeat:
see /etc/termcap

>Fix:
I think that each entries must be checked with the terminal status, one by one.
I cannot found no other way.

>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Mon Oct 19 22:38:45 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA08955
          for freebsd-bugs-outgoing; Mon, 19 Oct 1998 22:38:45 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA08947;
          Mon, 19 Oct 1998 22:38:41 -0700 (PDT)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id PAA29977;
	Tue, 20 Oct 1998 15:38:12 +1000
Date: Tue, 20 Oct 1998 15:38:12 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199810200538.PAA29977@godzilla.zeta.org.au>
To: freebsd-bugs@FreeBSD.ORG, FreeBSD-gnats-submit@FreeBSD.ORG,
        robert+freebsd@cyrus.watson.org
Subject: Re: kern/8376: clock_gettime and CLOCK_VIRTUAL -- not implemented
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

>Additionally, POSIX.1b-1993 indicates that the clock_* functions and
>CLOCK_* constants should be defined in time.h, not in sys/time.h. 

So does <sys/time.h> :-].  POSIX.1b is mostly not implemented.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Mon Oct 19 22:40:07 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA09234
          for freebsd-bugs-outgoing; Mon, 19 Oct 1998 22:40:07 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA09224
          for <freebsd-bugs@FreeBSD.org>; Mon, 19 Oct 1998 22:40:05 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id WAA25388;
	Mon, 19 Oct 1998 22:40:02 -0700 (PDT)
Date: Mon, 19 Oct 1998 22:40:02 -0700 (PDT)
Message-Id: <199810200540.WAA25388@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.ORG
From: Bruce Evans <bde@zeta.org.au>
Subject: Re: kern/8376: clock_gettime and CLOCK_VIRTUAL -- not implemented
Reply-To: Bruce Evans <bde@zeta.org.au>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR kern/8376; it has been noted by GNATS.

From: Bruce Evans <bde@zeta.org.au>
To: freebsd-bugs@FreeBSD.ORG, FreeBSD-gnats-submit@FreeBSD.ORG,
        robert+freebsd@cyrus.watson.org
Cc:  Subject: Re: kern/8376: clock_gettime and CLOCK_VIRTUAL -- not implemented
Date: Tue, 20 Oct 1998 15:38:12 +1000

 >Additionally, POSIX.1b-1993 indicates that the clock_* functions and
 >CLOCK_* constants should be defined in time.h, not in sys/time.h. 
 
 So does <sys/time.h> :-].  POSIX.1b is mostly not implemented.
 
 Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Mon Oct 19 22:40:07 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA09233
          for freebsd-bugs-outgoing; Mon, 19 Oct 1998 22:40:07 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA09220
          for <freebsd-bugs@FreeBSD.org>; Mon, 19 Oct 1998 22:40:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id WAA25383;
	Mon, 19 Oct 1998 22:40:01 -0700 (PDT)
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA08665;
          Mon, 19 Oct 1998 22:34:26 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199810200534.WAA08665@hub.freebsd.org>
Date: Mon, 19 Oct 1998 22:34:26 -0700 (PDT)
From: nakaji@zeisei3.dpri.kyoto-u.ac.jp
To: freebsd-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: www-1.0
Subject: conf/8379: check_rcpt returns OK for nonexistent address
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8379
>Category:       conf
>Synopsis:       check_rcpt returns OK for nonexistent address
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Oct 19 22:40:00 PDT 1998
>Last-Modified:
>Originator:     NAKAJI Hiroyuki
>Organization:
DPRI, Kyoto University
>Release:        3.0-current
>Environment:
FreeBSD zeisei19.dpri.kyoto-u.ac.jp 3.0-CURRENT FreeBSD 3.0-CURRENT #5: Sat Oct 17 19:36:24 JST 1998     root@:/usr/src/sys/compile/PV5000  i386
>Description:
Default sendmail.cf's address rewriting is buggy. check_* rulesets must
return `error' for non-existent address.
>How-To-Repeat:
/usr/sbin/sendmail -bt
> check_rcpt nakaji@zeisei.kyoto-u.ac.jp
rewrite: ruleset 188   input: nakaji @ zeisei . kyoto-u . ac . jp
rewrite: ruleset 189   input: nakaji @ zeisei . kyoto-u . ac . jp
rewrite: ruleset 189 returns: nakaji @ zeisei . kyoto-u . ac . jp
rewrite: ruleset 187   input: nakaji @ zeisei . kyoto-u . ac . jp
rewrite: ruleset 196   input: nakaji @ zeisei . kyoto-u . ac . jp
rewrite: ruleset   3   input: nakaji @ zeisei . kyoto-u . ac . jp
rewrite: ruleset  96   input: nakaji < @ zeisei . kyoto-u . ac . jp >
rewrite: ruleset  96 returns: nakaji < @ zeisei . kyoto-u . ac . jp . dpri . kyoto-u . ac . jp . >
rewrite: ruleset   3 returns: nakaji < @ zeisei . kyoto-u . ac . jp . dpri . kyoto-u . ac . jp . >
rewrite: ruleset 199   input: nakaji < @ zeisei . kyoto-u . ac . jp . dpri . kyoto-u . ac . jp . >
rewrite: ruleset 199 returns: nakaji < @ zeisei . kyoto-u . ac . jp . dpri . kyoto-u . ac . jp . >
rewrite: ruleset 196 returns: nakaji < @ zeisei . kyoto-u . ac . jp . dpri . kyoto-u . ac . jp >
rewrite: ruleset 187 returns: OK
rewrite: ruleset 188 returns: OK

>Fix:

>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 00:30:06 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id AAA17570
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 00:30:06 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA17563
          for <freebsd-bugs@FreeBSD.org>; Tue, 20 Oct 1998 00:30:03 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id AAA00350;
	Tue, 20 Oct 1998 00:30:00 -0700 (PDT)
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id AAA16860;
          Tue, 20 Oct 1998 00:21:08 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199810200721.AAA16860@hub.freebsd.org>
Date: Tue, 20 Oct 1998 00:21:08 -0700 (PDT)
From: namgeun@cc.gatech.edu
To: freebsd-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: www-1.0
Subject: kern/8380: swap_page error: out of swap space
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8380
>Category:       kern
>Synopsis:       swap_page error: out of swap space
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Oct 20 00:30:00 PDT 1998
>Last-Modified:
>Originator:     Namgeun Jeong
>Organization:
College of Computing, Georgia Tech
>Release:        2.2.7
>Environment:
FreeBSD r49h138.res.gatech.edu 2.2.7-RELEASE FreeBSD 2.2.7-RELEASE #0: Sun Oct 18 03:24:18 EST 1998     root@r49h138.res.gatech.edu:/usr/src/sys/compile/GUREUMI  i386
>Description:
system halted while trying to update to release 3.0
>How-To-Repeat:

>Fix:

>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 01:40:07 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id BAA22863
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 01:40:07 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA22858
          for <freebsd-bugs@FreeBSD.org>; Tue, 20 Oct 1998 01:40:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id BAA02779;
	Tue, 20 Oct 1998 01:40:01 -0700 (PDT)
Date: Tue, 20 Oct 1998 01:40:01 -0700 (PDT)
Message-Id: <199810200840.BAA02779@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.ORG
From: Greg Lehey <grog@lemis.com>
Subject: Re: kern/8380: swap_page error: out of swap space
Reply-To: Greg Lehey <grog@lemis.com>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR kern/8380; it has been noted by GNATS.

From: Greg Lehey <grog@lemis.com>
To: namgeun@cc.gatech.edu, freebsd-gnats-submit@FreeBSD.ORG
Cc:  Subject: Re: kern/8380: swap_page error: out of swap space
Date: Tue, 20 Oct 1998 18:03:29 +0930

 On Tuesday, 20 October 1998 at  0:21:08 -0700, namgeun@cc.gatech.edu wrote:
 >
 >> Synopsis:       swap_page error: out of swap space
 >> Description:
 > system halted while trying to update to release 3.0
 
 This is a configuration error, not a software bug.
 
 >> Fix:
 
 Add more swap space.
 
 Greg
 --
 See complete headers for address, home page and phone numbers
 finger grog@lemis.com for PGP public key

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 03:59:15 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id DAA00768
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 03:59:15 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA00756
          for <bugs@freebsd.org>; Tue, 20 Oct 1998 03:59:09 -0700 (PDT)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id UAA23848
	for bugs@freebsd.org; Tue, 20 Oct 1998 20:58:38 +1000
Date: Tue, 20 Oct 1998 20:58:38 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199810201058.UAA23848@godzilla.zeta.org.au>
To: bugs@FreeBSD.ORG
Subject: amusing vi bug
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

After

	umask 777      # silly season
	rm -f /tmp/z
	touch /tmp/z
	vi /tmp/z

vi recurses endlessly in file_open() and files up /tmp with temporary
files until the filesysem containing /tmp runs out of indodes or some
other limit is hit.

This may have been fixed.  contrib/nvi is 8 versions out of date
(1.79 - 1.71).

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 04:01:36 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id EAA01529
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 04:01:36 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from ifi.uio.no (ifi.uio.no [129.240.64.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA01490
          for <bugs@FreeBSD.ORG>; Tue, 20 Oct 1998 04:01:24 -0700 (PDT)
          (envelope-from dag-erli@ifi.uio.no)
Received: from bilskirnir.ifi.uio.no (2602@bilskirnir.ifi.uio.no [129.240.64.135])
	by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id NAA05906;
	Tue, 20 Oct 1998 13:00:50 +0200 (MET DST)
Received: (from dag-erli@localhost) by bilskirnir.ifi.uio.no ; Tue, 20 Oct 1998 13:00:49 +0200 (MET DST)
Mime-Version: 1.0
To: "MISTY D LINVILLE" <linvilmd@daleth.grace.edu>
Cc: bugs@FreeBSD.ORG
Subject: Re: 3.0 install from DOS
References: <199810200452.XAA17688@daleth.grace.edu>
Organization: University of Oslo, Department of Informatics
X-url: http://www.stud.ifi.uio.no/~dag-erli/
X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list
X-disclaimer-1: The views expressed in this article are mine alone, and do
X-disclaimer-2: not necessarily coincide with those of any organisation or
X-disclaimer-3: company with which I am or have been affiliated.
X-Stop-Spam: http://www.cauce.org/
From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= )
Date: 20 Oct 1998 13:00:48 +0200
In-Reply-To: "MISTY D LINVILLE"'s message of "Mon, 19 Oct 1998 22:58:01 +0000"
Message-ID: <xzpzparsdjz.fsf@bilskirnir.ifi.uio.no>
Lines: 14
X-Mailer: Gnus v5.5/Emacs 19.34
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id EAA01522
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

"MISTY D LINVILLE" <linvilmd@daleth.grace.edu> writes:
> Even though I have all of the install directories in the right place 
> (under c:\freebsd), the 3.0 install floppy refuses torecognize any of 
> the distributions at install time.  I think this must be a bug.  

Could you give us some more detailed information, such as what error
message you get and a complete directory listing of c:\freebsd\ and
all its subdirectories (or at least the bin subdirectory)? It's hard
to do anything constructive when all you're told is "It doesn't work.
Fix it."

DES
-- 
Dag-Erling Smørgrav - dag-erli@ifi.uio.no

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 04:35:43 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id EAA06305
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 04:35:43 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA06285;
          Tue, 20 Oct 1998 04:35:19 -0700 (PDT)
          (envelope-from des@FreeBSD.org)
From: "Dag-Erling C. Sm\xf8rgrav" <des@FreeBSD.ORG>
Received: (from des@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id EAA10505;
	Tue, 20 Oct 1998 04:35:17 -0700 (PDT)
Date: Tue, 20 Oct 1998 04:35:17 -0700 (PDT)
Message-Id: <199810201135.EAA10505@freefall.freebsd.org>
To: ajk@purdue.edu, des@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG, des@FreeBSD.ORG
Subject: Re: bin/8353
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: vipw and chpass echo bogus error messages

State-Changed-From-To: open-closed
State-Changed-By: des
State-Changed-When: Tue Oct 20 04:34:22 PDT 1998
State-Changed-Why: 
Slightly different patch applied, thanks.


Responsible-Changed-From-To: freebsd-bugs->des
Responsible-Changed-By: des
Responsible-Changed-When: Tue Oct 20 04:34:22 PDT 1998
Responsible-Changed-Why: 
I broke it, I fixed it.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 04:50:09 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id EAA07552
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 04:50:09 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA07542
          for <freebsd-bugs@FreeBSD.org>; Tue, 20 Oct 1998 04:50:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id EAA11073;
	Tue, 20 Oct 1998 04:50:01 -0700 (PDT)
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id EAA06954;
          Tue, 20 Oct 1998 04:41:36 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199810201141.EAA06954@hub.freebsd.org>
Date: Tue, 20 Oct 1998 04:41:36 -0700 (PDT)
From: shirai@nintnedo.co.jp
To: freebsd-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: www-1.0
Subject: i386/8382: [PATCH] /stand/sysinstall don't unmount CD-ROM
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8382
>Category:       i386
>Synopsis:       [PATCH] /stand/sysinstall don't unmount CD-ROM
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Oct 20 04:50:01 PDT 1998
>Last-Modified:
>Originator:     Takashi SHIRAI
>Organization:
>Release:        2.2.6-RELEASE
>Environment:
FreeBSD chandra2 2.2.6-RELEASE FreeBSD 2.2.6-RELEASE #0: Fri Sep  4 11:48:37 JST 1998      shirai@chandra2:/usr/src/sys/compile/chandra2  i386
>Description:
In case that no item is selected in packages installation with /stand/sysinstall,
sysinstall don't unmount CD-ROM device at the end. (The other devices have no problem.)

Following is the patch.
diff -ur ../sysinstall/cdrom.c ./cdrom.c
--- ../sysinstall/cdrom.c       Wed Jan 29 10:11:22 1997
+++ ./cdrom.c   Thu Oct  1 12:26:45 1998
@@ -83,7 +83,6 @@
            msgConfirm("Error mounting %s on %s: %s (%u)", dev->devname, mountpo
int, strerror(errno), errno);
            return FALSE;
        }
-       cdromMounted = TRUE;
     }

     if (!file_readable(string_concat(mountpoint, "/cdrom.inf"))) {
@@ -122,6 +121,7 @@
        }
     }
     msgDebug("Mounted FreeBSD CDROM from device %s\n", dev->devname);
+    cdromMounted = TRUE;
     return TRUE;
 }

But, this patch is not enough.
Even if the directory /dist is already mounted by CD-ROM from the first, sysinstall will unmount /dist to exit.
I think that it's necessary to prepare the flag telling if mounted already or not.
This problem is not concernd only the CD-ROM device, but all devices.

>How-To-Repeat:
With /stand/sysinstall, select Configure -> Packages -> CDROM, and exit at once.
You will find /dist in the output of `df`.

>Fix:
The patch is effective, and you must fix not to unmount already mounted /dist.

>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 05:18:06 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id FAA09590
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 05:18:06 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA09572
          for <bugs@FreeBSD.ORG>; Tue, 20 Oct 1998 05:17:54 -0700 (PDT)
          (envelope-from peter@netplex.com.au)
Received: from spinner.netplex.com.au (localhost [127.0.0.1])
	by spinner.netplex.com.au (8.9.1/8.9.1/Spinner) with ESMTP id UAA11514;
	Tue, 20 Oct 1998 20:16:22 +0800 (WST)
	(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199810201216.UAA11514@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Bruce Evans <bde@zeta.org.au>
cc: bugs@FreeBSD.ORG
Subject: Re: amusing vi bug 
In-reply-to: Your message of "Tue, 20 Oct 1998 20:58:38 +1000."
             <199810201058.UAA23848@godzilla.zeta.org.au> 
Date: Tue, 20 Oct 1998 20:16:22 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Bruce Evans wrote:
> After
> 
> 	umask 777      # silly season
> 	rm -f /tmp/z
> 	touch /tmp/z
> 	vi /tmp/z
> 
> vi recurses endlessly in file_open() and files up /tmp with temporary
> files until the filesysem containing /tmp runs out of indodes or some
> other limit is hit.

Hmm..  mk[s]temp() bug in libc.

> This may have been fixed.  contrib/nvi is 8 versions out of date
> (1.79 - 1.71).

Eh?  ":version" reports:
Version 1.79 (10/23/96) The CSRG, University of California, Berkeley.

> Bruce

Cheers,
-Peter



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 06:03:37 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA13161
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 06:03:37 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA13155
          for <bugs@FreeBSD.ORG>; Tue, 20 Oct 1998 06:03:34 -0700 (PDT)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id XAA01071;
	Tue, 20 Oct 1998 23:03:05 +1000
Date: Tue, 20 Oct 1998 23:03:05 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199810201303.XAA01071@godzilla.zeta.org.au>
To: bde@zeta.org.au, peter@netplex.com.au
Subject: Re: amusing vi bug
Cc: bugs@FreeBSD.ORG
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

>> 	umask 777      # silly season
>> 	rm -f /tmp/z
>> 	touch /tmp/z
>> 	vi /tmp/z
>> 
>> vi recurses endlessly in file_open() and files up /tmp with temporary
>> files until the filesysem containing /tmp runs out of indodes or some
>> other limit is hit.
>
>Hmm..  mk[s]temp() bug in libc.

There seems to be only a documentation bug for this in libc.  mkstemp()
honours the umask, but the man page doesn't mention this.  glibc-2.0.5c's
mkstemp() is similar except it opens the file with mode 0666 instead of
mode 0600.

BTW, I've also seen the tmp file left undeleted in normal operation, and
lots of tmp files left undeleted by (mostly remote?) cvs.

>> This may have been fixed.  contrib/nvi is 8 versions out of date
>> (1.79 - 1.71).
>
>Eh?  ":version" reports:
>Version 1.79 (10/23/96) The CSRG, University of California, Berkeley.

Oops.  The README says 1.71.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 09:00:12 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA00455
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 09:00:12 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA00406
          for <freebsd-bugs@FreeBSD.org>; Tue, 20 Oct 1998 09:00:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id JAA26115;
	Tue, 20 Oct 1998 09:00:00 -0700 (PDT)
Received: from europe.std.com (europe.std.com [199.172.62.20])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA29984
          for <FreeBSD-gnats-submit@freebsd.org>; Tue, 20 Oct 1998 08:58:44 -0700 (PDT)
          (envelope-from cmascott@world.std.com)
Received: from world.std.com by europe.std.com (8.7.6/BZS-8-1.0)
	id LAA16024; Tue, 20 Oct 1998 11:58:07 -0400 (EDT)
Received: from europa.local (world-f.std.com) by world.std.com (TheWorld/Spike-2.0)
	id AA26429; Tue, 20 Oct 1998 11:58:01 -0400
Received: (from cmascott@localhost)
	by europa.local (8.8.8/8.8.8) id LAA00522;
	Tue, 20 Oct 1998 11:57:27 -0400 (EDT)
	(envelope-from cmascott)
Message-Id: <199810201557.LAA00522@europa.local>
Date: Tue, 20 Oct 1998 11:57:27 -0400 (EDT)
From: cmascott@world.std.com
Reply-To: cmascott@world.std.com
To: FreeBSD-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: 3.2
Subject: kern/8383: msdosfs wipes out NT VFAT lower case flags
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8383
>Category:       kern
>Synopsis:       msdosfs wipes out NT VFAT lower case flags
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Oct 20 09:00:00 PDT 1998
>Last-Modified:
>Originator:     Carl Mascott
>Organization:
>Release:        FreeBSD 2.2.7-RELEASE i386
>Environment:

FreeBSD europa.local 2.2.7-RELEASE FreeBSD 2.2.7-RELEASE #0: Mon Aug 24 20:48:25 EDT 1998     cmascott@europa.local:/usr/src/sys/compile/EUR980824  i386

>Description:

The accompanying patch fixes the following three bugs in msdosfs:

1. When msdosfs updates an NT VFAT DOS (short name) directory entry
   it unconditionally clears the lower case flags (in the byte
   immediately following the file attributes).  Thus all NT VFAT
   files with short names when accessed by msdosfs have their NT
   names converted to upper case.

2. msdosfs does not use the NT VFAT lower case flags when converting
   a short name from DOS to UNIX (with -l in effect).  Thus files
   that have short lower case names on NT get upper case names on UNIX.

3. msdosfs updates access times even if the filesystem is mounted
   with "noatime".

Problems #1 and #2 occur because msdosfs is unaware of the
presence of the NT VFAT lower case flags in the directory entry.

NOTE: The Windows 9x VFAT implementation does not use or recognize
      the NT VFAT lower case flags.  Thus it would not be a good
      idea to modify msdosfs to use these flags when creating a
      short lower case filename.

>How-To-Repeat:

Mount an NT VFAT filesystem with -l.
Copy a file with a short lower case (on NT) name.

>Fix:
	
Apply this patch.

--------------------------- (cut here) ------------------------------
*** sys/msdosfs/msdosfs_vnops.c.orig	Wed Jul 15 22:01:44 1998
--- sys/msdosfs/msdosfs_vnops.c	Tue Oct 13 11:59:43 1998
***************
*** 200,205 ****
--- 200,206 ----
  
  	ndirent.de_Attributes = (ap->a_vap->va_mode & VWRITE) ?
  				ATTR_ARCHIVE : ATTR_ARCHIVE | ATTR_READONLY;
+ 	ndirent.de_LowerCase = 0;
  	ndirent.de_StartCluster = 0;
  	ndirent.de_FileSize = 0;
  	ndirent.de_dev = pdep->de_dev;
***************
*** 847,853 ****
  			return (error);
  		}
  		error = uiomove(bp->b_data + on, (int) n, uio);
! 		if (!isadir)
  			dep->de_flag |= DE_ACCESS;
  		brelse(bp);
  	} while (error == 0 && uio->uio_resid > 0 && n != 0);
--- 848,854 ----
  			return (error);
  		}
  		error = uiomove(bp->b_data + on, (int) n, uio);
! 		if (!isadir && !(vp->v_mount->mnt_flag & MNT_NOATIME))
  			dep->de_flag |= DE_ACCESS;
  		brelse(bp);
  	} while (error == 0 && uio->uio_resid > 0 && n != 0);
***************
*** 1715,1720 ****
--- 1716,1722 ----
  		goto bad;
  
  	ndirent.de_Attributes = ATTR_DIRECTORY;
+ 	ndirent.de_LowerCase = 0;
  	ndirent.de_StartCluster = newcluster;
  	ndirent.de_FileSize = 0;
  	ndirent.de_dev = pdep->de_dev;
***************
*** 2050,2055 ****
--- 2052,2058 ----
  				dirbuf.d_namlen = dos2unixfn(dentp->deName,
  				    (u_char *)dirbuf.d_name,
  				    pmp->pm_flags & MSDOSFSMNT_SHORTNAME,
+ 				    dentp->deLowerCase[0],
  				    pmp->pm_flags & MSDOSFSMNT_U2WTABLE,
  				    pmp->pm_d2u,
  				    pmp->pm_flags & MSDOSFSMNT_ULTABLE,
*** sys/msdosfs/direntry.h.orig	Wed Jul 15 22:01:41 1998
--- sys/msdosfs/direntry.h	Tue Oct 13 12:04:49 1998
***************
*** 65,71 ****
  #define	ATTR_VOLUME	0x08		/* entry is a volume label */
  #define	ATTR_DIRECTORY	0x10		/* entry is a directory name */
  #define	ATTR_ARCHIVE	0x20		/* file is new or modified */
! 	u_int8_t	deReserved[1];	/* reserved */
  	u_int8_t	deCHundredth;	/* hundredth of seconds in CTime */
  	u_int8_t	deCTime[2];	/* create time */
  	u_int8_t	deCDate[2];	/* create date */
--- 65,73 ----
  #define	ATTR_VOLUME	0x08		/* entry is a volume label */
  #define	ATTR_DIRECTORY	0x10		/* entry is a directory name */
  #define	ATTR_ARCHIVE	0x20		/* file is new or modified */
! 	u_int8_t	deLowerCase[1];	/* NT VFAT lower case flags */
! #define LCASE_BASE	0x08		/* filename base is lower case */
! #define LCASE_EXT	0x10		/* filename extension is lower case */
  	u_int8_t	deCHundredth;	/* hundredth of seconds in CTime */
  	u_int8_t	deCTime[2];	/* create time */
  	u_int8_t	deCDate[2];	/* create date */
***************
*** 130,136 ****
  void unix2dostime __P((struct timespec *tsp, u_int16_t *ddp, 
  	     u_int16_t *dtp, u_int8_t *dhp));
  void dos2unixtime __P((u_int dd, u_int dt, u_int dh, struct timespec *tsp));
! int dos2unixfn __P((u_char dn[11], u_char *un, int lower, int d2u_loaded, u_int8_t *d2u, int ul_loaded, u_int8_t *ul));
  int unix2dosfn __P((const u_char *un, u_char dn[12], int unlen, u_int gen, int u2d_loaded, u_int8_t *u2d, int lu_loaded, u_int8_t *lu));
  int unix2winfn __P((const u_char *un, int unlen, struct winentry *wep, int cnt, int chksum, int table_loaded, u_int16_t *u2w));
  int winChkName __P((const u_char *un, int unlen, struct winentry *wep, int chksum, int u2w_loaded, u_int16_t *u2w, int ul_loaded, u_int8_t *ul));
--- 132,138 ----
  void unix2dostime __P((struct timespec *tsp, u_int16_t *ddp, 
  	     u_int16_t *dtp, u_int8_t *dhp));
  void dos2unixtime __P((u_int dd, u_int dt, u_int dh, struct timespec *tsp));
! int dos2unixfn __P((u_char dn[11], u_char *un, int shortname, unsigned lcflags, int d2u_loaded, u_int8_t *d2u, int ul_loaded, u_int8_t *ul));
  int unix2dosfn __P((const u_char *un, u_char dn[12], int unlen, u_int gen, int u2d_loaded, u_int8_t *u2d, int lu_loaded, u_int8_t *lu));
  int unix2winfn __P((const u_char *un, int unlen, struct winentry *wep, int cnt, int chksum, int table_loaded, u_int16_t *u2w));
  int winChkName __P((const u_char *un, int unlen, struct winentry *wep, int chksum, int u2w_loaded, u_int16_t *u2w, int ul_loaded, u_int8_t *ul));
*** sys/msdosfs/denode.h.orig	Wed Jul 15 22:01:41 1998
--- sys/msdosfs/denode.h	Sun Oct 11 18:21:59 1998
***************
*** 156,161 ****
--- 156,162 ----
  #endif
  	u_char de_Name[12];	/* name, from DOS directory entry */
  	u_char de_Attributes;	/* attributes, from directory entry */
+ 	u_char de_LowerCase;	/* NT VFAT lower case flags */
  	u_char de_CHun;		/* Hundredth of second of CTime*/
  	u_short de_CTime;	/* creation time */
  	u_short de_CDate;	/* creation date */
***************
*** 196,201 ****
--- 197,203 ----
  #define DE_INTERNALIZE(dep, dp)				\
  	(bcopy((dp)->deName, (dep)->de_Name, 11),	\
  	 (dep)->de_Attributes = (dp)->deAttributes,	\
+ 	 (dep)->de_LowerCase = (dp)->deLowerCase[0],	\
  	 (dep)->de_CHun = (dp)->deCHundredth,		\
  	 (dep)->de_CTime = getushort((dp)->deCTime),	\
  	 (dep)->de_CDate = getushort((dp)->deCDate),	\
***************
*** 210,217 ****
  	 putushort((dp)->deHighClust, (dep)->de_StartCluster >> 16)
  #define DE_EXTERNALIZE(dp, dep)				\
  	(bcopy((dep)->de_Name, (dp)->deName, 11),	\
! 	 bzero((dp)->deReserved, 10),                   \
  	 (dp)->deAttributes = (dep)->de_Attributes,	\
  	 (dp)->deCHundredth = (dep)->de_CHun,		\
  	 putushort((dp)->deCTime, (dep)->de_CTime),	\
  	 putushort((dp)->deCDate, (dep)->de_CDate),	\
--- 212,220 ----
  	 putushort((dp)->deHighClust, (dep)->de_StartCluster >> 16)
  #define DE_EXTERNALIZE(dp, dep)				\
  	(bcopy((dep)->de_Name, (dp)->deName, 11),	\
! 	 bzero((dp)->deLowerCase, 10),                  \
  	 (dp)->deAttributes = (dep)->de_Attributes,	\
+ 	 (dp)->deLowerCase[0] = (dep)->de_LowerCase,	\
  	 (dp)->deCHundredth = (dep)->de_CHun,		\
  	 putushort((dp)->deCTime, (dep)->de_CTime),	\
  	 putushort((dp)->deCDate, (dep)->de_CDate),	\
*** sys/msdosfs/msdosfs_denode.c.orig	Wed Jul 15 22:01:42 1998
--- sys/msdosfs/msdosfs_denode.c	Sun Oct 11 18:13:55 1998
***************
*** 324,329 ****
--- 324,330 ----
  		nvp->v_flag |= VROOT; /* should be further down		XXX */
  
  		ldep->de_Attributes = ATTR_DIRECTORY;
+ 		ldep->de_LowerCase = 0;
  		if (FAT32(pmp))
  			ldep->de_StartCluster = pmp->pm_rootdirblk;
  			/* de_FileSize will be filled in further down */
*** sys/msdosfs/msdosfs_conv.c.orig	Wed Jul 15 22:01:42 1998
--- sys/msdosfs/msdosfs_conv.c	Tue Oct 13 11:57:22 1998
***************
*** 394,412 ****
   * null.
   */
  int
! dos2unixfn(dn, un, lower, d2u_loaded, d2u, ul_loaded, ul)
  	u_char dn[11];
  	u_char *un;
! 	int lower;
  	int d2u_loaded;
  	u_int8_t *d2u;
  	int ul_loaded;
  	u_int8_t *ul;
  {
  	int i;
  	int thislong = 1;
  	u_char c;
  
  	/*
  	 * If first char of the filename is SLOT_E5 (0x05), then the real
  	 * first char of the filename should be 0xe5. But, they couldn't
--- 394,416 ----
   * null.
   */
  int
! dos2unixfn(dn, un, shortname, lcflags, d2u_loaded, d2u, ul_loaded, ul)
  	u_char dn[11];
  	u_char *un;
! 	int shortname;
! 	unsigned lcflags;
  	int d2u_loaded;
  	u_int8_t *d2u;
  	int ul_loaded;
  	u_int8_t *ul;
  {
  	int i;
+ 	int lower;
  	int thislong = 1;
  	u_char c;
  
+ 	lower = shortname || (lcflags & LCASE_BASE);
+ 
  	/*
  	 * If first char of the filename is SLOT_E5 (0x05), then the real
  	 * first char of the filename should be 0xe5. But, they couldn't
***************
*** 440,445 ****
--- 444,450 ----
  	 * the extension.
  	 */
  	if (*dn != ' ') {
+ 		lower = shortname || (lcflags & LCASE_EXT);
  		*un++ = '.';
  		thislong++;
  		for (i = 0; i < 3 && *dn != ' '; i++) {
--------------------------- (cut here) ------------------------------
>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 09:10:07 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA01637
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 09:10:07 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA01629
          for <freebsd-bugs@FreeBSD.org>; Tue, 20 Oct 1998 09:10:03 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id JAA26720;
	Tue, 20 Oct 1998 09:10:00 -0700 (PDT)
Received: from david.siemens.de (david.siemens.de [192.35.17.14])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA00601
          for <FreeBSD-gnats-submit@freebsd.org>; Tue, 20 Oct 1998 09:00:57 -0700 (PDT)
          (envelope-from udo.schweigert@mchp.siemens.de)
Received: from mail.siemens.de (salomon.siemens.de [139.23.33.13])
	by david.siemens.de (8.9.1a/8.9.1) with ESMTP id SAA14810
	for <FreeBSD-gnats-submit@freebsd.org>; Tue, 20 Oct 1998 18:00:25 +0200 (MET DST)
Received: from reims.mchp.siemens.de (reims.mchp.siemens.de [139.23.202.134])
	by mail.siemens.de (8.9.1a/8.9.1) with ESMTP id SAA07769
	for <FreeBSD-gnats-submit@freebsd.org>; Tue, 20 Oct 1998 18:00:27 +0200 (MET DST)
Received: (from ust@localhost)
	by reims.mchp.siemens.de (8.8.8/8.8.8) id QAA00691;
	Tue, 20 Oct 1998 16:00:23 GMT
	(envelope-from ust)
Message-Id: <199810201600.QAA00691@reims.mchp.siemens.de>
Date: Tue, 20 Oct 1998 16:00:23 GMT
From: Udo.Schweigert@mchp.siemens.de
Reply-To: Udo.Schweigert@mchp.siemens.de
To: FreeBSD-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: 3.2
Subject: kern/8384: Problem with xl network driver (3c9xx cards)
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8384
>Category:       kern
>Synopsis:       Problem with xl network driver (3c9xx cards)
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Oct 20 09:10:00 PDT 1998
>Last-Modified:
>Originator:     Udo Schweigert
>Organization:
Siemens CERT, Siemens AG, ZT IK 3
>Release:        FreeBSD 2.2.7-STABLE i386
>Environment:
FreeBSD 2.2.7-STABLE cvsuped 20/10/98
>Description:
The xl driver for the 3c9xx cards generates the following error messages on 
the console (and into /var/adm/messages) when trying to do a rcp or 
while performing NFS:

Oct 20 13:21:54 reims /kernel: xl0: transmission error: 90

>How-To-Repeat:

e.g.: rcp file machine:.

>Fix:
	
 Changing /usr/src/sys/pci/if_xl.c from revision 1.5.2.10 to 1.5.2.9
 and      /usr/src/sys/pci/if_xlreg.h from 1.3.2.5 to 1.3.2.4 

 fixed it for me.
>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 09:28:14 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA03902
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 09:28:14 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from ns.prisma-presse.com (ns.prisma-presse.com [195.25.46.33])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03853
          for <freebsd-bugs@FreeBSD.ORG>; Tue, 20 Oct 1998 09:28:06 -0700 (PDT)
          (envelope-from mstutzmann@prisma-presse.com)
Received: from mstutz.oleane.net (dialup-196.def.oleane.com [195.25.5.196])
          by ns.prisma-presse.com (8.8.4/8.8.4) with ESMTP
	  id SAA03085 for <freebsd-bugs@FreeBSD.ORG>; Tue, 20 Oct 1998 18:19:17 +0200 (MET DST)
Message-Id: <199810201619.SAA03085@ns.prisma-presse.com>
From: "Marc Stutzmann" <mstutzmann@prisma-presse.com>
To: <freebsd-bugs@FreeBSD.ORG>
Subject: Y2K compliance of FreeBSD
Date: Tue, 20 Oct 1998 17:41:33 +0200
X-MSMail-Priority: Normal
X-Priority: 3
X-Mailer: Microsoft Internet Mail 4.70.1155
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01BDFC50.E0D23E20"
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Ceci est un message avec plusieurs parties au format MIME.


------=_NextPart_000_01BDFC50.E0D23E20
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

Do you have a document telling answering thequestion : "up to which version
FreeBSD is Y2K compliant ?" ?
In our company, we have the following releases of FreeBSD : 2.1.6, 2.2.1,
2.2.5.
I am looking forward for your reply.

Sincerely,

--------------------------
Marc Stutzmann
Y2K Project Manager
Prisma Presse
6 Rue Daru
75379 PARIS CEDEX 08
Tél : (33) 1 44 15 32 10
Fax : (33) 1 44 15 33 89
email : mstutzmann@prisma-presse.com
--------------------------
------=_NextPart_000_01BDFC50.E0D23E20
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<html><head></head><BODY bgcolor=3D"#FFFFFF"><p><font size=3D2 =
color=3D"#000000" face=3D"Arial">Do you have a document telling =
answering thequestion : &quot;up to which version FreeBSD is Y2K =
compliant ?&quot; ?<br>In our company, we have the following releases of =
FreeBSD : 2.1.6, 2.2.1, 2.2.5.<br>I am looking forward for your =
reply.<br><br>Sincerely,<br><br>--------------------------<br>Marc =
Stutzmann<br>Y2K Project Manager<br>Prisma Presse<br>6 Rue Daru<br>75379 =
PARIS CEDEX 08<br>T=E9l : (33) 1 44 15 32 10<br>Fax : (33) 1 44 15 33 =
89<br>email : =
mstutzmann@prisma-presse.com<br>--------------------------</p>
</font></body></html>
------=_NextPart_000_01BDFC50.E0D23E20--


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 09:41:32 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA05886
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 09:41:32 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from smtp.enteract.com (thor.enteract.com [207.229.143.11])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA05865
          for <freebsd-bugs@FreeBSD.ORG>; Tue, 20 Oct 1998 09:41:28 -0700 (PDT)
          (envelope-from jrs@enteract.com)
Received: (qmail 5741 invoked from network); 20 Oct 1998 16:41:02 -0000
Received: from adam.enteract.com (jrs@206.54.252.1)
  by thor.enteract.com with SMTP; 20 Oct 1998 16:41:02 -0000
Date: Tue, 20 Oct 1998 11:41:02 -0500 (CDT)
From: John Sconiers <jrs@enteract.com>
To: Marc Stutzmann <mstutzmann@prisma-presse.com>
cc: freebsd-bugs@FreeBSD.ORG
Subject: Re: Y2K compliance of FreeBSD
In-Reply-To: <199810201619.SAA03085@ns.prisma-presse.com>
Message-ID: <Pine.BSF.3.96.981020114030.536B-100000@adam.enteract.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Transfer-Encoding: 8BIT
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Tue, 20 Oct 1998, Marc Stutzmann wrote:
> Do you have a document telling answering thequestion : "up to which version
> FreeBSD is Y2K compliant ?" ?
> In our company, we have the following releases of FreeBSD : 2.1.6, 2.2.1,
> 2.2.5.
> I am looking forward for your reply.

http://www.freebsd.org/y2kbug.html


> Sincerely,
> 
> --------------------------
> Marc Stutzmann
> Y2K Project Manager
> Prisma Presse
> 6 Rue Daru
> 75379 PARIS CEDEX 08
> Tél : (33) 1 44 15 32 10
> Fax : (33) 1 44 15 33 89
> email : mstutzmann@prisma-presse.com
> --------------------------


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 10:10:06 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA09102
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 10:10:06 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA09094
          for <freebsd-bugs@FreeBSD.org>; Tue, 20 Oct 1998 10:10:03 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id KAA29475;
	Tue, 20 Oct 1998 10:10:00 -0700 (PDT)
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA08698;
          Tue, 20 Oct 1998 10:04:04 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199810201704.KAA08698@hub.freebsd.org>
Date: Tue, 20 Oct 1998 10:04:04 -0700 (PDT)
From: lamer_number_one@hotmail.com
To: freebsd-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: www-1.0
Subject: i386/8385: 2.2.7 hangs while detecting type of COM1's UART on TX-97E motherboard
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8385
>Category:       i386
>Synopsis:       2.2.7 hangs while detecting type of COM1's UART on TX-97E motherboard
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Oct 20 10:10:00 PDT 1998
>Last-Modified:
>Originator:     Yuric
>Organization:
Home network
>Release:        2.2.7
>Environment:
>Description:
If I choose in UserConfig communications device for COM1 (port 0x3F8, irq 4), os hangs while trying to detect type of UART.
Type of second port detected correctly - 16550A (of cource, if first is disabled in UserConfig). UARTs are the same. I tried to
swap ports in BIOS, i.e. real com2 have port 0x3F8, irq 4, and com1 was set up as 0x2F8, irq 3 - system hangs again on the
real com1 (or second for system).
My com1 works! I have Genius mouse 3 attached to it (of cource, I tried to unplug it) and it work perfectly under dos & winnt.

>How-To-Repeat:
Find comp with the TX97-E motherboard and try to install 2.2.7-release (sorry for cheek-like phraze)
Choose serial ports in hardware configuration and go.
>Fix:
Unfortunately, I don't know how to fix it.
>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 10:20:08 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA09818
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 10:20:08 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA09809
          for <freebsd-bugs@FreeBSD.org>; Tue, 20 Oct 1998 10:20:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id KAA29745;
	Tue, 20 Oct 1998 10:20:00 -0700 (PDT)
Received: from eubie.lbl.gov (eubie.lbl.gov [131.243.2.36])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA09524
          for <FreeBSD-gnats-submit@freebsd.org>; Tue, 20 Oct 1998 10:15:32 -0700 (PDT)
          (envelope-from jin@eubie.lbl.gov)
Received: (from jin@localhost)
	by eubie.lbl.gov (8.9.1/8.9.1) id KAA00422;
	Tue, 20 Oct 1998 10:15:06 -0700 (PDT)
	(envelope-from jin)
Message-Id: <199810201715.KAA00422@eubie.lbl.gov>
Date: Tue, 20 Oct 1998 10:15:06 -0700 (PDT)
From: Jin Guojun (FTG staff) <jin@eubie.lbl.gov>
Reply-To: jin@eubie.lbl.gov
To: FreeBSD-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: 3.2
Subject: kern/8386: modload failure
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8386
>Category:       kern
>Synopsis:       modload failure
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Oct 20 10:20:00 PDT 1998
>Last-Modified:
>Originator:     Jin Guojun (FTG staff)
>Organization:
>Release:        FreeBSD 3.0-19981015-BETA i386
>Environment:

	currently test under 3.0-19981015-BETA, last one prior to
	3.0-RELEASE

>Description:

	code segment in modload.c

        /*
         * Transfer the relinked module to kernel memory in chunks of
         * MODIOBUF size at a time.
         */
        for (bytesleft = info_buf.a_text + info_buf.a_data;
            bytesleft > 0;
            bytesleft -= sz) {
                sz = min(bytesleft, MODIOBUF);
                read(modfd, buf, sz);
                ldbuf.cnt = sz;
                ldbuf.data = buf;
                if (ioctl(devfd, LMLOADBUF, &ldbuf) == -1)
                        err(11, "error transferring buffer");
        }
 
        /*
         * Save ourselves before disaster (potentitally) strikes...
         */
        sync();
 
        /*
         * Trigger the module as loaded by calling the entry procedure;
         * this will do all necessary table fixup to ensure that state
         * is maintained on success, or blow everything back to ground
         * zero on failure.
         */
        if (ioctl(devfd, LMREADY, &modentry) == -1)	/* failed HERE	*/
                err(14, "error initializing module");	/* exited HERE	*/
 

DEBUG output from kern_lkm.c

... (repeating lines omitted)
LKM: LMLOADBUF (loading @ 285184 of 329868, i = 512) 2
LKM: LMLOADBUF (loading @ 285696 of 329868, i = 512) 2
LKM: LMLOADBUF (loading @ 286208 of 329868, i = 512) 2
lkm_state is 00
LKM: LMUNRESERV

------------

	As we see LMLOADBUF is lkm_state=2, and the "for loop " for the
	ioctl(devfd, LMLOADBUF, &ldbuf) was successfully finished.
	After sync(), somehow, lkm_state became 00 which causes kern_lkm
	return ENXIO (Device not configured) and let modload exit at
	the last two line printed above.
	There is no other code between these two segments except sync().
	Could sync() zeros out the local variable "lkm_state"?
	What could happen here?


>How-To-Repeat:

	compile kernel with "make DEBUG=-D_DEBUG" or modified Makefile
	to add DEBUG=-DDEBUG line, then install the kernel and reboot.
	Testing modload anything to see the output.

>Fix:
	
	

>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 10:30:05 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA10612
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 10:30:05 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10593
          for <freebsd-bugs@FreeBSD.org>; Tue, 20 Oct 1998 10:30:03 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id KAA29972;
	Tue, 20 Oct 1998 10:30:01 -0700 (PDT)
Date: Tue, 20 Oct 1998 10:30:01 -0700 (PDT)
Message-Id: <199810201730.KAA29972@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.ORG
From: Bruce Evans <bde@zeta.org.au>
Subject: Re: kern/8324: failure to deliver SIGIO when fildes marked for async i/o
Reply-To: Bruce Evans <bde@zeta.org.au>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR kern/8324; it has been noted by GNATS.

From: Bruce Evans <bde@zeta.org.au>
To: archie@whistle.com
Cc:  Subject: Re: kern/8324: failure to deliver SIGIO when fildes marked for async i/o
Date: Thu, 15 Oct 1998 17:52:43 +1000

 >>Description:
 >
 >	Run the program below. It will periodically hang until
 >	you press return (which causes a readability condition).
 >	It should (as far as I can tell) generate continuous
 >	output without pausing at all.
 
 The program seems to only make sense for ttys (fcntl returns a value
 which is always ignored...) and seems to only hang for ptys.  It hangs
 because wakeups for output-wouldn't block are only sent to processes
 in the kernel - for output there are only select-style wakeups, not
 SIGIO wakeups.  The select-style wakeups are poorly implemented too -
 processes gets woken up whenever the space in the output buffer increases,
 and then usually go back to sleep until the space reaches a watermark.
 
 While debugging this, I was reminded of other problems: the O_NONBLOCK
 and O_ASYNC flags are sticky, and syscons is not reentrant - a breakpoint
 in ttwakeup() soon caused a panic.
 
 Bruce
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 10:30:07 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA10632
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 10:30:07 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10605
          for <freebsd-bugs@FreeBSD.org>; Tue, 20 Oct 1998 10:30:05 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id KAA29990;
	Tue, 20 Oct 1998 10:30:02 -0700 (PDT)
Received: from mail.baileynm.com (fw.baileynm.com [206.109.159.11])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA10375
          for <FreeBSD-gnats-submit@freebsd.org>; Tue, 20 Oct 1998 10:27:51 -0700 (PDT)
          (envelope-from peter@pobox.eng.baileynm.com)
Received: (qmail 22329 invoked from network); 20 Oct 1998 17:27:24 -0000
Received: from pobox.eng.baileynm.com (198.178.0.191)
  by fw.nmti.com with SMTP; 20 Oct 1998 17:27:24 -0000
Received: (from root@localhost)
	by pobox.eng.baileynm.com (8.8.7/8.8.7) id MAA06981;
	Tue, 20 Oct 1998 12:27:24 -0500 (CDT)
	(envelope-from peter)
Message-Id: <199810201727.MAA06981@pobox.eng.baileynm.com>
Date: Tue, 20 Oct 1998 12:27:24 -0500 (CDT)
From: peter@baileynm.com
Reply-To: peter@baileynm.com
To: FreeBSD-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: 3.2
Subject: misc/8388: Windows DUN sends DOMAINusername, ppp is unhappy.
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8388
>Category:       misc
>Synopsis:       Windows DUN sends DOMAIN\username, ppp is unhappy.
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Tue Oct 20 10:30:01 PDT 1998
>Last-Modified:
>Originator:     Peter da Silva
>Organization:
Bailey Network Management
>Release:        FreeBSD 2.2.5-RELEASE i386
>Environment:

	FreeBSD box as dial-in server with ppp and Windows users.

>Description:

	Users forget to take out "DOMAIN" in DUN dialog box when switching
	between NT and BSD dial-in servers. Dialin fails. Users assume it's
	because FreeBSD is a POS and whine about using NT instead. Sysadmin
	fixes problem instead of whining on IRC. Nobody dies.

>How-To-Repeat:

	Dial-in with DOMAIN in DUN dialog box.

>Fix:
	
	If getpwnam fails in pap.c, then call it again with remainder of
	username (pap.c, about line 125) :

     result = (pwd = getpwnam(name)) &&
              !strcmp(crypt(key, pwd->pw_passwd), pwd->pw_passwd);
+    if(!result) {
+        if(!pwd) { /* disgusting hack to avoid complaints about domain auth */
+                char *s;
+                if(s=strchr(name, '\\')) {
+                    result = (pwd = getpwnam(s+1)) &&
+                     !strcmp(crypt(key, pwd->pw_passwd), pwd->pw_passwd);
+                }
+                if(!pwd)
+                        LogPrintf(LogLCP, "No such user?\n");
+        }
+    }
     endpwent();


>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 12:30:08 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA22990
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 12:30:08 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA22981
          for <freebsd-bugs@FreeBSD.org>; Tue, 20 Oct 1998 12:30:06 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id MAA03909;
	Tue, 20 Oct 1998 12:30:00 -0700 (PDT)
Date: Tue, 20 Oct 1998 12:30:00 -0700 (PDT)
Message-Id: <199810201930.MAA03909@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.ORG
From: Jin Guojun (FTG staff) <jin@george.lbl.gov>
Subject: Re: kern/8386: modload failure
Reply-To: Jin Guojun (FTG staff) <jin@george.lbl.gov>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR kern/8386; it has been noted by GNATS.

From: Jin Guojun (FTG staff) <jin@george.lbl.gov>
To: FreeBSD-gnats-submit@FreeBSD.ORG
Cc:  Subject: Re: kern/8386: modload failure
Date: Tue, 20 Oct 1998 12:26:52 -0700 (PDT)

 >       currently test under 3.0-19981015-BETA, last one prior to
 >       3.0-RELEASE
 
 The new 3.0-RELEASE does the samething.
 
 > DEBUG output from kern_lkm.c
 >  
 > ... (repeating lines omitted)
 > LKM: LMLOADBUF (loading @ 285184 of 329868, i = 512) 2
 > LKM: LMLOADBUF (loading @ 285696 of 329868, i = 512) 2
 > LKM: LMLOADBUF (loading @ 286208 of 329868, i = 512) 2
 > lkm_state is 00
 > LKM: LMUNRESERV
 
 In 2.2.7-RELEASE, the output looks like following:
 
 ... (repeating lines omitted)
 LKM: LMLOADBUF (loading @ 207360 of 251884, i = 512)
 LKM: LMLOADBUF (loading @ 207872 of 251884, i = 512)
 LKM: LMLOADBUF (loading @ 208384 of 251884, i = 512)
 znatm0 <Zeitnet PCI ATM 0001> rev 10 int a irq 9 on pci0:13:0
 ZAALGlobInit sb_modifhandler name ZNI,ZATMSB155
 ZS10MsgHandler: Entry efbffc6c 1
 ZAALGlobInit sb_modifhandler name ZNI,ZATMSB
 ZS10MsgHandler: Entry efbffc6c 1
 ZAALGlobInit sb_modifhandler name ZATMSBUS
 ZS10MsgHandler: Entry efbffc6c 1
 ZS10MsgHandler: Entry efbffc54 3
 ZeitNet : Version 3.0(1.22) 
 ATM: Loss of frame detected on Link 0
 ATM: Driver For OC3-MultiModeFiber Successfully Initialized
 ZS10MsgHandler: Entry efbffbd4 5
 ZS10MsgHandler: Entry efbffa58 5
 ZATM domain added
 LKM: LMREADY
 
 	-Jin

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 13:27:45 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA29063
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 13:27:45 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA29053
          for <bugs@freebsd.org>; Tue, 20 Oct 1998 13:27:42 -0700 (PDT)
          (envelope-from brett@lariat.org)
Received: (from brett@localhost)
	by lariat.lariat.org (8.8.8/8.8.6) id OAA05955;
	Tue, 20 Oct 1998 14:27:14 -0600 (MDT)
Message-Id: <4.1.19981020142239.06c13d50@mail.lariat.org>
X-Sender: brett@mail.lariat.org
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Tue, 20 Oct 1998 14:23:27 -0600
To: bugs@FreeBSD.ORG
From: Brett Glass <brett@lariat.org>
Subject: No terminal echo after certain commands
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

After executing certain shell commands in FreeBSD's csh (especially ones
involving "more"), I sometimes find that characters don't echo. This most
frequently occurs when I ^C out of something that's scrolling text through
more, but also occurs at other times.

To get the system to echo what I type, I have to use the command "tset
<whatever>".

This problem occurs both at the main system console (I'm not using VT100
emulation; just plain old cons25) and during telnet sessions.

The systems on which I've seen this problem range from 2.1.5 to 2.2.7-RELEASE.

Have others seen this? Is there a fix?

--Brett 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 14:45:39 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA07378
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 14:45:39 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07365
          for <bugs@FreeBSD.ORG>; Tue, 20 Oct 1998 14:45:37 -0700 (PDT)
          (envelope-from Studded@gorean.org)
Received: from gorean.org (Studded@localhost [127.0.0.1])
	by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id OAA05242;
	Tue, 20 Oct 1998 14:44:59 -0700 (PDT)
	(envelope-from Studded@gorean.org)
Message-ID: <362D045A.576B783A@gorean.org>
Date: Tue, 20 Oct 1998 14:44:58 -0700
From: Studded <Studded@gorean.org>
Organization: Triborough Bridge & Tunnel Authority
X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 2.2.7-STABLE-1015 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Brett Glass <brett@lariat.org>
CC: bugs@FreeBSD.ORG
Subject: Re: No terminal echo after certain commands
References: <4.1.19981020142239.06c13d50@mail.lariat.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Brett Glass wrote:
> 
> After executing certain shell commands in FreeBSD's csh (especially ones
> involving "more"), I sometimes find that characters don't echo. This most
> frequently occurs when I ^C out of something that's scrolling text through
> more, but also occurs at other times.

	"Doctor, it hurts when I do this." "So, don't do that." :) Try reading
the man page for 'more' to see what the proper way to exit out of it is
and you will avoid this problem. 

Good luck,

Doug
-- 
***           Chief Operations Officer, DALnet IRC network          ***

    Go PADRES!

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 14:55:23 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA08258
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 14:55:23 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08253
          for <bugs@FreeBSD.ORG>; Tue, 20 Oct 1998 14:55:21 -0700 (PDT)
          (envelope-from brett@lariat.org)
Received: (from brett@localhost)
	by lariat.lariat.org (8.8.8/8.8.6) id PAA06858;
	Tue, 20 Oct 1998 15:54:51 -0600 (MDT)
Message-Id: <4.1.19981020155224.06d3cab0@mail.lariat.org>
X-Sender: brett@mail.lariat.org
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Tue, 20 Oct 1998 15:53:13 -0600
To: Studded <Studded@gorean.org>
From: Brett Glass <brett@lariat.org>
Subject: Re: No terminal echo after certain commands
Cc: bugs@FreeBSD.ORG
In-Reply-To: <362D045A.576B783A@gorean.org>
References: <4.1.19981020142239.06c13d50@mail.lariat.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

No program should leave the console partially or completely disabled,
no matter how it exits. Sounds like this is a bug in "more"!

--Brett

At 02:44 PM 10/20/98 -0700, Studded wrote:
 
>Brett Glass wrote:
>> 
>> After executing certain shell commands in FreeBSD's csh (especially ones
>> involving "more"), I sometimes find that characters don't echo. This most
>> frequently occurs when I ^C out of something that's scrolling text through
>> more, but also occurs at other times.
>
>	"Doctor, it hurts when I do this." "So, don't do that." :) Try reading
>the man page for 'more' to see what the proper way to exit out of it is
>and you will avoid this problem. 
>
>Good luck,
>
>Doug
>-- 
>***           Chief Operations Officer, DALnet IRC network          ***
>
>    Go PADRES!


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 16:00:04 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA13499
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 16:00:04 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from laker.net (jet.laker.net [205.245.74.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13439
          for <bugs@FreeBSD.ORG>; Tue, 20 Oct 1998 15:59:31 -0700 (PDT)
          (envelope-from sfriedri@laker.net)
Received: from nt (digital-pbi-128.laker.net [208.0.233.28]) by laker.net (8.9.0/8.9.LAKERNET.NO-SPAM.SPAMMERS.AND.RELAYS.WILL.BE.TRACKED.AND.PROSECUTED.) with SMTP id SAA25216; Tue, 20 Oct 1998 18:58:55 -0400
Message-Id: <199810202258.SAA25216@laker.net>
From: "Steve Friedrich" <SteveFriedrich@Hot-Shot.com>
To: "Brett Glass" <brett@lariat.org>, "Studded" <Studded@gorean.org>
Cc: "bugs@FreeBSD.ORG" <bugs@FreeBSD.ORG>
Date: Tue, 20 Oct 1998 18:57:51 -0400
Reply-To: "Steve Friedrich" <SteveFriedrich@Hot-Shot.com>
X-Mailer: PMMail 98 Professional (2.01.1600) For Windows NT (4.0.1381;3)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: No terminal echo after certain commands
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Tue, 20 Oct 1998 15:53:13 -0600, Brett Glass wrote:

>No program should leave the console partially or completely disabled,
>no matter how it exits. Sounds like this is a bug in "more"!

Actually, Control-C is used by a user who specifically wants to exit
RIGHT NOW (emergency exit) with a very short path thru any code that
could hang.  It is NOT meant as a non-emergency exit signal.

In short, Studded is right, you are not.
Unix systems measure "uptime" in years, Winblows measures it in minutes.



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 16:00:06 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA13512
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 16:00:06 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13498
          for <freebsd-bugs@FreeBSD.org>; Tue, 20 Oct 1998 16:00:03 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id QAA10357;
	Tue, 20 Oct 1998 16:00:00 -0700 (PDT)
Date: Tue, 20 Oct 1998 16:00:00 -0700 (PDT)
Message-Id: <199810202300.QAA10357@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.ORG
From: Jin Guojun (FTG staff) <jin@george.lbl.gov>
Subject: Re: kern/8386: modload failure
Reply-To: Jin Guojun (FTG staff) <jin@george.lbl.gov>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR kern/8386; it has been noted by GNATS.

From: Jin Guojun (FTG staff) <jin@george.lbl.gov>
To: FreeBSD-gnats-submit@FreeBSD.ORG
Cc: se@mi.uni-koeln.de
Subject: Re: kern/8386: modload failure
Date: Tue, 20 Oct 1998 15:55:29 -0700 (PDT)

 Here is the problem in pci/pci_compat.c. Is it line ???? supposed to be
 
 	if (lkm == NULL)	{
 		return	-1;
 	}
 
 segment of pci/pci_compat.c
 
 static void
 pci_rescan(void)
 {
         /* XXX do nothing, currently, soon to come ... */
 }
  
 int pci_register_lkm (struct pci_device *dvp, int if_revision)
 { 
         struct pci_lkm *lkm;
   
         if (if_revision != 0) {
                 return (-1);
         }
         if (dvp == NULL || dvp->pd_probe == NULL || dvp->pd_attach == NULL) {
                 return (-1);
         }
         lkm = malloc (sizeof (*lkm), M_DEVBUF, M_WAITOK);
         if (lkm != NULL) {	/* ?????????????????????????	*/
                 return (-1);
         }
  
         lkm->dvp = dvp;
         lkm->next = pci_lkm_head;
         pci_lkm_head = lkm;
         pci_rescan();  
         return (0);
 }
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 17:03:32 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA20114
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 17:03:32 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA20107
          for <bugs@FreeBSD.ORG>; Tue, 20 Oct 1998 17:03:30 -0700 (PDT)
          (envelope-from Studded@gorean.org)
Received: from gorean.org (Studded@localhost [127.0.0.1])
	by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id RAA07421;
	Tue, 20 Oct 1998 17:02:51 -0700 (PDT)
	(envelope-from Studded@gorean.org)
Message-ID: <362D24AA.9BA5BA0@gorean.org>
Date: Tue, 20 Oct 1998 17:02:50 -0700
From: Studded <Studded@gorean.org>
Organization: Triborough Bridge & Tunnel Authority
X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 2.2.7-STABLE-1015 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Brett Glass <brett@lariat.org>
CC: bugs@FreeBSD.ORG
Subject: Re: No terminal echo after certain commands
References: <4.1.19981020142239.06c13d50@mail.lariat.org> <4.1.19981020155224.06d3cab0@mail.lariat.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Brett Glass wrote:
> 
> No program should leave the console partially or completely disabled,
> no matter how it exits. Sounds like this is a bug in "more"!

	We eagerly await your patch.
-- 
***           Chief Operations Officer, DALnet IRC network          ***

    Go PADRES!

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 17:22:30 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA21514
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 17:22:30 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA21500
          for <bugs@FreeBSD.ORG>; Tue, 20 Oct 1998 17:22:28 -0700 (PDT)
          (envelope-from brett@lariat.org)
Received: (from brett@localhost)
	by lariat.lariat.org (8.8.8/8.8.6) id SAA08357;
	Tue, 20 Oct 1998 18:21:55 -0600 (MDT)
Message-Id: <4.1.19981020161523.06d1d5a0@mail.lariat.org>
Message-Id: <4.1.19981020161523.06d1d5a0@mail.lariat.org>
X-Sender: brett@mail.lariat.org
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Tue, 20 Oct 1998 16:19:22 -0600
To: Studded <Studded@gorean.org>
From: Brett Glass <brett@lariat.org>
Subject: Re: No terminal echo after certain commands
Cc: bugs@FreeBSD.ORG
In-Reply-To: <362D045A.576B783A@gorean.org>
References: <4.1.19981020142239.06c13d50@mail.lariat.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

P.S. -- I don't see anything on the man page that says there's any problem with terminating "more" via ^C. It seems to me that it should know how to handle SIGINT.

--Brett

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 17:22:30 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA21515
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 17:22:30 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA21501
          for <bugs@FreeBSD.ORG>; Tue, 20 Oct 1998 17:22:28 -0700 (PDT)
          (envelope-from brett@lariat.org)
Received: (from brett@localhost)
	by lariat.lariat.org (8.8.8/8.8.6) id SAA08360;
	Tue, 20 Oct 1998 18:21:55 -0600 (MDT)
Message-Id: <4.1.19981020181535.06ad01a0@mail.lariat.org>
X-Sender: brett@mail.lariat.org
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Tue, 20 Oct 1998 18:16:22 -0600
To: "Steve Friedrich" <SteveFriedrich@Hot-Shot.com>,
        "Studded" <Studded@gorean.org>
From: Brett Glass <brett@lariat.org>
Subject: Re: No terminal echo after certain commands
Cc: "bugs@FreeBSD.ORG" <bugs@FreeBSD.ORG>
In-Reply-To: <199810202258.SAA25216@laker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Well, if you really had an emergency, you'd CERTAINLY want your
terminal to work! I do not think that anyone would consider
this optional.

--Brett

At 06:57 PM 10/20/98 -0400, Steve Friedrich wrote:
 
>On Tue, 20 Oct 1998 15:53:13 -0600, Brett Glass wrote:
>
>>No program should leave the console partially or completely disabled,
>>no matter how it exits. Sounds like this is a bug in "more"!
>
>Actually, Control-C is used by a user who specifically wants to exit
>RIGHT NOW (emergency exit) with a very short path thru any code that
>could hang.  It is NOT meant as a non-emergency exit signal.
>
>In short, Studded is right, you are not.
>Unix systems measure "uptime" in years, Winblows measures it in minutes.
>
>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 17:59:06 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA25116
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 17:59:06 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from laker.net (jet.laker.net [205.245.74.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25111
          for <bugs@FreeBSD.ORG>; Tue, 20 Oct 1998 17:59:04 -0700 (PDT)
          (envelope-from sfriedri@laker.net)
Received: from nt (digital-pbi-128.laker.net [208.0.233.28]) by laker.net (8.9.0/8.9.LAKERNET.NO-SPAM.SPAMMERS.AND.RELAYS.WILL.BE.TRACKED.AND.PROSECUTED.) with SMTP id UAA30643; Tue, 20 Oct 1998 20:58:30 -0400
Message-Id: <199810210058.UAA30643@laker.net>
From: "Steve Friedrich" <SteveFriedrich@Hot-Shot.com>
To: "Brett Glass" <brett@lariat.org>, "Studded" <Studded@gorean.org>
Cc: "bugs@FreeBSD.ORG" <bugs@FreeBSD.ORG>
Date: Tue, 20 Oct 1998 20:57:26 -0400
Reply-To: "Steve Friedrich" <SteveFriedrich@Hot-Shot.com>
X-Mailer: PMMail 98 Professional (2.01.1600) For Windows NT (4.0.1381;3)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: No terminal echo after certain commands
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Tue, 20 Oct 1998 17:02:50 -0700, Studded wrote:

>Brett Glass wrote:
>> 
>> No program should leave the console partially or completely disabled,
>> no matter how it exits. Sounds like this is a bug in "more"!
>
>	We eagerly await your patch.

It REALLY shouldn't be fixed.  It is important to keep INTR handling to
the minimum possible exit code possible. Adding "clean-up" code will
add potential that programs will "hang" in this clean up code and INTR
will no longer work all the time for that program.  This is all caused
by someone who doesn't understand UNIX signals and what they were
designed for.  I'd bet he is a current or former DOS or Winblows user
who developed this bad habit there.  Microsoft stole the idea but
created (once again) a very poor implementation.  He needs to learn how
to exit an application properly, and that is application dependant. He
wants a "standard" and he thinks he's got that in INTR. He doesn't.
Unix systems measure "uptime" in years, Winblows measures it in minutes.



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 18:03:08 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA25487
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 18:03:08 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from laker.net (jet.laker.net [205.245.74.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA25480
          for <bugs@FreeBSD.ORG>; Tue, 20 Oct 1998 18:03:06 -0700 (PDT)
          (envelope-from sfriedri@laker.net)
Received: from nt (digital-pbi-128.laker.net [208.0.233.28]) by laker.net (8.9.0/8.9.LAKERNET.NO-SPAM.SPAMMERS.AND.RELAYS.WILL.BE.TRACKED.AND.PROSECUTED.) with SMTP id VAA30851; Tue, 20 Oct 1998 21:02:33 -0400
Message-Id: <199810210102.VAA30851@laker.net>
From: "Steve Friedrich" <SteveFriedrich@Hot-Shot.com>
To: "Brett Glass" <brett@lariat.org>, "Studded" <Studded@gorean.org>
Cc: "bugs@FreeBSD.ORG" <bugs@FreeBSD.ORG>
Date: Tue, 20 Oct 1998 21:01:36 -0400
Reply-To: "Steve Friedrich" <SteveFriedrich@Hot-Shot.com>
X-Mailer: PMMail 98 Professional (2.01.1600) For Windows NT (4.0.1381;3)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: No terminal echo after certain commands
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Tue, 20 Oct 1998 16:19:22 -0600, Brett Glass wrote:

>P.S. -- I don't see anything on the man page that says there's any problem with terminating "more" via ^C. It seems to me that it should know how to handle SIGINT.

It DOES.  You don't understand that SIGINT is NOT a general purpose
exit.  If it were, no UNIX utility would have used something like q to
exit gracefully.  SIGINT is NOT a graceful exit, but an immediate one. 
Use q to exit more.
Unix systems measure "uptime" in years, Winblows measures it in minutes.



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 18:16:18 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA26915
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 18:16:18 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26910
          for <bugs@FreeBSD.ORG>; Tue, 20 Oct 1998 18:16:17 -0700 (PDT)
          (envelope-from brett@lariat.org)
Received: (from brett@localhost)
	by lariat.lariat.org (8.8.8/8.8.6) id TAA08819;
	Tue, 20 Oct 1998 19:15:40 -0600 (MDT)
Message-Id: <4.1.19981020191142.06b355b0@mail.lariat.org>
X-Sender: brett@mail.lariat.org
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Tue, 20 Oct 1998 19:15:26 -0600
To: "Steve Friedrich" <SteveFriedrich@Hot-Shot.com>,
        "Studded" <Studded@gorean.org>
From: Brett Glass <brett@lariat.org>
Subject: Re: No terminal echo after certain commands
Cc: "bugs@FreeBSD.ORG" <bugs@FreeBSD.ORG>
In-Reply-To: <199810210058.UAA30643@laker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

At 08:57 PM 10/20/98 -0400, Steve Friedrich wrote:
 
>It REALLY shouldn't be fixed.  It is important to keep INTR handling to
>the minimum possible exit code possible. Adding "clean-up" code will
>add potential that programs will "hang" in this clean up code and INTR
>will no longer work all the time for that program.  

It's possible that anything programmed badly will hang. However, failure
to return the console to usability after a quick exit is not optional.
Otherwise, it does no good to make a quick exit.

>This is all caused
>by someone who doesn't understand UNIX signals and what they were
>designed for.

Sorry, but you're not only insulting but wrong. I've been using UNIX
since 1977.

>I'd bet he is a current or former DOS or Winblows user
>who developed this bad habit there.

You're arguing ad hominem. Which is especially dangerous when you
have no idea whom you're talking about.

Again, ANY way of interrupting a program shouldn't leave the
console unusable.

--Brett


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 18:17:51 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA27111
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 18:17:51 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA27104
          for <bugs@FreeBSD.ORG>; Tue, 20 Oct 1998 18:17:50 -0700 (PDT)
          (envelope-from brett@lariat.org)
Received: (from brett@localhost)
	by lariat.lariat.org (8.8.8/8.8.6) id TAA08836;
	Tue, 20 Oct 1998 19:17:18 -0600 (MDT)
Message-Id: <4.1.19981020191601.00c54180@mail.lariat.org>
X-Sender: brett@mail.lariat.org
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Tue, 20 Oct 1998 19:17:11 -0600
To: "Steve Friedrich" <SteveFriedrich@Hot-Shot.com>,
        "Studded" <Studded@gorean.org>
From: Brett Glass <brett@lariat.org>
Subject: Re: No terminal echo after certain commands
Cc: "bugs@FreeBSD.ORG" <bugs@FreeBSD.ORG>
In-Reply-To: <199810210102.VAA30851@laker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

At 09:01 PM 10/20/98 -0400, Steve Friedrich wrote:
 
>Unix systems measure "uptime" in years, Winblows measures it in minutes.

So, just because UNIX is more reliable than Windows (not a difficult
feat), no one should attempt to fix bugs in it?

--Brett Glass


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 18:50:06 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA00878
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 18:50:06 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from mayn.de (airbus.mayn.de [194.95.209.24])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA00873
          for <bugs@FreeBSD.ORG>; Tue, 20 Oct 1998 18:50:02 -0700 (PDT)
          (envelope-from mkb@altair.mayn.de)
Received: (qmail 16564 invoked from network); 21 Oct 1998 01:50:03 -0000
Received: from wuff.mayn.de (qmailr@194.95.209.17)
  by airbus.mayn.de with SMTP; 21 Oct 1998 01:50:03 -0000
Received: (qmail 13429 invoked by uid 5); 21 Oct 1998 01:49:30 -0000
Received: from altair.mayn.de (localhost [127.0.0.1]) by altair.mayn.de (8.8.8/8.7.3) with ESMTP id DAA01224; Wed, 21 Oct 1998 03:49:52 +0200 (CEST)
Message-Id: <199810210149.DAA01224@altair.mayn.de>
X-Mailer: exmh version 2.0.2 2/24/98
To: Brett Glass <brett@lariat.org>
Cc: bugs@FreeBSD.ORG
Subject: Re: No terminal echo after certain commands 
In-Reply-To: Your message of "Tue, 20 Oct 1998 19:15:26 MDT."
             <4.1.19981020191142.06b355b0@mail.lariat.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 21 Oct 1998 03:49:50 +0200
From: Matthias Buelow <mkb@altair.mayn.de>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

"Brett Glass <brett@lariat.org>" wrote:

>Again, ANY way of interrupting a program shouldn't leave the
>console unusable.

It most probably isn't unusable; ^Jreset^J should return it to a
sane state.  If you kill -9 a program, there's no way for it to
reset the terminal to the previous state either.  I think it's a
little exaggerated for a small utility like "more" to catch all
catchable signals (including SEGV, BUS etc.) just to reset the tty
to its previous state.  INTR is in no way different from SEGV or BUS;
the user usually wants the thing to quit fast.  If you kill full-
screen programs, you have to reset the tty yourself.

 - mkb



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 19:03:24 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA02250
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 19:03:24 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02243
          for <bugs@FreeBSD.ORG>; Tue, 20 Oct 1998 19:03:22 -0700 (PDT)
          (envelope-from brett@lariat.org)
Received: (from brett@localhost)
	by lariat.lariat.org (8.8.8/8.8.6) id UAA09241;
	Tue, 20 Oct 1998 20:02:47 -0600 (MDT)
Message-Id: <4.1.19981020195137.00c54280@mail.lariat.org>
X-Sender: brett@mail.lariat.org
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Tue, 20 Oct 1998 20:02:41 -0600
To: Matthias Buelow <mkb@altair.mayn.de>
From: Brett Glass <brett@lariat.org>
Subject: Re: No terminal echo after certain commands 
Cc: bugs@FreeBSD.ORG
In-Reply-To: <199810210149.DAA01224@altair.mayn.de>
References: <Your message of "Tue, 20 Oct 1998 19:15:26 MDT."             <4.1.19981020191142.06b355b0@mail.lariat.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

At 03:49 AM 10/21/98 +0200, Matthias Buelow wrote:
 
>It most probably isn't unusable; ^Jreset^J should return it to a
>sane state.

I've been using "tset", but "reset" does also work.

>If you kill -9 a program, there's no way for it to
>reset the terminal to the previous state either.  

True.

>I think it's a
>little exaggerated for a small utility like "more" to catch all
>catchable signals (including SEGV, BUS etc.) just to reset the tty
>to its previous state.

No, but SIGINT is much more likely to happen, and in fact is the
OFFICIAL way to get out of lots of screen-oriented programs.

>INTR is in no way different from SEGV or BUS; the user usually 
>wants the thing to quit fast.  

True. But so fast that the console is unusable? I'd save that
for a signal with greater severity. 

The usual convention is that ^C makes a quick but still
graceful exit, while kill -9 is the take-no-prisoners,
don't-clean-up version. 

/bin/mail is a good example of the use of ^C. Yes, ^C kills the 
message you're writing, but it doesn't mess up your mail file
or your terminal. (In fact, because the ^C can destroy a lot of 
work, there's an option -- often enabled by default -- to give 
the user a second chance before quitting.)

>If you kill full-screen programs, you have to reset the tty 
>yourself.

Again, it seems to me that if you killed them with a sledgehammer,
that would be fine. But ^C? Again, it (or something like it) is 
the standard way out of too many things. It should clean up,
as it does on Slowlaris and other UNIX implementations.

--Brett


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 20:31:20 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA09619
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 20:31:20 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from peak.mountin.net (peak.mountin.net [207.227.119.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA09612
          for <bugs@FreeBSD.ORG>; Tue, 20 Oct 1998 20:31:19 -0700 (PDT)
          (envelope-from jeff-ml@mountin.net)
Received: (from daemon@localhost)
	by peak.mountin.net (8.9.1/8.9.1) id WAA19331;
	Tue, 20 Oct 1998 22:30:44 -0500 (CDT)
Received: from harkol-105.isdn.mke.execpc.com(169.207.64.233) by peak.mountin.net via smap (V1.3)
	id sma019327; Tue Oct 20 22:30:24 1998
Message-Id: <3.0.3.32.19981020222556.01047304@207.227.119.2>
X-Sender: jeff-ml@207.227.119.2
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32)
Date: Tue, 20 Oct 1998 22:25:56 -0500
To: Brett Glass <brett@lariat.org>,
        "Steve Friedrich" <SteveFriedrich@Hot-Shot.com>,
        "Studded" <Studded@gorean.org>
From: "Jeffrey J. Mountin" <jeff-ml@mountin.net>
Subject: Re: No terminal echo after certain commands
Cc: "bugs@FreeBSD.ORG" <bugs@FreeBSD.ORG>
In-Reply-To: <4.1.19981020191142.06b355b0@mail.lariat.org>
References: <199810210058.UAA30643@laker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

At 07:15 PM 10/20/98 -0600, Brett Glass wrote:
>At 08:57 PM 10/20/98 -0400, Steve Friedrich wrote:
> 
>>It REALLY shouldn't be fixed.  It is important to keep INTR handling to
>>the minimum possible exit code possible. Adding "clean-up" code will
>>add potential that programs will "hang" in this clean up code and INTR
>>will no longer work all the time for that program.  
>
>It's possible that anything programmed badly will hang. However, failure
>to return the console to usability after a quick exit is not optional.
>Otherwise, it does no good to make a quick exit.
>
>>This is all caused
>>by someone who doesn't understand UNIX signals and what they were
>>designed for.
>
>Sorry, but you're not only insulting but wrong. I've been using UNIX
>since 1977.
>
>>I'd bet he is a current or former DOS or Winblows user
>>who developed this bad habit there.

Ala /p?

>You're arguing ad hominem. Which is especially dangerous when you
>have no idea whom you're talking about.
>
>Again, ANY way of interrupting a program shouldn't leave the
>console unusable.

Have you ever had a case where you absolutely *had* to ^C?  Or ^T or ^Z?

By now one should have found using 1 keystroke "q" easier than a
combination "CTL-c". </facetious>

Doug's point is along line that only a novice would try this and hopefully
read the man page and learn about the "q" exit command.

I agree in principle, but this also follow the "cat" thread a while back.
Oddly enough there are many examples that cat files (not in a script) in
the Handbook.

At least it doesn't want escape-enter.  ;)


Jeff Mountin - Unix Systems TCP/IP networking
jeff@mountin.net

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 21:13:34 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA13339
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 21:13:34 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13334
          for <bugs@FreeBSD.ORG>; Tue, 20 Oct 1998 21:13:32 -0700 (PDT)
          (envelope-from brett@lariat.org)
Received: (from brett@localhost)
	by lariat.lariat.org (8.8.8/8.8.6) id WAA10331;
	Tue, 20 Oct 1998 22:12:56 -0600 (MDT)
Message-Id: <4.1.19981020220950.06c1aca0@mail.lariat.org>
X-Sender: brett@mail.lariat.org
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Tue, 20 Oct 1998 22:12:45 -0600
To: "Jeffrey J. Mountin" <jeff-ml@mountin.net>,
        "Steve Friedrich" <SteveFriedrich@Hot-Shot.com>,
        "Studded" <Studded@gorean.org>
From: Brett Glass <brett@lariat.org>
Subject: Re: No terminal echo after certain commands
Cc: "bugs@FreeBSD.ORG" <bugs@FreeBSD.ORG>
In-Reply-To: <3.0.3.32.19981020222556.01047304@207.227.119.2>
References: <4.1.19981020191142.06b355b0@mail.lariat.org>
 <199810210058.UAA30643@laker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

At 10:25 PM 10/20/98 -0500, Jeffrey J. Mountin wrote:

>By now one should have found using 1 keystroke "q" easier than a
>combination "CTL-c". </facetious>

Perhaps. But ^C is programmed into many folks' fingertips. ESPECIALLY
UNIX hackers. It's the correct way out of many, MANY things.

>Doug's point is along line that only a novice would try this and hopefully
>read the man page and learn about the "q" exit command.

Sometimes I do use "q". However, using ^C should be acceptable as well.
Restoring echo on the terminal is not a time-consuming operation or
one that's going to fail unless the system is crashing.

>At least it doesn't want escape-enter.  ;)

That's a minor relief.... ;-)

--Brett


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 23:00:07 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id XAA19893
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 23:00:07 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA19885
          for <freebsd-bugs@FreeBSD.org>; Tue, 20 Oct 1998 23:00:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id XAA25458;
	Tue, 20 Oct 1998 23:00:01 -0700 (PDT)
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA19843;
          Tue, 20 Oct 1998 22:59:34 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199810210559.WAA19843@hub.freebsd.org>
Date: Tue, 20 Oct 1998 22:59:34 -0700 (PDT)
From: wlr@jps.net
To: freebsd-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: www-1.0
Subject: bin/8395: /usr/src/sbin/vinum/Makefile doesn't understand /usr/src/make -DNOLKM
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8395
>Category:       bin
>Synopsis:       /usr/src/sbin/vinum/Makefile doesn't understand /usr/src/make -DNOLKM
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Oct 20 23:00:01 PDT 1998
>Last-Modified:
>Originator:     Bill Richter
>Organization:
>Release:        3.0-RELEASE
>Environment:
3.0-RELEASE i386
>Description:
When making world, using the -DNOLKM option, compiling of 
/usr/src/sbin/vinum fails since it appears to not understand
that /usr/src/lkm doesn't exist.  
>How-To-Repeat:
make -DNOLKM world
>Fix:
if -DNOLKM, don't build either the program or the LKM piece.

>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Tue Oct 20 23:50:05 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id XAA22594
          for freebsd-bugs-outgoing; Tue, 20 Oct 1998 23:50:05 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA22586
          for <freebsd-bugs@FreeBSD.org>; Tue, 20 Oct 1998 23:50:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id XAA27206;
	Tue, 20 Oct 1998 23:50:01 -0700 (PDT)
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id XAA22569;
          Tue, 20 Oct 1998 23:50:01 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199810210650.XAA22569@hub.freebsd.org>
Date: Tue, 20 Oct 1998 23:50:01 -0700 (PDT)
From: pantor@chat.ru
To: freebsd-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: www-1.0
Subject: conf/8396: Don't work NIS server
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8396
>Category:       conf
>Synopsis:       Don't work NIS server
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Oct 20 23:50:00 PDT 1998
>Last-Modified:
>Originator:     Sergey
>Organization:
Analog-Digital Systems
>Release:        2.2.7
>Environment:
>Description:

>How-To-Repeat:

>Fix:

>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Wed Oct 21 00:07:03 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id AAA23631
          for freebsd-bugs-outgoing; Wed, 21 Oct 1998 00:07:03 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA23626
          for <bugs@FreeBSD.ORG>; Wed, 21 Oct 1998 00:07:01 -0700 (PDT)
          (envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id JAA27156;
	Wed, 21 Oct 1998 09:01:42 +0200 (CEST)
To: Brett Glass <brett@lariat.org>
cc: "Steve Friedrich" <SteveFriedrich@Hot-Shot.com>,
        "Studded" <Studded@gorean.org>, "bugs@FreeBSD.ORG" <bugs@FreeBSD.ORG>
Subject: Re: No terminal echo after certain commands 
In-reply-to: Your message of "Tue, 20 Oct 1998 19:15:26 MDT."
             <4.1.19981020191142.06b355b0@mail.lariat.org> 
Date: Wed, 21 Oct 1998 09:01:42 +0200
Message-ID: <27154.908953302@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

In message <4.1.19981020191142.06b355b0@mail.lariat.org>, Brett Glass writes:
>At 08:57 PM 10/20/98 -0400, Steve Friedrich wrote:
> 
>>It REALLY shouldn't be fixed.  It is important to keep INTR handling to
>>the minimum possible exit code possible. Adding "clean-up" code will
>>add potential that programs will "hang" in this clean up code and INTR
>>will no longer work all the time for that program.  
>
>It's possible that anything programmed badly will hang. However, failure
>to return the console to usability after a quick exit is not optional.
>Otherwise, it does no good to make a quick exit.

Ok: can it!

 move this stuff to -chat or kill it.


--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
"ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Wed Oct 21 00:16:20 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id AAA24367
          for freebsd-bugs-outgoing; Wed, 21 Oct 1998 00:16:20 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.6.53])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA24360
          for <freebsd-bugs@FreeBSD.org>; Wed, 21 Oct 1998 00:16:16 -0700 (PDT)
          (envelope-from joey@xs4all.nl)
Received: from xs4all.nl (p030.hlm.euronet.nl [194.134.33.166])
	by smtp3.xs4all.nl (8.8.8/8.8.8) with ESMTP id JAA18228
	for <freebsd-bugs@FreeBSD.org>; Wed, 21 Oct 1998 09:15:47 +0200 (CEST)
Message-ID: <362D6E39.E56B2928@xs4all.nl>
Date: Wed, 21 Oct 1998 07:16:41 +0200
From: Joey Hofstede <joey@xs4all.nl>
X-Mailer: Mozilla 4.07 [en] (Win98; I)
MIME-Version: 1.0
To: freebsd-bugs@FreeBSD.ORG
Subject: Upgrade to version 3.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Hello,

Yesterday I tried to upgrade from 2.2.7 to 3.0 via FTP.

OK, I did something not quiet right, I performed the upgrade within X.
But now, the morning after, I noticed that the upgrade was killed due to
'Out of swap space'.
OK, that can happen. BUT I restarted FreeBSD with <kernel.old> and when
the login prompt appears, suddenly  I can login as root WITHOUT a
password?!?!?!?!?!

There is always a good explanation, ..."new passwd was not written
yet...."
It is not a big deal, 'cause it was a test machine, I thought you should
now.

With regards,

Joey Hofstede


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Wed Oct 21 01:00:07 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id BAA27405
          for freebsd-bugs-outgoing; Wed, 21 Oct 1998 01:00:07 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from ifi.uio.no (ifi.uio.no [129.240.64.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA27400
          for <bugs@freebsd.org>; Wed, 21 Oct 1998 01:00:05 -0700 (PDT)
          (envelope-from dag-erli@ifi.uio.no)
Received: from hel.ifi.uio.no (2602@hel.ifi.uio.no [129.240.64.91])
	by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id JAA23999
	for <bugs@freebsd.org>; Wed, 21 Oct 1998 09:59:37 +0200 (MET DST)
Received: (from dag-erli@localhost) by hel.ifi.uio.no ; Wed, 21 Oct 1998 09:59:36 +0200 (MET DST)
Mime-Version: 1.0
To: bugs@FreeBSD.ORG
Subject: ["MISTY D LINVILLE" <linvilmd@daleth.grace.edu>] Re: 3.0 install from DOS
Organization: University of Oslo, Department of Informatics
X-url: http://www.stud.ifi.uio.no/~dag-erli/
X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list
X-disclaimer-1: The views expressed in this article are mine alone, and do
X-disclaimer-2: not necessarily coincide with those of any organisation or
X-disclaimer-3: company with which I am or have been affiliated.
X-Stop-Spam: http://www.cauce.org/
From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= )
Date: 21 Oct 1998 09:59:35 +0200
Message-ID: <xzpaf2qbb14.fsf@hel.ifi.uio.no>
Lines: 1201
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

------- Start of forwarded message -------
Message-Id: <199810210533.AAA05696@daleth.grace.edu>
From: "MISTY D LINVILLE" <linvilmd@daleth.grace.edu>
To: dag-erli@ifi.uio.no (Dag-Erling C. Smorgrav )
Date: Tue, 20 Oct 1998 23:39:21 +0000
Subject: Re: 3.0 install from DOS
References: "MISTY D LINVILLE"'s message of "Tue, 20 Oct 1998 09:38:46 +0000"


--Message-Boundary-16754
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body

Alrighty,  I put Linux back on just so I could list the FREEBSD 
directory recursively for you.  Hope it helps figure out the problem. 
 For what it's worth, I tried leaving all the directories in 
lowercase at first, then changed them to all caps (because it seemed 
that they were that way in the installation guide) and neither way 
worked.  They're still all caps right now, as you can see.  Thanks!

~Misty

> To:            "MISTY D LINVILLE" <linvilmd@daleth.grace.edu>
> Subject:       Re: 3.0 install from DOS
> From:          dag-erli@ifi.uio.no (Dag-Erling C. Smorgrav )
> Date:          20 Oct 1998 19:27:47 +0200

> "MISTY D LINVILLE" <linvilmd@daleth.grace.edu> writes:
> > The error is something to the effect of "Could not find the following 
> > distributions on the media you chose: bin, des, dict, etc,etc.  I 
> > don't have tree for dos, so I'll have to show you the directory 
> > structure by hand.
> > 
> > C:\FREEBSD\BIN
> > 	bin.aa
> > 	bin.ab
> > 	bin.ac
> > 	bin.ad
> > 	......
> > 
> > Is this as it should be?  I hope this is enough info. :)
> 
> Are bin.inf and bin.mtree (or whatever it's called in 8.3) there also?
> 
> DES
> -- 
> Dag-Erling Smorgrav - dag-erli@ifi.uio.no
> 
> 


--Message-Boundary-16754
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Text from file 'ls_r'

00_index.txt
BIN
CATPAGES
COMMERCE
COMPAT1X
COMPAT20
COMPAT21
DES
DICT
DOC
FLOPPIES
GAMES
INFO
MANPAGES
PACKAGES
PORTS
PROFLIBS
SRC
TOOLS
about.txt
boot.bin
bootinst.exe
cdrom.inf
ckdist.exe
ckdist.man
errata.txt
extipl.exe
fbsdboot.exe
fdimage.exe
fips.exe
gunzip.exe
gzip.exe
hardware.txt
ide_conf.exe
install.txt
layout.txt
ls_R
osbs135.exe
osbsbeta.exe
pfdisk.exe
presizer.doc
presizer.exe
rawrite.exe
readme
readme.txt
relnotes.txt
restorrb.exe
setup.exe
setup.hlp
setup.pif
trouble.txt
upgrade.txt
ws_ftp.log
xf86332

BIN:
bin.aa
bin.ab
bin.ac
bin.ad
bin.ae
bin.af
bin.ag
bin.ah
bin.ai
bin.aj
bin.ak
bin.al
bin.am
bin.an
bin.ao
bin.ap
bin.aq
bin.ar
bin.as
bin.at
bin.au
bin.av
bin.aw
bin.ax
bin.ay
bin.az
bin.ba
bin.bb
bin.bc
bin.bd
bin.be
bin.bf
bin.bg
bin.bh
bin.bi
bin.bj
bin.bk
bin.bl
bin.bm
bin.bn
bin.bo
bin.bp
bin.bq
bin.br
bin.bs
bin.bt
bin.bu
bin.bv
bin.bw
bin.bx
bin.by
bin.bz
bin.ca
bin.cb
bin.cc
bin.cd
bin.ce
bin.cf
bin.cg
bin.ch
bin.ci
bin.cj
bin.ck
bin.cl
bin.cm
bin.cn
bin.co
bin.cp
bin.cq
bin.cr
bin.cs
bin.ct
bin.cu
bin.cv
bin.cw
bin.cx
bin.cy
bin.cz
bin.da
bin.db
bin.dc
bin.dd
bin.de
bin.df
bin.dg
bin.dh
bin.di
bin.dj
bin.dk
bin.dl
bin.dm
bin.dn
bin.do
bin.dp
bin.dq
bin.dr
bin.ds
bin.dt
bin.du
bin.dv
bin.dw
bin.dx
bin.dy
bin.dz
bin.ea
bin.eb
bin.ec
bin.ed
bin.ee
bin.ef
bin.eg
bin.eh
bin.ei
bin.ej
bin.ek
bin.el
bin.em
bin.en
bin.eo
bin.ep
bin.eq
bin.er
bin.es
bin.inf
bin.mtree
checksum.md5
install.sh
ws_ftp.log

CATPAGES:
catpages.aa
catpages.ab
catpages.ac
catpages.ad
catpages.ae
catpages.af
catpages.ag
catpages.ah
catpages.ai
catpages.aj
catpages.ak
catpages.al
catpages.am
catpages.an
catpages.ao
catpages.ap
catpages.inf
catpages.mtree
checksum.md5
install.sh
ws_ftp.log

COMMERCE:
3d
audio
databases
desktop
development
emulators
games
graphics
mail
netcon
networking
readme.txt
utils
ws_ftp.log
x

COMMERCE/3d:
Blender
readme.txt
ws_ftp.log

COMMERCE/3d/Blender:
blacksmith.tar.gz
ws_ftp.log

COMMERCE/audio:
ossfreebsd38-beta15.tar.gz
readme.txt
ws_ftp.log

COMMERCE/databases:
CBase
readme.txt
ws_ftp.log

COMMERCE/databases/CBase:
cdrom_fbsd.tar.gz
readme.txt
ws_ftp.log

COMMERCE/desktop:
WordPerfect
axene
readme.txt
ws_ftp.log

COMMERCE/desktop/WordPerfect:
graphics.tar.gz
linux.txt
linuxceg.tar.gz
linuxcfg.tar.gz
linuxdeg.tar.gz
linuxesg.tar.gz
linuxfrg.tar.gz
linuxgui.tar.gz
linuxitg.tar.gz
linuxnlg.tar.gz
linuxozg.tar.gz
linuxukg.tar.gz
manual.tar.gz
sdk.tar.gz
ws_ftp.log

COMMERCE/desktop/axene:
AxeneInstall
LICENSE.French
Packages
RECENT.WEEK
free
license
order
readme
recent.day
ws_ftp.log

COMMERCE/desktop/axene/Packages:

COMMERCE/development:
Java
horus
mocka
p4
readme.txt
ws_ftp.log

COMMERCE/development/Java:
jdk102.11-26.tar.gz
ws_ftp.log

COMMERCE/development/horus:
horus-demo.tar.gz
horus-readme.tar.gz
readme.txt
ws_ftp.log

COMMERCE/development/mocka:
mocka9502main.tar.gz
mocka9502src.tar.gz
readme.txt
ws_ftp.log

COMMERCE/development/p4:
p4
p4d
readme.txt
ws_ftp.log

COMMERCE/emulators:
executor
readme.txt
ws_ftp.log

COMMERCE/emulators/executor:
executor-aout-demo.tar.gz
executor-common.tar.gz
executor-elf-demo.tar.gz
install_demo
readme.txt
ws_ftp.log

COMMERCE/games:
SimCity
phost
readme.txt
ws_ftp.log

COMMERCE/games/SimCity:
SimCity-3.6b.tgz
readme.txt
ws_ftp.log

COMMERCE/games/phost:
phostv2.9.tar.gz
readme.txt
ws_ftp.log

COMMERCE/graphics:
dislin_fbsd.63.tar.gz
readme
ws_ftp.log

COMMERCE/mail:
cgatepro

COMMERCE/mail/cgatepro:
CGatePro-FreeBSD-Intel-26.tgz
readme
ws_ftp.log

COMMERCE/netcon:
README-61.TXT
README.TXT
bsd61.tgz
bsd7022.tgz
ws_ftp.log

COMMERCE/networking:
NetTracker
dnews
etinc
lanstat
legato
readme.txt
ws_ftp.log

COMMERCE/networking/NetTracker:
n3p-fbsd.tar.Z
readme.txt
ws_ftp.log

COMMERCE/networking/dnews:
dnews-27q.tgz
dnews27q_freebsd.tar.Z
license.txt
readme.txt
ws_ftp.log

COMMERCE/networking/etinc:
bwmgr.tar
readme.txt
ws_ftp.log

COMMERCE/networking/lanstat:
lanstat.tar.gz
readme.txt
ws_ftp.log

COMMERCE/networking/legato:
freebsd2.tar.gz
readme.txt
ws_ftp.log

COMMERCE/utils:
readme.txt
vsh35b
ws_ftp.log

COMMERCE/utils/vsh35b:
readme.txt
vsh-dynamic
vsh-static
vsh.man
vsh.ps
ws_ftp.log

COMMERCE/x:
UnixCockpit
Xaccel
readme.txt
ws_ftp.log

COMMERCE/x/UnixCockpit:
readme.txt
uc
uc-bsd2.2-v2.0.gz
uc-dynamic
ws_ftp.log

COMMERCE/x/Xaccel:
2.1.freebsd.tar.gz
readme.txt
ws_ftp.log

COMPAT1X:
checksum.md5
compat1x.aa
compat1x.ab
compat1x.ac
compat1x.inf
compat1x.mtree
install.sh
ws_ftp.log

COMPAT20:
checksum.md5
compat20.aa
compat20.ab
compat20.inf
compat20.mtree
install.sh
ws_ftp.log

COMPAT21:
checksum.md5
compat21.aa
compat21.ab
compat21.inf
compat21.mtree
install.sh
ws_ftp.log

DES:
checksum.md5
des.aa
des.ab
des.inf
des.mtree
install.sh
krb.aa
krb.ab
krb.ac
krb.ad
krb.ae
krb.inf
krb.mtree
scrypto.aa
scrypto.ab
scrypto.ac
scrypto.inf
skerbero.aa
skerbero.inf
ssecure.aa
ssecure.inf
ws_ftp.log

DICT:
checksum.md5
dict.aa
dict.ab
dict.ac
dict.ad
dict.ae
dict.inf
dict.mtree
install.sh
ws_ftp.log

DOC:
checksum.md5
doc.aa
doc.ab
doc.ac
doc.ad
doc.ae
doc.af
doc.ag
doc.ah
doc.ai
doc.aj
doc.ak
doc.al
doc.am
doc.an
doc.ao
doc.ap
doc.aq
doc.ar
doc.inf
doc.mtree
install.sh
ws_ftp.log

FLOPPIES:
Shortcut to rawrite.pif
boot.flp
checksum.md5
fixit.flp
kern.flp
mfsroot.gz
readme.txt
ws_ftp.log

GAMES:
checksum.md5
games.aa
games.ab
games.ac
games.ad
games.ae
games.af
games.ag
games.ah
games.ai
games.aj
games.inf
games.mtree
install.sh
ws_ftp.log

INFO:
checksum.md5
info.aa
info.ab
info.ac
info.ad
info.ae
info.af
info.ag
info.ah
info.inf
info.mtree
install.sh
ws_ftp.log

MANPAGES:
checksum.md5
install.sh
manpages.aa
manpages.ab
manpages.ac
manpages.ad
manpages.ae
manpages.af
manpages.ag
manpages.ah
manpages.ai
manpages.aj
manpages.ak
manpages.al
manpages.am
manpages.an
manpages.ao
manpages.ap
manpages.aq
manpages.ar
manpages.as
manpages.at
manpages.au
manpages.av
manpages.aw
manpages.ax
manpages.ay
manpages.az
manpages.ba
manpages.bb
manpages.inf
manpages.mtree
ws_ftp.log

PACKAGES:
All

PACKAGES/All:
afterstep-1.0.tgz
apache-1.3.2.tgz
asclock-1.0.tgz
asedit-1.3.2.tgz
asfiles-1.0.tgz
asmail-0.50.tgz
autoconf-2.12.tgz
automake-1.3.tgz
bash-2.02.1.tgz
bind-8.1.2.tgz
bzip2-0.1p2.tgz
colorls-2.2.7.tgz
dict-1.4.9.tgz
egcs-19980914.tgz
electriceyes-0.3.tgz
electricfence-2.0.5.tgz
elm-2.4ME+43.tgz
eterm-0.8.6.tgz
fbsd-icons-1.0.tgz
fetchmail-4.6.0.tgz
freefonts-0.10.tgz
freetype-1.1.tgz
fvwm-1.24r.tgz
fvwm-2.0.46.tgz
fvwm95-2.0.43a.tgz
gimp-1.0.1.tgz
index
ircii-2.8.2-epic3.004.tgz
isc-dhcp2.b1.6.tgz
joe-2.8.tgz
less-332.tgz
linux-netscape-4.05.tgz
linux_devel-0.2.tgz
linux_lib-2.5.tgz
lynx-2.8.tgz
ncftp-2.4.3.tgz
netscape-navigator-4.07.tgz
pine-4.05.tgz
procmail-3.11p7.tgz
rxvt-2.4.7.tgz
sharutils-4.2.tgz
smtpd-2.0.tgz
staroffice-3.1.tgz
sudo-1.5.4.tgz
tar-1.12.tgz
tcl-8.0.2.tgz
tclX-8.0.2.tgz
tcp_wrappers-7.6.tgz
tcsh-6.07.02.tgz
textutils-1.22.tgz
tix-4.1.0.006.tgz
tk-8.0.2.tgz
traceroute-961230.tgz
unzip-5.3.2.tgz
windowmaker-0.20.1.tgz
ws_ftp.log
wu-ftpd-2.4.2b18.tgz
xcolors-1.3.tgz
xloadimage-4.1.tgz
xmail-1.6.tgz
zip-2.2.tgz

PORTS:
checksum.md5
install.sh
ports.tgz
ws_ftp.log

PROFLIBS:
checksum.md5
install.sh
proflibs.aa
proflibs.ab
proflibs.ac
proflibs.ad
proflibs.ae
proflibs.af
proflibs.ag
proflibs.ah
proflibs.inf
proflibs.mtree
ws_ftp.log

SRC:
checksum.md5
install.sh
sbase.aa
sbase.inf
sbin.aa
sbin.ab
sbin.ac
sbin.ad
sbin.inf
scontrib.aa
scontrib.ab
scontrib.ac
scontrib.ad
scontrib.ae
scontrib.af
scontrib.ag
scontrib.ah
scontrib.ai
scontrib.aj
scontrib.ak
scontrib.al
scontrib.am
scontrib.an
scontrib.ao
scontrib.ap
scontrib.aq
scontrib.ar
scontrib.as
scontrib.at
scontrib.au
scontrib.av
scontrib.aw
scontrib.ax
scontrib.ay
scontrib.az
scontrib.ba
scontrib.bb
scontrib.bc
scontrib.bd
scontrib.be
scontrib.bf
scontrib.bg
scontrib.bh
scontrib.bi
scontrib.bj
scontrib.bk
scontrib.bl
scontrib.bm
scontrib.bn
scontrib.bo
scontrib.bp
scontrib.bq
scontrib.br
scontrib.bs
scontrib.bt
scontrib.bu
scontrib.bv
scontrib.bw
scontrib.bx
scontrib.by
scontrib.bz
scontrib.ca
scontrib.cb
scontrib.cc
scontrib.cd
scontrib.ce
scontrib.cf
scontrib.cg
scontrib.ch
scontrib.ci
scontrib.cj
scontrib.ck
scontrib.cl
scontrib.cm
scontrib.cn
scontrib.co
scontrib.cp
scontrib.cq
scontrib.cr
scontrib.cs
scontrib.ct
scontrib.cu
scontrib.cv
scontrib.cw
scontrib.cx
scontrib.cy
scontrib.cz
scontrib.da
scontrib.db
scontrib.dc
scontrib.dd
scontrib.de
scontrib.df
scontrib.dg
scontrib.dh
scontrib.di
scontrib.dj
scontrib.inf
setc.aa
setc.inf
sgames.aa
sgames.ab
sgames.ac
sgames.ad
sgames.ae
sgames.af
sgames.ag
sgames.ah
sgames.ai
sgames.aj
sgames.ak
sgames.inf
sgnu.aa
sgnu.ab
sgnu.ac
sgnu.ad
sgnu.ae
sgnu.af
sgnu.ag
sgnu.ah
sgnu.ai
sgnu.aj
sgnu.ak
sgnu.al
sgnu.inf
sinclude.aa
sinclude.inf
slib.aa
slib.ab
slib.ac
slib.ad
slib.ae
slib.af
slib.ag
slib.ah
slib.ai
slib.aj
slib.ak
slib.al
slib.am
slib.an
slib.ao
slib.inf
slibexec.aa
slibexec.ab
slibexec.inf
slkm.aa
slkm.inf
srelease.aa
srelease.ab
srelease.ac
srelease.inf
ssbin.aa
ssbin.ab
ssbin.ac
ssbin.ad
ssbin.inf
sshare.aa
sshare.ab
sshare.ac
sshare.ad
sshare.ae
sshare.af
sshare.ag
sshare.ah
sshare.ai
sshare.aj
sshare.ak
sshare.inf
ssys.aa
ssys.ab
ssys.ac
ssys.ad
ssys.ae
ssys.af
ssys.ag
ssys.ah
ssys.ai
ssys.aj
ssys.ak
ssys.al
ssys.am
ssys.an
ssys.ao
ssys.ap
ssys.aq
ssys.ar
ssys.as
ssys.at
ssys.au
ssys.av
ssys.aw
ssys.ax
ssys.ay
ssys.az
ssys.ba
ssys.bb
ssys.inf
stools.aa
stools.inf
subin.aa
subin.ab
subin.ac
subin.ad
subin.ae
subin.af
subin.ag
subin.ah
subin.ai
subin.aj
subin.ak
subin.al
subin.am
subin.inf
susbin.aa
susbin.ab
susbin.ac
susbin.ad
susbin.ae
susbin.af
susbin.ag
susbin.ah
susbin.ai
susbin.aj
susbin.ak
susbin.al
susbin.inf
ws_ftp.log

TOOLS:
00_index.txt
boot.bin
bootinst.exe
ckdist.exe
ckdist.man
dist
extipl.exe
fbsdboot.exe
fdimage.exe
fips.exe
gunzip.exe
gzip.exe
ide_conf.exe
osbs135.exe
osbsbeta.exe
pfdisk.exe
presizer
presizer.doc
presizer.exe
rawrite.exe
readme
restorrb.exe
setup.exe
setup.hlp
srcs
ws_ftp.log

TOOLS/dist:
bteasy14.zip
bteasy17.zip
ckdist10.zip
extipl30.zip
fdimag12.zip
fips11.zip
fips15c.tar.gz
ide_conf.tar
pfdisktc.zip
presz120.zip
setup101.zip
setup220.zip
ws_ftp.log

TOOLS/presizer:
file_id.diz
presizer.doc
presizer.exe
presizer.faq
readme.1st
trouble.doc
vendor.doc
ws_ftp.log

TOOLS/srcs:
bteasy
extipl
fdimage.c
fips
ide_conf
pfdisk
rawrite
ws_ftp.log

TOOLS/srcs/bteasy:
boot.asm
boot.bin
boot.lst
bootinst.c
bootinst.exe
compile.bat
readme
ws_ftp.log

TOOLS/srcs/extipl:
_extipl.asm
develop
develop.doc
develop.eng
extipl.c
extipl.doc
extipl.eng
extipl.exe
makefile
readme.1st
ws_ftp.log

TOOLS/srcs/extipl/develop:
caps-fd.asm
caps-fd.bin
caps-hd.asm
caps-hd.bin
extfdtst.asm
extfdtst.bin
extipl.asm
extipl.bin
mkipl.bat
ws_ftp.log

TOOLS/srcs/fips:
copying
errors.txt
fips.doc
history.txt
readme.1st
restorrb
source
techinfo.txt
ws_ftp.log

TOOLS/srcs/fips/restorrb:
restorrb.c
rtypes.h
ws_ftp.log

TOOLS/srcs/fips/source:
calculat.cpp
check.cpp
cmdl_arg.cpp
disk_io.cpp
disk_io.h
fat.cpp
fat.h
fdstruct.h
fipsspec.cpp
fipsspec.h
global.cpp
global.h
hdstruct.cpp
hdstruct.h
host_os.cpp
host_os.h
input.cpp
input.h
logdr_st.cpp
logdr_st.h
main.cpp
save.cpp
types.h
ws_ftp.log

TOOLS/srcs/ide_conf:
ide_conf.c
wddefs.h
ws_ftp.log

TOOLS/srcs/pfdisk:
make_tcc.bat
pfdisk.doc
pfdiskaz.c
s_msdos.c
syscodes.c
syscodes.h
sysdep.h
ws_ftp.log

TOOLS/srcs/rawrite:
rawrite.c
rawrite.doc
ws_ftp.log

xf86332:
PC98-Servers
Servers
X9set.tgz
Xbin.tgz
Xcfg.tgz
Xdoc.tgz
Xf100.tgz
Xfcyr.tgz
Xfnon.tgz
Xfnts.tgz
Xfscl.tgz
Xfsrv.tgz
Xhtml.tgz
Xjdoc.tgz
Xlib.tgz
Xlk98.tgz
Xlkit.tgz
Xman.tgz
Xnest.tgz
Xprog.tgz
Xprt.tgz
Xps.tgz
Xset.tgz
Xvfb.tgz
checksum.md5
extract
postinst.sh
preinst.sh
readme
relnotes
ws_ftp.log

xf86332/PC98-Servers:
X9480.tgz
X9EGC.tgz
X9GA9.tgz
X9GAN.tgz
X9LPW.tgz
X9MGA.tgz
X9NKV.tgz
X9NS3.tgz
X9SPW.tgz
X9SVG.tgz
X9TGU.tgz
X9WEP.tgz
X9WS.tgz
X9WSN.tgz
ws_ftp.log

xf86332/Servers:
X8514.tgz
XAGX.tgz
XI128.tgz
XMa32.tgz
XMa64.tgz
XMa8.tgz
XMono.tgz
XP9K.tgz
XS3.tgz
XS3V.tgz
XSVGA.tgz
XVG16.tgz
XW32.tgz
ws_ftp.log

--Message-Boundary-16754--

------- End of forwarded message -------

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Wed Oct 21 06:26:28 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA16154
          for freebsd-bugs-outgoing; Wed, 21 Oct 1998 06:26:28 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from peak.mountin.net (peak.mountin.net [207.227.119.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA16125
          for <freebsd-bugs@FreeBSD.ORG>; Wed, 21 Oct 1998 06:26:21 -0700 (PDT)
          (envelope-from jeff-ml@mountin.net)
Received: (from daemon@localhost)
	by peak.mountin.net (8.9.1/8.9.1) id IAA20873;
	Wed, 21 Oct 1998 08:25:56 -0500 (CDT)
Received: from harkol-51.isdn.mke.execpc.com(169.207.64.179) by peak.mountin.net via smap (V1.3)
	id sma020871; Wed Oct 21 08:25:28 1998
Message-Id: <3.0.3.32.19981021082127.0105af18@207.227.119.2>
X-Sender: jeff-ml@207.227.119.2
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32)
Date: Wed, 21 Oct 1998 08:21:27 -0500
To: Joey Hofstede <joey@xs4all.nl>, freebsd-bugs@FreeBSD.ORG
From: "Jeffrey J. Mountin" <jeff-ml@mountin.net>
Subject: Re: Upgrade to version 3.0
In-Reply-To: <362D6E39.E56B2928@xs4all.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

At 07:16 AM 10/21/98 +0200, Joey Hofstede wrote:
>Hello,
>
>Yesterday I tried to upgrade from 2.2.7 to 3.0 via FTP.

wheeee!

>OK, I did something not quiet right, I performed the upgrade within X.
>But now, the morning after, I noticed that the upgrade was killed due to
>'Out of swap space'.
>OK, that can happen. BUT I restarted FreeBSD with <kernel.old> and when
>the login prompt appears, suddenly  I can login as root WITHOUT a
>password?!?!?!?!?!
>
>There is always a good explanation, ..."new passwd was not written
>yet...."
>It is not a big deal, 'cause it was a test machine, I thought you should
>now.

This almost sounds like a fresh install and you didn't choose to go to the
Options menu and set a password.  Hmmm...

This may not be a bug, but did you verify that /etc/master.passwd was not
clobbered by the upgrade?

Nevermind my musings above, but you did say the install did NOT complete,
which means certain saved files from /etc (moved to /var/tmp/etc?) would
not be restored.

No offense to Jordan and others that work on the upgrade procedure, but my
preference to fresh installs and not upgrade or cvsup's for major/point
releases has grounds in security as well.  Even so, you would be better to
upgrade first the OS and then deal with X and ports/packages.  Sure some
things will break, but small steps are easier than large ones.

Since it's a test machine, try again with a more simple upgrade and record
any problems.  Be thorough and either post the problem to -current or file
a PR.

Kudos for testing first. ;)


Jeff Mountin - Unix Systems TCP/IP networking
jeff@mountin.net

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Wed Oct 21 07:13:35 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA22618
          for freebsd-bugs-outgoing; Wed, 21 Oct 1998 07:13:35 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA22607
          for <bugs@FreeBSD.ORG>; Wed, 21 Oct 1998 07:13:34 -0700 (PDT)
          (envelope-from brett@lariat.org)
Received: (from brett@localhost)
	by lariat.lariat.org (8.8.8/8.8.6) id IAA13531;
	Wed, 21 Oct 1998 08:09:12 -0600 (MDT)
Message-Id: <4.1.19981021080750.0674c860@mail.lariat.org>
X-Sender: brett@mail.lariat.org
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Wed, 21 Oct 1998 08:09:00 -0600
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
From: Brett Glass <brett@lariat.org>
Subject: Re: No terminal echo after certain commands 
Cc: "Steve Friedrich" <SteveFriedrich@Hot-Shot.com>,
        "Studded" <Studded@gorean.org>, "bugs@FreeBSD.ORG" <bugs@FreeBSD.ORG>
In-Reply-To: <27154.908953302@critter.freebsd.dk>
References: <Your message of "Tue, 20 Oct 1998 19:15:26 MDT."             <4.1.19981020191142.06b355b0@mail.lariat.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

With all due respect, I do not think this belongs in -chat. It is a bug,
and a serious departure from the behavior of other UNIX implementations;
it really needs fixing.

--Brett

At 09:01 AM 10/21/98 +0200, Poul-Henning Kamp wrote:
 
>
>Ok: can it!
>
> move this stuff to -chat or kill it.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Wed Oct 21 07:56:55 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA27852
          for freebsd-bugs-outgoing; Wed, 21 Oct 1998 07:56:55 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA27840
          for <bugs@FreeBSD.ORG>; Wed, 21 Oct 1998 07:56:53 -0700 (PDT)
          (envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id QAA28630;
	Wed, 21 Oct 1998 16:51:35 +0200 (CEST)
To: Brett Glass <brett@lariat.org>
cc: "Steve Friedrich" <SteveFriedrich@Hot-Shot.com>,
        "Studded" <Studded@gorean.org>, "bugs@FreeBSD.ORG" <bugs@FreeBSD.ORG>
Subject: Re: No terminal echo after certain commands 
In-reply-to: Your message of "Wed, 21 Oct 1998 08:09:00 MDT."
             <4.1.19981021080750.0674c860@mail.lariat.org> 
Date: Wed, 21 Oct 1998 16:51:34 +0200
Message-ID: <28628.908981494@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


I'm sorry, I don't belive you belong in FreeBSD, with your excessive whining,
and complaining.  It's a serious departure from the project spirit which is
"If it's broke, go fix it!" not "If it's broke, whine until people want to
inflict bodily harm on you!".

Poul-Henning

In message <4.1.19981021080750.0674c860@mail.lariat.org>, Brett Glass writes:
>With all due respect, I do not think this belongs in -chat. It is a bug,
>and a serious departure from the behavior of other UNIX implementations;
>it really needs fixing.
>
>--Brett
>
>At 09:01 AM 10/21/98 +0200, Poul-Henning Kamp wrote:
> 
>>
>>Ok: can it!
>>
>> move this stuff to -chat or kill it.
>
>

--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
"ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Wed Oct 21 08:00:06 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA28209
          for freebsd-bugs-outgoing; Wed, 21 Oct 1998 08:00:06 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA28199
          for <freebsd-bugs@FreeBSD.org>; Wed, 21 Oct 1998 08:00:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id IAA20969;
	Wed, 21 Oct 1998 08:00:01 -0700 (PDT)
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA27962;
          Wed, 21 Oct 1998 07:57:22 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199810211457.HAA27962@hub.freebsd.org>
Date: Wed, 21 Oct 1998 07:57:22 -0700 (PDT)
From: djw@shopsite.com
To: freebsd-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: www-1.0
Subject: i386/8397: Code using popen compiled on BSDI BSD/OS 2.0 does not work on Beta 3.0
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8397
>Category:       i386
>Synopsis:       Code using popen compiled on BSDI BSD/OS 2.0 does not work on Beta 3.0
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Oct 21 08:00:00 PDT 1998
>Last-Modified:
>Originator:     Darren Whittaker
>Organization:
Open Market, Inc.
>Release:        3.x beta
>Environment:
did not have telnet access to 3.x machine
>Description:
The first popen/fgets/pclose works once but not twice. A test program
compiled on BSDI BSD/OS 2.0 will fail on freeBSD 3.x, the same program 
compiled on a 2.x freeBSD machine will work on freeBSD 3.x. The test prorgam
is a simple for loop that does a popen of the data command, displays its's
output and then does a pclose. Only the first time through the loop displays
any output. Have also found that the system function does the same thing, works
once but never again.
>How-To-Repeat:
See full dscription
>Fix:

>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Wed Oct 21 08:04:04 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA28563
          for freebsd-bugs-outgoing; Wed, 21 Oct 1998 08:04:04 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA28558
          for <bugs@FreeBSD.ORG>; Wed, 21 Oct 1998 08:04:02 -0700 (PDT)
          (envelope-from brett@lariat.org)
Received: (from brett@localhost)
	by lariat.lariat.org (8.8.8/8.8.6) id IAA14011;
	Wed, 21 Oct 1998 08:59:08 -0600 (MDT)
Message-Id: <4.1.19981021085539.066afdd0@mail.lariat.org>
X-Sender: brett@mail.lariat.org
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Wed, 21 Oct 1998 08:58:57 -0600
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
From: Brett Glass <brett@lariat.org>
Subject: Re: No terminal echo after certain commands 
Cc: "Steve Friedrich" <SteveFriedrich@Hot-Shot.com>,
        "Studded" <Studded@gorean.org>, "bugs@FreeBSD.ORG" <bugs@FreeBSD.ORG>
In-Reply-To: <28628.908981494@critter.freebsd.dk>
References: <Your message of "Wed, 21 Oct 1998 08:09:00 MDT."             <4.1.19981021080750.0674c860@mail.lariat.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

I don't think that pointing out a bug that renders one's console
unusable is "whining." Of any of the things I've mentioned thus
far, I think this is the one most clearly in need of fixing.
I'm quite surprised to see that anyone would disagree!
The behavior is both damaging to productivity and different
from what is expected, and from what other implementations do.
I think you're blowing this WAY out of proportion when what it
needs is a simple fix.

--Brett

At 04:51 PM 10/21/98 +0200, Poul-Henning Kamp wrote:
 
>
>I'm sorry, I don't belive you belong in FreeBSD, with your excessive whining,
>and complaining.  It's a serious departure from the project spirit which is
>"If it's broke, go fix it!" not "If it's broke, whine until people want to
>inflict bodily harm on you!".
>
>Poul-Henning
>
>In message <4.1.19981021080750.0674c860@mail.lariat.org>, Brett Glass writes:
>>With all due respect, I do not think this belongs in -chat. It is a bug,
>>and a serious departure from the behavior of other UNIX implementations;
>>it really needs fixing.
>>
>>--Brett
>>
>>At 09:01 AM 10/21/98 +0200, Poul-Henning Kamp wrote:
>> 
>>>
>>>Ok: can it!
>>>
>>> move this stuff to -chat or kill it.
>>
>>
>
>--
>Poul-Henning Kamp             FreeBSD coreteam member
>phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
>"ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Wed Oct 21 09:20:39 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA05872
          for freebsd-bugs-outgoing; Wed, 21 Oct 1998 09:20:39 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA05865
          for <bugs@FreeBSD.ORG>; Wed, 21 Oct 1998 09:20:34 -0700 (PDT)
          (envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id SAA28888;
	Wed, 21 Oct 1998 18:15:12 +0200 (CEST)
To: Brett Glass <brett@lariat.org>
cc: "Steve Friedrich" <SteveFriedrich@Hot-Shot.com>,
        "Studded" <Studded@gorean.org>, "bugs@FreeBSD.ORG" <bugs@FreeBSD.ORG>
Subject: Re: No terminal echo after certain commands 
In-reply-to: Your message of "Wed, 21 Oct 1998 08:58:57 MDT."
             <4.1.19981021085539.066afdd0@mail.lariat.org> 
Date: Wed, 21 Oct 1998 18:15:12 +0200
Message-ID: <28886.908986512@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


Brett, let me try one more time:

	If you want it fixed, go do it, otherwise shut up.

Poul-Henning

In message <4.1.19981021085539.066afdd0@mail.lariat.org>, Brett Glass writes:
>I don't think that pointing out a bug that renders one's console
>unusable is "whining." Of any of the things I've mentioned thus
>far, I think this is the one most clearly in need of fixing.
>I'm quite surprised to see that anyone would disagree!
>The behavior is both damaging to productivity and different
>from what is expected, and from what other implementations do.
>I think you're blowing this WAY out of proportion when what it
>needs is a simple fix.
>
>--Brett
>
>At 04:51 PM 10/21/98 +0200, Poul-Henning Kamp wrote:
> 
>>
>>I'm sorry, I don't belive you belong in FreeBSD, with your excessive whining,
>>and complaining.  It's a serious departure from the project spirit which is
>>"If it's broke, go fix it!" not "If it's broke, whine until people want to
>>inflict bodily harm on you!".
>>
>>Poul-Henning
>>
>>In message <4.1.19981021080750.0674c860@mail.lariat.org>, Brett Glass writes:
>>>With all due respect, I do not think this belongs in -chat. It is a bug,
>>>and a serious departure from the behavior of other UNIX implementations;
>>>it really needs fixing.
>>>
>>>--Brett
>>>
>>>At 09:01 AM 10/21/98 +0200, Poul-Henning Kamp wrote:
>>> 
>>>>
>>>>Ok: can it!
>>>>
>>>> move this stuff to -chat or kill it.
>>>
>>>
>>
>>--
>>Poul-Henning Kamp             FreeBSD coreteam member
>>phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
>>"ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal
>
>

--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
"ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Wed Oct 21 09:40:05 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA07691
          for freebsd-bugs-outgoing; Wed, 21 Oct 1998 09:40:05 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07684
          for <freebsd-bugs@FreeBSD.org>; Wed, 21 Oct 1998 09:40:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id JAA24421;
	Wed, 21 Oct 1998 09:40:01 -0700 (PDT)
Received: from vanmaren.aros.net (vanmaren.aros.net [208.219.24.33])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06921
          for <FreeBSD-gnats-submit@freebsd.org>; Wed, 21 Oct 1998 09:31:27 -0700 (PDT)
          (envelope-from vanmaren@vanmaren.aros.net)
Received: (from vanmaren@localhost)
	by vanmaren.aros.net (8.9.1/8.9.1) id KAA01422;
	Wed, 21 Oct 1998 10:31:18 -0600 (MDT)
	(envelope-from vanmaren)
Message-Id: <199810211631.KAA01422@vanmaren.aros.net>
Date: Wed, 21 Oct 1998 10:31:18 -0600 (MDT)
From: vanmaren@cs.utah.edu
Reply-To: vanmaren@cs.utah.edu
To: FreeBSD-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: 3.2
Subject: kern/8400: Aopen AW37Pro isn't supported by Luigi's driver
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8400
>Category:       kern
>Synopsis:       ad1848.c does not recognize the CS4235 chip.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Oct 21 09:40:01 PDT 1998
>Last-Modified:
>Originator:     Kevin Van Maren
>Organization:
University of Utah, CSL
>Release:        FreeBSD 3.0-BETA i386
>Environment:

	Luigi's driver in the latest 3.0 (and 2.2-STABLE)

FreeBSD vanmaren.aros.net 3.0-BETA FreeBSD 3.0-BETA #42: Tue Oct 20 18:21:32 MDT 1998     vanmaren@vanmaren.aros.net:/usr/src/sys/compile/VANMAREN  i386

>Description:

	The sound driver in 2.2-STABLE and 3.0-RELEASE/CURRENT
does not recognize the chip ID used in the new AOPen AW37Pro sound cards

>How-To-Repeat:

	Try to use an AOpen AW37Pro sound card.

>Fix:

Treat the CS4235 as a CS4237, used in the AW35Pro.  This is enough
to play pcm and mp3 files, at least.


Index: ad1848.c
===================================================================
RCS file: /cvs/src/sys/i386/isa/snd/ad1848.c,v
retrieving revision 1.14
diff -u -r1.14 ad1848.c
--- ad1848.c    1998/10/04 16:22:25     1.14
+++ ad1848.c    1998/10/21 16:20:04
@@ -1406,6 +1406,8 @@
        s = "CS4236" ;
     else if ( id == 0x3500630e )
        s = "CS4236B" ;
+    else if ( id == 0x2500630e )
+       s = "CS4235" ;
     else if ( id == 0x3200630e)
        s = "CS4232" ;
     else if ( id == 0x2000a865)
@@ -1416,6 +1418,8 @@
        s = "Yamaha YMF719 OPL-SA3";
     else if (vend_id == 0x8140d315)
        s = "SoundscapeVIVO";
+    else
+       printf("unknown ID: 0x%8x\n", vend_id);
     if (s) {
        struct pnp_cinfo d;
        read_pnp_parms(&d, 0);
@@ -1482,6 +1486,7 @@
            break;
 
        case 0x3700630e:        /* CS4237 */
+       case 0x2500630e:        /* CS4235 */
            tmp_d.bd_id = MD_CS4237 ;
            break;


>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Wed Oct 21 09:45:18 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA08658
          for freebsd-bugs-outgoing; Wed, 21 Oct 1998 09:45:18 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08648
          for <bugs@FreeBSD.ORG>; Wed, 21 Oct 1998 09:45:14 -0700 (PDT)
          (envelope-from winter@jurai.net)
Received: from localhost (winter@localhost)
	by sasami.jurai.net (8.8.8/8.8.7) with SMTP id MAA09796;
	Wed, 21 Oct 1998 12:44:24 -0400 (EDT)
Date: Wed, 21 Oct 1998 12:44:23 -0400 (EDT)
From: "Matthew N. Dodd" <winter@jurai.net>
To: Brett Glass <brett@lariat.org>
cc: "bugs@FreeBSD.ORG" <bugs@FreeBSD.ORG>
Subject: Re: No terminal echo after certain commands 
In-Reply-To: <4.1.19981021080750.0674c860@mail.lariat.org>
Message-ID: <Pine.BSF.4.02.9810211242070.17054-100000@sasami.jurai.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Wed, 21 Oct 1998, Brett Glass wrote:
> With all due respect, I do not think this belongs in -chat. It is a bug,
> and a serious departure from the behavior of other UNIX implementations;
> it really needs fixing.

Which other implementations?

Solaris, NetBSD, and FreeBSD all appear to behave the same when I ^C out
of '/usr/bin/more .cshrc'.  I see no differences.

'less' of course, doesn't allow the user to exit via ^C.

> At 09:01 AM 10/21/98 +0200, Poul-Henning Kamp wrote:
>  
> >
> >Ok: can it!
> >
> > move this stuff to -chat or kill it.
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-bugs" in the body of the message
> 

-- 
| Matthew N. Dodd  | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS |
| winter@jurai.net |      This Space For Rent     | ix86,sparc,m68k,pmax,vax  |
| http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage?   |


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Wed Oct 21 09:56:17 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA09726
          for freebsd-bugs-outgoing; Wed, 21 Oct 1998 09:56:17 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09721
          for <bugs@FreeBSD.ORG>; Wed, 21 Oct 1998 09:56:16 -0700 (PDT)
          (envelope-from brett@lariat.org)
Received: (from brett@localhost)
	by lariat.lariat.org (8.8.8/8.8.6) id KAA15073;
	Wed, 21 Oct 1998 10:55:40 -0600 (MDT)
Message-Id: <4.1.19981021104929.065773d0@mail.lariat.org>
X-Sender: brett@mail.lariat.org
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Wed, 21 Oct 1998 10:55:33 -0600
To: "Matthew N. Dodd" <winter@jurai.net>
From: Brett Glass <brett@lariat.org>
Subject: Re: No terminal echo after certain commands 
Cc: "bugs@FreeBSD.ORG" <bugs@FreeBSD.ORG>
In-Reply-To: <Pine.BSF.4.02.9810211242070.17054-100000@sasami.jurai.net>
References: <4.1.19981021080750.0674c860@mail.lariat.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

At 12:44 PM 10/21/98 -0400, Matthew N. Dodd wrote:
 
>On Wed, 21 Oct 1998, Brett Glass wrote:
>> With all due respect, I do not think this belongs in -chat. It is a bug,
>> and a serious departure from the behavior of other UNIX implementations;
>> it really needs fixing.
>
>Which other implementations?

Let's see. I just logged onto The WELL, whose login message says "UNIX(r) 
System V Release 4.0". ^C out of more(1) doesn't cause the terminal to
stop echoing characters. I then logged onto remarque.org, which says 
"SunOS Release 4.1.1_U1", and *it* doesn't stop echoing when I ^C out of 
more(1).

I can double-check on a few others, but frankly I have never seen this
behavior anywhere but the recent releases of FreeBSD that I've tested.

--Brett


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Wed Oct 21 10:03:35 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA10676
          for freebsd-bugs-outgoing; Wed, 21 Oct 1998 10:03:35 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10671
          for <bugs@FreeBSD.ORG>; Wed, 21 Oct 1998 10:03:33 -0700 (PDT)
          (envelope-from winter@jurai.net)
Received: from localhost (winter@localhost)
	by sasami.jurai.net (8.8.8/8.8.7) with SMTP id NAA10143;
	Wed, 21 Oct 1998 13:02:49 -0400 (EDT)
Date: Wed, 21 Oct 1998 13:02:49 -0400 (EDT)
From: "Matthew N. Dodd" <winter@jurai.net>
To: Brett Glass <brett@lariat.org>
cc: "bugs@FreeBSD.ORG" <bugs@FreeBSD.ORG>
Subject: Re: No terminal echo after certain commands 
In-Reply-To: <4.1.19981021104929.065773d0@mail.lariat.org>
Message-ID: <Pine.BSF.4.02.9810211301130.17054-100000@sasami.jurai.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Wed, 21 Oct 1998, Brett Glass wrote:
> Let's see. I just logged onto The WELL, whose login message says "UNIX(r) 
> System V Release 4.0". ^C out of more(1) doesn't cause the terminal to
> stop echoing characters. I then logged onto remarque.org, which says 
> "SunOS Release 4.1.1_U1", and *it* doesn't stop echoing when I ^C out of 
> more(1).
> 
> I can double-check on a few others, but frankly I have never seen this
> behavior anywhere but the recent releases of FreeBSD that I've tested.

I didn't observe broken behavior under FreeBSD either.

Sounds like a problem with whatever you're doing.

I ammend my previous statement that Solaris, NetBSD and FreeBSD all
exhibit the same behavior when using ^C.  NetBSD does not allow you to ^C
out of more.

-- 
| Matthew N. Dodd  | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS |
| winter@jurai.net |      This Space For Rent     | ix86,sparc,m68k,pmax,vax  |
| http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage?   |


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Wed Oct 21 11:12:24 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA18646
          for freebsd-bugs-outgoing; Wed, 21 Oct 1998 11:12:24 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA18575
          for <bugs@FreeBSD.ORG>; Wed, 21 Oct 1998 11:12:14 -0700 (PDT)
          (envelope-from brian@Awfulhak.org)
Received: from woof.lan.awfulhak.org (brian@woof.lan.awfulhak.org [172.16.0.7])
	by awfulhak.org (8.8.8/8.8.8) with ESMTP id TAA03636;
	Wed, 21 Oct 1998 19:11:38 +0100 (BST)
	(envelope-from brian@Awfulhak.org)
Received: from woof.lan.awfulhak.org (brian@localhost [127.0.0.1])
	by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id LAA01031;
	Wed, 21 Oct 1998 11:12:55 +0100 (BST)
	(envelope-from brian@woof.lan.awfulhak.org)
Message-Id: <199810211012.LAA01031@woof.lan.awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Steve Friedrich" <SteveFriedrich@Hot-Shot.com>
cc: "Brett Glass" <brett@lariat.org>, "Studded" <Studded@gorean.org>,
        "bugs@FreeBSD.ORG" <bugs@FreeBSD.ORG>
Subject: Re: No terminal echo after certain commands 
In-reply-to: Your message of "Tue, 20 Oct 1998 18:57:51 EDT."
             <199810202258.SAA25216@laker.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 21 Oct 1998 11:12:55 +0100
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> On Tue, 20 Oct 1998 15:53:13 -0600, Brett Glass wrote:
> 
> >No program should leave the console partially or completely disabled,
> >no matter how it exits. Sounds like this is a bug in "more"!
> 
> Actually, Control-C is used by a user who specifically wants to exit
> RIGHT NOW (emergency exit) with a very short path thru any code that
> could hang.  It is NOT meant as a non-emergency exit signal.

That doesn't excuse the fact that it mis-handles SIGINT.  I would 
expect SIGQUIT to exit without restoring the terminal, but SIGINT 
should DTRT.

> In short, Studded is right, you are not.

I disagree.  As it happens though, ``more'' behaves correctly under 
-current and glancing through the code doesn't show up any reasons 
why there might be a problem in either -stable or -current.

> Unix systems measure "uptime" in years, Winblows measures it in minutes.

-- 
Brian <brian@Awfulhak.org>, <brian@FreeBSD.org>, <brian@OpenBSD.org>
      <http://www.Awfulhak.org>
Don't _EVER_ lose your sense of humour....



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Wed Oct 21 11:25:20 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA19877
          for freebsd-bugs-outgoing; Wed, 21 Oct 1998 11:25:20 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19857
          for <bugs@FreeBSD.ORG>; Wed, 21 Oct 1998 11:25:16 -0700 (PDT)
          (envelope-from Studded@gorean.org)
Received: from gorean.org (Studded@localhost [127.0.0.1])
	by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id LAA18201;
	Wed, 21 Oct 1998 11:22:13 -0700 (PDT)
	(envelope-from Studded@gorean.org)
Message-ID: <362E2654.98A1A839@gorean.org>
Date: Wed, 21 Oct 1998 11:22:12 -0700
From: Studded <Studded@gorean.org>
Organization: Triborough Bridge & Tunnel Authority
X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 2.2.7-STABLE-1015 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Brian Somers <brian@Awfulhak.org>
CC: Steve Friedrich <SteveFriedrich@Hot-Shot.com>,
        Brett Glass <brett@lariat.org>, "bugs@FreeBSD.ORG" <bugs@FreeBSD.ORG>
Subject: Re: No terminal echo after certain commands
References: <199810211012.LAA01031@woof.lan.awfulhak.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Brian Somers wrote:

Someone else said:
> > In short, Studded is right, you are not.
> 
> I disagree.  As it happens though, ``more'' behaves correctly under
> -current and glancing through the code doesn't show up any reasons
> why there might be a problem in either -stable or -current.

	For the record what I actually said was that if it leaves your terminal
hosed when you ^C out of it, don't do that, and read the man page for
how to do it right. I tend to agree that more should handle INTR more
gracefully, but I also said that if brett wanted it fixed, he should fix
it. Droning on and on about it isn't useful or productive. 

Doug
-- 
***           Chief Operations Officer, DALnet IRC network          ***

    Go PADRES!

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Wed Oct 21 12:07:01 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA25739
          for freebsd-bugs-outgoing; Wed, 21 Oct 1998 12:07:01 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA25704;
          Wed, 21 Oct 1998 12:06:37 -0700 (PDT)
          (envelope-from dt@FreeBSD.org)
From: Dmitrij Tejblum <dt@FreeBSD.ORG>
Received: (from dt@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id MAA00197;
	Wed, 21 Oct 1998 12:06:34 -0700 (PDT)
Date: Wed, 21 Oct 1998 12:06:34 -0700 (PDT)
Message-Id: <199810211906.MAA00197@freefall.freebsd.org>
To: dt@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG, dt@FreeBSD.ORG
Subject: Re: kern/8383
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: msdosfs wipes out NT VFAT lower case flags

Responsible-Changed-From-To: freebsd-bugs->dt
Responsible-Changed-By: dt
Responsible-Changed-When: Wed Oct 21 12:02:45 PDT 1998
Responsible-Changed-Why: 
I will look at it.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Wed Oct 21 12:50:09 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA01062
          for freebsd-bugs-outgoing; Wed, 21 Oct 1998 12:50:09 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01051
          for <freebsd-bugs@FreeBSD.org>; Wed, 21 Oct 1998 12:50:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id MAA01913;
	Wed, 21 Oct 1998 12:50:01 -0700 (PDT)
Received: from smtp1.erols.com (smtp1.erols.com [207.172.3.234])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00618
          for <FreeBSD-gnats-submit@freebsd.org>; Wed, 21 Oct 1998 12:46:46 -0700 (PDT)
          (envelope-from shmit@natasya.noc.erols.net)
Received: from natasya.noc.erols.net (natasya.noc.erols.net [207.172.25.236])
	by smtp1.erols.com (8.8.8/8.8.5) with ESMTP id PAA08629
	for <FreeBSD-gnats-submit@freebsd.org>; Wed, 21 Oct 1998 15:46:18 -0400 (EDT)
Received: (from shmit@localhost)
	by natasya.noc.erols.net (8.9.1/8.9.1) id PAA08369;
	Wed, 21 Oct 1998 15:46:18 -0400 (EDT)
Message-Id: <199810211946.PAA08369@natasya.noc.erols.net>
Date: Wed, 21 Oct 1998 15:46:18 -0400 (EDT)
From: Brian Cully <shmit@rcn.com>
Reply-To: shmit@rcn.com
To: FreeBSD-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: 3.2
Subject: bin/8402: Add Jon Postel's birth/death to calendars.
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8402
>Category:       bin
>Synopsis:       Add Jon Postel's birth/death to calendars.
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Wed Oct 21 12:50:01 PDT 1998
>Last-Modified:
>Originator:     Brian Cully
>Organization:
>Release:        FreeBSD 3.0-CURRENT i386
>Environment:

>Description:

	Jon Postel's birth and death should be in the system calendar
	files.

>How-To-Repeat:

>Fix:
>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Wed Oct 21 13:15:28 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA04694
          for freebsd-bugs-outgoing; Wed, 21 Oct 1998 13:15:28 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from smtp2.erols.com (smtp2.erols.com [207.172.3.235])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04686
          for <bugs@FreeBSD.ORG>; Wed, 21 Oct 1998 13:15:26 -0700 (PDT)
          (envelope-from shmit@natasya.noc.erols.net)
Received: from natasya.noc.erols.net (natasya.noc.erols.net [207.172.25.236])
	by smtp2.erols.com (8.8.8/8.8.5) with ESMTP id QAA11021;
	Wed, 21 Oct 1998 16:15:02 -0400 (EDT)
Received: (from shmit@localhost)
	by natasya.noc.erols.net (8.9.1/8.9.1) id QAA08734;
	Wed, 21 Oct 1998 16:14:38 -0400 (EDT)
Message-ID: <19981021161438.D266@kublai.com>
Date: Wed, 21 Oct 1998 16:14:38 -0400
From: Brian Cully <shmit@kublai.com>
To: Brett Glass <brett@lariat.org>,
        Steve Friedrich <SteveFriedrich@Hot-Shot.com>,
        Studded <Studded@gorean.org>
Cc: "bugs@FreeBSD.ORG" <bugs@FreeBSD.ORG>
Subject: Re: No terminal echo after certain commands
Reply-To: shmit@kublai.com
References: <199810210102.VAA30851@laker.net> <4.1.19981020191601.00c54180@mail.lariat.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <4.1.19981020191601.00c54180@mail.lariat.org>; from Brett Glass on Tue, Oct 20, 1998 at 07:17:11PM -0600
X-Sender: If your mailer pays attention to this, it's broken.
X-PGP-Info: finger shmit@kublai.com for my public key.
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Tue, Oct 20, 1998 at 07:17:11PM -0600, Brett Glass wrote:
> At 09:01 PM 10/20/98 -0400, Steve Friedrich wrote:
>  
> >Unix systems measure "uptime" in years, Winblows measures it in minutes.
> 
> So, just because UNIX is more reliable than Windows (not a difficult
> feat), no one should attempt to fix bugs in it?

I think that's just a poorly delimited signature.

FWIW, the comments in main.c:quit() seem to indicate that the terminal
should be reset to a sane state on ^C (which calls quit()):

        /*
         * Put cursor at bottom left corner, clear the line,
         * reset the terminal modes, and exit.
         */

If it's not doing that, I'm sure no one will complain if you submit a
patch (or at least a reasonably detailed PR describing the circumstances
under which you see this behaviour).

-- 
Brian Cully						<shmit@rcn.com>
	They Might Be Giant's Dial-a-Song service: (718) 387-6962.
		``Free when you call from work!''

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Wed Oct 21 15:13:41 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA18828
          for freebsd-bugs-outgoing; Wed, 21 Oct 1998 15:13:41 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from mail.ikasths.dk (mail.ikasths.dk [194.182.53.3])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18812
          for <freebsd-bugs@FreeBSD.org>; Wed, 21 Oct 1998 15:13:37 -0700 (PDT)
          (envelope-from nicolai.s@mail.ikasths.dk)
Received: from a-vizion ([195.249.113.68]) by mail.ikasths.dk
          (Post.Office MTA v3.5.2 release 221 ID# 0-56697U2000L200S0V35)
          with SMTP id dk for <freebsd-bugs@FreeBSD.org>;
          Thu, 22 Oct 1998 00:20:03 +0100
Reply-To: <nicolai.sch@usa.net>
From: nicolai.s@mail.ikasths.dk (Nicolai Schlenzig)
To: <freebsd-bugs@FreeBSD.ORG>
Subject: Installation of FreeBSD 3.0-RELEASE
Date: Thu, 22 Oct 1998 00:12:35 +0200
Message-ID: <000101bdfd3f$e7f80500$6e00a8c0@a-vizion.domination.dk>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Hi,

I tried to install FreeBSD 3.0 on a clean system, with only a FAT16
partition containing the dist.

The result was that the setup was unable to find the file 'bin.mtree' which
is most likely due to the 8+3 filename convention for MS-DOS. I tried to
tamper the CHECKSUM file, but no luck.

Thanks in advance

Nicolai Schlenzig,
Denmark


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Wed Oct 21 15:23:47 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA20111
          for freebsd-bugs-outgoing; Wed, 21 Oct 1998 15:23:47 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20078
          for <bugs@FreeBSD.ORG>; Wed, 21 Oct 1998 15:23:39 -0700 (PDT)
          (envelope-from brett@lariat.org)
Received: (from brett@localhost)
	by lariat.lariat.org (8.8.8/8.8.6) id QAA18184;
	Wed, 21 Oct 1998 16:22:52 -0600 (MDT)
Message-Id: <4.1.19981021161615.00be3ef0@mail.lariat.org>
X-Sender: brett@mail.lariat.org
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Wed, 21 Oct 1998 16:22:48 -0600
To: shmit@kublai.com, Steve Friedrich <SteveFriedrich@Hot-Shot.com>,
        Studded <Studded@gorean.org>
From: Brett Glass <brett@lariat.org>
Subject: Re: No terminal echo after certain commands
Cc: "bugs@FreeBSD.ORG" <bugs@FreeBSD.ORG>
In-Reply-To: <19981021161438.D266@kublai.com>
References: <4.1.19981020191601.00c54180@mail.lariat.org>
 <199810210102.VAA30851@laker.net>
 <4.1.19981020191601.00c54180@mail.lariat.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

At 04:14 PM 10/21/98 -0400, Brian Cully wrote:
 
>FWIW, the comments in main.c:quit() seem to indicate that the terminal
>should be reset to a sane state on ^C (which calls quit()):
>
>        /*
>         * Put cursor at bottom left corner, clear the line,
>         * reset the terminal modes, and exit.
>         */
>
>If it's not doing that, I'm sure no one will complain if you submit a
>patch (or at least a reasonably detailed PR describing the circumstances
>under which you see this behaviour).

That's just what I was doing when I received this message. The interesting
thing is that the NetBSD and FreeBSD versions are almost the same, and both 
OUGHT to respond to SIGINT by executing the following code:

       /*
         * Put cursor at bottom left corner, clear the line,
         * reset the terminal modes, and exit.
         */
        quitting = 1;
        lower_left();
        clear_eol();
        deinit();
        flush();
        raw_mode(0);
        exit(0);

Where deinit() just sends the "deinitialization" terminal string from the
termcaps entry. In other words, the author DID INTEND to clean up gracefully
on SIGINT. Yet we have one report that they don't. This means that the problem 
could be in the termcaps database, in the tty driver, in I/O from signal 
handlers.... Not sure. And this is a tough one to debug, because using a 
debugger on the same terminal will (of course) mess up what's happening with 
the screen.

Suggestions on how to attack this? It looks as if the code really is not
operating as intended.

--Brett





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Wed Oct 21 23:00:04 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id XAA00649
          for freebsd-bugs-outgoing; Wed, 21 Oct 1998 23:00:04 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA00641
          for <freebsd-bugs@FreeBSD.org>; Wed, 21 Oct 1998 23:00:03 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id XAA22337;
	Wed, 21 Oct 1998 23:00:00 -0700 (PDT)
Received: from fuji.slab.ntt.co.jp (fuji.pearnet.org [204.162.42.40])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA00180
          for <FreeBSD-gnats-submit@freebsd.org>; Wed, 21 Oct 1998 22:51:00 -0700 (PDT)
          (envelope-from toyo@fuji.slab.ntt.co.jp)
Received: (from toyo@localhost)
	by fuji.slab.ntt.co.jp (8.9.1/3.7W) id OAA01404;
	Thu, 22 Oct 1998 14:50:31 +0900 (JST)
Message-Id: <199810220550.OAA01404@fuji.slab.ntt.co.jp>
Date: Thu, 22 Oct 1998 14:50:31 +0900 (JST)
From: toyo@fuji.slab.ntt.co.jp
Reply-To: toyo@fuji.slab.ntt.co.jp
To: FreeBSD-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: 3.2
Subject: bin/8405: There is extra ping.o
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8405
>Category:       bin
>Synopsis:       There is extra ping.o
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Oct 21 23:00:00 PDT 1998
>Last-Modified:
>Originator:     FUJIURA Toyonori
>Organization:
>Release:        FreeBSD 3.0-RELEASE i386
>Environment:

	
NO

>Description:

There is extra ping.o in /usr/src/sbin/ping.

>How-To-Repeat:

% ls /usr/src/sbin/ping

>Fix:
	
# rm /usr/src/sbin/ping/ping.o
>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Wed Oct 21 23:57:31 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id XAA04160
          for freebsd-bugs-outgoing; Wed, 21 Oct 1998 23:57:31 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from kbtelecom.nalnet.ru ([195.209.251.10])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA04125
          for <freebsd-bugs@FreeBSD.org>; Wed, 21 Oct 1998 23:56:59 -0700 (PDT)
          (envelope-from svd@kbtelecom.nalnet.ru)
Received: (from svd@localhost)
	by kbtelecom.nalnet.ru (8.8.8/8.8.7) id KAA14959
	for freebsd-bugs@FreeBSD.org; Thu, 22 Oct 1998 10:55:58 +0400 (MSD)
From: "Sergey V.Dorokhov" <svd@kbtelecom.nalnet.ru>
Message-Id: <199810220655.KAA14959@kbtelecom.nalnet.ru>
Subject: Bug in 3.0-RELEASE
To: freebsd-bugs@FreeBSD.ORG
Date: Thu, 22 Oct 1998 10:55:58 +0400 (MSD)
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

We has found and fixed some trouble with Aout-Shared Library compat1x.

Description:
 In file /etc/rc.conf

ldconfig_paths_aout="/usr/lib/compat/aout /usr/X11R6/lib/aout /usr/local/lib/aout"
		     ^^^^^^^^^^^^^^^^^^^^
this directory contain only 5 shared-library. All other aout-shared-library in
/usr/lib/compat.

Therefore, we need move all aout-sh-library from /usr/lib/compat
to /usr/lib/compat/aout, or add in ldconfig_paths_aout (rc.conf)
directory /usr/lib/compat.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Thu Oct 22 00:57:35 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id AAA07803
          for freebsd-bugs-outgoing; Thu, 22 Oct 1998 00:57:35 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: (from torstenb@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id AAA07780;
          Thu, 22 Oct 1998 00:57:28 -0700 (PDT)
          (envelope-from torstenb)
Date: Thu, 22 Oct 1998 00:57:28 -0700 (PDT)
From: Torsten Blum <torstenb>
Message-Id: <199810220757.AAA07780@hub.freebsd.org>
To: shmit@rcn.com, torstenb, freebsd-bugs
Subject: Re: bin/8402
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: Add Jon Postel's birth/death to calendars.

State-Changed-From-To: open-closed
State-Changed-By: torstenb
State-Changed-When: Thu Oct 22 00:56:39 PDT 1998
State-Changed-Why: 
Jon Postels birth/death has been added to calendar.birthday

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Thu Oct 22 01:04:28 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id BAA08375
          for freebsd-bugs-outgoing; Thu, 22 Oct 1998 01:04:28 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from gate.simcb.ru (gate.simcb.ru [194.135.97.3])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA08366
          for <freebsd-bugs@freebsd.org>; Thu, 22 Oct 1998 01:04:21 -0700 (PDT)
          (envelope-from john@simcb.ru)
Received: (from john@localhost)
	by gate.simcb.ru (8.9.1a/8.9.1) id MAA14421
	for freebsd-bugs@freebsd.org; Thu, 22 Oct 1998 12:03:46 +0400 (MSD)
From: john gladkih <john@simcb.ru>
Message-Id: <199810220803.MAA14421@gate.simcb.ru>
Subject: system hangs
To: freebsd-bugs@FreeBSD.ORG
Date: Thu, 22 Oct 1998 12:03:45 +0400 (MSD)
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Hi!

in short:

I use SMP kernel with dual-CPU system (HP Vectra XU 6/200), 64M RAM.

toor@gate[~]2:#> id
uid=0(toor) gid=0(wheel) groups=0(wheel), 2(kmem), 3(sys), 4(tty), 5(operator), 20(staff) 31(guest)
toor@gate[~]3:#> uname -a
FreeBSD gate.simcb.ru 3.0-19980804-SNAP FreeBSD 3.0-19980804-SNAP #0: Sat Sep 19 08:23:32
GMT 1998     john@gate.simcb.ru:/usr/src/sys/compile/PROXY-2CPU  i386
toor@gate[~]4:#> dd if=/dev/mem of=/dev/null

After 20 minutes later system was die. :-(

-- 
John, http://www.simcb.ru/~john

-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCC/CM d- s:+ a C+++ UB++++(--) P+ L- E--- W++ N++ o-- K- w--- O++(+++) 
M? V+ PS+ PE++ Y+ PGP- t+ 5+ X? R- tv? b+ DI-- D++ G e h--- r+++ y+++
------END GEEK CODE BLOCK------

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Thu Oct 22 01:46:44 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id BAA11331
          for freebsd-bugs-outgoing; Thu, 22 Oct 1998 01:46:44 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11326
          for <freebsd-bugs@FreeBSD.ORG>; Thu, 22 Oct 1998 01:46:43 -0700 (PDT)
          (envelope-from xroot@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id BAA02056;
	Thu, 22 Oct 1998 01:47:34 -0700 (PDT)
Message-Id: <199810220847.BAA02056@implode.root.com>
To: john gladkih <john@simcb.ru>
cc: freebsd-bugs@FreeBSD.ORG
Subject: Re: system hangs 
In-reply-to: Your message of "Thu, 22 Oct 1998 12:03:45 +0400."
             <199810220803.MAA14421@gate.simcb.ru> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Thu, 22 Oct 1998 01:47:33 -0700
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

>I use SMP kernel with dual-CPU system (HP Vectra XU 6/200), 64M RAM.
>
>toor@gate[~]2:#> id
>uid=0(toor) gid=0(wheel) groups=0(wheel), 2(kmem), 3(sys), 4(tty), 5(operator), 20(staff) 31(guest)
>toor@gate[~]3:#> uname -a
>FreeBSD gate.simcb.ru 3.0-19980804-SNAP FreeBSD 3.0-19980804-SNAP #0: Sat Sep 19 08:23:32
>GMT 1998     john@gate.simcb.ru:/usr/src/sys/compile/PROXY-2CPU  i386
>toor@gate[~]4:#> dd if=/dev/mem of=/dev/null
                        ^^^^^^^^
>
>After 20 minutes later system was die. :-(

   Don't do that. It's not safe to read from /dev/mem like that since it will
touch device shared memory and other things.

-DG

David Greenman
Co-founder/Principal Architect, The FreeBSD Project

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Thu Oct 22 08:57:22 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA14096
          for freebsd-bugs-outgoing; Thu, 22 Oct 1998 08:57:22 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14080;
          Thu, 22 Oct 1998 08:57:15 -0700 (PDT)
          (envelope-from wpaul@FreeBSD.org)
From: Bill Paul <wpaul@FreeBSD.ORG>
Received: (from wpaul@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id IAA24462;
	Thu, 22 Oct 1998 08:57:11 -0700 (PDT)
Date: Thu, 22 Oct 1998 08:57:11 -0700 (PDT)
Message-Id: <199810221557.IAA24462@freefall.freebsd.org>
To: Udo.Schweigert@mchp.siemens.de, wpaul@FreeBSD.ORG,
        freebsd-bugs@FreeBSD.ORG
Subject: Re: kern/8384
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: Problem with xl network driver (3c9xx cards)

State-Changed-From-To: open-closed
State-Changed-By: wpaul
State-Changed-When: Thu Oct 22 08:53:57 PDT 1998
State-Changed-Why: 

I have reverted the transmit queueing changes. I didn't encounter any
problems when I tested them here, but clearly I missed something. Sorry
for the trouble. If problems persist, please don't hesitate to contact
me or file another PR.

-Bill

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Thu Oct 22 09:20:07 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA16184
          for freebsd-bugs-outgoing; Thu, 22 Oct 1998 09:20:07 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16170
          for <freebsd-bugs@FreeBSD.org>; Thu, 22 Oct 1998 09:20:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id JAA25320;
	Thu, 22 Oct 1998 09:20:00 -0700 (PDT)
Received: from enky.mxim.com (enky.mxim.com [204.17.143.155])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA15799
          for <FreeBSD-gnats-submit@freebsd.org>; Thu, 22 Oct 1998 09:16:42 -0700 (PDT)
          (envelope-from michaele@enky.mxim.com)
Received: (from michaele@localhost)
	by enky.mxim.com (8.9.1/8.9.1) id JAA01072;
	Thu, 22 Oct 1998 09:16:42 -0700 (PDT)
	(envelope-from michaele)
Message-Id: <199810221616.JAA01072@enky.mxim.com>
Date: Thu, 22 Oct 1998 09:16:42 -0700 (PDT)
From: Michael Enkelis <michaele@enky.mxim.com>
Reply-To: michaele@enky.mxim.com
To: FreeBSD-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: 3.2
Subject: kern/8409: Small code cleanup in xl driver
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8409
>Category:       kern
>Synopsis:       Small code cleanup in xl driver
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Oct 22 09:20:00 PDT 1998
>Last-Modified:
>Originator:     Michael Enkelis
>Organization:
none
>Release:        FreeBSD 3.0-CURRENT i386
>Environment:

	N/A

>Description:

	Invalid "C" syntax in if_xl.c
	There should be a "," between "0 NULL"
	and the ":" at end of line should be ";"

>How-To-Repeat:

	compile with "FORCE_AUTONEG_TFOUR" defined.


>Fix:
On line #986 of /usr/src/sys/pci/if_xl.c:
                ifmedia_add(&sc->ifmedia, IFM_ETHER|IFM_AUTO, 0 NULL):	
                                                               ^     ^
Change to:
                ifmedia_add(&sc->ifmedia, IFM_ETHER|IFM_AUTO, 0, NULL);	

>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Thu Oct 22 09:30:07 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA17246
          for freebsd-bugs-outgoing; Thu, 22 Oct 1998 09:30:07 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17227
          for <freebsd-bugs@FreeBSD.org>; Thu, 22 Oct 1998 09:30:05 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id JAA25721;
	Thu, 22 Oct 1998 09:30:02 -0700 (PDT)
Received: from enky.mxim.com (enky.mxim.com [204.17.143.155])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16812
          for <FreeBSD-gnats-submit@freebsd.org>; Thu, 22 Oct 1998 09:26:14 -0700 (PDT)
          (envelope-from michaele@enky.mxim.com)
Received: (from michaele@localhost)
	by enky.mxim.com (8.9.1/8.9.1) id JAA01229;
	Thu, 22 Oct 1998 09:25:43 -0700 (PDT)
	(envelope-from michaele)
Message-Id: <199810221625.JAA01229@enky.mxim.com>
Date: Thu, 22 Oct 1998 09:25:43 -0700 (PDT)
From: Michael Enkelis <michaele@enky.mxim.com>
Reply-To: michaele@enky.mxim.com
To: FreeBSD-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: 3.2
Subject: kern/8412: hard to read sound card probe result.
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8412
>Category:       kern
>Synopsis:       hard to read sound card probe result.
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Oct 22 09:30:02 PDT 1998
>Last-Modified:
>Originator:     Michael Enkelis
>Organization:
N/A
>Release:        FreeBSD 3.0-CURRENT i386
>Environment:

	system with PnP OPL3 sound card and driver by  Luigi Rizzo.

>Description:

	Missing newline in OPL probe routine causes hard to
	read probe result message.

>How-To-Repeat:

	boot kernel with OPL? chipset

>Fix:
Change /usr/src/sys/i386/isa/snd/ad1848.c  Line #957
old:
	DDB(printf("set yamaha master volume to max"); )

new:
	DDB(printf("set yamaha master volume to max\n"); )


>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Thu Oct 22 09:48:17 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA19793
          for freebsd-bugs-outgoing; Thu, 22 Oct 1998 09:48:17 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19773;
          Thu, 22 Oct 1998 09:48:12 -0700 (PDT)
          (envelope-from wpaul@FreeBSD.org)
From: Bill Paul <wpaul@FreeBSD.ORG>
Received: (from wpaul@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id JAA26407;
	Thu, 22 Oct 1998 09:48:09 -0700 (PDT)
Date: Thu, 22 Oct 1998 09:48:09 -0700 (PDT)
Message-Id: <199810221648.JAA26407@freefall.freebsd.org>
To: michaele@enky.mxim.com, wpaul@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG
Subject: Re: kern/8409
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: Small code cleanup in xl driver

State-Changed-From-To: open-closed
State-Changed-By: wpaul
State-Changed-When: Thu Oct 22 09:47:35 PDT 1998
State-Changed-Why: 

Fix applied. Thanks, and sorry for the trouble.

-Bill

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Thu Oct 22 10:46:15 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA28960
          for freebsd-bugs-outgoing; Thu, 22 Oct 1998 10:46:15 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from george.lbl.gov (george.lbl.gov [131.243.2.12])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28942;
          Thu, 22 Oct 1998 10:46:13 -0700 (PDT)
          (envelope-from jin@george.lbl.gov)
Received: (from jin@localhost)
	by george.lbl.gov (8.8.8/8.8.8) id KAA29913;
	Thu, 22 Oct 1998 10:45:31 -0700 (PDT)
Date: Thu, 22 Oct 1998 10:45:31 -0700 (PDT)
From: Jin Guojun (FTG staff) <jin@george.lbl.gov>
Message-Id: <199810221745.KAA29913@george.lbl.gov>
To: hackers@FreeBSD.ORG
Subject: ld for loading dynamic library changed in 3.0-RELEASE?
Cc: bugs@FreeBSD.ORG
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


It seems that ld in 3.0-RELEASE changed its behaving.
In loading a dynamic library, it loads entire library regardless
if objects are used or not. I do not know if this is a bug or intended
goal, but it does not make sense to build libraries at this point.

Would some one please look into this issue?

Thanks,

	-Jin


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Thu Oct 22 12:01:28 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA09649
          for freebsd-bugs-outgoing; Thu, 22 Oct 1998 12:01:28 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from alpha.xerox.com (omega.Xerox.COM [13.1.64.95])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA09640
          for <bugs@freebsd.org>; Thu, 22 Oct 1998 12:01:23 -0700 (PDT)
          (envelope-from fenner@parc.xerox.com)
Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <433644(5)>; Thu, 22 Oct 1998 12:00:42 PDT
Received: from localhost by crevenia.parc.xerox.com with SMTP id <177539>; Thu, 22 Oct 1998 12:00:01 -0700
To: Brett Glass <brett@lariat.org>
cc: shmit@kublai.com, Steve Friedrich <SteveFriedrich@hot-shot.com>,
        Studded <Studded@gorean.org>, "bugs@FreeBSD.ORG" <bugs@FreeBSD.ORG>
Subject: Re: No terminal echo after certain commands 
In-reply-to: Your message of "Wed, 21 Oct 98 15:22:48 PDT."
             <4.1.19981021161615.00be3ef0@mail.lariat.org> 
Date: Thu, 22 Oct 1998 11:59:54 PDT
From: Bill Fenner <fenner@parc.xerox.com>
Message-Id: <98Oct22.120001pdt.177539@crevenia.parc.xerox.com>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

In message <4.1.19981021161615.00be3ef0@mail.lariat.org> you write:
>Suggestions on how to attack this? It looks as if the code really is not
>operating as intended.

Run "more" in one window, and run "gdb more <pid>" in another.  That
way your gdb window doesn't have to get mangled by the terminal futzing
that "more" does.

  Bill

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Thu Oct 22 12:26:16 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA13801
          for freebsd-bugs-outgoing; Thu, 22 Oct 1998 12:26:16 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from laker.net (jet.laker.net [205.245.74.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13794
          for <bugs@freebsd.org>; Thu, 22 Oct 1998 12:26:13 -0700 (PDT)
          (envelope-from sfriedri@laker.net)
Received: from nt (digital-pbi-147.laker.net [208.0.233.47]) by laker.net (8.9.0/8.9.LAKERNET.NO-SPAM.SPAMMERS.AND.RELAYS.WILL.BE.TRACKED.AND.PROSECUTED.) with SMTP id PAA19893; Thu, 22 Oct 1998 15:25:15 -0400
Message-Id: <199810221925.PAA19893@laker.net>
From: "Steve Friedrich" <SteveFriedrich@Hot-Shot.com>
To: "Bill Fenner" <fenner@parc.xerox.com>, "Brett Glass" <brett@lariat.org>
Cc: "bugs@FreeBSD.ORG" <bugs@FreeBSD.ORG>,
        "shmit@kublai.com" <shmit@kublai.com>, "Studded" <Studded@gorean.org>
Date: Thu, 22 Oct 1998 15:24:10 -0400
Reply-To: "Steve Friedrich" <SteveFriedrich@Hot-Shot.com>
X-Mailer: PMMail 98 Professional (2.01.1600) For Windows NT (4.0.1381;3)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: No terminal echo after certain commands
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Thu, 22 Oct 1998 11:59:54 PDT, Bill Fenner wrote:

>In message <4.1.19981021161615.00be3ef0@mail.lariat.org> you write:
>>Suggestions on how to attack this? It looks as if the code really is not
>>operating as intended.
>
>Run "more" in one window, and run "gdb more <pid>" in another.  That
>way your gdb window doesn't have to get mangled by the terminal futzing
>that "more" does.

A recent post indicated that this aberrant behavior does not exist in
the latest versions. I can't remember if they said 3.0R and stable, or
current??  You may want to check the archives and find out which
versions appear to not have the problem so you can try out your
testcase. Could save you from wasting your time fixing something that's
already done...

Of course, it's also a great academic exercise...
Unix systems measure "uptime" in years, Winblows measures it in minutes.



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Thu Oct 22 12:52:43 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA18586
          for freebsd-bugs-outgoing; Thu, 22 Oct 1998 12:52:43 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA18569
          for <bugs@freebsd.org>; Thu, 22 Oct 1998 12:52:41 -0700 (PDT)
          (envelope-from brett@lariat.org)
Received: (from brett@localhost)
	by lariat.lariat.org (8.8.8/8.8.6) id NAA27389;
	Thu, 22 Oct 1998 13:52:07 -0600 (MDT)
Message-Id: <4.1.19981022135102.06684cc0@mail.lariat.org>
X-Sender: brett@mail.lariat.org
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Thu, 22 Oct 1998 13:51:56 -0600
To: Bill Fenner <fenner@parc.xerox.com>
From: Brett Glass <brett@lariat.org>
Subject: Re: No terminal echo after certain commands 
Cc: shmit@kublai.com, Steve Friedrich <SteveFriedrich@hot-shot.com>,
        Studded <Studded@gorean.org>, "bugs@FreeBSD.ORG" <bugs@FreeBSD.ORG>
In-Reply-To: <98Oct22.120001pdt.177539@crevenia.parc.xerox.com>
References: <Your message of "Wed, 21 Oct 98 15:22:48 PDT."             <4.1.19981021161615.00be3ef0@mail.lariat.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

I'm not running X.... That would also introduce another variable. 
Can I do the same thing between ptys and/or virtual consoles?

--Brett

At 11:59 AM 10/22/98 -0700, Bill Fenner wrote:
 
>In message <4.1.19981021161615.00be3ef0@mail.lariat.org> you write:
>>Suggestions on how to attack this? It looks as if the code really is not
>>operating as intended.
>
>Run "more" in one window, and run "gdb more <pid>" in another.  That
>way your gdb window doesn't have to get mangled by the terminal futzing
>that "more" does.
>
>  Bill


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Thu Oct 22 13:30:06 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA24825
          for freebsd-bugs-outgoing; Thu, 22 Oct 1998 13:30:06 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24815
          for <freebsd-bugs@FreeBSD.org>; Thu, 22 Oct 1998 13:30:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id NAA03473;
	Thu, 22 Oct 1998 13:30:01 -0700 (PDT)
Date: Thu, 22 Oct 1998 13:30:01 -0700 (PDT)
Message-Id: <199810222030.NAA03473@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.ORG
From: vanmaren@fast.cs.utah.edu (Kevin Van Maren)
Subject: Re: gnu/8138: gcc -pipe xxx.s hangs
Reply-To: vanmaren@fast.cs.utah.edu (Kevin Van Maren)
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR gnu/8138; it has been noted by GNATS.

From: vanmaren@fast.cs.utah.edu (Kevin Van Maren)
To: freebsd-gnats-submit@freebsd.org, se@freebsd.org
Cc:  Subject: Re: gnu/8138: gcc -pipe xxx.s hangs
Date: Thu, 22 Oct 1998 14:20:57 -0600

 I hit this problem running configure as well.  Roland McGrath told
 me about the problem:
 
 	The problematic bit is "%{pipe:-}" in the `*asm_final:' section of the
 	specs file; remove it.
 
 I haven't tried this, though.
 
 Kevin

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Thu Oct 22 14:34:24 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA04360
          for freebsd-bugs-outgoing; Thu, 22 Oct 1998 14:34:24 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from ns2.interlinks.net (ns2.interlinks.net [207.107.160.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA04338;
          Thu, 22 Oct 1998 14:34:20 -0700 (PDT)
          (envelope-from bill@interlinks.net)
Received: from localhost (bill@localhost)
	by ns2.interlinks.net (8.9.1/8.8.8) with ESMTP id RAA04990;
	Thu, 22 Oct 1998 17:26:53 -0400 (EDT)
Date: Thu, 22 Oct 1998 17:26:52 -0400 (EDT)
From: Bill Sandiford <bill@interlinks.net>
To: freebsd-bugs@FreeBSD.ORG
cc: freebsd-isp@FreeBSD.ORG
Subject: FreeBSD 3.0 Release and pw command - Potential Bug?  (fwd)
Message-ID: <Pine.BSF.4.05.9810221726130.4502-100000@ns2.interlinks.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


We are having a problem with FreeBSD 3.0 Release and it's associated pw
command.  We have scripts that used to work perfectly in the 2.2.x line.
The script still works perfectly when we run it manually as root (logged
in at the terminal) however when cron executes the script, the pw commands
in the script don't work.  We are executing the script using the crontab
for root.  We know that the script is executing because some of the
other commands in the script are happening and working.  The script is
designed to add a new user to our system and the line with pw looks
something like this :

echo password | pw useradd username -h 0 -c "Full Name" -g group -u uid -m -d homedir

obviously we substitute a correct numeric id for uid and proper groupname
for group, etc.

We are not sure if this is a problem with our system or a bug with the pw
command that is in the 3.0 release...we have also tried invoking the
script from and inetd process as well.....we have tried this script on 3
different systems and it doesn't work on any of them except when invoked
manually.

Any help please!!!

------------------------------------------
Bill Sandiford Jr. - Systems Administrator
Interlinks - http://www.interlinks.net
sysop@interlinks.net - bill@interlinks.net
(905)404-0810




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Thu Oct 22 14:45:31 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA06037
          for freebsd-bugs-outgoing; Thu, 22 Oct 1998 14:45:31 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA06023;
          Thu, 22 Oct 1998 14:45:27 -0700 (PDT)
          (envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1])
	by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA01146;
	Thu, 22 Oct 1998 14:49:08 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199810222149.OAA01146@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Jin Guojun (FTG staff) <jin@george.lbl.gov>
cc: hackers@FreeBSD.ORG, bugs@FreeBSD.ORG
Subject: Re: ld for loading dynamic library changed in 3.0-RELEASE? 
In-reply-to: Your message of "Thu, 22 Oct 1998 10:45:31 PDT."
             <199810221745.KAA29913@george.lbl.gov> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 22 Oct 1998 14:49:07 -0700
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> 
> It seems that ld in 3.0-RELEASE changed its behaving.

Actually, it was completely replaced, so you could say it changed, yes.

> In loading a dynamic library, it loads entire library regardless
> if objects are used or not. I do not know if this is a bug or intended
> goal, but it does not make sense to build libraries at this point.

I'm sorry, but you're not making yourself very clear here.  Could you 
explain a little more?

-- 
\\  Sometimes you're ahead,       \\  Mike Smith
\\  sometimes you're behind.      \\  mike@smith.net.au
\\  The race is long, and in the  \\  msmith@freebsd.org
\\  end it's only with yourself.  \\  msmith@cdrom.com



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Thu Oct 22 15:00:06 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA08351
          for freebsd-bugs-outgoing; Thu, 22 Oct 1998 15:00:06 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08334
          for <freebsd-bugs@FreeBSD.org>; Thu, 22 Oct 1998 15:00:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id PAA05753;
	Thu, 22 Oct 1998 15:00:01 -0700 (PDT)
Received: from kakapo.pinnacle.co.nz (pinsoft.internet.co.nz [202.37.141.181])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07938
          for <FreeBSD-gnats-submit@freebsd.org>; Thu, 22 Oct 1998 14:57:39 -0700 (PDT)
          (envelope-from jonc@kakapo.pinnacle.co.nz)
Received: (from jonc@localhost)
	by kakapo.pinnacle.co.nz (8.8.8/8.8.8) id KAA03060;
	Fri, 23 Oct 1998 10:57:45 +1300 (NZDT)
	(envelope-from jonc)
Message-Id: <199810222157.KAA03060@kakapo.pinnacle.co.nz>
Date: Fri, 23 Oct 1998 10:57:45 +1300 (NZDT)
From: Jonathan Chen <jonc@pinnacle.co.nz>
Reply-To: jonc@pinnacle.co.nz
To: FreeBSD-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: 3.2
Subject: i386/8414: ibcs2 emulation sets serial baud-rate incorrectly
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8414
>Category:       i386
>Synopsis:       ibcs2 emulation sets serial baud-rate incorrectly
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Oct 22 15:00:01 PDT 1998
>Last-Modified:
>Originator:     Jonathan Chen
>Organization:
Pinnacle Software Limited
>Release:        FreeBSD 2.2.7-RELEASE i386
>Environment:

	FreeBSD 2.2.7-RELEASE on HP Netserver E-40,
		with Stallion EasyIO/8 PCI card,
		with a serial terminal @ 38400.

	Output from dmesg:
		FreeBSD 2.2.7-RELEASE #0: Thu Oct 22 15:13:09 NZDT 1998
			root@sapphire.smp-bearings.co.nz:/usr/src/sys/compile/SAPPHIRE
		CPU: Pentium Pro (199.74-MHz 686-class CPU)
		  Origin = "GenuineIntel"  Id = 0x619  Stepping=9

		Features=0xf9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV>
		real memory  = 100663296 (98304K bytes)
		avail memory = 96186368 (93932K bytes)
		Probing for devices on PCI bus 0:
		chip0 <Intel 82440FX (Natoma) PCI and memory controller> rev 2 on
		pci0:0:0
		chip1 <Intel 82371SB PCI-ISA bridge> rev 1 on pci0:4:0
		chip2 <Intel 82371SB IDE interface> rev 0 on pci0:4:1
		fxp0 <Intel EtherExpress Pro 10/100B Ethernet> rev 2 int a irq 10 on
		pci0:6:0
		fxp0: Ethernet address 00:a0:c9:a7:24:17
		ahc0 <Adaptec aic7850 SCSI host adapter> rev 1 int a irq 11 on
		pci0:7:0
		ahc0: Using left over BIOS settings
		ahc0: aic7850 Single Channel, SCSI Id=7, 3 SCBs
		ahc0 waiting for scsi devices to settle
		(ahc0:0:0): "HP 2.13GB A 50-300U VCOD" type 0 fixed SCSI 2
		sd0(ahc0:0:0): Direct-Access 2033MB (4165272 512 byte sectors)
		(ahc0:1:0): "IBM DDRS-34560 S97B" type 0 fixed SCSI 2
		sd1(ahc0:1:0): Direct-Access 4357MB (8925000 512 byte sectors)
		(ahc0:5:0): "ARCHIVE Python 28388-XXX 4.CM" type 1 removable SCSI 2
		st0(ahc0:5:0): Sequential-Access density code 0x13, 512-byte blocks,
		write-enabled
		stl0 <EasyIO-PCI> rev 1 int a irq 9 on pci0:12:0
		stl0: EasyIO-PCI (driver version 2.0.0) unit=0 nrpanels=1 nrports=8


>Description:

	SCO COFF binaries which set ioctl values of a serial device
	will always set the baud-rate to incorrect value.

>How-To-Repeat:

	..

>Fix:

	Patch to /usr/src/sys/i386/ibcs2/ibcs2_ioctl.c required. The existing
	code incorrectly inspects IBCS-termio.c_lflag for a baud-rate setting
	when it should be inspecting IBCS-termio.c_cflag.

*** ibcs2_ioctl.c.old	Fri Oct 23 10:29:59 1998
--- ibcs2_ioctl.c	Fri Oct 23 10:29:52 1998
***************
*** 188,193 ****
--- 188,194 ----
  	if (l & IBCS2_HUPCL)	r |= HUPCL;
  	if (l & IBCS2_CLOCAL)	r |= CLOCAL;
  	bt->c_cflag = r;
+ 	bt->c_ispeed = bt->c_ospeed = s2btab[l & 0x0000000f];
  
  	l = st->c_lflag;	r = 0;
  	if (l & IBCS2_ISIG)	r |= ISIG;
***************
*** 199,206 ****
  	if (l & IBCS2_NOFLSH)	r |= NOFLSH;
  	if (l & IBCS2_TOSTOP)	r |= TOSTOP;
  	bt->c_lflag = r;
- 
- 	bt->c_ispeed = bt->c_ospeed = s2btab[l & 0x0000000f];
  
  	bt->c_cc[VINTR]	=
  	    st->c_cc[IBCS2_VINTR]  ? st->c_cc[IBCS2_VINTR]  : _POSIX_VDISABLE;
--- 200,205 ----

>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Thu Oct 22 15:07:23 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA09621
          for freebsd-bugs-outgoing; Thu, 22 Oct 1998 15:07:23 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from george.lbl.gov (george.lbl.gov [131.243.2.12])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09604;
          Thu, 22 Oct 1998 15:07:19 -0700 (PDT)
          (envelope-from jin@george.lbl.gov)
Received: (from jin@localhost)
	by george.lbl.gov (8.8.8/8.8.8) id PAA07047;
	Thu, 22 Oct 1998 15:06:50 -0700 (PDT)
Date: Thu, 22 Oct 1998 15:06:50 -0700 (PDT)
From: Jin Guojun (FTG staff) <jin@george.lbl.gov>
Message-Id: <199810222206.PAA07047@george.lbl.gov>
To: mike@smith.net.au
Subject: Re: ld for loading dynamic library changed in 3.0-RELEASE?
Cc: bugs@FreeBSD.ORG, hackers@FreeBSD.ORG
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> > In loading a dynamic library, it loads entire library regardless
> > if objects are used or not. I do not know if this is a bug or intended
> > goal, but it does not make sense to build libraries at this point.
>  
> I'm sorry, but you're not making yourself very clear here.  Could you 
> explain a little more?

Let's say libtest.so containing three (3) files a.c b.c c.c.
a.c:
	a()	{ printf("a");	}

b.c:
	b()	{ b_printf("b");	}

c.c:
	c()	{ c_printf("c");	}

make them into regular library libtest.a and shared library libtest.so.

creating test file test.c:

main()
{
	a();
}

cc -o test test.c -ltest

on all platforms, this cc will be successfully compiled and linked,
but FreeBSD 3.0 complains :

libtest.so: Undefined symbol '_b_printf' referenced from text segment
libtest.so: Undefined symbol '_c_printf' referenced from text segment

However, "cc -o test test.c -static -ltest" is happy when no shared library
is used.

So, it looks like just for linking shared library.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Thu Oct 22 15:44:27 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA14897
          for freebsd-bugs-outgoing; Thu, 22 Oct 1998 15:44:27 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from lodgenet.com (cline.lodgenet.com [204.124.122.251])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA14892;
          Thu, 22 Oct 1998 15:44:24 -0700 (PDT)
          (envelope-from johnp@lodgenet.com)
Received: from milo.lodgenet.com (milo.lodgenet.com [10.0.122.42]) by lodgenet.com (8.7.5/8.7.3) with ESMTP id RAA04562; Thu, 22 Oct 1998 17:43:52 -0500
Received: from milo.lodgenet.com (localhost [127.0.0.1])
	by milo.lodgenet.com (8.9.1/8.9.1) with ESMTP id RAA03187;
	Thu, 22 Oct 1998 17:43:34 -0500 (CDT)
	(envelope-from johnp@milo.lodgenet.com)
Message-Id: <199810222243.RAA03187@milo.lodgenet.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Bill Sandiford <bill@interlinks.net>
cc: freebsd-bugs@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG
Subject: Re: FreeBSD 3.0 Release and pw command - Potential Bug? (fwd) 
In-reply-to: Your message of "Thu, 22 Oct 1998 17:26:52 EDT."
             <Pine.BSF.4.05.9810221726130.4502-100000@ns2.interlinks.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 22 Oct 1998 17:43:34 -0500
From: John Prince <johnp@lodgenet.com>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

I am not sure what your crontabs file looks like, however..
`pw' is locate in /usr/sbin.. 
Check your path..
Better yet, include it in your script.
--John

Bill Sandiford writes:
> 
> We are having a problem with FreeBSD 3.0 Release and it's associated pw
> command.  We have scripts that used to work perfectly in the 2.2.x line.
> The script still works perfectly when we run it manually as root (logged
> in at the terminal) however when cron executes the script, the pw commands
> in the script don't work.  We are executing the script using the crontab
> for root.  We know that the script is executing because some of the
> other commands in the script are happening and working.  The script is
> designed to add a new user to our system and the line with pw looks
> something like this :
> 
> echo password | pw useradd username -h 0 -c "Full Name" -g group -u uid -m -d
     homedir
> 
> obviously we substitute a correct numeric id for uid and proper groupname
> for group, etc.
> 
> We are not sure if this is a problem with our system or a bug with the pw
> command that is in the 3.0 release...we have also tried invoking the
> script from and inetd process as well.....we have tried this script on 3
> different systems and it doesn't work on any of them except when invoked
> manually.
> 
> Any help please!!!
> 
> ------------------------------------------
> Bill Sandiford Jr. - Systems Administrator
> Interlinks - http://www.interlinks.net
> sysop@interlinks.net - bill@interlinks.net
> (905)404-0810
> 
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-isp" in the body of the message
> 




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Thu Oct 22 17:00:08 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA25247
          for freebsd-bugs-outgoing; Thu, 22 Oct 1998 17:00:08 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25238
          for <freebsd-bugs@FreeBSD.org>; Thu, 22 Oct 1998 17:00:05 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id RAA08922;
	Thu, 22 Oct 1998 17:00:01 -0700 (PDT)
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA25097;
          Thu, 22 Oct 1998 16:59:07 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199810222359.QAA25097@hub.freebsd.org>
Date: Thu, 22 Oct 1998 16:59:07 -0700 (PDT)
From: ect@andrew.cmu.edu
To: freebsd-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: www-1.0
Subject: kern/8415: SMP kernel freezes while downloading large files over ppp using tun.
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8415
>Category:       kern
>Synopsis:       SMP kernel freezes while downloading large files over ppp using tun.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Oct 22 17:00:01 PDT 1998
>Last-Modified:
>Originator:     Evan C. Tsue
>Organization:
>Release:        3.0-CURRENT
>Environment:
FreeBSD molly.windsormgmt.com 3.0-CURRENT FreeBSD 3.0-CURRENT #9: Sun Oct 18 12:03:07 GMT 1998     root@molly.windsormgmt.com:/usr/src/sys/compile/MOLLY-SINGLE  i386

>Description:
When downloading a large file over ppp using the tun interface, the
SMP kernel freezes the machine.
>How-To-Repeat:
Download a large file over ppp using the tun interface on an SMP
machine.
>Fix:

>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Thu Oct 22 18:00:06 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA01858
          for freebsd-bugs-outgoing; Thu, 22 Oct 1998 18:00:06 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA01849
          for <freebsd-bugs@FreeBSD.org>; Thu, 22 Oct 1998 18:00:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id SAA10879;
	Thu, 22 Oct 1998 18:00:01 -0700 (PDT)
Received: from midten.fast.no (midten.fast.no [195.139.251.11])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA01530
          for <FreeBSD-gnats-submit@freebsd.org>; Thu, 22 Oct 1998 17:56:01 -0700 (PDT)
          (envelope-from tegge@not.fast.no)
Received: from not.fast.no (IDENT:tegge@not.fast.no [195.139.251.12])
	by midten.fast.no (8.9.1/8.9.1) with ESMTP id CAA15963
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 23 Oct 1998 02:55:30 +0200 (CEST)
Received: (from tegge@localhost)
	by not.fast.no (8.9.1/8.8.8) id CAA10512;
	Fri, 23 Oct 1998 02:55:30 +0200 (CEST)
	(envelope-from tegge@not.fast.no)
Message-Id: <199810230055.CAA10512@not.fast.no>
Date: Fri, 23 Oct 1998 02:55:30 +0200 (CEST)
From: Tor Egge <tegge@not.fast.no>
Reply-To: tegge@not.fast.no
To: FreeBSD-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: 3.2
Subject: kern/8416: vm_fault might deadlock when locking backing store vnode
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8416
>Category:       kern
>Synopsis:       vm_fault might deadlock when locking backing store vnode
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Oct 22 18:00:00 PDT 1998
>Last-Modified:
>Originator:     Tor Egge
>Organization:
Fast Search & Transfer ASA
>Release:        FreeBSD 3.0-CURRENT i386
>Environment:

FreeBSD not.fast.no 3.0-CURRENT FreeBSD 3.0-CURRENT #1: Fri Oct 23 00:39:19 CEST 1998     root@not.fast.no:/usr/src/sys/compile/NOT  i386

>Description:

A system I manage recently hung due to a user having used the ls command while
a grep process was running.

The grep program was GNU grep version 2.1, which optimizes reads by
using mmap.  The final fragment is retrieved using read.

If, during the read(), another process attempts to obtain an exclusive
lock on the vnode (e.g. via the lstat() system call performed by ls),
vm_fault() blocks when attempting to obtain a second shared lock
on the vnode (vn_read obtained the first shared lock).  Deadlock.

#0  mi_switch () at ../../kern/kern_synch.c:683
#1  0xe013a0cd in tsleep (ident=0xe1c8ae00, priority=8, 
    wmesg=0xe01c75d3 "inode", timo=0) at ../../kern/kern_synch.c:452
#2  0xe0133673 in acquire (lkp=0xe1c8ae00, extflags=16777280, wanted=1792)
    at ../../kern/kern_lock.c:152
#3  0xe013383c in lockmgr (lkp=0xe1c8ae00, flags=16973889, 
    interlkp=0xeb081648, p=0xeae88e00) at ../../kern/kern_lock.c:207
#4  0xe0157720 in vop_stdlock (ap=0xeafc3c84) at ../../kern/vfs_default.c:201
#5  0xe01cfc95 in ufs_vnoperate (ap=0xeafc3c84)
    at ../../ufs/ufs/ufs_vnops.c:2291
#6  0xe0160593 in vn_lock (vp=0xeb0815e0, flags=16973889, p=0xeae88e00)
    at vnode_if.h:811
#7  0xe0159ecf in vget (vp=0xeb0815e0, flags=16908353, p=0xeae88e00)
    at ../../kern/vfs_subr.c:1284
#8  0xe01dfa3a in vnode_pager_lock (object=0xeb031660)
    at ../../vm/vnode_pager.c:933
#9  0xe01d268a in vm_fault (map=0xeae8d440, vaddr=554504192, 
    fault_type=3 '\003', fault_flags=8) at ../../vm/vm_fault.c:246
#10 0xe01f1bd2 in trap_pfault (frame=0xeafc3dd8, usermode=0)
    at ../../i386/i386/trap.c:760
#11 0xe01f186f in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = 554504192, 
      tf_esi = -418590720, tf_ebp = -352567740, tf_isp = -352567808, 
      tf_ebx = 8192, tf_edx = -418590720, tf_ecx = 2048, tf_eax = 554512384, 
      tf_trapno = 12, tf_err = 2, tf_eip = -534838059, tf_cs = 8, 
      tf_eflags = 66054, tf_esp = 8192, tf_ss = -352567504})
    at ../../i386/i386/trap.c:399
#12 0xe01f04d5 in generic_copyout ()
#13 0xe01c8053 in ffs_read (ap=0xeafc3eec) at ../../ufs/ufs/ufs_readwrite.c:204
#14 0xe016004d in vn_read (fp=0xe1ce69c0, uio=0xeafc3f30, cred=0xe1cf8200)
    at vnode_if.h:303
#15 0xe01409fd in read (p=0xeae88e00, uap=0xeafc3f84)
    at ../../kern/sys_generic.c:121
#16 0xe01f2453 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = -541076236, 
      tf_esi = 2, tf_ebp = -541076280, tf_isp = -352567340, 
      tf_ebx = -541076224, tf_edx = 0, tf_ecx = 0, tf_eax = 3, tf_trapno = 12, 
      tf_err = 2, tf_eip = 554187896, tf_cs = 31, tf_eflags = 531, 
      tf_esp = -541076412, tf_ss = 39}) at ../../i386/i386/trap.c:1038
#17 0xe01e6e4c in Xint0x80_syscall ()
#18 0x8048519 in ?? ()


>How-To-Repeat:

>Fix:
>Audit-Trail:
>Unformatted:
>Workaround: 

Allow vm_fault to obtain a shared lock on the vnode even though an exclusive
lock has been requested (but not obtained) by a different process.

Index: kern_lock.c
===================================================================
RCS file: /home/ncvs/src/sys/kern/kern_lock.c,v
retrieving revision 1.19
diff -u -r1.19 kern_lock.c
--- kern_lock.c	1998/04/17 04:53:44	1.19
+++ kern_lock.c	1998/10/22 22:34:21
@@ -203,6 +204,12 @@
 
 	case LK_SHARED:
 		if (lkp->lk_lockholder != pid) {
+			if ((lkp->lk_flags & LK_SHARE_NONZERO) != 0 &&
+			    (flags & LK_CANRECURSE) != 0) {
+				sharelock(lkp, 1);
+				COUNT(p, 1);
+				break;
+			}
 			error = acquire(lkp, extflags,
 				LK_HAVE_EXCL | LK_WANT_EXCL | LK_WANT_UPGRADE);
 			if (error)



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Thu Oct 22 18:20:07 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA03560
          for freebsd-bugs-outgoing; Thu, 22 Oct 1998 18:20:07 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA03552
          for <freebsd-bugs@FreeBSD.org>; Thu, 22 Oct 1998 18:20:05 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id SAA11410;
	Thu, 22 Oct 1998 18:20:01 -0700 (PDT)
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA03283;
          Thu, 22 Oct 1998 18:17:24 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199810230117.SAA03283@hub.freebsd.org>
Date: Thu, 22 Oct 1998 18:17:24 -0700 (PDT)
From: cmetz@inner.net
To: freebsd-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: www-1.0
Subject: kern/8417: 3.0 config(8) doesn't check that root fs device driver is present
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8417
>Category:       kern
>Synopsis:       3.0 config(8) doesn't check that root fs device driver is present
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Oct 22 18:20:01 PDT 1998
>Last-Modified:
>Originator:     Craig Metz
>Organization:
>Release:        3.0-RELEASE
>Environment:
>Description:
config(8) should check that the arguments to:

config kernel root on <foo> dumps on <bar>

to ensure that the controllers for <foo> and <bar> are in fact present
in the config file. If they are not, config(8) works, the kernel builds,
and you get a mysterious trap on line 165 of ffs_mount (where it first
dereferences bdevsw) where it tries to access the device, but the
pointer to the driver is bogus.

At the least, config(8) should do this sanity check. It's also worth
looking into why the value of bdevsw[major(rootdev)] is bogus but not
NULL under these conditions (there may be another bug in there).

>How-To-Repeat:
Try:

config kernel root on sd0

(3.0 not having a sd0 anymore...)

>Fix:

>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Thu Oct 22 19:40:07 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA10364
          for freebsd-bugs-outgoing; Thu, 22 Oct 1998 19:40:07 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA10357
          for <freebsd-bugs@FreeBSD.org>; Thu, 22 Oct 1998 19:40:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id TAA13859;
	Thu, 22 Oct 1998 19:40:01 -0700 (PDT)
Received: from nhj.nlc.net.au (nhj.nlc.net.au [203.24.133.1])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA10226
          for <FreeBSD-gnats-submit@freebsd.org>; Thu, 22 Oct 1998 19:38:46 -0700 (PDT)
          (envelope-from root@nlc.net.au)
Received: (qmail 18307 invoked from network); 23 Oct 1998 12:38:18 +1000
Received: from monster.nlc.net.au (203.24.133.4)
  by nhj.nlc.net.au with SMTP; 23 Oct 1998 12:38:18 +1000
Received: (qmail 19721 invoked by uid 0); 23 Oct 1998 12:38:14 +1000
Message-Id: <19981023023814.19720.qmail@monster.nlc.net.au>
Date: 23 Oct 1998 12:38:14 +1000
From: john@nlc.net.au
Reply-To: john@nlc.net.au
To: FreeBSD-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: 3.2
Subject: i386/8418: sh MAKEDEV all - fails to create hard links properly
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8418
>Category:       i386
>Synopsis:       sh MAKEDEV all - fails to create hard links properly
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Oct 22 19:40:00 PDT 1998
>Last-Modified:
>Originator:     John Saunders
>Organization:
NORTHLINK COMMUNICATIONS
>Release:        FreeBSD 2.2.7-STABLE i386
>Environment:

	FreeBSD 2.2.7-STABLE cvsupped October 12th. Problem appeared
	in the process of finalizing a make world by re-running
	sh MAKEDEV all in /dev.

>Description:

	For the following MAKEDEV targets; fd, ft and st; MAKEDEV
	tries to make a hard link for several names to the one
	device node. However because an old version of the name
	exists, and the -f option isn't supplied, the link fails.
	This leaves the alternative names linked to an old device
	node. In the case that the major or minor device number
	changes for these devices, this will cause incorrect
	system operation.

>How-To-Repeat:

	In the /dev directory run "sh MAKEDEV fd0", then "ls -l fd0*".
	The device nodes fd0, fd0a, fd0b, ... fd0h should be all linked
	to the same device node (2,0). There should be a link count
	of 9. However with the bug fd0 gets re-created and fd0a ...
	fd0h are orphaned because the hard link fails. (link count is
	8 on fd0a ... fd0h, and 1 on fd0).

>Fix:
	
	The link problem exists for the fd, ft and st devices. The following
	patch corrects the problem. The patch is against this version.

	$Id: MAKEDEV,v 1.127.2.20 1998/07/06 10:59:17 des Exp $

--- /usr/src/etc/etc.i386/MAKEDEV.orig	Mon Oct 12 16:57:47 1998
+++ /usr/src/etc/etc.i386/MAKEDEV	Fri Oct 23 02:59:42 1998
@@ -342,8 +342,8 @@
 		# Fake BSD partitions
 		for i in a b c d e f g h
 		do
-			ln ${name}${unit} ${name}${unit}$i
-			ln r${name}${unit} r${name}${unit}$i
+			ln -f ${name}${unit} ${name}${unit}$i
+			ln -f r${name}${unit} r${name}${unit}$i
 		done
 		# User-readable and programmer-readable name sets
 
@@ -422,8 +422,8 @@
 	0|1|2|3)
 		mknod ${name}${unit}   b $blk `expr $unit '*' 64 + 32`
 		mknod r${name}${unit}  c $chr `expr $unit '*' 64 + 32`
-		ln ${name}${unit} ${name}${unit}a
-		ln r${name}${unit} r${name}${unit}a
+		ln -f ${name}${unit} ${name}${unit}a
+		ln -f r${name}${unit} r${name}${unit}a
 		chgrp operator ${name}${unit}* r${name}${unit}*
 		;;
 	*)
@@ -586,9 +586,9 @@
 		mknod rst${unit}.ctl c $chr `expr $unit '*' 16 + $scsictl `
 		chmod 600 rst${unit}.ctl
 
-		ln rst${unit}.0 rst${unit}
-		ln nrst${unit}.0 nrst${unit}
-		ln erst${unit}.0 erst${unit}
+		ln -f rst${unit}.0 rst${unit}
+		ln -f nrst${unit}.0 nrst${unit}
+		ln -f erst${unit}.0 erst${unit}
 		;;
 	*)
 		echo bad unit for tape in: $i

>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Thu Oct 22 19:58:09 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA11725
          for freebsd-bugs-outgoing; Thu, 22 Oct 1998 19:58:09 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from alpha.xerox.com (omega.Xerox.COM [13.1.64.95])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA11719;
          Thu, 22 Oct 1998 19:58:07 -0700 (PDT)
          (envelope-from fenner@parc.xerox.com)
Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <430465(4)>; Thu, 22 Oct 1998 19:57:34 PDT
Received: from localhost by crevenia.parc.xerox.com with SMTP id <177539>; Thu, 22 Oct 1998 19:57:28 -0700
To: Bill Sandiford <bill@interlinks.net>
cc: freebsd-bugs@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG
Subject: Re: FreeBSD 3.0 Release and pw command - Potential Bug? (fwd) 
In-reply-to: Your message of "Thu, 22 Oct 98 14:26:52 PDT."
             <Pine.BSF.4.05.9810221726130.4502-100000@ns2.interlinks.net> 
Date: Thu, 22 Oct 1998 19:57:25 PDT
From: Bill Fenner <fenner@parc.xerox.com>
Message-Id: <98Oct22.195728pdt.177539@crevenia.parc.xerox.com>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Is /usr/sbin in your $PATH when using cron?  (Check the X-Cron-Env:
headers of the email that cron sends you).

  Bill

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Thu Oct 22 21:50:05 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA19860
          for freebsd-bugs-outgoing; Thu, 22 Oct 1998 21:50:05 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA19854
          for <freebsd-bugs@FreeBSD.org>; Thu, 22 Oct 1998 21:50:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id VAA18673;
	Thu, 22 Oct 1998 21:50:01 -0700 (PDT)
Date: Thu, 22 Oct 1998 21:50:01 -0700 (PDT)
Message-Id: <199810230450.VAA18673@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.ORG
From: Donn Miller <dmm125@bellatlantic.net>
Subject: Re: i386/8370: unable to install 3.0-RELEASE from dos partition
Reply-To: Donn Miller <dmm125@bellatlantic.net>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR i386/8370; it has been noted by GNATS.

From: Donn Miller <dmm125@bellatlantic.net>
To: freebsd-gnats-submit@freebsd.org, tomas@ftp.sk
Cc:  Subject: Re: i386/8370: unable to install 3.0-RELEASE from dos partition
Date: Thu, 22 Oct 1998 23:08:55 +0000

 To install 3.0-RELEASE and 3.0-current, do this.  When booting up from a
 boot floppy, and the main menu appears, choose
 
 (4) Options
 
 Here, you can set the installation options.  Find "Release Name".  It
 may say "3.0-RELEASE".  Change it to FREEBSD, FreeBSD, or whatever you
 named the release on your DOS partition.
 
 Also, the file ERRATA.TXT or INSTALL.TXT will need updated to reflect
 this problem for both 3.0 and 3.0-current.
 
 
 Donn
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Thu Oct 22 22:10:10 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA21383
          for freebsd-bugs-outgoing; Thu, 22 Oct 1998 22:10:10 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA21357
          for <freebsd-bugs@FreeBSD.org>; Thu, 22 Oct 1998 22:10:05 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id WAA19139;
	Thu, 22 Oct 1998 22:10:01 -0700 (PDT)
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA21246;
          Thu, 22 Oct 1998 22:08:36 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199810230508.WAA21246@hub.freebsd.org>
Date: Thu, 22 Oct 1998 22:08:36 -0700 (PDT)
From: N/A@FreeBSD.ORG
To: freebsd-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: www-1.0
Subject: kern/8420: __getcwd() from an (forcibly) unmounted fs panics.
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8420
>Category:       kern
>Synopsis:       __getcwd() from an (forcibly) unmounted fs panics.
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Oct 22 22:10:00 PDT 1998
>Last-Modified:
>Originator:     Juha Nurmela
>Organization:
N/A
>Release:        3.0-19980831-SNAP
>Environment:
FreeBSD pena 3.0-19980831-SNAP
FreeBSD 3.0-19980831-SNAP #25:
Thu Oct 22 14:43:39 EEST 1998
junki@pena:/usr/src/sys/compile/PENA  i386
>Description:
Optimization to "pwd" causes a reference to bad current directory,
in kern/vfs_syscalls.c:__getcwd(), when filesystem has been
taken away by force (when changing CD's with simple scripts, for example).

>How-To-Repeat:
mount /cdrom
cd /cdrom/foo

umount -f /cdrom    # typically from another terminal, wm menu etc.

pwd                 # any command that does getcwd(3)
>Fix:
Workaround: sysctl -w debug.disablecwd=1
Probable fix: another loop termination clause to __getcwd() ?

>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Fri Oct 23 00:31:42 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id AAA02741
          for freebsd-bugs-outgoing; Fri, 23 Oct 1998 00:31:42 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from zwei.siemens.at (zwei.siemens.at [193.81.246.12])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA02735;
          Fri, 23 Oct 1998 00:31:39 -0700 (PDT)
          (envelope-from lada@pc8811.gud.siemens.at)
Received: from scesie04.sie.siemens.at (root@firix-hme0 [10.1.140.1])
	by zwei.siemens.at  with ESMTP id JAA00267;
	Fri, 23 Oct 1998 09:30:32 +0200 (MET DST)
Received: from scegud01.gud.siemens.at (scegud01.gud.siemens.at [195.3.240.30])
	by scesie04.sie.siemens.at () with ESMTP id JAA07851;
	Fri, 23 Oct 1998 09:30:29 +0200 (METDST)
Received: from pc8811.gud.siemens.at (pc8811.gud.siemens.at [195.3.22.159])
	by scegud01.gud.siemens.at (8.8.8/8.8.5) with ESMTP id JAA17370;
	Fri, 23 Oct 1998 09:30:28 +0200 (METDST)
Message-ID: <XFMail.981023093056.lada@pc8811.gud.siemens.at>
X-Mailer: XFMail 1.2 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <199810221745.KAA29913@george.lbl.gov>
Date: Fri, 23 Oct 1998 09:30:56 +0200 (CEST)
Organization: Siemens Austria AG
From: Marino Ladavac <lada@pc8811.gud.siemens.at>
To: (FTG staff) <jin@george.lbl.gov>, freebsd-hackers@FreeBSD.ORG,
        freebsd-bugs@FreeBSD.ORG
Subject: RE: ld for loading dynamic library changed in 3.0-RELEASE?
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


On 22-Oct-98 FTG staff wrote:
> 
> It seems that ld in 3.0-RELEASE changed its behaving.
> In loading a dynamic library, it loads entire library regardless
> if objects are used or not. I do not know if this is a bug or intended
> goal, but it does not make sense to build libraries at this point.

This ld.so behavior is consistent with ld.so behavior on any other U*x system
that I know and which supports the shared libraries.

dlopen/dlsym do indeed map all the entry points to the library.  But please note
that the library itself is only mapped into the address space, and the mapping
remains the same for all processes which use the same library.  Thus, the space
is not wasted.  Furthermore, only the code pages actually referenced will be
pulled into core.

> 
> Would some one please look into this issue?

If I understand you correctly, there is no issue to look at.  AFAIK, this is
an ELF requirement.

/Marino
> 
> Thanks,
> 
>       -Jin
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message

----------------------------------
Marino Ladavac
Date: 23-Oct-98
Time: 09:25:49
----------------------------------

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Fri Oct 23 01:00:06 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id BAA05042
          for freebsd-bugs-outgoing; Fri, 23 Oct 1998 01:00:06 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA05037
          for <freebsd-bugs@FreeBSD.org>; Fri, 23 Oct 1998 01:00:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id BAA24472;
	Fri, 23 Oct 1998 01:00:00 -0700 (PDT)
Date: Fri, 23 Oct 1998 01:00:00 -0700 (PDT)
Message-Id: <199810230800.BAA24472@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.ORG
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Subject: Re: i386/8414: ibcs2 emulation sets serial baud-rate incorrectly 
Reply-To: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR i386/8414; it has been noted by GNATS.

From: Poul-Henning Kamp <phk@critter.freebsd.dk>
To: jonc@pinnacle.co.nz
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: i386/8414: ibcs2 emulation sets serial baud-rate incorrectly 
Date: Fri, 23 Oct 1998 09:49:58 +0200

 I think you sent the wrong patch, didn't you ?  Or did it get truncated ?
 
 >>Fix:
 >
 >	Patch to /usr/src/sys/i386/ibcs2/ibcs2_ioctl.c required. The existing
 >	code incorrectly inspects IBCS-termio.c_lflag for a baud-rate setting
 >	when it should be inspecting IBCS-termio.c_cflag.
 >
 >*** ibcs2_ioctl.c.old	Fri Oct 23 10:29:59 1998
 >--- ibcs2_ioctl.c	Fri Oct 23 10:29:52 1998
 >***************
 >*** 188,193 ****
 >--- 188,194 ----
 >  	if (l & IBCS2_HUPCL)	r |= HUPCL;
 >  	if (l & IBCS2_CLOCAL)	r |= CLOCAL;
 >  	bt->c_cflag = r;
 >+ 	bt->c_ispeed = bt->c_ospeed = s2btab[l & 0x0000000f];
 >  
 >  	l = st->c_lflag;	r = 0;
 >  	if (l & IBCS2_ISIG)	r |= ISIG;
 >***************
 >*** 199,206 ****
 >  	if (l & IBCS2_NOFLSH)	r |= NOFLSH;
 >  	if (l & IBCS2_TOSTOP)	r |= TOSTOP;
 >  	bt->c_lflag = r;
 >- 
 >- 	bt->c_ispeed = bt->c_ospeed = s2btab[l & 0x0000000f];
 >  
 >  	bt->c_cc[VINTR]	=
 >  	    st->c_cc[IBCS2_VINTR]  ? st->c_cc[IBCS2_VINTR]  : _POSIX_VDISABLE;
 >--- 200,205 ----
 >
 >>Audit-Trail:
 >>Unformatted:
 >
 >To Unsubscribe: send mail to majordomo@FreeBSD.org
 >with "unsubscribe freebsd-bugs" in the body of the message
 >
 
 --
 Poul-Henning Kamp             FreeBSD coreteam member
 phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
 "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Fri Oct 23 03:10:58 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id DAA13393
          for freebsd-bugs-outgoing; Fri, 23 Oct 1998 03:10:58 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA13387;
          Fri, 23 Oct 1998 03:10:47 -0700 (PDT)
          (envelope-from jkh@FreeBSD.org)
From: "Jordan K. Hubbard" <jkh@FreeBSD.ORG>
Received: (from jkh@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id DAA29628;
	Fri, 23 Oct 1998 03:10:44 -0700 (PDT)
Date: Fri, 23 Oct 1998 03:10:44 -0700 (PDT)
Message-Id: <199810231010.DAA29628@freefall.freebsd.org>
To: axl@iafrica.com, jkh@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG
Subject: Re: i386/7695
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: [PATCH] rc.i386 only enables mouse support for ttyv0

State-Changed-From-To: open-closed
State-Changed-By: jkh
State-Changed-When: Fri Oct 23 03:10:36 PDT 1998
State-Changed-Why: 
fixed

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Fri Oct 23 07:26:41 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA03284
          for freebsd-bugs-outgoing; Fri, 23 Oct 1998 07:26:41 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA03279
          for <freebsd-bugs@freefall.cdrom.com>; Fri, 23 Oct 1998 07:26:39 -0700 (PDT)
          (envelope-from directresponse@cwix.com)
From: directresponse@cwix.com
Received: from mail.mia.bellsouth.net (1Cust23.tnt19.atl2.da.uu.net [153.36.120.23])
	by freefall.freebsd.org (8.8.8/8.8.5) with SMTP id HAA14288
	for <freebsd-bugs@freefall.cdrom.com>; Fri, 23 Oct 1998 07:26:30 -0700 (PDT)
Message-Id: <199810231426.HAA14288@freefall.freebsd.org>
To: <freebsd-bugs@freefall.cdrom.com>
Subject: advertisment
Date: Fri, 23 Oct 1998 12:50:01
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

This Message was Composed using Extractor Pro '98 Bulk E- Mail 
Software. If 
you wish to be removed from this advertiser's future mailings, 
please reply 
with the subject "Remove" and this software will automatically 
block you 
from their future mailings.

The person who chooses to try something and fails is a far 
greater person than the person
who chooses to try nothing and succeeds!

The difference between the successful person and the unsuccessful 
person is that the successful 
person is willing to do that which the unsuccessful person is 
not!

If you are looking to dable or window shop, this is not for you. 
Please do not respond to this message
 unless you know you have what it takes and you are truly willing 
to put in the effort to become
 successful. This Business Opportunity is for the person who is 
serious about making money, 
controling their schedule, reducing their tax liability and 
becoming financially independent!

Believe it or not the majority of people are not truly committed 
to making the financial and time 
committment it takes to achieve financial independence.  The 
question is.... are you?

If you are, you will never find a business opportunity that 
offers such a high return on your time and 
dollar investment, than we are offering here.


No Risk Guarantee!      -     Prospects Call You!

Not MLM!          Honest, Ethical Business!

See why heavy hitters are leaving there Multi-level programs 
forever.

With DESIRE & EFFORT.... YOU ABSOLUTELY CANNOT FAIL!

$8,000 - $10,000 first 4 to 8 weeks!

All you need is a telephone,  fax machine and the passion to 
succeed.

Would you take 2 minutes to find out how! CALL NOW!!!

1-800-781-7046 ext.6053
Only serious inquiries please.

I have been involved in this business for only 5 weeks and I 
cannot believe the income! I am this 
coming week ending a twenty year career.  My wife and family love 
it. They will see me more than 
ever. I've been in several MLM's and experienced moderate 
success. This is not MLM. It is a 
legitamate turn-key business with an outstanding product, 
unbelievable compensation structure, lead 
generation system and I have all the qualified leads than I can 
contact every week! The support and
 training are fantastic!
 
You owe it to yourself and your family to check it out.
Sincerely,
Jim

1-800-781-7046 ext.6053







to be removed type "remove" in the subject header and e mail back 
emailking.associates@cwix.com

sent e mail king and associates
1790 bonhill rd
mississauga on
l5t 1e1
 
 
 
 
 
 
 
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Fri Oct 23 07:53:13 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA06152
          for freebsd-bugs-outgoing; Fri, 23 Oct 1998 07:53:13 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from george.lbl.gov (george.lbl.gov [131.243.2.12])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06134;
          Fri, 23 Oct 1998 07:53:11 -0700 (PDT)
          (envelope-from jin@george.lbl.gov)
Received: (from jin@localhost)
	by george.lbl.gov (8.8.8/8.8.8) id HAA04643;
	Fri, 23 Oct 1998 07:52:41 -0700 (PDT)
Date: Fri, 23 Oct 1998 07:52:41 -0700 (PDT)
From: Jin Guojun (FTG staff) <jin@george.lbl.gov>
Message-Id: <199810231452.HAA04643@george.lbl.gov>
To: freebsd-bugs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG,
        lada@pc8811.gud.siemens.at
Subject: RE: ld for loading dynamic library changed in 3.0-RELEASE?
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> This ld.so behavior is consistent with ld.so behavior on any other U*x system
> that I know and which supports the shared libraries.

Any other Un*x systems that support the shared libraries will not have such
behavior, including FreeBSD itself. This is elf/ld issue.

> dlopen/dlsym do indeed map all the entry points to the library.  But please note
> that the library itself is only mapped into the address space, and the mapping
> remains the same for all processes which use the same library.  Thus, the space
> is not wasted.  Furthermore, only the code pages actually referenced will be
> pulled into core.
> 
> > 
> > Would some one please look into this issue?
> 
> If I understand you correctly, there is no issue to look at.  AFAIK, this is
> an ELF requirement.
> 
> /Marino

Again, this is elf/ld issue. As Mike Smith, thanks Mike, pointed out,
by setting OBJFORMAT to aout, the compiling and linking systems will use aout/*
instead elf/*, and problem goes away. This is a temp solution. As we know,
the 3.0 kernel also uses aout format. In long run, if FreeBSD will move to
use elf format in system wide range, the elf/ld behavor has to be corrected.

	-Jin

P.S.	By the way, there is another problem was found in 3.0 RELEASE,
	the aout/ld complains that the libX11.a has bag magic, even
	the file and objformat all confirmed the libX11.a is in aout format.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Fri Oct 23 10:00:06 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA19855
          for freebsd-bugs-outgoing; Fri, 23 Oct 1998 10:00:06 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA19850
          for <freebsd-bugs@FreeBSD.org>; Fri, 23 Oct 1998 10:00:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id KAA21223;
	Fri, 23 Oct 1998 10:00:00 -0700 (PDT)
Date: Fri, 23 Oct 1998 10:00:00 -0700 (PDT)
Message-Id: <199810231700.KAA21223@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.ORG
From: "Daniel M. Eischen" <eischen@vigrid.com>
Subject: Re: kern/8375: pthread_cond_wait() spins the CPU
Reply-To: "Daniel M. Eischen" <eischen@vigrid.com>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR kern/8375; it has been noted by GNATS.

From: "Daniel M. Eischen" <eischen@vigrid.com>
To: freebsd-gnats-submit@freebsd.org, info@highwind.com
Cc: jb@freebsd.org
Subject: Re: kern/8375: pthread_cond_wait() spins the CPU
Date: Fri, 23 Oct 1998 12:40:19 -0400

 This is a multi-part message in MIME format.
 
 --------------446B9B3D2781E494167EB0E7
 Content-Type: text/plain; charset=us-ascii
 Content-Transfer-Encoding: 7bit
 
 The spinlock ordering of the cond_wait and mutex structures
 can lead to a deadlock.  Also, kernel scheduling initiated
 by a SIGVTALRM can cause improper mutex and condition
 variable operation.
 
 Attach is a patch that fixes these problems and also
 makes pthread_mutex[try]lock and pthread_cond_[timed]wait
 return EDEADLK when the caller has not locked the mutex.
 
 Dan Eischen
 eischen@vigrid.com
 
 --------------446B9B3D2781E494167EB0E7
 Content-Type: text/plain; charset=us-ascii; name="uthread.diffs"
 Content-Transfer-Encoding: 7bit
 Content-Disposition: inline; filename="uthread.diffs"
 
 *** pthread_private.h.orig	Thu Oct 22 12:15:26 1998
 --- pthread_private.h	Thu Oct 22 12:16:04 1998
 ***************
 *** 446,451 ****
 --- 446,463 ----
   	/* Signal number when in state PS_SIGWAIT: */
   	int		signo;
   
 + 	/*
 + 	 * Set to non-zero when this thread has locked out thread
 + 	 * scheduling.  We allow this lock to be recursively taken.
 + 	 */
 + 	int		sched_lock;
 + 
 + 	/*
 + 	 * Set to TRUE if this thread should yield after reenabling
 + 	 * thread scheduling.
 + 	 */
 + 	int		yield_on_sched_unlock;
 + 
   	/* Miscellaneous data. */
   	char		flags;
   #define PTHREAD_EXITING		0x0100
 ***************
 *** 655,660 ****
 --- 667,674 ----
   void    _thread_kern_sched(struct sigcontext *);
   void    _thread_kern_sched_state(enum pthread_state,char *fname,int lineno);
   void    _thread_kern_set_timeout(struct timespec *);
 + void    _thread_kern_sched_lock(void);
 + void    _thread_kern_sched_unlock(void);
   void    _thread_sig_handler(int, int, struct sigcontext *);
   void    _thread_start(void);
   void    _thread_start_sig_handler(void);
 *** uthread_cond.c.orig	Sat Oct 17 19:46:57 1998
 --- uthread_cond.c	Thu Oct 22 11:44:46 1998
 ***************
 *** 137,142 ****
 --- 137,150 ----
   	 */
   	else if (*cond != NULL ||
   	    (rval = pthread_cond_init(cond,NULL)) == 0) {
 + 		/*
 + 		 * Disable thread scheduling.  If the thread blocks
 + 		 * in some way, thread scheduling is reenabled.  When
 + 		 * the thread wakes up, thread scheduling will again
 + 		 * be disabled.
 + 		 */
 + 		_thread_kern_sched_lock();
 + 
   		/* Lock the condition variable structure: */
   		_SPINLOCK(&(*cond)->lock);
   
 ***************
 *** 150,184 ****
   			 */
   			_thread_queue_enq(&(*cond)->c_queue, _thread_run);
   
 - 			/* Unlock the mutex: */
 - 			pthread_mutex_unlock(mutex);
 - 
 - 			/* Wait forever: */
 - 			_thread_run->wakeup_time.tv_sec = -1;
 - 
   			/* Unlock the condition variable structure: */
   			_SPINUNLOCK(&(*cond)->lock);
   
 ! 			/* Schedule the next thread: */
 ! 			_thread_kern_sched_state(PS_COND_WAIT,
 ! 			    __FILE__, __LINE__);
   
 ! 			/* Lock the condition variable structure: */
 ! 			_SPINLOCK(&(*cond)->lock);
   
 ! 			/* Lock the mutex: */
 ! 			rval = pthread_mutex_lock(mutex);
   			break;
   
   		/* Trap invalid condition variable types: */
   		default:
   			/* Return an invalid argument error: */
   			rval = EINVAL;
   			break;
   		}
   
 ! 	/* Unlock the condition variable structure: */
 ! 	_SPINUNLOCK(&(*cond)->lock);
   	}
   
   	/* Return the completion status: */
 --- 158,193 ----
   			 */
   			_thread_queue_enq(&(*cond)->c_queue, _thread_run);
   
   			/* Unlock the condition variable structure: */
   			_SPINUNLOCK(&(*cond)->lock);
   
 ! 			/* Unlock the mutex: */
 ! 			if (rval = pthread_mutex_unlock(mutex) == 0) {
 ! 
 ! 				/* Wait forever: */
 ! 				_thread_run->wakeup_time.tv_sec = -1;
   
 ! 				/* Schedule the next thread: */
 ! 				_thread_kern_sched_state(PS_COND_WAIT,
 ! 			 	   __FILE__, __LINE__);
   
 ! 				/* Lock the mutex: */
 ! 				rval = pthread_mutex_lock(mutex);
 ! 			}
   			break;
   
   		/* Trap invalid condition variable types: */
   		default:
 + 			/* Unlock the condition variable structure: */
 + 			_SPINUNLOCK(&(*cond)->lock);
 + 
   			/* Return an invalid argument error: */
   			rval = EINVAL;
   			break;
   		}
   
 ! 		/* Reenable thread scheduling. */
 ! 		_thread_kern_sched_unlock();
   	}
   
   	/* Return the completion status: */
 ***************
 *** 201,206 ****
 --- 210,223 ----
   	 */
   	else if (*cond != NULL ||
   	    (rval = pthread_cond_init(cond,NULL)) == 0) {
 + 		/*
 + 		 * Disable thread scheduling.  If the thread blocks
 + 		 * in some way, thread scheduling is reenabled.  When
 + 		 * the thread wakes up, thread scheduling will again
 + 		 * be disabled.
 + 		 */
 + 		_thread_kern_sched_lock();
 + 
   		/* Lock the condition variable structure: */
   		_SPINLOCK(&(*cond)->lock);
   
 ***************
 *** 221,226 ****
 --- 238,246 ----
   			 */
   			_thread_queue_enq(&(*cond)->c_queue, _thread_run);
   
 + 			/* Unlock the condition structure: */
 + 			_SPINUNLOCK(&(*cond)->lock);
 + 
   			/* Unlock the mutex: */
   			if ((rval = pthread_mutex_unlock(mutex)) != 0) {
   				/*
 ***************
 *** 230,245 ****
   				 */
   				_thread_queue_deq(&(*cond)->c_queue);
   			} else {
 - 				/* Unlock the condition variable structure: */
 - 				_SPINUNLOCK(&(*cond)->lock);
 - 
   				/* Schedule the next thread: */
   				_thread_kern_sched_state(PS_COND_WAIT,
   				    __FILE__, __LINE__);
   
 - 				/* Lock the condition variable structure: */
 - 				_SPINLOCK(&(*cond)->lock);
 - 
   				/* Lock the mutex: */
   				if ((rval = pthread_mutex_lock(mutex)) != 0) {
   				}
 --- 250,259 ----
 ***************
 *** 253,265 ****
   
   		/* Trap invalid condition variable types: */
   		default:
   			/* Return an invalid argument error: */
   			rval = EINVAL;
   			break;
   		}
   
 ! 	/* Unlock the condition variable structure: */
 ! 	_SPINUNLOCK(&(*cond)->lock);
   	}
   
   	/* Return the completion status: */
 --- 267,282 ----
   
   		/* Trap invalid condition variable types: */
   		default:
 + 			/* Unlock the condition structure: */
 + 			_SPINUNLOCK(&(*cond)->lock);
 + 
   			/* Return an invalid argument error: */
   			rval = EINVAL;
   			break;
   		}
   
 ! 		/* Reenable thread scheduling. */
 ! 		_thread_kern_sched_unlock();
   	}
   
   	/* Return the completion status: */
 ***************
 *** 276,281 ****
 --- 293,306 ----
   	if (cond == NULL || *cond == NULL)
   		rval = EINVAL;
   	else {
 + 		/*
 + 		 * Disable thread scheduling.  If the thread blocks
 + 		 * in some way, thread scheduling is reenabled.  When
 + 		 * the thread wakes up, thread scheduling will again
 + 		 * be disabled.
 + 		 */
 + 		_thread_kern_sched_lock();
 + 
   		/* Lock the condition variable structure: */
   		_SPINLOCK(&(*cond)->lock);
   
 ***************
 *** 299,304 ****
 --- 324,332 ----
   
   		/* Unlock the condition variable structure: */
   		_SPINUNLOCK(&(*cond)->lock);
 + 
 + 		/* Reenable thread scheduling. */
 + 		_thread_kern_sched_unlock();
   	}
   
   	/* Return the completion status: */
 ***************
 *** 315,320 ****
 --- 343,356 ----
   	if (cond == NULL || *cond == NULL)
   		rval = EINVAL;
   	else {
 + 		/*
 + 		 * Disable thread scheduling.  If the thread blocks
 + 		 * in some way, thread scheduling is reenabled.  When
 + 		 * the thread wakes up, thread scheduling will again
 + 		 * be disabled.
 + 		 */
 + 		_thread_kern_sched_lock();
 + 
   		/* Lock the condition variable structure: */
   		_SPINLOCK(&(*cond)->lock);
   
 ***************
 *** 342,347 ****
 --- 378,386 ----
   
   		/* Unlock the condition variable structure: */
   		_SPINUNLOCK(&(*cond)->lock);
 + 
 + 		/* Reenable thread scheduling. */
 + 		_thread_kern_sched_unlock();
   	}
   
   	/* Return the completion status: */
 *** uthread_create.c.orig	Sat Oct 17 19:46:57 1998
 --- uthread_create.c	Thu Oct 22 11:44:46 1998
 ***************
 *** 90,95 ****
 --- 90,97 ----
   			new_thread->stack = stack;
   			new_thread->start_routine = start_routine;
   			new_thread->arg = arg;
 + 			new_thread->sched_lock = 0;
 + 			new_thread->yield_on_sched_unlock = 0;
   
   			/*
   			 * Write a magic value to the thread structure
 *** uthread_kern.c.orig	Thu Oct 22 12:20:14 1998
 --- uthread_kern.c	Thu Oct 22 23:44:55 1998
 ***************
 *** 196,201 ****
 --- 196,206 ----
   		/* Check if there is a current thread: */
   		if (_thread_run != &_thread_kern_thread) {
   			/*
 + 			 * This thread no longer needs to yield the CPU.
 + 			 */
 + 			_thread_run->yield_on_sched_unlock = 0;
 + 
 + 			/*
   			 * Save the current time as the time that the thread
   			 * became inactive: 
   			 */
 ***************
 *** 1303,1307 ****
 --- 1308,1333 ----
   		}
   	}
   	return;
 + }
 + 
 + void
 + _thread_kern_sched_lock(void)
 + {
 + 	/* Allow the scheduling lock to be recursively set. */
 + 	_thread_run->sched_lock++;
 + }
 + 
 + void
 + _thread_kern_sched_unlock(void)
 + {
 + 	/* Decrement the scheduling lock count. */
 + 	_thread_run->sched_lock--;
 + 
 + 	/* Check to see if we need to yield. */
 + 	if ((_thread_run->sched_lock == 0) &&
 + 	    (_thread_run->yield_on_sched_unlock != 0)) {
 + 		_thread_run->yield_on_sched_unlock = 0;
 + 		sched_yield();
 + 	}
   }
   #endif
 *** uthread_mutex.c.orig	Sat Oct 17 19:46:58 1998
 --- uthread_mutex.c	Thu Oct 22 11:44:46 1998
 ***************
 *** 168,173 ****
 --- 168,181 ----
   	 * initialization:
   	 */
   	else if (*mutex != NULL || (ret = init_static(mutex)) == 0) {
 + 		/*
 + 		 * Disable thread scheduling.  If the thread blocks
 + 		 * in some way, thread scheduling is reenabled.  When
 + 		 * the thread wakes up, thread scheduling will again
 + 		 * be disabled.
 + 		 */
 + 		_thread_kern_sched_lock();
 + 
   		/* Lock the mutex structure: */
   		_SPINLOCK(&(*mutex)->lock);
   
 ***************
 *** 215,220 ****
 --- 223,231 ----
   
   		/* Unlock the mutex structure: */
   		_SPINUNLOCK(&(*mutex)->lock);
 + 
 + 		/* Reenable thread scheduling. */
 + 		_thread_kern_sched_unlock();
   	}
   
   	/* Return the completion status: */
 ***************
 *** 234,239 ****
 --- 245,258 ----
   	 * initialization:
   	 */
   	else if (*mutex != NULL || (ret = init_static(mutex)) == 0) {
 + 		/*
 + 		 * Disable thread scheduling.  If the thread blocks
 + 		 * in some way, thread scheduling is reenabled.  When
 + 		 * the thread wakes up, thread scheduling will again
 + 		 * be disabled.
 + 		 */
 + 		_thread_kern_sched_lock();
 + 
   		/* Lock the mutex structure: */
   		_SPINLOCK(&(*mutex)->lock);
   
 ***************
 *** 241,270 ****
   		switch ((*mutex)->m_type) {
   		/* Fast mutexes do not check for any error conditions: */
   		case MUTEX_TYPE_FAST:
 ! 			/*
 ! 			 * Enter a loop to wait for the mutex to be locked by the
 ! 			 * current thread: 
 ! 			 */
 ! 			while ((*mutex)->m_owner != _thread_run) {
 ! 				/* Check if the mutex is not locked: */
 ! 				if ((*mutex)->m_owner == NULL) {
 ! 					/* Lock the mutex for this thread: */
 ! 					(*mutex)->m_owner = _thread_run;
 ! 				} else {
 ! 					/*
 ! 					 * Join the queue of threads waiting to lock
 ! 					 * the mutex: 
 ! 					 */
 ! 					_thread_queue_enq(&(*mutex)->m_queue, _thread_run);
 ! 
 ! 					/* Unlock the mutex structure: */
 ! 					_SPINUNLOCK(&(*mutex)->lock);
 ! 
 ! 					/* Block signals: */
 ! 					_thread_kern_sched_state(PS_MUTEX_WAIT, __FILE__, __LINE__);
 ! 
 ! 					/* Lock the mutex again: */
 ! 					_SPINLOCK(&(*mutex)->lock);
   				}
   			}
   			break;
 --- 260,295 ----
   		switch ((*mutex)->m_type) {
   		/* Fast mutexes do not check for any error conditions: */
   		case MUTEX_TYPE_FAST:
 ! 			if ((*mutex)->m_owner == _thread_run)
 ! 				ret = EDEADLK;
 ! 			else {
 ! 				/*
 ! 				 * Enter a loop to wait for the mutex to be
 ! 				 * locked by the current thread: 
 ! 				 */
 ! 				while ((*mutex)->m_owner != _thread_run) {
 ! 					/* Check if the mutex is not locked: */
 ! 					if ((*mutex)->m_owner == NULL) {
 ! 						/* Lock the mutex for this thread: */
 ! 						(*mutex)->m_owner = _thread_run;
 ! 					} else {
 ! 						/*
 ! 						 * Join the queue of threads
 ! 						 * waiting to lock the mutex: 
 ! 						 */
 ! 						_thread_queue_enq(&(*mutex)->m_queue,
 ! 						    _thread_run);
 ! 
 ! 						/* Unlock the mutex structure: */
 ! 						_SPINUNLOCK(&(*mutex)->lock);
 ! 	
 ! 						/* Schedule the next thread: */
 ! 						_thread_kern_sched_state(PS_MUTEX_WAIT,
 ! 						    __FILE__, __LINE__);
 ! 
 ! 						/* Lock the mutex structure again: */
 ! 						_SPINLOCK(&(*mutex)->lock);
 ! 					}
   				}
   			}
   			break;
 ***************
 *** 283,288 ****
 --- 308,316 ----
   
   					/* Reset the lock count for this mutex: */
   					(*mutex)->m_data.m_count = 0;
 + 
 + 					/* Unlock the mutex structure: */
 + 					_SPINUNLOCK(&(*mutex)->lock);
   				} else {
   					/*
   					 * Join the queue of threads waiting to lock
 ***************
 *** 293,302 ****
   					/* Unlock the mutex structure: */
   					_SPINUNLOCK(&(*mutex)->lock);
   
 ! 					/* Block signals: */
   					_thread_kern_sched_state(PS_MUTEX_WAIT, __FILE__, __LINE__);
   
 ! 					/* Lock the mutex again: */
   					_SPINLOCK(&(*mutex)->lock);
   				}
   			}
 --- 321,330 ----
   					/* Unlock the mutex structure: */
   					_SPINUNLOCK(&(*mutex)->lock);
   
 ! 					/* Schedule the next thread: */
   					_thread_kern_sched_state(PS_MUTEX_WAIT, __FILE__, __LINE__);
   
 ! 					/* Lock the mutex structure again: */
   					_SPINLOCK(&(*mutex)->lock);
   				}
   			}
 ***************
 *** 307,319 ****
   
   		/* Trap invalid mutex types: */
   		default:
   			/* Return an invalid argument error: */
   			ret = EINVAL;
   			break;
   		}
   
 ! 		/* Unlock the mutex structure: */
 ! 		_SPINUNLOCK(&(*mutex)->lock);
   	}
   
   	/* Return the completion status: */
 --- 335,350 ----
   
   		/* Trap invalid mutex types: */
   		default:
 + 			/* Unlock the mutex structure: */
 + 			_SPINUNLOCK(&(*mutex)->lock);
 + 
   			/* Return an invalid argument error: */
   			ret = EINVAL;
   			break;
   		}
   
 ! 		/* Reenable thread scheduling. */
 ! 		_thread_kern_sched_unlock();
   	}
   
   	/* Return the completion status: */
 ***************
 *** 328,333 ****
 --- 359,372 ----
   	if (mutex == NULL || *mutex == NULL) {
   		ret = EINVAL;
   	} else {
 + 		/*
 + 		 * Disable thread scheduling.  If the thread blocks
 + 		 * in some way, thread scheduling is reenabled.  When
 + 		 * the thread wakes up, thread scheduling will again
 + 		 * be disabled.
 + 		 */
 + 		_thread_kern_sched_lock();
 + 
   		/* Lock the mutex structure: */
   		_SPINLOCK(&(*mutex)->lock);
   
 ***************
 *** 381,386 ****
 --- 420,428 ----
   
   		/* Unlock the mutex structure: */
   		_SPINUNLOCK(&(*mutex)->lock);
 + 
 + 		/* Reenable thread scheduling. */
 + 		_thread_kern_sched_unlock();
   	}
   
   	/* Return the completion status: */
 *** uthread_sig.c.orig	Thu Oct 22 12:28:16 1998
 --- uthread_sig.c	Thu Oct 22 12:14:24 1998
 ***************
 *** 115,120 ****
 --- 115,128 ----
   			yield_on_unlock_thread = 1;
   
   		/*
 + 		 * Check if the scheduler interrupt has come when
 + 		 * the currently running thread has disabled thread
 + 		 * scheduling.
 + 		 */
 + 		else if (_thread_run->sched_lock)
 + 			_thread_run->yield_on_sched_unlock = 1;
 + 
 + 		/*
   		 * Check if the kernel has not been interrupted while
   		 * executing scheduler code:
   		 */
 
 --------------446B9B3D2781E494167EB0E7--
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Fri Oct 23 10:10:10 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA20779
          for freebsd-bugs-outgoing; Fri, 23 Oct 1998 10:10:10 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA20759
          for <freebsd-bugs@FreeBSD.org>; Fri, 23 Oct 1998 10:10:05 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id KAA21533;
	Fri, 23 Oct 1998 10:10:01 -0700 (PDT)
Received: from snarf.gta.com (snarf.gta.com [199.120.225.4])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA20083
          for <FreeBSD-gnats-submit@freebsd.org>; Fri, 23 Oct 1998 10:02:29 -0700 (PDT)
          (envelope-from lab@snarf.gta.com)
Received: (from lab@localhost)
	by dual.gta.com (8.9.1/8.9.1) id LAA02013;
	Fri, 23 Oct 1998 11:39:10 -0400 (EDT)
	(envelope-from lab)
Message-Id: <199810231539.LAA02013@dual.gta.com>
Date: Fri, 23 Oct 1998 11:39:10 -0400 (EDT)
From: lab@gta.com
Reply-To: lab@gta.com
To: FreeBSD-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: 3.2
Subject: kern/8423: Intel PILA8461 NIC panics 2.2.7 during probe
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8423
>Category:       kern
>Synopsis:       Intel PILA8461 NIC panics 2.2.7 during probe
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Oct 23 10:10:00 PDT 1998
>Last-Modified:
>Originator:     Larry Baird
>Organization:
Global Technology Associates, Inc,
>Release:        FreeBSD 2.2.7-RELEASE i386
>Environment:

NOTE: This dmesg is from a boot with a working PILA8460 NIC

GNAT Box: Kernel #102 bugmaster@gnatbox.com:/GNATBOX
CPU: AMD Am5x86 Write-Back (486-class CPU)
  Origin = "AuthenticAMD"  Id = 0x4f4  Stepping=4
  Features=0x1"FPU"
real memory  = 8388608 (8192K bytes)
avail memory = 6619136 (6464K bytes)
Probing for devices on PCI bus 0:
fxp0 "Intel EtherExpress Pro 10/100B Ethernet" rev 5 int a irq 9 on pci0:12:0
fxp0: Ethernet address 00:90:27:18:d7:b8
de0 "Digital 21140A Fast Ethernet" rev 32 int a irq 12 on pci0:13:0
de0: SMC 9332BDT 21140A [10-100Mb/s] pass 2.0
de0: address 00:00:c0:5e:a1:e9
fxp1 "Intel EtherExpress Pro 10/100B Ethernet" rev 2 int a irq 10 on pci0:14:0
fxp1: Ethernet address 00:a0:c9:91:5a:ee
chip0 "generic PCI bridge (vendor=1060 device=8881 subclass=0)" rev 4 on pci0:16:0
chip1 "generic PCI bridge (vendor=1060 device=886a subclass=1)" rev 14 on pci0:18:0
pci0:18:1: UMC, device=0x673a, class=storage (ide) [no driver assigned]
Probing for devices on the ISA bus:
sc0 at 0x60-0x6f irq 1 on motherboard
sc0: VGA color "3 virtual consoles, flags=0x0"
ed0 not found at 0x280
ed1 not found at 0x300
ed2 not found at 0x320
ed3 not found at 0x340
ed4 not found at 0x360
sio0 at 0x3f8-0x3ff irq 4 on isa
sio0: type 16550A
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16550A
sio2 at 0x3e8-0x3ef irq 5 on isa
sio2: type 16550A
sio3: configured irq 9 not in bitmap of probed irqs 0
sio3 not found at 0x2e8
lpt0 at 0x378-0x37f irq 7 on isa
lpt0: Interrupt-driven port
rb0 at 0x0 drq 0 on isa
rb0/lp0: dongle
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fd0: 1.44MB 3.5in
cs0 not found at 0x300
ep0 not found at 0xffffffff
ep1 not found at 0xffffffff
ep2 not found at 0xffffffff
le0 not found at 0x300
le1 not found at 0x280
le2 not found at 0x320
le3 not found at 0x340
ze0 not found at 0x300
ze1 not found at 0x280
zp0 not found at 0x300
zp1 not found at 0x280
npx0 flags 0x1 on motherboard
npx0: INT 16 interface
de0: enabling 10baseT port

>Description:

A Intel EtherExpress PRO/100+ Managment Adapter (PILA8461) panics a
2.2.7 kernel at boot during a probe.


>How-To-Repeat:

Put a PILA8461 card in a boot.

>Fix:
	
I don't know the fix, but I have narrowed it down to the line of code
with the problem.  The problem is in the function pci_map_mem() in the
file /sys/pci/pci.c.  The size of the region to map (psize) is
calculated incorrectly.

This function uses pci_conf_read() to intialize a variable called data.

On a PILA8461 card data is set to 0x7ffff000.

Then psize is calculated using the following magic code:

#define        PCI_MAP_MEMORY_ADDRESS_MASK     0xfffffff0
	psize = -(data & PCI_MAP_MEMORY_ADDRESS_MASK);

This results in psize receiving a value of 0x80001000.

This value of psize when passed to pmap_mapdev() causes a panic.

FYI, values from a working PILA8460 card are:
   data - 0xfffff008
  psize - 0x1000



>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Fri Oct 23 10:59:14 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA25531
          for freebsd-bugs-outgoing; Fri, 23 Oct 1998 10:59:14 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from alpha.xerox.com (omega.Xerox.COM [13.1.64.95])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA25519
          for <bugs@freebsd.org>; Fri, 23 Oct 1998 10:58:59 -0700 (PDT)
          (envelope-from fenner@parc.xerox.com)
Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <430588(2)>; Fri, 23 Oct 1998 10:58:18 PDT
Received: from localhost by crevenia.parc.xerox.com with SMTP id <177539>; Fri, 23 Oct 1998 10:58:08 -0700
To: Brett Glass <brett@lariat.org>
cc: "bugs@FreeBSD.ORG" <bugs@FreeBSD.ORG>
Subject: Re: No terminal echo after certain commands 
In-reply-to: Your message of "Thu, 22 Oct 98 12:51:56 PDT."
             <4.1.19981022135102.06684cc0@mail.lariat.org> 
Date: Fri, 23 Oct 1998 10:57:55 PDT
From: Bill Fenner <fenner@parc.xerox.com>
Message-Id: <98Oct23.105808pdt.177539@crevenia.parc.xerox.com>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

In message <4.1.19981022135102.06684cc0@mail.lariat.org> you write:
>I'm not running X.... That would also introduce another variable. 
>Can I do the same thing between ptys and/or virtual consoles?

Sure, you'd just have to alt-F1 / alt-F2 to switch between the debugger
and the debugged process.

  Bill

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Fri Oct 23 12:10:05 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA01214
          for freebsd-bugs-outgoing; Fri, 23 Oct 1998 12:10:05 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01206
          for <freebsd-bugs@FreeBSD.org>; Fri, 23 Oct 1998 12:10:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id MAA26360;
	Fri, 23 Oct 1998 12:10:01 -0700 (PDT)
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA01138;
          Fri, 23 Oct 1998 12:08:56 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199810231908.MAA01138@hub.freebsd.org>
Date: Fri, 23 Oct 1998 12:08:56 -0700 (PDT)
From: cmetz@inner.net
To: freebsd-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: www-1.0
Subject: gnu/8425: 3.0's gdb can't read 3.0's kernel to debug dumps
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8425
>Category:       gnu
>Synopsis:       3.0's gdb can't read 3.0's kernel to debug dumps
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Oct 23 12:10:00 PDT 1998
>Last-Modified:
>Originator:     Craig Metz
>Organization:
>Release:        3.0-RELEASE
>Environment:
>Description:
The gdb shipped with 3.0 doesn't seem to recognize a.out anymore, and it
can't read /kernel or /var/crash/kernel.*; this makes kernel core dumps
not nearly as useful as they should be. The gdb shipped with earlier
versions of FreeBSD doesn't seem to be able to read 3.0's core dumps
either.

>How-To-Repeat:
Cause 3.0 to core dump (an exercise left to the reader)

gdb /var/crash/kernel.0

>Fix:

>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Fri Oct 23 13:00:06 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA04463
          for freebsd-bugs-outgoing; Fri, 23 Oct 1998 13:00:06 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04456
          for <freebsd-bugs@FreeBSD.org>; Fri, 23 Oct 1998 13:00:05 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id NAA27890;
	Fri, 23 Oct 1998 13:00:01 -0700 (PDT)
Date: Fri, 23 Oct 1998 13:00:01 -0700 (PDT)
Message-Id: <199810232000.NAA27890@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.ORG
From: Jin Guojun (FTG staff) <jin@george.lbl.gov>
Subject: Re: gnu/8425: 3.0's gdb can't read 3.0's kernel to debug dumps
Reply-To: Jin Guojun (FTG staff) <jin@george.lbl.gov>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR gnu/8425; it has been noted by GNATS.

From: Jin Guojun (FTG staff) <jin@george.lbl.gov>
To: cmetz@inner.net, freebsd-gnats-submit@FreeBSD.ORG
Cc:  Subject: Re: gnu/8425: 3.0's gdb can't read 3.0's kernel to debug dumps
Date: Fri, 23 Oct 1998 12:49:44 -0700 (PDT)

 It becauses that kernel uses aout format, but user space uses elf format.
 It is messy now.
 For debug kernel, go get one at ftp://ftp.lemis.com/pub/vinum/gdb-aout.
 
 	-Jin

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Fri Oct 23 16:30:07 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA22609
          for freebsd-bugs-outgoing; Fri, 23 Oct 1998 16:30:07 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA22603
          for <freebsd-bugs@FreeBSD.org>; Fri, 23 Oct 1998 16:30:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id QAA04810;
	Fri, 23 Oct 1998 16:30:01 -0700 (PDT)
Date: Fri, 23 Oct 1998 16:30:01 -0700 (PDT)
Message-Id: <199810232330.QAA04810@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.ORG
From: Dmitrij Tejblum <dima@tejblum.dnttm.rssi.ru>
Subject: Re: kern/8375: pthread_cond_wait() spins the CPU 
Reply-To: Dmitrij Tejblum <dima@tejblum.dnttm.rssi.ru>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR kern/8375; it has been noted by GNATS.

From: Dmitrij Tejblum <dima@tejblum.dnttm.rssi.ru>
To: "Daniel M. Eischen" <eischen@vigrid.com>
Cc: freebsd-gnats-submit@FreeBSD.ORG, jb@FreeBSD.ORG
Subject: Re: kern/8375: pthread_cond_wait() spins the CPU 
Date: Sat, 24 Oct 1998 03:22:31 +0400

 Daniel, 
 
 IMO, your _thread_kern_sched_[un]lock() is a bad idea. Theses functions 
 defeat the idea of spinlocks. What is the need to do _SPINLOCK/_SPINUNLOCK 
 when scheduling is blocked? Your code do it a lot. OTOH, spinlocks are 
 designed exactly to make rescheduling harmless. And they works; the only 
 problem is that spinlocks are released in a bit wrong time. (BTW, why you 
 disable scheduling in pthread_cond_signal and pthread_cond_broadcast?)
 
 The whole concept of disabling the scheduler is suspicious. There are data 
 structures, they has to be locked sometimes to provide atomic access to 
 them; why ever disable scheduling? Just lock and unlock properly...
 
 Dima
 
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Fri Oct 23 17:54:48 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA28764
          for freebsd-bugs-outgoing; Fri, 23 Oct 1998 17:54:48 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from server.pentalpha.com.hk ([202.82.29.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28758
          for <freebsd-bugs@FreeBSD.ORG>; Fri, 23 Oct 1998 17:54:45 -0700 (PDT)
          (envelope-from danny@pentalpha.com.hk)
Received: from danny (danny [10.0.0.111])
	by server.pentalpha.com.hk (8.9.1a/8.9.1) with SMTP id IAA00533
	for <freebsd-bugs@FreeBSD.ORG>; Sat, 24 Oct 1998 08:54:05 +0800 (CST)
Message-ID: <015301bdfee8$afd854e0$6f00000a@danny.pentalpha.com.hk>
From: "Danny" <danny@pentalpha.com.hk>
To: <freebsd-bugs@FreeBSD.ORG>
Subject: transmission error
Date: Sat, 24 Oct 1998 08:53:11 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="big5"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

I am using FreeBSD 2.2.7-STABLE. I just make world and rebuild the kernel.
After I rebuild the kernel and running on it, I found the following error.

/kernel: xl0: transmission error: 90

After I reboot on old kernel it is OK. However, after I rebuild the kernel
again, I got the same message again.

How can I slove it?


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Fri Oct 23 18:14:49 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA00585
          for freebsd-bugs-outgoing; Fri, 23 Oct 1998 18:14:49 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA00579
          for <bugs@freebsd.org>; Fri, 23 Oct 1998 18:14:46 -0700 (PDT)
          (envelope-from wpaul@skynet.ctr.columbia.edu)
Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id VAA03154; Fri, 23 Oct 1998 21:19:20 -0400
From: Bill Paul <wpaul@skynet.ctr.columbia.edu>
Message-Id: <199810240119.VAA03154@skynet.ctr.columbia.edu>
Subject: Re: transmission error
To: danny@pentalpha.com.hk (Danny)
Date: Fri, 23 Oct 1998 21:19:19 -0400 (EDT)
Cc: bugs@FreeBSD.ORG
In-Reply-To: <015301bdfee8$afd854e0$6f00000a@danny.pentalpha.com.hk> from "Danny" at Oct 24, 98 08:53:11 am
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Of all the gin joints in all the towns in all the world, Danny had to 
walk into mine and say:

> I am using FreeBSD 2.2.7-STABLE. I just make world and rebuild the kernel.
> After I rebuild the kernel and running on it, I found the following error.
> 
> /kernel: xl0: transmission error: 90
> 
> After I reboot on old kernel it is OK. However, after I rebuild the kernel
> again, I got the same message again.
> 
> How can I slove it?

This was my fault: I made some changes to the xl driver that broke it.
The changes were backed out yesterday and the driver should work again.
If you cvsup again to the latest FreeBSD-stable, you will get a newer
version of the xl driver which will fix the problem. If you do not want
to build the world all over again, you can do the following:

- Get a new copy of if_xl.c and if_xlreg.h from the following URL:
	http://www.freebsd.org/~wpaul/3Com/2.2
- Copy if_xl.c and if_xlreg.h to /sys/pci
- Compile and new kernel and boot it.

-Bill

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

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Fri Oct 23 20:40:09 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA09474
          for freebsd-bugs-outgoing; Fri, 23 Oct 1998 20:40:09 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA09464
          for <freebsd-bugs@FreeBSD.org>; Fri, 23 Oct 1998 20:40:05 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id UAA09998;
	Fri, 23 Oct 1998 20:40:01 -0700 (PDT)
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA09177;
          Fri, 23 Oct 1998 20:33:21 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199810240333.UAA09177@hub.freebsd.org>
Date: Fri, 23 Oct 1998 20:33:21 -0700 (PDT)
From: graphix@iastate.edu
To: freebsd-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: www-1.0
Subject: bin/8426: gprof still expects gmon.out
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8426
>Category:       bin
>Synopsis:       gprof still expects gmon.out
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Oct 23 20:40:01 PDT 1998
>Last-Modified:
>Originator:     Kent Vander Velden
>Organization:
ISU
>Release:        -current
>Environment:
FreeBSD pseudo 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Sat Oct 17 16:37:40 CDT 1998     kent@pseudo:/usr/src/sys/compile/PSEUDO  i386

>Description:
A program compiled with -pg and run will generate a file filename.gmon
but gprof still expects gmon.out to exist.

>How-To-Repeat:
/tmp|Fri10:30pm} cat > test.c
int
main(void) {
  return 0;
}
/tmp|Fri10:30pm} cc -pg -o test test.c
/tmp|Fri10:30pm} ./test
/tmp|Fri10:30pm} gprof test
gmon.out: No such file or directory
/tmp|Fri10:31pm} ls
done_articles  nbcCD7004      nbcbL7057      out            out2           out3           test*          test.c         test.gmon      vi.recover/

>Fix:

>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Fri Oct 23 21:40:08 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA13421
          for freebsd-bugs-outgoing; Fri, 23 Oct 1998 21:40:08 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13408
          for <freebsd-bugs@FreeBSD.org>; Fri, 23 Oct 1998 21:40:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id VAA11277;
	Fri, 23 Oct 1998 21:40:00 -0700 (PDT)
Date: Fri, 23 Oct 1998 21:40:00 -0700 (PDT)
Message-Id: <199810240440.VAA11277@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.ORG
From: Daniel Eischen <eischen@vigrid.com>
Subject: Re: kern/8375: pthread_cond_wait() spins the CPU
Reply-To: Daniel Eischen <eischen@vigrid.com>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR kern/8375; it has been noted by GNATS.

From: Daniel Eischen <eischen@vigrid.com>
To: dima@tejblum.dnttm.rssi.ru, eischen@vigrid.com
Cc: freebsd-gnats-submit@FreeBSD.ORG, jb@FreeBSD.ORG
Subject: Re: kern/8375: pthread_cond_wait() spins the CPU
Date: Sat, 24 Oct 1998 00:28:38 -0400 (EDT)

 > IMO, your _thread_kern_sched_[un]lock() is a bad idea. Theses functions 
 > defeat the idea of spinlocks. What is the need to do _SPINLOCK/_SPINUNLOCK 
 > when scheduling is blocked? Your code do it a lot. OTOH, spinlocks are 
 > designed exactly to make rescheduling harmless. And they works; the only 
 > problem is that spinlocks are released in a bit wrong time. (BTW, why you 
 > disable scheduling in pthread_cond_signal and pthread_cond_broadcast?)
 
 I don't see any other way of making pthread_cond_[timed]wait     
 bulletproof without disabling scheduling.  You shouldn't    
 allow nesting of spinlocks being taken if there is a chance
 of creating a deadlock.  Let's assume that you do not nest
 the condition variable and mutex spinlocks.  Then pthread_cond_wait
 looks something like this:
 
 		/* Lock the condition variable structure: */
 		_SPINLOCK(&(*cond)->lock);
 
 		/* Process according to condition variable type: */
 		switch ((*cond)->c_type) {
 		/* Fast condition variable: */
 		case COND_TYPE_FAST:
 			/* Set the wakeup time: */
 			_thread_run->wakeup_time.tv_sec = abstime->tv_sec;
 			_thread_run->wakeup_time.tv_nsec = abstime->tv_nsec;
 
 			/* Reset the timeout flag: */
 			_thread_run->timeout = 0;
 
 			/*
 			 * Queue the running thread for the condition
 			 * variable:
 			 */
 			_thread_queue_enq(&(*cond)->c_queue, _thread_run);
 
 			/* Unlock the condition variable structure: */
 			_SPINUNLOCK(&(*cond)->lock);
 
 			/* Unlock the mutex: */
 			if ((rval = pthread_mutex_unlock(mutex)) != 0) {
 
 What happens if you get a SIGVTALRM right after the spinunlock
 of the condition lock and before the pthread_mutex_lock?  Another
 thread can get scheduled and possibly dequeue the thread that
 you just placed on the condition variable queue.  When this
 thread comes back and unlocks the mutex, his state will change
 to PS_COND_WAIT but he'll never be woken up because he's not 
 in the queue anymore.
 
 You need to disable thread scheduling.  The way I've done it,
 it doesn't hurt anything and will prevent needless thrashing
 of threads.  You want mutex_lock and cond_wait and friends
 to be atomic and this does that without needless thrashing.
 Note that _thread_kern_sched_lock will *not* block scheduling
 when the thread waits during a spinlock or other blocking
 operations that invoke the thread scheduler.
 
 > The whole concept of disabling the scheduler is suspicious. There are data 
 > structures, they has to be locked sometimes to provide atomic access to 
 > them; why ever disable scheduling? Just lock and unlock properly...
 
 Sure, where you can.  BTW, I didn't invent this idea myself.
 I stole it from VxWorks and it has the same semantics as
 taskLock and taskUnlock do in VxWorks.  This is also how
 pthread_mutex_lock and pthread_cond_wait are implemented.
 
 Perhaps I was a little overzealous in my usage of _thread_kern_sched_lock
 in pthread_cond_signal and pthread_cond_broadcast.  They are
 probably not needed there, but they would let the operation
 continue without causing needless thrashing.
 
 I didn't take out the spinlocks because I thought they would
 work across processes, whereas locking out thread scheduling,
 at least as implemented here, only works within the process.
 
 Dan Eischen
 eischen@vigrid.com

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Fri Oct 23 21:50:07 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA14218
          for freebsd-bugs-outgoing; Fri, 23 Oct 1998 21:50:07 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14202
          for <freebsd-bugs@FreeBSD.org>; Fri, 23 Oct 1998 21:50:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id VAA11503;
	Fri, 23 Oct 1998 21:50:00 -0700 (PDT)
Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13450
          for <FreeBSD-gnats-submit@freebsd.org>; Fri, 23 Oct 1998 21:40:16 -0700 (PDT)
          (envelope-from gdonl@tsc.tdk.com)
Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191])
	by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id VAA22897
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 23 Oct 1998 21:39:45 -0700 (PDT)
	(envelope-from gdonl@tsc.tdk.com)
Received: from w3.gv.tsc.tdk.com (gdonl@w3.gv.tsc.tdk.com [192.168.240.195])
	by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id VAA10612
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 23 Oct 1998 21:39:43 -0700 (PDT)
Received: (from gdonl@localhost)
	by w3.gv.tsc.tdk.com (8.8.8/8.8.5) id VAA14919;
	Fri, 23 Oct 1998 21:39:22 -0700 (PDT)
Message-Id: <199810240439.VAA14919@w3.gv.tsc.tdk.com>
Date: Fri, 23 Oct 1998 21:39:22 -0700 (PDT)
From: Don Lewis <Don.Lewis@tsc.tdk.com>
Reply-To: gdonl@tsc.tdk.com
To: FreeBSD-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: 3.2
Subject: bin/8427: [PATCH] fsdb buglet
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8427
>Category:       bin
>Synopsis:       [PATCH] fsdb buglet
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Oct 23 21:50:00 PDT 1998
>Last-Modified:
>Originator:     Don Lewis
>Organization:
TDK Semiconductor
>Release:        FreeBSD 3.0-CURRENT
>Environment:

	FreeBSD 2.1 through 3.0

>Description:

	There is a minor bug in the CMDFUNCSTART() routine in fsdb.
	The code accidentally happens to compile and run correctly because
	it finds an unrelated variable declaration in fsck.h that just
	happens to have a type that makes the code work.

	This bug needs to be fixed before Kirk McKusick's softupdates
	aware fsck can be integrated.

>How-To-Repeat:


>Fix:
	

--- fsdb/fsdb.c.orig	Mon Jun 15 00:12:19 1998
+++ fsdb/fsdb.c	Fri Oct 23 18:12:24 1998
@@ -617,7 +617,7 @@
 	return 1;
     type = curinode->di_mode & IFMT;
     for (tp = typenamemap;
-	 tp < &typenamemap[sizeof(typemap)/sizeof(*typemap)];
+	 tp < &typenamemap[sizeof(typenamemap)/sizeof(*typenamemap)];
 	 tp++) {
 	if (!strcmp(argv[1], tp->typename)) {
 	    printf("setting type to %s\n", tp->typename);
@@ -625,7 +625,7 @@
 	    break;
 	}
     }
-    if (tp == &typenamemap[sizeof(typemap)/sizeof(*typemap)]) {
+    if (tp == &typenamemap[sizeof(typenamemap)/sizeof(*typenamemap)]) {
 	warnx("type `%s' not known", argv[1]);
 	warnx("try one of `file', `dir', `socket', `fifo'");
 	return 1;
>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Fri Oct 23 21:50:07 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA14220
          for freebsd-bugs-outgoing; Fri, 23 Oct 1998 21:50:07 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14205
          for <freebsd-bugs@FreeBSD.org>; Fri, 23 Oct 1998 21:50:05 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id VAA11508;
	Fri, 23 Oct 1998 21:50:01 -0700 (PDT)
Date: Fri, 23 Oct 1998 21:50:01 -0700 (PDT)
Message-Id: <199810240450.VAA11508@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.ORG
From: Daniel Eischen <eischen@vigrid.com>
Subject: Re: kern/8375: pthread_cond_wait() spins the CPU
Reply-To: Daniel Eischen <eischen@vigrid.com>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR kern/8375; it has been noted by GNATS.

From: Daniel Eischen <eischen@vigrid.com>
To: dima@tejblum.dnttm.rssi.ru, eischen@vigrid.com
Cc: freebsd-gnats-submit@FreeBSD.ORG, jb@FreeBSD.ORG
Subject: Re: kern/8375: pthread_cond_wait() spins the CPU
Date: Sat, 24 Oct 1998 00:46:23 -0400 (EDT)

 BTW, pthread_mutex_lock also has the same problem as
 pthread_cond_wait if thread scheduling comes at an
 inopportune time:
 
 		_SPINLOCK(&(*mutex)->lock);
 
 		/* Process according to mutex type: */
 		switch ((*mutex)->m_type) {
 		/* Fast mutexes do not check for any error conditions: */
 		case MUTEX_TYPE_FAST:
 			/*
 			 * Enter a loop to wait for the mutex to be locked by the
 			 * current thread: 
 			 */
 			while ((*mutex)->m_owner != _thread_run) {
 				/* Check if the mutex is not locked: */
 				if ((*mutex)->m_owner == NULL) {
 					/* Lock the mutex for this thread: */
 					(*mutex)->m_owner = _thread_run;
 				} else {
 					/*
 					 * Join the queue of threads waiting to lock
 					 * the mutex: 
 					 */
 					_thread_queue_enq(&(*mutex)->m_queue, _thread_run);
 
 					/* Unlock the mutex structure: */
 					_SPINUNLOCK(&(*mutex)->lock);
 
 					/* Block signals: */
 					_thread_kern_sched_state(PS_MUTEX_WAIT, __FILE__, __LINE__);
 
 If thread scheduling is kicked off right after the last
 SPINUNLOCK, then you can also have a thread removed
 from the mutex queue, but it'll never get woken up.
 
 Dan Eischen
 eischen@vigrid.com

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Fri Oct 23 22:00:07 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA15196
          for freebsd-bugs-outgoing; Fri, 23 Oct 1998 22:00:07 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA15186
          for <freebsd-bugs@FreeBSD.org>; Fri, 23 Oct 1998 22:00:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id WAA11825;
	Fri, 23 Oct 1998 22:00:00 -0700 (PDT)
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA14541;
          Fri, 23 Oct 1998 21:52:40 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199810240452.VAA14541@hub.freebsd.org>
Date: Fri, 23 Oct 1998 21:52:40 -0700 (PDT)
From: zhu@router.rdcps.ac.cn
To: freebsd-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: www-1.0
Subject: kern/8428: Is FreeBSD 3.0-RELEASE support 640MByte MO disk?
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8428
>Category:       kern
>Synopsis:       Is FreeBSD 3.0-RELEASE support 640MByte MO disk?
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Oct 23 22:00:00 PDT 1998
>Last-Modified:
>Originator:     Zhu Peng
>Organization:
RDCPS, ISCAS, China.
>Release:        3.0-RELEASE
>Environment:
FreeBSD 3.0-RELEASE, i586
>Description:

 I can not mount 640MB MO disks for its 2048 B/sector.
 There is a patch for 2.2.6-RELEASE, and can it be used on 3.0-RELEASE?
>How-To-Repeat:

mail
>Fix:

>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Fri Oct 23 22:00:07 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA15200
          for freebsd-bugs-outgoing; Fri, 23 Oct 1998 22:00:07 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA15188
          for <freebsd-bugs@FreeBSD.org>; Fri, 23 Oct 1998 22:00:05 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id WAA11830;
	Fri, 23 Oct 1998 22:00:01 -0700 (PDT)
Date: Fri, 23 Oct 1998 22:00:01 -0700 (PDT)
Message-Id: <199810240500.WAA11830@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.ORG
From: John Birrell  <jb@cimlogic.com.au>
Subject: Re: kern/8375: pthread_cond_wait() spins the CPU
Reply-To: John Birrell  <jb@cimlogic.com.au>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR kern/8375; it has been noted by GNATS.

From: John Birrell  <jb@cimlogic.com.au>
To: eischen@vigrid.com (Daniel Eischen)
Cc: dima@tejblum.dnttm.rssi.ru, eischen@vigrid.com,
        freebsd-gnats-submit@FreeBSD.ORG, jb@FreeBSD.ORG
Subject: Re: kern/8375: pthread_cond_wait() spins the CPU
Date: Sat, 24 Oct 1998 15:02:14 +1000 (EST)

 Daniel Eischen wrote:
 > BTW, pthread_mutex_lock also has the same problem as
 > pthread_cond_wait if thread scheduling comes at an
 > inopportune time:
 [...]
 > 					 * Join the queue of threads waiting to lock
 > 					 * the mutex: 
 > 					 */
 > 					_thread_queue_enq(&(*mutex)->m_queue, _thread_run);
 > 
 > 					/* Unlock the mutex structure: */
 > 					_SPINUNLOCK(&(*mutex)->lock);
 > 
 > 					/* Block signals: */
 > 					_thread_kern_sched_state(PS_MUTEX_WAIT, __FILE__, __LINE__);
 > 
 > If thread scheduling is kicked off right after the last
 > SPINUNLOCK, then you can also have a thread removed
 > from the mutex queue, but it'll never get woken up.
 
 The simple solution to this is to change the thread state to PS_MUTEX_WAIT
 while the mutex is locked, then enter the scheduler without changing the
 state. I don't think that the problem is one of locking - just the
 possibility that the thread state will be overwritten at an inoportune
 time (i.e. the thread state may be changed to PS_RUNNING before it
 gets a chance to set it's state to PS_MUTEX_WAIT).
 
 
 -- 
 John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/
 CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Fri Oct 23 22:10:07 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA16160
          for freebsd-bugs-outgoing; Fri, 23 Oct 1998 22:10:07 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA16154
          for <freebsd-bugs@FreeBSD.org>; Fri, 23 Oct 1998 22:10:05 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id WAA12093;
	Fri, 23 Oct 1998 22:10:01 -0700 (PDT)
Received: from shell6.ba.best.com (shell6.ba.best.com [206.184.139.137])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA15695
          for <FreeBSD-gnats-submit@freebsd.org>; Fri, 23 Oct 1998 22:03:28 -0700 (PDT)
          (envelope-from jkb@shell6.ba.best.com)
Received: (from jkb@localhost)
	by shell6.ba.best.com (8.9.0/8.9.0/best.sh) id WAA25980;
	Fri, 23 Oct 1998 22:01:48 -0700 (PDT)
Message-Id: <199810240501.WAA25980@shell6.ba.best.com>
Date: Fri, 23 Oct 1998 22:01:48 -0700 (PDT)
From: jkb@best.com
Reply-To: jkb@FreeBSD.ORG
To: FreeBSD-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: 3.2
Subject: misc/8429: typo in tcpdump man page 
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8429
>Category:       misc
>Synopsis:       typo in tcpdump man page
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Oct 23 22:10:01 PDT 1998
>Last-Modified:
>Originator:     Jan B. Koum
>Organization:
>Release:        FreeBSD 2.2.7-STABLE i386
>Environment:

	2.2 and 3.0

>Description:

	From tcpdump man page:

	To   print   all   ICMP   packets   that   are   not  echo
	requests/replies (i.e., not ping packets):
                tcpdump 'icmp[0] != 8 and icmp[0] != 0"
                       ^^^                           ^^^

>How-To-Repeat:

	man tcpdump
	Try to follow the example:

rafraf# tcpdump 'icmp[0] != 8 and icmp[0] != 0"
Unmatched '.

	Make sure both are " ' " 

rafraf# tcpdump 'icmp[0] != 8 and icmp[0] != 0'
tcpdump: listening on xl0
21:54:43.368414 192.168.1.100 > rafraf: icmp: time exceeded in-transit [tos 0xc0]
21:54:43.424888 192.168.1.100 > rafraf: icmp: time exceeded in-transit [tos 0xc0]

>Fix:

	Change
              tcpdump 'icmp[0] != 8 and icmp[0] != 0"
	to
              tcpdump 'icmp[0] != 8 and icmp[0] != 0'

>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Fri Oct 23 22:40:07 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA17966
          for freebsd-bugs-outgoing; Fri, 23 Oct 1998 22:40:07 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA17958
          for <freebsd-bugs@FreeBSD.org>; Fri, 23 Oct 1998 22:40:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id WAA12725;
	Fri, 23 Oct 1998 22:40:00 -0700 (PDT)
Received: from shell6.ba.best.com (shell6.ba.best.com [206.184.139.137])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA17518
          for <FreeBSD-gnats-submit@freebsd.org>; Fri, 23 Oct 1998 22:30:11 -0700 (PDT)
          (envelope-from jkb@shell6.ba.best.com)
Received: (from jkb@localhost)
	by shell6.ba.best.com (8.9.0/8.9.0/best.sh) id WAA28633;
	Fri, 23 Oct 1998 22:28:46 -0700 (PDT)
Message-Id: <199810240528.WAA28633@shell6.ba.best.com>
Date: Fri, 23 Oct 1998 22:28:46 -0700 (PDT)
From: jkb@best.com
Reply-To: jkb@FreeBSD.ORG
To: FreeBSD-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: 3.2
Subject: misc/8430: tcpdump man page typos
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8430
>Category:       misc
>Synopsis:       tcpdump man page typos
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Oct 23 22:40:00 PDT 1998
>Last-Modified:
>Originator:     Jan B. Koum
>Organization:
>Release:        FreeBSD 2.2.7-STABLE i386
>Environment:

	2.2 and 3.0 systems

>Description:


	tcpdump man page "SEE ALSO" section point to non-existent
	man pages.

	SEE ALSO
       	traffic(1C), nit(4P), bpf(4), pcap(3)

	We don't have traffic and nit ones.

>How-To-Repeat:

	man tcpdump
	/SEE ALSO

>Fix:

	Delete traffic(1C) and nit(4P)?
>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Sat Oct 24 03:09:26 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id DAA29635
          for freebsd-bugs-outgoing; Sat, 24 Oct 1998 03:09:26 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA29628;
          Sat, 24 Oct 1998 03:09:18 -0700 (PDT)
          (envelope-from thepish@FreeBSD.org)
From: Peter Hawkins <thepish@FreeBSD.ORG>
Received: (from thepish@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id DAA18023;
	Sat, 24 Oct 1998 03:09:15 -0700 (PDT)
Date: Sat, 24 Oct 1998 03:09:15 -0700 (PDT)
Message-Id: <199810241009.DAA18023@freefall.freebsd.org>
To: jkb@FreeBSD.ORG, thepish@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG
Subject: Re: misc/8429
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: typo in tcpdump man page

State-Changed-From-To: open-closed
State-Changed-By: thepish
State-Changed-When: Sat Oct 24 03:08:52 PDT 1998
State-Changed-Why: 
applied

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Sat Oct 24 05:00:06 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id FAA07231
          for freebsd-bugs-outgoing; Sat, 24 Oct 1998 05:00:06 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA07217
          for <freebsd-bugs@FreeBSD.org>; Sat, 24 Oct 1998 05:00:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id FAA23686;
	Sat, 24 Oct 1998 05:00:00 -0700 (PDT)
Date: Sat, 24 Oct 1998 05:00:00 -0700 (PDT)
Message-Id: <199810241200.FAA23686@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.ORG
From: Dmitrij Tejblum <dima@tejblum.dnttm.rssi.ru>
Subject: Re: kern/8375: pthread_cond_wait() spins the CPU 
Reply-To: Dmitrij Tejblum <dima@tejblum.dnttm.rssi.ru>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR kern/8375; it has been noted by GNATS.

From: Dmitrij Tejblum <dima@tejblum.dnttm.rssi.ru>
To: Daniel Eischen <eischen@vigrid.com>
Cc: freebsd-gnats-submit@FreeBSD.ORG, jb@FreeBSD.ORG
Subject: Re: kern/8375: pthread_cond_wait() spins the CPU 
Date: Sat, 24 Oct 1998 15:49:13 +0400

 Daniel Eischen wrote:
 > I don't see any other way of making pthread_cond_[timed]wait     
 > bulletproof without disabling scheduling.  You shouldn't    
 > allow nesting of spinlocks being taken if there is a chance
 > of creating a deadlock.  Let's assume that you do not nest
 > the condition variable and mutex spinlocks.  
 
 Why? Frankly, I don't see any harm here. Sure, it is not safe to 
 _SPINUNLOCK the condition lock before pthread_mutex_unlock. So it has to be 
 done in other way around.
 
 > You need to disable thread scheduling.  The way I've done it,
 > it doesn't hurt anything and will prevent needless thrashing
 > of threads.  You want mutex_lock and cond_wait and friends
 > to be atomic and this does that without needless thrashing.
 
 I don't think the "trashing" is dangerous. Spinlocks are held due to very 
 short period of time (this is the main assumption in their design and 
 implementation). The chances that a thread holding a spinlock will be 
 preempted are very low. Even if the thread will be preempted, the chances 
 that another thread will try to lock the same spinlock are low.
 
 Dima
 
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Sat Oct 24 05:00:06 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id FAA07232
          for freebsd-bugs-outgoing; Sat, 24 Oct 1998 05:00:06 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA07219
          for <freebsd-bugs@FreeBSD.org>; Sat, 24 Oct 1998 05:00:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id FAA23691;
	Sat, 24 Oct 1998 05:00:01 -0700 (PDT)
Date: Sat, 24 Oct 1998 05:00:01 -0700 (PDT)
Message-Id: <199810241200.FAA23691@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.ORG
From: Dmitrij Tejblum <dima@tejblum.dnttm.rssi.ru>
Subject: Re: kern/8375: pthread_cond_wait() spins the CPU 
Reply-To: Dmitrij Tejblum <dima@tejblum.dnttm.rssi.ru>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR kern/8375; it has been noted by GNATS.

From: Dmitrij Tejblum <dima@tejblum.dnttm.rssi.ru>
To: John Birrell <jb@cimlogic.com.au>
Cc: eischen@vigrid.com (Daniel Eischen), freebsd-gnats-submit@FreeBSD.ORG,
        jb@FreeBSD.ORG
Subject: Re: kern/8375: pthread_cond_wait() spins the CPU 
Date: Sat, 24 Oct 1998 15:49:22 +0400

 John Birrell wrote:
 > Daniel Eischen wrote:
 > > BTW, pthread_mutex_lock also has the same problem as
 > > pthread_cond_wait if thread scheduling comes at an
 > > inopportune time:
 > [...]
 > > 					 * Join the queue of threads waiting to lock
 > > 					 * the mutex: 
 > > 					 */
 > > 					_thread_queue_enq(&(*mutex)->m_queue, _thread_run);
 > > 
 > > 					/* Unlock the mutex structure: */
 > > 					_SPINUNLOCK(&(*mutex)->lock);
 > > 
 > > 					/* Block signals: */
 > > 					_thread_kern_sched_state(PS_MUTEX_WAIT, __FILE__, __LINE__);
 > > 
 > > If thread scheduling is kicked off right after the last
 > > SPINUNLOCK, then you can also have a thread removed
 > > from the mutex queue, but it'll never get woken up.
 > 
 > The simple solution to this is to change the thread state to PS_MUTEX_WAIT
 > while the mutex is locked, then enter the scheduler without changing the
             ^^^^^ spinlock?
 > state. I don't think that the problem is one of locking - just the
 > possibility that the thread state will be overwritten at an inoportune
 > time (i.e. the thread state may be changed to PS_RUNNING before it
 > gets a chance to set it's state to PS_MUTEX_WAIT).
 
 IMO, is this _SPINUNLOCK is too early or changing the thread state is too late 
 is not that important :-). Anyway, I would suggest to add 'spinlock_t *' 
 parameter to _thread_kern_sched_state. _thread_kern_sched_state would set 
 the state, unlock the spinlock and enter the scheduler. This would be useful 
 in quite a lot of places. (Richard Seaman sent a patch with a similar idea, but 
 I don't like something in it).
 
 Dima
 
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Sat Oct 24 05:40:07 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id FAA08982
          for freebsd-bugs-outgoing; Sat, 24 Oct 1998 05:40:07 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA08977
          for <freebsd-bugs@FreeBSD.org>; Sat, 24 Oct 1998 05:40:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id FAA24654;
	Sat, 24 Oct 1998 05:40:00 -0700 (PDT)
Date: Sat, 24 Oct 1998 05:40:00 -0700 (PDT)
Message-Id: <199810241240.FAA24654@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.ORG
From: Daniel Eischen <eischen@vigrid.com>
Subject: Re: kern/8375: pthread_cond_wait() spins the CPU
Reply-To: Daniel Eischen <eischen@vigrid.com>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR kern/8375; it has been noted by GNATS.

From: Daniel Eischen <eischen@vigrid.com>
To: dima@tejblum.dnttm.rssi.ru, jb@cimlogic.com.au
Cc: eischen@vigrid.com, freebsd-gnats-submit@FreeBSD.ORG, jb@FreeBSD.ORG
Subject: Re: kern/8375: pthread_cond_wait() spins the CPU
Date: Sat, 24 Oct 1998 08:30:57 -0400 (EDT)

 > IMO, is this _SPINUNLOCK is too early or changing the thread state is too late 
 > is not that important :-). Anyway, I would suggest to add 'spinlock_t *' 
 > parameter to _thread_kern_sched_state. _thread_kern_sched_state would set 
 > the state, unlock the spinlock and enter the scheduler. This would be useful 
 > in quite a lot of places. (Richard Seaman sent a patch with a similar idea, but 
 > I don't like something in it).
 
 I don't like that idea because it adds complication.  It's not
 necessary in most cases.  The thread schedule locking is
 very simple and could be more generally useful in the future
 for other things.
 
 Dan Eischen
 eischen@vigrid.com

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Sat Oct 24 06:10:08 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA10831
          for freebsd-bugs-outgoing; Sat, 24 Oct 1998 06:10:08 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA10826
          for <freebsd-bugs@FreeBSD.org>; Sat, 24 Oct 1998 06:10:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id GAA25085;
	Sat, 24 Oct 1998 06:10:01 -0700 (PDT)
Date: Sat, 24 Oct 1998 06:10:01 -0700 (PDT)
Message-Id: <199810241310.GAA25085@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.ORG
From: Daniel Eischen <eischen@vigrid.com>
Subject: Re: kern/8375: pthread_cond_wait() spins the CPU
Reply-To: Daniel Eischen <eischen@vigrid.com>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR kern/8375; it has been noted by GNATS.

From: Daniel Eischen <eischen@vigrid.com>
To: eischen@vigrid.com, jb@cimlogic.com.au
Cc: dima@tejblum.dnttm.rssi.ru, freebsd-gnats-submit@FreeBSD.ORG,
        jb@FreeBSD.ORG
Subject: Re: kern/8375: pthread_cond_wait() spins the CPU
Date: Sat, 24 Oct 1998 08:52:45 -0400 (EDT)

 > > If thread scheduling is kicked off right after the last
 > > SPINUNLOCK, then you can also have a thread removed
 > > from the mutex queue, but it'll never get woken up.
 > 
 > The simple solution to this is to change the thread state to PS_MUTEX_WAIT
 > while the mutex is locked, then enter the scheduler without changing the
 > state. I don't think that the problem is one of locking - just the
 > possibility that the thread state will be overwritten at an inoportune
 > time (i.e. the thread state may be changed to PS_RUNNING before it
 > gets a chance to set it's state to PS_MUTEX_WAIT).
 
 That works.  If you want to keep your __FILE__ and __LINE__
 debug thingys, you'll have to add another interface for
 _thread_kern_sched_state that doesn't change the state,
 though.
 
 Dan Eischen
 eischen@vigrid.com

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Sat Oct 24 07:10:05 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA14071
          for freebsd-bugs-outgoing; Sat, 24 Oct 1998 07:10:05 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA14066
          for <freebsd-bugs@FreeBSD.org>; Sat, 24 Oct 1998 07:10:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id HAA02740;
	Sat, 24 Oct 1998 07:10:01 -0700 (PDT)
Date: Sat, 24 Oct 1998 07:10:01 -0700 (PDT)
Message-Id: <199810241410.HAA02740@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.ORG
From: Daniel Eischen <eischen@vigrid.com>
Subject: Re: kern/8375: pthread_cond_wait() spins the CPU
Reply-To: Daniel Eischen <eischen@vigrid.com>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR kern/8375; it has been noted by GNATS.

From: Daniel Eischen <eischen@vigrid.com>
To: dima@tejblum.dnttm.rssi.ru, eischen@vigrid.com
Cc: freebsd-gnats-submit@FreeBSD.ORG, jb@FreeBSD.ORG
Subject: Re: kern/8375: pthread_cond_wait() spins the CPU
Date: Sat, 24 Oct 1998 09:54:39 -0400 (EDT)

 > > I don't see any other way of making pthread_cond_[timed]wait     
 > > bulletproof without disabling scheduling.  You shouldn't    
 > > allow nesting of spinlocks being taken if there is a chance
 > > of creating a deadlock.  Let's assume that you do not nest
 > > the condition variable and mutex spinlocks.  
 >
 > Why? Frankly, I don't see any harm here. Sure, it is not safe to 
 > _SPINUNLOCK the condition lock before pthread_mutex_unlock. So it has to be 
 > done in other way around.
 
 I thought I found a way that you could get a deadlock
 condition here, but it's early in the morning here and
 I can't see how it could happen anymore.  Surely after
 the thread returns from _thread_kern_sched_state you
 don't want to relock (spinlock) the condition variable.
 That fixes the original problem posted.
 
 Dan Eischen
 eischen@vigrid.com

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Sat Oct 24 08:10:06 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA17804
          for freebsd-bugs-outgoing; Sat, 24 Oct 1998 08:10:06 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17799
          for <freebsd-bugs@FreeBSD.org>; Sat, 24 Oct 1998 08:10:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id IAA04757;
	Sat, 24 Oct 1998 08:10:00 -0700 (PDT)
Date: Sat, 24 Oct 1998 08:10:00 -0700 (PDT)
Message-Id: <199810241510.IAA04757@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.ORG
From: Daniel Eischen <eischen@vigrid.com>
Subject: Re: kern/8375: pthread_cond_wait() spins the CPU
Reply-To: Daniel Eischen <eischen@vigrid.com>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR kern/8375; it has been noted by GNATS.

From: Daniel Eischen <eischen@vigrid.com>
To: dima@tejblum.dnttm.rssi.ru, eischen@vigrid.com
Cc: freebsd-gnats-submit@FreeBSD.ORG, jb@FreeBSD.ORG
Subject: Re: kern/8375: pthread_cond_wait() spins the CPU
Date: Sat, 24 Oct 1998 11:08:34 -0400 (EDT)

 > IMO, your _thread_kern_sched_[un]lock() is a bad idea. Theses functions 
 > defeat the idea of spinlocks. What is the need to do _SPINLOCK/_SPINUNLOCK 
 > when scheduling is blocked? Your code do it a lot. OTOH, spinlocks are 
 > designed exactly to make rescheduling harmless. And they works; the only 
 > problem is that spinlocks are released in a bit wrong time. (BTW, why you 
 > disable scheduling in pthread_cond_signal and pthread_cond_broadcast?)
 
 Especially for pthread_cond_broadcast, you do not want to
 get preempted while walking the condition variable queue
 to signal waiters.  If you are preempted, other threads
 run, time increments, and that can cause a thread that
 would normally be signalled to be woken up with a timeout
 (assuming it was doing a pthread_cond_timedwait).  At the
 time of the pthread_cond_broadcast, all threads that are
 currently on the waiting list should be woken up.  You do
 not want the scheduler to run and wakeup some of these threads.
 
 Another thing that looks possible, is that the condition
 variable queue can be corrupted.  When a thread is on
 the queue and it times out, I don't see where the scheduler
 removes it from the queue (_thread_queue_remove isn't used).
 What if it timesout and immediately does another pthread_cond_timedwait?
 I'll look at this some more later today - perhaps I'm just
 overlooking something.
 
 Dan Eischen
 eischen@vigrid.com

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Sat Oct 24 10:36:52 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA25982
          for freebsd-bugs-outgoing; Sat, 24 Oct 1998 10:36:52 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from ns1.seidata.com (cb-dial45.seidata.com [208.10.209.112])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25977
          for <bugs@freebsd.org>; Sat, 24 Oct 1998 10:36:49 -0700 (PDT)
          (envelope-from thanes@ns1.seidata.com)
Received: (from thanes@localhost)
	by ns1.seidata.com (8.9.1/8.9.1) id MAA00212
	for bugs@freebsd.org; Sat, 24 Oct 1998 12:38:10 -0500 (EST)
	(envelope-from thanes)
Date: Sat, 24 Oct 1998 12:38:10 -0500 (EST)
From: Thomas E Haynes <thanes@ns1.seidata.com>
Message-Id: <199810241738.MAA00212@ns1.seidata.com>
To: bugs@FreeBSD.ORG
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

I just loaded FreeBSD 3.0-RELEASE (New OS for me). My display has a bad habit of blanking everything after the BIOS setup information until the first clear screen command (or some mechanism in that type of command because most dos programs or even the FreeBSD setup information beging printing again). Would it be possible to add this mechinism or at least a clear screen command to the very beginning of the boot manager? I can not read what it wants me to type. Or if you know why this is occuring can you let me know how to fix my hardware.
HARDWARE
--------
Cirus Logic GD5430 SVGA controler
VTech LASER monitor mdl 6448/51V
Gateway Pentium 100mhz motherboard
Pentium 90mhz processor
BIOS Gateway P90 FlashBIOS 1.00.11 BS0T Upgrade
Thank you


Thomas E Haynes tehaynes@hotmail.com
P.S. This is not a bug in FreeBSD or the Bootmanager. Just a device fault I believe.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Sat Oct 24 11:59:01 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA00978
          for freebsd-bugs-outgoing; Sat, 24 Oct 1998 11:59:01 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from ceia.nordier.com (m1-28-dbn.dial-up.net [196.34.155.28])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA00971
          for <bugs@FreeBSD.ORG>; Sat, 24 Oct 1998 11:58:54 -0700 (PDT)
          (envelope-from rnordier@nordier.com)
Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id UAA14568; Sat, 24 Oct 1998 20:57:16 +0200 (SAT)
From: Robert Nordier <rnordier@nordier.com>
Message-Id: <199810241857.UAA14568@ceia.nordier.com>
Subject: Re: your mail
In-Reply-To: <199810241738.MAA00212@ns1.seidata.com> from Thomas E Haynes at "Oct 24, 98 12:38:10 pm"
To: thanes@ns1.seidata.com (Thomas E Haynes)
Date: Sat, 24 Oct 1998 20:57:13 +0200 (SAT)
Cc: bugs@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Thomas E Haynes wrote:
> I just loaded FreeBSD 3.0-RELEASE (New OS for me). My display has
> a bad habit of blanking everything after the BIOS setup information
> until the first clear screen command (or some mechanism in that
> type of command because most dos programs or even the FreeBSD setup
> information beging printing again). Would it be possible to add
> this mechinism or at least a clear screen command to the very
> beginning of the boot manager? I can not read what it wants me to
> type. Or if you know why this is occuring can you let me know how
> to fix my hardware.

Chances are this could be cured by some different hardware setting,
though I'm not familiar enough with your hardware to suggest anything.

If you're keen to experiment, we could probably work out some patches
for you to install locally.  However, all of the boot managers
supplied with FreeBSD are designed to fit into a single 512-byte
sector, so space is probably too tight to warrant offering this as a
standard option.

An alternative might be to try one of the various freeware, shareware,
or commercial boot managers available.

-- 
Robert Nordier

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Sat Oct 24 16:50:08 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA16670
          for freebsd-bugs-outgoing; Sat, 24 Oct 1998 16:50:08 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16656
          for <freebsd-bugs@FreeBSD.org>; Sat, 24 Oct 1998 16:50:05 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id QAA18390;
	Sat, 24 Oct 1998 16:50:01 -0700 (PDT)
Received: from sakura.res.cmu.edu (SAKURA.RES.CMU.EDU [128.2.92.1])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16494
          for <FreeBSD-gnats-submit@freebsd.org>; Sat, 24 Oct 1998 16:46:14 -0700 (PDT)
          (envelope-from yunching@sakura.res.cmu.edu)
Received: (from yunching@localhost)
	by sakura.res.cmu.edu (8.9.1/8.9.1) id TAA00633;
	Sat, 24 Oct 1998 19:45:37 -0400 (EDT)
	(envelope-from yunching)
Message-Id: <199810242345.TAA00633@sakura.res.cmu.edu>
Date: Sat, 24 Oct 1998 19:45:37 -0400 (EDT)
From: Yun-Ching Lee <yunching@sakura.res.cmu.edu>
Reply-To: yunching@sakura.res.cmu.edu
To: FreeBSD-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: 3.2
Subject: i386/8435: boot.flp does not give shell prompt after mounting fixit.flp
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8435
>Category:       i386
>Synopsis:       boot.flp does not give shell prompt after mounting fixit.flp
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Oct 24 16:50:01 PDT 1998
>Last-Modified:
>Originator:     Yun-Ching Lee
>Organization:
>Release:        FreeBSD 3.0-RELEASE i386
>Environment:

Booted up boot.flp.  In the main menu.

>Description:

When sysinstall prompts for mounting fixit.flp, it keeps prompting for
the floppy, even though the file system is mounted (observation from
holographic shell created during normal installation).  sysinstall enters
an infinite loop of prompting for fixit.flp.

There is no way to terminate the loop, except by Control-C or
Control-Alt-Del to reboot.

>How-To-Repeat:

1.  Boot boot.flp
2.  Select 8 Fixit.
3.  Select 2 Floppy.
4.  Change floppy disk as prompted.
5.  sysinstall keeps prompting for fixit.flp.

>Fix:
	
N/A.

>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Sat Oct 24 17:10:05 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA18063
          for freebsd-bugs-outgoing; Sat, 24 Oct 1998 17:10:05 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18056
          for <freebsd-bugs@FreeBSD.org>; Sat, 24 Oct 1998 17:10:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id RAA18664;
	Sat, 24 Oct 1998 17:10:00 -0700 (PDT)
Received: from sakura.res.cmu.edu (SAKURA.RES.CMU.EDU [128.2.92.1])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17744
          for <FreeBSD-gnats-submit@freebsd.org>; Sat, 24 Oct 1998 17:06:21 -0700 (PDT)
          (envelope-from yunching@sakura.res.cmu.edu)
Received: (from yunching@localhost)
	by sakura.res.cmu.edu (8.9.1/8.9.1) id UAA00884;
	Sat, 24 Oct 1998 20:05:47 -0400 (EDT)
	(envelope-from yunching)
Message-Id: <199810250005.UAA00884@sakura.res.cmu.edu>
Date: Sat, 24 Oct 1998 20:05:47 -0400 (EDT)
From: Yun-Ching Lee <yunching@sakura.res.cmu.edu>
Reply-To: yunching@sakura.res.cmu.edu
To: FreeBSD-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: 3.2
Subject: i386/8436: boot.flp sysinstall crashes when probing
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8436
>Category:       i386
>Synopsis:       boot.flp sysinstall crashes when probing 2k/sector medium
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Oct 24 17:10:00 PDT 1998
>Last-Modified:
>Originator:     Yun-Ching Lee
>Organization:
>Release:        FreeBSD 3.0-RELEASE i386
>Environment:

System has AHA-2940AU
ID 0-4 are hard disks
ID 5 is Fujitsu DynaMO 640SE
ID 6 is CD-ROM

>Description:

Sysinstall crashes during probe when there is a 2k/sector formatted
medium in the MO drive.  Error message on vty1 complains about not able
to handle 2048 byte/sector medium.

On vty0, /bin/init dies and system is forced to reboot.

>How-To-Repeat:

1.  Mount a 2k/sector formatted MO cartridge, like 640MB 3.5" cartridge.
2.  Boot with boot.flp.
3.  Load kernel.
4.  During sysinstall's probe of system devices, sysinstall dies when
    probing the said MO cartridge.
5.  System reboots.

>Fix:
	
Remove MO cartridge before booting boot.flp.

>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Sat Oct 24 17:20:07 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA18977
          for freebsd-bugs-outgoing; Sat, 24 Oct 1998 17:20:07 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18968
          for <freebsd-bugs@FreeBSD.org>; Sat, 24 Oct 1998 17:20:05 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id RAA18935;
	Sat, 24 Oct 1998 17:20:01 -0700 (PDT)
Received: from rr.iij4u.or.jp (h028.p060.iij4u.or.jp [210.130.60.28])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA18179
          for <FreeBSD-gnats-submit@freebsd.org>; Sat, 24 Oct 1998 17:11:09 -0700 (PDT)
          (envelope-from sada@rr.iij4u.or.jp)
Received: (qmail 11337 invoked by uid 1000); 25 Oct 1998 09:10:35 +0900
Message-Id: <19981025001035.11336.qmail@sada.e-mail.ne.jp>
Date: 25 Oct 1998 09:10:35 +0900
From: sada@e-mail.ne.jp
To: FreeBSD-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: 3.2
Subject: bin/8437: libc/locale/ansi.c problem
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8437
>Category:       bin
>Synopsis:       libc/locale/ansi.c problem
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Oct 24 17:20:01 PDT 1998
>Last-Modified:
>Originator:     SADA Kenji
>Organization:
Nagoya.Aichi.Japan
>Release:        FreeBSD 3.0-CURRENT
>Environment:

	FreeBSD 3.0-CURRENT #0: Sun Oct 25 05:38:45 JST 1998
	XFree86 3.3.2.3

>Description:

	The file `/usr/src/lib/libc/locale/ansi.c' seems to have a bug
	and couse problems on treating Japanese locale functions.

>How-To-Repeat:

	Go <URL:http://www.bres.tsukuba.ac.jp/~yohta/netscape/>,
	see FreeBSD relating pages, and try the method:
	"How to set 'libxpg4.so.2.0' on LD_PRELOAD environment variable"

>Fix:
	
--- ansi.c.orig Thu Apr 18 16:01:46 1996
+++ ansi.c      Sat Oct 24 05:18:11 1998
@@ -132,7 +132,7 @@
        if (!pwcs || !s)
                return (-1);

-       while (n > 0) {
+       while ((signed int)n > 0) {
                if (*pwcs == 0) {
                        *s = 0;
                        break;
>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Sat Oct 24 18:55:19 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA24957
          for freebsd-bugs-outgoing; Sat, 24 Oct 1998 18:55:19 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA24941;
          Sat, 24 Oct 1998 18:55:13 -0700 (PDT)
          (envelope-from a0074@netcologne.de)
Received: from bsd3.scs-koeln.de (dial5-108.netcologne.de [194.8.195.108])
	by mail2.netcologne.de (8.8.8/8.8.8) with SMTP id CAA00500;
	Sun, 25 Oct 1998 02:54:38 +0100 (MET)
X-Ncc-Regid: de.netcologne
Message-ID: <XFMail.981025025420.a0074@netcologne.de>
X-Mailer: XFMail 1.1 [p0] on FreeBSD
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Date: Sun, 25 Oct 1998 02:41:16 +0100 (CET)
From: "R. Luettgen" <a0074@netcologne.de>
To: freebsd-bugs@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG
Subject: problems with release 3.0 and SCSI
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Hi,

this night I update my box ( K6, 64 MB, 2 GB SCSI Seagate, 1 GB Nec ) from
release 2.2.7 to 3.0. The old one runs very good and secure. I use a boot disk.
when I boot the box with the 3.0 boot disk it hangs during reprobing. 

My NEC disk has the ID 0 and the Seagate Barracude has ID 1.

I changed the disks and then the machine boots and I can install the whole
release.

After that I want to fdisk the nec disk, but I cannot.

I try : fdisk /dev/rda1

Then the system hangs without any error message. Nothing works. The only thing I
 can do is turn off the power.

The model of the NEC disk is : NEC D3845 0307 ( from dmesg )


Is this a bug ?







----------------------------------
E-Mail: R. Luettgen <a0074@netcologne.de>
Date: 25-Oct-98
Time: 02:41:16

This message was sent by XF-Mail
----------------------------------

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Sat Oct 24 19:00:29 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA25677
          for freebsd-bugs-outgoing; Sat, 24 Oct 1998 19:00:29 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA25671
          for <freebsd-bugs@freebsd.org>; Sat, 24 Oct 1998 19:00:27 -0700 (PDT)
          (envelope-from a0074@netcologne.de)
Received: from bsd3.scs-koeln.de (dial6k-170.netcologne.de [195.14.233.170])
	by mail2.netcologne.de (8.8.8/8.8.8) with SMTP id CAA00636
	for <freebsd-bugs@freebsd.org>; Sun, 25 Oct 1998 02:59:53 +0100 (MET)
X-Ncc-Regid: de.netcologne
Message-ID: <XFMail.981025025935.a0074@netcologne.de>
X-Mailer: XFMail 1.1 [p0] on FreeBSD
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Date: Sun, 25 Oct 1998 02:54:39 +0100 (CET)
From: "R. Luettgen" <a0074@netcologne.de>
To: freebsd-bugs@FreeBSD.ORG
Subject: no time changing
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Hi,

this night is installed the new 3.0 release on my box.
Here in Germany this night our local time is changed from summer to winter time.
This means from 3 a.m to 2 a.m.

My 3.0 box didn't change the time automaticaly.
My other 3 boxes (2.2.7 Release) change there time on there own.


What's wrong?




----------------------------------
E-Mail: R. Luettgen <a0074@netcologne.de>
Date: 25-Oct-98
Time: 02:54:39

This message was sent by XF-Mail
----------------------------------

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Sat Oct 24 19:07:44 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA26032
          for freebsd-bugs-outgoing; Sat, 24 Oct 1998 19:07:44 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA26027
          for <freebsd-bugs@freebsd.org>; Sat, 24 Oct 1998 19:07:42 -0700 (PDT)
          (envelope-from a0074@netcologne.de)
Received: from bsd3.scs-koeln.de (dial4-100.netcologne.de [195.14.233.100])
	by mail2.netcologne.de (8.8.8/8.8.8) with SMTP id DAA00807
	for <freebsd-bugs@freebsd.org>; Sun, 25 Oct 1998 03:07:08 +0100 (MET)
X-Ncc-Regid: de.netcologne
Message-ID: <XFMail.981025030700.a0074@netcologne.de>
X-Mailer: XFMail 1.1 [p0] on FreeBSD
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Date: Sun, 25 Oct 1998 03:03:29 +0100 (CET)
From: "R. Luettgen" <a0074@netcologne.de>
To: freebsd-bugs@FreeBSD.ORG
Subject: mistake in files.i386 file
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Hi,

when I try to build a new kernel from the 3.0 source, the config
program returns the message, that in the file 'files.i386' the npx device
has to be standard or optional but not mandatory.

After I changed the entry I can compile a new kernel.


By

----------------------------------
E-Mail: R. Luettgen <a0074@netcologne.de>
Date: 25-Oct-98
Time: 03:03:29

This message was sent by XF-Mail
----------------------------------

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Sat Oct 24 19:58:38 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA29400
          for freebsd-bugs-outgoing; Sat, 24 Oct 1998 19:58:38 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from nagual.pp.ru (lsd.relcom.eu.net [193.125.27.73])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA29392
          for <freebsd-bugs@FreeBSD.ORG>; Sat, 24 Oct 1998 19:58:36 -0700 (PDT)
          (envelope-from ache@nagual.pp.ru)
Received: (from ache@localhost)
	by nagual.pp.ru (8.9.1/8.9.1) id FAA14088;
	Sun, 25 Oct 1998 05:57:59 +0300 (MSK)
	(envelope-from ache)
Message-ID: <19981025055758.A13872@nagual.pp.ru>
Date: Sun, 25 Oct 1998 05:57:58 +0300
From: "Andrey A. Chernov" <ache@nagual.pp.ru>
To: "R. Luettgen" <a0074@netcologne.de>, freebsd-bugs@FreeBSD.ORG
Subject: Re: no time changing
Mail-Followup-To: "R. Luettgen" <a0074@netcologne.de>,
	freebsd-bugs@FreeBSD.ORG
References: <XFMail.981025025935.a0074@netcologne.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <XFMail.981025025935.a0074@netcologne.de>; from a0074@netcologne.de on Sun, Oct 25, 1998 at 02:54:39AM +0100
Organization: Biomechanoid
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Sun, Oct 25, 1998 at 02:54:39AM +0100, R. Luettgen wrote:
> My 3.0 box didn't change the time automaticaly.
> My other 3 boxes (2.2.7 Release) change there time on there own.

Strange indeed, because adjkerntz is the same in 2.2.7 and 3.0

-- 
Andrey A. Chernov
http://www.nagual.pp.ru/~ache/
MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Sat Oct 24 20:00:07 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA29581
          for freebsd-bugs-outgoing; Sat, 24 Oct 1998 20:00:07 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA29574
          for <freebsd-bugs@FreeBSD.org>; Sat, 24 Oct 1998 20:00:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id UAA22227;
	Sat, 24 Oct 1998 20:00:01 -0700 (PDT)
Received: from sleipnir.watson.org (n234-113.mtholyoke.edu [138.110.234.113])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA29393
          for <FreeBSD-gnats-submit@freebsd.org>; Sat, 24 Oct 1998 19:58:36 -0700 (PDT)
          (envelope-from robert@sleipnir.watson.org)
Received: (from robert@localhost)
	by sleipnir.watson.org (8.9.1/8.9.1) id HAA15863;
	Sat, 24 Oct 1998 07:43:18 -0400 (EDT)
	(envelope-from robert)
Message-Id: <199810241143.HAA15863@sleipnir.watson.org>
Date: Sat, 24 Oct 1998 07:43:18 -0400 (EDT)
From: robert@fledge.watson.org
Reply-To: robert+freebsd@cyrus.watson.org
To: FreeBSD-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: 3.2
Subject: bin/8438: ex/vi: Error: tcsetattr: Interrupted system call
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8438
>Category:       bin
>Synopsis:       ex/vi: Error: tcsetattr: Interrupted system call
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Oct 24 20:00:00 PDT 1998
>Last-Modified:
>Originator:     Robert Watson
>Organization:
>Release:        FreeBSD 3.0-BETA i386
>Environment:

3.0-BETA/RELEASE, using vi against a file in the local FFS file system
/usr.  X-windows using xterm, XiG's X server for notebooks.

>Description:

When resizing an xterm and using vi, once in a while I get:

ex/vi: Error: tcsetattr: Interrupted system call

This kills vi.  This is not good.  I believe I have observed this both
in command and edit modes.

>How-To-Repeat:

Start editing a file.  Now resize your xterm.  This does not always
appear to happen -- in fact, only infrequently.  I'm not sure if there
is a correspondence to the size of the file being edited.  I am unable
to repeat this consistently, but it has happened at least a few times 
in the past few months.

>Fix:
	
I'm on the road, so can't check the source or see if there is already
a PR in for this.  However, I'd guess that something in curses/ncurses/
whatever vi uses doesn't wrap a syscall in a check for EINTR, and this
results in vi terminating from an error it does not expect.

>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Sat Oct 24 20:50:07 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA02448
          for freebsd-bugs-outgoing; Sat, 24 Oct 1998 20:50:07 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA02441
          for <freebsd-bugs@FreeBSD.org>; Sat, 24 Oct 1998 20:50:04 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id UAA23262;
	Sat, 24 Oct 1998 20:50:01 -0700 (PDT)
Received: from istari.home.net (cc158233-a.catv1.md.home.com [24.3.25.17])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA02312
          for <FreeBSD-gnats-submit@freebsd.org>; Sat, 24 Oct 1998 20:47:35 -0700 (PDT)
          (envelope-from sjr@home.net)
Received: (from sjr@localhost)
	by istari.home.net (8.9.1/8.8.6) id XAA16750;
	Sat, 24 Oct 1998 23:46:39 -0400 (EDT)
Message-Id: <199810250346.XAA16750@istari.home.net>
Date: Sat, 24 Oct 1998 23:46:39 -0400 (EDT)
From: sjr@home.net
Reply-To: sjr@home.net
To: FreeBSD-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: 3.2
Subject: bin/8440: 3.0-RELEASE has wrong permissions on game score files
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8440
>Category:       bin
>Synopsis:       3.0-RELEASE has wrong permissions on game score files
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Oct 24 20:50:00 PDT 1998
>Last-Modified:
>Originator:     Stephen J. Roznowski
>Organization:
>Release:        FreeBSD 3.0-RELEASE i386
>Environment:

	From a fresh 3.0-RELEASE install.

>Description:

	The score files under /var/games are mode 644 (root, games),
	but need to be 664 (root, games) for the games to be able
	to update them.

>How-To-Repeat:

	Try to play a game and save a score file...

>Fix:
	
	

>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Sat Oct 24 20:58:24 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA03110
          for freebsd-bugs-outgoing; Sat, 24 Oct 1998 20:58:24 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from mayn.de (airbus.mayn.de [194.95.209.24])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA03105
          for <freebsd-bugs@freebsd.org>; Sat, 24 Oct 1998 20:58:22 -0700 (PDT)
          (envelope-from mkb@altair.mayn.de)
Received: (qmail 19253 invoked from network); 25 Oct 1998 05:58:18 -0000
Received: from wuff.mayn.de (qmailr@194.95.209.17)
  by airbus.mayn.de with SMTP; 25 Oct 1998 05:58:18 -0000
Received: (qmail 1255 invoked by uid 5); 25 Oct 1998 03:57:34 -0000
Received: from altair.mayn.de (localhost [127.0.0.1]) by altair.mayn.de (8.8.8/8.7.3) with ESMTP id EAA02496; Sun, 25 Oct 1998 04:58:45 +0100 (CET)
Message-Id: <199810250358.EAA02496@altair.mayn.de>
To: robert+freebsd@cyrus.watson.org
Cc: freebsd-bugs@FreeBSD.ORG
Subject: [patch] Re: bin/8438: ex/vi: Error: tcsetattr: Interrupted system call 
In-Reply-To: Your message of "Sat, 24 Oct 1998 07:43:18 EDT."
             <199810241143.HAA15863@sleipnir.watson.org> 
Date: Sun, 25 Oct 1998 04:58:43 +0100
From: Matthias Buelow <mkb@altair.mayn.de>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

"robert@fledge.watson.org" wrote:

>>Number:         8438
>>Category:       bin
>>Synopsis:       ex/vi: Error: tcsetattr: Interrupted system call

>3.0-BETA/RELEASE, using vi against a file in the local FFS file system
>/usr.  X-windows using xterm, XiG's X server for notebooks.
>
>>Description:
>
>When resizing an xterm and using vi, once in a while I get:
>
>ex/vi: Error: tcsetattr: Interrupted system call
>
>This kills vi.  This is not good.  I believe I have observed this both
>in command and edit modes.
>
>>How-To-Repeat:
>
>Start editing a file.  Now resize your xterm.  This does not always
>appear to happen -- in fact, only infrequently.  I'm not sure if there
>is a correspondence to the size of the file being edited.  I am unable
>to repeat this consistently, but it has happened at least a few times 
>in the past few months.
>
>>Fix:
>	
>I'm on the road, so can't check the source or see if there is already
>a PR in for this.  However, I'd guess that something in curses/ncurses/
>whatever vi uses doesn't wrap a syscall in a check for EINTR, and this
>results in vi terminating from an error it does not expect.

Yes, there're two occurrances of tcsetattr that are checked for errors,
but EINTR is not taken care of.  It is quite trivial to do this.
Keith Bostic (the author of nvi) is busy with db 2.x since 1996 (and
doesn't seem to have time for fixing bugs), so you could try the following
patch from a mere user (me :).  Please let me know if the problem goes
away.  You could also try to get the source for 1.79 and build with the
internal curses subset, instead of linking against FreeBSD libcurses
(it is linked against the system's curses at least in 2.2.6 and 2.2.7;
this is probably not the best idea, since the bundled curses is supposed
to work best with it).


--- cl/cl_screen.c.orig-1.79	Sun Oct 25 04:49:59 1998
+++ cl/cl_screen.c	Sun Oct 25 04:50:54 1998
@@ -368,6 +368,8 @@
 
 fast:	/* Set the terminal modes. */
 	if (tcsetattr(STDIN_FILENO, TCSASOFT | TCSADRAIN, &clp->vi_enter)) {
+		if (EINTR == errno)
+			goto fast;
 		msgq(sp, M_SYSERR, "tcsetattr");
 err:		(void)cl_vi_end(sp->gp);
 		return (1);
@@ -486,6 +488,8 @@
 #endif
 
 fast:	if (tcsetattr(STDIN_FILENO, TCSADRAIN | TCSASOFT, &clp->ex_enter)) {
+		if (EINTR == errno)
+			goto fast;
 		msgq(sp, M_SYSERR, "tcsetattr");
 		return (1);
 	}

 - mkb

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Sat Oct 24 21:19:18 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA04579
          for freebsd-bugs-outgoing; Sat, 24 Oct 1998 21:19:18 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA04573
          for <freebsd-bugs@FreeBSD.ORG>; Sat, 24 Oct 1998 21:19:13 -0700 (PDT)
          (envelope-from grog@freebie.lemis.com)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
	by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id OAA04870;
	Sun, 25 Oct 1998 14:48:33 +1030 (CST)
Received: (from grog@localhost)
	by freebie.lemis.com (8.9.1/8.9.0) id OAA17072;
	Sun, 25 Oct 1998 14:48:31 +1030 (CST)
Message-ID: <19981025144831.I16609@freebie.lemis.com>
Date: Sun, 25 Oct 1998 14:48:31 +1030
From: Greg Lehey <grog@lemis.com>
To: "R. Luettgen" <a0074@netcologne.de>, freebsd-bugs@FreeBSD.ORG
Subject: Re: no time changing
References: <XFMail.981025025935.a0074@netcologne.de> <19981025055758.A13872@nagual.pp.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <19981025055758.A13872@nagual.pp.ru>; from Andrey A. Chernov on Sun, Oct 25, 1998 at 05:57:58AM +0300
WWW-Home-Page: http://www.lemis.com/~grog
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Sunday, 25 October 1998 at  5:57:58 +0300, Andrey A. Chernov wrote:
> On Sun, Oct 25, 1998 at 02:54:39AM +0100, R. Luettgen wrote:
>> My 3.0 box didn't change the time automaticaly.
>> My other 3 boxes (2.2.7 Release) change there time on there own.
>
> Strange indeed, because adjkerntz is the same in 2.2.7 and 3.0

You don't need adjkerntz for DST transitions.  It's designed to fake
the correct time zone when the hardware clock shows local time (for
Microsoft compatibility) instead of UTC like it should.

I don't use adjkerntz (or Microsoft :-), and my transitions worked
fine.

Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Sat Oct 24 22:08:27 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA07378
          for freebsd-bugs-outgoing; Sat, 24 Oct 1998 22:08:27 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA07368;
          Sat, 24 Oct 1998 22:08:12 -0700 (PDT)
          (envelope-from ache@FreeBSD.org)
From: "Andrey A. Chernov" <ache@FreeBSD.ORG>
Received: (from ache@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id WAA24765;
	Sat, 24 Oct 1998 22:08:08 -0700 (PDT)
Date: Sat, 24 Oct 1998 22:08:08 -0700 (PDT)
Message-Id: <199810250508.WAA24765@freefall.freebsd.org>
To: sada@e-mail.ne.jp, ache@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG
Subject: Re: bin/8437
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: libc/locale/ansi.c problem

State-Changed-From-To: open-closed
State-Changed-By: ache
State-Changed-When: Sat Oct 24 22:07:34 PDT 1998
State-Changed-Why: 
fixed differently in ansi.c v1.3

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

From owner-freebsd-bugs  Sat Oct 24 22:09:51 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA07626
          for freebsd-bugs-outgoing; Sat, 24 Oct 1998 22:09:51 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from pollux.usc.edu (pollux.usc.edu [128.125.253.192])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA07618
          for <freebsd-bugs@FreeBSD.ORG>; Sat, 24 Oct 1998 22:09:48 -0700 (PDT)
          (envelope-from jungh@pollux.usc.edu)
Received: from pollux.usc.edu (lvl-sun701.usc.edu [128.125.140.179])
	by pollux.usc.edu (8.8.8/8.8.8/usc) with ESMTP
	id WAA01269 for <freebsd-bugs@FreeBSD.ORG>; Sat, 24 Oct 1998 22:09:16 -0700 (PDT)
Message-ID: <3632B27B.82DAC87D@pollux.usc.edu>
Date: Sat, 24 Oct 1998 22:09:15 -0700
From: "Jung, Hyuckchul" <jungh@pollux.usc.edu>
X-Mailer: Mozilla 4.07 [en] (X11; U; SunOS 5.6 sun4u)
MIME-Version: 1.0
To: freebsd-bugs@FreeBSD.ORG
Subject: server goes down
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

I am a new freebsd user. In my lab, there are one server and seven
clients PC whose OS is FreeBSD. But, when I mount a file system from the

server to a client and run an executable file on that file system.
Server goes down. I guess there may be many reasons. Could you give me
any advice about this problem? Thanks.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message