[Galaxy S I9000 Android Development] androidsfan:
I wondered from where I could get the needed files.

Please, bear with me if I need still some thinking ;) Is it really a syntax error? Wildcards seem to be allowed and there is indeed a blockdevice /sys/devices/platform/s3c-sdhci.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0. As I understand it, the page you refer to just shows examples. Also, the correct partition is mounted (that is the first partition on mmcblk0) -- only in the wrong way. I also took a look at the kernel messages and the partition seems to be correctly identified:

[ 67.160974] SELinux: initialized (dev mmcblk0p1, type vfat), uses genfs_contexts
[ 67.397601] type=1400 audit(1473015066.238:25): avc: denied { module_request } for pid=1922 comm="sh" kmod="personality-8" scontext=u:r:blkid_untrusted:s0 tcontext=u:r:kernel:s0 tclass=system permissive=1
[ 68.536369] binder: 1729:1802 refcount change on invalid ref 7
[ 68.536531] binder: 1729:1802 refcount change on invalid ref 7
[ 68.536681] binder: transaction release 10719 bad handle 7
[ 69.687810] SELinux: initialized (dev mmcblk1p1, type vfat), uses genfs_contexts
[ 69.755190] type=1400 audit(1473015068.753:26): avc: denied { module_request } for pid=2016 comm="sdcard" kmod="personality-8" scontext=u:r:sdcardd:s0 tcontext=u:r:kernel:s0 tclass=system permissive=1
[ 69.934767] SELinux: initialized (dev fuse, type fuse), uses genfs_contexts
[ 69.936523] SELinux: initialized (dev fuse, type fuse), uses genfs_contexts
[ 69.939320] SELinux: initialized (dev fuse, type fuse), uses genfs_contexts

I was wondering whether the "noemulatedsd" key could be a problem. From the android 5.x definitions, which probably didn't change:

After looking more closely at my configuration and the documentation you pointed to I now believe the situation is like this:

As "setprop ro.vold.primary_physical 1" is commented out in init.aries.rc, primary storage (/sdcard) is emulated on top of internal storage.

As there is the line you quoted in fstab.aries the first partition of mmcblk0 (my old internal sdcard) is mounted as nonremovable sdcard. And maybe, as there is the "noemulatedsd" key it is not further managed by fuse.

As there is the following line in fstab.aries my external sdcard is mounted as such. And perhaps, as there is no "noemulatedsd" key it is not further managed by fuse.

One possibility would be to leave out the first line. This might result in my old internal sdcard again be adopted as such. (This would be either the first or second of my desired solutions.) But maybe not: It is formated as vfat, and I vaguely remember to have read something about a vfat partition no longer be usable as internal sdcard. (But I might be wrong.) Another possibility would be to just leave out the "noemulatedsd" key. Maybe this results in this partition being offered by fuse like the external card. This would go into the direction of the third solution. If this was a normal linux machine I would just try it out as I know I could access the file again booting from somewhere else. But I'm afraid that's not the way with an android smartphone :(

To use a build is better than to just change a configuration file like fstab.aries? Thanks again!