RE: animated gif
From: garbicha > I'm a kind of new to cygwin and gnu .I want to make an animated > gif/png movie using gnuplot. Can someone help me with that? This is question is about gnuplot, not cygwin, so is off-topic here. You would do better to ask a gnuplot list. -- 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/
Deprecating ntea
Hi, I think it's time to remove the CYGWIN=ntea setting from Cygwin. (see http://cygwin.com/cygwin-ug-net/using-cygwinenv.html) The reason is that it's just a fake. It fakes POSIX permission bits by using the "extended attributes" capability built into NTFS. it also works on FAT by creating a bulky file in the root directory of the partition. Extended attributes were never implemented on FAT32, so "ntea" could never work on FAT32. So, IMO, ntea is not at all necessary. Given that practically all Windows systems nowadays are using NTFS and given that NTFS supports real permissions, not only faked ones, I don't see any need for ntea. I even consider ntea as dangerous, because it pretends a security which doesn't exist. That's what the default ntsec setting is for, utilizing real permission settings. Ok, that's my opinion, which should make it clear that I think ntea is old cruft which should be removed from Cygwin. My questions are thus: Does anybody seriously use ntea? Do you think you can't live without it? Is using ntsec or just switching off ntsec no option for you? Why? Or, to phrase it as I did on the cygwin-developers list: Does anybody have a good argument to keep this cruft against all reason? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/
Missing dependencies for qt3-devel
Hi, pkg-config file "qt-mt.pc" lists several libraries that are not installed when "qt3-devel-3.3.4-2" is selected. The missing libraries can be found in: XFree86-lib-compat xorg-x11-devel minires-devel It is quite difficult to figure out which packages are required, so I would suggest adding them to the dependencies of qt3-devel. Cheers, Rafal -- 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/
[ANNOUNCEMENT] Updated: astyle-1.20.2-1
I've uploaded a new version astyle, 1.20.2-1, in keeping with the current upstream release. For a list of changes check out http://astyle.sourceforge.net/astyle_release_notes.html. To update your installation, click on the "Install Cygwin now" link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Then, run setup and answer all of the questions. If you have questions or comments, please send them to the Cygwin mailing list at: cygwin@cygwin.com . *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. Chris -- Chris Sutcliffe http://ir0nh34d.googlepages.com http://ir0nh34d.blogspot.com http://emergedesktop.org -- 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/
Regarding Problems with the mount command inside a script
Hello, I'm running a command inside Cygwin mount -b /cygdrive/c/cygwin/rakesh /cygdrive/c/cygwin/rakesh/usr/cygnus But I get the following error mount: /cygdrive/c/cygwin/rakesh/usr/cygnus: Invalid argument Is the mount command wrongly given?? Regards, Rakesh _ Latest updates from the world of sports http://content.msn.co.in/Sports/Default -- 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/
Re: Regarding Problems with the mount command inside a script
Rakesh Kumar wrote: > I'm running a command inside Cygwin > > mount -b /cygdrive/c/cygwin/rakesh /cygdrive/c/cygwin/rakesh/usr/cygnus > > But I get the following error > > mount: /cygdrive/c/cygwin/rakesh/usr/cygnus: Invalid argument > > Is the mount command wrongly given?? Yes. Take a look at "mount --help". The first argument is a win32 path -- that is the whole point of mount table entries, to map a win32 path to a POSIX path. And you should not be using /cygdrive like that. Assuming that c:/cygwin is mounted as /, then you probably want something like mount c:/cygwin/rakesh /usr/cygnus Brian -- 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/
Re: Ambiguous error from ./configure
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Forrest Aldrich on 2/27/2007 9:31 AM: > I've been working on building a patched version of SSH. Using the > standard configure, it's generating this error: > > configure:4187: error: C preprocessor "gcc -E" fails sanity check In this case, you are better off looking in config.log, not configure, for figuring out why $ac_preproc_ok was not set to a good value. Did you correctly install gcc? > Problem reports: http://cygwin.com/problems.html And following directions by including 'cygcheck -svr' output as a text attachment might be helpful. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF5X7V84KuGfSFAYARAn7HAKDVVZof5J6bkVlgZrIWWDis8yb3lwCfTVqH kdBGzUmoRtjVO3vBWvnWYqc= =Mdd5 -END PGP SIGNATURE- -- 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/
Re: Strange message from updatedb
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Phil Edwards on 2/27/2007 11:50 AM: > On 2/27/07, Furash Gary <[EMAIL PROTECTED]> wrote: >> /cygdrive/c/System\ Volume\ Information > > Quotes and backslashes aren't going to solve the problem, I think. I > looked at updatedb (it's a shell script), and the --prunepaths > argument is passed through a sed script which replaces spaces in order > to turn it all into a regexp. There's no way of telling sed to avoid > some spaces and translate others. I've reported this upstream. I also agree with Enrico's suggestion of using . instead of a quoted space, since that is the regex character that will match a space: updatedb --prunepaths='/cygdrive/c/WINDOWS /cygdrive/e /cygdrive/d /cygdrive/z cygdrive/y /proc /cygdrive/c/System.Volume.Information /usr /var /cygdrive/c/Documents.and.Settings/furashg/Local.Settings/Temporary.Internet.Files /usr/bin /cygdrive/c/System.Volume.Information /c/cygwin' > > You used to be able to set the internal PRUNEREGEX variable directly, > in a .conf file, but apparently that file is only used under Linux > versions of updatedb, or something. Perhaps that was in distro-modified versions. I just included updatedb as it is upstream, plus a single patch to recognize that on cygwin, the filesystem recognition code doesn't work very well. > > Most lists of dirs are passed around with colon (or some such) > separators to avoid just such problems with paths containing > whitespace. updatedb is still living in the 80's. > I agree that directory name lists should look like a PATH, and not be space separated, but we will see what the upstream maintainer thinks. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF5YFe84KuGfSFAYARAiSNAJ4noRa0o7zVr2xZmqQFmUd908zirwCfaqxo +grDYlWCZCLjEjB+IkXHQ+Q= =QZKC -END PGP SIGNATURE- -- 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/
Re: Sony Dual [CD/DVD] RW Drive Problems
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to LDR on 2/20/2007 3:30 PM:
> I have one of those IEEE 1394 (Firewire) CD/DVD-RW+RW drives.
>
> When I recursively copy one directory ('x.ab') from my HDD to a DVD-RW
> in Explorer, everything looks good until I do an 'ls -l' on the drive.
> Then I see in the 'ls -l' output listing many copies of the directory as
> some kind of a binary (?) file. E.g.,
>
> br---T 9281 Everyone root 22, 34090 Jan 14 1979 x.ab
> br---T 9281 Everyone root 22, 34090 Jan 14 1979 x.ab
> br---T 9281 Everyone root 22, 34090 Jan 14 1979 x.ab
Sorry for the delayed reply; I was on vacation when this arrived. I have
no idea what's going wrong here, but wonder if it is an issue with the
underlying readdir call. At this point, an strace of the failure might
prove more informative as to what Windows is telling cygwin about the
contents of that directory. But the strace is likely to be huge. Maybe
Corinna has some more advice about what to look for?
- --
Don't work too hard, make some time for fun as well!
Eric Blake [EMAIL PROTECTED]
volunteer cygwin coreutils maintainer
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFF5YmH84KuGfSFAYARAu9eAJ9f43Jg8z57X3n4exvGc+3f979WxgCcD9LP
c/Ni9b9fCu6FJywOoLPj6Vc=
=dlSh
-END PGP SIGNATURE-
--
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/
Re: /dev/null timing and clock skew problems
It seems the 'Clock Skew' warnings are the only serious ones. They never used to occur on previous Cygwin releases though. I am building LLVM with Cygwin and am getting the warnings but on building GCC I am getting no clock skew or modification time warnings. http://llvm.org CVS and build instructions :- http://www.aarongray.org/LLVM/BuildingLLVMonCygwin.html The clock skew warnings appear after a link or archive. I cannot seem to find a flag for make to display executed commands though. On my 1.4Ghz XP machine Clock Skews could be serious, but on my 1.6Ghz Vista machine they appear not to be. Could someone give me any idea when this will be fixed. Many thanks, Aaron -- 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/
RE: Strange message from updatedb
Okay, for a vanilla cygwin user, is there anything *I* should be doing, or just ignore it and wait for a patch. Thanks for helping. I use find all the time .. :-) -Original Message- From: Eric Blake [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 28, 2007 6:19 AM Cc: Furash Gary; cygwin@cygwin.com Subject: Re: Strange message from updatedb -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Phil Edwards on 2/27/2007 11:50 AM: > On 2/27/07, Furash Gary <[EMAIL PROTECTED]> wrote: >> /cygdrive/c/System\ Volume\ Information > > Quotes and backslashes aren't going to solve the problem, I think. I > looked at updatedb (it's a shell script), and the --prunepaths > argument is passed through a sed script which replaces spaces in order > to turn it all into a regexp. There's no way of telling sed to avoid > some spaces and translate others. I've reported this upstream. I also agree with Enrico's suggestion of using . instead of a quoted space, since that is the regex character that will match a space: updatedb --prunepaths='/cygdrive/c/WINDOWS /cygdrive/e /cygdrive/d /cygdrive/z cygdrive/y /proc /cygdrive/c/System.Volume.Information /usr /var /cygdrive/c/Documents.and.Settings/furashg/Local.Settings/Temporary.Inte rnet.Files /usr/bin /cygdrive/c/System.Volume.Information /c/cygwin' > > You used to be able to set the internal PRUNEREGEX variable directly, > in a .conf file, but apparently that file is only used under Linux > versions of updatedb, or something. Perhaps that was in distro-modified versions. I just included updatedb as it is upstream, plus a single patch to recognize that on cygwin, the filesystem recognition code doesn't work very well. > > Most lists of dirs are passed around with colon (or some such) > separators to avoid just such problems with paths containing > whitespace. updatedb is still living in the 80's. > I agree that directory name lists should look like a PATH, and not be space separated, but we will see what the upstream maintainer thinks. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF5YFe84KuGfSFAYARAiSNAJ4noRa0o7zVr2xZmqQFmUd908zirwCfaqxo +grDYlWCZCLjEjB+IkXHQ+Q= =QZKC -END PGP SIGNATURE- -- 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/
Re: Strange message from updatedb
Try replacing spaces ' ' with dots '.' in the paths specified with --prunepaths. In a regexp a dot matches any character. I had tried that, but --prunepaths='/cygdrive/c/System.Volume.Information' still caused the corresponding directory to be searched. I didn't have time to look further then, maybe somebody else will beat me to it. -- 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/
Re: 1.7.0 CVS & perl mutex panic
On Tue, Feb 27, 2007 at 05:59:36PM -0600, Brian Ford wrote: > FYI > > $ uname -a > CYGWIN_NT-5.1 PC1163-8460-XP 1.7.0(0.166/4/2) 2007-02-26 09:41 i686 > unknown unknown Cygwin > > $ perl --version > > This is perl, v5.8.7 built for cygwin-thread-multi-64int > (with 1 registered patch, see perl -V for more detail) > [snip] > > $ perl -e 'open(x, "ls|")' > panic: MUTEX_UNLOCK (1) [util.c:2279] at -e line 1. BTW: I also saw this with a make job when I checked out of CVS a couple of days ago. there was a change to mutex handling in the changelogs further back but unfortunately I hadn't done anything to track it down yet. Just chiming in to let it be known that others see this same error as well. -cl -- 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/
Re: GDB Ctrl-C Interrupt Fails WORKAROUND
On Thu, Jun 15, 2006 at 11:04:56AM -0400, Christopher Faylor wrote: > >I'm happy for you that CTRL-C works for you. It does not work for me. > > > >I'm almost never running gdb from a genuine DOS command prompt. > >Sometimes via ssh, sometimes via a terminal emulator. CTRL-C doesn't > >work in those. > > > >Also, if you have "tty" in your CYGWIN variable it doesn't work even > >from a DOS command prompt. > > Which is exactly what I theorized above. So, characterizing CTRL-C as > not working in gdb is rather an overstatement without more details. > > Now you know that you can use a standard console window for debugging > and all will be well. > > >Lacking the ability to interrupt a running program severely limits > >gdb's usefulness. Fortunately there's a workaround available. > > Yep. Use a console window. > > cgf Where in the cygwin source tree would the best place be to look for where SIGINT handling is being done at the tty/pty level so that I can remove this pointless limitation from my builds? -cl -- 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/
Re: GDB Ctrl-C Interrupt Fails WORKAROUND
Christopher Layne escreveu: On Thu, Jun 15, 2006 at 11:04:56AM -0400, Christopher Faylor wrote: I'm happy for you that CTRL-C works for you. It does not work for me. I'm almost never running gdb from a genuine DOS command prompt. Sometimes via ssh, sometimes via a terminal emulator. CTRL-C doesn't work in those. Also, if you have "tty" in your CYGWIN variable it doesn't work even >from a DOS command prompt. Which is exactly what I theorized above. So, characterizing CTRL-C as not working in gdb is rather an overstatement without more details. Now you know that you can use a standard console window for debugging and all will be well. Lacking the ability to interrupt a running program severely limits gdb's usefulness. Fortunately there's a workaround available. Yep. Use a console window. Is there a reason DebugBreakProcess can't be used from inside gdb if sending a ctrl-c with GenerateConsoleCtrlEvent (CTRL_C_EVENT, pid) doesn't work? Where in the cygwin source tree would the best place be to look for where SIGINT handling is being done at the tty/pty level so that I can remove this pointless limitation from my builds? See gdb/win32-nat.c:win32_stop and also: http://sourceware.org/ml/gdb-patches/2007-02/msg00294.html Look for win32_send_signal in the patch. Note that DebugBreakProcess only exists on XP or Windows 2003 server onwards. For WinNT < XP, it should be possible to simulate it with CreateRemoteThread with entry point set to DebugBreak or something similar. The worst case would be that a dll would have to be injected to load a function that does the DebugBreak in the debuggee's address space. Cheers, Pedro Alves -- 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/
Re: GDB Ctrl-C Interrupt Fails WORKAROUND
On Thu, Mar 01, 2007 at 12:15:12AM +, Pedro Alves wrote: >Is there a reason DebugBreakProcess can't be used from inside >gdb if sending a ctrl-c with GenerateConsoleCtrlEvent (CTRL_C_EVENT, pid) >doesn't work? I suppose that it could be used for that but it might be tricky figuring out when it was required and when it wasn't. You wouldn't want to interrupt the process twice if it already saw the CTRL-C. Although, maybe if you used this you could tell the inferior process not to process CTRL-C at all via some CreateProcess setting. cgf -- 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/
Re: GDB Ctrl-C Interrupt Fails WORKAROUND
Christopher Faylor escreveu: On Thu, Mar 01, 2007 at 12:15:12AM +, Pedro Alves wrote: Is there a reason DebugBreakProcess can't be used from inside gdb if sending a ctrl-c with GenerateConsoleCtrlEvent (CTRL_C_EVENT, pid) doesn't work? I suppose that it could be used for that but it might be tricky figuring out when it was required and when it wasn't. You wouldn't want to interrupt the process twice if it already saw the CTRL-C. Although, maybe if you used this you could tell the inferior process not to process CTRL-C at all via some CreateProcess setting. What about doing it the other way around? Use DebugBreakProcess if available, and fallback to GenerateConsoleCtrlEvent? Is there anything internal to Cygwin that uses it? We could teach gdb that the next BreakPoint inside kernel32 (, or whatever dll DebugBreakProcess breaks in,) is mapped to SIGINT, remap the event, and switch to the main thread, so the user doesn't see we stopped inside kernel32. Cheers, Pedro Alves -- 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/
Re: GDB Ctrl-C Interrupt Fails WORKAROUND
On Thu, Mar 01, 2007 at 01:12:21AM +, Pedro Alves wrote: >Christopher Faylor escreveu: >>On Thu, Mar 01, 2007 at 12:15:12AM +, Pedro Alves wrote: >>>Is there a reason DebugBreakProcess can't be used from inside gdb if >>>sending a ctrl-c with GenerateConsoleCtrlEvent (CTRL_C_EVENT, pid) >>>doesn't work? >> >>I suppose that it could be used for that but it might be tricky >>figuring out when it was required and when it wasn't. You wouldn't >>want to interrupt the process twice if it already saw the CTRL-C. >>Although, maybe if you used this you could tell the inferior process >>not to process CTRL-C at all via some CreateProcess setting. > >What about doing it the other way around? Use DebugBreakProcess if >available, and fallback to GenerateConsoleCtrlEvent? ? Maybe we're not talking about the same thing but I don't see why it matters what the order of function calls is. If the inferior process has already responded to a CTRL-C you don't want it to get another interrupt. >Is there anything internal to Cygwin that uses it? We could teach gdb >that the next BreakPoint inside kernel32 (, or whatever dll >DebugBreakProcess breaks in,) is mapped to SIGINT, remap the event, and >switch to the main thread, so the user doesn't see we stopped inside >kernel32. I think if gdb sends a break because it saw a CTRL-C and then gets a break from the sub-process it is safe for gdb to assume that the interrupt was a CTRL-C without needing to check where the break hit. I don't know about going to the effort of switching to thread 1, though. cgf -- 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/
Re: 100% CPU Usage and Error Message: Error, messageQ semaphore not equal to zero.
Hi, Thanks for your instant reply. I have a few queries regarding cygserver and cygipc. We have just started looking into our programs to see what the impact will be to move from cygipc to cygserver. 1. Can you please give us an idea of the things that need to be done to move from cygipc to cygserver. Our programs are coded in C. 2. We were trying to just get the cygserver up and running. We have successfully installed cyserver. But, when starting Cygserver, the following error occurs: "System Error 3 has Occured --- The System cannot find the path specified". I have checked services.msc for the cygserver service, it is installed correctly and the path to the exectuable is pointing to cygrunsrv.exe in the correct folder. What could be the problem? Thanks and Regards, Neo. - Original Message From: Corinna Vinschen <[EMAIL PROTECTED]> To: cygwin@cygwin.com Sent: Friday, 23 February, 2007 6:13:04 PM Subject: Re: 100% CPU Usage and Error Message: Error, messageQ semaphore not equal to zero. On Feb 23 17:55, neo napster wrote: > Hi, > > I am using the below system configuration: > > 1. Windows 2003 > 2. CYGWin 1.3 and CYGIPC 1.09 > 3. MyApplication created in COBOL i.e., cobol dll's The last 1.3 release (1.3.22) is from March 2003. The first time Windows 2003 Server got supported was in Cygwin 1.5.0, back in May 2003. Cygipc has been made redundant beginning November 2003. It's February 2007. The conclusion is this: The software you're using is hopelessly outdated and not supported anymore for a long time. Update to the current release 1.5.24 and switch to using Cygserver instead of Cygipc. If you still have problems, feel free to ask this mailing list for help. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/ ___ The all-new Yahoo! Mail goes wherever you go - free your email address from your Internet provider. http://uk.docs.yahoo.com/nowyoucan.html -- 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/
Regarding mount command inside CYGWIN
Hello, I'm running a command inside Cygwin mount -b /cygdrive/c/cygwin/rakesh /cygdrive/c/cygwin/rakesh/usr/cygnus But I get the following error mount: /cygdrive/c/cygwin/rakesh/usr/cygnus: Invalid argument Is the mount command wrongly given?? Regards, Rakesh _ Latest updates from the world of sports http://content.msn.co.in/Sports/Default -- 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/
Re: Regarding mount command inside CYGWIN
On Thu, Mar 01, 2007 at 11:13:00AM +0530, Rakesh Kumar wrote: > Hello, > > I'm running a command inside Cygwin > >mount -b /cygdrive/c/cygwin/rakesh >/cygdrive/c/cygwin/rakesh/usr/cygnus > > But I get the following error? > > mount: /cygdrive/c/cygwin/rakesh/usr/cygnus: Invalid argument > > Is the mount command wrongly given?? > > Regards, > Rakesh > Yes. You need a win32 path for the mount source. man mount. -cl -- 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/
