that causes in updating.
Submitted by: Robert Watson
[[ NB: marko and I are trying an experiment: he'll try to fix typos
quickly in UPDATING, while I concentrate on content. ]]
cookbook section about needing to copy GENERIC.hints to
/boot/device.hints, as well as a footnote about exceptions to this
rule.
Partially suggested by: obrien
o BUILD_SUIDPERL replaces NOSUIDPERL
o New /etc/rc.conf settings for secure networking may require changes
to those upgrading.
o nullfs in loader.conf.
older versions of FreeBSD.
o Continue to document the old way of doing it with a warning stating if that
doesn't work, to do the {build,install}kernel thing.
o minor wordsmithing on what a make world really is.
files and put it in my freebsd web area. Rewrite the entry in
UPDATING to point to it the message and hopefully not confuse people
like the old one did.
July 4th due to the new sys/modules/sound/drivers/* being added to the
tree. You will need to do this until you do a make installworld with
my bsd.kmod.mk change.
system. Well, not really required if you know what you are doing, but
there's enough people that don't fit into this class that are getting
burned now that we need to say it is required. The actual message
says that one should treat it as if it was required to try to be
weasilly for the nitpickers amoung us :-)Killed by signal 2.
o add note about binutils 2.10 fixing the problems noted on 20000522.
o Add some very brief text to the '612 entry on the config changes.
A better howto would be warmly added to the file.
people have suggested the workaround to me (use only PIO mode) and
I've not seend a message saying ths was fixed. I'll removed the bold
warning stars after the issue is corrected.
into UPDATING. However, in this case I'm making an exception. I'm
adding a recommendation that people update their boot blocks. Old
boot blocks will cause a system to become unbootable if you have
removed /dev/{,r}wd*.
Submitted by: Jeroen Ruigrok/Asmodai <asmodai@freebsd.org>
file and start over.
Also note that we're in the traditional whack-a-ball kernel model/api
reorg for 5.0 and that one needs to be extra careful about making sure
models and kernels are in sync.
those questions that come up all the time (eg, how do I build a
kernel). This is intended to be a very brief reminder for people that
are basically clueful what the steps are to do these common things.
What it lacks in verbosity it makes up in terseness.
