On Wed, 02 Feb 2011 12:12:41 +0100, Joseph L. Casale
wrote:
>> If not, what is the correct procedure to do this within Windows?
>> How do you list the complete filesystem so that everything shows, are
>> there specialist tools for this? (it appears to be impossible to access
>> some dirs even i
>If not, what is the correct procedure to do this within Windows?
>How do you list the complete filesystem so that everything shows, are
>there specialist tools for this? (it appears to be impossible to access
>some dirs even if using console/administrator and explorer/DOS show a
>different v
On Mon, 31 Jan 2011 18:24:10 +0100, John Drescher
wrote:
> On Mon, Jan 31, 2011 at 12:20 PM, Randy Katz
> wrote:
>> On 1/31/2011 9:08 AM, John Drescher wrote:
John, thanks, but this was already addressed to the list, using the
onefs
option to yes takes care of
the is
On 1/31/2011 9:24 AM, John Drescher wrote:
> On Mon, Jan 31, 2011 at 12:20 PM, Randy Katz
> wrote:
>> On 1/31/2011 9:08 AM, John Drescher wrote:
John, thanks, but this was already addressed to the list, using the onefs
option to yes takes care of
the issue, and no, there is no othe
On Mon, Jan 31, 2011 at 12:20 PM, Randy Katz
wrote:
> On 1/31/2011 9:08 AM, John Drescher wrote:
>>>
>>> John, thanks, but this was already addressed to the list, using the onefs
>>> option to yes takes care of
>>> the issue, and no, there is no other target drive other then "C:".
>>>
>> My point
On 1/31/2011 9:08 AM, John Drescher wrote:
>> John, thanks, but this was already addressed to the list, using the onefs
>> option to yes takes care of
>> the issue, and no, there is no other target drive other then "C:".
>>
> My point is no the onefs option does not properly fix the issue. If
> the
On 1/31/2011 9:08 AM, John Drescher wrote:
>> John, thanks, but this was already addressed to the list, using the onefs
>> option to yes takes care of
>> the issue, and no, there is no other target drive other then "C:".
>>
> My point is no the onefs option does not properly fix the issue. If
> the
> John, thanks, but this was already addressed to the list, using the onefs
> option to yes takes care of
> the issue, and no, there is no other target drive other then "C:".
>
My point is no the onefs option does not properly fix the issue. If
the target of the junction is on C: you do NOT want t
On 1/31/2011 8:45 AM, John Drescher wrote:
> On Mon, Jan 31, 2011 at 7:33 AM, Randy Katz
> wrote:
>> Hi,
>>
>> I am seeing this error:
>>
>> 31-Jan 03:42 win1-fd JobId 157:
>> C:/inetpub/vhosts/Servers/3/localuser/dirrec is a junction point or a
>> different filesystem. Will not descend fr
On Mon, Jan 31, 2011 at 7:33 AM, Randy Katz wrote:
> Hi,
>
> I am seeing this error:
>
> 31-Jan 03:42 win1-fd JobId 157:
> C:/inetpub/vhosts/Servers/3/localuser/dirrec is a junction point or a
> different filesystem. Will not descend from C:/inetpub into it.
>
> I have many of these in C:/i
> On Mon, 31 Jan 2011 04:59:29 -0800, Randy Katz said:
>
> On 1/31/2011 4:46 AM, Christian Manal wrote:
> > Am 31.01.2011 13:33, schrieb Randy Katz:
> >> Hi,
> >>
> >> I am seeing this error:
> >>
> >> 31-Jan 03:42 win1-fd JobId 157:
> >> C:/inetpub/vhosts/Servers/3/localuser/dirrec is a
On 1/31/2011 4:46 AM, Christian Manal wrote:
> Am 31.01.2011 13:33, schrieb Randy Katz:
>> Hi,
>>
>> I am seeing this error:
>>
>> 31-Jan 03:42 win1-fd JobId 157:
>> C:/inetpub/vhosts/Servers/3/localuser/dirrec is a junction point or a
>> different filesystem. Will not descend from C:/inetpu
Am 31.01.2011 13:33, schrieb Randy Katz:
> Hi,
>
> I am seeing this error:
>
> 31-Jan 03:42 win1-fd JobId 157:
> C:/inetpub/vhosts/Servers/3/localuser/dirrec is a junction point or a
> different filesystem. Will not descend from C:/inetpub into it.
>
> I have many of these in C:/inetpub/v
Hi,
I am seeing this error:
31-Jan 03:42 win1-fd JobId 157:
C:/inetpub/vhosts/Servers/3/localuser/dirrec is a junction point or a different
filesystem. Will not descend from C:/inetpub into it.
I have many of these in C:/inetpub/vhosts/Servers/3/localuser/
How can I get these backed up,
14 matches
Mail list logo