[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: how to detect a debian kernel from `uname -r`



On Sat, Sep 10, 2005 at 09:42:17PM +0200, Sven Luther wrote:
> On Sat, Sep 10, 2005 at 08:02:38PM +0200, Sven Luther wrote:
> > On Sat, Sep 10, 2005 at 05:57:12PM +0200, Andrea Arcangeli wrote:
> > > On Sat, Sep 10, 2005 at 05:33:29PM +0200, Sven Luther wrote:
> > > > Sure, i am not stupid, i perfectly noticed that, now my question is why do you
> > > > want to know that ?
> > > 
> > > That's for the klive project, I added two links in the first email just
> > > check it again.
> > 
> > Also, your list is bogus, debian supports actually 12 architectures, and you
> > only list x86 flavours.
> 
> Mmm, rereading me this sounds a bit too aggresive, which was not my intention,

The reason klive don't list all 12 archs is primarly because there are
no klive users coming from all those 12 archs. See the unknown list.

If you can improve this regexp (which seems the way to go for now)
you're very welcome:

	'Debian' : re.compile(r'^(\d+)\.(\d+)\.(\d+)(?:-git(\d+)|\.(\d+)|-rc(\d+))?-(\d+)-(?:[3456]86|k7|generic|amd64-k8)')

Right now I only added the basics to catch the most frequent archs in
klive unknown listing, it's true I can't catch all 12 archs if somebody
would be running klive on top of them.

Since the ubuntu kernel seems to be very different from debian kernel, I
wonder how I can detect it with uname -r, I guess I can't right now.

Anyway klive was made primarly for mainline, so I don't care that much
if I can't differentiate between debian and ubuntu.



Reply to: