From: Aleksandar Milivojevic <amilivojevic@pbl.ca>
To: "netfilter@lists.netfilter.org" <netfilter@lists.netfilter.org>
Subject: Re: linux-2.6.9-rc1 compilation and configuration issue (fwd)
Date: Wed, 08 Sep 2004 14:00:27 -0500 [thread overview]
Message-ID: <413F56CB.2090509@pbl.ca> (raw)
In-Reply-To: <1094667545.11117.30.camel@nostromo.bgsecm.com>
Jose Maria Lopez wrote:
[snip]
> there are things simply impossible.
Impossible? There's no such thing ;-)
> I don't see the difference with Solaris. If you want to upgrade your
> Solaris you have to apply a lot of upgrades, also to the kernel. That's
> the impression I have from the little contact I had with Solaris.
Not really. Solaris (well, SunOS actually) has "disadvantage" of being
closed-source. So Sun had to publish API and document data structures
garanteed not to change in set period of time (as defined in Solaris
device driver development guides). That allows for a third party to
provide loadable kernel module that works with current version of
Solaris kernel (both generic and patched), and possibly future versions
of Solaris kernel (up to some point). Of course, if developer doesn't
wonder into the undocumented land ;-) More than once I used kernel
module compiled for previous version of Solaris (one was driver for
Sun's unfortunate BigMac ethernet card, don't remember exatly what the
others were).
If there was such a thing in Linux kernel, bringing some of the new
features might be a bit slower and harder task for core Linux developers
(you can't just change that function call, or data structure), but on
the other hand some of the "impossible" to implement features would
become "possible"...
Becoming way off topic, anyhow...
--
Aleksandar Milivojevic <amilivojevic@pbl.ca> Pollard Banknote Limited
Systems Administrator 1499 Buffalo Place
Tel: (204) 474-2323 ext 276 Winnipeg, MB R3T 1L7
next prev parent reply other threads:[~2004-09-08 19:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-07 23:33 linux-2.6.9-rc1 compilation and configuration issue (fwd) James B. Hiller
2004-09-08 0:27 ` Jason Opperisano
2004-09-08 1:55 ` James B. Hiller
2004-09-08 14:10 ` Aleksandar Milivojevic
2004-09-08 17:39 ` Jose Maria Lopez
2004-09-08 18:23 ` Aleksandar Milivojevic
2004-09-08 18:19 ` Jose Maria Lopez
2004-09-08 19:00 ` Aleksandar Milivojevic [this message]
2004-09-08 19:37 ` Jose Maria Lopez
2004-09-08 20:46 ` Aleksandar Milivojevic
2004-09-08 20:41 ` James B. Hiller
2004-09-08 19:26 ` Cedric Blancher
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=413F56CB.2090509@pbl.ca \
--to=amilivojevic@pbl.ca \
--cc=netfilter@lists.netfilter.org \
/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.