On Fri, Jun 08, 2007 at 09:13:37AM -0700, Freddie Cash wrote:
> Good morning,
>
> I'm having a bit of an issue getting a 3CR990B-TXM NIC detected and
> usable. Just wondering if anyone knows of any issues with this NIC
> chipset and/or with the motherboard chipset.
>
> The motherboard i
First of all, your question is about ports, so it should have been
directed to the freebsd-ports@ list, FYI.
Stephen Clark wrote:
> There is a deadly embrace.
I think you are overthinking this, and it didn't help that the only
advice you got was to re-read the instructions.
You want to first upg
On Fri, Jun 08, 2007 at 04:20:29PM -0400, Stephen Clark wrote:
> So I should wait a about week after I do a cvsup of ports - then
> hopefully most of the packages will be there - right?
Yes, but you'll have to check. Some ports (not the X11 ones) can't be
packaged due to licensing restrictions.
Mark Linimon wrote:
On Fri, Jun 08, 2007 at 03:26:21PM -0400, Stephen Clark wrote:
Thats another question - why aren't packages released simultaneously
with the ports update?
There's a circular dependency here. The ports tree is updated by checkins,
which is then pushed to the packag
On Fri, Jun 08, 2007 at 03:26:21PM -0400, Stephen Clark wrote:
> Thats another question - why aren't packages released simultaneously
> with the ports update?
There's a circular dependency here. The ports tree is updated by checkins,
which is then pushed to the package building system, which the
Nikolay Pavlov wrote:
On Friday, 8 June 2007 at 14:34:14 -0400, Stephen Clark wrote:
Kevin Oberman wrote:
Date: Fri, 08 Jun 2007 12:45:34 -0400
From: Stephen Clark <[EMAIL PROTECTED]>
Sender: [EMAIL PROTECTED]
Tom Evans wrote:
On Fri, 2007-06-08 at 09:22 -0400, Stephen
On Friday, 8 June 2007 at 14:34:14 -0400, Stephen Clark wrote:
> Kevin Oberman wrote:
>
> >>Date: Fri, 08 Jun 2007 12:45:34 -0400
> >>From: Stephen Clark <[EMAIL PROTECTED]>
> >>Sender: [EMAIL PROTECTED]
> >>
> >>Tom Evans wrote:
> >>
> >>
> >>>On Fri, 2007-06-08 at 09:22 -0400, Stephen Clark
> Date: Fri, 08 Jun 2007 12:45:34 -0400
> From: Stephen Clark <[EMAIL PROTECTED]>
> Sender: [EMAIL PROTECTED]
>
> Tom Evans wrote:
>
> >On Fri, 2007-06-08 at 09:22 -0400, Stephen Clark wrote:
> >
> >
> >>Hello List,
> >>
> >>A few weeks ago I installed 6.2. I did a cvsup of the ports and now
>
Kevin Oberman wrote:
Date: Fri, 08 Jun 2007 12:45:34 -0400
From: Stephen Clark <[EMAIL PROTECTED]>
Sender: [EMAIL PROTECTED]
Tom Evans wrote:
On Fri, 2007-06-08 at 09:22 -0400, Stephen Clark wrote:
Hello List,
A few weeks ago I installed 6.2. I did a cvsup of the ports and now
Stephen Clark wrote:
> There is a deadly embrace.
>
> The /usr/src/UPDATING says I am going to miss out if I
> don't have the meta port installed (which I currently don't), but when I
> try to install
> the meta port it tells me I should use portupgrade to upgrade Xorg, but
> the /usr/src/UPDATING
On Jun 8, 2007, at 10:41 AM, Stephen Clark wrote:
There is a deadly embrace.
The /usr/src/UPDATING says I am going to miss out if I
don't have the meta port installed (which I currently don't), but
when I try to install
the meta port it tells me I should use portupgrade to upgrade Xorg,
but
Oliver Fromme wrote:
Stephen Clark wrote:
> Tom Evans wrote:
> > Stephen Clark wrote:
> > I'd read /usr/ports/UPDATING again, if you follow the exact instructions
> >
> I have it printed out sitting right
> in front of me.
Then there shouldn't be any prob
Stephen Clark wrote:
> Tom Evans wrote:
> > Stephen Clark wrote:
> > I'd read /usr/ports/UPDATING again, if you follow the exact instructions
> >
> I have it printed out sitting right
> in front of me.
Then there shouldn't be any problem.
> But what a
Tom Evans wrote:
On Fri, 2007-06-08 at 09:22 -0400, Stephen Clark wrote:
Hello List,
A few weeks ago I installed 6.2. I did a cvsup of the ports and now
anytime I try to make
anything that uses X I get something like the following:
===> Patching for tk-8.5.a.6_1
===> Applying FreeBSD p
On Fri, 2007-06-08 at 09:22 -0400, Stephen Clark wrote:
> Hello List,
>
> A few weeks ago I installed 6.2. I did a cvsup of the ports and now
> anytime I try to make
> anything that uses X I get something like the following:
>
> ===> Patching for tk-8.5.a.6_1
> ===> Applying FreeBSD patches fo
Hi, list.
I'm find in source tree :
/usr/src/lib/libautofs
/usr/src/sbin/mount_autofs
/usr/src/share/examples/autofs
/usr/src/share/man/man5/autofs.5
Sorry, for stupid question.
Could somebody explain me, how I can build it and why it doesn't build
by default?
WBR.
Dmitriy
__
Hello List,
A few weeks ago I installed 6.2. I did a cvsup of the ports and now
anytime I try to make
anything that uses X I get something like the following:
===> Patching for tk-8.5.a.6_1
===> Applying FreeBSD patches for tk-8.5.a.6_1
===> tk-8.5.a.6_1 depends on file: /usr/local/libdata
On Wed, 6 Jun 2007, Matthew Dillon wrote:
MD> :IV> > Upd: on GENERIC/amd64 kernel I got the same errors.
MD> :IV>
MD> :IV> Do you perhaps run with TSC timecounter? (that's the only cause I've
notice
MD> :IV> that can generate this message).
MD> :
MD> :Nope:
MD> :
MD> :[EMAIL PROTECTED]:~> sysctl
> A couple comments just from reading through this, see below.
>
> > #!/bin/sh
> >
> > # PROVIDE: iscsi
> > # REQUIRE: NETWORKING
> > # BEFORE: DAEMON
> > # KEYWORD: nojail shutdown
> >
> > #
> > # Add the following lines to /etc/rc.conf to enable iscsi:
> > #
> > # iscsi_enable="YES"
> > # iscs
Kim Attree wrote:
> I've setup a machine as a diskless server, using PXEBoot with ihc-dhcpd
> to offer dhcp and dhcp configuration information. I did a test reboot on
> the server, and found to my dismay that the server NIC's are sending out
> dhcp discover packets and trying to get an address.
On Fri, Jun 08, 2007 at 11:35:33AM +0400, Alexey Karagodov wrote:
> just another some words:
>
> i have had similar trouble but my server reboots
>
> problem was in ECC correctable errors but FreeBSD kernel just reboot machine
> when this occures
> linux kernel wrote me what is the problem
> i do
just another some words:
i have had similar trouble but my server reboots
problem was in ECC correctable errors but FreeBSD kernel just reboot machine
when this occures
linux kernel wrote me what is the problem
i don't know how to figure out that in FreeBSD and other hardware issues ...
...
> > The message on the machine running scsi-target is: "Unsupported INQUIRY
> > VPD page 80"
> yes, I have tested it against ports/net/iscsi-target, I use it to try out
> errror recovery :-), and as far as I could tell it's harmelss.
> Anothere thing I can report is that running both (target/i
23 matches
Mail list logo
