Re: policy on GPL'd drivers?

2003-05-27 Thread Wilko Bulte
On Tue, May 27, 2003 at 10:23:04AM -0400, Alexander Kabaev wrote: On Tue, 27 May 2003 07:20:17 -0700 Steve Kargl [EMAIL PROTECTED] wrote: On Tue, May 27, 2003 at 08:45:29AM -0400, Alexander Kabaev wrote: On Tue, 27 May 2003 14:36:26 +0200 I and no doubt many others will insist on

Re: policy on GPL'd drivers?

2003-05-27 Thread David Leimbach
On Tuesday, May 27, 2003, at 10:40AM, Alexander Kabaev [EMAIL PROTECTED] wrote: On Tue, 27 May 2003 10:32:42 -0500 David Leimbach [EMAIL PROTECTED] wrote: Ugh... the network driver portion of the nforce drivers is *not* GPL'd but it has a linux only and anti-reverse engineeing clause.

Buildkernel broken

2003-05-27 Thread Krzysztof Parzyszek
Hello, I cvsupped the source this morning and I get: [...] === firewire/firewire cc -O -pipe -march=pentium2 -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -DKLD_MODULE -nostdinc

RE: Buildkernel broken

2003-05-27 Thread Will Saxon
-Original Message- From: Krzysztof Parzyszek [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2003 11:50 AM To: [EMAIL PROTECTED] Subject: Buildkernel broken Hello, I cvsupped the source this morning and I get: [...] === firewire/firewire cc -O -pipe -march=pentium2

Re: policy on GPL'd drivers?

2003-05-27 Thread Alexander Kabaev
On Tue, 27 May 2003 10:49:40 -0500 David Leimbach [EMAIL PROTECTED] wrote: On Tuesday, May 27, 2003, at 10:40AM, Alexander Kabaev [EMAIL PROTECTED] wrote: On Tue, 27 May 2003 10:32:42 -0500 David Leimbach [EMAIL PROTECTED] wrote: Ugh... the network driver portion of the nforce

Re: policy on GPL'd drivers?

2003-05-27 Thread Terry Lambert
Alexander Kabaev wrote: Wilko Bulte [EMAIL PROTECTED] wrote: Yes, see for example the GPL_ed floating point emulator. Aside: I thought the license had been changed on this? I and no doubt many others will insist on keeping GPLed drivers out of the tree. I have no objections for this drivers

Re: policy on GPL'd drivers?

2003-05-27 Thread David Leimbach
. Well, network driver is a special case as it is this weird binary 'kernel' + OS shim combination which is getting popular lately. Have you thought about getting NVidia's permission to link non-GPLed shims with their binary object? I have thought about it... but don't know enough to pursue it

Re: policy on GPL'd drivers?

2003-05-27 Thread David Leimbach
Remember that's it's legal to to distribute seperate binaries, as long as you comply with the GPL for the GPL'ed binary, but it's a violation of clause 6(b) of the GPL to combine them into one binary and distribute them, if you are legally obligated to not give out the source code for the

RE: Buildkernel broken

2003-05-27 Thread David Wolfskill
Date: Tue, 27 May 2003 12:17:18 -0400 From: Will Saxon [EMAIL PROTECTED] I cvsupped the source this morning and I get: [...] === firewire/firewire ... In file included from /usr/src/sys/dev/firewire/fwohci.c:72: @/dev/firewire/fwdma.h:38: redefinition of `bus_dmasync_op_t'

FreeBSD V5.0 and USB to Serial on Toshiba Satellite 1110

2003-05-27 Thread Richard Kaestner
My Notebook (Toshiba Satellite 1110) does not have serial ports, so I wanted to connect a serial adapter. The adapter is recognized (see below), but I can't access any of the serial ports: [EMAIL PROTECTED] minicom minicom: cannot open /dev/ucom0: Device not configured [EMAIL PROTECTED] [EMAIL

Re: policy on GPL'd drivers?

2003-05-27 Thread David O'Brien
On Tue, May 27, 2003 at 07:43:15AM -0500, David Leimbach wrote: However the idea is that all GPL infected stuff be isolated, allowing a fully working kernel without GPL stuff in there. Sounds like a kernel module is the way to go then. Perhaps it could exist in the ports tree instead of the

Re: policy on GPL'd drivers?

2003-05-27 Thread David Leimbach
On Tuesday, May 27, 2003, at 01:40PM, David O'Brien [EMAIL PROTECTED] wrote: On Tue, May 27, 2003 at 07:43:15AM -0500, David Leimbach wrote: However the idea is that all GPL infected stuff be isolated, allowing a fully working kernel without GPL stuff in there. Sounds like a kernel module

Re: policy on GPL'd drivers?

2003-05-27 Thread David Leimbach
On Tuesday, May 27, 2003, at 01:40PM, David O'Brien [EMAIL PROTECTED] wrote: On Tue, May 27, 2003 at 07:43:15AM -0500, David Leimbach wrote: However the idea is that all GPL infected stuff be isolated, allowing a fully working kernel without GPL stuff in there. Sounds like a kernel module

Re: policy on GPL'd drivers?

2003-05-27 Thread David Leimbach
On Tuesday, May 27, 2003, at 01:40PM, David O'Brien [EMAIL PROTECTED] wrote: On Tue, May 27, 2003 at 07:43:15AM -0500, David Leimbach wrote: However the idea is that all GPL infected stuff be isolated, allowing a fully working kernel without GPL stuff in there. Sounds like a kernel module

Re: policy on GPL'd drivers?

2003-05-27 Thread David Leimbach
On Tuesday, May 27, 2003, at 01:40PM, David O'Brien [EMAIL PROTECTED] wrote: On Tue, May 27, 2003 at 07:43:15AM -0500, David Leimbach wrote: However the idea is that all GPL infected stuff be isolated, allowing a fully working kernel without GPL stuff in there. Sounds like a kernel module

Re: policy on GPL'd drivers?

2003-05-27 Thread David Leimbach
On Tuesday, May 27, 2003, at 01:40PM, David O'Brien [EMAIL PROTECTED] wrote: On Tue, May 27, 2003 at 07:43:15AM -0500, David Leimbach wrote: However the idea is that all GPL infected stuff be isolated, allowing a fully working kernel without GPL stuff in there. Sounds like a kernel module

Re: policy on GPL'd drivers?

2003-05-27 Thread David Leimbach
On Tuesday, May 27, 2003, at 01:40PM, David O'Brien [EMAIL PROTECTED] wrote: On Tue, May 27, 2003 at 07:43:15AM -0500, David Leimbach wrote: However the idea is that all GPL infected stuff be isolated, allowing a fully working kernel without GPL stuff in there. Sounds like a kernel module

Re: policy on GPL'd drivers?

2003-05-27 Thread David Leimbach
On Tuesday, May 27, 2003, at 01:40PM, David O'Brien [EMAIL PROTECTED] wrote: On Tue, May 27, 2003 at 07:43:15AM -0500, David Leimbach wrote: However the idea is that all GPL infected stuff be isolated, allowing a fully working kernel without GPL stuff in there. Sounds like a kernel module

Just give me a good smack...

2003-05-27 Thread David Leimbach
I don't know what the hell happened but it won't happen again as I am now vowing to avoid using the Safari, .mac webmail combination. For some reason it kept coming back with no server response and giving me no confirmation that the mail was ever sent via webmail... I just retried a few times

Re: FreeBSD V5.0 and USB to Serial on Toshiba Satellite 1110

2003-05-27 Thread Bernd Walter
On Tue, May 27, 2003 at 08:38:51PM +0200, Richard Kaestner wrote: My Notebook (Toshiba Satellite 1110) does not have serial ports, so I wanted to connect a serial adapter. The adapter is recognized (see below), but I can't access any of the serial ports: [EMAIL PROTECTED] minicom

make buildkernel currently broken in sys/pci/agp_intel.c

2003-05-27 Thread Lukas Ertl
cc -c -O -pipe -march=athlon -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/dev -I/usr/src/sys/contrib/dev/acpica

Re: Timecounter TSC frequency 451024462

2003-05-27 Thread Dag-Erling Smorgrav
Roberto Nunnari [EMAIL PROTECTED] writes: What is interesting is that with 4.7-Stable the faulty timer was handled correctly (or correctly ignored).. That's because 4.7 incorrectly fails to use ACPI to configure the system. As a result, 4.7 is unusable on newer laptops (which no longer support

[Fwd: cvs commit: www/en/releases/5.1R schedule.sgml]

2003-05-27 Thread Scott Long
All, As noted below, the release engineering team has decided to delay the RELENG_5_1 branch by three days in order to allow time for a few more items on the TODO list to be addressed. We apologize for the slip, but feel that it is neccessary to make 5.1 be a good release. The Release

tinderbox currently slightly broken

2003-05-27 Thread Dag-Erling Smorgrav
JFYI, there seems to be a bug in Perl 5.6.1 (which is what's installed on the -CURRENT tinderbox machine) which causes the entire process to bomb when a build fails and it tries to mail out the report. Failure reports (there have been a couple lately) won't be mailed out until this is fixed.

Re: FBSD 5.1b2 Inst. Results on Dell i8500

2003-05-27 Thread Mark Santcroos
On Thu, May 22, 2003 at 11:05:03PM +0200, Mark Santcroos wrote: The same here, that's what I mentioned earlier, that I need to investigate this. Hope to have that fixed before 'de haan kraait' tomorrow morning ;-) Can you send me your whole asl, I'm curious how close it is to mine. Hrm, a bit

Re: FBSD 5.1b2 Inst. Results on Dell i8500

2003-05-27 Thread Stijn Hoop
On Tue, May 27, 2003 at 10:28:32PM +0200, Mark Santcroos wrote: On Thu, May 22, 2003 at 11:05:03PM +0200, Mark Santcroos wrote: The same here, that's what I mentioned earlier, that I need to investigate this. Hope to have that fixed before 'de haan kraait' tomorrow morning ;-) Can you send

HEADSUP: acpi patches in the tree

2003-05-27 Thread Nate Lawson
I have committed changes to nsalloc.c and dsmethod.c. Please cvsup and test ACPI, especially if you had problems with it (that were not present before 0228 was imported). Commit message follows: Fix false AE_NOT_FOUND messages, reported in NetBSD port-i386/20897. NetBSD dsmethod.c rev 1.7 Fix

Re: FBSD 5.1b2 Inst. Results on Dell i8500

2003-05-27 Thread Stijn Hoop
On Tue, May 27, 2003 at 10:55:11PM +0200, Stijn Hoop wrote: On Tue, May 27, 2003 at 10:28:32PM +0200, Mark Santcroos wrote: With a stock kernel and patched dsdt I have a fully working system again. All Dell laptop users with problems might want to give this a look as at least Stijn's

Re: Libthr stable enough for testing

2003-05-27 Thread Craig Boston
On Mon, 2003-05-26 at 17:51, Mike Makonnen wrote: Most major locking work in libthr is finished. I believe it is stable enough now that it can be used for most applications[1]. I would appreciate it if people would try it out and report any bugs. Just installed a freshly cvsup-ped current and

Re: HEADSUP: acpi patches in the tree

2003-05-27 Thread Shin-ichi YOSHIMOTO
Subject: HEADSUP: acpi patches in the tree, On Tue, 27 May 2003 14:06:50 -0700 (PDT), Nate Lawson wrote: I have committed changes to nsalloc.c and dsmethod.c. Please cvsup and test ACPI, especially if you had problems with it (that were not present before 0228 was imported). After this

LOR in vm_object/vm_kern

2003-05-27 Thread Dennis Kristensen
Hi! I just got the below LOR on: FreeBSD lap.snicki.dk 5.1-BETA FreeBSD 5.1-BETA #49: Tue May 27 22:28:31 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LAP i386 sources from about half an hour before the kernel build. lock order reversal 1st 0xc5fd3378 vm object (vm object) @

Re: policy on GPL'd drivers?

2003-05-27 Thread Marcin Dalecki
David Leimbach wrote: On Tuesday, May 27, 2003, at 10:40AM, Alexander Kabaev [EMAIL PROTECTED] wrote: On Tue, 27 May 2003 10:32:42 -0500 David Leimbach [EMAIL PROTECTED] wrote: Ugh... the network driver portion of the nforce drivers is *not* GPL'd but it has a linux only and anti-reverse

Re: ACPI crash

2003-05-27 Thread Andrew Thomson
I feel your pain, my thinkpad doesn't co-operate with 5.1 either... ajt. On Tue, May 27, 2003 at 11:10:26AM -0400, Mikhail Kruk wrote: Hello, I've seen this reported before, but don't see a resolution. Maybe my logs will help solve the problem. When my Gateway laptop boots, I get a couple

Re: LOR in vm_object/vm_kern

2003-05-27 Thread Kris Kennaway
On Wed, May 28, 2003 at 12:21:21AM +0200, Dennis Kristensen wrote: Hi! I just got the below LOR on: FreeBSD lap.snicki.dk 5.1-BETA FreeBSD 5.1-BETA #49: Tue May 27 22:28:31 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LAP i386 sources from about half an hour before the kernel

panic: don't do that, in ugen(4)

2003-05-27 Thread Juli Mallett
Running `quickcam' twice from: http://people.freebsd.org/~jmallett/qce-freebsd.tgz Yields the following loveliness: %%% Script started on Tue May 27 17:59:35 2003 ([EMAIL PROTECTED]:~)1% gdb -k /boot/kernel/kernel vmcore.0 GNU gdb 5.2.1 (FreeBSD) Copyright 2002 Free Software

Latest -Current ACPI issues...

2003-05-27 Thread John Wilson
Hello all. I just finished rebuilding -Current as of about 6:45pm EST and have now noticed the following on boot: [EMAIL PROTECTED]/home/jmw: uname -a FreeBSD neuro.charter.net 5.1-BETA FreeBSD 5.1-BETA #2: Tue May 27 18:39:04 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GEN i386 [EMAIL

Re: policy on GPL'd drivers?

2003-05-27 Thread Chris BeHanna
On Tuesday 27 May 2003 08:43, David Leimbach wrote: On Tuesday, May 27, 2003, at 07:36 AM, Wilko Bulte wrote: On Tue, May 27, 2003 at 02:35:41PM +0200, Stijn Hoop wrote: On Tue, May 27, 2003 at 07:28:29AM -0500, David Leimbach wrote: I have the GPLd source to the nforce drivers for Linux

Re: policy on GPL'd drivers?

2003-05-27 Thread Dag-Erling Smorgrav
David Leimbach [EMAIL PROTECTED] writes: Ugh... the network driver portion of the nforce drivers is *not* GPL'd but it has a linux only and anti-reverse engineeing clause. ...which is null and void in countries with proper IP laws, such as Norway. DES -- Dag-Erling Smorgrav - [EMAIL

Re: HEADSUP: acpi patches in the tree

2003-05-27 Thread Nate Lawson
On Wed, 28 May 2003, Shin-ichi YOSHIMOTO wrote: After this update, I found some error messages like this: acpi0: IntelR AWRDACPI on motherboard ACPI-0438: *** Error: Looking up [\\_OS_] in namespace, AE_NOT_FOUND ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0._INI] (Node

Re: [acpi-jp 2267] Re: HEADSUP: acpi patches in the tree

2003-05-27 Thread Nate Lawson
On Tue, 27 May 2003, Nate Lawson wrote: On Wed, 28 May 2003, Shin-ichi YOSHIMOTO wrote: After this update, I found some error messages like this: acpi0: IntelR AWRDACPI on motherboard ACPI-0438: *** Error: Looking up [\\_OS_] in namespace, AE_NOT_FOUND ACPI-1287: *** Error:

Re: HEADSUP: acpi patches in the tree

2003-05-27 Thread Shin-ichi YOSHIMOTO
Subject: Re: HEADSUP: acpi patches in the tree, Please try the attached patch and see if it changes things for you. OK. I tried youre patch. Error messages is gone :-) Thanks ! acpi0: IntelR AWRDACPI on motherboard pcibios: BIOS version 2.10 Using $PIR table, 7 entries at 0xc00fdee0 acpi0:

