Package: initramfs-tools
Version: 0.90a
Severity: critical
Justification: breaks the whole system
Hi,
I have the same situation described by Beojan in one of my boxes but
not the other two - all three are debian testing.
His solution - yaird - also worked for me.
Reading the bug report I came
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.10.7
severity 446724 important
Bug#446724: SAME SITUATION - initramfs-tools: creates broken initramfs image as
reported on Bug #445688
Severity set to `important' from `critical'
End of
Please consider these patches for inclusion in the 2.6.18 kernel for
Etch.
The current Etch kernel occasionally drops all the sky2 NICs our
customer has off the network and the hosts require a reboot to resolve
the problem.
Given the maturity of the patch, I'm hoping its benefit:risk ratio
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.10.8
severity 446724 normal
Bug#446724: SAME SITUATION - initramfs-tools: creates broken initramfs image as
reported on Bug #445688
Severity set to `normal' from `important'
End of
Package: linux-image-2.6.18-5-amd64
Version: 2.6.18.dfsg.1-13etch4
Severity: critical
Justification: breaks the whole system
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel:
Hi everyone,
After reading /usr/share/initramfs-tools/hook-functions, I wanted to
comment that `basename $foo` is often replaced with the (posix)
shell expansion ${foo##*/} which expands to the value of foo with the
longest prefix matching shell wildcard */ stripped (but doesn't
modify foo).
Hello list,
I was trying to compile 2.6.23 starting from Debian sources, pulled from
the apt sources published here:
http://wiki.debian.org/DebianKernel
The 2.6.23 in those repos works a charm:
[EMAIL PROTECTED]:~$ uname -a
Linux vasquez 2.6.23-1-amd64 #1 SMP Sun Oct 14 03:58:39 UTC 2007
Processing commands for [EMAIL PROTECTED]:
severity 446744 important
Bug#446744: linux-image-2.6.18-5-amd64: System fail to boot with
linux-image-2.6.8-5-amd64 giving error message: Kernel Panic -
Severity set to `important' from `critical'
tags 446744 moreinfo unreproducible
Bug#446744:
severity 446744 important
tags 446744 moreinfo unreproducible
thanks
On Mon, Oct 15, 2007 at 12:50:18PM +0200, Eduard Wildknaap wrote:
Package: linux-image-2.6.18-5-amd64
Version: 2.6.18.dfsg.1-13etch4
Severity: critical
Justification: breaks the whole system
The error is somewhat related
Package: linux-image-2.6.22-2-k7
Version: 2.6.22-4
Severity: important
After resuming from suspend there is no network.
'ip add' only outputs the loopback device.
'/etc/init.d/networking restart' doesn't help either.
This bug does not occur with earlier kernel versions (i.e. =2.6.21).
My
On 10/12/07, Neil Brown [EMAIL PROTECTED] wrote:
On Friday October 12, [EMAIL PROTECTED] wrote:
yes I have.
Then I tried booting in knoppix to see if maybe there are hdd problems
so I run e2fsck on both drives to see if there are any issues.
reboot and it still does the same thing.
Ok,
On 10/15/07, Neil Brown [EMAIL PROTECTED] wrote:
On Monday October 15, [EMAIL PROTECTED] wrote:
seems as the size is the same?
seems.
I was hoping for
cat /proc/partitions
hplinux:/home/lucas# cat /proc/partitions
major minor #blocks name
3 0 312571224 hda
3 1
On Monday October 15, [EMAIL PROTECTED] wrote:
seems as the size is the same?
seems.
I was hoping for
cat /proc/partitions
and maybe even
fdisk -l /dev/hda /dev/hdb
I should have been more specific.
NeilBrown
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
As you say, the devices are exactly the same size, thanks.
On Monday October 15, [EMAIL PROTECTED] wrote:
how do I undo? mdadm /dev/md2 -f /dev/hda2
So I could try the sync in init 1
Lucas
Well, you could:
mdadm /dev/md2 -f /dev/hda2
mdadm /dev/md2 -r /dev/hda2
then when you are
14 matches
Mail list logo
