public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@transmeta.com>
To: Rogier Wolff <R.E.Wolff@BitWizard.nl>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: Sony Memory stick format funnies...
Date: Sun, 29 Apr 2001 13:09:22 -0700	[thread overview]
Message-ID: <3AEC74F2.7B219E4E@transmeta.com> (raw)
In-Reply-To: <200104292003.WAA25179@cave.bitwizard.nl>

Rogier Wolff wrote:
> 
> H. Peter Anvin wrote:
> > Followup to:  <200104282236.AAA06021@cave.bitwizard.nl>
> > By author:    R.E.Wolff@BitWizard.nl (Rogier Wolff)
> > In newsgroup: linux.dev.kernel
> > >
> > > # l /mnt/d1
> > > total 16
> > > drwxr-xr-x 512 root     root        16384 Mar 24 17:26 dcim/
> > > -r-xr-xr-x   1 root     root            0 May 23  2000 memstick.ind*
> > > #
> > >
> > > Where the *(&#$%& does that "dcim" directory come from????
> > >
> >
> > "dcim" probably stands for "digital camera images".  At least Canon
> > digital cameras always put their data in a directory named dcim.
> 
> Yes. I know. Seems to be standard. The stick is for my Sony camera.
> 
> However, the question is: how in **** is the Linux kernel seeing that
> directory while it's not on the stick? (the root directory has one
> MEMSTICK.IND file, and nothing else!)
> 

I doubt the kernel is seeing it without it being there (it doesn't have
much imagination.)  However, it may very well be there in a funny
manner.  You do realize, of course, that it's pretty much impossible for
us to help you answer that question without a complete dump of the
filesystem on hand, I hope?

	-hpa

-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt

  reply	other threads:[~2001-04-29 20:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-28 22:36 Sony Memory stick format funnies Rogier Wolff
2001-04-28 23:06 ` mirabilos
2001-04-29  0:03 ` H. Peter Anvin
2001-04-29  3:11   ` Michael Rothwell
2001-04-29  2:18     ` H. Peter Anvin
2001-04-29 20:03   ` Rogier Wolff
2001-04-29 20:09     ` H. Peter Anvin [this message]
2001-04-29 20:15       ` Gregory Maxwell
2001-04-29 20:17         ` H. Peter Anvin
2001-04-29 20:27           ` Rogier Wolff
2001-04-29 20:33             ` H. Peter Anvin
2001-04-29 20:45               ` Rogier Wolff
2001-04-30  4:24                 ` Matthew Dharm
2001-04-29 20:37             ` mirabilos
2001-04-29 20:39               ` Rogier Wolff
2001-04-29 20:23         ` Rogier Wolff
2001-04-29 20:18       ` Rogier Wolff
2001-04-29 20:23         ` H. Peter Anvin
  -- strict thread matches above, loose matches on Subject: below --
2001-04-30  6:31 Antwerpen, Oliver

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=3AEC74F2.7B219E4E@transmeta.com \
    --to=hpa@transmeta.com \
    --cc=R.E.Wolff@BitWizard.nl \
    --cc=hpa@zytor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox