Re: x86 kernel flavours was: 2.6.14-1 in incoming, status and future

2005-11-22 Thread Anand Kumria
On Tue, Nov 01, 2005 at 11:25:37AM +0900, Horms wrote: > > There was some discussion of cutting down on the number of flavours. > It all centred around, is there any real benifit. For instance, > it is conventional wisdom that 686 will run faster on a UP box than 686-smp, > but for a typical workl

Re: x86 kernel flavours was: 2.6.14-1 in incoming, status and future

2005-11-01 Thread Bastian Blank
On Tue, Nov 01, 2005 at 11:25:37AM +0900, Horms wrote: > However, as its a performance issue, what is needed is numbers. > I heard that Ubuntu were looking into it, but haven't heard > anything of late. I only heard something about a weird patch which noops the locks on runtime. Bastian -- Is t

Re: 2.6.14-1 in incoming, status and future

2005-11-01 Thread Bastian Blank
On Mon, Oct 31, 2005 at 06:44:29PM -0200, Otavio Salvador wrote: > - Allow us to fix detection problems without to need a kernel upload; As the modules checks against it own table, this is a noop. > - Allow by arch specific modules; The modules may specify that also. > - Allow by kernel vers

Re: x86 kernel flavours was: 2.6.14-1 in incoming, status and future

