Date: Sun, 12 May 1996 13:48:45 +0200 (MET DST) From: J Wunsch <j@uriah.heep.sax.de> To: coredump@nervosa.com (invalid opcode) Cc: freebsd-bugs@FreeBSD.org, jkh@time.cdrom.com Subject: Re: List of open Problem Reports Message-ID: <199605121148.NAA06979@uriah.heep.sax.de> In-Reply-To: <Pine.BSF.3.91.960512013953.20166B-100000@onyx.nervosa.com> from invalid opcode at "May 12, 96 02:07:17 am"
next in thread | previous in thread | raw e-mail | index | archive | help
As invalid opcode wrote: > > [1995/01/30] bin/198 1.1.5.1 pine binary loops; top shows fancy values > I'm sure we can assume this is fixed, as I'm running pine now. You run a 1.1.5.1 binary? > > [1995/05/13] misc/403 FreeBSD 1-compiled tcsh, bash and zsh binaries dump > > I'm sure this is fixed now. Again, a 1.1.5.1 binary? (Though i'm also in favor of ``timing out'' these PR's some day.) > > [1995/06/17] kern/528 slow 386 reports excessive interrupt-level buffer ov > > Isn't this natural for a slow 386? No. I can run a sio at 115 kbps on a 386/16 with almost zero of these messages. (But quite possible that the problem has either been fixed, or the PR refers to some other circumstances why this happened.) > > [1995/08/07] bin/661 Hercules is not capable of having a ISO-Latin1 Scree > > Is this a freebsd-bug? Yes. The console driver should remap the character table (as good as possible), and this should be documented in a way so it can easily be found (e.g. comments in /etc/sysinstall). I think it's the latter that's still missing. > > [1995/08/15] i386/692 My modem is not found if my external cache is disabl > > Is this a freebsd-bug or just a faulty computer? The internal modem with emulated UART saga. Bruce made the probe more benign i think, so the PR should be verified again by the submitter. > > [1995/09/23] docs/735 missing description for mount options in fstab(5) ma > > I believe this are documented in mount(8). No. The long options are deprecated, but still working. We should either document them (and mark as obsolete), or disable. > > [1995/10/03] kern/765 umount -f can`t umount a NFS filesystem in use > > This is a known bogon of NFS, not umount. No. umount -f is supposed to ``forcibly'' unmount, so it should not hang but revoke the underlying objects. > > [1995/11/27] bin/841 stale nfs mounts cannot be umounted > > This is a known bogon of NFS, not freebsd. No, unmounting should always be possible (the term `mount' always refers to a local machine). One must be able to get rid of a stale mount, since it's often impossible to ``un-stale'' it again. > > [1996/01/25] kern/971 Default limits for number of processes per user ridi > > Opinion, and most likely fixed. No. The default maxproc limit should be dynamic, dependent on the size of the machine/system. The current fixed value of 40 is too high for a 386/16 (you could still trash this machine with the fork trap), but too low for somebody with 32 MB RAM and a decent X11 workstation. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605121148.NAA06979>