On 21/07/16 20:22, Bjarne Saltbæk wrote:
Hi.
I have bought the very cute little powerful CuBox-i 4x4 and I have made
and update of the CuBox-i image from
ftp.redsleeve.org/pub/rootfs/cuboxi/rsel6-cuboxi-latest.img.xz
Updates:
* /boot - clean up of old boot images
* Updated the U-Boot to latest from SolidRun's git
(2013.10-rc4-g73d683b) - this is needed in order for the kernel to see
all the 4GB RAM the cute little box have
* Updated /etc/yum.repos.d/*.repo to point to valid repos
(.*packages.* changed to .*latest.*)
* Added ifcfg-eth0
- Missing is installing the newest redsleeve-release rpm (on the
todo list)
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]
https://lists.redsleeve.org/mailman/listinfo/users
