| 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
| ||
|
Message-ID: <48D164B9.7020507@redhat.com> Date: Wed, 17 Sep 2008 16:12:41 -0400 From: Chris Snook <csnook@...hat.com> To: Singaravelan Nallasellan <singaravelann@...il.com> CC: linux-kernel@...r.kernel.org Subject: Re: New IOCTLs Singaravelan Nallasellan wrote: > I need to send device control messages to the driver. I am planning to > use the IOCTLs. But I came to know that Linux community does not > accept any new IOCTLs anymore. > Can somebody provide the reason behind the decision? Are there any > better approach to implement the device control interface other than > sysfs interface. I have some issues in using the sysfs interface. > Thanks in advance. IOCTLs are discouraged, but not strictly forbidden. Is there something about sysfs that would make it an unsuitable interface, or are you just having trouble finding good documentation on using it? -- Chris -- 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