Determine home directory during install

[Brian Mathis]

I've noticed that when I install cygwin fresh on a new machine, my
home directory seems to change location.  Sometimes it's in
C:/cygwin/home/[user], but on this machine for some reason its in
C:/Documents and Settings/[user].

How does the installer determine where to put it?  I have admin rights
and access to create directories.  The only difference with this
machine is that it's on a domain.  The other machines I use are
standalone (like at home).

Thanks.

--
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: Adding to a windows zip file without zip.exe

[Brian Mathis]

On 5/16/07, Chadwick <[EMAIL PROTECTED]> wrote:


Unfortunatly I cannot install any new packages on these boxes at this time,
thus using zip.exe is not an option.   I am open to the idea of extracting
the files from the current ZIP and then rezipping them with my new files,
but the final ZIP file created must be a standard windows ZIP file (IE
openable by winzip)


Can you use a .tar.gz file?  tar and gzip should both be on the
system, and the combination of the two is effectively a .zip file.
This is also something that winzip can open.

--
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: hacked package on server

[Brian Mathis]

On 7/16/07, Igor Peshansky <[EMAIL PROTECTED]> wrote:

Ugh, top-posting...  Reformatted.

On Mon, 16 Jul 2007, Brian Kelly wrote:

> -Original Message-
> >From: Christopher Faylor <[EMAIL PROTECTED]>
> >Sent: Jul 16, 2007 11:52 AM
> >To: [EMAIL PROTECTED]

.  Thanks.

> >Subject: Re: hacked package on server
> >
> >On Mon, Jul 16, 2007 at 10:30:52AM -0500, Louis Kruger wrote:
> >> I also have a complaint:  the dialog that notifies the user of the
> >> failed MD5 is not well designed.  The dialog asks "Do you want to
> >> skip the package?" and has a yes and no button.  I read it quickly
> >> and pressed no before thinking about it, the package went ahead and
> >> tried to install.  I think there should be a little more effort to
> >> restrain the user from performing a dangerous action such as
> >> installing a package with a wrong MD5.
> >
> >Good point.  The message should probably be
> >
> >Do you want to not skip the package (No/Yes)?
> >
> >cgf
>
> This would be "more" helpful:
>
> Do you want to not skip the package (No/Yes/Maybe)?
>
> The "Maybe" can then consult a random number routine to decide whether
> or not to do the operation.

Jeez, guys.  Haven't you learned ANYTHING in a UI design course?
The main purpose of the UI is to give the user a warm fuzzy feeling and to
overwhelm him with critical information to the point of being incapable of
making rash decisions like this.

Therefore, the message should read thus:

Do you not want to not skip the abovementioned package?

And the buttons should read "Yes", "No", and "I need more time to decide",
the last one being in the middle and more prominent.  It would also help
to have a fake countdown running somewhere in the window, with large black
digits.  Guess which button the user will go for?
Igor



Yes, everyone now has been quite hilarious on this part of the matter,
but I think it's time to get past the arrogance and, god forbid,
consider that a user's reported problem, oh my god, might actually be
a problem!

Any time there's a report of a user having a problem with an
interface, *especially* one that's _supposedly_ so easy and obvious,
why not address it?  Or why not AT LEAST take a thought and say to
yourself, "if something is supposed to be so simple and obvious, and
yet someone is having a problem with it, maybe *I* am making an
assumption about the simplicity of it?"

In this case, a user running an installer is in the frame of mind of
*installing* things, not *skipping* things.  So when they are asked a
question, they should be asked questions about *installing*, not
*skipping*, and the answers should be taken in that context.  "Yes"
should do the install, while "No" should not.  Switching the context
to "skipping" causes the type of confusion that is going on here.

If it's so minor, be glad that someone actually reported it and now
you have the chance to make the project better.  Most people would
just get confused, stop, reread, hopefully make the right choice, and
move on, but retain the impression that it's hard to use and
confusing.  This may affect their decision to use it in the future, or
their decision to recommend it to others, etc...

Isn't that a much more intelligent response than, "Wow, our users are
such idiots!  I'm so much better than them because I'm a such a smart
computer guy!"


PS. This same concept applies to the recent discussion about
documentation, and all the previous ones as well.  If something is not
obvious enough for people to find it, then it should be made more
obvious (or at least some consideration given to the request).  One
does not have control over the ways people approach a problem.  This
project does have control over how/where documentation is located, and
the ease of finding it.  Focus on what you have control over.

--
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: How to run bash shell script in cygwin?

[Brian Mathis]

On 7/19/07, Larry Hall (Cygwin) <[EMAIL PROTECTED]> wrote:

myuser01 wrote:
> I have a script called "batchjob" that looks like this:
> #!/bin/bash
> echo 'I was here'
>
> -rwxr-xr-x  1 c10066 mkpasswd   48 Jul 19 09:30 batchjob
>
> But when I try to execute it from the cygwin shell I get this:
> $ batchjob
> bash: batchjob: command not found
>
> How do i execute a bash shell script from within cygwin?

This is not a Cygwin problem.  It's a usage issue.  You'd see
the same problem on other platforms.  Try:

./batchjob

--
Larry Hall  http://www.rfk.com


... and the reason for this is because the current directory, called
"." (dot), is not normally in the PATH environment variable.  This
variable is used to find programs that you are trying to run.  Since
"." is not in that list, it will not find the script.

Adding the "./" in front of the command name tells the shell to "look
in this directory (.) for the command"

You can read more about this by doing a google search like:
   http://www.google.com/search?q=path+environment+variable

--
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: hacked package on server

[Brian Mathis]

On 7/30/07, Steve Holden <[EMAIL PROTECTED]> wrote:
> Louis Kruger wrote:
> [...]
> >
> > I also have a complaint:  the dialog that notifies the user of the
> > failed MD5 is not well designed.  The dialog asks "Do you want to skip
> > the package?" and has a yes and no button.  I read it quickly and
> > pressed no before thinking about it, the package went ahead and tried to
> > install.  I think there should be a little more effort to restrain the
> > user from performing a dangerous action such as installing a package
> > with a wrong MD5.
> >
> What, you mean like a dialog that says "Should I assume you are an idiot
> and ignore your last request because you made a selection without
> thinking about it"? ;-)
>
> I swear that if you put up a dialog box saying "Drop a nuclear weapon on
> your home? Yes/No" half the world would click "Yes", then complain when
> their homes were destroyed.
>
> regards
>   Steve
> --
> Steve Holden+1 571 484 6266   +1 800 494 3119


Next time you feel the need to resurrect a week-old thread, and feel
the need to do it both rudely and not contributing anything of
substance, please follow these steps:
1. Write out your reply
2. Wait 5 minutes
3. Press the discard or cancel button.

so you can get it out of your system but spare the rest of the world
your inappropriate dribblings.

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

[Brian Mathis]

On 8/24/07, telus321 <[EMAIL PROTECTED]> wrote:
>
> guys, i am relatively a newbi when it comes linux bsd (cygnet) because i am
> windows user, i am trying to learn the linux platform/system, it comes to my
> attention the cygnet program i download does not have sudo command how can i
> have a complete installation which would allow to practice and learn the
> linux system.  Any input would help
>
> i am running on windows xp sp2

It's very good you have decided to try to learn something new.  Some
of the statements you made indicate that maybe you have a different
conception about what cygwin is used for.  Cygwin, while a very good
product for use on Windows, is not the same as Linux.  Using cygwin,
you will be able to get an understanding of how a linux-like system
works, and you should be able to get comfortable with the environment.
 However, it also has many differences from Linux, so many of the
things you might be looking for on a typical Linux system are not
available for cygwin.

For your specific questions, other's have already answered that should
help you in that regard.

--
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: Whither /dev/null ?

[Brian Mathis]

On 9/14/07, Lewis Hyatt <[EMAIL PROTECTED]> wrote:
> > I'm wondering what is the best way to deal with this? I'd like the
> > scripts to work straight out of the box and not have to make the users
> > create their own /dev and creating it for them would be tedious because
> > every script would have to check for this...
> >
> > Any advice?
> > Puzzled about nothing.
> > J
> >
> >
>
> Did you try it without doing mkdir /dev first? It should still work fine.
>
> [EMAIL PROTECTED] ~
> $ ls -l /dev
> ls: cannot access /dev: No such file or directory
>
> [EMAIL PROTECTED] ~
> $ ls -l /dev/null
> crw-rw-rw- 1 Lewis None 1, 3 Sep 14 11:12 /dev/null
>
> -Lewis
>

Maybe its been gone over before, but I question the wisdom of "hiding"
a directory like that.  It seems counterintuitive, and obviously
causes confusion for people.

Does creating a /dev directory (in the default install) cause a big problem?

--
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: Passing arguments to rxvt when it is used as an argument for chere

[Brian Mathis]

On 9/19/07, Richard Toy <[EMAIL PROTECTED]> wrote:
> Hi
>
> I don't tend to run an xserver so rxvt runs in native mode when
> invoked via chere.
>
> All was working ok but then an issue described here
> http://cygwin.com/ml/cygwin/2007-09/msg00359.html occurred so I needed
> some was to make the chere invoked rxvt appear with the correct font.
>
> I solved it with a bit of sed: -
>
> $ cat chere.sh
> chere -ipcf2 -t rxvt -s bash | sed 's! -e /bin! -fn \\"Lucida\
> Console-bold-12\\" -rv -ls -sb -sr -tcw -sl 3000 -e /bin!' >
> /tmp/$$.sh
> chmod 755 /tmp/$$.sh
> /tmp/$$.sh
> rm /tmp/$$.sh
>
> Regards
> Richard
>

In native mode, rxvt still uses the .Xdefaults file to read settings.
Here's what I'm using right now with it:

rxvt*foreground: gray
rxvt*background: black
rxvt*geometry: 132x50
rxvt*saveLines: 1000
rxvt*scrollBar: true
rxvt*scrollBar_right: true
rxvt*loginShell: true
rxvt*font: DejaVu Sans Mono-13

I'm sure sed is fun, but there's already a more elegant solution to
your problem.

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: strange behavior with perl v 5.8.8

[Brian Mathis]

