Richard Braakman wrote:
> We usually allow some time for license issues to be resolved. In the
> extreme case of KDE it was more than a year :)
You forget: KDE was removed from the archive during that time.
--
see shy jo
Greg KH <[EMAIL PROTECTED]> writes:
>Hm, I understand that you have a copyright claim on the keyspan.c file,
>but I don't see how that transfers to the keyspan_usa*_fw.h files?
I do not believe the keyspan_usa*_fw.h files are illegal by
themselves. However, compiling them, keyspan.c and 4
On Fri, Apr 27, 2001 at 07:37:10PM -0300, Carlos Laviola wrote:
> I currently, and intentionally, have no copyright over the fortunes
> collection. I encourage everyone to copy it and use it freely, and as
> far as your system goes, you're most certainly welcome to it.
That's all we need. A full
Greg KH <[EMAIL PROTECTED]>:
> Ok, I agree. Then you need to make sure all of the firmware images in
> the kernel tree are removed from the Debian version of the kernel.
Or you could just put the kernel into non-free. It's not really an
essential part of Debian, now that there's Debian GNU/Hurd
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Like I said before (see
> http://lists.debian.org/debian-devel-0104/msg01443.html), I intend to
> package Wayne Aiken's atheist fortunes available at his site
> (http://www4.ncsu.edu/~aiken/). This is the response I've got from him. I'm
> waiti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Like I said before (see
http://lists.debian.org/debian-devel-0104/msg01443.html), I intend to
package Wayne Aiken's atheist fortunes available at his site
(http://www4.ncsu.edu/~aiken/). This is the response I've got from him. I'm
waiting for advice (i
On Thu, Apr 26, 2001 at 12:33:09AM -0700, Aaron Lehmann wrote:
>
> GPL'd or not, I'm sorry Greg but the firmware is non-free software.
>
> 2. Source Code
> The program must include source code, and must allow
> distribution
> in source code as well as compiled
On Thu, Apr 26, 2001 at 04:31:12AM -0700, Adam J. Richter wrote:
> You told me that you would to be convinced only by a lawyer,
> Linus Torvalds or Alan Cox. I took that as an indication that you
> did not want me to involve you in discussions with anyone else
> on this issue.
I also assume
On Thu, Apr 26, 2001 at 01:34:06AM -0600, Walter Landry wrote:
> > - the file keyspan_pda_fw.h is under the GPL. Is is a compiled
> > image of the keyspan_pda.S in the same directory
> > (drivers/usb/serial in the kernel tree.) This is a wonderful
> > achievement by Brian Wa
On Fri, Apr 27, 2001 at 04:57:20PM +1000, Hugh Blemings wrote:
> On 27-Apr-2001 Thomas Bushnell, BSG wrote:
>
> > I agree completely that the patch should be integrated ASAP.
>
> I'm sorry, I beg to differ on this for 2.4.x kernels as it's quite an major
> change. For 2.5.x certainly, but as mai
Hello,
I would like to package a set of programs, that are linked against a
propritary library. The author has signed a NDA in order to develop the
library (see below) and is not allowed to publish the source. Though, he
placed the frontend tools unto GPL, and is willing to change the license
to a
> If there were no reason to ever want to change it, then they wouldn't have
made it
> uploadable in the first place
True. Although I don't remember the last time I had the urge to tweak the
BIOS of some hardware device. Not only am I likely to break it (certainly in
the case of devices with flash
Hi,
On 27-Apr-2001 Thomas Bushnell, BSG wrote:
> Walter Landry <[EMAIL PROTECTED]> writes:
> [snip]
>
> Most importantly, the fact is that the code in question cannot be
> legally copied, and distributing it as part of Debian is contrary to
> our principles and our guidelines.
As per my earlier e
Walter Landry <[EMAIL PROTECTED]> writes:
> I also don't see a (legal) problem with GPL programs that just move
> unfree data around. Otherwise cp would have serious use restrictions.
> However, cp doesn't contain within itself the unfree data. The
> keyspan drivers do. If Adam's patch is appli
> [EMAIL PROTECTED] (Thomas Bushnell, BSG) writes:
>
> > "mere aggregation" does not include linking. "mere aggregation"
> > implies *just* aggregation, and not combination. It's what you do
> > when you make a CD with a bunch of different programs.
>
> If this is the problem we have a lot ot
On Thu, Apr 26, 2001 at 01:05:55PM +0300, Richard Braakman wrote:
> > rather than whinge about the licenses and turn away vendors who are trying
> > to be useful, why not solve the problem? and no, forcing hardware vendors to
> > provide open source code is not the answer - most will probably just
"Sam Johnston" <[EMAIL PROTECTED]> writes:
> rather than whinge about the licenses and turn away vendors who are trying
> to be useful, why not solve the problem? and no, forcing hardware vendors to
> provide open source code is not the answer - most will probably just
> withdraw support, saving i
"Sam Johnston" <[EMAIL PROTECTED]> writes:
> certainly... host adapters, hard drives, motherboards, video cards, storage
> devices, digital cameras, etc. all have firmware that most likely contains a
> lot of juicy information about the hardware that vendors may want to keep
> secret. and we shoul
Hugh Blemings <[EMAIL PROTECTED]> writes:
> I'm a bit concerned that Keyspan are being painted as the "bad guys" here -
> for better or worse (seemingly the latter :) they were relying on me for
> guidance as to how best to walk the line between helping out and protecting
> their interests.
Wel
Sam Hartman <[EMAIL PROTECTED]> writes:
> I have to agree with you and disagree with Thomas. If the code is
> simply bits that will be spewed out to some device, that seems much
> more like a combination than linking.
I'm sorry; I think I insufficiently understood the case, but now I've
got it b
20 matches
Mail list logo
