public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Buhr <buhr@telus.net>
To: "Calin A. Culianu" <calin@ajvar.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Lazy Newbie Question
Date: 21 May 2002 13:58:32 -0700	[thread overview]
Message-ID: <87y9edfcav.fsf@saurus.asaurus.invalid> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0205211556040.16426-100000@rtlab.med.cornell.edu>

"Calin A. Culianu" <calin@ajvar.org> writes:
> 
> Get comedi-cvs.

Thanks.

> > > 'nuff said.
> >
> > On the contrary...
> 
> Yeah whatever.

Well, as you can see from the implementation of "comedi_open" that's
right in front of you, that code doesn't do anything with the filename
except parse it as string of the form "/dev/comediNNN" to get the
minor number "NNN".  It looks like a cheesy hack to fake the
kernel-mode interface to look like the user-mode interface, but that's
all it is.  So, as Richard said, we still haven't seen any evidence
that Comedi requires manipulating files in kernel space.

It's quite strange how rude and evasive you're being when everyone
who's replied has been polite and helpful.  Perhaps if you lost the
attitude and told us what it is you're really trying to do, we could
help you more effectively.

I mean, either we're all too dim to understand your device driver
hacking skills, in which case there's no point in you wasting your
time here, or one of us has enough of a clue to help, in which case
we'd all benefit from you explaining your problem as fully as you are
able instead of demanding we show you how to do the impossible (i.e.,
stat a file without a process context).

By the way, in case you missed it---and it seems you did---Richard
already gave you the right answer in the message you mistakenly
dismissed as a flame.  If you really need to stat a file from the
kernel, you do this with a helper process in the form of a bona fide
user process or a kernel thread.  Because this is relatively
complicated to get right (there's a damn good reason the code in
"comedi_open" just fakes it), you don't want to do this unless you
have to.

-- 
Kevin Buhr <buhr@telus.net>

  reply	other threads:[~2002-05-21 20:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.lnev59v.el8i1c@ifi.uio.no>
     [not found] ` <fa.kh0cciv.i5g73p@ifi.uio.no>
2002-05-21 18:32   ` Lazy Newbie Question Kevin Buhr
2002-05-21 19:56     ` Calin A. Culianu
2002-05-21 20:58       ` Kevin Buhr [this message]
2002-05-21 23:20         ` Calin A. Culianu
2002-05-21 23:42           ` Calin A. Culianu
2002-05-22  7:03           ` Zwane Mwaikambo
2002-05-21 15:36 Calin A. Culianu
2002-05-21 15:53 ` Richard B. Johnson
2002-05-21 16:07   ` Calin A. Culianu
2002-05-21 16:30     ` Eli Carter
2002-05-21 16:52     ` Richard B. Johnson
2002-05-21 17:38       ` Calin A. Culianu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y9edfcav.fsf@saurus.asaurus.invalid \
    --to=buhr@telus.net \
    --cc=calin@ajvar.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox