Practicing a system update more than anything else. Working from memory and reading the wrong (erk) FAQ pages, I did this:
cd /usr/src/sys/arch/`machine`/conf /usr/sbin/config GENERIC cd /usr/src/sys/arch/`machine`/compile/GENERIC make clean & make (Yes, I also did the concurrency instead of the logical and there. Sigh.) Got some parse error, cannot opens, of course. Realized I had forgetten the cvs update, so I did cd /usr/src/sys/arch/`machine`/compile/GENERIC make clean in the hopes that would suficiently clean up the mess I had made. Then, cd /usr/src cvs -d anon...@anoncvs.jp.openbsd.org/cvs -q up -Pd (Yeah, I forgot the colon, as well. Which is why I'm practicing. I hope I'l make enough mistakes to get things right when it counts.) That's where I get the message cvs server: use `cvs add' to create an entry for gnu/usr/bin/gcc/INSTALL" after which, it finds the update from 5.6 errata 015 P lib/libevent/buffer.c before it timed out pruning. Searching for the message found me this really old note on misc@, circa 2005: http://marc.info/?l=openbsd-misc&m=111362929106080&w=2 and apparently I now have a directory where I probably should have had a file named INSTALL? Indeed, /usr/src/gnu/usr.bin/gcc/INSTALL is a directory, with a bunch of .html files in it. Re-running the cvs update with ":/cvs" produces the same message. Should I just remove that directory and continue with the build process? Leave it there and ignore the mesage? Or should I scratch the source tree and restart it from the tarballs? -- Joel Rees Be careful when you look at conspiracy. Look first in your own heart, and ask yourself if you are not your own worst enemy. Arm yourself with knowledge of yourself, as well.
