Installing:
kernel-build-2.4.27-3_2.4.27-9sarge3_sparc.deb
to
pool/main/k/kernel-image-2.4.27-sparc/kernel-build-2.4.27-3_2.4.27-9sarge3_sparc.deb
kernel-headers-2.4.27-3-sparc32-smp_2.4.27-9sarge3_sparc.deb
to
pool/main/k/kernel-image-2.4.27-sparc/kernel-headers-2.4.27-3-sparc32-smp_2.4.27-
Installing:
kernel-build-2.4.27-3_2.4.27-10sarge3_ia64.deb
to
pool/main/k/kernel-image-2.4.27-ia64/kernel-build-2.4.27-3_2.4.27-10sarge3_ia64.deb
kernel-headers-2.4.27-3-itanium-smp_2.4.27-10sarge3_ia64.deb
to
pool/main/k/kernel-image-2.4.27-ia64/kernel-headers-2.4.27-3-itanium-smp_2.4.27-10
Installing:
kernel-headers-2.6.8-3-generic_2.6.8-16sarge4_alpha.deb
to
pool/main/k/kernel-image-2.6.8-alpha/kernel-headers-2.6.8-3-generic_2.6.8-16sarge4_alpha.deb
kernel-headers-2.6.8-3-smp_2.6.8-16sarge4_alpha.deb
to
pool/main/k/kernel-image-2.6.8-alpha/kernel-headers-2.6.8-3-smp_2.6.8-16s
Installing:
kernel-build-2.4.27-apus_2.4.27-10sarge3_powerpc.deb
to
pool/main/k/kernel-patch-powerpc-2.4.27/kernel-build-2.4.27-apus_2.4.27-10sarge3_powerpc.deb
kernel-build-2.4.27-nubus_2.4.27-10sarge3_powerpc.deb
to
pool/main/k/kernel-patch-powerpc-2.4.27/kernel-build-2.4.27-nubus_2.4.27-1
Installing:
kernel-build-2.6.8-3-power3-smp_2.6.8-12sarge4_powerpc.deb
to
pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-3-power3-smp_2.6.8-12sarge4_powerpc.deb
kernel-build-2.6.8-3-power3_2.6.8-12sarge4_powerpc.deb
to
pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-3-po
Installing:
kernel-headers-2.4_102sarge1_powerpc.deb
to pool/main/k/kernel-latest-powerpc/kernel-headers-2.4_102sarge1_powerpc.deb
kernel-headers-2.6_102sarge1_powerpc.deb
to pool/main/k/kernel-latest-powerpc/kernel-headers-2.6_102sarge1_powerpc.deb
kernel-headers_102sarge1_powerpc.deb
to po
Installing:
kernel-headers-2.6.8-3_2.6.8-5sarge4_s390.deb
to
pool/main/k/kernel-image-2.6.8-s390/kernel-headers-2.6.8-3_2.6.8-5sarge4_s390.deb
kernel-image-2.6.8-3-s390-tape_2.6.8-5sarge4_s390.deb
to
pool/main/k/kernel-image-2.6.8-s390/kernel-image-2.6.8-3-s390-tape_2.6.8-5sarge4_s390.deb
ke
Installing:
kernel-build-2.6.8-3_2.6.8-15sarge4_sparc.deb
to
pool/main/k/kernel-image-2.6.8-sparc/kernel-build-2.6.8-3_2.6.8-15sarge4_sparc.deb
kernel-headers-2.6.8-3-sparc32_2.6.8-15sarge4_sparc.deb
to
pool/main/k/kernel-image-2.6.8-sparc/kernel-headers-2.6.8-3-sparc32_2.6.8-15sarge4_sparc.
Installing:
kernel-headers-2.6-itanium-smp_2.6.8-14sarge4_ia64.deb
to
pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-itanium-smp_2.6.8-14sarge4_ia64.deb
kernel-headers-2.6-itanium_2.6.8-14sarge4_ia64.deb
to
pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-itanium_2.6.8-14sarge4
Installing:
kernel-headers-2.6.8-12-amd64-generic_2.6.8-16sarge4_i386.deb
to
pool/main/k/kernel-image-2.6.8-amd64/kernel-headers-2.6.8-12-amd64-generic_2.6.8-16sarge4_i386.deb
kernel-headers-2.6.8-12-amd64-k8-smp_2.6.8-16sarge4_i386.deb
to
pool/main/k/kernel-image-2.6.8-amd64/kernel-headers-
Installing:
kernel-headers-2.6.8-3-386_2.6.8-16sarge4_i386.deb
to
pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-3-386_2.6.8-16sarge4_i386.deb
kernel-headers-2.6.8-3-686-smp_2.6.8-16sarge4_i386.deb
to
pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-3-686-smp_2.6.8-16sarge4
Installing:
kernel-headers-2.4-generic_101sarge1_alpha.deb
to
pool/main/k/kernel-latest-2.4-alpha/kernel-headers-2.4-generic_101sarge1_alpha.deb
kernel-headers-2.4-smp_101sarge1_alpha.deb
to
pool/main/k/kernel-latest-2.4-alpha/kernel-headers-2.4-smp_101sarge1_alpha.deb
kernel-image-2.4-gener
Installing:
kernel-headers-2.4-386_101sarge1_i386.deb
to
pool/main/k/kernel-latest-2.4-i386/kernel-headers-2.4-386_101sarge1_i386.deb
kernel-headers-2.4-586tsc_101sarge1_i386.deb
to
pool/main/k/kernel-latest-2.4-i386/kernel-headers-2.4-586tsc_101sarge1_i386.deb
kernel-headers-2.4-686-smp_101
Installing:
kernel-headers-2.4-s390_2.4.27-1sarge1_s390.deb
to
pool/main/k/kernel-latest-2.4-s390/kernel-headers-2.4-s390_2.4.27-1sarge1_s390.deb
kernel-image-2.4-s390_2.4.27-1sarge1_s390.deb
to
pool/main/k/kernel-latest-2.4-s390/kernel-image-2.4-s390_2.4.27-1sarge1_s390.deb
kernel-image-2.4
Installing:
kernel-doc-2.6.8_2.6.8-16sarge4_all.deb
to pool/main/k/kernel-source-2.6.8/kernel-doc-2.6.8_2.6.8-16sarge4_all.deb
kernel-patch-debian-2.6.8_2.6.8-16sarge4_all.deb
to
pool/main/k/kernel-source-2.6.8/kernel-patch-debian-2.6.8_2.6.8-16sarge4_all.deb
kernel-source-2.6.8_2.6.8-16sarge
Installing:
kernel-doc-2.4.27_2.4.27-10sarge3_all.deb
to pool/main/k/kernel-source-2.4.27/kernel-doc-2.4.27_2.4.27-10sarge3_all.deb
kernel-patch-debian-2.4.27_2.4.27-10sarge3_all.deb
to
pool/main/k/kernel-source-2.4.27/kernel-patch-debian-2.4.27_2.4.27-10sarge3_all.deb
kernel-source-2.4.27_2.
Installing:
kernel-build-2.4.27-3_2.4.27-10sarge3_i386.deb
to
pool/main/k/kernel-image-2.4.27-i386/kernel-build-2.4.27-3_2.4.27-10sarge3_i386.deb
kernel-headers-2.4.27-3-386_2.4.27-10sarge3_i386.deb
to
pool/main/k/kernel-image-2.4.27-i386/kernel-headers-2.4.27-3-386_2.4.27-10sarge3_i386.deb
Installing:
kernel-build-2.4.27-3_2.4.27-10sarge3_alpha.deb
to
pool/main/k/kernel-image-2.4.27-alpha/kernel-build-2.4.27-3_2.4.27-10sarge3_alpha.deb
kernel-headers-2.4.27-3-generic_2.4.27-10sarge3_alpha.deb
to
pool/main/k/kernel-image-2.4.27-alpha/kernel-headers-2.4.27-3-generic_2.4.27-10sar
Installing:
kernel-headers-2.6-sparc32_101sarge1_sparc.deb
to
pool/main/k/kernel-latest-2.6-sparc/kernel-headers-2.6-sparc32_101sarge1_sparc.deb
kernel-headers-2.6-sparc64-smp_101sarge1_sparc.deb
to
pool/main/k/kernel-latest-2.6-sparc/kernel-headers-2.6-sparc64-smp_101sarge1_sparc.deb
kernel
Installing:
kernel-headers-2.6-386_101sarge1_i386.deb
to
pool/main/k/kernel-latest-2.6-i386/kernel-headers-2.6-386_101sarge1_i386.deb
kernel-headers-2.6-686-smp_101sarge1_i386.deb
to
pool/main/k/kernel-latest-2.6-i386/kernel-headers-2.6-686-smp_101sarge1_i386.deb
kernel-headers-2.6-686_101sa
Installing:
kernel-headers-2.6-generic_101sarge1_alpha.deb
to
pool/main/k/kernel-latest-2.6-alpha/kernel-headers-2.6-generic_101sarge1_alpha.deb
kernel-headers-2.6-smp_101sarge1_alpha.deb
to
pool/main/k/kernel-latest-2.6-alpha/kernel-headers-2.6-smp_101sarge1_alpha.deb
kernel-image-2.6-gener
Installing:
kernel-headers-2.4-sparc32-smp_42sarge2_sparc.deb
to
pool/main/k/kernel-latest-2.4-sparc/kernel-headers-2.4-sparc32-smp_42sarge2_sparc.deb
kernel-headers-2.4-sparc32_42sarge2_sparc.deb
to
pool/main/k/kernel-latest-2.4-sparc/kernel-headers-2.4-sparc32_42sarge2_sparc.deb
kernel-hea
Package: initramfs-tools
Version: 0.77
Severity: important
*** Please type your report below this line ***
mkinitramfs in initramfs-tools 0.77 is missing ${DESTDIR} before
/conf/mdrun.conf on lines 242 and 250:
# mkinitramfs -r /dev/md2 -o /boot/initrd.img-2.6.16-2-686-raid
/usr/sbin/mkinitra
hi, I 've used the kernel 2.4 for a long time, but 2.4 kernel doesn't support the udev and other new features so I decide to upgrade the kernel from 2.4 to 2.6.16. but when I installed the kernel 2.6.16, all the depends seems OK, but when I reboot my box, and select
2.6 kernel it hangs up fo
Dear Steve,
Thanks for your response.
> The bug log indicates that it's only exploitable when
>
> - you have a non-empty "staff" group on the client (+/- equivalent to
> untrusted root users on the client, since any root user can simply add
> users to this group)
> - you have NFS-shared files
On Thu, Aug 31, 2006 at 11:46:15AM +1000, Paul Szabo wrote:
> You seem to think that this is "important" but not "critical".
> Don't you agree that it is a root security hole?
Indeed I do not agree that it's a root security hole. The bug log indicates
that it's only exploitable when
- you have
Dear Steve,
You seem to think that this is "important" but not "critical".
Don't you agree that it is a root security hole?
Thanks,
Paul Szabo [EMAIL PROTECTED] http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics University of SydneyAustralia
--
To UNSUBSCRIBE,
Package: linux-image-2.6.16-2-xen-686
Version: 2.6.16-18
Severity: normal
Some time ago, I installed a Xen Dom0 under Debian using
linux-image-2.6.16-1-xen-686. Recently, I've installed two Xen Dom0's
under Debian using linux-image-2.6.16-2-xen-686, and I added that kernel
to the working Xen
On 08/30/06 02:11:51PM -0700, David Lang wrote:
> >Yep, but initramfs is initialized ways earlier than normal userspace.
> >
> >>however this is not soon enough to supply the firmware for devices like
> >>this.
> >
> >Are you sure of this ? This is somewhat contrary to what i have heard, and
> >it
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.20
> severity 384922 important
Bug#384922: NFS insecure without support for squashing multiple groups
Severity set to `important' from `critical'
>
End of message, stopping processing her
hey Giuseppe,
It is quite possible (we have seen this in other reports) that the
corruption occurred while you were running an earlier 2.6.17 build and
got written to disk. Then, when you were running 2.6.17-5, you
tripped over this corruption causing the problems you described.
Can you confirm
Your message dated Wed, 30 Aug 2006 16:47:16 -0600
with message-id <[EMAIL PROTECTED]>
and subject line fixed in sid
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reo
On Thu, Aug 31, 2006 at 12:12:42AM +0200, Frederik Schueler wrote:
> Please contact Bastian if you want to add a buildd for your
> architecture.
>
I can probably put an arm and a hppa up later this week.
Cheers,
Kyle
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "uns
Hi,
On Wed, Aug 30, 2006 at 05:59:42PM -0400, Kyle McMartin wrote:
> If each arch maintainer could give the kernel a testbuild, that would
> be great.
Ideally, we should have a snapshot buildd for every architecture, so far
only i386 sparc s390 ppc and amd64 are available:
http://kernel-archive
On Wed, Aug 30, 2006 at 11:35:56PM +0200, Frederik Schueler wrote:
> Thanks to Kyle the build failures on alpha hppa ia64 mips and mipsel
> should be fixed now.
>
If each arch maintainer could give the kernel a testbuild, that would
be great.
Cheers,
Kyle M.
--
To UNSUBSCRIBE, email t
Overview:
The Linux kernel source contains device drivers that ship with firmware
files provided by the hardware manufacturer. They are uploaded during
the driver initialization to the corresponding hardware device.
Some of these binary image files are provided as a hexdump of register
bank set
Hello,
I would like to schedule the next upload of linux-2.6, version 2.6.17-8
for tomorrow Thursday 31st.
Thanks to Kyle the build failures on alpha hppa ia64 mips and mipsel
should be fixed now.
If this version builds and works on all architectures, I would like to
call it a testing candidate
On Wed, 30 Aug 2006, Sven Luther wrote:
no, at least not in the current kernel. as was mentioned earlier in this
thread the ipw2200 needs the firmware at initialization, but some others
don't need it until open. I don't know if it's even possible to re-write
the driver to do this.
Oh well, thi
hello,
On Wed, Aug 30, 2006 at 05:01:23PM +0100, Dominic Hargreaves wrote:
> On Wed, Aug 30, 2006 at 05:38:40PM +0200, Bastian Blank wrote:
>
> > With the lack of responses to my restructuring the last weeks, it looks
> > like pkg-xen is dead.
> >
> > Now, what to do? My favorite is to merge it
FYI: The status of the linux-2.6.16 source package
in Debian's testing distribution has changed.
Previous version: 2.6.16-17
Current version: 2.6.16-18
--
This email is automatically generated; [EMAIL PROTECTED] is responsible.
See http://people.debian.org/~henning/trille/ for more informat
On Wed, Aug 30, 2006 at 12:34:16PM -0700, David Lang wrote:
> On Wed, 30 Aug 2006, Sven Luther wrote:
>
> >>>
> >>>Do you really need to bring up ipw2200 so early ? It is some kind of
> >>>wireless
> >>>device, right ?
> >>
> >>if modules are not in use the device is initialized when the kernel st
On Wed, 30 Aug 2006, Sven Luther wrote:
Do you really need to bring up ipw2200 so early ? It is some kind of
wireless
device, right ?
if modules are not in use the device is initialized when the kernel starts
up. this is before any userspace starts.
Well. but you could do the initialization
On Wed, Aug 30, 2006 at 11:20:53AM -0700, David Lang wrote:
> On Wed, 30 Aug 2006, Sven Luther wrote:
>
> >On Wed, Aug 30, 2006 at 10:52:02AM -0700, David Lang wrote:
> >>On Wed, 30 Aug 2006, Olaf Hering wrote:
> >>
> you are assuming that
>
> 1. modules are enabled and ipw2200 is com
On Wed, 30 Aug 2006, Sven Luther wrote:
On Wed, Aug 30, 2006 at 10:52:02AM -0700, David Lang wrote:
On Wed, 30 Aug 2006, Olaf Hering wrote:
you are assuming that
1. modules are enabled and ipw2200 is compiled as a module
No, why?
becouse if the ipw isn't compiled as a module then it's in
On Wed, 30 Aug 2006, Olaf Hering wrote:
you are assuming that
1. modules are enabled and ipw2200 is compiled as a module
No, why?
becouse if the ipw isn't compiled as a module then it's initialized (without
firmware) before the initramfs or initrd is run. if it could be initialized
later
On Wed, Aug 30, 2006 at 10:52:02AM -0700, David Lang wrote:
> On Wed, 30 Aug 2006, Olaf Hering wrote:
>
> >>you are assuming that
> >>
> >>1. modules are enabled and ipw2200 is compiled as a module
> >
> >No, why?
>
> becouse if the ipw isn't compiled as a module then it's initialized
> (without
On Wed, Aug 30, 2006 at 05:38:40PM +0200, Bastian Blank wrote:
> With the lack of responses to my restructuring the last weeks, it looks
> like pkg-xen is dead.
>
> Now, what to do? My favorite is to merge it into the kernel repository
> where I have my infrastructure (archive and autobuilders fo
On Sun, Aug 20, 2006 at 09:25:01PM +0200, Norbert Tretkowski wrote:
> I think I have a patch which fixes this problem, building a new kernel
> currently...
if that's 2.6.17-2 then I'm sorry to report that -smp still doesn't work
(same scsi errors; see attached log). -generic works fine though.
A
On Wed, 30 Aug 2006, [EMAIL PROTECTED] wrote:
> On Wed, Aug 30, 2006 at 08:36:58AM +0200, maximilian attems wrote:
> > On Tue, Aug 29, 2006 at 03:32:50PM -0700, Vagrant Cascadian wrote:
> > > i believe ipconfig defines ROOTSERVER when it is passed via the ip=
> > > parameter, and thus it's not nec
hello,
On Wed, 30 Aug 2006, Tim Phipps wrote:
> The top part of init has this:
>
> mkdir /sys
> mkdir /proc
> mkdir /tmp
> mkdir -p /var/lock
they are very fast to create on initramfs,
i'll put guards on those too if someone thinks to need to ship
them in initramfs.
> These can all be put in
On Mon, 28 Aug 2006 11:27:47 +0200, maximilian attems <[EMAIL PROTECTED]> said:
> i'd like to have a better /etc/kernel-img.conf, but Manoj doesn't
> want to update that config file at all so you have to stop
> installation to add obvious things there like do_initrd=yes. even
> if you add this yo
On Mon, 28 Aug 2006 10:07:42 +0200, Sven Luther <[EMAIL PROTECTED]> said:
> On Mon, Aug 28, 2006 at 12:59:53AM +0200, Michael Biebl wrote:
>> severity 383600 serious thanks
>>
>> I'm raising the severity to serious, because as already outlined,
>> packages that call update-initramfs -u in posti
[EMAIL PROTECTED] wrote:
> I am clueless with kernel programming. Still, I have came up with the
> following - hopefully straight forward - patch. Any comments?
The patch looks good to me, please send it to the upstream driver
maintainer.
I figure you want to have a look a http://www.kernelnewb
Processing commands for [EMAIL PROTECTED]:
> retitle 384922 NFS insecure without support for squashing multiple groups
Bug#384922: please support NFS squashing multiple groups
Changed Bug title.
> tags 384922 security
Bug#384922: NFS insecure without support for squashing multiple groups
There we
retitle 384922 NFS insecure without support for squashing multiple groups
tags 384922 security
severity 384922 critical
thanks
Dear Steinar,
> ... You may want to actually talk to the NFS kernel server people ...
Huh? I thought that is what have I been doing until now! (Oops, my mistake,
package
Processing commands for [EMAIL PROTECTED]:
> reassign 385284 linux-2.6
Bug#385284: Serial controller Timedia stop work on new kernel
Warning: Unknown package 'linux-image-2.6.17-2'
Bug reassigned from package `linux-image-2.6.17-2' to `linux-2.6'.
> --
Stopping processing here.
Please contact me
Package: linux-image-2.6.17-2
Version: 2.6.17-2
Severity: normal
I have a serial controller Timedia, that works fine under 2.4.27-3-686 but not
on kernel 2.6.16-2-686 and 2.6.17-2-686.
thanks in advance,
João Serrachinha
Linux version 2.4.27-3-686 ([EMAIL PROTECTED]) (gcc version 3.3.5 (Debia
Package: initramfs-tools
Version: 0.76
Severity: minor
The top part of init has this:
mkdir /sys
mkdir /proc
mkdir /tmp
mkdir -p /var/lock
These can all be put in the initramfs image can't they? Also (not a
bug), I can't figure out how /root gets created, it's not in the image
and there's no "mk
Processing commands for [EMAIL PROTECTED]:
> retitle 384922 please support NFS squashing multiple groups
Bug#384922: root_squash does not squash the staff group
Changed Bug title.
> reassign 384922 linux-2.6.16
Bug#384922: please support NFS squashing multiple groups
Bug reassigned from package `
Package: kernel-image-2.4.27-i386
Severity: serious
The kernel-image-2.4.27-i386 package build-depends on kernel-source-2.4.27,
which is RC-buggy and in any case not targetted for inclusion in the etch
release. This package will be removed from etch, and this bug is filed to
keep it from re-enter
On Wed, Aug 30, 2006 at 08:36:58AM +0200, maximilian attems wrote:
> On Tue, Aug 29, 2006 at 03:32:50PM -0700, Vagrant Cascadian wrote:
> > i believe ipconfig defines ROOTSERVER when it is passed via the ip=
> > parameter, and thus it's not necessary to re-implement this code with
> > SERVER_IP in
hello vagrant,
On Tue, Aug 29, 2006 at 03:32:50PM -0700, Vagrant Cascadian wrote:
> Package: initramfs-tools
> Version: 0.77
> Severity: minor
>
> i believe ipconfig defines ROOTSERVER when it is passed via the ip=
> parameter, and thus it's not necessary to re-implement this code with
> SERVER_I
On Tue, Aug 29, 2006 at 08:58:56PM -0700, Vagrant Cascadian wrote:
> Package: initramfs-tools
> Version: 0.77
> Severity: wishlist
> Tags: patch
>
> when etherboot is configured to pass the ip= option(so you only get one
> call to dhcp), it unfortunately doesn't pass the whole string, but only
> t
63 matches
Mail list logo
