richw writes:
> I modified /etc/exports to read
> / (ro,no_root_squash)
> /usr/bin (ro,no_root_squash)
> /usr/lib (ro,no_root_squash)
> and then tried a mount.
> I was surprised that I could not mount /usr/bin, but I could mount /bin.
> (Is that correct? Why?)
It probably means that /usr/lib and /
On 6/20/2012 8:45 PM, richw wrote:
ASSI wrote:
Those should see the following mount points according to cygcheck3.out:
C:\cygwin/ system binary,auto
C:\cygwin\bin/usr/bin system binary,auto
C:\cygwin\lib/usr/lib system binary,auto
cygdrive prefix /cygdrive
http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
--
View this message in context:
http://old.nabble.com/-bin-and--lib-mount-points-occasionally-lost-tp34007108p34044781.html
Sent
t: Mounting 192.168.1.40:/usr/bin on /mnt failed: Invalid argument
> 50:/root # mount 192.168.1.40:/bin /mnt
> 50:/root # ls /mnt/y*
> /mnt/yacc /mnt/yes.exe
> 50:/root #
--
View this message in context:
http://old.nabble.com/-bin-and--lib-mount-points-occasionally-lost-tp34007108p
richw writes:
>>when you access the NFS export, three daemons get started
>>(mountd, nfsd and portmap) under their own account (apparently .\nfs?).
> The daemons are apparently started before the NFS export is accessed.
> At least, the windows "services" report shows them as "started".
> The logon
difference between (user) and
(auto) in
the mount command response. When I do the mount manually to correct
for the missing mount, it shows (user). When I reboot and run bash first,
I see (auto) as expected.
/etc/fstab is empty (except for comments), as is /etc/fstab.d
--
View this message in cont
richw writes:
> I believe what needs to be studied is why an access from a remote system
> to an nfs file system before opening a bash prompt causes the automatic
> mount of /usr/bin and /usr/lib to be skipped.
With the most likely problem apparently out of the way, let's look at
the second: when
access from a remote system
to an nfs file system before opening a bash prompt causes the automatic
mount of /usr/bin and /usr/lib to be skipped.
When I open a bash prompt before accessing the nfs file system, everything
works as it should.
cygcheck2.out was created when the system was working correct
On 6/20/2012 7:26 AM, richw wrote:
marco atzeri-4 wrote:
cool down
your message of 19 Jun
http://cygwin.com/ml/cygwin/2012-06/msg00336.html
...
has still an old one cygcheck.out as link.
so please so kind to provide us the right and updated info
Regards
Marco
I apologize. I have app
ly been bitten by uploading two different files
with the same name. When I clicked on the link in the message of the 19th, I
got the correct file. So, after a name change, we have:
http://old.nabble.com/file/p34040469/cygcheck2.out cygcheck2.out
--
View this message in context:
http://old.nabble.co
On 6/20/2012 3:07 AM, richw wrote:
ASSI wrote:
richw writes:
rw@seven ~
$ /bin/uname -a
CYGWIN_NT-6.1-WOW64 seven 1.7.15(0.260/5/3) 2012-05-09 10:25 i686 Cygwin
Your cygcheck.out said I should be expecting a 1.7.11 version here. So
maybe you didn't nuke all extra versions or your cygcheck
t's the date
on the file. An excerpt from that file:
2235k 2012/05/09 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
"cygwin1.dll" v0.0 ts=2012/5/9 9:25
Cygwin DLL version info:
DLL version: 1.7.15
--
View this message in context:
http://old.nabb
richw writes:
>> rw@seven ~
>> $ /bin/uname -a
>> CYGWIN_NT-6.1-WOW64 seven 1.7.15(0.260/5/3) 2012-05-09 10:25 i686 Cygwin
Your cygcheck.out said I should be expecting a 1.7.11 version here. So
maybe you didn't nuke all extra versions or your cygcheck output wasn't
for your actual installation...
WIN_NT-6.1-WOW64 seven 1.7.15(0.260/5/3) 2012-05-09 10:25 i686 Cygwin
>
> rw@seven ~
> $
--
View this message in context:
http://old.nabble.com/-bin-and--lib-mount-points-occasionally-lost-tp34007108p34038496.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Pr
richw writes:
[...]
> A reboot fixes the problem, as long as I run cygwin.bat before I access nfs.
The problem quite likely lies with your 11 different copies of
cygwin1.dll. You start the NFS server and it picks up one of those,
just not the one for your actual Cygwin installation. Now Cygwin i
noumount,auto)
>
> rw@seven ~
>
A reboot fixes the problem, as long as I run cygwin.bat before I access nfs.
--
View this message in context:
http://old.nabble.com/-bin-and--lib-mount-points-occasionally-lost-tp34007108p34037768.html
Sent from the Cygwin list mailing list archive at
On Wed, Jun 13, 2012 at 06:21:13PM -0700, richw wrote:
>
>
>Warren Young wrote:
>>
>> On 6/13/2012 5:32 PM, richw wrote:
>>>
>>> What was I doing? I rebooted the computer.
>>
>> You're being pedantic. I mean, what program(s) did you run before you
>> noticed Cygwin stopped working, causing you
of the copies.
If the problem recurs in a week or a month, I'll come back here!
If it doesn't, thanks for your help.
--
View this message in context:
http://old.nabble.com/-bin-and--lib-mount-points-occasionally-lost-tp34007108p34009433.html
Sent from the Cygwin list mailin
On 6/13/2012 5:32 PM, richw wrote:
What was I doing? I rebooted the computer.
You're being pedantic. I mean, what program(s) did you run before you
noticed Cygwin stopped working, causing you to reboot to fix it?
I believe you are running something that fights with Cygwin somehow, and
thi
l, but I have never run it.
The other two copies on C: are detritus left over from creating
a windows installer that included it, before I figured out how to make
an executable that didn't require it.
--
View this message in context:
http://old.nabble.com/-bin-and--lib-mount-points-occasional
On 6/13/2012 11:19 AM, richw wrote:
I occasionally find that cygwin is broken, and I find that /usr/bin and
/usr/lib no longer are useful.
It would help if you could pin down what you were doing before Cygwin
breaks each time.
Can you please search your entire hard drive for a second copy o
ated
> by the Cygwin DLL similar to the way the root directory is evaluated.
> /usr/bin points to the directory the Cygwin DLL is installed in, /usr/lib
> is supposed to point to the /lib directory. This choice is safe and
> usually shouldn't be changed. An fstab entry for them
On 6/13/2012 9:47 PM, richw wrote:
Christopher Faylor-8 wrote:
On Wed, Jun 13, 2012 at 10:19:42AM -0700, richw wrote:
I occasionally find that cygwin is broken, and I find that /usr/bin and
/usr/lib no longer are useful. The mount command (for which I need to
type /bin/mount) shows nothing
ive/d type ntfs (binary,posix=0,user,noumount,auto)
rw@seven ~
$
I note that another cygwin installation has (binary,auto) instead of
(binary,user) for the two mounts in question.
--
View this message in context:
http://old.nabble.com/-bin-and--lib-mount-points-occasionally-lost-tp3400710
On Wed, Jun 13, 2012 at 10:19:42AM -0700, richw wrote:
>I occasionally find that cygwin is broken, and I find that /usr/bin and
>/usr/lib no longer are useful. The mount command (for which I need to
>type /bin/mount) shows nothing mounted there. I type the following two
>commands:
>mount c:/cygwi
(through reboots) for a while, and then break again.
Any hints how I can keep this from happening, or what might cause it?
--
View this message in context:
http://old.nabble.com/-bin-and--lib-mount-points-occasionally-lost-tp34007108p34007108.html
Sent from the Cygwin list mailing list archive at
26 matches
Mail list logo
