hardcoded mmcblk0

[civic9]

I am running armbian under BeeLink MXIII. It is S905, almost like Odroid C2. I know it is not supported by armbian, but I think there are many similar devices on the market and they are quite attractive - cheap, powerfull, with power supply and nice casing, etc. Good for small home servers.

Main problem for me to run armbian (using odroid c2 image) has been hardcoded mmcblk0 in a few places:

• /etc/fstab
• /etc/init.d/firstrun (resizing root fs) It was hard to diagnose it without serial nor hdmi display (which is enabled only after successfull root fs mount). mmcblk0 would be fine for running from emmc which gets mmcblk0 name, but I am running arbian from sdcard which is mmcblk1.

I think it can be easly "fixed" by using something else instead of direct device name, like filesystem label, e.g.LABEL=ROOTFS, LABEL=BOOT in /etc/fstab and e.g. "tunefs -L ROOTFS rootfspartitons" during image generation phase.

Probably there are some other places directly referencing mmcblk0.

[zador-blood-stained]

/etc/fstab

Newer (beta) images and next release images for C2 use UUID in fstab and boot script, so this should not be a problem

/etc/init.d/firstrun (resizing root fs)

This is a known issue (#467), it will be fixed eventually

I can also add that u-boot installation (postinst) script will need adjustment too