From: Don Bailey <don.bailey@gmail.com>
To: Dworkin Muller <dworkin@weaselfish.com>
Cc: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Definitinon list of the # filesystems
Date: Fri, 22 Jan 2021 00:44:05 -0700 [thread overview]
Message-ID: <CAL_X0tAuGhuE5xQqSYPzNTUfS33WqP4U8mhRV+Tmv02Cp+drfA@mail.gmail.com> (raw)
In-Reply-To: <20210122.002319.1458799558913362257.dworkin@weaselfish.com>
[-- Attachment #1: Type: text/plain, Size: 954 bytes --]
Grep the kernel tree for 'devtab'. Each device has a character and its name
listed in the devtab definition. Pretty easy.
D
On Fri, Jan 22, 2021 at 12:23 AM Dworkin Muller <dworkin@weaselfish.com>
wrote:
> On Fri, 22 Jan 2021 00:12:27 -0700, Don Bailey <don.bailey@gmail.com>
> wrote:
> don.bailey> Trust the process. Grep the src. Also don't trust /dev/drivers
> because it
> don.bailey> only includes compiled in things, not things that are
> available in the
> don.bailey> tree.
>
> Like I said, that's literally 109,636 hits (in /sys/src on a
> freshly-installed 9front system). I'll start with Ori's suggestion of
> /dev/drivers and expand from there if/as needed.
>
> Thanks.
>
> Dworkin
>
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tc21478a4dc8e2df1-Mfe0c556a7ddea53d6be0022a
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 1834 bytes --]
next prev parent reply other threads:[~2021-01-22 7:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 6:47 dlm-9fans
2021-01-22 6:51 ` Don Bailey
2021-01-22 7:10 ` Dworkin Muller
2021-01-22 7:12 ` Don Bailey
[not found] ` <20210122.002319.1458799558913362257.dworkin@weaselfish.com>
2021-01-22 7:44 ` Don Bailey [this message]
2021-01-22 8:47 ` Bakul Shah
2021-01-22 7:09 ` ori
2021-01-22 10:31 ` Richard Miller
2021-01-22 10:43 ` Richard Miller
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=CAL_X0tAuGhuE5xQqSYPzNTUfS33WqP4U8mhRV+Tmv02Cp+drfA@mail.gmail.com \
--to=don.bailey@gmail.com \
--cc=9fans@9fans.net \
--cc=dworkin@weaselfish.com \
/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;
as well as URLs for NNTP newsgroup(s).