On 9/27/07, Andrew Louie <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I've run into a strange adding problem with perl:
>
> when incrementing by 0.1 i get a strange behavior where at some
> arbitrary  number, it will append 0.99 to the end of the
> number.
>

There's an excellent explanation of this (just posted today about the
recently discovered Excel 2007 bug) here:
http://www.joelonsoftware.com/items/2007/09/26b.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: How to remotely log in and execute a program

[Brian Mathis]

On 10/13/07, Gary Johnson <[EMAIL PROTECTED]> wrote:
> On 2007-10-13, ppmoore wrote:
> > Hello again,
> >
> > Just to say that I found a partial solution, by copying the ssh login keys
> > generated on Cygwin on the Windows box to the .ssh directory on the remote
> > Linux box, and then executing from a local Cygwin xterm:
> >   DISPLAY=localhost:0.0 ssh -Y -C -q [EMAIL PROTECTED] "command"
> >
> > But is there a way to do it by running a Cygwin script on the Windows box?
>
> IIUUC, yes, just install the ssh server on your Cygwin/Windows box.
> The instructions are here:
>
>/usr/share/doc/Cygwin/openssh.README
>
> Regards,
> Gary
>

There's not need for an SSH server on the Windows box.  You only need
the client, as the login is going from Windows to Linux.

To execute a script instead of xterm, just run the script instead! :)
In your command above, forget the "DISPLAY" stuff and put whatever the
name of the command you want to run inside "command".  In most cases,
a simple "ssh [EMAIL PROTECTED] command" would suffice.  Once you have the
ssh keys set up, you don't even need a password.

Once that is done and working, if you want to run it automatically,
look into "cron".

--
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: Best AVS to use with cygwin

[Brian Mathis]

On 10/15/07, Olivier Langlois <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I am currently using Kaspersky AVS but I am looking for a replacement because 
> using it with Cygwin brings my system unstable whenever a bunch of child 
> processes are spawn (ie: find . -name '*.h' -exec grep -l pattern {} \;'. 
> Someone has even put the blame on Cygwin on their forum:
[...]
> Olivier Langlois


While not exactly an answer to your question, generally using "find"
with -exec is horribly inefficient.  In many cases, you can get the
same result by using:
find -name '*.h' | xargs grep -l pattern
Your version spawns a new grep process for every single file, while
using xargs only spawns a new process when the max argument length has
been reached.  If the problem comes from kaspersky because of the
process creation overhead, that would help you out a LOT.  You'll
probably also notice that your greps go much faster.

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

[Brian Mathis]

The most likely answer you're going to get is to switch to using ssh.
There's certainly a lot more people using that these days, so any bugs
or problems with it will be ironed out very quickly.


On 10/16/07, thefinn <[EMAIL PROTECTED]> wrote:
> I've noticed rsh doesn't seem to work on cygwin. It gives the following
> error:
> $ rsh -l thefinn 10.0.0.1 ls
> 5 [main] rsh 12 C:\cygwin\bin\rsh.exe: *** fatal error - couldn't
> dynamically determine load address for 'rcmd' (handle 0x73A8), Win32
> error 127
>
> After much testing I get the same basic error any time a normal rsh
> command should be run.
>
> I've looked around (google) and while there are some mentions of the
> same kind of thing, there's no real fix been posted anywhere I can see.
>
> Can someone tell me a good fix for this or point me in the right
> direction of one?
>
> Thanks
> TF.
>
>
> --
> 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: running ssh from windows desktop

[Brian Mathis]

You might want to try using -f.  You can read about it in the man page
(man ssh).


On 10/16/07, thefinn <[EMAIL PROTECTED]> wrote:
> Ok, this is a rather frivolous question, but just something I want to
> get right so it doesn't become an itch I can't scratch ;)
>
> When I access ssh from windows dos mode, I don't seem to be able to
> background the process and thus make the windows dos box go away after I
> double-click a program to open off a remote unix box.
>
> Anyone know how to make the dos box go away? :)
>
> Thanks
> TF.
> (yes I moved on from my previous rsh question)

--
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: copying a million tiny files?

[Brian Mathis]

On 10/31/07, sam reckoner <[EMAIL PROTECTED]> wrote:
> I'm not exaggerating. I have over one million small files that like to
> move between disks. The problem is that even getting a directory
> listing takes forever.
>
> Is there a best practice for this?
>
> I don't really need the directory listing, I just need to move all the
> files. I have been using rsync, but that takes a very long time to
> generate the list of files to be moved.
>
> Any alternatives?
> Thanks in advance.


Try using tar or zip to make 1 file of the whole folder, then transfer
that one file.

--
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: Wish Setup would accept my Perl

[Brian Mathis]

On 11/5/07, Michael Kairys <[EMAIL PROTECTED]> wrote:
> I've been using ActiveState Perl and Cygwin together for years and have only
> one complaint: Setup keeps hassling me about dependencies and I have to make
> sure always to uncheck Perl in the setu list (and again in the dependency
> check) or I end up with two Perl installations, which I don't want.
>
> I wish Setup could recognize that I already have a Perl installation...
>

The answer is "Don't do that".  Perl on cygwin and ActiveState Perl
are completely different things.  You've been using them together for
years [without problems], [except for this one big problem].

ActiveState Perl is a Windows app and should only be accessed through
Windows, such as the cmd.exe window or by using the .pl file
extension.  If you think the cmd.exe window sucks, try console2 on
sourceforge.  It's just lipstick on a pig, but at least it looks
better.

If you want to interoperate with other utilities that are provided by
cygwin, use the cygwin perl and not ActiveState.

Having both on your machine should work just fine, as long as you
don't try to share anything between them.  Treat them as completely
different things (which they are).

--
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: Wish Setup would accept my Perl

[Brian Mathis]

On 11/6/07, Andrew DeFaria <[EMAIL PROTECTED]> wrote:
>
> Would you similarly complain that you already have del and dir and not
> want rm and ls?
>
> Personally I dislike ActiveState Perl. Things like setsid just don't
> work and signal handling is not reliable (that may be better). Plus
> things written for ActiveState sometimes don't port easily to
> Linux/Unix. This is not the case with Cygwin's Perl.
> --
> Andrew DeFaria 
>

I must say with respect that if there are problems porting from
Activestate to linux/unix, that's a problem with the programmer who
wrote the code, not Perl.  There's no reason that code that's general
in nature would not be portable.  Of course, anything that uses
specific Windows services could not be ported.

ActiveState Perl works very nicely (and the alternative is what,
vbscript?) on Windows.  I have a feeling the last time you used it was
a long time ago, because signals, threading, ans everything else works
quite well -- but opinions for or against are really off topic from
the OP.

--
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: Wish Setup would accept my Perl

[Brian Mathis]

On Nov 7, 2007 10:31 AM, Andrew DeFaria <[EMAIL PROTECTED]> wrote:
> Brian Mathis wrote:
> > ActiveState Perl works very nicely (and the alternative is what,
> > vbscript?) on Windows.
> No the alternative is Cygwin's Perl on Windows, of course. Oh, and BTW,
> how much $$$ does ActiveState Perl cost? And how much was Cygwin's again?
>

It costs, nothing. zero. zilch. nada.  free.

I guess we both need to get our facts straight.

--
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: Wish Setup would accept my Perl

[Brian Mathis]

On Nov 7, 2007 10:44 AM, Andrew DeFaria <[EMAIL PROTECTED]> wrote:
> DePriest, Jason R. wrote:
> > I once, like you, wondered why I couldn't just have one installation
> > of Perl or Python that works in either environment. Since I write
> > scripts, not code,
>
> An aside? How is a Perl script not Perl code?!? Just wondering...
>
> > I assumed it was because it was just too hard to do and began to use
> > each program in its appropriate place.
>
> Hmmm... I'm curious. As you said you have both AS Perl and Cygwin's
> Perl. Now you say use each one where it is appropriate. I can't think of
> a reason why using one or the other is more appropriate than the other.
> As you state below regarding PPM, AS Perl is obviously Windows centric
> and Cygwin's Perl is admittedly Posix centric. Being as I don't see many
> Unix/Linux Perls with a Window's centric viewpoint I would think that
> sticking with Posix through and through (including CPAN rather than the
> uniquely AS PPM) would provide the best shot at being the most portable
> out of the gate!

How about if you are writing a Windows application?  What if you need
to manipulate the Registry or access Win32::OLE objects?  You
certainly need AS Perl for that.  It's not hard to imagine why you'd
need a Windows-centric version.

> Granted the programmer also needs be concerned about what he's about to
> do and whether or not that will be portable to "the other side". All too
> often the lazy programmer cops out and says "Well this'll never be run
> on Unix/Linux anyway. It's not a requirement", etc. and wham you have
> platform dependent code being made. Indeed search for a Unix/Linux Perl
> that will provide a Win32 backend or other Windows only concepts. You
> probably will not find one.
>
> However if the programmer bears in mind portability from the start then
> the chances are high that the code will port with little effort. IOW the
> real common denominator here is Posix, NOT Win32! And I have had many
> years of direct experience that tells me that this indeed is the case.
>
> > PS - I use PPM to manage perl modules for ActiveState Perl and cpan to
> > manage modules for cygwin perl. PPM is super-Windows-centric.
> --
> Andrew DeFaria 


Portability is not the be-all, end-all purpose of an application, and
eschewing it is not necessarily laziness.  It's actually pretty low on
the list of priorities.  Normally "getting the job done" is higher on
the list.  For most people, the goal of scripting is to accomplish a
task, like data processing or automation.  Each of those goals is
almost guaranteed to interact with some other proprietary part of the
system that is also not portable.  That's the difference between
coding an app and scripting.  Scripting is more often the glue between
other parts.

That's not to say that you can't also write a portable, full-blown
application in Perl, but that's coming from a different perspective.
Maybe that's where the differences lay here, in the perspective.

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

[Brian Mathis]

On Nov 19, 2007 11:01 AM, 123cu <[EMAIL PROTECTED]> wrote:
>
> First, I am a newbee to Cygwin so please excuse my lack of knowledge.
>
> I have a text file (aaa.txt) which contains a simple grep command. When I
> start Cygwin.bat, I want this file to be started (executed) as part of
> invoking the cygwin.bat file. I don't know how to do it. Any help will be
> appreciated.
>
> cygwin.bat file
> @echo on
>
> C:
> chdir C:\cygwin\bin
> set HOME=\cygwin
> bash --login -i

