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: Tue, 16 Nov 2010 06:59:33 -0500 From: Richard Williams <richard@...chsoft.com> To: Bart Van Assche <bvanassche@....org> CC: Boaz Harrosh <bharrosh@...asas.com>, FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>, Mike Christie <michaelc@...wisc.edu>, Vladislav Bolkhovitin <vst@...b.net>, "linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>, Greg KH <greg@...ah.com>, Dmitry Torokhov <dmitry.torokhov@...il.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, James Bottomley <James.Bottomley@...senpartnership.com>, scst-devel <scst-devel@...ts.sourceforge.net>, Hannes Reinecke <hare@...e.de>, Andy Yan <ayan@...vell.com>, Andrew Morton <akpm@...ux-foundation.org>, Vu Pham <vuhuong@...lanox.com> Subject: Re: [Scst-devel] [PATCH 8/19]: SCST SYSFS interface implementation I'm just an outsider - but maybe my perspective has value - it seems there are two sides to this debate: 1) sysfs is great for scst due to certain stability concerns and code concerns 2) sysfs is bad for scst due to the intended role of sysfs and its namespace Maybe I misunderstand - But if both sides have merit then wouldn't a compromise be appropriate? Maybe the sensical compromise is to use sysfs code to create a new namespace that would fit this purpose? It seems that I am also hearing that the alternatives to sysfs aren't always adequate - so why not use sysfs, but have a place where it's appropriate to use it? Apologies in advance if I'm just way off base here... - Richard Williams-- 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