Return to BSD News archive
Newsgroups: comp.unix.bsd
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!uunet!acd4!iedv7!smm
From: smm@iedv7.acd.com ( Steve McCoole )
Subject: Diffs to BSDI BSD/386 Ported Software List 02/02
Message-ID: <1993Apr8.020133.22717@acd4.acd.com>
Followup-To: comp.unix.bsd
Keywords: BSD, PC, Available Software, Patches and Enhancements
Sender: news@acd4.acd.com (USENET News System)
Organization: Applied Computing Devices, Inc., Terre Haute IN
References: <1993Apr8.015726.22485@acd4.acd.com>
Date: Thu, 8 Apr 1993 02:01:33 GMT
Lines: 153
4c4
< Date: Mon Jan 18 19:00:29 EST 1993
---
> Date: Mon Apr 05 19:00:29 EST 1993
12,13c12
< Starting with this issue I have been removing entries which are beta
< level specific.
---
> Notes for beta level stuff have been deleted.
624c623,628
< gamma4.pagermap.wait.patch: Subject: (Gamma 3) Deadlock in page daemon
---
> gamma3.pagermap.wait.patch: Subject: (Gamma 3) Deadlock in page daemon
> gamma3.security.patch: Subject: Fix for a security hole in Gamma 3.
> gamma3.sigsuspend.patch: Subject: (Gamma 3) Sigsuspend(2) problem.
> gamma3.socket.patch: Subject: (Gamma 3) Several bugs in receive from socket.
> gamma3.unp_discard.patch: Subject: (Gamma 3) Wrong access rights
> handling in unix domain sockets.
808a813,941
> (GAMMA 4)
> Fix to the w_char redefinition problem in Xlib.h.
> File: bsdi.com : Xlib.h.patch.Z
> rd@pixie.aii.com (Robert D. Thrush)
> -------
> (GAMMA 4)
> I'd like to ask you to test the new version of VGA driver
> on your VGA cards -- it does some trickery to save/restore
> fonts and it is possible that some cards don't like that.
> The changes are supposed to fix the problem with restoring
> screen on exit from X on Trident and some other VGA cards.
> I also added code for loading user font.
> File: bsdi.com : antovov.vga.driver.Z
> avg@uunet.uu.net (Vadim Antonov)
> -------
> (GAMMA 4)
> I have had enough requests for the new 3C509 driver that I will use
> multicast to reply. Here are the patches for /usr/src/sys/i386/isa/if_ef.c.
> They fix three problems: there was a possible hang if there were excessive
> collisions, some machines could not configure more than 1 card, and some
> machines could not configure the 3C509 on a reboot without a power-up.
>
> I have forgotten whether the 0.9.4.1 patches include this, but I think
> the answer is "no".
>
> A couple of folks asked about performance; I don't have performance
> numbers (or a 3C509!), but several reports put it substantially ahead
> of the other cards we support.
>
> At least one person asked about the card for which we just added support.
> It is the Intel EtherExpress 16.
> File: bsdi.com : ethernet.3c509.patch.Z
> karels@bsdi.com (Mike Karels)
> -------
> (GAMMA 4)
> > I have a question about the return value from fflush. According to the
> > manpage, fflush will fail if the stream is not open for writing.
> > However, it fails when the stream is opened for reading and writing with
> > mode "w+".
>
> I thought I'd sent in this patch -- I'm pretty sure I did, but would need
> to search through my archives to double check. Just in case, I'll CC this
> to problems@bsdi.com, also. For those that want to fix it now, I include
> a patch to /usr/src/lib/libc/stdio/fflush.c below my signature.
> File: bsdi.com : fflush.patch.Z
> composer@beyond.dreams.org (Jeff Kellem)
> -------
> (GAMMA 4)
> Check the 'speed' with stty. If it's 38,400 or higher, more gets
> confused. If you're using xterm, the simple answer is to drop the
> speed down to (say) 9600, since it makes no difference to anything
> else. Otherwise you need to patch more...
> File : bsdi.com : more.highspeed.patch
> donn@bsdi.com (Donn Seeley)
> -------
> (GAMMA 4)
> Followup to msgs(1) problem (bug #001975)
> The fopen(fname, "a+") didn't actually work either like I thought it had.
> Soo...opening for read/write ("r+"), and then opening for write ("w")
> if that doesn't work (if the file doesn't exist) does the trick.
> I tested it running msgs(1) a few times, and removing my .msgsrc, and
> repeating the whole process a few times. I can't get it to fail anymore,
> and here is my resultant patch:
> File: bsdi.com : msgs.patch.Z
> From: tod@vision.intel.com (Tod Oace)
> -------
> (GAMMA 4)
> Fix to allow boot without a keyboard
> In srt0.s, a call is made to kbd_reset. This call hangs unless the following
> patch is applied to /sys/i386/stand/kbd.c. The patch will put an upper
> bound on how long the code waits for the reset command to complete.
> File: bsdi.com : no_kbd_boot.patch.Z
> From: Robert Hagens <hagens@reston.ans.net>
> -------
> (GAMMA 4)
> Another problem with sed. The gamma-4 sed failed the following sed
> script found in the brand new GROFF 1.07 release (psstrip.sed)
>
> #!/bin/sed -f
> # Strip a PostScript prologue of unnecessary comments and white space.
> /^%[%!]/b
> s/^[ ][ ]*//
> s/[ ][ ]*$//
> s/%.*//
> /^$/d
> s/[ ]*\([][}/{]\)[ ]*/\1/g
>
>
> The last line fails to compile, sed complaining about unbalanced []'s.
> This is due to compile_delimited not really knowing the traditionally
> rules about [] expressions (namely that inside a [s] expression, the first
> character of s is allowed to be ] and that \ has no special meaning.
>
> The following patch corrects this. I have a vague nasty feeling though
> that we should run sed through a complete set of tests after this change.
> I have done a few tests, but nothing VERY extensive.
> File: bsdi.com : sed.patch.Z
> From: root@eab.retix.com (Erik Forsberg)
> ------
> (GAMMA 4)
> I found a problem in sort with a large file where it hits the end of the
> sort buffer, and because of the way trecheaders are allocated, bufend could
> be less than opos, so the memmove gets a negative length.
> Context diffs follow:
> File: bsdi.com : sort.large.file.patch.Z
> From: Kent.Peacock@eng.sun.com (Kent Peacock [CONTRACTOR])
> -------
> (GAMMA 4)
> Haven't seen mention of this, so i hope i'm not replicating something
> obvious. All that's needed to get tcsh 6.03 up and running on BSD/386
> is one small change - BSD/386 defines BSD4_4 but doesn't have the
> "quad_t" type (yet;-)).
> [ I believe that tcsh is back in the normal distribution for 1.0 SMM ]
> File: bsdi.com : tcsh-6.03.patch.Z
> From: sms@wlv.iipo.gtegsc.com (Steven M. Schultz)
> -------
> (GAMMA 4)
> Patch for "panic: vm_map_entry_create: out of map entries"
> Several folks have run into this panic recently. The direct cause of
> the panic is severe fragmentation of an internal kernel map, which
> we haven't been able to reproduce when we try to cause it. One way
> for it to happen is for the buffer cache to fill with lots of small files;
> a news feed or NFS mounts with small rsize/wsize have both been seen to do
> this under some circumstances. Here is a change for /usr/src/sys/vm/vm_map.c
> that alleviates the problem. If you have not seen this panic, you probably
> don't need the fix.
> File: bsdi.com : vm_map_entry_create.panic.patch
> From: karels@bsdi.com (Mike Karels)
> -------
813c946
< Date: Wed Feb 17 19:00:29 EST 1993
---
> Date: Mon Apr 05 19:00:29 EST 1993