From: devzero@web.de
To: ewanm89@googlemail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: distro specific kernels vs vanilla kernel and how to compare
Date: Sat, 17 Nov 2007 11:35:16 +0100 [thread overview]
Message-ID: <2090717360@web.de> (raw)
>I would also like to see something like this
nice to get positive feedback, thanks :)
>as some work I'm doing on
>working some funny networking (unfortunately IT department don't have
>common sense) across multiple distros.
so if _you_ have common sense, it`s up to you alone to make your own life easier and you should try hard to change their mind.
how can you make sure your code is good and stable if other`s don`t review it ?
why should you constantly work on porting your code to the next kernel release ?
even worse, you need to port it to different vendor specific kernels. that`s a real waste of time...
please try changing their minds and if you need some help/arguments i`m sure there are people who can help you freeing the source ! ;)
maybe you will find some at http://www.kroah.com/log/linux/ols_2006_keynote.html
regards
roland
List: linux-kernel
Subject: Re: distro specific kernels vs vanilla kernel and how to compare
From: ewanm89 <ewanm89 () googlemail ! com>
Date: 2007-11-17 5:17:56
Message-ID: 20071117051756.4b1d20da () ewanm89-laptop
[Download message RAW]
On Fri, 16 Nov 2007 23:25:27 +0100
Andi Kleen <andi@firstfloor.org> wrote:
> devzero@web.de writes:
>
> > does somebody know if there is a website or a project for giving
> > comfortable and deeper insight into what`s specific to distro`s
> > kernels and what`s their difference to vanilla kernel ?
> >
> > i mean some way to have some transparancy to what different distro
> > vendors add to vanilla kernel sources and thus turning it into
> > their own specific version.
>
> There used to be such a page at kernelnewbies, but at some point it
> disappeared.
>
> I agree it would be a useful resource.
>
> -Andi
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
I would also like to see something like this, as some work I'm doing on
working some funny networking (unfortunately IT department don't have
common sense) across multiple distros. Tracking the kernel patche
differences between the distros seems to be the hardest part (comparing
them to find what's needed for all distros to work).
--
Ewan Marshall (ewanm89)
_______________________________________________________________________
Jetzt neu! Schützen Sie Ihren PC mit McAfee und WEB.DE. 3 Monate
kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc=022220
reply other threads:[~2007-11-17 10:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2090717360@web.de \
--to=devzero@web.de \
--cc=ewanm89@googlemail.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox