To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
or, via email, send a message with subject or body 'help' to
freebsd-sta...@freebsd.org
You can reach the person managing the list at
freebsd-st...@freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-stable digest..."
Today's Topics:
1. 6.4-RELEASE missing from mirrors (David Boyd)
2. Rent in Belgrade // Short term accommodation
(RentBEO Apartments in Belgrade)
3. panic during work with jailed postgresql8.4 (Oleg Lomaka)
4. Results of BIND RFC (Doug Barton)
5. Re: Results of BIND RFC (Peter Thoenen)
----------------------------------------------------------------------
Message: 1
Date: Thu, 1 Apr 2010 11:07:43 -0400
From: "David Boyd" <David...@insightbb.com>
Subject: 6.4-RELEASE missing from mirrors
To: <freebsd...@freebsd.org>
Message-ID: <OJEBKOFDEOADELCOBJC...@insightbb.com>
Content-Type: text/plain; charset="iso-8859-1"
The link (actually file) called "6.4 moved to ftp-archive" is missing from
most/all mirrors.
We have been using these files to "follow" the releases when they move.
It works as long as the "6.4 moved to ftp-archive" file is present.
Please help.
Thanks.
------------------------------
Message: 2
Date: Thu, 1 Apr 2010 18:47:18 +0200
From: "RentBEO Apartments in Belgrade" <off...@rentbeo.com>
Subject: Rent in Belgrade // Short term accommodation
To: freebsd...@freebsd.org
Message-ID: <85jssn$hv...@e12mailgw05.isp.nadlanu.com>
Content-Type: text/plain; charset="us-ascii"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logo_beorent.jpg
Type: application/octet-stream
Size: 18601 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20100401/8ac173e5/logo_beorent-0001.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mid_200912271810030.jpg
Type: application/octet-stream
Size: 4304 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20100401/8ac173e5/mid_200912271810030-0001.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mid_201001211425500.jpg
Type: application/octet-stream
Size: 4453 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20100401/8ac173e5/mid_201001211425500-0001.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mid_201001190915070.jpg
Type: application/octet-stream
Size: 5489 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20100401/8ac173e5/mid_201001190915070-0001.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mid_200912271743380.jpg
Type: application/octet-stream
Size: 5040 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20100401/8ac173e5/mid_200912271743380-0001.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mid_201003161746350.jpg
Type: application/octet-stream
Size: 4616 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20100401/8ac173e5/mid_201003161746350-0001.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mid_201001221956000.jpg
Type: application/octet-stream
Size: 4701 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20100401/8ac173e5/mid_201001221956000-0001.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mid_201001222004040.jpg
Type: application/octet-stream
Size: 4902 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20100401/8ac173e5/mid_201001222004040-0001.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rentbeo_10.jpg
Type: application/octet-stream
Size: 9658 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20100401/8ac173e5/rentbeo_10-0001.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: eng.jpg
Type: application/octet-stream
Size: 9036 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20100401/8ac173e5/eng-0001.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 200810191904530.jpg
Type: application/octet-stream
Size: 809 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20100401/8ac173e5/200810191904530-0001.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 201001131425520.jpg
Type: application/octet-stream
Size: 833 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20100401/8ac173e5/201001131425520-0001.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 200912051454130.jpg
Type: application/octet-stream
Size: 831 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20100401/8ac173e5/200912051454130-0001.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 201001131428000.jpg
Type: application/octet-stream
Size: 772 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20100401/8ac173e5/201001131428000-0001.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 201002131706420.jpg
Type: application/octet-stream
Size: 779 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20100401/8ac173e5/201002131706420-0001.obj
------------------------------
Message: 3
Date: Thu, 1 Apr 2010 21:18:20 +0300
From: Oleg Lomaka <oleg....@gmail.com>
Subject: panic during work with jailed postgresql8.4
To: freebsd...@freebsd.org
Message-ID: <44FD9C14-7114-4270...@gmail.com>
Content-Type: text/plain; charset="us-ascii"
Hello,
I have a kernel panic when connect to postgresql8.4 server installed in one of jails from another jail. It's 100% reproducible.
Also I have tried to connect from host machine to jailed pg server. That way it works fine without crash.
Server configuration uses geli and zfs. Four disks encrypted using geli. And raidz2 is using ad8.eli, ad10.eli, ad12.eli, ad14.eli providers. All jails located at this raidz2 pool.
Also I use ezjail for jails management. And it uses NFS to mount directories with base system.
atal double fault
rip = 0xffffffff8063510a
rsp = 0xffffff80eaec5f50
rbp = 0xffffff80eaec6040
cpuid = 1; apic id = 02
panic: double fault
cpuid = 1
Uptime: 7m11s
Physical memory: 8169 MB
uname -a
FreeBSD cerberus.regredi.com 8.0-STABLE FreeBSD 8.0-STABLE #7 r206031: Thu Apr 1 13:43:57 EEST 2010 ro...@cerberus.regredi.com:/usr/obj/usr/src/sys/GENERIC amd64
Link to dmesg.boot:
http://docs.google.com/leaf?id=0B-irbkAqk9i7OGY2ZWJiODgtOWJmMy00NDQ1LTliZDctZjU3N2YwNmMxNjZl&hl=en
Link to kernel core backtrace:
http://docs.google.com/Doc?docid=0AeirbkAqk9i7ZGc5Yzc2ZndfM2M4NzYydmRw&hl=en
Can I help to spot this trouble by providing additional info?
Thanks.
------------------------------
Message: 4
Date: Thu, 01 Apr 2010 15:16:59 -0700
From: Doug Barton <do...@FreeBSD.org>
Subject: Results of BIND RFC
To: freebs...@FreeBSD.org, freebsd...@FreeBSD.org,
freebsd...@FreeBSD.org
Message-ID: <4BB51B5B...@FreeBSD.org>
Content-Type: text/plain; charset=ISO-8859-1
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
Greetings,
SUMMARY
On February 21 I sent a message to freebs...@FreeBSD.org detailing
the current state of BIND on FreeBSD, and plans for the future. You can
see that message here:
http://lists.freebsd.org/pipermail/freebsd-arch/2010-February/009908.html
In that message I asked for feedback on my plans for dealing with BIND
in the base. There wasn't much response on the lists, however I did
receive a great deal of response privately, all more or less to the
effect of, "Do we really need to continue having BIND in the base at
all?" After careful consideration and private discussion about this
issue the conclusion has been reached that the answer to this question
is, "No." Therefore we will be removing BIND from the FreeBSD base.
BACKGROUND
"Back in the day" when the FreeBSD project started there was really only
one show in the DNS town, BIND. In the last 10 years several truly
viable, first-class DNS options have been developed, in both the
authoritative and resolving server spaces. There are ports available for
each of these options, and many FreeBSD users take advantage of them.
There are of course also ports available for all supported BIND
versions, as well as dns/bind9 for BIND version 9.3 which has been
EOL'ed by ISC but is still in FreeBSD version 6.
This also leads to the issue mentioned in the post above, the
desynchronization between FreeBSD and ISC release schedules. While
FreeBSD 6 is scheduled to EOL in November of this year, it contains BIND
version 9.3.6-P1, which has long been EOL. There are a number of
problems related to upgrading the version of BIND in a release branch of
FreeBSD. Given the ease with which FreeBSD users can upgrade BIND with
the ports tree, and given the characteristics of the vulnerabilities
that have come to light with BIND 9.3.x to date, this hasn't been a
problem. There is no guarantee that this will continue to be the case.
This problem will reappear again in FreeBSD version 7 with BIND 9.4, and
FreeBSD version 8 with BIND 9.6.
PROS
This change will have several advantages.
1) Users of all FreeBSD versions will be able to have easy access to the
latest versions of BIND, and an easy upgrade path that does not involve
a full OS upgrade.
2) The release synchronization problem mentioned above will no longer be
a problem.
3) Users of other DNS solutions will no longer need to customize their
build using the various WITH/WITHOUT_BIND* knobs.
CONS
Of course this change will have some costs. Users of named who rely on
the current defaults will have some change management to deal with,
however the costs will be minimal. The one area that has come up
repeatedly in previous discussions about this topic is that users like
having access to the command line tools dig, host, and nslookup. To deal
with that issue I will be creating a bind-tools port so that those who
want just those tools can easily add them, without the overhead of the
rest of the BIND suite. If anyone has suggestions for other BIND tools
that should be included in the port, please let me know.
IMPLEMENTATION TIMELINE
I will be removing BIND from HEAD today. Removal from the other branches
will occur far enough in advance of their upcoming releases to ensure
that the users have a chance to shake things out first. I'll also be
committing the bind-tools and bind-config ports today so that users will
continue to have easy access to the work I've done on named.conf,
rc.d/named, etc.
I have been maintaining BIND in the base for almost 8 years now, and
while it's been challenging in a lot of ways, it's also been a great
privilege to be able to help the FreeBSD community in this way. I can't
say that I'll miss the drama of src updates though. :)
Many happy returns of the day,
Doug
- --
... and that's just a little bit of history repeating.
-- Propellerheads
Improve the effectiveness of your Internet presence with
a domain name makeover! http://SupersetSolutions.com/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (FreeBSD)
iEYEAREDAAYFAku1G1sACgkQyIakK9Wy8PuPgQCfdrhgscMQ+KPLcoRXx66f4f6M
T8wAniZqULdwM+4oRsbOkFSDZIceWn0u
=Syor
-----END PGP SIGNATURE-----
------------------------------
Message: 5
Date: Thu, 1 Apr 2010 15:30:20 -0700 (PDT)
From: Peter Thoenen <peter....@yahoo.com>
Subject: Re: Results of BIND RFC
To: freebs...@FreeBSD.org, freebsd...@FreeBSD.org,
freebsd...@FreeBSD.org, Doug Barton <do...@FreeBSD.org>
Message-ID: <328862....@web111402.mail.gq1.yahoo.com>
Content-Type: text/plain; charset=us-ascii
May I only hope this is legit and not a April Fool's joke :)
------------------------------
End of freebsd-stable Digest, Vol 350, Issue 5
**********************************************