When the cygdrive prefix is /mnt (via fstab modification) vim swap
file creation malfunctions as following. Shell working directory is ~
in the examples but doesn't seem to matter:
vi -p foo /mnt/d/bar
(swap files created for both)
vi -p /mnt/d/bar foo
(swap file only created for bar)
vi -p
On 09/09/2014 08:03 PM, Mitch Deoudes wrote:
Thanks for the suggestions.
@Linda:
>> Have you tried 'mount -h'?
Yes - I believe I mentioned it above. Changing the prefix via mount does
not seem to survive between sessions, on this install.
@Andrey
>> Simplest would be to just reboot the box
Thanks for the suggestions.
@Linda:
>> Have you tried 'mount -h'?
Yes - I believe I mentioned it above. Changing the prefix via mount
does not seem to survive between sessions, on this install.
@Andrey
>> Simplest would be to just reboot the box to be absolutely sure.
I believe these boxes
Greetings, Mitch Deoudes!
> I'm teaching a class at a local college, and since their computer lab is
> stocked with Windows 7 & 8 machines, I had them install cygwin64 to use
> as a command line.
> The only change I requested they make to the config is to replace the
> "/cygdrive" in /etc/fstab w
Have you tried 'mount -h'?
It shows an option to change the cygdrive.
I've always used that. In regards to the cygdrive
prefix I thought the results of changing the prefix with
the 'mount' command were recorded in /etc/fstab --
and that it wasn't the source of t
I'm teaching a class at a local college, and since their computer lab is
stocked with Windows 7 & 8 machines, I had them install cygwin64 to use
as a command line.
The only change I requested they make to the config is to replace the
"/cygdrive" in /etc/fstab with "/". This is my config at home,
Matt D. wrote:
I've always used Cygwin's fstab /cygdrive default but I'm growing
tired of always typing it out; msys's simple "/a" "/c" "/d" prefix for
drive letters always seemed closer to home while on a Windows machine.
The only problem I've encountered is a borked ls display when an
actua
Matt D. writes:
> I've always used Cygwin's fstab /cygdrive default but I'm growing
> tired of always typing it out; msys's simple "/a" "/c" "/d" prefix for
> drive letters always seemed closer to home while on a Windows machine.
If typing is your problem then you can either use a shorter prefix l
On 07/22/2014 07:38 AM, Matt D. wrote:
I've always used Cygwin's fstab /cygdrive default but I'm growing tired of
always typing it out...
I'm in the habit of creating '/cygdrive' as a directory. Doing so gets me
tab-completion so I never have to type all of
On 7/22/2014 05:38, Matt D. wrote:
I've always used Cygwin's fstab /cygdrive default but I'm growing tired
of always typing it out; msys's simple "/a" "/c" "/d" prefix for drive
letters always seemed closer to home while on a Windows machine.
It's not clear to me from your message if you know t
On 7/22/2014 7:38 AM, Matt D. wrote:
I've always used Cygwin's fstab /cygdrive default but I'm growing tired of
always typing it out;
msys's simple "/a" "/c" "/d" prefix for drive letters always seemed closer to
home while on a
Windows machine.
The only problem I've encountered is a borked ls
I've always used Cygwin's fstab /cygdrive default but I'm growing tired
of always typing it out; msys's simple "/a" "/c" "/d" prefix for drive
letters always seemed closer to home while on a Windows machine.
The only problem I've encountered is a borked ls display when an actual
folder "a", "b
On 10/2/2013 7:45 PM, Diego Mesa wrote:
Hello!
I've tried the mount -c / command, as well as the changes in fstab
with a restart and it still doesnt work! Am I missing something?
You appear to be expecting that you can run the command above while
you're sitting in a path under /cygdrive and th
; # This is default anyway:
>>> #none /cygdrive cygdrive binary,posix=0,user 0 0
>>> none / cygdrive binary 0 0
>>>
>>> :pwd
>>> /cygdrive/c/Users/myname
>>>
>>> :ls -al
>>> .bashrc
>>>
>>
binary,posix=0,user 0 0
>> none / cygdrive binary 0 0
>>
>> :pwd
>> /cygdrive/c/Users/myname
>>
>> :ls -al
>> .bashrc
>>
>> The actual contents of C/users/myname are all of my custom files which
>> are not showing up here.
&
n of the file format, see the Users Guide
>> # http://cygwin.com/cygwin-ug-net/using.html#mount-table
>>
>> # This is default anyway:
>> none /cygdrive cygdrive binary,posix=0,user 0 0
>> none / cygdrive binary 0 0
>>
>> :ls
>> .bashrc
&g
unt-table
>
Seems the FAQ is missing the easiest method to change the /cygdrive
prefix. To make /cygdrive simply be / all you need is the following
command. Remove the lines you've inserted in /etc/fstab and then
execute the command.
$ mount -c /
--
Earnie
-- https://sites.google.com/s
d done as suggested on this realted question [#1] about
> removing cygdrive prefix but am still unable to get ride of the
> /cygdrive/c prefix, and have encountered even stranger errors!
>
> My True directory
> :pwd
> /cygdrive/c/Users/myname
> :ls
> file1
> fil
On 10/1/2013 17:55, Diego Mesa wrote:
none /cygdrive cygdrive binary,posix=0,user 0 0
none / cygdrive binary 0 0
You should pound the first line out, or remove it from the file
entirely. You're trying to define two conflicting "cygdrive"s here.
--
Problem reports: http://cyg
Hello,
Ive seen and done as suggested on this realted question [#1] about
removing cygdrive prefix but am still unable to get ride of the
/cygdrive/c prefix, and have encountered even stranger errors!
My True directory
:pwd
/cygdrive/c/Users/myname
:ls
file1
file2
...
My
Hi Brian,
On Sat, Aug 21, 2010 at 10:53 PM, Brian Kelly wrote:
>
> Ok - so I did a re-install and mount -p is back. But a setup "bug" (probably
> not setup.exe's fault) was discovered in the process.
>
> I first tried a re-install and once again was told cygwin1.dll could not be
> replaced beca
ocesses and services BEFORE running setup.exe. Otherwise ...
"your mileage may vary" ...
-Original Message-
>From: Brian Kelly
>Sent: Aug 21, 2010 3:18 PM
>To: cygwin@cygwin.com
>Subject: Re: 1.7.6-1: mount -p and mount --show-cygdrive-prefix broken in
>late
rian Kelly
>Sent: Aug 21, 2010 4:00 PM
>To: cygwin@cygwin.com
>Subject: Re: 1.7.6-1: mount -p and mount --show-cygdrive-prefix broken in
>latest release
>
>kb06...@chg211134 ~
>Here's the latest test - notice it reports correctly when just "mount" is
>invo
11134 ~
$
-Original Message-
>From: Corinna Vinschen
>Sent: Aug 21, 2010 3:29 PM
>To: cygwin@cygwin.com
>Subject: Re: 1.7.6-1: mount -p and mount --show-cygdrive-prefix broken in
>latest release
>
>On Aug 21 15:17, Brian Kelly wrote:
>> I have a script that relies o
tion - ''
>
> You get the same error when I tried the other argument:
>
> $ mount --show-cygdrive-prefix
> mount: invalid option - ''
>
> This behavior is seen in the straight bash environment, outside of my script.
> Apparently with the latest update. I
On 17/02/2010 11:03, Fergus wrote:
> On my system I've changed the cygdrive path prefix by setting
>mount -c "/"
> (and have done this for years). I've just tried using dvipdf which
> appears to have a hardwired requirement to locate a temporary file under
> /cygdrive/c/..
It seems pretty u
On my system I've changed the cygdrive path prefix by setting
mount -c "/"
(and have done this for years). I've just tried using dvipdf which
appears to have a hardwired requirement to locate a temporary file under
/cygdrive/c/.. and so I'm getting an error message
Could not open ..
and
On Jan 11 09:46, Karl M wrote:
>
> > Date: Mon, 11 Jan 2010 16:45:28 +
> > From: gchicares
> > Subject: Re: "mount -a" has no effect on the cygdrive prefix
> >
> > On 2010-01-11 16:16Z, Karl M wrote:
> >>
> >> I just reviewed chapte
> Date: Mon, 11 Jan 2010 16:45:28 +
> From: gchicares
> Subject: Re: "mount -a" has no effect on the cygdrive prefix
>
> On 2010-01-11 16:16Z, Karl M wrote:
>>
>> I just reviewed chapter 3 of the user guide and found no mention of posix=0
>
On 2010-01-11 16:16Z, Karl M wrote:
>
> I just reviewed chapter 3 of the user guide and found no mention of posix=0
> as the default for /cygdrive.
http://www.cygwin.com/cygwin-ug-net/using-specialnames.html
| To ease the pain, the /cygdrive path is case-insensitive by default
| and you have to
> Date: Mon, 11 Jan 2010 13:15:29 +0100
> From: corinna
> Subject: Re: "mount -a" has no effect on the cygdrive prefix
>
> On Dec 30 12:46, Corinna Vinschen wrote:
>> On Dec 29 16:27, Karl M wrote:
>>>> From: corinna-cygwin
>>>> The cygdr
On Dec 30 12:46, Corinna Vinschen wrote:
> On Dec 29 16:27, Karl M wrote:
> > > From: corinna-cygwin
> > > The cygdrive prefix is explicitely ignored when calling mount -a.
> > > The problem is, I'm not sure anymore *why* I did it that way.
> > > I adde
On Dec 29 16:27, Karl M wrote:
>
> > Date: Thu, 24 Dec 2009 12:10:47 +0100
> > From: corinna-cygwin
> > Subject: Re: "mount -a" has no effect on the cygdrive prefix
> >
> > On Dec 23 08:32, Karl M wrote:
> >> Hi All...
> >>
> >&g
> Date: Thu, 24 Dec 2009 12:10:47 +0100
> From: corinna-cygwin
> Subject: Re: "mount -a" has no effect on the cygdrive prefix
>
> On Dec 23 08:32, Karl M wrote:
>> Hi All...
>>
>> With the last 1.7.0 version and with a clean 1.7.1 install on an XP Pr
On Dec 23 08:32, Karl M wrote:
> Hi All...
>
> With the last 1.7.0 version and with a clean 1.7.1 install on an XP Pro SP3
> machine,
> if I edit my fstab to change my cygdrive prefix and then do a "mount -a", my
> mounts
> as shown by the mount command or catti
Hi All...
With the last 1.7.0 version and with a clean 1.7.1 install on an XP Pro SP3
machine,
if I edit my fstab to change my cygdrive prefix and then do a "mount -a", my
mounts
as shown by the mount command or catting mtab are not updated. I only tried it
with
the cygdrive p
that happens, *only* drives are enumerated
> since the cygdrive directory is a virtual directory anyway.
> This method can't work on / since then you would have a broken
> filesystem tree. That's why we frown on / as cygdrive directory (at
> least I do, but apparently nobod
On Sep 29 17:08, Mikel Ward wrote:
> Corinna Vinschen wrote:
> > > Is there any way to disable this special case to get the behavior I want
> > > with prefix=/?
> >
> > No, sorry.
>
> OK.
>
> I don't understand why, but if you don't have time to explain, that's
> fine.
I don't know what you wou
Corinna Vinschen wrote:
> > Is there any way to disable this special case to get the behavior I want
> > with prefix=/?
>
> No, sorry.
OK.
I don't understand why, but if you don't have time to explain, that's
fine.
But are there any other possible problems with having prefix=/ that I
should be
On Sep 29 09:19, Mikel Ward wrote:
> Corinna Vinschen wrote:
> > Mikel Ward wrote:
> > > If I use a standard install with the cygdrive prefix as /cygdrive, the
> > > drive letters appear in a directory listing:
> > >
> > > $ ls /cygdrive
> &g
Corinna Vinschen wrote:
> Mikel Ward wrote:
> > If I use a standard install with the cygdrive prefix as /cygdrive, the
> > drive letters appear in a directory listing:
> >
> > $ ls /cygdrive
> > c d w
> >
> > But if I change cygdrive to /, they don
On Sep 28 11:04, Mikel Ward wrote:
> Hi All
>
> If I use a standard install with the cygdrive prefix as /cygdrive, the
> drive letters appear in a directory listing:
>
> $ ls /cygdrive
> c d w
>
> But if I change cygdrive to /, they don't:
>
> $
Mikel Ward wrote:
Hi All
If I use a standard install with the cygdrive prefix as /cygdrive, the
drive letters appear in a directory listing:
$ ls /cygdrive
c d w
But if I change cygdrive to /, they don't:
$ mount -c /
$ ls /
Cygwin.bat bindev home optsbin usr
Cygwi
Hi All
If I use a standard install with the cygdrive prefix as /cygdrive, the
drive letters appear in a directory listing:
$ ls /cygdrive
c d w
But if I change cygdrive to /, they don't:
$ mount -c /
$ ls /
Cygwin.bat bindev home optsbin usr
Cygwin.ico cygdrive
> Wow. Nice summation of the reasons for the need for a c:\cygwin.
>
> Can I get a goldstar here?
Awarded. Sorry for the delay.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe
Linda Walsh (cyg...@tlinx.org) wrote:
> OTOH, at least the defaults are pretty sensible (I can just hit ENTER),
> through the setup -- EXCEPT...at the end -- how many times do I
> have to tell setup that I *STILL* don't want the icon on my desktop??!
I'm using cygwin on two different computers (h
Harald Joerg wrote:
> Linda Walsh writes:
>
>> [...] OTOH, at least the defaults are pretty sensible ...
>
> Pretty sensible, indeed. I love /cygdrive as just another example of a
> pretty sensible default.
---
Well, MS, put their unix in /unix. Wouldn't it make sense to put
a cygwin su
Hi Andy,
Andy Koppe wrote:
2009/9/16 Dave Korn:
whatever) prefixes when accessing stuff from the other side of the
fence.
Never mind the fence, what colour are we going to paint the bikeshed?
This is purely a matter of taste.
Exactly. I didn't mean to suggest that Cygwin sh
Christopher Faylor wrote:
Haven't we already looped several times in this discussion? I don't
think there is any new information that needs to be imparted. Can we
close this down now?
People obviously wish to discuss the issue. If you're not interested in
their discussion then can't you simply
Jim Reisert AD1C wrote:
On Wed, Sep 16, 2009 at 10:16 AM, Andrew Schulman
wrote:
Personally I like /win/c etc., but sure, I guess you could put
none / cygdrive binary,posix=0,user 0 0
into /etc/fstab and get /c, /d, etc.
There is a huge downside to this. I tried it. It totally broke all my
p
On Thu, Sep 17, 2009 at 06:25:44PM -0600, Eric Blake wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>According to Larry Hall (Cygwin) on 9/17/2009 12:53 PM:
>> While I'm not suggesting that people should reassign their "cygdrive"
>> prefix
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Larry Hall (Cygwin) on 9/17/2009 12:53 PM:
> While I'm not suggesting that people should reassign their "cygdrive"
> prefix
> to "/", I think the problem you saw in your case is a result of having set
&g
it. It totally broke all my
projects using CVS, because /cygdrive no longer existed, and all my
CVS projects used /cygdrive/f/CVSROOT as the Root
So try/use at your own risk! I think symbolic links are the way to go.
While I'm not suggesting that people should reassign their "cygdri
On Wed, Sep 16, 2009 at 10:16 AM, Andrew Schulman
wrote:
> Personally I like /win/c etc., but sure, I guess you could put
>
> none / cygdrive binary,posix=0,user 0 0
>
> into /etc/fstab and get /c, /d, etc.
There is a huge downside to this. I tried it. It totally broke all my
projects using CV
On Thu, Sep 17, 2009 at 06:36:26AM +0100, Andy Koppe wrote:
>2009/9/17 Christopher Faylor:
>>>My real gripe is with setup telling me off about putting Cygwin in the
>>>root dir ON EVERY SINGLE UPDATE.
>>
>> My real gripe is people who COMPLAIN ABOUT FREE SOFTWARE where they
>> HAVE THE SOURCE CODE.
On 09/17/2009 01:18 AM, Andy Koppe wrote:
2009/9/16 Dave Korn:
whatever) prefixes when accessing stuff from the other side of the
fence.
Never mind the fence, what colour are we going to paint the bikeshed?
This is purely a matter of taste.
Exactly. I didn't mean to suggest that Cygwin
Harald Joerg wrote:
... -- EXCEPT...at the end -- how many times do I have to tell setup
that I *STILL* don't want the icon on my desktop??!
I eventually got around that one.
I found that I do not want *any* icons on my desktop and switched them
off completely. There is an option in the "Sor
Linda Walsh writes:
> [...] OTOH, at least the defaults are pretty sensible ...
Pretty sensible, indeed. I love /cygdrive as just another example of a
pretty sensible default.
> ... (I can just hit ENTER), through the setup ...
...and the default buttons in the GUI are always in the same place
* Andy Koppe (Wed, 16 Sep 2009 22:06:45 +0100)
> 2009/9/16 Thorsten Kampe
> > you shouldn't install Cygwin
> > directly to C:\ (but to C:\cygwin): so you don't have the Cygwin and the
> > Windows root folder structure mixed.
>
> And where exactly is the harm in that? Apple certainly don't see a
>
Shaddy Baddah wrote:
> In this case, although cygwin has a package management system, it is
> not going to manage the non-cygwin stuff dropped into c:/bin,lib,
> etc. And that means if a user goes and installs something like msys
---
I knew I had a good reason for thinking it would cause tr
Andy Koppe wrote:
> 2009/9/17 Christopher Faylor:
>>> My real gripe is with setup telling me off about putting Cygwin in the
>>> root dir ON EVERY SINGLE UPDATE.
>> My real gripe is people who COMPLAIN ABOUT FREE SOFTWARE where they
>> HAVE THE SOURCE CODE.
>
> Ah, that old lazy chestnut. Feedback
2009/9/17 Christopher Faylor:
>>My real gripe is with setup telling me off about putting Cygwin in the
>>root dir ON EVERY SINGLE UPDATE.
>
> My real gripe is people who COMPLAIN ABOUT FREE SOFTWARE where they
> HAVE THE SOURCE CODE.
Ah, that old lazy chestnut. Feedback not welcome. At least get a
On Thu, Sep 17, 2009 at 06:18:21AM +0100, Andy Koppe wrote:
>2009/9/16 Dave Korn:
>>> whatever) prefixes when accessing stuff from the other side of the
>>> fence.
>>
>> ??Never mind the fence, what colour are we going to paint the bikeshed?
>>
>> ??This is purely a matter of taste.
>
>Exactly. I d
2009/9/16 Dave Korn:
>> whatever) prefixes when accessing stuff from the other side of the
>> fence.
>
> Never mind the fence, what colour are we going to paint the bikeshed?
>
> This is purely a matter of taste.
Exactly. I didn't mean to suggest that Cygwin should go into C:\ by
default. And ye
Hi,
Before I start, I want to admit that I think I may have
misinterpreted Andy Koppe's email. I now see that Andy may have been
defending *not* demarcating the rest of the windows world with a
/cygdrive prefix by just having all c:/ subpaths accessabile directly
from the / prefix. That
On Wed, Sep 16, 2009 at 9:44 PM, Christopher Faylor wrote:
[re: Shaddy Baddah]
> Wow. Nice summation of the reasons for the need for a c:\cygwin.
>
> Can I get a goldstar here?
Indeed, a nice summary.
Let me dispel some misconceptions that piped up in the Apple
comparison: the two ways of thinki
On Thu, Sep 17, 2009 at 11:35:11AM +1000, Shaddy Baddah wrote:
>Hi,
>
>Andy Koppe wrote:
>> 2009/9/16 Thorsten Kampe
>>
>>> you shouldn't install Cygwin
>>> directly to C:\ (but to C:\cygwin): so you don't have the Cygwin and the
>>> Windows root folder structure mixed.
>>>
>>
>> And where
Hi,
Andy Koppe wrote:
2009/9/16 Thorsten Kampe
you shouldn't install Cygwin
directly to C:\ (but to C:\cygwin): so you don't have the Cygwin and the
Windows root folder structure mixed.
And where exactly is the harm in that? Apple certainly don't see a
problem with it, with the likes
s directly to a drive without entering
> cygdrive? Is there any reason for that ?
----
Just set your cygdrive prefix to "" (null)
Then you can use /d/, /e/, and _usually_, "/" = your root drive
...
Works REAL well, when you install cygwin in the root dir, since then all the
p
On Wed, Sep 16, 2009 at 10:40:33PM +0100, Dave Korn wrote:
>Andy Koppe wrote:
>> 2009/9/16 Thorsten Kampe
>> whatever) prefixes when accessing stuff from the other side of the
>> fence.
>
> Never mind the fence, what colour are we going to paint the bikeshed?
Please take this discussion to cygwin
to c:\windows:
$ cd /cygdrive/c/windows
To get to c:\cygwin:
$ cd /cygdrive/c/cygwin
or $ cd /
Now do the following (in cygwin 1.5; I don't know how ver. 1.7 works)
(though you might want to add some other flags, e.g., -b or -u)
$ mount --change-cygdrive-pref
Andy Koppe wrote:
> 2009/9/16 Thorsten Kampe
> whatever) prefixes when accessing stuff from the other side of the
> fence.
Never mind the fence, what colour are we going to paint the bikeshed?
This is purely a matter of taste. To each their own and de gustibus non
disputandum est.
cheer
2009/9/16 Thorsten Kampe
> you shouldn't install Cygwin
> directly to C:\ (but to C:\cygwin): so you don't have the Cygwin and the
> Windows root folder structure mixed.
And where exactly is the harm in that? Apple certainly don't see a
problem with it, with the likes of /Applications and /Users l
* Vincent R. (Wed, 16 Sep 2009 18:08:59 +0200)
>
> On Wed, 16 Sep 2009 09:02:19 -0700, Andrew DeFaria
> wrote:
> > Vincent R. wrote:
> >> Hi,
> >>
> >> Is there any good reason to force user to use /cygdrive/ before
> >> accessing a drive ?
> > Considering you aren't forced to use /cygdrive/ (se
Vincent R. wrote:
> Wouldn't be easier to access directly to a drive without entering
> cygdrive? Is there any reason for that ?
Dave Korn wrote:
> Go ahead. You can create a mountpoint anywhere you like, so if you want
> MinGW-style /c, /d, etc., just use the 'mount' command or edit the fstab.
> > Wouldn't be easier to access directly to a drive without entering
> > cygdrive? Is there any reason for that ?
>
> Go ahead. You can create a mountpoint anywhere you like, so if you want
> MinGW-style /c, /d, etc., just use the 'mount' command or edit the fstab.
Personally I like /win/c et
Vincent R. wrote:
Ok I see your point but I find it weird to complicate things by adding
/cygdrive.
/cygdrive is just the string of characters the coder implementing that
code choose to use. Be thankful. He could have choose
/ThisIsThePathIWantedToUseToIndicateWindowsDrives! ;-)
Maybe some pe
On Wed, 16 Sep 2009 09:02:19 -0700, Andrew DeFaria
wrote:
> Vincent R. wrote:
>> Hi,
>>
>> Is there any good reason to force user to use /cygdrive/ before
>> accessing a drive ?
> Considering you aren't forced to use /cygdrive/ (see mount(1m)) no...
>> I am asking it because I regularly switch fr
Vincent R. wrote:
Hi,
Is there any good reason to force user to use /cygdrive/ before
accessing a drive ?
Considering you aren't forced to use /cygdrive/ (see mount(1m)) no...
I am asking it because I regularly switch from cygwin to mingw and
some simple script needs to be adapted every time.
Vincent R. wrote:
> Wouldn't be easier to access directly to a drive without entering
> cygdrive? Is there any reason for that ?
Go ahead. You can create a mountpoint anywhere you like, so if you want
MinGW-style /c, /d, etc., just use the 'mount' command or edit the fstab.
cheers,
Hi,
Is there any good reason to force user to use /cygdrive/ before accessing
a drive ?
I am asking it because I regularly switch from cygwin to mingw and some
simple script needs
to be adapted every time.
Wouldn't be easier to access directly to a drive without entering
cygdrive? Is there any rea
"Stepp, Charles" wrote:
> Symlink?
>
> ln -s /cygdrive/c /c
Oh please no. If you want that just set the cygdrive prefix to /
("mount -c /").
Brian
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.co
On 6/15/06, Buchbinder, Barry (NIH/NIAID) [E] wrote:
Does the following do what you want?
mount -u -b --change-cygdrive-prefix "/"
Stepp, Charles wrote:
> Symlink?
>
> ln -s /cygdrive/c /c
No... Thanks but no. Barry and Charles, i think you're answering a
d
Does the following do what you want?
mount -u -b --change-cygdrive-prefix "/"
You may want to change the -u and -b options to fit your circumstances.
(I'm surprised that this wasn't mentioned previously, so I may have
misunderstood and this may not be the sol
Symlink?
ln -s /cygdrive/c /c
Charles Stepp
Unix SA
CYGWIN ROCKS!!
-Original Message-
From: kralius [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 13, 2006 11:26 PM
To: cygwin@cygwin.com
Subject: Re: cygdrive flags / hiding cygdrive prefix directory (the old
behavior)
Thanks for the
system called cygdrive,
> >
> > I don't know where you got this idea but it's absolutely not true.
> > There should never be a physical directory backing the cygdrive prefix,
> > and no package (and certainly not setup.exe) should ever create it.
> > Some users
e a physical directory backing the cygdrive prefix,
and no package (and certainly not setup.exe) should ever create it.
Some users may create it to assist in tab-completion, but that is
something they would have done by hand.
I agree that it shouldn't create this directory... But i have tried
kralius wrote:
> changed to become visible. The cygwin installer now also creates a
> real directory on the windows file system called cygdrive,
I don't know where you got this idea but it's absolutely not true.
There should never be a physical directory backing the cygdriv
0PM -0500, kralius wrote:
>I'm trying to find a way to make the cygdrive prefix directory
>(default: /cygdrive) appear hidden within cygwin (for example, to ls or
>find).
>
>This was actually the old behavior in cygwin, but at some point it
>changed to become visible. The
On Tue, Jun 13, 2006 at 08:22:20PM -0500, kralius wrote:
>I'm trying to find a way to make the cygdrive prefix directory
>(default: /cygdrive) appear hidden within cygwin (for example, to ls or
>find).
>
>This was actually the old behavior in cygwin, but at some point it
>ch
I'm trying to find a way to make the cygdrive prefix directory
(default: /cygdrive) appear hidden within cygwin (for example, to ls
or find).
This was actually the old behavior in cygwin, but at some point it
changed to become visible. The cygwin installer now also creates a
real directo
wrote:
> > > > >Is there a way to find out in a bash script the cygdrive prefix?
> > > > >I thought something simple like
> > > > > mount -p|tail -1|cut -f1
> > > > >but that incorrectly assumed the fields were tab delimited.
>
On Tue, 2005-08-16 at 20:41 -0500, Gary R. Van Sickle wrote:
> [snip]
> >
> > NOTE: A digital camera shows up as an USB drive, i.e. a DOS
> > drive -> e.g. /cygdrive/ - and is available
> > so long as the camera stays ON (it eventually WILL go OFF
> > after last use, just as your screen blanker
Gary R. Van Sickle wrote:
[snip]
NOTE: A digital camera shows up as an USB drive, i.e. a DOS
drive -> e.g. /cygdrive/ - and is available
so long as the camera stays ON (it eventually WILL go OFF
after last use, just as your screen blanker! Depending on how
you've set it or use it.)
[snip]
>
> NOTE: A digital camera shows up as an USB drive, i.e. a DOS
> drive -> e.g. /cygdrive/ - and is available
> so long as the camera stays ON (it eventually WILL go OFF
> after last use, just as your screen blanker! Depending on how
> you've set it or use it.)
>
A USB Mass Storage De
From: Sam Steingold
Subject: Re: Programatically finding value of "cygdrive" prefix
Date: Tue, 16 Aug 2005 17:51:00 -0400
> * Igor Pechtchanski <[EMAIL PROTECTED]> [2005-08-16 17:10:25 -0400]:
>
>
> was asking for the actual problem that programmatically accessi
Sam Steingold wrote:
> > was asking for the actual problem that programmatically accessing the
> > cygdrive prefix was supposed to solve.
>
> I already explained that in
> <http://article.gmane.org/gmane.os.cygwin:67856>.
>
> let me try to do it again:
>
&
> * Igor Pechtchanski <[EMAIL PROTECTED]> [2005-08-16 17:10:25 -0400]:
>
>
> was asking for the actual problem that programmatically accessing the
> cygdrive prefix was supposed to solve.
I already explained that in
<http://article.gmane.org/gmane.os.cygwin:67856>.
On Tue, 16 Aug 2005, Christopher Faylor wrote:
> On Tue, Aug 16, 2005 at 05:10:25PM -0400, Igor Pechtchanski wrote:
> >There may not be a C: drive, but "cygpath -u c:" will do the right thing
> >-- try it with a drive you don't have.
>
> mount -f c: /willthisthreadeverdie
> cygpath -u c:
> /
On Tue, Aug 16, 2005 at 05:28:26PM -0400, Christopher Faylor wrote:
>On Tue, Aug 16, 2005 at 05:10:25PM -0400, Igor Pechtchanski wrote:
>>There may not be a C: drive, but "cygpath -u c:" will do the right thing
>>-- try it with a drive you don't have.
>
> mount -f c: /willthisthreadeverdie
> cygp
1 - 100 of 157 matches
Mail list logo