Re: panic: don't do that, in ugen(4)

2003-05-27 Thread Jay Cornwall
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 28 May 2003 00:06 am, Juli Mallett wrote: Running `quickcam' twice from: http://people.freebsd.org/~jmallett/qce-freebsd.tgz Yields the following loveliness: [..] This is the same issue another person (Mark Blackman) is

Re: [acpi-jp 2269] Re: HEADSUP: acpi patches in the tree

2003-05-27 Thread Nate Lawson
On Wed, 28 May 2003, Shin-ichi YOSHIMOTO wrote: Subject: Re: HEADSUP: acpi patches in the tree, Please try the attached patch and see if it changes things for you. OK. I tried youre patch. Error messages is gone :-) Thanks ! Please respond to my other email as well. Without that patch, do

Re: [acpi-jp 2269] Re: HEADSUP: acpi patches in the tree

2003-05-27 Thread Shin-ichi YOSHIMOTO
Subject: Re: [acpi-jp 2269] Re: HEADSUP: acpi patches in the tree, On Tue, 27 May 2003 17:56:47 -0700 (PDT), Nate Lawson wrote: Please respond to my other email as well. Without that patch, do you have problems or is it just the error message? Oh, sorry. Without that patch, no problems. It's

Re: passwd NIS+ YP compat mode

2003-05-27 Thread TOMITA Yoshinori
On Tue, 27 May 2003 21:46:04 +0900, TOMITA Yoshinori [EMAIL PROTECTED] said: T Hello all, T After cvsup-ed today 2003-5-27 and make buildworld and so on, T NIS passwd database are completely ignored. T But NIS group database seems to be used as usual. T Out NIS server is actually NIS+ in YP

Re: policy on GPL'd drivers?

2003-05-27 Thread Daniel O'Connor
On Tue, 27 May 2003 22:13, David Leimbach wrote: However the idea is that all GPL infected stuff be isolated, allowing a fully working kernel without GPL stuff in there. Sounds like a kernel module is the way to go then. Perhaps it could exist in the ports tree instead of the mainline

Re: policy on GPL'd drivers?

2003-05-27 Thread Q
I have been burnt by this in the past also. I think that it would be useful if you could allow kernel modules to be bound to a particular kernel version/date/whatever, and have external modules refuse to load and/or complain if the kernel is upgraded. This should prevent unnecessary kernel panics

Re: policy on GPL'd drivers?

2003-05-27 Thread Scott Long
Q wrote: I have been burnt by this in the past also. I think that it would be useful if you could allow kernel modules to be bound to a particular kernel version/date/whatever, and have external modules refuse to load and/or complain if the kernel is upgraded. This should prevent unnecessary

Re: policy on GPL'd drivers?

2003-05-27 Thread Q
Don't overreact. I'm not suggesting taking the linux approach of versioning every module. But rather allowing the loader or a module (most likely a 3rd part or from a port) the ability to make a decision based on some internal revision/date based version as to whether it is safe to proceed to

Re: policy on GPL'd drivers?

2003-05-27 Thread Scott Long
Q wrote: Don't overreact. Heh. I live this hell every day with Linux in my day job. I'm not suggesting taking the linux approach of versioning every module. But rather allowing the loader or a module (most likely a 3rd part or from a port) the ability to make a decision based on some internal

Re: policy on GPL'd drivers?

2003-05-27 Thread Michael Edenfield
* Scott Long [EMAIL PROTECTED] [030527 23:51]: I am thinking of ports like rtc, ltmdm or Vmware here.. where it is not uncommon that they require reinstalling after an upgrade. I have experienced kernel panics on several occasions from out of date vmware kernel modules. I'm really of the

Re: policy on GPL'd drivers?

2003-05-27 Thread Daniel O'Connor
On Wed, 28 May 2003 13:17, Scott Long wrote: I am thinking of ports like rtc, ltmdm or Vmware here.. where it is not uncommon that they require reinstalling after an upgrade. I have experienced kernel panics on several occasions from out of date vmware kernel modules. I'm really of the

Kernel module inconsistency was policy on GPL'd drivers?

2003-05-27 Thread Q
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

Re: Kernel module inconsistency was policy on GPL'd drivers?

2003-05-27 Thread Scott Long
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

Re: 5.1-BETA2 FAILURE on IBM A30p Thinkpad

2003-05-27 Thread Jesse D. Guardiani
Kevin Oberman [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] From: Jesse D. Guardiani [EMAIL PROTECTED] Date: Sat, 24 May 2003 02:12:32 -0400 Sender: [EMAIL PROTECTED] Andre Guibert de Bruet [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] [...] Does you r

Re: Kernel module inconsistency was policy on GPL'd drivers?

2003-05-27 Thread Alexey Neyman
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

Re: policy on GPL'd drivers?

2003-05-27 Thread M. Warner Losh
In message: [EMAIL PROTECTED] Daniel O'Connor [EMAIL PROTECTED] writes: : The only downside is that there are no hooks into the build process so you : have to be VERY careful when you update your kernel, or you get panics :( This is true. I'd thought that MODULES_OVERRIDE would

Re: policy on GPL'd drivers?

2003-05-27 Thread M. Warner Losh
In message: [EMAIL PROTECTED] Daniel O'Connor [EMAIL PROTECTED] writes: : Maybe the kernel build stuff can look in /usr/local/src/sys/modules for things : to build or something.. YUCK! Warner ___ [EMAIL PROTECTED] mailing list

Re: HEADSUP: acpi patches in the tree

2003-05-27 Thread Anish Mistry
On Tuesday 27 May 2003 07:58 pm, Nate Lawson wrote: On Wed, 28 May 2003, Shin-ichi YOSHIMOTO wrote: After this update, I found some error messages like this: acpi0: IntelR AWRDACPI on motherboard ACPI-0438: *** Error: Looking up [\\_OS_] in namespace, AE_NOT_FOUND ACPI-1287: ***

Re: Kernel module inconsistency was policy on GPL'd drivers?

2003-05-27 Thread M. Warner Losh
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

Re: policy on GPL'd drivers?

2003-05-27 Thread Daniel O'Connor
On Wed, 28 May 2003 14:41, M. Warner Losh wrote: In message: [EMAIL PROTECTED] Daniel O'Connor [EMAIL PROTECTED] writes: : Maybe the kernel build stuff can look in /usr/local/src/sys/modules for : things to build or something.. YUCK! *WHY?* I have asked this before BTW, and I

Re: Kernel module inconsistency was policy on GPL'd drivers?

2003-05-27 Thread Q
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

Re: policy on GPL'd drivers?

2003-05-27 Thread Terry Lambert
David Leimbach wrote: IANAL but I think the GPL has provisions for binaries that contain code that is not necessarily dependant but merely aggregated into one package. Linking is not mere agregation. If you can cite the section of the GPL you are talking about, it would be useful (this is a

Re: policy on GPL'd drivers?

2003-05-27 Thread Daniel O'Connor
On Wed, 28 May 2003 14:22, M. Warner Losh wrote: In message: [EMAIL PROTECTED] Daniel O'Connor [EMAIL PROTECTED] writes: : The only downside is that there are no hooks into the build process so : you have to be VERY careful when you update your kernel, or you get : panics :(

Re: policy on GPL'd drivers?

2003-05-27 Thread Q
By doing that aren't you assuming that the kernel will be installed on the machine that built it, and not potentially somewhere else? What about sysinstall upgrades that don't require src? Seeya...Q On Wed, 2003-05-28 at 15:17, Daniel O'Connor wrote: On Wed, 28 May 2003 14:41, M. Warner Losh