Re: updating remote 2.5 to current

[William Allen Simpson <wsimpson_(_at_)_greendragon_(_dot_)_com>]

"John K." wrote:
> 
> What OS were you going to run instead? 

That's the problem.  There is no other OS to "run instead" with this 
feature set.  Security is very important to me.  I just wish that 
ease of use was a priority with the core developers.

Noting your domain name, maybe I should be looking harder at MacOS X.  
I've heard that they are closely following the OpenBSD changes.  And 
ease of use is certainly an Apple hallmark.

I wonder whether they will keep the security, though.  The AirPort has 
only 40-bit, and you have to turn it OFF to interoperate with Lucent. 
Not a good sign of things to come.


> Maybe you should just spit out the
> cash and build another box that you rotate between upgrades. 

Yes, compared with the cost of flying down and installing, another box 
is much cheaper.  In this case, I'm probably going to have them ship 
the machine back to me, install, and ship it back down there.  We can
live without network monitoring at that remote POP for a short period 
of time.  And are already living without the security....

It was an experiment.  That was the only OpenBSD box we've got in 
production operations.  Everything else is commercial boxes.

But I'd kinda hoped that I could add more open source boxes, instead 
of using commercial.  OpenBSD was/is getting better.  Install has 
gradually improved over the past 2 years, although it's still not easy 
enough to do by regular tech support. 


> Maybe you
> shouldn't have upgraded.
> 
Wanted the 2.6 features.  Knew upgrading was hard.  Looked at it for 
months before doing it.  Solicited advice, and followed it.  At least 
one person (on this list) has upgraded remotely successfully.

WSimpson_(_at_)_UMich_(_dot_)_edu
    Key fingerprint =  17 40 5E 67 15 6F 31 26  DD 0D B9 9B 6A 15 2C 32