Contributed by mk/reverse on from the dept.
By hand | 82.2% (162 votes) | ||
Tepatche | 0.5% (1 votes) | ||
Binary Update Project | 4.6% (9 votes) | ||
Custom Scripts | 9.1% (18 votes) | ||
Other (please comment) | 3.6% (7 votes) | ||
Total votes: 197
(Comments are closed)
OpenBSD Journal
Contributed by mk/reverse on from the dept.
By hand | 82.2% (162 votes) | ||
Tepatche | 0.5% (1 votes) | ||
Binary Update Project | 4.6% (9 votes) | ||
Custom Scripts | 9.1% (18 votes) | ||
Other (please comment) | 3.6% (7 votes) | ||
Total votes: 197
(Comments are closed)
Copyright © - Daniel Hartmeier. All rights reserved. Articles and comments are copyright their respective authors, submission implies license to publish on this web site. Contents of the archive prior to as well as images and HTML templates were copied from the fabulous original deadly.org with Jose's and Jim's kind permission. This journal runs as CGI with httpd(8) on OpenBSD, the source code is BSD licensed. undeadly \Un*dead"ly\, a. Not subject to death; immortal. [Obs.]
By Ray (209.120.187.2) ray@cyth.net on
Comments
By sean (139.142.208.98) on
Comments
By Ray (209.120.187.2) ray@cyth.net on
Upgrading using snapshots, everything was transparent to me, including the infamous a.out->elf change. Snapshots are great—they’re like binary patches, but from the OpenBSD team.
I don’t see what’s so difficult. I just have a -current source somewhere, NFS mount it, mergemaster to update /etc, and boot from either a floppy or bsd.rd. Done.
Comments
By sean (24.77.212.220) on
By sean (139.142.208.98) on
At least with diffs it is trivial to reverse the patch and rebuild albiet longer and 'more complicated.' Feel free to enlighten me on this topic but until there is a source of binary 'patches' I can trust and a way to back out of the patch if need be I'm sticking with the 'by hand' method.
By chort (216.148.213.196) on http://www.smtps.net/email-sec/
I really, really wish they would integrate some option for building your own binary patches (and maybe distribute them on the FTP sites, too).
Comments
By Anonymous Coward (204.214.120.254) on
By gabriel (200.221.124.40) on
By almeida (66.31.180.15) on
Comments
By sean (24.77.212.220) on
It takes a lot of effort to evaulate a patch. If there is any doubt it affects me I roll it out. If it's a real pain there are other methods dealing with the problems. You don't need to worry about a reliability fix for some hardware you don't own.
Now that was a tangental post. :L
By Pascal Lalonde (69.70.147.211) plalonde@overnet.qc.ca on
http://www.openbsd.org.mx/~santana/binpatch.html
You can either download binary patches, or build them yourself by using the framework provided on the website. The amount of work required to generate a binary patch is comparable to patching by hand, except that you only need to do it once. You can then untar the binary patch everywhere else (as long as it is the same arch, of course). I've been using it since 3.1. It works great, and it doesn't try to be a wizard that does everything for you, which is something I like about it. You're still the one in control.
By I.S. (212.184.216.33) on
--is
Comments
By Kevin R (209.89.223.95) on
By Paladdin (80.58.46.107) on
On the other hand, OpenBSD default installation policy should make really easy to full-install a new release with no pain because it stores /var and /home in their own disklabels. Just keep an eye on /etc... :-)