I run cygwin on a variety of systems (Vista, 2k3, XP).
With the update to cron 4.1, my XP system now fails to process /etc/crontab
due to 'WRONG FILE OWNER', where it was working fine.
I have tried changing ownership to the following, all with the same results:
root:root
root:sy
Dave Korn, le Mon 23 Apr 2007 02:43:41 +0100, a écrit :
> Or you could follow the model of the ioperm package, which requires you to
> manually run "ioperm -i" to install the .sys file.
>
Brian Dessent, le Sun 22 Apr 2007 18:44:50 -0700, a écrit :
> I think it would be very bad to install a (ker
Samuel Thibault wrote:
> Yes of course (I actually call the uninstallation script at preremove).
> But the question is "do we dare installing a driver just because the
> user asked for package installation?".
>
> The problem is that libusb-win32 might be pulled as a dependency of
> another packag
On 23 April 2007 02:33, Samuel Thibault wrote:
> Yes of course (I actually call the uninstallation script at preremove).
> But the question is "do we dare installing a driver just because the
> user asked for package installation?".
>
> The problem is that libusb-win32 might be pulled as a depend
Hi,
Larry Hall (Cygwin), le Sun 22 Apr 2007 21:25:50 -0400, a écrit :
> The final decision is, of course, yours but I would say that if it's
> really just an installation step, there's nothing technically stopping
> you from performing the step automatically through a postinstall script,
> for exa
Brian Dessent wrote:
> > The workaround for this problem that I have found is to set the
> > *Windows* path to include C:\cygwin\bin before running setup.exe. So
> > for example this sequence works:
> >
> > set PATH=C:\cygwin\bin;%PATH%
> > setup.exe
> >
> > Then /bin/sh is actually created, the
Samuel Thibault wrote:
> Hi,
>
> Larry Hall (Cygwin), le Sun 22 Apr 2007 11:14:07 -0400, a écrit :
>> A good reason for this division is to allow for user input during the
>> configuration step, which "setup.exe" doesn't have support for.
>
> It doesn't need user input.
>
>> If running your libu
[Samuel Thibault]
In a ./configure script, I call a test program (native python, actually)
that outputs "True\r\n" and I put this result in variable foo. The
problem is that [ "$foo" = True ] doesn't return true because foo
actually contains True\r, not True.
[Michael Hoffman]
* [ ${foo/%$'\r'
On 23 April 2007 00:16, Morgan Gangwere wrote:
> On 4/22/07, Samuel Thibault wrote:
On 22 April 2007 14:49, Morgan Gangwere wrote:
> On 4/22/07, Brian Dessent wrote:
On 22 April 2007 15:45, Morgan Gangwere wrote:
> On 4/22/07, Samuel Thibault ens-lyon.org> wrote:
:-) Thank you Morgan!
On 4/22/07, Samuel Thibault wrote:
Hi,
Larry Hall (Cygwin), le Sun 22 Apr 2007 11:14:07 -0400, a écrit :
> A good reason for this division is to allow for user input during the
> configuration step, which "setup.exe" doesn't have support for.
It doesn't need user input.
> If running your libu
On 22 April 2007 23:32, sethk wrote:
> I've had some success using a different version of zsh on vista.
>
> In the UnxUtils package, there is a version of zsh, named sh. (Not copied
> or linked to zsh, for whatever reason, and, I should say, named sh.exe.)
>
> I created a shortcut for this exec
I've had some success using a different version of zsh on vista.
In the UnxUtils package, there is a version of zsh, named sh. (Not copied
or linked to zsh, for whatever reason, and, I should say, named sh.exe.)
I created a shortcut for this executable. It mostly works. I'm having some
issues
On Sun, Apr 22, 2007 at 06:40:29PM +0100, Michael Hoffman wrote:
>Samuel Thibault wrote:
>>Hi,
>>
>>In a ./configure script, I call a test program (native python, actually)
>>that outputs "True\r\n" and I put this result in variable foo. The
>>problem is that [ "$foo" = True ] doesn't return true b
Samuel Thibault wrote:
> In a ./configure script, I call a test program (native python, actually)
> that outputs "True\r\n" and I put this result in variable foo. The
> problem is that [ "$foo" = True ] doesn't return true because foo
> actually contains True\r, not True.
$foo=$(python command |
"Michael D. Adams" wrote:
> > Please try the latest setup.exe snapshot, if you can. And even better
> > would be to debug the problem. I don't have access to a Vista system
> > but if I did I think I would start by running it under gdb/insight and
> > putting a breakpoint at script.cc:run() righ
Michael Hoffman, le Sun 22 Apr 2007 18:40:29 +0100, a écrit :
> >In a ./configure script, I call a test program (native python, actually)
> >that outputs "True\r\n" and I put this result in variable foo. The
> >problem is that [ "$foo" = True ] doesn't return true because foo
> >actually contains T
Samuel Thibault wrote:
Hi,
In a ./configure script, I call a test program (native python, actually)
that outputs "True\r\n" and I put this result in variable foo. The
problem is that [ "$foo" = True ] doesn't return true because foo
actually contains True\r, not True.
Is there a nice way around
Hi,
In a ./configure script, I call a test program (native python, actually)
that outputs "True\r\n" and I put this result in variable foo. The
problem is that [ "$foo" = True ] doesn't return true because foo
actually contains True\r, not True.
Is there a nice way around this?
Samuel
--
Unsubs
Samuel Thibault wrote:
> Hi,
>
> Installing my libusb-win32 package doesn't automatically install the USB
> driver, the user has to run /usr/sbin/libusb-install. I preferred to go
> this way for safety.
>
> However, some user reported that it would be better that the
> installation is automatica
On 4/22/07, Brian Dessent <[EMAIL PROTECTED]> wrote:
"Michael D. Adams" wrote:
> The workaround for this problem that I have found is to set the
> *Windows* path to include C:\cygwin\bin before running setup.exe. So
> for example this sequence works:
>
> set PATH=C:\cygwin\bin;%PATH%
> setup.ex
Brian Dessent wrote:
"Michael D. Adams" wrote:
he workaround for this problem that I have found is to set the
*Windows* path to include C:\cygwin\bin before running setup.exe. So
for example this sequence works:
set PATH=C:\cygwin\bin;%PATH%
setup.exe
Then /bin/sh is actually created, the pro
On 4/22/07, Michael D. Adams <[EMAIL PROTECTED]> wrote:
On 4/22/07, Brian Dessent <[EMAIL PROTECTED]> wrote:
> "Michael D. Adams" wrote:
>
> > The workaround for this problem that I have found is to set the
> > *Windows* path to include C:\cygwin\bin before running setup.exe. So
> > for example
On 4/22/07, Brian Dessent wrote:
"Michael D. Adams" wrote:
> The workaround for this problem that I have found is to set the
> *Windows* path to include C:\cygwin\bin before running setup.exe. So
> for example this sequence works:
>
> set PATH=C:\cygwin\bin;%PATH%
> setup.exe
[Snip]
That wou
Hi,
Installing my libusb-win32 package doesn't automatically install the USB
driver, the user has to run /usr/sbin/libusb-install. I preferred to go
this way for safety.
However, some user reported that it would be better that the
installation is automatically performed (since if one installs
li
Hi,
Larry Hall (Cygwin), le Sun 22 Apr 2007 11:14:07 -0400, a écrit :
> A good reason for this division is to allow for user input during the
> configuration step, which "setup.exe" doesn't have support for.
It doesn't need user input.
> If running your libusb-install is more like a configuratio
On 2007-04-22 14:38Z, Michael D. Adams wrote:
> On 4/22/07, Brian Dessent
[raw email address removed]
> wrote:
>>
>> Please try the latest setup.exe snapshot, if you can. And even better
>> would be to debug the problem.
[...]
> Where are those snapshots located? A quick google didn't turn them
Hi,
Morgan Gangwere, le Sun 22 Apr 2007 08:44:55 -0600, a écrit :
> On 4/22/07, Samuel Thibault ens-lyon.org> wrote:
> >Installing my libusb-win32 package doesn't automatically install the USB
> >driver, the user has to run /usr/sbin/libusb-install. I preferred to go
> >this way for safety.
> >
>
On 4/22/07, Samuel Thibault ens-lyon.org> wrote:
Hi,
Installing my libusb-win32 package doesn't automatically install the USB
driver, the user has to run /usr/sbin/libusb-install. I preferred to go
this way for safety.
However, some user reported that it would be better that the
installation i
28 matches
Mail list logo
