On Sat, 2017-06-10 at 02:41 +0200, Heinrich Schuchardt wrote: > On 06/10/2017 02:11 AM, Ben Hutchings wrote: > > On Sat, 2017-06-10 at 00:59 +0200, Heinrich Schuchardt wrote: > >> On 06/10/2017 12:31 AM, Martin Michlmayr wrote: > >>>>> * Heinrich Schuchardt <xypron.g...@gmx.de> [2017-06-09 23:18]: > >>>> flash-kernel currently fails if the boot partition is FAT32. > >>>> > >>>> On FAT32 symbolic links cannot be created. > >>> > >>> Unless something has changed, FAT for /boot isn't supported > anyway. > >>> > >>> See https://lists.debian.org/debian-boot/2014/01/msg00188.html > >>> > >> > >> That information seems to be outdated. > > [...] > > > > I think you didn't follow the thread far enough: > > https://lists.debian.org/debian-boot/2014/01/msg00195.html > > > > Ben. > > > > So this further complication stems from function tarobject() in > package > dpgk?
FAT* are simply not POSIX compatible filesystems and as such are not supported as /boot (or /, /var, or /usr etc for that matter), irrespective of how it might appear to you to be working under some circumstances. If your device's firmware requires a FAT partition to boot from then you should configure flash-kernel in the mode where it mounts that partition temporarily to copy the boot files to it while /boot remains a POSIX filesystem (ext4 etc). Ian.
