Re: ipv6 related warnings

Kevin Oberman schrieb am 2009-09-28:
> > Date: Mon, 28 Sep 2009 15:24:02 +0200 (CEST)
> > From: Alexander Best <alexbestms_at_math.uni-muenster.de>
> > Sender: owner-freebsd-current_at_freebsd.org

> > Dag-Erling Smørgrav schrieb am 2009-09-28:
> > > Andriy Gapon <avg_at_icyb.net.ua> writes:
> > > > Dag-Erling Smørgrav <des_at_des.no> writes:
> > > > > No, you can build a *kernel* without IPv6, just not userland.
> > > > > Parts
> > > > > of userland will respect WITHOUT_INET6, others won't, and
> > > > > others
> > > > > yet
> > > > > will build but not run correctly.
> > > > So shouldn't those disrespecting parts of userland be fixed?

> > > Why?  In most (userland) cases, it takes more work to write code
> > > that
> > > supports IPv4 but not IPv6 than to write code that supports both.

> > > > Besides, returning to the original post, those messages weren't
> > > > there
> > > > just a few days ago, this is a new addition.

> > > ...if by "just a few days" you mean "two weeks".  If this really
> > > is
> > > "a
> > > new addition", it dates back to one of hrs_at_'s commits on
> > > 2009-09-13.
> > > However, the most likely cause of the OP's problem is incorrect
> > > use
> > > of
> > > mergemaster.  If he did indeed run "mergemaster -p" and
> > > "mergemaster
> > > -i", but nothing more, his /etc is completely out of sync.

> > mergemaster -p and mergemaster -i aren't sufficient to sync /etc
> > with
> > /usr/src/etc? but that's what UPDATING recommends.

> mergemaster -i (or, for sanity, -iUF) is adequate as long as the
> proper
> things are done when mergemaster notes a difference to be merged. But
> there is nothing "wrong" with using just '-i'. The real question is
> whether you install, delete, or merge any of the changes mergemaster
> reports.

> If you always install, you will probably break localizations. If you
> always skip or delete, you will end up with a /etc that is not going
> to
> work right.

> mergemaster is a wonderful tool as anyone who ran FreeBSD 2.2 or 3
> can
> tell you, but it is not a panacea. You still need to take enough time
> to
> properly evaluate each merge and DTRT.

> (And, to be clear, I have no reason to assume that you did not DTRT.)

just to clear things up. i just did `mergemaster -i` to see which files from
/etc and /usr/src/etc i'm getting asked about (which means they differ).
here's the list:

--- /boot/device.hints  2009-08-03 18:52:42.000000000 +0200
+++ ./boot/device.hints 2009-09-28 22:21:46.000000000 +0200

--- /etc/bluetooth/hcsecd.conf  2009-08-12 15:19:10.000000000 +0200
+++ ./etc/bluetooth/hcsecd.conf 2009-09-28 22:21:45.000000000 +0200

--- /etc/bluetooth/hosts        2009-05-03 22:03:57.000000000 +0200
+++ ./etc/bluetooth/hosts       2009-09-28 22:21:45.000000000 +0200

--- /etc/mail/freebsd.mc        2009-09-12 11:17:23.000000000 +0200
+++ ./etc/mail/freebsd.mc       2009-09-28 22:21:46.000000000 +0200

--- /etc/mail/freebsd.cf        2009-09-12 11:17:28.000000000 +0200
+++ ./etc/mail/freebsd.cf       2009-09-28 22:21:46.000000000 +0200

--- /etc/mail/freebsd.submit.cf 2009-09-12 11:08:55.000000000 +0200
+++ ./etc/mail/freebsd.submit.cf        2009-09-28 22:21:46.000000000 +0200

--- /etc/mail/sendmail.cf       2009-09-27 16:35:24.000000000 +0200
+++ ./etc/mail/sendmail.cf      2009-09-28 22:21:46.000000000 +0200

--- /etc/mail/submit.cf 2009-09-27 16:35:24.000000000 +0200
+++ ./etc/mail/submit.cf        2009-09-28 22:21:46.000000000 +0200

--- /etc/crontab        2009-09-24 18:13:24.000000000 +0200
+++ ./etc/crontab       2009-09-28 22:21:45.000000000 +0200

--- /etc/devd.conf      2009-09-12 02:38:27.000000000 +0200
+++ ./etc/devd.conf     2009-09-28 22:21:45.000000000 +0200

