@aikida3k `tac -r -s 'x\|[^x]' input_file`
@aikida3k figured out how to read in reverse byte by byte, makes sense for 256GB fields on a 256GB server, for example - already primes whatever of the next field and lands the current one fresh into fscache
and yes, tac is cat backwards, but have to do that silly regex trick to have it properly handle there being a byte matching `\n`
why does backwards help?
@Rotonen there's a tool you can easily compile/install on linux `vmtouch` that allows you to specifically cache a specific file or directory into ram.
n34t
I noticed this on-chain voting cool
@Clueless yes, catting to dev null does that as well, but not byte for byte in reverse
@Fireduck say you have a 256GB server with the 256GB field and the activated field is the 128GB field
@Rotonen Thanks, I'll get a chance to try it out: power flashed off and back on from a storm. But for now I am going to get some sleep
It's hard to be at 2 places discord and slack and i want to read everything as i don't understand this project well
reading everything sounds like a very time consuming hobby
hello, just wondering how much space do i need to run a miner? I was quite surprised when a 50GB miner was maxed out
also if you guys need some help with some frontend stuff idm helping out
currently 128GB, probably soon 256GB
its possible mine whit mac os?
yes