Well, just to let you know and for others who also encountered this behaviour, I think I got it to work now.
Reading the messages that fly over the screen while booting (after buying myself a magnifier!), I stumbled across a message that read "invalid mount option: user" or the like.
So, I changed "/etc/fstab" to the following:
/dev/mtdblock4 / jffs2 defaults 1 1
proc /proc proc defaults 0 0
#/dev/hda1 /mnt/cf auto defaults,sync,noatime,user,exec,suid,gid=100,umask=0002 0 0
/dev/mmcda1 /mnt/card auto defaults,sync,noauto,noatime,user,exec,suid 0 0
tmpfs /var tmpfs defaults 0 0
# we use a non-volatile ramdisk, see /etc/init.d/ramdisk
#tmpfs /mnt/ram tmpfs defaults 0 0
/dev/hda1 /mnt/cf auto defaults 0 0
/dev/hda1 auto defaults 0 0
Original line 3 got commented out (/dev/hda1 /mnt/cf auto defaults,sync,...). One of the options given at the end of this line caused the card to not get mounted. Dunno which one it was yet. After that I changed the last line of the old fstab (see above) to "/dev/hda1 /mnt/cf auto defaults 0 0". Now, after rebooting or after re-inserting the cf card it automounts!
What I don't understand is why "/dev/hda1 auto defaults 0 0" is always appended to "/etc/fstab" after rebooting if it is not existing in the file. Again, it shows up in my fstab (last line above), but doesn't seem to cause any trouble.
Is this a bug? My problem only? Any one else experienced this?
Peace,
Frank
