public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: richw <richaw@gmail.com>
To: cygwin@cygwin.com
Subject: Re: /bin and /lib mount points occasionally lost
Date: Wed, 20 Jun 2012 18:55:00 -0000	[thread overview]
Message-ID: <34044781.post@talk.nabble.com> (raw)
In-Reply-To: <87hau5esiq.fsf@Rainer.invalid>


So the domain is "." and the account "nfs"?

I have no idea what .\nfs means. I'm just reporting what services reports.

>>Those should see the following mount points according to cygcheck3.out:
> I don't have /usr/bin or /usr/lib in exports, but I think you are
> saying that if I did, I could access them via NFS.

Maybe.  It could be worth a try.

Works, but not as I expected, as in another post (exporting /usr/bin
allowed /bin to be mounted successfully)

>>When you run bash before starting the daemons you said you see these
>>mounts instead:
> I goofed, and didn't initially notice the 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).

Do the mounts resurrect correctly via "mount -a"?

mount -a does not resurrect mounts.

> When I reboot and run bash first, I see (auto) as expected.
> /etc/fstab is empty (except for comments), as is /etc/fstab.d

Do you get things back to working state by closing all Cygwin
applications, then stopping all Cygwin services and then starting bash?

Yes, this did work. Bash started up normally.

Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   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 from the Cygwin list mailing list archive at Nabble.com.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2012-06-20 18:55 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-13 17:19 richw
2012-06-13 17:48 ` Christopher Faylor
2012-06-13 19:47   ` richw
2012-06-13 21:05     ` marco atzeri
2012-06-13 22:38       ` richw
2012-06-13 22:50 ` Warren Young
2012-06-13 23:33   ` richw
2012-06-14  1:03     ` Warren Young
2012-06-14  1:21       ` richw
2012-06-14  4:20         ` Christopher Faylor
2012-06-19 17:06 ` richw
2012-06-19 18:16   ` Achim Gratz
2012-06-19 19:15     ` richw
2012-06-19 21:07       ` Achim Gratz
2012-06-20  1:07         ` richw
2012-06-20  4:39           ` marco atzeri
2012-06-20  5:26             ` richw
2012-06-20  7:08               ` marco atzeri
2012-06-20 15:43                 ` richw
2012-06-20 17:23                   ` Achim Gratz
2012-06-20 18:23                     ` richw
2012-06-20 18:41                       ` Achim Gratz
2012-06-20 18:55                         ` richw [this message]
2012-06-20 18:45                     ` richw
2012-06-20 18:55                       ` marco atzeri
2012-06-20 19:23                       ` Achim Gratz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=34044781.post@talk.nabble.com \
    --to=richaw@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).