Re: Definitely no sshd on FAT32?

[Corinna Vinschen]

On Mar  3 22:57, Jason Pyeron wrote:
> Is there a way around the permission check on the private key files for the
> ssh client?
> 
> The key files are on a mapped drive for the domain controller. The domain
> controller was switched to samba who reports:
> [...]
> But in reality the files are 600 on the ext3 partition.

If you are a domain user then there's a good chance that your Samba
server is part of the domain and manages file permissions for domain
users as needed.  In this case try setting the environment variable
CYGWIN to contain "smbntsec":

  bash$ CYGWIN=smbntsec ssh remote-host

If that works, use this setting in your profile. Otherwise there's a
temporary solution.  Use

  bash$ CYGWIN=nontsec ssh remote-host

on every invocation of ssh.


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/

Re: ZSH - UTF-8

[Corinna Vinschen]

On Mar  4 03:59, Paul-Kenji Cahier wrote:

http://cygwin/com/acronyms/#TOFU

> LC_ALL set to C.UTF-8 in all cases. Cygwin freshly installed.
> Also tried LC_ALL=en_US.UTF-8(which shouldnt exist) and it did
> not work either.

Newlib uses "C-UTF-8", not "C.UTF-8" for some reason.  I don't see that
newlib understands the dot.  Moreover, Cygwin doesn't support utf-8 yet,
so you might have strange effects using utf-8 for filenames.


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/

[ANNOUNCEMENT] New package: qsf 1.2.7-1 -- Lightweight statistical spam filter

[Jari Aalto]

PACKAGE DESCRIPTION
===

Homepage: http://freshmeat.net/projects/qsf
License : GPL

Quick Spam Filter (qsf) is a lightweight statistical spam filter. It
is designed to be small, fast, reliable, easy to install, and simple
to use in a procmail recipe. For these reasons it is not written in
Perl (slow to start up) and does not run as a daemon handling requests
(more complex, harder to install and use).

CHANGES SINCE LAST RELEASE
==

See:
  /usr/share/doc/qsf-*/{changelog,NEWS}
  http://qsf.cvs.sourceforge.net/qsf/qsf/doc/NEWS?revision=HEAD&view=markup

INSTALL OR UPGRADE NOTES


Standard install.

CYGWIN INSTALLATION INFORMATION
===

To install this package, click on the "Install Cygwin now" link on the
 web page. This downloads setup.exe to your
system. Then, run setup and answer all of the questions. You'll find
the package listed in the "All" category. After installation, read the
documentation at directories:

/usr/share/doc//*
/usr/share/doc/Cygwin/.README

If you have questions or comments, please send them to the Cygwin
mailing list at .

CYGWIN-ANNOUNCE UNSUBSCRIBE INFO


This message has been sent to cygwin-announce list.

If you want to unsubscribe from the 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]

More information on unsubscribing can be found:

http://sources.redhat.com/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is available
starting at the above URL.

-- 
Welcome to FOSS revolution: we fix and modify until it shines

--
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[2]: ZSH - UTF-8

[Paul-Kenji Cahier]

>>?LC_ALL set to C.UTF-8 in all cases. Cygwin freshly installed.
>>?Also tried LC_ALL=en_US.UTF-8(which shouldnt exist) and it did
>>?not work either.

>?Newlib uses "C-UTF-8", not "C.UTF-8" for some reason.  I don't see that
>?newlib understands the dot.  Moreover, Cygwin doesn't support utf-8 yet,
>?so you might have strange effects using utf-8 for filenames.

>?Corinna

(this time text under quote, didnt know it bothered)

I'm still failing to get zsh working with utf-8, even
with C-UTF-8 as LC_ALL: as specified in my previous message
non-ascii bytes get displayed as <00cxx> which the line editor
does manage properly. But there is still no way to actually see
utf-8 characters displayed, or even their unicode values(ie
it's still a single byte editing mode). If someone manages
to get it working, please post:)

