From: Petr Grillinger Subject: Re: procfs proc_write_file bug Date: Fri, 19 Nov 2004 17:48:14 +0100 Message-ID: <419E23CE.2040109@kiv.zcu.cz> References: <419DFF37.5040401@kiv.zcu.cz> <20041119162612.GA19004@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org Return-path: Received: from venus.vmars.tuwien.ac.at ([128.130.39.30]:31239 "EHLO venus.vmars.tuwien.ac.at") by vger.kernel.org with ESMTP id S261490AbUKSQsc (ORCPT ); Fri, 19 Nov 2004 11:48:32 -0500 To: Greg KH In-Reply-To: <20041119162612.GA19004@kroah.com> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Sorry about the tabs, I forgot to change my editor settings. I use procfs to export information about my module - in text form. I also use it to export the binary image of some configuration data (about 16KB). To be able to configure the module by writing into /procfs (binary/text) would be nice, because then the interface is all in one place. But still thanks for the idea, it didn't occur to me that I could solve it by creating my own FS. Maybe next time :-) Petr Grillinger Greg KH wrote: > On Fri, Nov 19, 2004 at 03:12:07PM +0100, Petr Grillinger wrote: > >>I needed recently to write a large file into the /proc FS, > > > Why do you need to do this? Wouldn't it be simpler to create your own > fs if you want to accept large ammounts of data? /proc isn't meant for > something like this. > > Oh, and you forgot to use tabs in your code :) > > thanks, > > greg k-h > - > To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >