Re: cygwin 1.7.0-40: Socket operation on non-socket

[Corinna Vinschen]

On Feb 12 08:59, Steffen Sledz wrote:
> On one of my machines running cygwin a few programs (like rsync or dig) fail 
> with an error like this (for detailed info see attached strace.txt):
> 
>  $ dig @dns1.dresearch.de www.cygwin.com
>  
> /usr/src/ports/net/bind/bind-9.6.0-1/src/bind-9.6.0/lib/isc/unix/socket.c:4525:
>  bind: Socket operation on non-socket
>  dig: isc_socket_bind: unexpected error

You already sent this message, why don't you stick to the original
thread?  Anyway, works for me.  This error message is never generated
explicitely by Cygwin, it's always a return code from a Winsock
function.  Whatever the reason is on your machine, it's not under the
control of Cygwin, apparently.

Did you check for http://cygwin.com/acronyms/#BLODA?  See this in your
cygcheck output:

> Potential app conflicts:
> 
> ByteMobile laptop optimization client
> Detected: Named file.

Also, see this very old reply
http://www.cygwin.com/ml/cygwin/2004-09/msg00444.html and the followup
http://www.cygwin.com/ml/cygwin/2004-09/msg00458.html to this very old
thread you're referring to
>  
As well as
http://sourceware.org/ml/cygwin/2008-01/msg00342.html

If you really can't nail down the reason, we need a reproducible testcase,
preferrably in plain C source code.  The above one is not reproducible.


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: cygwin 1.7.0-40: Socket operation on non-socket

[Dave Korn]

Steffen Sledz wrote:

> H? That's a pity. But as seen in the mailing lists i'm not the only one
> with such problems. May be there is generic workaround for this? Or a guide
> line how to identify the dodgy app?

  Unfortunately this is not a very easy task.  The failures are provoked in
different ways by different interfering applications, and what works around
one has no guarantee of working for another.  Figuring out the responsible
application often involves attaching a debugger to the process while an error
occurs and trying to get a look at the stack, to see any OS hooks that might
have been inserted.

  You might get interesting results by running "netsh winsock show catalog" in
a cmd.exe window, as that will show us if there is some other layered service
provider potentially interfering with your networking.

cheers,
  DaveK



--
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: cygwin 1.7.0-40: Socket operation on non-socket

[Allan Schrum]

> Subject: Re: cygwin 1.7.0-40: Socket operation on non-socket
> 
> Steffen Sledz wrote:
> 
> > H? That's a pity. But as seen in the mailing lists i'm not the
> only one
> > with such problems. May be there is generic workaround for this? Or a
> guide
> > line how to identify the dodgy app?
> 
>   Unfortunately this is not a very easy task.  The failures are
> provoked in
> different ways by different interfering applications, and what works
> around
> one has no guarantee of working for another.  Figuring out the
> responsible
> application often involves attaching a debugger to the process while an
> error
> occurs and trying to get a look at the stack, to see any OS hooks that
> might
> have been inserted.
> 
>   You might get interesting results by running "netsh winsock show
> catalog" in
> a cmd.exe window, as that will show us if there is some other layered
> service
> provider potentially interfering with your networking.
> 
> cheers,
>   DaveK

Using "msconfig" from the "Run" command restart your machine with all 
non-Microsoft
programs stopped.
On the "Services" tag, click "Hide all Microsoft Services", then "Disable All".
On the "Startup" tag, click "Disable All".
Click "OK" and reboot.

Does the problem still occur? If not, then BLODA may be to blame.
If so, then the problem space is smaller and maybe easier to find
a test case.

-Allan

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

CygWine 1.0 Beta -- an new cygwin package manager

[Brant Young]

Hi everyone,

I have launched a opensource project -- CygWine ( a cygwin package
management utility, project homepage: http://cygwine.googlecode.com )

CygWine 1.0 beta was just released, you can download the executable
and browse screenshots at http://cygwine.googlecode.com.

Compared to cygwin official install tool -- setup.exe, CygWine is more
easy to use, has more intuitive UI.

Currently, some of setup.exe features not supported by CygWine, I will
add more functions in the next release.

I hope you will like it, suggestions and contributions are welcome.

Regards,

Yospaly

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

mingw SEARCH_LIB: was gcc FAQ entries

[Reini Urban]

Chris Sutcliffe schrieb:

At one point we will get a mingw cross compiler, right?  wrong?


I'd appreciate having once since I use Cygwin to produce my MinGW packages.


BTW: Your linker script SEARCH_LIB("/usr/lib"); ... entries cause 
headaches on mingw pure. mingw ld should not be linked with that.


E.g. see https://trac.parrot.org/parrot/ticket/322

mingw32\lib\ldscripts\i386pe.x:
/* Default linker script, for normal executables */
OUTPUT_FORMAT(pei-i386)
SEARCH_DIR("/mingw/mingw32/lib"); SEARCH_DIR("/mingw/lib"); 
SEARCH_DIR("/usr/local/lib"); SEARCH_DIR("/lib"); SEARCH_DIR("/usr/lib");

...
--
Reini Urban
http://phpwiki.org/  http://murbreak.at/

--
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: mingw SEARCH_LIB: was gcc FAQ entries

[Chris Sutcliffe]

Hey Reini,

> BTW: Your linker script SEARCH_LIB("/usr/lib"); ... entries cause headaches
> on mingw pure. mingw ld should not be linked with that.

Thanx for the heads up!

I'm curious, I use the binutils package I uploaded to the MinGW site
daily (with mingw pure, i.e. no Cygwin) and have not seen any issues,
can you please provide an example of the issue (assuming it's not too
much work)?

Chris

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

Re: Tried mintty but it locks-up on enabling "Copy on select"

[rhubbell]

Turns out I tried again to see if some particular app was part of the problem.
Tried YIM, Word, etc. But couldn't pinpoint. But I did see the problem
again. Still occurred while in the Options menu but was not in the copy-on-
select menu.  Just switching between sub-menus.

Maybe I'll try again some time and use ollydbg.

On Thu, 12 Feb 2009 07:33:51 +
Andy Koppe  wrote:

> > 1) run setup.exe
> > 2) download -- but don't install
> > 3) run setup.exe -- install from local dir
> > 4) in filemanager dbl-click mintty.exe
> > 5) in the term rt-click->Options->mouse->enable copy-on-select
> > 6) mintty becomes unresponsive
> > 7) kill mintty.exe and the associated bash.exe
> >
> > I tried these steps today and was unable to reproduce.
> 
> Thanks for trying anyway!
> 
> > Q2) Have you got any clipboard utilities running?
> > A2) Every application has access to the clipboard, right? So yes.
> 
> You can get various 3rd party utilities for adding stuff like a
> clipboard history or Windows-wide copy-on-select.
> 
> > Q3) Does it work if you delete or rename ~/.minttyrc to go back to the 
> > default settings and copy something through the context menu?
> > A3) Didn't find a .minttyrc, does mintty create one when it starts?
> 
> No, it only creates one when you press OK in the options dialog, but
> of course you didn't get to that.
> 
> >What does mintty put in there if it creates one?
> 
> Its settings, in the form of key-value pairs like 'CopyOnSelect=1'.
> (I'd asked in case it was a particular combination of options that
> triggered the crash.)
> 
> Andy
> 
> --
> 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/
> 

--
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: mingw SEARCH_LIB: was gcc FAQ entries

[Chris Sutcliffe]

>> BTW: Your linker script SEARCH_LIB("/usr/lib"); ... entries cause headaches
>> on mingw pure. mingw ld should not be linked with that.
>
> Thanx for the heads up!
>
> I'm curious, I use the binutils package I uploaded to the MinGW site
> daily (with mingw pure, i.e. no Cygwin) and have not seen any issues,
> can you please provide an example of the issue (assuming it's not too
> much work)?

FWIW, I just went back to the older binutils packages, that they have:

SEARCH_DIR("/mingw/mingw32/lib"); SEARCH_DIR("/mingw/lib");
SEARCH_DIR("/usr/local/lib"); SEARCH_DIR("/lib");
SEARCH_DIR("/usr/lib");

Defined in the ldscripts\i386pe.x.  So it's been this way for quite some time.

Chris

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

Re: CygWine 1.0 Beta -- an new cygwin package manager

[Warren Young]

Brant Young wrote:


I have launched a opensource project -- CygWine ( a cygwin package
management utility, project homepage: http://cygwine.googlecode.com )


My initial thought on seeing the name is that it was a port of Wine to 
Cygwin, which would be tres silly.


We don't really need two different installers, so I hope you find a way 
to merge your efforts with those working on setup.exe.  The licenses are 
the same.  If that happens, then maybe your program just becomes 
setup.exe, and the naming issue goes away, too,


On starting it here, I get an error message about being unable to load 
from /setup.bz2.  I then manually set a mirror, which did nothing until 
I restarted the app.  Your program shouldn't have to ask for either of 
these things: it can get them from the same place setup.exe does.  If it 
has neither, it should ask, like setup.exe does, before it presents the 
package list.


When I clicked (Re)Install Cygwin, its first choice of directory to 
upgrade is my Cygwin 1.5 directory, not my 1.7 directory.  It's not 
clear to me if this means it just looks for 1.5 first, or if it really 
only supports 1.5.  I don't want to wreck anything, so I haven't used 
CygWine to install anything yet.


Speaking of, one of the weaknesses of setup.exe is that it gets confused 
if you have Cygwin 1.7 installed in c:\cygwin (as I do) and then try to 
install 1.5 somewhere else.  It happens because the 1.5 version of 
setup.exe grabs the package list from c:\cygwin, not realizing that it's 
for a different version of Cygwin.  I don't know how much work you want 
to put into making your program cope with two versions of Cygwin, but 
you should take some care not to entangle them if they're both present. 
 How exactly you go about that depends on whether you want to support 
both versions at all -- maybe you intend to support only 1.7, given that 
1.5's run is almost over.


I like that it detects which Cygwin-using programs are running and names 
them for you, instead of making you guess which files conflict, as 
setup.exe does.  I also like that it's proactive, not waiting until it 
encounters a file copying error to complain.  Your program should also 
handle that copying error, but the proactive approach should make that 
code path difficult to hit.


The only problem is, you're doing that check too early, before you know 
whether the advice in the dialog is actually correct.  It asked me 
before I'd even selected any packages to download.  There's no way it 
knows what I need to shut down so early.  It should wait until all the 
tarballs are down, then look into them to see what files will be 
replaced, and figure out whether any files currently loaded into memory 
will be replaced.  Unless you're replacing a running service, bash, or 
cygwin1.dll, changes are good that you can install while those things 
stay running.


A long-standing wishlist item for setup.exe is something like you see in 
Linux distributions, where the installer abstracts away the full package 
 list, with its first screen showing a relatively small number of 
groups of mutually coherent and supporting sets of packages.  You can 
still get at the full package list, but the idea is that most people 
will just select those package sets that include the functionality they 
want.  This ends up installing more packages than is strictly required, 
but human time is more expensive than bandwidth in most cases.


For instance, I'd like to be able to select the "Text Based Internet" 
category and get ssh, rsync, lynx, wget, and lftp.  When there are 
multiple packages in Cygwin providing a given function (e.g. lynx, 
elinks, and w3c), you should just pick one and call it your standard.


I'd also like to see a command line interface to the program, and for 
CygWine to install itself into c:\cygwin\bin.  I'd like to be able to 
say "cygwine install rsync" from a bash prompt, and have it 
automatically go to the last mirror I selected through the GUI, grab the 
package and its dependencies, place them in the last place it downloaded 
packages[*], and install them.  If you do this, please copy the command 
line format of one of the tools that do this on other OSes.  I'd prefer 
yum, but apt-get or fink would be fine.  These three all have 
differences, despite being so similar in effective function.  This wheel 
has been reinvented enough times now.


Combining these two, the way I'd most like it to work is this:

1. Start CygWine, it asks you where to install, what mirror to use, 
etc., like setup.exe does


2. Then it gives you a list of maybe 20 groups of packages.  Checking 
off all of them doesn't install absolutely everything, just that subset 
that provides all of the named functions.  You then have a branch:


3a. Click Install to install those package groups

3b. Click Select Individual Packages to switch into the current CygWine 
view.  The packages belonging to the groups you selected on the previuos 
screen are already checked of

Re: CygWine 1.0 Beta -- an new cygwin package manager

[Dave Korn]

Brant Young wrote:
> Hi everyone,
> 
> I have launched a opensource project -- CygWine ( a cygwin package
> management utility, project homepage: http://cygwine.googlecode.com )
> 
> CygWine 1.0 beta was just released, you can download the executable
> and browse screenshots at http://cygwine.googlecode.com.
> 
> Compared to cygwin official install tool -- setup.exe, CygWine is more
> easy to use, has more intuitive UI.

  I like the nice wx-based GUI, that's really pretty.

> Currently, some of setup.exe features not supported by CygWine, I will
> add more functions in the next release.
> 
> I hope you will like it, suggestions and contributions are welcome.

  I'm taking a quick browse through the code.  I see that you've based it on
chunks of the core setup.exe code, somewhat refactored and restructured.  I
wonder if we couldn't merge the two codebases, in such a way that there's one
common 'setup engine' with a couple of alternative GUI front-ends; that might
be a neat way to fix up all the missing features and make sure there is
thoroughly consistent behaviour between the two different installers.  You
know your own code better than I do - do you think that would be practical?

cheers,
  DaveK


--
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: CygWine 1.0 Beta -- an new cygwin package manager

[Mark J. Reed]

On Thu, Feb 12, 2009 at 12:37 PM, Warren Young wrote:
> Brant Young wrote:

You two aren't related, are you? :)

>> I have launched a opensource project -- CygWine ( a cygwin package
>> management utility, project homepage: http://cygwine.googlecode.com )
>
> My initial thought on seeing the name is that it was a port of Wine to
> Cygwin, which would be tres silly.

I had that exact same thought.  If it can't be merged into the
standard setup.exe, I would at least recommend a different name.

-- 
Mark J. Reed 

--
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: CygWine 1.0 Beta -- an new cygwin package manager

[Ralph Hempel]

Dave Korn wrote:


  I'm taking a quick browse through the code.  I see that you've based it on
chunks of the core setup.exe code, somewhat refactored and restructured.  I
wonder if we couldn't merge the two codebases, in such a way that there's one
common 'setup engine' with a couple of alternative GUI front-ends; that might
be a neat way to fix up all the missing features and make sure there is
thoroughly consistent behaviour between the two different installers.  You
know your own code better than I do - do you think that would be practical?


As long as the command-line options don't go away you can do
whatever you want with the front end :-)

Ralph

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

Cygwin 1.7 Does not work

[Jaspreet Singh]

Hi there,

today i tried to start using 1.7 , but there there where many problems
like

cygrunsrv -S init

gives lots of 

init: error reading initrequest
init: can't open /dev/console

We got bind9 but nobody told how to install it


and just tell me if init works so good in cygwin why not to have
just init and cygserver as windows services and rest like httpd
named, postgresql, proftpd etc in init scripts in which main process
of cygwin like init and cygserver starts with windows and then init
starts all procces with scripts in runlevel.

this will give a kind of Linux feelling tell me if i am wrong

This is just to starting

any help


  Add more friends to your messenger and enjoy! Go to 
http://messenger.yahoo.com/invite/

--
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: CygWine 1.0 Beta -- an new cygwin package manager

[Tim McDaniel]

On Thu, 12 Feb 2009, Mark J. Reed wrote:

On Thu, Feb 12, 2009 at 12:37 PM, Warren Young wrote:

Brant Young wrote:

I have launched a opensource project -- CygWine ( a cygwin package
management utility, project homepage:
http://cygwine.googlecode.com )


My initial thought on seeing the name is that it was a port of Wine
to Cygwin, which would be tres silly.


I had that exact same thought.


M3 T00, AOL, or whatever other means by which the whippersnappers
express agreement now-a-days.

--
Tim McDaniel, t...@panix.com

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

1.7.0 /cygdrive text/binary behavior

[Garber, Dave (GE Infra, Energy, Non-GE)]

Hi,

I've been testing out the 1.7.0-40 release and noticed an odd behavior
with /cygdrive.  Without any modifications, when I try to run a script
from /cygdrive/v, I get errors due to the trail '\r' characters.  This
is expected since /cygdrive/v is a binary mount.  So, I add an entry
into fstab to make /cygdrive/v be a text mount:

V: /cygdrive/v netapp text 0 0

The script still fails with the same errors due to '\r'.  So, I add
another fstab entry:

V: /v netapp text 0 0 

Which is the same thing, but not under the special /cygdrive and running
the script from that works.  So I'm guessing that Cygwin assumes all
/cygdrive mounts to be binary regardless of what is specified in fstab.
That's fine, but mount (see below) shows both being text.  So Cygwin
should either 1) honor the mount type in fstab (my pick) or 2) show that
cygdrive is really being mounted as binary.

$ mount
C:/Apps/cygwin/bin on /usr/bin type ntfs (binary)
C:/Apps/cygwin/lib on /usr/lib type ntfs (binary)
C:/Apps/cygwin on / type ntfs (binary)
D:/Users on /users type ntfs (binary)
V: on /cygdrive/v type netapp (text)   < see here
V: on /v type netapp (text)< and here
C: on /cygdrive/c type ntfs (binary,posix=0,user,noumount)
D: on /cygdrive/d type ntfs (binary,posix=0,user,noumount)
M: on /cygdrive/m type vfat (binary,posix=0,user,noumount)
Y: on /cygdrive/y type vfat (binary,posix=0,user,noumount)


Thanks,
Dave


--
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: CygWine 1.0 Beta -- an new cygwin package manager

[Brian Mathis]

As a layman (not a cygwin developer or anything), I have to say this
looks really great.  The current setup.exe program is certainly (and
almost exclusively) _functional_, this kind of UI is really the next
step.

One thing that could use a major rethink, and seems to be carried over
from the current setup.exe, is the need to right-click to "Mark for
installation", "...reinstallation", etc...  The handling of what to
install, upgrade, or remove is probably one of the biggest issues with
the current setup.exe, and is one of the main parts that could use
some UI brainstorming.

I suggest 3 tabs in the main package information window, for
"Available", "Installed", and "Updates".  The "available" tab would
list packages that are not installed, "installed" would list installed
packages, and "updates" would list packages that have newer versions
available.  Each listing would have a column with checkboxes for each
package, that allows the user to select packages to install, remove,
or update, on each tab.

I see you have something along these lines in the "Packages" section,
but those seelctions seem to muddy the purpose of that panel.

If it were really necessary, a forth tab could be included that shows
a queue of the things that will be done, like installing, updating,
removing, and the apply button might even be on that tab.  I might be
able to mock something up if GIMP weren't so infuriatingly hard to
use.

I was also thrown by the inclusion of "Wine" in the name.  I'm not
familiar with Wine, but the project tagline "make Cygwin like Wine"
doesn't make sense to me.  Maybe this has a similar UI to the Wine
*installer*?  If that's the case, I'm not sure that the interface of
an installer should be considered as equivalent to the entire package,
and in any case is confusing in this context.

Anyway, it looks like really good work!


On Thu, Feb 12, 2009 at 11:25 AM, Brant Young  wrote:
> Hi everyone,
>
> I have launched a opensource project -- CygWine ( a cygwin package
> management utility, project homepage: http://cygwine.googlecode.com )
>
> CygWine 1.0 beta was just released, you can download the executable
> and browse screenshots at http://cygwine.googlecode.com.
>
> Compared to cygwin official install tool -- setup.exe, CygWine is more
> easy to use, has more intuitive UI.
>
> Currently, some of setup.exe features not supported by CygWine, I will
> add more functions in the next release.
>
> I hope you will like it, suggestions and contributions are welcome.
>
> Regards,
>
> Yospaly
>

--
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: Can't get unison to syncroze permission bits

[Andrew Schulman]

> I can't get unison to syncronize the permission bits between my C: drive and 
> my USB drive. Both are NTFS. I use "perms -1".
>  
> What am I missing?

Morten, thanks for the report.  I'll look at this as soon as I can, but I don't
think it will be this week.

My initial guess is that there's some problem in propagating permissions to
removable media.  I.e. if permissions will propagate between directories on the
hard drive, but not between the hard drive and a USB drive, then that's the
problem.  

Anyway I'll try to reproduce the problem here.  I sync over the network with
permissions, and it works fine.

Andrew.


--
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: Cygwin 1.7 Does not work

[Ralph Hempel]

Not to put too fine a point on it, but if you're
trying to run a Linux system on a Windows machine,
why not download the FREE VMWare Server 2.0 and
install Linux as a VM?

You can give the VM a couple of virtual network
adapters and use one for a host-only network and
the other for connectins on your "real" network.

Thi smight be easier than making Cygwin what it is not.

Ralph

--
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: Can't get unison to syncroze permission bits

[Morten Kjærulff]

Hi,

On Thu, Feb 12, 2009 at 8:39 PM, Andrew Schulman wrote:
>> I can't get unison to syncronize the permission bits between my C: drive and 
>> my USB drive. Both are NTFS. I use "perms -1".
>>
>> What am I missing?
>
> Morten, thanks for the report.  I'll look at this as soon as I can, but I 
> don't
> think it will be this week.
>
> My initial guess is that there's some problem in propagating permissions to
> removable media.  I.e. if permissions will propagate between directories on 
> the
> hard drive, but not between the hard drive and a USB drive, then that's the
> problem.

Same thing if I syncornize 2 directories on the C: drive:
(
Note the lines:
[copy] copyRegFile(/home/Compaq_Ejer/da,a) -> (/home/Compaq_Ejer/db,a,/home/Comp
aq_Ejer/db,.unison.a.62dd79.unison.tmp,modified on 2009-02-12 at 20:48:48  size
2 read-write)
[copy] Copy.localFile /home/Compaq_Ejer/da / a to /home/Compaq_Ejer/db / .unison
.a.62dd79.unison.tmp
[abort] Checking line 1
[props] Setting permissions for /home/Compaq_Ejer/db/.unison.a.62dd79.unison.tmp
 to read-write (600/200)
(




compaq_e...@gitmoe ~
$ mkdir da

compaq_e...@gitmoe ~
$ mkdir db

compaq_e...@gitmoe ~
$ echo a>da/a

compaq_e...@gitmoe ~
$ chmod a+x da/a

compaq_e...@gitmoe ~
$ unison -debug verbose -perms -1 da db
[startup] Preferences:
ui = graphic
host =
server = false
prefsdocs = false
doc =
version = false
silent = false
dumbtty = true
testserver = false
rest = db
rest = da
showprev = false
selftest = false
confirmmerge = false
retry = 0
repeat =
contactquietly = false
key =
label =
expert = false
reusewindows = false
height = 20
auto = false
maxthreads = 20
prefer =
force =
sortnewfirst = false
sortbysize = false
keeptempfilesaftermerge = false
diff = diff -u CURRENT2 CURRENT1
fastcheck = default
ignorelocks = false
dumparchives = false
showarchive = false
rootsName =
backupdir =
maxbackups = 2
backups = false
backupsuffix =
backupprefix = .bak.$VERSION.
backuplocation = central
rsync = true
allHostsAreRunningWindows = false
someHostIsRunningWindows = false
confirmbigdeletes = true
batch = false
root = db
root = da
killserver = false
addversionno = false
servercmd =
sshargs =
rshargs =
rshcmd = rsh
sshcmd = ssh
xferbycopying = true
sshversion =
pretendwin = false
times = false
group = false
owner = false
numericids = false
perms = -1
rsrc-aux = false
rsrc = default
someHostIsInsensitive = false
ignorecase = default
timers = false
terse = false
logfile = /home/Compaq_Ejer/unison.log
log = true
debugtimes = false
debug = verbose
addprefsto =
Contacting server...
[globals] Checking path '' for expansions
Connected [//Gitmoe//home/Compaq_Ejer/da -> //Gitmoe//home/Compaq_Ejer/db]
[startup] Roots:
db
da
  i.e.
db
da
  i.e. (in canonical order)
   /home/Compaq_Ejer/da
   /home/Compaq_Ejer/db

[props] Setting permission mask to 200 (177 and 200)
[stasher] initBackupsLocal
[stasher] d = /
[stasher] New pattern being added to ignore preferences: Regex (.*/)?\.bak\.[0-9
]+\..*
[stasher] Prefix and suffix regexps for backup filenames have been updated
[stasher] initBackupsLocal
[stasher] d = /
[stasher] New pattern being added to ignore preferences: Regex (.*/)?\.bak\.[0-9
]+\..*
[stasher] Prefix and suffix regexps for backup filenames have been updated
Looking for changes
[update+] Archive name is //Gitmoe//home/Compaq_Ejer/da;//Gitmoe//home/Compaq_Ej
er/da, //Gitmoe//home/Compaq_Ejer/db;22; hashcode is daf265e5e54c31aba72697ea39b
e8157
[update+] Archive name is //Gitmoe//home/Compaq_Ejer/da;//Gitmoe//home/Compaq_Ej
er/da, //Gitmoe//home/Compaq_Ejer/db;22; hashcode is daf265e5e54c31aba72697ea39b
e8157
[update+] Archive name is //Gitmoe//home/Compaq_Ejer/da;//Gitmoe//home/Compaq_Ej
er/da, //Gitmoe//home/Compaq_Ejer/db;22; hashcode is daf265e5e54c31aba72697ea39b
e8157
<>Starting new major GC cycle
![update+] Archive name is //Gitmoe//home/Compaq_Ejer/da;//Gitmoe//home/Compaq_E
jer/da, //Gitmoe//home/Compaq_Ejer/db;22; hashcode is daf265e5e54c31aba72697ea39
be8157
[update+] Archive name is //Gitmoe//home/Compaq_Ejer/da;//Gitmoe//home/Compaq_Ej
er/da, //Gitmoe//home/Compaq_Ejer/db;22; hashcode is daf265e5e54c31aba72697ea39b
e8157
[update] Loading archive from /home/Compaq_Ejer/.unison/ardaf265
[update] Archive /home/Compaq_Ejer/.unison/ardaf265 not found
[update+] Archive name is //Gitmoe//home/Compaq_Ejer/db;//Gitmoe//home/Compaq_Ej
er/da, //Gitmoe//home/Compaq_Ejer/db;22; hashcode is 62dd79820bf9492c7b2a432ef9f
78e1e
[update+] Archive name is //Gitmoe//home/Compaq_Ejer/db;//Gitmoe//home/Compaq_Ej
er/da, //Gitmoe//home/Compaq_Ejer/db;22; hashcode is 62dd79820bf9492c7b2a432ef9f
78e1e
[update+] Archive name is //Gitmoe//home/Compaq_Ejer/db;//Gitmoe//home/Compaq_Ej
er/da, //Gitmoe//home/Compaq_Ejer/db;22; hashcode is 62dd79820bf9492c7b2a432ef9f
78e1e
[update+] Archive name is //Gitmoe//home/Compaq_Ejer/db;//Gitmoe//home/Compaq_Ej
er/da, //Gitmoe//home/Compaq_Ejer/db;22; hashcode is 62dd79820bf9492c7b2a432ef9f
78e1e
[u

Re: Can't get unison to syncroze permission bits

[Andrew Schulman]

Which version of Unison are you running?


--
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: Can't get unison to syncroze permission bits

[Andrew Schulman]

> Which version of Unison are you running?

Nevermind, I see it's 2.27.57.


--
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: CygWine 1.0 Beta -- an new cygwin package manager

[Yitzchak Scott-Thoennes]

I'd rather see the common code put into a library (and available in
both cygwin and mingw flavors).  Then it would be pretty easy to
have a Cygwin::Setup perl extension and command line tools using it.
(Substitute your other glue language of choice as desired.)

On Thu, February 12, 2009 10:17 am, Dave Korn wrote:
> I'm taking a quick browse through the code.  I see that you've based it
> on chunks of the core setup.exe code, somewhat refactored and
> restructured.  I wonder if we couldn't merge the two codebases, in such a
> way that there's one common 'setup engine' with a couple of alternative
> GUI front-ends; that might
> be a neat way to fix up all the missing features and make sure there is
> thoroughly consistent behaviour between the two different installers.



--
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: GCC 4.3.2 OpenMP Support in Cygwin

[Michael Craft]

I compiled it myself using the "--enable-libgomp" flag on the configure script.

On Wed, Feb 11, 2009 at 1:57 AM, Dave Korn
 wrote:
> Larry Hall (Cygwin) wrote:
>> Michael Craft wrote:
>>> I am trying to compile an OpenMP program in Cygwin using GCC 4.3.2
>>> installed from the repositories. This program compiles in linux with
>>> the exact same compiler fine.
>>>
>>> $ gcc-4 -std=gnu99 -fopenmp -o mvp-cygwin matrix-vector-bench.c
>>> matrix-vector-bench.c:11:18: error: omp.h: No such file or directory
>>>
>>> Can anyone help?
>>
>> Sorry, I know nothing about OpenMP but the above suggests to me that
>> the compiler can't find "omp.h".  Does it exist?
>
>  GOMP, the GNU OpenMP library implementation, is shipped with GCC series 4,
> but was not enabled in earlier builds of the Cygwin distro compiler.  It will
> be included in the upcoming gcc4-4.3.2-2 release, ETA within the next seven
> days.  There's a home page at:
>
> http://gcc.gnu.org/projects/gomp/
>
>cheers,
>  DaveK
>
> --
> 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/
>
>

--
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: CygWine 1.0 Beta -- an new cygwin package manager

[Brant Young]

Hi brother, thanks for all you reviews and suggestions.

I like yum and apt-get too.

CygWine still in somewhat early age, I will consider your proposals
seriously during the next release.

Regards,

Brant

On Fri, Feb 13, 2009 at 1:37 AM, Warren Young  wrote:
> Brant Young wrote:
>>
>> I have launched a opensource project -- CygWine ( a cygwin package
>> management utility, project homepage: http://cygwine.googlecode.com )
>
> My initial thought on seeing the name is that it was a port of Wine to
> Cygwin, which would be tres silly.
>
> We don't really need two different installers, so I hope you find a way to
> merge your efforts with those working on setup.exe.  The licenses are the
> same.  If that happens, then maybe your program just becomes setup.exe, and
> the naming issue goes away, too,
>
> On starting it here, I get an error message about being unable to load from
> /setup.bz2.  I then manually set a mirror, which did nothing until I
> restarted the app.  Your program shouldn't have to ask for either of these
> things: it can get them from the same place setup.exe does.  If it has
> neither, it should ask, like setup.exe does, before it presents the package
> list.
>
> When I clicked (Re)Install Cygwin, its first choice of directory to upgrade
> is my Cygwin 1.5 directory, not my 1.7 directory.  It's not clear to me if
> this means it just looks for 1.5 first, or if it really only supports 1.5.
>  I don't want to wreck anything, so I haven't used CygWine to install
> anything yet.
>
> Speaking of, one of the weaknesses of setup.exe is that it gets confused if
> you have Cygwin 1.7 installed in c:\cygwin (as I do) and then try to install
> 1.5 somewhere else.  It happens because the 1.5 version of setup.exe grabs
> the package list from c:\cygwin, not realizing that it's for a different
> version of Cygwin.  I don't know how much work you want to put into making
> your program cope with two versions of Cygwin, but you should take some care
> not to entangle them if they're both present.  How exactly you go about that
> depends on whether you want to support both versions at all -- maybe you
> intend to support only 1.7, given that 1.5's run is almost over.
>
> I like that it detects which Cygwin-using programs are running and names
> them for you, instead of making you guess which files conflict, as setup.exe
> does.  I also like that it's proactive, not waiting until it encounters a
> file copying error to complain.  Your program should also handle that
> copying error, but the proactive approach should make that code path
> difficult to hit.
>
> The only problem is, you're doing that check too early, before you know
> whether the advice in the dialog is actually correct.  It asked me before
> I'd even selected any packages to download.  There's no way it knows what I
> need to shut down so early.  It should wait until all the tarballs are down,
> then look into them to see what files will be replaced, and figure out
> whether any files currently loaded into memory will be replaced.  Unless
> you're replacing a running service, bash, or cygwin1.dll, changes are good
> that you can install while those things stay running.
>
> A long-standing wishlist item for setup.exe is something like you see in
> Linux distributions, where the installer abstracts away the full package
>  list, with its first screen showing a relatively small number of groups of
> mutually coherent and supporting sets of packages.  You can still get at the
> full package list, but the idea is that most people will just select those
> package sets that include the functionality they want.  This ends up
> installing more packages than is strictly required, but human time is more
> expensive than bandwidth in most cases.
>
> For instance, I'd like to be able to select the "Text Based Internet"
> category and get ssh, rsync, lynx, wget, and lftp.  When there are multiple
> packages in Cygwin providing a given function (e.g. lynx, elinks, and w3c),
> you should just pick one and call it your standard.
>
> I'd also like to see a command line interface to the program, and for
> CygWine to install itself into c:\cygwin\bin.  I'd like to be able to say
> "cygwine install rsync" from a bash prompt, and have it automatically go to
> the last mirror I selected through the GUI, grab the package and its
> dependencies, place them in the last place it downloaded packages[*], and
> install them.  If you do this, please copy the command line format of one of
> the tools that do this on other OSes.  I'd prefer yum, but apt-get or fink
> would be fine.  These three all have differences, despite being so similar
> in effective function.  This wheel has been reinvented enough times now.
>
> Combining these two, the way I'd most like it to work is this:
>
> 1. Start CygWine, it asks you where to install, what mirror to use, etc.,
> like setup.exe does
>
> 2. Then it gives you a list of maybe 20 groups of packages.  Checking off
> all of them doesn't

Re: CygWine 1.0 Beta -- an new cygwin package manager

[Brant Young]

> I'm taking a quick browse through the code.  I see that you've based it on 
> chunks of the core setup.exe code, somewhat refactored and restructured.

Yes, a lot of non-UI code were migrated from setup.exe.

> I wonder ... do you think that would be practical?

I think you made a wonderful proposal.

I'd like to see a common 'setup engine' separated from setup.exe, and
besides GUI front-ends, a console front-end is also necessary ( like
yum and apt-get in Linux, they are very convenient )

I suggest split current setup.exe to three components :

* setup engine dll (which expose native C API, maintains package
install/remove/upgrade, dependence, download cache, notification
callbacks etc.)

* setup console app ( just a front-end, process command line
options, main functions should implements in 'setup engine dll' )

* setup GUI app ( GUI front-end )

Regards,

Brant

On Fri, Feb 13, 2009 at 2:17 AM, Dave Korn
 wrote:
> Brant Young wrote:
>> Hi everyone,
>>
>> I have launched a opensource project -- CygWine ( a cygwin package
>> management utility, project homepage: http://cygwine.googlecode.com )
>>
>> CygWine 1.0 beta was just released, you can download the executable
>> and browse screenshots at http://cygwine.googlecode.com.
>>
>> Compared to cygwin official install tool -- setup.exe, CygWine is more
>> easy to use, has more intuitive UI.
>
>  I like the nice wx-based GUI, that's really pretty.
>
>> Currently, some of setup.exe features not supported by CygWine, I will
>> add more functions in the next release.
>>
>> I hope you will like it, suggestions and contributions are welcome.
>
>  I'm taking a quick browse through the code.  I see that you've based it on
> chunks of the core setup.exe code, somewhat refactored and restructured.  I
> wonder if we couldn't merge the two codebases, in such a way that there's one
> common 'setup engine' with a couple of alternative GUI front-ends; that might
> be a neat way to fix up all the missing features and make sure there is
> thoroughly consistent behaviour between the two different installers.  You
> know your own code better than I do - do you think that would be practical?
>
>cheers,
>  DaveK
>
>
> --
> 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/
>
>

--
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: CygWine 1.0 Beta -- an new cygwin package manager

[Brant Young]

> On Thu, Feb 12, 2009 at 12:37 PM, Warren Young wrote:
> I had that exact same thought.  If it can't be merged into the standard 
> setup.exe, I would at least recommend a different name.

Everyone hates the name  :-)

It seems I should change the name in the next major release.

Regards,

Brant

On Fri, Feb 13, 2009 at 3:07 AM, Mark J. Reed  wrote:
> On Thu, Feb 12, 2009 at 12:37 PM, Warren Young wrote:
>> Brant Young wrote:
>
> You two aren't related, are you? :)
>
>>> I have launched a opensource project -- CygWine ( a cygwin package
>>> management utility, project homepage: http://cygwine.googlecode.com )
>>
>> My initial thought on seeing the name is that it was a port of Wine to
>> Cygwin, which would be tres silly.
>
> I had that exact same thought.  If it can't be merged into the
> standard setup.exe, I would at least recommend a different name.
>
> --
> Mark J. Reed 
>
> --
> 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/
>
>

--
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: CygWine 1.0 Beta -- an new cygwin package manager

[Reini Urban]

2009/2/12 Yitzchak Scott-Thoennes:
> I'd rather see the common code put into a library (and available in
> both cygwin and mingw flavors).  Then it would be pretty easy to
> have a Cygwin::Setup perl extension and command line tools using it.
> (Substitute your other glue language of choice as desired.)

For my unfinished cmdline perl installer I've added the requirement to
have the library (Cygwin::Install) and cmdline tool into a single file.
cfg's unfinished cmdline installer in perl also uses a single file.
(search the list for the url)

I take patches.
http://code.google.com/p/cygwin-rurban/source/browse/trunk/contrib/cyginstall/cyginstall
-- 
Reini Urban
http://phpwiki.org/  http://murbreak.at/

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