screen [ping cgf]

screen [ping cgf]

[Andrew Schulman]

> Will this have any impact on having a version of screen that works?

I have a working version of screen on Cygwin.  I use it daily, and it works
fine.  With CYGWIN=tty set, the reattachment bug appears to be solved; it
detaches and reattaches sessions normally, which was a problem for a long
time.  Not many patches are needed any more.  More patches used to be
required, one of which was specific to Win9x, but I believe that
improvements in the Cygwin DLL have rendered those unnecessary now.

At this point I know of only one main outstanding bug in screen:  when you
kill a window or the whole screen session, the child processes aren't
killed.  They hang around and you have to kill them manually.

screen is an extremely useful program, that people have been asking for in
Cygwin for a long time.  I'd be willing to package it, but when I floated
the idea a year ago or so, the feeling seemed to be that there were still
too many bugs to make it useful.  If people can live with (or even better,
test and help me try to fix) the unkilled-child-process bug, then I'm
willing.  I could release it as a test version.

Yes?  No?
A.

--
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: screen [ping cgf]

[Christopher Faylor]

On Thu, Feb 15, 2007 at 04:27:22PM -0500, Andrew Schulman wrote:
>> Will this have any impact on having a version of screen that works?
>
>I have a working version of screen on Cygwin.  I use it daily, and it works
>fine.  With CYGWIN=tty set, the reattachment bug appears to be solved; it
>detaches and reattaches sessions normally, which was a problem for a long
>time.  Not many patches are needed any more.  More patches used to be
>required, one of which was specific to Win9x, but I believe that
>improvements in the Cygwin DLL have rendered those unnecessary now.
>
>At this point I know of only one main outstanding bug in screen:  when you
>kill a window or the whole screen session, the child processes aren't
>killed.  They hang around and you have to kill them manually.
>
>screen is an extremely useful program, that people have been asking for in
>Cygwin for a long time.  I'd be willing to package it, but when I floated
>the idea a year ago or so, the feeling seemed to be that there were still
>too many bugs to make it useful.  If people can live with (or even better,
>test and help me try to fix) the unkilled-child-process bug, then I'm
>willing.  I could release it as a test version.
>
>Yes?  No?

What do I have to do with this?  If you are responding to something that
I said then please post a reference and don't leave everyone guessing.

Otherwise propose to package it using the standard procedure.

cgf

--
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: screen [ping cgf]

[Andrew Schulman]

> >screen is an extremely useful program, that people have been asking for in
> >Cygwin for a long time.  I'd be willing to package it, but when I floated
> >the idea a year ago or so, the feeling seemed to be that there were still
> >too many bugs to make it useful.  If people can live with (or even better,
> >test and help me try to fix) the unkilled-child-process bug, then I'm
> >willing.  I could release it as a test version.
> >
> >Yes?  No?
> 
> What do I have to do with this?  If you are responding to something that
> I said then please post a reference and don't leave everyone guessing.

I was imagining that you would remember the conversation.

http://www.cygwin.com/ml/cygwin-apps/2005-04/msg00183.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: screen [ping cgf]

[Christopher Faylor]

On Thu, Feb 15, 2007 at 08:16:02PM -0500, Andrew Schulman wrote:
>> >screen is an extremely useful program, that people have been asking for in
>> >Cygwin for a long time.  I'd be willing to package it, but when I floated
>> >the idea a year ago or so, the feeling seemed to be that there were still
>> >too many bugs to make it useful.  If people can live with (or even better,
>> >test and help me try to fix) the unkilled-child-process bug, then I'm
>> >willing.  I could release it as a test version.
>> >
>> >Yes?  No?
>> 
>> What do I have to do with this?  If you are responding to something that
>> I said then please post a reference and don't leave everyone guessing.
>
>I was imagining that you would remember the conversation.

...from almost two years ago.  Uh huh.

>http://www.cygwin.com/ml/cygwin-apps/2005-04/msg00183.html

So, as I so wisely said two years ago: If you can't use one of the major
features of screen, it doesn't sound like the package is ready for prime
time.

And, just in case you're wondering if I am going to volunteer to help you
track down problems - I'm not.  So, maybe anyone who wants screen should
volunteer to help.

cgf

--
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: screen [ping cgf]

[Frank Fesevur]

Andrew Schulman wrote:
> screen is an extremely useful program, that people have been asking for in
> Cygwin for a long time.  I'd be willing to package it, but when I floated
> the idea a year ago or so, the feeling seemed to be that there were still
> too many bugs to make it useful.  If people can live with (or even better,
> test and help me try to fix) the unkilled-child-process bug, then I'm
> willing.  I could release it as a test version.

Could you post a link to your latest build (and sources), so people can 
test and comment on it.

And that unkilled-child-process bug... Isn't that similar to the rxvt 
bug that was fixed here: 
http://sourceware.org/ml/cygwin-announce/2006-12/msg00018.html

Regards,
Frank

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

[Andrew Schulman]

> And, just in case you're wondering if I am going to volunteer to help you
> track down problems - I'm not.  So, maybe anyone who wants screen should
> volunteer to help.

No, that was not my intention.  I was trying to be courteous.  But that's a
two-way street.  Forget it, I won't bother next time.


--
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: screen [ping cgf]

[Andrew Schulman]

> Could you post a link to your latest build (and sources), so people can 
> test and comment on it.

Sure:

