>>I guess the service name has changed?
It's still mcshield, but there are several other related services
running, including McAfee Framework Service (FrameworkService.exe), and
Network Associates Task Manager (vstskmgr.exe). I'm not sure if these
caused a problem or not. The following still work
On Thu, Apr 12, 2007 at 12:09:48PM -0500, Matthew Woehlke wrote:
>PCYMTNQREAIYR, especially don't quote cygwin AT cygwin DOT com!
>
>Jeff Hawk wrote:
>>Thorsten Kampe wrote:
>>>\cygwin\usr\bin and \cygwin\usr\lib are /real/ directories created by
>>>the initial Cygwin installation routine. He shoul
On Thu, 12 Apr 2007, Dave Korn wrote:
> On 12 April 2007 18:02, Igor Peshansky wrote:
>
> > Setup's io_stream uses Cygwin mounts. Thus, once "file:///usr" is
> > created, mkdir_p("file:///usr/bin") is a no-op...
>
> Not on the first ever install, I woulda thunk, since *these*
>
> create_mount
On 12 April 2007 18:46, Igor Peshansky wrote:
>> By gum, I think you've got it. I disabled my McAfee VirusScan software,
>> and a re-install of tar was successful. Thanks again to all who helped.
>
> This brings two things to mind:
>
> 1) Is anyone planning to work on getting some support for
On Thu, 12 Apr 2007, Cheney, Christian wrote:
> >> Are you by any chance running any of:
> >>Sonic Solutions burning software containing DLA component
> >>Norton/MacAffee/Symantec antivirus or antispyware
> >>Logitech webcam software with "Logitech process monitor" service
> >>Kerio, Agnitum or Z
>> Are you by any chance running any of:
>>Sonic Solutions burning software containing DLA component
>>Norton/MacAffee/Symantec antivirus or antispyware
>>Logitech webcam software with "Logitech process monitor" service
>>Kerio, Agnitum or ZoneAlarm Personal Firewall
>>Iolo System Mechanic/AntiVir
On 12 April 2007 18:02, Igor Peshansky wrote:
> Setup's io_stream uses Cygwin mounts. Thus, once "file:///usr" is
> created, mkdir_p("file:///usr/bin") is a no-op...
Not on the first ever install, I woulda thunk, since *these*
create_mount ("/", get_root_dir (), istext, issystem);
create
On 12 April 2007 18:05, Cheney, Christian wrote:
> OK, let's start over. I used the uninstall procedures on the website to
> completely uninstall the software. I removed all previously downloaded
> files, including setup.exe. I downloaded and ran setup.exe, chose a
> different mirror (ftp.cise.
PCYMTNQREAIYR, especially don't quote cygwin AT cygwin DOT com!
Jeff Hawk wrote:
Thorsten Kampe wrote:
\cygwin\usr\bin and \cygwin\usr\lib are /real/ directories created by
the initial Cygwin installation routine. He shouldn't delete those
directories - just keep them empty...
Not true...
I
OK, let's start over. I used the uninstall procedures on the website to
completely uninstall the software. I removed all previously downloaded
files, including setup.exe. I downloaded and ran setup.exe, chose a
different mirror (ftp.cise.ufl.edu), and downloaded and installed fresh.
I am still g
On Thu, 12 Apr 2007, Igor Peshansky wrote:
> On Thu, 12 Apr 2007, Dave Korn wrote:
>
> > On 12 April 2007 17:49, Jeff Hawk wrote:
> >
> > >> -Original Message-
> > >> From: Thorsten Kampe
> > >> Sent: Thursday, April 12, 2007 11:03 AM
> >
> > >> \cygwin\usr\bin and \cygwin\usr\lib are /rea
On Thu, 12 Apr 2007, Dave Korn wrote:
> On 12 April 2007 17:49, Jeff Hawk wrote:
>
> >> -Original Message-
> >> From: Thorsten Kampe
> >> Sent: Thursday, April 12, 2007 11:03 AM
>
> >> \cygwin\usr\bin and \cygwin\usr\lib are /real/ directories created by
> >> the initial Cygwin installatio
On 12 April 2007 17:49, Jeff Hawk wrote:
>> -Original Message-
>> From: Thorsten Kampe
>> Sent: Thursday, April 12, 2007 11:03 AM
>> \cygwin\usr\bin and \cygwin\usr\lib are /real/ directories created by
>> the initial Cygwin installation routine. He shouldn't delete those
>> directories -
On Thu, 12 Apr 2007, Jeff Hawk wrote:
> > -Original Message-
> > From: On Behalf
> > Of Thorsten Kampe
> > Sent: Thursday, April 12, 2007 11:03 AM
> > To: [EMAIL PROTECTED]
<http://cygwin.com/acronyms/#PCYMTNQREAIYR>. Thanks.
> >
> -Original Message-
> From: On Behalf
> Of Thorsten Kampe
> Sent: Thursday, April 12, 2007 11:03 AM
> To: [EMAIL PROTECTED]
> Subject: RE: bash: tar: command not found
>
>
> \cygwin\usr\bin and \cygwin\usr\lib are /real/ directories created by
> the initi
On Thu, 12 Apr 2007, Dave Korn wrote:
> [snip]
> This means that tar.exe has been unpacked into C:\cygwin\usr\bin.
> That's why setup thinks it's installed.
Not quite. Setup only uses /etc/setup to find out what packages are
installed. I suspect a corrupt package instead. That is not to say
On 12 April 2007 17:10, Cheney, Christian wrote:
>>> Did you even try typing /usr/bin/tar at any point?
> I thank you all for your help. Tar.exe does not exist in the /bin
> directory, or anywhere else under C:\cygwin. Winzip may have created
> the /usr/bin folder, but it didn't put anything in
>>Did you even try typing /usr/bin/tar at any point?
>>This means that tar.exe has been unpacked into C:\cygwin\usr\bin.
That's
>>why setup thinks it's installed. But you can't find it in your $PATH
or
>>anything, because when cygwin goes to look in /usr/bin (which is where
tar.exe
>>has been put
* Dave Korn (Thu, 12 Apr 2007 16:26:57 +0100)
> On 12 April 2007 16:19, Cheney, Christian wrote:
> >>> Don't extract things using non-Cygwin tools unless you really know what
> >>> you're doing (or have been told to do so). You can make a real mess doing
> >>> this.
> > I would've used CYGWIN, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Cheney, Christian on 4/12/2007 9:21 AM:
>>> How about running /usr/bin/tar? Sounds like you just don't have the
>>> PATH set up correctly?
> Unfortunately, there is nothing in the /usr/bin/ directory. Thanks,
> anyhew.
In a default cygw
On Thu, Apr 12, 2007 at 08:21:02AM -0700, Cheney, Christian wrote:
>>>How about running /usr/bin/tar? Sounds like you just don't have the
>>>PATH set up correctly?
>Unfortunately, there is nothing in the /usr/bin/ directory. Thanks,
>anyhew.
There is never anything in c:\cygwin\usr\bin.
Did you
On 12 April 2007 16:19, Cheney, Christian wrote:
>>> Don't extract things using non-Cygwin tools unless you really know what
>>> you're doing (or have been told to do so). You can make a real mess doing
>>> this.
> I would've used CYGWIN, but, unfortunately, tar didn't work ;)
You've destroyed
>>How about running /usr/bin/tar? Sounds like you just don't have the
>>PATH set up correctly?
Unfortunately, there is nothing in the /usr/bin/ directory. Thanks,
anyhew.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Doc
>>Don't extract things using non-Cygwin tools unless you really know
what
>>you're doing (or have been told to do so). You can make a real mess
doing
>>this.
I would've used CYGWIN, but, unfortunately, tar didn't work ;)
>>If you're saying by the above that you have c:\cygwin\bin\bunzip2.exe
>>an
On Wed, Apr 11, 2007 at 05:25:08PM -0700, Cheney, Christian wrote:
>>>Look in '/etc/postinstall' and see if there are any scripts there
>>>that don't end in ".done".
>There are none
>
>>>Also, check '/var/log/setup.log.full' for any messages that would
>>>indicate the problem.
>I can't see anythi
Cheney, Christian wrote:
Look in '/etc/postinstall' and see if there are any scripts there
that don't end in ".done".
There are none
Also, check '/var/log/setup.log.full' for any messages that would
indicate the problem.
I can't see anything. Take a look.
In the worst case, you can try run
>>Look in '/etc/postinstall' and see if there are any scripts there
>>that don't end in ".done".
There are none
>>Also, check '/var/log/setup.log.full' for any messages that would
>>indicate the problem.
I can't see anything. Take a look.
>>In the worst case, you can try running each of the sc
Cheney, Christian wrote:
I didn't see cygcheck output attached to your previous post.
Therefore,
you either did not follow the instructions, or your mailer is broken.
My bad :0)
OK, 'tar' is installed. Given your description of the problem and your
subsequent problems with reinstalling, I'
>>I didn't see cygcheck output attached to your previous post.
Therefore,
>>you either did not follow the instructions, or your mailer is broken.
My bad :0)
cygcheck.out
Description: cygcheck.out
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://c
Cheney, Christian wrote:
learn.to/quote <-- please do (no TOFU*, in particular)
And PCYMTNQREAIYR* while you are at it.
(*http://cygwin.com/acronyms)
Christopher Faylor wrote:
On Wed, Apr 11, 2007 at 01:57:33PM -0700, Cheney, Christian wrote:
I have installed cygwin on Windows XP using the d
Please expound. Been there, done that. Hence, the post.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Christopher Faylor
Sent: Wednesday, April 11, 2007 2:36 PM
To: cygwin@cygwin.com
Subject: Re: bash: tar: command not found
On Wed, Apr 11, 2007 at
On Wed, Apr 11, 2007 at 01:57:33PM -0700, Cheney, Christian wrote:
>I have installed cygwin on Windows XP using the default setup. When I
>try to use tar, I am getting "bash: tar: command not found." If I try
>to reinstall tar using the setup utility, it copies some files, but then
>gives a "no p
32 matches
Mail list logo
