Hello, thank you all for your "binary upgrade" responses, but I do not think that it is the right method for my conditions.
My machines are about 500km away and my remote access is solved by openvpn clients. Physical access to them and booting from external CD (or other installXX.iso image) is possible - hopefully only about once a year. Quick look into /usr/src/etc/Makefile reveals, that only way to install rc.d scripts are through "make distribution-etc-root-var", which is called by "make release" (so here is that binary upgrade), but not by "make install" or "make build". So, 1) is there any way to do binary upgrade from release files without loosing remote connectivity? 2) upgrade from source will be no more supported for obsd5 ? 3) if I do that cp/chmod/chgrp for /etc/rc.d/* files by hand, what else will be missing in upgraded system? Alexander On Sun, 2011-07-24 at 15:49 +0200, Alexander KrE!ek wrote: > Hello, > > may be this is something I simply overlooked, but I found out (hard way) > that my way of building/updating -current system from source (FAQ 5.3 + > FAQ 5.5 w/o "Making a release" + sysmerge) left my system without > new /etc/rc.d/ startup files (and may be some else). > > Is this a) bug, b) documented feature, or c) my stupidity? > If c) is right, what is "the right way" of complete upgrade -current > system from source? > > Alexander
