On Tue, 2002-02-26 at 11:44, Simon Wong wrote:
> On Tue, 2002-02-26 at 11:28, Matthew Palmer wrote:
> > I don't think it will help, actually. Because the machine that needs to
> > know lonewolf's IP is the machine you're connecting to, which has no idea
> > that you've gotten that IP via DHCP, and hence can't have updated /etc/hosts
> > for it.
>
> Sorry - I think I am being unclear :-(
>
> I am SSHing TO lonewolf i.e.
>
> Remote ---SSH---> Lonewolf(DHCP) (OK - it's a laptop).
>
> So I need lonewolf to update it's /etc/hosts when it receives the IP via
> DHCP. Then when the display is set "lonewolf:10.0" it can resolve
> itself.
I'm sure somebody's going to give me a good reason why you shouldn't do
it, but:
Couldn't you just insert an entry in your hosts file aliasing lonewolf
to 127.0.0.1?
Something like:
127.0.0.1 fizgig localhost
--
Peter
[EMAIL PROTECTED]
It's fifteen hundred miles to Ankh-Morpork. We've got three hundred and
sixty-three elephants, fifty carts of forage, the monsoon's about to
break
and we're wearing... we're wearing... sort of things, like glass, only
dark... dark glass things on our eyes...
-- Azhural N'choate
(Terry Pratchett, Moving Pictures)
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
