NFS help (.. is definitely needed)

[Otto Haliburton]

> -----Original Message-----
> From: redhat-install-list-bounces at redhat.com [mailto:redhat-install-list-
> bounces at redhat.com] On Behalf Of Vince LaMonica
> Sent: Sunday, August 28, 2005 10:41 PM
> To: Getting started with Red Hat Linux
> Subject: RE: NFS help (.. is definitely needed)
> 
> On Sun, 28 Aug 2005, Otto Haliburton wrote:
> 
> } > you have gone through what you think is a heavy analysis, let me now
> give
> } > the the simplest and the skinny about how you isp works, when your
> router
> } > comes up it goes to the DHCP for the ISP and get assigned a IP address
> } > this
> } > ISP address is usually assigned to computername.state.city.isp.domain
> in
> } > the
> } > dns now you can go from there
> } >
> } >
> } I forgot to attach the mac address which is what makes it unique in the
> dns.
> 
> A NIC's MAC address has 100% nothing to do with DNS. So far, what you have
> written is 99% inaccurate and will only cause people to be confused. You
> best read what others have written, since it is clear you don't have the
> knowledge you think you have.
> 
> /vjl/
> 
I decided that you don't know what you are talking about when you say that a
NIC card has nothing to do with MAC address.  Your router has it's own MAC
address, if it is not present then the MAC address for the NIC is used.  But
of course you know what you are talking about, do you know what a DNS is, Do
you know how MAC addresses are assigned.  Do you know whether they are
unique.  And the last thing do you know what you are talking about.  There
is a general confusion here and this thread has been blown completely out of
proportion.  This guy gives this heavy analysis of how my ISP assigns me a
IP and he does it with WAN, etc and it is really simple.  My ISP uses a DHCP
just as my router does to assign me a IP and this IP is then assigned to a
primary DNS and a secondary DNS with a unique identifier for my node.  That
is not complicated but simple.  All communications on the net has a too and
a from header and data.  Each stage adds it too and from header to the
packet until it reaches  it's destination the reply begins to unwind these
header to get you back to where you started.  Anyway, read all this BS and
continue on you way of thinking.