> >Also, usual tools, rlogin, rlogind, rsh, rshd, telnet,
> >telnetd, ftp, ftpd, and inetd are already IPv6 capable.
>
> Hm. rlogin and rsh attempt to connect, but my inetd isn't listening;
> do I have to update inetd.conf to get inetd to listen on IPv6 addresses?
Yes, if tcp, please specify
> Yesterday, I tested ping6 between two hosts using link-local
> addresses, and it worked. The week before, however, I couldn't get a
> different machine to transmit packets when it had IPv6 in the kernel.
> I'm not sure about the relative dates involved.
>
> -GAWollman
Some driver seems to hav
>Also, usual tools, rlogin, rlogind, rsh, rshd, telnet,
>telnetd, ftp, ftpd, and inetd are already IPv6 capable.
Hm. rlogin and rsh attempt to connect, but my inetd isn't listening;
do I have to update inetd.conf to get inetd to listen on IPv6 addresses?
telnet can't parse ::1:
emachine% teln
i've had ipv6 working with freenet6.net.. well, partially working, the
full feature should work fine soon though.
the tunneling through gif works, and i'm about to test IPSec with IPv4.
more testing is in order though, so, i'll try to pass on some more info
when i have it.
-- jan
On Thu, 27 J
< said:
> Is there a quick primer on getting IPv6 up and running? I built a
> kernel with INET6 and the ipsec stuff, and my interfaces now have IPv6
> addresses, but no userland apps seem to be able to parse IPv6 addresses,
> e.g. "ping ::1" says "no such host". (This is 4.0-2125-CURRENT).
> >Test IPv6 support! You've all been asking for it, test it.
>
> Is there a quick primer on getting IPv6 up and running? I built a
> kernel with INET6 and the ipsec stuff, and my interfaces now have IPv6
> addresses, but no userland apps seem to be able to parse IPv6 addresses,
> e.g. "ping ::
>Test IPv6 support! You've all been asking for it, test it.
Is there a quick primer on getting IPv6 up and running? I built a
kernel with INET6 and the ipsec stuff, and my interfaces now have IPv6
addresses, but no userland apps seem to be able to parse IPv6 addresses,
e.g. "ping ::1" says "no
< said:
> Comparing LINT and GENERIC is made more difficult by the significantly
> different ordering. Is there some good reason for this, or would an
> offer of GENERIC re-written into the same order as LINT be accepted?
Speaking as the person who attempted to impart some semblance of order
to
In article <[EMAIL PROTECTED]>,
Rodney W. Grimes <[EMAIL PROTECTED]> wrote:
> Ohhh.. and please update your cvsup-mirror stats, the sizes of things are way
> way way out of date:
I think I'm just going to remove the stats and replace them with a URL
for an automatically-updated list. It's pract
On 2000-Jan-23 07:03:10 +1100, Jeroen Ruigrok/Asmodai <[EMAIL PROTECTED]> wrote:
>Also, are GENERIC and LINT in sync?
Comparing LINT and GENERIC is made more difficult by the significantly
different ordering. Is there some good reason for this, or would an
offer of GENERIC re-written into the sa
> > Also, are GENERIC and LINT in sync?
>
> Do we want a LINT for alpha too?
I guess so. I'm in favour of it. We could start of with simply copying
GENERIC.
Nick
--
[EMAIL PROTECTED]
[EMAIL PROTECTED] USB project
http://www.etla.net/~n_hibma/
To Unsub
On Sat, 22 Jan 2000, John Polstra wrote:
> It works for me. Not all mirrors carry the more esoteric
> collections like gnats. I know that cvsup[15678] carry it. I think
> cvsup2 doesn't, and I'm not sure about 3 and 4.
Hah, I forgot to delete the tag=. line. Oops :)
- alex
To Unsubscribe
> In article ,
> Alex Zepeda <[EMAIL PROTECTED]> wrote:
> >
> > I'm looking at /usr/{src,}/share/examples/cvsup/gnats-supfile, and as
> > "equipped" it's not working (well it goes through the motions but checks
> > out no files). Hmm.
>
> It w
In article ,
Alex Zepeda <[EMAIL PROTECTED]> wrote:
>
> I'm looking at /usr/{src,}/share/examples/cvsup/gnats-supfile, and as
> "equipped" it's not working (well it goes through the motions but checks
> out no files). Hmm.
It works for me. No
On Fri, 21 Jan 2000, Nick Hibma wrote:
> - writing manpages (or send a skeleton of to someone who will
> finish it)
> - update HARDWARE.TXT
> - check UPDATING
> - replace controller with device in all manpages
> - improving manpages in general
> - FIXING
> On Sat, Jan 22, 2000 at 09:01:36PM +0100, Jeroen Ruigrok/Asmodai wrote:
> > -On [2122 15:22], Nick Hibma ([EMAIL PROTECTED]) wrote:
>
> > > - update HARDWARE.TXT
>
> Urgh...
>
> > doing them or mdoc if someone wrote the bare text. But if someone takes
> > this task from my shoulders,
On Sat, Jan 22, 2000 at 09:01:36PM +0100, Jeroen Ruigrok/Asmodai wrote:
> -On [2122 15:22], Nick Hibma ([EMAIL PROTECTED]) wrote:
> > - update HARDWARE.TXT
Urgh...
> doing them or mdoc if someone wrote the bare text. But if someone takes
> this task from my shoulders, I'd be happy.
>
-On [2122 15:22], Nick Hibma ([EMAIL PROTECTED]) wrote:
>
> - writing manpages (or send a skeleton of to someone who will
> finish it)
Damn right! =)
> - update HARDWARE.TXT
> - check UPDATING
> - replace controller with device in all manpages
I think I solved
we all should have time to fix up all those little things that needed to
be done anyway. Like:
- writing manpages (or send a skeleton of to someone who will
finish it)
- update HARDWARE.TXT
- check UPDATING
- replace controller with device in all manpages
19 matches
Mail list logo