On Fri, Oct 13, 2006 at 02:43:45PM -0700, Joshua Daniel Franklin wrote:
>On 10/11/06, Christopher Faylor wrote:
>>Good point, Brian. If anything qualifies as a FAQ, this certainly does.
>>Joshua, would you be willing to write something up about the philosophy
>>of MS-DOS and Cygwin? Known gotchas
On 10/11/06, Christopher Faylor wrote:
Good point, Brian. If anything qualifies as a FAQ, this certainly does.
Joshua, would you be willing to write something up about the philosophy
of MS-DOS and Cygwin? Known gotchas would be a good thing to include,
even if they were only examples.
This lo
On Fri, 13 Oct 2006, Christopher Faylor wrote:
> On Fri, Oct 13, 2006 at 10:18:17AM -0400, Igor Peshansky wrote:
> >On Thu, 12 Oct 2006, Igor Peshansky wrote:
> >> [...] And if we make it the job of /etc/postinstall/base-files-mketc.sh,
> >> we're depriving the user of a scarce resource -- a mount
On Fri, Oct 13, 2006 at 10:18:17AM -0400, Igor Peshansky wrote:
>On Thu, 12 Oct 2006, Igor Peshansky wrote:
>> [...] And if we make it the job of /etc/postinstall/base-files-mketc.sh,
>> we're depriving the user of a scarce resource -- a mount table entry
>> (unless we raise the limit, but then aga
On Fri, 13 Oct 2006, Corinna Vinschen wrote:
> On Oct 12 22:08, Igor Peshansky wrote:
> > On Thu, 12 Oct 2006, Corinna Vinschen wrote:
> > > > So it looks like using mixed paths (cygpath -m) would be an easy way
> > > > out of this for now.
> > >
> > > Naah, scratch that. Creating a mount point f
On Oct 12 22:08, Igor Peshansky wrote:
> On Thu, 12 Oct 2006, Corinna Vinschen wrote:
> > > So it looks like using mixed paths (cygpath -m) would be an easy way
> > > out of this for now.
> >
> > Naah, scratch that. Creating a mount point for $SYSTEMROOT seems the
> > better solution.
>
> I'll go
On 10/12/2006, John Morrison wrote:
I've changed the script (which I didn't write!) to use cygpath --sysdir
which outputs cygdrive paths.
Not entirely true if you install Cygwin into $SystemDrive but probably
academic unless you're using this specifically to find out what cygdrive
is, which I
On Thu, 12 Oct 2006, John Morrison wrote:
> On Thu, October 12, 2006 2:41 pm, Igor Peshansky wrote:
> > On Thu, 12 Oct 2006, John Morrison wrote:
> >
> >> On Thu, October 12, 2006 12:54 pm, Corinna Vinschen wrote:
> >> >
> >> > I think it is needed. At least the base-files-mketc.sh postinstall
>
On Thu, 12 Oct 2006, Corinna Vinschen wrote:
> On Oct 12 16:48, Corinna Vinschen wrote:
> > On Oct 12 15:36, John Morrison wrote:
> > > On Thu, October 12, 2006 2:41 pm, Igor Peshansky wrote:
> > > > I wrote the script originally, and the initial version did use POSIX
> > > > paths.
> > >
> > > I
Christopher Faylor wrote:
On Thu, Oct 12, 2006 at 01:54:16PM +0200, Corinna Vinschen wrote:
I think it is needed. At least the base-files-mketc.sh postinstall
script creates paths which point outside the Cygwin root, so it either
needs to reference cygdrive paths, or use DOS paths. Using cygdr
On Oct 12 16:48, Corinna Vinschen wrote:
> On Oct 12 15:36, John Morrison wrote:
> > On Thu, October 12, 2006 2:41 pm, Igor Peshansky wrote:
> > > I wrote the script originally, and the initial version did use POSIX
> > > paths.
> >
> > I thought you did and was suprised to find it not using POSIX
On Oct 12 15:36, John Morrison wrote:
> On Thu, October 12, 2006 2:41 pm, Igor Peshansky wrote:
> > I wrote the script originally, and the initial version did use POSIX
> > paths.
>
> I thought you did and was suprised to find it not using POSIX paths but
> assumed that there was a reason...
>
>
On Thu, Oct 12, 2006 at 09:41:33AM -0400, Igor Peshansky wrote:
>P.S. One annoying thing about /cygdrive is that tab-completion for it is
>annoying OOTB, since there are also /cygwin.bat and /cygwin.ico. One
>thing I normally do on all new installs is rename those two files to
>/Cygwin.bat and /Cy
On Thu, October 12, 2006 2:41 pm, Igor Peshansky wrote:
> On Thu, 12 Oct 2006, John Morrison wrote:
>
>> On Thu, October 12, 2006 12:54 pm, Corinna Vinschen wrote:
>> >
>> > I think it is needed. At least the base-files-mketc.sh postinstall
>> > script creates paths which point outside the Cygwin
Igor Peshansky cs.nyu.edu> writes:
> P.S. One annoying thing about /cygdrive is that tab-completion for it is
> annoying OOTB, since there are also /cygwin.bat and /cygwin.ico. One
> thing I normally do on all new installs is rename those two files to
> /Cygwin.bat and /Cygwin.ico -- since bash
On Thu, 12 Oct 2006, John Morrison wrote:
> On Thu, October 12, 2006 12:54 pm, Corinna Vinschen wrote:
> >
> > I think it is needed. At least the base-files-mketc.sh postinstall
> > script creates paths which point outside the Cygwin root, so it either
> > needs to reference cygdrive paths, or us
On Oct 12 08:43, Christopher Faylor wrote:
> On Thu, Oct 12, 2006 at 02:32:17PM +0200, Corinna Vinschen wrote:
> >Recent Linux distros are using /media to point to several... media.
> >For instance /media/cdrom. So, something like /media/dosdrive/c sounds
> >interesting, too.
>
> Wow! Two new su
On Thu, Oct 12, 2006 at 02:32:17PM +0200, Corinna Vinschen wrote:
>On Oct 12 14:21, Kai Raphahn wrote:
>> Christopher Faylor wrote:
>>
>> > We're already cluttering the root one less than linux since modern linuxes
>> > use /dev, /proc, and /sys.
>>
>> > Hmm. /sys/drive/c has a nice feel to it,
On Oct 12 14:21, Kai Raphahn wrote:
> Christopher Faylor wrote:
>
> > We're already cluttering the root one less than linux since modern linuxes
> > use /dev, /proc, and /sys.
>
> > Hmm. /sys/drive/c has a nice feel to it, although this is YA a case where
> > the existence of a filesystem under
On Oct 12 08:09, Christopher Faylor wrote:
> On Thu, Oct 12, 2006 at 01:54:16PM +0200, Corinna Vinschen wrote:
> >I think it is needed. At least the base-files-mketc.sh postinstall
> >script creates paths which point outside the Cygwin root, so it either
> >needs to reference cygdrive paths, or us
Christopher Faylor wrote:
> We're already cluttering the root one less than linux since modern linuxes
> use /dev, /proc, and /sys.
> Hmm. /sys/drive/c has a nice feel to it, although this is YA a case where
> the existence of a filesystem under this directory is not linux-like.
What about /mn
On Thu, Oct 12, 2006 at 01:54:16PM +0200, Corinna Vinschen wrote:
>I think it is needed. At least the base-files-mketc.sh postinstall
>script creates paths which point outside the Cygwin root, so it either
>needs to reference cygdrive paths, or use DOS paths. Using cygdrives
>paths is preferable,
On Thu, October 12, 2006 12:54 pm, Corinna Vinschen wrote:
>
> I think it is needed. At least the base-files-mketc.sh postinstall
> script creates paths which point outside the Cygwin root, so it either
> needs to reference cygdrive paths, or use DOS paths. Using cygdrives
> paths is preferable,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Frank Fesevur on 10/12/2006 12:44 AM:
>> Maybe the base-files package should create the symlinks to cygdrive
>> paths in
>> the first place? It solves the problem:
>
> Indeed it should do so. OR there should be an automatic translation
On Oct 12 07:18, Christopher Faylor wrote:
> On Thu, Oct 12, 2006 at 08:55:23AM +0200, Corinna Vinschen wrote:
> >On Oct 11 13:10, mwoehlke wrote:
> >> Dave Korn wrote:
> >> >... although I can see problems arising when someone uses mount to rename
> >> >the
> >> >cygdrive mount. Maybe it would b
On Thu, Oct 12, 2006 at 08:55:23AM +0200, Corinna Vinschen wrote:
>On Oct 11 13:10, mwoehlke wrote:
>> Dave Korn wrote:
>> >... although I can see problems arising when someone uses mount to rename
>> >the
>> >cygdrive mount. Maybe it would be worth providing a notation that means
>> >'cygdrive,
On Oct 11 13:10, mwoehlke wrote:
> Dave Korn wrote:
> >... although I can see problems arising when someone uses mount to rename
> >the
> >cygdrive mount. Maybe it would be worth providing a notation that means
> >'cygdrive, no matter how it may have been renamed.
This sounds like a good idea to
At 11-10-2006 19:36, Dave Korn wrote:
On 11 October 2006 18:15, Frank Fesevur wrote:
I've tried his test case and Mark is right. When a symlink is created
with a win32 path, vim can not create the swapfile. When a symlink is
created with POSIX filenames there is no problem.
Well of course n
On Wed, Oct 11, 2006 at 04:39:59PM -0700, Brian Dessent wrote:
>Christopher Faylor wrote:
>>Good point, Brian. If anything qualifies as a FAQ, this certainly
>>does. Joshua, would you be willing to write something up about the
>>philosophy of MS-DOS and Cygwin? Known gotchas would be a good thin
Christopher Faylor wrote:
> Good point, Brian. If anything qualifies as a FAQ, this certainly does.
> Joshua, would you be willing to write something up about the philosophy
> of MS-DOS and Cygwin? Known gotchas would be a good thing to include,
> even if they were only examples.
I'll see about
On Wed, Oct 11, 2006 at 02:23:56PM -0700, Brian Dessent wrote:
>Dave Korn wrote:
>>>I've tried his test case and Mark is right. When a symlink is created
>>>with a win32 path, vim can not create the swapfile. When a symlink is
>>>created with POSIX filenames there is no problem.
>>
>>Well of cour
Dave Korn wrote:
> > I've tried his test case and Mark is right. When a symlink is created
> > with a win32 path, vim can not create the swapfile. When a symlink is
> > created with POSIX filenames there is no problem.
>
> Well of course not. Cygwin - as a special feature - interprets DOS path
Dave Korn wrote:
... although I can see problems arising when someone uses mount to rename the
cygdrive mount. Maybe it would be worth providing a notation that means
'cygdrive, no matter how it may have been renamed.
Hmm, how about /dev/fs/? ;-)
--
Matthew
Will your shell have salvation? Onl
On 11 October 2006 18:15, Frank Fesevur wrote:
> I've tried his test case and Mark is right. When a symlink is created
> with a win32 path, vim can not create the swapfile. When a symlink is
> created with POSIX filenames there is no problem.
Well of course not. Cygwin - as a special feature -
At 11-10-2006 18:06, Corinna Vinschen wrote:
On Oct 11 17:56, Frank Fesevur wrote:
At 10-10-2006 10:34, Corinna Vinschen wrote:
I have updated the version of vim on cygwin.com to 7.0.122-1.
This is an update to the latest patchlevel 122. Cygwin Vim still builds
>from the vanilla sources.
I'
On Oct 11 17:56, Frank Fesevur wrote:
> At 10-10-2006 10:34, Corinna Vinschen wrote:
> >I have updated the version of vim on cygwin.com to 7.0.122-1.
> >
> >This is an update to the latest patchlevel 122. Cygwin Vim still builds
> >from the vanilla sources.
>
> I'm still having problems editing /
At 10-10-2006 10:34, Corinna Vinschen wrote:
I have updated the version of vim on cygwin.com to 7.0.122-1.
This is an update to the latest patchlevel 122. Cygwin Vim still builds
from the vanilla sources.
I'm still having problems editing /etc/hosts. Also see my earlier report
in http://cygw
I have updated the version of vim on cygwin.com to 7.0.122-1.
This is an update to the latest patchlevel 122. Cygwin Vim still builds
from the vanilla sources.
To update your installation, click on the "Install Cygwin now" link on
the http://cygwin.com/ web page. This downloads setup.exe to yo
38 matches
Mail list logo
