[MythDora] New video4linux packages
mythtv at frouse3.homelinux.com
Mon Apr 23 18:07:03 CEST 2007
> Jarod Wilson wrote:
>> On Sunday 22 April 2007 23:47:52 gchris wrote:
>>> gchris wrote:
>>>> That's also very smart. I'd noticed in my last mythtv build that
>>>> seems to be moving some things around and adding new settings for
>>>> time builders to screw up, so anything that you can do to reduce
>>>> that need to be made is almost certainly a good thing.
>>> P.S. One thing that bothered me about the earlier MythDora releases is
>>> nagging feeling that 'localhost' is a reserved name in Windows
>>> not to be used as an actual host name within a network. Does that ring
>>> any bells at all or is it just a figment of my imagination?
>> Well, localhost is typically reserved on all hosts, solely for pointing
>> at the
>> local host's loopback address, 127.0.0.1. Its set up by default on every
>> Linux box and has been for some time. We don't do anything special to
>> it, so
>> I think there's nothing to worry about there.
> The association that you described is exactly the way it is used in
> Windows machines as well but in the Windows world the association is
> hard coded so 'localhost' always means '127.0.0.1'. The problem arises
> when you use 'localhost' as a machine's network name. It's been way too
> many years since I last encountered this but it seems to me that some
> Windows code refuses to talk to a box on a network which is named
> localhost, either because the address is out of range for a network or
> because the code assumes the traffic is destined for *this* box, not a
> remote one. The "special" thing that MythDora does is it defaults to
> localhost.localdomain as the box's network name, and if I recall
> correctly, doesn't follow normal Fedora conventions for allowing the
> user to change that.
It sounds as though you're expecting to be able to resolve
localhost.localdomain from another machine by name. Linux by default won't
advertise it's hostname over netbios or wins,etc. So you Windows machines
(or other any other machines) will not have name resolution the host. And
if you specifically call for localhost you'll most definitely end up
speaking the local machines loopback.
The only way you're going to get windows to talk to a linux machine called
"localhost" is by overiding tcpip with netbios and explicitly having samba
on your linux machine broadcast it's netbios / wins name as localhost.
> But now my brain is overheating so I think it's time to go read Groklaw.
> mythdora mailing list
> mythdora at atrpms.net
More information about the mythdora