http://home.comcast.net/~andrex/cygwin/screen/setup.hint
http://home.comcast.net/~andrex/cygwin/screen/screen-4.0.2-0test1.tar.bz2
http://home.comcast.net/~andrex/cygwin/screen/screen-4.0.2-0test1-src.tar.bz2

> And that unkilled-child-process bug... Isn't that similar to the rxvt 
> bug that was fixed here: 
> http://sourceware.org/ml/cygwin-announce/2006-12/msg00018.html

Thanks, this is helpful.  I'll look into it.
Andrew.


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

[Christopher Faylor]

On Fri, Feb 16, 2007 at 01:01:23PM -0500, Andrew Schulman wrote:
>> And, just in case you're wondering if I am going to volunteer to help you
>> track down problems - I'm not.  So, maybe anyone who wants screen should
>> volunteer to help.
>
>No, that was not my intention.  I was trying to be courteous.  But that's a
>two-way street.  Forget it, I won't bother next time.

Since you were pinging me and since (on rereading) you were consistently
asking for help, I don't think it was a huge leap for me to surmise that
you might be wanting my help debugging problems.  By stating my
intentions, I wanted to make it clear that someone else needs to step
in.

cgf

--
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: screen [ping cgf]

[Frank Fesevur]

At 16-2-2007 19:10, Andrew Schulman wrote:
>> Could you post a link to your latest build (and sources), so people can 
>> test and comment on it.
> 
> Sure:
> 
> http://home.comcast.net/~andrex/cygwin/screen/setup.hint
> http://home.comcast.net/~andrex/cygwin/screen/screen-4.0.2-0test1.tar.bz2
> http://home.comcast.net/~andrex/cygwin/screen/screen-4.0.2-0test1-src.tar.bz2

I have just tried it and so far it works for me. Although I must admit I 
have only used it very limited. But a colleague just mailed that he 
could not detach/retach :-S

One thing I notices about the package, the etc/postinstall/screen.sh is 
in CRLF, so you need to dos2unix it.

Regards,
Frank


--
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: screen [ping cgf]

[Thorsten Kampe]

* Andrew Schulman (Fri, 16 Feb 2007 13:10:47 -0500)
> > Could you post a link to your latest build (and sources), so people can 
> > test and comment on it.
> 
> Sure:
> 
> http://home.comcast.net/~andrex/cygwin/screen/setup.hint
> http://home.comcast.net/~andrex/cygwin/screen/screen-4.0.2-0test1.tar.bz2
> http://home.comcast.net/~andrex/cygwin/screen/screen-4.0.2-0test1-src.tar.bz2
> 
> > And that unkilled-child-process bug... Isn't that similar to the rxvt 
> > bug that was fixed here: 
> > http://sourceware.org/ml/cygwin-announce/2006-12/msg00018.html
> 
> Thanks, this is helpful.  I'll look into it.

Can't run screen from a portable FAT32 drive:
Directory '/tmp/uscreens' must have mode 777.

"chmod -R 777 /tmp/uscreens" doesn't work but "rm -rf /tmp/uscreens" 
works - but only until the next start of screen...

Thorsten


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

[Christopher Layne]

On Fri, Feb 16, 2007 at 04:14:06PM -0500, Christopher Faylor wrote:
> On Fri, Feb 16, 2007 at 01:01:23PM -0500, Andrew Schulman wrote:
> >> And, just in case you're wondering if I am going to volunteer to help you
> >> track down problems - I'm not.  So, maybe anyone who wants screen should
> >> volunteer to help.
> >
> >No, that was not my intention.  I was trying to be courteous.  But that's a
> >two-way street.  Forget it, I won't bother next time.
> 
> Since you were pinging me and since (on rereading) you were consistently
> asking for help, I don't think it was a huge leap for me to surmise that
> you might be wanting my help debugging problems.  By stating my
> intentions, I wanted to make it clear that someone else needs to step
> in.
> 
> cgf

You know this kind of things just shuts people off and turns them away right?
People are trying to make progress, trying to make things better, and they're
basically being told to go away. If he could do it himself, I'm sure he would
have solved the issue by now. If he can't, perhaps he needs the help. I don't
see what's so groundbreaking about "I'm not going to be able to help you with
it now as I'm too busy, but perhaps throw the idea out there along with your
observations and see who else bites." Is that somehow worse than "Look, I don't
have the time to help you track down problems, find someone else." ?

-cl

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

[Christopher Faylor]

On Sun, Feb 18, 2007 at 08:29:41AM -0800, Christopher Layne wrote:
>On Fri, Feb 16, 2007 at 04:14:06PM -0500, Christopher Faylor wrote:
>> On Fri, Feb 16, 2007 at 01:01:23PM -0500, Andrew Schulman wrote:
>> >> And, just in case you're wondering if I am going to volunteer to help you
>> >> track down problems - I'm not.  So, maybe anyone who wants screen should
>> >> volunteer to help.
>> >
>> >No, that was not my intention.  I was trying to be courteous.  But that's a
>> >two-way street.  Forget it, I won't bother next time.
>> 
>> Since you were pinging me and since (on rereading) you were consistently
>> asking for help, I don't think it was a huge leap for me to surmise that
>> you might be wanting my help debugging problems.  By stating my
>> intentions, I wanted to make it clear that someone else needs to step
>> in.
>
>You know this kind of things just shuts people off and turns them away right?
>People are trying to make progress, trying to make things better, and they're
>basically being told to go away. If he could do it himself, I'm sure he would
>have solved the issue by now. If he can't, perhaps he needs the help. I don't
>see what's so groundbreaking about "I'm not going to be able to help you with
>it now as I'm too busy, but perhaps throw the idea out there along with your
>observations and see who else bites." Is that somehow worse than "Look, I don't
>have the time to help you track down problems, find someone else." ?

