On Fri, 17 Mar 2000, Tom Legg wrote:
> I've reproduced the missing crypto bug when compiling a kernel.....
> I think I've isolated it. If you try to build a custom kernel with
> IPSEC options the make will bomb. This will happen even after the
> current UPDATING instructions are complete.
You do have the src-sys-crypto sources, right? /usr/src/sys/crypto/?
> But... if you do a buildworld and installworld with existing source
> after getting 4.0 running, then you can implement IPSEC in the kernel.
Hmm..I think you'd have to provide a build log showing where it failed
without this step - I don't know why it would be the case.
> Admittedly I had built a custom kernel as well as a generic kernel
> when testing 'make buildkernel'. So I had /kernel /kernel.old
> /kernel.GENERIC /kernel.prev and /CUSTOMKERNEL taking up all of the
> disk space, but hopefully a userfriendly upgrade document might
> mention this condition, just in case someone wades in to the deep
> end only to find themselves buried deep in the ****
Surely it's fairly obvious if you get an out of disk space message what
the problem and fix is?
Kris
----
In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe <[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
