case.
Thanks,
Guido
>From 9f638f2eabb49da543ca153f6649601630c7f478 Mon Sep 17 00:00:00 2001
From: Guido Trotter
Date: Thu, 21 Oct 2010 16:58:53 +0100
Subject: [PATCH] Don't try build initramfs on non-modular kernel
If the kernel is build without modules support (for example for a
virtual
Package: linux-libc-dev
Version: 2.6.30-3
Severity: important
Compiling something like:
cat > t.c <
int main(void) { return 0; }
EOF
gcc -o t t.c
Fails with:
In file included from /usr/include/linux/socket.h:23,
from /usr/include/linux/netlink.h:4,
from t.c:1:
I had a similar problem for 2.6.20 and 2.6.21, but it was solved for me in
2.6.22... Does this work for you too? Can this be closed?
Guido
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi!
I've reassigned the bug we had against xen to initramfs-tools, as it is, as
reported, the same bug, and being a bug with the image generation we can't do
anything on our side about it.
Also I re-raised the severity to critical because, as stated by the severity
description, this bug "makes u
Package: ipw3945d
Version: 1.7.22-2
Severity: wishlist
Hi, ipw3945d documentation says it can work in non-root mode and
provides examples for that... Can the debian package be done so it by
default adds an unprivileged ipw3945d and runs the daemon under it?
Thanks,
Guido
-- System Information:
Hi!
What I found out is that the debian ipw3945-modules-* package (made by
kernel-package with make-kpkg) distributes the /etc/modprobe.d/ipw3945-modules
file while ipw3945d distributes /etc/modprobe.d/ipw3945d which both start the
daemon. This might be the cause of the problem. I suggest removi
On Mon, Feb 27, 2006 at 02:29:51PM +0100, Sven Luther wrote:
Hi,
> I guess that if people are able to find a kernel source tree outside of
> debian, they are perfectly capable of downloading and applying a patch too.
>
> Just include an URL to wherever such a patch is in the README.Debian of the
On Tue, Feb 28, 2006 at 02:17:45PM +0100, Sven Luther wrote:
Hi,
> > I can.
>
> :)
>
> Guido, be warned that Bastian often communicates with a few monosylabes and
> SVN commits :) This doesn't make working with him too problematic usually
> though :)
>
We've been a bit more chatty, for now, b
On Tue, Feb 28, 2006 at 10:15:39AM +0100, Bastian Blank wrote:
Hi,
> The current package from pkg-xen is not releasable.
>
Then why don't you just join and commit your fixes before anybody tried to
release it?
Guido
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscrib
On Mon, Feb 27, 2006 at 01:51:51PM +0100, Sven Luther wrote:
Hi,
> The kernel patches for XEN should be maintained inside the kernel team and in
> linux-2.6, they are free to join the kernel team to handle this, but it is
> unacceptable to have some kind of external patch to the kernel floating
>
On Sat, Feb 25, 2006 at 01:11:35AM +0100, Frederik Schueler wrote:
Hi,
> I am sorry things have rushed today, things which should have better been
> discussed by all concerned persons, _before_.
>
True, we're sorry on our part about that!
> We have been tracking xen support in the linux-2.6 so
On Fri, Feb 24, 2006 at 05:40:04PM -0800, Steve Langasek wrote:
Hi,
> FWIW, the policy on kernel patches for sarge was that if it didn't apply to
> the kernel sources we shipped, it didn't need to be included as a package in
> stable. We're obviously not shipping a 2.6.12 kernel for etch, so I
>
On Fri, Feb 24, 2006 at 05:34:44PM -0800, Steve Langasek wrote:
Hi,
> > Yeah, it's a sort of kernel, but it's not the linux kernel... And it seems
> > the
> > kernel team is about the linux kernel, not just any kernel, isn't it?
>
> The dom0 kernel is a Linux kernel built for the Xen hypervisor
On Fri, Feb 24, 2006 at 06:06:22PM +0100, Bastian Blank wrote:
Hi,
> It is a sort of kernel.
Yeah, it's a sort of kernel, but it's not the linux kernel... And it seems the
kernel team is about the linux kernel, not just any kernel, isn't it?
> Just to say, how connected xen to linux is:
>
> Fo
On Fri, Feb 24, 2006 at 05:41:53PM +0100, Isaac Clerencia wrote:
Hi,
> I agree. I just would like to ask that, please, don't disband just because of
> disagreement with the kernel team, but try to cooperate anyway.
>
I don't think we want to! And I hope there is no disagreement (we still don't
On Fri, Feb 24, 2006 at 05:20:17PM +0100, Isaac Clerencia wrote:
Hi,
> Well, if the kernel team answers "left to the kernel team" and you close the
> alioth project, I guess you can always move into the kernel team ;)
>
Yes, we could, of course... But on the other hand I believe that the xen
h
On Fri, Feb 24, 2006 at 04:54:24PM +0100, Julien Danjou wrote:
Hi,
> As far as I understand, you will just maintain Xen kernel images. (for
> dom0 only ?).
Actually I think he meant the hypervisors too... Anyway I also think that if the
kernel team is going to maintain the kernel images there sh
On Fri, Feb 24, 2006 at 04:37:56PM +0100, Bastian Blank wrote:
Hi,
> > This is great! In the meantime we are working on uploading xen 3.0 to
> > unstable,
> > and our packages I think are almost ready too!
>
> This is insufficient. Either maintain both 3.0 and unstable or none. In
> the meantim
Bastian Blank wrote:
Hi!
> The debian kernel team will maintain xen images with the linux-2.6
> source. I currently prepare both xen 3.0 and unstable packages, which
> can be hopefully uploaded today. Maintainer will be the kernel team, as
> there are heavy dependencies between xen and the kernel
19 matches
Mail list logo
