Doom 2 seen running on an E-Ink display

[geekmaster]

Originally Posted by twobob

... and the GM as it was his 0 Day that made the testing in-the-end a bearable process...

Unpublished 0-day exploit (until we need it). You are welcome! And congratulations!

EDIT: My 0-day exploit works on the Paperwhite too. I remember running diags, and I thought I tested my exploit, but I do not remember how I got my Paperwhite into diags. ???

[knc1]

Now see if chattr +/- i ... works on your K5
Not even 'root' can deleted a file or directory with 'i' set on it.

Note:
Best that I know, mmcblk0p3 (a.k.a: /var/local) is mounted at the same point in the file system in both 'main' and 'diags'.
I.E: It is common to both of them.
So if we take over an increased size /var/local for end-user applications . . .

[twobob]

yeah...

[root@[192_168_15_244] root]# df

Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root                63671     55007      5464  91% /
tmpfs                   127832         4    127828   0% /dev
tmpfs                   127832         0    127832   0% /dev/shm
/dev/mmcblk0p3           31729     15634     14457  52% /var/local
fsp                    3323544   1559144   1764400  47% /mnt/us
/dev/loop/0            3323544   1559144   1764400  47% /mnt/base-us

5.5 Mb is a bit buttock clenching already.

[knc1]

Originally Posted by twobob

yeah...

5.5 Mb is a bit buttock clenching already.

Yup, that eMMC could do with more than just a bit of tender, loving care.

When I get that broken DX(G) to network boot . . .
Then the eMMC will be just another piece of hardware that we can diddle with as we please.
Starting with sym-linking that OTA updater's name to /bin/true.

The network booting only depends on u-boot, one "HowTo" should (mostly) fit all K's

[twobob]

Originally Posted by knc1

Now see if chattr +/- i ... works on your K5
Not even 'root' can deleted a file or directory with 'i' set on it.

Note:
Best that I know, mmcblk0p3 (a.k.a: /var/local) is mounted at the same point in the file system in both 'main' and 'diags'.
I.E: It is common to both of them.
So if we take over an increased size /var/local for end-user applications . . .

[root@[192_168_15_244] root]# chattr -h

Usage: chattr [-RVf] [-+=AacDdeijsSu] [-v version] files...

[root@[192_168_15_244] root]# lsattr -h

Usage: lsattr [-RVadlv] [files...]

: ) yep workers

[knc1]

Ah, maybe you missed it during all of the excitement:
http://www.mobileread.com/forums/sho...&postcount=138

[twobob]

Originally Posted by knc1

Ah, maybe you missed it during all of the excitement:
http://www.mobileread.com/forums/sho...&postcount=138

ah sorry. : )

[root@[192_168_15_244] root]# touch /var/local/something_new
[root@[192_168_15_244] root]# chattr +i /var/local/something_new
[root@[192_168_15_244] root]# lsattr /var/local/something_new

----i---------- /var/local/something_new

[root@[192_168_15_244] root]# chattr -i /var/local/something_new
[root@[192_168_15_244] root]# rm /var/local/something_new

[knc1]

Originally Posted by twobob

ah sorry. : )

[root@[192_168_15_244] root]# touch /var/local/something_new
[root@[192_168_15_244] root]# chattr +i /var/local/something_new
[root@[192_168_15_244] root]# lsattr /var/local/something_new

[root@[192_168_15_244] root]# chattr -i /var/local/something_new
[root@[192_168_15_244] root]# rm /var/local/something_new

And if you had tried to rm /var/local/something_new after setting the 'i' (immutable) attribute you would have gotten a "permission denied" - even as 'root'.
Works for directories also, but I don't know what would happen if the start-up script got a "permission denied" error code.
I didn't see much error checking in that lab126 script you posted.

[eureka]

Isn't it (chattr) was explored in purposes of securing /usr/local at diags partition? I'm just confused with example of setting attrubute on /var/local...

[qlob]

Originally Posted by eureka

Isn't it (chattr) was explored in purposes of securing /usr/local at diags partition? I'm just confused with example of setting attrubute on /var/local...

I think the above was a test of chattr....

[twobob]

Originally Posted by knc1

And if you had tried to rm /var/local/something_new after setting the 'i' (immutable) attribute you would have gotten a "permission denied" - even as 'root'.
Works for directories also, but I don't know what would happen if the start-up script got a "permission denied" error code.
I didn't see much error checking in that lab126 script you posted.

[root@[192_168_15_244] /dev]# rm /var/local/something_new
rm: remove '/var/local/something_new'? y
rm: can't remove '/var/local/something_new': Operation not permitted

heh. classic.

Originally Posted by eureka

Isn't it (chattr) was explored in purposes of securing /usr/local at diags partition? I'm just confused with example of setting attrubute on /var/local...

just a "for example".

[twobob]

so - how does one "shutdown" from diags?

init level?

[root@[192_168_15_244] /dev]# shutdown -r now
-sh: shutdown: not found

[qlob]

poweroff maybe?

[twobob]

I'll sync first. and tidy up /etc/fstab

just to be on the same side.

[root@[192_168_15_244] /dev]# poweroff -h

BusyBox v1.17.1 (2012-04-16 16:44:42 PDT) multi-call binary.

Usage: poweroff [-d DELAY] [-n] [-f]

Halt and shut off power

Options:
-d Delay interval for halting
-n Do not sync
-f Force power off (don't go through init)

[knc1]

Remove battery?

OR do a "geekmaster" -
leave this one in 'diags', buy another, then leave that one in 'main'
At least I think that is why he has dozens of them.