Updating openbsd

I've used Free BSD for about 5 years - server/Desktop - and I've tended to take my apt-get/yum upgrade everything habits along with me ( I admin Debian/RHEL/Cent boxes as well -- I know, I know ...should be more discerning regardless of platform ). Then just clean up any messes afterwards ..they occur.This, I realize, is a fairly excessive un-BSD way to do things. Do you run a portaudit/portversion -- check output then update (make deinstall ...etc) after careful consideration? I see myself cvsupping the ports tree, running the "out of date" script, then just upgrading critical ports --- but leaving the kernel/binaries alone and just upgrading every six months.snap checks the `BUILDINFO` file located on the remote mirror, and will warn you if the snapshot is not newer than the currently running version.By default snap verifies the signature for the set files it downloads.https://ftp.openbsd.org/pub/Open BSD/Open SSH/openssh-6.6gz If you are installing Open SSH 6.6 on Open BSD 5.4 or earlier, you will need the the following patch: https://ftp.openbsd.org/pub/Open BSD/Open SSH/openbsd54_6.6.patch.

While that’s running, let’s get the download files. This isn’t a big deal, except for those few that must be built as ports because I require something unusual.

The firmware is already on the system - would I need to drop to shell and manually load it? if I misunderstood your question just ignore my often-foolish post : your case is similar to mine in that I too need wpi firmware to be downloaded .. We ask that members do not turn threads into a smorgasboard of different topics.

what I do is just download the right firmware for later use after pkg_deleting everything .. This make searching for specific information difficult (since most members use the site's search facility the most...). I suspect you have note found that your follow-up question has been split from its parent thread.

(This might also invalidate any bug report you send.) Don’t do this if you have any need or respect for your computer. One annoyance with using an MSDOS-formatted disk for backup is that you can’t have a file larger than 4GB. I must use gtar to back up my home directory, and use the multiple-volumes option. Sysmerge will compare your installed /etc with the snapshot fileset and show you the diffs.

I treat my desktop with a mix of indifference and contempt, so I’ll proceed. When gtar completes a 4GB file, it asks me to prepare a new volume. Kill all daemons that aren’t necessary for a minimally-running system. You can install the new file, delete the new file, or merge the two together.


Leave a Reply