From: David Masover <ninja@slaphack.com>
To: Rudy Zijlstra <rudy@edsons.demon.nl>
Cc: Mark Junker <mjscod@gmx.de>, Hans Reiser <reiser@namesys.com>,
reiserfs-list@namesys.com
Subject: Re: where are reiser4 sources
Date: Thu, 24 Feb 2005 22:34:33 -0600 [thread overview]
Message-ID: <421EAAD9.5050907@slaphack.com> (raw)
In-Reply-To: <421DE8C8.9030107@edsons.demon.nl>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Rudy Zijlstra wrote:
| Mark Junker wrote:
|
|> Rudy Zijlstra schrieb:
|>
|>>
|> This sounds to me that I can only use GPL'd software with other GPL'd
|> software but this cannot be true because you're allowed to use it with
|> libraries with other licenses too as long as they don't contain
|> conflicts ...
|>
| Take a look at the difference between GPL and LGPL. LGPL allows dynamic
| linking against non GPL SW, GPL does not. Both allow usage of the
| interfaces *without* linking, either dynamic or static. Neither allow
| static linking to non (L)GPL.
Come to think of it, isn't that kind of how nvidia can put a binary
driver in Linux?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iQIVAwUBQh6q2HgHNmZLgCUhAQLPQhAAkbyHLLoW/WHsH6N5aEIZ7EPNz6YC4mme
Uli/UOzSStwjwcB5B071IC8hk5OQnjSbBbpv/IGVmoio2/f4ritCavcP3aJzi00A
JD744eAUDs4CJBnAAkU3VylY82fkSqz7Wp5PprTaJBPx6gX3lbWqxeeq3sX/bDk0
l9TxczUh7aM+AR9CRrk8upik/XFUaekokAe58ZmeEXQ8eC9hvFfkJUg9iDsVBi0a
ZXf1ne5yukrBetfN10+xE9sIvFRHnnX0u156RmMx+nNwAtdo1JEhhJl+/s94MbIy
tAwSC0NiVkVqL1PTiCEnIx4luJrkOreFNnnXCKUzsQNA9fX7WhgmJ7UBW+0TUP9L
f2sga67VpnJjgb5M1mscfCS5VrwUzVy/i+qeHZlGJt2XXLLJXKjavyaiB2FIYTKB
iIiT+OYQNj2MDxerQ+ar9xC8xhPwzvlbrIBa/mRUjcuoP0gOKXIpAN3MdUMVio4t
qvIswayQheyZ1FBN0VFbuG5LVR721WfRc6bDdZXR8qGaagiQAxI6XBpo6TK3CcwI
T8UBqKldXSs7I+nGw4ozzaWLSYSD6T7tAhctv2vc5NiC5LAi5lTWHHFJcA1MyyrP
fwcs18QCy92+I+fTxathWe63kOW1xCooppNTPyPeQg6wNyOhe4oTDhG47TBLLYo9
XwGMXxFE20M=
=B41A
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-02-25 4:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 16:16 where are reiser4 sources Mark Junker
2005-02-21 17:10 ` Sander Sweers
2005-02-21 17:59 ` Mark Junker
2005-02-22 2:08 ` David Masover
2005-02-22 15:20 ` Mark Junker
2005-02-22 18:41 ` Hans Reiser
2005-02-22 18:51 ` Valdis.Kletnieks
2005-02-23 17:10 ` Hans Reiser
2005-02-23 20:56 ` Mounting ReiserFS 3.6 RO increments journal count ? Linux Tard
2005-02-22 18:54 ` where are reiser4 sources Mark Junker
2005-02-23 17:19 ` Hans Reiser
2005-02-23 18:14 ` Mark Junker
2005-02-23 18:39 ` Rudy Zijlstra
2005-02-23 18:53 ` Hans Reiser
2005-02-23 21:06 ` Mark Junker
2005-02-23 21:03 ` Mark Junker
2005-02-24 14:46 ` Rudy Zijlstra
2005-02-25 4:34 ` David Masover [this message]
2005-02-25 8:20 ` Chester R. Hosey
2005-02-23 21:16 ` Mark Junker
2005-02-28 23:41 ` Hans Reiser
2005-02-28 21:44 ` Valdis.Kletnieks
2005-02-23 22:00 ` Jonathan Briggs
2005-02-24 0:58 ` David Masover
2005-02-22 18:56 ` Lehmann
2005-02-22 17:49 ` Hans Reiser
2005-02-22 18:29 ` Mark Junker
2005-03-02 6:29 ` Alex Zarochentsev
-- strict thread matches above, loose matches on Subject: below --
2005-03-01 16:52 Burnes, James
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=421EAAD9.5050907@slaphack.com \
--to=ninja@slaphack.com \
--cc=mjscod@gmx.de \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=rudy@edsons.demon.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.