Kernelpath & arplookup.

[Szilveszter Adam]

Hello,

On Fri, Oct 24, 2003 at 09:51:48PM +0200, Peter Terpstra wrote:
> A few weeks ago I installed FreeBSD an I liked it very much, its easier than
> Linux I think. No problems with installing/configuring  X or ssh or Postfix.

I think everybody here is glad to hear that. I hope you will have many
pleasant experinces in the land of FreeBSD :-)

> My questions:
> I compiled a new (lighter) kernel and it works great but I found the path
> mentioned in dmesg or `uname -v' a bit strange, its the place of compile:
> 
> peter at k7:~:0>uname -v
> FreeBSD 5.1-RELEASE #0: Fri Oct 24 01:12:56 CEST 2003
> root at k7.localdomain:/usr/src/sys/i386/compile/MYKERNEL-K6

Yes, your observation is correct.

> Does that mean I cannot remove the old kernel-source?

No, you may be confused a bit here. The "path" mentioned in uname is
just there so that you know when and from what kernel config file you
compiled your kernel. But your kernel always lives in /kernel if you are
on FreeBSD version 4.x, or under /boot/kernel/kernel if you are under
version 5.x. You can delete the kernel source if you do not need it, it
is not required for running. You can also simply use "make clean" in
your kernel compile dir after you know that your new kernel performs as
it should, and thus save the disk space, but conserve the config file
with your settings, so that you can reuse it later.

> I did a `configure MYKERNEL-K6;make depend;make; make install' just as
> mentioned in the on-line FreeBSD handbook.
> Why isn't the path something with /boot/kernel?

It is, if you look at your /var/log/messages, it will even tell it to
you upon each boot.

> arp:
> Frequently I get this message on the first console:
> arplookup 213.84.240.105 failed: host is not on local network
> 
> I searched the inter-net, but I did not found a satisfying answer.
> 213.84.240.105 is hanging on the inter-net, an FreeBSD has a local IP-adres.
> So why this arplookup? What causes this lookup?

This has come up a couple of times lately, but I do not know the answer
off-hand. It may have something to do with your host having more than
one network card and some packets not arriving on the interface FreeBSD
would expect them to.

But really, I am not sure. Maybe someone else can tell.

-- 
Regards:

Szilveszter ADAM
Budapest
Hungary