You could achieve the same result without breaking a bunch of cardinal
rules by taking an MD5 hash of the kernel when the port is first
installed, then modify the rc.d script that loads the module to only run
if that MD5 hash matches the current kernel. If a mismatch occurs it
should spew out an
Q wrote:
You could achieve the same result without breaking a bunch of cardinal
rules by taking an MD5 hash of the kernel when the port is first
installed, then modify the rc.d script that loads the module to only run
if that MD5 hash matches the current kernel. If a mismatch occurs it
should spew
Hi, there!
On Wednesday 28 May 2003 08:25, Scott Long wrote:
SL Don't forget that some modules need to be loaded at boot time. Also, if
SL I recompile my kernel to trim down an unused driver, the MD5 will
SL change.
It'll change even if you do not mess with the configuration at all: the
In message: [EMAIL PROTECTED]
Alexey Neyman [EMAIL PROTECTED] writes:
: I'd rather see something like
: PORTS_KMODS=audio/aureal-kmod xxx/yyy
: knob in the /etc/make.conf
Funny, I had similar thoughts before seeing your patch. Here's my
latest patch. You could put it in
Yes, I'm aware of the implications.. I was merely proposing a ports
legal way of achieving the same result that Mike put forward without
stuffing a foreign module into /boot. Although, like I said, this is not
really a long term solution to the problem.
All the port's originating kernel modules I
