Date: Thu, 13 Jul 2000 07:53:56 -0500 From: "Shawn Barnhart" <swb@grasslake.net> To: "Warner Losh" <imp@village.org> Cc: "Kris Kennaway" <kris@FreeBSD.ORG>, <stable@FreeBSD.ORG> Subject: Re: HEADS UP! Always use the 'make buildkernel' target to make yerkernels Message-ID: <000e01bfecc9$67ec3c20$0102a8c0@k6> References: <00b801bfeb66$94ab2960$9b239fc0@mobocracy> <Pine.BSF.4.21.0007102332020.70151-100000@freefall.freebsd.org> <200007130506.XAA21015@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message ----- From: "Warner Losh" <imp@village.org> | | Read UPDATING for late breaking news. We've been recommending this | proceedure for building kernels since before 4.0 was released. It is | documented. If there isn't a note in the handbook to look at | UPDATING, there should be. I can appreciate that, but what often frustrates me about FreeBSD (and maybe I'm still too used to the Linux world) is that the documentation seems to lag. Maybe after another six months of use it won't matter to me and I'll understand why its not a priority, but major stuff like the kernel build changes ought to be a documentation update priority to prevent the throngs from posting 10,000 messages asking "Why doesn't my kernel/world build right?" Is UPDATING the primary source for late-breaking changes? Can I count on that to keep me informed of changes? I try to keep up with the mailing list but its not always possible for me to do so. -- swb@grasslake.net Hard work often pays off after time, but laziness always pays off now. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000e01bfecc9$67ec3c20$0102a8c0>