Moved to the talk list.

cgf

--
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: screen [ping cgf]

[Frank Fesevur]

At 16-2-2007 22:38, Frank Fesevur wrote:
> I have just tried it and so far it works for me. Although I must admit I 
> have only used it very limited. But a colleague just mailed that he 
> could not detach/retach :-S

This detach/retach problem seems to be caused by an incomplete uninstall 
of an older test version. After upgrading to the latest cygwin dll 
version and making sure he was running your latest build of screen, it 
seems to work fine now.

Regards,
Frank


--
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: screen [ping cgf]

[Andrew Schulman]

> At 16-2-2007 22:38, Frank Fesevur wrote:
> > I have just tried it and so far it works for me. Although I must admit I 
> > have only used it very limited. But a colleague just mailed that he 
> > could not detach/retach :-S
> 
> This detach/retach problem seems to be caused by an incomplete uninstall 
> of an older test version. After upgrading to the latest cygwin dll 
> version and making sure he was running your latest build of screen, it 
> seems to work fine now.

Excellent!  I'll keep on hoping for the best on that problem.  The
detach/retach problem persisted for years.  I looked at it for a while but
it was way beyond my skill to fix, and no one ever did fix it as such, i.e.
there was never a patch offered to fix it.  But AFAICT it's fixed now,
presumably because of improvements in the Cygwin DLL.


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

[Andrew Schulman]

>> Yes, the reattachment problem is now solved AFAICT, using Cygwin 1.5.17 or 
>> later.  Most of it works just fine, but there's one problem that I haven't 
>> solved yet:  when you detach a session, it stays bound to its parent 
>> shell.  So if you then try to exit the parent shell, it hangs.  You can 
>> terminate the parent shell, but then screen exits too.  Obviously this 
>> takes away one of the big advantages of screen, which is the ability to 
>> detach a session, leaving it running in the background, and then reattach 
>> later from a different terminal.
> 
> hmm I have not had that problem? I run rxvt's with bash and can exit all
> terminals leaving no bash process but screen lives on. I can then fire
> up another shell and re-connect to screen and any jobs it has running.
> (ie it works just like it should!)

Interesting.  Okay, I hadn't noticed this before, but the problem does
seem to be particular to the Cygwin console.  It doesn't occur with
rxvt.  Also, it doesn't occur in the Cygwin console if I start a
subshell first, and invoke screen from there.  Maybe useful to know.
Still, I do want to solve the problem before I release screen.


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

[Shaun Broadbent]

Andrew.Schulman wrote
-------------------

> OK.  I later changed the version number from 1 to 0test1, so the URLs for 
> download are now
> 
> http://home.comcast.net/~andrex/cygwin/screen/screen-4.0.2-0test1.tar.bz2 
> (binary)
> http://home.comcast.net/~andrex/cygwin/screen/screen-4.0.2-0test1-src.tar.bz2 
> (source)

Thank you for that.

> Yes, the reattachment problem is now solved AFAICT, using Cygwin 1.5.17 or 
> later.  Most of it works just fine, but there's one problem that I haven't 
> solved yet:  when you detach a session, it stays bound to its parent 
> shell.  So if you then try to exit the parent shell, it hangs.  You can 
> terminate the parent shell, but then screen exits too.  Obviously this 
> takes away one of the big advantages of screen, which is the ability to 
> detach a session, leaving it running in the background, and then reattach 
> later from a different terminal.

hmm I have not had that problem? I run rxvt's with bash and can exit all
terminals leaving no bash process but screen lives on. I can then fire
up another shell and re-connect to screen and any jobs it has running.
(ie it works just like it should!)

- Shaun

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

screen

[Schulman.Andrew]

> Firstly I apologize for emailing you directly, I am not familiar with
> posting to cygwin and couldn't see any other way to get in touch.

No problem, but the approved method is to send your query to cygwin a 
cygwin d com, with "screen" in the subject.  I should normally see that, 
and then other cygwin readers will also benefit from the discussion.

> I am just trying to get hold of your screen build that you posted.
> It seems to not be available any more via
> http://home.comcast.net/~andrex/cygwin/screen/screen-4.0.2-1.tar.bz2

OK.  I later changed the version number from 1 to 0test1, so the URLs for 
download are now

http://home.comcast.net/~andrex/cygwin/screen/screen-4.0.2-0test1.tar.bz2 
(binary)
http://home.comcast.net/~andrex/cygwin/screen/screen-4.0.2-0test1-src.tar.bz2 
(source)
 
