Hi,
I got the following problem : rlogin : No Buffer space available
rlogin: connection closed.
I saw that this problem was reported in the following references :
References: <[EMAIL PROTECTED]> <
[EMAIL PROTECTED]> <
[EMAIL PROTECTED]> <
[EMAIL PROTECTED
On Feb 20 11:09, [EMAIL PROTECTED] wrote:
>
> Hi,
>
> I got the following problem : rlogin : No Buffer space available
> rlogin: connection closed.
> I saw that this problem was reported in the following references :
> References: <[EMAIL PROTECTED]> <
> [EMAIL PROTE
Hi,
I'm trying to access files for reading via the / directive, i.e. vi
/usr/foo.txt
However, this will not open foo.txt, vi creates a new file in the current
directory instead.
I can cd to the /usr directory and open the file with vi usr.txt. I'm using
vi as an example, I'm actually trying to co
On Tue, Feb 20, 2007 at 05:44:51AM -0800, Jeff2007 wrote:
>Hi,
>
>I'm trying to access files for reading via the / directive, i.e. vi
>/usr/foo.txt
>However, this will not open foo.txt, vi creates a new file in the current
>directory instead.
>I can cd to the /usr directory and open the file with v
Jeff2007 wrote:
> I'm trying to access files for reading via the / directive, i.e. vi
> /usr/foo.txt
> However, this will not open foo.txt, vi creates a new file in the current
> directory instead.
> I can cd to the /usr directory and open the file with vi usr.txt. I'm using
> vi as an example, I'
>You have a whole mess of non-Cygwin programs in your path.
Ah... it looks like I have a lot of housekeeping to take care of that I
didn't know about. I need to do some reading up on the PATH variable, I
thought it was only the stuff in /usr/etc/profile that set the PATH.
Thanks!
Jeff.
--
Just to conclude my query, in the file usr/etc/profile I've added the line:
PATH=
Above my other PATH variables. When I run cygcheck again, all of the
pre-existing Windows Path environment variables have gone, which seems to be
what I needed to happen.
Thanks to all,
Jeff.
--
View this messag
Michael wrote:
> Hello,
>
> I'm trying to install cygwin+sshd on a WinXPPro-machine, but get an
> error, when starting the service.
> It would be great, if someone is able to help me find a hint for a
> solution for this problem!
>
> Here a summary what I did:
> - logged in with domain-user with
Jan Djärv wrote:
Christopher Faylor wrote:
Thanks much for the details. We do want to make things work correctly
but, if that just means some work in emacs source code, then someone who
is familiar with emacs will have to do that, i.e., someone else will
have to come up with the config.h.
OT
* Jeff2007 (Tue, 20 Feb 2007 07:22:54 -0800 (PST))
> Just to conclude my query, in the file usr/etc/profile I've added the line:
> PATH=
>
> Above my other PATH variables. When I run cygcheck again, all of the
> pre-existing Windows Path environment variables have gone, which seems to be
> what I
On 2/20/07, Jeff2007 wrote:
Hi,
I'm trying to access files for reading via the / directive, i.e. vi
/usr/foo.txt
However, this will not open foo.txt, vi creates a new file in the current
directory instead.
I can cd to the /usr directory and open the file with vi usr.txt. I'm using
vi as an exa
On 2/20/07, Jeff2007 wrote:
Hi,
I'm trying to access files for reading via the / directive, i.e. vi
/usr/foo.txt
However, this will not open foo.txt, vi creates a new file in the current
directory instead.
I can cd to the /usr directory and open the file with vi usr.txt. I'm using
vi as an exa
Hi,
I am trying to port a program from Windows XP to Vista and am running into
several issues.
1) When I issue an fopen of a file with "rb" or "wb" modes they fails. I have
since switched to just a "r" and "w" and it now works. This was not an issue on
XP.
2) When I issue a CreateFile() func
Folks I could really use some help here. I still cannot get the ls
command to work reliably. It worked for years and about two weeks ago
started sputtering. I have completely unstalled all cygwin packages,
deleted the directories, and reinstalled from scratch. Even just
installing the bare mimimum
Jan D. wrote:
Jan Djärv wrote:
Christopher Faylor wrote:
Thanks much for the details. We do want to make things work correctly
but, if that just means some work in emacs source code, then someone who
is familiar with emacs will have to do that, i.e., someone else will
have to come up with th
Folks I could really use some help here. I still cannot get the ls
command to work reliably.
Well, I ran sum -r (I'm running cygwin 1.5.24):
~$ sum -r /bin/ls.exe /bin/cygwin1.dll
0875696 /bin/ls.exe
59473 1830 /bin/cygwin1.dll
You might do the same and see if there is perhaps a
Ken Shaffer wrote:
>> Folks I could really use some help here. I still cannot get the ls
>> command to work reliably.
>
> Well, I ran sum -r (I'm running cygwin 1.5.24):
>
>~$ sum -r /bin/ls.exe /bin/cygwin1.dll
>0875696 /bin/ls.exe
>59473 1830 /bin/cygwin1.dll
>
> You might do
Can you please check these md5sum's for me?
$ md5sum /bin/ls.exe /usr/bin/ls.exe /usr/bin/dir.exe
64e3dc0e3a5ef0eeeaa4f2e9b984844d */bin/ls.exe
64e3dc0e3a5ef0eeeaa4f2e9b984844d */usr/bin/ls.exe
60a0c7768052ec4306c3e0f680331afa */usr/bin/dir.exe
Same.
~$ md5sum /bin/ls.exe /usr/bin/ls.exe /u
Chuck wrote:
Folks I could really use some help here. I still cannot get the ls
command to work reliably. It worked for years and about two weeks ago
started sputtering. I have completely unstalled all cygwin packages,
deleted the directories, and reinstalled from scratch. Even just
installing t
While poking around with managed mounts following yesterday's mail, it
occured to me that the managed-mount filename munging misses some cases,
namely, filenames with trailing spaces, and filenames that look like Windows
short-form names corresponding to existing file names.
Here's an example:
$
Folks,
Never mind. I went through and changed the permissions on the f: drive and now
it is working again. Even though my userId in cygwin is administrator Windows
does not seem to recognise me as such. CreateFile() is now able to create a
valid handle once more. I also dont seem to have any si
Larry Hall (Cygwin) wrote:
> Chuck wrote:
>> Folks I could really use some help here. I still cannot get the ls
>> command to work reliably. It worked for years and about two weeks ago
>> started sputtering. I have completely unstalled all cygwin packages,
>> deleted the directories, and reinstall
Chuck wrote:
Larry Hall (Cygwin) wrote:
Chuck wrote:
Folks I could really use some help here. I still cannot get the ls
command to work reliably. It worked for years and about two weeks ago
started sputtering. I have completely unstalled all cygwin packages,
deleted the directories, and reinst
On 2007-02-20, Chuck wrote:
> Folks I could really use some help here. I still cannot get the ls
> command to work reliably. It worked for years and about two weeks ago
> started sputtering. I have completely unstalled all cygwin packages,
> deleted the directories, and reinstalled from scratch. E
Gary Johnson wrote:
On 2007-02-20, Chuck wrote:
Folks I could really use some help here. I still cannot get the ls
command to work reliably. It worked for years and about two weeks ago
started sputtering. I have completely unstalled all cygwin packages,
deleted the directories, and reinstalled
Gary Johnson wrote:
> On 2007-02-20, Chuck wrote:
>> Folks I could really use some help here. I still cannot get the ls
>> command to work reliably. It worked for years and about two weeks ago
>> started sputtering. I have completely unstalled all cygwin packages,
>> deleted the directories, and r
Larry Hall (Cygwin) wrote:
> Chuck wrote:
>> Larry Hall (Cygwin) wrote:
>>> Chuck wrote:
Folks I could really use some help here. I still cannot get the ls
command to work reliably. It worked for years and about two weeks ago
started sputtering. I have completely unstalled all cygwi
On 2/20/07, Chuck wrote:
Your wish is my command. Attached are two strace output files. The names
should be self-explanatory. Please let me know if you see anything. In
the mean time I'm going to refresh myself on the use of gcc and gdb and
see if I can trace the execution of ls. Like I said in
On 02/20/2007, Chuck wrote:
Larry Hall (Cygwin) wrote:
> Can you send the output of a successful 'ls -l' from within a directory
> with one file and then the strace of a failing case of 'ls' within this
> directory and a non-failing case of the same to the list?
>
> Does it work fine without 'tt
Frodak Baksik wrote:
> On 2/20/07, Chuck wrote:
>
>> Your wish is my command. Attached are two strace output files. The names
>> should be self-explanatory. Please let me know if you see anything. In
>> the mean time I'm going to refresh myself on the use of gcc and gdb and
>> see if I can trace
Frodak Baksik wrote:
On 2/20/07, Chuck wrote:
Your wish is my command. Attached are two strace output files. The names
should be self-explanatory. Please let me know if you see anything. In
the mean time I'm going to refresh myself on the use of gcc and gdb and
see if I can trace the execution
Larry Hall (Cygwin) wrote:
> Frodak Baksik wrote:
>> On 2/20/07, Chuck wrote:
>>
>>> Your wish is my command. Attached are two strace output files. The names
>>> should be self-explanatory. Please let me know if you see anything. In
>>> the mean time I'm going to refresh myself on the use of gcc a
Dear cygwin readers,
I have just ported an application from Linux to Cygwin.
In one archive (.a) I have several global constructors,
2-3 in two .o files. When I run my program only one
initializer function is called in that archive. Leaving
the other uninitialized/uncalled.
I have found this is
Chuck wrote:
I think it's actually something to do with the gmane interface that I
post to. I attach the files with Thunderbird but when they post to the
list, they end up being embedded. Apologies but there doesn't seem to be
any way for me to control that.
No, it's working right... your files
Chuck wrote:
Folks I could really use some help here. I still cannot get the ls
command to work reliably. It worked for years and about two weeks ago
started sputtering. I have completely unstalled all cygwin packages,
deleted the directories, and reinstalled from scratch. Even just
installing t
Larry Hall (Cygwin) wrote:
> On 02/20/2007, Chuck wrote:
>> Larry Hall (Cygwin) wrote:
>> > Can you send the output of a successful 'ls -l' from within a directory
>> > with one file and then the strace of a failing case of 'ls' within this
>> > directory and a non-failing case of the same to the l
> 2) When I issue a CreateFile() function call against f: which is a USB drive
> an
> invalid handle error is returned.
In general, it is a bad idea to mix Windows APIs with cygwin, since
you are going behind cygwin's back, and can no longer guarantee
cygwin's POSIX-y behavior. Using CreateFile
> Can you please check these md5sum's for me?
>
> $ md5sum /bin/ls.exe /usr/bin/ls.exe /usr/bin/dir.exe
> 64e3dc0e3a5ef0eeeaa4f2e9b984844d */bin/ls.exe
> 64e3dc0e3a5ef0eeeaa4f2e9b984844d */usr/bin/ls.exe
> 60a0c7768052ec4306c3e0f680331afa */usr/bin/dir.exe
/bin and /usr/bin are typically the same
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
Patric Ljung itn.liu.se> writes:
>
> Dear cygwin readers,
>
> I have just ported an application from Linux to Cygwin.
> In one archive (.a) I have several global constructors,
> 2-3 in two .o files. When I run my program only one
> initializer function is called in that archive. Leaving
> the
Cesar Strauss wrote:
> Chuck wrote:
>> Folks I could really use some help here. I still cannot get the ls
>> command to work reliably. It worked for years and about two weeks ago
>> started sputtering. I have completely unstalled all cygwin packages,
>> deleted the directories, and reinstalled fro
On 02/20/2007, Chuck wrote:
I downloaded the source for coreutils and see that in ls.c the same source
code is used to compile ls, dir, and vdir. The strange thing is that dir
and vdir never fail. Only ls does. I haven't figured out how to compile
with the debugging info yet.
make CFLAGS="-g"
Chuck wrote:
Cesar Strauss wrote:
Chuck wrote:
Folks I could really use some help here. I still cannot get the ls
command to work reliably. It worked for years and about two weeks ago
started sputtering. I have completely unstalled all cygwin packages,
deleted the directories, and reinstalled
Lewis Hyatt wrote:
Patric Ljung itn.liu.se> writes:
I have just ported an application from Linux to Cygwin.
In one archive (.a) I have several global constructors,
2-3 in two .o files. When I run my program only one
initializer function is called in that archive. Leaving
the other uninitialize
Hey,
I recently installed rxvt-unicode. That much was easy. Could
someone please tell me how to launch a shell?
And just out of curiosity, what's the "best" shell option in
cygwin if I want my Linux shell on Windows?
Thanks,
- GM
--
Unsubscribe info: http://cygwin.com/ml/#unsubscrib
Grok Mogger wrote:
> I recently installed rxvt-unicode. That much was easy. Could
> someone please tell me how to launch a shell?
First of all, realize that the rxvt-unicode package is X11 only. So you
need to run the X server first before launching urxvt. And also,
despite its name, it does
46 matches
Mail list logo