Chuck Swiger wrote:
On Jan 15, 2007, at 4:11 PM, Jay Chandler wrote:
Is it possible to install (instead of upgrading) FreeBSD from my
local CVS repository? Looking to find a good way to automate
installations, and figured I'd start there.
Sure, it's possible. You'd have to build a working
stan wrote:
Is there a way to document the entire depedency tree for a given port?
EG, if a dpends on b which depends on d e, which in turn depend on z,
I'd like to print out this dependency list.
A good question, which I've taken the liberty of researching.
montreal# cd
In the last episode (Jan 15), stan said:
Is there a way to document the entire depedency tree for a given port?
EG, if a dpends on b which depends on d e, which in turn depend on z,
I'd like to print out this dependency list.
cd into the port's directory and run make all-depends-list.
linux quest wrote:
I have a problem with the DNS setting in FreeBSD. Every 1 hour, I will not be able to ping google.com (because I need to type in my ISP's DNS into /etc/resolv.conf) May I know what is the best solution for this, so that I do not have to type in my ISP's DNS to the resolver all
Dear Jay The FreeBSD Communities,
Thanks for putting your time and patience to help me out. Anyway, I tried it
out, both changing the rc.conf and the dhclient.conf (one at a time). After
that (for both of the ways), I did manage to stop the resolv.conf from being
overwritten after the PC
Hi:
This is not exactly a question rather it is wrapup for a
series of questions. I had a tricky, confusing problem
getting FreeBSD on the net but I was able to solve it
with help from this list.. Ian Smith in particular.
The DHCP lease from my ISP set the nameserver
address as being
linux quest wrote:
Dear Jay The FreeBSD Communities,
Thanks for putting your time and patience to help me out. Anyway, I tried it
out, both changing the rc.conf and the dhclient.conf (one at a time). After
that (for both of the ways), I did manage to stop the resolv.conf from being
Dear Jay The FreeBSD Communities,
Thanks for putting your time and patience to help me out. Anyway, I
tried it out, both changing the rc.conf and the dhclient.conf (one at a
time). After that (for both of the ways), I did manage to stop the
resolv.conf from being overwritten after the PC
If you really want to copy resolv.conf from /root to /etc every 30 min
you don't need a startup script. Just add the following line in
/etc/crontab:
*/30 * * * * rootcp /root/resolv.conf
/etc/resolv.conf
I don't know what exactly are you trying to do, but this is
101 - 109 of 109 matches
Mail list logo