Hi,
I started to use Cygwin recently. I'm having a problem with
authentication. I cannot login unless the user belongs to DomainAdmins
group.
I haven't modified my installation anyway. After installation I have
just added cygwin/bin directory to path environment variable and added
new environment
On 11/14/2003 5:42 PM, Randy W. Sims wrote:
> There is still a problem to be worked out, but I'm not yet sure where
the problem is. Can you tell post your perl & Cwd version.
>
> Dave, What versions of perl, Cwd, & M::B have you tested Alzabo with?
>
> This problem doesn't seem directly related t
On Sat, Nov 15, 2003 at 07:07:26PM +1100, Robert Collins wrote:
>On Sat, 2003-11-15 at 15:43, Christopher Faylor wrote:
>>Yes, I've already (obviously?) been to SUSv3. I wasn't talking about
>>standards. I was talking about common practice.
>>
>>If you have a common practice web site that you wan
On Sat, Nov 15, 2003 at 11:45:34AM -0500, Christopher Faylor wrote:
>On Sat, Nov 15, 2003 at 07:07:26PM +1100, Robert Collins wrote:
>>On Sat, 2003-11-15 at 15:43, Christopher Faylor wrote:
>>>Yes, I've already (obviously?) been to SUSv3. I wasn't talking about
>>>standards. I was talking about c
On Sat, 15 Nov 2003, Lorenzo Travaglio wrote:
> > Ugh. Again, what OS and what filesystem, and:
> Sorry. Win98.
>
And FAT32, and did you read these?
> Brian Ford wrote:
> > More likely, you are running an NT variant at work and 9x at home? See:
> >
> > http://cygwin.com/faq/faq_toc.html#TOC45 a
On Sat, Nov 15, 2003 at 11:21:41AM -0600, Brian Ford wrote:
>I'm sorry for being grumpy, but I just don't know what's left to tell.
>I guess WJM rubs off quickly, huh?
It's the subliminal messages we put in the cygwin DLL source code. As
soon as you start to become more knowledgeable about cygwin
I am having trouble mounting a linking to a directory. The mounted file
doesn't go to "/" as I specified in the mount command instead it goes to
/cygdrive/c/Documents\ and\ Settings/erica. What am I doing wrong? This is
what I do:
$ mount -tf "c:\PalmDev" /PalmDev
$ ln -s "C:\Palm OS 5 SDK (6
Why do I feel like I'm watching an Ed Wood movie?
Thank God you guys write better code than you do comedy.
Suggested ad copy for "attracting" more non-contributing end-users:
Cygwin! - Come for the software, stay for the BERATEMENT!
:-l
bits and bytes may break my code, but your 'word's will n
On Sat, 15 Nov 2003, Christopher Faylor wrote:
> Btw, I've moved this discussion here from cygwin-patches because we are
> talking about a change which could impact a number of people. Robert is
> submitting patches which increase the maximum path length for NT-class
> systems.
>
> My concern is
On Sat, Nov 15, 2003 at 01:37:04PM -0500, Brian Kelly wrote:
>Why do I feel like I'm watching an Ed Wood movie?
>
>Thank God you guys write better code than you do comedy.
>
>Suggested ad copy for "attracting" more non-contributing end-users:
>
>Cygwin! - Come for the software, stay for the BERATEM
On Sat, Nov 15, 2003 at 01:09:00PM -0600, Brian Ford wrote:
>On Sat, 15 Nov 2003, Christopher Faylor wrote:
>
>> Btw, I've moved this discussion here from cygwin-patches because we are
>> talking about a change which could impact a number of people. Robert is
>> submitting patches which increase t
On Sat, 15 Nov 2003, Christopher Faylor wrote:
> On Sat, Nov 15, 2003 at 01:09:00PM -0600, Brian Ford wrote:
> >Well, since your soliciting opinions...
> >
> >I don't have much of one other than I'd really prefer to keep
> >PATH_MAX/MAX_PATH and define them to the largest allowable path so they
>
BRAVO!
My hearty congratulations to Mr. Ford.
I'm sure it will look good on his resume.
>>> *I was actually given Brian Ford*
I thought slavery in this country ended with the Civil War, or is Mr. Ford
a form of *artificial intelligence*?
Anyhow - how much do you want for him/it?
;-D
-bk
On Sat, 15 Nov 2003 [EMAIL PROTECTED] wrote:
> BRAVO!
>
> My hearty congratulations to Mr. Ford.
>
> I'm sure it will look good on his resume.
>
> >>> *I was actually given Brian Ford*
>
> I thought slavery in this country ended with the Civil War, or is Mr. Ford
> a form of *artificial intellige
> Anyway, can we *please* just drop this noise now.
Agreed - enough.
> I'll gladly relinquish it if it'll make you feel better.
HECK NO!! cgf doesn't give those out every day - and besides, in my not
so humble opinion you've contributed MORE than enough to deserve one
outside of this *noise* - a
On Sun, 2003-11-16 at 06:09, Brian Ford wrote:
> On Sat, 15 Nov 2003, Christopher Faylor wrote:
>
> > Btw, I've moved this discussion here from cygwin-patches because we are
> > talking about a change which could impact a number of people. Robert is
> > submitting patches which increase the maxim
On Wed, 2003-11-05 at 08:06, Christian Weinberger wrote:
> After some investigation I found an interim solution to get the current
> cygwin squid version (2.4-STABLE7) working with the new 1.5 DLL series.
> This has been tested and works for me with 1.5.5, but should work with
> all 1.5 versions
> It doesn't. Cygwin != Linux.
>
> Also, AFAIK, if a Linux application is directly including linux/*, it is
> broken.
Not necessarily. Not every application is designed to work across different
platforms. Sometimes a programmer may choice to sacrifice portability for
some other advantage. In f
On Fri, Nov 14, 2003 at 11:32:58PM -0500, Christopher Faylor wrote:
> Lets recap:
> 1) X posts a message about a non-cygwin topic
Sorry, but X postings are off-topic for this list.
(ducks)
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com
On Sat, Nov 15, 2003 at 03:39:36PM -0600, Joshua Daniel Franklin wrote:
>On Fri, Nov 14, 2003 at 11:32:58PM -0500, Christopher Faylor wrote:
>> Lets recap:
>> 1) X posts a message about a non-cygwin topic
>
>Sorry, but X postings are off-topic for this list.
>
>(ducks)
Heh. Probably the funniest
Before the upgrade to 1.5* - 64 bit cygwin, this used to compile with the
default configuration just fine.
Now it can't. I am aware that the entire perl IPC distribution never did
ever work with cygwin - especially named pipes. However, the Semaphore
module *did* - and before the 1.5* upgrade, comp
Oops!! My goof - I meant Win32::Semaphore. DOH!
-bk
[EMAIL PROTECTED]@cygwin.com on 11/15/2003 05:10:54 PM
Sent by:[EMAIL PROTECTED]
To:[EMAIL PROTECTED]
cc: (bcc: Brian Kelly/WTC1/Empire)
Subject:cpan/gcc cannot compile perl module after cygwin 1.5*
Before the upgrade t
Before the upgrade to 1.5* - 64 bit cygwin, this used to compile with the
default configuration just fine. Now it can't. I am aware that the entire
perl libwin32-0.191 distribution never did work completely with cygwin -
especially named pipes. However, the Win32::Semaphore module *did* - and
befor
On Sun, 2003-11-16 at 09:41, [EMAIL PROTECTED] wrote:
> Of course I'm aware that cygwin is now *64* bit compiled, and that I'm
> looking to compile a *32* bit module. So I guess my first question, is
> there backward compatibilty? And, if there is, how can I invoke it for
> successful compilation?
Hello all
Something just happened with my Cygwin installation. I just had to
reinstall Cygwin from the net because I accidentally broke some things.
Anyway, the reason doesn't matter.
The install went apparently fine until I noticed to absence of the Bin
directory. I've looked on Google for tha
25 matches
Mail list logo
