On Tue, 19 Feb 2002, Giacomo Catenazzi wrote:
> I agree, but we know some strange 'behaviour' of MS.
> They have a lot of lawers, they can make us a lot of trouble.
> (You will notice that there are no copyright statment on that file,
> only the name of authors).
>
> Remember the RMS (a flame
Daniel Phillips wrote:
>>. A Microsoft engineer wrote scripts/Configure. For three years, I have
>> lived in fear that Microsoft would notice this fact and use it to attack
>> Linux through public relations channels or legal means. They haven't yet,
>> so I have been wrong so far.
>>
>
>
> . A Microsoft engineer wrote scripts/Configure. For three years, I have
> lived in fear that Microsoft would notice this fact and use it to attack
> Linux through public relations channels or legal means. They haven't yet,
> so I have been wrong so far.
Teehee. I don't think you have a
> Personal I would like to see kbuild-2.5 included ASAP. Among other stuff
> I like the compressed output during compilation.
So do I. I like the clean design of kbuild-2.5 and i'm more than fine with
the overall speed.
I vote for inclusion in 2.5. As small as my vote can be co
[[EMAIL PROTECTED]]
> I want to know where all i have to make entries in the source code of
> linux so that while building the Linux kernel i can include my device
> driver in the kernel.
There are files in many of the directories of the kernel called
'Config.in'. Find an appropriate one and ad
[EMAIL PROTECTED] wrote:
> Hello All,
>
> I want to know where all i have to make entries in the source code of
> linux so that while building the Linux kernel i can include my device
> driver in the kernel.
>
> 1. Where I have to write Makefile so that make utility can know to
> execute t
Hello All,
I want to know where all i have to make entries in the source code of
linux so that while building the Linux kernel i can include my device
driver in the kernel.
1. Where I have to write Makefile so that make utility can know to
execute this Makefile. This Makefile is required for
