public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam <ambx1@netscape.net>
To: root@chaos.analogic.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: driverfs question
Date: Thu, 21 Feb 2002 16:56:22 -0500	[thread overview]
Message-ID: <3C756D06.7090901@netscape.net> (raw)
In-Reply-To: <Pine.LNX.3.95.1020221161906.254A-100000@chaos.analogic.com>



root@chaos.analogic.com wrote:

> On Thu, 21 Feb 2002, Adam wrote:
> 
>>All devices will be arranged according to type.  There will be a folder 
>>
>                                                                    ^^^^^
> 
>>Method 2:
>>Folders are created for each bus then devices are placed within them.
>>
>   ^^^^^^^
> 
> 
>>member of a pci bus, it's folder will be within the pci folder.  The 
>>
>                             ^^^^^^                        ^^^^^^
> 
> What is this? Do you mean "directory" or "file", or even "inode"?
> 
> Or is this a troll from Microsoft?  We don't have such things in
> real operating systems. Next thing you know, we'll need a "cabinet"
> to keep the "folders" in.
> 
> 
> Cheers,
> Dick Johnson
> 
> Penguin : Linux version 2.4.1 on an i686 machine (797.90 BogoMips).
> 
>         111,111,111 * 111,111,111 = 12,345,678,987,654,321
> 
> 


You're absolutely right.  What I meant to say is a directory.  It's 
simply a bad habit.  In fact, one, of several, reason I became 
interested in the Linux kernel project is that I was unhappy with the 
Micro$oft licensing policy.  The term folder is used by micro$oft simply 
to make it's OS sound more user friendly.


  reply	other threads:[~2002-02-21 21:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-21 20:37 driverfs question Adam
2002-02-21 20:48 ` Patrick Mochel
2002-02-21 21:25 ` Richard B. Johnson
2002-02-21 21:56   ` Adam [this message]
2002-02-21 21:59     ` Richard B. Johnson
2002-03-12 21:17     ` H. Peter Anvin
2002-02-21 21:53 ` Greg KH

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=3C756D06.7090901@netscape.net \
    --to=ambx1@netscape.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.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