From: "Hannu E K Nevalainen" <garbage_collector@telia.com>
To: "ML CygWIN" <cygwin@cygwin.com>
Subject: RE: echo $HOME returns /cygdrive/c/documents and setting/mrane
Date: Thu, 06 May 2004 20:19:00 -0000 [thread overview]
Message-ID: <NGBBLLIAMFLGJEOAJCCEKELCDKAA.garbage_collector@telia.com> (raw)
In-Reply-To: <409A78A8.8000508@x-ray.at>
> From: Reini Urban
> Sent: Thursday, May 06, 2004 7:41 PM
> Igor Pechtchanski schrieb:
> > Or 'mount -s c:/Documents\ and\ Settings/ /home', if you don't mind
> > putting up with '/home/All Users', etc...
>
> Sure, mount is the method which is used more often.
> And it is faster and easier.
> But it is not as transparent to the poor end-user as the symlinks.
> He will not see /home when doing "ls /"
YET another POV (YAPOV!); To be "safe" (THIS IS UNTESTED! BEWARE ;-)
with one little difference...
$ cd /home
$ tar --create --remove-files - * | \
tar --directory="$(cygpath -u -H)" --extract -
$ mount "$(cygpath -w -H)" /home
i.e. what I've attempted to describe here is, line by line:
1 - work from any existing "/home" (assumes "/home/" exists!)
2 - move any files to the new position
3 - reposition /home
NOTE for the diff: leave /home/ as an empty directory, thus it WILL show up
with "ls" and in name completions (will work for anything *in* /home too)
and whatever you try...
/Hannu E K Nevalainen, B.Sc. EE - 59+16.37'N, 17+12.60'E
** on a mailing list; please keep replies on that particular list **
-- printf("LocalTime: UTC+%02d\n",(DST)? 2:1); --
--END OF MESSAGE--
--
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/
next prev parent reply other threads:[~2004-05-06 20:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-05 22:41 Montana Rane
2004-05-06 1:18 ` Larry Hall
2004-05-06 10:02 ` Reini Urban
2004-05-06 13:27 ` Igor Pechtchanski
2004-05-06 17:47 ` Reini Urban
2004-05-06 20:19 ` Hannu E K Nevalainen [this message]
2004-05-07 17:10 ` Christopher Faylor
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=NGBBLLIAMFLGJEOAJCCEKELCDKAA.garbage_collector@telia.com \
--to=garbage_collector@telia.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).