Talk:Advanced booting
(New page: Great someone is documenting this, thanks :-) Few random comments: cp -a /mnt/initfs initfs is not best idea, you will copy also unneeded stuff in proc, sys, dev, tmp ... and you may also...) |
m (Protected "Talk:Advanced booting" [edit=autoconfirmed:move=autoconfirmed]) |
||
| (4 intermediate revisions not shown) | |||
Latest revision as of 17:01, 8 August 2012
Great someone is documenting this, thanks :-) Few random comments:
cp -a /mnt/initfs initfs is not best idea, you will copy also unneeded stuff in proc, sys, dev, tmp ... and you may also miss hidden stuff under some such mount point (/dev), safer is
mount -t jffs2 /dev/mtdblock3 initfs.orig cp -a initfs.orig initfs
As for inplace editing, this is somewhat safe with Diablo. With older 2MB big initfs the danger was real. With just few (5-10?) edits of linuxrc file one may end with partially written (truncated) linuxrc and no way to fix it.
As for pre-caching initfs before flashing - this may not be strictly needed, maybe everything important is already cached, it is added just in case. We want to prevent situation where we are erasing/flashing /dev/mtd3 and bme or dsme causes some (both read or write) I/O and jffs2 driver becomes confused since we just erased mtd3 or completely rewrote it with different data.
- This page was last modified on 8 August 2012, at 17:01.
- This page has been accessed 7,806 times.