On 2014-07-18, Antoine Jacoutot <ajacou...@bsdfrog.org> wrote: > On Fri, Jul 18, 2014 at 12:16:00PM -0400, RD Thrush wrote: >> For many years, I have reliably used read-only partitions for /usr and >> /usr/local. -current sysmerge breaks that assumption. > > I don't think we ever officially supported a RO /usr...
the FAQ is fairly official..though, see my comment below. >> sha256: ///usr/share/sysmerge/examplessum: Read-only file system slashslashslash! (untidy extra /'s is a pet hate :) >> +<li><a href="#20140716">2014/07/16 - sysmerge requires writeable /usr >> partition</a> this one may make sense, but it's "writable", only 1 e >> Index: faq4.html >> =================================================================== >> RCS file: /pub2/cvsroot/OpenBSD/www/faq/faq4.html,v >> retrieving revision 1.339 >> diff -u -p -u -p -r1.339 faq4.html >> --- faq4.html 15 Jul 2014 00:24:32 -0000 1.339 >> +++ faq4.html 18 Jul 2014 15:58:50 -0000 >> @@ -2331,9 +2331,7 @@ Some of the things that end up here (and >> This is where most of OpenBSD resides. >> Program binaries, libraries, documentation, manual pages, etc. are all >> located in the <tt>/usr</tt> directory. >> -The files in this mount point are relatively unchanging -- in many >> -cases, you could easily mount the <tt>/usr</tt> partition read-only with >> -no other system changes until your next upgrade or update. >> +The files in this mount point are relatively unchanging. I would argue that sysmerge is covered by "until your next upgrade or update".
