Date: Fri, 24 Oct 2003 21:14:02 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Peter Terpstra <peter@k6.xs4all.nl> Cc: freebsd-doc@freebsd.org Subject: Re: Kernelpath & arplookup. Message-ID: <20031024201402.GA54905@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <Pine.LNX.4.58.0310242110150.2157@k6.xs4all.nl> References: <Pine.LNX.4.58.0310242110150.2157@k6.xs4all.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
--azLHFNyN32YCQGCU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Oct 24, 2003 at 09:51:48PM +0200, Peter Terpstra wrote:
> 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:
>=20
> peter@k7:~:0>uname -v
> FreeBSD 5.1-RELEASE #0: Fri Oct 24 01:12:56 CEST 2003
> root@k7.localdomain:/usr/src/sys/i386/compile/MYKERNEL-K6
>=20
> Does that mean I cannot remove the old kernel-source?
> 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?
As you say, that isn't the location in the file system where the
kernel is installed: it's where the kernel was compiled. To find
where the kernel was booted from try:
% sysctl kern.bootfile
You can certainly clear out your kernel compile directory without
affecting the operation of the system.
While the way you compiled the kernel certainly works, it's actually
the 'old' way. Nowadays the commonest way to build and install a
kernel is:
# cd /usr/src
# make buildkernel KERNCONF=3DMYKERNEL-K6
# make installkernel KERNCONF=3DMYKERNEL-K6
In thins case, you'll find that the kernel compile path is
/usr/obj/usr/src/sys/MYKERNEL-K6
As to quite why it's like this I'm not sure. I think it's one of
those things that has always been that way, and because it's been like
that for so long no one is going to change it now.
=20
> arp:
> Frequently I get this message on the first console:
> arplookup 213.84.240.105 failed: host is not on local network
Yes. This isn't necessarily an error. All it means is that there is
a host on the same physical network segment but with an IP number that
belongs to a different network than your machine. If this isn't a
misconfiguration then you can suppress the error message by:
# sysctl net.link.ether.inet.log_arp_wrong_iface 0
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
--azLHFNyN32YCQGCU
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQE/mYgKdtESqEQa7a0RAnR1AKCXu9chSCRYD3fewYMenZp0dZ5C0wCeJB6P
IL+es7kkdJ6m50SISFod/FU=
=Ufq+
-----END PGP SIGNATURE-----
--azLHFNyN32YCQGCU--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031024201402.GA54905>