Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

two spaces after a sentence

  • Loading branch information...
commit d4396aafb37111c8d96d0a7d4a10cc47aae34436 1 parent 37e3ade
itojun authored
Showing with 15 additions and 15 deletions.
  1. +2 −2 INSTALL
  2. +7 −7 PORTABILITY
  3. +6 −6 README
View
4 INSTALL
@@ -1,6 +1,6 @@
Installation procedure - preparation of the tree
KAME project
- $KAME: INSTALL,v 1.27 2001/07/11 00:53:25 itojun Exp $
+ $KAME: INSTALL,v 1.28 2001/07/23 15:07:47 itojun Exp $
Let's call the entire file-tree under this directory "the KAME tree".
@@ -63,7 +63,7 @@ perform "make obj" unless you are ready to tackle those troubles.
otherwise the include files and source code become out-of-sync.
1. See the "VERSION" file and identify a symbol name for your target
- operating system. For the rest of this document, we assume "netbsd"
+ operating system. For the rest of this document, we assume "netbsd"
for explanation.
2. Be sure to have the complete KAME tree. For certain platforms
View
14 PORTABILITY
@@ -1,6 +1,6 @@
Portability guideline
KAME project
- $KAME: PORTABILITY,v 1.60 2001/05/08 05:54:14 itojun Exp $
+ $KAME: PORTABILITY,v 1.61 2001/07/23 15:07:20 itojun Exp $
Source code in the "kame" directory will be shared among operating systems
@@ -266,7 +266,7 @@ across those possibilities.
- Developers are advised to use pedantic compilation options (like -Wall
-Werror). To configure default make settings, /etc/make.conf (freebsd),
/etc/mk.conf (netbsd/openbsd), and/or /usr/share/mk/sys.mk (bsdi) should be
- useful. Note, however, that the default compiler of bsdi3 (/usr/ucb/cc)
+ useful. Note, however, that the default compiler of bsdi3 (/usr/ucb/cc)
does not suppport the -Werror option.
Note that the meaning of -Wall is different across *BSD because *BSD use
@@ -279,9 +279,9 @@ across those possibilities.
- For portability in kernel networking code, look at kame/sys/net/net_osdep.h.
- The -interface modifier of the route(8) command does not take an
- argument except on FreeBSD. Also, the original FreeBSD's extension
+ argument except on FreeBSD. Also, the original FreeBSD's extension
has several bugs (although those bugs are fixed in the route command
- in the KAME kit). If you regard portability and stability, it would
+ in the KAME kit). If you regard portability and stability, it would
be better to use a mixture of the "change" operation and the -ifp
modifier of the route command.
@@ -292,15 +292,15 @@ across those possibilities.
# route change -inet6 default ::1 -ifp gif0
Note that the kernel code to perform the change operation assumes
- that gif0 has at least one IPv6 address. If you are not sure about
+ that gif0 has at least one IPv6 address. If you are not sure about
this, you might want to execute
# ifconfig gif0 up
before executing the route command.
BSDI4 users can take the following approach as well:
# route add -inet6 default ::1 -ifp gif0
- which would be much simpler. This is because BSDI4 has improved
- kernel code of handling routing sockets. We will eventually merge
+ which would be much simpler. This is because BSDI4 has improved
+ kernel code of handling routing sockets. We will eventually merge
this improvement into other OSes.
- (Not really a portability issue) Fixes/improvements to libpcap and tcpdump
View
12 README
@@ -1,6 +1,6 @@
README of KAME kit
KAME Project
- $KAME: README,v 1.57 2001/07/10 09:49:18 itojun Exp $
+ $KAME: README,v 1.58 2001/07/23 15:04:33 itojun Exp $
<<<Project Overview>>>
@@ -115,16 +115,16 @@ When you report bugs, please be sure to include the following information:
- (if necessary) IPv6/v4 connectivity status in your network
Don't try to *describe* your settings, just paste command output itself
-onto the report instead. A bad example is "I assigned a global address on
-my ethernet interface, but ping6 didn't work. Why?" No one will be
-able to answer this kind of question. Instead, you should type as follows:
+onto the report instead. A bad example is "I assigned a global address on
+my ethernet interface, but ping6 didn't work. Why?" No one will be
+able to answer this kind of question. Instead, you should type as follows:
# /usr/local/v6/sbin/ifconfig -a
-(paste the output. Again, the exact output is best. Do not try to
+(paste the output. Again, the exact output is best. Do not try to
describe the output by your own word)
# /usr/local/v6/sbin/ifconfig ne0 inet6 2001:200::1234 prefixlen 64 alias
(paste the output)
# /usr/local/v6/sbin/ifconfig -a
-(paste the output. The difference between the two "ifconfig -a" might
+(paste the output. The difference between the two "ifconfig -a" might
be important.)
# /usr/local/v6/sbin/ping6 -n 2001:300::1
(paste the output, including errors and warnings)
Please sign in to comment.
Something went wrong with that request. Please try again.