From owner-freebsd-questions Mon Dec 22 21:44:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA04795 for questions-outgoing; Mon, 22 Dec 1997 21:44:50 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from gdi.uoregon.edu (cisco-ts7-line16.uoregon.edu [128.223.150.63]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA04775 for ; Mon, 22 Dec 1997 21:44:42 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id VAA07780; Mon, 22 Dec 1997 21:44:35 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Date: Mon, 22 Dec 1997 21:44:34 -0800 (PST) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: John Frader cc: freebsd-questions@FreeBSD.ORG Subject: Re: Bad file descriptor? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Dec 1997, John Frader wrote: > Below is what I started getting in the system security messages. > Could anyone tell me what this means? If I do a ls in /dev I don't see ch0 > but if I do a ls -l, I get the same thing /dev/ch0: Bad file descriptor > > checking setuid files and devices: > find: /dev/ch0: Bad file descriptor Your /dev/ch0 file is corrupted. If you don't use the SCSI tape changer, you can simply remove the file. If you do, then remove /dev/ch0 then run `/dev/MAKEDEV ch0'. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major