From: John Covici <covici@ccs.covici.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] devfs v183 available
Date: 30 Jul 2001 02:59:55 -0400 [thread overview]
Message-ID: <m3lml652c4.fsf@ccs.covici.com> (raw)
In-Reply-To: <200107230502.f6N528g05023@vindaloo.ras.ucalgary.ca> <m3lml7yt4o.fsf@ccs.covici.com> <200107300353.f6U3ruc02345@mobilix.ras.ucalgary.ca>
In-Reply-To: <200107300353.f6U3ruc02345@mobilix.ras.ucalgary.ca>
OK, thanks much -- but how do I build the man pages -- I saw nothing
in the source which said anything about it.
Thanks again for your quick response.
Richard Gooch <rgooch@ras.ucalgary.ca> writes:
> John Covici writes:
> > I have two questions -- please forgive me if they are somewhat dumb.
> >
> > First, if I have the 2.4.7 source tree what patch level of devfs do I
> > have -- how is that related to the devfs 183 you announced?
>
> Check Documentation/filesystems/devfs/ChangeLog
>
> > Second, I need to change a driver which is now not devfs aware, but
> > hangs the kernel if devfs is not present -- where can I get
> > documentation for the devfs api?
>
> Build the man pages: the source code has markups so that documentation
> can be automatically extracted.
>
> Regards,
>
> Richard....
> Permanent: rgooch@atnf.csiro.au
> Current: rgooch@ras.ucalgary.ca
--
John Covici
covici@ccs.covici.com
next prev parent reply other threads:[~2001-07-30 7:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-23 5:02 [PATCH] devfs v183 available Richard Gooch
2001-07-30 3:48 ` John Covici
2001-07-30 3:53 ` Richard Gooch
2001-07-30 6:59 ` John Covici [this message]
2001-07-30 11:13 ` john slee
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=m3lml652c4.fsf@ccs.covici.com \
--to=covici@ccs.covici.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.