morning.
On Tue, 21 Aug 2007, Bastian Blank wrote:
I think its another time to reconsider the available i386 images.
Currently we build:
- 486
- 686
- 686-bigmem
- k7
- amd64
I propose the following:
- Rename 686-bigmem to 686-pae. pae is more than support for much
memory, it
On Tue, 21 Aug 2007, Bastian Blank wrote:
* Rename linux(-[-a-z]+|)-2.6 into linux\1.
* Drop the 2.6 version identifier from meta packages:
cool
thanks for picking that up :)
--
maks
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
On Tue, Aug 21, 2007 at 07:08:47PM +0200, Bastian Blank wrote:
Hi folks
* Rename linux(-[-a-z]+|)-2.6 into linux\1.
* Drop the 2.6 version identifier from meta packages:
Package: linux-image-686
Provides: linux-image, linux-latest-modules-2.6.22-1-686
Depends:
Hello List,
I'm administering several linux hosts, which are all set up to boot from a
luks-encrypted partition (which partly live in LVM). I was hacked off to have
to go down to the basement and enter the passwords manually on each and every
reboot. So why not let this be managed by a central
On Wed, Aug 22, 2007 at 09:18:44AM +0200, maximilian attems wrote:
- Drop k7.
ack
486 image is fine for those and the hardware is no longer
so wide spread.
There are a whole lot of k7 boxes out there.
I would not like to use the 486 flavour on my K7-smp servers, but I can
run some
Hello,
On Wed, Aug 22, 2007 at 02:11:48AM -0700, Steve Langasek wrote:
I object; if and when there ever is a new upstream kernel branch that we
want to track separately this would have to be reverted, and in the meantime
it would cause more confusion and work because of the need to shuffle the
On Wed, Aug 22, 2007 at 02:05:29PM +0200, Frederik Schueler wrote:
There are a whole lot of k7 boxes out there.
k6-3 and k7 are 686.
Bastian
--
What terrible way to die.
There are no good ways.
-- Sulu and Kirk, That Which Survives, stardate unknown
--
To
On Wed, Aug 22, 2007 at 02:11:48AM -0700, Steve Langasek wrote:
I object; if and when there ever is a new upstream kernel branch that we
want to track separately this would have to be reverted,
No. We never had complete support for more than one branch. And I really
doubt that anyone wants the
On Wed, Aug 22, 2007 at 02:07:23PM +0200, Frederik Schueler wrote:
On Wed, Aug 22, 2007 at 02:11:48AM -0700, Steve Langasek wrote:
I object; if and when there ever is a new upstream kernel branch that we
want to track separately this would have to be reverted, and in the meantime
it would
Package: linux-image-2.6.18-5-486
Version: 2.6.18.dfsg.1-13etch1
Severity: critical
Justification: breaks the whole system
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The 2.6.18-5-486 kernel that was pushed over the last few days to replace
2.6.18-4
makes this system completely unbootable. I
On Wed, Aug 22, 2007 at 06:06:28PM +0300, Martin-Eric Racine wrote:
Package: linux-image-2.6.18-5-486
Version: 2.6.18.dfsg.1-13etch1
Severity: critical
Justification: breaks the whole system
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The 2.6.18-5-486 kernel that was pushed over the
reassign linux-2.6
thanks
On Tue, Aug 21, 2007 at 07:20:59PM +0100, Martin wrote:
I was looking at trying out Trusted Grub
( http://www.prosec.rub.de/trusted_grub.html ) but found that the stock
Debian kernels seem to be built without the required drivers. It
appears they were disabled by in
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.10.7
reassign 439020 linux-2.6
Bug#439020: Please could CONFIG_TCG_TPM be set to 'm'
Bug reassigned from package `linux-image-2.6-686' to `linux-2.6'.
End of message, stopping processing
Your message dated Wed, 22 Aug 2007 18:47:25 +0300
with message-id [EMAIL PROTECTED]
and subject line Bug#439134: linux-image-2.6.18-5-486: 2.6.18-5-486 fails to
boot
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
Its been over 24 hrs since I committed something to the etch branch
and I haven't yet seen new builds appear in:
http://kernel-archive.buildserver.net/pool/main/l/linux-2.6/
So, I checked the status page to see if there was a failure, but it
looks like its currently down:
Hi,
this problem occurs also on my SGI Indigo2 with 256MB RAM:
BUG: warning at kernel/softirq.c:137/local_bh_enable()
Call Trace:
[8800f850] dump_stack+0x18/0x58
[880413dc] local_bh_enable+0x11c/0x128
[c00e5d58] $L436+0x50/0x88 [ip_conntrack]
# cat /proc/cpuinfo
system
On Wed, Aug 22, 2007 at 09:37:47AM -0600, dann frazier wrote:
Debian kernels seem to be built without the required drivers. It
appears they were disabled by in commit r3389 to the kernel-svn:
http://lists.alioth.debian.org/pipermail/kernel-svn-changes/2005-June/002083.html
As far as
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.10.7
severity 439134 important
Bug#439134: linux-image-2.6.18-5-486: 2.6.18-5-486 fails to boot
Severity set to `important' from `critical'
End of message, stopping processing here.
On Wed, Aug 22, 2007 at 09:18:44AM +0200, maximilian attems wrote:
- Rename 686-bigmem to 686-pae. pae is more than support for much
memory, it includes things like NX.
nack
as already told on private channel to many pentium m out there are
don't support pae
What is the problem than?
Package: linux-image-2.6-xen-amd64
Version: 2.6.18-5
When I start up multiple domUs (for example the third one)
I get the following kernel panic:
Aug 22 18:22:13 fourty2 kernel: --- [cut here ] -
[please bite here ] -
Aug 22 18:22:13 fourty2 kernel: Kernel BUG at
On Wed, Aug 22, 2007 at 07:18:08PM +0200, Bastian Blank wrote:
On Wed, Aug 22, 2007 at 09:18:44AM +0200, maximilian attems wrote:
- Rename 686-bigmem to 686-pae. pae is more than support for much
memory, it includes things like NX.
nack
as already told on private channel to many
Hi Adrian,
On Wed, Aug 22, 2007 at 04:13:19AM +0200, Josip Rodin wrote:
I'm reporting this bug that I have been seeing for a while and which is
a regression from a few months/years ago - the line-in input simply doesn't
work right. arecord(1) just doesn't record anything with it, it doesn't
Processing commands for [EMAIL PROTECTED]:
tags 434752 + patch
Bug#434752: Kernel hangs when I echo 0 /proc/sys/vm/vdso_enabled
There were no tags set.
Tags added: patch
stop
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
tags 434752 + patch
stop
On Thu, Jul 26, 2007, Loïc Minier wrote:
Since some months, I get unusable backtraces from gdb; I was pointed at
an OpenSuse bug at:
https://bugzilla.novell.com/show_bug.cgi?id=258433
I extracted the patch Novell/OpenSuse applied to its kernel, would be
nice
On Wed, Aug 22, 2007 at 09:18:44AM +0200, maximilian attems wrote:
I propose the following:
- Rename 686-bigmem to 686-pae. pae is more than support for much
memory, it includes things like NX.
nack
as already told on private channel to many pentium m out there are
don't support pae
Package: linux-2.6
Version: 2.6.18.dfsg.1-13etch1
Severity: important
Hi Dann,
There's a nasty bug in NVidia onboard ethernet chipsets:
The MAC address provided by the BIOS is invalid (it's inverted); as a
consequence
the kernel creates a random MAC as a workaround. In combination with udev this
On Wed, Aug 22, 2007 at 02:21:18PM +0200, Bastian Blank wrote:
On Wed, Aug 22, 2007 at 02:11:48AM -0700, Steve Langasek wrote:
I object; if and when there ever is a new upstream kernel branch that we
want to track separately this would have to be reverted,
No. We never had complete support
Steve Langasek [EMAIL PROTECTED] writes:
On Wed, Aug 22, 2007 at 02:21:18PM +0200, Bastian Blank wrote:
On Wed, Aug 22, 2007 at 02:11:48AM -0700, Steve Langasek wrote:
I object; if and when there ever is a new upstream kernel branch that we
want to track separately this would have to be
linux-latest-2.6_6etch2_ia64.changes uploaded successfully to localhost
along with the files:
linux-latest-2.6_6etch2.dsc
linux-latest-2.6_6etch2.tar.gz
linux-image-itanium_2.6.18+6etch2_ia64.deb
linux-image-2.6-itanium_2.6.18+6etch2_ia64.deb
On Tue, Aug 21, 2007 at 09:10:02AM -0600, dann frazier wrote:
On Tue, Aug 21, 2007 at 09:15:22AM +0200, Bastian Blank wrote:
On Mon, Aug 20, 2007 at 04:10:31PM -0600, dann frazier wrote:
Are security updates visible at this point in the install. I think
they are (except for network-less
Greetings,
I recently installed etch on an amd64 box which previously had Fedora.
It had a small ext2 /boot and large LVM, so I shrunk Fedora's volume and
made a new one for Debian, where I installed everything. I included the
LVM modules in /etc/initramfs-tools/modules . Then I added the
Have the same problem with
linux-image-2.6.18-5-amd64 2.6.18.dfsg.1-13etch1
after upgrading (linux-image-2.6.18-4-amd64 work fine)
Motherboard P5B
Display adapter ATI RADEON X1600 Series
Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz
MemTotal
Have the same problem with
linux-image-2.6.18-5-amd64 2.6.18.dfsg.1-13etch1
after upgrading (linux-image-2.6.18-4-amd64 work fine)
Motherboard P5B
Display adapter ATI RADEON X1600 Series
Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz
MemTotal
Otavio Salvador [EMAIL PROTECTED] writes:
Steve Langasek [EMAIL PROTECTED] writes:
On Wed, Aug 22, 2007 at 02:21:18PM +0200, Bastian Blank wrote:
On Wed, Aug 22, 2007 at 02:11:48AM -0700, Steve Langasek wrote:
I object; if and when there ever is a new upstream kernel branch that we
want
On Wed, Aug 22, 2007 at 10:49:30PM -0300, Otavio Salvador wrote:
experimental might be used if we had a linux-2.7 or something while
it's not OK for sid and Maks and Bastian agree that we're not going to
have more the one kernel source on the distro anymore so there's no
more need to allow
On Wed, Aug 22, 2007 at 09:39:02AM -0400, Kyle McMartin wrote:
On Wed, Aug 22, 2007 at 09:18:44AM +0200, maximilian attems wrote:
I propose the following:
- Rename 686-bigmem to 686-pae. pae is more than support for much
memory, it includes things like NX.
nack
as already told on
On Wed, Aug 22, 2007 at 08:20:22PM -0700, Steve Langasek wrote:
On Wed, Aug 22, 2007 at 09:39:02AM -0400, Kyle McMartin wrote:
On Wed, Aug 22, 2007 at 09:18:44AM +0200, maximilian attems wrote:
I propose the following:
- Rename 686-bigmem to 686-pae. pae is more than support for much
37 matches
Mail list logo
