On Sat, Oct 22, 2005 at 07:24:35PM -0700, Brandon Fosdick wrote:
> Dick Hoogendijk wrote:
> >>Oops, it seems this feature is in 7-CURRENT only. If the appropiate
> >>person is reading this, why isnt something like that available in 6? I
> >>think it would be a very useful feature.
> >
> >
> > Wh
Dick Hoogendijk wrote:
>>Oops, it seems this feature is in 7-CURRENT only. If the appropiate
>>person is reading this, why isnt something like that available in 6? I
>>think it would be a very useful feature.
>
>
> What a shame. You made me glad for a very short time. This seemed to be
> the opt
On Sat, Oct 22, 2005 at 03:41:33PM +0200, dick hoogendijk wrote:
> On Fri, 21 Oct 2005 15:30:52 -0400
> Kris Kennaway <[EMAIL PROTECTED]> wrote:
>
> > > But he old libraries are still on the system than, aren't they?
> > > Or will they not be used and if not, why?
> >
> > Use libchk and pkg_which
On 22 Oct Mike Jakubik wrote:
> On Sat, October 22, 2005 12:25 pm, Mike Jakubik wrote:
>
> > You can run make check-old in /usr/src.
> >
> Oops, it seems this feature is in 7-CURRENT only. If the appropiate
> person is reading this, why isnt something like that available in 6? I
> think it would
On Sat, October 22, 2005 12:25 pm, Mike Jakubik wrote:
> You can run make check-old in /usr/src.
>
>
> # check-old - Print a list of old files/directories in the
> system. # delete-old - Delete obsolete files and directories
> interactively. # delete-old-libs - Delete obsole
On Sat, October 22, 2005 9:41 am, dick hoogendijk wrote:
> On Fri, 21 Oct 2005 15:30:52 -0400
> Kris Kennaway <[EMAIL PROTECTED]> wrote:
>
>
>>> But he old libraries are still on the system than, aren't they?
>>> Or will they not be used and if not, why?
>>>
>>
>> Use libchk and pkg_which..see thei
On Fri, 21 Oct 2005 15:30:52 -0400
Kris Kennaway <[EMAIL PROTECTED]> wrote:
> > But he old libraries are still on the system than, aren't they?
> > Or will they not be used and if not, why?
>
> Use libchk and pkg_which..see their manpages.
After looking into the manual(s) this seems to be a "dan
On Fri, Oct 21, 2005 at 08:21:27PM +0200, dick hoogendijk wrote:
> On Wed, 19 Oct 2005 18:53:51 -0400
> Kris Kennaway <[EMAIL PROTECTED]> wrote:
>
> > On Wed, Oct 19, 2005 at 11:36:35PM +0200, Ronald Klop wrote:
> > > COMPAT_FREEBSD5 is meant for running FreeBSD-5 binary applications.
> > > If you
On Wed, 19 Oct 2005 18:53:51 -0400
Kris Kennaway <[EMAIL PROTECTED]> wrote:
> On Wed, Oct 19, 2005 at 11:36:35PM +0200, Ronald Klop wrote:
> > COMPAT_FREEBSD5 is meant for running FreeBSD-5 binary applications.
> > If you have them it's ok. If you recompile everything you don't
> > need the COMPAT
On Oct 20, 2005, at 4:16 PM, Michael Nottebrock wrote:
On Thursday, 20. October 2005 21:20, Vivek Khera wrote:
personally, I don't see the point of doing that. just let your ports
naturally get replaced as they are upgraded due to version bumps and
such.
That is dangerous, see other repli
On Thu, Oct 20, 2005 at 03:20:52PM -0400, Vivek Khera wrote:
>
> On Oct 19, 2005, at 5:10 PM, dick hoogendijk wrote:
>
> >Wat is the best way to get the cleanest FreeBSD-6.x system without
> >installing from scratch? Recompile each port? Or use the
> >COMPAT_FREEBSD5 layer?
> >
> >
>
> this is a
On Thursday, 20. October 2005 21:20, Vivek Khera wrote:
> personally, I don't see the point of doing that. just let your ports
> naturally get replaced as they are upgraded due to version bumps and
> such.
That is dangerous, see other replies in this thread for the reasons why.
--
,_, | Mi
On Oct 19, 2005, at 5:10 PM, dick hoogendijk wrote:
Wat is the best way to get the cleanest FreeBSD-6.x system without
installing from scratch? Recompile each port? Or use the
COMPAT_FREEBSD5 layer?
this is a different question than you asked before... the
COMPAT_FREEBSD5 will allow your
On Wed, Oct 19, 2005 at 11:36:35PM +0200, Ronald Klop wrote:
> On Wed, 19 Oct 2005 23:10:46 +0200, dick hoogendijk <[EMAIL PROTECTED]> wrote:
>
> >On Mon, 17 Oct 2005 15:52:00 -0400
> >Vivek Khera <[EMAIL PROTECTED]> wrote:
> >
> >>On Oct 16, 2005, at 7:57 AM, dick hoogendijk wrote:
> >
> >>> The
On Wed, 19 Oct 2005 23:10:46 +0200, dick hoogendijk <[EMAIL PROTECTED]> wrote:
On Mon, 17 Oct 2005 15:52:00 -0400
Vivek Khera <[EMAIL PROTECTED]> wrote:
On Oct 16, 2005, at 7:57 AM, dick hoogendijk wrote:
> The *ONLY* question is: will I need to *recompile* all installed
> ports if I go fro
On Mon, 17 Oct 2005 15:52:00 -0400
Vivek Khera <[EMAIL PROTECTED]> wrote:
> On Oct 16, 2005, at 7:57 AM, dick hoogendijk wrote:
> > The *ONLY* question is: will I need to *recompile* all installed
> > ports if I go from 5.4 to 6.0 release?
>
> No, the kernel has COMPAT_FREEBSD5 and COMPAT_FREEB
On Tue, October 18, 2005 10:30 pm, Joel Rees wrote:
>
>>> How come the kernel is reporting that an AMD chip has HTT? Is this
>>> a bug?
>>>
>>
>> No, this is how dual core is reported.
>>
>
> Huh?
>
>
> Don't scare me like that, Mike.
I guess i got a little confused here. Before multicore detectio
On 平成 17/10/18, at 13:05, Mike Jakubik wrote:
On Mon, October 17, 2005 11:56 pm, Brett Glass wrote:
Features=0x178bfbff,PG
E,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
Features2=0x1
AMD Features=0xe2500800
AMD Features2=0x3
Multicore: 2 physical cores
How come the kernel is reporti
On 平成 17/10/18, at 17:21, Pertti Kosunen wrote:
Brett Glass wrote:
How come the kernel is reporting that an AMD chip has HTT? Is this
a bug?
It is the AMD HyperTransport™ Technology, not Hyper Threading as
Intels have.
http://www.amd.com/us-en/Processors/DevelopWithAMD/
0,,30_2252_2
On Mon, Oct 17, 2005 at 07:56:34PM -0600, Brett Glass wrote:
> At 06:38 PM 10/17/2005, Mike Tancsa wrote:
>
> >Two of our scanners in the cluster are SMP boxes-- dual core AMD running in
> >386 mode and an Intel D830.
> >Both work really well, and take quite a load against them network / cpu
>
At 11:56 PM 17/10/2005, Brett Glass wrote:
At 08:13 PM 10/17/2005, Mike Tancsa wrote:
One thing we're looking at doing is deploying some single-core AMD64s.
Some of the motherboards use the NVidia NForce chipsets, so we
need to know if the nve driver works
I have seen lots of problem reports
Brett Glass wrote:
How come the kernel is reporting that an AMD chip has HTT? Is this a bug?
It is the AMD HyperTransport™ Technology, not Hyper Threading as Intels
have.
http://www.amd.com/us-en/Processors/DevelopWithAMD/0,,30_2252_2353,00.html
__
On Mon, October 17, 2005 11:56 pm, Brett Glass wrote:
>> Features=0x178bfbff> E,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
>> Features2=0x1
>> AMD Features=0xe2500800
>> AMD Features2=0x3
>> Multicore: 2 physical cores
>>
>
> How come the kernel is reporting that an AMD chip has HTT? Is this
At 08:13 PM 10/17/2005, Mike Tancsa wrote:
One thing we're looking at doing is deploying some single-core AMD64s.
Some of the motherboards use the NVidia NForce chipsets, so we
need to know if the nve driver works
I have seen lots of problem reports with the nve. A board that
works well for
At 09:56 PM 17/10/2005, Brett Glass wrote:
At 06:38 PM 10/17/2005, Mike Tancsa wrote:
>Two of our scanners in the cluster are SMP boxes-- dual core AMD
running in 386 mode and an Intel D830.
>Both work really well, and take quite a load against them network
/ cpu wise. Lots of threads running
At 06:38 PM 10/17/2005, Mike Tancsa wrote:
>Two of our scanners in the cluster are SMP boxes-- dual core AMD running in
>386 mode and an Intel D830.
>Both work really well, and take quite a load against them network / cpu wise.
>Lots of threads running.
>Also have FAST_IPSEC clients and a ser
At 07:46 PM 15/10/2005, Brett Glass wrote:
The release schedule for FreeBSD 6.0, on the FreeBSD Web site, doesn't show a
projected date for the finished product. How close is it?
My guess, very soon. But for me, RELENG_6 has been small 's' stable
for some time. Got with 6.0R when it comes
On Oct 16, 2005, at 7:57 AM, dick hoogendijk wrote:
The news I read about fFreeBSD-6.0 is quit good lately. I might even
upgrade my 5.4 box. I'm told it will be a rather smooth proces.
so far, I've upgraded from 5.4-RELEASE: a Dell PE1300 (pentium 3
750MHz) SCSI disks, a generic AMD Duron
On Mon, Oct 17, 2005 at 05:05:34PM +0200, Oliver Fromme wrote:
> Brett Glass <[EMAIL PROTECTED]> wrote:
> > The release schedule for FreeBSD 6.0, on the FreeBSD Web site, doesn't
> show a
> > projected date for the finished product. How close is it?
>
> I can't speak for the RE team, but from
Brett Glass <[EMAIL PROTECTED]> wrote:
> The release schedule for FreeBSD 6.0, on the FreeBSD Web site, doesn't show a
> projected date for the finished product. How close is it?
I can't speak for the RE team, but from watching the BETA
and RC progress and reports in the mailing lists ... my
gu
On Sunday, 16. October 2005 18:34, Ronald Klop wrote:
> There are a couple of options:
> 1. Do not remove old (5.4) libraries. All 5.4 libs wil still be found.
> 2. Remove old libraries and install ports/misc/compat5x. All 5.4 lib wil
> still be found.
> 3. Remove old libraries and use /etc/libmap
On Sun, 16 Oct 2005 13:57:52 +0200, dick hoogendijk <[EMAIL PROTECTED]> wrote:
On Sat, 15 Oct 2005 23:03:53 -0400
"Joshua Coombs" <[EMAIL PROTECTED]> wrote:
For what it's worth, on UP, my 386 (stop laughing) is showing twice
the inbound and outbound tcp throughput across multiple apps compared
On Sun, 16 Oct 2005, dick hoogendijk wrote:
On Sat, 15 Oct 2005 23:03:53 -0400
"Joshua Coombs" <[EMAIL PROTECTED]> wrote:
For what it's worth, on UP, my 386 (stop laughing) is showing twice
the inbound and outbound tcp throughput across multiple apps compared
to 4.11. Disk throughput is sligh
On Sat, 15 Oct 2005 23:03:53 -0400
"Joshua Coombs" <[EMAIL PROTECTED]> wrote:
> For what it's worth, on UP, my 386 (stop laughing) is showing twice
> the inbound and outbound tcp throughput across multiple apps compared
> to 4.11. Disk throughput is slightly higher, but nothing super
> impres
Brett Glass wrote:
At 06:34 PM 10/15/2005, David Syphers wrote:
http://www.freebsd.org/releases/6.0R/todo.html
Linked to from the schedule page...
Been there. Want to get folks' opinions, and also more detail
than is likely to appear on th epage.
Good to see alot of it just need
"Brett Glass" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
The release schedule for FreeBSD 6.0, on the FreeBSD Web site,
doesn't show a
projected date for the finished product. How close is it? We are
(believe it
or not) still running and building production servers with 4.11,
At 06:34 PM 10/15/2005, David Syphers wrote:
>http://www.freebsd.org/releases/6.0R/todo.html
>
>Linked to from the schedule page...
Been there. Want to get folks' opinions, and also more detail
than is likely to appear on th epage.
--Brett
___
freebsd
On Saturday 15 October 2005 04:46 pm, Brett Glass wrote:
> With what known problems
> is 6.0 likely to ship, and of these which are likely to impact uniprocessor
> systems? Are any "showstopper" bugs merely being worked around for release?
http://www.freebsd.org/releases/6.0R/todo.html
Linked to
The release schedule for FreeBSD 6.0, on the FreeBSD Web site, doesn't show a
projected date for the finished product. How close is it? We are (believe it
or not) still running and building production servers with 4.11, and would
love to move to 6.0 (at least for uniprocessor systems; we may wait
39 matches
Mail list logo