Thanks Gordon. I actually got onto this topic in my research last night, but would have completely hosed myself due to the byte alignment issue. I'll let you know how I do. On Jul 7, 2012 2:49 AM, "Gordan Bobic" <[email protected]> wrote:
> Hi Tom, > > You should be able to simply edit the partition to enlarge it with fdisk. > Delete it, then create a new one of the same type (primary or extended, > presumably primary), with the same number and the same starting point > sector, and make it the size of the rest of the media. Boot into it. > > Make sure you set /proc/cpu/alignment to 3 (fixup+warn): > # echo 3 > /proc/cpu/alignment > > Anything that is < ARMv7 doesn't do transparent alignment fixup and a lot > of software, including things like e2fsprogs, do very dangerous and > unportable things in their code such as allocating an array of char as a > buffer (which is byte aligned) and then casting it into a struct (which > needs to be at least word aligned). Otherwise whatever you get out of the > struct afterwards will be corrupted unless you are very lucky. Yes, this is > dangerous - outrageously dangerous in things like e2fsprogs (probability of > completely trashing your fs). I filed a bug for this but I don't know if it > has been fixed upstream in Fedora, and it is even less likely it has been > pulled down into RHEL6. So make sure you set the kernel based transparent > alignment fixup (performance overhead is a lesser evil). This is mostly an > issue due to a lot of developers suffering x86 induced brain damage, > despite most architectures apart from x86 and ARMv7+ not having transparent > alignment fixup (e.g. ARMv6-, SPARC, Itanium). > > Back to the original point - once you have done all that, shutdown to > single user mode, and use resize2fs to expand the file system to fill up > the available partition. > > Gordan > > On 07/07/2012 02:33, Tom Lynn wrote: > >> OK, this all sounds pretty straight-forward. I see one issue. Having >> purchased a 16GB card, how do I reconcile the size difference in the >> downloadable image? I think it expands to about 3.9gb or thereabouts. >> Can I extract the files from the image file on the FTP server? >> >> On Thu, Jul 5, 2012 at 6:39 AM, Gordan Bobic <[email protected] >> <mailto:[email protected]>> wrote: >> >> On 04/07/2012 21:47, Tom Lynn wrote: >> >> Gordon, >> I have Debian working now on the Sheeva Plug. Could I plug a 2nd >> SD >> card into the USB port and then move the kernel and initrd onto >> the boot >> partition of the new SD card? >> >> >> Yes, provided the partitioning and file systems are the same (e.g. >> FAT for /boot), then you should be able to just copy the files. >> >> >> If I need dracut to build the initrd, can >> I do that from Debian? >> >> >> You should be able to use the existing kernel uimage/initrd. >> Ultimately all they do is load up the drivers, mount the rootfs, and >> switchroot execute /sbin/init. >> >> Once you have RS booting you could have a go with the kernel rpm >> package and uboot-tools and see if that works for you. The kernel >> rpm situation is still, ahem, "experimental". :) >> >> >> and then later swap cards after putting the >> rootfs into the 2nd partition and updating the uboot variables >> (which I >> don't yet have specific for)? >> >> >> If you are specifying the rootfs by partition device rather than FS >> UUID (I think partition device is is the default anyway with the >> default setup on the plug), you shouldn't need to change anything in >> uboot. Just swap the cards and it should boot the new rootfs. As >> long as the kernel is the same file name on the same partition on >> the same FS type, and as long as the rootfs is on the same partition >> with the same FS type, it should "just work". Just make sure you >> also copy over /lib/modules and /lib/firmware, otherwise you might >> not have the drivers for things USB or ethernet available. >> >> >> Gordan >> ______________________________**___________________ >> users mailing list >> [email protected] >> <mailto:[email protected].**org<[email protected]> >> > >> >> http://lists.redsleeve.org/__**mailman/listinfo/users<http://lists.redsleeve.org/__mailman/listinfo/users> >> >> <http://lists.redsleeve.org/**mailman/listinfo/users<http://lists.redsleeve.org/mailman/listinfo/users> >> > >> >> >> >> >> ______________________________**_________________ >> users mailing list >> [email protected] >> http://lists.redsleeve.org/**mailman/listinfo/users<http://lists.redsleeve.org/mailman/listinfo/users> >> > > ______________________________**_________________ > users mailing list > [email protected] > http://lists.redsleeve.org/**mailman/listinfo/users<http://lists.redsleeve.org/mailman/listinfo/users> >
_______________________________________________ users mailing list [email protected] http://lists.redsleeve.org/mailman/listinfo/users
