Storage expansion drives in Aspire One

[roberts]

The issue you are now facing is not really a mnttool concern but fstab instead.
mnttool uses fstab for mount options.

fstab does not "see" your mmc device as vfat and therefore uses "auto" as the fstype and hence no umask=000

What does fdisk -l show for your mmc device?

[^thehatsrule^]

Those dirs are probably not created if the modules weren't loaded yet.

afaik mtab shows mounted stuff, so there's no use looking in there.

You could test it out first after replacing the line in fstab, i.e. with `mount /mnt/mmcblk0p1 `

[Onyarian]

After boot and mmc.tce loaded during boot, and with /mnt/mmcblk0p1 created, the fdisk -l don't detect mmc drive:

tc@box:~$ fdisk -l

Disk /dev/hdc: 8069 MB, 8069677056 bytes
255 heads, 63 sectors/track, 981 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/hdc1   *           1         850     6827593+ 83 Linux
/dev/hdc2             851         981     1052257+ 82 Linux swap

Disk /dev/sda: 1048 MB, 1048576000 bytes
255 heads, 63 sectors/track, 127 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1   *           1         127     1020096   b Win95 FAT32

But now seems to work when I substitute in fstab

/dev/mmcblk0p1  /mnt/mmcblk0p1  auto     noauto,users,exec,umask=000    0 0 # Added by TC

with

/dev/mmcblk0p1  /mnt/mmcblk0p1  vfat     noauto,users,exec,umask=000    0 0 # Added by TC

Thanks to both!