> >
> > Thanks for the analysis. The reason I originally posted is to see why
> > this might have popped up in 8.x, as it never happened in 7.x.
> > -- George Mitchell
> >
> I suspect two things make this occur more frequently with 8.x. One is
> that it does IPv6 first (I suspect IPv6 wasn't enabl
>
> Thanks for the analysis. The reason I originally posted is to see why
> this might have popped up in 8.x, as it never happened in 7.x.
> -- George Mitchell
>
I suspect two things make this occur more frequently with 8.x. One is
that it does IPv6 first (I suspect IPv6 wasn't enabled by default
Am 09.03.2011 21:52, schrieb Josh Carroll:
> On Wed, Mar 9, 2011 at 12:15 PM, Thomas David Rivers
> wrote:
>>
>> Just installed a fresh 8.2-stable on a brand-spanking-new 64-bit
>> machine...
>>
>> But, when I try to build 32-bit programs I get problems linking,
>> and I stumbled onto PR bin/1391
On Wed, Mar 09, 2011 at 03:15:39PM -0500, Thomas David Rivers wrote:
> But, when I try to build 32-bit programs I get problems linking,
> and I stumbled onto PR bin/139146.
That one was closed as a duplicate of gnu/112215. I've forwarded your
email to GNATS with the followup redirected there.
mc
Thanks everyone! -B/usr/lib32 worked around the issue...
- Dave Rivers -
--
riv...@dignus.comWork: (919) 676-0847
Get your mainframe programming tools at http://www.dignus.com
___
freebsd-stable@freebsd.org mailing list
h
On Wed, Mar 9, 2011 at 12:15 PM, Thomas David Rivers wrote:
>
> Just installed a fresh 8.2-stable on a brand-spanking-new 64-bit
> machine...
>
> But, when I try to build 32-bit programs I get problems linking,
> and I stumbled onto PR bin/139146.
>
> The PR mentions this quick test:
>
> uname -s
Just installed a fresh 8.2-stable on a brand-spanking-new 64-bit
machine...
But, when I try to build 32-bit programs I get problems linking,
and I stumbled onto PR bin/139146.
The PR mentions this quick test:
uname -sr && echo "int main () { }" > t.c && gcc -v --help 2>&1 | grep m32 &&
gcc -
[1]If this email does not display correctly click = here
[2]3D""
EVERYBODY loves spring! Flowers bloom. The = weather turns
warmer. And summer is one season closer. It's the perfect time to
engage kids in the = interesting science of weather! It's also a good
time to discus
Hello,
Am 09.03.2011 um 14:28 schrieb Tom Evans:
> I don't think this is accurate. Prefetch was certainly disabled by
> default on 8.0 if you had 4GB of RAM or less, requiring the sysctl
> vfs.zfs.prefetch_disable=0 to be set if you wanted prefetch and had
> 4GB of RAM or less.
My configuration
Am 09.03.2011 14:28, schrieb Tom Evans:
> On Wed, Mar 9, 2011 at 12:51 PM, Jeremy Chadwick
> wrote:
>>
>> Otherwise, I can imagine that prefetching could cause what you describe,
>> which is enabled by default in 8.0 and 8.1 and auto-disables in 8.2 if
>> the amount of available memory is less tha
On Wed, Mar 9, 2011 at 12:51 PM, Jeremy Chadwick
wrote:
>
> Otherwise, I can imagine that prefetching could cause what you describe,
> which is enabled by default in 8.0 and 8.1 and auto-disables in 8.2 if
> the amount of available memory is less than 4GB.
>
I don't think this is accurate. Prefet
On Wed, Mar 09, 2011 at 11:56:49AM +0100, Matthias Andree wrote:
> Am 08.03.2011 12:48, schrieb Jeremy Chadwick:
> > On Tue, Mar 08, 2011 at 12:26:49PM +0100, Patrick M. Hausen wrote:
> >> we use a big JBOD and ZFS with raidz2 as the target
> >> for our nightly Amanda backups.
> >>
> >> I already s
On Wed, Mar 09, 2011 at 07:07:26AM -0500, George Mitchell wrote:
> On 03/09/11 03:09, Daniel Braniss wrote:
> >>Under 8.2-PRERELEASE (GENERIC kernel), about 15% of the times I boot up
> >>(with rpc.statd and rpc.lockd enabled in rc.conf), I get:
> >>
> >>Feb 4 07:31:11 wonderland rpc.statd: bindre
On 03/09/11 03:09, Daniel Braniss wrote:
Under 8.2-PRERELEASE (GENERIC kernel), about 15% of the times I boot up
(with rpc.statd and rpc.lockd enabled in rc.conf), I get:
Feb 4 07:31:11 wonderland rpc.statd: bindresvport_sa: Address already in use
Feb 4 07:31:11 wonderland root: /etc/rc: WARNI
Am 08.03.2011 12:48, schrieb Jeremy Chadwick:
> On Tue, Mar 08, 2011 at 12:26:49PM +0100, Patrick M. Hausen wrote:
>> we use a big JBOD and ZFS with raidz2 as the target
>> for our nightly Amanda backups.
>>
>> I already suspected that the fact that the FS was > 90% full might
>> be the cause of ou
On 09/03/2011, at 20:47, Marius Strobl wrote:
>> Is it possible to use some device.hints entry to prohibit the probing of
>> bge1?
>> I think that would be the easiest solution to the problem? Other suggestions
>> are of course welcome. I can provide more config details and dmesg output
>> if nee
On Mon, Mar 07, 2011 at 01:26:01PM +0100, Patrick M. Hausen wrote:
> Hi, all,
>
> I just discovered a minor problem when updating some rather dated
> systems from FreeBSD 6.x to 7.x or 8.x.
>
> The servers are Fujitsu Technology Solutions (former Fujitsu-Siemens)
> RX100 S4. The current generatio
On 3/8/11 11:52 PM, Dave Johnson wrote:
> Hi all
>
>
> An IPFW problem?
>
> An help gladly accepted
>
> It would appear Port 80 closed
>
> Ports 21 25 443 587 998 work well
>
>
> rc.conf
> defaultrouter="192.168.0.1"
> gateway_enable="YES"
> hostname="xxx.xxx.xxx"
> ifconfig_re0="inet 192.16
> Under 8.2-PRERELEASE (GENERIC kernel), about 15% of the times I boot up
> (with rpc.statd and rpc.lockd enabled in rc.conf), I get:
>
> Feb 4 07:31:11 wonderland rpc.statd: bindresvport_sa: Address already in use
> Feb 4 07:31:11 wonderland root: /etc/rc: WARNING: failed to start statd
>
> an
19 matches
Mail list logo
