On 29.04.2007 21:08, Dave Jones wrote:
> On Sun, Apr 29, 2007 at 03:03:42PM +0200, Thorsten Leemhuis wrote:
>
> > So, what will we do in the future? Can we (after F7 is out and rawhide
> > rolls again) please switch to something less confusing where version
> > somehow allows normal users to cl
On Sun, Apr 29, 2007 at 08:30:02PM -0700, Pete Zaitcev wrote:
> On Sun, 29 Apr 2007 16:55:15 -0500, Jay Cliburn <[EMAIL PROTECTED]> wrote:
>
> > What about MSI? On or off?
>
> Off for FC6, on for Rawhide, or at least this is how I understood
> DaveJ's preference.
I did the same thing in r
On Sun, 29 Apr 2007 16:55:15 -0500, Jay Cliburn <[EMAIL PROTECTED]> wrote:
> What about MSI? On or off?
Off for FC6, on for Rawhide, or at least this is how I understood
DaveJ's preference. Considering how unstable it is, makes sense, I guess.
I have a laptop (Dell 1501), where MSI is DOA. Very
On Sun, 2007-04-29 at 19:28 -0500, Tom "spot" Callaway wrote:
> On Sun, 2007-04-29 at 15:11 -0400, Dave Jones wrote:
>
> > silo can't be fixed ?
>
> Maybe. How's your forth?
I've noticed similar restrictions in yaboot.
josh
___
Fedora-kernel-list mai
On Sun, Apr 29, 2007 at 04:55:15PM -0500, Jay Cliburn wrote:
> > Early preview of F7 features, saves power yadayada, may find new
> > bugs. (Gets us that nice fuzzy 'f6 bugs are f7 bugs' bonus though)
> > - Turn NO_HZ on, but do the same as we did for MSI (enable the config,
> > but only
On Sun, 29 Apr 2007 14:57:49 -0400
Dave Jones <[EMAIL PROTECTED]> wrote:
> We could do a rebase to .21 this week, and push that out to testing,
> and if anything critical turns up before that becomes deemed stable,
> we could push a branched build off of .20 directly to updates.
>
> Most of the s
On Sun, 2007-04-29 at 15:11 -0400, Dave Jones wrote:
> silo can't be fixed ?
Maybe. How's your forth?
~spot
___
Fedora-kernel-list mailing list
Fedora-kernel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-kernel-list
On Sun, Apr 29, 2007 at 08:13:19AM -0500, Tom spot Callaway wrote:
> The SPARC bootloader (silo) can't handle label names longer than 15
> characters. So, for example, when booty tries to automagically label a
> new kernel on Aurora, we get a label like:
>
> 2.6.22-1.3200.fc
>
> The more
On Sun, Apr 29, 2007 at 03:03:42PM +0200, Thorsten Leemhuis wrote:
> So, what will we do in the future? Can we (after F7 is out and rawhide
> rolls again) please switch to something less confusing where version
> somehow allows normal users to clearly see what kernel they got? And one
> that d
On Sun, Apr 29, 2007 at 06:36:32PM +0200, dragoran wrote:
> 2.6.21.1 is out ... so whats the plan now? Relase a FC6
> update(updates-testing) or stick with 2.6.20.x until 2.6.22 is
> out/2.6.21 get some more testing?
We could do a rebase to .21 this week, and push that out to testing,
and if
2.6.21.1 is out ... so whats the plan now? Relase a FC6
update(updates-testing) or stick with 2.6.20.x until 2.6.22 is
out/2.6.21 get some more testing?
___
Fedora-kernel-list mailing list
Fedora-kernel-list@redhat.com
https://www.redhat.com/mailman/l
On Sun, 2007-04-29 at 15:03 +0200, Thorsten Leemhuis wrote:
> kernel-2.6.22-1.3200.fc7.rc2.git15
Not to distract from Thorsten's good points here, but the longer the
kernel n-v-r, the more painful it is for SPARC.
The SPARC bootloader (silo) can't handle label names longer than 15
characters. So
Hi all!
I'd like to put a old but still valid discussion on the table again
where a solution never was found: Pre-release kernel versioning.
In short: Kernel like for example kernel-2.6.20-1.3066.fc7 are in
reality 2.6.21-rc6-git5. That's not only confusing to users, it also
breaks outside kernel
13 matches
Mail list logo
