| 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: Sun, 20 Nov 2011 12:19:15 -0800 From: Randy Dunlap <rdunlap@...otime.net> To: Bernd Petrovitsch <bernd@...rovitsch.priv.at> CC: jidanni@...anni.org, linux-kernel@...r.kernel.org Subject: Re: Documentation/input/input.txt.gz has a bug On 11/16/2011 04:50 AM, Bernd Petrovitsch wrote: > On Die, 2011-11-15 at 11:35 -0800, Randy Dunlap wrote: > [...] >> Doing a "cat /dev/input/mouse0" (char device 13,32) will verify that >> a mouse is also emulated; characters should appear if you move it. >> Doing a >> $ cat /dev/input/mouse > > Hmm, how is this written in the other documentation? There is very little consistency among all of the Documentation/ files (hopefully there is some consistency within any one file). I found many of: a. using a prompt, e.g.: $ cat /dev/input/mouse b. using backquotes: `cat /dev/input/mouse` c. using double quotes: "cat /dev/input/mouse" d. using a colon: type (or enter): cat /dev/input/mouse > Both are fine with me. FWIW in emails and the like, I use backquotes > usually as in > ---- snip ---- > Doing a `cat /dev/input/mouse0` (char device 13,32) will verify that > a mouse is also emulated; characters should appear if you move it. > ---- snip ---- Yes, that's OK also. -- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** -- 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