Re: Find tool contained in unknown pkg
First off, thanks posters for the responses "Dave Korn" <[EMAIL PROTECTED]> writes: > Since 'id' on its own might give you too many matches, it's worth mentioning > the handy trick that (this being 'doze not linux really) the full name of the > program is of course 'id.exe'. > > http://cygwin.com/cgi-bin2/package-grep.cgi?grep=id.exe > > That narrows it down sufficiently... Yes Nice Thank you Igor Peshansky <[EMAIL PROTECTED]> writes: [...] > > Ah, but this will not match scripts or symlinks. Since most executables > live in something that ends in "bin", and the package search page supports > full perl regular expressions, you can do > > http://cygwin.com/cgi-bin2/package-grep.cgi?grep=bin%2Fid%5Cb Also nice... both are really nice tips "Jerry D. Hedden" <[EMAIL PROTECTED]> writes: [...] > coreutils I figured something basic... but in a moment I'll explain why it appeared to be missing. [EMAIL PROTECTED] (Eric Blake) writes: >> I've just installed a very minimal cygwin. I noticed the `id' tool is >> not present > > A little too minimal, I would say. id is part of coreutils, which is > a Base package, and as such, it should be part of every working > cygwin installation. You may want to run 'cygcheck -c' to see > which packages are incomplete, and should be reinstalled using > setup.exe. Not too minimal just too dumb on my part. It was nothing more serious than path not getting setup to point to C:/cygwin as `/'. I'm not sure why that would happen, but I may have left out some basic step in there I trashed an old install then ran a new one and didn't really read up on the proper steps for a cygwin install. > Also, following the directions here >> Problem reports: http://cygwin.com/problems.html Ahh yes sorry. But it turns out to be operator error thru and thru. -- 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: Find tool contained in unknown pkg
> I've just installed a very minimal cygwin. I noticed the `id' tool is > not present A little too minimal, I would say. id is part of coreutils, which is a Base package, and as such, it should be part of every working cygwin installation. You may want to run 'cygcheck -c' to see which packages are incomplete, and should be reinstalled using setup.exe. Also, following the directions here > Problem reports: http://cygwin.com/problems.html about attaching 'cygcheck -svr' as a text attachment to your email might help us spot anything else suspicious in your installation. -- Eric Blake volunteer cygwin coreutils maintainer -- 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: Find tool contained in unknown pkg
On Fri, 17 Mar 2006, Dave Korn wrote: > On 17 March 2006 20:28, Harry Putnam wrote: > > > I've just installed a very minimal cygwin. I noticed the `id' tool is > > not present and looking on the packages page I don't see it listed > > separately so I'm guessing it is contained in a package whos name may > > not reflect its presence. > > > > Anyone know which package that might be? > > http://cygwin.com/packages > > Since 'id' on its own might give you too many matches, it's worth > mentioning the handy trick that (this being 'doze not linux really) the > full name of the program is of course 'id.exe'. > > http://cygwin.com/cgi-bin2/package-grep.cgi?grep=id.exe > > That narrows it down sufficiently... Ah, but this will not match scripts or symlinks. Since most executables live in something that ends in "bin", and the package search page supports full perl regular expressions, you can do http://cygwin.com/cgi-bin2/package-grep.cgi?grep=bin%2Fid%5Cb (which corresponds to a search string "bin/id\b", i.e., a program named "id" with no more letters after that, in a directory that ends in "bin"). In case of "id" the results are identical, but if you try your approach with, for example, "vi", you'll find that it doesn't work. HTH, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte." "But no -- you are no fool; you call yourself a fool, there's proof enough in that!" -- Rostand, "Cyrano de Bergerac" -- 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: Find tool contained in unknown pkg
On 17 March 2006 20:28, Harry Putnam wrote: > I've just installed a very minimal cygwin. I noticed the `id' tool is > not present and looking on the packages page I don't see it listed > separately so I'm guessing it is contained in a package whos name may > not reflect its presence. > > Anyone know which package that might be? http://cygwin.com/packages Since 'id' on its own might give you too many matches, it's worth mentioning the handy trick that (this being 'doze not linux really) the full name of the program is of course 'id.exe'. http://cygwin.com/cgi-bin2/package-grep.cgi?grep=id.exe That narrows it down sufficiently... cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Find tool contained in unknown pkg
> I've just installed a very minimal cygwin. I noticed the `id' tool is > not present and looking on the packages page I don't see it listed > separately so I'm guessing it is contained in a package whos name may > not reflect its presence. > > Anyone know which package that might be? coreutils -- 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/