> I have been using it on a few pc's and would like to install it on
> another but have stupidly deleted the package.
> BTW it seems to work very well for me once I switched to a snapshot dll.
> I Can detach,re-attach with no problems (all pc's running xp sp2)

Yes, the reattachment problem is now solved AFAICT, using Cygwin 1.5.17 or 
later.  Most of it works just fine, but there's one problem that I haven't 
solved yet:  when you detach a session, it stays bound to its parent 
shell.  So if you then try to exit the parent shell, it hangs.  You can 
terminate the parent shell, but then screen exits too.  Obviously this 
takes away one of the big advantages of screen, which is the ability to 
detach a session, leaving it running in the background, and then reattach 
later from a different terminal.

I've gotten some hints about how to attack this problem, but I just 
haven't been able to spend any time on it yet.  It's high on my to-do 
list.  Screen is great, and if I can solve that one problem it will be 
ready for Cygwin.

There are also a few terminal oddities and intermittent display problems. 
But these are minor, so I don't think I'll wait for them to release the 
package.  At least, I can put it into testing so people can try it out 
while I work on resolving the other problems.

> Thanks
> 
> - Shaun


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

[Karsten M. Self]

on Tue, Apr 29, 2003 at 03:57:37PM -0400, Igor Pechtchanski (pechtcha@cs.nyu.edu) wrote:
> On Tue, 29 Apr 2003, Karsten M. Self wrote:
> 
> > on Sat, Apr 26, 2003 at 11:25:20AM +0200, Cant (cant_reed@yahoo.com) wrote:
> > > How come when i use screen and i want to detach the screen then re-attach it
> > > again it says this...
> > >
> > > $ screen -r
> > > There is a screen on:
> > > There is no screen to be resumed.
> > > $ ps x
> > >       PID    PPID    PGID     WINPID  TTY  UID    STIME COMMAND
> > >      3264       1    3264       3264    ? 1012 11:21:33
> > > /home/Cant/screen-3.9.15/screen
> > >      3276    3264    3276       3232    1 1012 11:21:34 /usr/bin/tcsh
> > >       212    3276     212        340    1 1012 11:21:40 /usr/bin/links
> > >      1556    3520    1556       1580    0 1012 11:22:43 /usr/bin/tcsh
> > >      1576    1556    1576       2072    0 1012 11:23:23 /usr/bin/ps
> > > $
> > >
> > > the links is in the screen session and i cant re-attach it in order to get
> > > back to it... ]; any ideas?
> >
> > I'd love to have your problem.  Where'd  you find 'screen'?
> >
> > Try 'screen -ls' to list currently active screen sessions.  It's
> > possible that the cygwin port is borked.
> >
> > Peace.
> 
> There is no Cygwin port (or an official package) of screen.  I posted a
> patch a while ago that would make it compile (and sort of run).  It's
> possible that screen relies on some features that aren't portable.

Ah.  I remember using it at one point, and noting that it didn't work
particularly well....

Peace.

-- 
Karsten M. Self <kmself@ix.netcom.com>        http://kmself.home.netcom.com/
 What Part of "Gestalt" don't you understand?
   The Consumer Broadband and Digital Television Promotion Act:
     Feinstein's answer to Enron envy.
       http://www.politechbot.com/docs/cbdtpa/hollings.s2048.032102.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: screen

[Igor Pechtchanski]

On Tue, 29 Apr 2003, Karsten M. Self wrote:

> on Sat, Apr 26, 2003 at 11:25:20AM +0200, Cant (cant_reed@yahoo.com) wrote:
> > How come when i use screen and i want to detach the screen then re-attach it
> > again it says this...
> >
> > $ screen -r
> > There is a screen on:
> > There is no screen to be resumed.
> > $ ps x
> >       PID    PPID    PGID     WINPID  TTY  UID    STIME COMMAND
> >      3264       1    3264       3264    ? 1012 11:21:33
> > /home/Cant/screen-3.9.15/screen
> >      3276    3264    3276       3232    1 1012 11:21:34 /usr/bin/tcsh
> >       212    3276     212        340    1 1012 11:21:40 /usr/bin/links
> >      1556    3520    1556       1580    0 1012 11:22:43 /usr/bin/tcsh
> >      1576    1556    1576       2072    0 1012 11:23:23 /usr/bin/ps
> > $
> >
> > the links is in the screen session and i cant re-attach it in order to get
> > back to it... ]; any ideas?
>
> I'd love to have your problem.  Where'd  you find 'screen'?
>
> Try 'screen -ls' to list currently active screen sessions.  It's
> possible that the cygwin port is borked.
>
> Peace.

There is no Cygwin port (or an official package) of screen.  I posted a
patch a while ago that would make it compile (and sort of run).  It's
possible that screen relies on some features that aren't portable.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Knowledge is an unending adventure at the edge of uncertainty.
  -- Leto II


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

[Karsten M. Self]

on Sat, Apr 26, 2003 at 11:25:20AM +0200, Cant (cant_reed@yahoo.com) wrote:
> How come when i use screen and i want to detach the screen then re-attach it
> again it says this...
> 
> $ screen -r
> There is a screen on:
> There is no screen to be resumed.
> $ ps x
>       PID    PPID    PGID     WINPID  TTY  UID    STIME COMMAND
>      3264       1    3264       3264    ? 1012 11:21:33
> /home/Cant/screen-3.9.15/screen
>      3276    3264    3276       3232    1 1012 11:21:34 /usr/bin/tcsh
>       212    3276     212        340    1 1012 11:21:40 /usr/bin/links
>      1556    3520    1556       1580    0 1012 11:22:43 /usr/bin/tcsh
>      1576    1556    1576       2072    0 1012 11:23:23 /usr/bin/ps
> $
> 
> the links is in the screen session and i cant re-attach it in order to get
> back to it... ]; any ideas?

I'd love to have your problem.  Where'd  you find 'screen'?

Try 'screen -ls' to list currently active screen sessions.  It's 
possible that the cygwin port is borked.

Peace.

-- 
Karsten M. Self <kmself@ix.netcom.com>        http://kmself.home.netcom.com/
 What Part of "Gestalt" don't you understand?
    SCO is the thief who puts a gun to his own head and says give me
    your money or I'll shoot.
    -- Bruce Perens  http://slashdot.org/comments.pl?sid=56225&&cid=5456337

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

screen

[Cant]

How come when i use screen and i want to detach the screen then re-attach it
again it says this...

$ screen -r
There is a screen on:
There is no screen to be resumed.
$ ps x
      PID    PPID    PGID     WINPID  TTY  UID    STIME COMMAND
     3264       1    3264       3264    ? 1012 11:21:33
/home/Cant/screen-3.9.15/screen
     3276    3264    3276       3232    1 1012 11:21:34 /usr/bin/tcsh
      212    3276     212        340    1 1012 11:21:40 /usr/bin/links
     1556    3520    1556       1580    0 1012 11:22:43 /usr/bin/tcsh
     1576    1556    1576       2072    0 1012 11:23:23 /usr/bin/ps
$

the links is in the screen session and i cant re-attach it in order to get
back to it... ]; any ideas?

--
---------------------------------------------------------------
brian AT nkjo DOT torun DOT pOlAND
You got questions? We got mean-ass otters with two middle fingers...!
---------------------------------------------------------------




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

[Cant]

[;




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: screen

[Cant]

well great it worked... wonderful except when i go to detach i cant reattach
it again... any more thoughts...?

ps. aha... very funny...

Uzytkownik "Igor Pechtchanski" <pechtcha@cs.nyu.edu> napisal w wiadomosci
news:Pine.GSO.4.44.0304112001180.26381-100000@slinky.cs.nyu.edu...
> Try "patch -p0 < patchfile" from the screen source directory.  Be
> prepared, thought, that it might reject some chunks...  You'll have to
> adapt the chunks rejected yourself.
>
> As for the otter, see the following thread:
> <http://cygwin.com/ml/cygwin/2003-04/msg01143.html>
> Igor
>
> On Sat, 12 Apr 2003, Cant wrote:
>
> > well i have .15 will it still work and how do i apply the patch?
> >
> > ps. whats with the otter?
> >
> > Uzytkownik "Igor Pechtchanski" <pechtcha@cs.nyu.edu> napisal w
wiadomosci
news:Pine.GSO.4.44.0304111954160.26381-200000@slinky.cs.nyu.edu...
> > > On Sat, 12 Apr 2003, Cant wrote:
> > >
> > > > just for fun i thought i would try and install screen... but for
some
> > > > reason when i go to make it, it says this:
> > > >
> > > > $ make
> > > > [snip]
> > > > gcc -c -I. -I.    -g -O2 misc.c
> > > > misc.c: In function `xsetenv':
> > > > misc.c:648: too few arguments to function `setenv'
> > > > make: *** [misc.o] Error 1
> > > > $
> > > >
> > > > any thoughts..?
> > >
> > > Which version of screen?  I've attached my patch for 3.9.13.
> > >
> > > > ---------------------------------------------------------------
> > > > brian AT nkjo DOT torun DOT pOlAND
> > > > You got questions? We got busy phones...
> > > > ---------------------------------------------------------------
> > >
> > > I like this one.  How about: "You got questions? We got a mean otter
with
> > > an AK-47..."? ;-)
> > > Igor
>
> --
> http://cs.nyu.edu/~pechtcha/
>       |\      _,,,---,,_ pechtcha@cs.nyu.edu
> ZZZzz /,`.-'`'    -.  ;-;;,_ igor@watson.ibm.com
>      |,4-  ) )-,_. ,\ (  `'-' Igor Pechtchanski
>     '---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!
>
> Knowledge is an unending adventure at the edge of uncertainty.
>   -- Leto II
>
>




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: screen

[Igor Pechtchanski]

Try "patch -p0 < patchfile" from the screen source directory.  Be
prepared, thought, that it might reject some chunks...  You'll have to
adapt the chunks rejected yourself.

As for the otter, see the following thread:
<http://cygwin.com/ml/cygwin/2003-04/msg01143.html>
	Igor

On Sat, 12 Apr 2003, Cant wrote:

> well i have .15 will it still work and how do i apply the patch?
>
> ps. whats with the otter?
>
> Uzytkownik "Igor Pechtchanski" <pechtcha@cs.nyu.edu> napisal w wiadomosci news:Pine.GSO.4.44.0304111954160.26381-200000@slinky.cs.nyu.edu...
> > On Sat, 12 Apr 2003, Cant wrote:
> >
> > > just for fun i thought i would try and install screen... but for some
> > > reason when i go to make it, it says this:
> > >
> > > $ make
> > > [snip]
> > > gcc -c -I. -I.    -g -O2 misc.c
> > > misc.c: In function `xsetenv':
> > > misc.c:648: too few arguments to function `setenv'
> > > make: *** [misc.o] Error 1
> > > $
> > >
> > > any thoughts..?
> >
> > Which version of screen?  I've attached my patch for 3.9.13.
> >
> > > ---------------------------------------------------------------
> > > brian AT nkjo DOT torun DOT pOlAND
> > > You got questions? We got busy phones...
> > > ---------------------------------------------------------------
> >
> > I like this one.  How about: "You got questions? We got a mean otter with
> > an AK-47..."? ;-)
> > Igor

-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Knowledge is an unending adventure at the edge of uncertainty.
  -- Leto II


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: screen

[Cant]

well i have .15 will it still work and how do i apply the patch?

ps. whats with the otter?

Uzytkownik "Igor Pechtchanski" <pechtcha@cs.nyu.edu> napisal w wiadomosci
news:Pine.GSO.4.44.0304111954160.26381-200000@slinky.cs.nyu.edu...
> On Sat, 12 Apr 2003, Cant wrote:
>
> > just for fun i thought i would try and install screen... but for some
> > reason when i go to make it, it says this:
> >
> > $ make
> > [snip]
> > gcc -c -I. -I.    -g -O2 misc.c
> > misc.c: In function `xsetenv':
> > misc.c:648: too few arguments to function `setenv'
> > make: *** [misc.o] Error 1
> > $
> >
> > any thoughts..?
>
> Which version of screen?  I've attached my patch for 3.9.13.
>
> > ---------------------------------------------------------------
> > brian AT nkjo DOT torun DOT pOlAND
> > You got questions? We got busy phones...
> > ---------------------------------------------------------------
>
> I like this one.  How about: "You got questions? We got a mean otter with
> an AK-47..."? ;-)
> Igor
> --
> http://cs.nyu.edu/~pechtcha/
>       |\      _,,,---,,_ pechtcha@cs.nyu.edu
> ZZZzz /,`.-'`'    -.  ;-;;,_ igor@watson.ibm.com
>      |,4-  ) )-,_. ,\ (  `'-' Igor Pechtchanski
>     '---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!
>
> Knowledge is an unending adventure at the edge of uncertainty.
>   -- Leto II
>


----------------------------------------------------------------------------
----


>




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: screen

[Igor Pechtchanski]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1041 bytes --]

On Sat, 12 Apr 2003, Cant wrote:

> just for fun i thought i would try and install screen... but for some
> reason when i go to make it, it says this:
>
> $ make
> [snip]
> gcc -c -I. -I.    -g -O2 misc.c
> misc.c: In function `xsetenv':
> misc.c:648: too few arguments to function `setenv'
> make: *** [misc.o] Error 1
> $
>
> any thoughts..?

Which version of screen?  I've attached my patch for 3.9.13.

> ---------------------------------------------------------------
> brian AT nkjo DOT torun DOT pOlAND
> You got questions? We got busy phones...
> ---------------------------------------------------------------

I like this one.  How about: "You got questions? We got a mean otter with
an AK-47..."? ;-)
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Knowledge is an unending adventure at the edge of uncertainty.
  -- Leto II

[-- Attachment #2: Type: TEXT/PLAIN, Size: 8048 bytes --]

diff -u -p -r orig/screen-3.9.13/configure.in ./configure.in
--- orig/screen-3.9.13/configure.in	2002-08-12 10:34:14.000000000 -0400
+++ ./configure.in	2002-09-09 16:39:27.000000000 -0400
@@ -270,7 +270,7 @@ dnl   Solaris seteuid doesn't change the
 dnl     multiuser screen sessions
 AC_CHECKING(seteuid)
 AC_TRY_LINK(,[
-#if defined(linux) || defined(NeXT) || defined(_AUX_SOURCE) || defined(AUX) || defined(ultrix) || (defined(sun) && defined(SVR4)) || defined(ISC) || defined(sony_news)
+#if defined(linux) || defined(NeXT) || defined(_AUX_SOURCE) || defined(AUX) || defined(ultrix) || (defined(sun) && defined(SVR4)) || defined(ISC) || defined(sony_news) || defined (__CYGWIN__)
 seteuid_is_broken(0);
 #else
 seteuid(0);
@@ -865,7 +865,7 @@ fi
 
 if test -z "$load" ; then
 AC_EGREP_CPP(yes,
-[#if defined(NeXT) || defined(apollo) || defined(linux)
+[#if defined(NeXT) || defined(apollo) || defined(linux) || defined (__CYGWIN__)
   yes;
 #endif
 ], load=1)
diff -u -p -r orig/screen-3.9.13/loadav.c ./loadav.c
--- orig/screen-3.9.13/loadav.c	2002-01-08 10:43:43.000000000 -0500
+++ ./loadav.c	2002-09-09 16:39:27.000000000 -0400
@@ -56,7 +56,7 @@ static int loadok;
 
 /***************************************************************/
 
-#if defined(linux) && !defined(LOADAV_DONE)
+#if (defined(linux) || defined (__CYGWIN__)) && !defined(LOADAV_DONE)
 #define LOADAV_DONE
 /*
  * This is the easy way. It relies in /proc being mounted.
@@ -110,7 +110,7 @@ GetLoadav()
     }
   return i;
 }
-#endif /* linux */
+#endif /* linux || __CYGWIN__ */
 
 /***************************************************************/
 
diff -u -p -r orig/screen-3.9.13/misc.c ./misc.c
--- orig/screen-3.9.13/misc.c	2002-08-29 10:47:36.000000000 -0400
+++ ./misc.c	2002-09-09 16:39:27.000000000 -0400
@@ -638,11 +638,11 @@ char *value;
    */
 # endif /* NEEDSETENV */
 #else /* USESETENV */
-# if defined(linux) || defined(__convex__) || (BSD >= 199103)
+# if defined(linux) || defined(__convex__) || (BSD >= 199103) || defined (__CYGWIN__)
   setenv(var, value, 1);
 # else
   setenv(var, value);
-# endif /* linux || convex || BSD >= 199103 */
+# endif /* linux || convex || BSD >= 199103 || __CYGWIN__ */
 #endif /* USESETENV */
 }
 
diff -u -p -r orig/screen-3.9.13/os.h ./os.h
--- orig/screen-3.9.13/os.h	2002-01-08 10:42:33.000000000 -0500
+++ ./os.h	2002-09-09 16:39:27.000000000 -0400
@@ -32,9 +32,9 @@
 # define hpux
 #endif
 
-#if defined(__bsdi__) || defined(__386BSD__) || defined(_CX_UX) || defined(hpux) || defined(_IBMR2) || defined(linux)
+#if defined(__bsdi__) || defined(__386BSD__) || defined(_CX_UX) || defined(hpux) || defined(_IBMR2) || defined(linux) || defined (__CYGWIN__)
 # include <signal.h>
-#endif /* __bsdi__ || __386BSD__ || _CX_UX || hpux || _IBMR2 || linux */
+#endif /* __bsdi__ || __386BSD__ || _CX_UX || hpux || _IBMR2 || linux || __CYGWIN__ */
 
 #ifdef ISC
 # ifdef ENAMETOOLONG
@@ -260,7 +260,7 @@ extern int errno;
 #endif
 
 #if defined(UTMPOK) || defined(BUGGYGETLOGIN)
-# if defined(SVR4) && !defined(DGUX) && !defined(__hpux) && !defined(linux)
+# if defined(SVR4) && !defined(DGUX) && !defined(__hpux) && !defined(linux) && !defined (__CYGWIN__)
 #  include <utmpx.h>
 #  define UTMPFILE	UTMPX_FILE
 #  define utmp		utmpx
@@ -411,7 +411,7 @@ extern int errno;
 #endif
 
 /* Geeeee, reverse it? */
-#if defined(SVR4) || (defined(SYSV) && defined(ISC)) || defined(_AIX) || defined(linux) || defined(ultrix) || defined(__386BSD__) || defined(__bsdi__) || defined(POSIX) || defined(NeXT)
+#if defined(SVR4) || (defined(SYSV) && defined(ISC)) || defined(_AIX) || defined(linux) || defined(ultrix) || defined(__386BSD__) || defined(__bsdi__) || defined(POSIX) || defined(NeXT) || defined (__CYGWIN__)
 # define SIGHASARG
 #endif
 
diff -u -p -r orig/screen-3.9.13/osdef.sh ./osdef.sh
--- orig/screen-3.9.13/osdef.sh	2001-06-18 13:08:15.000000000 -0400
+++ ./osdef.sh	2002-09-09 16:39:27.000000000 -0400
@@ -24,7 +24,7 @@ cat << EOF > osdef0.c
 #ifndef sun
 #include <sys/ioctl.h>
 #endif
-#ifdef linux
+#if defined(linux) || defined (__CYGWIN__)
 #include <string.h>
 #include <stdlib.h>
 #endif
diff -u -p -r orig/screen-3.9.13/pty.c ./pty.c
--- orig/screen-3.9.13/pty.c	2002-02-11 07:44:18.000000000 -0500
+++ ./pty.c	2002-09-09 16:39:27.000000000 -0400
@@ -37,7 +37,7 @@ RCS_ID("$Id: pty.c,v 1.6 1994/05/31 12:3
 #endif
 
 /* for solaris 2.1, Unixware (SVR4.2) and possibly others */
-#ifdef HAVE_SVR4_PTYS
+#if defined(HAVE_SVR4_PTYS) && !defined(__CYGWIN__)
 # include <sys/stropts.h>
 #endif
 
@@ -126,7 +126,7 @@ int f;
 {
   if (f < 0)
     return;
-#if defined(I_PUSH) && defined(HAVE_SVR4_PTYS) && !defined(sgi) && !defined(linux) && !defined(__osf__) && !defined(M_UNIX)
+#if defined(I_PUSH) && defined(HAVE_SVR4_PTYS) && !defined(sgi) && !defined(linux) && !defined(__osf__) && !defined(M_UNIX) && !defined (__CYGWIN__)
   if (ioctl(f, I_PUSH, "ptem"))
     Panic(errno, "InitPTY: cannot I_PUSH ptem");
   if (ioctl(f, I_PUSH, "ldterm"))
@@ -244,13 +244,13 @@ char **ttyn;
   register int f;
   char *m, *ptsname();
   int unlockpt __P((int)), grantpt __P((int));
-#if defined(HAVE_GETPT) && defined(linux)
+#if defined(HAVE_GETPT) && (defined(linux) || defined (__CYGWIN__))
   int getpt __P((void));
 #endif
   sigret_t (*sigcld)__P(SIGPROTOARG);
 
   strcpy(PtyName, "/dev/ptmx");
-#if defined(HAVE_GETPT) && defined(linux)
+#if defined(HAVE_GETPT) && (defined(linux) || defined (__CYGWIN__))
   if ((f = getpt()) == -1)
 #else
   if ((f = open(PtyName, O_RDWR | O_NOCTTY)) == -1)
diff -u -p -r orig/screen-3.9.13/screen.c ./screen.c
--- orig/screen-3.9.13/screen.c	2002-08-29 06:14:20.000000000 -0400
+++ ./screen.c	2002-09-09 17:53:28.000000000 -0400
@@ -984,8 +984,10 @@ char **av;
 	      n = (eff_uid == 0 && (real_uid || (st.st_mode & 0775) != 0775)) ? 0755 :
 	          (eff_gid == st.st_gid && eff_gid != real_gid) ? 0775 :
 		  0777;
+#if !defined(__CYGWIN__)
 	      if ((st.st_mode & 0777) != n)
 		Panic(0, "Directory '%s' must have mode %03o.", SockDir, n);
+#endif
 	    }
 	  sprintf(SockPath, "%s/S-%s", SockDir, LoginName);
 	  if (access(SockPath, F_OK))
@@ -1015,8 +1017,10 @@ char **av;
       if (st.st_uid != real_uid)
 	Panic(0, "You are not the owner of %s.", SockPath);
     }
+#if !defined(__CYGWIN__)
   if ((st.st_mode & 0777) != 0700)
     Panic(0, "Directory %s must have mode 700.", SockPath);
+#endif
   if (SockMatch && index(SockMatch, '/'))
     Panic(0, "Bad session name '%s'", SockMatch);
   SockName = SockPath + strlen(SockPath) + 1;
diff -u -p -r orig/screen-3.9.13/utmp.c ./utmp.c
--- orig/screen-3.9.13/utmp.c	2002-08-22 15:26:34.000000000 -0400
+++ ./utmp.c	2002-09-09 16:39:27.000000000 -0400
@@ -93,7 +93,7 @@ static void endutent __P((void));
 static int  initutmp __P((void));
 static void setutent __P((void));
 #endif
-#if defined(linux) && defined(GETUTENT)
+#if (defined(linux) || defined (__CYGWIN__)) && defined(GETUTENT)
 static struct utmp *xpututline __P((struct utmp *utmp));
 # define pututline xpututline
 #endif
@@ -593,7 +593,7 @@ makedead(u)
 struct utmp *u;
 {
   u->ut_type = DEAD_PROCESS;
-#if !defined(linux) || defined(EMPTY)
+#if (!defined(linux) && !defined (__CYGWIN__)) || defined(EMPTY)
   u->ut_exit.e_termination = 0;
   u->ut_exit.e_exit = 0;
 #endif
@@ -611,7 +611,7 @@ int pid;
   u->ut_type = USER_PROCESS;
   strncpy(u->ut_user, user, sizeof(u->ut_user));
   /* Now the tricky part... guess ut_id */
-#if defined(sgi) || defined(linux)
+#if defined(sgi) || defined(linux) || defined (__CYGWIN__)
   strncpy(u->ut_id, line + 3, sizeof(u->ut_id));
 #else /* sgi */
 # ifdef _IBMR2
@@ -862,7 +862,7 @@ getlogin()
 }
 # endif /* BUGGYGETLOGIN */
 
-#if defined(linux) && defined(GETUTENT)
+#if (defined(linux) || defined (__CYGWIN__)) && defined(GETUTENT)
 # undef pututline
 
 /* aargh, linux' pututline returns void! */

[-- Attachment #3: Type: text/plain, Size: 214 bytes --]

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

screen

[Cant]

just for fun i thought i would try and install screen... but for some reason
when i go to make it, it says this:

$ make
CPP="gcc -E " srcdir=. sh ./osdef.sh
AWK=gawk CC="gcc -g -O2" srcdir=. sh ./comm.sh
AWK=gawk srcdir=. sh ./term.sh
gcc -c -I. -I.    -g -O2 screen.c
gcc -c -I. -I.    -g -O2 ansi.c
gcc -c -I. -I.    -g -O2 fileio.c
gcc -c -I. -I.    -g -O2 mark.c
gcc -c -I. -I.    -g -O2 misc.c
misc.c: In function `xsetenv':
misc.c:648: too few arguments to function `setenv'
make: *** [misc.o] Error 1
$

any thoughts..?

--
---------------------------------------------------------------
brian AT nkjo DOT torun DOT pOlAND
You got questions? We got busy phones...
---------------------------------------------------------------




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Screen

[cv23iuy]

 SUBLIMINALLY ENTICE ANY WOMAN TO BE YOURS!
              GUARANTEED.

We know you may be skeptical, but if you're not totally 
satisfied with your sex life and who you're dating you owe 
it to yourself to visit our web site (your choice of 
ENGLISH or ESPANOL) at http://208.166.10.22/ and learn 
how the power of subliminal mind control can change your 
life. It is simply a fact that sexual impulses can be 
awakened and greatly intensified by using subliminal 
commands. We guarantee it!

But, most subliminal enticement tapes don't work. Confused? 
Take 1 minute, go to  http://208.166.10.22/ and read the 
section entitled "THE NUMBER 1 REASON OUR TAPES WORK 
AND THEIRS DON'T!" to find out why.  If nothing else, 
you'll get a good laugh at how downright silly some other 
tapes are.

  EVERYTHING (AND WE MEAN EVERYTHING!) TO GAIN 
              AND NOTHING TO LOSE!

We're so sure that OUR tapes work that every one comes with 
a 100% MONEY BACK GUARANTEE!

Now that you know about the hottest tapes on the Internet, you 
have no excuse not to be successful with any woman you choose. 
If you don't get the facts, you are cheating yourself out of 
HAPPINESS, ROMANCE, GREAT SEX and the TIME OF YOUR LIFE!

Click here http://208.166.10.22/

Millennium Creations, LLC
520 Washington Blvd., Suite 287
Marina Del Rey, Ca. 90292
310-281-6737

To be remove from future mailings, reply to:  
inside2000@AILJ0BAJLJI0D.NET with remove in the subject.
Please understand that our system has filters and any 
files larger than 2K, foul language, multiple emails 
and/or attachments within the email will automatically 
delete your email without removal from our database.  
Thank you.




 
 
 
 
 
 
 
 
 
 
 
 
 
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".