2005-10-31 Thread Horms
On Tue, Nov 01, 2005 at 02:03:46AM +1100, Anand Kumria wrote: > On Sun, 30 Oct 2005 02:31:01 -0800, Steve Langasek wrote: > > > On Sun, Oct 30, 2005 at 07:57:34PM +1100, Anand Kumria wrote: > > > >> Speaking of kernel flavours (we weren't, but what the hey); is the plan > >> still to reduce all o

Re: 2.6.14-1 in incoming, status and future

2005-10-31 Thread Eddy Petrişor
On 10/31/05, Otavio Salvador <[EMAIL PROTECTED]> wrote: > > We are not using discover2 yet, but discover1, and i thought the way to the > > future was to use hotplug only, as ubuntu did ? > > In installer itself, for sure. But discover2 has some important > feature that cannot be satisfied by hotp

Re: 2.6.14-1 in incoming, status and future

2005-10-31 Thread Otavio Salvador
Eddy Petrişor <[EMAIL PROTECTED]> writes: > On 10/31/05, Otavio Salvador <[EMAIL PROTECTED]> wrote: >> > We are not using discover2 yet, but discover1, and i thought the way to the >> > future was to use hotplug only, as ubuntu did ? >> >> In installer itself, for sure. But discover2 has some imp

Re: x86 kernel flavours was: 2.6.14-1 in incoming, status and future

2005-10-31 Thread Sven Luther
On Tue, Nov 01, 2005 at 02:03:46AM +1100, Anand Kumria wrote: > On Sun, 30 Oct 2005 02:31:01 -0800, Steve Langasek wrote: > > > On Sun, Oct 30, 2005 at 07:57:34PM +1100, Anand Kumria wrote: > > > >> Speaking of kernel flavours (we weren't, but what the hey); is the plan > >> still to reduce all o

Re: x86 kernel flavours was: 2.6.14-1 in incoming, status and future

2005-10-31 Thread Anand Kumria
On Sun, 30 Oct 2005 02:31:01 -0800, Steve Langasek wrote: > On Sun, Oct 30, 2005 at 07:57:34PM +1100, Anand Kumria wrote: > >> Speaking of kernel flavours (we weren't, but what the hey); is the plan >> still to reduce all of the x86 flavours down to two: generic x86 and >> generic x86-smp? > > "

Re: 2.6.14-1 in incoming, status and future

2005-10-31 Thread Otavio Salvador
Sven Luther <[EMAIL PROTECTED]> writes: > On Sat, Oct 29, 2005 at 10:57:30AM -0200, Otavio Salvador wrote: >> Marco Amadori <[EMAIL PROTECTED]> writes: >> >> > Alle 14:18, sabato 29 ottobre 2005, hai scritto: >> >> Marco Amadori <[EMAIL PROTECTED]> writes: >> >> > If there is also a proposal that

Re: x86 kernel flavours was: 2.6.14-1 in incoming, status and future

2005-10-30 Thread Norbert Tretkowski
* Anand Kumria wrote: > I can recall quite a number of incident where i've moved a disk from > an athlon k6 to k7 (and vice versa) and found random failures until > I picked the right kernel package. Hu? Running a k6 kernel on a k7 shouldn't be a problem. Norbert -- To UNSUBSCRIBE, email to [E

Re: x86 kernel flavours was: 2.6.14-1 in incoming, status and future

2005-10-30 Thread Steve Langasek
On Sun, Oct 30, 2005 at 07:57:34PM +1100, Anand Kumria wrote: > On Sun, 30 Oct 2005 09:46:30 +0100, Sven Luther wrote: > > On Sat, Oct 29, 2005 at 02:36:53PM +0200, Marco Amadori wrote: > > As said, i think that the only way to solve this for debian-installer would > > be > > to follow up with m

x86 kernel flavours was: 2.6.14-1 in incoming, status and future

2005-10-30 Thread Anand Kumria
On Sun, 30 Oct 2005 09:46:30 +0100, Sven Luther wrote: > On Sat, Oct 29, 2005 at 02:36:53PM +0200, Marco Amadori wrote: > As said, i think that the only way to solve this for debian-installer would be > to follow up with my plan, and mandate a policy of all packaged modules to > provide .debs and

Re: 2.6.14-1 in incoming, status and future

2005-10-30 Thread Sven Luther
On Sat, Oct 29, 2005 at 10:57:30AM -0200, Otavio Salvador wrote: > Marco Amadori <[EMAIL PROTECTED]> writes: > > > Alle 14:18, sabato 29 ottobre 2005, hai scritto: > >> Marco Amadori <[EMAIL PROTECTED]> writes: > >> > If there is also a proposal that at install time scans through external > >> > m

Re: 2.6.14-1 in incoming, status and future

2005-10-30 Thread Sven Luther
On Sat, Oct 29, 2005 at 02:36:53PM +0200, Marco Amadori wrote: > Alle 14:18, sabato 29 ottobre 2005, hai scritto: > > Marco Amadori <[EMAIL PROTECTED]> writes: > > > If there is also a proposal that at install time scans through external > > > modules to find those needed by the host system I will

Re: x86 kernel flavours was: 2.6.14-1 in incoming, status and future

2005-10-30 Thread Sven Luther
On Sun, Oct 30, 2005 at 07:57:34PM +1100, Anand Kumria wrote: > On Sun, 30 Oct 2005 09:46:30 +0100, Sven Luther wrote: > > > On Sat, Oct 29, 2005 at 02:36:53PM +0200, Marco Amadori wrote: > > > As said, i think that the only way to solve this for debian-installer would > > be > > to follow up wi

Re: 2.6.14-1 in incoming, status and future

2005-10-29 Thread Otavio Salvador
Marco Amadori <[EMAIL PROTECTED]> writes: > Alle 14:18, sabato 29 ottobre 2005, hai scritto: >> Marco Amadori <[EMAIL PROTECTED]> writes: >> > If there is also a proposal that at install time scans through external >> > modules to find those needed by the host system I will be happier :-) >> >> Th

Re: 2.6.14-1 in incoming, status and future

2005-10-29 Thread Marco Amadori
Alle 14:18, sabato 29 ottobre 2005, hai scritto: > Marco Amadori <[EMAIL PROTECTED]> writes: > > If there is also a proposal that at install time scans through external > > modules to find those needed by the host system I will be happier :-) > > That can be one area where discover2 can work. It ha

Re: 2.6.14-1 in incoming, status and future

2005-10-29 Thread Otavio Salvador
Marco Amadori <[EMAIL PROTECTED]> writes: > If there is also a proposal that at install time scans through external > modules to find those needed by the host system I will be happier :-) That can be one area where discover2 can work. It has some good and flexible enough database for it. We only

Re: 2.6.14-1 in incoming, status and future

2005-10-29 Thread Horms
On Sat, Oct 29, 2005 at 09:42:58AM +0200, Norbert Tretkowski wrote: > * Sven Luther wrote: > > but alpha, hppa and arm all three had commits fixing the FTBFS a few > > hours after the upload, so as soon as we get confirmation of the > > build success, we can do -2. > > Confirmed for alpha, 2.6.14-

Re: 2.6.14-1 in incoming, status and future

2005-10-29 Thread Marco Amadori
Alle 08:06, sabato 29 ottobre 2005, Sven Luther ha scritto: > Hello all, > > Well, as you may have noticed, we uploaded 2.6.14-1 to unstable yesterday, Really Good Job, it's nearly incredible fast! > Ok, let's finish with the next things to work on : > > - clear the external module situation. P

Re: 2.6.14-1 in incoming, status and future

2005-10-29 Thread Norbert Tretkowski
* Sven Luther wrote: > but alpha, hppa and arm all three had commits fixing the FTBFS a few > hours after the upload, so as soon as we get confirmation of the > build success, we can do -2. Confirmed for alpha, 2.6.14-2 builds fine. Norbert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a

2.6.14-1 in incoming, status and future

2005-10-28 Thread Sven Luther
Hello all, Well, as you may have noticed, we uploaded 2.6.14-1 to unstable yesterday, we needed 6 hours from when i was made aware of the upstream release and the moment it entered NEW, and missed dinstall only by a couple of hours, so the packages are now in incoming and not unstable, we should c