From owner-freebsd-bugs Thu Feb 23 07:43:51 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id HAA04951 for bugs-outgoing; Thu, 23 Feb 1995 07:43:51 -0800 Received: from stcgate.statcan.ca (stcgate.statcan.ca [142.206.192.1]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id HAA04943 for ; Thu, 23 Feb 1995 07:43:38 -0800 Received: from stcinet.statcan.ca by stcgate.statcan.ca id aa06427; 23 Feb 95 10:38 EST Received: by statcan.ca (5.0/SMI-SVR4) id AA22006; Thu, 23 Feb 1995 10:47:10 +0500 From: Andrew Atrens Message-Id: <9502231547.AA22006@statcan.ca> Subject: umount bug To: bugs@FreeBSD.org Date: Thu, 23 Feb 1995 10:47:10 -0500 (EST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1834 Sender: bugs-owner@FreeBSD.org Precedence: bulk Running FreeBSD 2.0 The problem in a nutshell: ------------------------- umount -a -t nfs umount -a -t ufs umount -a -t procfs all run without error, but fail to unmount anything. the corollary is that occasionally the system allows me to mount nfs filesystems twice. and umount -a -t cd9660 barfs with "umount: cd9660: unknown mount type" ------- ------- I tried the January (complete) snapshot of the OS, with similar results. ------- ------- I'm currently running the February 10th (complete) snapshot, and the problems still persist. Other pet peeves ( maybe features, not bugs ): ============================================= My soundblaster 16 won't work ( according to the docs its not supported, however the information in "Voxware" leads me to believe there is a chance it may work ) My 3Com Etherlink 3 card only works on the AUI port ( I read the newsgroup references to fixing this with a "link" paraemeter given to ifconfig combined with reprogramming the card to use the UTP port, but no dice, she still doesn't work. ) My 3Com Etherlink 3 card barfs a lot with error 2002, apparently it doesn't like our level of network traffic ?? The FreeBSD boot: program needs to do away with the really hokey "hd(x,x)" device. I would like to hardcode a non-standard boot disk as default, eg sd(2,a), however since I have a couple of ide disks (which may soon be going away) I am relunctant to, because the "hd" number of my scsi disk changes depending on how many ide's are installed on my system (ack!). Though I griping here, overall I'm very impressed with the product, and am recommending it to folks around here. Especially impressive is the memory management (as compared to linux 1.1.75). Regards, Andrew Atrens, Statistics Canada.