Thread: Embedded.
View Single Post
Old 29th March 2009
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 7,975
Default

The size of /var will need to be set based on your application needs, and there's no way to predict it without knowing your application set and use requirements.

"noatime" is a helpful primarily for power consumption savings with hard drives (or flash memory) with read/write disk. It can also have performance savings, too. By default, a read/write FFS filesystem will store the last-time-of-access for every file. It isn't used on read/only mounts, so "noatime" will have no impact on them. For MFS filesystems which do not get swapped, you won't see any impact from "noatime". If there is any swapping, "noatime" may reduce the amount occuring, depending on access patterns.

The use of "nodev" and "nosuid" are for security, and are recommended. If need be, "dev" or "suid" may be enabled with mount -u.

-----

I was joking a little bit about deploying RAIDframe to create a complete set of filesystems-in-RAM. I would say you'd need a lot more operational experience with OpenBSD, first. Why? Because that "how to" document is:
  1. unofficial
  2. out of date
  3. uses a custom kernel, which is unsupported
A more modern method, at first glance, would be to use softraid(8) to accomplish the same thing. But recoverability with softraid is not yet possible, nor is root-on-RAID, so the setup and mirror management pieces would need to be completely revamped.
Reply With Quote