Alexander Viro writes:
> On Sun, 5 Nov 2000, Dave Zarzycki wrote:
>> On Sun, 5 Nov 2000, Alexander Viro wrote:
>>
>>> However, kernfs is _not_ procfs \setminus procfs-proper. It's our current
>>> /proc/sys.
>>
>> Okay. I didn't realize that's what you had in mind when you wrote
>> "kernfs." Mind i
On Sun, 5 Nov 2000, Dave Zarzycki wrote:
> On Sun, 5 Nov 2000, Alexander Viro wrote:
>
> > However, kernfs is _not_ procfs \setminus procfs-proper. It's our current
> > /proc/sys.
>
> Okay. I didn't realize that's what you had in mind when you wrote
> "kernfs." Mind if I ask why you didn't ca
On Sun, 5 Nov 2000, Alexander Viro wrote:
> However, kernfs is _not_ procfs \setminus procfs-proper. It's our current
> /proc/sys.
Okay. I didn't realize that's what you had in mind when you wrote
"kernfs." Mind if I ask why you didn't call it "sysctlfs" or "sysfs?"
In you earlier e-mail, you s
On Sun, 5 Nov 2000, Dave Zarzycki wrote:
> I got bored this evening and decided to learn more about the Linux kernel
> by splitting out procfs into two separate file systems:
>
> taskfs which contains /proc/self and /proc/[1-9]*
> kernfs which contains everything else that procfs provides.
>
4 matches
Mail list logo