Date: Tue, 06 Nov 2001 10:00:31 -0700 From: Warner Losh <imp@harmony.village.org> To: Dag-Erling Smorgrav <des@ofug.org> Cc: "Kevin D.Wooten" <kwooten@home.com>, freebsd-hackers@FreeBSD.ORG Subject: Re: devfs? Message-ID: <200111061700.fA6H0V724455@harmony.village.org> In-Reply-To: Your message of "06 Nov 2001 17:16:31 %2B0100." <xzp3d3rc1sw.fsf@flood.ping.uio.no> References: <xzp3d3rc1sw.fsf@flood.ping.uio.no> <77717.1004986298@critter.freebsd.dk> <01110512492207.08198@newton.cevio.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <xzp3d3rc1sw.fsf@flood.ping.uio.no> Dag-Erling Smorgrav writes: : Kevin D.Wooten <kwooten@home.com> writes: : > Well the linux devfs has a compatibility mode that maintains a /dev : > that looks exactly like pre-devfs ( the actual list of files is : > static ), and only links up ( mknod ) the newly added devices to the : > pre-existing files. There is also the non-compatible mode which only : > has files for the devices you actually have, and creates the files : > on demand. : : What's the point with having device nodes for devices you don't have? So open return -1 with errno set to ENXIO rater than ENOENT. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200111061700.fA6H0V724455>