Re: Strange behaviour of files in /proc Explanation??
On Friday 28 January 2011 05:02:14 Dr. Ed Morbius wrote:
> on 00:56 Fri 28 Jan, Lisi (firstname.lastname@example.org) wrote:
> > On Thursday 27 January 2011 19:41:06 Dr. Ed Morbius wrote:
> > > on 17:43 Thu 27 Jan, Lisi (email@example.com) wrote:
> > > > On my main desktop running Lenny and KDE 3.5.10, I can open files in
> > > > /proc with cat, vi or OOo. I can open them neither with KWord nor
> > > > with KWrite, neither of which can even see them.
> > > >
> > > > Can anyone explain this??
> > >
> > > These are virtual files which are actually interfaces to kernel state,
> > > and while some text-based tools can work with them (generally by
> > > copying the contents to another buffer: cat, more/less/most, even vim),
> > > word-processign tools
> > I ran none of the applications that I mentioned as root. The files
> > that did open, did so read only. Moreover 3 of the 5 above are text
> > editors, not word processors.
> > > may have other issu
> > > es and really aren't the
> > > appropriate tool for working with /proc & /sys files. Or for use under
> > > root, which is required for most /proc & /sys files.
> > Who said anything about ...
> Nobody said anything about *not* operating in certain modes. I wasn't
> assuming one way or the other. I *was* providing information which
> might prove useful and/or helpful.
It was neither. It was dictatorial, arrogant and condescending. Apart from
the bit about virtual files, which was helpful..
> I'm not particularly interested in arguing an intent which you alone are
> privy to, or any number of other pissing matches.
So why go to so much trouble to instruct me - fairly unpleasantly - not to do
something that I wasn't doing?