Package: src:linux
Version: 4.19.28-2
Severity: grave
Tags: security
Justification: user security hole
Dear Maintainer,
An issue was discovered in rds_tcp_kill_sock in net/rds/tcp.c in the Linux
kernel before 5.0.8.
There is a race condition leading to a use-after-free, related to net namespace
Yes, we revert that commit and build our own kernel. The fix was
available upstream, but debian haven't picked up yet.
Jeff
On Tue, Sep 13, 2016 at 3:59 AM, Thomas Martin wrote:
> Hello Jeff,
>
> I'm having the same issue you had [1], could you please tell me if you fixed
&g
ttps://patchwork.ozlabs.org/patch/647778/
Thanks a lot!
Jeff Wu
-- Package-specific info:
** Version:
Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc
version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt25-2+deb8u3
(2016-07-02)
** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64
root=
issue to linux-scsi to start. I'm thinking this will end
up as a USB storage quirk.
--
Jeff DeFouw
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org
On Sat, 12 Jan 2013 10:28:01 -0800
John Darrah wrote:
> On Fri, Jan 11, 2013 at 08:27:16AM -0500, Jeff Layton wrote:
> > On Thu, 10 Jan 2013 20:29:43 -0800
> > John Darrah wrote:
> >
> > > On Fri, Jan 04, 2013 at 07:09:33AM -0500, Jeff Layton wrote:
> > &
On Thu, 10 Jan 2013 20:29:43 -0800
John Darrah wrote:
> On Fri, Jan 04, 2013 at 07:09:33AM -0500, Jeff Layton wrote:
> > On Thu, 3 Jan 2013 21:29:22 -0800
> > John Darrah wrote:
> >
> > > On Sat, Dec 29, 2012 at 12:26:07PM +0100, Ben Hutchings wrote:
> > &
On Sat, 29 Dec 2012 01:24:36 +0100
Ben Hutchings wrote:
> On Mon, 2012-12-24 at 09:14 -0500, Jeff Layton wrote:
> > On Sun, 23 Dec 2012 09:10:34 -0500
> > Jeff Layton wrote:
> [...]
> > > I had a look at the code today and suspect that I know what the problem
> &
On Wed, 25 Apr 2012 11:20:44 +0200
Rik Theys wrote:
> Hi,
>
> On 04/24/2012 11:16 PM, Jeff Layton wrote:
> > On Tue, 24 Apr 2012 13:35:13 -0700
> > Greg KH wrote:
> >
> >> On Tue, Apr 24, 2012 at 10:22:50PM +0200, Rik Theys wrote:
> >>> Hi,
&g
attempt to do an NFS mount
after memory is already heavily fragmented. This allocation was
fricking huge before those patches...
That said, I'm not sure that really qualifies as stable-kernel fodder...
--
Jeff Layton
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120424171641.6cb6b...@tlielax.poochiereds.net
On Wed, 28 Sep 2011 11:09:33 +0200
John Hughes wrote:
> On 27/09/11 20:27, Jeff Layton wrote:
> > On Mon, 26 Sep 2011 14:31:32 -0400
> > Jeff Layton wrote:
> >
> >
> >>
> >> Not sure what happened here. Looks like the "freeze phase"
On Mon, 26 Sep 2011 14:31:32 -0400
Jeff Layton wrote:
> On Mon, 26 Sep 2011 17:52:58 +0200
> John Hughes wrote:
>
> > On 23/09/11 17:09, Jeff Layton wrote:
> > > I went ahead and attached the latest one to the RHBZ above. If you can
> > > grab it from there
On Mon, 26 Sep 2011 17:52:58 +0200
John Hughes wrote:
> On 23/09/11 17:09, Jeff Layton wrote:
> > I went ahead and attached the latest one to the RHBZ above. If you can
> > grab it from there and test it, that would be great.
> >
>
> Ok, I'm now testing th
On Fri, 23 Sep 2011 19:58:45 -0500
Jonathan Nieder wrote:
> found 642409 linux-2.6/2.6.32-35squeeze2
> found 642409 linux-2.6/3.0.0-4
> found 642409 linux-2.6/3.1.0~rc4-1~experimental.1
> tags 642409 + upstream
> quit
>
> Hi Jeff and John,
>
> John Hughes wrot
On Fri, 23 Sep 2011 17:01:20 +0200
John Hughes wrote:
> On 23/09/11 16:40, Jeff Layton wrote:
> > On Fri, 23 Sep 2011 16:30:36 +0200
> > John Hughes wrote:
> >
> >
> >> Well, after minor modifications (needed to include freezer.h in
> >> fs/nfs/i
On Fri, 23 Sep 2011 16:30:36 +0200
John Hughes wrote:
> Well, after minor modifications (needed to include freezer.h in
> fs/nfs/inode.c and net/sunrpc/sched.c) I've installed Jeff Layton's
> patch from https://bugzilla.redhat.com/show_bug.cgi?id=717735 in my
> 3.1-rc7
t;
> The changes start after tag debian/2.6.32-35squeeze1.
>
> The kernel configuration files we use are at
> <http://kernel.alioth.debian.org/config/2.6.32-33/>.
>
> Full source and binary packages containing these and other backported
> drivers can now be found at:
>
>
On Wed, Aug 18, 2010 at 15:07, Ben Hutchings wrote:
> I doubt it.
I thought there was a chance it was something like the change below
(not that change, but you get the idea).
> The kernel configuration for each flavour is are made by combining
> multiple files. There is no simple way to view t
On Wed, Aug 11, 2010 at 20:26, Ben Hutchings wrote:
> The kernel team (in conjunction with the security team) decided that one
> kernel per release is less trouble.
Is there information available anywhere about this? (Maybe some
thoughts on things of this nature could be added to the debian kern
On Mon, Aug 9, 2010 at 19:04, Ben Hutchings wrote:
> This is an experimental repository that hopefully makes it easier to see
> the patches we apply. You can build packages from it using 'make
> deb-pkg', but that's not what we do.
It would be helpful if you could include a config file. I tried
. This might benefit kernel
development in general. Lots of users are aware of apt-cache search &
would try them on a wider array of machines. Particularly in sid where
users are a bit more savvy.
--
Jeff
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a
On Tue, Aug 10, 2010 at 05:48, Ben Hutchings wrote:
> Once squeeze is released we'll upload the latest kernel to unstable,
> whether that's 2.6.35 or .36.
It would be helpful to me if there was a way to make newer kernels
available in sid. Is there anything we could do to help? I seem to
remembe
ork on a lenovo
T61p.
--
Jeff
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/aanlktin+ud2tqlli7=jxtp_9ru+flyu3n0rz0ppxt...@mail.gmail.com
-handbook.alioth.debian.org/) is
very helpful. I never knew about it until today because it wasn't
referenced anywhere in the kernel-image package (that I could find).
In other regards, thanks for maintaining this helpful information,
Jeff
--
To UNSUBSCRIBE, email to debian-kernel-requ...@li
Is there a way to pull down newer versions of the kernels? I put sid
on a new laptop, but the wireless is flaky. It's of course worth
trying newer kernels with something like this. I'd try the stock deb
packages if there was a apt repository for them.
--
To UNSUBSCRIBE, email to debian-kernel-re
Workaround is to blacklist the nouveau driver.
In /etc/modprobe.d/blacklist.conf insert the line:
blacklist nouveau
However, recent updates in Sid fix this for me. Packages are
libdrm-nouveau1 2.4.18-5
xserver-xorg-video-nouveau 1:0.0.15+git20100329+7858345-3
On my system, this is no longer
The "drbd-connector.patch" worked for us. Our DRBD system is back up and
running correctly again. Thanks!
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4b99ef22.
On 12/20/2009 02:12 PM, Ben Hutchings wrote:
Only some drivers (and none before kernel version 2.6.31) currently
set these flags. When the flags are equal to 0 and so we don't know
what the link partner advertised, don't report anything.
Signed-off-by: Ben Hutchings
---
ethtool.c |4 +++-
sh to -stable too?
>
> If you now have the information you need about contention, then it seems
> to me that it would be worthwhile to remove the unnecessary warnings.
> If you don't want to submit a stable update then I can patch it out in
> the Debian kernel package.
>
>
I'm actually just running a debootstrapped Debian on a Fedora box.
Nevertheless, I've confirmed this bug on a full-blown Debian box as well.
Attached is a patch to fix the bug:
-Jeff
-- System Information:
Debian Release: 5.0
APT prefers stable
APT policy: (500, 'stable'
c
e7841f70 c03751a0kernel_init
e7841ff0 c00136d4kernel_thread
Let me know if any numbers need to be check or added.
I can reboot and report fairly quickly.
-jeff
-- Package-specific info:
-- System Information:
Debian Release: lenny/sid
Architecture: powerpc (ppc)
Kernel: Linux 2.6.24
I had the same problem, here is what worked for me:
apt-get install hwinfo
hwinfo --framebuffer
Look at the Mode lines, find the one I want:
Mode 0x0323: 1024x768 (+4096), 24 bits
convert 0323 from base 16 to base 10
put result into menu.lst kernel line:
vga=803
You don't need hwinfo to get
Package: linux-image-2.6.25-2-powerpc
Version: 2.6.25-6
Severity: grave
Justification: renders package unusable
Here's the OOPS data that I wrote down:
NIP: c013abac LR: c013af18 CTR:
REGS: e7841c(e?)50 TRAP: 0200 Not tainted
MSR: 00049030 CR: 8422 XER: 2000
TASK: e783
ols will go away forever.
Tks,
Jeff Bailey
On Fri, Apr 18, 2008 at 9:21 AM, Tomasz Chmielewski <[EMAIL PROTECTED]> wrote:
> Sounds like this bug could have been avoided if /dev/null and /dev/console
> were provided as static entries in udev package?
>
>
>
> Tomasz Chmielewsk
Package: ipw3945-modules-2.6.21-1-686
Version: 2.6.21+1.2.1-1
Severity: grave
Justification: renders package unusable
The package is missing the module file:
$ dpkg -L ipw3945-modules-2.6.21-1-686
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/ipw3945-modules-2.6.21-1-686
/usr/share/doc/ipw3945
Get me off of this stupid list.
Thank you
Jeff Stanich
Simix Reactive Solutions, LLC
http://www.simixsolutions.com
-Original Message-
From: Matthew Wakeling [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 06, 2007 3:16 PM
To: Debian Bug Tracking System
Subject: Bug#427841: linux-image
Unpacking linux-image-2.6.18-4-xen-686 (from
.../linux-image-2.6.18-4-xen-686_2.6.18.dfsg.1-10_i386.deb) ...
Setting up linux-image-2.6.18-4-xen-686 (2.6.18.dfsg.1-10) ...
/boot/initrd.img-2.6.18-4-xen-686 does not exist. Cannot update.
That it's even possible for this script to exit like this is
I just installed a new machine and noticed I couldn't apt-get
initrd-tools. It looks like it might have been accidentally deleted by
an automated script:
http://packages.qa.debian.org/i/initrd-tools/news/20070103T061312Z.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsu
On 01/09/07 14:57, dann frazier wrote:
> my Keyspan device. I'm not a lawyer, but its also questionable to me
> whether or not the license permits us to distribute it an the the
> non-free modules package.
It's probably best to assume that IBM's legal team knows what they are
doing on this one :)
On 01/09/07 11:50, dann frazier wrote:
> On Mon, Jan 08, 2007 at 07:49:19PM -0800, Jeff Carr wrote:
>> I've not seen conclusive evidence that the keyspan firmware file is
>> not the best effort of freeness.
>
> "This firmware may not be modified and may only b
On 01/08/07 17:47, Sam Morris wrote:
> On Mon, 08 Jan 2007 19:49:19 -0800, Jeff Carr wrote:
>> On 01/06/07 10:13, Marco d'Itri wrote:
>>> In linux.debian.devel.release Marc Haber <[EMAIL PROTECTED]> wrote:
>>>> So keyspan USB devices will be useless with De
ans binary firmware files.
It's either we pull them out or hide them inside like is done today.
Happy hacking,
Jeff
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
http://www.debian.org/vote/2006/vote_007
What legal advice did you receive that made you determine that it is
illegal to distribute them?
Regards,
Jeff
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Wed, 2007-01-03 at 09:32 -0500, Jeff Licquia wrote:
> I am running the complete lsb-runtime-test suite against the new kernels
> (as installed yesterday from the sid apt repo at
> http://kernel-archive.buildserver.net/debian-kernel), but I also did a
> run with just the msync test,
On Fri, 2006-12-29 at 15:01 +0100, Martin Michlmayr wrote:
> Yes, I agree. I'm CCing the linux-mm list in hope that someone can
> review your patch. In the meantime, I've asked the Debian LSB folks to
> verify that your patch fixes the LSB problem.
I am running the complete lsb-runtime-test suit
On Tue, 2006-12-19 at 17:08 +0100, Martin Michlmayr wrote:
> So it seems that the patches needed for msync() conformance we applied
> from 2.6.19 to our 2.6.18 cause filesystem corruption, see the current
> discussion on this on lkml. From what I understand it, plain 2.6.18
> is not LSB 3.1 confor
I have more news on the LSB test regressions I reported on earlier.
On Sun, 2006-10-15 at 18:22 -0400, Jeff Licquia wrote:
> The two tests are:
>
> /tset/LSB.os/mfiles/msync_P/T.msync_P 7 FAIL
As far as I can tell, the test is correct. The test does an mmap() of
three pages from a l
Package: linux-image-2.6.17-2-686
Version: 2.6.17-9
Severity: important
>From a recent run of the LSB 3.1 tests:
10|852 /tset/LSB.os/mfiles/msync_P/T.msync_P 22:58:49|TC Start, scenario ref
858-0
15|852 3.6-lite 9|TCM Start
400|852 7 1 22:59:13|IC Start
200|852 7 22:59:13|TP Start
520|852 7
code.
What do you think should be done if source code doesn't make sense or
can't be made?
Jeff
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
out that it was almost
immeasurably fast on a tmpfs. =)
While it's generally true that it's important not to optimise without
test data to measure against, many of the things that I expected to take
alot of time just don't because everything is already in memory.
Tks,
Jeff Bailey
--
ing to get support, why should this support *not* be available everywhere? Requiring the user to do a step that a computer ought to have done doesn't make sense.
tks,
Jeff Bailey
--
Although when you're in the situation that RMS is telling you that
you're being too ideologi
Package: kernel
Severity: normal
After upgrading from 2.6.15 to 2.6.16 (both Debian stock kernels -k7-smp), X's
mga drm failed to initialize (using xserver-xorg 6.9.0.dfsg.1-5). This
was due to the 'OldDmaInit' workaround necessary for 2.6.15. Once I
disabled that, drm was initialized. However, w
I have a NetRAID-1M and have been trying to use it in a 2.6.11 or
greater kernel. Google has not helped, and neither has the linux-scsi
ml. Is this patch ready or is more modification still needed?
Thanks for any pointers!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubs
d while you are at it
> - - you can also subscribe to the page, to get notified each time it is
> updated).
*lol* I'm clearly tired. I hadn't noticed that it was the wiki. =)
I'll update it tomorrow or so.
Tks,
Jeff Bailey
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
just a trace from the glibc
dynamic linker.
Tks,
Jeff Bailey
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
to be happy about, and not only from a d-i point of view.
> waldi: Why is mklibs-copy needed?
In Ubuntu we're not using mklibs, we use ldd and sed instead. If this
behaviour can be restored, we can drop the python dep.
Tks,
Jeff Bailey
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
, since this is basically a ramdisk, once the
> boot is over, what happens to the memory used to hold it ?
It gets freed as part of run-init, which goes through and rm's
everything on the ramdisk to cause it to be returned to the system.
Tks,
Jeff Bailey
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
aren't in my tree. If this is considered a
negative thing, just roll the changes back. =)
initramfs-tools maintained by, please add Adam Conrad to the list of
names there. Scott James Remnant is also a major contributor to the
Ubuntu package.
Tks,
Jeff Bailey
--
To UNSUBSCRIBE, email to [
On dim, 2005-11-13 at 20:34 +0100, Frans Pop wrote:
> On Sunday 13 November 2005 18:32, Jeff Bailey wrote:
> > On dim, 2005-11-13 at 12:46 +0100, Bastian Blank wrote:
> > > I think it is possible at least for initramfs-tools to run without
> > > sysfs on the building
at you're likely
interested in booting with in the initramfs and detecting which ones to
use at boot time. If you ask it to detect which modules are needed, it
needs a valid sysfs tree to scan (although it is resiliant in that case
against module name changes)
Tks,
Jeff Bailey
--
To UNSUBSC
s -u" and have it regenerated.
If it has been altered by the user, it will say so, and refuse to touch
it.
This is key to the strategy of pushing as many of the add-on bits out to
other packages as possible.
For those that haven't looked at the initramfs-tools code, please
consider doing so. It's written in shell. =) If you have questions,
lemme know. I'm subscribed to this list, but don't check the folder
often, so cc:'ing me is usually good if you need a fast response.
Tks,
Jeff Bailey
signature.asc
Description: Ceci est une partie de message numériquement signée
Le samedi 08 octobre 2005 à 09:48 +0200, Sven Luther a écrit :
On Fri, Oct 07, 2005 at 06:10:17PM -0400, Jeff Bailey wrote:
> Le jeudi 06 octobre 2005 à 18:07 +0200, Sven Luther a écrit :
>
> > initrd-tool can do either ext2 or cramfs, but not really initramfs, altough i
> &g
on
2.6 ones, i believe.
initramfs-tools and yaird default to initramfs format, but could probably
generate cramfs or ext2 just as well.
And initrd requires pivot_root to chain to the root system. On an initramfs, a pivot_root will crash it. You need to do a move mount instead.
Tks,
Jeff
ere with no d-i changes is zero.
Colin would be best to poll about that, I guess. Ubuntu is using initramfs-tools, so Debian could just inherit those changes.
Tks,
Jeff Bailey
signature.asc
Description: Ceci est une partie de message numériquement signée
workaround for the compile error for sparc.
The ports that I listed as known-working above are using initramfs-tools for the Breezy release. So I generally *hope* they're well enough tested. I'll let you know in a week ;)
Tks,
Jeff Bailey
signature.asc
Description: Ceci
these are ready for prime time, with known problems. Move
them to Kconfig, and I have to deal with the bug reports. No thanks...
Jeff
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Horms wrote:
Hi Jeff, Hi All,
In the cause of debuging a problem with a DVD burner[1]
Brett Smith brought to my attention that there are several
variables in ./include/linux/libata.h, that when changed
from #undef to #define, enable features in the ATA subsystem.
Is there any interest in a
On Fri, Jun 24, 2005 at 02:01:13PM +0200, Klaus Fuerstberger wrote:
> Package: initrd-tools
> Version: 0.1.81.1
> Severity: normal
> File: /usr/sbin/mkinitrd
>
> Hi all,
>
> found this bug Subject archived as #299103 when searching for devfs and
> mkinitrd.
> The Bug that was fixed was for the
should be provided externally. I'd appreciate any feedback. I don't think I've committed this work yet, since I finised it yesterday and then went out drinking. =) Look for it in the next 24 hours, though.
Tks,
Jeff Bailey
oes *not* need to be added to the boot
process, an error on my part due to confusion (or ignorance...take your
pick).
jeff
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
-detected if you
wanted a .rpm or .deb.
Thanks for any pointers to the "correct" methods of doing things,
Jeff
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
be someone knows why this is happening.
Lots of problem potentially. It's better to make an initrd and include
all the modules you need to support your hard disk.
Jeff
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
uot; in that it uses `uname -r`
to determine the kernel headers. So, one can just go into the dir and
type make;make install and spca5xx.ko will automatically be loaded the
next time the user boots.
So I guess I should start by looking at the files in
/usr/src/kernel-patches/all/2.6.11/debian/ ?
Jeff
--
broadcom driver for the tg3 which I think is gpl'd. So the firmware
may legitimately be under the GPL.
It is.
Jeff
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
h.
* Firmwares such as tg3 should be shipped with the kernel tarball.
In short, there are plenty of technical problems to resolve before this
is even a reasonable request. Currently, a user upgrading to a tg3 sans
firmware will simply get tg3 sans firmware.
Jeff
--
To UNSUBSCRIBE,
We do not add comments to the kernel source code which simply state the
obvious.
Jeff
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
rt addr,
image size, ...). The current interface is complete crap for this sort
of setup.
The firmware loader really needs to be loading -archives- not individual
files.
We are a -long- way from moving the firmware out of the tg3 source code.
Jeff
--
To UNSUBSCRIBE, email to [EMAIL PROTE
Sven Luther wrote:
On Mon, Apr 04, 2005 at 03:55:55PM -0400, Jeff Garzik wrote:
Matthew Wilcox wrote:
On Mon, Apr 04, 2005 at 10:51:30AM -0700, Greg KH wrote:
Then let's see some acts. We (lkml) are not the ones with the percieved
problem, or the ones discussing it.
Actually, there are
this came up, the Acenic firmware was
mentioned:
http://lists.debian.org/debian-legal/2004/12/msg00078.html
Seems to me that situation is still not resolved.
And it looks like no one cares enough to make the effort to resolve this...
I would love an open source acenic firmware.
Jeff
reopen 287189
reassign 287189 initrd-tools
thanks
On Mon, 2005-02-07 at 10:36 +0100, Thomas Hood wrote:
> Was #287189 closed by mistake? The original report (now reassigned to
> initrd-tools) is that mkinitrd looks for /bin/discover. According to
> the changelog, the discover program is now at /
On Thu, 2005-02-03 at 10:30 +0100, Thomas Hood wrote:
> The current executables in discover are:
>
> /sbin/discover-modprobe
> /bin/discover-static
> /usr/bin/discover
> /usr/bin/discover-config
>
> In discover1 there is only:
>
> /sbin/discover
>
> Where does the faulty dis
file follows.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 7 Dec 2004 21:12:02 -0500
Source: initrd-tools
Binary: initrd-tools
Architecture: source all
Version: 0.1.75
Distribution: experimental
Urgency: low
Maintainer: Debian kernel team
Changed-By: Jeff Bailey <[EM
absolute
minimum needed for userspace applications to use.
We (the glibc folks) will probably update it after Sarge releases,
though.
Tks,
Jeff Bailey
signature.asc
Description: This is a digitally signed message part
I can't reproduce this on any of my hardware here, Can someone who can
please email me, and we'll work out a time we can both sit on IRC and
fix this? It would be helpful if you had two machines, so that we can
IRC on the one that's not booting.
Tks,
Jeff Bailey
--
I do not ag
This kernel patch solved my problem:
http://www.ussg.iu.edu/hypermail/linux/kernel/0408.2/0538.html
e differences to work from, but also where
it's taking the time would be useful to know. It really shouldn't spend
a significant amount of time in the initrd at all.
Tks,
Jeff Bailey
--
I never know what to expect when you respond to my postings. No insult
intended, you are merely
th working from, but I'm not picky about
it. =)
Tks,
Jeff Bailey
Andrew Morton wrote:
Jeff Garzik <[EMAIL PROTECTED]> wrote:
Luis, you, or somebody should create a new patch series with just the
critical fixes, NO WHITESPACE/FORMATTING CHANGES mixed in, and send
those first.
Whitespace changes are often nice, but they should be the very first
patch[
/14" patch, because without
them the driver is unusable on big-endian architectures.
The entire patch series was dropped.
Luis, you, or somebody should create a new patch series with just the
critical fixes, NO WHITESPACE/FORMATTING CHANGES mixed in, and send
those first.
Jeff
88 matches
Mail list logo
