Jens Schmalzing <[EMAIL PROTECTED]> writes:
> Hi,
>
> Sven Luther writes:
>
>> Could this not be solved by simply making the kernel-source
>> kernel-tree kernel-patch-debian dependency strict ?
>
> This is equivalent to dropping kernel-tree and kernel-patch-debian
> altogether.
kernel-tree-2.x.y-
Hi,
Sven Luther writes:
> Could this not be solved by simply making the kernel-source
> kernel-tree kernel-patch-debian dependency strict ?
This is equivalent to dropping kernel-tree and kernel-patch-debian
altogether.
> After all, there is almost zero chance to have the patches in
> separate s
On Thu, Aug 05, 2004 at 09:19:01PM +0200, Jens Schmalzing wrote:
> Hi,
>
> Sven Luther writes:
>
> > So what is the problem ?
>
> The problem arises when stuff gets out of sync, i.e. applying the
> latest revision of kernel-patch-debian to an older revision of
> kernel-source doesn't result in
Hi,
Sven Luther writes:
> So what is the problem ?
The problem arises when stuff gets out of sync, i.e. applying the
latest revision of kernel-patch-debian to an older revision of
kernel-source doesn't result in the latest revision of kernel-source.
This was demonstrated nicely by the 2.4 buil
William Lee Irwin III <[EMAIL PROTECTED]> writes:
>> There's a major security update pending, so we'll need to upload new
>> kernel images for everything in the universe in short order anyway.
On Thu, Aug 05, 2004 at 08:47:01PM +0200, Goswin von Brederlow wrote:
> I'm just about to upload a new ke
William Lee Irwin III <[EMAIL PROTECTED]> writes:
> On Thu, Aug 05, 2004 at 06:53:03AM -0700, William Lee Irwin III wrote:
>>> This will be necessary for major security issues, e.g. CAN-2004-0415,
>>> anyway, so I think we'll be okay. The bit about latest kernel-source
>>> is rather hopeful; if we
Have you guys seen this advisory yet? It looks rather serious:
http://isec.pl/vulnerabilities/isec-0016-procleaks.txt
Apparently this is fixed in 2.4.27-rc5 (don't know about 2.6 series):
http://lwn.net/Articles/96485/
The fix should probably go into Debian kernels in sarge...
regards,
--
Kev
On Thu, Aug 05, 2004 at 07:10:35PM +0200, Jens Schmalzing wrote:
> Hi,
>
> Sven Luther writes:
>
> > I think the kernel-tree did depend on the exact same version of the
> > kernel-source and kernel-patch-debian packages,
>
> kernel-tree depends on any revision of kernel-source and the latest
> r
Hi,
Sven Luther writes:
> I think the kernel-tree did depend on the exact same version of the
> kernel-source and kernel-patch-debian packages,
kernel-tree depends on any revision of kernel-source and the latest
revision of kernel-patch-debian. Together, this allows one to get the
latest revisi
Hi,
Sven Luther writes:
> Well, if the patch replaces the old patch in such a way that there is no
> interaction with newer patches, this should be no major problem, right ?
It becomes a problem if you have an older revision of kernel-source
installed and wish to get the source tree to the late
Hi,
Sven Luther writes:
> Yeah, thanks, i had forgotten about this, will fix it later today.
It's already fixed.
> Let's wait one more day to be sure that other things don't come up.
Fair enough.
Regards, Jens.
--
J'qbpbe, le m'en fquz pe j'qbpbe!
Le veux aimeb et mqubib panz je pézqbpbe je
On Thu, Aug 05, 2004 at 06:47:17PM +0200, Jens Schmalzing wrote:
> Hi,
>
> Sven Luther writes:
>
> > Well, if the patch replaces the old patch in such a way that there is no
> > interaction with newer patches, this should be no major problem, right ?
>
> It becomes a problem if you have an olde
On Thu, Aug 05, 2004 at 08:42:46AM -0700, William Lee Irwin III wrote:
> On Thu, Aug 05, 2004 at 07:57:16AM -0700, William Lee Irwin III wrote:
> >> There's a major security update pending, so we'll need to upload new
> >> kernel images for everything in the universe in short order anyway.
>
> On
Package: kernel-image-2.6.7-1-686
Version: 2.6.7-2
Severity: grave
Justification: causes non-serious data loss
Attempting to mount a CDROM results in the CD spinning for approximately
30 seconds, then the system locks up completely (unresponsive to
keyboard, mouse, and network). The lockup does no
On Thu, Aug 05, 2004 at 07:57:16AM -0700, William Lee Irwin III wrote:
>> There's a major security update pending, so we'll need to upload new
>> kernel images for everything in the universe in short order anyway.
On Thu, Aug 05, 2004 at 05:10:49PM +0200, Sven Luther wrote:
> Ok. Should i go ahead
On Thu, Aug 05, 2004 at 07:57:16AM -0700, William Lee Irwin III wrote:
> On Thu, Aug 05, 2004 at 06:53:03AM -0700, William Lee Irwin III wrote:
> >> This will be necessary for major security issues, e.g. CAN-2004-0415,
> >> anyway, so I think we'll be okay. The bit about latest kernel-source
> >> i
On Thu, Aug 05, 2004 at 06:53:03AM -0700, William Lee Irwin III wrote:
>> This will be necessary for major security issues, e.g. CAN-2004-0415,
>> anyway, so I think we'll be okay. The bit about latest kernel-source
>> is rather hopeful; if we take this as a precedent for architectures to
>> update
On Thu, Aug 05, 2004 at 03:52:47PM +0200, Jens Schmalzing wrote:
> Hi,
>
> Sven Luther writes:
>
> > Modified: trunk/kernel/source/kernel-source-2.6.7-2.6.7/debian/patch
> > es/marvell-pegasos.dpatch
>
> Let me re-iterate: You must never, ever change dpatch files that have
> already made it into
On Thu, Aug 05, 2004 at 06:53:03AM -0700, William Lee Irwin III wrote:
> On Thu, Aug 05, 2004 at 06:28:31AM -0700, William Lee Irwin III wrote:
> >> I'd be inclined to push this kind of thing in general to the generic
> >> package so long as no generic code is affected.
>
> On Thu, Aug 05, 2004 at
On Thu, Aug 05, 2004 at 02:33:02PM +0200, Jens Schmalzing wrote:
> Hi,
>
> Sven Luther writes:
>
> > I have to update the marvell-pegasos.dpatch patch,
>
> Keep in mind that you must not change patches that have been part of
> previous uploads. An update has to go in as marvell-pegasos-2.dpatch
Hi,
Sven Luther writes:
> Modified: trunk/kernel/source/kernel-source-2.6.7-2.6.7/debian/patch
> es/marvell-pegasos.dpatch
Let me re-iterate: You must never, ever change dpatch files that have
already made it into uploads. Otherwise, you will certainly break
kernel-tree. See debian/README.NMU,
Hi,
Sven Luther writes:
> I have to update the marvell-pegasos.dpatch patch,
Keep in mind that you must not change patches that have been part of
previous uploads. An update has to go in as marvell-pegasos-2.dpatch.
> I have upto now refrained from doing the upload, since the changes
> there w
On Thu, Aug 05, 2004 at 06:28:31AM -0700, William Lee Irwin III wrote:
>> I'd be inclined to push this kind of thing in general to the generic
>> package so long as no generic code is affected.
On Thu, Aug 05, 2004 at 03:51:24PM +0200, Sven Luther wrote:
> Yes, but this means a potential need for
On Thu, Aug 05, 2004 at 06:28:31AM -0700, William Lee Irwin III wrote:
> On Thu, Aug 05, 2004 at 01:40:36PM +0200, Sven Luther wrote:
> > I have to update the marvell-pegasos.dpatch patch, and this would thus
> > warrant
> > either a kernel-source upload or an addition of a patch patching the abov
On Thu, Aug 05, 2004 at 01:40:36PM +0200, Sven Luther wrote:
> I have to update the marvell-pegasos.dpatch patch, and this would thus warrant
> either a kernel-source upload or an addition of a patch patching the above
> patch in the powerpc kernel-patch.
> I have upto now refrained from doing the
Hello,
I have to update the marvell-pegasos.dpatch patch, and this would thus warrant
either a kernel-source upload or an addition of a patch patching the above
patch in the powerpc kernel-patch.
I have upto now refrained from doing the upload, since the changes there where
mostly powerpc specifi
Hi Jens,
Jens Schmalzing wrote:
Hi,
Harald Dunkel writes:
the patch [...] looks into /proc/modules (the user space interface
for module management) to get a list of loaded modules.
This only works if you are building an initrd for a kernel with the
exact same module configuration.
The module conf
Hi,
Harald Dunkel writes:
> the patch [...] looks into /proc/modules (the user space interface
> for module management) to get a list of loaded modules.
This only works if you are building an initrd for a kernel with the
exact same module configuration.
> On the other side, the current mkinitrd
* Martin Michlmayr wrote:
> * Norbert Tretkowski <[EMAIL PROTECTED]> [2004-07-30 23:57]:
> > > What needs to be done to update alpha?
> >
> > http://people.debian.org/~nobse/kernel-image-2.6.7-alpha/
> > I'm still waiting for feedback.
>
> Has anyone reviewed or tested them in the meantime?
I go
This is /proc/scsi for my PC (booted from a disk managed by
sata_sil):
# ls -ld $(find /proc/scsi )
dr-xr-xr-x 3 root root 0 Aug 5 08:32 /proc/scsi
-r--r--r-- 1 root root 0 Aug 5 08:32 /proc/scsi/device_info
-r--r--r-- 1 root root 0 Aug 5 08:32 /proc/scsi/scsi
dr-xr-xr-x 2 root root 0 Aug 5
Martin Michlmayr wrote:
* Harald Dunkel <[EMAIL PROTECTED]> [2004-08-03 10:36]:
Attached you can find a patch.
This looks like a hack to me which works around the real problem. See
maybe #256113.
I don't see that the patch is a hack. It looks into /proc/modules
(the user space interface for modul
On Thu, Aug 05, 2004 at 12:46:08AM +0200, Bluefuture wrote:
> Package: kernel
> Version: unknown
> Severity: wishlist
> Tags: patch
> X-Debbugs-CC: [EMAIL PROTECTED]
>
> Please add Packet Writing support to debian kernel for CD-RW DVD-RW:
> Home: http://w1.894.telia.com/~u89404340/packet.html
> Pa
32 matches
Mail list logo
