Hello from the Eighth Doctor
Since my normal developer's box that runs Slackware 10.0, will also be visited by
customers, via SSH, I decided to add quotas. I did the one for the first user, and
then for root.

Rebooted, and during the process the system installed the qouta module. It
complained insisting that the module's installation would compromise the kernel, it
would "taint it", it stated. After the sequence had completed, and it created the quota
settings for the root user, I checked the list of modules.

Under "tainted", there was a blank in the line for the quota module. Now this is the
same module that was built along with everything else the last time I built a new
kernel for the system. Last night in fact.

To create the quotas, I followed the instructions included in the rc.M file. I can't see
why the kernel module loader would complain, especially since the module source
code came from the same code base, that the kernel source code itself contains.
Basically I am confused.

Also I did look at the entries discussing the problem of "tainting", with regards to
modules and the GPL the first time it came up and made a nuisance of itself. It made
no mention of my problem then, which happened to be the same as before.
-------
Gregg drwho8 atsign att dot net

The Eighth Doctor wrote:
> Hello from the Eighth Doctor
> Since my normal developer's box that runs Slackware 10.0, will also be visited by
> customers, via SSH, I decided to add quotas. I did the one for the first user, and
> then for root.
>
> Rebooted, and during the process the system installed the qouta module. It
> complained insisting that the module's installation would compromise the kernel, it
> would "taint it", it stated. After the sequence had completed, and it created the quota
> settings for the root user, I checked the list of modules.
>
> Under "tainted", there was a blank in the line for the quota module. Now this is the
> same module that was built along with everything else the last time I built a new
> kernel for the system. Last night in fact.
>
> To create the quotas, I followed the instructions included in the rc.M file. I can't see
> why the kernel module loader would complain, especially since the module source
> code came from the same code base, that the kernel source code itself contains.
> Basically I am confused.
>
> Also I did look at the entries discussing the problem of "tainting", with regards to
> modules and the GPL the first time it came up and made a nuisance of itself. It made
> no mention of my problem then, which happened to be the same as before.
> -------
> Gregg drwho8 atsign att dot net
>

You don't have to worry, the taint nag is 'political engineering' not
software engineering...

In article <10vbi2jhp9050f5@corp.supernews.com>, csoren@isd.net says...
>
>The Eighth Doctor wrote:
>> Hello from the Eighth Doctor
>> Since my normal developer's box that runs Slackware 10.0, will also be visited
by
>> customers, via SSH, I decided to add quotas. I did the one for the first user, and
>> then for root.
>>
>> Rebooted, and during the process the system installed the qouta module. It
>> complained insisting that the module's installation would compromise the kernel,
it
>> would "taint it", it stated. After the sequence had completed, and it created the
quota
>> settings for the root user, I checked the list of modules.
>>
>> Under "tainted", there was a blank in the line for the quota module. Now this is
the
>> same module that was built along with everything else the last time I built a new
>> kernel for the system. Last night in fact.
>>
>> To create the quotas, I followed the instructions included in the rc.M file. I can't
see
>> why the kernel module loader would complain, especially since the module
source
>> code came from the same code base, that the kernel source code itself contains.
>> Basically I am confused.
>>
>> Also I did look at the entries discussing the problem of "tainting", with regards
to
>> modules and the GPL the first time it came up and made a nuisance of itself. It
made
>> no mention of my problem then, which happened to be the same as before.
>> -------
>> Gregg drwho8 atsign att dot net
>>
>
>You don't have to worry, the taint nag is 'political engineering' not
>software engineering...
Hello from the Eighth Doctor
Oh.
I'd like to send the <Expletive deleted!> to Kessel, or Hoth, for allowing that to
happen. Oh I'm not worried, but it is annoying.
--
Gregg drwho8 atsign att dot net