My dmesg is flooded with error messages.

[patrikg]

I think it's easy fix. Just don't know where the mount -o loop command is.
I presume it in some of the files in /etc/init.d
I think it's the mount command tries first to mount the tcz files in F2FS filesystem.

Maybe it's a new function in busybox.. what i can see...it says...
Filesystem autodetection requires /proc...
Don't know how it's detection is made through proc.

I presume this could also be like default for not just picore, for even the others tiny core.

Like this:
sudo mount -t squashfs -o loop tczfile.tcz mountpoint

8 lines of this error messages by tcz file.

Code: (bash) [Select]

[ 2373.739716] F2FS-fs (loop18): Magic Mismatch, valid(0xf2f52010) - read(0x39ccf62b)
[ 2373.739731] F2FS-fs (loop18): Can't find valid F2FS filesystem in 1th superblock
[ 2373.739747] F2FS-fs (loop18): Magic Mismatch, valid(0xf2f52010) - read(0x1e353db1)
[ 2373.739762] F2FS-fs (loop18): Can't find valid F2FS filesystem in 2th superblock


[patrikg]

file /usr/bin/tce-bootload

I made it my self.. find it...at line 86...

Code: (python) [Select]

        fp.close()
        os.mkdir(root + '/tmp/tcloop/' + p[:-4])
        os.system('sudo mount -t squashfs -o loop ' + sys.argv[1] + '/optional/'
    except OSError:
        print("\nNot available 1:", p)
        continue

The dmesg is now in order...

[Zlika]

Thank you for the fix. I hope it will be integrated in the next release.

[patrikg]

When I investigated a little more this case, i found that my sentence in my
first post, is not relevant, because the -t squashfs is there. 

- I presume this could also be like default for not just picore, for even the others tiny core.


It seams that the picore uses micropython to do things such as mounting the tcz at boot.
Haven't seen that before, my bad.

[Misalf]

Still, you found the cause for  dmesg's  output getting spammed.

[bmarkus]

@patrikg

Thanks, it is fixed in 8.1.6

Recently mount from util-linux was replaced with a BusyBox applet and while util-linux works fine without -t BusyBox need it to get rid of this message even if it can mount properly.

[patrikg]

Good that i found the thing..my self....learning a lot how to search in linux systems by doing this.
Just found -prune in find...maybe i will make a alias of this...
Exaple: find / -path /proc -prune -or -iname *findme*
or do it little crazy with for this:
grep loop $(file * | grep ASCII|cut -f1 -d':')

So if i understand you correctly this micropython thing is just a workaround for buggy busybox util-linux ?

[bmarkus]

So if i understand you correctly this micropython thing is just a workaround for buggy busybox util-linux ?

No, it is to speed up boot.

[patrikg]

Now i find the explanation of the problem with busybox mount command.
It just tries all fs'es in /proc/filesystems.

Sorry for the stackoverflow link, but i describes it very well with link to busybox mount source code

http://stackoverflow.com/a/11398511

[richarde]

Thanks, it is fixed in 8.1.6

Are there plans for an 8.1.6 release?  (The most recent I see on the releases page is 8.1.5).

Or is the current recommendation to follow the remastering instructions on the wiki to
- unpack
- modify /usr/bin/tce-bootload
- repack
?

Thanks,
Richard

[bmarkus]

Thanks, it is fixed in 8.1.6

Are there plans for an 8.1.6 release?  (The most recent I see on the releases page is 8.1.5).

Or is the current recommendation to follow the remastering instructions on the wiki to
- unpack
- modify /usr/bin/tce-bootload
- repack
?

Thanks,
Richard

No 8.1.6 -> see 9.0