I have been following the discussion on this list regarding the wear-ability of CF cards, and in the past have done non-Read Only installs, using both CF and microdrives. There are two primary reasons why I am interested in doing this:
1) To learn more about OpenBSD itself. Solving all of the issues that have come up so far has been very beneficial and I've enjoyed the process 2) Setting up a RO system gives a level of redundancy in the case of power outages (or more likely in my neck of the world) or brownouts. I've had a case in the past where a normal OpenBSD install, on a micro-drive, was in a situation where due to an electrical storm, in the span of about 15 minutes the power blinked a number of times (and who knows how many brownouts). This caused the system to repeatedly reboot and then get shutdown suddenly. I was out of the house at the time and could not pull the plug on the system, and due to an oversight this unit was not plugged into a UPS. The next morning, when I tried to bring it back up the system was badly scrambled. Both the hardware and the micro-drive were not damaged, but the OS needed a lot of help. I would like to be able to deploy systems away from my personal control, where having a system be able to came back up in a similar situation would be useful. Peter -----Original Message----- From: Philip Guenther [mailto:guent...@gmail.com] Sent: Sunday, July 11, 2010 6:22 PM To: Peter Bako Cc: misc@openbsd.org Subject: Re: PTY allocation error On Sun, Jul 11, 2010 at 4:31 PM, Peter Bako <pe...@bakonet.org> wrote: > I'm setting up (well, trying to I guess :-) ) a read-only OpenBSD system to > run off a small CF card. Never having done this before, I found an > excellent article written by Daniele Mazzocchio > (http://www.kernel-panic.it/openbsd/embedded/) to use as my guide. I had a > few minor issues crop up, but have been able to work my way through them. > However I finally got to one that I am stumped with. Since this problem doesn't occur in a normal installation that just followed the instructions from OpenBSD itself, perhaps you should take this up with the author of the instructions that you followed, because 1) they should understand why their directions include whatever step is causing the problem, and therefore can consider the effect of changing it, and 2) they'll want to integrate whatever fix is necessary into their directions. If the author of the instructions can't help you (or isn't responsive), then you should consider the wisdom of following unsupported directions that apparently have a bug. The question also arises of why you are using these extra instructions instead of doing a normal install. "What problem are you trying to solve?" What makes you think that these steps solve that problem? Philip Guenther
