https://maemo.octonezd.me/api.php?action=feedcontributions&feedformat=atom&user=109.186.40.225Maemo Wiki Mirror - User contributions [en]2026-04-22T17:10:19ZUser contributionsMediaWiki 1.45.1https://maemo.octonezd.me/index.php?title=Talk:Advanced_booting&diff=43662Talk:Advanced booting2011-12-16T06:13:33Z<p>109.186.40.225: /* all-inclusive */ new section</p>
<hr />
<div>Great someone is documenting this, thanks :-) Few random comments:<br />
<br />
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<br />
mount -t jffs2 /dev/mtdblock3 initfs.orig<br />
cp -a initfs.orig initfs<br />
<br />
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.<br />
<br />
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.<br />
<br />
== all-inclusive ==<br />
<br />
<a href=http://www.001casino.com>online casino</a> <a href=http://www.casinovisa.com/no-deposit-casinos/>free casino</a> , <a href=http://www.concordiaresearch.com/games/video-poker/index.html>poker</a> , <a href=http://www.realcazinoz.com/ukr>paypal casinos</a> , <a href=http://www.avi.vg/>adult toys</a></div>109.186.40.225