I am not so sure that having that having the line there doesn't break things.

With the line there then when I power up without any cards in, mount will
still show a mmcblk device mounted on mmc1.

If I start up maemo-mapper in this mode, it seems to die. (Seems to die
because although its windows never comes up, the process is still there if
you do a 'ps'.) I think that this is because I have configured mapper to
store its map cache under the /media/mmc1 directory.

If I start mapper without any cards installed *and* with the mmc line in fstab
removed, then mapper complains about not being able to create the cache
file (becuase it can't get the the "/media/mmc1/Maps" directory), but still
succeeds in bring up its window - and can be terminated.

Once I get into this mode where mapper is hung, I cannot shut the box
down. I have to pop the battery out to reset it. (Fortunately, this doesn't
seem to cause any problems. Perhaps I've just been luck in this part.)

Although the screen eventually shuts off, the box is still running and I can
ssh into it.

A 'ps' shows that the mini-shutdown routine is (supposedly) running, but
nothing much is happening. Trying to reboot/shutdown from the ssh
session also does nothing.

(I also cannot 'kill -9' the mapper process.)

To me It has the feel that the system is trying to unmount the filesystems as
part of the shutdown process. But, it might be getting stuck on the mmcblk
device that really isn't there (but that the mapper application might be trying
to use). And, it is patiently waiting - forever - for that "device" to unmount.

But I may be wrong.

In any case, things "seem" to work a bit more nicely without that line there.

I say "seems" becuase I'm still having problems with mounting cards. (I'll
continue this in the other thread I started on potential hardware problems.)

Ed