Installing on a Samba share drive

Installing on a Samba share drive

[Tom Leonard]

Hi,

I created a Samba share on my Debian system, mapped it to a drive letter 
on my XP Home system and did a full network install of Cygwin on the 
root of the mapped drive.  When I tried to use Cygwin to compile some 
programs, I found that a number of the symbolic links from the install 
(eg all of the low level .exe's like am.exe from gcc) could not be 
found.  While I could manually create the necessary symbolic links, it 
was impossible to know what exactly was broken.  I resolved the issue by 
"uninstalling" from the Samba drive and reinstalling on a local XP drive.

Can anyone shed some light on why the symbolic links might be broken.  
Because I need to support different library configurations, I'd like to 
use the technique of maintaining a number of different Cygwin 
environments on my Debian system where I have lots of disk space, and 
map to XP as and when needed.

Thanks,

Tom

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Installing on a Samba share drive

[Larry Hall (Cygwin)]

Tom Leonard wrote:
> Hi,
> 
> I created a Samba share on my Debian system, mapped it to a drive letter 
> on my XP Home system and did a full network install of Cygwin on the 
> root of the mapped drive.  When I tried to use Cygwin to compile some 
> programs, I found that a number of the symbolic links from the install 
> (eg all of the low level .exe's like am.exe from gcc) could not be 
> found.  While I could manually create the necessary symbolic links, it 
> was impossible to know what exactly was broken.  I resolved the issue by 
> "uninstalling" from the Samba drive and reinstalling on a local XP drive.
> 
> Can anyone shed some light on why the symbolic links might be broken.  
> Because I need to support different library configurations, I'd like to 
> use the technique of maintaining a number of different Cygwin 
> environments on my Debian system where I have lots of disk space, and 
> map to XP as and when needed.


System attribute of the symlinks weren't/couldn't be set?


-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
216 Dalton Rd.                          (508) 893-9889 - FAX
Holliston, MA 01746

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Installing on a Samba share drive

[Christopher Faylor]

On Wed, Dec 05, 2007 at 10:45:43PM -0500, Larry Hall (Cygwin) wrote:
> Tom Leonard wrote:
>> Hi,
>> I created a Samba share on my Debian system, mapped it to a drive letter 
>> on my XP Home system and did a full network install of Cygwin on the root 
>> of the mapped drive.  When I tried to use Cygwin to compile some programs, 
>> I found that a number of the symbolic links from the install (eg all of 
>> the low level .exe's like am.exe from gcc) could not be found.  While I 
>> could manually create the necessary symbolic links, it was impossible to 
>> know what exactly was broken.  I resolved the issue by "uninstalling" from 
>> the Samba drive and reinstalling on a local XP drive.
>> Can anyone shed some light on why the symbolic links might be broken.  
>> Because I need to support different library configurations, I'd like to 
>> use the technique of maintaining a number of different Cygwin environments 
>> on my Debian system where I have lots of disk space, and map to XP as and 
>> when needed.
>
>
> System attribute of the symlinks weren't/couldn't be set?

You're showing your age, Larry.  :-) .lnk files shouldn't have system
attributes.  They should just be readonly.  But that would be the case if
a *cygwin* cp/tar/cpio/etc. command was used to create the files.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Installing on a Samba share drive

[Larry Hall (Cygwin)]

Christopher Faylor wrote:
> On Wed, Dec 05, 2007 at 10:45:43PM -0500, Larry Hall (Cygwin) wrote:
>> Tom Leonard wrote:
>>> Hi,
>>> I created a Samba share on my Debian system, mapped it to a drive letter 
>>> on my XP Home system and did a full network install of Cygwin on the root 
>>> of the mapped drive.  When I tried to use Cygwin to compile some programs, 
>>> I found that a number of the symbolic links from the install (eg all of 
>>> the low level .exe's like am.exe from gcc) could not be found.  While I 
>>> could manually create the necessary symbolic links, it was impossible to 
>>> know what exactly was broken.  I resolved the issue by "uninstalling" from 
>>> the Samba drive and reinstalling on a local XP drive.
>>> Can anyone shed some light on why the symbolic links might be broken.  
>>> Because I need to support different library configurations, I'd like to 
>>> use the technique of maintaining a number of different Cygwin environments 
>>> on my Debian system where I have lots of disk space, and map to XP as and 
>>> when needed.
>>
>> System attribute of the symlinks weren't/couldn't be set?
> 
> You're showing your age, Larry.  :-) .lnk files shouldn't have system
> attributes.  They should just be readonly.  But that would be the case if
> a *cygwin* cp/tar/cpio/etc. command was used to create the files.


Has 'setup.exe' finally been updated to create .lnk file style symlinks?
Guess it has been a while since I've wandered through that code. :-)


-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
216 Dalton Rd.                          (508) 893-9889 - FAX
Holliston, MA 01746

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Installing on a Samba share drive

[Christopher Faylor]

On Wed, Dec 05, 2007 at 11:38:54PM -0500, Larry Hall (Cygwin) wrote:
> Christopher Faylor wrote:
>> On Wed, Dec 05, 2007 at 10:45:43PM -0500, Larry Hall (Cygwin) wrote:
>>> Tom Leonard wrote:
>>>> Hi,
>>>> I created a Samba share on my Debian system, mapped it to a drive letter 
>>>> on my XP Home system and did a full network install of Cygwin on the 
>>>> root of the mapped drive.  When I tried to use Cygwin to compile some 
>>>> programs, I found that a number of the symbolic links from the install 
>>>> (eg all of the low level .exe's like am.exe from gcc) could not be 
>>>> found.  While I could manually create the necessary symbolic links, it 
>>>> was impossible to know what exactly was broken.  I resolved the issue by 
>>>> "uninstalling" from the Samba drive and reinstalling on a local XP 
>>>> drive.
>>>> Can anyone shed some light on why the symbolic links might be broken.  
>>>> Because I need to support different library configurations, I'd like to 
>>>> use the technique of maintaining a number of different Cygwin 
>>>> environments on my Debian system where I have lots of disk space, and 
>>>> map to XP as and when needed.
>>>
>>> System attribute of the symlinks weren't/couldn't be set?
>> You're showing your age, Larry.  :-) .lnk files shouldn't have system
>> attributes.  They should just be readonly.  But that would be the case if
>> a *cygwin* cp/tar/cpio/etc. command was used to create the files.
>
>
> Has 'setup.exe' finally been updated to create .lnk file style symlinks?
> Guess it has been a while since I've wandered through that code. :-)

Ah, good point.  I was actually thinking this might have been the same
thing that as someone on IRC was reporting where I thought they said
that they just saw .lnk files but I see now that this wasn't mentioned
above.  Sorry about that.

Same answer, though.  Using cygwin utiltities to create the files should
rectify the problem.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Installing on a Samba share drive

[Albrecht Schlosser]

Christopher Faylor wrote:
> On Wed, Dec 05, 2007 at 11:38:54PM -0500, Larry Hall (Cygwin) wrote:
>> Christopher Faylor wrote:
>>> On Wed, Dec 05, 2007 at 10:45:43PM -0500, Larry Hall (Cygwin) wrote:
>>>> Tom Leonard wrote:
>>>>> Hi,
>>>>> I created a Samba share on my Debian system, mapped it to a drive letter 
>>>>> on my XP Home system and did a full network install of Cygwin on the 
>>>>> root of the mapped drive. 

>> Has 'setup.exe' finally been updated to create .lnk file style symlinks?
>> Guess it has been a while since I've wandered through that code. :-)
> 
> Ah, good point.  I was actually thinking this might have been the same
> thing that as someone on IRC was reporting where I thought they said
> that they just saw .lnk files but I see now that this wasn't mentioned
> above.  Sorry about that.
> 
> Same answer, though.  Using cygwin utiltities to create the files should
> rectify the problem.

Well, the OP wrote that he used setup.exe to do "a full network 
install". Since setup.exe is a native windows program, would this mean 
that an install to a network share wouldn't work?

Albrecht


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Installing on a Samba share drive

[Corinna Vinschen]

On Dec  6 11:16, Albrecht Schlosser wrote:
> Christopher Faylor wrote:
>> On Wed, Dec 05, 2007 at 11:38:54PM -0500, Larry Hall (Cygwin) wrote:
>>> Christopher Faylor wrote:
>>>> On Wed, Dec 05, 2007 at 10:45:43PM -0500, Larry Hall (Cygwin) wrote:
>>>>> Tom Leonard wrote:
>>>>>> Hi,
>>>>>> I created a Samba share on my Debian system, mapped it to a drive 
>>>>>> letter on my XP Home system and did a full network install of Cygwin 
>>>>>> on the root of the mapped drive. 
>
>>> Has 'setup.exe' finally been updated to create .lnk file style symlinks?
>>> Guess it has been a while since I've wandered through that code. :-)
>> Ah, good point.  I was actually thinking this might have been the same
>> thing that as someone on IRC was reporting where I thought they said
>> that they just saw .lnk files but I see now that this wasn't mentioned
>> above.  Sorry about that.
>> Same answer, though.  Using cygwin utiltities to create the files should
>> rectify the problem.
>
> Well, the OP wrote that he used setup.exe to do "a full network install". 
> Since setup.exe is a native windows program, would this mean that an 
> install to a network share wouldn't work?

setup.exe is creating symlinks of the "plain file with magic header and
system bit set" type, which is also used for unix sockets and also for
symlinks if you set the CYGWIN=nowinsymlinks option.  The problem with
Samba is that it's running on file systems which don't support DOS file
attributes natively. 

However, Samba supports a mapping mechanism which uses the  execute bits
in the file permissions to simulate the DOS attribute bits system,
hidden and archive, as well as, in newer Samba versions, a mapping
mechanism which uses extended attributes to map these bits.  For more
information see `man smb.conf'.  Using one of these mechanisms should
allow Cygwin symlinks created by setup.exe to work on Samba shares.  Of
course, they are still just plain files.  They are not visible as real
symlinks from the Linux side, they still only work from Cygwin.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/