just wanna jump in while it's hot...
I work for a commercial company, and I did what I could to convince
people that *BSD is the way, and we're happily using FreeBSD.
now, we modiy the kernel sources, and this is a problem since this changes
the way people build the kernel.
what we did is provide procedures to modify the kernel config file (GENERIC
for example), conf/files and so, in order to build the kernel.
While this is ok, it doesn't sound perfect to me. I'd love it if thrid party
modifications were intended in the kernel sources. I'm ready to do the work.
mainly, I'd propose some patches to config so that thrid party
additions/modifications
are made easier [the real problem is that when many companies modify the
kernel.
If they all do it as we do, then it's impossible. but if it's provided by
the system, then
it's easier].
regards,
mouss
At 21:45 27/12/00 +0200, Taavi Talvik wrote:
>On Wed, 27 Dec 2000, someone on freebsd-hackers wrote:
>
> > > They dont want your stinking binary contributions. Get used to it.
> >
> > Not suprisingly you're both wrong. Many binary-only ports exist
> > in the FreeBSD ports tree.
>
>World is not black and white.
>
>There are binary ports (for example netscape). But there are no well
>defined procedures for including binary device drivers with FreeBSD.
>Even building modules outside /usr/src/sys/modules is not easy task.
>What about asking for additional driver modules on fresh install?
>
>Lack of well defined procedures for inclusion of binary only drivers is
>definitely our shortcoming. We are moving to right direction (kernel
>modules etc.), but we are not there yet.
>
>There are reasons for binary only drivers. For example - ADSL, it is
>coming more common, but supply chain is just too long. Card manufacturers
>are helpful, they provide programming information, but they are not free,
>they just can't ignore chipset suppliers (who are not ready for releasing
>some firmware yet).
>
>best regards,
>taavi
>
>
>
>To Unsubscribe: send mail to [EMAIL PROTECTED]
>with "unsubscribe freebsd-hackers" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
