Caltrops - Rants





	[quote name="Senor Barborito"][quote name="Chairman Mao"]Hey Barbie, I want to do an install of OpenBSD-current. I've never done a -current install of anything before. Recommendations?[/quote] I compiled a 3.3 --stable kernel with source grabbed off CVS. Unfortunately there are so many changes going in 3.4 that there are fundamental problems with binary incompatibility and things just not working in the --current branch right now. This is like common knowledge in the community at this point so I'm surprised you haven't heard. Among the changes: a.out ELF crap, ProPolice being moved from strictly userland to include kernel (includes fundamental changes to init_main.c), and the new WorX tech. Early after a new release is the worst time to toss over to --current, and the 3.3->3.4 changeover triply so. Grab src.tar.gz, sys.tar.gz from your local ftp and unroll them into a /usr source tree. If you're using ksh: export CVSROOT=anoncvs@anoncvs.ca.openbsd.org:/cvs (change export to setenv and drop the '=' for csh or sh, I believe) then, IIRC (it was late) cd /usr cvs -q up -rOPENBSD_3_3 -Pd to patch up to --stable (the 3.3 + obvious non-security bugfixes) If you really want to experiment with --current, try: cvs -q up -Pd Please note this is how I did it - I might be wrong! CVS is, unfortunately, not my greatest strength. The manual on how to do it is <a href="http://www.openbsd.org/anoncvs.html">here</a>, and if I'm not mistaken what I've just described is accurate. Compiling your own kernel is trivial - compiling it well is a process of painful trial and error, refer to sections <a href="http://www.openbsd.org/faq/faq5.html#Options">5.3 and 5.4</a> of the FAQ for 'how' - I followed this exactly and managed, with good options to trim off 2MBs and with the addition of a bunch of special compiler flags for gcc managed to really optimize it as well. Geodsoft also contains a very outdated but useful <a href="http://www.geodsoft.com/howto/harden/OpenBSD/kernel.htm">Howto</a> on this. --SB[/quote]