On Fri, Mar 25, 2005 at 08:45:40AM -0700, dann frazier wrote:
> On Thu, 2005-03-24 at 19:37 -0800, Steve Langasek wrote:
> > On Thu, Mar 24, 2005 at 06:22:32PM -0700, dann frazier wrote:
> > > I'm trying to decide what I want to do about the ia64 kernel ABI. I
> > > rev'd it from -2 (currently in
On Thu, 2005-03-24 at 19:37 -0800, Steve Langasek wrote:
> On Thu, Mar 24, 2005 at 06:22:32PM -0700, dann frazier wrote:
> > I'm trying to decide what I want to do about the ia64 kernel ABI. I
> > rev'd it from -2 (currently in sarge) to -3 to turn off PREEMPT
> > (prevents at least one user trigg
Steve Langasek wrote:
> On Fri, Mar 25, 2005 at 08:04:30AM +0100, Martin Schulze wrote:
>
> > I've also been told that many module packages aren't built the Debian
> > way with a .dsc file that can be used as basis for dpkg-buildpackage
> > or similar. This makes the problem more difficult.
>
>
On Fri, Mar 25, 2005 at 08:04:30AM +0100, Martin Schulze wrote:
> I've also been told that many module packages aren't built the Debian
> way with a .dsc file that can be used as basis for dpkg-buildpackage
> or similar. This makes the problem more difficult.
The kernel module packages we know o
dann frazier wrote:
> It seems to me that the best use of everyone's time would be for the
> kernel team to have an agreement with the security team that we will
> restrict changes to our 2.4.27/2.6.8 kernels in such a way that they can
> start with our unstable packages for sarge updates (with may
On Thu, 2005-03-24 at 19:37 -0800, Steve Langasek wrote:
> On Thu, Mar 24, 2005 at 06:22:32PM -0700, dann frazier wrote:
> > I'm trying to decide what I want to do about the ia64 kernel ABI. I
> > rev'd it from -2 (currently in sarge) to -3 to turn off PREEMPT
> > (prevents at least one user trigg
On Thu, Mar 24, 2005 at 06:22:32PM -0700, dann frazier wrote:
> I'm trying to decide what I want to do about the ia64 kernel ABI. I
> rev'd it from -2 (currently in sarge) to -3 to turn off PREEMPT
> (prevents at least one user triggerable oops). This seemed convenient,
> since the k-s-2.6.8-14 h
I'm trying to decide what I want to do about the ia64 kernel ABI. I
rev'd it from -2 (currently in sarge) to -3 to turn off PREEMPT
(prevents at least one user triggerable oops). This seemed convenient,
since the k-s-2.6.8-14 had its own ABI change.
Well, turns out this was a bad idea - we've de
8 matches
Mail list logo
