<br><br><div><span class="gmail_quote">On 8/29/07, <b class="gmail_sendername">Marius Vollmer</b> <<a href="mailto:marius.vollmer@nokia.com">marius.vollmer@nokia.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>The internal card is always mounted on /media/mmc2, and the external<br>card is always mounted on /media/mmc1.</blockquote><div><br>And when the Nokia n900 (just guessing) gets released, and it has a memory stick socket or some other type of memory card, I assume we won't be able to rely on this anymore. But, sounds like for at least the short term (or long term in Internet years) relying on mount and /media/mmc* is the way to go. Assuming you don't need notifications of card insert.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">You can also use the environment variables MMC_MOUNTPOINT and<br>INTERNAL_MMC_MOUNTPOINT, but then you have to make sure that they are
<br>always set correctly in your environment. (I don't think using<br>environment variables for this kind of system information is a good<br>idea.)</blockquote><div><br>Agreed. Especially with the numbers of morons like me that are likely to screw those up ;-)
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">The device files are not constant like this: the internal card might<br>be /dev/mmcblk0 or /dev/mmcblk1, as far as I understand. Someone with
<br>better low-level knowledge please correct me.</blockquote></div><br>I had thought this might be the case, especially since my /dev/mmcblk0 goes to /media/mmc2 and /dev/mmcblk1 goes to /media/mmc1 on my device. Seemed kind of reversed to me.
<br>