| 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: <50030.21278.qm@web31808.mail.mud.yahoo.com> Date: Mon, 4 Feb 2008 16:32:18 -0800 (PST) From: Luben Tuikov <ltuikov@...oo.com> To: linux-scsi <linux-scsi@...r.kernel.org>, James Bottomley <James.Bottomley@...senPartnership.com> Cc: linux-kernel <linux-kernel@...r.kernel.org>, linux-ide <linux-ide@...r.kernel.org>, "Accardi, Kristen C" <kristen.c.accardi@...el.com> Subject: Re: [PATCH] enclosure: add support for enclosure services --- On Sun, 2/3/08, James Bottomley <James.Bottomley@...senPartnership.com> wrote: > The enclosure misc device is really just a library providing > sysfs > support for physical enclosure devices and their > components. Who is the target audience/user of those facilities? a) The kernel itself needing to read/write SES pages? b) A user space application using sysfs to read/write SES pages? At the moment SES device management is done via an application (user-space) and a user-space library used by the application and /dev/sgX to send SCSI commands to the SES device. One could have a very good argument to not bloat the kernel with this but leave it to a user-space application and a library to do all this and communicate with the SES device via the kernel's /dev/sgX. Luben -- 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