Date: Fri, 13 Oct 2006 11:09:20 +0100 From: Florent Thoumie <flz@FreeBSD.org> To: martinko <gamato@pobox.sk> Cc: freebsd-ports@freebsd.org Subject: Re: man hier? -- FreeBSD Port: sysutils/fusefs-kmod Message-ID: <1160734160.81679.8.camel@mayday.esat.net> In-Reply-To: <452E6E3C.7070604@pobox.sk> References: <452E6E3C.7070604@pobox.sk>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-qCTF8yQE2auPvPjflIbi Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2006-10-12 at 18:33 +0200, martinko wrote: > Hello, >=20 > I wonder what is the reasoning behind fusefs-kmod port way of dealing > with kernel module(s). > I remember iwi ports putting their modules into /boot/modules and then > one only had to edit /boot/loader.conf[.local] > Now fusefs-kmod creates new directory /usr/local/modules where it puts > its module, then it optionally edit /etc/sysctl.conf to modify > kern.module_path and rc.conf to run /usr/local/etc/rc.d/fusefs script. > Is all of this really necessary and why please ?? It makes the port/package PREFIX-clean. I could have done that for intel firmware ports but I thought it would be too painful for the end-user. --=20 Florent Thoumie flz@FreeBSD.org FreeBSD Committer --=-qCTF8yQE2auPvPjflIbi Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQBFL2XQMxEkbVFH3PQRAsOBAJ93RQiPUNb8ylfkk2mMKX0tdR5DmQCfUuGl QMMLHog8YZwlq1OuWsjIHPY= =6619 -----END PGP SIGNATURE----- --=-qCTF8yQE2auPvPjflIbi--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1160734160.81679.8.camel>