[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: updating remote 2.5 to current
- To: tech_(_at_)_openbsd_(_dot_)_org
- Subject: Re: updating remote 2.5 to current
- From: William Allen Simpson <wsimpson_(_at_)_greendragon_(_dot_)_com>
- Date: Wed, 08 Dec 1999 10:42:12 -0500
Theo de Raadt wrote:
> Life is tough.
> We specifically said, time after time, that upgrading from 2.5 to 2.6
> was very difficult to do.
> You didn't listen. You even phoned me to personally complain about
Actually, to set the record straight, I called to ask whether I should
work on trying to build an automated environment for updating, so that
the lessons I was learning wouldn't have to be repeated. You turned me
down, saying "this is not a priority for us."
According to you, folks running remote or embedded systems just never
update. Certainly this is antithetical to my 20+ years of experience in
computer networking. I know that on the netblazer project, we put quite
a lot of effort into the automated update. Operationally, we update our
ciscos and portmasters regularly.
It certainly is harder for OpenBSD, because the powers that be don't
seem to be interested in careful planning.... But, since widespread use
of OpenBSD would make the Internet a better place, I think that planning
upgrades and migration would be a good thing.
Meanwhile, I documented some of the major etc26 changes to this list,
and documented what appear to be redundant directories in base26. Or
maybe that have to be there for some obscure reason. I asked pretty
Some pedants would rather complain than explain.
Why do you have to be so hard to deal with?
Key fingerprint = 17 40 5E 67 15 6F 31 26 DD 0D B9 9B 6A 15 2C 32
Visit your host, monkey.org