CRUX PPC

Theodore Tso brought up some interesting tests about sticking to using noatime rather than relatime, especially when used with SSD's.

http://thunk.org/tytso/blog/2009/03/01/ ... erelatime/

Even though I'm not using an SSD with my ppc box, I have long been a fan of noatime.

Noatime has been discussed for years, so I won't rehash the whole thing here. Since I don't need hard-core forensic timestamp security, nor new-mail message notifications from mutt, I stick to noatime.

I thought I'd throw this out for those who might be using embedded or other ssd ssd-type systems, or guys like me who just want the least amount of wear and tear on their legacy hardware. :)

(On a related note, one may want to investigate using either elevator=deadline or elevator=noop in their kernel scheduler with ssd's. For my spinning hard-drive, I just use CFQ)

well, we use to be aligned with the main CRUX project when there aren't troubles on Power Architecture.
CRUX (and CRUX PPC) primary focus is KISS but the secondary one is utilization of new Linux features and recent tools and libraries.

I followed this interesting topic:
http://kerneltrap.org/node/14148