From mboxrd@z Thu Jan  1 00:00:00 1970
From: greg@kroah.com (Greg KH)
Date: Wed, 22 Feb 2012 06:53:09 -0800
Subject: Iterating through all the processes in a module
In-Reply-To: <CAPNxggbWfMioMGPokZ4qK0rtFThDJuJPaeA_LCH_tkUuz8OA3A@mail.gmail.com>
References: <CAPNxggakgukeLsAQbaESN0LC5EUxzks1USy0hKH1JbkuFq5i1Q@mail.gmail.com>
	<20120207191702.GA9172@kroah.com>
	<CAPNxggbWfMioMGPokZ4qK0rtFThDJuJPaeA_LCH_tkUuz8OA3A@mail.gmail.com>
Message-ID: <20120222145309.GA25682@kroah.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org


A: No.
Q: Should I include quotations after my reply?

http://daringfireball.net/2007/07/on_top

On Wed, Feb 22, 2012 at 02:07:22PM +0100, Arokux B. wrote:
> Dear Greg,
> 
> thank you very much for your quick reply.
> 
> Having my code as a module I can trigger its execution (load a module)
> and disable it (unload a module). How can I achieve this if the code
> is inside the kernel? One possibility I see is adding an entry in the
> procfs.

I don't see what procfs has to do with this, please explain.

And as you said this was for "learning purposes", then just build it
into the kernel, there's no need for it to be a module.

good luck,

greg k-h