Re: proc file system

[Jan Hudec]

> Well, to get tail -f to work, minimally you'll have to support
> maintaining a fileposition, so tell() and seek() have something useful
> to work on.  It's been a while since I looked at the source for tail,
> pretty much for similar reasons (wanted to follow a /proc file).  Most
> /proc files are considered (relatively) fixed-length files, who's
> contents get updated.  tail -f expects to follow a file that is
> growing in size.

... thus it won't work on char dev at all;-) (but simple cat will do
lot better). Well, it does not matter what proc files are supposed to
be, they can behave any way you want. They can even behave like devices.
(And it even shouldn't be more work)

AFAIK the only differences remaining are that devices can initialize module
autoloading and that you can put device node anywhere.

> I don't have sources in front of me, so hopefully someone else will
> step-up and provide more detail than I have.
> 
> Steve Brueggeman
> 
> 
> On Tue, 9 Oct 2001 15:41:34 +0200, you wrote:
> 
> >> On Sat, Oct 06, 2001 at 12:02:18AM +0200, [e-mail] wrote:
> >> > i've written a prog interface for my logger utility to make it easy
> >> > to transport my logging information from kernel to userspace using
> >> > shell commands. now i want to use tail -f /prog/<mylogfile>. what
> >> > do i have to do for that to work. when using tail my loginfo gets
> >> > read form my ringbuffer, but nothing gets printed in the terminal.
> >> 
> >> I think you actually want a character device instead of a /proc file.
> >
> >Could you please explain why? I can't see the advantage (read and write
> >are fileops; you can have them exactly the same for proc file and device).
> >
--------------------------------------------------------------------------------
                  				- Jan Hudec `Bulb' <[e-mail]>