I came across a similar problem--I think the error message I saw was
'could not create session' or some such thing--when trying to login as
root. I think the only way I could get past that was to reformat the
rootfs partition--but I don't know if it was ext3 or ext4.
It would appear that the uboot param and the fs format must agree or
things seem to get messed up. It would get so bad at times that I would
see console messages that the root partition was getting remounted as
read-only and a e2fsck was required.
BTW--anyone know how to check if a given partition is truly formatted as
ext3 or ext4? I poked around in the /proc tree but it seemed that any
info there simply mirrored what the uboot param was set to.
On 12/10/2012 6:16 PM, Alan DuBoff wrote:
Peter,
I can't tell you if there is any difference, but noticed the same.
I had an microSD that I did format to ext4 on the rootfs partition,
and it seemed that it would write faster when I un-tar'd the rootfs
image to the partition. But then I ran into a problem where I
installed mysql5 on the image, and could log in and setup the database
(after commenting out the /etc/default/RCS files it tries to source,
which breaks the startup), made a few changes, and then when I reboot
the device it couldn't start a session (permission problem) when I was
trying to log in as root. Odd thing is that it seemed my partition was
mounted as ext3, and not sure that makes a difference or not...but I
went back to an ext3 partition, and after a couple boots had the same
problem, didn't have permissions to start a session for root.
I am still not sure if ext4 would be better or worse, so watching what
others have to say about this.
_______________________________________________
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
