Re: A path that's invalid on 1.7 but presumably valid on 1.5
- Date: Tue, 15 Jul 2008 14:00:19 -0400
- From: "Lee Maschmeyer" <lee_maschmeyer@xxxxxxxxx>
- Subject: Re: A path that's invalid on 1.7 but presumably valid on 1.5
You could try to remove the /e mount point for testing. It's possible that the problem I patched yesterday is the cause of the problem.
No, that didn't help. I didn't reboot but I did restart Cygwin which I think is enough.
For completeness I'm attaching my fstab. Would it help if I change "some_fs" to ntfs?
-- Lee Maschmeyer Computing Center Services Computing and Information Technology Wayne State UniversityDetroit, Michigan, USA
Attachment:
fstab
Description: Binary data
-- 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/
- Follow-Ups:
- Re: A path that's invalid on 1.7 but presumably valid on 1.5
- From: Corinna Vinschen
- Re: A path that's invalid on 1.7 but presumably valid on 1.5
- References:
- A path that's invalid on 1.7 but presumably valid on 1.5
- From: Lee Maschmeyer
- Re: A path that's invalid on 1.7 but presumably valid on 1.5
- From: Corinna Vinschen
- Re: A path that's invalid on 1.7 but presumably valid on 1.5
- From: Lee Maschmeyer
- Re: A path that's invalid on 1.7 but presumably valid on 1.5
- From: Corinna Vinschen
- A path that's invalid on 1.7 but presumably valid on 1.5
- Prev by Date: Re: write big buffer to connected socket, then close socket hangs cygwin
- Next by Date: Re: Freeze with the letter "e"
- Previous by thread: Re: A path that's invalid on 1.7 but presumably valid on 1.5
- Next by thread: Re: A path that's invalid on 1.7 but presumably valid on 1.5
- Index(es):