public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: cygwin@kosowsky.org
To: cygwin@cygwin.com
Subject: Re: Home directory not accessible but really there...
Date: Wed, 28 Aug 2019 16:14:00 -0000	[thread overview]
Message-ID: <23910.42455.722565.268415@consult.pretender> (raw)
In-Reply-To: <23909.35055.868804.891225@consult.pretender>

Silly me -- problem was due to a typo in an old (and forgotten)
fstab.d file.
Never mind. Sorry for the troubles...

"" wrote at about 15:47:59 -0400 on Tuesday, August 27, 2019:
 > In summary:
 > 1. Home directory is not accessible via: 'cd <return>' or 'cd ~' (it
 >    takes me to /tmp) and 'ls -al /home' shows my home directory as
 >    having corrupted permissions, UID and GID (all are ???)
 > 
 > 2. Home directory is accessible and shows proper perms/UID/GID when I
 >    go there with the full path from /cygdrive/c
 > 
 > Specifically, 
 > 
 > After installing cygwin (using --noadmin flag), rebooting, and
 > launching a cygwin shell, I get the message:
 >     mkdir: cannot create directory '/home/myname': No such file or directory
 >     /home/myname could not be created.
 >     Setting HOME to /tmp
 > 
 > Then, if I go to /home and type:
 >       #ls -al
 >       ls: cannot access 'myname': No such file or directory
 >       total 4
 >       drwxrwxrwt+ 1 myname somegroup(513) 0 Aug 27 15:35 .
 >       drwx------+ 1 myname somegroup(513) 0 Aug 25 17:55 ..
 >       d?????????? ? ?      ?              ?            ? myname
 > 
 > And, indeed from there, I can't ls/cd into the 'myname' home directory
 > - nor can I change the perms or uid/gid.
 > 
 > HOWEVER, if I go manually to the home directory using the full path
 > relative to C:, everything seems fine.
 > 
 > #cd /cygdrive/c/Users/myname/Desktop/cygwin/home
 > #ls -al
 > drwxrwxrwt+ 1 myname somegroup(513) 0 Aug 27 15:35 .
 > drwx------+ 1 myname somegroup(513) 0 Aug 25 17:55 ..
 > drwxr-xr-x+ 1 myname somegroup(513) 0 Aug 27 14:55 myname
 > 
 > And I can then ls/cd into the intact 'myname' home directory.
 > 
 > Note I don't have admin permission on this machine so I used
 > 'cygwin-setup --no-admin' to install Cygwin.
 > 
 > --
 > 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
 > 

--
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:[~2019-08-28 16:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-27 20:37 cygwin
2019-08-28 16:14 ` cygwin [this message]

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=23910.42455.722565.268415@consult.pretender \
    --to=cygwin@kosowsky.org \
    --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).