Hi,
from r206082 on: $Subject
Make sure to read UPDATING (short: make sure there is no WITH_CTF in
src.conf or make.conf).
Bye,
Alexander.
--
You will save yourself a lot of needless worry if you
don't burn your bridges until you come to them.
http://www.Leidinger.netAlexander @ Leidin
On 02.04.2010 9:24, Stanislav Sedov wrote:
While it certainly might make sense to drop BIND out of the base, I'm not
sure dropping bind tools as well from it is the best decision. How hard
it will be to continue maintaining bind tools inside the base (so the
critical ones like dig and nslookup s
On Thu, 01 Apr 2010 15:16:59 -0700
Doug Barton mentioned:
>
> 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 d
Hi, Tom,
On Thu, Apr 1, 2010 at 12:59 PM, Tom Uffner wrote:
[...]
> i realize this. i was just adding to the list of ports that no longer
> build after this change. ghostscript is kind of important for print
> support.
>
> i doubt this is "right" either, but it is a quick & dirty way to
> make mp
On 04/01/2010 23:48, Randy Bush wrote:
>> May I only hope this is legit and not a April Fool's joke :)
>
> actually, as an unbound user, i would be quite happy to have bind
> removed. bloated, ever-buggy, config religion, ...
>
> randy
At least I hope that this will be removed and added to the
> May I only hope this is legit and not a April Fool's joke :)
actually, as an unbound user, i would be quite happy to have bind
removed. bloated, ever-buggy, config religion, ...
randy
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.
i have a year old 8 soekris system i am about to upgrade. it is pppoe
externally, and has a bridged natted wireless/ether internal net.
..
||
| b --wlan0|
| r| 192.168.0.0/24
ext ii
May I only hope this is legit and not a April Fool's joke :)
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Greetings,
SUMMARY
On February 21 I sent a message to freebsd-a...@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
Xin LI writes:
> Tom Uffner writes:
> > Michael Butler writes:
> > > This breaks most (if not all) of the QT4-dependent ports for the
> > > lack of a definition of "off64_t".
> > it also breaks multimedia/mplayer, graphics/ImageMagick, and
> > print/ghostscript8 & everything that depends on it.
On 2010-04-01 21:02, Robert Noland wrote:
After a while I've noticed some SMART errors on ad1, so I've booted
machine
with seatools for dos and made long test. One bad sector was found and
reallocated, nothing to worry about.
As I was in seatools already, I've decided to adjust LBA size on
t
On Thu, Apr 1, 2010 at 12:59 PM, Tom Uffner wrote:
> Xin LI wrote:
>>
>> On Wed, Mar 31, 2010 at 6:56 PM, Tom Uffner wrote:
>>>
>>> Michael Butler wrote:
>>>
This breaks most (if not all) of the QT4-dependent ports for the lack of
a definition of "off64_t".
>>>
>>> it also breaks multim
On 2010-04-01 19:34, Marcel Moolenaar wrote:
On Apr 1, 2010, at 6:23 AM, Bartosz Stec wrote:
Unfortunately it wasn't so easy. First of all system booted, and as I expected
kernel message shows GPT error on ad1. Zpool was degraded but alive and
kicking. However, when I tried to execute any
Xin LI wrote:
On Wed, Mar 31, 2010 at 6:56 PM, Tom Uffner wrote:
Michael Butler wrote:
This breaks most (if not all) of the QT4-dependent ports for the lack of
a definition of "off64_t".
it also breaks multimedia/mplayer, graphics/ImageMagick, and
print/ghostscript8 & everything that depend
Robert Noland wrote:
Olivier Smedts wrote:
2010/4/1 Bartosz Stec :
Hello ZFS and GPT hackers :)
I'm sending this message to both freebsd-current and freebsd-fs
because it
doesn't seems to be a CURRENT-specific issue.
Yesterday I tried to migrate my mixed UFS/RAIDZ config to clean RAIDZ
Bartosz,
One thing to remember is that GPT stores it's header and entry tables at
both the start and end of the disk for redundancy.
As far as I understand it, by making the disk physically smaller, the
GPT primary header and entry data would have become invalid as the last
partition would no
Olivier Smedts wrote:
2010/4/1 Bartosz Stec :
Hello ZFS and GPT hackers :)
I'm sending this message to both freebsd-current and freebsd-fs because it
doesn't seems to be a CURRENT-specific issue.
Yesterday I tried to migrate my mixed UFS/RAIDZ config to clean RAIDZ with
GPT boot. I've follow
On 01/-10/-28163 20:59, Jack Vogel wrote:
OH, as to my last statement, the code in CURRENT will NOT work on 8.0
RELEASE,
it would require a change to sys/conf/files, and it also has a fix in the
stack that is not
in RELEASE. SO taking the latest would require you take the whole tree.
Jack
On W
2010/4/1 Bartosz Stec :
> Hello ZFS and GPT hackers :)
>
> I'm sending this message to both freebsd-current and freebsd-fs because it
> doesn't seems to be a CURRENT-specific issue.
>
> Yesterday I tried to migrate my mixed UFS/RAIDZ config to clean RAIDZ with
> GPT boot. I've following mostly this
On Apr 1, 2010, at 6:23 AM, Bartosz Stec wrote:
> Unfortunately it wasn't so easy. First of all system booted, and as I
> expected kernel message shows GPT error on ad1. Zpool was degraded but alive
> and kicking. However, when I tried to execute any gpart command on ad1, it
> return:
>
> a
On Thu, Apr 1, 2010 at 10:30 AM, Thomas Gellekum wrote:
>
> Jack Vogel wrote:
> > The device subfamily on those motherboards is called PCH, and its only in
> > the em driver as of
> > last December, The CVS delta of if_em is 1.27. You can either update to
> > STABLE/8 or CURRENT.
> > If you wish
Yup, gonna MFC the code from CURRENT to STABLE/8 first thing next week, at
least that's my plan.
Sorry, I thought STABLE/8 already had PCH in it, my bad. I checked and the
ALTQ fix is in the tree, so pulling the directory from HEAD and adding it to
STABLE/8 should work fine.
MFC will be coming fi
2010/4/1 Bartosz Stec :
> Hello ZFS and GPT hackers :)
>
> I'm sending this message to both freebsd-current and freebsd-fs because it
> doesn't seems to be a CURRENT-specific issue.
>
> Yesterday I tried to migrate my mixed UFS/RAIDZ config to clean RAIDZ with
> GPT boot. I've following mostly this
Jack Vogel wrote:
> The device subfamily on those motherboards is called PCH, and its only in
> the em driver as of
> last December, The CVS delta of if_em is 1.27. You can either update to
> STABLE/8 or CURRENT.
> If you wish to just pull the e1000 driver directory it should work fine in
> 8.0 RE
Thanks. I'll give STABLE/8 a try.
Jack Vogel wrote:
OH, as to my last statement, the code in CURRENT will NOT work on 8.0
RELEASE,
it would require a change to sys/conf/files, and it also has a fix in
the stack that is not
in RELEASE. SO taking the latest would require you take the whole tree
Hello ZFS and GPT hackers :)
I'm sending this message to both freebsd-current and freebsd-fs because
it doesn't seems to be a CURRENT-specific issue.
Yesterday I tried to migrate my mixed UFS/RAIDZ config to clean RAIDZ
with GPT boot. I've following mostly this guide:
http://wiki.freebsd.org
- Original Message
> From: Ganbold
> To: PseudoCylon
> Cc: freebsd-current@freebsd.org
> Sent: Wed, March 31, 2010 8:08:29 AM
> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
>
> Does stock run(4) support hostap mode yet?
No. There were some bugs and I thought I fixed th
27 matches
Mail list logo