Also I know about the lack of utf-8 support in cygwin for most
of the windows calls(and personally think that the cygwin utf-8
wrapper code patch would be a vast improvement, that is the one
from okisoft that got posted to cygwin's ml long ago, though
I understand some people dont like how it's done). This should
still not be a problem for one to do an "echo éé"
in his term transparently.
(no problematic wide windows calls involved there as far as I know).

Paul-Kenji Cahier


--
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: [ANNOUNCEMENT] Updated: [experimental] cygwin-1.5.25-10

[Corinna Vinschen]

On Mar  3 21:33, Robin Walker wrote:
> --On 03 March 2008 11:46 + Robin Walker wrote:
>
>> I noticed the same with 1.5.25-9 last night.  It's not just calls to
>> localhost: it's ssh calls to anywhere that hang: in other words, it's a
>> client-side problem, not server-side.  I noticed that the -vv option of
>> ssh threw an error report just before the hang, but I did not have the
>> time to do any analysis, as I needed the ssh too urgently.  Backing off
>> to the released version of cygwin1.dll restored normal ssh operation.  I
>> will try the experimental version again when I am less time-strapped, and
>> copy the -vv log of the failed calls.
>
> ... and I get the same with 1.5.25-10.  cygcheck.out attached.
>
> Here are the last few lines of ssh -vv under 1.5.25-10:
> [...]

They are not helpful, unfortunately.  I still can't reproduce it and I
can't debug what I can't reproduce.  For good measure I tested this
additionally on NT4 and Vista.  Works fine every time.  This is yet
another case where the problem should be debugged by a person who can
reproduce this problem.


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/

Re: chown with not existing user/group

[Matthieu CASTET]

Corinna Vinschen  cygwin.com> writes:

> 
> On Feb 29 09:16, Matthieu CASTET wrote:
> > Hi,
> 
> Why do you want to fake security when yoi can get the real thing?
> 
For the same reason that fakeroot is used on UNIX : I want to create images with
special unix right.

Also according to my posix reading [1], chown should be able to change perm to
any uid/gid. I was thinking cygwin goal was to emulate as much as possible posix
spec.


Matthieu

[1] http://www.opengroup.org/onlinepubs/009695399/functions/chown.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/

Re: chown with not existing user/group

[Eric Blake]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Matthieu CASTET on 3/4/2008 6:28 AM:
| Also according to my posix reading [1], chown should be able to change
perm to
| any uid/gid.

You read wrong.  POSIX also allows chown implementations to impose
additional restrictions.  And on cygwin, we impose the additional
restriction that you can't change to a uid/gid that isn't recognized by
Windows.

| I was thinking cygwin goal was to emulate as much as possible posix
| spec.

Yes, and cygwin's behavior in this case is still POSIX compliant.

- --
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

iD8DBQFHzVFA84KuGfSFAYARAjI9AJwI/o6Or9YnPMPHrI6wvO4byQGqZgCgn/1s
J2vBp2lLTx4nVupkqr6KNVg=
=DsSR
-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: chown with not existing user/group

[Corinna Vinschen]

On Mar  4 06:40, Eric Blake wrote:
> | I was thinking cygwin goal was to emulate as much as possible posix
> | spec.
>
> Yes, and cygwin's behavior in this case is still POSIX compliant.

Right.  The error code in question is this:

  [EINVAL]
The owner or group ID supplied is not a value supported by the
implementation.

We *could* create non-existant SIDs in the security descriptors of
files, but I don't know what the sense would be.  These SIDs would
never, on no machine, have a real user or group representation.  It's
not quite comparable with using non-existant uids on a Unix box.  These
uids can exist on another machine where they make sense.  That's not how
it is with SIDs since SIDs are bound to a computer or domain.  Fake SIDs
are bound to nothing at all and are never correctly recognized.


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/

RE: Definitely no sshd on FAT32?

[Dave Korn]

On 04 March 2008 03:57, Jason Pyeron wrote:

> Top posting, sorry.

  Shift, Ctrl+End, delete.  It's an awful lot less keypresses than an
apology!

  Oh, should mention BTW that those disclaimers are utterly without basis
and invalid and are in fact barred on sourceware.org mailing lists.  I
notice you had to use a spammers' trick to sneak it past the filters.
DON'T.  The fact you had to go to such lengths should have made it clear to
you that it isn't wanted.  Please refresh your memory of list policy at y

http://sourceware.org/lists.html
http://cygwin.com/lists.html

cheers,
  DaveK

-- 
Can't think of a witty .sigline today


--
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/

writing to /proc file system

[Jeff Fulmer]

I'd like to access and write to the /proc file system from a java program.
Can somebody steer me in the right direction? I'm starting to feel that
I've exhausted my search options...

TIA,
Jeff


--
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: writing to /proc file system

[Corinna Vinschen]

On Mar  4 10:12, Jeff Fulmer wrote:
> I'd like to access and write to the /proc file system from a java program.
> Can somebody steer me in the right direction? I'm starting to feel that
> I've exhausted my search options...

/proc is not writable on Cygwin.


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/

Re: writing to /proc file system

[Christopher Faylor]

On Tue, Mar 04, 2008 at 04:29:15PM +0100, Corinna Vinschen wrote:
>On Mar  4 10:12, Jeff Fulmer wrote:
>> I'd like to access and write to the /proc file system from a java program.
>> Can somebody steer me in the right direction? I'm starting to feel that
>> I've exhausted my search options...
>
>/proc is not writable on Cygwin.

And, if the java program doesn't use the cygwin DLL the /proc filesystem
isn't even accessible.

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: Definitely no sshd on FAT32?

[Christopher Faylor]

On Mon, Mar 03, 2008 at 10:57:20PM -0500, Jason Pyeron wrote:
>[snip obfuscated disclaimer]

You apparently received a bounce message telling you that we don't
accept the type of disclaimers found in a message you attempted to send
here.  So, you just added some dots to the disclaimer.

This is unacceptable.  You are knowingly violating site policy.  If you do
it again, your ability to send email to mailing lists at this site will
be suspended.

FYI.

--
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: Serial port using USB adaptor

[Stepp, Charles]

Yeah. RS232C can operate in many different ways, using the various "wires" 
differently. Opening a serial port is just the beginning of the work; then 
there is deciding what signals and handshake to use. Ohthe good ol' days.

Charles Stepp
Meskimen's Law:
There's never time to do it rite, but there's always time to do it over.

-Original Message-
From: Samuel Thibault [mailto:[EMAIL PROTECTED] 
Sent: Saturday, March 01, 2008 5:05 AM
To: cygwin@cygwin.com
Subject: Re: Serial port using USB adaptor

hce, le Sat 01 Mar 2008 20:20:21 +1100, a écrit :
> One more thing, if a serial port is not connected by a serial cable,
> it can still open a serila port without errors. That was very stange
> to everybody when a problem printed out "Open Serial Port /dev/com1
> success", but actually there was no cable connected to that port. Is
> it a bug in Cygwin?

That's not a bug: a daemon can then open a port and detect whenever you
plug something and switch it on.

Samuel

--
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/

bug with touch t/

[Eric Blake]

According to POSIX (and as implemented on Linux):

$ rm -Rf t
$ touch t/
touch: setting times of `t/': No such file or directory
$ : > t/
t/: Is a directory.


The ENOENT failure is correct, since you are using the syntax to open (or 
create) a directory but are not going through mkdir.  However, on cygwin, both 
commands mistakenly create the regular file 't'.  This is also an issue with

touch 't\'

which likewise mistakenly creates the regular file 't' by treating \ as an 
alternate directory separator - as a result, the current git checkout of 
autoconf is triggering spurious failures when testing whether the file system 
supports \ embedded in file names rather than as directory separators.

-- 
Eric Blake



--
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: [ANNOUNCEMENT] Updated: [experimental] cygwin-1.5.25-10

[Karl M]

> Date: Tue, 4 Mar 2008 13:54:18 +0100
> From: [EMAIL PROTECTED]
> To: cygwin@cygwin.com
> Subject: Re: [ANNOUNCEMENT] Updated: [experimental] cygwin-1.5.25-10
>
> On Mar 3 21:33, Robin Walker wrote:
>> --On 03 March 2008 11:46 + Robin Walker wrote:
>>
>>> I noticed the same with 1.5.25-9 last night. It's not just calls to
>>> localhost: it's ssh calls to anywhere that hang: in other words, it's a
>>> client-side problem, not server-side. I noticed that the -vv option of
>>> ssh threw an error report just before the hang, but I did not have the
>>> time to do any analysis, as I needed the ssh too urgently. Backing off
>>> to the released version of cygwin1.dll restored normal ssh operation. I
>>> will try the experimental version again when I am less time-strapped, and
>>> copy the -vv log of the failed calls.
>>
>> ... and I get the same with 1.5.25-10. cygcheck.out attached.
>>
>> Here are the last few lines of ssh -vv under 1.5.25-10:
>> [...]
>
> They are not helpful, unfortunately. I still can't reproduce it and I
> can't debug what I can't reproduce. For good measure I tested this
> additionally on NT4 and Vista. Works fine every time. This is yet
> another case where the problem should be debugged by a person who can
> reproduce this problem.
>
>
> Corinna
>
Hi All...

Here is a little more information.

1) I have attached the output of ssh -v -v -v localhost from a good run and a 
bad (1.5.25-10) run. These were actually taken on two similar Cygwin 
installations.

2) I can ssh from the good machine to the bad one with no problem. And... from 
there, I can ssh localhost just fine.

3) When I ssh localhost on the bad machine, it appears not to really be hung. 
If I type exit, it returns; it looks as if I am just not getting any output.

4) I run bash from a cmd window (XP SP2), with CYGWIN=tty on both machines.

Thanks,

...Karl
_
Climb to the top of the charts! Play the word scramble challenge with star 
power.
http://club.live.com/star_shuffle.aspx?icid=starshuffle_wlmailtextlink_jan

--
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: [ANNOUNCEMENT] Updated: [experimental] cygwin-1.5.25-10

[Karl M]

>> Date: Tue, 4 Mar 2008 13:54:18 +0100
>> Subject: Re: [ANNOUNCEMENT] Updated: [experimental] cygwin-1.5.25-10
>>
>> On Mar 3 21:33, Robin Walker wrote:
>>> --On 03 March 2008 11:46 + Robin Walker wrote:
>>>
 I noticed the same with 1.5.25-9 last night. It's not just calls to
 localhost: it's ssh calls to anywhere that hang: in other words, it's a
 client-side problem, not server-side. I noticed that the -vv option of
 ssh threw an error report just before the hang, but I did not have the
 time to do any analysis, as I needed the ssh too urgently. Backing off
 to the released version of cygwin1.dll restored normal ssh operation. I
 will try the experimental version again when I am less time-strapped, and
 copy the -vv log of the failed calls.
>>>
>>> ... and I get the same with 1.5.25-10. cygcheck.out attached.
>>>
>>> Here are the last few lines of ssh -vv under 1.5.25-10:
>>> [...]
>>
>> They are not helpful, unfortunately. I still can't reproduce it and I
>> can't debug what I can't reproduce. For good measure I tested this
>> additionally on NT4 and Vista. Works fine every time. This is yet
>> another case where the problem should be debugged by a person who can
>> reproduce this problem.
>>
>>
>> Corinna
>>
> Hi All...
>
> Here is a little more information.
>
> 1) I have attached the output of ssh -v -v -v localhost from a good run and a 
> bad (1.5.25-10) run. These were actually taken on two similar Cygwin 
> installations.
>
> 2) I can ssh from the good machine to the bad one with no problem. And... 
> from there, I can ssh localhost just fine.
>
> 3) When I ssh localhost on the bad machine, it appears not to really be hung. 
> If I type exit, it returns; it looks as if I am just not getting any output.
>
> 4) I run bash from a cmd window (XP SP2), with CYGWIN=tty on both machines.
>
> Thanks,
>
> ...Karl

OOPS! the attachments.

_
Connect and share in new ways with Windows Live.
http://www.windowslive.com/share.html?ocid=TXT_TAGHM_Wave2_sharelife_012008[EMAIL PROTECTED] ~
$ ssh -v -v -v localhost
OpenSSH_4.7p1, OpenSSL 0.9.8g 19 Oct 2007
debug1: Reading configuration data /home/user/.ssh/config
debug1: Applying options for localhost
debug2: ssh_connect: needpriv 0
debug1: Connecting to localhost [127.0.0.1] port 10022.
debug1: Connection established.
debug1: identity file /home/user/.ssh/identity type 0
debug3: Not a RSA1 key file /home/user/.ssh/id_rsa.
debug2: key_type_from_name: unknown key type '-BEGIN'
debug3: key_read: missing keytype
debug2: key_type_from_name: unknown key type 'Proc-Type:'
debug3: key_read: missing keytype
debug2: key_type_from_name: unknown key type 'DEK-Info:'
debug3: key_read: missing keytype
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug2: key_type_from_name: unknown key type '-END'
debug3: key_read: missing keytype
debug1: identity file /home/user/.ssh/id_rsa type 1
debug3: Not a RSA1 key file /home/user/.ssh/id_dsa.
debug2: key_type_from_name: unknown key type '-BEGIN'
debug3: key_read: missing keytype
debug2: key_type_from_name: unknown key type 'Proc-Type:'
debug3: key_read: missing keytype
debug2: key_type_from_name: unknown key type 'DEK-Info:'
debug3: key_read: missing keytype
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug2: key_type_from_name: unknown key type '-END'
debug3: key_read: missing keytype
debug1: identity file /home/user/.ssh/id_dsa type 2
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.7
debug1: match: OpenSSH_4.7 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.7
debug2: fd 3 setting O_NONBLOCK
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received

Re: [ANNOUNCEMENT] Updated: [experimental] cygwin-1.5.25-10

[Corinna Vinschen]

On Mar  4 13:52, Karl M wrote:
> 4) I run bash from a cmd window (XP SP2), with CYGWIN=tty on both machines.
^^^
That's what I was missing.

Should be fixed in the next test release which I'll prepare tomorrow.


Thanks,
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/

Re: writing to /proc file system

[NightStrike]

On 3/4/08, Corinna Vinschen <[EMAIL PROTECTED]> wrote:
> On Mar  4 10:12, Jeff Fulmer wrote:
> > I'd like to access and write to the /proc file system from a java program.
> > Can somebody steer me in the right direction? I'm starting to feel that
> > I've exhausted my search options...
>
> /proc is not writable on Cygwin.

I'm pretty sure it's not writable on any system, let alone cygwin.
It's not a real filesystem per se.  It's instead a read-only gateway
into the kernel.

--
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: writing to /proc file system

[Brian Dessent]

NightStrike wrote:

> I'm pretty sure it's not writable on any system, let alone cygwin.
> It's not a real filesystem per se.  It's instead a read-only gateway
> into the kernel.

What?  No.  The entire /proc/sys tree on Linux is writable, which allows
you to tune a great number of kernel parameters at runtime, including
networking stack parameters, filesystems, cacheing, memory management,
etc.  In fact this forms the basis for the entire sysctl settings
system.  For example you can clear all disk caches with "echo 3 >
/proc/sys/vm/drop_caches".  More at:






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[2]: ZSH - UTF-8

[Peter A. Castro]

On Tue, 4 Mar 2008, Paul-Kenji Cahier wrote:

Greetings, Paul-Kenji,


?LC_ALL set to C.UTF-8 in all cases. Cygwin freshly installed.
?Also tried LC_ALL=en_US.UTF-8(which shouldnt exist) and it did
?not work either.



?Newlib uses "C-UTF-8", not "C.UTF-8" for some reason.  I don't see that
?newlib understands the dot.  Moreover, Cygwin doesn't support utf-8 yet,
?so you might have strange effects using utf-8 for filenames.



?Corinna


(this time text under quote, didnt know it bothered)

I'm still failing to get zsh working with utf-8, even
with C-UTF-8 as LC_ALL: as specified in my previous message
non-ascii bytes get displayed as <00cxx> which the line editor
does manage properly. But there is still no way to actually see
utf-8 characters displayed, or even their unicode values(ie
it's still a single byte editing mode). If someone manages
to get it working, please post:)


Can you send me the specific key sequence you are using to generate this?
Are you using a CMD window or rxvt or an xterm?  Also, are you using the
stock zsh 4.3.5 source distro or have you applied the Cygwin patches from
4.3.4 to it before building?

I've recently built 4.3.5 for Cygwin and have been testing it before
releasing it.  Send me the key sequences you are using and I'll see if I
can repro it.

As Corinna noted, Cygwin doesn't really support utf-8, so this might have
some bearing on the matter.  And, you should know that some multi-byte
delete issues have been identified on other, supposedly, UTF-8 compliant
systems, so you aren't the first to hit this.


Also I know about the lack of utf-8 support in cygwin for most
of the windows calls(and personally think that the cygwin utf-8
wrapper code patch would be a vast improvement, that is the one
from okisoft that got posted to cygwin's ml long ago, though
I understand some people dont like how it's done). This should
still not be a problem for one to do an "echo éé"
in his term transparently.
(no problematic wide windows calls involved there as far as I know).

Paul-Kenji Cahier


--
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/



--
Peter A. Castro <[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
"Cats are just autistic Dogs" -- Dr. Tony Attwood
--
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/

Help with GCC on Cygwin

[Balaji V. Iyer]

Hello Everyone,
I am trying to do some development on the C Compiler in Cygwin and I
am doing the following to build it:
 
$ ../gcc-4.0.2/gcc/configure
--prefix=/home/Balaji/Software_Tools/install --enable-languages="c"
 
The problem i am getting is this:
 
$ make all install
TARGET_CPU_DEFAULT="" \
HEADERS="auto-host.h ansidecl.h config/i386/xm-cygwin.h"
DEFINES="" \
/bin/sh ../gcc-4.0.2/gcc/mkconfig.sh config.h
TARGET_CPU_DEFAULT="" \
HEADERS="config/i386/i386.h config/i386/unix.h config/i386/bsd.h
config/
i386/gas.h config/dbxcoff.h config/i386/cygming.h config/i386/cygwin.h
defaults.
h" DEFINES="" \
/bin/sh ../gcc-4.0.2/gcc/mkconfig.sh tm.h
TARGET_CPU_DEFAULT="" \
HEADERS="auto-host.h ansidecl.h config/i386/xm-cygwin.h"
DEFINES="" \
/bin/sh ../gcc-4.0.2/gcc/mkconfig.sh bconfig.h
/home/Balaji/Software_Tools/gcc-4.0.2/compile gcc
-c   -g -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes
-Wmissing-protot
ypes -Wold-style-definition-DHAVE_CONFIG_H -DGENERATOR_FILE -I.
-Ibuild -I..
/gcc-4.0.2/gcc -I../gcc-4.0.2/gcc/build -I../gcc-4.0.2/gcc/../include
-I../gcc-4
.0.2/gcc/../libcpp/include -o build/genmodes.o
../gcc-4.0.2/gcc/genmodes.c
/home/Balaji/Software_Tools/gcc-4.0.2/compile gcc
-c   -g -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes
-Wmissing-protot
ypes -Wold-style-definition-DHAVE_CONFIG_H -DGENERATOR_FILE -I.
-Ibuild -I..
/gcc-4.0.2/gcc -I../gcc-4.0.2/gcc/build -I../gcc-4.0.2/gcc/../include
-I../gcc-4
.0.2/gcc/../libcpp/include -o build/errors.o
../gcc-4.0.2/gcc/errors.c
make: *** No rule to make target
`../build-i686-pc-cygwin/libiberty/libiberty.a'
, needed by `build/genmodes.exe'.  Stop.
 
 
I am currently using cygwin on a x86 machine, gcc version 4.0.2 (I have
to use this version...can't use a diferent one), 
 
 
Any help is very highly appreciated!
 
Thanking You,
 
Yours Sincerely,
 
Balaji V. Iyer.
 
 
PS. Here is the output I received right after I ran the configur
command.
 
checking build system type... i686-pc-cygwin

checking host system type... i686-pc-cygwin

checking target system type... i686-pc-cygwin

checking LIBRARY_PATH variable... ok

checking GCC_EXEC_PREFIX variable... ok

checking whether to place generated files in the source directory... no

checking whether a default linker was specified... no

checking whether a default assembler was specified... no

checking for gcc... gcc

checking for C compiler default output file name... a.exe

checking whether the C compiler works... yes

checking whether we are cross compiling... no

checking for suffix of executables... .exe

checking for suffix of object files... o

checking whether we are using the GNU C compiler... yes

checking whether gcc accepts -g... yes

checking for gcc option to accept ANSI C... none needed

checking whether gcc and cc understand -c and -o together... yes

checking how to run the C preprocessor... gcc -E

checking for inline... inline

checking for long long int... yes

checking for __int64... no

checking for egrep... grep -E

checking for ANSI C header files... yes

checking for sys/types.h... yes

checking for sys/stat.h... yes

checking for stdlib.h... yes

checking for string.h... yes

checking for memory.h... yes

checking for strings.h... yes

checking for inttypes.h... yes

checking for stdint.h... yes

checking for unistd.h... yes

checking for void *... yes

checking size of void *... 4

checking for short... yes

checking size of short... 2

checking for int... yes

checking size of int... 4

checking for long... yes

checking size of long... 4

checking for long long... yes

checking size of long long... 8

checking whether gcc accepts -Wno-long-long... yes

checking whether gcc accepts -Wno-variadic-macros... no

checking whether gcc accepts -Wold-style-definition... yes

checking valgrind.h usability... no

checking valgrind.h presence... no

checking for valgrind.h... no

checking whether make sets $(MAKE)... yes

checking for gawk... gawk

checking whether ln -s works... yes

checking whether ln works... yes

checking for ranlib... ranlib

checking for a BSD compatible install... /usr/bin/install -c

checking for cmp's capabilities... gnucompare

checking for mktemp... yes

checking for makeinfo... makeinfo

checking for modern makeinfo... yes

checking for recent Pod::Man... yes

checking for flex... flex

checking for bison... bison

checking for nm... nm

checking for ar... ar

checking for GNU C library... no

checking for ANSI C header files... (cached) yes

checking whether time.h and sys/time.h may both be included... yes

checking whether string.h and strings.h may both be included... yes

checking for sys/wait.h that is POSIX.1 compatible... yes

checking for limits.h... yes

checking for stddef.h... yes

checking for string.h... (cached) yes

checking for strings.h... (cached) yes

checking for stdlib.h... (cached) yes

checking for time.h... yes

checking for iconv.h... yes

checking for fcntl.

Re: Help with GCC on Cygwin

[Eric Lilja]

Crap, I didn't notice the stupid CC. Oh well, I won't authorize it so 
gmane should trap 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: Help with GCC on Cygwin

[Ian Lance Taylor]

"Balaji V. Iyer" <[EMAIL PROTECTED]> writes:

> I am trying to do some development on the C Compiler in Cygwin and I
> am doing the following to build it:

[EMAIL PROTECTED] is the wrong mailing list.  Please send any further
e-mail to [EMAIL PROTECTED]  Thanks.

> $ ../gcc-4.0.2/gcc/configure

Run ../gcc-4.0.2/configure, not ../gcc-4.0.2/gcc/configure.

Ian

--
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: Help with GCC on Cygwin

[Eric Lilja]

Balaji V. Iyer wrote:
[snip]
I'm used to building in a separate directory. Say I've unpacked the 
tarball in my home directory, I would do something like:

$ mkdir gcc-build
$ cd gcc-build
$ ../gcc-4.0.2/configure --prefix=/usr/local/gcc-4.0.2 --enable-languages=c
(And a few more flags but I've omitted them here.)
$ make bootstrap
$ make install

The prefix is to not mess with the old gcc. If you keep the gcc-build 
directory you can install gcc 4.0.2 with $ make uninstall. The make all 
install you're doing I'm not familiar with.


- Eric


--
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: Help with GCC on Cygwin

[Balaji V. Iyer]

Thank you Ian. I did the modification you mentioned...now I am running
into more problems.

Now it is failing somewhere in libiberty.. here is the exact message (I
just simply typed "make all install") (I get same messae when I just do
"make")

Configuring in fixincludes
configure: loading cache ./config.cache
checking build system type... i686-pc-cygwin
checking host system type... i686-pc-cygwin
checking target system type... i686-pc-cygwin
checking for i686-pc-cygwin-gcc... gcc
checking for C compiler default output file name... a.exe
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... .exe
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking stddef.h usability... yes
checking stddef.h presence... yes
checking for stddef.h... yes
checking for stdlib.h... (cached) yes
checking for strings.h... (cached) yes
checking for unistd.h... (cached) yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking sys/file.h usability... yes
checking sys/file.h presence... yes
checking for sys/file.h... yes
checking for sys/stat.h... (cached) yes
checking for clearerr_unlocked... no
checking for feof_unlocked... no
checking for ferror_unlocked... no
checking for fflush_unlocked... no
checking for fgetc_unlocked... no
checking for fgets_unlocked... no
checking for fileno_unlocked... no
checking for fprintf_unlocked... no
checking for fputc_unlocked... no
checking for fputs_unlocked... no
checking for fread_unlocked... no
checking for fwrite_unlocked... no
checking for getchar_unlocked... yes
checking for getc_unlocked... yes
checking for putchar_unlocked... yes
checking for putc_unlocked... yes
checking whether abort is declared... yes
checking whether errno is declared... no
checking whether clearerr_unlocked is declared... no
checking whether feof_unlocked is declared... no
checking whether ferror_unlocked is declared... no
checking whether fflush_unlocked is declared... no
checking whether fgetc_unlocked is declared... no
checking whether fgets_unlocked is declared... no
checking whether fileno_unlocked is declared... no
checking whether fprintf_unlocked is declared... no
checking whether fputc_unlocked is declared... no
checking whether fputs_unlocked is declared... no
checking whether fread_unlocked is declared... no
checking whether fwrite_unlocked is declared... no
checking whether getchar_unlocked is declared... yes
checking whether getc_unlocked is declared... yes
checking whether putchar_unlocked is declared... yes
checking whether putc_unlocked is declared... yes
checking for an ANSI C-conforming const... yes
checking sys/mman.h usability... yes
checking sys/mman.h presence... yes
checking for sys/mman.h... yes
checking for mmap... yes
checking whether read-only mmap of a plain file works... yes
checking whether mmap from /dev/zero works... no
checking for MAP_ANON(YMOUS)... yes
checking whether mmap with MAP_ANON(YMOUS) works... no
checking whether to enable maintainer-specific portions of Makefiles...
no
updating cache ./config.cache
configure: creating ./config.status
config.status: creating Makefile
config.status: creating mkheaders
config.status: creating config.h
Configuring in libiberty
configure: creating cache ./config.cache
checking whether to enable maintainer-specific portions of Makefiles...
no
checking for makeinfo... makeinfo
checking for perl... perl
checking build system type... i686-pc-cygwin
checking host system type... i686-pc-cygwin
checking for i686-pc-cygwin-ar... ar
checking for i686-pc-cygwin-ranlib... ranlib
checking for i686-pc-cygwin-gcc... gcc
checking for C compiler default output file name... a.exe
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... .exe
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking how to run the C preprocessor... gcc -E
checking whether gcc and cc understand -c and -o together... yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking whether byte ordering is bigendian... no
checking for a BSD-compatible install... /usr/bin/install -c
checking for sys/file.h... yes
checking for sys/param.h... yes
checking for limits.h... yes
checking for stdlib.h... ye