linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrik Wallstrom <pawal@blipp.com>
To: Larry McVoy <lm@bitmover.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: double entries in /proc/dri?
Date: Wed, 13 Jun 2001 07:03:59 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.33.0106130659070.18749-100000@vic20.blipp.com> (raw)
In-Reply-To: <20010612185603.A2031@work.bitmover.com>

On Tue, 12 Jun 2001, Larry McVoy wrote:

> This is cute:
>
> $ ls -li /proc
> ...
>    4106 -r--r--r--    1 root     root            0 Jun 12 18:53 dma
>    4347 dr-xr-xr-x    3 root     root            0 Jun 12 18:53 dri
>    4347 dr-xr-xr-x    3 root     root            0 Jun 12 18:53 dri
>    4121 dr-xr-xr-x    2 root     root            0 Jun 12 18:53 driver
> ...
>
> $ uname -a
> Linux work.bitmover.com 2.4.5 #1 Mon May 28 10:54:32 PDT 2001 i686 unknown
>
> Repeatable.  If other users of 2.4.5 do NOT see this, please let me know.

Linux pawalski.blipp.com 2.4.5-0.2.9 #1 Wed May 30 06:50:52 EDT 2001 i686 unknown

This is the Red Hat kernel from rawhide.

-r--r--r--    1 root     root            0 Jun 13 06:59 dma
dr-xr-xr-x    2 root     root            0 Jun 13 06:59 driver
-r--r--r--    1 root     root            0 Jun 13 06:59 execdomains

However, I saw this on a self compiled 2.4.4 with Cisco 350 PC-Card
installed using pcmcia-cs and the Cisco airo_cs.o module up and running.

--
 patrik wallstrom     |      f o o d f i g h t
 tel: +46-8-6188428   |      s t o c k h o l m
 gsm: +46-708405080   |      - - - - - - - - -



  parent reply	other threads:[~2001-06-13  5:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-13  1:56 double entries in /proc/dri? Larry McVoy
2001-06-13  2:10 ` Robert Love
2001-06-13  5:03 ` Patrik Wallstrom [this message]
2001-06-14 18:00   ` Alan Cox

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=Pine.LNX.4.33.0106130659070.18749-100000@vic20.blipp.com \
    --to=pawal@blipp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.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).