--- /etc/ftpusers       2009-06-13 22:35:46.000000000 +0200
+++ ./etc/ftpusers      2009-09-28 22:21:45.000000000 +0200

--- /etc/group  2009-09-08 11:23:58.000000000 +0200
+++ ./etc/group 2009-09-28 22:21:45.000000000 +0200

--- /etc/hosts  2009-08-16 16:59:41.000000000 +0200
+++ ./etc/hosts 2009-09-28 22:21:45.000000000 +0200

--- /etc/login.conf     2009-07-01 12:49:55.000000000 +0200
+++ ./etc/login.conf    2009-09-28 22:21:45.000000000 +0200

--- /etc/motd   2009-09-27 16:39:30.000000000 +0200
+++ ./etc/motd  2009-09-28 22:21:45.000000000 +0200

--- /etc/shells 2009-09-27 17:19:31.000000000 +0200
+++ ./etc/shells        2009-09-28 22:21:45.000000000 +0200

--- /etc/sysctl.conf    2009-08-16 13:45:47.000000000 +0200
+++ ./etc/sysctl.conf   2009-09-28 22:21:45.000000000 +0200

--- /etc/ttys   2009-06-16 15:14:43.000000000 +0200
+++ ./etc/ttys  2009-09-28 22:21:45.000000000 +0200

--- /etc/master.passwd  2009-09-08 11:23:58.000000000 +0200
+++ ./etc/master.passwd 2009-09-28 22:21:45.000000000 +0200

so to me this means that apart from these files /etc and /usr/src/etc are in
sync and i'm quite sure none of these files have anything to do with ipv6
apart from sysctl.conf, but as you can see:

--- /etc/sysctl.conf    2009-08-16 13:45:47.000000000 +0200
+++ /usr/src/etc/sysctl.conf    2009-09-23 21:55:11.000000000 +0200
_at__at_ -7,12 +7,3 _at__at_
 # Uncomment this to prevent users from seeing information about processes
 that
 # are being run under another UID.
 #security.bsd.see_other_uids=0
-#
-kern.ipc.shmmax=67108864
-kern.ipc.shmall=32768
-vfs.usermount=1
-net.inet.tcp.blackhole=1
-net.inet.udp.blackhole=1
-hw.snd.vpc_autoreset=0
-kern.ipc.shm_allow_removed=1
-compat.linux.osrelease=2.6.16

i have nothing ipv6 related in that file.

as another reference i'm posting all the options i have in my /etc/src.conf:

WITHOUT_ACCT=true
WITHOUT_AMD=true
WITHOUT_APM=true
WITHOUT_ATM=true
WITHOUT_AUDIT=true
WITHOUT_BIND=true
WITHOUT_BSNMP=true
WITHOUT_CDDL=true
WITHOUT_CTM=true
WITHOUT_FLOPPY=true
WITHOUT_FREEBSD_UPDATE=true
WITHOUT_GAMES=true
WITHOUT_GPIB=true
WITH_IDEA=true
WITHOUT_INET6=true
WITHOUT_IPFILTER=true
WITHOUT_IPFW=true
WITHOUT_IPX=true
WITHOUT_JAIL=true
WITHOUT_LPR=true
WITHOUT_MAILWRAPPER=true
WITHOUT_NCP=true
WITHOUT_NDIS=true
WITHOUT_NETCAT=true
WITHOUT_NIS=true
WITHOUT_NLS=true
WITHOUT_NLS_CATALOGS=true
WITHOUT_NS_CACHING=true
WITHOUT_PAM=true
WITHOUT_PF=true
WITHOUT_PORTSNAP=true
WITHOUT_PPP=true
WITHOUT_QUOTAS=true
WITHOUT_RCMDS=true
WITHOUT_RCS=true
WITHOUT_ROUTED=true
WITHOUT_SLIP=true
WITHOUT_TCSH=true
WITHOUT_TELNET=true
WITHOUT_WPA_SUPPLICANT_EAPOL=true
WITHOUT_CDDL=true

so...as far as i can see there's no way of building an ipv6-unaware world any
longer. it seems like the WITHOUT_INET6 option has become obsolete.

if this is the case the option should completely be removed from the whole
source and defining it should no longer trigger any ifdef's. also it should be
removed from `man src.conf` and a note should be added to UPDATING telling
users that WITHOUT_INET6 won't work any longer.

if however WITHOUT_INET6 as an option should remain supported and infact let
the user build an ipv6-unaware world this should be fixed imo.

cheers.
alex