cygwin.bat is typically used to start the cygwin environment, usually
by starting a bash shell.  The bash shell then runs some "startup"
scripts, like .bashrc and .bash_profile.  Those files are where you
would normally put anything that you want to run every time you start
a shell.

Based on your description, it sounds like you may be doing something
that might not fit with the idea of how cygwin works.  If you can
explain in more detail what you are trying to accomplish, we may be
able to find a better solution, or help you to integrate it better.

--
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: Vim: segmentation fault

[Brian Mathis]

On Nov 20, 2007 2:16 PM, Matt Wozniski <[EMAIL PROTECTED]> wrote:
> On Nov 20, 2007 2:02 PM, Aldi Kraja wrote:
> > Hi,
> > Opening a file 1.5 GB cygwin Vim reports segmentation fault.
> > Vim: Caught deadly signal SEGV.
> >
> > Is there any way that one can expand the setting of Vim?
> >
> > I need to change the header of the file to some extent, but I do not
> > think that emacs will do it. Less is a pager. Any other idea how to edit
> > a file this large?
>
> If it's only a header you need to edit, you do it the usual unix way...
> for a 15000 line file, where the header is in the first 100 lines:
>
> $ head -100 BIGFILE > filehead
> $ tail -14900 BIGFILE > filetail
> $ vim filehead
> # modify...
> $ cat filehead filetail > BIGFILE
> $ rm filehead filetail
>
> And, there's no reason that should crash vim.  Do you have the
> 1.5 GB of memory that you'd need to open that file?
>
> ~Matt

You could also 'split' the file into more manageable chunks if it's
not at the head, then 'cat' it back together when done.

--
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: [Fwd: sshd display]

[Brian Mathis]

On Nov 21, 2007 3:58 PM, Robert Kiesling <[EMAIL PROTECTED]> wrote:
> [ Charset UTF-8 unsupported, converting... ]
> > On 11/21/2007, Uber Zooka wrote:
> > > Because he's trying to go from a linux machine to a machine running
> > > Cygwin
> >
> > I think you're missing my point.  If there's an answer to this question
> > in the Linux->Linux case (or on any other UNIXy platforms that don't include
> > Cygwin) then that same approach should work on Cygwin.  If it doesn't, then
> > that's a Cygwin issue and on-topic.  If it does work, then that's the answer
> > to the question and Cygwin has no bearing, thus the original inquiry is
> > off-topic.
> >
> > > He's trying to run an app on a windows machine and wants to know
> > > how to make the console on the windows machine stay there.
> >
> > Since 'ssh' is a client program on the client machine that's logging in
> > remotely to the server machine, there's nothing visible on the server.
> > Output goes to the client terminal.  There's no visible mechanism on the
> > server for this output to "stay" on.  There may be other ways to achieve
> > something that would be a reasonable alternative in this case but that
> > would presuppose that we understand what actual problem the OP was trying
> > to solve.  That's why I suggested he provide more info if he has a Cygwin-
> > specific issue.
>
> An off-topic answer would be xon(1).


You're both missing the point.  Throwing in your two cents without
providing any help is just as bad, if not worse, than someone who's
asking a *possibly* off-topic question, which, since this involves
cygwin, is not likely.  If such a marginally off-topic message on this
incredibly high volume mailing list bothers you, there's a "delete"
button in your email client.


To help the OP:
An ssh connection typically does not create any sort of console window
on the system that is being connected to (this is the same on Linux or
Windows/Cygwin).  Depending on your needs, you may be able to emulate
something like this using 'screen'.

You can open screen in the local terminal (rxvt is recommended), and
start a screen session inside of it.  Then when you ssh in, you can
attach to that screen session using "screen -x" and both parties will
be able to see what's going on.  There's a little more to it than
that, and will probably need some experimentation, but that's
something that can get you started.

--
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: [Fwd: sshd display]

[Brian Mathis]

On Nov 26, 2007 10:56 AM, Roger Wells <[EMAIL PROTECTED]> wrote:
> Please forgive my silence and I really do appreciate your attention to my 
> problem.
> I originally posted my question on the cygwin-apps list and at Corinna's 
> suggestion I
> posted it on this list without realizing that I was not subscribed.  I only 
> now have
> seen your responses as I searched the archives.  I can now provide a specific 
> example
> of what I am doing.
>
> On one cygwin installation:
> uname -a => CYGWIN_NT-5.1 dac1 1.5.21(0.156/4/2) 2006-07-30 14:21 i686 Cygwin
>
> the following command on the linux client:
> ssh wellsr start foo.exe
> results in a windows console popping up with the application (foo) running in 
> it.
> control immediately returns to the linux console.
>
> The key to this working is the following script ("start")
> that runs on the cygwin machine:
>
> #!/usr/bin/bash
> #
> # There must be no spaces in the title field of the start command
> # Otherwise, this seems to work, but I don't know how!
> #
> #
> export XAPPLRESDIR="C:\iss60\app-def"
> cmd /c start /I \ $1\  $2 $3 $4 $5 $6
>
> (obviously the last line is the operative one)
>
> on another cygwin installation:
> uname => CYGWIN_NT-5.1 wellsr 1.5.24(0.156/4/2) 2007-01-31 10:57 i686 Cygwin
>
> the same sequence launches the application and returns control to the linux
> console but in this case there is no console window on the cygwin side.  The
> application appears on the task list but no window exists.
>

When the sshd service is installed on the cygwin machine, you must
make sure that "Interact with desktop" has been enabled.  I suspect it
was enabled on the one machine, but not the other.  On the system that
is not working, reinstall the cygwin sshd service, and enable that
option.

--
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: Wish Setup would accept my Perl

[Brian Mathis]

