From: Quantum Scientific <Info@Quantum-Sci.com>
To: netdev@oss.sgi.com
Subject: Re: Kernel 2.6 IPV6 Busted
Date: Sun, 27 Feb 2005 10:29:02 -0600 [thread overview]
Message-ID: <200502271029.02532.Info@Quantum-Sci.com> (raw)
In-Reply-To: <20050228.011038.129063054.yoshfuji@linux-ipv6.org>
On Sunday 27 February 2005 10:10, YOSHIFUJI Hideaki / 吉藤英明 wrote:
> > usagi.snap.split-tool-s20050214.tar.bz2
> > ... however this has no kernel patch within.
> >
> > So I DLed
> > usagi.snap.kit-linux26-s20050214.tar.bz2
> > ... and no kernel patch here either. Only the kernel and tools. I would
have
> > to run a USAGI-specific kernel, in order to have proper IPV6 support. I
must
> > stay with the Debian kernel.
>
> I believe you should cry at debian-ipv6 list.
>
> And, you can find usagi kernel patch in split directory, and
> you can even find (unsupported) daily kernel snapshot (diff).
I have 'cried' to the Debian list, and no response. (except viruses)
And I have looked at every single file in the Split directory, and there are
absolutely no .diff files. .diff files are how patch files are identified in
*nix, of course. I thought, maybe I should copy the kernel files into my
kernel tree by hand, for building. But this doesn't make sense because the
only file under usagi-split/kernel/usagi/net/ipv6 is utils.c . This is not
an IPV6 stack, nor ip6tables. I see lots of apps, which likely have the
USAGI improvements, but no kernel stack, patch, ipv6filters, etc. And no
mention of patching a non-USAGI kernel. Split 20050214 appears to be
utilities only.
Please show where could I be going wrong?
Carl Cook
next prev parent reply other threads:[~2005-02-27 16:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-27 15:28 Kernel 2.6 IPV6 Busted Quantum Scientific
2005-02-27 16:10 ` YOSHIFUJI Hideaki / 吉藤英明
2005-02-27 16:29 ` Quantum Scientific [this message]
2005-02-27 17:28 ` YOSHIFUJI Hideaki / 吉藤英明
2005-02-27 18:08 ` Quantum Scientific
2005-03-15 5:00 ` Horms
2005-02-27 17:40 ` Andre Tomt
2005-02-27 18:20 ` Quantum Scientific
2005-02-27 18:59 ` Jeff Garzik
2005-02-27 19:10 ` Quantum Scientific
2005-02-27 19:58 ` Jeff Garzik
2005-02-27 20:10 ` Quantum Scientific
2005-02-27 21:35 ` David S. Miller
2005-03-01 10:07 ` Denis Vlasenko
2005-03-01 13:50 ` Quantum Scientific
2005-03-01 16:26 ` Jeff Garzik
2005-03-01 20:46 ` Tomasz Torcz
2005-03-01 23:55 ` Quantum Scientific
2005-03-02 14:02 ` Denis Vlasenko
2005-03-02 19:12 ` Jeff Garzik
2005-03-01 21:50 ` Andre Tomt
2005-03-01 23:59 ` Quantum Scientific
2005-02-27 18:12 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200502271029.02532.Info@Quantum-Sci.com \
--to=info@quantum-sci.com \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).