From owner-freebsd-bugs Sun Feb 19 17:48:10 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id RAA22614 for bugs-outgoing; Sun, 19 Feb 1995 17:48:10 -0800 Received: from seraph.uunet.ca (uunet.ca [142.77.1.254]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id RAA22606 for ; Sun, 19 Feb 1995 17:48:05 -0800 Received: from portnoy.canrem.com ([198.133.42.17]) by mail.uunet.ca with SMTP id <172875-3>; Sun, 19 Feb 1995 17:00:11 -0500 Received: from canrem.com by portnoy.canrem.com (4.1/SMI-4.1) id AA29143; Sun, 19 Feb 95 16:55:47 EST Received: by canrem.com (PCB-UUCP 1.1f) id 1D0DC6; Sun, 19 Feb 95 16:38:18 -0500 To: bugs@FreeBSD.org Subject: FreeBSD 2.0 installation problems From: barnaby.ng@canrem.com (Barnaby Ng) Message-Id: <60.17148.104.0C1D0DC6@canrem.com> Date: Sun, 19 Feb 1995 16:23:00 -0500 Organization: CRS Online (Toronto, Ontario) Sender: bugs-owner@FreeBSD.org Precedence: bulk I'm the unfortunate soul who had the "Fatal code=5888" error while trying to install FreeBSD 2.0 from Walnut Creek CD. I took the "proper" way to fix the problem: changed the extended BIOS translation and low level format the drives. (Justin Gibbs suggested that I should specify 255/63 translation in fdisk, but it didn't work) Now I got passed the initial stage of installation (boot and cpio) and tried to install the bindist. After I specified the source of the bindist, sysinstall verified the checksums, and extracted some files onto my disk, and then it STOPPED. The install screen still shown "Extracting bindist distribution. Please wait!", but it just sit there, no disk i/o, no nothing. The machine was not hung. I could switch between the install and debug screen, but it just won't finish installing bindist. I'd tried other modules: no problem installing games, but ran into the same problem installing manpages. I tried changing hardware setup like slow the CD-ROM transfer rate to 5MB/sec, disable synchronous negotiation, introduce more wait state etc. NOTHING helps. The debug screen show the followings:- (a bunch of "/stand/cpio: umount linked" message) /stand/cpio:umount linked to tip umount 2286 blocks Progress Progress Progress Extracting bindist, please wait. And then it just sit there. HELP PLEASE!!! % Barnaby Ng % Toronto, Canada % barnaby.ng@canrem.com From owner-freebsd-bugs Sun Feb 19 17:53:03 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id RAA23033 for bugs-outgoing; Sun, 19 Feb 1995 17:53:03 -0800 Received: from helix.nih.gov (helix.nih.gov [128.231.2.3]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id RAA23026 for ; Sun, 19 Feb 1995 17:53:02 -0800 Received: by helix.nih.gov (940715.SGI.52/1.35(m-sg-1.0)) id AA08020; Sun, 19 Feb 95 13:50:09 -0500 Date: Sun, 19 Feb 95 13:50:09 -0500 From: crtb@helix.nih.gov (Chuck Bacon) Message-Id: <9502191850.AA08020@helix.nih.gov> To: bugs@FreeBSD.org Subject: xdvi and latex2e Sender: bugs-owner@FreeBSD.org Precedence: bulk BUG: latex2e and xdvi both root in /home/jmz/local instead of /usr/local. So I created /home/jmz -> /usr. This apparently worked, although strings xdvi revealed that /home/jmz was needed after installation too. Latex2e apparently works. At least it creates a .dvi file. But both dvips and xdvi either fail or go into a loop trying to find fonts. In particular, xdvi gives a large collection of messages of the form: - MakeTeXPK cmti10 300 300 magstep\(0\) //home/jmz/local/lib/texmf/fonts/pk/cmti10.300pk already exists! - MakeTeXPK cmr10 300 300 magstep\(0\) //home/jmz/local/lib/texmf/fonts/pk/cmr10.300pk already exists! Can't find font cmti10. Similar five-line messages occur for many font names. Always the font name cited for the first MakeTeXPK invocation of a pair is the subject of the "Can't find" message. Of course, I'd rather have 360-dpi fonts, since I have a 360-dpi printer. Should I try to find pre-built fonts from a CTAN archive, or can I trust MakeTeXPK to satisfy my needs? Chuck Bacon - crtb@helix.nih.gov ABHOR SECRECY - DEFEND PRIVACY From owner-freebsd-bugs Sun Feb 19 18:05:33 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id SAA23567 for bugs-outgoing; Sun, 19 Feb 1995 18:05:33 -0800 Received: from relay4.UU.NET (relay4.UU.NET [192.48.96.14]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id SAA23561 for ; Sun, 19 Feb 1995 18:05:31 -0800 Received: from ast.com by relay4.UU.NET with SMTP id QQydue19371; Sun, 19 Feb 1995 13:13:12 -0500 Received: from trsvax.fw.ast.com (fw.ast.com) by ast.com with SMTP id AA08924 (5.67a/IDA-1.5 for uunet!freebsd.org!freebsd-bugs); Sun, 19 Feb 1995 10:16:44 -0800 Received: by trsvax.fw.ast.com (/\=-/\ Smail3.1.18.1 #18.1) id ; Sun, 19 Feb 95 12:13 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #18) id m0rgG2o-0004vtC; Sun, 19 Feb 95 12:07 CST Message-Id: Date: Sun, 19 Feb 95 12:07 CST To: freebsd-bugs@FreeBSD.org, jkh@freefall.cdrom.com From: uhclem@nemesis.lonestar.org (Frank Durda IV) Sent: Sun Feb 19 1995, 12:07:41 CST Subject: Bugs in snap 021095 Cc: uhclem@nemesis.lonestar.org Sender: bugs-owner@FreeBSD.org Precedence: bulk Hello, I am working with getting the Matsushita(Panasonic) CD-ROM driver running on 2.1. To that end I installed the latest snap (021095), which I had to re-install repeatedly (10 times?) due to some bugs that have surfaced in the install procedure. I installed 2.0-R in one try the previous evening. (I suspect the problem is that I an doing FTP from a local server rather than from one of the Internet sites and I don't think that option was tested very well.) Is this the address to report bugs in a SNAP version to? Let me know and I will type them up. Please reply at uhclem%nemesis@fw.ast.com If you reply to my domain address, it may take a week for the mail to reach me, due to a problem at the domain mail handler (not under my control). Thanks Frank Durda IV |"The Knights who say "LETNi" or uhclem%nemesis@trsvax.ast.com (Internet)| demand... A WORKING PENTIUM!!! ...letni!rwsys!nemesis!uhclem |"A what?" ...decvax!trsvax.fw.ast.com!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983 From owner-freebsd-bugs Sun Feb 19 18:12:37 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id SAA23788 for bugs-outgoing; Sun, 19 Feb 1995 18:12:37 -0800 Received: from xmission.xmission.com (root@xmission.xmission.com [198.60.22.2]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id SAA23782 for ; Sun, 19 Feb 1995 18:12:36 -0800 Received: (from rlenk@localhost) by xmission.xmission.com (8.6.9/8.6.9) id RAA03402; Sun, 19 Feb 1995 17:17:16 -0700 From: Ron Lenk Message-Id: <199502200017.RAA03402@xmission.xmission.com> Subject: Bug with PPP To: bugs@FreeBSD.org Date: Sun, 19 Feb 1995 17:17:15 -0700 (MST) Cc: rlenk@xmission.com (Ron Lenk) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 5654 Sender: bugs-owner@FreeBSD.org Precedence: bulk I have encountered a possible bug in the implementation of the PPP on FreeBSD 2.0, both the "RELEASE", and in all of the following snapshots, including 950210. The problem can best be described as a failure of the PPP link, but only when certain network applications are executed. The best repeatable examples that I have noted are during FTP sessions to "ftp.mcom.com", and during the startup of IRC-II. The modem connection is usually lost as well. There are never any error messages reported, either to the console, or to /var/log/messages. The only possible way to resolve the problem is to kill pppd, and then restart it, assuming that the connection is not lost. SLIP works fine. The command line used to invoke pppd was: pppd crtscts defaultroute /dev/cuaa0 57600 The connection is made to my employer's network. We use Xylogics Micro-Annex terminal servers, equipped with both SLIP and PPP. I have attached my machine's configuation data, as well as a copy of the my kernel configuration file for the 950210 snapshot. I would appreciate any advice on how to resolve the problem. ( It's actually not a huge problem, but I'd like to have a working PPP ) Other than this, the latest snapshot appears to be more stable than any of the previous. The only other bug that I know of involves non-working menus in some of the simple apps such as "xman" that are included with X. ( I'm assuming that this is probably a bug in the Athena Widget Set that is included with XFree86 3.1.1 ) Finally, I would like to thank the entire FreeBSD development team for producing such a great OS. Ron Lenk, Technical support, XMission Internet. rlenk@xmission.com ------------ My configuration: Genoa TurboExpress 486-VL3 Motherboard. Intel 486-DX2 66 Mhz processor. 20 Mbytes 60 ns RAM. Adaptec 2842-VL SCSI controller. (ahc0) Micropolis 2210 1.05 Gbyte SCSI hard drive. (sd0) Quantum PD170S 170 Mbyte SCSI hard drive. (sd1) Texel DM-5028 SCSI CD-ROM drive. (cd0) Diamond Stealth 64 DRAM. Teac 3.5" and 5.25" floppies (fd0, fd1) 3Com 3C503 Ethernet adapter (ed0) Logitech bus mouse. 2 16550A UARTs (sio0, sio1) Practical Peripherals PM288MT V.34 modem. ( on cuaa0 ) My kernel configuration file for the 950210 snapshot: ------------- # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # GENERIC,v 1.31 1995/02/09 11:21:07 jkh Exp # machine "i386" #cpu "I386_CPU" cpu "I486_CPU" #cpu "I586_CPU" ident HACKED maxusers 16 #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 options "SCSI_DELAY=15" #Be pessimistic about Joe SCSI device options BOUNCE_BUFFERS #include support for DMA bounce buffers options UCONSOLE #Allow users to grab the console config kernel root on sd0 swap on sd0 and vn0 dumps on sd0 controller isa0 #controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 #tape ft0 at fdc0 drive 2 #controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr #disk wd0 at wdc0 drive 0 #disk wd1 at wdc0 drive 1 #controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr #disk wd2 at wdc1 drive 0 #disk wd3 at wdc1 drive 1 #controller ncr0 controller ahc0 at isa? bio irq ? vector ahcintr #controller bt0 at isa? port "IO_BT0" bio irq ? vector btintr #controller uha0 at isa? port "IO_UHA0" bio irq ? drq 5 vector uhaintr #controller ahc1 at isa? bio irq ? vector ahcintr #controller ahb0 at isa? bio irq ? vector ahbintr #controller aha0 at isa? port "IO_AHA0" bio irq ? drq 5 vector ahaintr #controller aic0 at isa? port 0x340 bio irq 11 vector aicintr #controller nca0 at isa? port 0x1f88 bio irq 10 vector ncaintr #controller nca1 at isa? port 0x350 bio irq 5 vector ncaintr #controller sea0 at isa? bio irq 5 iomem 0xc8000 iosiz 0x2000 vector seaintr controller scbus0 device sd0 device sd1 device sd2 #device st0 device cd0 #Only need one of these, the code dynamically grows #device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr #device mcd0 at isa? port 0x300 bio irq 10 vector mcdintr #device mcd1 at isa? port 0x340 bio irq 11 vector mcdintr #device scd0 at isa? port 0x230 bio device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr #device sio2 at isa? port "IO_COM3" tty irq 5 vector siointr #device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr device mse0 at isa? port 0x23c tty irq 5 vector mseintr device lpt0 at isa? port? tty irq 7 vector lptintr #device lpt1 at isa? port? tty #device lpt2 at isa? port? tty #device de0 device ed0 at isa? port 0x280 net irq 9 iomem 0xd8000 vector edintr #device ed1 at isa? port 0x300 net irq 5 iomem 0xd8000 vector edintr #device ie0 at isa? port 0x360 net irq 7 iomem 0xd0000 vector ieintr #device ep0 at isa? port 0x300 net irq 10 vector epintr #device lnc0 at isa? port 0x280 net irq 10 drq 0 vector lncintr #device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 vector le_intr #device ze0 at isa? port 0x300 net irq 5 iomem 0xd8000 vector zeintr pseudo-device loop pseudo-device ether pseudo-device log pseudo-device sl 1 pseudo-device ppp 1 pseudo-device pty 16 pseudo-device speaker pseudo-device gzip # Exec gzipped a.out's pseudo-device vn ---------- From owner-freebsd-bugs Sun Feb 19 18:14:04 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id SAA23843 for bugs-outgoing; Sun, 19 Feb 1995 18:14:04 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id SAA23827 for ; Sun, 19 Feb 1995 18:13:50 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA10354; Sun, 19 Feb 1995 19:23:56 +0100 Received: by sax.sax.de (8.6.9/8.6.9-s1) with UUCP id TAA20399 for bugs@FreeBSD.org; Sun, 19 Feb 1995 19:23:55 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.6.9/8.6.9) id SAA01199 for bugs@FreeBSD.org; Sun, 19 Feb 1995 18:56:51 +0100 From: J Wunsch Message-Id: <199502191756.SAA01199@uriah.heep.sax.de> Subject: Re: Bug in tar To: bugs@FreeBSD.org Date: Sun, 19 Feb 1995 18:56:50 +0100 (MET) In-Reply-To: from "Pete Carah" at Feb 17, 95 09:53:00 am Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 797 Sender: bugs-owner@FreeBSD.org Precedence: bulk As Pete Carah wrote: > > >file /etc/rmt > >/etc/rmt: symbolic link to ../usr/etc/rmt > > >So you see it's not quite so simple. If no one objects, I'll add > >the link to the install rule in rmt.. > > Main reason it's not that simple is that we can make that change to > our own sources all we want, but it won't help the user on a Sun or > SGI or HP, etc etc. trying to use our tape. The symlink really has > to be there. ... and btw., it would be a _very bad_ idea to rename the ``outgoing call'' for the rmt utility into /usr/sbin/rmt or something else, since this will just prevent us from using any arbitrary box as a remote rmt server. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Sun Feb 19 18:29:20 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id SAA24291 for bugs-outgoing; Sun, 19 Feb 1995 18:29:20 -0800 Received: from post.demon.co.uk (post.demon.co.uk [158.152.1.72]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id SAA24282 for ; Sun, 19 Feb 1995 18:29:15 -0800 Received: from pencotts.demon.co.uk by post.demon.co.uk id aa01529; 20 Feb 95 0:23 GMT Received: (from root@localhost) by pencotts.demon.co.uk (8.6.9/8.6.6) id AAA05771 for bugs@freebsd.org; Mon, 20 Feb 1995 00:21:52 GMT From: Andrew.Gordon@net-tel.co.uk X400-Received: by mta "eldorado" in "/PRMD=net-tel/ADMD=gold 400/C=gb/"; Relayed; Mon, 20 Feb 95 0:20:59 +0000 X400-Received: by mta "net-tel cambridge" in "/PRMD=net-tel/ADMD=gold 400/C=gb/"; Relayed; Mon, 20 Feb 95 0:20:56 +0000 X400-Received: by "/PRMD=NET-TEL/ADMD=Gold 400/C=GB/"; Relayed; Mon, 20 Feb 95 0:20:56 +0000 X400-MTS-Identifier: ["/PRMD=NET-TEL/ADMD=Gold 400/C=GB/";hst:298-950220002056-7FAC] X400-Content-Type: P2-1984 (2) X400-Originator: Andrew.Gordon@net-tel.co.uk Original-Encoded-Information-Types: IA5-Text X400-Recipients: bugs@freebsd.org Date: Mon, 20 Feb 95 0:20:56 +0000 Content-Identifier: Bug in ppp packe Message-Id: <"MAC-950220002210-359B*/G=Andrew/S=Gordon/O=Net-Tel Computer Systems Ltd/PRMD=Net-Tel/ADMD=Gold 400/C=GB/"@MHS> To: bugs@FreeBSD.org Subject: Bug in ppp packet filter (and fix!) Sender: bugs-owner@FreeBSD.org Precedence: bulk Bug in: /usr/sbin/ppp Version: SNAP-950210, and source of about 2 days ago Detail: The 'set ifilter'/'set ofilter' commands accept a syntax containing IP addresses and/or protocol+port, but in the case where both are supplied, it happily accepts the command but ignores the proto+port It also attempts to handle the case where the second IP address is omitted, but this doesn't work. Fix: In src/usr.sbin/ppp/filter.c: *** filter.c.old Sun Feb 19 22:37:05 1995 --- filter.c Sun Feb 19 22:44:11 1995 *************** *** 317,321 **** } ! fp->proto = proto = ParseProto(argc, argv); if (proto == P_NONE) { if (ParseAddr(argc, argv, &fp->saddr, &fp->smask, &fp->swidth)) { --- 317,321 ---- } ! proto = ParseProto(argc, argv); if (proto == P_NONE) { if (ParseAddr(argc, argv, &fp->saddr, &fp->smask, &fp->swidth)) { *************** *** 327,333 **** } proto = ParseProto(argc, argv); ! if (proto) { ! argc--; argv++; ! } } } else { --- 327,333 ---- } proto = ParseProto(argc, argv); ! } ! if (proto) { ! argc--; argv++; } } else { *************** *** 340,343 **** --- 340,344 ---- val = 1; + fp->proto = proto; switch (proto) { *************** *** 353,357 **** } [The key change is the extra line fp->proto = proto; - the rest is just cleaning up]. From owner-freebsd-bugs Sun Feb 19 18:44:41 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id SAA24641 for bugs-outgoing; Sun, 19 Feb 1995 18:44:41 -0800 Received: from cabri.obs-besancon.fr (cabri.obs-besancon.fr [193.52.184.3]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id SAA24634 for ; Sun, 19 Feb 1995 18:44:39 -0800 Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C) id AA20082; Mon, 20 Feb 95 03:43:26 +0100 Date: Mon, 20 Feb 95 03:43:26 +0100 From: jmz@cabri.obs-besancon.fr (Jean-Marc Zucconi) Message-Id: <9502200243.AA20082@cabri.obs-besancon.fr> To: crtb@helix.nih.gov Cc: bugs@FreeBSD.org In-Reply-To: <9502191850.AA08020@helix.nih.gov> (crtb@helix.nih.gov) Subject: Re: xdvi and latex2e X-Mailer: Emacs Sender: bugs-owner@FreeBSD.org Precedence: bulk >>>>> "Chuck" == Chuck Bacon writes: > BUG: latex2e and xdvi both root in /home/jmz/local > instead of /usr/local. :-) :-) > So I created /home/jmz -> /usr. It would be better to install the package with the -p option: pkg_add -p /usr/local latex.tgz. There is no simple fix for xdvi or dvips (I will replace the packages at freefall). > This apparently worked, although strings xdvi revealed that > /home/jmz was needed after installation too. > Latex2e apparently works. At least it creates a .dvi file. > But both dvips and xdvi either fail or go into a loop trying > to find fonts. In particular, xdvi gives a large collection > of messages of the form: > - MakeTeXPK cmti10 300 300 magstep\(0\) > //home/jmz/local/lib/texmf/fonts/pk/cmti10.300pk already exists! > - MakeTeXPK cmr10 300 300 magstep\(0\) > //home/jmz/local/lib/texmf/fonts/pk/cmr10.300pk already exists! > Can't find font cmti10. > Similar five-line messages occur for many font names. Always > the font name cited for the first MakeTeXPK invocation of a pair > is the subject of the "Can't find" message. This is because the package is bogus. > Of course, I'd rather have 360-dpi fonts, since I have a 360-dpi > printer. The best solution is to get dvips and xdvi in the ports directory and to install from the sources. > Should I try to find pre-built fonts from a CTAN archive, or > can I trust MakeTeXPK to satisfy my needs? pre-build fonts may not be suited to your printer. Installing from the sources allows you to specify the printer mode. > Chuck Bacon - crtb@helix.nih.gov > ABHOR SECRECY - DEFEND PRIVACY Jean-Marc. -- ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~ Jean-Marc Zucconi | jmz@cabri.obs-besancon.fr Observatoire de Besancon | F 25010 Besancon cedex | PGP Key: finger jmz@cabri.obs-besancon.fr ========================================================================= From owner-freebsd-bugs Sun Feb 19 22:50:48 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id WAA00333 for bugs-outgoing; Sun, 19 Feb 1995 22:50:48 -0800 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id WAA00326; Sun, 19 Feb 1995 22:50:47 -0800 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: uhclem%nemesis@fw.ast.com (Frank Durda IV) cc: freebsd-bugs@FreeBSD.org Subject: Re: Bugs in snap 021095 In-reply-to: Your message of "Sun, 19 Feb 95 12:07:00 CST." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 19 Feb 1995 22:50:47 -0800 Message-ID: <325.793263047@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: bugs-owner@FreeBSD.org Precedence: bulk > Is this the address to report bugs in a SNAP version to? Let > me know and I will type them up. Yes it is, please do! You should not have had to install this thing 10 times, regardless of what ftp site you may have used. > Please reply at uhclem%nemesis@fw.ast.com You really should set your Reply-To address if you're going to maintain this practice - it's entirely unreasonable to expect those replying to always have to hand-edit their outgoing replies. I know that I am going to simply forget to do so 4 times out of 5 and I get far too much mail to make any special exceptions for people.. Especially when it can be done with a simple change to ones MH config or sendmail.cf. Jordan From owner-freebsd-bugs Mon Feb 20 06:25:10 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id GAA22838 for bugs-outgoing; Mon, 20 Feb 1995 06:25:10 -0800 Received: from isl.cf.ac.uk (isl-gate.elsy.cf.ac.uk [131.251.22.1]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id GAA22804 for ; Mon, 20 Feb 1995 06:24:25 -0800 Received: (from paul@localhost) by isl.cf.ac.uk (8.6.9/8.6.9) id OAA13182; Mon, 20 Feb 1995 14:18:52 GMT From: Paul Richards Message-Id: <199502201418.OAA13182@isl.cf.ac.uk> Subject: Re: Another lnc0 bug? To: alex@ineos.ac.ru Date: Mon, 20 Feb 1995 14:18:52 +0000 (GMT) Cc: bugs@FreeBSD.org In-Reply-To: <199502171248.PAA07860@alpha.ineos.ac.ru> from "Alexander V. Polyakov" at Feb 17, 95 03:48:02 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1327 Sender: bugs-owner@FreeBSD.org Precedence: bulk In reply to Alexander V. Polyakov who said > > I'm using a PCnet-PCI (AMD 79C970) ethernet card and it also Hmm, I've had a report that these aren't even seen by the driver, obviously they are. > produces weird error messages on the console all the time. > But instead of "Memory error -- Resetting" they say: > >