| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 4 Apr 2007 11:22:34 -0500 From: linas@...tin.ibm.com (Linas Vepstas) To: Brad Boyer <flar@...andria.com> Cc: David Woodhouse <dwmw2@...radead.org>, linuxppc-dev@...abs.org, Paul Mackerras <paulus@...ba.org>, linux-kernel@...r.kernel.org Subject: Re: [PATCH] Stop pmac_zilog from abusing 8250's device numbers. On Tue, Apr 03, 2007 at 04:09:08PM -0700, Brad Boyer wrote: > The issue is that the naming should be consistent. I > shouldn't need to know what the hardware is to use what is fundamentally > an abstraction of "serial port" as far as the user is concerned. On > Solaris, I can say "/dev/term/a" and know that I will get the first > serial port if it is available without needing to care if it is the > zs, se or asy driver talking to the hardware. I presume that a correctly structured set of rules for udev should accomplish the same thing; when udev runs, it could create links to /dev/serial0 or /dev/serial/0 etc. as you wish. Applications "should" use the udev-created links, not the raw, underlying device nodes. The biggest problem would seem to be that the assignment would depend on the detection order; there don't seem to be unique id's that would help udev consistently assign device names in consistent order. --linas - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists