Hi Gordan. It just "tickles my OCD" that i have to set uboot boot and root args different for every arm device. Could we not agree on a 256 mb boot partition 1 and OS size specific root partition 2 for a Redsleeve SD card? I am open for a discussion about file systems. Thats a minor kernel/uboot compilation issue to me.
BR, Bjarne _____________________________ From: Gordan Bobic <[email protected]<mailto:[email protected]>> Sent: lørdag, juli 23, 2016 11:50 AM Subject: Re: [RedSleeve-Users] CuBox-i 4x4 updated rsel 6 image To: <[email protected]<mailto:[email protected]>> > Question: do we have any guidelines about disk partition layout? The > previous CuBox imaged just had one big ext4 partition. I am used to > always having the /boot as a FAT partition for easier kernel > manipulation when I screw up a kernel compilation and makes a invalid > boot image. Whether /boot is FAT or something else comes down to what the device's u-boot can handle. There are still a LOT of devices out there that use custom patched u-boot without sources and without support in upstream u-boot, and their ancient version of u-boot only supports FAT. As a general rule, I use the best FS the device's u-boot can handle, usually ext4, sometimes ext2, and in the worst case FAT16. If CuBox supports ext, I'd say use ext on that image. Another thing to consider is whether there is any point in having a separate /boot if u-boot supports ext4, and the root partition is ext4 anyway. Personally, I use the appropriate /boot partition and have root on ZFS for root and everything else, if I am booting from u-boot. Gordan _______________________________________________ users mailing list [email protected]<mailto:[email protected]> https://lists.redsleeve.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] https://lists.redsleeve.org/mailman/listinfo/users
