Personal computing discussed
Moderators: renee, SecretSquirrel, notfred
mail -s'some subject' [email protected] < filename
flip-mode wrote:Thanks Forge. I am having fun with this. Thanks for the patience everyone.
I just ranXorg -configure
and it recognized my Dell 2007 FPW and claimed to recognize my mouse. But when I runXorg -conf xorg.conf.new
the mouse does not work. Any thoughts?
Eventually, I want to get either KDE or Gnome (don't care which) running so I can do some web browsing and such.
Now that I have my two NICs up and running I am going to start exploring the firewall. I want an inclusive firewall I think (where only the traffic I specify is allowed) and I want NAT and port forwarding. Besides "read the handbook", is there any other advice that anyone has or any "heads up" type stuff to be said?
The other task at the top of the list is email. I haven't even gotten started on that.
Oh, and Samba.
And eventually, web browsing.
Buub wrote:Thanks Buub. I am getting name server timeout errors.Code: Select allmail -s'some subject' [email protected] < filename
titan wrote:I am taking a look at Samba right now.When you're ready for Samba, let me know and I'll point you to the right spot. It is actually not as difficult as all the articles out there make it out to be.
startx does fire up X.Org, but the mouse does not work. When I run Xorg -configure though, the mouse does work.As for X.Org, it writes all of its data to "xorg.conf", and not "xorg.conf.new". Try just running X.Org without any options. (In Linux, the command to start X.Org is "startx", but your system may be different.)
flip-mode wrote:Buub wrote:Thanks Buub. I am getting name server timeout errors.Code: Select allmail -s'some subject' [email protected] < filename
Buub wrote:flip-mode wrote:Buub wrote:Thanks Buub. I am getting name server timeout errors.Code: Select allmail -s'some subject' [email protected] < filename
Sounds like you need to configure /etc/resolv.conf
On a normally configured system this file should not be necessary. The only name server to be queried will be on the local machine, the domain name is determined from the host name, and the domain search path is constructed from the domain name.
nameserver 1.2.3.4
nameserver 1.2.3.5
Buub wrote:Sounded strange to me too but it is directly from the resolv.conf man page.The rest of what you're describing sounds baffling to me. I can only guess that it either means a machine that doesn't have a network connection, or a machine that runs its own DNS server.
flip-mode wrote:Buub wrote:Sounded strange to me too but it is directly from the resolv.conf man page.The rest of what you're describing sounds baffling to me. I can only guess that it either means a machine that doesn't have a network connection, or a machine that runs its own DNS server.
nameserver 192.168.1.1
flip-mode wrote:Buub wrote:Sounded strange to me too but it is directly from the resolv.conf man page.The rest of what you're describing sounds baffling to me. I can only guess that it either means a machine that doesn't have a network connection, or a machine that runs its own DNS server.
flip-mode wrote:Can someone explain this section from the resolv.conf man page:On a normally configured system this file should not be necessary. The only name server to be queried will be on the local machine, the domain name is determined from the host name, and the domain search path is constructed from the domain name.
I am even more of a DNS noob than a *nix noob. Why would the local machine normally be the machine to be querried? I thought querries were always made to a nameserver?
titan wrote:That is exactly what my resolv.conf looks like. And yes, both adapters are configured for DHCP in rc.confThe resolv.conf should look like this if you're behind a router:Why DHCP isn't handling it though is you're real concern. You are using DHCP?nameserver 192.168.1.1
flip-mode wrote:titan wrote:That is exactly what my resolv.conf looks like. And yes, both adapters are configured for DHCP in rc.confThe resolv.conf should look like this if you're behind a router:Why DHCP isn't handling it though is you're real concern. You are using DHCP?nameserver 192.168.1.1
Pinging the router works just fine.
Maybe something in my router's settings? I haven't really screwed with anything in there.
flip-mode wrote:Yep! That was it! Damn, that only took 4 days to figure out. It seems quite odd to me that such a setting would not be stored in resolv.conf
flip-mode wrote:Thanks BV, NF.
Not using DHCP here at work.
I have learned that using route add default xxx.xxx.xxx.xxx is only temporary and that I should add defaultrouter="xxx.xxx.xxx.xxx" in rc.conf to configure a default gateway. But adding that option does not seem to work at all! Any help?
#This file now contains just the overrides from /etc/defaults/rc.conf
gateway_enable="no"
hostname="bsdbox"
ifconfig_bge0="inet 10.1.1.240 netmask 255.255.255.0"
sshd_enable="yes"
# -- sysinstall generated deltas -- # Sun Nov 16 18:25:29 2008
moused_type="microsoft"
moused_enable="no"
defal S.H.I.7____N E V E R M I N D
flip-mode wrote:You have all been helpful and patient and I do appreciate it and just wanted to say it.