On Dec 6, 2007 2:23 PM, Michael Kairys <[EMAIL PROTECTED]> wrote:
> William Sutton  trilug.org> writes:
> >
> > Having done a bit of this myself, I'm interested into enquiring further
> > into your difficulties.  Except for win32-specific modules, perl code
> > *should* *just work* for either cygwin perl of for ActiveState.  Last I
> > checked (and it's been about a year), you should be able to get the
> > win32-specific modules for cygwin as well, so I'm not sure why you can't
> > just invoke the script in your bash shell and have it run.
>
> Thank you for your encouraging note. I would prefer to maintain only one Perl
> installation and would in fact be perfectly happy to dump AS in favor of
> Cygwin if I could do so without major pain. You have encouraged me to at least
> give it a try.
>

The major pain will come with file path names.  If you are using
Windows paths in your scripts, those will not work in cygwin.  Really
the issue here is that you have become used to doing something that is
bad, which is running windows programs in a cygwin shell.  Because
Perl exists in both places, you have intertwined yourself into a
complex situation of not knowing which scripts run in what
environment.  I don't think there's an easy fix for this.

I actually would recommend the opposite... since AS Perl is the native
Windows version, I recommend you use that instead of the cygwin
version for anything that interacts in a "windows way" (registry,
files, services, etc...).  For stuff that works only in cygwin, use
the cygwin perl.

Since you're at home on the command line, you might want to check out
"console" http://sourceforge.net/projects/console/ which offers a
marginal improvement over the windows command shell.

--
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/regtool on 64bit windows (vista)

[Brian Mathis]

I'm curious what the plans or status is of compatibility efforts
between cygwin (32bit) and 64bit Windows (Vista).  In particular, I'm
interested in getting 'chere' working on 64bit Vista.  I notice chere
uses 'regtool', which in turn is a 32bit application.  Because it's
32bit, when it tries to access the registry is is getting virtualized
into the 32bit space, and as such does not allow chere to interact
with the 64bit explorer.

I see in the regtool source that there are some options for this (-w
and -W), but I don't see those options available in the regtool
release on my system (version 1.8), which, afaik, is the latest
release.  Are there plans to release this version of regtool?  The
last update to it in CVS was 13 months ago.  -w and -W are not
documented, and regtool does not seem to recognize the options.

--
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: RXVT and Bitstream Vera Sans Mono

[Brian Mathis]

On Dec 6, 2007 4:04 PM, Jeff <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I use RXVT because it makes Cygwin accessible to me. Its color and font
> support gives me a console window I can *see*, as opposed to the native
> Windows console that BASH runs in by default, which I cannot see. Part
> of my strategy to increase visibility is to specify a bold font for
> -fn/font: and crank up the point size just as large as I can make it
> and still have an 80x25 console fit on my screen.
>
> I probably don't have to tell anyone who uses RXVT that Windows XP
> ships with only two usable monospaced fonts: Lucida Console, and
> Courier New; I probably also don't have to mention how well a
> proportional font (doesn't) work with RXVT. I've been getting by with
> Lucida Console-bold, but lately even that has become a little difficult
> for me to see. So, I decided to see if I could find a more visible
> font.
>
> I found this useful page at http://www.lowing.org/fonts/ which lists
> several monospaced fonts for coders/programmers, with Bitstream Vera
> Sans Mono ranked as the best of them. The page provides links, too--
> the Bitstream fonts are available at http://www.gnome.org/fonts/ as
> advertised. I then noticed that this font is mentioned in the RXVT
> README text, and saw it mentioned in a recent thread on this list as
> being the default font in the current Cygwin RXVT.
>
> After trying a few point sizes, I quickly determined that the largest I
> could use and still have an 80x25 console fit on the screen was 24.
> However, I got some really strange display anomalies at that point size
> (and not at any other within the range of 22-28)-- and they occur in
> all variations of the font: normal, bold, and oblique (Italic). I had
> characters overlapping and obscuring each other. In joe, the text
> editor I use, a line of text extended farther to the right than where
> the cursor would land when given a "goto end of line" command. Any
> attempt to edit under those circumstances caused characters to
> disappear from the screen; it was necessary to move the cursor and
> redraw the screen to see what I had there.
>
> Setting the size to 23 works just great and is better than using Lucida
> Console (or the other fonts mentioned on lowing.org, for that matter),
> but 24 is significantly larger and would be easier on my eyes. I
> thought it would be better to ask here first before contacting
> Bitstream; the font seems to work just fine at that point size in MS
> Word.
>
> I'm running the latest Cygwin RXVT (2.7.10, or 20050409-4) in native
> mode (I have no use for X11, since I run only console mode apps in
> Cygwin) along with the latest cygwin1.dll release on Win XP Pro SP2
> with all the latest updates. I have tried what I am describing and have
> had the same results on three different computors, each running at a
> different screen resolution and DPI setting-- the notebook on which I
> am typing this maxes out (and is set at) 1024x768, and is set for
> Normal size (96 DPI). BASH is my shell, and my .Xdefaults file is as
> follows:
>
> *background: #8A
> *foreground: #DADA00
> *colorBD: #D0D0D0
> *colorUL: #8CD70F
> *font: "Bitstream Vera Sans Mono Bold-23"
> *visualBell: True
> *loginShell: True
> *termName: rxvt-cygwin-native
> *saveLines: 300
> *geometry: 80x25
>
> It makes no difference whether I just invoke RXVT and let it call BASH
> by default (assuming that RXVT does not read the $SHELL environment
> variable, which points to BASH), or make it explicit with 'rxvt.exe -e
> bash -li'.
>
> I hope someone (Charles?) can duplicate my results, and then figure out
> what's causing it. Please let me know if any other information is
> needed to troubleshoot this. My eyes will thank you, and so will I.
>
> Jeff
>

The Bitstream Vera fonts were released a long time ago, and AFAIK have
been mostly abandoned by Bitstream (at least you won't get any support
from them).  The successor to them which has had many updates since
their release is the DejaVu fonts.  I know they have had many releases
and fixed a lot of bugs, so that might resolve this problem you are
seeing.  You can download them here:
http://dejavu.sourceforge.net/wiki/index.php/Download

--
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: Wish Setup would accept my Perl

[Brian Mathis]

On Dec 7, 2007 4:53 PM, Michael Kairys <[EMAIL PROTECTED]> wrote:
> Well, I gave it a try, and I can see that ain't gonna happen :)
>
> I reran setup and let it install perl and whatever else it wanted to (so I now
> have ruby and phython as well); then I began running scripts under both perls.
> I quickly realized AS perl exec's cmd.exe whilst Cygwin perl exec's sh, so
> much of my system and backquote constructs broke. I also noticed that ENV
> {PATH} and ENV{HOME} return Windows or Unix syntax paths, depending. The
> Cygwin perl builtins like chdir and chmod were quite happy with Windows paths,
> as I would expect.
>
> As an aside, there seems to be something broken in my installation re. Tk (or
> perhaps I'm missing something). If I run a script containing (only) "use Tk" I
> get: Can't load '/usr/lib/perl5/vendor_perl/5.8/cygwin/auto/Tk/Tk.dll' for
> module Tk: No such file or directory
> at /usr/lib/perl5/5.8/cygwin/DynaLoader.pm line 230.
>
> ... however /usr/lib/perl5/vendor_perl/5.8/cygwin/auto/Tk/Tk.dll is in fact
> there.
>
> So given that I "should" keep Cygwin perl around (meaning that someday I'm
> likely to regret it if I don't :) and that I'm going to keep AS perl as well,
> I need to find the best way for them to coexist. I think the suggestion made
> elsewhere in this thread (sorry, I forget who made it) that I forego "perl -S"
> in favor of shebang is good; I find that #!/local/perl/bin/perl finds my AS
> perl (which is in D:\Local\Perl, and D:\Local is mounted on /local). ASsuming
> Cygwin correctly shebangs any scripts it needs to use, I can remove AS perl
> from my Cygwin path (as set in .bashrc) but leave it in my Windows path (as
> set via the Control Panel) and as I understand it to date, everything should
> work. If I don't in fact understand it (not unlikely :) please advise.
>
> But given my "programmer's OCD" I will probably keep poking at why my AS
> scripts don't run on Cygwin perl, so any advice about setting it up, why Tk
> doesn't work, etc. would be appreciated (as are all your comments).


Using the shebang (#!) line will only be useful for scripts run in
cygwin.  Windows will need an association of the .pl extension to the
AS Perl binary in order to run.  The shebang line will do nothing for
scripts run by double-clicking on them or those run from the DOS
command line.

I think the biggest problem you're having is conceptual.  It's easy to
view a bash prompt as just a better DOS prompt that gives you unix
commands in addition to windows command line commands.  THAT is what
is creating the problem here, because cygwin is NOT just a cooler DOS
prompt.  It presents the environment to a running program very
differently.  It just so happens that most Windows/DOS commands are
too stupid to notice the difference.

Operating under that thought process, it's very easy to create a
mishmash of commands that rely on each other, crossing the boundaries
back and forth between cygwin and windows.  Since perl exists in
both... well, you already can see the problems that can cause.

The solution is to start breaking the habit of using a bash prompt for
windows commands.  Open a DOS command window and use that (as much as
it hurts).  Any perl run from that command window will use AS perl.
Even "better", don't run AS perl scripts from a prompt at all,
double-click on them and start them like any other windows app.  Do
not try to use AS perl from a bash prompt.  Anything run from a bash
prompt should use cygwin perl.

You should not have AS perl in your cygwin path -- cygwin should not
know about it at all.  I also think this is a bad idea:
"#!/local/perl/bin/perl finds my AS perl (which is in D:\Local\Perl,
and D:\Local is mounted on /local)"

As a Programmer, listen to this System Administrator (this one time, I
know it's hard ;-)), this isn't a software issue, it's a management /
usage pattern problem.

--
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: Stop turning CPAN modules into Cygwin packages

[Brian Mathis]

On Dec 12, 2007 10:04 AM, Jerry D. Hedden <[EMAIL PROTECTED]> wrote:
> Eric Blake wrote:
> > A new package, perl-Error-0.17010-1, is now available for use.
> >
> > NEWS:
> > =
> > This is a new package, providing the Error module for perl.
>
> What is the point of making this a Cygwin package?  There
> are no Cygwin specific changes, and it it can be installed
> directly from CPAN using:
> cpan -i Error
>
> This seems to be becoming a trend.  So far there are 8 CPAN
> modules that have been made into Cygwin packages.  Only 3
> have Cygwin specific changes that would justify them being
> made into package:
> perl-Locale-gettext
> perl-Tk
> perl-libwin32
>
> The other 5 have no Cygwin specific changes:
> perl-Error
> perl-ExtUtils-Depends
> perl-ExtUtils-PkgConfig
> perl-Module-Build
> perl-Win32-GUI
>
> This seems like a bad practice.  It adds a maintenance
> burden on the Cygwin system (because the packages will need
> to be updated when the modules are updated), they needlessly
> take up storage on the Cygwin servers, and turning them into
> Cygwin packages adds no value over obtaining the modules
> directly from CPAN.
>
> Just because you can turn a CPAN module into a Cygwin
> package doesn't mean that you should unless there are Cygwin
> specific changes that need to be made.  Even then, a better
> approach is to send the appropriate patches to the module's
> maintainer so that they can be integrated into the code and
> uploaded to CPAN.
>

Because when you package something using a distro's packaging system,
you can start to have other programs that depend on it install them
automatically using the package system.  Also, installing from CPAN,
while very easy to do, does not keep track or even know about a
distro's package management system.  So if you wanted to remove it
later, it is not easy to do, and you could easily run into problems
where you have installed one version from CPAN, then another package
requires that module, but because you installed via CPAN it doesn't
know that, and will then install an older version, overwriting your
CPAN-installed version.

--
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: Stop turning CPAN modules into Cygwin packages

[Brian Mathis]

On Dec 12, 2007 11:43 AM, Archie Warnock <[EMAIL PROTECTED]> wrote:
> Igor Peshansky wrote:
> > BTW, this problem must have been encountered (and, hopefully, solved) by
> > other distros.  How does the Debian git package handle this?  I seem to
> > recall that at least Red Hat Linux at some point had packages for some
> > CPAN modules...
>
> I don't know how they solve dependencies, or if it has anything to do with
> dependencies, but I can tell you that Fedora Core 8 (and earlier versions) 
> have
> a _lot_ of CPAN modules packaged as RPMs.
>
> I, too, prefer to get my modules directly from CPAN but I do run into 
> occasional
> compilation problems from time to time.  At those times, it's really handy to
> have the packages available.  But, as already mentioned, those should be fixes
> that are passed upstream to the CPAN module owner/maintainer anyway.
>
> --
> Archie
>

Fedora (and the other distros) do this because they understand that
for a really good working distro, you need to have everything on the
system managed by the system's package manager.  It doesn't really
matter that installing from CPAN is easy, because it always screws up
the dependencies on the system.

The same goes for compiling other packages from tar.gz files and
installing them without first rolling an rpm (for example).  Yes,
compiling is not hard, and it might make one feel that they are a more
empowered or advanced Admin, but it cannot be said emphatically enough
that compiling things from .tar.gz files should be the absolute last
resort way to get some software onto a system.

CPAN is sort of a gray area because it's another package manager in
and of itself, and perl modules mostly are not "compiled", but it
creates the same problems.

--
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: Intermittent perl crash

[Brian Mathis]

On Dec 17, 2007 3:22 PM, Michael Kairys <[EMAIL PROTECTED]> wrote:
>
> "Michael Kairys" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
>
> > By "fairly simple" I mean ones I'm working on that at this point are only
> > reading arguments and doing string operations.
>
> Sorry, one more thing, and probably "the" thing: system("notepad &");
> So this is clearly fork-related, but I can't get it to fail consistently
> (or, right now, at all.)
>

How are you starting the script?  From a cygwin bash shell, command
prompt, or clicking on the .pl file?  The references to
"D:\Local\Cygwin\bin\perl.exe" make me think the script is being
called through a windows mechanism instead of a cygwin one.

Maybe the .dll messages mean something to someone else?

--
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: Starting native windows GUI app via ssh.

[Brian Mathis]

On Dec 17, 2007 3:20 PM, Clayton Holloway <[EMAIL PROTECTED]> wrote:
> Is it at all possible to start a native windows application(GUI) via ssh
> and have it actually appear on the windows box?
>
> No matter what app I run via ssh (firefox, notepad, etc) the process is
> listed in the task manager, but is nowhere to be found on the screen. If
> X were in use here, I'd just set the DISPLAY variable, but afaik windows
> won't use a DISPLAY.
>
> Any information on this would be greatly appreciated.

You need to install the cygwin ssh service with the "Interact with
desktop" option enabled.

--
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: Remote Linux desktop in my Cygwin windows PC

[Brian Mathis]

On Jan 2, 2008 2:17 AM, Erich Dollansky <[EMAIL PROTECTED]> wrote:
> Hi,
>
> marcos rebelo wrote:
> >
> > I'm really basic with Linux. I'm running remote applications with:
> >
> > xhost
> > ssh
> > export DISPLAY
> >
> > So I'm using Eclipse, gedit, firefox, ... like this for example in my
> > windows. Now I'm curios if I'm able to have the full desktop of my
> > Linux machine like a window in my remote Windows PC.
> >
> > I'm using the Ubuntu 7.10 in the Linux PC
> >
> just start the windo manager of your choice at the Linux box.
>
> startx should do the job.
>
> You can chose then to have the Linux desktop in one window or it will
> replace your current Windows desktop.
>
> Windows will stay in the background.
>
> Running the window manager on the Windows machine has the advantage that
> your Linux windows integrate fully into you Windows environment.
>
> I find it a bit disturbing to have the Unix part separated from the
> Windows part when the Windows manager was running on the Unix box.
>
> Erich

Another option is to use a VNC server on the linux machine, and then
the VNC viewer on windows.  This is similar to Remote Desktop, so that
might be what you're looking for.  Yet another option which gives good
results is "NX", which is also similar to remote desktop, and is
faster than VNC.

In either case, you will need to set up something on the linux server
to allow you to do this.

--
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: David's new address

[Brian Mathis]

Maybe you'd get less spam if you didn't post the new address to a
mailing list with public archives at the beginning of the year!


On Jan 3, 2008 7:27 AM, David T-G old address <[EMAIL PROTECTED]> wrote:
> Good morning, wherever you are!
>
> It's that time of year again, and I have a new email address.  Somewhat
> unsurprisingly, it is
>
>   [EMAIL PROTECTED]
>
> for this year.  I made it through last year without dying from the spam
> (but as we can see at
>
>   http://www.userfriendly.org/cartoons/archives/08jan/uf011102.gif
>
> it's getting worse), so I am hopeful that I won't have to rotate again
> for another year.
>
> In the past I've had some issues sending a blind-copied mass email, so
> this time I'm sending a note to each person individually.  Still, though,
> it's just a form letter; sorry :-)
>
>
> Love, Best Wishes, and Happy New Year to all!
>
> :-D
> --
> David T-G
> See http://justpickone.org/email/
>
>
> --
> 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: How to use encrypted folder (or filesystem)

[Brian Mathis]

On Jan 9, 2008 10:11 PM, Larry Hall (Cygwin)
<[EMAIL PROTECTED]> wrote:
> CABROL PERALES Alexandre wrote:
> > Hi everybody,
> >
> > i'm using Cygwin Easy version on an usb disk.
>
> This is really a question that is more appropriately directed towards the
> maintainers of "Cygwin Easy", since that's a separate project and anything
> we might say here may not be appropriate for "Cygwin Easy".   That said...
>
> > I would like to kow if we can use encrypted FileSystem or folder with
> > cygwin.
> >
> > e.g.:
> > mount -t vfat info.img info/ -oencrypted=aes128
> >
> > or another way.
>
> Cygwin is not Linux (or Unix or BSD or)  It has no file-system drivers
> and relies on Windows to provide file access.  Translation - you cannot
> mount a file system with Cygwin like you show above.  Cygwin's mount is
> not too much more than a mapping of Windows-style paths to POSIX ones.
>
> > Purpose:
> > be able to use mobile cygwin with an encrypted device (partition,
> > folder, fs image) without have to alter hoster system (no modifications
> > on the operating system, even on c: drive).
> >
> > Do you have any idea?
>
> In general, if you can do it with Windows, you should be able to do it
> with Cygwin and that may translate into being able to do it with "Cygwin
> Easy".  But to do it with Windows means you need an NTFS file system on
> your USB disk.  If that's a problem for you, then I believe you have
> provided the answer to yourself. ;-)
>
> --
> Larry Hall  http://www.rfk.com
> RFK Partners, Inc.  (508) 893-9779 - RFK Office
> 216 Dalton Rd.  (508) 893-9889 - FAX
> Holliston, MA 01746


Though not part of cygwin, truecrypt is an excellent and open source
utility that will allow you to make and encrypted disk.  Then you can
install whatever you like on it.

http://www.truecrypt.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: Equivalent of recycle bin?

[Brian Mathis]

On Mon, Jan 28, 2008 at 9:20 AM, Brian Mathis <[EMAIL PROTECTED]> wrote:
> On Mon, Jan 28, 2008 at 4:22 AM, Eric Lilja <[EMAIL PROTECTED]> wrote:
>  > Hello, I messed up royally today when I was merging two bash scripts.
>  >  When I was going to test if my argument handling worked I had forgot to
>  >  comment out a call to "rm -f" that took a relative path and since the
>  >  script wasn't executed where it was supposed to it removed several
>  >  files. Many of those are easily replaced but some were source files that
>  >  have been modified the past months and the last backup was from july
>  >  23rd 2007. =/
>  >
>  >  I know I should robustify my script but I was wondering if there's an
>  >  equivalent of the recycle bin I can use so I can easily restore files
>  >  that were not supposed to be deleted?
>  >
>  >  - Eric
>
>  No, there is no "recycle bin" in Linux.  Sorry.  The best you can do
>  is do a google for "undelete linux" and see if any of that helps you.
>  You *may* be able to recover the files if you take a bit-for-bit image
>  of the disk, then manually look through that X GB file for the disk
>  clusters that contain some strings that you remember are in those
>  scripts.  Chances are that if you didn't shut down the server
>  immediately after, the files are gone.
>
>  Of course you know that you should always have backups, but most
>  people need a catastrophe to really understand *how* important they
>  are.  Consider this your catastrophe.

OK, so I'm on the cygwin mailing list and a linux mailing list.  Guess
which I thought I was reading? :)

If you are on Windows Server or Vista, Volume Shadow Copy might help
you get those back.

--
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: Equivalent of recycle bin?

[Brian Mathis]

On Mon, Jan 28, 2008 at 4:22 AM, Eric Lilja <[EMAIL PROTECTED]> wrote:
> Hello, I messed up royally today when I was merging two bash scripts.
>  When I was going to test if my argument handling worked I had forgot to
>  comment out a call to "rm -f" that took a relative path and since the
>  script wasn't executed where it was supposed to it removed several
>  files. Many of those are easily replaced but some were source files that
>  have been modified the past months and the last backup was from july
>  23rd 2007. =/
>
>  I know I should robustify my script but I was wondering if there's an
>  equivalent of the recycle bin I can use so I can easily restore files
>  that were not supposed to be deleted?
>
>  - Eric

No, there is no "recycle bin" in Linux.  Sorry.  The best you can do
is do a google for "undelete linux" and see if any of that helps you.
You *may* be able to recover the files if you take a bit-for-bit image
of the disk, then manually look through that X GB file for the disk
clusters that contain some strings that you remember are in those
scripts.  Chances are that if you didn't shut down the server
immediately after, the files are gone.

Of course you know that you should always have backups, but most
people need a catastrophe to really understand *how* important they
are.  Consider this your catastrophe.

--
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 not working well with vista 64

[Brian Mathis]

On Wed, Jan 30, 2008 at 6:14 PM, Ashutosh Singh
<[EMAIL PROTECTED]> wrote:
>Hi,
>I downloaded the lates cygwin and I still see problems with
>createProcess.
>fork() fails in many cases.
>Editing files is also an issue. Has the issue been punted, should I
>forget
>about making cygwin work
>reliably on windows. I need XWindows badly and would have to move back
>to
>Exceed. Other utilities
>work fine. I have done the rebase etc, as mentioned in the forums.
>regards,
>Ashutosh

I have been running cygwin on Vista 64bit with no issues, and have not
had to do anything other than the regular installation.  I have not
had to rebase or anything.  The only config change I have made is to
disable UAC in Vista, so maybe that would help (though not the best
thing).

I have not used X Windows specifically though, so maybe there is an
issue directly related to that.

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

Long filename support, soon?

[Brian Mathis]

I've been running into problems with rsync and "too long" filenames.
I've done the searching and know that it's an issue with the cygwin
library not using the unicode system calls.

Is there a timetable for when this will be changed?  I know it's a
pain, but so is not being able to use a lot of the great tools cygwin
provides because of this problem.

Anyway, just wanted to ask and also add my vote for support for this.
Thanks.

--
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: Long filename support, soon?

[Brian Mathis]

On Fri, Mar 7, 2008 at 5:22 AM, Corinna Vinschen
<[EMAIL PROTECTED]> wrote:
> On Mar  6 17:39, Larry Hall (Cygwin) wrote:
>  > Adam Thompson wrote:
>  >> On 06/03/2008, Larry Hall (Cygwin) <[EMAIL PROTECTED]>
>  >> wrote:
>  >>> It is one of the many enhancements in the forthcoming 1.7 series.  And
>  >>>  it seems it is also an excruciatingly large task.  There is no timetable
>  >>>  for 1.7 as a result.  But many hands make light work.  If you and others
>  >>>  you know have hands to lend, I know Corinna has a list of tasks that can
>  >>>  use them.
>  >>>
>  >> Is this list published anywhere?
>  >> I'm not a developer (unless you're porting to Sinclair ZX BASIC), but
>  >> perhaps there are some tasks that us sysadmin/support/doco people can
>  >> help with?
>  >
>  > I remember a list of tasks being sent to this list by Corrina but I can't
>
>   s/rrin/rinn/
>
>  That list was send to the developer's ML.
>
>
>  > put my finger on it right now.  As I recall, these were all development
>  > tasks.  Corrina would be the best one to say if there are specific tasks
>  > in the areas you mentioned.
>
>  I'm going to check in my changes today, which will really enable using
>  long pathnames for the first time.  it can now access and create long
>  paths, as well as start applications stored in long paths.
>
>  However, it's certainly still buggy and missing features.  I'll follow
>  up with what is done and what's not done on the developer's list.
>
>  For the curious and the brave, the next developer's snapshot from
>  http://cygwin.com/snapshots will be something to test.
>
>
>  Corinna
>
>  --
>  Corinna Vinschen  Please, send mails regarding Cygwin to
>  Cygwin Project Co-Leader  cygwin AT cygwin DOT com
>  Red Hat


Wow, that's great.  Here I am being a pain about it, and it looks like
it's getting close to landing.  I just want to say that I appreciate
all of your hard work on cygwin.  I don't think I could use Windows
without 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: Finding either boot time or login time

[Brian Mathis]

On Fri, Jan 30, 2009 at 10:33 AM, Ronald Fischer
 wrote:
> Eric Blake  byu.net> writes:
>> man uptime
>
> I have thought of uptime, but this requires doing date calculation (I have to
> subtract the uptime from the current time), which I wanted to avoid; plus I
> wanted to have it reproducible (i.e. if I calculate the "startup time" twice
> in succession, I wanted to get the same result - using the uptime calculation
> might well give differences of, say, one, in rare cases 2, seconds for the
> startup time on repeated calculations.
>
> But it seems there is no alternative. I had not expected that Windows would
> not log such events, like starting up or having some user logged in...
>
> Ronald

This information is available in windows by using one of two commands:
net stats srv
or
systeminfo

In both cases, you will need to grep (if calling from cygwin) or use
the windows "find" command (equivalent of grep), to isolate just the 1
line.

I've noticed that, on Vista, "net stats srv" always seems to return
1980, while systeminfo returns the correct result.

If that doesn't work for you, I'm sure there are other ways to do it.
You might need to write some vbs and query WMI to get the uptime
(http://www.microsoft.com/technet/scriptcenter/resources/qanda/sept04/hey0907.mspx)
 Or you can install the "uptime" tool from Microsoft
(http://support.microsoft.com/kb/232243)

--
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: 64 bit system compatibility

[Brian Mathis]

I have been running cygwin on 64-bit Vista for over a year now.  In my
configuration, I have disabled UAC, so if you have that enabled it
might be something to look at.  Also, any of the X programs require
that the X server is running before they will run.  You can start X by
opening a normal cygwin window, then typing "startx".  You should see
an "X" in the windows system tray.

If you're just looking for an xterm-like thing, I suggest you also
take a look at rxvt.  It is similar to xterm but does not require the
full X server to be running for it to work.  MinTTY is a recent
alternative that others here have said works well too.


PS. You typically do not need a "64-bit version" of any kind of
software for it to work on Vista 64-bit.  Vista will also run 32-bit
applications.

On Fri, Feb 6, 2009 at 6:32 AM, Giacomo Bruno  wrote:
> Hello,
>
> I just moved to a new machine with a 64 bit windows vista os . I wanted
> to install and run cygwin. While the installation process run to the
> end, programs like emacs xterm and xwin do not work. I also  do not get
> a home directory when I run for the first time cygwin (I thought it
> would be created automatically). I just read on the cygwin FAQ that
> "..As far as we know no one is working on a native 64 bit version of
> Cygwin.."
> I interpret it like my system is unsupported and I should not expect the
> above mentioned programs from the current version of cygwin to work out
> of the box. Is that correct? Is it planned to release a Vista 64-bit
> compatible cygwin version? When?
> Actually I'd be happy if I managed to have at least ssh, scp and xterm
> work. Is it just a matter of recompiling them with a proper compiler or
> it is more than that?
> Thanks a lot for any clarification in advance
> Best
> Giacomo (very deceived...)
>
> Cheers
> Giacomo
>
>
>
> --
> 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

[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: How can I assign a hotkey to run a cygwin/bash script?

[Brian Mathis]

On Fri, Mar 6, 2009 at 10:59 AM, Arun Biyani  wrote:
>
>>>
>>> Arun Biyani wrote:
>>>
>>> > It appears that Windows XP shortcuts have a limitation. The
> shortcut
>>> must
>>> > be to a target on the desktop (or to a target in a folder on
> desktop).
>>>
>>>   Surely you can't mean what you've written there exactly how you've
>>> worded
>>> it: I thought shortcuts can point *to* anywhere, on any windows
> version.
>>>
>>>   Did you mean that in order for the /hotkey/ to work, the shortcut
>>> itself has
>>> to be *on* the desktop or in a folder on the desktop?
>>>
>>>     cheers,
>>>       DaveK
>
> Yes. Meant exactly that. I created a shortcut on desktop for mintty.
> Assigned it the key "ctrl+alt+M". I like my desktop to be uncluttered.
> So after assigning the key, I moved the shortcut icon into my work
> folder
> "/c/home/wrk". The hotkey stopped working. I then moved the icon back to
> the desktop and it worked again. Now, all my hot-key-assigned shortcuts
> sit in a folder "shortcuts" on the desktop and they all work.
>

The hotkey is pointing to the location where you had the shortcut.
Since you moved it, there's nothing there for the hotkey to execute.

Hotkeys are not attached to the shortcut, even though the horrible UI
the Explorer uses seems to indicate they are.  They are stored in a
systemwide table that doesn't know if you've moved the target of the
key.  I recommend avoiding the built-in hotkey fields in shortcuts,
and instead use any one of the numerous hotkey managers out there,
such as the one I've written here:
http://directedge.us/content/winhotkey

--
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: How can I assign a hotkey to run a cygwin/bash script?

[Brian Mathis]

On Fri, Mar 6, 2009 at 12:58 PM, Spiro Trikaliotis
 wrote:
> Hello,
>
> * On Fri, Mar 06, 2009 at 12:07:37PM -0500 Buchbinder, Barry (NIH/NIAID) [E] 
> wrote:
>
>> I looked at the properties of shortcuts on my Desktop, in the Start Menu,
>> and in a directory outside of "C:\Documents and Settings" (the equivalent
>> of "c:\home\wrk").  In none was the option to set a hotkey grayed out.
>
> They do not need to be grayed out: You can set these option.
> Unfortunately, they do not have any effect. This is something different.
>
>>                                                        I would think that
>> Windows keeps a table of hotkeys and shortcuts (not targets) and it looks
>> for the shortcut itself when you hit the hotkey so the shortcut's
>> contents can be read.
>
> Well, we can think about many things: However, this is not the way it
> works on Windows, obviously.


Windows keeps a systemwide table of hotkeys, and when one is pressed
Windows runs whatever is in the table as the target.  If the target is
a shortcut, it opens the shortcut.  If it's a document, it opens the
document.  Whatever the type of the file is that the target is
pointing to, Windows will execute it as if you had double-clicked on
the file.  The filetype must have a program associated with it in
order for it to launch correctly.

Even though there is a field in the shortcut property dialog box for
hot key, it is not tied to the shortcut at all.  When you set the
hotkey in a shortcut, it updates the systemwide table and that's it.


>> BTW, if assigning the hotkey after the shortcut is in "c:\home\wrk"
>> really doesn't work, I suspect that the Start Menu may.
>
> Yes, the start menu works. This was news for me, too. In quick start,
> it does not work, though.
>
> So, start menu and desktop work. Anything else? ;)
>
> Best regards,
> Spiro.

--
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: How can I assign a hotkey to run a cygwin/bash script?

[Brian Mathis]

On Fri, Mar 6, 2009 at 3:59 PM, Spiro Trikaliotis
 wrote:
> Hello Brian,
>
> * On Fri, Mar 06, 2009 at 01:29:02PM -0500 Brian Mathis wrote:
>> On Fri, Mar 6, 2009 at 12:58 PM, Spiro Trikaliotis
>>  wrote:
>
>> > Well, we can think about many things: However, this is not the way it
>> > works on Windows, obviously.
>>
>> Windows keeps a systemwide table of hotkeys, and when one is pressed
>> Windows runs whatever is in the table as the target.
>
> Ok. If you know for sure, I stand corrected. However, from the
> behaviour, this is not the way it seemed to work to me.
>
> Can you explain then why a shortcut I define in the quick start does not
> get applied? Yes, I defined it directly there, I did not move a file
> there.
>
> Best regards,
> Spiro.


I just tested this on Vista, and you are right, it does not seem to
work if you have set the hotkey there.  It may be a conflict with the
already-set hotkeys for the items in the Quicklaunch toolbar.  If
you're not familiar, on Vista you can use Win+1, Win+2, etc... to
start the 1st, 2nd, etc... icon in the quicklaunch bar.  This feature
is not there for XP though.

I suspect that it would work just fine with winhotkey if you were to
point the target to the shortcut in the quicklaunch bar, but I haven't
tried it.  At that point, it's just another path.

--
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: Calling Cygwin to start a shellscript

[Brian Mathis]

On Fri, May 15, 2009 at 5:35 PM, Thomas Wiedmann  wrote:
> Hello,
>
> How can a shellscript be called from the Windows cmd console using Cygwin,
> i. e. by which command, options and arguments has Cygwin to be called to run
> a shellscript, e. g. myscript.sh?
>
> Thomas Wiedmann


What I have done is associate files with a .sh extension to run the
bash.exe file.  Works for me, but I'm not sure if it pulls in all the
environment variables - but I don't need them.

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

[Brian Mathis]

On Thu, Mar 27, 2008 at 2:38 PM, Diego Costa <[EMAIL PROTECTED]> wrote:
> Please how can i configure the cygwin shell to be exactly like the
>  solaris command prompt ?
>
>  Can anyone help me ?
>
>  Thanks
>  --
>  Diego
>

Cygwin by default uses the "bash" shell and runs it in the "Command
Prompt" window for windows.  You can change the shell to something
else if you like, by editing the cygwin.bat file.  You can change the
window it runs in by using either xterm (also requires X Windows to be
installed and running) or by using rxvt, which doesn't require X
Windows.  'rxvt' is a great solution and you will probably think it
works very much like solaris.

Remember that cygwin is not solaris (or any other type of unix) -- it
is its own thing and has its own unique feel to it (though it may be
similar to unix).

--
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: Getting started with bash

[Brian Mathis]

On Mon, Apr 7, 2008 at 4:25 AM, Michael Holm <[EMAIL PROTECTED]> wrote:
> Hi,
>
>  I have read a lot of documents, but i really cant get this issue solved :(
>  All i want is to be able to execute bash scripts from a windows
>  desktop.. what i do now is..
>
>
>  a batch script:
>  c:\cygwin\bin\bash c:\cygwin\example.sh
>
>  this is my bash script.
>
>  example.sh
>  ls -l
>
>
>  but i get the following output:
>  command not found.
>
>  i hope that someone can give me a hit... all i have done is:
>  install cygwin, made my batch script.. and made my bash script.. do i
>  need to set any environment vars or something?
>
>  mvh
>  Michael Holm


What works for me is to create a text file (script) with a .sh
extension.  Make something simple like:
echo 123
sleep 10

Then double-click on it, and windows will ask what program to open the
.sh extension.  Select "choose another program" and browse to
c:\cygwin\bash.exe.

That's always worked for me, with no need for doing any "login shell" stuff.

--
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: Thought/Suggestion/Is it Possible for the new Cygwin 1.7 /etc/fstab

[Brian Mathis]

On Tue, Jun 10, 2008 at 3:10 PM, Brian Keener
<[EMAIL PROTECTED]> wrote:
> Dave Korn wrote:
>> > But as I say I am probably overthinking this for the Cygwin on Windows
>> > environment - does it really care if I change cd's without a unmount and
>> > then mount?
>>
>>   'mount' and 'unmount' are utterly different kinds of beast on Cygwin as
>> they are on the Linux platform; they don't do the same job, and in any case
>> that job doesn't even need doing.
>
> Thanks Dave and Corinna for the response and clarification - just as I
> thought - I was overthinking it.
>
> bk


Keep in mind that cygwin is not Linux/Unix, it's CYGWIN.  It makes
life on Windows much easier by being "unix-LIKE", but it's not unix.

--
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: Fwd: md5sum using Cygwin in Windows

[Brian Mathis]

On Wed, Jun 25, 2008 at 12:26 AM, Christopher Faylor
<[EMAIL PROTECTED]> wrote:
>
> think "Wow! Zing!" was not anyone trying to be professional or
> encouraging.  I very much do not care what version of Linux someone uses
> and do not care if someone learns Unix.  I do think that people should
> spend a modicum of time familiarizing themselves with something before
> offering criticisms, suggestions, or advice, however.  If they can't be
> bothered to do that, and want to lecture or criticize, they should be
> prepared not to be taken very seriously.
>

I _also_ think people should spend a modicum of time familiarizing
themselves with something before using it, especially when it allows
them to communicate with others of the human race.  One should, before
attempting to communicate with others, become well-versed in skills
like "common courtesy", "politeness", and "how not to be an a**hole".

It's also useful if people remember that at one point they did not
know anything, and had to learn things.  It would also be good for
them to remember that all knowledge comes from other people, and
anything they learned was once taught to them by another person, be it
through direct communication or recorded media.

In addition, a bit of time should be spent thinking about the effect
that ignoring these rules might have on someone else who is starting
down a path of knowledge and learning, and how a member of that
community's response might forever damage the education and perception
said new person will have about that community.


While one may not always strive to be professional, one should always
strive to be human.

--
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: bash term with multiple tabs - bash (without X)

[Brian Mathis]

Cygwin now has the 'screen' command available.  Once you install it,
you will have the ability to run multiple terminal sessions inside 1
window.  I would also suggest using rxvt instead of the default
cmd.exe shell (rxvt does not require X).  If you put the following
code in your .screenrc or /etc/screenrc file, you will get a nice bar
on the bottom that acts sort of like tabs:

# Change scrollback to 2000 lines
defscrollback 2000

# status line at the bottom
hardstatus on
hardstatus alwayslastline
hardstatus string "%{.bW}%-w%{.rW}%f%n %t%{-}%+w %=%{..G}[%H %l]
%{..Y} %m/%d %c "

It's not 'true' tabs, but once you know screen, you will be using it
all the time on remote connections as well.


On Fri, Jul 25, 2008 at 4:38 PM, Administrator <[EMAIL PROTECTED]> wrote:
> I'm looking for a terminal / shell utility that will let me have multiple
> tabs open (shell terminal or term in each tab doing something different).  I
> find that I have several cygwin bash shells open at any one time and want to
> reduce this to one window.
>
> Is there anything that does this?  I don't want to run X but am willing to
> purchase commercial software if it will do the trick.  I am on Windows XP.
>
>
> thanks
>
>
> Raj
>
> --
> 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: script

[Brian Mathis]

On Mon, Jul 28, 2008 at 12:15 PM, r <[EMAIL PROTECTED]> wrote:
>
> ok, I'm going to learn to manage basic cygwin-linux features
[...]
> I saw unlike linux that cygwin does not warn me when there are new
[...]
> Is there a way ( like in linux ) to send a message to my prompt
[...]
>
> R

I think one source of confusion is because of the areas I have
highlighted.  Don't expect cygwin to be like linux, because it is not
linux.  It is cygwin.  Cygwin gives Windows a "UNIX-like" environment,
it does not turn Windows into linux or UNIX.

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

Recent change to terminal icon / mintty breaks taskbar pinning

[Brian Mathis]

I recently updated to the latest set of cygwin packages, and something
has broken the terminal icon when pinned to the start menu.  When
starting from the Start menu "Cygwin Terminal" icon, mintty comes up
normally, loads my user profile, and the cwd is set to ~.

However, if I right-click the icon on the taskbar and select "Pin to
taskbar", close the existing terminal, then open by clicking on the
pinned taskbar icon, the terminal starts but it does not load the
profile, the cwd is /usr/bin, and no commands can be found (e.g. ls:
command not found).  I have tracked this down to the pinned icon
missing the arguments "-i /Cygwin-Terminal.ico -".

I'm sure this worked prior to the update, so something seems to have
changed.  I update fairly often, so this is something recent within
the past month or so.  I'm on Windows 8.1 x64 using Cygwin 32bit.

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Cygwin installer: "Next" button should not be default on "Select Packages" page

[Brian Mathis]

Current behavior:
I have, many times, started typing something into the Search box at
the top of the page and instinctively press Enter.  Because the Next
button is default, this causes the installer to advance to the
installation stage (which may take a while as the actual installation
occurs, so it is not easy to quickly go back and change the package
selection).

Expected result:
Search filter should be applied and installer should not advance to
next stage until Next button. is explicitly clicked.


It doesn't matter that the search box dynamically updates the results;
there is still a natural instinct to press Enter after typing in the
search query.

~ Brian

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Cygwin installer: "Next" button should not be default on "Select Packages" page

[Brian Mathis]

On Tue, Nov 17, 2015 at 5:21 PM, Andrey Repin  wrote:
> Greetings, Brian Mathis!
>
>> Current behavior:
>> I have, many times, started typing something into the Search box at
>> the top of the page and instinctively press Enter.  Because the Next
>> button is default, this causes the installer to advance to the
>> installation stage (which may take a while as the actual installation
>> occurs, so it is not easy to quickly go back and change the package
>> selection).
>
>> Expected result:
>> Search filter should be applied and installer should not advance to
>> next stage until Next button. is explicitly clicked.
>
> The "Next" button should be the default action, however, in your specific use
> case, the current behavior is, indeed, undesirable.


Why "should" it be the default action?  Without specific reasoning
behind such a statement, it has no merit.


>> It doesn't matter that the search box dynamically updates the results;
>> there is still a natural instinct to press Enter after typing in the
>> search query.
>
> I don't know. I've long since unlearned that habit.
> And not only because of Cygwin setup. Many applications adopted the same
> pattern of dynamically filtered list, and it is actually very useful.


Seeing as it is a "habit" that you had to unlearn, it only reinforces
that this is incorrect behavior for this case.  Users should not have
to unlearn/relearn a common behavior just for a single control in a
single application.  The argument is not in consistency of coding
(i.e. all panels have "Next" as default, so this one also should), but
consistency of user experience (i.e. when I type something into a
search box and then press Enter, I expect a search to be initiated).

Whether the list is filtered dynamically is beyond the point.  Dynamic
filtering can stay as it is, just the Enter key should either also
initiate filtering (which is probably redundant), or it should simply
do nothing.


> --
> With best regards,
> Andrey Repin
> Tuesday, November 17, 2015 19:18:50
>
> Sorry for my terrible english...
>

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Updated: Perl distributions

[Brian Mathis]

On Fri, Dec 18, 2015 at 10:33 AM, Jim Reisert AD1C
 wrote:
> Let's say that I installed one of these modules using "cpan
> install..." instead of downloading from the Cygwin repository:
>
>> perl-Archive-Zip-1.55-1
>> etc.
>
> How can I go about reversing that to use the module from the Cygwin
> repository instead?  Is it as simple as downloading the module from
> the Cygwin repository, or do I need to uninstall the module from my
> Perl installation first?
>
> --
> Jim Reisert AD1C, , http://www.ad1c.us


There is no easy way to remove modules installed via CPAN.  You can
Google how to do it, but it's mostly manual.  You also need to
consider how to handle dependencies that were pulled in.

To avoid this in the future, only install packages using the package
manager (i.e. cygwin setup), and for anything that's not in there, use
the perl local::lib module to setup a dedicated location for any
additional packages you need.

~ Brian

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Is ping only supposed to work for admin accounts?

[Brian Mathis]

Yes.  Ping needs admin rights in all operating systems, but they have
various ways to allow access, such as running suid in unix or using a
special API call on Windows.  If you need ping from cygwin, it's best
to rely on the Windows version without installing the cygwin one.

~ Brian

On Sun, Mar 20, 2016 at 5:34 PM, Ray Satiro  wrote:
> I just used the cygwin installer to install ping-1.0.2-1.tar.xz but it
> doesn't work for limited user accounts:
>
> $ ping google.com
> ping: socket: Operation not permitted
>
>   149   29930 [main] ping 11668 dup_ent: duping protoent "icmp", 0xD56580
>46   29976 [main] ping 11668 dup_ent: protoent icmp 0x80039F64 0x1
>21   29997 [main] ping 11668 dup_ent: duped protoent "icmp", 0x80039F50
>21   30018 [main] ping 11668 cygwin_socket: socket (2, 3 (flags 0x0), 1)
> --- Process 11668 loaded C:\Windows\SysWOW64\WSHTCPIP.DLL at 73BB
>  1084   31102 [main] ping 11668 __set_errno: void
> __set_winsock_errno(const char*, int):235 setting errno 1
>37   31139 [main] ping 11668 __set_winsock_errno: cygwin_socket:694
> - winsock error 10013 -> errno 1
>57   31196 [main] ping 11668 cygwin_socket: -1 = socket(2, 3 (flags
> 0x0), 1), errno 1
>
>
>
>
>
> --
> Problem reports:   http://cygwin.com/problems.html
> FAQ:   http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
>

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: libav or ffmpeg and associated tools

[Brian Mathis]

Is there any reason not to use the native Windows build instead?  What
does the cygwin port gain you over that?


On Thu, Jun 16, 2016 at 12:02 PM, David Stacey  wrote:
> On 16/06/16 13:49, Marco Atzeri wrote:
>>
>> On 16/06/2016 14:44, Václav Haisman wrote:
>>>
>>> Hi.
>>>
>>> I have noticed a lack of ffmpeg and/or libav and associated tools on
>>> Cygwin. It would be nice to have them.
>>>
>>> But I am not going to try and package them, sorry. :)
>>>
>>
>> same reason as fedora...
>>
>>
>> http://rpmfusion.org/FAQ#Why_doesn.27t_the_Fedora_project_ship_the_Software_that_RPM_Fusion_offers.3F
>
>
>
> ffmpeg-2.6.3 is available in CygwinPorts.
> http://cygwinports.org/
>
> Dave.
>
>
>
> --
> Problem reports:   http://cygwin.com/problems.html
> FAQ:   http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
>

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: chere mintty window position

[Brian Mathis]

Are you seeing this on Windows 10?  I have noticed a lot of other apps
do this as well on Windows 10, such as Evernote and Firefox.  It seems
to be caused by the invisible window border that Windows 10 puts on
everything to make it appear that apps have no border, but still give
you enough pixels to grab them to resize with the mouse.  You won't
notice it if you always have your apps maximized.

In that case, I don't think even a position parameter would help,
since the 0,0 would still include the invisible window border, unless
maybe you tried negative positions.

The fix needs to be done in code, as described here:

http://stackoverflow.com/questions/35259756/wpf-and-windows-10-invisible-border-around-windows

You can pass options to mintty when you run chere using the -o option.
Try something like -o "-p -5,-5".  Run "chere -h" to see help.



On Mon, Aug 8, 2016 at 5:51 PM, Brent  wrote:
> Hello.
>
> I recently did a clean reinstallation of 32 bit cygwin, and as part of that, 
> downloaded the chere package so that I could get Windows Explorer context 
> menu bash here support.
>
> I like my cygwin bash terminal windows to come up maximized by default.
>
> So, my usual procedure the first time that I use the context menu bash here 
> feature is to:
> 1) click on mintty's Windows square button in the top right to maximize the 
> window
> 2) right click inside mintty --> Options... --> Window --> click on Current 
> Size button
>
> Doing that this time ALMOST works.  When I try the context menu bash here 
> feature now, the mintty window does come up greatly enlarged.  BUT it is not 
> correctly centered!  It actually is shifted to the right by ~5 or so pixels!  
> That means that the right side scroll bars, for example, are partly going off 
> the right side of the screen.  This is very annoying.
>
> Is this a known bug with mintty?
>
> Is there a fix?
>
> I have one guess.  This mintty page
> https://mintty.github.io/mintty.1.html
> says that it supports a
> -p, --position X,Y
> options, so something like
> -p 0,0
> should do the trick.  The question is how can I supply an option like that to 
> mintty when it is opened by chere from a Windows Explorer context menu.
>
> --
> Problem reports:   http://cygwin.com/problems.html
> FAQ:   http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
>

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Installer request: Remember state of final checkboxes between runs

[Brian Mathis]

Every time the installer is run, it asks to create an icon on the
desktop.  I do not want an icon on my desktop, and I have to uncheck
this box every time.  I have probably done this 100 times since I've
been using Cygwin over the years.

The installer should remember that this option was declined and
default the checkbox to that state on the next run.

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Installer request: Remember state of final checkboxes between runs

[Brian Mathis]

Thanks for the information, which I did not know about.

However, Achim is correct, and this should be implemented on
principle, even if there's a bad workaround.  When one is working with
and providing programs for a GUI-based environment, the program should
act as expected as a *GUI*, and not require someone to change contexts
to a command-line just to get an obvious feature.  The cygwin
environment is command-line-based, but the installer is GUI-based, and
should function as such.


On Fri, Jan 13, 2017 at 10:51 AM, Markus Hoenicka
 wrote:
> At 2017-01-13 16:46, Achim Gratz was heard to say:
>>
>> Marco Atzeri writes:
>>>
>>> On 13/01/2017 16:14, Brian Mathis wrote:
>>>>
>>>> The installer should remember that this option was declined and
>>>> default the checkbox to that state on the next run.
>>>>
>>>
>>> there are some options available for this
>>>
>>>  -N --no-startmenu Disable creation of start menu
>>> shortcut
>>>  -d --no-desktop   Disable creation of desktop shortcut
>>
>>
>> I would imagine that the OP just double clicks the installer icon, so no
>> options are in effect.
>>
>>
>
> I would imagine that a little Windows knowledge suffices to add those
> options to the command represented by the icon.
>
> regards,
> Markus

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Installer request: Remember state of final checkboxes between runs

[Brian Mathis]

On Fri, Jan 13, 2017 at 5:27 PM, cyg Simple  wrote:
> On 1/13/2017 10:14 AM, Brian Mathis wrote:
>> Every time the installer is run, it asks to create an icon on the
>> desktop.  I do not want an icon on my desktop, and I have to uncheck
>> this box every time.  I have probably done this 100 times since I've
>> been using Cygwin over the years.
>>
>
> You only need to check the boxes on initial install.
>
>> The installer should remember that this option was declined and
>> default the checkbox to that state on the next run.
>>
>
> They are not checked by default because you only need to create them
> once.  You don't need to create them on update unless you've removed the
> shortcuts created.
>
> --
> cyg Simple


No, this is not correct.  If you run the install and DEselect to
create icons, it will ask you to create them again next time.  It's
only doing a simple check if files exist to determine if the box is
checked.  If the files don't exist, then is asks to create them, so
there is no way to say "never create icons".

The only way it doesn't ask to create them is if they're already
there, which is no help to people who never want them.

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Perl library request - local::lib

[Brian Mathis]

Please add the local::lib library to the available perl packages.

This allows bootstrapping many other packages directly from cpan into
a local directory without polluting the main Cygwin files.

Thank you.
~ Brian

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Perl library request - local::lib

[Brian Mathis]

On Wed, Feb 1, 2017 at 1:46 PM, Achim Gratz  wrote:
> Brian Mathis writes:
>> Please add the local::lib library to the available perl packages.
>
> It was a deliberate decision to not include it.  Just throwing out a
> request like that won't convince me otherwise, but I may change my mind
> if you have any arguments with substance.
>
>> This allows bootstrapping many other packages directly from cpan into
>> a local directory without polluting the main Cygwin files.
>
> This is still more error prone than one would like and I expect anyone
> capable of getting all the little things right to not have a problem
> with bootstrapping local::lib themselves (I'd do it via cpanm, but there
> are other ways of course).  Also, just by installing CPAN you aren't
> polluting main Cygwin files: the modules distributed with Cygwin install
> under perl_vendor, the modules installed by cpan will end up in
> perl_site.
>
>
> Regards,
> Achim.
> --


I appreciate your feedback on this.  Is there somewhere that rationale
is laid out?  If there was a mailing list discussion, then I must have
missed it.  Would you happen to know where it would be in the archive?


Thanks
~ Brian

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

chere: Add cygwin icon to context menu

[Brian Mathis]

For anyone using 'chere' interested in having the Cygwin icon in the
context menu, you can use the following commands:

regtool -w -s set
/HKCU/Software/Classes/Drive/Shell/cygwin64_bash/Icon
'C:\cygwin64\Cygwin-Terminal.ico'
regtool -w -s set
/HKCU/Software/Classes/Drive/Background/Shell/cygwin64_bash/Icon
'C:\cygwin64\Cygwin-Terminal.ico'
regtool -w -s set
/HKCU/Software/Classes/Directory/Shell/cygwin64_bash/Icon
'C:\cygwin64\Cygwin-Terminal.ico'
regtool -w -s set
/HKCU/Software/Classes/Directory/Background/Shell/cygwin64_bash/Icon
'C:\cygwin64\Cygwin-Terminal.ico'


You can remove them with this:

regtool -w unset /HKCU/Software/Classes/Directory/Shell/cygwin64_bash/Icon
regtool -w unset
/HKCU/Software/Classes/Directory/Background/Shell/cygwin64_bash/Icon
regtool -w unset /HKCU/Software/Classes/Drive/Shell/cygwin64_bash/Icon
regtool -w unset
/HKCU/Software/Classes/Drive/Background/Shell/cygwin64_bash/Icon

This works for me on Windows 10 64-bit, with Cygwin 64-bit.  It would
be nice if this became an option in 'chere' to do this automatically.

~ Brian

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: chere: Add cygwin icon to context menu

[Brian Mathis]

On Wed, Jul 26, 2017 at 1:33 PM, Doug Henderson  wrote:
> On 26 July 2017 at 11:08, Brian Mathis wrote:
>> For anyone using 'chere' interested in having the Cygwin icon in the
>> context menu, you can use the following commands:
>>
>
> On Win7, chere has installed icons for me since 23 Jan 2014 on 64 bit
> and 12 Aug 2016 for 32 bit.
>
> Note that the path to the icon file is the windows path to the icon
> file installed in the cygwin root directory, i.e.
>
> $ cygpath -w /Cygwin-Terminal.ico
> D:\cygwin64\Cygwin-Terminal.ico
>
>
> HTH
> Doug


Which 'chere' are you using?  I've got 1.4 and there's no mention in
the source of the required "Icon" registry value that would add this
to the context menu.

~Brian

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple