Talk:Advanced booting - Revision history

andre: Protected "Talk:Advanced booting" [edit=autoconfirmed:move=autoconfirmed]

andre — Wed, 08 Aug 2012 17:01:12 GMT

Protected "Talk:Advanced booting" [edit=autoconfirmed:move=autoconfirmed]

← Older revision

Revision as of 17:01, 8 August 2012

joerg_rw: Undo revision 48906 by 37.113.8.128 (Talk) SPAM

joerg_rw — Mon, 06 Aug 2012 15:42:06 GMT

Undo revision 48906 by 37.113.8.128 (Talk) SPAM

← Older revision		Revision as of 15:42, 6 August 2012
Line 8:		Line 8:

	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.		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.
-
-	~~== suasweta ==~~
-
-	~~http://acheter-viagra-generique.org/ achat viagra~~
-	~~http://viagra-generico-espana.org/ viagra~~
-	~~http://achatviagragenerique.org/ generique viagra~~
-	~~http:///acheter-viagra-generique.net/ viagra acheter~~
-	~~http://comprar-viagra-sinreceta.net/ viagra 50 mg~~
-	~~http://bestellenviagragenerika.net/ viagra bestellen~~
-	~~http://acquistare-viagra-generico.net/ viagra~~

37.113.8.128: /* suasweta */ new section

37.113.8.128 — Mon, 06 Aug 2012 08:29:22 GMT

suasweta: new section

← Older revision		Revision as of 08:29, 6 August 2012
Line 8:		Line 8:

	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.		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.
		+
		+	== suasweta ==
		+
		+	http://acheter-viagra-generique.org/ achat viagra
		+	http://viagra-generico-espana.org/ viagra
		+	http://achatviagragenerique.org/ generique viagra
		+	http:///acheter-viagra-generique.net/ viagra acheter
		+	http://comprar-viagra-sinreceta.net/ viagra 50 mg
		+	http://bestellenviagragenerika.net/ viagra bestellen
		+	http://acquistare-viagra-generico.net/ viagra

joerg_rw: Undo revision 46049 by 109.186.40.225 (Talk) spam

joerg_rw — Fri, 16 Dec 2011 06:26:46 GMT

Undo revision 46049 by 109.186.40.225 (Talk) spam

← Older revision		Revision as of 06:26, 16 December 2011
Line 8:		Line 8:

	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.		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.
-
-	~~== all-inclusive ==~~
-
-	<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>

109.186.40.225: /* all-inclusive */ new section

109.186.40.225 — Fri, 16 Dec 2011 06:13:33 GMT

all-inclusive: new section

← Older revision		Revision as of 06:13, 16 December 2011
Line 8:		Line 8:

	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.		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.
		+
		+	== all-inclusive ==
		+
		+	<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>

fanoush: 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...

fanoush — Thu, 14 Aug 2008 07:16:56 GMT

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...

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 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.