From owner-freebsd-alpha Sat Jan 20 19:43:43 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id BC03537B400 for ; Sat, 20 Jan 2001 19:43:25 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id WAA11767; Sat, 20 Jan 2001 22:43:25 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id f0L3hOG08174; Sat, 20 Jan 2001 22:43:24 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 20 Jan 2001 22:43:24 -0500 (EST) To: leclercn@videotron.ca Cc: freebsd-alpha Subject: Re: FIFO files: device not configured In-Reply-To: <3A6A5558.1040300@videotron.ca> References: <3A6A156B.1010809@videotron.ca> <14954.13113.352982.366550@grasshopper.cs.duke.edu> <3A6A5558.1040300@videotron.ca> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14954.23071.555967.914243@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org tcn writes: > > The only thing I can think of which makes any sense is that, by > > default, sio1 is reserved for the kernel debugger. (This should > > Unfortunately, my modem is assigned to sio2 on IO_COM3, irq 5 with > flags 0x20000. I tried removing the 16550 flag but it didn't do > anything. I removed all flags from all sios and tried again with no > success. It seems like the problem does not lie in the communication > ports configuration. I suspect something else like missing sockets > (since from what I understand, fifo files are sockets). You can verify for yourself that fifos work. Read the mkfifo(1) man page and play with the result. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message