Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP
id AA1509 ; Tue, 23 Feb 93 14:45:49 EST
Newsgroups: comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!sun-barr!cs.utexas.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: <1993Feb17.220256.6393@acd4.acd.com>
Followup-To: comp.unix.bsd
Sender: news@acd4.acd.com (USENET News System)
Organization: Applied Computing Devices, Inc., Terre Haute IN
References: <1993Feb17.215927.6174@acd4.acd.com>
Date: Wed, 17 Feb 1993 22:02:56 GMT
Lines: 726
10a11,13
>
> Starting with this issue I have been removing entries which are beta
> level specific.
13,28d15
< Patches to nfs_socket.c adding code that searches through the reserved
< ports, and binds the socket to the first unused port it finds. This
< is done just after the call to soconnect, that creates the socket used
< by the nfs client. Rob Fristrom <rrf@cs.umd.edu>
< -----
< Patches for tolower(), toupper(), floor(), and ceil() functions from
< the libm math library. donn@ibapah.bsdi.com (Donn Seeley)
< -----
< Patches to support German [ and more generic? ] keyboad maps. "Dirk
< Husemann" <Dirk.Husemann@informatik.uni-erlangen.de>
< -----
< Compatiblity routines for re_comp and re_exec using the new
< regcomp/regexec routines. James da Silva <jds@cs.umd.edu>
< -----
< Patches for MouseSystems compatible 3-button mouse.
< jtkohl@kolvir.elcr.ca.us (John T Kohl)
30,36d16
< Parallel (printer) port and bus mouse drivers. Also includes a
< printer filter for ascii to postscript printing. The busmouse driver
< is at version 3.0 and the printer driver is version 5.0.
< Erik also reports having a Logitech version of his
< busmouse driver that he has not tested extensively since he does not
< have a Logitech. David Boyce reports that he has had the Logitech
< busmouse driver working since June.
41,195d20
< Additions to math lib including srand48(), drand48(), erf(), and
< erfc(). bts!bill@uunet.uu.net ( Bill Hatch )
< -----
< I have a patch for the tty compatibility code that makes it more
< careful about setting the ISTRIP flag when doing TIOCGETP followed by
< TIOCSETP. With this change installed in the kernel
< (/usr/src/sys/kern/tty_compat.c), I was able to run vi in 8-bit mode
< and edit a file with non-ASCII characters on the console. (I'm using
< a derivative of Dirk Husemann's keyboard modifications to use ALT as a
< meta key.) Mike Karels ( sent by Jeff Polk <polk@bsdi.com> )
< -----
< PD version of the pr program. Posted to the beta list. This is part
< of the distribution on GAMMA releases. bjorn@sysadmin.com
< (Bjorn Satdeva)
< -----
< Package that allows booting BSDI or DOS from the same hard disk.
< Requires bootany.zip from DOS archives such as ftp.uu.net.
< John T Kohl <jtkohl@kolvir.elcr.ca.us>
< -----
< Patch to pccons.c to allow ALT key to generate META for emacs on BSDI
< console. John T Kohl <jtkohl@kolvir.elcr.ca.us>
< -----
< This patch makes init do proper "logging out" (according to utmp/wtmp)
< of users. John T Kohl <jtkohl@kolvir.elcr.ca.us>
< -----
< The following patch adds the "buffered" and "unbuffered" commands
< to mt(1) to enable and disable buffered writes.
< visenix!beattie@uunet.uu.net (Brian Beattie)
< -----
< I made a small modification to the kernel source file
< i386/isa/pccons.c to allow
< SCO-style terminal escapes to change colors on a character-mode screen, for
< those of us who haven't gotten X to work yet. The escape sequences are:
< ESC[=nF - set normal foreground color to n
< ESC[=nG - set normal background color to n
< ESC[=nH - set reverse video foreground color to n
< ESC[=nI - set reverse video background color to n
< where n is one of the following:
< 0 - black 1 - blue 2 - green 3 - cyan
< 4 - red 5 - magenta 6 - brown 7 - white
< 8 - gray 9 - light blue 10 - lt green 11 - lt cyan
< 12 - lt red 13 - lt magenta 14 - yellow 15 - hi white
< For the background settings, colors 8-15 are the same as 0-7, and the 0x8 bit
< turns on blinking (at least on my hardware). This can be changed by
< reprogramming the meaning of the bit in the hardware, but I haven't done that
< yet. Kent Peacock <kentp@svmp03>
< -----
< Fix for select(2) inadvertently turning a very short timeout value into
< a zero (infinite) sleep request. John T Kohl <jtkohl@kolvir.elcr.ca.us>
< -----
< Some people have not had great success using uucp as supplied with
< the BSDI package. I recompiled the uucp sources to use exclusively
< BNU style configuration (which I understand), created BNU configuration
< files, and now things work great. brian@apt.bungi.com (Brian Litzinger)
< -----
< I have an older Wangtek QIC150 tape drive that does not fully support
< SCSI-1. The drive seems to be support some of the features of SCSI-1
< so, to better support it I have made some modifications to the scsi tape
< device driver. These changes may be usefull to others who have drive
< that do not fully support SCSI-1. visenix!beattie@uunet.uu.net
< (Brian Beattie)
< -----
< I have a new version of the console terminal emulator code (kernel pccons.c)
< with a number of changes from various beta sites, as well as some fixes
< that I have made and a lot of cleanup. It is based on fixes from
< John Haugen for the PS/2 machines and the code from Dirk Husemann
< to do (most of) the German keyboard stuff using the ALT key(s).
< It does not (yet?) have Greg Lehey's code for German multiple-key
< sequences. The current tables use ALT as a meta key except where
< it is used for alternate characters.
<
< Because the files are moderately large, I have put them out for
< anonymous FTP from liberty.BSDI.COM for the moment; they are in
< /hidden/pccons.shar. I will mail them on request to folks
< without FTP access, and will mail them now those who have already
< requested them.
<
< I think it fixes these problems:
<
< o left and right shift, control and alt keys are recognized separately,
< and it correctly deals with pressing both keys and then releasing one.
<
< o it recognizes extended-keyboard keys separately from the main keyboard
< (or keypad) equivalents (this was needed for right control and alt).
< As a result, arrow keys and editing keypad keys no longer produce digits.
<
< o The arrow keys are now supported.
<
< o The num lock key is recognized and used, and the keypad produces numbers
< only when num lock is on. Num lock is set at initialization.
<
< o the normal, standout and kernel foreground/background colors are settable
< by SCO-compatible escape sequences (from Kent Peacock), and the cursor
< can be changed to a block cursor.
<
< o a problem resulting in reentrance of sput is fixed, and output reordering
< problems that resulted seem to be fixed. A side effect may be that
< more of the output processing, including scrolling, will be done
< at base priority rather than spltty. (This may help reduce silo
< overflows on machines where the console is in use but X is not.)
<
< o a lot of the code has been cleaned up, and even uses manifest constants
< for many of the magic numbers (not yet all)
<
< o no longer crashes when cursor addressing, etc. are out of range
<
< o the cursor is kept in sync during most kernel output (during autoconfig,
< for kernel input, etc.)
<
<
< At least the following are not yet fixed:
<
< o recognition of the stupid pause key code sequence (it still toggles num lock)
<
< o function keys, arrow keys, still do nothing useful, although the keys
< are recognized and they can now be defined to produce a string.
< Similarly for numeric keypad keys when num-lock is not set.
< I don't know what these keys should send.
<
< o the standalone kbd.c has not been converted yet; I compile it using
< the old pcconstab.* files for now.
<
<
< Notes on the new escape sequences:
<
< Color codes:
<
< 0 - black 1 - blue 2 - green 3 - cyan
< 4 - red 5 - magenta 6 - brown 7 - white
<
< For foreground, the following "intense" color variants are available.
< (In background, these set the corresponding value above plus the blinking
< attribute.)
<
< 8 - gray 9 - light blue 10 - lt green 11 - lt cyan
< 12 - lt red 13 - lt magenta 14 - yellow 15 - hi white
<
< ESC[=nF - set normal foreground color to n (default white)
< ESC[=nG - set normal background color to n (default black)
< ESC[=nH - set reverse video foreground color to n (default black)
< ESC[=nI - set reverse video background color to n (default white)
< ESC[=nK - set kernel foreground color to n (default hi white, had been yellow)
< ESC[=nL - set kernel background color to n (default blue)
<
< ESC[1_ - set block cursor
< ESC[0_ - set underscore cursor
< karels@bsdi.com (Mike Karels)
< -----
< Patches to pccons to allow German keyboard multiple key sequences.
< uunet!lemis!grog (Greg Lehey)
< -----
< Patches to com driver for modem control. Com driver is at version 3.0
< with some additional patches.
< Brad Huntting <huntting@misc.glarp.com>
< -----
201,203d25
< Patches to allow you to read 720k floppies in a HD 3.5" drive.
< John T Kohl <jtkohl@kolvir.elcr.ca.us>
< -----
207,239d28
< Program reads /etc/slipsite to determin which of two gateways
< to call for slip.
<
< And here are some diffs for sbin/slattach/slattach.c to allow it
< to catch HUP's when the line dies, syslog when it connects and when
< it dies, allow more creative line speeds, leave the line speed
< alone when you dont specificly ask for a particular speed (this is
< not the way its advertised, I just think the "default baud rate"
< bit is ludicrously ussless).
< Brad Huntting <huntting@misc.glarp.com>
< -----
< Patch to talk program to allow automatic word wrap.
< Marc G. Frank <mfrank@well.sf.ca.us>
< -----
< When attempting to get uucp to work, I noticed that uucico would
< reliably dump core when it was the wrong time to make a call. The fault
< was a zero dereference in fcall(), thus:
< Andy Rutter <andy@hoskyns.co.uk>
< -----
< Someone else's patches to GNU emacs for 386BSD apply equally well to
< BSD/386's emacs, to make subprocess signals to work properly (this
< problem has been oustanding for quite a while). I've attached them
< (relative to the beta EMACS sources). Thanks to Bill Sommerfeld
< (sommerfeld@apollo.hp.com)!
< John T Kohl <jtkohl@kolvir.elcr.ca.us>
< ------
< Workaround for FPE emulation on systems with no hardware co-processor.
< karels@bsdi.com
< ------
< ksh dies because the setvbuf routine is defective. Here is a fix that
< Chris Torek has sent me.
< pc@bsdi.com
< ------
244,249d32
< Patches to the com.v3 driver to allow use of a multi-port comm board.
< brian@apt.bungi.com (Brian Litzinger)
< ------
< Patches to fix NFS pwd problems on a client of a BSDI server.
< karels@bsdi.com
< ------
260,262d42
< Fixes for the floating point emulator.
< karels@bsdi.com
< ------
341,388d120
< Patch to com.v3 that:
< Added MODEM_OPEN macro that tests to see if the minor device has the 5th
< bit set. If it does then it does the wait for CD otherwise it does not. The
< UNIT number now can be from 0-15 (are more needed?).
<
< After applying the below patch on the Com.v3 driver...
<
< Do a:
< mknod /dev/com0 c 8 0 for hard-wired terminals (the default)
< -or-
< mknod /dev/com0 c 8 16 for modems (hang waiting for CD)
<
< or hey:
< mknod /dev/com0 c 8 0
< -AND-
< mknod /dev/modem0 c 8 16 AND HAVE BOTH (what a concept :-).
< gray@antaire.com (Gray Watson)
< -------
< Patch to X server to eliminate having to use stty and a long sleep to get
< raw mode when using some MouseSystems Mice.
< Robert "J.Dunlop" <rjd@chaser.co.uk>
< -------
< Promiscuous mode was not implemented in the Western Digital
< driver (at least in the Beta version). Here is a patch that adds
< promiscuous mode and makes tcpdump work.
< andy@terasil.terasil.com (Andrew H. Marrinson)
< -------
< I believe the below patch fixes at least 2 bugs from the bug list (#455 and
< ???) . The second one I turned in the other day but forgot the auto-response
< number.
<
< Hopefully it won't create any new ones. :-)
<
< This patch fixes the problems:
<
< - 'kill -HUP 1' did not respawn a job if you've changed its command line.
< - init restarted too fast (I stuck in 2 second pause before job spawning)
< - init respawned a job too fast after it was respawning too fast. I split
< one define into two.
<
< Let me know if I've done something bad here but our system has been up for
< hours (and numerous kill -HUP 1 calls) with no problems.
<
< Also, the logout.patch from the patch directory that I applied, generate tons
< of "can't register logout..." messages (1 for each time a job restarted) so I
< removed the else and the warning. Anyone else have this problem?
< gray@antaire.com (Gray Watson)
< -------
399,416d130
< Tcl/Tk patches working under beta. Setenv/unsetenv hack may not be
< robust. Problems with the strod function as provided by the package (
< BSDI has a prototype for the function but not the function itself ).
< hartzell@cory.berkeley.edu (George Hartzell)
< -------
< Tcl/Tk patches also working under beta.
< cpetterb@javelin.sim.es.com (Cary Petterborg)
< -------
< We aquired a used DEC hard drive which did not seem to spin up at all.
< After digging around an Ultrix system, we discovered that the drive
< needed a START_UNIT command to get it going. Here is a fix for the
< scsi/sd.c driver which will issue a start unit upon boot (only to a
< DEC drive at this moment. Issueing the start unit did not
< cause problems for other drives, so I think the DEC compare can be
< safely removed). If anyone else is having trouble getting unknown drives
< to spin-up this will probably fix the problem.
< tomm@ingres.com (Tom Markson)
< -------
491c205
< This file is in /bsdi.sw/sw/patches/compressed_more.patch on bsdi.com.
---
> File: bsdi.com:compressed_more.patch.
496c210
< /bsdi.sw/sw/progs/fdisk.mtoolsrc.prog on bsdi.com.
---
> File: bsdi.com:fdisk.mtoolsrc.prog.
501c215
< bsdi.com.
---
> File: bsdi.com:gcc2.3.2.compile
506c220
< /bsdi.sw/sw/info/webb.install.notebook.noether on bsdi.com.
---
> File: bsdi.com:webb.install.notebook.noether.
511,512c225,226
< CD-ROM. File in /bsdi.sw/sw/gamma/progs/cdlink,cdlink.patch01 on
< bsdi.com.
---
> CD-ROM.
> File: bsdi.com:cdlink and cdlink.patch01.
514a229
> (GAMMA)
518c233
< /bsdi.sw/sw/gamma/patches/gamma.math.funcs.patch on bsdi.com.
---
> File: bsdi.com:gamma.math.funcs.patch.
525,526c240
< File: /bsdi.sw/sw/gamma/patches/gamma3.sed.patch
< on bsdi.com.
---
> File: bsdi.com:gamma3.sed.patch
535,536c249
< File: /bsdi.sw/sw/gamma/patches/host.unreachable.slip.patch
< on bsdi.com.
---
> File: bsdi.com:host.unreachable.slip.patch
541,542c254
< File: /bsdi.sw/sw/gamma/patches/iso9660.man
< on bsdi.com.
---
> File: bsdi.com:iso9660.man
549,550c261
< Files: /bsdi.sw/sw/gamma/patches/ps.com.report.patch*
< on bsdi.com.
---
> Files: bsdi.com:ps.com.report.patch*
571,572c282
< File: /bsdi.sw/sw/gamma/patches/sed.dash.patch
< on bsdi.com
---
> File: bsdi.com:sed.dash.patch
586c296
< File:/bsdi.sw/sw/gamma/patches/tcpdump.patch[1-2]
---
> File: bsdi.com:patches/tcpdump.patch[1-2]
592c302
< File:/bsdi.sw/sw/gamma/progs/web.makelinks.script on bsdi.com
---
> File: bsdi.com:web.makelinks.script.
615,616c325
< File: /bsdi.sw/sw/gamma/app.patches/ingress.lock.driver.patches
< on bsdi.com
---
> File: bsdi.com:ingress.lock.driver.patches
629c338
< File: /bsdi.sw/sw/gamma/app.patches/smail-3.28.patches
---
> File: bsdi.com:smail-3.28.patches
634c343
< File: /bsdi.sw/sw/gamma/gnu/libg++-2.3.patches
---
> File: bsdi.com:libg++-2.3.patches
644c353
< File: /bsdi.sw/sw/gamma/progs/frank.perl.getopt
---
> File: bsdi.com:frank.perl.getopt
649c358
< File: /bsdi.sw.sw/gamma/app.patches/elm2.4.pl17.patch
---
> File: bsdi.com:elm2.4.pl17.patch
659c368
< File: /bsdi.sw/sw/gamma/gnu/gdb4.7.patch
---
> File: bsdi.com:gdb4.7.patch
666c375
< File: /bsdi.sw/sw/gamma/drivers/sblast1.5.gamma.patches
---
> File: bsdi.com:sblast1.5.gamma.patches
676c385
< File: /bsdi.sw/sw/gamma/patches/gamma4.autorepeat.key.patch
---
> File: bsdi.com:gamma4.autorepeat.key.patch
686c395
< via anonymous FTP from BSDI.COM, path /sw/gamma4/patches/bidir.tar.Z.
---
> via anonymous FTP from BSDI.COM, bidir.tar.Z.
689c398
< File: /sw/gamma4/patches/bidir.tar.Z
---
> File: bsdi.com:bidir.tar.Z
697c406
< File: /bsdi.sw/sw/gamma/patches/gamma4.ctrl.alt.del.no.reboot.patch
---
> File: bsdi.com:gamma4.ctrl.alt.del.no.reboot.patch
704c413
< File: /bsdi.sw/sw/gamma/patches/gamma4.diskdefect.patch
---
> File: bsdi.com:gamma4.diskdefect.patch
718c427
< File: /bsdi.sw/sw/gamma/patches/gamma4.esia.174x.tape.patch
---
> File: bsdi.com:gamma4.esia.174x.tape.patch
726c435
< File: /bsdi.sw/sw/gamma/patches/gamma4.fstab.comment.patch
---
> File: bsdi.com:gamma4.fstab.comment.patch
731c440
< File: /bsdi.sw/sw/gamma/patches/gamma4.fstat.patch
---
> File: bsdi.com:gamma4.fstat.patch
738c447
< File: /bsdi.sw/sw/gamma/gamma4.join.patch
---
> File: bsdi.com:gamma4.join.patch
761c470
< File: /bsdi.sw/sw/gamma/patches/gamma4.ne2000.generic.kernel.conf.patch
---
> File: bsdi.com:gamma4.ne2000.generic.kernel.conf.patch
768c477
< File: /bsdi.sw/sw/gamma/patches/gamma4.ne2000.patch
---
> File: bsdi.com:gamma4.ne2000.patch
774c483
< File: /bsdi.sw/sw/gamma/patches/gamma4.rundos.floppy.panic.patch
---
> File: bsdi.com:gamma4.rundos.floppy.panic.patch
783c492
< File: /bsdi.sw/sw/gamma/patches/gamma4.scsi.tape.exebyte.patch
---
> File: bsdi.com:gamma4.scsi.tape.exebyte.patch
795c504
< File: /bsdi.sw/sw/gamma/patches/gamma4.slattach.patch
---
> File: bsdi.com:gamma4.slattach.patch
806c515
< File: /bsdi.sw/sw/gamma/patches/gamma4.slip.hang.patch
---
> File: bsdi.com:gamma4.slip.hang.patch
817c526
< File: /bsdi.sw/sw/gamma/patches/gamma4.stray.interrupt.panic.patch
---
> File: bsdi.com:gamma4.stray.interrupt.panic.patch
826c535
< File: /bsdi.sw/sw/gamma/patches/gamma4.taylor.uucp.patch
---
> File: bsdi.com:gamma4.taylor.uucp.patch
835c544
< Files: /bsdi.sw/sw/gamma/patches/gamma4.telebit.tip.patch[1-2]
---
> Files: bsdi.com:gamma4.telebit.tip.patch[1-2]
845c554
< File: /bsdi.sw/sw/gamma/patches/gamma4.tex.trek.patch
---
> File: bsdi.com:gamma4.tex.trek.patch
856c565
< File: /bsdi.sw/sw/gamma/patches/gamma4.tty.crash.patch
---
> File: bsdi.com:gamma4.tty.crash.patch
865c574
< File: /bsdi.sw/sw/gamma/patches/gamma4.uucp.1logfile.patch
---
> File: bsdi.com:gamma4.uucp.1logfile.patch
876c585
< File: /bsdi.sw/sw/gamma/patches/gamma4.wt.tape.patch
---
> File: bsdi.com:gamma4.wt.tape.patch
878a588,664
> There was a message on comp.unix.bsd a while back with a DOS program
> that determined the real disk parameters on IDE disks. It works on
> at least some ESDI and probably most other modern controllers as well.
> It prints the CMOS geometry, asks the drive for its current geometry
> and prints it, then resets the controller and asks again for the native
> geometry. It then forces DOS to be rebooted, as the controller is
> not in synch with the software. We may incorporate something like
> this into disksetup in the future, but it is a bit tricky (not all
> controllers necessarily support this). When I ran it, I discovered
> that one of my drives was using a mapped geometry, although I hadn't
> realized it.
>
> The files aren't large, so I will include them here. The shar
> contains the README file, the sources, and a uuencoded DOS executable.
> This will not work under rundos.
> File: bsdi.com:disk.geometry.dos.prog
> karels@bsdi.com (Mike Karels)
> -------
> (GAMMA 3)
> [One of the most prolific kernel fixers I've seen on the list is
> Yuval Yarom <yval@cs.huji.ac.il>. Several kernel patches against
> gamma 3 have been sent to the list. I will try to list each
> patch and the Subject line of the message with the name
> that the file will have on the archive. Thanks Yuval! SMM]
>
> gamma3.boottrap.patch: Subject: (Gamma 3) traps on boot.
> gamma3.execve.lock.patch: Subject: (Gamma 3) deadlock in execve
> gamma3.kernel.size.patch: Subject: (Gamma 3) solution to kernel size problem
> gamma3.memleak.deadlock.patch: Subject: (Gamma 3) Kernel memory leak in exec.
> gamma3.mmap.range.patch: Subject: (Gamma 3) Wrong range check in mmap.
> gamma3.msync.patch: Subject: (Gamma 3) panic in msync
> gamma3.munmap.patch: Subject: (Gamma 3) Wrong range check in munmap.
> gamma3.physio.patch: Subject: (Gamma 3) Wrong address validation in physio.
> gamma3.stack.alloc.patch: Subject: (Gamma 3) Stack allocation problem
> gamma3.vmmap.anon.patch: Subject: (Gamma 3) Wrong caching of anonymous
> memory regions
> gamma4.pagermap.wait.patch: Subject: (Gamma 3) Deadlock in page daemon
> -------
> (GAMMA 4)
> The ash bug which almost everyone seems to report is the one that makes
> ash require a semicolon before 'do' in a 'for' loop if there is no 'in'
> clause. Without the 'in' clause, there is no ambiguity about whether
> the 'do' must be a keyword, so this seems to be reasonable, if
> inconsistent, behavior. Here are some examples:
> File: bsdi.com:gamma4.ash.for.patch
> donn@bsdi.com (Donn Seeley)
> -------
> (GAMMA 4)
> At least two of my audio CD's induce an infinite loop in mitsumi_probe().
> Release:
> Gamma.4 (0.9.4)
> Repeat-By:
> Insert the disk "Claude Bolling Suite for Flute & Jazz Piano
> Trio, No. 2) (CBS records, catalog MK 42318). Run cdctl. Watch it
> spend eternity frobbing with the disk.
> Fix:
> I don't know what this test in the code is for, but commenting
> it out gets rid of the problem.
> File: bsdi.com:gamma4.cdrom.infinite.loop.patch
> John T Kohl <jtkohl@kolvir.blrc.ma.us>
> -------
> (GAMMA 4)
> Description:
> The floppy controller is returning EINVAL instead of ENOSPC
> when EOF is reached making multi-volume tar archives impossible.
> Release:
> 0.9.4
> Repeat-By:
> tar -cMvf /dev/fd0 something-larger-than-the-floppy
> Fix:
> The below *seems* to work. I've not tested it much and don't
> have time.
> File: bsdi.com:gamma4.fd.ENOSPC.patch
> gray@antaire.com (Gray Watson)
> -------
> (GAMMA 4)
> I have the following problem with low density floppies:
879a666,809
> I cannot access 360 or 720 KB floppies in my 1.2 MB 5.25 drive and 720 KB
> floppies in my 1.44 MB 3.5 drive (I use the floppycontroler from
> the adaptec 1542b).
>
> Low density access works, if I use a typed device node, but not when I want
> to use automatic density detection. The autodetection works for HD-floppies,
> but fails for others. So the driver uses the first entry of a drive for low
> density floppies (the HD entry) and the floppy access fails.
>
> I dont know why the autodetection fails, but the following workaround works
> for 720 KB in 1.44 drive and 360 KB in 1.2 drive. If you comment out the
> line, which sets the first entry as default, the driver uses the last
> entry as default, if autodetection fails. This is 360 KB for a 1.2 drive
> and 720 Kb for a 1.44 drive. This Workaround does not work for 720 KB in
> a 1.2 MB 5.25 drive, because the detection fails and the 360 KB entry is
> used as default. HD floppy access works also with this code, because the
> autodetection does not fail for HD-floppies.
>
> File: bsdi.com: gamma4.floppy.lowdensity.workaround
> "Christoph Koppe (Inf4 - hiwi)"
> <chkoppe@immd4.informatik.uni-erlangen.de>
> -------
> (GAMMA 4)
> ftime(3) uses data returned by gettimeofday(2) to fill out the timeb
> structure it is passed, this is a problem because per gettimeofday's
> man page it does not fill out the timezone part. The attached ftime.c
> does a call to localtime to get the added information. Just replace
> /usr/src/lib/libcompat/ftime.c with what folows.
> File: bsdi.com: gamma4.ftime.patch
> nerd@percival.rain.com
> -------
> (GAMMA 4)
> This m4 input:
> define(msg, printf $1)
> msg(("fmt", arg));
>
> results in:
> printf ("fmt" arg);
>
> Notice the dropped comma between "fmt" and arg.
>
> This is the patch for /usr/src/usr.bin/m4/main.c. This patch is going to
> be dropped into the master source tree. Anyone that uses m4 might want
> to try this to be sure it doesn't break anything else. I've run our m4
> tests and everything works ok.
> File: bsdi.com: gamma4.m4.patch
> sanders@bsdi.com
> -------
> (GAMMA 4)
> Here are the changes for the console driver to support multiple console
> screens, done by Vadim Antonov. As reported earlier, this driver allows
> multiple character-mode console sessions (default 8, can be changed with
> "options NPCSCREENS=12", etc). X and rundos can still be used, but they
> take over the entire console while running and it is not possible to switch
> to another screen until they exit (or rundos is suspended). Output to
> any of the virtual screens while X or rundos is using the display
> will be discarded.
>
> A shar file below includes the patches for the gamma4 console driver,
> /usr/src/sys/i386/isa/pccons.c.
> File: bsdi.com: gamma4.multiconsole.patch
> karels@bsdi.com (Mike Karels)
> -------
> (GAMMA 4)
> > > The termcap entries provided with the new console driver 'break' less, vi,
> > > emacs, and probably lots of other stuff too.
> > The new termcap entry for ibmpc3 is incorrect. Correct escape
> > sequence for Insert Line should be al=\E[L.
> Oops. You are right. Anyone who installed/installs the new driver should
> use this corrected termcap. I'm not sure how that happened, but obviously
> it happened after I had done most of my testing.
> File: bsdi.com: gamma4.pc3termcap.patch
> karels@bsdi.com (Mike Karels)
> -------
> (GAMMA 4)
> > At the end of the script I get this message
>
> > stty: stdout appears redirected, but stdin is the control descriptor
>
> > Is this normal?
>
> There is a little bug in stty that causes this message to be printed
> even when the "-f" flag is used. It's harmless but if it annoys you
> here's the patch:
> File: bsdi.com: gamma4.stty.message.patch
> huntting@misc.glarp.com
> -------
> (GAMMA 4)
> Ain't this insidious? This fix seems to make xview work reasonably well
> (enough so that I can now work on the CDROM bugs in workman rather than
> xview bugs in workman...watch this space for more details!).
> Description:
> syscall(2) doesn't work right. It leaves $sp off by a word,
> which can lead to disaster when it's called repeatedly (as it is in
> XView3.0).
> Release:
> Gamma.4 (0.9.4)
> Repeat-By:
> Write a program that has a local variable on the stack;
> initialize it, then call syscall() repeatedly. Note that the value
> eventually gets trashed when the stack works its way up over the variable.
> File: bsdi.com: gamma4.syscall.patch
> John T Kohl <jtkohl@kolvir.blrc.ma.us>
> -------
> (GAMMA 4)
> Seems xman has a problem. It appeared to have a problem with the MANPATH, but
> in reality it was with the "cat" subdirectories. In looking at the source, it
> appears that man.c requires MAN to be set to the subdirectory prefix which in
> our case is "cat". However, vendor.h sets MAN to "man".
> File: bsdi.com: gamma4.xman.patch
> ektron1!wutt@uunet.uu.net (William Wuttke)
> -------
> If any of you have had to SLIP into a site with a terminal server
> you know how difficult it can be to get the suplied startslip
> program to function with anything but the "standard" bsd login
> sequence.
>
> The enclosed shar file has a perl script which can be "easily"
> modified to deal with a wide range of send-expect login sequences.
> It does not have a chit-chat config file, you must edit the script
> itself. I've tried to make it easy to modify, but it's still perl
> (the worlds most pathalogically unreadable computer language)...
>
> The present config is used to dial in to the Annex where I work.
>
> I sugest placing the "slipup" script in /usr/local/bin, and the
> slipup.conf in /etc (if you place slipup.conf elsewhere, be shure
> to change the pathname in the "slipup" script that reads it).
>
> File: bsdi.com: huntting.slipup.perl
> Brad Huntting <huntting@glarp.com>
> -------
> (GAMMA 4)
> tmpnam() will return a filename in the form of "/var/tmp//tmp..."
> because it assumes P_tmpdir (from stdio.h) does not end in a slash
> (which it does).
>
> For those who care here is a "graceful" patch -- or you can remove the
> extra / from tmpnam.c. :-)
>
> File: bsdi.com: tmpnam.patch
> gray@antaire.com (Gray Watson)
> -------
>
883c813
< Date: Mon Jan 18 19:00:29 EST 1993
---
> Date: Wed Feb 17 19:00:29 EST 1993
933c863
< for BSD/386 systems. The archive is at bsdi.com [192.48.96.23] in the
---
> for BSD/386 systems. The archive is at bsdi.com [153.39.128.11] in the
938,939c868,872
< The archive includes all of the patches that have been posted to the beta
< mailing list and a list of all postings to the bata list, stored by month.
---
> The archive includes the old postings from the beta and gamma mailing
> lists and the new bsdi-users mailing list. Patches are on-line for
> the gamma release of BSD/386. The beta patches will be removed in a
> reorganization that will occur very soon.
>
943,946d875
<
< I will also be setting up a "gamma" directory under /bsdi.sw/sw/gamma
< for storing programs and patches for the gamma release of BSD/386.
< The gamma mailing list will also be archived there on a monthly basis.