sharing folders with Nautilus

[Tom H]

On Mon, Nov 8, 2010 at 11:41 AM, NoOp <glgxg at sbcglobal.net> wrote:
> On 11/07/2010 11:44 PM, Tom H wrote:
>> On Sun, Nov 7, 2010 at 7:34 PM, NoOp <glgxg at sbcglobal.net> wrote:
>>> On 11/07/2010 12:02 PM, Scott Berry wrote:
>>>>>
>>>>> $ cat /etc/hosts
>>>>
>>>> 192.168.1.100 Princess        # Added by NetworkManager
>>>> 127.0.0.1     localhost.localdomain    localhost
>>>> ::1   Princess        localhost6.localdomain6 localhost6 scott.CANINE
>>>>
>>>>> $ hostname
>>>>
>>>> Princess
>>>>
>>>>> $ users
>>>>
>>>> scott scott
>>>>
>>>>> $ cat /etc/samba/smb.conf
>>>>> [note: *only* provide the lines containing:
>>>>> # Change this to the workgroup/NT-domain name your Samba server will part of
>>>> workgroup = CANINE ( just changed)
>>>>
>>>>> Now: please provide the Windows workgroup name that you use on your
>>>>> Windows systems (right click 'My Computer' & click on
>>>>> Properties|Computer Name - you'll see is listed as 'Workgroup:
>>>>> <workgroupname>).
>>>>
>>>> CANINE
>>>
>>> Then
>>> 127.0.0.1 localhost scott.Canine
>>> would be the correct entry.
>>
>> "scott.Canine"?! "<user>.<workgroup>"?!
>>
>> Don't you mean "Princess.Canine"?


> Sorry, you are correct, should be
> 127.0.0.1    localhost  localhost.localdomain  servername
> which would be:
> 127.0.0.1 localhost Princess.Canine

No probs. I think that you were mislead by the ipv6 line that had
"Scott.Canine"...


>> As a follow-up to a thread of the last few days and for the sake of
>> Googlers, the canonical Debian/Ubuntu ipv4 "/etc/hosts" setup would be
>> (even though I don't use it):
>>
>> 192.168.1.100 Princess   # Added by NetworkManager
>> 127.0.0.1   localhost.localdomain   localhost
>
> The above caused issues back in Feisty etc. The solution, at the time
> was to ensure that localhost was first. See:
> <http://lists.debian.org/debian-devel/2005/10/msg00387.html>
> So I've always reversed them. Perhaps it's been fixed by now, but...

[That's one of the fight-threads that I alluded to in an earlier email
regarding "/etc/hosts".  :)  Thanks for finding it.]

I've usually deleted "localhost.localdomain" so I didn't notice the
Feisty problem. The thread does continue with:

<begin>
> You give nice explanations how things work, but fail to say anywhere why
> having localhost.localdomain first is so wrong.
> What breaks? What standards (with reference please) are not honored?

Well, even if Jeff didn't provide anything helpful in this regard, the
thread does show at least two specific packages that break when using
localhost.localdomain as the canonical name for 127.0.0.1: mysql, and inn.
<end>

Whatever the arguments, etc, it was and is the default setup of a
Ubuntu/Debian "/etc/hosts" file.



>> 127.0.1.1   Princess.Canine   Princess
>
> Heads up:
> <https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/234543>
> [Note comment 12 & 13 - looks as if they've modified network manager]
> but of course that creates new problems:
> <https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/659872>
> [Aliases in /etc/hosts overwritten]
> https://bugzilla.gnome.org/show_bug.cgi?id=632157
>  https://bugzilla.gnome.org/show_bug.cgi?id=514580
> Here we go again...

What a mess. If NM's creating a "ip_address hostname # added by NM"
line then a "127.0.1.1 hostname" isn't necessary, AFAIK. When Debian
came up with this "127.0.1.1" setup, they said that it was a hack; so,
like all hacks, it comes back to screw you at some point...