Live data from Hacker News

Ramroot – Run Arch Linux Entirely from RAM (2017)

ostechnix.com

81–83 of 83 posts

Re: Ramroot – Run Arch Linux Entirely from RAM (2017)

#81

Earlier quoted context omitted.

Never having finished Home pxe setup is a great sadness of mine.

Turn that sadness into joy! Even an RPI can host your TFTP and your boot files... Today! http://ipxe.org/start has all the info you'll need.

I shall attempt soon then. Thanks

Re: Ramroot – Run Arch Linux Entirely from RAM (2017)

#82
post #53

Earlier quoted context omitted.

> Then when the cops would seize the machines and cut power to save as much evidence as they could, they'd actually be doing the opposite. Let's for a second assume that forensic computer technicians aren't completely incompetent and actually understand that you do not pull the plug on a system that potentially contains evidence the first thing you do. While this has been known to happen in the past, I can almost gua…

Lol, forensic technicians are pretty incompetent overall. Like I remember a peer reviewed article on PS3 forensics where they explicitly have a section on trying to run a PS3 disk image in VMWare and didn't understand why they couldn't get it to work. And this piratebay mitigation was in the early 2000s. At that point most of the anti forensic mitigations were booby traps on input channels (keyboard, console, etc) an…

> Under that scheme, pulling power before inspection is what you want to do.

Why? Are you saying there were no measures to make data inaccessible in case of power failure?

Re: Ramroot – Run Arch Linux Entirely from RAM (2017)

#83
post #33

I wonder whether this achieves anything performance-wise that just cat'ing every file to /dev/null to warm up the buffer cache wouldn't achieve. In theory, the kernel uses a buffer cache that will hold on to disk pages until they're invalidated by writes. It'll evict the cache if there's memory pressure. But this setup will presumably just crash if there's memory pressure, so that doesn't seem like a win for the RAM…

I can't hard-core prove anything, but I've read the theory on how if I'm accessing warm disk cache, putting things into a RAM disk shouldn't speed them up, and every time I've done it and tested it, putting things in a RAM disk is faster than having it on disk, even when the very act of copying the stuff into RAM should definitely have just warmed everything up just before the test. I've not done it very often, but e…

It shouldn't matter _if_ all you're doing is reading. If you boot Linux, there's a ton of things that do small writes and then call fsync. That won't do anything on a RAM disk but is relatively slow, even on an SSD.
Post reply on HN