[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Handling of fat32

From: Michael Stather <stather.external_at_onespin-solutions.com>
Date: 2006-04-06 13:43:52 CEST

Stefan Küng wrote:

>On 4/6/06, Michael Stather <stather.external@onespin-solutions.com> wrote:
>
>
>>I already asked this on the svn mailing list but I was told that perhaps
>>someone could help me here.
>>I can´t run svn on fat32 partitions (under linux), it just complains
>>about not being able to set permissions which is of course not supported.
>>How do you manage this in tortoisesvn?
>>
>>
>
>* TortoiseSVN does not run under Linux
>* of course, you can't set Linux file permissions on files on a fat32 partition
>* you can ignore those errors, it should work anyway
>
>The best thing you can do is:
>* use a separate working copy for each OS you're using, on 'native'
>partitions to that OS
>* never access a repository or working copy on a partition that's not
>fully supported by the OS
>
>Stefan
>
>--
> ___
> oo // \\ "De Chelonian Mobile"
> (_,\/ \_/ \ TortoiseSVN
> \ \_/_\_/> The coolest Interface to (Sub)Version Control
> /_/ \_\ http://tortoisesvn.tigris.org
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
>For additional commands, e-mail: users-help@tortoisesvn.tigris.org
>
>
>
Yes I know it´s windows-only.
But my problem is that svn exits when it can´t write the file
permissions, and how do you actually handle this?
I mean svn will always fail under a fat32 partition, how have you got it
to work?
Is there a command-line switch to svn? Or a compile-option?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Thu Apr 6 13:44:10 2006

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.