Difference between revisions of "OpenBSD readonly root"
Jump to navigation
Jump to search
m (→Installation) |
(link to other pages) |
||
| Line 5: | Line 5: | ||
mostly in the end-user or volatile-power routing environments. Most often, I've done this<br /> | mostly in the end-user or volatile-power routing environments. Most often, I've done this<br /> | ||
on [http://www.soekris.com/ Soekris] [http://www.soekris.com/net4801.htm net4801] devices.<br /> | on [http://www.soekris.com/ Soekris] [http://www.soekris.com/net4801.htm net4801] devices.<br /> | ||
| − | |||
| − | |||
<br /> | <br /> | ||
To perform such a magic trick, you need to do a bit more planning. It's not as easy to run some<br /> | To perform such a magic trick, you need to do a bit more planning. It's not as easy to run some<br /> | ||
| Line 15: | Line 13: | ||
space.<br /> | space.<br /> | ||
| − | = | + | = Detailed Examples = |
| + | * [[OpenBSD Soekris Read Only Root]] | ||
| + | * [[Sun Netra t1 compact flash root]] | ||
| − | = | + | = Other Useful Info = |
| − | + | * [[Setting up PXE]] or: "building a netboot server" | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 17:40, 3 December 2009
Theory
In a lot of situations, you'll find yourself not wanting to check filesystems, thereby
facilitating hard power-downs with ~no data loss. I've come across this case a few times,
mostly in the end-user or volatile-power routing environments. Most often, I've done this
on Soekris net4801 devices.
To perform such a magic trick, you need to do a bit more planning. It's not as easy to run some
services in a configuration like this, since they need areas to write to. Even worse is when they
need to write data that you actually want to keep. In this case, I like to avoid the RO root
scenario, because it adds some awkward complexity that involves a regular mount-writable/sync/remount-ro
cycle. In general though, most services you can get away with just providing them ramdisk scratch
space.
Detailed Examples
Other Useful Info
- Setting up PXE or: "building a netboot server"