Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 19 Jan 2007 09:13:24 -0000
From:      "Martin Tournoij" <carpetsmoker@xs4all.nl>
To:        "Charlie Hynson III" <dachaos@dachaos.com>, freebsd-questions@freebsd.org
Subject:   Re: Hide ports make options/config
Message-ID:  <op.tmd88xr5kagcwh@phong.carpetsmoker.net>
In-Reply-To: <002e01c73ba2$c609f2f0$7800a8c0@carla>
References:  <002e01c73ba2$c609f2f0$7800a8c0@carla>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 19 Jan 2007 08:21:07 -0000, Charlie Hynson III  
<dachaos@dachaos.com> wrote:

> I am making myself an easy install sh shell script that configures my own
> basic setup on FreeBSD 6.2 Release. Wondering how I tell make when
> installing a port not to ask me make options/config (silent install). For
> all ports and or individual ports. Since I have my make options set in
> pkgtools config for sysutils/portupgrade.
> For example portupgrade -RN /usr/ports/lang/php4
> Will ask me make options which I have already set. How do I hide the
> options.
> I tried searching a few places before asking with no luck.
>
>
> P.S.
> Thanks FreeBSD Team for another great release so far 6.2 Release is  
> running
> really smooth on my P4 2.6 i386 system without any problems. By default
> FreeBSD 6.2 Release works with my re0 1000/baseTX Full Duplex LinkSys
> Gigabit NIC. Which really impresses me since I have to install a driver  
> on
> windows 2003 server enterprise before the card works. Not FreeBSD!!!
>
> Thanks,
> Charlie
>

-DBATCH

For example:
make install -DBATCH [OTHER SWITCHES]

Hope this helps.

Windows 2003 probably has the driver for your NIC, but can't find because  
your card is one revision higher, let's say Gigabit 123b, and windows only  
has a driver for Gigabit123a or something like that.
Quite often (~90% of the time) this is the case on Windows 2000 and XP  
when it can't find a driver.
One (or a few) revisions higher or lower doesn't matter for the driver.
although I don't have any experience with Windows 2003, I think I can  
safely assume this is the case for windows 2003 to.
You will have to select the driver manually.

Martin





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.tmd88xr5kagcwh>