//
Which is bad since FAT32 has no security at all. Any process of any
user on the machine can overwrite any file, even in the Windows folder.
NTFS is much more secure and has a couple of features you never get with
FAT32, and hardlinks are only one minor advantage. You should really
update the
On 11/11/2009 07:40, Fergus wrote:
I have made no alterations/ patches/ amendments and have a completely
current [1.7] system.
For all of
cygwin1.7.61.dll - cygwin1.7.64.dll
the command
run XWin
fails with a reference to /vat/log/XWin.0.log which reads
Can't read lock file /tmp/.X0.lock
On 11/11/2009 10:07, Corinna Vinschen wrote:
On Nov 11 07:40, Fergus wrote:
Q1. Is it still the case that this problem is not well understood
as in this reference?
http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-cant-read-lock-file
Hardlinks don't work on FAT filesystems since FAT
On Nov 11 07:40, Fergus wrote:
Q1. Is it still the case that this problem is not well understood
as in this reference?
http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-cant-read-lock-file
Hardlinks don't work on FAT filesystems since FAT doesn't support them.
Up to Cygwin 1.7.0-60,
On 11/11/2009 02:40 AM, Fergus wrote:
Q4 Why are questions about X specifically directed to a different
mailing list? Apart from occasional high-frequency dialogue as at
present, posts about X are (or seem to me to be) no more frequent than
posts about grep or ls or chmod or ... . The main
I have made no alterations/ patches/ amendments and have a completely
current [1.7] system.
For all of
cygwin1.7.61.dll - cygwin1.7.64.dll
the command
run XWin
fails with a reference to /vat/log/XWin.0.log which reads
Can't read lock file /tmp/.X0.lock
But when reverting
Cygwin gurus,
After happily using cygwin-X for many years, I have just encountered
my first true frustration.
After updating my cygwin distribution earlier this week, I found that
I can no longer start X windows, getting the same can't read lock
file that other users have experienced.
I tried
Rich Signell wrote:
Cygwin gurus,
After happily using cygwin-X for many years, I have just encountered
my first true frustration.
After updating my cygwin distribution earlier this week, I found that
I can no longer start X windows, getting the same can't read lock
file that other users have
James Ertle wrote:
Fatal server error:
Can't read lock file /tmp/.X0-lock
As a workaround, you should be able to add -nolock to the command line used
to start Xwin (in startxwin.bat, I'm guessing, in your case).
Since a few people seem to have this problem, I'd like to get a resolution.
Sadly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon TURNEY wrote:
Sadly, I have no theory about how this could be happening, except perhaps it
could be related to 'unusual' permissions on /tmp which could somehow let you
create but not rename a file (so the output of 'ls -al /tmp' might
Jon TURNEY wrote:
James Ertle wrote:
Fatal server error:
Can't read lock file /tmp/.X0-lock
As a workaround, you should be able to add -nolock to the command line used
to start Xwin (in startxwin.bat, I'm guessing, in your case).
Since a few people seem to have this problem, I'd like
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon TURNEY wrote:
Ok, my archaeological investigations in this area have revealed that this
locking code probably wasn't enabled in 6.8.99. I don't think it is actually
giving any benefit, since we also have a native named mutex is used in the
12 matches
Mail list logo
