Thanks for the help, but I've managed to find the culprit, and it was
the dev machine all along. My lesson is not to trust KDE (I'm using
Kubuntu 11.10) and the GUIs.

Now I do these steps, with the extra directories mnt1 and mnt2, plus the
CF ext2 partition card is /dev/sdc1:

sudo mount -o loop output/images/rootfs.ext2 /mnt/mnt1
sudo mount /dev/sdc1 /mnt/mnt2
sudo rm -vr /mnt/mnt2/*
sudo cp -vr /mnt/mnt1/* /mnt/mnt2
sudo umount /mnt/mnt2
sudo umount /mnt/mnt1

umount takes a lot longer than KDE did to dismount the CF card so I
think umount seems to be doing a better job. After this method, the
network worked first time with the file being updated.

Thanks!
Steven Graham


On 12/01/2011 04:58 PM, Denis Kuzmenko wrote:
> On 12/02/2011 12:45 AM, Steven Graham wrote:
>> On 12/01/2011 04:32 PM, Denis Kuzmenko wrote:
>>> Hi Steven,
>>>
>>> On 12/01/2011 10:57 PM, Steven Graham wrote:
>>>> Hi
>>>> What am I doing wrong?
>>> I remember has same problem with ext2/3 (handled by ext4 driver) mounted
>>> over mtdblock device. The only way I was able to change a configuration
>>> file was to generate new fs image and write it to the drive. That time
>>> the problem was fixed by using JFFS2 instead of ext.
>>>
>> sorry for the double post, but does grub understand the JFF2 file
>> system? This is a normal BIOS based PC system.
> Sorry for misprint, that was YAFFS2.
>
> No, there's no support for YAFFS2 in 3.0 vanilla kernel, but it can be
> easily patched for that (but for 3.1 you'll have to fix cuople of simple
> compilation errors causes by VFS API and mtd driver changes).
>
> Is you CF and mtd-based device? I don't think YAFFS is capable to
> operate on top of generic block device.
>
> I don't think GRUB supports YAFFS. However, you can use separate storage
> (physical drive or partition) to load the kernel.
>
> What FS are you currently using? What's it's configuration in the
> kernel? Can you try same FS with other medium (USB-Stick for example).
>

_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox

Reply via email to