Sorry, no time to do this right -- just throwing in some gross notes to help jog my memory if I find myself stuck here again...
See 10.0 install for personal customizations. (Ignore stuff about 'bsdintall'.) Install 'emacs24'. Skip 'bind99' install (see below).
Note: 'putty' with SSH->X11, select "Enable X11 forwarding" and put ":0.0" in the location box. Don't forget to 'setenv $DISPLAY=localhost:10.0' on the server. I used to use an older ssh client where this would work with localhost set to the client IP addr - this does not work with putty. Oh, btw I had to change to putty as my old client is now rejected by server with errors about old protocols no longer accepted.
'named' is now 'bind' and is no longer installed by default.
Installed that ('pkg install'), started getting bitch messages about
that being too old, please update to BIND911. So moral of this part
of story is to start with BIND911.
BIND911 now requires some dang kernel tweak or you'll get logspam something about "TCP_FASTOPEN". Gosub build custom kernel.
First time only:
pkg install subversion
svn checkout http://svn.freebsd.org/base/releng/11.1/usr/src
(Note: YOURSYSTEMNAME is traditionally done in all uppercase. I use the same name as the DNS name for the box)
cp GENERIC /root/kernels/YOURSYSNAME.i386
ln -s /root/kernels/YOURSYSNAME.i386 YOURSYSNAME
Edit your file
ident GENERIC to
(Note filename will have dot-architecture - ident does not.)
(Note: takes a few mins)
(Note: takes an hour or so)
(Note: change number to YYYYMMDDxx, year, month, day, attempt that day.)
make buildkernel KERNCONF=YOURSYSTEMNAME TARGET=i386 |& tee /root/kernels/20172600buildkernel.log
(Note: takes a few mins)
(Note: kernconf is kernel ident, not filename - no dot architecture)
(Note: output filename changes to "install" - was "build" in previous - as well as date and sequence)
Once you get a successful complete build:
make installkernel KERNCONF=YOURSYSTEMNAME TARGET=i386 |& tee /root/kernels/20172600installkernel.log
All should be ready, you can check that the install happened by checking the dates on the files in
/boot/kernel and make
sure it's now.
shutdown -r now
If you get an unbootable kernel, at the loader prompt you should be
able to proceed by entering
Once running, check which kernel you actually are running
/var/log/dmesg.today. Ignore the 6th line where it
gives a path to a GENERIC file - this seems to be the build that the
original files were based upon, as opposed to the actual build time
and date. Search for
not. Problems still? Google is your friend.
Now do same steps with
Now same steps with
/var/log/console - if this file is
not there, go back to this section in my release 10 install
I'm getting the same old dang boot error about more swap than
maxswzone that I was getting in
release 10. Tried same stuff as last time, still haven't gotten this
to go away yet, but it doesn't seem to have caused any problems so
will continue to ignore for now. Have spent unbelievable number of
hours googling, rebooting, trying stuff but never got this one
And you know what? After all this fucking shit, it still hasn't fixed
the fucking TCP_FASTOPEN error in the fucking console log from the
fucking 'bind' server. Fuck. Fuck. Fuck. Days in the toilet -
Am also seeing and have not figured out:
module_register_init: MOD_LOAD (vesa, 0xc10123d0, 0) error 19
pcib0: _OSC returned error 0x10