On Wed, Aug 10, 2011 at 4:13 PM, Ray Rashif wrote:
> On 10 August 2011 21:46, Tom Gundersen wrote:
>> On Wed, Aug 10, 2011 at 3:29 PM, Ray Rashif wrote:
>>> I'd just remove these from the kernel itself :) People can always
>>> modprobe
>>
>> What do you mean? If we remove the modules from the ke
On 10 August 2011 21:46, Tom Gundersen wrote:
> On Wed, Aug 10, 2011 at 3:29 PM, Ray Rashif wrote:
>> I'd just remove these from the kernel itself :) People can always
>> modprobe
>
> What do you mean? If we remove the modules from the kernel package,
> then people would have to recompile them ma
On Wed, Aug 10, 2011 at 3:29 PM, Ray Rashif wrote:
> I'd just remove these from the kernel itself :) People can always
> modprobe
What do you mean? If we remove the modules from the kernel package,
then people would have to recompile them manually to get them...
-t
On 10 August 2011 18:53, Tom Gundersen wrote:
> On Wed, Aug 10, 2011 at 12:13 PM, Pierre Schmitz wrote:
>> I just wondered why I had ipx and appletalk modules loaded. After some
>> tests I figured out that simply running ifconfig triggers the kernel to
>> load them. This does not happen with an o
On Wed, Aug 10, 2011 at 12:13 PM, Pierre Schmitz wrote:
> I just wondered why I had ipx and appletalk modules loaded. After some
> tests I figured out that simply running ifconfig triggers the kernel to
> load them. This does not happen with an older kernel; e.g. our lts
> package. Any ideas about
Hi,
I just wondered why I had ipx and appletalk modules loaded. After some
tests I figured out that simply running ifconfig triggers the kernel to
load them. This does not happen with an older kernel; e.g. our lts
package. Any ideas about that? It might not break anything but it is
strange anyway.
6 matches
Mail list logo
