-
I must say, you are being very un-you. I used to respect what you say. Now, I'm not so sure. I feel that this site is an excellent place to get info from people who know what they're doing and have experience. I'm sorry if you feel that I'm treating it like a "****ing nursery". Like I said before, I'm a newbie to the world of Linux, so I don't know what I'm doing yet. I'm trying to learn. I'm sorry you don't like the way I'm going about it.
Once again, I used to respect you. Now, you're going on my ignore list. I'm trying to learn, not get into a flame war.
-
The funny thing is, i like trying to answer questions - i don't know why i become so truculent at the weekends, must be something to do with the drink and drugs ;-)
I wouldn't take anything i say to heart, who am i to tell you not to post questions, post whatever you like, its a free world - and if anybody tells you different - tell em to **** away off.
-
I can't tell if you're being serious or sarcastic. It's very hard to tell sometimes when the conversations are in text. ;)
If you're being serious, I'd like to extend the olive branch to you. If you're being sarcastic, I'd like to beat you down with it.
NOTE: If I sound like a dick, I don't mean to. I just don't want a fight.
-
Do you have your linux box pointing at a valid DNS server?
As for mapping network drives - try smbclient for mapping windows drives or mount for nfs.
Raff
-
This thread is old and I was getting ready to delete it, but since you ask, I have solved the little DNS problem since my last post. There was a file hidden somewhere that had the DNS configuration in it. When I added my router in it, everything worked fine.
-
Hidden file? linux doesn't hide files.
-
Pete,
I don't think that stflook meant hidden, as in hidden attribute, but rather a lesser recognized file known as resolve.conf (for those unaware it keeps a listing of the DNS servers you communicate with; sometimes the network config tools -- linuxconf, netconf, netcfg, netconfig -- don't set it properly so you have to manually edit it). ;)
Perhaps a tutorial on basic unix commands or on common important network files might be necessary. ;) Ah.. Idears are a flowing!
-
I'm pretty sure thats what he meant too msmittens, my point was looking in /etc and understanding the importance of the files held there should really have been one of the first ports of call.
Until you get the time/motivation to do a tutorial on unix commands msmittens, here's a link to help:
http://www.emba.uvm.edu/CF/basic.html
-
Yes, thats what I meant. It was some file that I never would have found on my own. I was fortunate enough to have talked to somebody who had the same problem before.
My Linux box is now my web server as I had planned. All I have left to look into is a little problem with subdirectories in my web folder, but that's no biggie. I should be able to solve that with minimal effort.
