Re: Important: following -current update!

2013-04-16 Thread Michał Markowski
$ cd /usr/src/sys/arch/`uname -m`/config
cd: no such file or directory: /usr/src/sys/arch/i386/config
$ cd /usr/src/sys/arch/`uname -m`/conf
$


--- /cvs/www/faq/current.html   Tue Apr 16 11:54:22 2013
+++ /tmp/current.html   Tue Apr 16 12:10:27 2013
@@ -597,7 +597,7 @@
 ul
 liUpdate entire source tree using cvs
 liconfigure and build a new kernel:
-blockquotepreb   cd /usr/src/sys/arch/`uname -m`/config
+blockquotepreb   cd /usr/src/sys/arch/`uname -m`/conf
config GENERIC  # or GENERIC.MP or whatever config you use
cd ../compile/GENERIC   # or GENERIC.MP or ...
make clean


--
Michał Markowski



Important: following -current update!

2013-04-15 Thread Philip Guenther
While it's often the case that you can leave our steps when building
-current from source, it is sometimes ABSOLUTELY REQUIRED that you
followed the steps precisely.

This is one of those times.

If you build a -current kernel without running config(8) and make
clean, then the resulting kernel WILL NOT RUN YOUR INSTALLED
USERLAND.  If that happens, you will have to boot from the old kernel
(do you know how?) or boot from an alternate device like a CD.

If you are not 100% comfortable with doing that recovery, then you
should wait and install the next snapshot instead.


Philip Guenther

-- Forwarded message --
From: Philip Guenther guent...@cvs.openbsd.org
Date: Mon, Apr 15, 2013 at 8:56 PM
Subject: CVS: cvs.openbsd.org: www
To: source-chan...@cvs.openbsd.org
...
Modified files:
faq: current.html

Log message:
statfs change requires strict following of the build steps, or you'll
end up with a userland that can't mount (or remount!) critical filesystems