Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!hp9000.csc.cuhk.hk!uakari.primate.wisc.edu!usenet.coe.montana.edu!warp.mhd.montana.edu!osynw From: osynw@warp.mhd.montana.edu (Nate Williams) Newsgroups: comp.unix.bsd Subject: Unofficial User Supported Bug List being created Message-ID: <1992Jul29.174221.20280@coe.montana.edu> Date: 29 Jul 92 17:42:21 GMT Sender: usenet@coe.montana.edu (USENET News System) Organization: Try to get some. Lines: 76 Since the Jolitz's and Chris are very busy people, I figured it would be nice for them and for us to have a bug list. Since I have some free time until school starts (1 month), I am volunteering to try and make an organized bug list for 386BSD 0.1. I will attempt to keep this list current with recent official and unofficial patches, so when the first patch to 0.1 is released, I will try to update my list (assuming I have it out by the time the patch is released). The advantages to us doing it are: ---------------------------------- 1) It takes some work of the developers. When I get the list organized, I can send it off to the maintainers of 386BSD, and as people send in more bugs I can try and organize them in a (hopefully) coherent manner. 2) It may help co-ordination of the user group's efforts. There are alot of talented people who read news, and it would be nice to know who is working on what so we don't get redundancy. 3) This kinda of thing may help new users. I hope to integrate Terry Lambert's FAQ into this list, and separate bugs into kernel bugs, installation bugs, user program bugs, and other misc. bugs. 4) It's just plain nice to know sometimes that what you are seeing is a bug, and not you going crazy expecting something else. ;-) What I propose is people fill out a simple bug report form, which is hopefully easier to fill out than fixing the bugs. If you would send me the bug report, with a mail heading of 386BSD BUGS, I can organize these reports and then re-post them to the network and/or upload them to the ftp sites. Here is my second shot at a BUG REPORT form. ----------------------------BUG REPORT------------------------ Name: Email address: Date: Hardware info: [Whatever you think is necessary for creating the problem CPU, BIOS, Chipset, Memory, cards, disk, ....] Problem description: [As much info as you can give, how to re-produce, etc..] Problem suspicions: [What/where you think the problem is if you don't have a fix] Solution: ---------------------------------------------------------------- So if you know of bugs in 386BSD 0.1, please send me email with the subject line of: 386BSD BUGS, and I will try and get this thing together sometime this week. At first, if your bug-list is in a different format, and you think I will understand it, send it to me in whatever form you can, but as time goes by, I would like to auto-mate this a little so as you find new bugs, try and use the form. (which will problaby change as time goes on) Thanks a lot Bill and Lynne et al. for giving us 386BSD, Nate (if you have problems emailing this account, try the one in my .sig) -- osynw@terra.oscs.montana.edu | A hacker w/out a home. Anyone interested work: (406) 994-5991 | in a used Sys. Admin., which alot of home: (406) 586-0579 | good hacks left?