Package: kernel-image-2.6.7-1-386
Version: 2.6.7-2
Severity: minor
The conf file /etc/kernel-img.conf has this inside by default:
# Do not create symbolic links in /
do_symlinks = yes
As you can see, the comment says the symbolic links are not created but
the option below says they are
Hi,
just for info: I had exactly the same CRC errors, using a stock
(non-Debian) 2.6.7 kernel.
With a 2.6.8-rc2-bk9 kernel things work fine right now, no CRC
errors so far.
I attached some current config info.
Greetings, Bastian
--
,''`.Bastian Kleineidam . calvin (at) debian.org
: :'
Probably you are the uploader of the following file(s) in
the Debian upload queue directory:
kernel-image-2.6.7-alpha_2.6.7-1.dsc
kernel-image-2.6.7-alpha_2.6.7-1.tar.gz
This looks like an upload, but a .changes file is missing, so the job
cannot be processed.
If no .changes file arrives
kernel-image-2.6.7-alpha_2.6.7-1_alpha.changes uploaded successfully to
localhost
along with the files:
kernel-image-2.6.7-alpha_2.6.7-1.dsc
kernel-image-2.6.7-alpha_2.6.7-1.tar.gz
kernel-headers-2.6.7-1_2.6.7-1_alpha.deb
kernel-headers-2.6-generic_2.6.7-1_alpha.deb
At some point in the past, I wrote:
The 2.6.8 release has been almost exclusively focused on stabilization.
I highly recommend adopting as much of 2.6.8 as possible if not the
whole delta between 2.6.7 and 2.6.8. If not incrementing the version
number after freeze is the primary constraint,
Package: kernel-image-2.6.7-1-686
Version: 2.6.7-2
Severity: important
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.7-1-686
Locale: LANG=C, LC_CTYPE=C
Versions of packages
(attached are lsmod's and dmesg's after the file in rcS.d was execed)
(by the way it looks like yenta is the pooee module)
-- lsmod --
Module Size Used by
af_packet 22376 1
eepro100 30700 0
snd_intel8x0m 20264 0
snd_intel8x0
Probably you are the uploader of the following file(s) in
the Debian upload queue directory:
kernel-image-2.4.26-alpha_2.4.26-3.dsc
kernel-image-2.4.26-alpha_2.4.26-3.tar.gz
This looks like an upload, but a .changes file is missing, so the job
cannot be processed.
If no .changes file arrives
On Sun, Aug 01, 2004 at 04:57:40AM -0700, William Lee Irwin III wrote:
At some point in the past, I wrote:
The 2.6.8 release has been almost exclusively focused on stabilization.
I highly recommend adopting as much of 2.6.8 as possible if not the
whole delta between 2.6.7 and 2.6.8. If not
kernel-image-2.4.26-alpha_2.4.26-3_alpha.changes uploaded successfully to
localhost
along with the files:
kernel-image-2.4.26-alpha_2.4.26-3.dsc
kernel-image-2.4.26-alpha_2.4.26-3.tar.gz
kernel-headers-2.4.26-1_2.4.26-3_alpha.deb
kernel-image-2.4-generic_2.4.26-3_alpha.deb
Accepted:
kernel-build-2.4.26-1_2.4.26-3_alpha.deb
to
pool/main/k/kernel-image-2.4.26-alpha/kernel-build-2.4.26-1_2.4.26-3_alpha.deb
kernel-headers-2.4.26-1-generic_2.4.26-3_alpha.deb
to
pool/main/k/kernel-image-2.4.26-alpha/kernel-headers-2.4.26-1-generic_2.4.26-3_alpha.deb
Package: kernel
Version: 20040801
Severity: normal
Setting up kernel-image-2.4.18-1-686-smp (2.4.18-13.1) ...
/usr/sbin/mkinitrd: /dev/vg0/lv1: Unknown root device
Please refer to the manual page.
Failed to create initrd image.
dpkg: error processing kernel-image-2.4.18-1-686
Hi!
This is my correct e-mail address, [EMAIL PROTECTED] doesn't exist.
--
Joosep-Georg Järvemaa
On Sun, Aug 01, 2004 at 09:28:46PM -0400, Andres Salomon wrote:
Note that one thing I'm concerned about (and probably should've mentioned
in my original post) is ia64 and alpha; getting 2.6.8 into sarge will be
tight. Assume that i386 and powerpc will be thrown in w/ kernel-source,
as those
On Mon, 02 Aug 2004 04:45:57 +0200, Goswin von Brederlow wrote:
[...]
Aren't experimental and unstable in different override files?
Quoting AJ:
For people uploading to experimental, you should be aware of the
following:
* experimental uses the same overrides as unstable. Packages
15 matches
Mail list logo
